Lab C5: EIGRP
Head office has never run EIGRP, and everything around it does. R2 speaks it the modern way, in named mode, with authentication it will not do without. R3 speaks it the old way and sits on a slower circuit. Behind them is a branch homed to both, and one more router behind the branch. You bring head office in, in named mode, for both address families, and then decide what it gets to see: a summary instead of the branch's detail, with one exception; a branch that announces only what it should, with one exception; and two unequal paths, both carrying traffic.
What you will do
- Head office joins
- One route for the branch, and one exception
- A branch that is only a branch
- Both circuits earning their keep
- Save it
New in this lab: named mode, wide metrics, feasible successor, stub, leak-map.
How it is checked
Each of the 5 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 5 pass.
The lessons it follows
It opens after these, and uses what they teach:
- EIGRP adjacencies
- Reported distance, computed distance, feasible distance, feasibility condition, successor, feasible successor
- Classic metrics and wide metrics
- EIGRP general operations
- EIGRP topology table
- EIGRP packet types
- Stuck-in-active
- EIGRP graceful shutdown
- EIGRP named mode
- Query propagation boundaries
- Leak-map with summary routes
- EIGRP stub with leak map
Open the lab benchIt needs a computer: phones and tablets are not supported.
