RackSwitch G8000 Application Guide
Chapter 7: Remote Monitoring
117BMD00041, November 2008
Use one of the following commands to correlate an Alarm index to an Event index:
When the alarm threshold is reached, the corresponding event is triggered.
Alarm MIB objects
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. The following are examples of RMON statistics:
1.3.6.1.2.1.5.1.0 – mgmt.icmp.icmpInMsgs
1.3.6.1.2.1.2.2.1.10.x – ifInOctets
The last digit (x) represents the interface on which to monitor, which corresponds to the inter-
face number, or port number, as follows:
1-128 = IF 1-128
129 = port 1
130 = port 2
…
172 = port 44
This value represents the alarm’s MIB OID, as a string. Note that for non-tables, you must sup-
ply a .0 to specify end node.
Configuring RMON Alarms
Example 1
1. Configure the RMON Alarm parameters to track the number of packets received on
port 1.
This configuration creates an RMON alarm that checks ifInOctets on port 1 once every
hour. If the statistic exceeds two billion, an alarm is generated that triggers event index 100.
RS G8000 (config)# rmon alarm <alarm number> rise-event <event number>
RS G8000 (config)# rmon alarm <alarm number> fall-event <event number>
RS G8000 (config)# rmon alarm 1 oid 1.3.6.1.2.1.2.2.1.10.129
alarm-type rising rise-event 100
RS G8000 (config)# rmon alarm 1 interval-time 3600
RS G8000 (config)# rmon alarm 1 rising-threshold 2000000000
RS G8000 (config)# rmon alarm 1 owner "Alarm for ifInOctets"
