Lab R2: EIGRP, broken
This is the network you built in the last lab, exactly as you left it, and it ran for a day. Then there was a maintenance window. This morning the office cannot reach the branch. The design has not changed and you are not to change it: the autonomous system, the two dialects, the authentication on both links, the stub, the summary and the variance are all as documented in lab R1. Something that was typed last night does not match the design. There are four of them. R1's own configuration is known to be good.
What you will do
- How bad is it
- R1 and R2: the same secret, typed twice
- R1 and R3: two routers that measure differently
- R4 and R5: advertised, and silent
- Every neighbor up, and half the design missing
- Leave it as designed
New in this lab: neighbors, feasible successor.
How it is checked
Each of the 6 tasks is checked on the devices themselves as you finish it: the bench reads how the network is configured and what it does, not what you typed. The lab is done when all 6 pass.
The lessons it follows
It opens after these, and uses what they teach:
- EIGRP's two styles, both families, global and VRF
- EIGRP neighbors and authentication
- DUAL: the backup that's already waiting, and stuck in active
- EIGRP metrics and load balancing
- Stubs, summarization, filtering and split horizon
- Troubleshooting EIGRP from symptom to cause (timed)
- Routing inside VRFs: EIGRP, OSPF and BGP VRF-Lite
Open the lab benchIt needs a computer: phones and tablets are not supported.
