EVPN all-active multi-homing

Note:

The 7210 SAS supports only single-active multi-homing. All-active multi-homing (with aliasing) is not supported on any 7210 SAS platform described in this document. References to all-active multi-homing (and aliasing) are only included in this section for completeness of feature description and are not intended to imply support on the 7210 SAS. Refer to the 7210 SAS Software Release Notes 22.x.Rx, part number 3HE 18217 000x TQZZA, for information about features supported in each load of the Release 22.x.Rx software.

In accordance with RFC 7432, all-active multi-homing is only supported on access LAG SAPs, and it is mandatory to configure the CE with a LAG to avoid duplicated packets to the network. LACP is optional.

When PE3 installs MAC1 in the Forwarding Database (FDB), it associates MAC1 not only with the advertising PE (PE1), but also with all the PEs advertising the same esi (ESI2) for the service. In this example, PE1 and PE2 advertise an AD per-EVI route for ESI2; therefore, PE3 installs the two next-hops associated with MAC1.

To enable aliasing, configure ECMP greater than 1 in the bgp-evpn>mpls context.