Information Technology Reference
In-Depth Information
Example 8-25 CEF Path for 192.168.100.6 on R1
R1#show ip cef 192.168.100.6
192.168.100.6/32, version 44, epoch 0, cached adjacency to Serial8/0
0 packets, 0 bytes
via 192.168.15.5, Serial8/0, 1 dependency
next hop 192.168.15.5, Serial8/0
valid cached adjacency
Example 8-26 shows the CEF path for 192.168.100.6 on R2 after R4 is moved out of the
forwarding paths.
Example 8-26 CEF Path for 192.168.100.6 on R2
R2#show ip cef 192.168.100.6
192.168.100.6/32, version 33, epoch 0, cached adjacency to Serial10/0
0 packets, 0 bytes
via 192.168.25.5, Serial10/0, 1 dependency
next hop 192.168.25.5, Serial10/0
valid cached adjacency
Step 2: Replace R4's BGP Process with the Confederation Configuration and Update
All Routers
Migrate R4 by replacing the current BGP process with the member AS 65001, and
configure a confederation using the current BGP AS number 100 as the confederation ID.
Use 100 and 65000 as the member AS peers.
Example 8-27 shows the new confederation configuration on R4 as entered line by line.
Example 8-27 BGP Confederation Configurations on R4
R4(config)#no router bgp 100
R4(config)#bgp router 65001
R4(config-router)#bgp confederation identifier 100
R4(config-router)#bgp confederation peers 100 65000
In a real migration, Steps 2 and 3 would be combined. Two steps are presented here for
easier discussion.
NOTE
Add confederation configurations to all other routers in AS 100—specifically, the bgp
confederation identifier 100 and bgp confederation peers commands. Consult the final
topology to determine the member AS numbers to use.
 
Search WWH ::




Custom Search