MIBs Depot

CISCO-IF-MONITOR-NOTIF-MIB

Last updated
2002-10-11 00:00
Organization
Cisco Systems, Inc.
Revisions
2002-10-11 00:00
Namespace
cisco
Source file
CISCO-IF-MONITOR-NOTIF-MIB
Digest
sha256:8b5a16b87ee67c688fecacdb4fe6ff61a0f82ee49bda662fb9189242a46ab130

Description

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.

Contact

Cisco Systems Customer Service Postal: 170 W Tasman Drive San Jose, CA 95134 USA Tel: +1 800 553-NETS E-mail: cs-snmp@cisco.com

Imports

FromSymbols
CISCO-SMIciscoExperiment
IF-MIBifIndex
SNMPv2-CONFMODULE-COMPLIANCE, NOTIFICATION-GROUP, OBJECT-GROUP
SNMPv2-SMIMODULE-IDENTITY, NOTIFICATION-TYPE, OBJECT-IDENTITY, OBJECT-TYPE, Unsigned32, iso
SNMPv2-TCDisplayString, TEXTUAL-CONVENTION, TimeStamp

Imported by

Nothing in this corpus imports this module.

Load order

Every file a consumer needs in order to load this module, dependencies first.

CISCO-IF-MONITOR-NOTIF-MIB
CISCO-SMI
IANAifType-MIB
IF-MIB
SNMPv2-CONF
SNMPv2-MIB
SNMPv2-SMI
SNMPv2-TC

Objects

NameOIDSyntaxAccessStatus
cIfMonNotifMIBNotifications
OBJECT-IDENTITY
1.3.6.1.4.1.9.10.999.0
cIfMonNotifMIBObjects
OBJECT-IDENTITY
1.3.6.1.4.1.9.10.999.1
cIfMonNotifCount
OBJECT-TYPE
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.
1.3.6.1.4.1.9.10.999.1.1Unsigned32 (1..4294967295)read-onlycurrent
cIfMonNotifTable
OBJECT-TYPE
This table contains information about the last notification that was sent for a particular interface.
1.3.6.1.4.1.9.10.999.1.2not-accessiblecurrent
cIfMonNotifEntry
OBJECT-TYPE
Each entry contains information about the last notification sent for this interface.
1.3.6.1.4.1.9.10.999.1.2.1not-accessiblecurrent
cIfMonNotifLastChange
OBJECT-TYPE
This object specifies the value of sysUpTime at the last time a notification was sent for this interface.
1.3.6.1.4.1.9.10.999.1.2.1.1TimeStampread-onlycurrent
cIfMonNotifSeverity
OBJECT-TYPE
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.
1.3.6.1.4.1.9.10.999.1.2.1.2INTEGER {red(1), yellow(2)}read-onlycurrent
cIfMonNotifCause
OBJECT-TYPE
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.
1.3.6.1.4.1.9.10.999.1.2.1.3INTEGER {aborts(1), crc(2), drops(3), flaps(4), frame-reject(5), runts(6), sabm(7), frmr(8), disc(9)}read-onlycurrent
cIfMonNotifValue
OBJECT-TYPE
The value of the link errors over an interval that reached/exceeded the threshold, causing a severe condition.
1.3.6.1.4.1.9.10.999.1.2.1.4Unsigned32 (1..4294967295)read-onlycurrent
cIfMonNotifThreshold
OBJECT-TYPE
The threshold which was reached/exceeded by the link errors over an interval, causing a severe condition.
1.3.6.1.4.1.9.10.999.1.2.1.5Unsigned32 (1..100000)read-onlycurrent
cIfMonNotifInterval
OBJECT-TYPE
The interval over which the link errors reached/exceeded the threshold, causing a severe condition.
1.3.6.1.4.1.9.10.999.1.2.1.6Unsigned32 (5..600)read-onlycurrent
cIfMonNotifMIBConformance
OBJECT-IDENTITY
1.3.6.1.4.1.9.10.999.2
cIfMonNotifMIBCompliances
OBJECT-IDENTITY
1.3.6.1.4.1.9.10.999.2.1
cIfMonNotifMIBGroups
OBJECT-IDENTITY
1.3.6.1.4.1.9.10.999.2.2

Notifications

NameOIDStatus
cIfMonNotifEvent
NOTIFICATION-TYPE
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.
1.3.6.1.4.1.9.10.999.0.1current

Conformance

NameOIDStatus
cIfMonNotifMIBCompliance
MODULE-COMPLIANCE
The compliance statement for entities which implement the Cisco Interface Monitor Notification MIB
1.3.6.1.4.1.9.10.999.2.1.1current
cIfMonNotifObjectGroup
OBJECT-GROUP
A collection of mandatory managed objects for sending notifications when certain errors over an interval have reached/exceeded a threshold, causing a severe condition.
1.3.6.1.4.1.9.10.999.2.2.1current
cIfMonNotifEventGroup
NOTIFICATION-GROUP
A collection of notifications generated on an interface when certain errors over an interval have reached/exceeded a threshold, causing a severe condition.
1.3.6.1.4.1.9.10.999.2.2.2current