Configuring RMON Alarm and Event Settings from the Command Line Interface (CLI)

This document describes how to set up Remote Monitoring (RMON) Alarms and Events on a router from the command line interface (CLI).

Background Information
RMON is a method similar to Simple Network Management Protocol (SNMP) to track statistics on network device interfaces or ports.

The RMON feature typically is useful in a LAN switch environment, but is available on access routers (for example, the 2x00 Series) in Cisco IOS® Software Release 11.1 or later. Sometimes, you need to set up RMON on remote routers only when you can not get access to the LAN equipment (such as hubs) to view the traffic. RMON does not require you to actively poll for SNMP variables on a regular basis. The devices store the needed information, and then it is dumped periodically to a RMON network management station.

Note: By default all switches support mini-rmon, so that alarms, events, stats and history are directly received from the switches. In order to receive all other detailed information from switches, you require Network Analysis Module (NAM).

Syntax To Set Up An Event

Cisco IOS software allows you to set up RMON alarms and events from the CLI. This section and the next one provide the syntax of the required commands, with the same names that are used for the eventTable and the alarmTable.
eventTable OBJECT-TYPE

MAX-ACCESS not-accessible
STATUS current
"A list of events to be generated."
::= { event 1 }

alarmTable OBJECT-TYPE

MAX-ACCESS not-accessible
STATUS current
"A list of alarm entries."
::= { alarm 1 }

rmon event eventIndex [log] [trap eventCommunity] [description eventDescription] [owner eventOwner]

Syntax Description

1. event—Configure an RMON event.
2. eventIndex— Event number (1–65535)
3. log—(Optional) Generate an RMON log when the event fires.
4. trap eventCommunity —(Optional) Generate an SNMP trap when the event fires, for the specified SNMP community string.
5. description eventDescription —(Optional) Specify a WORD or a description of the event.
6. owner eventOwner —(Optional) Specify an owner for the event.

  • If you do not specify either the log or the trap option, the alarmTable object eventType ( is set to none.
  • If you only specify log, eventType is set to log.
  • If you only specify trap, the eventType is set to snmp-trap.
  • If you specify both log and trap, eventType is set to log-and-trap.

Syntax To Set Up An Alarm
rmon alarm alarmIndex alarmVariable alarmInterval {absolute delta} rising-threshold alarmRisingThreshold [alarmRisingEventIndex] falling-threshold alarmFallingThreshold [alarmFallingEventIndex] [owner alarmOwner]

Syntax Description

1. alarm—Configure an RMON alarm.
2. alarmIndex—Alarm number (1–65535)
3. alarmVariable—MIB object to monitor (WORD)
4. alarmInterval—Sample interval (1–4294967295)
5. absolute—Test each sample directly.
6. delta—Test delta between samples.
7. rising-threshold—Configure the rising threshold.
8. alarmRisingThreshold—Rising threshold value (-2147483648–2147483647)
9. alarmRisingEventIndex—(optional) Event to fire when the rising threshold is crossed (1–65535)
10. falling-threshold—Configure the falling threshold.
11. alarmFallingThreshold—Falling threshold value (-2147483648–2147483647)
12. alarmFallingEventIndex—(Optional) Event to fire when the falling threshold is crossed (1–65535)
13. owner alarmOwner —(Optional) Specify an owner for the alarm (WORD).

The alarmVariable is specified one of these ways:

  • As the entire dotted decimal Abstract Syntax Notation One (ASN.1) object identifier (OID) for the object (such as .
  • With the table entry name followed by the table object number and the instance

For example, to specify ifInOctets for the first instance, use ifEntry.10.1 for the alarmVariable.

In the examples in this section, “public” is the Read-Only (RO) SNMP community string and is the host that receives the trap.

In order to set up an event to send a trap when triggered, issue these commands:
!--- Enter these commands on one line each.
rmon event 3 log trap public
description "Event to create log entry and SNMP notification"
owner "jdoe 171.68 118.100 2643"

rmon alarm 2 ifEntry.10.12 30 delta
rising-threshold 2400000 3 falling-threshold 1800000 3
owner "jdoe 71.68 118.100 2643"

In this example, a Cisco 2500 is configured to send a trap and to log an event, when the alarm threshold that monitors its own ifInOctets (ifEntry.10.1) exceeds an absolute value of 90000:
snmp-server host public
SNMP-server community public RO
rmon event 1 log trap public description "High ifInOctets" owner jdoe
!--- Enter this command on one line:
rmon alarm 10 ifEntry.10.1 60 absolute
rising-threshold 90000 1 falling-threshold 85000 owner jdoe

The monitoring occurs every 60 seconds, and the falling-threshold is 85000. In this case, the NetView management station received this trap:
A RMON Rising Alarm:
Bytes received exceeded
threshold 90000;

VALUE=483123 (sample TYPE=1; alarm index=10)

Issue these commands to view logged alarms and events:

  • show rmon events—Displays the contents of the RMON event table of the router. This command has no arguments or keywords.

Router#show rmon events

Event 12 is active, owned by manager 1
Description is interface-errors
Event firing causes log and trap to community public, last fired 00:00:00

  • Event 12 is active, owned by manager1—Unique index into the eventTable, which shows the event status as active and shows the owner of this row, as defined in the eventTable of RMON.
  • Description is interface-errors—Type of event; in this case, an interface error.
  • Event firing causes log and trap—Type of notification that the router will make about this event. Equivalent to eventType in RMON.
  • community public—If an SNMP trap is to be sent, it is sent to the SNMP community that is specified by this octet string. Equivalent to eventCommunity in RMON.
  • last fired—The last time that the event was generated.

  • show rmon alarms—Displays the contents of the RMON alarm table of the router. This command has no arguments or keywords.
    Router#show rmon alarms
    Alarm 2 is active, owned by manager1
    Monitors ifEntry.1.1 every 30 seconds
    Taking delta samples, last value was 0
    Rising threshold is 15, assigned to event 12
    Falling threshold is 0, assigned to event 0
    On startup enable rising or falling alarm
  • Alarm2 is active, owned by manager1—Unique index into the alarmTable, which shows the alarm status as active and shows the owner of this row, as defined in the alarmTable of RMON.
  • Monitors ifEntry.1.1—OID of the particular variable to be sampled. Equivalent to alarmVariable in RMON.
  • every 30 seconds—Interval in seconds over which the data is sampled and compared with the rising and falling thresholds. Equivalent to alarmInterval in RMON.
  • Taking delta samples—Method to sample the selected variable and calculate the value to be compared against the thresholds. Equivalent to alarmSampleType in RMON.
  • Last value was—Value of the statistic during the last sampling period. Equivalent to alarmValue in RMON.
  • Rising threshold is—Threshold for the sampled statistics. Equivalent to alarmRisingThreshold in RMON.
    assigned to event—Index of the EventEntry that is used when a rising threshold is crossed. Equivalent to alarmRisingEventIndex in RMON.
  • Falling threshold is—Threshold for the sampled statistic. Equivalent to alarmFallingThreshold in RMON.
    Assigned to event—Index of the EventEntry that that is used when a falling threshold is crossed.
  • Equivalent to alarmFalllingEventIndex in RMON.
  • On startup enable rising or falling alarm—Alarm that may be sent when this entry is first set to valid. Equivalent to alarmStartupAlarm in RMON.
Post a Comment

Popular posts from this blog

Pairwise Master Key (PMK) vs Parewise Transient Key(PTK) vs PseudoRandom Function(PRF) vs GTK (Groupwise Transient Key)

DSSS(直接序列展頻技術) vs OFDM(正交頻率多重分割)