The switch supports the SLA Mon agent. You must have an Avaya Diagnostic Server with SLA Mon technology in your network to use the SLA Mon feature. Most of the SLA Mon configuration occurs on the server; configuration on the SLA Mon agent is minimal.
The SLA Mon server initiates the SLA Mon 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 Mon 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 Mon implementation.
An SLA Mon agent remains dormant until it receives a User Datagram Protocol (UDP) discovery packet from a server. The agent accepts the discovery packet to register with an SLA Mon server. If the registration process fails, the agent remains dormant until it receives another discovery packet.
An agent can attempt to register with an SLA Mon server once every 60 seconds. After a successful registration, the agent reregisters with the server every 6 hours to exchange a new encryption key.
An agent only accepts commands from the SLA Mon server to which it is registered. An agent can use alternate SLA Mon servers to provide backup for time-out and communication issues with the primary SLA Mon server.
Note
If you configure the SLA Mon agent address under an IP address for a VLAN or brouter, you must remove the SLA Mon address before you can remove the IP address for the VLAN or brouter.
SLA Monitor agent provides partial HA support. In HA mode, the agent startup and initialization occurs only on the master CP module. When reset occurs, the standby CP takes over the operations. Based on the SLAMon agent operation-mode, the agent on the standby CP restarts the initialization and registration and gets registered only when the server sends a discovery. The user configuration updates on the Master CP is saved on the Standby CP and used when the reset occurs.