
CISCO-DEVICE-EXCEPTION-REPORTING-MIB
File:
CISCO-DEVICE-EXCEPTION-REPORTING-MIB.mib (10595 bytes)
Imported modules
Imported symbols
Defined Objects
| 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. |
| MODULE-IDENTITY |
|
|
|
| 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. |
| OBJECT-TYPE |
|
|
|
| |
Unsigned32 |
0..1024 |
|
| 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. |
| OBJECT-TYPE |
|
|
|
| |
Counter32 |
|
|
| 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. |
| OBJECT-TYPE |
|
|
|
| |
Counter32 |
|
|
| cderExceptionEntry |
1.3.6.1.4.1.9.9.224.1.1.5.1 |
| An entry containing information about an exception. |
| OBJECT-TYPE |
|
|
|
| |
CderExceptionEntry |
|
|
| 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. |
| OBJECT-TYPE |
|
|
|
| |
Unsigned32 |
1..4294967295 |
|
| 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. |
| OBJECT-TYPE |
|
|
|
| |
SnmpAdminString |
SIZE(1..64) |
|
| 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. |
| OBJECT-TYPE |
|
|
|
| |
OCTET STRING |
SIZE(0..1024) |
|
Defined Objects
| CderExceptionEntry |
|
| SEQUENCE |
|
|
|
| |
Unsigned32 as cderExcepTableIndex |
|
|
| |
SnmpAdminString as cderExcepId |
|
|
| |
InetAddressType as cderExcepHostAddressType |
|
|
| |
InetAddress as cderExcepHostAddress |
|
|
| |
SnmpAdminString as cderExcepPriorityDescription |
|
|
| |
TimeStamp as cderExcepTime |
|
|
| |
OCTET STRING as cderExcepData |
|
|
| |
SnmpAdminString as cderExcepReportedBy |
|
|