Having made it through the protocol overview and enterprise application section, it is now time to apply your knowledge of BGP and Junos software to the first of three practical BGP deployment scenarios.
The first scenario begins when the CIO at Beer-Co seizes upon the organization’s newfound appreciation for all things BGP by applying for a public ASN and detailing a BGP deployment plan that ultimately involves dual-homing to multiple providers. BGP deployment will occur in a phased approach, and you have been selected to head up phase 1: establishment of the initial BGP peering and related policy to Botnet in AS 34.
The deployment goals for initial BGP peering with Botnet are as follows:
Establish EBGP interface-based peering to Botnet/AS 34.
Use import policy to reject all but the default route that originates within Botnet/AS 34.
Use export policy to advertise a single aggregate route that represents Beer-Co’s internal prefixes.
Use a static route to direct traffic to the backup link only in the event of BGP session disruption, and to ensure that traffic switches back to the primary upon service restoration.
Redistribute a default route to provide external reachability for internal Beer-Co routers.
Figure 7-8 details the current Beer-Co internal topology and the newly activated access links to Botnet.
Figure 7-8. Beer-Co to Botnet peering