 | Copyright © 2008, Juniper Networks, Inc. All rights reserved. Trademark Notice. | |
Typically, a VPLS domain is associated with customers who want to use Ethernet-based layer 2 VPNs to connect geographically dispersed sites in their organization across an MPLS-based service provider core, also known as an MPLS backbone. Each VPLS domain consists of the set of PE routers running the corresponding VPLS instance that participates in that domain. In BGP-signaled VPLS, a VPLS domain is identified by the route target extended community, similarly to how a layer3 VPN domain is identified in layer 3VPNs.
Figure 127depicts two VPLS domains: VPLS A and VPLS B. The VPLS A domain connects Customer A’s Boston and Chicago offices, and consists of provider edge routers PE 1 and PE 2, each of which runs a VPLS instance named vplsA. Similarly, the VPLS B domain connects Customer B’s Boston and Chicago offices, and consists of provider edge routers PE 1 and PE 2, each of which also runs a VPLS instance named vplsB.
| Copyright © 2008, Juniper Networks, Inc. All rights reserved. Trademark Notice. | |