Setting the RMON Alarm
To set an alarm on any MIB object, use the
rmon alarm
or
rmon hc-alarm
command in GLOBAL CONFIGURATION mode.
•
Set an alarm on any MIB object.
CONFIGURATION mode
[no] rmon alarm
number variable interval
{delta | absolute} rising-threshold [
value event-
number
] falling-threshold
value event-number
[owner
string
]
OR
[no] rmon hc-alarm
number variable interval
{delta | absolute} rising-threshold
value event-
number
falling-threshold
value event-number
[owner
string
]
Configure the alarm using the following optional parameters:
•
number
: alarm number, an integer from 1 to 65,535, the value must be unique in the RMON Alarm Table.
•
variable
: the MIB object to monitor — the variable must be in SNMP OID format; for example, 1.3.6.1.2.1.1.3. The object type
must be a 32-bit integer for the
rmon alarm
command and 64 bits for the
rmon hc-alarm
command.
•
interval
: time in seconds the alarm monitors the MIB variable, the value must be between 1 to 3,600.
•
delta
: tests the change between MIB variables, this option is the alarmSampleType in the RMON Alarm table.
•
absolute
: tests each MIB variable directly, this option is the alarmSampleType in the RMON Alarm table.
•
rising-threshold
value
: value at which the rising-threshold alarm is triggered or reset. For the
rmon alarm
command,
this setting is a 32-bits value, for the
rmon hc-alarm
command, this setting is a 64-bits value.
•
event-number
: event number to trigger when the rising threshold exceeds its limit. This value is identical to the
alarmRisingEventIndex in the alarmTable of the RMON MIB. If there is no corresponding rising-threshold event, the value should be
zero.
•
falling-threshold
value
: value at which the falling-threshold alarm is triggered or reset. For the
rmon alarm
command,
this setting is a 32-bits value, for the
rmon hc-alarm
command this setting is a 64 bits value.
•
event-number
: event number to trigger when the falling threshold exceeds its limit. This value is identical to the
alarmFallingEventIndex in the alarmTable of the RMON MIB. If there is no corresponding falling-threshold event, the value should be
zero.
•
owner
string
: (Optional) specifies an owner for the alarm, this setting is the alarmOwner object in the alarmTable of the RMON
MIB. Default is a
null-terminated string
.
Example of the
rmon alarm
Command
To disable the alarm, use the
no
form of the command.
The following example configures RMON alarm number 10. The alarm monitors the MIB variable 1.3.6.1.2.1.2.2.1.20.1 (ifEntry.ifOutErrors)
once every 20 seconds until the alarm is disabled, and checks the rise or fall of the variable. The alarm is triggered when the
1.3.6.1.2.1.2.2.1.20.1 value shows a MIB counter increase of 15 or more (such as from 100000 to 100015). The alarm then triggers event
number 1, which is configured with the RMON event command. Possible events include a log entry or an SNMP trap. If the
1.3.6.1.2.1.2.2.1.20.1 value changes to 0 (falling-threshold 0), the alarm is reset and can be triggered again.
Dell(conf)#rmon alarm 10 1.3.6.1.2.1.2.2.1.20.1 20 delta rising-threshold
15 1 falling-threshold 0 1 owner nms1
Configuring an RMON Event
To add an event in the RMON event table, use the
rmon event
command in GLOBAL CONFIGURATION mode.
•
Add an event in the RMON event table.
Remote Monitoring (RMON)
683
Summary of Contents for S3048-ON
Page 1: ...Dell Configuration Guide for the S3048 ON System 9 11 2 5 ...
Page 137: ...0 Gi 1 1 Gi 1 2 rx Flow N A N A 0 0 No N A N A yes Access Control Lists ACLs 137 ...
Page 142: ...Figure 10 BFD Three Way Handshake State Changes 142 Bidirectional Forwarding Detection BFD ...
Page 241: ...Dell Control Plane Policing CoPP 241 ...
Page 287: ... RPM Synchronization GARP VLAN Registration Protocol GVRP 287 ...
Page 428: ...Figure 53 Inspecting the LAG Configuration 428 Link Aggregation Control Protocol LACP ...
Page 477: ...Figure 73 Configuring Interfaces for MSDP Multicast Source Discovery Protocol MSDP 477 ...
Page 478: ...Figure 74 Configuring OSPF and BGP for MSDP 478 Multicast Source Discovery Protocol MSDP ...
Page 483: ...Figure 77 MSDP Default Peer Scenario 2 Multicast Source Discovery Protocol MSDP 483 ...
Page 484: ...Figure 78 MSDP Default Peer Scenario 3 484 Multicast Source Discovery Protocol MSDP ...
Page 745: ...Figure 104 Single and Double Tag TPID Match Service Provider Bridging 745 ...
Page 746: ...Figure 105 Single and Double Tag First byte TPID Match 746 Service Provider Bridging ...