TOS36013 08 04 VPLS Configuration

Do not delete this graphic elements in here:
83
Section 8
Basic Services
Module 3
VPLS Configuration
TOS36013-0804 Issue 1.0
5620 SAM
5620 SAM (Service Aware Manager) R7.0 Operator
TOS36010 Issue 1.0
All Rights Reserved Alcatel-Lucent 2009

TOS36013-0804 Issue 1.0
Section 8 Module 3 Page 1
Document History
Switch to notes view!
832
Basic Services VPLS Configuration

5620 SAM 5620 SAM (Service Aware Manager) R7.0 Operator
This page is left blank intentionally
Document History
Edition
Date
Author
Remarks
01
2009-08-14
GARCIA LOZANO, Ren
First edition

TOS36013-0804 Issue 1.0
Module Objectives
Upon completion of this module, you will be able to:

Describe the characteristics of a VPLS service
List the steps in configuring a VPLS service
833


TOS36013-0804 Issue 1.0
How is a VPLS provided over MPLS?
Bridging capable PE routers
connected with a full mesh of MPLS LSP tunnels
Per-Service VC labels
negotiated using draft-Martini

PE B
Unknown/broadcast
traffic replicated in a service domain
VPLS
VPLS
Service
Service
MAC learning
over tunnel & access ports

separate FIB per VPLS
PE A
PE C
IP / MPLS
Network
LSP FullMesh
PE D
834

For each VPN at each site, a Customer Edge (CE) device connects to the Provider Edge (PE) router via a pointto-point access connection.
Ethernet serves as the framing technology between the CE device and the PE router in the providers network.
Frames can include IEEE 802.1Q Ethernet VLAN tags, which allow customers to segment their networks and
assign quality of service priorities to LAN traffic. VPLS also supports QinQ encapsulation, where a second
VLAN tag is added as a service delimiter. From the customers perspective, the entire VPN looks like a single
Ethernet LAN, with the PE acting as a bridge that switches frames on the basis of their Layer-2 destination
MAC addresses.
On the providers side, however, PEs are interconnected with Generic Routing Encapsulation (GRE) and/or
Multiprotocol Label Switching (MPLS) tunnels. If PEs are connected using GRE tunnels traffic is encapsulated
and routed through the core network using standard IP frame formats and addressing. If PEs are connected
using MPLS tunnels traffic is encapsulated in an MPLS frame and transmitted using MPLS labels. MPLS routes
can be signaled using RSVP-TE or LDP.

TOS36013-0804 Issue 1.0
VPLS: Customer View
All locations appear to be on the same Ethernet LAN
Entire provider network appears to be a Layer 2 switch
CE-PE interface
Simple Ethernet interface

Removes L2 protocol conversion
between LAN and WAN
No additional training required on
WAN technologies such as FR
VLAN A
L2 switch
CE
VPLS
Service
CE
CE
835


TOS36013-0804 Issue 1.0
VPLS: Customer Operation

Customers maintain complete control over routing

Adding new sites simplified: no re-configuration at existing
sites
CE A
CE B
CE B
VPLS #1
10.10.1.
x
VPLS #2
20.20.2.
x
CE A
836
CE A
CE B

Customers maintain complete control over their routing (unlike with VPRN).
This clear demarcation of functionality between service provider and customer makes troubleshooting easier
Adding a new site requires no configuration of the service providers equipment or the customer equipment at
existing sites

TOS36013-0804 Issue 1.0
VPLS: Service Provider View

Clear demarcation of functionality

between service provider and
customer networks
Service provider does not have to
deal with customer routing issues
Separate Ingress/Egress Traffic
Parameters
Detailed billing and accounting
Ethernet
IP / MPLS
Network
Access
Network
7750
CE
IP / MPLS
Network
837
PE


TOS36013-0804 Issue 1.0
VPLS - VC Label
VC-label Signaling between PEs per VPLS service

instance
Each PE initiates a targeted LDP session to the farend System IP address
Tells far-end what VC label to use when sending
packets for each service
PE-2
M-3
pe2-1
PE-1
pe1-2
PE1->PE2: For Svc-id 101 UseVC-label pe2-1

PE2->PE1: For Svc-id 101 Use VC-label pe1-2
pe3-2
M-1
VPLS
pe2-3
pe3-1

PE-3
pe1-3
M-4

838

Customer packets are transported either inside an IP packet (GRE) or inside an MPLS packet.
The packet carries an inner (VC) label that identifies the service the packet belongs to. This label is
sometimes referred to as the Martini label.
When a packet arrives at the destination, the outer IP address or MPLS label is stripped off. At this point the
inner label is examined to determine which service the packet belongs to.
After determining which service the packet belongs to, the customers Ethernet packet is examined and its
MAC address is looked up in a table on the PE to determine which SAP the packet should go to.
VC labels can be assigned manually or automatically using targeted LDP (TLDP). The TLDP protocol is used to
dynamically negotiate VC labels between PEs. This method is not error prone and scales much better then
manually assigning labels.

TOS36013-0804 Issue 1.0
Spoke and Mesh SDPs
PE-A
SDP
Mesh
SDP
Spoke SDP
replicated on all other ports

(spoke and mesh SDPs and SAPs)
not replicated on the port it was
received on
Service G
SDP
Spoke
SAP
SDP
PE-A
SDP
Mesh
Mesh SDP
SDP
Service G
SDP
Spoke
SAP
SDP
Spoke
839
Flooded traffic received on

spoke SDP is:
Flooded traffic received on mesh

SDP on the
Service is:
replicated on spoke SDPs and SAPs
not transmitted on any mesh SDPs

An SDP is a logical method of advertising and connecting to an encapsulation tunnel and must be bound to a
service before the service can be used. The method of binding an SDP to a service, spoke or mesh,
determines how flooded traffic is transmitted.
Spoke SDP
A spoke SDP treats flooded traffic like a traditional bridged port. Flooded traffic received on a spoke SDP is
replicated on all other ports (other spoke and mesh SDPs or SAPs) but not the port on which it was received.
Mesh SDP
Mesh SDPs bound to the same service are treated like a single bridge port. Flooded traffic received on a mesh
SDP on the service is replicated to other ports (spoke SDPs and SAPs) but are not transmitted to other mesh
SDPs.

TOS36013-0804 Issue 1.0
Configuration Workflow - VPLS

Create
Create aa
Customer
Customer
Create
Create
Service
Service

Create
Create SAPs
SAPs

Create
Create SDP
SDP
Bindings
Bindings
Manage
Manage Service
Service
8 3 10

Create a Customer
Specify Service Type

Specify Service Sites
Configure L2 Interfaces
Configure Access ports
Specify MTU
Assign Encapsulation value
Select a Service Tunnel
Assign VC Label
View Service Topology Properties

Properties

The workflow illustrated above describes the steps for a network administrator or operator to configure a
Virtual Private LAN Service.
Customer - must be assigned to the service. Though the service can have only one Customer,
that customer may be assigned to more than one service.

Create Service - specify the service type (VPLS) and add the appropriate service sites.
Create Service Access Points as discussed, a SAP is a Layer 2 interface configured on a physical port.
Configure the port Mode for Access, define the Encapsulation Type, specify the Encapsulation ID (as
required) and specify the service MTU size.
Create SDP Bindings Create the Spoke SDP or Mesh SDP Bindings by associating the service to service
tunnels. The VC Label may be assigned manually, by the network administrator or operator, or
automatically, by the 5620 SAM.
Manage Service through the Properties window and/ or by using the Service Topology View.

TOS36013-0804 Issue 1.0
Create a Customer
1.Select ManageCustomers
2.Select Create
3.Define the
Customer
Attributes
8 3 11

A service it must be associated with a customer. The customer may be associated with multiple services yet
there can only be one customer per service.
To create a customer:
Select Manage Customers from the Main menu
Click on the Create button
Under the General tab of the Customer Create window, complete the appropriate customer information
then click OK.
Verify that the customer has been created by selecting Manage Customers from the Main menu and click
the Search button. A list of customers, based upon the configured filter, will appear. Verify the customer
appears in the list.

TOS36013-0804 Issue 1.0
Configure Access Port
8 3 12

As discussed, a service requires a port facing the customer edge to be configured for Access and an
Encapsulation type specified. To configure a port:
Navigate to the Equipment view in the Navigation Tree
Expand the tree and select the appropriate port or ports. It is possible to configure multiple ports at the
same time by through the Shift Click or Ctrl Click method.
Right-click and select Properties from the contextual menu
From the Mode drop-down menu, select Access
From the Encapsulation Type drop-down menu, select the appropriate encapsulation type
Set the port MTU. Remember that the port MTU must be set to a value set to support the largest service
MTU to be supported on that port.
Select OK to complete the configuration.

TOS36013-0804 Issue 1.0
Create a VPLS
2. Choose Select
1. Select Create Service VPLS
3.Select the Customer

Service Name
Description (optional)
Automatic SDP Binding Creation (optional)
8 3 13

To create a service, select the service type and assign the managed devices upon which the service will
terminate, referred to as the Service Sites.
To create a VPLS:
Select Create Service VPLS from the Main Menu
Click the Select button in the Customer block
Select a customer from the list that appears and click the OK button
Complete the remaining parameters, as required. Though optional, providing a service name and relevant
description will enable the network administrator or operator to find the service using the Search filter.
Click Apply
Automatic SDP Binding Creation This option enables the network administrator or operator to leave the
creation of SDP bindings to the 5620 SAM instead of having to manually assign service tunnels (discussed
later in this module).

TOS36013-0804 Issue 1.0
Create a VPLS
1. Components VPLS Create Site
2. Select Sites
3. Confirm Sites
8 3 14

Having clicked the Apply button, the configuration window remains open and the changes are saved in the
5620 SAM database. However, service components (Service Sites, Access Interfaces and SDP Bindings) have
yet to be configured for the service to be commissioned.
To configure service sites:
Navigate to the Components window of the service configuration form
Select VPLS and right-click
Select Create Site and select the sites to participate in the VPLS service from the list. This may be done
individually or by selecting multiple entries at once.
Click the OK button
Confirm the sites have been added in the Components window
It is important to remember that, even though they appear in the configuration window, the changes will not
be sent to the managed devices and saved to the 5620 SAM database until the OK or Apply button at the
bottom of the window (referred to as the Containing Window) is clicked.

TOS36013-0804 Issue 1.0
Create SAPs
1. Right-click Create L2 access Interface
2. Port tab click on Select
3. Search OK
8 3 15

Service Access Points are virtual interfaces to provide customer access to the service providers network. An
SAP consists of: a physical port configured to support Access points; an encapsulation type; and, an
encapsulation ID value unique to the port.
To create a SAP:
Navigate to the Component window for the service
Navigate to the Access Interface of the appropriate Site
Right-click and select Create L2 Access Interface
Click the Port tab and then click the Select button
Click the Search button. All Access ports on the managed device will appear in the list. Select the
appropriate port and click the OK button

TOS36013-0804 Issue 1.0
Create SAPs
1. Assign Encapsulation Value
(as required)
2. Confirm Access Interface
8 3 16

The SAP also requires an encapsulation ID value that is unique to the port upon which it is being created. To
assign an encapsulation ID:
Select the Port tab
Assign the Outer Encapsulation Value and Inner Encapsulation Value, as required
Click the OK or Apply button
Confirm that the SAP has been configured. To so so:
Expand the Access Interface list under the Components window
Confirm the SAP is listed and verify its status.
Repeat this process for the remaining Access Interfaces to participate in the VPLS.

TOS36013-0804 Issue 1.0
Create SDP Bindings

1. Create Mesh SDP Binding
2. Select Termination Site (mandatory)
1. Create Spoke SDP Binding
8 3 17

Service Distribution Paths are required when Service Access Points are located on separate network devices
(distributed service). An SDP is created when a service is associated (bound) to a Service Tunnel.
The network administrator or operator has the option of either manually or automatically creating SDP
bindings. To manually create the SDP Bindings:
Expand the Site listing under the Components window for the service
Navigate to either Mesh SDP Bindings or Spoke SDP Bindings
Right-click and select Create Mesh SDP Bindings or Spoke SDP Bindings, as required based upon network
requirements.
Click the Select button in the Termination Site section of the new window
Select the terminating Site ID from the list and click OK.

TOS36013-0804 Issue 1.0
Create SDP Bindings

1. Manual Tunnel Assignment
2. Select tunnel OK
1. Automatic Tunnel Select
8 3 18
3. Confirm SDP Configuration

With the Terminating Site identified, the network administrator or operator can assign a Service Tunnel. To
manually assign a Service Tunnel:
Click the Select button in the Tunnel section of the configuration window
Select the appropriate Service Tunnel from the list
Click the OK button
SDP Binding configuration is verified by expanding the appropriate Site listing under the Components
window.
Repeat this process until the remaining SDP Bindings required to support the VPLS have been configured.
Click the OK or Apply at the bottom of the containing window to save the configuration to the 5620 SAM and
send the configuration changes to the managed nodes.
Automatic SDP Binding Creation is possible if the network administrator or operator has checked this option
under the General tab of the configuration window (already discussed). When selected, it is possible to
specify the Tunnel Transport protocol from the drop-down menu in the configuration form, as shown
above.

TOS36013-0804 Issue 1.0
Manage VPLS Service
8 3 19

Once created, the network administrator or operator is able to view and/ or manage the VPLS service from
the 5620 SAM GUI.
To manage or view the VPLS service configuration:
Select Manage Services from the Main Menu
Set the Search filter parameters, as required
Click on the Search button
Select the service from the list.
The configuration window appears on the screen. Service configuration information is provided under the
appropriate tabs listed at the top of the window. Parameters in drop-down menus or in the white blocks
may be changed. Changes to an existing service will prompt a warning to which the network administrator
or operator will be required to acknowledge before changes will be affected.
Viewing a graphical representation of the service is possible by clicking on the Topology View button of either
window. An example is provided on the next page.

TOS36013-0804 Issue 1.0
View Service Topology
Service Type
Service ID: Site ID
8 3 20
Service Access Point

SDP Bindings
Port ID:Outer Encap: Inner Encap

The Service Topology View displays the service components configuration and status information at a glance.
Information available includes:
Service Type indicated within the Site icon (VPLS, in this case). The Service ID and Site ID are posted
below the icon.
Service Access Point the square with two arrows contained within the icon. The Port ID and Outer and
Inner Encapsulation ID are posted below the icon.
SDP Bindings arrows indicate direction of the bindings between service sites.
Select any component in the Topology View.
Right-clicking provides a contextual menu for the selected item.

TOS36013-0804 Issue 1.0
End of Module
VPLS Configuration
8 3 21


TOS36013-0804 Issue 1.0
Last Blank Page

Switch to notes view!
8 3 22
This page is left blank intentionally

TOS36013-0804 Issue 1.0

TOS36013 08 04 VPLS Configuration

Caricato da

Informazioni sul documento

Copyright

Formati disponibili

Condividi questo documento

Condividi o incorpora il documento

Opzioni di condivisione

Hai trovato utile questo documento?

Questo contenuto è inappropriato?

Copyright:

Formati disponibili

TOS36013 08 04 VPLS Configuration

Caricato da

Copyright:

Formati disponibili

Do not delete this graphic elements in here:

All Rights Reserved Alcatel-Lucent 2009

All Rights Reserved Alcatel-Lucent 2009

All Rights Reserved Alcatel-Lucent 2009

Basic Services VPLS Configuration

This page is left blank intentionally

GARCIA LOZANO, Ren

All Rights Reserved Alcatel-Lucent 2009

Upon completion of this module, you will be able to:

All Rights Reserved Alcatel-Lucent 2009

Basic Services VPLS Configuration

All Rights Reserved Alcatel-Lucent 2009

How is a VPLS provided over MPLS?

Bridging capable PE routers

connected with a full mesh of MPLS LSP tunnels

negotiated using draft-Martini

traffic replicated in a service domain

over tunnel & access ports

All Rights Reserved Alcatel-Lucent 2009

Basic Services VPLS Configuration

All Rights Reserved Alcatel-Lucent 2009

VPLS: Customer View

All locations appear to be on the same Ethernet LAN

Entire provider network appears to be a Layer 2 switch

Simple Ethernet interface

All Rights Reserved Alcatel-Lucent 2009

Basic Services VPLS Configuration

All Rights Reserved Alcatel-Lucent 2009

VPLS: Customer Operation

Customers maintain complete control over routing

All Rights Reserved Alcatel-Lucent 2009

Basic Services VPLS Configuration

All Rights Reserved Alcatel-Lucent 2009

VPLS: Service Provider View

Clear demarcation of functionality

All Rights Reserved Alcatel-Lucent 2009

Basic Services VPLS Configuration

All Rights Reserved Alcatel-Lucent 2009

VC-label Signaling between PEs per VPLS service

PE1->PE2: For Svc-id 101 UseVC-label pe2-1

PE1->PE3: For Svc-id 101 Use VC-label pe3-1

PE3->PE2: For Svc-id 101 Use VC-label pe2-3

PE2->PE3: For Svc-id 101 Use VC-label pe3-2

All Rights Reserved Alcatel-Lucent 2009

Basic Services VPLS Configuration

All Rights Reserved Alcatel-Lucent 2009

Spoke and Mesh SDPs

replicated on all other ports

Flooded traffic received on

Flooded traffic received on mesh

All Rights Reserved Alcatel-Lucent 2009

Basic Services VPLS Configuration

All Rights Reserved Alcatel-Lucent 2009

Configuration Workflow - VPLS

Specify Service Type

View Service Topology Properties

Basic Services VPLS Configuration

that customer may be assigned to more than one service.

All Rights Reserved Alcatel-Lucent 2009

All Rights Reserved Alcatel-Lucent 2009

Basic Services VPLS Configuration

All Rights Reserved Alcatel-Lucent 2009

Configure Access Port

All Rights Reserved Alcatel-Lucent 2009