interconnect
Syntax
interconnect {
encapsulation {
mpls;
vxlan;
}
esi identifier {
all-active;
df-election-type {
mod;
preference {
value value (0..65535);
}
}
}
interconnected-vlan-list ([vlan-list] | all);
interconnected-vni-list ([vni-list] | all);
route-distinguisher [number:id | ip-address:id];
vrf-export (policy-name | [policy-names]);
vrf-import (policy-name | [policy-names]);
vrf-target {
community;
import community-name;
export community-name;
}
}
Description
Use this statement to enable seamless interconnection of:
EVPN-VXLAN points of delivery (PODs) in a data center.
Different EVPN-VXLAN data centers. This use case is also known as data center interconnect (DCI).
In these use cases, a Juniper Networks device that supports the seamless EVPN-VXLAN stitching feature can serve as either a spine or super spine device that interconnects the PODs or data centers through an EVPN-VXLAN WAN network.
When configuring the interconnection, you can set up a single routing instance of type virtual-switch or evpn on each spine or super spine device. Or, you can use the default switching instance. In the instance, you specify these elements:
-
Two sets of route distinguishers (RDs) and route targets. The first set is the local RD and route target for the POD or data center network. The second set, which you specify in the
interconnectconfiguration stanza, is for the WAN network.Note:The interconnect RD must be different from the local RD in the routing instance.
When you configure DCI with seamless stitching for EVPN Type 2 routes, the device throws a commit error if you try to configure the same value for the interconnect RD and the local RD.
In the same case for DCI seamless stitching with EVPN Type 5 routes, you won't see a commit error with Junos OS and Junos OS Evolved Releases before 22.4R2 and 23.1R1. However, the interconnect and local RD values in the same routing instance must still be different. Starting in those releases, the device does throw the commit error to enforce this condition.
-
An Ethernet segment identifier (ESI) if a spine or super spine device is multihomed in
all-activemode using an aggregated Ethernet interface. -
Peer gateway configurations for Active-Active redundancy with the
interconnect-multihoming-peer-gatewaysstatement set under global prorocols evpn.Note:When configuring the ESI, keep in mind that the seamless EVPN-VXLAN stitching feature does not support
single-activemode, theauto-derive lacpoption, or thesource-bmacoption. All or a list of VXLAN network identifiers (VNIs) that the spine or super spine device translates when different VNIs are configured for the same VLAN in the PODs or data centers, and WAN. For more information about setting up VNI translation, see translation-vni and interconnected-vni-list.
After you configure these elements, the EVPN control plane stitches the EVPN routes from the POD or data center network and from the WAN network into a single MAC forwarding table.
Options
The remaining statements are explained separately. Search for a statement in CLI Explorer or click a linked statement in the Syntax section for details.
Required Privilege Level
routing—To view this statement in the configuration.
routing-control—To add this statement to the configuration.
global protocols evpn [edit global protocols evpn] —To enable DCI interconnection and
configure Active-Active multihoming with the
interconnect-multihoming-peer-gateways statement.
Release Information
The statement interconnected-vni-list was introduced in Junos OS Release 20.3R1.
The addition of interconnected-vlan-list and encapsulation
mpls is part of Junos OS Release 21.4R1. The statement
interconnect-multihoming-peer-gateways is introduced in Junos
OS Release 22.2.