Rmon Group 3-Alarms; Alarm Mib Objects - Lenovo Flex System Fabric CN4093 Application Manual

3. View RMON history for the port.
RMON Group 3–Alarms

Alarm MIB Objects

526
CN4093 Application Guide for N/OS 8.2
CN4093(config)# show rmon history
RMON History group configuration:
Index IFOID Interval Rbnum Gbnum
­­­­­ ­­­­­­­­­­­­­­­­­­­­­­­ ­­­­­­­­ ­­­­­ ­­­­­
1 1.3.6.1.2.1.2.2.1.1.1 120 30 30
Index Owner
­­­­­ ­­­­­­­­­­­­­­­­­­­­­­­­­­­­­­­­­­­­­­­­­­­­­­
1 rmon port 1 history
The RMON Alarm Group allows you to define a set of thresholds used to
determine network performance. When a configured threshold is crossed, an
alarm is generated. For example, you can configure the switch to issue an alarm if
more than 1,000 CRC errors occur during a 10‐minute time interval.
Each Alarm index consists of a variable to monitor, a sampling time interval, and
parameters for rising and falling thresholds. The Alarm group can be used to track
rising or falling values for a MIB object. The object must be a counter, gauge,
integer, or time interval.
Use one of the following commands to correlate an Alarm index to an Event index:
CN4093(config)# rmon alarm <alarm number> rising­crossing­index <event number>
CN4093(config)# rmon alarm <alarm number> falling­crossing­index <event number>
The most common data types used for alarm monitoring are ifStats: errors,
drops, bad CRCs, and so on. These MIB Object Identifiers (OIDs) correlate to the
ones tracked by the History group. An example of an ICMP stat is as follows:
1.3.6.1.2.1.5.1.<x> ­ mgmt.icmp.icmpInMsgs
where x represents the interface on which to monitor, which corresponds to the
switch interface number or port number, as follows:
1 through 128 = Switch interface number

 129 = Switch port 1
130 = Switch port 2

 131 = Switch port 3, and so on.
This value represents the alarmʹs MIB OID, as a string. Note that for non‐tables,
you must supply a .0 to specify an end node.