Routing

Hi all,

First of all my setup was using LDP-VPLS for Layer 2 services. The PE consists of Juniper and cisco. If i want to do some traffic engineering for certain LDP-VPLS traffic is it possible? I means we force certain vlan in VPLS service to enter specific LSP. I'm read this doc and it show use community. But in my case, i'm use LDP-VPLS based so is it the community was created as tag only the traffic? Is it the both PE need to use same community tag? Below is my config and appreciate any feedback if have someone can verify whether is correct or not.

https://www.juniper.net/documentation/us/en/software/junos/vpn-l2/topics/concept/vpns-mapping-vpls-traffic-to-specific-lsps.html

https://supportportal.juniper.net/s/article/M-MX-T-How-to-map-a-L2circuit-traffic-to-take-a-particular-RSVP-LSP-if-there-are-multiple-equal-cost-RSVP-LSP-s-available-to-reach-the-L2circuit-neighbor?language=en_US

MX304-1# run show configuration protocols mpls 
traffic-engineering {
    mpls-forwarding;
}
explicit-null;
icmp-tunneling;
no-cspf;
label-switched-path mx304-1-to-PE3-CSC-ISRv {
    from 10.251.2.1;
    to 10.251.2.6;
    primary MX304-1->PE2->PE3;
}

MX304-1# run show configuration routing-options forwarding-table 
export [ mapping-v2449-to-lsp ];

[edit policy-options policy-statement mapping-v2449-to-lsp]
root@MX304-1# show 
term 1 {
    from {

       protocol vpls
        rib mpls.0;
        community vpls-2449;
    }
    then {
        install-nexthop lsp mx304-1-to-PE3-CSC-ISRv;
        accept;
    }
}

root@MX304-1# run show configuration routing-instances LDP-VPLS-v2449 
instance-type vpls;
protocols {
    vpls {
        

 neighbor 10.251.2.6 {
            community vpls-2449;
            pseudowire-status-tlv {
                hot-standby-vc-on;
            }                           
        }                               
                    
        encapsulation-type ethernet-vlan;
        no-tunnel-services;             
        vpls-id 2449;                   
        ignore-mtu-mismatch;            
        ignore-encapsulation-mismatch;  
        pseudowire-status-tlv;          
        connectivity-type ce;           
    }                                   
}                                       

community vpls-2449 members 300:300

Thanks

In policy mapping-v2449-to-lsp - term 1: remove "from rib mpls.0" and it will work. Also, I think the community should be a RT extended community, not a standard one.

Hi @btodorovic,

As i'm understand the RT extended community just use incase we use BGP-VPLS but in my case just use LDP-VPLS. So is it need RT extended community? Appreciate your feedback.

Thanks

Last time when I tested this, I also used LDP-signaled L2VPN services (Martini L2CKTs actually). And I think RT extended community was required. Since LDP-VPLS uses Martini pseudowires under its engine hood, I think this applies there as well. Give it a try if the standard community does not work for you.

Also, remove "protocol vpls". Just leave the community value.

Hello, 

You can use transport-class to do this. 
Check the file.