Automatically derived ESI configuration

In the current implementation, Junos OS derives the Ethernet segment identifier (ESI) from the system ID and the administrative key on the local multihomed provider edge (PE) device that is a part of the LACP link (actor). Starting in Junos OS, you can also configure the multihomed devices on an EVPN-VXLAN network to automatically generate the ESI from:

• The system ID and administrative key on the remote customer edge (CE) device (partner).
• The locally configured mac and local discriminator values

To automatically derive the ESI using the system ID and administrative key on the remote CE device, include type-1-lacp at the [edit interfaces aeX aggregated-ether-options lacp auto-derive] hierarchy level.

To automatically derive the ESI using locally configured values, configure mac and local-discriminator at the [edit interfaces aeX aggregated-ether-options lacp auto-derive type-3-system-mac] hierarchy level.