BGP IPv6 - Route Reflector
Route Reflector
The BGP (Border Gateway Protocol) IPv6 Route Reflector serves as a key architectural element in BGP networks, particularly in large-scale deployments where maintaining a full mesh of BGP peer connections can become impractical. In a BGP IPv6 Route Reflector setup, certain routers are designated as Route Reflectors, responsible for propagating BGP routing information among the routers within their cluster. Instead of requiring all routers to maintain direct peer connections with each other, Route Reflectors selectively reflect BGP updates to other routers, simplifying the overall BGP topology. This hierarchical structure improves scalability and reduces the complexity of BGP peer relationships. BGP IPv6 Route Reflectors play a crucial role in enhancing the efficiency of BGP networks by centralizing the route distribution process, contributing to a more streamlined and manageable BGP routing environment in large and complex networks.
Lab:
Disclaimer
This Configuration Guide is designed to assist members to enhance their skills in particular technology area. While every effort has been made to ensure that all material is as complete and accurate as possible, the enclosed material is presented on an “as is” basis. Neither the authors nor Forum assume any liability or responsibility to any person or entity with respect to loss or damages incurred from the information contained in this guide. This configuration guide was developed by Forum. Any similarities between material presented in this configuration guide and any other material is completely coincidental.
Cisco IOS Software, Linux Software (I86BI_LINUX-ADVENTERPRISEK9-M), Version 15.2(4)M1, DEVELOPMENT TEST SOFTWARE
Task 1: Configure IPv4 BGP process for Autonomous
Step 1: Configure Ipv6 BGP Route Reflector
R2:
router bgp 65000
neighbor 11:0:1::1 remote-as 65000
address-family ipv6
neighbor 11:0:1::1 route-reflector-client
exit
neighbor 33:0:1::3 remote-as 65000
exit
Step 2: Verify IPv6 BGP routes by following command:
R1# show bgp ipv6 unicast
BGP table version is 19, local router ID is 11.0.3.1
Status codes: s suppressed, d damped, h history, * valid, > best, i - internal,
r RIB-failure, S Stale, m multipath, b backup-path, f RT-Filter,
x best-external, a additional-path, c RIB-compressed,
Origin codes: i - IGP, e - EGP, ? - incomplete
RPKI validation codes: V valid, I invalid, N Not found
Network Next Hop Metric LocPrf Weight Path
*> 11:0:1::/64 :: 0 32768 i
*> 11:0:2::/64 :: 0 32768 i
*> 11:0:3::/64 :: 0 32768 i
*>i 22:0:1::/64 22:0:1::2 0 100 0 i
*>i 22:0:2::/64 22:0:1::2 0 100 0 i
*>i 22:0:3::/64 22:0:1::2 0 100 0 i
*>i 33:0:1::/64 33:0:1::3 0 100 0 i
*>i 33:0:2::/64 33:0:1::3 0 100 0 i
*>i 33:0:3::/64 33:0:1::3 0 100 0 i
*>i 44:0:1::/64 44:0:1::4 0 100 0 65200 i
*>i 44:0:2::/64 44:0:1::4 0 100 0 65200 i
*>i 44:0:3::/64 44:0:1::4 0 100 0 65200 i
Using Route Reflector, R1 router is configured as route reflector client and R3 router as route reflector non-cleint. Cient to Non-client BGP routes forwarding is allowed and therefore R1 now receives IPv6 BGP routes from R3 as well as R4 along with R2. Therefore now all IPv6 BGP routes are seen on R1 router.
R2# show bgp ipv6 unicast
BGP table version is 19, local router ID is 22.0.3.2
Status codes: s suppressed, d damped, h history, * valid, > best, i - internal,
r RIB-failure, S Stale, m multipath, b backup-path, f RT-Filter,
x best-external, a additional-path, c RIB-compressed,
Origin codes: i - IGP, e - EGP, ? - incomplete
RPKI validation codes: V valid, I invalid, N Not found
Network Next Hop Metric LocPrf Weight Path
*>i 11:0:1::/64 11:0:1::1 0 100 0 i
*>i 11:0:2::/64 11:0:1::1 0 100 0 i
*>i 11:0:3::/64 11:0:1::1 0 100 0 i
*> 22:0:1::/64 :: 0 32768 i
*> 22:0:2::/64 :: 0 32768 i
*> 22:0:3::/64 :: 0 32768 i
*>i 33:0:1::/64 33:0:1::3 0 100 0 i
*>i 33:0:2::/64 33:0:1::3 0 100 0 i
*>i 33:0:3::/64 33:0:1::3 0 100 0 i
*>i 44:0:1::/64 44:0:1::4 0 100 0 65200 i
*>i 44:0:2::/64 44:0:1::4 0 100 0 65200 i
*>i 44:0:3::/64 44:0:1::4 0 100 0 65200 i
R3# show bgp ipv6 unicast
BGP table version is 13, local router ID is 33.0.3.3
Status codes: s suppressed, d damped, h history, * valid, > best, i - internal,
r RIB-failure, S Stale, m multipath, b backup-path, f RT-Filter,
x best-external, a additional-path, c RIB-compressed,
Origin codes: i - IGP, e - EGP, ? - incomplete
RPKI validation codes: V valid, I invalid, N Not found
Network Next Hop Metric LocPrf Weight Path
*>i 11:0:1::/64 11:0:1::1 0 100 0 i
*>i 11:0:2::/64 11:0:1::1 0 100 0 i
*>i 11:0:3::/64 11:0:1::1 0 100 0 i
*>i 22:0:1::/64 22:0:1::2 0 100 0 i
*>i 22:0:2::/64 22:0:1::2 0 100 0 i
*>i 22:0:3::/64 22:0:1::2 0 100 0 i
*> 33:0:1::/64 :: 0 32768 i
*> 33:0:2::/64 :: 0 32768 i
*> 33:0:3::/64 :: 0 32768 i
*> 44:0:1::/64 44:0:1::4 0 0 65200 i
*> 44:0:2::/64 44:0:1::4 0 0 65200 i
*> 44:0:3::/64 44:0:1::4 0 0 65200 i
Using Route Reflector, R1 router is configured as route reflector client and R3 router as route reflector non-client. Non-client to client IPv6 BGP routes forwarding is allowed and therefore R3 now receives IPv6 BGP routes from R1 along with R2 and R4. Therefore now all IPv6 BGP routes are seen on R3 router.
R4# show bgp ipv6 unicast
BGP table version is 13, local router ID is 44.0.3.4
Status codes: s suppressed, d damped, h history, * valid, > best, i - internal,
r RIB-failure, S Stale, m multipath, b backup-path, f RT-Filter,
x best-external, a additional-path, c RIB-compressed,
Origin codes: i - IGP, e - EGP, ? - incomplete
RPKI validation codes: V valid, I invalid, N Not found
Network Next Hop Metric LocPrf Weight Path
*> 11:0:1::/64 33:0:1::3 0 65000 i
*> 11:0:2::/64 33:0:1::3 0 65000 i
*> 11:0:3::/64 33:0:1::3 0 65000 i
*> 22:0:1::/64 33:0:1::3 0 65000 i
*> 22:0:2::/64 33:0:1::3 0 65000 i
*> 22:0:3::/64 33:0:1::3 0 65000 i
*> 33:0:1::/64 33:0:1::3 0 0 65000 i
*> 33:0:2::/64 33:0:1::3 0 0 65000 i
*> 33:0:3::/64 33:0:1::3 0 0 65000 i
*> 44:0:1::/64 :: 0 32768 i
*> 44:0:2::/64 :: 0 32768 i
*> 44:0:3::/64 :: 0 32768 i