Log in to ask questions, share your expertise, or stay connected to content you value. Don’t have a login? Learn how to become a member.
MPLS technology is evolving, with more services being offered using MPLS connectivity. Junos OS features are also evolving to implement these services on Juniper Networks routers.
The most common MPLS connectivity services include:
VPLS provides a multipoint Ethernet service that emulates an Ethernet LAN. From the customer edge (CE) perspective, the service provider VPLS network operates like a private Ethernet broadcast domain.
A VPLS domain consists of a set of provider edge (PE) routers that acts as a single virtual Ethernet bridge for sites connected to those PE routers on the customer side. Pseudowire tunnels are created between those PE routers to aggregate traffic from one PE router to another. The PE routers exchange the MPLS labels used for the VPLS pseudowire, using either Label Distribution Protocol (LDP) forwarding equivalence classes (FECs), as described in RFC 4762, Virtual Private LAN Service (VPLS) Using Label Distribution Protocol (LDP) Signaling, or BGP, as described in RFC 4761, Virtual Private LAN Service (VPLS) Using BGP for Auto-Discovery and Signaling.
Junos OS Release 11.2 and later supports BGP autodiscovery for LDP VPLS using forwarding equivalence class (FEC) 129. As a workaround for older releases, you can manually provision each LDP PE router in an LDP mesh group by including the neighbor statement.
IGMP snooping is not supported on NG-VPLS when point-to-multipoint is in the core.
To ramp up on VPLS in Junos OS, click Layer 2 VPNs and VPLS Feature Guide.
This article provides answers to the most common questions about VPLS configurations on Juniper Networks MX Series routers.