
Configuring BayStack Remote Access
6-16 117341-A Rev. A
Example
When you enable a DCM, the RMON agent automatically creates a History
configuration. Suppose you then start a third-party RMON application that creates
its own History configuration for the agent. The RMON agent stores the data in
two places, wasting memory.
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 SNMP, or by resetting the DCM.
RMON Memory Use
The total amount of RMON memory depends on the DRAM installed in the DCM
(T
able 6-3).
The following sections describe how much memory you need to do the following:
• Configure an RMON group (for example, to configure the Matrix group or the
Filter and Packet Capture groups)
• Store the data for an RMON group (for example, to store the packets a DCM
captures)
Table 6-3. DRAM and RMON Memory Size
Installed DRAM (MB) RMON Memory (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.
Comments to this Manuals