Avaya 3500 Series Troubleshooting Manual page 22

Troubleshooting fundamentals
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 will reregister 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.
QoS tests
SLA Monitor uses two types of tests to determine QoS benchmarks:
• Real Time Protocol (RTP)
This test measures network performance, for example, jitter, delay, and loss, by injecting
a short stream of UDP packets from source to destination (an SLA Monitor agent).
• New Trace Route (NTR)
This test is similar to traceroute but also includes DSCP values at each hop in the path
from the source to the destination. The destination does not need to be an SLA Monitor
agent.
Limitations
SLA Monitor agent communications are IPv4–based. Agent communications do not currently
support IPv6.
22 Troubleshooting 5.1
Comments? infodev@avaya.com
February 2013