Avaya Configuring SNMP, RMON, BOOTP, DHCP, and RARP Services Uživatelský manuál Strana 50

  • Stažení
  • Přidat do mých příruček
  • Tisk
  • Strana
    / 148
  • Tabulka s obsahem
  • KNIHY
  • Hodnocené. / 5. Na základě hodnocení zákazníků
Zobrazit stránku 49
Configuring SNMP, RMON, BOOTP, DHCP, and RARP Services
2-18 114070 Rev. B
RMON Applications
Some network management applications automatically set up their own
configurations for an RMON group, without checking to see if the RMON agent
already has a default configuration. In addition, when you terminate those
applications, they may not remove the configurations they set up for the RMON
agent. These features can result in the RMON agent using excessive amounts of
memory and processing power.
Example
When you enable an Ethernet DCM, the RMON agent automatically creates a
History configuration. Suppose you then start a third-party RMON History
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 the
SNMP tool or network management station, or by resetting the Ethernet DCM. If
you use too many resources for an RMON task, the DCM can run out of memory
for other RMON tasks and perform more slowly.
RMON Memory Use
The total amount of available RMON memory depends on the dynamic random
access memory (DRAM) in the Ethernet DCM (T
able 2-3).
Table 2-3. DRAM and RMON Memory Size
Installed DRAM (MB)
Available RMON
Memory in Bytes
2 162,578
4 2,077,330
8 5,222,034
16 12,561,042
Zobrazit stránku 49
1 2 ... 45 46 47 48 49 50 51 52 53 54 55 ... 147 148

Komentáře k této Příručce

Žádné komentáře