EVPN MPLS multi-homing is supported on PEs that use non-system IPv4 or IPv6 addresses for tunnel resolution. Similar to multi-homing in EVPN VXLAN networks, (see Non-system IPv4 and IPv6 VXLAN Termination for EVPN VXLAN Multihoming), additional configuration steps are required.
The configure service system bgp-evpn eth-seg es-orig-ip ip-address command must be configured with the non-system IPv4 or IPv6 address used for the EVPN-MPLS service. This command modifies the originating IP field in the ES routes advertised for the Ethernet Segment, and makes the system use this IP address when adding the local PE as DF candidate.
The configure service system bgp-evpn eth-seg route-next-hop ip-address command must also be configured with the non-system IP address. This command changes the next-hop of the ES and AD per-ES routes to the configured address.
All the EVPN MPLS services that make use of the Ethernet Segment must be configured with the configure service vpls|epipe bgp-evpn mpls route-next-hop ip-address command.
When multi-homing is used in the service, the same IP address should be configured in all three of the commands detailed above, so the DF Election candidate list is built correctly.