BLADE OS™ Application Guide HP GbE2c Ethernet Blade Switch for c-Class BladeSystem Version 5.1 Advanced Functionality Software

BLADE OS 5.1 Application Guide
222  Chapter 13: Remote Monitoring BMD00113, September 2009
RMON Alarm Example 2
This example configuration creates an RMON alarm that checks icmpInEchos on the switch
once every minute. If the statistic exceeds 200 within a 60 second interval, an alarm is generated
that triggers event index 5.
1. Configure the RMON Alarm parameters to track ICMP messages.
2.Apply and save the configuration.
RMON Group 9—Events
The RMON Event Group allows you to define events that are triggered by alarms. An event can be
a log message, an SNMP trap message, or both.
When an alarm is generated, it triggers a corresponding event notification. Use the following
command to correlate a rising alarm to an event index:
/cfg/rmon/alarm <x>/revtidx
Use the following command to correlate a falling alarm to an event index:
/cfg/rmon/alarm <x>/fevtidx
RMON events use SNMP and system logs to send notifications. Therefore, an SNMP trap host must
be configured for trap event notification to work properly.
RMON uses a syslog host to send syslog messages. Therefore, an existing syslog host
(/cfg/sys/syslog) must be configured for event log notification to work properly. Each log
event generates a system log message of type RMON that corresponds to the event.
>> # /cfg/rmon/alarm 5 (Select RMON Alarm 5)
>> RMON Alarm 5# oid 1.3.6.1.2.1.5.8.0
>> RMON Alarm 5# intrval 60
>> RMON Alarm 5# almtype rising
>> RMON Alarm 5# rlimit 200
>> RMON Alarm 5# revtidx 5
>> RMON Alarm 5# sample delta
>> RMON Alarm 5# owner "Alarm_for_icmpInEchos"
>> RMON Alarm 5# apply (Make your changes active)
>> RMON Alarm 5# save (Save for restore after reboot)