Description

VPLS is not using specific lsp as per the configured policy despite community match.


As per the policy named test ,lsp 'test' needs to mapped to LDP-VPLS however the mapped lsp is test2 to same destination PE.

Further the community is matching correctly in the policy and is exported in forwarding-table



[edit routing-instances LDP-VPLSCUST]
lab@MX# show
instance-type vpls;
protocols {
    vpls {
        interface xe-0/0/3.100;
        neighbor 30.30.30.30;
        no-tunnel-services;
        vpls-id 100;
    }
}
interface xe-0/0/3.100;
route-distinguisher 1:9;
vrf-target target:100:1;



[edit policy-options policy-statement test]
lab@MX# show
term 1 {
    from {
        rib mpls.0;
        community MPLS-TE-Testing;
    }
    then {
        install-nexthop lsp test;
        accept;
    }
}


[edit routing-options]
lab@MX# show
router-id 6.6.6.6;
autonomous-system 65004;

forwarding-table {
    export test;
}

community MPLS-TE-Testing members target:100:1;


However incorrect lsp gets associated with lsi as below

lab@MX# run show route table mpls.0

mpls.0: 8 destinations, 8 routes (8 active, 0 holddown, 0 hidden)
+ = Active Route, - = Last Active, * = Both

lsi.1048839        *[VPLS/7] 00:00:02, metric2 1
                       to 10.1.2.1 via xe-0/0/0.0, label-switched-path test
                    >  to 10.1.2.1 via xe-0/0/0.0, label-switched-path test2
 

Symptoms

Incorrect lsp will be associated with lsi despite community match as per  policy

Solution

Inorder to resolve the issue associated the PE neighbor in the VPLS with community which is being matched in policy test.

Post above solution correct lsp test will be associated with VPLS in accordance to policy configured

 [edit routing-instances LDP-VPLSCUST]
lab@MX# show  
instance-type vpls;
protocols {
    vpls {
        interface xe-0/0/3.100;
        neighbor 30.30.30.30 {
            community MPLS-TE-Testing;
        }
        no-tunnel-services;
        vpls-id 100;
    }
}
interface xe-0/0/3.100;
route-distinguisher 1:9;
vrf-target target:100:1;


[edit routing-instances LDP-VPLSCUST]
lab@MX# run show route table mpls.0

mpls.0: 8 destinations, 8 routes (8 active, 0 holddown, 0 hidden)
+ = Active Route, - = Last Active, * = Both

   
lsi.1048839        *[VPLS/7] 00:02:29, metric2 1
                       to 10.1.2.1 via xe-0/0/0.0, label-switched-path test

[edit routing-instances LDP-VPLSCUST]
lab@MX#  

Modification History

NA