Information Technology Reference
In-Depth Information
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. You can remove the unneeded sessions with routers
on the other POP. Example 8-39 shows the new BGP configurations on R3.
Example 8-39
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 65001
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-40 shows the current BGP summary table on R2. The down session with R1 (in
Active state) is expected, because R1 is not updated with the correct peering with R2. This
is not needed, because you migrate R1 next.
Example 8-40
BGP Summary Table on R2
R2#show ip bgp summary
BGP router identifier 192.168.100.2, local AS number 65000
BGP table version is 9, main routing table version 9
4 network entries and 7 paths using 668 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 5/35 prefixes, 9/2 paths, scan interval 60 secs
Neighbor V AS MsgRcvd MsgSent TblVer InQ OutQ Up/Down State/PfxRcd
192.168.24.4 4 65001 32 27 9 0 0 00:12:50 3
192.168.25.5 4 65001 33 34 9 0 0 00:12:08 3
192.168.100.1 4 65000 37 37 0 0 0 never Active
192.168.100.3 4 65000 39 43 9 0 0 00:02:27 1
