MoFRR over RSVP-TE unicast domain is possible if there are multiple RSVP-TE tunnels.
For the direct case, that is, where there is a direct T-LDP session from the leaf node to the root node, LDP MoFRR is not set up. The operator must set up RSVP FRR if redundancy is required.
For the indirect case, that is, where there are T-LDP sessions from the leaf node to the intermediate nodes, LDP sets up MoFRR if multiple eligible tunnel endpoints are provided by IGP and T-LDP sessions exist to these.
LDP uses the tunneled NH tunnel far-end provided in the RTM route to select a phop. If multiple tunneled NH tunnel far-ends are provided, LDP can use one as primary and one as backup to select the phops. If the RTM route has non-tunneled next-hops to multiple phop nodes, it selects a primary and a backup.
For MLDP over RSVP or MLDP over IGP shortcut, upstream MoFRR works only if ECMP is set to 2 or greater. There is currently no support for MoFRR leveraging an LFA route. Without ECMP set to 2 or greater, LDP cannot calculate the backup MoFRR path required for upstream traffic protection. The primary and backup ECMP selected path must be disjoint throughout the RSVP-TE cloud to protect against physical failures.