Avaya 8800 Troubleshooting Manual page 46

Troubleshooting tool fundamentals
The SLA Monitor server initiates the SLA Monitor functions on one or more agents, and the
agents run specific QoS tests at the request of the server. Agents can exchange packets
between one another to conduct the QoS tests.
SLA Monitor can monitor a number of key items, including the following:
• network paths
• Differentiated Services Code Point (DSCP) markings
• loss
• jitter
• delay
The following figure shows an SLA Monitor implementation.
Figure 2: SLA Monitor network
An SLA Monitor agent remains dormant until it receives a User Datagram Protocol (UDP)
discovery packet from the a server. The agent accepts the discovery packet to register with
an SLA Monitor server. If the registration process fails, the agent remains dormant until it
receives another discovery packet.
An agent can attempt to register with a server once every 60 seconds. After a successful
registration, the agent reregisters with the server every 6 hours to exchange a new encryption
key, if encryption is supported.
An agent only accepts commands from the server to which it is registered. An agent can use
alternate servers to provide backup for timeout and communication issues with the primary
server.
46 Troubleshooting
Comments? infodev@avaya.com
July 2013