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.
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
Question How can I prevent the receipt of hub routes on a directly-connected customer premises equipment (CPE) spoke interface in a hub provider edge router?
Junos OS features are also evolving to implement these services on Juniper Networks routers. The most common MPLS connectivity services include: Virtual Private LAN Service (VPLS) Layer 3 virtual private networks (VPNs) Layer 2 circuits and Layer 2 VPNs Layer 2 circuits and Layer 2 VPNs are point-to-point Layer 2 services built over the service provider’s MPLS transport
The PE router advertises a separate label block for each of these site IDs to the remote PE routers. The label block associated with the lowest site ID number is selected to build pseudowires between the local PE router and the remote PE routers. You can use the show vpls connections command to verify that the pseudowire that has "Up" status between two PE routers is associated with the lowest site IDs on both PE routers. Router PE1 derives its labels from the label block associated with Site 2, which comes through Router PE2
In this example, first assume that Router PE2 is a Juniper Networks MX Series 3D Universal Edge Router. The packets from Router CE1 for VLAN700 are flooded from Router PE2 only on the ports connected to VLAN700. This behavior is VPLS qualified learning. MX Series routers perform qualified lookups and qualified learning
no search term matches found in comments.
Question What is the behavior of a virtual tunnel interface in different services routing instances? Answer If you configure a virtual tunnel (vt) interface on the egress PE router and that router is also a transit router for the point-to-multipoint LSP, the penultimate hop router sends just one copy of each packet over the link to the egress PE router
Question Is indirect next hop supported for VPLS in MX Series routers with I-chip-based DPCs?...With this constraint removed, you can configure VPLS with indirect next hops and the routing protocol process (rpd) will ignore the VPLS configuration
Answer You can have up to 14 mesh groups per VPLS on MX Series routers. For example, for a given VPLS instance, if you need LDP-BGP interworking, there must be one mesh group for every LDP-VPLS cloud that is connected to the BGP-VPLS cloud, at the interworking router
Question What is the maximum number of VPLS instances supported, and the maximum number of sites supported per VPLS instance, on MX Series routers? Answer The maximum number of VPLS instances supported on MX Series routers is 8,000. This number is derived as follows: The logical interface limit on an MX Series router is 64,000. In BGP VPLS, the default label block size is eight, which provides eight pseudowires per VPLS