Training PE-7750 ALU

Services

Services
1. Services Overview
2. Services Architecture 3. Layer 2 Service: VLL (Epipe) 4. Layer 2 Service: VPLS 5. Layer 3 Service: IES 6. Layer 3 Service: VPRN 7. Quy hoch mt s tham s

Services Overview

Services Overview
VN2 Services Internet Enhanced Service (IES/HSI) Layer 2 VPN services (VPLS & VLL)
Virtual Leased Line Services (VLL) Virtual Private LAN Service (VPLS)

Layer 3 IP-VPN services: Virtual Private Routed Network Service (VPRN) Voice over IP (VoIP) Multicast Video services (e.g. IPTV, Video Conferencing) Unicast Video services (e.g. Video on Demand) PE-7750 Services
VPLS, VLL, VPRN, IES, MyTV

Services Overview
Each Service is uniquely identified by a service ID with a service area. The 7750SR service model uses logical service entities to construct a service. Some benefits of the of the Alcatel-Lucent Service-centric model are: Many services can be bound to a single customer. Many services can be bound to a single tunnel. Tunnel configurations are independent of the services they carry. Changes are made to a single logical entity rather than multiple ports on multiple devices. It is easier to change one tunnel rather than several services. QoS policies, filter policies and accounting policies are applied to each service instead of correlating parameters and statistics from ports to customers and services.

Services Overview (Contd)

The 7750SR offers the following types of subscriber services:
Virtual Leased Line Services (VLL):
Etherpipe (Epipe) ATM VLL (Apipe) Frame Relay VLL (Fpipe) IP Pipe (Ipipe)

Virtual Private LAN Service (VPLS) Internet Enhanced Service (IES) Virtual Private Routed Network Service (VPRN)

7 | Presentation Title | Month

7750SR Service Definition Requirements

Customer ID:
Assigned when the customer account is created. To provision a service a customer ID must be associated with the service at the time of service creation.

Service Access Point (SAP):

Each subscriber service type is configured with at least one SAP. A SAP identifies the customer interface point for a service.

Service Distribution Point (SDP):

An SDP acts as a logical way to direct traffic from one 7750SR to another through a uni-directional (one-way) service tunnel. The SDP terminates at the far-end 7750SR which directs packets to the correct service egress SAP(s) on that device.

8 | Presentation Title | Month

Services Architecture

Service Architecture
MPLS, GRE or Other Tunnel Supporting Martini Type Service Encapsulations. Generally, Tunnels are Considered to be Unidirectional.

SDP (Service Distribution Point) Binds Multiple Services to a Tunnel.

Egress and Ingress VC Label Provisioned or Dynamically Assigned, Uniquely Identifies the Service to the Tunnels Far End.

SAP (Service Access Point) Customer point of access

7x50-A
SAP

VC-Label

SDP

SDP

VC-Label

7x50-B
SAP

Service-G

VC-Label Demux

VC-Label Demux

Service-G

SAP Encapsulation Types

Null - supports a single service on a port.

SAP Encapsulation Types

Ethernet Encapsulation

Dot1q (802.1q) supports multiple services for a single customer or multiple services for multiple customers. Q-in-Q provides a way to differentiate customer services based on Q tags.

Network ports

NULL Dot1Q: Service is delimited by VLAN tag

Access ports

QinQ: Service is delimited by two VLAN tags (QinQ)

Service Access Points (SAP) - Configuration

SAP with no encapsulation
*A:P1> configure port 1/1/1 *A:P1>config>port# info ----------------------------ethernet mode access encap-type null exit no shutdown ----------------------------*A:P1# show service sap-using [sap <id>]

SAP with dot1q encapsulation

*A:P1> configure port 1/1/1 *A:P1>config>port# info ----------------------------ethernet mode access encap-type dot1q exit no shutdown -----------------------------

SAP with QinQ encapsulation

*A:P1> configure port 1/1/1 *A:P1>config>port# info ----------------------------ethernet mode access encap-type qinq exit no shutdown -----------------------------

Service Distribution Point (SDP)

When a SDP is bound to a service, it is bound as either a spoke SDP or mesh SDP. The type of SDP indicates how flooded traffic is transmitted. Spoke SDP: Treated as the equivalent of a traditional bridge port where flooded traffic received on the spoke SDP is replicated on all other ports (other spoke and mesh SDPs or SAPs) and not transmitted on the port it was received. Mesh SDP: Treated as a single bridge port for flooded traffic where flooded traffic received on any mesh SDP on the service is replicated to other ports (spoke SDPs and SAPs) and not transmitted on any mesh SDPs.

SDP Encapsulation Types

The Alcatel-Lucent 7750SR service model uses encapsulation tunnels through the core to interconnect SR routers. An SDP is a logical way of referencing the entrance to an encapsulation tunnel. Encapsulations supported:
Generic Routing Encapsulation (GRE) RSVP signaled, loose or strict hop non-reserved MPLS LSP RSVP-TE signaled, bandwidth reserved MPLS LSP LDP signaled

Service Distribution points - Configuration

MPLS based, RSVP
*A:P1# configure service sdp 12 mpls create *A:P1>config>service>sdp# info far-end 10.1.1.2 lsp "l-1-2" keep-alive shutdown exit no shutdown

GRE based
*A:P1# configure service sdp 12 gre create *A:P1>config>service>sdp# info far-end 10.1.1.2 keep-alive shutdown exit no shutdown

MPLS based, LDP

*A:P1# configure service sdp 12 mpls create *A:P1>config>service>sdp# info far-end 10.1.1.2 ldp keep-alive shutdown exit no shutdown

spoke-sdp vs mesh-sdp

Layer 2 Service: VLL (Epipe)

What is MPLS L2 VPN

MPLS L3 VPN
Tunnel Label Inner Label Layer3 Header Data

MPLS L2 VPN

Tunnel Label

VC Label

Layer2 Header

Data

MPLS L2 VPN Characters

The service provider use MPLS network to provide Layer 2 services to the customer. It seems that CEs are connected directly or connected through layer2 switch networks, such as ATM, FR, Ethernet switch networks. Routing occurs between CE routers

E-Pipe Service Types

Local Epipe Distributed Epipe

SAP SDP SAP SAP SDP SAP

PW-Switching Epipe

SDP

SDP

Epipe Service
customer service
port 1/1/4 dot1q SAP SDP

customer
SWAP of MPLS Outer label
physical network link

service SDP SA P packet

packet

VID

Private wire service

packet

VC-label

TLDP is used to signal VClabels MPLS Transport or Outer Tunnel (unidirectional)

packet

VC-label

packet
configure service epipe 2 customer 3 sap 1/1/4:36 spoke-sdp 12:2
configure service sdp 12 mpls create far-end 10.1.1.2
Two MPLS labels :

VC-label Inner-label

label Outer-label

Port-ID:VLAN-ID SDP-ID:VCID

configure service epipe 2 customer 3 sap 1/1/1 spoke-sdp 21:2 configure service sdp 21 mpls create far-end 10.1.1.1

Used by TLDP

Layer 2 Service: VPLS

Virtual Private LAN Service (VPLS)

Bridged multipoint Ethernet service (point to multipoint) From customers perspective it looks as if all sites are connected to single switched VLAN PE routers are inter-connected with MPLS LSP tunnels Per-Service VC labels negotiated using draft-martini (T-LDP) or provisioned MAC learning over tunnel & access ports Separate FIB per VPLS

PE B
LSP FullMesh

VPLS Service1 VPLS Service2

PE A
IP / MPLS Network

PE C

PE D

VPLS: Customer operation

CE A

CE B VPLS #1 10.10.1.x VPLS #2 20.20.2.x CE A

CE B

CE A

CE B

VPLS Service Types #1: Switch Inter-connect

Allows customers to connect Layer-2 switches into the VPLS service Service supports multiple MAC addresses per site
Small Office

Small Office
VB

VB

VPLS

L2 Switch

Service Provider Infrastructure

VB

Small Office

VPLS Service Types #2: Router Inter-connect

Most prevalent VPLS service type Customers can only connect routers into the VPLS service Routers provide clean service demarcation
Limits to one MAC address per site

Branch Office

Corporate HQ
VB

VB

VPLS

Router

Service Provider Infrastructure

VB

Branch Office

Working process of VPLS

Working process of VPLS

Member relationship discovery (control plane) PW creation and maintenance (control plane) Forwarding based on MAC addresses (data plane)

Working process of VPLS

Control Plane

Member discovery: It is the process to find all other PEs in the same VPLS. This can be implemented either through manual configuration or automatically by the use of some protocols. In the later case, it is called auto discovery. Signaling mechanism: It is the process to use the signaling protocol between the PEs of the same VPLS to establish, maintain and remove PW. use of the BGP or LDP to implement the control plane of VPLS, referred to as Kompella VPLS and Martini VPLS respectively.

Working process of VPLS

Data Plane

Encapsulation: When receiving Ethernet frames from CE, PE sends them to PSN after encapsulation. Forwarding: How to forward packets depends on the interface receiving the packets and the destination MAC addresses of the packets .

VC Label Signaling
Trong dch v VPLS, VC-label Signaling c s dng gia PEs
Mi PE khi to mt targeted LDP session ti far-end PEs Thng bo cho far-end PEs bit VC label no c s dng gi packets M-3 cho mi dch v PE-2
PE1->PE2: For Svc-id 101 UseVC-label pe2-1 PE2->PE1: For Svc-id 101 Use VC-label pe1-2 PE1->PE3: For Svc-id 101 Use VC-label pe3-1
M-1 pe3-1 PE-3 pe1-3 VB M-4 pe2-1 PE-1 VB pe1-2 pe3-2 VPLS pe2-3 VB

PE3->PE1: For Svc-id 101 Use VC-label pe1-3

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

VPLS Learning
M3
Packet Walkthrough for VPLS Service-id 101 1/1/2:0
VPLS Svc-id = 101 MAC M3 Location Local Mapping 1/1/2:0

PE 2

M1

1/1/1:100 PE 1 PE 3
VPLS Svc-id = 101

1/1/2:0

M4
MAC M3 Location Remote Mapping Tunnel to PE2

M2

1/1/1:200
Send a packet from M3 to M1

VPLS Svc-id = 101

MAC M3

Location Remote

Mapping Tunnel to PE2

- PE2 learns that M3 is reached on Port 1/1/2:0 - PE2 floods to PE1 with VC-label pe2-1 and PE3 with VC-label pe2-3 - PE1 learns from the VC-label pe2-1that M3 is behind PE2 - PE1 sends on Port 1/1/1:100 & 1/1/1:200

- M1 receives packet

- PE3 learns from the VC-label pe2-3that M3 is behind PE2 - PE3 sends on Port 1/1/2:0

VPLS Packet Forwarding

Packet Walkthrough for VPLS Service-id 101

M3
1/1/2:0 PE 2

VPLS Svc-id=101 MAC M3 M1 Location Local Remote Mapping 1/1/2:0 Tunnel to PE1

1/1/1:100

1/1/2:0 PE 3

M1

PE 1

M4

M2
VPLS Svc-id=101
MAC M3 M1

1/1/1:200
Reply with a packet from M1 to M3 - PE1 learns M1 is on Port 1/1/1:100 - PE1 knows that M3 is reachable via PE2 - PE1 sends to PE2 using VC-label pe1-2 - PE2 knows that M3 is reachable on Port 1/1/2:0 - M3 receives packet

Location Remote Local

Mapping Tunnel to PE2 1/1/1:100

Layer 3 Service: IES

Creating an IES Service

IES service data packets are not encapsulated:
no SDP required

7x50-A

5 4

Create Routes Apply Filters

SAP

Epipe / VPLS

SDP

SAP

IP interface

iES Service

Create the SAP

Create IP Interface

1 Create the Service

Layer 3 Service: VPRN

How does VPLS differ from BGP/MPLS L3 VPN?

BGP/MPLS L3 VPN
Limited to IP protocol only Routed solution Customers relinquish control of routing to the Service Provider IP addressing for each site on VPN must be coordinated with the Service Provider Service Provider must have first line technicians trained in complex routing issues No clear demarcation of functionality and responsibility between Customer & Service Provider results in customer care call even when the routing problem is within the customer network

VPLS
Multi-protocol solution Bridged solution Customers retain control of routing IP addressing is simpler (all sites are in a single subnet) and requires no interaction with the Service Provider Service Provider does not require that much personnel trained to deal with customer routing issues Clear demarcation of functionality and responsibility between Service Provider (Bridging) and Customer (Routing) results in easy troubleshooting of customer problems

Quy hoch

Quy hoch
Mt s tham s khai bo trong PE c quy hoch - Service id v VC id - SDP id - Tn Interface

SDP ID
Quy hoch SDP ID SDP IDs cho cc node trong VTN1, cc thng s ny c quy hoch thng nht trn ton b cc PE: Cc node trong VTN1 : 1001 1999 T VTN1 VTN2 : 2001 2999 T VTN1 VTN3 : 3001 3999 <region><octet cui cng ca PE router id>

SDP ID
SDP ID 1 ch s <region> 3 ch s <octet cui cng ca PE router id>

STT

M t

-<region>

- SDP gia cc PE trong cng VTN1 th c gi tr bng 1 - SDP t PE thuc VTN1 n PE thuc VTN2 c gi tr bng 2 - SDP t PE thuc VTN1 n PE thuc VTN3 c gi tr bng 3

-<octet cui cng ca PE router id>

- L gi tr ca octet cui cng ca PE router ID

SDP ID

Service id v VC id
Khuyn ngh nn s dng Service id v vc id cng gi tr <Service Type><Customer id><Channel type><Channel group>
Service id / VC id 1 ch s 3 ch s 1 ch s 1 ch s

Service Type

Customer id

Channel type

Channel group

Service id v VC id
STT 1 <Service Type> M t y l tham s nhn dng loi dch v Vi dch v VLL c gi tr bng 1 Vi dch v VPLS c gi tr bng 2 Vi dch v VPRN c gi tr bng 3 Vi dch v IES c gi tr bng 4

2 3

<Customer id> <Channel type> <Channel group>

- L mt id nhn dng khch hng, tun theo nhn dng khch hng ca cc dch v trong VN1. - Vi knh ni tnh k VTN c gi tr bng 0 - Vi knh ni tnh k VNPT tnh thnh c gi tr bng 2 - Vi knh lin tnh c gi tr bng 4 - L nhn dng nhm knh ca khch hng khi khch hng cho nhiu nhm knh trong mt loi dch v

Tn Interface
<a-end site>:<b-end site>:<number>

Interface Naming 8 k t 8 k t 2 ch s

<a-end site>

<b-end site>

<number>

STT

M t

1
2

<a-end>
<b-end site>

Tn ca node ti im u ca link kt ni
Tn ca node ti im cui ca link kt ni

<number>

2 digit tip theo i din cho s link kt ni gia 2 node