Help us improve your experience.

Let us know what you think.

Do you have time for a two-minute survey?

 
ON THIS PAGE
 

Integrated DCI (VXLAN Stitching)

Overview

Integrated Data Center Interconnect (DCI) was introduced as a technology preview in Apstra version 4.2.0 and became GA as of Apstra version 4.2.1.

Note:

In Apstra version 4.2.0, this feature is classified as a Juniper Apstra Technology Preview feature. These features are "as is" and are for voluntary use. Juniper Support will attempt to resolve any issues that customers experience when using these features and create bug reports on behalf of support cases. However, Juniper may not provide comprehensive support services to Tech Preview features.

For additional information, refer to the Juniper Apstra Technology Previews page or contact JuniperSupport.
Note:

Apstra also supports two other types of DCI:

  • External Handoff where an external connection is set with a standard Layer 2 VLAN handoff external connection with traditional Flood MA VLAN learning. This extends a single Network/Broadcast domain with a traditional demarcation point.

  • OTT (over the top) Extending the Single EVPN-VXLAN domain between data centers.

For device information, see the Interconnect Gateway Leaf section of the Qualified Devices and NOS Versions page.

Integrated DCI, also known as VXLAN stitching, allows Apstra users to extend EVPN Type 2 and Type 5 routes between data centers using designated border leaf(s) to act as DCI gateways at each data center.

  • Apstra's Integrated DCI reference design follows RFE-9014 and draft-sharma-bess.

  • Each data center is treated as its own independent domain.

Configuring Integrated DCI within Apstra:

  • DCI configuration must be configured as part of each data center deployment/blueprint and use the same Interconnect Route Target (iRT).

  • The steps below guide you through the process for each blueprint and deployment.

1. Create Interconnect Domain

  1. From the blueprint, navigate to Staged > DCI > Integrated Interconnect and click Create Interconnect Domain.
  2. In the dialog that opens, enter the following information:

    • Interconnect Domain Name

    • Interconnect Route Target (iRT) - All interconnect gateways must use the same iRT. The iRT is an additional unique RT for the interconnect domain. The iRT must be globally unique; it must not be in use for every DCI-connected data center.

    • Interconnect ESI (optional) - Each site requires a unique site ID iESI at the MAC-VRF level, either auto-derived or set manually.

  3. Click Update to create the interconnect domain and return to the Integrated Interconnect page.

2. Create Remote Interconnect Gateway

  1. From the Integrated Interconnect page, click Local and Remote Gateways.
  2. Click Create Remote Interconnect Gateway
  3. Enter a name for the remote border leaf interconnect gateway and add the remote BGP IP/ASN. Select the local border leaf devices that will establish a session with this remote DCI gateway.
  4. Click Create to create the gateway and return to the Integrated Interconnect page.

3. Create Routing Policy

  1. From the Integrated Interconnect page, click Layer-3 Policy.
  2. Click Create Routing Policy.
  3. You can create a routing policy that can be used with VRF routes to exchange and extend the EVPN Type 5 routes via Integrated DCI. If you only plan to extend VNI and exchange EVPN Type 2 routes then you don't need to enable the VRFs for DCI EVPN Type 5 route exchange. The example below is for a route-map policy for the blue VRF.
  4. After entering routing policy details, click Create to create the routing policy and return to the Integrated Interconnect page.
  5. To assign the routing policy and enable the VRF for DCI Type 5 route exchange (as applicable), select the check box for the VRF, then click the Edit button that appears above the table.
  6. In the dialog that opens, toggle on Type 5 enablement (if applicable), select the routing policy from the drop-down list, and enter the iRT. Interconnect gateways must use the same Interconnect Route Target (iRT). The iRT is an additional unique route target for the interconnect domain.
  7. Click Update to save your changes and return to the Integrated Interconnect page.

4. Update Connectivity Type

This configuration section allows extending VNI EVPN Type 2 routes across data centers via Integrated DCI. Let's configure virtual networks to be exchanged via Integrated DCI.
  1. From the Integrated Interconnect page, click Connection Type (in right panel).
  2. Select the check boxes for the Layer 2 virtual networks and Layer 3 VRFs that need to extend to the remote DCI gateway. Remember, for every VRF that is to be enabled for Type 5 EVPN route exchange, it must be enabled on the Layer-3 Policy tab.
  3. Click the Edit button that appears above the table.
  4. In the dialog that opens, enable Layer 2 EVPN Type 2 route exchange. Translation VNI is the intermediate VNI to be used. It isn't required, but it needs to match the remote VNI either by translation on the other side or by both data centers using the same VNI for the virtual network that's being extended.
  5. Click Update to save your changes and return to the Integrated Interconnect page.
  6. After enabling all virtual networks and VRFs that will be extended to the remote DCI gateway, ensure that the Uncommitted tab is green and that you can commit the changes to enable the local Integrated DCI gateways that have been configured. (You'll repeat all these steps for the remote DCI gateway.)
Repeat the process for all Layer 2 virtual networks and Layer 3 VRFs that need to extend to the remote DCI gateway. Remember, every VRF that is to be enabled for Type 5 EVPN route exchange must be enabled on the Layer-3 Policy tab.

5. Configure ESI MAC MSB

All data centers must be configured to use a different ESI MAC MSB (most significant byte). Refer to Update ESI MAC MSB for details.

6. Configure Remote DCI Gateway

After configuring ESI MAC MSB, repeat the above steps to configure the remote DCI gateway.