CCNP ENCOR lab 30 of 36
Embedded Event Manager applets
Teach Bristol's router to look after itself with EEM: bring a backup link up and down from a tracked probe, collect evidence the moment the WAN fails, take health snapshots on demand and on a timer, and block accidental reloads.
Run this lab
It needs Lite: its 3 nodes are set to 3 vCPU and 1,536 MB in total. That fits the free demo too.
In your workspace: Shared, then CCNP ENCOR 350-401 guided labs, then 30 - Embedded Event Manager applets
- Level
- Intermediate
- Time
- About 60 minutes
- Nodes need
- 3 vCPU, 1,536 MB
- Smallest plan
- Lite
The scenario
Fernhill Freight's Bristol router (R1) has a primary WAN link to HQ and a 4G backup that costs money for every megabyte, so the backup interface (Gi0/1) is kept shut until it's needed. Today an engineer has to log in and bring it up by hand during an outage, and nobody captures any evidence of what happened.
You'll use the Embedded Event Manager (EEM) on R1 to:
- bring the 4G link up automatically when HQ stops answering over the primary link, and shut it again when the primary recovers;
- save evidence to flash the moment the WAN fails;
- take a health snapshot on demand, and log the probe results every minute;
- stop anyone reloading the router by accident.
| Device | Interface | Address | Connects to |
|---|---|---|---|
| R1 | Gi0/0 | 10.0.12.1/30 | R2 Gi0/0 (primary) |
| R1 | Gi0/1 | 10.0.13.1/30 (shut) | R3 Gi0/0 (4G provider) |
| R1 | Lo10 | 10.20.10.1/24 | Bristol LAN |
| R2 (HQ) | Lo0 / Lo10 | 10.255.0.2/32 / 10.10.30.1/24 | – |
| R2 | Gi0/1 | 10.0.23.2/30 | R3 Gi0/1 |
| R3 (4G) | Gi0/0 / Gi0/1 | 10.0.13.2/30 / 10.0.23.1/30 | R1 / R2 |
R1 has a default route through R2 and a floating one (AD 10) through R3. R2 and R3 are already configured.
Topology: a triangle. R1 — R2 primary, R1 — R3 — R2 backup.
What you’ll practise
- Explain EEM event detectors, actions and the applet structure
- Automate configuration with applets triggered by object tracking
- Automate data collection with syslog-triggered, timer and manual applets that write to flash
- Intercept a CLI command with a synchronous applet
- Verify registered policies and the EEM history, and test applets safely
The tasks
- Understand applets
- Give EEM something to watch
- Automate the backup link
- Collect evidence when the WAN fails
- Snapshots on demand and on a timer
- Block accidental reloads
- Test the failover end to end
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.
Every link, as text
- R1
Gi0/0to R2Gi0/0 - R1
Gi0/1to R3Gi0/0 - R3
Gi0/1to R2Gi0/1
| Node | Device | Image in Add Node | Set to |
|---|---|---|---|
| R1 | Cisco IOSv | vios-adventerprisek9-m.spa.159-3.m9 | 1 vCPU, 512 MB |
| R2 | Cisco IOSv | vios-adventerprisek9-m.spa.159-3.m9 | 1 vCPU, 512 MB |
| R3 | Cisco IOSv | vios-adventerprisek9-m.spa.159-3.m9 | 1 vCPU, 512 MB |
How to open this lab
Sign in to your workspace at
lab.cloudlabbox.com.In File Manager, open Shared, then the folder
CCNP ENCOR 350-401 guided labs.Open
30 - Embedded Event Manager appletsand 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
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.