CloudLabBox
Try the free demo

CCNP ENCOR lab 27 of 36

IP SLA, object tracking and policy-based routing

Make the Bristol branch fail over when the MPLS service breaks beyond the first hop, measure voice quality to HQ with UDP jitter, and send guest traffic out of the broadband link with policy-based routing.

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 ENCOR 350-401 guided labs, then 27 - IP SLA object tracking and policy-based routing

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

Fernhill Freight's Bristol branch router (BR) has two WAN links: an MPLS service to Leeds HQ (primary) and a broadband line (backup, and the guests' route to the internet). Last month the MPLS provider had a fault deep inside its network: BR's link stayed up, so the static default route stayed in the table, and Bristol was cut off for three hours.

Your tasks:

  1. Fail over to broadband whenever HQ stops answering through MPLS, not just when the local link drops.
  2. Measure the voice quality to HQ for the telephony team.
  3. Send all guest Wi-Fi traffic out of the broadband link, whatever the routing table says.
DeviceInterfaceAddressConnects to
BRGi0/010.0.1.2/30MPLS 10.0.1.1
BRGi0/110.0.2.2/30BB 10.0.2.1
BRGi0/2 / Gi0/310.20.10.1/24 / 10.20.50.1/24staff PC1 / guest PC2
HQGi0/0 / Gi0/110.0.13.2/30 / 10.0.23.2/30MPLS / BB
HQLo0 / Lo1010.255.0.4/32 / 10.10.30.1/24–
BBLo0198.51.100.1/24"the internet"
PC1 / PC2eth010.20.10.10/24 / 10.20.50.10/24gateways .1

BR has a single static default route via MPLS. You manage BR and HQ; MPLS and BB are the providers' routers.

Topology: BR connects to MPLS and BB; both connect to HQ; PC1 and PC2 hang off BR.

What you’ll practise

  • Configure IP SLA ICMP echo and UDP jitter operations and read their statistics
  • Track an IP SLA operation and tie a static route to it, with a floating static backup
  • Avoid the classic trap of a probe that follows the route it's protecting
  • Explain policy-based routing and steer one subnet with a route map, verified next hop and tracking
  • Verify PBR with route-map counters, debugs and traceroute

The tasks

  1. See the problem
  2. Probe HQ through MPLS
  3. Track the probe and fail over
  4. Measure voice quality
  5. Send the guests out of broadband with PBR
  6. Verify the policy

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 IP SLA object tracking and policy-based routing6 nodes, 6 links. Every link is listed as text below the diagram.BRMPLSBBHQPC1PC2Gi0/2eth0Gi0/3eth0Gi0/0Gi0/0Gi0/1Gi0/0Gi0/1Gi0/0Gi0/1Gi0/1
6 nodes, with the interface names each link uses. On a narrow screen, scroll the diagram sideways.
Every link, as text
  • BR Gi0/0 to MPLS Gi0/0
  • BR Gi0/1 to BB Gi0/0
  • MPLS Gi0/1 to HQ Gi0/0
  • BB Gi0/1 to HQ Gi0/1
  • BR Gi0/2 to PC1 eth0
  • BR Gi0/3 to PC2 eth0
Nodes in IP SLA, object tracking and policy-based routing, with the image each runs and the vCPU and RAM it’s set to
NodeDeviceImage in Add NodeSet to
BRCisco IOSvvios-adventerprisek9-m.spa.159-3.m91 vCPU, 512 MB
MPLSCisco IOSvvios-adventerprisek9-m.spa.159-3.m91 vCPU, 512 MB
BBCisco IOSvvios-adventerprisek9-m.spa.159-3.m91 vCPU, 512 MB
HQCisco IOSvvios-adventerprisek9-m.spa.159-3.m91 vCPU, 512 MB
PC1VPCS hostBuilt in to EVE-NGCounted as 1 vCPU, 1,024 MB
PC2VPCS 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 ENCOR 350-401 guided labs.

  3. Open 27 - IP SLA object tracking and policy-based routing 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 ENCOR labs

All CCNP ENCOR 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.