Information Technology Reference
In-Depth Information
Example 8-67
BGP Configurations on R4 (Continued)
bgp log-neighbor-changes
bgp confederation identifier 100
bgp confederation peers 100 65000
neighbor Internal peer-group
neighbor Internal remote-as 65001
neighbor Internal update-source Loopback0
neighbor 192.168.14.1 remote-as 100
neighbor 192.168.24.2 remote-as 65000
neighbor 192.168.100.5 peer-group Internal
neighbor 192.168.100.6 peer-group Internal
neighbor 192.168.100.7 peer-group Internal
no auto-summary
After the routing information is received on R2, put R2 back in the forwarding paths by
removing the IGP metric changes made in Step 9.
Step 11: Move R3 from Member AS 100 to Member AS 65000
Move R3 from member AS 100 to member AS 65000, which is service-affecting for the
prefix originated locally on the router. In this case, the prefix 192.168.200.0/24 is tempo-
rarily unavailable during the configuration change on R3. Example 8-68 shows the new
BGP configurations on R3.
Example 8-68
BGP Configurations on R3
router bgp 65000
no synchronization
bgp router-id 192.168.100.3
bgp log-neighbor-changes
bgp confederation identifier 100
bgp confederation peers 65000
network 192.168.200.0
neighbor Internal peer-group
neighbor Internal remote-as 65000
neighbor Internal update-source Loopback0
neighbor 192.168.100.1 peer-group Internal
neighbor 192.168.100.2 peer-group Internal
no auto-summary
Example 8-69 shows the current BGP summary table on R2. As expected, the session with
R1 is down. This is fine, because R2 receives all routes correctly, and you will migrate R1
next.
