Help us improve your experience.

Let us know what you think.

Do you have time for a two-minute survey?

 

esi

 

Syntax

Hierarchy Level

Release Information

Statement introduced in Junos OS Release 14.1.

Statement introduced in Junos OS Releases 15.1F6 and 17.1 on MX Series routers with MPCs.

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.

Description

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 using the auto-derive lacp configuration statements.

    If you configure automatic ESI on an aggregated Ethernet interface, an ESI is generated, and that particular ESI is assigned to all logical interfaces on the aggregated Ethernet interface. If you configure automatic ESI on one or more logical interfaces on an aggregated Ethernet interface, an ESI is generated for each logical interface on which the feature is enabled and assigned to that particular logical interface.

Note

If you manually configure an ESI and enable the automatic ESI feature on an aggregated Ethernet interface or aggregated Ethernet logical interface, you will receive an error when you try to commit the configuration.

In releases before Junos OS Release 15.1F6 and 17.1R1 for MX Series routers and Junos OS Release 17.3R1 for EX9200 switches, you can specify an ESI only on a physical or aggregated Ethernet interface, for example, set interfaces ae0 esi 00:11:22:33:44:55:66:77:88:99. If you specify an ESI on a physical or aggregated Ethernet interface, keep in mind that an ESI is a factor in the designated forwarder (DF) election process. For example, assume that you configure EVPN multihoming active-standby on aggregated Ethernet interface ae0, and given the ESI configured on ae0 and other determining factors, the DF election results in ae0 being in the down state. Further, all logical interfaces configured on aggregated Ethernet interface ae0, for example, set interfaces ae0 unit 1 and set interfaces ae0 unit 2 are also in the down state, which renders logical interfaces ae0.1 and ae0.2 unable to provide services to their respective customer sites (VLANs).

Starting with 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. If you specify an ESI on a logical interface, the DF election process now occurs at the individual logical interface level, which enables you to better utilize logical interfaces. For example, assume that you configure logical interfaces ae0.1 and ae0.2 on aggregated Ethernet interface ae0. You configure EVPN multihoming active-standby on both logical interfaces and given the ESI configured on ae0.1 and other determining factors, the DF election results in ae0.1 being in the down state. Despite logical interface ae0.1 being down, logical interface ae0.2 and other logical interfaces configured on ae0 can be in the up state and provide services to their respective customer sites (VLANs).

Options

esi identifierTen octet value. ESI value 0 and all fixed filters are reserved, and not used for configuring a multihomed Ethernet segment.
Note
  • Two interfaces (physical, logical, or aggregated Ethernet) cannot be configured with the same ESI value.

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

all-activeConfigure the EVPN active-active multihoming mode of operation.
single-activeConfigure the EVPN active-standby multihoming mode of operation.

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.