
Configuring AN and ANH Features
114074 Rev. A 6-25
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 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, because 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.
History Group
When you enable the DCM, the RMON agent automatically creates a History
configuration that collects History data at two intervals. The first configuration
provides short-term history by sampling statistics every 30 seconds and holding
up to 50 samples (in RMON terms “buckets”). The second configuration provides
long-term history by sampling statistics every 30 minutes and holding up to 50
buckets.
Through your RMON network management application, you can create as many
History configurations as memory permits, up to the RMON limit of 65,535
configurations.You can also set the number of buckets a particular History
configuration uses to as many as available memory allows. If you request more
buckets than memory allows, the agent allocates enough buckets to fill available
memory.
You need 504 bytes of memory for each History configuration (252 bytes each for
the short-term and long-term History configurations).
Comentarios a estos manuales