
Connecting BayStack AN and ANH Systems to a Network
6-24 114074 Rev. A
In addition, when you terminate the third-party RMON application, it does not
remove its History configuration, using memory and processing power
indefinitely.
You can release these resources only by using another application, such as the
SNMP tool or network management station, or by resetting the DCM. If you use
too many resources for an RMON task, the DCM can run out of memory for other
RMON tasks and performs more slowly.
RMON Memory Use
The total amount of RMON memory depends on the DRAM in the DCM
(Table 6-1).
The following sections describe how much memory you need to
• Configure an RMON group (for example, to configure the Matrix group or to
configure Filter and Packet Capture groups).
• Store the data for an RMON group (for example, to store the packets a 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.
Table 6-1. DRAM and RMON Memory Size
Installed DRAM (MB) RMON Memory in Bytes
2 162,578
4 2,077,330
8 5,222,034
16 12,561,042
Note: 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.
Commentaires sur ces manuels