When running IP SLA, which application type should be used if you want to know round-trip delay,
jitter, and packet loss for the full path?
A.
ICMP path echo
B.
UDP echo
C.
ICMP path jitter
D.
Application Performance Monitor
E.
TCP connect
Explanation:
Before configuring any IP SLAs application, you can use the show ip sla application command to
verify that the operation type is supported on your software image. In contrast with other IP SLAs
operations, the IP SLAs Responder does not have to be enabled on either the target device or
intermediate devices for Path Jitter operations. However, the operational efficiency may improve if
you enable the IP SLAs Responder. The IP SLAs ICMP Path Jitter operation is ICMP-based.
ICMP-based operations can compensate for source processing delay but cannot compensate for
target processing delay. For more robust monitoring and verifying, use of the IP SLAs UDP Jitter
operation is recommended. The jitter values obtained using the ICMP Path Jitter operation are
approximates because ICMP does not provide the capability to embed processing times on
routers in the packet. If the target router does not place ICMP packets as the highest priority, then
the router will not respond properly. ICMP performance also can be
affected by the configuration of priority queueing on the router and by ping response.
The path jitter operation does not support hourly statistics and hop information.
Unlike other IP SLAs operations, the ICMP Path Jitter operation is not supported in the RTTMON
MIB. Path Jitter operations can only be configured using Cisco IOS commands and statistics can
only be returned using the show ip sla commands. The IP SLAs Path Jitter operation does not
support the IP SLAs History feature (statistics history buckets) because of the large data volume
involved with Jitter operations.