The Remote Network Monitoring (RMON) MIB was developed by the IETF to support monitoring and protocol analysis of local area networks (LANs). The original version (sometimes referred to as RMON1) focused on OSI layer 1 and layer 2 information in Ethernet and Token Ring networks. It has been extended by RMON2 which adds support for Network- and Application-layer monitoring and by SMON which adds support for switched networks. It is an industry-standard specification that provides much of the functionality offered by proprietary network analyzers. RMON agents are built into many high-end switches and routers.
Remote Monitoring (RMON) is a standard monitoring specification that enables various network monitors and console systems to exchange network-monitoring data. RMON provides network administrators with more freedom in selecting network-monitoring probes and consoles with features that meet their particular networking needs. An RMON implementation typically operates in a client/server model. Monitoring devices (commonly called "probes" in this context) contain RMON software agents that collect information and analyze packets. These probes act as servers and the Network Management applications that communicate with them act as clients. While both agent configuration and data collection use SNMP, RMON is designed to operate differently than other SNMP-based systems:
Probes have more responsibility for data collection and processing, which reduces SNMP traffic and the processing load of the clients.
Information is only transmitted to the management application when required, instead of continuous polling and monitoring
In short, RMON is designed for "flow-based" monitoring, while SNMP is often used for "device-based" management. RMON is similar to other flow-based monitoring technologies such as NetFlow and SFlow because the data collected deals mainly with traffic patterns rather than the status of individual devices. One disadvantage of this system is that remote devices shoulder more of the management burden, and require more resources to do so. Some devices balance this trade-off by implementing only a subset of the RMON MIB groups (see below). A minimal RMON agent implementation could support only statistics, history, alarm, and event.
The RMON1 MIB consists of ten groups:
Statistics: real-time LAN statistics e.g. utilization, collisions, CRC errors
History: history of selected statistics
Alarm: definitions for RMON SNMP traps to be sent when statistics exceed defined thresholds
Hosts: host specific LAN statistics e.g. bytes sent/received, frames sent/received
Hosts top N: record of N most active connections over a given time period
Matrix: the sent-received traffic matrix between systems
Filter: defines packet data patterns of interest e.g. MAC address or TCP port
Capture: collect and forward packets matching the Filter
Event: send alerts (SNMP traps) for the Alarm group
Token Ring: extensions specific to Token Ring
The RMON2 MIB adds ten more groups:
Protocol Directory: list of protocols the probe can monitor
Protocol Distribution: traffic statistics for each protocol
Address Map: maps network-layer (IP) to MAC-layer addresses
Network-Layer Host: layer 3 traffic statistics, per each host
Network-Layer Matrix: layer 3 traffic statistics, per source/destination pairs of hosts
Application-Layer Host: traffic statistics by application protocol, per host
Application-Layer Matrix: traffic statistics by application protocol, per source/destination pairs of hosts
User History: periodic samples of user-specified variables
Probe Configuration: remote configure of probes
RMON Conformance: requirements for RMON2 MIB conformance
Important RFCsedit
RMON1: RFC 2819 - Remote Network Monitoring Management Information Base
RMON2: RFC 4502 - Remote Network Monitoring Management Information Base Version 2 using SMIv2
HCRMON: RFC 3273 - Remote Network Monitoring Management Information Base for High Capacity Networks
RAMON: open-source implementation of a RMON2 agent
January 01, 1970
rmon, remote, monitoring, redirects, here, medical, technology, remote, patient, monitoring, this, article, relies, excessively, references, primary, sources, please, improve, this, article, adding, secondary, tertiary, sources, find, sources, news, newspapers. Remote monitoring redirects here For the medical technology see Remote patient monitoring This article relies excessively on references to primary sources Please improve this article by adding secondary or tertiary sources Find sources RMON news newspapers books scholar JSTOR October 2010 Learn how and when to remove this message The Remote Network Monitoring RMON MIB was developed by the IETF to support monitoring and protocol analysis of local area networks LANs The original version sometimes referred to as RMON1 focused on OSI layer 1 and layer 2 information in Ethernet and Token Ring networks It has been extended by RMON2 which adds support for Network and Application layer monitoring and by SMON which adds support for switched networks It is an industry standard specification that provides much of the functionality offered by proprietary network analyzers RMON agents are built into many high end switches and routers Contents 1 Overview 2 Important RFCs 3 See also 4 External linksOverview editRemote Monitoring RMON is a standard monitoring specification that enables various network monitors and console systems to exchange network monitoring data RMON provides network administrators with more freedom in selecting network monitoring probes and consoles with features that meet their particular networking needs An RMON implementation typically operates in a client server model Monitoring devices commonly called probes in this context contain RMON software agents that collect information and analyze packets These probes act as servers and the Network Management applications that communicate with them act as clients While both agent configuration and data collection use SNMP RMON is designed to operate differently than other SNMP based systems Probes have more responsibility for data collection and processing which reduces SNMP traffic and the processing load of the clients Information is only transmitted to the management application when required instead of continuous polling and monitoring In short RMON is designed for flow based monitoring while SNMP is often used for device based management RMON is similar to other flow based monitoring technologies such as NetFlow and SFlow because the data collected deals mainly with traffic patterns rather than the status of individual devices One disadvantage of this system is that remote devices shoulder more of the management burden and require more resources to do so Some devices balance this trade off by implementing only a subset of the RMON MIB groups see below A minimal RMON agent implementation could support only statistics history alarm and event The RMON1 MIB consists of ten groups Statistics real time LAN statistics e g utilization collisions CRC errors History history of selected statistics Alarm definitions for RMON SNMP traps to be sent when statistics exceed defined thresholds Hosts host specific LAN statistics e g bytes sent received frames sent received Hosts top N record of N most active connections over a given time period Matrix the sent received traffic matrix between systems Filter defines packet data patterns of interest e g MAC address or TCP port Capture collect and forward packets matching the Filter Event send alerts SNMP traps for the Alarm group Token Ring extensions specific to Token Ring The RMON2 MIB adds ten more groups Protocol Directory list of protocols the probe can monitor Protocol Distribution traffic statistics for each protocol Address Map maps network layer IP to MAC layer addresses Network Layer Host layer 3 traffic statistics per each host Network Layer Matrix layer 3 traffic statistics per source destination pairs of hosts Application Layer Host traffic statistics by application protocol per host Application Layer Matrix traffic statistics by application protocol per source destination pairs of hosts User History periodic samples of user specified variables Probe Configuration remote configure of probes RMON Conformance requirements for RMON2 MIB conformanceImportant RFCs editRMON1 RFC 2819 Remote Network Monitoring Management Information Base RMON2 RFC 4502 Remote Network Monitoring Management Information Base Version 2 using SMIv2 HCRMON RFC 3273 Remote Network Monitoring Management Information Base for High Capacity Networks SMON RFC 2613 Remote Network Monitoring MIB Extensions for Switched Networks Overview RFC 3577 Introduction to the RMON Family of MIB ModulesSee also editNetwork performance management Network tapExternal links editRMON Remote Monitoring MIBs RAMON open source implementation of a RMON2 agent Retrieved from https en wikipedia org w index php title RMON amp oldid 1207766274, wikipedia, wiki, book, books, library,
