
RMON Configuration
353
View name:ViewDefault
MIB Subtree:snmpModules.18
Subtree mask:
Storage-type: nonVolatile
View Type:excluded
View status:active
RMON Configuration
Remote Network Monitoring (RMON) is a type of IETF-defined MIB. It is the most
important enhancement to the MIB II standard. It is mainly used for monitoring
the data traffic on a segment and even on a whole network. It is one of the most
widely used Network Management standards.
RMON is implemented fully based on the SNMP architecture (which is one of its
outstanding advantages) and compatible with the existing SNMP framework, and
therefore it is unnecessary to adjust the protocol. RMON includes NMS and the
Agent running on the network devices. On the network monitor or detector,
RMON Agent tracks and accounts different traffic information on the segment
connected to its port, such as the total number of packets on a segment in a
certain period of time or that of the correct packets sent to a host. RMON helps
SNMP monitor the remote network device more actively and effectively, which
provides a highly efficient means for the monitoring of the subnet operations.
RMON can reduce the communication traffic between the NMS and the agent,
thus facilitating effective management over large interconnected networks.
RMON allows multiple monitors. It can collect data in two ways.
■
One is to collect data with a special RMON probe. NMS directly obtains the
management information from the RMON probe and controls the network
resource. In this way, it can obtain all the information of the RMON MIB.
■
Another way is to implant the RMON Agent directly into the network devices
(such as a Switch, Hub, etc.), so that the devices become network facilities with
RMON probe function. RMON NMS uses the basic SNMP commands to
exchange data information with SNMP Agent and collect NM information.
However, limited by the device resources, normally, not all the data of the
RMON MIB can be obtained with this method. In most cases, only four groups
of information can be collected. The four groups include trap information,
event information, history information and statistics information.
The Switch implements RMON as described in the second bullet point above. With
the RMON-supported SNMP Agent running on the network monitor, NMS can
obtain such information as the overall traffic of the segment connected to the
managed network device port, the error statistics and performance statistics,
thereby implementing the management (generally remote management) over the
network.
Configuring RMON
RMON configuration includes:
■
Add/Delete an Entry to/from the Alarm table
■
Add/Delete an Entry to/from the Event table
■
Add/Delete an Entry to/from the History Control terminal
■
Add/Delete an Entry to/from the extended RMON alarm table
Summary of Contents for SuperStack 4
Page 6: ...18 ABOUT THIS GUIDE ...
Page 34: ...46 CHAPTER 1 GETTING STARTED ...
Page 62: ...74 CHAPTER 3 VLAN OPERATION ...
Page 69: ...PoE Configuration 81 ...
Page 70: ...82 CHAPTER 4 POWER OVER ETHERNET POE CONFIGURATION ...
Page 98: ...110 CHAPTER 5 NETWORK PROTOCOL OPERATION ...
Page 220: ...232 CHAPTER 8 ACL CONFIGURATION ...
Page 408: ...420 CHAPTER B RADIUS SERVER AND RADIUS CLIENT SETUP ...
Page 432: ...444 APPENDIX D 3COM XRN ...