CISCO-DEVICE-EXCEPTION-REPORTING-MIB
AI MIB Summary
The CISCO-DEVICE-EXCEPTION-REPORTING-MIB enables Cisco network devices to generate SNMP notifications for abnormal hardware and software service states, facilitating the transmission of administrator-defined or pre-configured exceptions to northbound Network Management Systems. This module serves as a standardized reporting mechanism for critical system anomalies, allowing external management applications to ingest and process alerts regarding component failures or service disruptions without defining the specific exception criteria itself.
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.
Main OID:
ciscoDevExcepReportMIB.1.3.6.1.4.1.9.9.224
23
Objects
Active
Status
6
Dependencies
Imported Objects
Objects
23 total| Object Name |
|---|
ciscoDevExcepReportMIBThis 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. MODULE-IDENTITY .1.3.6.1.4.1.9.9.224 |
ciscoDevExcepReportMIBObjects OBJECT IDENTIFIER .1.3.6.1.4.1.9.9.224.1 |
cderExceptionData OBJECT IDENTIFIER .1.3.6.1.4.1.9.9.224.1.1 |
cderMaxExceptionRecordsThe 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.rw Unsigned32 .1.3.6.1.4.1.9.9.224.1.1.1 |
cderNotificationEnabledEnable or disable exception notification
via SNMP.rw TruthValue (SNMPv2-TC) .1.3.6.1.4.1.9.9.224.1.1.2 |
cderNotificationsSentThe 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.ro Counter32 .1.3.6.1.4.1.9.9.224.1.1.3 |
cderNotificationsDroppedThe 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.ro Counter32 .1.3.6.1.4.1.9.9.224.1.1.4 |
cderExceptionTableThis table keeps an history of exceptions
found. SEQUENCE OF CderExceptionEntry .1.3.6.1.4.1.9.9.224.1.1.5 |
cderExceptionEntryAn entry containing information about an
exception. CderExceptionEntry .1.3.6.1.4.1.9.9.224.1.1.5.1 |
cderExcepTableIndexAn monotonically increasing number for
the sole purpose of indexing entries. When
it reaches maximum value, the agent sets
it back to 1. Unsigned32 .1.3.6.1.4.1.9.9.224.1.1.5.1.1 |
cderExcepIdIdentification for this exception. This
object should uniquely identify the
exception.ro SnmpAdminString .1.3.6.1.4.1.9.9.224.1.1.5.1.2 |
cderExcepHostAddressTypeRepresents the type of address stored in
cderExcepHostAddress.ro InetAddressType (INET-ADDRESS-MIB) .1.3.6.1.4.1.9.9.224.1.1.5.1.3 |
cderExcepHostAddressHost device address where the exception
happened.ro InetAddress (INET-ADDRESS-MIB) .1.3.6.1.4.1.9.9.224.1.1.5.1.4 |
cderExcepPriorityDescriptionA 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.ro SnmpAdminString .1.3.6.1.4.1.9.9.224.1.1.5.1.5 |
cderExcepTimeTimestamp when the exception happened.ro TimeStamp (SNMPv2-TC) .1.3.6.1.4.1.9.9.224.1.1.5.1.6 |
cderExcepDataMore 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.ro OCTET STRING .1.3.6.1.4.1.9.9.224.1.1.5.1.7 |
cderExcepReportedByName of the reporting service, or process,
or other component of the device that
reports this exception.ro SnmpAdminString (SNMP-FRAMEWORK-MIB) .1.3.6.1.4.1.9.9.224.1.1.5.1.8 |
cderMIBNotifPrefix OBJECT IDENTIFIER .1.3.6.1.4.1.9.9.224.2 |
cderMIBNotifications OBJECT IDENTIFIER .1.3.6.1.4.1.9.9.224.2.0 |
cderMonitoredExceptionEventThis notification is sent when an exception
is detected on the managed device. This
notification can be enabled or disabled via
cderNotificationEnable. NOTIFICATION-TYPE .1.3.6.1.4.1.9.9.224.2.0.1 |
ciscoDEReportMIBConformance OBJECT IDENTIFIER .1.3.6.1.4.1.9.9.224.3 |
ciscoDEReportMIBCompliances OBJECT IDENTIFIER .1.3.6.1.4.1.9.9.224.3.1 |
ciscoDEReportMIBGroups OBJECT IDENTIFIER .1.3.6.1.4.1.9.9.224.3.2 |