Information Technology Reference
In-Depth Information
Step 4: Update the Peering on R1 and R2
On R1 and R2, change the current iBGP peering with R4 to eBGP peering. To make R8
reachable within confederation 100, put the link between R1 and R8 as part of the IGP. Also
remove the
next-hop-self
setting in both peer groups on R1. Consult Step 4 in Case Study 2
for the various options for setting BGP next hops.
Example 8-58 shows the modified BGP configurations on R1. Similar configuration
changes are made to R2 (not shown).
Example 8-58
BGP Configuration Changes on R1
router bgp 100
no synchronization
bgp router-id 192.168.100.1
bgp log-neighbor-changes
bgp confederation identifier 100
bgp confederation peers 65001
neighbor Internal peer-group
neighbor Internal remote-as 100
neighbor Internal update-source Loopback0
neighbor Clients peer-group
neighbor Clients remote-as 100
neighbor Clients update-source Loopback0
neighbor Clients route-reflector-client
neighbor 192.168.14.4 remote-as 65001
neighbor 192.168.18.8 remote-as 200
neighbor 192.168.100.2 peer-group Internal
neighbor 192.168.100.3 peer-group Clients
neighbor 192.168.100.5 peer-group Internal
no auto-summary
Figure 8-10 shows the updated network topology.
Step 5: Move R6 from Member AS 100 to Member AS 65001 and Put R4 Back in the
Forwarding Paths
Move R6 into member AS 65001, which is service-affecting for the prefix originated
locally on the router. Example 8-59 shows the new BGP configurations on R6. Note that R6
has peer sessions with all other routers in the right POP.
Example 8-59
Current BGP Configurations on R6
router bgp 65001
no synchronization
bgp router-id 192.168.100.6
bgp log-neighbor-changes
bgp confederation identifier 100
bgp confederation peers 100 65000
network 192.168.201.0
continues
