HP 6125G HP 6125G & 6125G/XG Blade Switches Network Management and Mon - Page 107

customized by users.

Get HP 6125G PDF manuals and user guides View all HP 6125G manuals
Add to My Manuals
Save this manual to your list of manuals

Page 107 highlights

Use undo rmon prialarm to remove a private alarm entry from the private alarm table of RMON. Before creating an alarm entry, use the rmon event command to define the events to be referenced in the event table. You cannot create an entry that has the same alarm variable formula (prialarm-formula), sampling type (absolute changeratio or delta), rising threshold (threshold-value1), and falling threshold (threshold-value2) as an existing private alarm entry. You can create up to 50 private alarm entries. The system handles private alarm entries as follows: 1. Samples the private alarm variables in the private alarm formula at the specified sampling interval. 2. Performs calculation on the sampled values with the formula. 3. Compares the calculation result with the predefined thresholds and does the following: { If the result is equal to or greater than the rising threshold, the system triggers the event specified by the event-entry1 argument. { If the result is equal to or smaller than the falling threshold, the system triggers the event specified by the event-entry2 argument. Related commands: display rmon prialarm, rmon event, rmon history, and rmon statistics. Examples # Monitor the ratio of the broadcast packets received on the interface by using the private alarm. Calculate the private alarm variables with the (1.3.6.1.2.1.16.1.1.1.6.1*100/.1.3.6.1.2.1.16.1.1.1.5.1) formula and sample the variables at 10-second intervals. (Broadcast packet ratio= total number of broadcast packets received on the interface/total number of packets received on the interface; the formula is customized by users.) The rising threshold (80%) triggers event 1 to log the event. The falling threshold (5%) triggers event 2, but the event defines neither log nor trap action. Set the lifetime of the entry to forever and owner to user1. system-view [Sysname] rmon event 1 log [Sysname] rmon event 2 none [Sysname] interface gigabitethernet 1/0/1 [Sysname-GigabitEthernet1/0/1] rmon statistics 1 [Sysname-GigabitEthernet1/0/1] quit [Sysname] rmon prialarm 1 (.1.3.6.1.2.1.16.1.1.1.6.1*100/.1.3.6.1.2.1.16.1.1.1.5.1) BroadcastPktsRatioOfEth1/1 10 absolute rising-threshold 80 1 falling-threshold 5 2 entrytype forever owner user1 1.3.6.1.2.1.16.1.1.1.6.1 is the OID of the node etherStatsBroadcastPkts.1, and 1.3.6.1.2.1.16.1.1.1.5.1 is the OID of the node etherStatsPkts.1. 1 indicates the serial number of the interface statistics entry. Therefore, if you execute the rmon statistics 5 command, you should use 1.3.6.1.2.1.16.1.1.1.6.5 and 1.3.6.1.2.1.16.1.1.1.5.5. This example enables the RMON agent to do the following: • Samples and monitors interface GigabitEthernet 1/0/1. • If the portion of incoming broadcast packets in the total traffic crosses 80%, the system logs the event. If the portion is less than or equal to 5%, the system takes no action. To view the event log, use the display rmon eventlog command. 101

  • 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
  • 166
  • 167
  • 168
  • 169
  • 170
  • 171
  • 172
  • 173
  • 174
  • 175
  • 176
  • 177
  • 178
  • 179
  • 180
  • 181
  • 182
  • 183
  • 184
  • 185
  • 186
  • 187
  • 188
  • 189
  • 190
  • 191
  • 192
  • 193
  • 194
  • 195
  • 196
101
Use
undo rmon prialarm
to remove a private alarm entry from the private alarm table of RMON.
Before creating an alarm entry, use the
rmon event
command to define the events to be referenced in the
event table.
You cannot create an entry that has the same alarm variable formula (
prialarm-formula
), sampling type
(
absolute changeratio
or
delta
), rising threshold (
threshold-value1
), and falling threshold
(
threshold-value2
) as an existing private alarm entry.
You can create up to 50 private alarm entries.
The system handles private alarm entries as follows:
1.
Samples the private alarm variables in the private alarm formula at the specified sampling interval.
2.
Performs calculation on the sampled values with the formula.
3.
Compares the calculation result with the predefined thresholds and does the following:
{
If the result is equal to or greater than the rising threshold, the system triggers the event
specified by the
event
-
entry1
argument.
{
If the result is equal to or smaller than the falling threshold, the system triggers the event
specified by the
event
-
entry2
argument.
Related commands:
display rmon prialarm
,
rmon
event
,
rmon history
, and
rmon statistics
.
Examples
# Monitor the ratio of the broadcast packets received on the interface by using the private alarm.
Calculate the private alarm variables with the (1.3.6.1.2.1.16.1.1.1.6.1*100/.1.3.6.1.2.1.16.1.1.1.5.1) formula
and sample the variables at 10-second intervals. (Broadcast packet ratio= total number of broadcast
packets received on the interface/total number of packets received on the interface; the formula is
customized by users.)
The rising threshold (80%) triggers event 1 to log the event. The falling threshold (5%) triggers event 2, but
the event defines neither log nor trap action.
Set the lifetime of the entry to
forever
and owner to
user1
.
<Sysname> system-view
[Sysname] rmon event 1 log
[Sysname] rmon event 2 none
[Sysname] interface gigabitethernet 1/0/1
[Sysname-GigabitEthernet1/0/1] rmon statistics 1
[Sysname-GigabitEthernet1/0/1] quit
[Sysname] rmon prialarm 1 (.1.3.6.1.2.1.16.1.1.1.6.1*100/.1.3.6.1.2.1.16.1.1.1.5.1)
BroadcastPktsRatioOfEth1/1 10 absolute rising-threshold 80 1 falling-threshold 5 2
entrytype forever owner user1
1.3.6.1.2.1.16.1.1.1.6.1 is the OID of the node etherStatsBroadcastPkts.1, and 1.3.6.1.2.1.16.1.1.1.5.1 is the
OID of the node etherStatsPkts.1. 1 indicates the serial number of the interface statistics entry. Therefore,
if you execute the
rmon
statistics 5
command, you should use 1.3.6.1.2.1.16.1.1.1.6.5 and
1.3.6.1.2.1.16.1.1.1.5.5.
This example enables the RMON agent to do the following:
•
Samples and monitors interface GigabitEthernet 1/0/1.
•
If the portion of incoming broadcast packets in the total traffic crosses 80%, the system logs the
event. If the portion is less than or equal to 5%, the system takes no action. To view the event log,
use the
display rmon eventlog
command.