VPNv4 support
Route Reflector (RR) in BGP improves the scalability of iBGP sessions between iBGP peers and reduces the connectivity overload between BGP peers. The vRouter provides support for RR for VPNv4 address families in addition to IPv4 and IPv6 address families.
Note the following regarding RR support for VPNv4:
- RR cannot be used in the forwarding path for VPNv4.
- For best performance, Ciena recommends not configuring VRF on the VPNv4 RR.
The following diagram illustrates an RR configuration for reflecting the VPNv4 address family. The vRouter can be used as RR1 or RR2. PE1 and PE2 are third party devices that have full Layer 3 VPN support. The RR is not part of the forwarding path.
All BGP peerings within RR1 and RR2 are in the same AS (100 in the example). The AS is illustrated by the large blue circle in the diagram (RR applies to iBGP peerings only to avoid the full mesh between iBGP peers).
The following commands show how to configure the example in the diagram. MPLS configuration is not necessary on RR1 or RR2, because traffic is sent between PE1 and PE2 over an MPLS enabled network.
vyatta@vyatta:~$ set interfaces dataplane dp0s4 address 192.168.1.4/24
vyatta@vyatta:~$ set interfaces dataplane dp0s5 address 192.168.12.4/24
vyatta@vyatta:~$ set interfaces loopback lo address 10.1.1.1/32
vyatta@vyatta:~$ set protocols bgp 100 neighbor 192.168.1.1 address-family vpnv4-unicast route-reflector-client
vyatta@vyatta:~$ set protocols bgp 100 neighbor 192.168.1.1 remote-as 100
vyatta@vyatta:~$ set protocols bgp 100 neighbor 192.168.12.2 address-family vpnv4-unicast route-reflector-client
vyatta@vyatta:~$ set protocols bgp 100 neighbor 192.168.12.2 remote-as 100
vyatta@vyatta:~$ set protocols bgp 100 parameters router-id 10.1.1.1
vyatta@vyatta:~$ set protocols ospf area 0 network 10.1.1.1/32
vyatta@vyatta:~$ set protocols ospf area 0 network 192.168.1.0/24
vyatta@vyatta:~$ set protocols ospf area 0 network 192.168.12.0/24The following command displays summary information for the configuration.
vyatta@vyatta:~$ show ip bgp vpnv4 unicast summary
BGP router identifier 10.1.1.1, local AS number 100
BGP table version is 1
1 BGP GLOBAL AS-PATH entries
0 BGP community entries
Neighbor V AS MsgRcvd MsgSent TblVer InQ OutQ Up/Down Statd
192.1268.1.1 4 100 11 8 1 0 0 00:02:45 3
192.1268.12.2 4 100 27 51 1 0 0 00:10:18 1
Total number of neighbors 2
Total number of Established sessions 2The following example displays detailed information for the configuration.
vyatta@vyatta:~$ show ip bgp vpnv4 unicast
BGP table version is 1, local router ID is 10.1.1.1
Status codes: s suppressed, d damped, h history, * valid, > best, i - internal, l - labeled
S Stale
Origin codes: i - IGP, e - EGP, ? - incomplete
Network Next Hop Metric LocPrf Weight Path
Route Distinguisher: 1:1
*>i10.4.4.0/24 192.168.1.1 0 100 0 ?
*>i10.7.9.0/24 192.168.12.2 0 100 0 ?
BGP table version is 1, local router ID is 10.1.1.1
Status codes: s suppressed, d damped, h history, * valid, > best, i - internal, l - labeled
S Stale
Origin codes: i - IGP, e - EGP, ? - incomplete
Route Distinguisher: 2:2
*>i10.8.2.0/24 192.168.1.1 0 100 0 ?
BGP table version is 1, local router ID is 10.1.1.1
Status codes: s suppressed, d damped, h history, * valid, > best, i - internal, l - labeled
S Stale
Origin codes: i - IGP, e - EGP, ? - incomplete
Route Distinguisher: 3:3
*>i10.8.3.0/24 192.168.1.1 0 100 0 ?