Lab C7: BGP peering and paths

A company whose autonomous system number, 4200000100, does not fit in the two bytes older equipment expects. Its core router knows every inside router and should never have to be told about a new one. Its two edge routers each face a different provider, and one of them also carries a customer who uses a private number of its own. OSPF already carries the loopbacks; there is no BGP anywhere on your three routers. You build the sessions the way a network with forty routers would want them built, bring up both providers, read why the core likes one exit better, and then make it use both.

In Daveth Pro (Network)Build it from the brief · Seven routers · 5 tasks

What you will do

  1. Inside sessions that scale
  2. Two providers and a customer
  3. Why this exit and not that one
  4. Both exits
  5. Save it

New in this lab: templates, dynamic neighbors, 4-byte AS, attributes, load balancing.

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:

Open the lab benchIt needs a computer: phones and tablets are not supported.