CISCO-IF-MONITOR-NOTIF-MIB: View SNMP OID List / Download MIB

VENDOR: CISCO


 Home MIB: CISCO-IF-MONITOR-NOTIF-MIB
Download as:   
SNMPv2-CONF, IF-MIB, SNMPv2-SMI, CISCO-SMI, SNMPv2-TC

Download standard MIB format if you are planning to load a MIB file into some system (OS, Zabbix, PRTG ...) or view it with a MIB browser. CSV is more suitable for analyzing and viewing OID' and other MIB objects in excel. JSON and YAML formats are usually used in programing even though some systems can use MIB in YAML format (like Logstash).
Keep in mind that standard MIB files can be successfully loaded by systems and programs only if all the required MIB's from the "Imports" section are already loaded.
The tree-like SNMP object navigator requires no explanations because it is very simple to use. And if you stumbled on this MIB from Google note that you can always go back to the home page if you need to perform another MIB or OID lookup.


Object Name OID Type Access Info
 ciscoIfMonitorNotifMIB 1.3.6.1.4.1.9.10.999
Interface Monitor Notification MIB This MIB module defines the objects for sending notifications when certain errors over an interval have reached/exceeded a threshold, causing a severe condition.
         cIfMonNotifMIBNotifications 1.3.6.1.4.1.9.10.999.0
             cIfMonNotifEvent 1.3.6.1.4.1.9.10.999.0.1
The agent generates this notification when certain errors over an interval have reached/exceeded a threshold, causing a severe condition. The SNMP Notifications can be logged using the NOTIFICATION-LOG-MIB.
         cIfMonNotifMIBObjects 1.3.6.1.4.1.9.10.999.1
             cIfMonNotifCount 1.3.6.1.4.1.9.10.999.1.1 unsigned32 read-only
This object will be incremented and included in the varbind list of the cIfMonNotifEvent notification. This object is guaranteed to increase once per notification originated from the MIB. NMSes should track the value of this object received in each notification. If the difference in the value of this object across two consecutive notifications is more than one, a notification has been delayed, dropped, lost or routed out of sequence. The only reliable way to recover such notifications is via the NOTIFICATION-LOG-MIB. The NMS should preferably configure/create a log in the NOTIFICATION-LOG-MIB to capture cIfMonNotifEvent notifications. If possible, a named log should be created. When a notification loss is detected, the NMS can then poll the log to determine which notification was lost. The reader can look up RFC 3014 for more information on the NOTIFICATION-LOG-MIB. In addition to tracking the value of this object in each notification, the NMS should periodically poll this object. If the polled value of this object is two or more counts greater than the value from the last received notification, a notification has likely been dropped, and the NMS must use the NOTIFICATION-LOG-MIB to poll for the dropped notification.
             cIfMonNotifTable 1.3.6.1.4.1.9.10.999.1.2 no-access
This table contains information about the last notification that was sent for a particular interface.
                 cIfMonNotifEntry 1.3.6.1.4.1.9.10.999.1.2.1 no-access
Each entry contains information about the last notification sent for this interface.
                     cIfMonNotifLastChange 1.3.6.1.4.1.9.10.999.1.2.1.1 timestamp read-only
This object specifies the value of sysUpTime at the last time a notification was sent for this interface.
                     cIfMonNotifSeverity 1.3.6.1.4.1.9.10.999.1.2.1.2 integer read-only
The severity of the condition on the link when the notification is sent. A smaller enumerated integer value indicates that the exceeded condition is more severe. When a red severity notification is sent, it signifies that a severe event has occured, in which certain errors over an interval have reached/exceeded a high threshold . When a yellow severity notification is sent it signifies that an event has occured, in which certain errors over an interval have reached/exceeded a low threshold. Enumeration: 'yellow': 2, 'red': 1.
                     cIfMonNotifCause 1.3.6.1.4.1.9.10.999.1.2.1.3 integer read-only
The link errors over an interval which caused the severe condition on the link. aborts number of packet aborted crc number of crc errors in packets received drops number of input packet dropped flaps number of link flaps frame-reject number of HDLC frames rejected runts number of frame runts dropped (X.25 Parameters) sabm number of SABMS commands received frmr number of Frame Rejects disc number of disconnect command received. Enumeration: 'frmr': 8, 'sabm': 7, 'crc': 2, 'disc': 9, 'runts': 6, 'aborts': 1, 'drops': 3, 'frame-reject': 5, 'flaps': 4.
                     cIfMonNotifValue 1.3.6.1.4.1.9.10.999.1.2.1.4 unsigned32 read-only
The value of the link errors over an interval that reached/exceeded the threshold, causing a severe condition.
                     cIfMonNotifThreshold 1.3.6.1.4.1.9.10.999.1.2.1.5 unsigned32 read-only
The threshold which was reached/exceeded by the link errors over an interval, causing a severe condition.
                     cIfMonNotifInterval 1.3.6.1.4.1.9.10.999.1.2.1.6 unsigned32 read-only
The interval over which the link errors reached/exceeded the threshold, causing a severe condition.
         cIfMonNotifMIBConformance 1.3.6.1.4.1.9.10.999.2
             cIfMonNotifMIBCompliances 1.3.6.1.4.1.9.10.999.2.1
                 cIfMonNotifMIBCompliance 1.3.6.1.4.1.9.10.999.2.1.1
The compliance statement for entities which implement the Cisco Interface Monitor Notification MIB
             cIfMonNotifMIBGroups 1.3.6.1.4.1.9.10.999.2.2
                 cIfMonNotifObjectGroup 1.3.6.1.4.1.9.10.999.2.2.1
A collection of mandatory managed objects for sending notifications when certain errors over an interval have reached/exceeded a threshold, causing a severe condition.
                 cIfMonNotifEventGroup 1.3.6.1.4.1.9.10.999.2.2.2
A collection of notifications generated on an interface when certain errors over an interval have reached/exceeded a threshold, causing a severe condition.