[j-nsp] Need help on Multi-home bgp vpls

[Rajendra Maharjan]

HI Everyone,

We are searching for a solution with below scenario within bgp vpls. 

Customers A,B and C are all with same vpls domain. We tried with multihoming bgp vpls solution which will not solve our scenario. The solution works only when there is issue with link beween Router-A (PE)- Switch A or Router-B(PE)-Switch B or any PE's failure where Router-A working as primary or designated VPLS edge (VE) device and Router-B working as secondary VE device for a CE-A and CE-B for reachablility from CE-C.

But our main concern is when there is link breakage/failure between two switches, only primary connected switch with CE-A is up within vpls but the other CE-B wont be reachable. 
Is there any other solution that will make both CE's to be reachable with same vpls domain/instance when there is failure of link between 1-2  i.e. between two switches.

You can refer to this link with only one CE between 2 PE :

https://www.juniper.net/techpubs/en_US/junos/topics/topic-map/vpls-bgp-multihoming.html

Diagram:


 -------------			---------------			---------------
| Router-A |	<-------->	| Router-B |	<-------->	| Router-C |
 -------------			---------------			---------------
        |				         |					|
        |	   			         |					|
--------------			--------------			      CE - C
| Switch-A |   <------->  	| Switch-B |			
--------------			--------------			
        |				         |
        |				         |
   CE - A			           CE - B	 


ROUTER A

[edit]
protocols {
    mpls {
        interface ge-1/1/0.0;
    }
    bgp {
        family inet {
            unicast;
        }
        family inet-vpn {
            unicast;
        }
        family l2vpn {
            signaling;
        }
        local-as 65007;
        group INTERNAL {
            type internal;
            local-address 172.22.0.109;
        
            neighbor 172.22.0.108
            neighbor 172.22.0.103;
        }
    }

routing-instances {
    CUST-A {
        instance-type vpls;
        interface ge-1/1/9.999;
        route-distinguisher 65001:100;
        vrf-target target:65001:200;
        protocols {
            vpls {
                site-range 10;
                no-tunnel-services;
                site CUST-A {
                    site-identifier 1;
                    multi-homing;
                    site-preference 200;
                }
            }
        }
    }
}

Router B
[edit]
routing-instances {
    CUST-A {
        instance-type vpls;
        interface ge-1/1/9.999;
        route-distinguisher 65001:100;
        vrf-target target:65001:200;
        protocols {
            vpls {
                site-range 10;
                no-tunnel-services;
                site CUST-A {
                    site-identifier 1;
                    multi-homing;
                    site-preference 100;
                }
            }
        }
    }
}

Router C

[edit routing-instances CUST-A] 
instance-type vpls;
interface ae1.999;
route-distinguisher 65001:100;
vrf-target target:65001:200;
protocols {
    vpls {
        site-range 10;
        no-tunnel-services;
        site CUST-A {
            site-identifier 5;
        }
    }
}




Regards,
Rajendra Maharjan