Specify an LSP as the Next Hop for a Static Route

Static routes can be configured with a next hop that is a label-switched path (LSP). This is useful when implementing filter-based forwarding. You can specify an LSP as the next hop and assign an independent preference and metric to this next hop.

To specify an LSP as the next hop for a static route, include the following statements at the [edit routing-options static route] hierarchy level (for routing instances, include the statements at the [edit routing-instances routing-instance-name routing-options static route] hierarchy level):

[edit routing-options static route] 

lsp-next-hop lsp-name {

    metric metric;

    preference preference; 

}

 The preference and metric configured by means of the lsp-next-hop statement only apply to the LSP next hops. The LSP next-hop preference and metric override the route preference and metric (for that specific LSP next hop), similar to how the route preference overrides the default preference and metric (for that specific route).

The preference value can be a number in the range 1 through 255, with a lower number indicating a more preferred route. The metric value can be a number in the range 1 through 65,535.

The lsp-next-hop statement is mutually exclusive with all other types of next hops, except for next-hop address and qualified-next-hop. Therefore, you cannot configure next-hop reject, next-hop discard, next-hop receive, and next-table with lsp-next-hop for the same destination.