An ESI must be configured on a PE interface or a BD connected to a CE. The same ESI must be configured for PE interfaces connecting to the same CE.
The PEs connecting to the same CE or BD must have the same ESI configured. After PEs exchange routes that carry ESIs, a PE can be aware of the other PEs connecting to the same CE, helping implement load balancing or FRR.
The interface is in the up state. Otherwise, Ethernet segment routes cannot be generated.
An ESI is statically set on the interface.
An ESI is dynamically generated on the interface.
Static configuration is recommended. Compared with dynamic ESI generation, static configuration allows EVPN to implement faster traffic switching during a DF election in a dual-homing scenario with active-active PEs.
The features required in an EVPN dual-homing scenario, such as fast convergence, split horizon, and DF election, all become invalid in a single-homing scenario. In such a scenario, configuring an ESI is optional on a single-homing PE.
Perform this configuration if a VLAN is used to access an EVPN.
Perform this configuration if VXLAN is used to access an EVPN and the EVPN transmits ARP or MAC routes.