CISCO-IF-MONITOR-NOTIF-MIB
File:
CISCO-IF-MONITOR-NOTIF-MIB.mib (9712 bytes)
Imported modules
Imported symbols
Defined Types
| CIfMonNotifEntry |
|
| SEQUENCE |
|
|
|
| |
cIfMonNotifLastChange |
TimeStamp |
|
| |
cIfMonNotifSeverity |
INTEGER |
|
| |
cIfMonNotifCause |
INTEGER |
|
| |
cIfMonNotifValue |
Unsigned32 |
|
| |
cIfMonNotifThreshold |
Unsigned32 |
|
| |
cIfMonNotifInterval |
Unsigned32 |
|
Defined Values
| 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. |
| MODULE-IDENTITY |
|
|
|
| cIfMonNotifCount |
1.3.6.1.4.1.9.10.999.1.1 |
| 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. |
| Status: current |
Access: read-only |
| OBJECT-TYPE |
|
|
|
| |
Unsigned32 |
1..4294967295 |
|
| cIfMonNotifTable |
1.3.6.1.4.1.9.10.999.1.2 |
| This table contains information about the last
notification that was sent for a particular interface. |
| Status: current |
Access: not-accessible |
| OBJECT-TYPE |
|
|
|
| |
SEQUENCE OF |
|
|
| |
|
CIfMonNotifEntry |
|
| cIfMonNotifEntry |
1.3.6.1.4.1.9.10.999.1.2.1 |
| Each entry contains information about the last
notification sent for this interface. |
| Status: current |
Access: not-accessible |
| OBJECT-TYPE |
|
|
|
| |
CIfMonNotifEntry |
|
|
| cIfMonNotifLastChange |
1.3.6.1.4.1.9.10.999.1.2.1.1 |
| This object specifies the value of sysUpTime at the
last time a notification was sent for this interface. |
| Status: current |
Access: read-only |
| OBJECT-TYPE |
|
|
|
| |
TimeStamp |
|
|
| cIfMonNotifSeverity |
1.3.6.1.4.1.9.10.999.1.2.1.2 |
| 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. |
| Status: current |
Access: read-only |
| OBJECT-TYPE |
|
|
|
| |
INTEGER |
red(1), yellow(2) |
|
| cIfMonNotifCause |
1.3.6.1.4.1.9.10.999.1.2.1.3 |
| 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. |
| Status: current |
Access: read-only |
| OBJECT-TYPE |
|
|
|
| |
INTEGER |
aborts(1), crc(2), drops(3), flaps(4), frame-reject(5), runts(6), sabm(7), frmr(8), disc(9) |
|
| cIfMonNotifValue |
1.3.6.1.4.1.9.10.999.1.2.1.4 |
| The value of the link errors over an interval that
reached/exceeded the threshold, causing a severe condition. |
| Status: current |
Access: read-only |
| OBJECT-TYPE |
|
|
|
| |
Unsigned32 |
1..4294967295 |
|
| cIfMonNotifThreshold |
1.3.6.1.4.1.9.10.999.1.2.1.5 |
| The threshold which was reached/exceeded by the link
errors over an interval, causing a severe condition. |
| Status: current |
Access: read-only |
| OBJECT-TYPE |
|
|
|
| |
Unsigned32 |
1..100000 |
|
| cIfMonNotifInterval |
1.3.6.1.4.1.9.10.999.1.2.1.6 |
| The interval over which the link errors reached/exceeded
the threshold, causing a severe condition. |
| Status: current |
Access: read-only |
| OBJECT-TYPE |
|
|
|
| |
Unsigned32 |
5..600 |
|
| 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. |
| Status: current |
Access: read-only |
| NOTIFICATION-TYPE |
|
|
|
| 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 |
| Status: current |
Access: read-only |
| MODULE-COMPLIANCE |
|
|
|
| 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. |
| Status: current |
Access: read-only |
| OBJECT-GROUP |
|
|
|
| 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. |
| Status: current |
Access: read-only |
| NOTIFICATION-GROUP |
|
|
|