34
RMON C
ONFIGURATION
Introduction to RMON
Remote monitoring (RMON) is a kind of management information base (MIB)
defined by Internet Engineering Task Force (IETF). It is an important enhancement
made to MIB II standards. RMON is mainly used to monitor the data traffic across a
network segment or even the entire network, and is currently a commonly used
network management standard.
An RMON system comprises of two parts: the network management station
(NMS) and the agents running on network devices. RMON agents operate on
network monitors or network probes to collect and keep track of the statistics of
the traffic across the network segments to which their ports connect, such as the
total number of the packets on a network segment in a specific period of time and
the total number of packets successfully sent to a specific host.
■
RMON is fully based on SNMP architecture. It is compatible with the current
SNMP implementations.
■
RMON enables SNMP to monitor remote network devices more effectively and
actively, thus providing a satisfactory means of monitoring remote subnets.
■
With RMON implemented, the communication traffic between NMS and SNMP
agents can be reduced, thus facilitating the management of large-scale
internetworks.
Working Mechanism of
RMON
RMON allows multiple monitors. It can collect data in the following two ways:
■
Using the dedicated RMON probes. When an RMON system operates in this
way, the NMS directly obtains management information from the RMON
probes and controls the network resources. In this case, all information in the
RMON MIB can be obtained.
■
Embedding RMON agents into network devices (such as routers, switches and
hubs) directly to make the latter capable of RMON probe functions. When an
RMON system operates in this way, the NMS collects network management
information by exchanging information with the SNMP agents using the basic
SNMP commands. However, this way depends on device resources heavily and
an NMS operating in this way can only obtain the information about these four
groups (instead of all the information in the RMON MIB): alarm group, event
group, history group, and statistics group.
The 3Com Switch 4210 implements RMON in the second way. With an RMON
agent embedded, the Switch 4210 can serve as a network device with the RMON
probe function. Through the RMON-capable SNMP agents running on the switch,
an NMS can obtain the information about the total traffic, error statistics and
performance statistics of the network segments to which the ports of the
Summary of Contents for Switch 4210 9-Port
Page 22: ...20 CHAPTER 1 CLI CONFIGURATION ...
Page 74: ...72 CHAPTER 3 CONFIGURATION FILE MANAGEMENT ...
Page 84: ...82 CHAPTER 5 VLAN CONFIGURATION ...
Page 96: ...94 CHAPTER 8 IP PERFORMANCE CONFIGURATION ...
Page 108: ...106 CHAPTER 9 PORT BASIC CONFIGURATION ...
Page 122: ...120 CHAPTER 11 PORT ISOLATION CONFIGURATION ...
Page 140: ...138 CHAPTER 13 MAC ADDRESS TABLE MANAGEMENT ...
Page 234: ...232 CHAPTER 17 802 1X CONFIGURATION ...
Page 246: ...244 CHAPTER 20 AAA OVERVIEW ...
Page 270: ...268 CHAPTER 21 AAA CONFIGURATION ...
Page 292: ...290 CHAPTER 26 DHCP BOOTP CLIENT CONFIGURATION ...
Page 318: ...316 CHAPTER 29 MIRRORING CONFIGURATION ...
Page 340: ...338 CHAPTER 30 CLUSTER ...
Page 362: ...360 CHAPTER 33 SNMP CONFIGURATION ...
Page 368: ...366 CHAPTER 34 RMON CONFIGURATION ...
Page 450: ...448 CHAPTER 39 TFTP CONFIGURATION ...
Page 451: ......
Page 452: ...450 CHAPTER 39 TFTP CONFIGURATION ...
Page 470: ...468 CHAPTER 40 INFORMATION CENTER ...
Page 496: ...494 CHAPTER 44 DEVICE MANAGEMENT ...