Routing

Expand all | Collapse all

rsvp lsp fallback

  • 1.  rsvp lsp fallback

    Posted 13 days ago
    Hello, I have the following scenario using rsvp and ldp:

    l2vpn 1 lsp 01
    l2vpn 2 lsp 02
    l2vpn 3 lsp 03

    label-switched-path lsp01 {
        to 10.30.32.13;
        bandwidth 100m;
        priority 7 7;
    }
    label-switched-path lsp02 {
        to 10.30.32.13;
        bandwidth 100m;
        priority 6 6;
    }
    label-switched-path lsp03 {
        to 10.30.32.14;
        bandwidth 100m;
        priority 6 6;
    }​

    First requirement is that a l2vpn should only use 1 specific lsp, got it done using a policy and community with strict lsp.

    term default {
        from {
            protocol l2vpn;
            community l2vpn-01;
        }
        then {
            install-nexthop strict lsp lsp01;
        }
    }​

    Next requirement is that in case of rsvp failure, only specific l2vpns should be allowed to use ldp as fallback. What's is the equivalent option for cisco "disable-fallback" ?



  • 2.  RE: rsvp lsp fallback

    Posted 13 days ago
    Hi Alan,

    You can try  filtering the received LDP label bindings for the concerned destination on ingress PE.

    https://www.juniper.net/documentation/en_US/junos/topics/reference/configuration-statement/import-edit-protocols-ldp.html

    Please not when a binding is filtered, it still appears in the LDP database, but is not considered for installation as part of a label-switched path (LSP)  also the label should be marked as "Filtered" in LDP database.

    ------------------------------
    Nupur Kanoi
    3xJNCIE, Juniper Ambassador and Ingenious Champion
    ------------------------------



  • 3.  RE: rsvp lsp fallback

    Posted 7 days ago
    @kanoi.nupur some l2vpns should be able to use ldp as fallback ​, like 2 lvpns to the same pe.