
SNMP, RMON, BOOTP, DHCP, and RARP Concepts
114070 Rev. B 2-19
If the RMON memory pool is full or if the RMON agent reaches an
implementation limit, the agent responds to an SNMP set command
on an
RMON control table entry with an SNMP GEN-ERROR.
The following sections describe how much memory you need to
• Configure an RMON group (for example, to configure the Matrix group or to
configure the Filter and Capture groups)
• Store the data for an RMON group (for example, to store the packets on
Ethernet DCM captures)
In the following sections, the word configuration means the set of control tables
for a group. For example, a Matrix configuration includes only the
matrixControlTable. Note that you can create more than one configuration for
some RMON groups. For example, you can create more than one History
configuration, allowing you to specify different intervals for sampling statistics.
Interoperability Issues and Memory Use for RMON Groups
You should understand the following issues about each RMON group’s memory
requirements and ability to operate with third-party RMON network management
applications.
Statistics Group
When you enable the Ethernet DCM, the RMON agent automatically creates a
Statistics configuration that records data for each network interface. Through your
RMON network management application, you can create as many Statistics
configurations as memory permits, up to the RMON limit of 65,535
configurations.
If you create multiple configurations, it is possible to collect the same set of
statistics for the same interface in multiple data tables. The absolute values of
those statistics may vary from table to table, since the baseline of each statistics
counter occurs when you create a configuration. You may prefer, however, to use
only one Statistics configuration, to conserve memory for other RMON groups.
You need 200 bytes of memory for each Statistics configuration.
Commentaires sur ces manuels