Avaya Configuring SNMP, BOOTP, DHCP, and RARP Services Manual de usuario descargar pdf (Pagina 28)

Configuring SNMP, BOOTP, DHCP, and RARP Services

1-10

Read the following sections to learn about RMON memory use and

interoperability issues you should consider when using RMON network

management applications with the DCM. These sections assume that you have a

good understanding of each RMON group, and do not refer to the low-level

details of the MIB, such as RMON MIB objects. Refer to “Remote Network

Monitoring (RMON),” earlier in this chapter, and RFC 1757 for information about

each RMON group.

RMON Interoperability Issues

Some network management applications automatically set up their own

conﬁgurations for an RMON group, without checking to see if the RMON agent

already has a default conﬁguration. In addition, when you terminate those

applications, they may not remove the conﬁgurations 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 a DCM, the RMON agent automatically creates a History

conﬁguration. Suppose you then start a third-party RMON History application,

which creates its own History conﬁguration 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 conﬁguration, using memory and processing power

indeﬁnitely.

You can only release these resources 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 1-3).

1 2 ... 23 24 25 26 27 28 29 30 31 32 33 ... 107 108

Sin comentarios

Avaya Configuring SNMP, BOOTP, DHCP, and RARP Services Manual de usuario Pagina 28