Lab R7: BGP, broken
The company of the last lab, as you left it: R3 reflecting for the other three, everything leaving through provider B, the path lengthened toward provider A, nothing passed between the providers. It ran for a day. This morning provider B's helpdesk says it has no route to your network at all, and your own monitoring says provider A has gone quiet. The design is lab R6's and is not to be changed. Find what was typed last night, on which routers, and take out only that.
What you will do
- Down, and which kind of down
- Switched off is not broken
- Trying, and never answered
- Everything up, and leaving by the wrong door
- A leftover that has not hurt anyone yet
- As designed
New in this lab: states, timers.
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:
- How two routers become BGP peers
- iBGP and eBGP: loopbacks, multihop, next hop and the full mesh
- Troubleshooting BGP neighbors, and peer groups
- Getting routes in and out: network, aggregate, refresh
- Route reflectors
- Best-path selection
- BGP policies: filtering and path manipulation
- MP-BGP for IPv6
- Troubleshooting BGP 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.
