CCNP ENARSI lab 15 of 35
Bidirectional Forwarding Detection for OSPF, EIGRP, BGP and static routes
Measure how long OSPF, EIGRP and BGP take to notice a silent link failure, then add BFD so that every protocol, and a static route, reacts in about a second and a half.
Run this lab
It needs Lite: its 4 nodes are set to 4 vCPU and 2,048 MB in total. That fits the free demo too.
In your workspace: Shared, then CCNP ENARSI 300-410 guided labs, then 15 - Bidirectional Forwarding Detection for OSPF EIGRP BGP and static routes
- Level
- Intermediate
- Time
- About 55 minutes
- Nodes need
- 4 vCPU, 2,048 MB
- Smallest plan
- Lite
The scenario
Halcyon Media's core router R1 talks OSPF to R2, EIGRP to R3 and eBGP to a partner (R4), plus a static route to the partner's extranet. The links run through a carrier's Ethernet service, so when the carrier has a problem, R1's interfaces stay up and only the routing protocol notices, after its hold or dead timer expires. During last month's carrier fault, video streams froze for 40 seconds on the OSPF path and three minutes on the BGP path.
You'll measure those delays, then add BFD so that every protocol learns about a failure in about 1.5 seconds.
| Device | Interface | Address | Protocol to R1 |
|---|---|---|---|
| R1 | Gi0/0 / Gi0/1 / Gi0/2 | 10.0.12.1 / 10.0.13.1 / 10.0.14.1 /24 | – |
| R1 | Lo1 | 10.1.1.1/24 | advertised in all three |
| R2 | Gi0/0, Lo1 | 10.0.12.2/24, 10.2.2.1/24 | OSPF area 0 |
| R3 | Gi0/0, Lo1 | 10.0.13.3/24, 10.3.3.1/24 | EIGRP AS 100 |
| R4 | Gi0/0, Lo1, Lo2 | 10.0.14.4/24, 10.4.4.1/24, 10.44.44.1/24 | eBGP 65004 (Lo1); static on R1 (Lo2) |
What you’ll practise
- Explain why routing protocols detect some failures slowly and how BFD helps
- Configure BFD timers on interfaces and register OSPF, EIGRP, BGP and static routes as clients
- Read show bfd neighbors and its details, including registered protocols
- Measure failure detection with and without BFD
The tasks
- Measure detection without BFD
- Configure BFD on the links
- Register OSPF and EIGRP
- Register BGP and the static route
- Measure again
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 - R1
Gi0/2to R4Gi0/0
| 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 |
| R4 | 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 ENARSI 300-410 guided labs.Open
15 - Bidirectional Forwarding Detection for OSPF EIGRP BGP and static routesand 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
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.