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
BMD00113, September 2009 Chapter 13: Remote Monitoring  221
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.
An example of an ICMP stat is as follows:
1.3.6.1.2.1.5.1.0 - mgmt.icmp.icmpInMsgs
The last digit (x) represents the interface on which to monitor, which corresponds to the interface
number, or port number, as follows:
 1-256 = IF 1-256
 For numbers 257 and above, the number represennts 256 + the port number:
 257 = port 1
 258 = port 2, 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 end node.
RMON Alarm Example 1
This example configuration creates an RMON alarm that checks ifInOctets on port 20 once
every hour. If the statistic exceeds two billion, an alarm is generated that triggers event index 6.
1. Configure the RMON Alarm parameters to track the number of packets received on a port.
2. Apply and save the configuration.
>> # /cfg/rmon/alarm 6 (Select RMON Alarm 6)
>> RMON Alarm 6# oid 1.3.6.1.2.1.2.2.1.10.276
>> RMON Alarm 6# intrval 3600
>> RMON Alarm 6# almtype rising
>> RMON Alarm 6# rlimit 2000000000
>> RMON Alarm 6# revtidx 6
>> RMON Alarm 6# sample abs
>> RMON Alarm 6# owner "Alarm_for_ifInOctets"
>> RMON Alarm 6# apply (Make your changes active)
>> RMON Alarm 6# save (Save for restore after reboot)