Information Technology Reference
In-Depth Information
Example 8-46 shows the BGP RIB on R5. Note that R5 receives three paths for 172.16.0.0
and 192.168.200.0: one from R4 via iBGP, one from R1 via intraconfederation eBGP, and
one from R2 via intraconfederation eBGP.
Example 8-46
BGP RIB on R5
R5#show ip bgp
BGP table version is 16, local router ID is 192.168.100.5
Status codes: s suppressed, d damped, h history, * valid, > best, i - internal,
r RIB-failure
Origin codes: i - IGP, e - EGP, ? - incomplete
Network Next Hop Metric LocPrf Weight Path
* i172.16.0.0 192.168.14.1 0 100 0 (65000) 200 i
*> 192.168.15.1 0 100 0 (65000) 200 i
* 192.168.100.1 0 100 0 (65000) 200 i
*> 192.168.200.0 192.168.15.1 0 100 0 (65000) i
* i 192.168.14.1 0 100 0 (65000) i
* 192.168.100.3 0 100 0 (65000) i
*>i192.168.201.0 192.168.100.6 0 100 0 i
*>i192.168.202.0 192.168.100.7 0 100 0 i
Example 8-47 shows the BGP RIB on R8. Note that all three prefixes from AS 100 are
received correctly.
Example 8-47
BGP RIB on R8
R8#show ip bgp
BGP table version is 27, local router ID is 192.168.18.8
Status codes: s suppressed, d damped, h history, * valid, > best, i - internal,
r RIB-failure
Origin codes: i - IGP, e - EGP, ? - incomplete
Network Next Hop Metric LocPrf Weight Path
*> 172.16.0.0 0.0.0.0 0 32768 i
*> 192.168.200.0 192.168.18.1 0 100 i
*> 192.168.201.0 192.168.18.1 0 100 i
*> 192.168.202.0 192.168.18.1 0 100 i
Case Study 3: Route Reflection to Confederation
Migration
This case study presents detailed procedures on how to migrate an RR-based network to a
confederation-based architecture. The starting topology is shown in Figure 8-2. The final
topology is shown in Figure 8-3. In the final topology, the same IGP is used across the
confederation member autonomous systems.
