(4.2) Vietnam VNPT Expansion LLD Present-Common Part(Final)

8/12/2019 (4.2) Vietnam VNPT Expansion LLD Present-Common Part(Final)

1/51

HUAWEI TECHNOLOGIES Co., Ltd.

www.huawei.com

Huawei Confidential

Vietnam VNPT MAN Low Level Design Present

Huawei Network Solution Dept.


2/51

Huawei Confidential Page 2

Agenda

Network Archi tecture

IP Address Plann ing

New Device Nam ing

MPLS Plann ing

VPN Design

High Avai labi l i ty Solut ion

QOS solu t ion

Exist ing Service Risk Analyzing


3/51


Network ArchitectureOverview

The PE need to use /32 mask routing item to

setup LDP LSP, but the UPE/PE-AGG didnt have

inter-province routing, so the E2E inter-province

LSP cannot setup, which mean the MPLS LDP

domains are separated naturally.

P

MPLS LDP Domain

For IP CORE

UPEPE

AGGSR

MPLS LDP Domain

For MANE B

MPLS LDP Domain

For MANE A

UPE

UPE

SRPE

AGG

PE-AGG

MANE UPE/PE-AGG only learn the detailed

routing item within this province, UPE/PE-AGG

avoid to learn the default route which means

UPE/PE-AGG can not access to other province.

MANEs routing items can be summarized by ISIS

Level-1-2 SR, Even flapping occurred in MANE

wont spread to IP CORE.

SR can leak particular routes to MANE based on

service requirement.

BRAS work as ISIS level 1 router, and has no IGP

interaction with MANE

MANE A

MANE C

MANE BISIS Level 1 ISIS Level 1

ISIS Level 1 ISIS Level 1ISIS Level 2

MANE D


4/51

Huawei Confidential

Network ArchitectureOverview

The network structure of each MAN will consist of Metro access ring and Metro

core ring.

Two selected routers in the Metro core ring will be connected to the BRAS and

the SR located at the backbone edge

DSLAM /MSAN /LSWwill connect to the UPE routers located in the Metroaccess ring.


5/51


Agenda



New Device Nam ing

MPLS Plann ing

VPN Design


QOS solu t ion


Summary Scenar io and Step for Migration


6/51


IP Address Planning

The IP Address Planning will follow phase 1&2

Connection to SR will be using the subnet /30 network range

provided by VTN.

For the link replacement situation, will be reused the IP addressassigned before.

For the new link interconnection will be using the IP address

which reserved before.

For the new device loopback interface, will be using the IP

address which reserved before.

ISIS design for new device will follow Phase1&2 no change


7/51


Agenda



New Device Nam ing

MPLS Plann ing

VPN Design


QOS solu t ion


Summary Scenar io and Step for Migration


8/51


New Device Naming

The New device which will be deployed in MAN-E, the Naming

will follow the design before.


9/51


Agenda



MPLS Plann ing

VPN Design


QOS solu t ion


Summary Scenar io and Step fo r Migrat ion


10/51


MPLS Design

MPLS works as the fundamental to forward packet in this network. All theMPLS parameter design will follow Phase1&2, no change.

Each metro layer for respective province will have its independent MPLS

domain. In addition MPLS domain in each metro layer is separated from

MPLS domain in the core layer as well. In another word, end-to-end inter

province LSP and province to core layer LSP will not be established.


11/51


MPLS TE

By integrating TE (Traffic Engineering) with

MPLS, we can further optimize the network

utilization. Through MPLS TE, RSVP-TE will be

used to set up LSP (Label Switch Path) tunnels

to a specific path. This can eliminate network

congestion and balance the network traffic.MPLS TE will also able to provide fast

recovery from link and node failures where

in VNPT scenario, TE hot standby will be

used.


12/51


MPLS Configuration

Template for configuration MPLS/MPLS-TE


13/51


14/51


VPN Design

CID XX YYY Z WWW A

S lng ti a(1UPE) Ghi ch

DvLoopback1 (gn) PEAGG(1,2,3) SthtHuawei=0/1,

Cisco=0

HSI 11 025 1/2/3 000 0/1 1000/UPE/tnh LL

oD 12 0

0 1000/UPE/tnhLoopback ca nt

gc, Z=0/VPLSoIP 13 0

L3 VPN 14 1/2/3 0/1 1000/UPE/tnh LL

Eline lin

nh 15 254 1/2/3 999 0/1 1000/UPE/tnh LL

L2 E-LAN 16 0

0 1000/UPE/tnhLoopback ca nt

gc, Z=0/VPLSL2 E-TREE 17 0

CID X YYY ZZZ WWW S lng ti a

Dv Loopback 1 Loopback 2 khch hng

Eline ninh 4 011 254 999 1000 gia2 UPE

All the VPN design will follow Phase1&2, no change. VPN using in MANE including

E-line, E-lan, E-Tree. Here is VC-ID design for all VPN services


15/51


16/51


Agenda



MPLS Plann ing

VPN Design


QOS solu t ion




17/51


VN2

Overview of High Availability Solution

End-to-end links/nodes

protection, including mid

links/nodes

End-to-end

links/nodes

protection, without

end nodes

UPE

Agg Ring

Acc Ring

SRPE AGG

BRAS

Video Headend

VoIP Server

Acc Ring

DSLAM

CE

UPEPE AGG

SR

CE

VRRP

IGP Fast Convergence/Graceful Restart

Internet

Acc Ring

SR

TE hot-standby TE hot-standby

IGP Fast Convergence/Graceful Restart


18/51


VN2

TE hot-standby LSP protection

PE-AGG

UPE

1

TE Tunnel

TE hot-standby Active LSP

TE hot-standby Backup LSP

2

SR BRAS


19/51


High Available Configuration

Template for configuration MPLS/MPLS-TE


20/51


Agenda



MPLS Plann ing

VPN Design


QOS solu t ion




21/51


QoS Overview

E2E QoS Design

MPLS QoS Deployment

HSI/FTTx QoS Model

IPTV/VoD QoS Model

Enterprise VPN QoS Model

3G Mobile Backhaul QoS Model

Template for Configuration

QoS Solution


22/51


QoS OverviewPriority Mapping and Queuing for reference

Index QoS Class Bandwidth Ratio

(%)

DSCP 802.1p

(CoS)

MPLS

EXP

Queuing

1 CONTROL 1 CS6 6 6 PQ

2 REAL-TIME 15 EF 5 5 PQ

3 VIDEO 30 AF41 4 4 WFQ

4 CRICTICAL

DATA1

15 AF31 3 3 WFQ

5 CRICTICAL

DATA2

10 AF21 2 2 WFQ

6 BUSINESS HSI 14 In - profile 1 1 WFQ

Out - profile 0 0 WFQ

7 RESIDENTAL

HSI

15 Default 0 0 BE


23/51


VN2

E2E QoS Design

UPE

Agg Ring

Acc Ring

PE AGG

BRAS

Video Headend

VoIP ServerDSLAM

CE

SR

Acc Ring

Internet

MGC

Pipe Mode

UPE PE-AGG SR/BRAS

Downstream _ UNI: CAR or shaping

NNI: Scheduling

H-QoS

Upstream UNI: H-QOS

NNI: Scheduling

_ Normal QoS

Scheduling

UNI UNINNI


24/51


VN2

MPLS QoS Deployment

Implement classification and remark at Ingress UPE for serviceschedule and bandwidth guarantee.

Implement service schedule and bandwidth guarantee at Egress PE.

Guarantee E2E QoS with PIPE model (HIS/FTTx, VoD/BTV BusinessVPN), UNIFORM model (3G Mobile Backhaul)

UPESRUPE SR

CE

Uniform

Pipe

Short-Pipe

DSCP/802.1P

5 4

4 4

4 4

CE

DSCP/802.1P

PE-AGG PE-AGG

4

5 4

5 4

4 4 4 4

5 4

5 4

EXP EXP


25/51


HSI/FTTx QoS ModelVN2

BRAS/Radius

PE-AGG

UPE

Traffic

Classiffier and

CAR

DSLAM/LSW

PPPOEVLL

Active

VLLStandby

Traffic

Classiffier and

CAR

The subscriber of HSI service was

limit by Radius server and DSLAM,

the bandwidth was guaranteed by

Radius server and DSLAM, so on

MAN-E no need deploy policy to limit

bandwidth for HSI service.

Traffic classification for HIS service

use default type, BE flow.

Deploy PQ (port queue) on NNI port

for BE flow to schedule.

UNI

UNI

NNI


26/51


VoD QoS Model

The subscriber of VOD&BTV service

was limit ed by DSLAM/LSW so on

MAN-E no need deploy policy to limit

bandwidth for VOD&BTV service.

Classify the VoD flow to AF31 when

access to MAN-E.


for AF31 flow to schedule.

PE-AGG

UPE

SR

SR

UPE

Metro

Access

PW1

PW1

MP-BGP

PE-PE

PE-AGG

VN2

PW2

VRRP

SR

UpstreamV

PLS

Downstream

VLL

STB

STB

L2VPN Access Point

L3VPN Access Point

UpstreamV

PLS

DownstreamV

LL

VOD Cache

VOD Cache

PW2

VRRP

DSLAM/LSW

DSLAM/LSW

NNI


27/51


IPTV QoS Model

VN2

PIM-SSM

IPTV

Headend

PE-AGG

UPE

SR

STB

IGMP

DSLAM

IGMP terminate

M-VLAN

Multicast

repeat node

BTV source

The subscriber of VOD&BTV service

was limit by DSLAM/LSW, so on MAN-

E no need deploy policy to limit

bandwidth for VOD&BTV service.

Classify the BTV flow to AF41 when

access to MAN-E.


for AF41 flow to schedule.

UNI

UNI

NNI


28/51



L2VPN Access Point

VPLS

VN2

UPE

SR

SR

UPE

VPLS

VPLS

VPLS

Branch A1

VN2

UPE

SR

SR

UPE

VPLS

VPLS

VPLSHeadquarter A

Branch B2

Headquarter B

Headquarter A

Branch A1Branch A2

Branch B1 Branch A2

NNI

UNI


29/51



Deploy SQ (subscriber queue) on MAN-E to limit the bandwidth for each VPN.

Classify the flow to AF21/AF11 when access to MAN-E. (high/low throughput)

Deploy PQ(port queue) on NNI port for AF21/AF11 flow to schedule.


30/51


Scenario 1 : With RNC (intra-province)

Node B

VSI

VSI

L2 SW

Mobile

Router

L2 SWNode B

VLAN 2400, 2401

VLAN 2411

Isolate

Isolate

MAN-E

Dot1q

H-VPLS

PE-AGG 2

PE-AGG 1

UPE2

UPE1

Node B

L2 SW

Node B

Isolate

RNC

TRUYN TI MOBILE BACKHAUL NI TNH(intra-province)

Tuyncpkhc

Tuyn

cpk

hc

VLAN 2400

VLAN 2400

VLAN 2401

L2 SWVLAN 2402

UPE3

Node B

L2 SW

VLAN 2402

Node B

Isolate

Trunking +

loadsharing

VSI

2401

VSI

2400

VSI2411

Trunking +

loadsharing

GW = Mobile

Router IP

GW = Mobile

Router IP

VSI

2411

VSI2400

VSI

2401

PW d phng ngui

VSI

2411

VSI

2400

Access

Trunk vlan2400

Access

VSI

2401

Access

Access

Access

Trunking +

loadsharing

User-termination

Mode + subinterface

NNI

UNI

Trust EXP, 802.1p,

DSCP NNI

Packet

schedule

UNI

Trust EXP, 802.1p,

DSCP

3G Mobile Backhaul QoS Model


31/51


32/51


Template for Configuration

Template for 3G Mobile Backhaul

Template for HSI, IPTV/VoD, Enterprise VPN

Diffserv Domain Default for reference


33/51


Agenda



MPLS Plann ing

VPN Design


QOS solu t ion




34/51


Existing Service Risk Analyzing

HSI/FTTx Service

VoD/BTV Service

VPN Enterprise Service

3G Backhaul Service


35/51


Existing Service Risk Analyzing-HIS/FTTx Service

For Internet services, currently some provinces do not have backup for this

service based on these scenario:

Scenario 1: HSI with configured backup in MANE and BRAS, this is reference

Scenario 2: HSI with configured backup in MANE but no backup link to BRAS

Scenario 3: PE-AGG connect to 2 different BRAS, HSI without configured

backup in MANE and link to BRAS

Scenario 4: FTTx, no service backup configured


36/51



Scenario 1: HSI with configured backup in MANE

and BRAS, this is reference

Interruption Analysis

Fault at point Scenario

1 & 2 TE Hot-standby protects PW. BFD for

LSP detect main LSP goes down and willdivert traffic using backup LSP.

3 PPPoE session disconnected. User need

to redial.

Recommendation

This scenario is standard follow design. In any case offailure show on above table, service not effect

No recommendation


37/51



Scenario 2: HSI with configured backup in MANE

but no backup link to BRAS



1 TE Hot-standby protects PW. BFD for

LSP detect main LSP goes down and willdivert traffic using backup LSP.

2&3 Service cannot recover

RecommendationConnect link from AGG2 to BRAS and test the backup

path before migration (follow scenario1)


38/51



Scenario 3: PE-AGG connect to 2 different BRAS, HSI

without configured backup in MANE and link to BRASInterruption Analysis

Fault at

point

Scenario

1 TE Hot-standby protects PW.

BFD for LSP detect main LSPgoes down and will divert

traffic using backup LSP.


RecommendationShould configure backup path in

UPE, BRAS

Should connect second link to both

BRAS as picture

Test backup path before migration


39/51



Scenario 4: FTTx, no service backup configured



1 TE Hot-standby protects PW. BFD for

LSP detect main LSP goes down and will

divert traffic using backup LSP.


Recommendation

Authentication in VISA system for this service is based

on 4 parameters so it cannot protect in BRAS

When swap AGG, service will be interrupted


40/51


Existing Service Risk Analyzing-VPN Service

There are 2 kind of VPN (Enterprise) Service: Inter-province and Intra-province.

In each kind devided by 2 subscribers: P2P (VLL), P2MP(VPLS).

For intra province VPN: We have 2 scenarios

VPN in the same Ring

VPN in different Ring

For inter province VPN: This case is the same with Intra province and combine

with HIS/FTTx/VoD/BTV to protect in VN2. So we dont mention here


41/51



Scenario 1: VPN in the same Ring



1 TE Hot-standby protects PW.

2 or 5 This occur when swap UPE, VPN

service must be effected

3 or 4 This occur when swap AGG, VPNservices not effected

Recommendation

When swap UPE by live swap, VPN service will be

effected

VPN channel established between UPE by

tunnel in the same Ring for customer, traffic will

not pass though AGG device


42/51



Scenario 1: VPN in different Ring


Fault at

point

Scenario

1 or 6 This occur when swap UPE, VPN

service must be effected

2,3,4,5 Protect by TE Hot standby, VPN

service will not be effected

Recommendation

When swap UPE by live swap, VPN service will be

effected

VPN channel established between UPE by

tunnel in the same Ring for customer, traffic will

not pass though AGG device


43/51


Existing Service Risk Analyzing-VoD/BTV Service

There are 2 existing multicast/VoD sources from different operator. But

only VASC source connect over VN2, the other connect directly to AGG in

province

Curently there are 2 model using in VN2 network

Province with 1 PE (SR)

Province with 2 PE (SR) use VRRP protocol


44/51



Scenario 1: Province with configured backup path


It is unavoidable that in a single SR

scenario, BTV service will fail when

the SR fails

Fault at

point

Scenario

(BTV)

1 ,2,3 BTV: ISIS Fastconvergence.

Recommendation

No recommendation, they are standard

Fault at

point

Scenario

(VoD)

1 Protect by TE Hot-standby

2,3 Only 2SR using VRRP

protect for BTV service


45/51



Scenario 2: Province with single PE and protect by LAG interface



(BTV)

1 or 3 BTV: ISIS Fast convergence.

2 When swap AGG1 Service will be

interrupted

Recommendation

Connect link from AGG2 to SR (PE) and configure

multicast routing for the links (follow scenario1)


(VoD)

1 or 3 Protect byTE Hot-standby

2 When swap AGG1 Service will be

interrupted


46/51



Scenario 3: Province with double PE and protect by LAG interface



(BTV)

1 BTV: ISIS Fast convergence.

2 or 3 When swap AGG1 Service will be

interrupted

Recommendation

Connect link from AGG2 to SR (PE) and configure

multicast routing for the links (follow scenario1)


(VoD)

1 Protect byTE Hot-standby

2 or 3 When swap AGG1 Service will be

interrupted


47/51


48/51


Existing Service Risk Analyzing-3G Service

Scenario 1: Layer2 in MANE, layer3 in M-PE, gateway for NodeB is M-PE


Fault

at

point

Scenario

1 Heartbeat is over

MANE, if link 1 down,

TE Hot-standby

protects PW.

2,3,4 MANE using HVPLS

will forward traffic to

the other way

M-PE no heartbeat

but link connect fromM-PE1 to AGG1 is

down so M-PE2 will

become master for

VRRP to forward

traffic

Recommendation

No because traffic is protected


49/51



Scenario 2: Both Layer2 in MANE and M-PE, gateway for NodeB is RNC,

intra province


Fault at

point

Scenario

1 Protect by TE-Hot

standby2,3,4 When swap AGG1: No

backup mechanism.

Service will be

interrupted. Must onsite

to configure on MANE to

recover

Recommendation when swap AGG1

VSI in UPE1 peer to AGG2

Add layer2 link in M-PE and pass vlans


50/51



Scenario 3: Both Layer2 in MANE and M-PE, gateway for NodeB is RNC,

inter provinceInterruption Analysis

Recommendation when swap AGG1

(Same with scenario2)

Fault at

point

Scenario

1 Protect by TE-Hot

standby2,3,4 When swap AGG1: No

backup mechanism.

Service will be

interrupted. Must onsite

to configure on MANE to

recover


51/51

Thank youwww.huawei.com

Documents

(4.2) Vietnam VNPT Expansion LLD Present-Common Part(Final)