The same Ethernet segment identifier (ESI) must be configured for provider edge (PE) interfaces connecting to the same customer edge (CE).
PEs connecting to the same CE must have the same ESI configured. PEs exchange routes that carry ESIs, so that a PE can discover other PEs connecting to the same CE as itself. This helps implement load balancing or FRR.
The interface has been bound to an I-EVPN instance using the evpn binding vpn-instance command.
The interface is in the Up state. Otherwise, Ethernet segment routes cannot be generated. In scenarios where a CE is dual-homed to two PEs over an Eth-Trunk, an E-Trunk must be configured to ensure that the two CE interfaces connecting to PEs are both Up.
An ESI can be either statically configured or dynamically generated on an interface.
Functions, such as rapid convergence, split horizon, and DF election that are required in the EVPN dual-homing scenario fail to take effect in a single homing scenario. In such a scenario, configuring the ESI is optional on a dual-homing PE.