> Chris, > > Thanks, I just tried it and this works...guess I was making it more difficult > that it needed to be. I haven't tested spanning tree through it or other > layer2 control protocols but you are thinking they should pass through just > like and l2vpn? > > Thanks again, > > Kevin
Correct. They all pass into the VPLS instance "unmolested" as I like to call it. (RSTP, CDP, PVST+ etc..) FWIW - I use this on SRX as MPLS-capable CPE for our VPLS service. (via targeted LDP L2CKT to the BGP VPLS on the "main PE"). This is a standard H-VPLS scenario, with a primary and a backup PE declared on the CPE). ( Naturally works on the native MX port as well, even without invoking an H-VPLS topology). For sakes of completeness -- I use LDP<>BGP Internetworking in PE's VPLS to "stitch' the CPE's L2CKT into the VPLS instance directly, without using lt-* interfaces. Scales well & provides PE redundancy. Easily enough done (check the Juniper JMV course on VPLS -- this is covered in detail on the later chapters on how to do both LDP and BGP-VPLS in the same instance, and do it reasonably effectively via no-tunnel-services). Anyways - doing the interface that way passes everything I can think of; sans LACP, but who the heck runs LACP into a multipoint VPLS anyways? =) (thats more of an E-LINE/P-to-P TLS service) Glad it worked out for you. - Ck. _______________________________________________ juniper-nsp mailing list [email protected] https://puck.nether.net/mailman/listinfo/juniper-nsp
