Skip to content
Back to Learning
CCNP · ENCORAdvanced

IP SLA and EEM: The Failover That Never Fires

The branch sits on its backup path although the primary is healthy. Fix the IP SLA tracking and add an EEM alert on four real routers, right below.

Live lab: real routersIP SLAObject trackingEEM

Symptom

A branch router sits on its backup path although the primary is healthy, and nobody is alerted when paths change. Fix the tracking and add an EEM alert on four real routers.

Your mission

Prove the cause, then fix it

Format

Four real routers

Need a hint?

Reveal the root cause when you're ready.

Try the investigation first, then use this as your escape hatch, not a dead end.

Locked

Create a free account to open IP SLA and EEM: The Failover That Never Fires. You get the root cause and the full step-by-step fix.

Prefer no password? Use an email link instead

No spam. The fix lands in your inbox too. Your account includes 5 guided labs free. After that, the Learning Pass unlocks every remaining lab.

Lab debrief

Turn the session into a repeatable troubleshooting pattern.

Use this reference after your attempt: first explain the symptom, then verify the evidence, then confirm the repair.

The problem

Branch router R1 reaches HQ's loopback, 4.4.4.4, through two providers: R2 is primary and R3 is backup. A tracked static route should keep traffic on R2 while R2's path works and move it to R3 when it fails. Today R1 sends everything through R3 although R2 is healthy, and operations has asked for a log message whenever the branch fails over.

What you'll practice

  • Read IP SLA configuration and statistics to tell whether a probe is actually running
  • Explain why a tracked static route is withdrawn while its track object is Down
  • Choose a probe target that detects a failure beyond the first hop
  • Write an EEM applet that reacts to a track object changing state
  • Prove failover and recovery by failing the primary provider's uplink

1. Floating static routes

A static route with a higher administrative distance is installed only while the preferred route is missing, which makes it a simple backup path.

2. What a probe proves

An ICMP echo probe proves that its target answered. A target on the near side of the next hop proves only that one link, not the path beyond it.

3. Object tracking

A track object follows an IP SLA operation's result. A static route tied to it is installed while the object is Up and withdrawn while it is Down.

4. EEM applets

An Embedded Event Manager applet pairs an event, such as a track object changing state, with actions such as writing a syslog message.

The topology

Four real routers. R1 is the branch, with loopback 1.1.1.1. R2 is the primary provider and R3 the backup, each with a link to R1 and a link to R4. R4 is HQ, with loopback 4.4.4.4. Routing is static only, and HQ already tracks its return path correctly.

Commands to run yourself

The real diagnostic commands for this lab, copy-paste ready. Run these in the same order to reproduce the investigation on your own session.

Which route R1 uses for HQ
show ip route 4.4.4.4
The track object's state
show track 1
The probe's settings and schedule
show ip sla configuration 1
Applets and the events they wait for
show event manager policy registered
IP SLA tracked static routesR1 prefers HQ through R2 and falls back to R3.10.0.12.0/30Et0/0 to Et0/010.0.13.0/30Et0/1 to Et0/010.0.24.0/30Et0/1 to Et0/010.0.34.0/30Et0/1 to Et0/1R1 · branchLo0 1.1.1.1Et0/0 10.0.12.1Et0/1 10.0.13.1R2 · primaryLo0 2.2.2.2Et0/0 10.0.12.2Et0/1 10.0.24.1R3 · backupLo0 3.3.3.3Et0/0 10.0.13.2Et0/1 10.0.34.1R4 · HQLo0 4.4.4.4Et0/0 10.0.24.2Et0/1 10.0.34.2R1 uses the backupR2's path is healthyFailover must follow R2's uplinkR2 Et0/1 to R4

Rate this lab

No ratings yet

Your rating

Frequently asked

Are these real routers or a simulation?

Real routers. Pressing Start boots four routers just for you, with full command sets: any valid command works, not only the ones the guide suggests. The first start can take a minute or two while the lab server wakes up.

Who can run this lab?

It is included with the Exam Pass and the Year Pass. Each session lasts up to three hours, and you can run one live lab at a time.

Does my exact fix have to match the answer?

No. The lab checks the routers' state: the route R1 uses for HQ before and after the uplink fails, the applets registered on R1 and its log, and R2's uplink. Any fix that produces that state passes, and the tempting partial fixes do not.

Which ENCOR topics does it cover?

IP SLA from the network assurance section (4.0) and EEM applets from the automation section (6.0) of the 350-401 blueprint.

Ready to run this lab yourself?

No setup, no image sourcing. Book a session or ask for a live demo.