Specifying an LSP as the Next Hop for Static Routes

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:

Note: 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).

For a list of hierarchy levels at which you can include these statements, see the statement summary sections for these statements.

The preference value can be a number in the range from 0 through 4,294,967,295 (2³² – 1) with a lower number indicating a more preferred route. The metric value can also be a number in the range from 0 through 4,294,967,295.

Note: 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.

To specify a point-to-multipoint LSP as the next hop for a static route, include the following statements:

For a list of hierarchy levels at which you can include these statements, see the statement summary sections for these statements.

Enable the qualified next-hop address on the interface by specifying the interface option. The preference value can be a number from 0 through 4,294,967,295 (2³² – 1). A lower number indicates a more preferred route. The metric value can also be a number from  0 through 4,294,967,295.