Transit chained composite next hops are not supported on MX platforms. If transit chained composite next hop is configured, it can cause traffic loss for transit traffic.
This article suggests the ideal workaround to avoid such traffic loss.
On MX platforms, if the following chained composite next hop transit configuration is enabled, it may cause traffic loss:
[edit routing-options forwarding-table chained-composite-next-hop] transit { (all | no-all); (l2vpn | no-l2vpn); (l3vpn | no-l3vpn); (labeled-bgp | no-labeled-bgp); (ldp | no-ldp); (ldp-p2mp | no-ldp-p2mp); lsp-statistics-from-route; (rsvp | no-rsvp); (rsvp-p2mp | no-rsvp-p2mp); (static | no-static); }
To resolve this issue, remove or delete the transit chained composite next hop configuration on the MX platform and reboot the router.
delete routing-options forwarding-table chained-composite-next-hop transit commit