для Cisco Cisco ASR 920-4SZ-A Router
Revised: December 23, 2014,
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.
(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
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.
module.
Use Cisco Feature Navigator to find information about platform support and Cisco software image support. To access Cisco Feature
Navigator, go to
Navigator, go to
. 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 device, 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.
Used in conjunction with the SNMP agent in a device, 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.
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.
contains the RMON MIB). A generic RMON console application is recommended in order to take advantage
of the RMON network management capabilities.
Note
RMON can be very data- and processor-intensive. Users should measure usage effects to ensure that the device performance is not
degraded by RMON and to minimize excessive management traffic overhead. Native mode in RMON is less intensive than promiscuous
mode.
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.
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.
2