Alcatel-Lucent 6850-48 参照ガイド
OmniSwitch CLI Reference Guide
September 2009
page 26-1
26 Virtual Private LAN
Service (VPLS) Commands
A Virtual Private LAN Service (VPLS) is a Virtual Private Network (VPN) technology that allows any-to-
any (multipoint) connectivity. The provider network emulates a LAN by connecting all the remote
customer sites at the edge of the provider network to a single bridged LAN. A full mesh of pseudo-wires
(PW) needs to be established to form a VPLS.
any (multipoint) connectivity. The provider network emulates a LAN by connecting all the remote
customer sites at the edge of the provider network to a single bridged LAN. A full mesh of pseudo-wires
(PW) needs to be established to form a VPLS.
A VPLS-capable network consists of Customer Edges (CE), Provider Edges (PE), and a core MPLS
network. The CE device is a router or switch located at the customer's premises and is connected to the PE
via an Attachment Circuit (AC). In the case of VPLS, it is assumed that Ethernet is the layer 2 protocol
used between the CE and the PE.
network. The CE device is a router or switch located at the customer's premises and is connected to the PE
via an Attachment Circuit (AC). In the case of VPLS, it is assumed that Ethernet is the layer 2 protocol
used between the CE and the PE.
The PE device is where the services originate and terminate and where all the necessary tunnels are set up
to connect to all the other PEs. As VPLS is an Ethernet Layer 2 service, the PE must be capable of Media
Access Control (MAC) learning, bridging, and replication on a per-VPLS basis.
to connect to all the other PEs. As VPLS is an Ethernet Layer 2 service, the PE must be capable of Media
Access Control (MAC) learning, bridging, and replication on a per-VPLS basis.
The IP/MPLS core network interconnects the PEs but does not participate in the VPN functionality. Traf-
fic is simply switched based on the MPLS labels.
fic is simply switched based on the MPLS labels.
This implementation of VPLS makes use of a service-based architecture that provides the following logi-
cal entities that are required to provision a service:
cal entities that are required to provision a service:
• Customers (subscribers). An account is created for each customer and assigned an ID. The customer
ID is required and associated with the service at the time the service is created.
• Service Access Points (SAPs). Each subscriber service type is configured with at least one SAP. A
SAP identifies the point at which customer traffic enters the service.
• Service Distribution Points (SDPs). A SDP provides a logical point at which customer traffic is
directed from one PE to another PE through a one-way service tunnel.
A distributed service consists of at least one SAP on a local node, one SAP on a remote node, and an SDP
binding the service to the service tunnel.
binding the service to the service tunnel.
This chapter provides information about the Command Line Interface (CLI) commands used to configure
the above entities required to provision a service.
the above entities required to provision a service.
MIB information for the LDP commands is as follows:
Filename: AlcatelIND1ServiceMgr.MIB
Module: Alcatel-IND1-SERVICE-MGR-MIB
Module: Alcatel-IND1-SERVICE-MGR-MIB
Filename: TIMETRA-SDP.MIB_mib
Module: TIMETRA-SDP-MIB
Module: TIMETRA-SDP-MIB