Recursive Next-hop Resolution with MPLS Next-hop
Overview
Recursive Next-hop Resolution with MPLS Next-hop enables OcNOS to resolve recursive BGP and Static routes using MPLS transport paths instead of IP next-hops. This feature allows seamless packet forwarding through an MPLS core where BGP is not active, supporting scalable BGP-Free Core deployments. The system recognizes available MPLS Label Switched Paths (LSPs) as valid forwarding options, ensuring reachability across label-switched domains without requiring additional routing protocols in the backbone.
Feature Characteristics
| • | Supports route resolution over LDP, RSVP-TE, and Segment Routing (SR-MPLS) tunnels. |
| • | Automatically updates route resolution when the underlying MPLS transport changes. |
| • | Integrates with MPLS ECMP, FRR, and TI-LFA for resiliency and load balancing. |
| • | Displays MPLS-resolved recursive routes in standard routing table views. |
| • | Maintains consistent behavior for both BGP and Static recursive routes. |
| • | Operates transparently without additional configuration changes to the routing process. |
Benefits
Enables BGP-Free Core Operation: Backbone routers forward traffic using MPLS without running BGP.
Simplified Architecture: Reduces control-plane load and configuration complexity.
Improved Resiliency: Leverages MPLS protection mechanisms for faster failover.
Optimized Traffic Flow: Supports equal-cost load sharing over multiple MPLS paths.
Operational Visibility: Provides clear differentiation of MPLS-resolved routes for easier troubleshooting.
Limitation
| • | BGP multipath is not supported for BGP-Free Core deployments. |
| • | If multiple BGP paths exist for the same prefix, the RIB selects only one path for MPLS next-hop resolution. |
| • | Equal-Cost Multipath (ECMP) and Fast Reroute (FRR) are provided only by the underlying MPLS transport for that single resolved path. |