Help us improve your experience.

Let us know what you think.

Do you have time for a two-minute survey?

header-navigation
keyboard_arrow_up
list Table of Contents
file_download PDF
{ "lLangCode": "en", "lName": "English", "lCountryCode": "us", "transcode": "en_US" }
English
keyboard_arrow_right

Establishing FA-LSP Path Information

date_range 04-Aug-23

When you configure explicit LSP paths for an FA-LSP, you must use the traffic engineering link remote address as your next-hop address. When CSPF is supported, you can use any path option you wish. However, when CSPF is disabled with the no-cspf statement at the [edit protocols mpls label-switched-path lsp-name] hierarchy level, you must use strict paths.

content_copy zoom_out_map
[edit] 
protocols {
    mpls {
        path path-name {
                             next-hop-address (strict | loose);               
        }
    }
}
Note:

If the end-to-end LSP originates on the same routing platform as the FA-LSP, you must disable CSPF and use strict paths.

footer-navigation