Help us improve your experience.

Let us know what you think.

Do you have time for a two-minute survey?




Hierarchy Level


Configure an Ethernet Segment Identifier (ESI) in either EVPN multihoming active/standby or active/active mode by using one of the following methods:

  • Manually configure an ESI on a physical, aggregated Ethernet, or logical interface using the esi identifier configuration statement.

  • Configure an aggregated Ethernet interface or aggregated Ethernet logical interface to automatically derive an ESI from the Link Aggregation Control Protocol (LACP) configuration. Use the auto-derive lacp configuration statement.

    If you configure automatic ESI on an aggregated Ethernet interface, the device generates an ESI. The device assigns that particular ESI to all logical interfaces on the aggregated Ethernet interface. You can also configure automatic ESI on one or more logical interfaces on an aggregated Ethernet interface. In that case, the device generates an ESI for each logical interface on which you enabled the feature.


You can't commit a configuration in which you try to configure the following on the same physical or logical aggregated Ethernet interface:

  • Manually configure an ESI on the aggregated Ethernet interface.
  • Enable the automatic ESI feature on the aggregated Ethernet interface.

Starting in Junos OS Releases 15.1F6 and 17.1R1 for MX Series routers and Junos OS Release 17.3R1 for EX9200 switches, you can specify an ESI on a logical interface. In earlier releases, you can configure an ESI only on a physical or aggregated Ethernet interface. For example:

When configuring an ESI, remember that the ESI is a factor in the designated forwarder (DF) election process. For example, let's look at a case in which you configure EVPN multihoming active/standby on aggregated Ethernet interface ae0. In this case, ae0 also has logical interfaces on unit 1 and unit 2. The DF election process might put ae0 into the down state due to the ESI and other determining factors. The logical interfaces configured on ae0 would also be down, and unable to provide services to their respective customer sites (VLANs).

If you specify an ESI on a logical interface, the DF election process now occurs at the individual logical interface level. You can better utilize logical interfaces. For example, you configure logical interfaces ae0.1 and ae0.2 on aggregated Ethernet interface ae0. You also enable EVPN multihoming active-standby on both logical interfaces. Then the DF election brings ae0.1 down based on the ESI on ae0.1 and other DF determining factors. Despite logical interface ae0.1 being down, logical interface ae0.2 and other ae0 logical interfaces can remain up. The DF election process doesn't disrupt customer services to the respective customer sites (VLANs).


A physical interface on which you configure an ESI won't become a DF if any one of its logical units is down. As a result, if you don't want logical interfaces in one unit to forward traffic, then delete the logical unit rather than disabling it. We recommend that you do not explicitly disable any logical units associated with a physical interface on which you configured an ESI.



Ten octet value. Reserved values: ESI value 0 and all fixed filters. You can't use the reserved values for configuring a multihomed Ethernet segment.

  • You can't configure two interfaces (physical, logical, or aggregated Ethernet) with the same ESI value.

  • The left most octet must be configured as 00. The other 9 octets are fully configurable.


Configure the EVPN active-active multihoming mode of operation.


Configure the EVPN active-standby multihoming mode of operation.


We don't support active-standby multihoming mode on QFX Series switches or in EVPN configurations with VXLAN overlays. As a result, if you configure the single-active option on QFX Series switches or in EVPN-VXLAN configurations, the device ignores that configuration item.

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

interface—To view this statement in the configuration.

interface-control—To add this statement to the configuration.

Release Information

Statement introduced in Junos OS Release 14.1.

source-bmac option introduced in Junos OS Release 18.1R1 on MX Series routers with MPCs and MICs.

auto-derive stanza introduced in Junos OS Release 18.4R1 on MX Series routers and QFX Series switches.

Support at the following hierarchy levels introduced in Junos OS Release 20.3R1 on QFX Series switches: [edit protocols evpn interconnect] and [edit routing-instances routing-instance-name protocols evpn interconnect].