Multivendor Support for Calculated LSPs

Unfortunately, some MPLS implementations do not support the ability to forward packets received on an egress LSP to their OSPF router ID and/or BGP next hop address.

If your MPLS network includes equipment that does not support this type of IP forwarding, you can use configuration commands to explicitly control the use of calculated LSP next hops.

The following commands enable and disable all use of LSP next hops. No IP traffic is routed over an LSP when mpls-next-hop IP routing capability is disabled.

enable iproute mpls-next-hop
disable iproute mpls-next-hop

These commands enable and disable the calculation of LSP next hops by OSPF:

enable ospf mpls-next-hop {vr vrf_name}
disable ospf mpls-next-hop {vr vrf_name}

These commands enable and disable the calculation of LSP next hops by BGP:

enable bgp mpls-next-hop
disable bgp mpls-next-hop