Figure 68: Basic H-Vpls With One Mtu And Two Pe-R Devices - Juniper ACX1000 Configuration Manual

Junos os; acx series universal access router

Hide thumbs Also See for ACX1000:

User manual (216 pages)

Hardware manual (204 pages)

Quick start manual (27 pages)

Table of Contents

H-VPLS uses LDP-based VPLS to signal and establish pseudowires. LDP-based VPLS

is defined in RFC 4762, Virtual Private LAN Service (VPLS) Using Label Distribution Protocol

(LDP) Signaling. RFC 4762 also defines a hierarchical mode of operation for LDP VPLS

called H-VPLS.

VPLS and H-VPLS are different with respect to scaling. VPLS requires a full mesh of

tunnel label-switched paths (LSPs) among all of the provider edge (PE) routers that

participate in the VPLS service. For each VPLS service, n*(n-1)/2 pseudowires must be

set up between the PE routers. In contrast, H-VPLS partitions the network into several

edge domains that are interconnected using an MPLS core. Each edge device only needs

to learn of one local PE device and therefore needs less routing table support. This has

the potential to allow service providers to use relatively less costly devices (such as EX

Series switches) at the customer edge.

As alternatives to H-VPLS, Juniper Networks offers other ways to

address VPLS scalability. For more information, see

Demystifying H-VPLS

H-VPLS defines two roles or functionalities:

PE-r—PE device that runs VPLS with other PE-r devices, but which also has pseudowires

(it can be based on QinQ access) with another device called a multi-tenant unit (MTU),

which provides the access layer.

MTU—PE device that represents the access layer on the H-VPLS architecture and

establishes pseudowires to one or more PE-r devices through which VPLS traffic is

Figure 68 on page 1311

shows the topology used in this example.