Information Technology Reference
In-Depth Information
Example 8-54
BGP Configurations on R7
router bgp 100
no synchronization
bgp router-id 192.168.100.7
bgp log-neighbor-changes
network 192.168.202.0
neighbor Internal peer-group
neighbor Internal remote-as 100
neighbor Internal update-source Loopback0
neighbor 192.168.100.4 peer-group Internal
neighbor 192.168.100.5 peer-group Internal
no auto-summary
The configurations on R8 remain the same. (See Example 8-55.)
Example 8-55
BGP Configurations on R8
router bgp 200
no synchronization
bgp log-neighbor-changes
network 172.16.0.0
neighbor 192.168.18.1 remote-as 100
no auto-summary
Migration Procedures
Because the high-level summary is similar to that in the previous case study, only detailed
procedures are provided in this section.
Step 1: Select R4 as the Starting Router and Move It out of the Forwarding Paths
Select R4 as the starting router. Because both clients R6 and R7 are served by two redun-
dant RRs, moving R4 out of the RR architecture does not affect BGP reachability. As in
Case Study 2, move R4 out of the forwarding path to avoid traffic loss.
Step 2: Migrate R4 from AS 100 to Member AS 65001 and Update All Other Routers
with Confederation Configurations
Migrate R4 by replacing the current BGP process with member AS 65001, and configure
the confederation using the current BGP AS number 100 as the confederation ID. Configure
100 and 65000 as member AS peers.
