 | Copyright © 2008, Juniper Networks, Inc. All rights reserved. Trademark Notice. | |
In a VPLS configuration, E-series PE routers host VPLS edge (VE) devices, which are also referred to as VE routers or, simply, VEs. A VE device is a VPLS instance that services a particular customer site.
Figure 127depicts two PE routers: PE 1, which is the local router, and PE 2, which is the remote router located at the other side of the service provider core. Each PE router must have a VPLS instance—the VE device—configured for each VPLS domain in which it participates. Consequently, the sample topology comprises a total of four separate VPLS instances: instances vplsA and vplsB configured on PE 1, and instances vplsA and vplsB configured with matching route target values on PE 2.
Each VPLS instance configured on the router is associated with two types of interfaces, also known as ports. The CE-facing interface is an Ethernet or bridged Ethernet network interface that directly connects the PE router to each CE device. The VPLS virtual core interface, although not an actual physical interface, is automatically generated by the router for each VPLS instance and represents all of the MPLS tunnels from the router to the remote PE devices. The router encapsulates Ethernet frames from the CE device in an MPLS packet and then forwards the encapsulated frames to the service provider core through the provider (P) router. This encapsulation is identical to Martini encapsulation for Ethernet layer 2 services over MPLS.
Each PE router in the sample topology has a total of two network interfaces and two VPLS virtual core interfaces configured, one interface of each type per VPLS instance.
| Copyright © 2008, Juniper Networks, Inc. All rights reserved. Trademark Notice. | |