Knowledge

RMON

Source 📝

189:
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
43: 212:
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
188:
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
179:
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.
204:
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
213:
subset of the RMON MIB groups (see below). A minimal RMON agent implementation could support only statistics, history, alarm, and event.
197:
Probes have more responsibility for data collection and processing, which reduces SNMP traffic and the processing load of the clients.
190: 126: 152: 337: 64: 57: 243: 200:
Information is only transmitted to the management application when required, instead of continuous polling and monitoring
374: 148: 107: 79: 31: 354: 221: 86: 53: 281:
Application-Layer Matrix: traffic statistics by application protocol, per source/destination pairs of hosts
167:
information in Ethernet and Token Ring networks. It has been extended by RMON2 which adds support for
93: 156: 75: 172: 315:: RFC 3273 - Remote Network Monitoring Management Information Base for High Capacity Networks 230:
Alarm: definitions for RMON SNMP traps to be sent when statistics exceed defined thresholds
164: 309:: RFC 4502 - Remote Network Monitoring Management Information Base Version 2 using SMIv2 275:
Network-Layer Matrix: layer 3 traffic statistics, per source/destination pairs of hosts
176: 160: 368: 168: 233:
Hosts: host specific LAN statistics e.g. bytes sent/received, frames sent/received
100: 17: 342: 42: 359: 278:
Application-Layer Host: traffic statistics by application protocol, per host
321:: RFC 2613 - Remote Network Monitoring MIB Extensions for Switched Networks 236:
Hosts top N: record of N most active connections over a given time period
193:, RMON is designed to operate differently than other SNMP-based systems: 159:(LANs). The original version (sometimes referred to as RMON1) focused on 205: 242:
Filter: defines packet data patterns of interest e.g. MAC address or
30:"Remote monitoring" redirects here. For the medical technology, see 220:
Statistics: real-time LAN statistics e.g. utilization, collisions,
303:: RFC 2819 - Remote Network Monitoring Management Information Base 209: 36: 272:
Network-Layer Host: layer 3 traffic statistics, per each host
327:: RFC 3577 - Introduction to the RMON Family of MIB Modules 269:
Address Map: maps network-layer (IP) to MAC-layer addresses
266:
Protocol Distribution: traffic statistics for each protocol
263:
Protocol Directory: list of protocols the probe can monitor
284:
User History: periodic samples of user-specified variables
290:
RMON Conformance: requirements for RMON2 MIB conformance
249:
Capture: collect and forward packets matching the Filter
239:
Matrix: the sent-received traffic matrix between systems
252:
Event: send alerts (SNMP traps) for the Alarm group
360:RAMON: open-source implementation of a RMON2 agent 287:Probe Configuration: remote configure of probes 155:to support monitoring and protocol analysis of 255:Token Ring: extensions specific to Token Ring 8: 127:Learn how and when to remove this message 227:History: history of selected statistics 216:The RMON1 MIB consists of ten groups: 63:Please improve this article by adding 7: 259:The RMON2 MIB adds ten more groups: 25: 41: 338:Network performance management 1: 65:secondary or tertiary sources 355:RMON: Remote Monitoring MIBs 27:Network monitoring standard 391: 29: 141:Remote Network Monitoring 32:Remote patient monitoring 52:relies excessively on 151:was developed by the 157:local area networks 375:Network management 175:monitoring and by 173:Application-layer 137: 136: 129: 111: 18:Remote monitoring 16:(Redirected from 382: 132: 125: 121: 118: 112: 110: 69: 45: 37: 21: 390: 389: 385: 384: 383: 381: 380: 379: 365: 364: 351: 334: 297: 186: 133: 122: 116: 113: 70: 68: 62: 58:primary sources 46: 35: 28: 23: 22: 15: 12: 11: 5: 388: 386: 378: 377: 367: 366: 363: 362: 357: 350: 349:External links 347: 346: 345: 340: 333: 330: 329: 328: 322: 316: 310: 304: 296: 295:Important RFCs 293: 292: 291: 288: 285: 282: 279: 276: 273: 270: 267: 264: 257: 256: 253: 250: 247: 240: 237: 234: 231: 228: 225: 202: 201: 198: 185: 182: 135: 134: 49: 47: 40: 26: 24: 14: 13: 10: 9: 6: 4: 3: 2: 387: 376: 373: 372: 370: 361: 358: 356: 353: 352: 348: 344: 341: 339: 336: 335: 331: 326: 323: 320: 317: 314: 311: 308: 305: 302: 299: 298: 294: 289: 286: 283: 280: 277: 274: 271: 268: 265: 262: 261: 260: 254: 251: 248: 245: 241: 238: 235: 232: 229: 226: 223: 219: 218: 217: 214: 211: 207: 199: 196: 195: 194: 192: 183: 181: 178: 174: 170: 166: 162: 158: 154: 150: 146: 142: 131: 128: 120: 109: 106: 102: 99: 95: 92: 88: 85: 81: 78: –  77: 73: 72:Find sources: 66: 60: 59: 55: 50:This article 48: 44: 39: 38: 33: 19: 324: 318: 312: 306: 300: 258: 215: 203: 187: 144: 140: 138: 123: 117:October 2010 114: 104: 97: 90: 83: 71: 51: 343:Network tap 161:OSI layer 1 87:newspapers 54:references 369:Category 332:See also 325:Overview 184:Overview 169:Network- 206:NetFlow 165:layer 2 101:scholar 313:HCRMON 224:errors 103:  96:  89:  82:  76:"RMON" 74:  307:RMON2 301:RMON1 210:SFlow 108:JSTOR 94:books 319:SMON 246:port 208:and 191:SNMP 177:SMON 171:and 163:and 153:IETF 145:RMON 139:The 80:news 244:TCP 222:CRC 149:MIB 56:to 371:: 147:) 67:. 143:( 130:) 124:( 119:) 115:( 105:· 98:· 91:· 84:· 61:. 34:. 20:)

Index

Remote monitoring
Remote patient monitoring

references
primary sources
secondary or tertiary sources
"RMON"
news
newspapers
books
scholar
JSTOR
Learn how and when to remove this message
MIB
IETF
local area networks
OSI layer 1
layer 2
Network-
Application-layer
SMON
SNMP
NetFlow
SFlow
CRC
TCP
Network performance management
Network tap
RMON: Remote Monitoring MIBs
RAMON: open-source implementation of a RMON2 agent

Text is available under the Creative Commons Attribution-ShareAlike License. Additional terms may apply.