CISCO-DEVICE-EXCEPTION-REPORTING-MIB.mib object view, vendor Cisco
Introduction
Most network devices and programs ship with so-called MIB files to describe the parameters and meanings (i.e.: friendly names) which are available for monitoring via SNMP.
ActiveXperts Network Monitor 2024 can import vendor-specific MIB files, so it can be used to monitor specific OID's (Object Identifiers).
This way, you can monitor your devices, computers, etc. by selecting your relevant OID's by name.
ActiveXperts Network Monitor 2024 can import MIB file CISCO-DEVICE-EXCEPTION-REPORTING-MIB and use it to monitor vendor specific OID's.
CISCO-DEVICE-EXCEPTION-REPORTING-MIB file content
Object view of CISCO-DEVICE-EXCEPTION-REPORTING-MIB:
| Scalar Object |
| cderMaxExceptionRecords |
.1.3.6.1.4.1.9.9.224.1.1.1 |
|
The maximun number of records to keep in
cderExceptionTable. New records will replace
the old records on a first-in-first-out
basis.
A value of 0 indicates no history will be
retained.
|
| cderNotificationEnabled |
.1.3.6.1.4.1.9.9.224.1.1.2 |
|
Enable or disable exception notification
via SNMP.
|
| cderNotificationsSent |
.1.3.6.1.4.1.9.9.224.1.1.3 |
|
The number of cderMonitoredExceptionEvent
events.
If a NMS is receiving notifications,
it can periodically poll this object
to find out if any notifications were
missed. In that case it could poll
cderExceptionTable to find out missing
exceptions.
|
| cderNotificationsDropped |
.1.3.6.1.4.1.9.9.224.1.1.4 |
|
The number of notifications dropped from the
cderExceptionTable table.
If the difference between two consecutive
polls of this object is greater than
cderMaxExceptionRecords, then it indicates
the NMS will not be able to find missing
exceptions. The solution is to either poll
the cderExceptionTable more frequently
or increase the size of the cderExceptionTable
by setting cderMaxExceptionRecords.
|
| cderExceptionEntry |
.1.3.6.1.4.1.9.9.224.1.1.5.1 |
|
An entry containing information about an
exception.
|
| Tabular Object |
| cderExcepTableIndex |
.1.3.6.1.4.1.9.9.224.1.1.5.1.1 |
|
An monotonically increasing number for
the sole purpose of indexing entries. When
it reaches maximum value, the agent sets
it back to 1.
|
| cderExcepId |
.1.3.6.1.4.1.9.9.224.1.1.5.1.2 |
|
Identification for this exception. This
object should uniquely identify the
exception.
|
| cderExcepHostAddressType |
.1.3.6.1.4.1.9.9.224.1.1.5.1.3 |
|
Represents the type of address stored in
cderExcepHostAddress.
|
| cderExcepHostAddress |
.1.3.6.1.4.1.9.9.224.1.1.5.1.4 |
|
Host device address where the exception
happened.
|
| cderExcepPriorityDescription |
.1.3.6.1.4.1.9.9.224.1.1.5.1.5 |
|
A string that tells the system administrator
about the priority of this exception.
This string is provided to the snmp agent
by the reporting service(s) which could be
any services or applications on the device.
The receiving NMS of this object should
understand the string in order to utilize this
object.
|
| cderExcepTime |
.1.3.6.1.4.1.9.9.224.1.1.5.1.6 |
|
Timestamp when the exception happened.
|
| cderExcepData |
.1.3.6.1.4.1.9.9.224.1.1.5.1.7 |
|
More information about the exception that
the reporting service(s) want to convey to
the NMS.
The receiving NMS should understand the
meaning of this object value in order to
use it.
|
| cderExcepReportedBy |
.1.3.6.1.4.1.9.9.224.1.1.5.1.8 |
|
Name of the reporting service, or process,
or other component of the device that
reports this exception.
|
| Table |
| cderExceptionTable |
.1.3.6.1.4.1.9.9.224.1.1.5 |
|
This table keeps an history of exceptions
found.
|
| Trap |
| cderMonitoredExceptionEvent |
.1.3.6.1.4.1.9.9.224.2.0.1 |
|
This notification is sent when an exception
is detected on the managed device. This
notification can be enabled or disabled via
cderNotificationEnable.
|
| Object Identifier |
| ciscoDevExcepReportMIB |
.1.3.6.1.4.1.9.9.224 |
|
This mib defines the SNMP objects to report
exceptions to north-bound NMS.
The devices implementing this MIB monitor
the status of hardware and software services, and
report any exceptions regarding these components.
These hardware and software services could
belong to the monitoring devices or other managed
devices.
An exception is something abnormal that the system
administrators should pay attention to. The criteria
for what is an exception could vary by system
and should be defined by the system administrators.
Certain NM devices or applications may have
pre-defined exceptions.
This MIB does not try to define exceptions. But
rather it defines SNMP objects for devices to
use SNMP notification as an exception reporting
mechanism. Exceptions may be pre-defined or defined
through other device management interface such as
CLI, GUI, or HTTP.
|
| ciscoDevExcepReportMIBObjects |
.1.3.6.1.4.1.9.9.224.1 |
| cderExceptionData |
.1.3.6.1.4.1.9.9.224.1.1 |
| cderMIBNotifPrefix |
.1.3.6.1.4.1.9.9.224.2 |
| cderMIBNotifications |
.1.3.6.1.4.1.9.9.224.2.0 |
| ciscoDEReportMIBConformance |
.1.3.6.1.4.1.9.9.224.3 |
| ciscoDEReportMIBCompliances |
.1.3.6.1.4.1.9.9.224.3.1 |
| ciscoDEReportMIBGroups |
.1.3.6.1.4.1.9.9.224.3.2 |
| Group |
| ciscoDERExceptionDataGroup |
.1.3.6.1.4.1.9.9.224.3.2.1 |
|
A collection of objects that enable the
exception notification for monitored
exceptions of network elements.
|
| ciscoDERExceptionGroup |
.1.3.6.1.4.1.9.9.224.3.2.2 |
|
A collection of the monitored
exception events.
|
