Help us improve your experience.

Let us know what you think.

Do you have time for a two-minute survey?




Hierarchy Level


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).

You can use this statement on devices that support seamless EVPN-VXLAN stitching to interconnect PODs or data centers through either:

  • An EVPN-VXLAN WAN network—Use the encapsulation vxlan option.

  • An EVPN-MPLS WAN network—Use the encapsulation mpls option.

The devices that enable the interconnection are called interconnection gateways (iGW devices). If possible, you should configure redundant iGW devices with all-active multihoming on each side of the interconnection, which we call multihoming peer iGW devices. The iGW devices are usually spine layer devices, or they are separate devices in a super-spine layer.

On each iGW device, you set up an EVPN routing instance using the default switching instance. Alternatively, you can configure the EVPN routing instance using instance-type virtual-switch or evpn, depending on the instance types the device supports. In the instance, 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 with this interconnect statement, is for the WAN network.


    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.

    To enforce this condition for DCI seamless stitching with EVPN Type 5 routes as well, you also see a commit error with Junos OS and Junos OS Evolved Releases starting in 22.4R2 and 23.1R1.

  • An interconnection Ethernet segment identifier (iESI) for all-active multihoming among the peer iGW devices on each side of the interconnection.

    You configure the iESI using the esi option of this interconnect statement. You must use the same iESI value on all peer iGW devices in the same POD or data center, and unique iESI values for each POD or data center.


    When configuring the interconnection ESI, keep in mind that the seamless EVPN-VXLAN stitching feature does not support single-active mode, the auto-derive lacp option, or the source-bmac option.

  • (Required for iGW devices with interconnect gateway multihoming) A list of the iGW device's peer multihoming iGW devices.

    On each iGW device, configure the interconnect-multihoming-peer-gateways statement at the global [edit protocols evpn] hierarchy level to specify the IP loopback addresses of that device's peer multihoming iGW devices. This option simplifies control plane route handling to optimize forwarding among the peer iGW devices, and helps avoid loops during EVPN configuration changes.

  • VXLAN network identifiers (VNIs) that the iGW 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 in DCI use cases, 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.


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

Option interconnected-vni-list introduced in Junos OS Release 20.3R1.

Options interconnected-vlan-list and encapsulation mpls introduced in Junos OS Release 21.4R1.