IP-SLA guidelines

  • ArubaOS-CX supports only SLA configuration through CLI and thresholds can be configured using NAE agents using WebUI/REST.

  • ArubaOS-CX supports only forever tests. On-demand tests are not supported.

  • Maximum sessions: IP-SLA source 500, IP-SLA responder 100.

  • NAE can effectively monitor a maximum of 300 parameters, reducing the maximum supported session by 300.

  • NAE supports only syslog.

  • NAE agents must be triggered for each IP-SLA test on every switch.

  • If multiple IP addresses are received for a DNS query, DNS works with the first resolved IP.

  • When the DNS server IP is not configured, the first DNS server in resolve.conf is used.

  • The source interface/IP option is not applicable for SLAs configured on 'mgmt' VRF, as it has only one interface.

  • A system time change because of NTP or a manual change causes an incorrect calculation.

  • There is no interoperability of UDP echo SLA between ArubaOS-CX and FlexFabric switches.

  • Source IP and source port combination must be unique across SLA sessions in a same switch.

  • Do not use the same source port across the source and responder sessions in a switch.

  • NTP synchronization is a must for SLA types involving one-way delay such as UDP jitter VoIP.

  • It is mandatory to set default CoPP to the max value when UDP jitter SLA is enabled otherwise 100% packet loss can be seen and UDP-Jitter sla probe will result in failure as seen in the following example. 

    copp-policy default
     class hypertext priority 6 rate 50000 burst 64
     default-class priority 6 rate 99999 burst 9999

  • Deviations with respect to PVOS results: The packet losses due to internal switch-related issues like interface shutdown or interface flaps will not be considered as 'Probes Timed-out error', as the IP-SLA solution is to measure network performance and anomalies. Rather, this kind of packet loss will be counted in internal counters like 'Destination address unreachable'.