21-4
Ethernet Card Software Feature and Configuration Guide, R7.2
January 2009
Chapter 21 Configuring RMON
Configuring RMON Alarms and Events
To disable an alarm, use the no rmon alarm number global configuration command on each alarm you
configured. You cannot disable all the alarms that you configured by not specifying a spec ific number.
You must disable each alarm separately. To disable an event, use the no rmon event number global
configuration command. To learn more about alarms and events and how they interact with each other,
see RFC 1757.
You can set an alarm on any MIB object. The following example configures RMON alarm number 10 by
using the rmon alarm command. The alarm monitors the MIB variable ifEntry.20.1 once every
20 seconds to check the change in the variable’s rise or fa ll until the alarm is disabled. If th e ifEntry.20.1
value shows a MIB counter increase of 15 or more, such as from 100000 to 100015, the alarm is
triggered. The alarm in turn triggers event number 1, which is configured with the rmon event
command. Possible events can include a log entry or an SNMP trap. If the ifEntry.20.1 value changes
by 0, the alarm is reset and can be triggered again.
ML_Series(config)# rmon alarm 10 ifInErrors.65539 20 delta rising 15 1 fall 0
Note The example does not trigger an optional event when the falling-threshold is 0.
Where 65539 is the SNMP IfIndex for interface POS 0. You can get the SNMP ifIndex for a given port
with an SNMP get. In the example output, you can see that the SNMP ifIndex for POS0 is 65539:
tuvoks-view:128> getmany -v2c 10.92.56.97 tcc@1 ifDescr
ifDescr.65536 = GigabitEthernet0
ifDescr.65537 = GigabitEthernet1
ifDescr.65538 = Null0
ifDescr.65539 = POS0
ifDescr.65540 = POS1
ifDescr.65541 = SPR1
tuvoks-view:129>
The following example creates RMON event number 1 by using the rmon event command. The event is
defined as High ifOutErrors and generates a log entry when the event is triggered by the alarm. The user
jjones owns the row that is created in the event table by this comm and. This example also generates an
SNMP trap when the event is triggered.
ML_Series(config)# rmon event 1 log trap eventtrap description "High ifOutErrors" owner
jjones