HP GbE2c HP GbE2c Ethernet Blade Switch for c-Class BladeSystem Application Gu - Page 134

RMON group 3—alarms, Alarm MIB objects

Page 134 highlights

RMON group 3-alarms 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 the /cfg/rmon/alarm x/revtidx or /fevtidx 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. 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 257 = port 1 258 = port 2 ... 280 = port 24 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 RMON Alarms (CLI example 1) 1. Configure the RMON Alarm parameters to track the number of packets received on a port. >> /cfg/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" (Select RMON Alarm 6) 2. Apply and save the configuration. >> RMON Alarm 6# apply >> RMON Alarm 6# save (Make your changes active) (Save for restore after reboot) This 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. Remote monitoring 134

  • 1
  • 2
  • 3
  • 4
  • 5
  • 6
  • 7
  • 8
  • 9
  • 10
  • 11
  • 12
  • 13
  • 14
  • 15
  • 16
  • 17
  • 18
  • 19
  • 20
  • 21
  • 22
  • 23
  • 24
  • 25
  • 26
  • 27
  • 28
  • 29
  • 30
  • 31
  • 32
  • 33
  • 34
  • 35
  • 36
  • 37
  • 38
  • 39
  • 40
  • 41
  • 42
  • 43
  • 44
  • 45
  • 46
  • 47
  • 48
  • 49
  • 50
  • 51
  • 52
  • 53
  • 54
  • 55
  • 56
  • 57
  • 58
  • 59
  • 60
  • 61
  • 62
  • 63
  • 64
  • 65
  • 66
  • 67
  • 68
  • 69
  • 70
  • 71
  • 72
  • 73
  • 74
  • 75
  • 76
  • 77
  • 78
  • 79
  • 80
  • 81
  • 82
  • 83
  • 84
  • 85
  • 86
  • 87
  • 88
  • 89
  • 90
  • 91
  • 92
  • 93
  • 94
  • 95
  • 96
  • 97
  • 98
  • 99
  • 100
  • 101
  • 102
  • 103
  • 104
  • 105
  • 106
  • 107
  • 108
  • 109
  • 110
  • 111
  • 112
  • 113
  • 114
  • 115
  • 116
  • 117
  • 118
  • 119
  • 120
  • 121
  • 122
  • 123
  • 124
  • 125
  • 126
  • 127
  • 128
  • 129
  • 130
  • 131
  • 132
  • 133
  • 134
  • 135
  • 136
  • 137
  • 138
  • 139
  • 140
  • 141
  • 142
  • 143
  • 144
  • 145
  • 146
  • 147
  • 148
  • 149
  • 150
  • 151
  • 152
  • 153
  • 154
  • 155
  • 156
  • 157
  • 158
  • 159
  • 160
  • 161
  • 162
  • 163
  • 164
  • 165

Remote monitoring 134
RMON group 3—alarms
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 the
/cfg/rmon/alarm x/revtidx
or
/fevtidx
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. 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
257 = port 1
258 = port 2
280 = port 24
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 RMON Alarms (CLI example 1)
1.
Configure the RMON Alarm parameters to track the number of packets received on a port.
>> /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”
2.
Apply and save the configuration.
>> RMON Alarm 6# apply
(Make your changes active)
>> RMON Alarm 6# save
(Save for restore after reboot)
This 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.