Information Technology Reference
In-Depth Information
Step 13: Update the Peerings with R1
On R4 and R5, update the peerings with R1. Example 8-72 shows the new BGP configura-
tions on R4. Similar changes are made to R5 (not shown). Additionally, you can remove the
intraconfederation peer 100 from the configurations in R4 and R5. Note that this does not
affect service.
Example 8-72
BGP Configurations on R4
router bgp 65001
no synchronization
bgp router-id 192.168.100.4
bgp log-neighbor-changes
bgp confederation identifier 100
bgp confederation peers 65000
neighbor Internal peer-group
neighbor Internal remote-as 65001
neighbor Internal update-source Loopback0
neighbor 192.168.14.1 remote-as 65000
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
Step 14: Verify All the Routing Information
Verify that all the sessions are up and that routes are properly received. This step completes
the migration. The following examples show some sample outputs.
Example 8-73 shows the BGP summary table on R1.
Example 8-73
BGP Summary Table on R1
R1#show ip bgp summary
BGP router identifier 192.168.100.1, local AS number 65000
BGP table version is 5, main routing table version 5
4 network entries and 8 paths using 708 bytes of memory
3 BGP path attribute entries using 180 bytes of memory
2 BGP AS-PATH entries using 48 bytes of memory
0 BGP route-map cache entries using 0 bytes of memory
0 BGP filter-list cache entries using 0 bytes of memory
BGP activity 4/8 prefixes, 8/0 paths, scan interval 60 secs
Neighbor V AS MsgRcvd MsgSent TblVer InQ OutQ Up/Down State/PfxRcd
192.168.14.4 4 65001 16 14 5 0 0 00:02:29 2
192.168.15.5 4 65001 16 14 5 0 0 00:01:50 2
192.168.18.8 4 200 9 10 5 0 0 00:04:32 1
192.168.100.2 4 65000 10 9 5 0 0 00:04:49 2
192.168.100.3 4 65000 10 10 5 0 0 00:05:01 1
