Service_20110913

Training PE-7750 ALU

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 hoạch một số tham số

Services

1 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.

7 | Presentation Title | Month 2006

Services Overview (Cont’d)

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)

8 | Presentation Title | Month 2006

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.

2 Services 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.

7x50-A

SAP

Service-G

7x50-B

Service-G

SAP

VC-Label

VC-LabelDemux

VC-LabelDemux

SAP (Service Access Point)Customer point of access

SDP VC-Label

SDP

Service Architecture

SAP Encapsulation Types

SAP Encapsulation

Types

Ethernet Encapsulation

Null - supports a single service on a port.

Dot1q (802.1q) – supports multiple services for a single customer or multiple services for multiple customers.

Q-in-Q – provides a way to differentiate customerservices based on Q tags.

NULL

Dot1Q: Service is delimited by VLAN tag

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

Netw

ork

ports

Access p

orts

Service Access Points (SAP) - Configuration

*A:P1# show service sap-using [sap <id>]*A:P1# show service sap-using [sap <id>]*A:P1> configure port 1/1/1 *A:P1>config>port# info -----------------------------

ethernet mode accessencap-type null

exit no shutdown-----------------------------

*A:P1> configure port 1/1/1 *A:P1>config>port# info -----------------------------

ethernet mode accessencap-type null

exit no shutdown-----------------------------


ethernet mode accessencap-type dot1q

exit no shutdown-----------------------------


ethernet mode accessencap-type dot1q

exit no shutdown-----------------------------


ethernet mode accessencap-type qinq

exit no shutdown-----------------------------


ethernet mode accessencap-type qinq

exit no shutdown-----------------------------

SAP with dot1q encapsulation

SAP with no encapsulation

SAP with QinQ encapsulation

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

GRE based

MPLS based, LDP

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

*A:P1# configure service sdp 12 mpls create*A:P1>config>service>sdp# info far-end 10.1.1.2 lsp "l-1-2"


*A:P1# configure service sdp 12 mpls create*A:P1>config>service>sdp# info far-end 10.1.1.2 ldp


*A:P1# configure service sdp 12 mpls create*A:P1>config>service>sdp# info far-end 10.1.1.2 ldp


*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

*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

spoke-sdp vs mesh-sdp

3 Layer 2 Service: VLL (Epipe)

What is MPLS L2 VPN

MPLS L3 VPN

MPLS L2 VPN

Tunnel Label Inner Label Layer3 Header Data

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

SAP

SAP

SAP SAP

SDP SDP

Local Epipe Distributed Epipe

SDP SDP

PW-Switching Epipe

Epipe Service

port 1/1/4

dot1q physical network link

servicecustomer

SAP SDP

servicecustomer

SAPSDP

packet VC-label

Private wire service

MPLS Transport or Outer Tunnel (unidirectional)

packet VC-label

Outer-labelInner-label

label

packet

packet VID

packet VC-label

TLDP is used to signal VC-labels

Port-ID:VLAN-IDSDP-ID:VCID

Two MPLS labels :

Used by TLDP

SWAP of MPLS Outer label

configure serviceepipe 2 customer 3 sap 1/1/4:36

spoke-sdp 12:2

configure serviceepipe 2 customer 3 sap 1/1/4:36

spoke-sdp 12:2

configure serviceepipe 2 customer 3 sap 1/1/1

spoke-sdp 21:2

configure serviceepipe 2 customer 3 sap 1/1/1

spoke-sdp 21:2

configure servicesdp 12 mpls create far-end 10.1.1.2




4 Layer 2 Service: VPLS

Virtual Private LAN Service (VPLS)

PE A PE C

PE B

PE D

IP / MPLS

Network

LSP Full-Mesh

VPLS Service1

VPLS Service2

Bridged multipoint Ethernet service (point to multipoint)

From customer’s 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

VPLS: Customer operation

VPLS #1

10.10.1.x

VPLS #2

20.20.2.x

CE A

CE B

CE A

CE B

CE A

CE B

VPLS Service Types #1: Switch Inter-connect

VPLVPLSS

Service ProviderService ProviderInfrastructureInfrastructure

Small OfficeSmall Office


VB

VB

VB


L2 Switch

Allows customers to connect Layer-2 switches into the VPLS service

Service supports multiple MAC addresses per site

VPLS Service Types #2: Router Inter-connect

VPLVPLSS

Service ProviderService ProviderInfrastructureInfrastructure

Corporate HQCorporate HQ

Branch OfficeBranch Office

Branch OfficeBranch Office

VB

VB

VB

Router

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

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 VPLSWorking process of VPLS


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.

Control PlaneControl 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 .

Data PlaneData Plane

VC Label Signaling

Trong dịch vụ VPLS, VC-label Signaling được sử dụng giữa PEs Mỗi PE khởi tạo một targeted LDP session tới far-end PEs Thông báo cho far-end PEs biết VC label nào được sử dụng để gửi

packets cho mỗi dịch vụ

PE-1

PE-2

PE-3

M-1

M-3

M-4

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

PE2->PE1: For Svc-id 101 Use VC-label pe1-2





VB

VB

VBpe2-1

pe1-2

pe3-2

pe3-1

pe1-3

pe2-3VPLSVPLS

VPLS Learning

M1

M2

M3

M41/1/1:100

1/1/1:200

1/1/2:0

1/1/2:0

Send a packet from M3 to M1

VPLSSvc-id = 101

1/1/2:0LocalM3

Mapping

Location

MAC

VPLS Svc-id = 101

Tunnel to PE2

RemoteM3

MappingLocation

MAC

VPLS Svc-id = 101

Tunnel to PE2

RemoteM3

MappingLocation

MAC

- 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

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

Packet Walkthrough for VPLS Service-id 101

PE 2

PE 3PE 1

VPLS Packet Forwarding

M1

M2

M3

M4

1/1/1:100

1/1/1:200

1/1/2:0

1/1/2:0

Reply with a packet from M1 to M3

Tunnel to PE1RemoteM1

1/1/2:0LocalM3

MappingLocationMAC

1/1/1:100LocalM1

Tunnel to PE2RemoteM3

MappingLocationMAC - 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

VPLS Svc-id=101

VPLS Svc-id=101

PE 2

PE 3PE 1

Packet Walkthrough for VPLS Service-id 101

5 Layer 3 Service: IES

Epipe / VPLSSAP

7x50-A

SDP

SAPiES ServiceIP interface

Create theService1Create IP

Interface2Create the SAP3

ApplyFilters4

Create Routes5

Creating an IES Service

IES service data packets are not encapsulated: no SDP required

6 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

7 Quy hoạch

Quy hoạch

Một số tham số khai báo trong PE được quy hoạch - Service id và VC id - SDP id - Tên Interface

SDP ID

Quy hoạch SDP ID SDP IDs cho các node trong VTN1, các thông số này được quy hoạch thống nhất trên toàn bộ các PE:

• Các node trong VTN1 : 1001 – 1999 • Từ VTN1 – VTN2 : 2001 – 2999 • Từ VTN1 – VTN3 : 3001 – 3999 <region><octet cuối cùng của PE router id>

SDP ID

SDP ID

1 chữ số 3 chữ số

<region> <octet cuối cùng của PE router id>

STT Mô tả

1 -<region> - SDP giữa các PE trong cùng VTN1 thì có giá trị bằng 1

- SDP từ PE thuộc VTN1 đến PE thuộc VTN2 có giá trị bằng 2

- SDP từ PE thuộc VTN1 đến PE thuộc VTN3 có giá trị bằng 3

2 -<octet cuối cùng của PE router id>

- Là giá trị của octet cuối cùng của PE router ID

SDP ID

Service id và VC id

Khuyến nghị nên sử dụng Service id và vc id cùng 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 Mô tả

1 <Service Type>

- Đây là tham số nhận dạng loại dịch vụ- Với dịch vụ VLL có giá trị bằng 1- Với dịch vụ VPLS có giá trị bằng 2- Với dịch vụ VPRN có giá trị bằng 3- Với dịch vụ IES có giá trị bằng 4

2 <Customer id>

- Là một id nhận dạng khách hàng, tuân theo nhận dạng khách hàng của các dịch vụ trong VN1.

3 <Channel type>

- Với kênh nội tỉnh ký VTN có giá trị bằng 0- Với kênh nội tỉnh ký VNPT tỉnh thành có giá trị bằng 2- Với kênh liên tỉnh có giá trị bằng 4

4 <Channel group>

- Là nhận dạng nhóm kênh của khách hàng khi khách hàng cho nhiều nhóm kênh trong một loại dịch vụ

Tên 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 <a-end> Tên của node tại điểm đầu của link kết nối

2 <b-end site> Tên của node tại điểm cuối của link kết nối

3 <number> 2 digit tiếp theo đại diện cho số link kết nối giữa 2 node

Service_20110913

Documents

service distribution

alive shutdown

service provider

pe thuc vtn1

flooded traffic

service access

flooded traffic

service provider