NOTE:
5400R requires V3 modules
◦ UDP Jitter
◦ UDP Jitter Voip
◦ UDP Echo
◦ TCP connect
◦ ICMP echo
◦ DHCP
• Measurement of RTT and jitter values is in milliseconds.
• IPv6 SLA for UDP jitter and VoIP is not supported.
• UDP jitter and UDP jitter for VoIP tests are not supported over Tunnel, Trunk, and OOBM interfaces.
• UDP jitter and UDP jitter for VoIP results are not carried forward across failover or a device reboot.
• History bucket size cannot be configured for UDP jitter and VoIP tests. Results are aggregated for the last 25
probes.
• System clocks between the source and the responder must be synchronized with NTP if One Way Delay
parameters have to be calculated for UDP Jitter & UDP Jitter for VoIP tests.
• The UDP jitter and UDP jitter for VoIP feature on ArubaOS-Switch has the following limited interoperability with
Comware 7 SLA v2 version:
◦ One Way packet drops (SD packet loss and DS packet loss) on the Comware Jitter initiator is not reported
when interoperating with Aruba Jitter Responder.
• IP SLA responder or initiator implementation is not interoperable with Cisco's IP SLA feature.
How IP SLA works
1.
The source originates a test packet to the destination.
2.
The destination responds to the test packet, at times embedding the needed information in the response
packet.
3.
Upon receiving the response, the source calculates the test results based on the timestamp, other packet
parameters, and so on.
4.
The source stores the results and updates the history records for the SLA.
5.
The source reschedules the SLA for the next run.
NOTE:
For one-way delay calculations, the IP SLA sender and IP SLA responder must be NTP Time
Synchronized.
Configuration commands
[no] ip-sla <ID>
Syntax
[no] ip-sla <ID>
588
Aruba 2930F / 2930M Management and Configuration Guide
for ArubaOS-Switch 16.08
