interconnect
Syntax
interconnect {
esi identifier {
all-active;
df-election-type {
mod;
preference {
value value (0..65535);
}
}
}
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;
}
}
Hierarchy Level
[edit protocols evpn] [edit routing-instances routing-instance-name protocols evpn]
Description
Enables interconnection of the following:
EVPN-VXLAN points of delivery (PODs) in a data center.
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 and route targets. The first set is for the POD or data center network. The second set, which you specify using the
interconnectstanza of configuration statements, is for the WAN network.An Ethernet segment identifier (ESI) if a spine or super spine device is multihomed in
all-activemode using an aggregated Ethernet interface.Note:When configuring the ESI, keep in mind that the seamless EVPN-VXLAN stitching feature does not support
single-activemode, and theauto-derive lacpandsource-bmacoptions.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.
Release Information
Statement introduced in Junos OS Release 20.3R1.