CloudLabBox
Try the free demo

CCNP ENARSI lab 13 of 35

Path control with PBR, IP SLA and tracked static routes

Give a dual-homed branch a default route that fails over when the provider's core breaks, not just when the local link goes down, and send guest traffic over the cheaper link with policy-based routing that falls back safely.

Run this lab

It needs Lite: its 6 nodes are set to 6 vCPU and 4,096 MB in total. That fits the free demo too.

In your workspace: Shared, then CCNP ENARSI 300-410 guided labs, then 13 - Path control with PBR IP SLA and tracked static routes

Try it free for 30 minutesRun it on Lite from £3 a day

The free demo needs no card and no email. Every lab plan includes every guided lab.

Level
Intermediate
Time
About 70 minutes
Nodes need
6 vCPU, 4,096 MB
Smallest plan
Lite

The scenario

Sparrowhawk Travel's branch router (R1) has two WAN links: a reliable MPLS circuit through R2 and a cheaper broadband link through R3. Both providers deliver traffic to head office (R4, servers on 10.4.4.0/24). R1 currently has one static default route through the MPLS circuit. Last month the provider's core failed between R2 and head office: R1's link to R2 stayed up, so the static route stayed in place and the branch was cut off for four hours.

The new requirements:

  1. Use MPLS while head office is actually reachable through it; fail over to broadband automatically when it isn't.
  2. Send all guest traffic (the GUEST PC, 10.1.1.20) over broadband, but if broadband fails, guests should use normal routing rather than lose service.
DeviceInterfaceAddressConnects to
R1Gi0/010.0.12.1/24R2 (MPLS)
R1Gi0/110.0.13.1/24R3 (broadband)
R1Gi0/210.1.1.1/24branch LAN: PC1 10.1.1.10, GUEST 10.1.1.20
R2 / R3Gi0/110.0.24.2 / 10.0.34.3 /24R4
R4Lo0 / Lo110.255.0.4/32 / 10.4.4.1/24probe target / HQ servers

R2, R3 and R4 run OSPF between them (the providers' network) and have routes back to the branch LAN. R1 runs no routing protocol.

What you’ll practise

  • Configure IP SLA ICMP echo probes and tracking objects
  • Attach a tracked primary default route and a floating static backup route
  • Configure policy-based routing with an ACL, a route map and ip policy
  • Make PBR next hops depend on reachability with verify-availability
  • Verify path selection with traceroute, show track and show route-map

The tasks

  1. Probe head office through the MPLS circuit
  2. Track the probes
  3. Tracked default route with a floating backup
  4. Test the fail-over
  5. Send guests over broadband with PBR
  6. Look at what you built

The Lab Tasks pane has the scenario, these tasks, the checks to run, hints and the full solution.

Topology and devices

The network as it opens in EVE-NG, drawn from the lab’s own canvas, and the image each node runs.

Topology of Path control with PBR IP SLA and tracked static routes6 nodes and 1 network, 7 links. Every link is listed as text below the diagram.R1R2R3R4PC1GUESTBranch-LANGi0/2eth0eth0Gi0/0Gi0/0Gi0/1Gi0/0Gi0/1Gi0/0Gi0/1Gi0/1
6 nodes and 1 network, with the interface names each link uses. On a narrow screen, scroll the diagram sideways.
Every link, as text
  • R1 Gi0/0 to R2 Gi0/0
  • R1 Gi0/1 to R3 Gi0/0
  • R2 Gi0/1 to R4 Gi0/0
  • R3 Gi0/1 to R4 Gi0/1
  • R1 Gi0/2 to Branch-LAN (network)
  • PC1 eth0 to Branch-LAN (network)
  • GUEST eth0 to Branch-LAN (network)
Nodes in Path control with PBR, IP SLA and tracked static routes, with the image each runs and the vCPU and RAM it’s set to
NodeDeviceImage in Add NodeSet to
R1Cisco IOSvvios-adventerprisek9-m.spa.159-3.m91 vCPU, 512 MB
R2Cisco IOSvvios-adventerprisek9-m.spa.159-3.m91 vCPU, 512 MB
R3Cisco IOSvvios-adventerprisek9-m.spa.159-3.m91 vCPU, 512 MB
R4Cisco IOSvvios-adventerprisek9-m.spa.159-3.m91 vCPU, 512 MB
PC1VPCS hostBuilt in to EVE-NGCounted as 1 vCPU, 1,024 MB
GUESTVPCS hostBuilt in to EVE-NGCounted as 1 vCPU, 1,024 MB

How to open this lab

  1. Sign in to your workspace at lab.cloudlabbox.com.

  2. In File Manager, open Shared, then the folder CCNP ENARSI 300-410 guided labs.

  3. Open 13 - Path control with PBR IP SLA and tracked static routes and start its nodes, then open Lab Tasks for the scenario and the steps.

The lab is read-only. You can start the nodes and configure the devices, but changes to the topology can’t be saved. To change it, rebuild it in your own folder.

More CCNP ENARSI labs

All CCNP ENARSI labs

Related labs in other courses

CloudLabBox is independent of Cisco. The lab follows exam topics and isn’t vendor training material; vendor names identify the exams and the images in the workspace.