CISCO-DEVICE-EXCEPTION-REPORTING-MIB

All MIBs › CISCO-DEVICE-EXCEPTION-REPORTING-MIB

Organization: Cisco Systems, Inc.

Last Updated: 2001-08-14

Category: Alarm and Event Management, Cisco Devices

Description: Manages device exception event reporting on Cisco equipment, configuring thresholds and forwarding rules for anomaly notifications.

Start monitoring vendor-neutral, standards-based MIB, any SNMPv3-capable network device (SNMP engine identity/boot/clock status) with a free 30-day trial of IPNetwork Monitor. Import MIBs, browse SNMP OIDs, create custom SNMP monitors, configure alerts, and monitor any SNMP-enabled network device from a single console.

What Is CISCO-DEVICE-EXCEPTION-REPORTING-MIB?

CISCO-DEVICE-EXCEPTION-REPORTING-MIB provides a generic mechanism on Cisco devices for reporting abnormal hardware and software exceptions to a northbound network management system. It exposes a table of exception records with identifiers, priority/description, source host, and timestamp, alongside counters for notifications sent and dropped, and global controls for maximum records retained and notification enablement. This MIB is explicitly designed for hardware and software status monitoring: it is meant to surface any abnormal condition the device or a monitored peer device detects, and cderNotificationsDropped reveals when the exception-reporting pipeline itself is overwhelmed and losing events. It is a general-purpose Cisco framework MIB that can carry exceptions sourced from many other subsystems/MIBs on the device. It is deployed across Cisco platforms as a supplementary fault-reporting channel alongside standard SNMP traps and syslog. Engineers can download the CISCO-DEVICE-EXCEPTION-REPORTING-MIB file directly to load it into their MIB browser.

IPNetwork Monitor allows you to monitor SNMP objects defined in CISCO-DEVICE-EXCEPTION-REPORTING-MIB. Use the built-in SNMP Monitoring Browser to explore available variables, view their current values and descriptions, and select the objects you want to monitor. You can then create SNMP monitors, configure thresholds, and receive alerts when monitored values change.

Supported Devices

Cisco router
Cisco switch

Monitoring Examples

An admin would poll cderExceptionTable, keyed by cderExcepTableIndex, reading cderExcepId, cderExcepPriorityDescription, and cderExcepTime to review recent abnormal hardware/software events reported by the device. Watching cderNotificationsDropped rising alongside cderNotificationsSent indicates the device is generating more exceptions than it can forward to the NMS, meaning some events are being lost. A steady increase in cderMaxExceptionRecords utilization suggests the exception buffer is filling faster than it is being drained.

What Can Be Monitored

logged exception records
exception priority/description
notifications sent vs dropped
exception source host address
exception timestamp

Imported Objects

From CISCO-SMI

ciscoMgmt

OBJECT-IDENTITY

From INET-ADDRESS-MIB

InetAddress
InetAddressType

From SNMP-FRAMEWORK-MIB

SnmpAdminString

From SNMPv2-CONF

MODULE-COMPLIANCE
NOTIFICATION-GROUP
OBJECT-GROUP

From SNMPv2-SMI

Counter32
MODULE-IDENTITY
NOTIFICATION-TYPE
OBJECT-TYPE
Unsigned32

From SNMPv2-TC

TimeStamp
TruthValue

How to Use in IPNetwork Monitor

Example using cderNotificationsSent OID:

Select a Cisco router or switch (exception reporting) as the target host to create a monitor — the SNMP service should be up and running on it. Click New Monitor, then check SNMP Custom on the Favorites tab, click Next, and confirm the host. On the next page, click Select... to open the built-in SNMP MIB Browser and type cderNotificationsSent into the Find box to locate it in the OID tree, then select it and click OK. 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. On the monitor's Main parameters page you can set the target's SNMP port (default 161), credentials, polling interval, and other settings — see the SNMP Monitor help for details. On the State conditions and Alerting tabs, configure when the monitor should change state and trigger an alert; since this is a Counter32-type OID, Value bounds is the most useful condition here — trigger an alert if the counter increases sharply between polls relative to its normal baseline, since an unexpected spike often reflects a real change in traffic or activity. Click Finish to create the monitor; you can adjust any parameter later.

OIDs

OID symbolic	OID numeric	Type	Access	Description
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
U32 cderMaxExceptionRecords	1.3.6.1.4.1.9.9.224.1.1.1	Unsigned32	read-write	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.
T/F cderNotificationEnabled	1.3.6.1.4.1.9.9.224.1.1.2	TruthValue	read-write	Enable or disable exception notification via SNMP.
C32 cderNotificationsSentEx	1.3.6.1.4.1.9.9.224.1.1.3	Counter32	read-only	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.
C32 cderNotificationsDropped	1.3.6.1.4.1.9.9.224.1.1.4	Counter32	read-only	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.
cderExceptionTable	1.3.6.1.4.1.9.9.224.1.1.5		not-accessible	This table keeps an history of exceptions found.
cderExceptionEntry	1.3.6.1.4.1.9.9.224.1.1.5.1		not-accessible	An entry containing information about an exception.
U32 cderExcepTableIndex	1.3.6.1.4.1.9.9.224.1.1.5.1.1	Unsigned32	not-accessible	An monotonically increasing number for the sole purpose of indexing entries. When it reaches maximum value, the agent sets it back to 1.
STR cderExcepId	1.3.6.1.4.1.9.9.224.1.1.5.1.2	SnmpAdminString	read-only	Identification for this exception. This object should uniquely identify the exception.
IPt cderExcepHostAddressType	1.3.6.1.4.1.9.9.224.1.1.5.1.3	InetAddressType	read-only	Represents the type of address stored in cderExcepHostAddress.
IP cderExcepHostAddress	1.3.6.1.4.1.9.9.224.1.1.5.1.4	InetAddress	read-only	Host device address where the exception happened.
STR cderExcepPriorityDescription	1.3.6.1.4.1.9.9.224.1.1.5.1.5	SnmpAdminString	read-only	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.
TIM cderExcepTime	1.3.6.1.4.1.9.9.224.1.1.5.1.6	TimeStamp	read-only	Timestamp when the exception happened.
OCT cderExcepData	1.3.6.1.4.1.9.9.224.1.1.5.1.7	OCTET STRING	read-only	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.
STR cderExcepReportedBy	1.3.6.1.4.1.9.9.224.1.1.5.1.8	SnmpAdminString	read-only	Name of the reporting service, or process, or other component of the device that reports this exception.
cderMIBNotifPrefix	1.3.6.1.4.1.9.9.224.2
cderMIBNotifications	1.3.6.1.4.1.9.9.224.2.0
NTF 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.
ciscoDEReportMIBConformance	1.3.6.1.4.1.9.9.224.3
ciscoDEReportMIBCompliances	1.3.6.1.4.1.9.9.224.3.1
ciscoDEReportMIBCompliance	1.3.6.1.4.1.9.9.224.3.1.1			The compliance statement for entities which implement the CISCO-DEVICE-EXCEPTION-REPORTING-MIB.
ciscoDEReportMIBGroups	1.3.6.1.4.1.9.9.224.3.2
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.

RFC description

Provides SNMP notification framework for reporting hardware and software exceptions on Cisco devices.

Start monitoring Cisco routers and switches (exception reporting) with a free 30-day trial of IPNetwork Monitor. Import MIBs, browse SNMP OIDs, create custom SNMP monitors, configure alerts, and monitor any SNMP-enabled network device from a single console.

Download CISCO-DEVICE-EXCEPTION-REPORTING-MIB