Routing
Routing

use a specific lsp for a l3VPN when LDP is the common protocol

‎09-18-2017 08:56 AM

Hi,
I have problem to force traffic to use a specfic lsp instead of ldp.
Is it supported in VMX (16.1) or is something wrong with my configuration?

Co

routing-options {                       
    router-id 10.250.0.4;
    autonomous-system 64512;
    forwarding-table {
        export force-vpn;
    }
}


protocols {
    rsvp {
        interface ge-0/0/1.0;
        interface ge-0/0/2.0;
    }
    mpls {
        optimize-timer 5;
        label-switched-path hk-sb {
            no-install-to-address;
            to 10.250.0.6;
            adaptive;
            primary hk-sb;
        }
        path hk-sb {
            10.1.0.1 strict;
            10.1.0.6 strict;
        }                               
        interface ge-0/0/1.0;
        interface ge-0/0/2.0;
    }
    bgp {
        mtu-discovery;
        group ibgp {
            type internal;
            family inet {
                unicast;
            }
            family inet-vpn {
                unicast;
            }
            neighbor 10.250.0.6 {
                local-address 10.250.0.4;
            }
            neighbor 10.250.0.5 {
                local-address 10.250.0.4;
            }
        }
    }
    ospf {
        traffic-engineering;            
        area 0.0.0.0 {
            interface ge-0/0/1.0;
            interface ge-0/0/2.0;
            interface lo0.0 {
                passive;
            }
        }
    }
    ldp {
        interface ge-0/0/1.0;
        interface ge-0/0/2.0;
    }
}
policy-options {
    policy-statement force-vpn {
        term 1 {
            from community force_vpn;
            then {
                install-nexthop strict lsp hk-sb;
            }
        }
        term accept_all {
            then accept;                
        }
    }
    community force_vpn members target:64512:100;
}

routing-instances {
    vpn-a {
        description Office;
        instance-type vrf;
        interface ge-0/0/0.0;
        route-distinguisher 64512:100;
        vrf-target target:64512:100;
        vrf-table-label;
        protocols {
            bgp {
                group ebgp {
                    type external;
                    neighbor 10.0.0.10 {
                        peer-as 65002;
                    }
                }
            }
        }
    }                                   
}

nfig:

7 REPLIES 7
Routing

Re: use a specific lsp for a l3VPN when LDP is the common protocol

‎09-18-2017 10:20 AM

Can you remove below command and check?

no-install-to-address  

 Also Before doing this, can you check if you egress router ip in inet.3 table?

 

 

Routing

Re: use a specific lsp for a l3VPN when LDP is the common protocol

‎09-18-2017 10:23 AM

Hi,

 

I think you can not use specific LSP for an instance when using LDP and RSVP. This policy works if you have 2 equal cost LSP paths.

 

The below old thread in the forum has great details.

 

Selecting an LSP for the VPLS Routing Instance

 

 

[KUDOS PLEASE! If you think I earned it!

If this solution worked for you please flag my post as an "Accepted Solution" so others can benefit..]

Routing

Re: use a specific lsp for a l3VPN when LDP is the common protocol

‎09-18-2017 11:16 AM

Few thought..

 

First: of all you need to remove this command because it's preventing RSVP route form being install into inet.3

no-install-to-address  

 If you don't resolve BGP next-hop with rsvp route in inet.3, you will not be able to use your strict-path LSP.

 

Second: I don't understand the reson of applying export policy to the forwarding table. Even if you don't apply the policy and simply remove no-install-to-address, it will work fine and your traffic will traverse across strict-path LSP

 

HTH

Routing

Re: use a specific lsp for a l3VPN when LDP is the common protocol

‎09-18-2017 09:53 PM

Hi,

Thanks for your comments.

 

The idea is that only a specific l3vpn should use the rsvp path, rest of the l3vpns should use ldp.

 

I have removed the no-install-to-address + changed the preference to 10 for the lsp.

 

Still only ldp is used.

 

//Niklas

 

 

Routing

Re: use a specific lsp for a l3VPN when LDP is the common protocol

‎09-18-2017 10:12 PM

Hi,

You have right about the forwarding policy.

It start to work direclty when I did two lsp.

 

//Niklas

Routing

Re: use a specific lsp for a l3VPN when LDP is the common protocol

‎09-18-2017 10:53 PM

Hi Niklas,

 

Great..

 

[KUDOS PLEASE! If you think I earned it!

If this solution worked for you please flag my post as an "Accepted Solution" so others can benefit..]

Routing

Re: use a specific lsp for a l3VPN when LDP is the common protocol

‎09-19-2017 02:25 AM

Hi,

 

You can have this working with the "no-install-address" but specifying another "install <alternative-next-hop>" in the LSP.

This would require a secondary loopback IP or a fictituous next-hop IP on the egress PE.

Either routes advertised by the egress PE will need to have its next-hop changed to this alternate next-hop or import policies applied at ingress PE to change next-hop.

        label-switched-path hk-sb {
            no-install-to-address;
            install <secondary-next-hop>

 

This should allow to selectively transport VPN traffic over specific LSPs.

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

http://forums.juniper.net/t5/Routing/Specfic-LSP-for-L3VPN/m-p/252074

 

Cheers,

Ashvin