3. View RMON history for the port.
RMON Group 3—Alarms
Alarm MIB objects
Configuring RMON Alarms
© Copyright Lenovo 2016
RS G8264(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:
RS G8264(config)# rmon alarm <alarm number> risingcrossingindex
<event number>
RS G8264(config)# rmon alarm <alarm number> fallingcrossingindex
<event number>
When the alarm threshold is reached, the corresponding event is triggered.
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 statistic follows:
1.3.6.1.2.1.5.1.0 – mgmt.icmp.icmpInMsgs
This value represents the alarm's MIB OID, as a string. Note that for non‐tables,
you must supply a .0 to specify end node.
Configure the RMON Alarm parameters to track ICMP messages.
RS G8264(config)# rmon alarm 1 oid 1.3.6.1.2.1.5.8.0
RS G8264(config)# rmon alarm 1 alarmtype rising
RS G8264(config)# rmon alarm 1 risingcrossingindex 110
RS G8264(config)# rmon alarm 1 intervaltime 60
RS G8264(config)# rmon alarm 1 risinglimit 200
RS G8264(config)# rmon alarm 1 sample delta
RS G8264(config)# rmon alarm 1 owner "Alarm for icmpInEchos"
Chapter 44: Remote Monitoring
691