Information Technology Reference
In-Depth Information
To prepare the migration of R5 (in the next step) and to avoid traffic loss, you should
move R5 out of the forwarding paths by increasing IGP metrics to R5. Because R4 has
reachability to all prefixes, traffic forwarding is unaffected. The current network topology
is shown in Figure 8-12.
Figure 8-12 Current Network Topology
AS 200
R8
172.16.0.0/16
AS 65001
RR
R1
R4
AS 100
192.168.201.0/24
192.168.200.0/24
R6
R3
192.168.202.0/24
Client
R2
RR
RR
R5
R7
Confederation 100
Step 7: Move R5 from Member AS 100 to Member AS 65001 and Put R5 Back in the
Forwarding Paths
Move R5 from member AS 100 to AS 65001. The warning messages on R4, R6, and R7
about the wrong AS are now gone. When the correct routing information is learned, you can
put R5 back in the forwarding paths. Example 8-64 shows the new BGP configurations
on R5.
Example 8-64 BGP Configurations on R5
router bgp 65001
no synchronization
bgp router-id 192.168.100.5
bgp log-neighbor-changes
bgp confederation identifier 100
bgp confederation peers 100 65000
neighbor Internal peer-group
continues
 
Search WWH ::




Custom Search