Download PNETLab Platform

PNETLAB Store
PNETLab.com

Configure IP SLA Tracking and Path Control

Lab Topology:

https://user.pnetlab.com/store/labs/detail?id=16037342007891
Objectives:
§ Configure and verify the IP SLA feature.
§ Test the IP SLA tracking feature

1
Download PNETLab Platform
PNETLAB Store
PNETLab.com

Task:
1. Configure loopbacks and assign addresses
2. Configure static route
3. Configure IP SLA probes
4. Configure tracking options
5. Verify IP SLA operation

Solution:
Task 1: Configure loopbacks and assign addresses
R1 ISP1 ( R2) ISP2 (R3)
hostname R1 hostname ISP1 hostname ISP2
interface Loopback 0 interface Loopback0 interface Loopback0
description R1 LAN description Simulated description Simulated
ip address 192.168.1.1 Internet Web Server Internet Web Server
255.255.255.0 ip address 209.165.200.254 ip address 209.165.200.254
! 255.255.255.255 255.255.255.255
interface e0/0 ! !
description R1 --> ISP1 interface Loopback1 interface Loopback1
ip address description ISP1 DNS Server description ISP2 DNS Server
209.165.201.2 ip address 209.165.201.30 ip address 209.165.202.158
255.255.255.252 255.255.255.255 255.255.255.255
bandwidth 128 ! !
no shutdown interface e0/0 interface e0/0
! description ISP1 --> R1 description ISP2 --> R1
interface e0/1 ip address 209.165.201.1 ip address 209.165.202.129
description R1 --> ISP2 255.255.255.252 255.255.255.252
ip address bandwidth 128 bandwidth 128
209.165.202.130 no shutdown no shutdown
255.255.255.252 ! !
bandwidth 128 interface e0/1 interface e0/1
no shutdown description ISP1 --> ISP2 description ISP2 --> ISP1
ip address 209.165.200.225 ip address 209.165.200.226
255.255.255.252 255.255.255.252
bandwidth 128 bandwidth 128
no shutdown no shutdown

2
Download PNETLab Platform
PNETLAB Store
PNETLab.com

Verify the configuration by using the show interfaces description command:

R1#show interfaces description | include up

Et0/0 up up R1-ISP1

Et0/1 up up R1-ISP2

Lo0 up up R1 LAN

ISP1#show interfaces description | include up

Et0/0 up up ISP1-R1
Et0/1 up up ISP1-ISP2
Lo0 up up Simulated Internet Web Server
Lo1 up up ISP1 DNS Server

ISP2#show interfaces description | include up

Et0/0 up up ISP2-R1
Et0/1 up up ISP2-ISP1
Lo0 up up Simulated Internet Web Server
Lo1 up up ISP2 DNS Server

Task 2: Configure static routing

R1(config)# ip route 0.0.0.0 0.0.0.0 209.165.201.2

ISP 1 ISP2

ISP1(config)# router eigrp 1 ISP2(config)# router eigrp 1

ISP1(config-router)# network ISP2(config-router)# network

209.165.200.224 0.0.0.3 209.165.200.224 0.0.0.3

ISP1(config-router)# network ISP2(config-router)# network

209.165.201.0 0.0.0.31 209.165.202.128 0.0.0.31

ISP1(config-router)# no auto-summary ISP2(config-router)# no auto-summary

ISP1(config-router)# exit ISP2(config-router)# exit

3
Download PNETLab Platform
PNETLAB Store
PNETLab.com

! !

ISP1(config-router)# ip route ISP2(config)# ip route 192.168.1.0

192.168.1.0 255.255.255.0 255.255.255.0 209.165.202.130
209.165.201.2

Task 3: Configure IP SLA probes

R1(config)# ip sla 11

R1(config-ip-sla)# icmp-echo 209.165.201.30

R1(config-ip-sla-echo)# frequency 10

R1(config-ip-sla-echo)# exit

R1(config)# ip sla schedule 11 life forever start-time now

The operation number of 11 is only locally significant to the router. The frequency
10 command schedules the connectivity test to repeat every 10 seconds. The
probe is scheduled to start now and to run forever.
Although not actually required because IP SLA session 11 alone could provide the
desired fault tolerance, create a second probe, 22, to test connectivity to the
second DNS server located on router ISP2:

R1(config)# ip sla 22

R1(config-ip-sla)# icmp-echo 209.165.202.158

R1(config-ip-sla-echo)# frequency 10

R1(config-ip-sla-echo)# exit

R1(config)# ip sla schedule 22 life forever start-time now

R1(config)# end

4
Download PNETLab Platform
PNETLAB Store
PNETLab.com

Verify the new probe using the show ip sla configuration and show ip sla
statistics commands:

R1# show ip sla configuration 22

IP SLAs, Infrastructure Engine-II.

Entry number: 22

Owner:

Tag:

Type of operation to perform: icmp-echo

Target address/Source address: 209.165.201.158/0.0.0.0

Type Of Service parameter: 0x0

Request size (ARR data portion): 28

Operation timeout (milliseconds): 5000

Verify data: No

Vrf Name:

Schedule:

Operation frequency (seconds): 10 (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

Recurring (Starting Everyday): FALSE

5
Download PNETLab Platform
PNETLAB Store
PNETLab.com

Status of entry (SNMP RowStatus): Active

Threshold (milliseconds): 5000 (not considered if react RTT is configured)

Distribution Statistics:

Number of statistic hours kept: 2

Number of statistic distribution buckets kept: 1

Statistic distribution interval (milliseconds): 20

History Statistics:

Number of history Lives kept: 0

Number of history Buckets kept: 15

History Filter Type: None

Enhanced History:

R1# show ip sla statistics 22

IPSLAs Latest Operation Statistics

IPSLA operation id: 22

Latest RTT: 16 milliseconds

Latest operation start time: 10:38:29 UTC Sat Jan 10 2015

Latest operation return code: OK

Number of successes: 82

Number of failures: 0

Operation time to live: Forever

6
Download PNETLab Platform
PNETLAB Store
PNETLab.com

R1# show ip sla statistics

IPSLAs Latest Operation Statistics

IPSLA operation id: 11

Latest RTT: 8 milliseconds

Latest operation start time: 10:33:18 UTC Sat Jan 10 2015

Latest operation return code: OK

Number of successes: 51

Number of failures: 0

Operation time to live: Forever

Task 4: Configure tracking options.

R1(config)# ip route 0.0.0.0 0.0.0.0 209.165.201.2 5

R1(config)# track 1 ip sla 11 reachability

R1(config-track)# delay down 10 up 1

To view routing table changes as they happen, first enable the debug ip
routing command.

R1(config)# ip route 0.0.0.0 0.0.0.0 209.165.201.2 2 track 1

Jan 10 10:45:39.119: RT: updating static 0.0.0.0/0 (0x0) : via 209.165.201.1 0

1048578

Jan 10 10:45:39.119: RT: closer admin distance for 0.0.0.0, flushing 1 routes

Jan 10 10:45:39.119: RT: add 0.0.0.0/0 via 209.165.201.1, static metric [2/0]

7
Download PNETLab Platform
PNETLAB Store
PNETLab.com

Jan 10 10:45:39.119: RT: updating static 0.0.0.0/0 (0x0) : via 209.165.201.1 0

1048578

Jan 10 10:45:39.119: RT: rib update return code: 17

Jan 10 10:45:39.119: RT: updating static 0.0.0.0/0 (0x0) : via 209.165.201.1 0

1048578

Jan 10 10:45:39.119: RT: rib update return code: 17

Notice that the default route with an administrative distance of 5 has been
immediately flushed because of a route with a better admin distance. It then adds
the new default route with the admin distance of 2. Repeat the steps for
operation 22:

R1(config)# track 2 ip sla 22 reachability

R1(config-track)# delay down 10 up 1

R1(config-track)# exit

R1(config)#

R1(config)# ip route 0.0.0.0 0.0.0.0 209.165.202.129 3 track 2

Verify the routing table again:

R1#show ip route | begin Gateway

Gateway of last resort is 209.165.201.1 to network 0.0.0.0

S* 0.0.0.0/0 [2/0] via 209.165.201.1

192.168.1.0/24 is variably subnetted, 2 subnets, 2 masks

C 192.168.1.0/24 is directly connected, Loopback0

L 192.168.1.1/32 is directly connected, Loopback0

8
Download PNETLab Platform
PNETLAB Store
PNETLab.com

209.165.201.0/24 is variably subnetted, 2 subnets, 2 masks

C 209.165.201.0/30 is directly connected, e0/0

L 209.165.201.2/32 is directly connected, e0/0

209.165.202.0/24 is variably subnetted, 2 subnets, 2 masks

C 209.165.202.128/30 is directly connected, e0/1

L 209.165.202.130/32 is directly connected, e0/1

Task 5: Verify IP SLA operation

In this step you observe and verify the dynamic operations and routing changes
when tracked objects fail. The following summarizes the process:
• Disable the DNS loopback interface on ISP1 (R2).
• Observe the output of the debug command on R1.
• Verify the static route entries in the routing table and the IP SLA statistics of R1.
• Re-enable the loopback interface on ISP1 (R2) and again observe the operation
of the IP SLA tracking feature.

Ø On ISP1, disable the loopback interface 1

ISP1(config-if)# int lo1

ISP1(config-if)# shutdown

Ø On R1, observe the debug output being generated. Recall that R1 will wait
up to 10 seconds before initiating action therefore several seconds will
elapse before the output is generated:

R1#

Jan 10 10:53:59.551: %TRACK-6-STATE: 1 ip sla 11 reachability Up -> Down

Jan 10 10:53:59.551: RT: del 0.0.0.0 via 209.165.201.1, static metric [2/0]

9
Download PNETLab Platform
PNETLAB Store
PNETLab.com

Jan 10 10:53:59.551: RT: delete network route to 0.0.0.0/0

Jan 10 10:53:59.551: RT: default path has been cleared

Jan 10 10:53:59.551: RT: updating static 0.0.0.0/0 (0x0) :

via 209.165.202.129 0 1048578

Jan 10 10:53:59.551: RT: add 0.0.0.0/0 via 209.165.202.129, static metric [3/0]

Jan 10 10:53:59.551: RT: default path is now 0.0.0.0 via 209.165.202.129

Jan 10 10:53:59.551: RT: updating static 0.0.0.0/0 (0x0) : via 209.165.201.1 0

1048578

Jan 10 10:53:59.551: RT: rib update return code: 17

Jan 10 10:53:59.551: RT: updating static 0.0.0.0/0 (0x0) : via 209.165.202.129

0 1048578

Jan 10 10:53:59.551: RT: updating static 0.0.0.0/0 (0x0) : via 209.165.201.1 0

1048578

Jan 10 10:53:59.551: RT: rib update return code: 17

The tracking state of track 1 changes from up to down. On R1, verify the routing
table:

R1# show ip route | begin Gateway

Gateway of last resort is 209.165.202.129 to network 0.0.0.0

S* 0.0.0.0/0 [3/0] via 209.165.202.129

192.168.1.0/24 is variably subnetted, 2 subnets, 2 masks

C 192.168.1.0/24 is directly connected, Loopback0

L 192.168.1.1/32 is directly connected, Loopback0

10
Download PNETLab Platform
PNETLAB Store
PNETLab.com

209.165.201.0/24 is variably subnetted, 2 subnets, 2 masks

C 209.165.201.0/30 is directly connected, e0/0

L 209.165.201.2/32 is directly connected, e0/0

209.165.202.0/24 is variably subnetted, 2 subnets, 2 masks

C 209.165.202.128/30 is directly connected, e0/1

L 209.165.202.130/32 is directly connected, e0/1

Verify the IP SLA statistics:

R1# show ip sla statistics

IPSLAs Latest Operation Statistics

IPSLA operation id: 11

Latest RTT: NoConnection/Busy/Timeout

Latest operation start time: 11:01:08 UTC Sat Jan 10 2015

Latest operation return code: Timeout

Number of successes: 173

Number of failures: 45

Operation time to live: Forever

IPSLA operation id: 22

Latest RTT: 8 milliseconds

Latest operation start time: 11:01:09 UTC Sat Jan 10 2015

Latest operation return code: OK

Number of successes: 218

11
Download PNETLab Platform
PNETLAB Store
PNETLab.com

Number of failures: 0

Operation time to live: Forever

12