Routing

last person joined: 4 days ago 

Ask questions and share experiences about ACX Series, CTP Series, MX Series, PTX Series, SSR Series, JRR Series, and all things routing, including portfolios and protocols.
  • 1.  Specfic LSP for L3VPN

     
    Posted 08-05-2014 01:15

    Hi All !

     

    I'm using LDP for all the VPN traffic. I have a special need to setup a "static path" for one specific L3VPN. I know I have to create an LSP (RSVP) and apply a policy. But it seems it will not work in my case because RSVP will be prefer over LDP for ALL the VPNs to that PE destination...

     

    is any way to have this working strategy :

    FROM vpn_community X

    THEN install-nexthop LSP_Y

    ELSE LDP

     

    I tried to play with this, but it doesn' work...

    lab@M120# show policy-options policy-statement LSP-FOR-VPN-GREEN 
    term 1 {
        from community L3VPN-GREEN;
        then {
            install-nexthop lsp PE1-TO-PE2;
            accept;
        }
    }
    term 2 {
        then {
            install-nexthop except lsp PE1-TO-PE2;
            accept;
        }
    }
    

     

     

    Thanks for your help !

     

    Salah

    JNCIE-SP

    JNCIE-ENT

     

     



  • 2.  RE: Specfic LSP for L3VPN
    Best Answer

    Posted 08-05-2014 01:59
    Search for no-install-to-address in the forums


  • 3.  RE: Specfic LSP for L3VPN

     
    Posted 08-05-2014 02:58

    Hi !

     

    thanks a lot for your quick reply.

     

    I did look your reply http://forums.juniper.net/t5/Routing/LDP-and-RSVP-together/m-p/235912/highlight/true#M11066

     

    I tried it and that works ! great !

     

    But how I can apply the policy (update nexthop) that match a specific PE AND VPN, if the VPN routes i received come from a RR. From my point of view, I have to apply this filter on the RR (EXPORT to PE1). Any other solution ?

     

    thanks



  • 4.  RE: Specfic LSP for L3VPN

    Posted 08-05-2014 03:37
    Yes, you can apply the next-hop change at the BGP export policy of the announcing PE.
    That's the standard approach.

    There are other methods (e.g. tagging with communities and setting the lsp-next-hop at the forwarding table, etc...) but I like them much less...