Configure BGP as shown in Figure 3-14 with the following peering:
R2 172.16.0.1 R3 172.16.0.2
R2 172.16.0.1 R1 10.80.80.1
R1 10.80.80.1 R8 10.8.8.8
R1 10.80.80.1 R6 10.6.6.6
R6 10.6.6.6 R4 10.4.4.4
R6 10.6.6.6 R5 10.5.5.5
R6 10.6.6.6 R7 10.7.7.7
Where possible, minimize the configuration required.
Figure 3-14. IP EGP Diagram
Inject the following networks into BGP, configure new loopback interfaces where required, do not use the network command, and ensure that all routes have a metric of 100 assigned to them:
R1 10.1.1.1/28
R2 2.2.2.2/28
R3 3.3.3.3/28
R4 10.4.4.4/28
R5 10.5.5.5/28
R6 10.6.6.6/28
R7 10.7.7.7/28
R8 10.8.8.8/28
Configure R6 to extend the range of network 2.2.2.0/28 into 2.2.2.0/24 when advertised into AS12. Ensure that the original attributes of this network are visible from AS12.
Users in AS11 are complaining that network 3.3.3.0 is unstable; configure R6 to control the instability of this route. Use the following values:
Reuse-value 30
Half-life 20
Suppress-value 1000
Maximum-suppress-time 130
On R2, set up a new loopback 22.22.22.22/24, advertise this within BGP using the network command. Similarly, set up 11.11.11.11/24 on R1. If the BGP route 22.22.22.0 is present on R1's BGP table, do not advertise network 11.11.11.0/24 to R8. If network 22.22.22.0/24 disappears, do advertise network 11.11.11.0/24 to R8.
On R5, set up a new loopback 5.5.5.5/28 and advertise this into AS11 using the network command, but do not allow this to be advertised into AS10 or AS12. Only configure R5 to achieve this.
R2 is due to have external directly connected BGP neighbors added to it on VLAN1. This VLAN has a tendency to flap because of a faulty switch; configure R2 so that if the VLAN should fail, the BGP sessions are not immediately reset.
Ensure that all BGP speakers within AS1 do not respond to hostile TCP resets or untrusted routing updates.
All BGP peers are to be able to communicate with all advertised BGP networks.
