odd010005 qos network design issue 1_1

8/13/2019 ODD010005 QoS Network Design ISSUE 1_1

1/67


2/67

HUAWEI TECHNOLOGIES CO., LTD. Page 1All rights reserved

As the rapid development of multimediatechnology, Internet evolves from a datatransmission network to an integrated

transmission network transmitting data,voice, and video services. The currentBest-Effort transmission mode falls shortof multimedia applications and QoS. AQoS control technology emerges to raiseutilization of network resources andprovide quality services, thus becomingone of core technologies of NGN.

PDF created with FinePrint pdfFactory Pro trial version www.pdffactory.com
http://www.pdffactory.com/http://www.pdffactory.com/


3/67


References

l VRP5 Operation Manual QoS Part

l Computer Network QoS

l End-to-End QoS Network Design

l Technical White Paper for QoS

l Huawei IP QoS Solution



4/67


This course helps you to:

[ Know about basic concepts and design principlesof QoS

[ Understand problems concerned in QoS designand planning

[ Master methods of planning and designing QoS



5/67


Chapter 1 Overview and Planning &Chapter 1 Overview and Planning &Design of QoSDesign of QoS

Chapter 2 QoS Design of CampusChapter 2 QoS Design of CampusNetworkNetwork

Chapter 3 QoS Design of WANChapter 3 QoS Design of WAN

Chapter 4 MPLS QoS DesignChapter 4 MPLS QoS Design

Chapter 5 QoS Design CaseChapter 5 QoS Design Case



6/67



1.1 QoS Concept1.1 QoS Concept

1.2 QoS Model1.2 QoS Model

1.3 Tools for Realizing QoS1.3 Tools for Realizing QoS

1.4 Principles of QoS Design1.4 Principles of QoS Design

1.5 Analysis of QoS Design1.5 Analysis of QoS Design



7/67


QoS Concept

l QoS definition stated in RFC2386: QoS is a

series of service requests to be satisfied in the

process of data stream transmission.

Performance indices such as bandwidth, delay,delay jitter, packet loss ratio, and throughput are

used to describe QoS.

QoS DefinitionQoS Definition

The commitment made by the network to

bandwidth

delay

Delay jitter

Loss ratio

throughput



8/67


9/67










10/67


QoS Models

l IntServ: Integrated service architecture

[ Guaranteed service

[ Controlled-Load service

[ Due to resource reservation and storage of soft state information,large-scaled deployment of IntServ is improper.

l DiffServ: distinguished service architecture

[ Expedited Forwarding

[ Assured Forwarding

[ Best-Effort (BE)

[ Because there is no need to reserve resources and save soft stateinformation, Diffuser is suitable to be deployed in an IP backbonenetwork.

Two QoS ModelsTwo QoS Models



11/67


Interworking Between Two QoS ModelsInterworking Between Two QoS Models

IP edge networkIP backbone network

Non DS areaDS area

IP edge network

Non DS area

Guaranteed service

Controlled-Load service

EF

AF

QoS Models



12/67










13/67


Tools for Realizing QoS

l Tools for classifying and marking

l Tools for monitoring and shaping

l Tools for avoiding congestion

Tools for Realizing QoSTools for Realizing QoS

REDWREDREDWRED

Receiving packets

Packet classifying and marking Congestion detection/avoidance

Packet sending

Outbound interfaceInbound interface

Source IPDestination IPSource portDestination portProtocol typeTOS

A C L

CAR

Traffic policing

Congestion managing

VOQ scheduling

DWRR/WFQ WFQPQ/DWRRWFQ/DWRR

Traffic scheduling

PQ/WFQ

Switching network Port schedulingPriority scheduling

Traffic scheduling/shaping

l Tools for managing congestion

l Tools for link effectiveness



14/67


15/67


Principles of QoS Design

l Universal design principles

l Principles of classifying and marking

l Principles of policing and degrading

l Principles of queuing and discarding

l Principles of migrating DoS and Worm attacks

l Principles of deployment

Principles of QoS DesignPrinciples of QoS Design



16/67










17/67


Analysis of QoS Design Requirements

l Voice

[ As stipulated in RFC3246, voice stream should be marked with DSCP EF.

[ Packet loss ratio < 1%

[ Unidirectional delay < 150ms[ Mean unidirectional jitter < 30ms

[ Bandwidth ranging from 21 kbps to 320 kpbs should be guaranteed tosupport various sampling rates, codec manners, and link overheads.

l Call-signaling

[ The Call-signaling traffic should be marked with DSCP CS3.

[ At least 150 bps bandwidth should be guaranteed for voice control trafficto support different Call-signaling.

Analysis of QoS Design Requirements Analysis of QoS Design Requirements -------- VoIPVoIP



18/67



l Interactive-Video

[ The traffic should be marked with DSCP AF41.

[ Excessive traffic is degraded to AF43.

[ Packet loss ratio < 1%

[ Unidirectional delay < 150 ms

[ Jitter < 30 ms

[ Minimum preferable bandwidth = stream speed + 20%

l Streaming-Video

[ The Call-signaling traffic should be marked with DSCP CS4.[ Packet loss ratio < 5%

[ Delay 5 s

Analysis of QoS Design Requirements Analysis of QoS Design Requirements -------- VideoVideo



19/67



l Best-effort Data

[ The traffic should be marked with DSCP 0.

[ Recommend reserving 20% bandwidth for it.

l Bulk Data

[ The traffic should be marked with DSCP AF11 and the excessive part, marked with AF12 or

AF13.[ Set proper bandwidth to avoid Bulk Data occupying the entire link.

l Transactional Data/Interactive Data

[ The traffic should be marked with DSCP AF21, and the excessive part, marked with AF22 or AF23.

[ Set proper bandwidth to guarantee transmission of interactive data.

l Mission-Critical Data

[ The traffic should be marked with DSCP AF31, and the excessive part, marked with AF32 or AF33.

[ Set proper bandwidth to guarantee the transmission of interactive data.

Analysis of QoS Design Requirements Analysis of QoS Design Requirements -------- DataData



20/67



l IP Routing

[ The traffic should be marked with DSCP CS6.

[ Reserve necessary bandwidth for it.

l Network Management


[ Reserve necessary bandwidth for it.

Analysis of QoS Design Requirements Analysis of QoS Design Requirements ---- Control PlaneControl Plane



21/67



l Definition of Scavenger class

[ The service level is lower than Best-Effort.

[ In the idle state of bandwidth, a few bandwidth is allocated to transmit it. In thecase of congestion, no bandwidth is allocated for it.

[ For example, traffic of games or videos in an enterprise networkl Function of Scavenger class

[ Restrict the transmission of Scavenger class.

[ Migrate DoS and Worm attacks.

l Requirements of Scavenger class


[ The least bandwidth should be allocated.

Scavenger ClassScavenger Class



22/67









23/67


Chapter 2 QoS Design of Campus NetworkChapter 2 QoS Design of Campus Network

2.1 Considerations of Campus Network QoS Design2.1 Considerations of Campus Network QoS Design

2.2 Campus Network QoS Design Planning2.2 Campus Network QoS Design Planning



24/67


QoS Design of Campus Network

l Policies of migrating DoSand Worm attacks

l Special traffic mark

l trust mode on the edge

l QoS policy when WANconnected

Design ConsiderationsDesign Considerations

Core layer

Distribution layer

Access layer



25/67


Chapter 2 QoS Design of Campus NetworkChapter 2 QoS Design of Campus Network

2.1 Considerations of Campus Network QoS Design2.1 Considerations of Campus Network QoS Design

2.2 Campus Network QoS Design Planning2.2 Campus Network QoS Design Planning



26/67


Campus Network QoS Design Planning

l Set traffic policing on a switch at access layer.

l Mark excessive traffic with DSCP CS1 (Scavenger class)

l When links are not congested, excessive traffic can be

transmitted.

l In the case of congestion, discard DSCP CS1 traffic first.

Policy of Migrating DoS and Worm AttacksPolicy of Migrating DoS and Worm Attacks

Prevent network down resulting from large traffic at source.



27/67



l Mark special traffic according to TCP/UDP port No. or other rules

Scavenger

Best-Effort

Bulk Data

Transactional Data

Mission-Critical Data

Network Management

IP-Routing

Call-Signaling

Streaming-Video

Interactive-Video

Voice

Marking Special TrafficMarking Special Traffic

Mark traffic of different types with different labels, thus providingdifferent QoSs for different traffic.

CS1

0

AF11

AF21

AF31

CS2

CS6

CS3

CS4

AF41

EF



28/67


29/67



l The interface bandwidth between the edge router and the LANshould be as identical to that between the edge router and theWAN as possible.

l Perform traffic shaping and traffic policing on a switch.

QoS Policy When WAN ConnectedQoS Policy When WAN Connected

WANLAN

Traffic policing and shaping



30/67









31/67



3.1 WAN QoS Deployment3.1 WAN QoS Deployment

3.2 Design of WAN Aggregator QoS3.2 Design of WAN Aggregator QoS

3.3 Design of WAN Branch Router QoS3.3 Design of WAN Branch Router QoS



32/67


WAN QoS Deployment

l WAN aggregator

l Branch router

Place for QoS DeploymentPlace for QoS Deployment

WAN

WAN aggregator

R R

Branch router

Branch router



33/67








34/67


Design of WAN Aggregator QoS

l Considerations of Software QoS

l design Bandwidth design of Best-Effort traffic

l Bandwidth design of real-time trafficl Design of link effectiveness

QoS Planning of WAN AggregatorQoS Planning of WAN Aggregator

WAN

WAN Aggregator

R R



35/67



l QoS in a LAN, recommend using hardware-based QoS of aswitch.

l A WAN aggregation router uses software-based QoS.

l Software-based QoS is CPU intensive.

l Ensure that the CPU occupied by QoS is less than 75%.

WAN AggregatorWAN Aggregator -------- Consideration of Software QoS DesignConsideration of Software QoS Design



36/67



l Best-Effort is a default traffic type.

l Recommend reserving 25% bandwidth for Best-Effort traffic.

WAN AggregatorWAN Aggregator -------- Design of BestDesign of Best --Effort TrafficEffort Traffic



37/67


l Real-time traffic is sensitive to delay, so insert it into LLQ.

l Bandwidth is allocated to real-time traffic first, but avoid excessiveoccupation of bandwidth of other traffic.

l The bandwidth of LLQ should be less than 1/3 of the total bandwidth.(recommended)

WAN AggregatorWAN Aggregator -------- Design of RealDesign of Real --Time TrafficTime Traffic




38/67


l Low-speed link ( 768 kbps)

[ Transmission of Interactive-Video traffic is not recommended.

[ Recommend starting link fragmentation and interleaving (LFI) totransmit VoIP traffic.

[ Recommend starting cRTP (RTP compression), but avoid excessiveCPU occupation.

WAN AggregatorWAN Aggregator -------- Design of Link Effectiveness (1)Design of Link Effectiveness (1)




39/67


l Middle-speed link (768 kbps speed T1/E1)

[ Insert VoIP traffic and Interactive-Video traffic into LLQ, but the

bandwidth of LLQ should be less than 1/3 of total bandwidth.[ If VoIP traffic and Interactive-Video traffic occupy more bandwidth

than expected, insert VoIP traffic into LLQ, and insert Interactive-Video traffic into CBWFQ.

[ No need to start LFI.

[ Choose to start cRTP.





40/67



l High-speed link (speed T1/E1)

[ No need to start LFI.

[ Recommend starting cRTP, but avoid excessive CPUoccupation.




41/67


l Low-speed/middle-speed linkWAN AggregatorWAN Aggregator -------- Traffic Type DesignTraffic Type Design

Three types Five types

Voice 33 #

Best-Effort 62 #

Call-Signaling 5 #

Voice 33 #

Best-Effort 25 #

Call-Signaling 5 #

Critical-Data 36 #Scavenger 1 #




42/67


l High-speed link

eight types Voice 18 #

Best-Effort 25 #

Call-Signaling 5 #Critical-Data 27#

Scavenger 1 #

Interactive-Video 15 #Bulk Data 4 #

Network 5 #

Design of WAN Aggregator QoSWAN AggregatorWAN Aggregator -------- Traffic Type DesignTraffic Type Design



43/67


44/67








45/67


Design of WAN Branch Router QoS

l The basic design is identical to that of a WAN aggregator.

l On the edge of a WAN, ignore unidirectional application traffic, for example,

Streaming-Video.

l On the edge of a LAN, the mapping from COS to DSCP may be set.

l On the edge of a LAN, classify and filter traffic.

QoS Design of a Branch RouterQoS Design of a Branch Router

WAN

WAN branch router

WAN borderLAN border



46/67


l On the edge of a WAN, ignoreunidirectional application traffic, forexample, Streaming-Video.

l Traffic types change.

QoS Design of a Branch RouterQoS Design of a Branch Router -------- on the Edge of a WANon the Edge of a WAN

Interactive-Video 15 #

Voice 18 #

Best-Effort 25 #

Scavenger 1 #

Bulk Data 4 #

Network-management 2 #

Routing 3 #

Transactional Data 12 #

Mission-Critical Data 15 #

Call-Signaling 5 #




47/67


l The mapping from COS to DSCP may be set.

l Classify and mark traffic.

l Identify harmful traffic and apply a filtering policy.

QoS Design of a Branch RouterQoS Design of a Branch Router -------- on the edge of a LANon the edge of a LAN

WAN

COS DSCP




48/67



Chapter 2 QoS Design of CampusChapter 2 QoS Design of Campus

NetworkNetwork






49/67



4.1 Place for MPLS QoS Deployment4.1 Place for MPLS QoS Deployment

4.2 Planning and Designing of CE QoS4.2 Planning and Designing of CE QoS

4.3 Planning and Design of PE QoS4.3 Planning and Design of PE QoS

4.4 Planning and Design of Backbone QoS4.4 Planning and Design of Backbone QoS



50/67


Place for MPLS QoS Deployment

l On the edge of CE, deploy traffic policing, shaping, classifying, marking, and linkeffectiveness.

l On the edge of PE, deploy traffic policing, shaping, re-marking, and linkeffectiveness.

l At the core of the network, it is unnecessary to deploy QoS. When necessary,deploy DiffServ.

R R

Place for QoS DeploymentPlace for QoS Deployment

MPLS VPN

R R

CE

R R

CE

PEPE

edge of CE

edge of PE

Core



51/67









52/67


Planning and Designing of CE QoS

l When the bandwidth of a CE-PE link is small, deploy LFI onthe edge of CE.

l Classify and mark traffic again on the edge of CE, because the

traffic type of VPN Site is inconsistent with that provided by SP.

QoS Deployment on the Edge of CEQoS Deployment on the Edge of CE



53/67









54/67


Planning and Designing of PE QoSQoS Deployment on the Edge of PEQoS Deployment on the Edge of PE

Real-Time 35 #

Best-Effort 25 #

Critical Data 45 #

Three types

Best-Effort 25 #

Critical Data 25 #

Four types

Real-Time 35 #

Video 15 #

Best-Effort 25 #

Critical Data 20 #

Five types

Real-Time 35 #

Video 15 #

Bulk Data 20 #

l Carriers are concerned about how to deploy QoS on PE.

l Various traffic classification policies are available on the edge of PE.



55/67









56/67


Planning and Design of Backbone QoS

l Uniform mode

l Short-Pipe mode

l Pipe mode

QoS Deployment at BackboneQoS Deployment at Backbone -------- Three ModelsThree Models



57/67


QoS Deployment at BackboneQoS Deployment at Backbone -------- Uniform modeUniform mode

IP:

DSCP

40

IP:

DSCP

40

MPLS

EXP 3

IP:

DSCP

40

MPLS

EXP 3

MPLS

EXP 0

IP2MPLS PUSH

MPLS2MPLS PUSH

IP:

DSCP

40

MPLS

EXP 3

MPLS

EXP 0

MPLS2MPLS SWAPMPLS2MPLS POP

MPLS2IP POP

IP:

DSCP

40

MPLS

EXP 0 IP:

DSCP

0




58/67


IP:

DSCP

40

IP:

DSCP

40

MPLS

EXP 3

IP:

DSCP

40

MPLS

EXP 3

MPLS

EXP 0

IP2MPLS PUSH

MPLS2MPLS PUSH MPLS2MPLS SWAP

MPLS2MPLS POP

MPLS2IP POP

IP:

DSCP

40

MPLS

EXP 3

MPLS

EXP 0

DSCP40 decides PHB.

IP:

DSCP

40

MPLS

EXP 0IP:

DSCP

40


QoS Deployment at BackboneQoS Deployment at Backbone -------- shortshort --pipe modepipe mode



59/67


IP:

DSCP40

IP:

DSCP

40

MPLS

EXP 3

IP:DSCP

40

MPLS

EXP 3

MPLS

EXP 0

IP2MPLS PUSH

MPLS2MPLS PUSH MPLS2MPLS SWAP

MPLS2MPLS POP

MPLS2IP POP

IP:DSCP

40

MPLS

EXP 3

MPLS

EXP 0

EXP 0 decides PHB

IP:

DSCP

40

MPLS

EXP 0IP:

DSCP40

Planning and Design of Backbone QoSQoS Deployment at BackboneQoS Deployment at Backbone -------- pipe modepipe mode



60/67



Chapter 2 QoS Design of CampusChapter 2 QoS Design of Campus

NetworkNetworkChapter 3 QoS Design of WANChapter 3 QoS Design of WAN





61/67


QoS Design Case

MAN QoS SolutionMAN QoS SolutionBranch access, IP priority mark, bandwidth limitation

Access layer

Network edge, service classification and adjustment,bandwidth limitationCore node, PHB

Core layer 2.5G PoS

Internet

622M PoSNE80

S3680

S8016

S3026

622M PoS

GE

FE

FE

Branch network

NE08/16

Provide cross-as QoS by SLA/TCAcoordination

SLA/TCAiManagerN2000

Branch network Branch network Branch network

Branch networkDistribution layer



62/67


QoS Solution of Enterprise Leased Line AccessQoS Solution of Enterprise Leased Line Access

R3680

DDN/FRDDN/FR

Lease line

PBX

Dialup line

Modem/NT1

PSTN/ISDN

R1760

E1

R2630

PBX

AT0/E&M

l Packet classificationl IP priority markl Congestion avoidance (WRED)

l CARl Queue scheduling (PQ, WFQ, and CBWFQ)l Traffic shaping (GTS)l Voice header compression

l Packet classificationl IP priority markl Congestion avoidance (WRED)l CARl Queue scheduling (PQ, WFQ, and CBWFQ)l Traffic shaping (GTS)l Voice header compression

QoS Design Case



63/67


QoS Solution of Ethernet Access in EnterprisesQoS Solution of Ethernet Access in Enterprises

S5516

IP networkIP network QoSQoS

S3526S3526

GE

GE

GE

l Packet classificationl IP priority markl Congestion avoidance (WRED)l CARl Queue scheduling (PQ, WFQ, WRR)l 802.1p

MCU GK

S3026

QoS Design Case



64/67


QoS Solution of Data CenterQoS Solution of Data Center

DS area

l 802.1p mappingl Service classification and traffic adjustment

l Forwarding packets in PHB manner

DS area

l 802.1p mappingl Service classification and traffic adjustment

l Forwarding packets in PHB manner

Layer 2 Ethernet QoSl Layer 2 packet classification

l Port-based, VLAN-based

l 802.1p tag

l Queue scheduling (PQ, WRR)

Layer 2 Ethernet QoSl Layer 2 packet classification

l Port-based, VLAN-based

l 802.1p tag

l Queue scheduling (PQ, WRR)

S8016/S5516

GEGE GEGE GEGE GEGE GEGE GEGE

FEFE FEFE

FEFE FEFE FEFE FEFE

S8016/S5516

S3526S3526

S3026 S3026 S3026S3026

S2024/S2403 S2024/S2403S2024/S2403S2024/S2403

Data center

server server

QoS Design Case


QoS Design Case


65/67


ThreeThree --inin--one QoS solutionone QoS solution

S5516

FE

server

Service center

S8016

NE16E

I n t e r n e t

ATMATM

NE08E

GKMCU

Mapping between IP QoS and ATM QoS

GK bandwidth management

MCU classifies media stream

and marks IP priority.

p Distinguishing between voice

and video Signaling and datagramp Priority markp Congestion avoidancep Queue schedulingp Traffic shaping

DS area, where service streams

are aggregated

and traffic is adjusted.

The traffic is forwarded in PHB manner.

If an MPLS network is in this area,

map MPLS CoS to DSCP.

Forward LSP in PHB manner.



66/67


Summaryl Use various QoS tools to deploy QoS.

l Plan and design proper QoS in different

network environments.

l Deploy QoS specific to devices with

different functions.



67/67

www.huawei.com

Thank You

http://www.huawei.com/http://www.pdffactory.com/http://www.pdffactory.com/http://www.huawei.com/

odd010005 qos network design issue 1_1

Documents