Hi Not directly an answer to the l2VPN but...
Maybe it is an option to switch the customer from L2VPN to VPLS For vpls with dual connection you can use Primary/Backup Interfaces (BGP VPLS only) ( setting "active-interface any" when you specify 2 interfaces under the site under protocol vpls under the routing-instance) Other less viable solutions: MC-LAG Ethernet Ring Protection A spanning tree protocol Regards alexander -----Ursprüngliche Nachricht----- Von: juniper-nsp [mailto:[email protected]] Im Auftrag von Muruganandham M Gesendet: Dienstag, 22. März 2016 14:05 An: [email protected] Betreff: [j-nsp] Kompella L2VPN redundancy solution Hi, There is a customer requirement where hub site has dual CEs connecting to dual CPEs which are connecting to the same PE router. The spoke site need to connect the hub site on primary-backup mode. Can not use the site preference in l2vpn instance since both primary and backup sites are terminating on the same PE. Tried testing with the two different routing instances with same RT and Site IDs on the hub site PE. This causes l2vpn connections of both the instances in hub PE to be up all the time [only one site in the spoke though]. This causes layer2 loop. Is there a fix for this? Diagram: CE_Switch1-----CPE-sw1-----| | HUB_PE------SPOKE_PE------CE_SW | CE_Switch2-----CPE-sw2-----| _______________________________________________ juniper-nsp mailing list [email protected] https://puck.nether.net/mailman/listinfo/juniper-nsp _______________________________________________ juniper-nsp mailing list [email protected] https://puck.nether.net/mailman/listinfo/juniper-nsp
