Procedure https://cll-ng.cisco.

com/content/xtrac/1

Discovery 24: Configure and Verify Cisco IP SLAs

Task 1: Configure an IP SLA Echo Operation
Activity
Step 1: On the HQ router, define the IP SLA with the number 1.
HQ(config)# ip sla 1
This step defines the IP SLA operation number. The operation number is an arbitrarily chosen number that
uniquely identifies an IP SLA test.
Step 2: Configure IP SLA 1 on HQ to perform ICMP echo tests to the BR IP address of 172.16.22.254.
HQ(config-ip-sla)# icmp-echo 172.16.22.254
HQ(config-ip-sla)# exit
HQ(config)#
Configuring the test to perform starts with the test-type keyword. In this example, the test type is icmp-echo. The
test type is followed by a list of parameters. In an ICMP echo IP SLA, the only mandatory parameter is the
destination IP address. In this example, the destination IP address is that of BR—172.16.22.254.
It is a good idea to configure an IP SLA to the remote router’s loopback interface if there are multiple paths to
reach that router.
Note
You must use the keyword type before defining the test type. So this example would be type icmp-echo
172.16.22.254.
Step 3: From global config, schedule IP SLA 1 on HQ to perform an ICMP echo test.
HQ(config)# ip sla schedule 1 life forever start-time now
The ip sla schedule command schedules when the test starts, for how long it runs, and for how long the collected
data is kept.
Router(config)# ip sla schedule operation-number [life {forever | seconds}] [start-time {hh:MM[:ss] [month day
| day month] | pending | now | after hh:mm:ss}] [ageout seconds] [recurring]
With the life keyword, you set how long the IP SLA test will run. If you choose forever, the test will run until you
manually remove it. By default, the IP SLA test will run for 1 hour.
With the start-time keyword, you set when the IP SLA test should start. You can start the test right away by
issuing the now keyword, or you can configure a delayed start.
With the ageout keyword, you can control how long the collected data is kept.
With the recurring keyword, you can schedule a test to run periodically—for example, at the same time each day.
Note
After an IP SLA test is scheduled to run, you will not be able to modify it.
Step 4: On HQ, verify the IP SLA configuration.
HQ# show ip sla configuration
IP SLAs Infrastructure Engine-III
Entry number: 1
Owner:

1 din 4 27.05.2020, 09:29

Procedure https://cll-ng.cisco.com/content/xtrac/1

Tag:
Operation timeout (milliseconds): 5000
Type of operation to perform: icmp-echo
Target address/Source address: 172.16.22.254/0.0.0.0
Type Of Service parameter: 0x0
Request size (ARR data portion): 28
Verify data: No
Vrf Name:
Schedule:
Operation frequency (seconds): 60 (not considered if randomly scheduled)
Next Scheduled Start Time: Start Time already passed
Group Scheduled : FALSE
Randomly Scheduled : FALSE
Life (seconds): Forever
Entry Ageout (seconds): never
<... output omitted ...>
When you verify the IP SLA configuration on HQ, you should see IP SLA 1 enabled to perform ICMP echo tests
from the local device to the IP address of 172.16.22.254. The operation frequency is set to 60 seconds and that test
will run forever, and collected entries will never age out.
Step 5: On HQ, verify the IP SLA statistics.
HQ# show ip sla statistics
IPSLAs Latest Operation Statistics

IPSLA operation id: 1

Latest RTT: 1 milliseconds
Latest operation start time: 23:31:26 PST Mon Jan 6 2014
Latest operation return code: OK
Number of successes: 32
Number of failures: 0
Operation time to live: Forever
Use the show ip sla statistics command to investigate the results of the test. In this example, the latest IP SLA 1
echo test had a response time of 1 millisecond, the IP SLA was successfully performed 32 times and it never
failed.
You can add the aggregated keyword to view a more summarized output of the show ip sla statistics command.
You can add the details keyword to view a more detailed output of the show ip sla statistics command.
Note
The show ip sla application command will show you which operations are supported on the platform and how
many operations are configured or active.

Task 2: Configure an IP SLA Jitter Operation

Activity
The IP SLA UDP jitter operation was designed primarily to diagnose network suitability for real-time traffic
applications such as VoIP, video over IP, or real-time conferencing.
Jitter defines inter-packet delay variance. When multiple packets are sent consecutively from the source to
destination, for example, 10 milliseconds apart, and the network is behaving ideally, the destination should receive
each packet 10 milliseconds apart. But if there are delays in the network (like queuing, arriving through alternate
routes, and so on) the arrival delay between packets might be greater than or less than 10 milliseconds.
Step 1: On the HQ router, define the IP SLA with the number 2.
HQ(config)# ip sla 2
This step defines the IP SLA operation number. The operation number is an arbitrarily chosen number that

2 din 4 27.05.2020, 09:29

Procedure https://cll-ng.cisco.com/content/xtrac/1

uniquely identifies an IP SLA test.

Step 2: Configure IP SLA 2 on HQ to perform a UDP jitter test to the BR IP address of 172.16.22.254.
HQ(config-ip-sla)# udp-jitter 172.16.22.254 65051 num-packets 20
HQ(config-ip-sla)# request-data-size 160
HQ(config-ip-sla)# frequency 30
HQ(config-ip-sla)# exit
HQ(config)#
From the IP SLA configuration mode, you define the UDP jitter test:
Router(config-ip-sla)# udp-jitter dest-ip-add dest-udp-port [source-ip src-ip-add] [source-port src-udp-port]
[num-packets num-of-packets] [interval packet-interval]
With the UDP jitter IP SLA configuration, you can specify the destination IP address, the port number that is used
for the packet stream, and the number of packets sent.
By default 10 packets, which are spaced at 20 milliseconds each, will be sent. You can override this behavior by
specifying the num-packets and interval keywords.
By default, the payload size for each packet is 10 bytes and the time between operations is every 60 secs. You can
override these settings with the request-data-size and frequency commands.
In this example, 20, 160-byte packets, will be sent 20 milliseconds apart every 30 seconds.
Step 3: From global config, schedule IP SLA 2 on HQ to perform the jitter test.
HQ(config)# ip sla schedule 2 start-time now
HQ(config)# exit
The test operation will begin right away by issuing the now keyword, or you can configure a delayed start.
Step 4: Configure Branch as an IP SLA responder.
Branch(config)# ip sla responder
Step 5: Back on HQ, verify the IP SLA configuration.
HQ# show ip sla configuration

Entry number: 2
Owner:
Tag:
Operation timeout (milliseconds): 5000
Type of operation to perform: udp-jitter
Target address/Source address: 172.16.22.254/0.0.0.0
Target port/Source port: 65051/0
<...output omitted...>
Schedule:
Operation frequency (seconds): 30 (not considered if randomly scheduled)
Next Scheduled Start Time: Start Time already passed
Group Scheduled : FALSE
Randomly Scheduled : FALSE
Life (seconds): 3600
Entry Ageout (seconds): never
Recurring (Starting Everyday): FALSE
Status of entry (SNMP RowStatus): Active
<...output omitted...>
When you verify the IP SLA configuration on HQ, you should see IP SLA 2 enabled to perform UDP jitter tests
from the local device to the IP address of 172.16.22.254.
Step 6: On HQ, verify the IP SLA statistics.
HQ# show ip sla statistics

3 din 4 27.05.2020, 09:29

Procedure https://cll-ng.cisco.com/content/xtrac/1

<...output omitted...>
IPSLA operation id: 2
Type of operation: udp-jitter
Latest RTT: 1 milliseconds
Latest operation start time: 17:26:19 PST Mon Jun 17 2019
Latest operation return code: OK
RTT Values:
Number Of RTT: 20 RTT Min/Avg/Max: 1/1/2 milliseconds
Latency one-way time:
Number of Latency one-way Samples: 5
Source to Destination Latency one way Min/Avg/Max: 1/0/1 milliseconds
Destination to Source Latency one way Min/Avg/Max: 0/0/1 milliseconds
Jitter Time:
Number of SD Jitter Samples: 19
Number of DS Jitter Samples: 19
Source to Destination Jitter Min/Avg/Max: 0/1/1 milliseconds
Destination to Source Jitter Min/Avg/Max: 0/1/1 milliseconds
Packet Loss Values:
Loss Source to Destination: 0
Source to Destination Loss Periods Number: 0
Source to Destination Loss Period Length Min/Max: 0/0
Source to Destination Inter Loss Period Length Min/Max: 0/0
Loss Destination to Source: 0
Destination to Source Loss Periods Number: 0
Destination to Source Loss Period Length Min/Max: 0/0
Destination to Source Inter Loss Period Length Min/Max: 0/0
Out Of Sequence: 0 Tail Drop: 0
Packet Late Arrival: 0 Packet Skipped: 0
Voice Score Values:
Calculated Planning Impairment Factor (ICPIF): 0
Mean Opinion Score (MOS): 0
Number of successes: 6
Number of failures: 0
Operation time to live: 3125 sec
Use the show ip sla statistics command to investigate the results of the test. In this example, the IP SLA 2 test on
HQ was successfully performed 6 times and the test has never failed.
A positive jitter value indicates that the packets arrived more than 10 milliseconds apart. If the packets arrive 12
milliseconds apart, then the positive jitter is 2 milliseconds; if the packets arrive 8 milliseconds apart, then the
negative jitter is 2 milliseconds. For delay-sensitive networks like VoIP, positive jitter values are undesirable, and
a jitter value of 0 is ideal.

© 2020 Cisco Systems, Inc.

4 din 4 27.05.2020, 09:29