3com 2928 User Guide

Page of 505
 
1-3 
z
 
Log-Trap: Logging event information in the event log table and sending a trap to the NMS. 
z
 
None: No action. 
Configuring RMON 
Configuration Task List 
Configuring the RMON statistics function 
RMON statistics function can be implemented by either the statistics group or the history group, but the 
objects of the statistics are different. You can choose to configure a statistics group or a history group 
accordingly. 
z
 
A statistics object of the statistics group is a variable defined in the Ethernet statistics table, and the 
recorded content is a cumulative sum of the variable from the time the statistics entry is created to 
the current time. Perform the tasks in 
 to configure RMON Ethernet statistics function. 
z
 
A statistics object of the history group is the variable defined in the history record table, and the 
recorded content is a cumulative sum of the variable in each period. Perform the tasks in 
 
to configure RMON history statistics function. 
Table 1-1 
RMON statistics group configuration task list 
Task 
Remarks 
Required 
You can create up to 100 statistics entries in a statistics table. 
After a statistics entry is created on an interface, the system collects 
statistics on various traffic information on the interface. It provides 
statistics about network collisions, CRC alignment errors, 
undersize/oversize packets, broadcasts, multicasts, bytes received, 
packets received, and so on. The statistics are cleared after the device 
reboots. 
 
Only one statistics entry can be created on one interface. 
 
Table 1-2 
RMON history group configuration task list 
Task 
Remarks 
Required 
You can create up to 100 history entries in a history table. 
After an entry is created, the system periodically samples the number of 
packets received/sent on the current interface, and saves the statistics as 
an instance under the leaf node of the etherHistoryEntry table. 
 
When you create an entry, if the value of the specified sampling interval is 
identical to that of the existing history entry, the system considers their 
configurations are the same and the creation fails.