User's Manual

450 CHAPTER 10: RMON
Table creation or deletion may fail if:
■ an incorrect community string is used
■ there are insufficient resources on the target device to create a table
You should try to delete RMON tables from a device when you no longer
require them. RMON tables take up resources on network devices, and
may affect the device's performance.
Be careful not to delete tables that you yourself did not create - they may
be in use by 3Com Network Director, or by another management
application on your network.
Examples This section describes some RMON examples supported by 3Com
Network Director.
How do I graph errors
on my core switch
links?
The RMON Statistics group contains useful error counters for interfaces
on devices that support this table. The RMON history group contains the
same values stored historically for predefined sampling periods. The
RMON host and matrix groups allow you to see the same data broken
down by specific hosts on the network.
If you know which interface on your core switch you are interested in,
launch RMON directly from the device icon on the 3Com Network
Director map. Alternatively, launch it from the right-click menu of an
attached link.
Launch your chosen RMON group, and from the View, select the Errors
view. clicking OK will launch RMONView, which will fetch and display the
following:
Table 78 Errors
Statistics Live counts of total errors seen on this interface
History Historical counts of total errors seen on this interface
Host Error packets transmitted by each host seen on this
interface
Matrix Error packets included in every conversation between
pairs of hosts seen on this interface.