[j-nsp] LDP H-VPLS interworking with BGP-VPLS Multi-homing

[Catalin Petrescu]

Hi all,

Anyone with experience with H-VPLS and BGP-VPLS multi-homing that can help
explaining if it's possible to achieve the following scenario:

-If CE2 link to PE2 fails then PE3 should be the DF for site id 1 and
l2circuit to PE33 should be taken down ( signal PW status code to anything
but 0 ).
-If PE33 main l2circuit fails then PE3 should be the DF for site 1.

If i have the vpls instance configured without mesh-group all the above
seems to work , once i configure mesh-group the DF is not changing if the
the CE2 link to PE2 fails ( connectivity-type ce not working as advertised
?? ).


Below the config

PE2:2.2.2.2/32
PE3:3.3.3.3/32
PE33:33.33.33/32



         - main l2circuit to PE2   - main link to   CE2
CE1-PE33 |
         - backup l2circuit to PE3 - backup link to CE2

PE33 relevant conf :

neighbor 2.2.2.2 {
    interface ge-1/0/1.40 { //ce1 interface
        virtual-circuit-id 40;
        ignore-mtu-mismatch;
        pseudowire-status-tlv;
        backup-neighbor 3.3.3.3 {
            virtual-circuit-id 40;
            standby;
        }
    }
}

PE2> show configuration routing-instances ORANGE
instance-type vpls;
vlan-id 40;
interface ge-1/0/0.40;
route-distinguisher 2:2;
vrf-target target:1:1;
protocols {
    vpls {
        interface ge-1/0/0.40;//ce2 interface
        no-tunnel-services;
        site R3 {
            site-identifier 1;
            multi-homing;
            mesh-group LDP;
            active-interface primary ge-1/0/0.40;
            interface ge-1/0/0.40;
        }
        ignore-mtu-mismatch;
        ignore-encapsulation-mismatch;
        mesh-group LDP {
            vpls-id 40;
            local-switching;
            neighbor 33.33.33.33 {
                encapsulation-type ethernet-vlan;
                ignore-encapsulation-mismatch;
                pseudowire-status-tlv;
            }
        }
        connectivity-type ce;
    }
}

PE3> show configuration routing-instances ORANGE
instance-type vpls;
vlan-id all;
interface ge-1/0/0.40;
route-distinguisher 3:3;
vrf-target target:1:1;
protocols {
    vpls {
        interface ge-1/0/0.40;//ce2 interface
        no-tunnel-services;
        site R3 {
            site-identifier 1;
            multi-homing;
            mesh-group LDP;
        }
        ignore-mtu-mismatch;
        mesh-group LDP {
            vpls-id 40;
            neighbor 33.33.33.33 {
                encapsulation-type ethernet-vlan;
                pseudowire-status-tlv;
            }
        }
        connectivity-type ce;
    }
}

Regards,

Catalin