Information Technology Reference
In-Depth Information
Example 8-108 BGP RIB on R3 (Continued)
Network Next Hop Metric LocPrf Weight Path
* i172.16.0.0 192.168.100.1 0 100 0 200 i
*>i 192.168.100.1 0 100 0 200 i
*> 192.168.200.0 0.0.0.0 0 32768 i
*>i192.168.201.0 192.168.100.6 0 100 0 i
* i 192.168.100.6 0 100 0 i
*>i192.168.202.0 192.168.100.7 0 100 0 i
* i 192.168.100.7 0 100 0 i
This step essentially completes the migration of routers from a confederation architecture
to an RR-based architecture. In the next step, you perform the final configuration cleanup.
Step 13: Remove the Confederation from the Configurations of All the Routers
in AS 100
Remove the confederation configurations from all routers in AS 100. Specifically, remove
the two lines from the BGP configurations for R4 that are shown in Example 8-109. This is
not service-affecting. After the configuration change in this step, routes that were classified
as from confed-internal peers are now from internal peers.
Example 8-109 Removing Confederation Configurations from R4
R4(config)#router bgp 100
R4(config-router)#no bgp confederation peers 65000 65001
R4(config-router)#no bgp confederation identifier 100
Also remove the unneeded peer group Peers on R4 and R5.
Step 14: Verify BGP Reachability for All Prefixes
Verify that all sessions are up and that all routes are received correctly. The following
examples show some sample outputs.
Example 8-110 shows the final BGP configurations on R1.
Example 8-110 BGP Configurations on R1
router bgp 100
no synchronization
bgp router-id 192.168.100.1
bgp log-neighbor-changes
neighbor Internal peer-group
continues
Search WWH ::




Custom Search