Quantcast
Channel: All Routing posts
Viewing all articles
Browse latest Browse all 8688

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

$
0
0

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:


Viewing all articles
Browse latest Browse all 8688

Trending Articles



<script src="https://jsc.adskeeper.com/r/s/rssing.com.1596347.js" async> </script>