Configuring RMON Support
The Remote Monitoring (RMON) MIB agent specification can be used in conjunction with Simple Network Management Protocol (SNMP) to monitor traffic using alarms and events.
Finding Feature Information
Your software release may not support all the features documented in this module. For the latest caveats and feature information, see Bug Search Tool and the release notes for your platform and software release. To find information about the features documented in this module, and to see a list of the releases in which each feature is supported, see the feature information table at the end of this module.
Use Cisco Feature Navigator to find information about platform support and Cisco software image support. To access Cisco Feature Navigator, go to www.cisco.com/go/cfn. An account on Cisco.com is not required.
Information About Configuring RMON Support
The RMON option identifies activity on individual nodes and allows you to monitor all nodes and their interaction on a LAN segment. Used in conjunction with the SNMP agent in a router, Combining RMON alarms and events (classes of messages that indicate traffic violations and various unusual occurrences over a network) with existing MIBs allows you to choose where proactive monitoring will occur.
 Note |
RMON requires that SNMP be configured (you must be running a version of SNMP on the server that contains the RMON MIB). A generic RMON console application is recommended in order to take advantage of the RMON network management capabilities. |
RMON can be very data- and processor-intensive. Users should measure usage effects to ensure that router performance is not degraded by RMON and to minimize excessive management traffic overhead. Native mode in RMON is less intensive than promiscuous mode.
All Cisco IOS XE software images ordered without the explicit RMON option include limited RMON support (RMON alarms and event groups only). Images ordered with the RMON option include support for all nine management groups (statistics, history, alarms, hosts, hostTopN, matrix, filter, capture, and event). As a security precaution, support for the capture group allows capture of packet header information only; data payloads are not captured.
RMON MIB features include the following:
- usrHistory group. This MIB group is similar to the RMON etherHistory group except that the group enables the user to specify the MIB objects that are collected at each interval.
- partial probeConfig group. This MIB group is a subset of the probeConfig group implemented in read-only mode. These objects implement the simple scalars from this group. The table below details new partial probeConfig group objects.
| Table 1 | partial probeConfig Group Objects |
| Object |
Description |
|---|---|
| probeCapabilities |
The RMON software groups implemented. |
| probeSoftwareRev |
The current version of Cisco IOS XE running on the device. |
| probeHardwareRev |
The current version of the Cisco device. |
| probeDateTime |
The current date and time. |
| probeResetControl |
Initiates a reset. |
| probeDownloadFile |
The source of the image running on the device. |
| probeDownloadTFTPServer |
The address of the server that contains the Trivial File Transfer Protocol (TFTP) file that is used by the device to download new versions of Cisco IOS XE software. |
| probeDownloadAction |
Specifies the action of the commands that cause the device to reboot. |
| probeDownloadStatus |
The state of a reboot. |
| netDefaultGateway |
The router mapped to the device as the default gateway. |
| hcRMONCapabilities |
Specifies the features mapped to this version of RMON. |
How to Configure RMON Support
Setting an RMON alarm or event
Perform the following steps to set an RMON alarm or event:
DETAILED STEPS
Troubleshooting Tips
You can set an alarm on any MIB object in the access server. To disable an alarm, you must enable the no form of this command on each alarm you configure. You cannot disable all the alarms you configure at once.
The RMON MIB defines two traps, the risingAlarm and fallingAlarm traps generated when an RMON alarmEntry risingThreshold or fallingThreshold event occurs. Thresholds allow you to minimize the number of notifications sent on the network. Alarms are triggered when a problem exceeds a set rising threshold value. No more alarm notifications are sent until the agent recovers, as defined by the falling threshold value. This means that notifications are not sent each time a minor failure or recovery occurs.
Monitoring and Verifying an RMON Configuration
To display the current RMON status, use one or more of the following commands in EXEC mode:
DETAILED STEPS
Configuration Examples for RMON
Configuring Alarms and Events Example
The following example shows how to add an event (in the RMON event table) that is associated with an RMON event number, using the rmon eventglobal configurationcommand:
Router(config)# rmon event 1 log trap eventtrap description "High ifOutErrors" owner owner_a
This example creates RMON event number 1, which is defined as "High ifOutErrors", and generates a log entry when the event is triggered by an alarm. The user "owner_a" owns the row that is created in the event table by this command. This example also generates an SNMP trap when the event is triggered.
The following example shows how to configure an RMON alarm using the rmon alarm global configuration command:
Router(config)# rmon alarm 10 ifEntry.20.1 20 delta rising-threshold 15 1 falling-threshold 0 owner owner_a
This example configures RMON alarm number 10. The alarm monitors the MIB variable ifEntry.20.1 once every 20 seconds until the alarm is disabled, and checks the change in the rise or fall of the variable. If the ifEntry.20.1 value shows a MIB counter increase of 15 or more, such as from 100000 to 100015, the alarm is triggered. The alarm in turn triggers event number 1, which is configured with the rmon event command. Possible events include a log entry or an SNMP trap. If the ifEntry.20.1 value changes by 0, the alarm is reset and can be triggered again.
Additional References
The following sections provide references related to the Configuring RMON Support feature.
MIBs
| MIB |
MIBs Link |
|---|---|
| Remote Monitoring (RMON) MIB |
To locate and download MIBs for selected platforms, Cisco IOS XE releases, and feature sets, use Cisco MIB Locator found at the following URL: |
Technical Assistance
| Description |
Link |
|---|---|
| The Cisco Support website provides extensive online resources, including documentation and tools for troubleshooting and resolving technical issues with Cisco products and technologies. To receive security and technical information about your products, you can subscribe to various services, such as the Product Alert Tool (accessed from Field Notices), the Cisco Technical Services Newsletter, and Really Simple Syndication (RSS) Feeds. Access to most tools on the Cisco Support website requires a Cisco.com user ID and password. |
Feature Information for Configuring RMON Support
The following table provides release information about the feature or features described in this module. This table lists only the software release that introduced support for a given feature in a given software release train. Unless noted otherwise, subsequent releases of that software release train also support that feature.
Use Cisco Feature Navigator to find information about platform support and Cisco software image support. To access Cisco Feature Navigator, go to www.cisco.com/go/cfn. An account on Cisco.com is not required.
| Table 2 | Feature Information for Configuring RMON Support |
| Feature Name |
Releases |
Feature Information |
|---|---|---|
| RMON Events and Alarms |
Cisco IOS XE Release 2.1 |
This feature was introduced on Cisco ASR 1000 Series Routers. The following commands are introduced or modified by this feature: rmon capture userdata, rmon collection history, rmon collection host, rmon collection matrix, rmon collection rmon1, show rmon capture, show rmon filter, show rmon hosts, show rmon matrix. |
Cisco and the Cisco logo are trademarks or registered trademarks of Cisco and/or its affiliates in the U.S. and other countries. To view a list of Cisco trademarks, go to this URL: www.cisco.com/go/trademarks. Third-party trademarks mentioned are the property of their respective owners. The use of the word partner does not imply a partnership relationship between Cisco and any other company. (1110R)
Any Internet Protocol (IP) addresses and phone numbers used in this document are not intended to be actual addresses and phone numbers. Any examples, command display output, network topology diagrams, and other figures included in the document are shown for illustrative purposes only. Any use of actual IP addresses or phone numbers in illustrative content is unintentional and coincidental.
Feedback