EVPN-MPLS services with RSVP multipath as a transport provides, Multiple RSVP tunnels which are grouped in ECMP/Multipath group to do load sharing for better optimized and efficient usages of multiple RSVP trunks towards the same Destination.

At ingress node the traffic is load-balanced based on the configured hash (L3 src/dest IP/port, L2 src/dst mac, or in-label if intermediate Autonomous segments). Each LSP path within multipath group can provide individual protection for each path (facility, 1-to-1, secondary).

Each tunnel path in multipath group cost may vary (can have different hop, with consideration for load-balancing the traffic).

Unicast traffic is load shared across all the available multipath member (but not mandatory always) where as in case of BUM only the Active member carries traffic. Addition/deletion should not have impact in traffic in case of unicast, and switchover time is not guaranteed <50ms in case of BUM traffic.

This feature supports across all EVPN service as both SH and MH modes and only BUM Traffic not supported for ELINE service alone as per RFC standard.

See Figure 24-1, Figure 24-3, Figure 24-5.

See the previous configurations to bring up the EVPN service for both SH and MH. Transport alone we need to change it from LDP/RSVP to RSVP Multipath as per below configurations.

Below command shows RSVP multipath group info per VPN-ID/destination.

Below show command gives info about which MP member carries traffic.

Below commend gives ingress and egress evpn mpls counters during bi-directional traffic for BUM and unicast traffic per VPN id.