Data Center Interconnect Design and Implementation Using IPVPN
This section describes how to configure DCI using IPVPN. We are using IPVPN to pass traffic between data centers.
In this reference architecture, IPVPN routes are exchanged between spine devices in different data centers to allow for the passing of traffic between data centers.
Physical connectivity between the data centers is required before IPVPN routes can be sent across data centers. The backbone devices in a WAN cloud provide the physical connectivity. A backbone device is connected to each spine device in a single data center and participates in the overlay IBGP and underlay EBGP sessions. EBGP also runs in a separate BGP group to connect the backbone devices to each other; EVPN signaling and IPVPN (inet-vpn) is enabled in this BGP group.
Figure 1 shows two data centers using IPVPN for DCI.
Configuring Data Center Interconnect Using IPVPN
Configuring DCI for IPVPN is similar to configuring DCI for EVPN Type 5 routes with the exceptions shown in this section.
In this example, we are showing the configuration of IPVPN on Spine 1.
- Configure the underlay link from the spine to the backbone. set interfaces ae4 aggregated-ether-options minimum-links 1set interfaces ae4 aggregated-ether-options lacp activeset interfaces ae4 aggregated-ether-options lacp periodic fastset interfaces ae4 unit 0 family inet address 172.16.104.3/31set interfaces ae4 unit 0 family mpls
- On the backbone device, configure IBGP and MPLS for the
overlay network. IPVPN requires that you use MPLS. set protocols bgp group IPVPN-BGP local-address 192.168.0.1set protocols bgp group IPVPN-BGP neighbor 192.168.2.1 family inet unicastset protocols bgp group IPVPN-BGP neighbor 192.168.2.1 family inet-vpn unicastset protocols bgp group IPVPN-BGP neighbor 192.168.2.1 family inet6-vpn unicastset protocols rsvp interface ae4.0set protocols rsvp interface lo0.0set protocols mpls label-switched-path SPINE01-TO-REMOTE-SPINE4 to 192.168.0.4set protocols mpls label-switched-path SPINE01-TO-REMOTE-SPINE4 no-cspfset protocols mpls label-switched-path SPINE01-TO-REMOTE-SPINE5 to 192.168.0.5set protocols mpls label-switched-path SPINE01-TO-REMOTE-SPINE5 no-cspfset protocols mpls interface ae4.0set protocols mpls interface lo0.0
- On the spine, configure a routing instance to support
DCI using IPVPN routes. This routing instance accepts L3VPN routes
and also advertises data center routes as L3VPN routes to other IPVPN
provider edge routers.set routing-instances VRF-601 instance-type vrfset routing-instances VRF-601 interface irb.2401set routing-instances VRF-601 interface irb.2402set routing-instances VRF-601 interface irb.2403set routing-instances VRF-601 interface irb.2404set routing-instances VRF-601 interface lo0.601set routing-instances VRF-601 route-distinguisher 192.168.0.1:601set routing-instances VRF-601 vrf-target target:200:601set routing-instances VRF-601 vrf-table-labelset routing-instances VRF-601 routing-options rib VRF-601.inet6.0 multipathset routing-instances VRF-601 routing-options multipath
Verifying Data Center Interconnect Using IPVPN
- Verify that data center routes are advertised as IPVPN
routes to remote data centers.
host@SPINE-1> show interfaces terse irb.2401
Interface Admin Link Proto Local Remote irb.2401 up up inet 22.214.171.124/24 126.96.36.199/24 inet6 2001:db8::30:0:191:244/112 2001:db8::30:0:191:254/112 fe80::e86:1009:61cd:bff2/64
host@SPINE-1> show route advertising-protocol bgp 192.168.2.1 table VRF-601.inet.0 match-prefix 188.8.131.52 extensive
VRF-601.inet.0: 6091 destinations, 6115 routes (6091 active, 0 holddown, 0 hidden) * 184.108.40.206/24 (1 entry, 1 announced) BGP group underlay-bgp type External Route Distinguisher: 192.168.0.4:601 VPN Label: 18 Nexthop: Self Flags: Nexthop Change AS path:  I Communities: target:200:601
- On Spine 4, verify that the remote data center accepts
the routes as IPVPN routes.
host@SPINE-4> show route table VRF-601.inet.0 match-prefix 220.127.116.11
VRF-601.inet.0: 6447 destinations, 6752 routes (6447 active, 0 holddown, 0 hidden) + = Active Route, - = Last Active, * = Both 18.104.22.168/24 *[BGP/170] 1d 01:40:26, localpref 100 AS path: 4200000004 I, validation-state: unverified > to 22.214.171.124 via ae4.0, Push 18 [BGP/170] 23:48:18, localpref 100 AS path: 4200000005 I, validation-state: unverified > to 126.96.36.199 via ae5.0, Push 18
Data Center Interconnect—Release History
Table 1 provides a history of all of the features in this section and their support within this reference design.
Table 1: DCI Using IPVPN Release History
QFX10002-60C switches running Junos OS Release 19.1R2 and later releases in the same release train support DCI using IPVPN.
MX routers running Junos OS Release 18.4R2-S2 and later releases in the same release train also support DCI using IPVPN.
All devices in the reference design that support Junos OS Release 18.1R3-S5 and later releases in the same release train also support DCI using IPVPN.