Prod Presentation0900aecd8031280f

7/30/2019 Prod Presentation0900aecd8031280f

1/43

Copyright 2003, Cisco Systems, Inc. All ri ghts reserved. Printed in USA.

Presentation_ID.scr

12003 Cisco Systems, Inc. All rights reserved.RST-1607 Networkers2004

QoS in MPLS NetworksRST-1607

Santiago lvarez

[email protected]

CCIE 3621


Prerequisites

Basic understanding of MPLS (L3VPN, L2VPN, TE)

Basic understanding of QoS (DiffServ)


2/43


Presentation_ID.scr


Agenda

Technology Overview

Backbone Infrastructure

IP Services

Layer-2 Services

Management


MPLS QoSTechnology Overview

444


3/43


Presentation_ID.scr


MPLS QoS Architectures

MPLS does NOT define new QoS architectures

MPLS QoS uses Differentiated Services (DiffServ) architecturedefined for IP QoS

DiffServ Architecture defined in RFC2475

MPLS support for DiffServ defined in RFC3270


Differentiated Services Architecture

Traffic Conditioning Agreement (TCA)

Classification/Marking/Policing/Shaping

Per-Hop Behavior (PHB)

Queuing/Dropping

IngressNode

InteriorNode

EgressNode

TCAPHB

PHB TCAPHB

DiffServ Domain


4/43


Presentation_ID.scr


Whats Unchanged in MPLS Support ofDiffServ

Functional components (TCA/PHB) and where they are used

Classification, marking, policing, and shaping at networkboundaries

Buffer management and packet scheduling mechanisms used toimplement PHB

PHB definitions

Expedited Forwarding (EF): low delay/jitter/loss

Assured Forwarding (AF): low loss

Default (DF): No guarantees (best effort)


Whats New in MPLS Support of DiffServ

How aggregate packet classifi cation is conveyed (E-LSP vs. L-LSP)

Interaction between MPLS DiffServ info and encapsulatedDiffServ info (e.g. IP DSCP)


5/43


Presentation_ID.scr


EXP-Inferred-PSC LSP (E-LSP)

Packet Class and drop precedence inferred from EXP (3-bit)field

RFC3270 does not recommend specific EXP values forDiffServ PHB (EF/AF/DF)

Used for frame-based MPLS

Layer-2 HeaderLayer-2 Header

Label HeaderLabel Header


0 1 2 3

0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1

Label EXP S TTLLabel EXP S TTLEXP

PayloadPayload

MPLS Shim Header

LabelStack

Frame Encapsulation

Class & DropPrecedence


Label-Only-Inferred-PSC LSP (L-LSP)

Packet Class in ferred from label

Drop precedence inferred from EXP or ATM CLP

Can be used for f rame-based and cell-based MPLS

Layer-2 HeaderLayer-2 Header



0 1 2 3

0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1

S TTLS TTLEXP

PayloadPayload

MPLS Shim Header

LabelStack

Frame Encapsulation

GFC VPI

VPI VCI

VCI

VCI PTI

HEC

GFC VPI

VPI VCI

VCI

VCI PTI

HEC

Drop Precedence

Label

CLP

Class

Label

Cell Encapsulation

CLPLabel

Drop PrecedenceClass


6/43


Presentation_ID.scr


E-LSP vs. L-LSP

An E-LSP may carry mul tiple classes (max 8, in real l ife lessthan that)

An L-LPS carries one class

Both E-LSP and L-LSP can use LDP or RSVP for labeldistribution

Cisco products currently support E-LSP for frame-modeMPLS

No demand for L -LSP suppor t with frame-mode MPLS yet


MPLS Support of DiffServ

All done with Modular QoS CLI (MQC)

Template-based command syntax fo r QoS

Separates classifi cation engine from QoS functionality

Platform-independent CLI for QoS features

Enters configuration sub-mode for policydefinition (marking, policing, shaping, queuing,etc.)

class-map [match-any | match-all] class-name

Command in interface configuration sub-mode

to apply QoS policy for in put or output tr affic

Enters configuration sub-mode for class definition

policy-map policy-name

service-policy {input | output} policy-name

class-map match-all REAL-TIME

match mpls experimental topmost 5

class-map match-all PREMIUM

match mpls experimental topmost 1 2

!

!

policy-map OUT-POLICY

class REAL-TIME

priority percent 25

class PREMIUM

bandwidth remaining percent 50

random-detect

class class-default

random-detect

!

i nterf ace POS1/ 0i p address 10. 150.1. 1 255. 255. 255. 0

service-policy output OUT-POLICY!


7/43


Presentation_ID.scr


MPLS QoSBackbone Infrastructure

1313132003, Cisco Systems, Inc. All rights reserved.Presentation_ID


QoS in my Backbone?

Do you think my corelooks like this?

Of course not (or doesit?)


8/43


Presentation_ID.scr


Backbone Requirements

Growing trend: MPLS asselected choice for next genmultiservice network

MPLS QoS architecture mustfit mutiservice strategy

Architecture must be f lex ib leand scalable

EthernetEthernet

ATMATMIPIP

VPNVPN

FrameFrameRelayRelayPPP

PPPIP/MPLS

InternetInternet

VoIPVoIP

IPv6IPv6

PSTNPSTN


Some Theory First

Delay and Loss vs. Utilization

* Measured on a large timescale

Linkutilization*

Delay/Loss

100%x%

y

Traffic patterns still debated(markovian, self-similar,others)

Queuing maths not full ycooked but:

if utilization* kept below x%,performance is excellent

as utili zation* approaches 100%,performance degrades


9/43


Presentation_ID.scr


Selecting Utilization Level (x%)

Target QoS guarantees(delay, jitter, loss )

Failure handling pol icies (link,node, SLRG)

School of thoughts for queuing theory

Heuristics

Risk tolerance

Testing Politics

Technology religion, etc.

Target Utilization Level (x%)is a function of:

Link

utilization*

Delay/Loss

100%x%

y

* Measured on a large timescale


Enforcing Utilization Level (x%)

Aggregate capacity planning

Ad just link capacity to expected link load

MPLS DiffServ

Ad just class capacity to expected class load

MPLS Traffic Engineering

Ad just link load to actual link capacity

MPLS DiffServ-Aware TE (DS-TE)Ad just class load to actual class capacity


10/43


Presentation_ID.scr


Lets Review Technology options MPLS DiffServ

Al ready discussed in overview sect ion

Only PHB relevant in the backbone

Traffic Conditioning Agreement (TCA)

Classification/Marking/Policing/Shaping

Per-Hop Behavior (PHB)

Queuing/Dropping

IngressNode

InteriorNode

EgressNode

TCAPHB

PHB TCAPHB

DiffServ Domain


MPLS TE Overview

Introduces explicit routing

Supports constrained-basedrouting

Supports admission control

Protection capabilities

RSVP-TE to establish LSPs

ISIS and OSPF extensions toadvertise link attributes

Lots more in session RST-2603

IP/MPLS

TE LSP


11/43


Presentation_ID.scr


How MPLS TE Works

Information Distribution

ISIS-TE

OSPF-TE

Path Calculation (CSPF)

Path Setup (RSVP-TE)

Forwarding Traffic downTunnel

Auto-route

Static

PBR

CBTS

Forwarding Adjacency

Tunnel select

IP/MPLS

Head end

Mid-point Tail end


IP/MPLS

DiffServ-Aware Traffic Engineering

(DS-TE)

Per-class constrained-based routing

Per-class admissioncontrol

Best-Effort TE LSP

Low-Latency TE LSP with Reserved BW

Brings per-classdimension to MPLS TE


12/43


Presentation_ID.scr


DiffServ-Aware Traffic Engineering(DS-TE)

Link BW distributed in poolsor Bandwidth Constrains(BC)

Up to 8 BW pools

Different BW pool models

Unreserved BW per TE classcomputed using BW poolsand existing reservations

Unreserved BW per TE classadvertised via IGP

MaximumReservableBandwidth

DS-TE BWAll ocat ion

Link/shaperrate

Forwarding Plane

Control Plane

DiffServBW

All ocat ion


Allclasses

DS-TE Bandwidth Pools

Maximum Allocation Model (MAM)


(MRB)

BW pool applies to one class

Sum of BW pools mayexceed MRB

Sum of total reserved BWmay not exceed MRB

BC2

BC1

BC0

Class2

BC0: 20% Best EffortBC1: 50% PremiumBC2: 30% Voice

Class1

Class3


13/43


Presentation_ID.scr


DS-TE Bandiwdth Pools Russian Dolls Model (RDM)

BC2

BC1

BC0

BW pool applies to one ormore classes

Global BW pool (BC0) equalsMRB

BC0..BCn used forcomputing unreserved BWfor class n

Allclasses

(class1+

Class2+

Class3)Class2+Class3

Class3


(MRB)

BC0: MRB Best Effort + Premium + VoiceBC1: 50% Premium + VoiceBC2: 30% Voice


DS-TE Bandiwdth Pools

Why Russian Dolls Model?

BC2

BC1

BC0

Allclasses

Class1+

Class2Class2


(MRB)

Good match for commonbandwidth allocation inforwarding plane

VoIP gets priority treatment andis unaffected by other traffic:use BC2

Business Data gets preferentialaccess to link vs. BE: use BC1

Best effort may use MRB if otherclasses not fully used, but

should be reduced if lots ofVOIP or Business Data: use BC0

Good isolation betweenclasses, efficient use ofbandwidth


14/43


Presentation_ID.scr


Class-Based Tunnel Selection CBTS

EXP-based selection betweenmultip le tunnels to samedestination

Local mechanism to head-end

Tunnels configured with EXPvalues to carry

Tunnels may be configured asdefault

No IGP extensions

VRF aware

Simplifies use of DS-TEtunnels

Similar operation to ATM/FRVC Bundles

T1

T2

T3

T5

T6

T7

Dst1

Dst2

Dst3

Tunnel7Dst3, *

Tunnel6Dst3, exp 4

Tunnel5Dst2, *

Tunnel4Dst2, exp 2

Tunnel3Dst2, exp 4

Tunnel2Dst1, *

Tunnel1Dst1, exp 4

T4

* Wildcard EXP value

FIB


Dealing with Failure Scenarios

During a failure:

Are you missing your SLA?

For how long?

Link failure may have 2x impacton load

Node / SRLG failu re may have a4x impact on load

Failure impact and durationdependent on:

Network topo logy

backbone QoS design

Load Capacity

Load Capacity

Load vs Capacity in the absence of failure

Load vs Capacity during failure


15/43


Presentation_ID.scr


MPLS TE Fast Re-Route (FRR)

Subsecond recovery againstnode/link failures

Scalable 1:N protection

Bandwidth protection

Greater protectiongranularity

Cost-effective alternative tooptical protection

PE

PE

PE

IP/MPLS

Primary TE LSP

Backup TE LSP


How MPLS TE FRR Works

PE

PE

PE

IP/MPLS

Primary TE LSP

Backup TE LSP

Next-hop backup tunnel forLink Protection

Next-next-hop backuptunnel for Node Protection

Point o f Local Repair (PLR)swaps label and pushesbackup label

Local repair in msecs

Failure detection criti cal for

total repair time PLR sends PathErr to head

end triggering global re-optimization

Point ofLocal Repair

(PLR)

Merge Point(MP)


16/43


Presentation_ID.scr


What should I Use in my Backbone?

Nothing

MPLS TE

MPLS DiffServ

MPLS DiffServ + MPLS TE

MPLS DiffServ + MPLS DS-TE

Any of the above + MPLS TEFRR


Backbone with Nothing

No MPLS DiffServ and No MPLS TE

Resource

Optimization

ServiceDifferentiation

Nothing

A solut ion when:

No d ifferentiation required

No optimization required

Capacity planning as QoS tool

Link over-provisioning to meetall SLAs

Adjust link capacity to

expected link load

Load Capacity


17/43


Presentation_ID.scr


Backbone with MPLS TE

ResourceOptimization


TE

A solut ion when:

No d ifferentiation required

Optimization required

Full mesh or selectivedeployment to avoid over-subscription

Increased network utilization

Adjust link load to actual linkcapacity

Load Capacity


Backbone with MPLS DiffServ

Resource

Optimization


DiffServ

A solut ion when:

Differentiation required


Per-class capacity planning

Same or lower number ofclasses than edge

Adjust class capacity to

expected class load

Load Capacity

Class2

Class3 Load Capacity

Load Capacity


18/43


Presentation_ID.scr


Backbone with MPLS DiffServ and MPLS TE



Load CapacityClass1

Class2

Class3 Load Capacity

Load Capacity

A solut ion when:

Differentiation required


Adjust class capacity toexpected class load

Adjust class load to actualclass capacity forone class

Al ternat ively , adjust link loadto actual link capacity

DiffServ+

TE


Backbone with MPLS DiffServ and MPLS

DS-TE

Resource

Optimization


DiffServ+

DS-TE

Class1

A solut ion when:

Strong differentiation required

Fine optimization required

Adjust class capacity toexpected class load

Adjust class load to actualclass capacity

Load Capacity

Class2

Class3 L oad Cap ac it y

Load Capacity


19/43


Presentation_ID.scr


Bringing MPLS TE FRR into the Mix



NothingFRR

DiffServ+

TE

DiffServ

DiffServ+

DS-TE

TE

Increases resili ency regardlessof backbone QoS design

Stronger SLAs during singlefailure conditions (link, node,SLRG)

Optimization of backupresources

FRR

FRR

FRR

FRR




NothingFRR

DiffServ+

TE

DiffServ

DiffServ+

DS-TE

TEFRR

FRR

FRR

FRR

What Model to Use?

OperationalComplexity

Take your pick !!!As sophist icated as necessary, but not more

EthernetEthernet

ATMATMIPIP

VPNVPN

FrameFrameRelayRelayPPP

PPPIP/MPLS

InternetInternet

VoIPVoIP

IPv6IPv6

PSTNPSTN


20/43


Presentation_ID.scr


MPLS QoSIP Services



QoS for IP Services

PE

PE

PE

CE

CE

CE

IP/MPLSCE

CE

Elaborate DiffServ Edgeimplementation

Access l ink capacity control ledby customer (prone tocongestion)

Trust boundary (SLAenforcement)

Appl ies to both IPv4 and IPv6

Backbone must be able to

support customer SLA Per-customer QoS pol icies

only at the edge

PE

CE


21/43


Presentation_ID.scr


Site IP SLA

Link/shaperrate

Typically between 3 and 5classes (real time, video,interactive, business, BE)

Delay, jitter and lossguarantees for conformingreal-time traffic

Combination of delay andloss guarantees for datatraffic

Sum of committed bandwidth(per-class CIR) not to exceedlink/shaper rate

Addi tional classes no t vis ib leto customer may exist (e.g.management, control traffic)

NA

Low

Low

Low

Loss

NA

NA

NA

Low

Jitter

NANABest Effort

NAZBusiness

LowYInteractive

LowXReal time

DelayCommitted BWClass

Class1

Class2

Class2Class4

Class5


IP SLA between Sites

PE

PE

PE

CE

CE

CE

IP/MPLS

Site-to-network (point-to-cloud) guarantees forconforming traffic

Each s ite may send x% ofclass n to network per SLA

Each site may receive x% ofclass n from network per SLA

No site-to-site (point-to-point)guarantees

PE

CE


22/43


Presentation_ID.scr


IP SLA Enforcement

Managed vs. unmanaged IPservice

Trust boundary on PE forunmanaged service

Trust boundary on CE formanaged service

Trust boundary defines SLAenforcement point

Different QoS design options

Site 1

Site 2

PEPEManagedCE

UnmanagedCE

IP/MPLS


Lets See how SLA enforcement is done

IP QoS Managed Service

PEManagedCE

CEOutput Policy

Classification /Marking

LLQ

WRED

[Shaping]

[LFI / cRTP]

PEOutput Policy

LLQWRED

[Shaping]

[LFI / cRTP]

CE output and PE outputpolicies enforce SLA

Traffic classification andmarking on CE

No input QoS policiesgenerally needed

Explicit-null encapsulationmay be used on CE to avoidremarking customer traffic


23/43


Presentation_ID.scr


IP QoS Unmanaged Service

PEInput Policy

Classification /Marking

Policing

PEOutput PolicyLLQ

WRED

[Shaping]

[LFI / cRTP]

PE input and PE outputpolic ies enforce SLA

Traffic classification andmarkings on PE

CE polic ies requirecoordination with PE policies(e.g. LFI, cRTP, end-to-endlatency)

PEUnmanagedCE

CEOutput Policy


Classifier Policing

?

Excess real time (voice)usually dropped

Excess data marked dow n

Dropping excess data atpolicer would affect many TCPsessions

Limited bandwidth sharingbetween classes withaggregate sub-rate

Voice and video will benefitfrom admission control

Sample PE Input Policy

Unmanaged Service

Real Time

Interactive

Business

BestEffort

Video


24/43


Presentation_ID.scr


Classifier Shaping

Congestion Management

Congestion Avoidance

LinkFragmentation

and Interleaving

(LFI)

Tail drop

Priority Queue

TD

TD

WRED

WRED

?

Sample CE Output Policy Managed Service

Real Time

Interactive

Business

BestEffort

Video

LFI used in slow links to reduce delay and jitter for real-time traffic

WRED used for TCP-friendly packet dropping


How DiffServ Markings Interact

DiffServ Tunneling Modes

EXP POP

PE

DSCPPUSH

MPLS IP

Several models (modes) ofinteraction between thesemarkings

RFC2983 defines models(uniform/pipe) for DiffServ wi thIP tunnels

RFC3270 defines models(uniform/pipe/short-pipe) forMPLS

Only relevant where pop orpush operations take place(both on IP or MPLS packets)

Explicit NULL label may beused for managed services

What is theirrelationship?


25/43


Presentation_ID.scr


MPLS DiffServ Tunneling Modes

CE1 PE1 PE2 CE2

Uniform

Pipe

ShortPipe

IP/MPLSIPIP


Uniform Mode

CE1 PE1 PE2 CE2

IP/MPLS

LabelLabel LabelLabel

Push Packet

remarked

Pop

Packet served onLSP DiffServ Marking(propagated dow n)

IPIP

IP or MPLSpacket

LSP DiffServMarking


26/43


Presentation_ID.scr


Pipe Mode

CE1 PE1 PE2 CE2

IP/MPLS

LSP DiffServMarking

Tunneled DiffServMarking


Push Packetremarked

PopPacket served onLSP DiffServ Marking*

IPIP

* Pipe mode precludes Penultimate Hop Popping (PHP)

IP or MPLSpacket


Short Pipe Mode

CE1 PE1 CE2

IP/MPLS

LSP DiffServMarking

Tunneled DiffServMarking


Push Packet

remarked

Pop

Packet served onTunneled DiffServ Marking

PE2IPIP

IP or MPLSpacket


27/43


Presentation_ID.scr


Local Packet Marking

QoS Group Id and Discardclass forlocal packet marking

Always an input feature(before label POP)

Used to implement uniformand pipe mode

Recommended semantics

QoS group identifies class

Discard class identifies dropprecedence

Discard class can drive WRED

Not all classes will have a dropprecedence (e.g. EF, besteffort)

EXP

QoS Group Id

Discard Class

InputPolicy

OutputPolicyPOP

PE

MPLS IP


DiffServ Tunneling Modes Keep present

EXP POP

PE

DSCPPUSH

MPLS IP

When input policy defines EXPto be imposed, value applies toall imposed labels

If no imposition EXP defined, IPprecedence copied to allimposed labels

EXP maintained during labelswaps

EXP not propagated down by

default during disposition Pipe mode precludes PHP

What is theirrelationship?


28/43


Presentation_ID.scr


AS65001

Prefix1 marking1Prefix2 marking2Prefix3 marking3

AS65000

Some Advanced Configurations QoS Policy Propagation via BGP (QPPB)

Despite the name, no pol iciesare really propagated

Input packet marking (IPprecedence, QoS Group Id)based on

Community

AS Path

IP Prefix

Packet marking happens beforeinput QoS policy

Supports IPv4 and VPNv4addresses

Could add intelligence to IP SLAbetween sites

PE

PE

PE

CE

CE

CE

IP/MPLS PECE

RR

eBGP

iBGP

BGP Table

RIB

FIB

BGP Update

RxPacket

Switch and Mark

TxPacket

Set community65172:1

Mark EF if:community 65172:1

orAS65000


IP QoS in Inter-Provider Environments

IP/MPLS

IP/MPLS

A-PE1

B-PE2

C-PE1

C-PE2

B-CE1

B-CE2

CustomerCarrier

CustomerCarrier

BackboneCarrier

IP VPNCustomer

IP VPNCustomer

IP/MPLS

A-PE2

B-CE2

B-CE1

B-PE1

IP/MPLS

A-PE2

B-PE1

B-PE2

B-CE1

B-CE2

Carrier A Carrier BIP VPNCustomer

IP VPNCustomer

IP/MPLSA-CE2

A-CE1

A-PE1

Complex coordinationbetween providers

Number of classes

Markings

SLAs

End user may receive leastcommon denominator

MPLS DiffServ tunnel modes

supports CsC hierarchies Tunnel modes my differ at

different levels in a hierarchyInter-AS

Carrier Supporting Carriers (CsC)


29/43


Presentation_ID.scr

MPLS QoSLayer-2 Services



QoS for Layer-2 Services

Well-defined SLAs fo rFrame Relay/ATM

Differentiation fo rEthernet services

Point-to-point SLA withexception of VPLS

Backbone must be able tosupport customer SLA

TE-enabled backbone

attractiveHDLCHDLC

ATMATM EthernetEthernet

FrameFrameRelayRelayPPPPPP IP/MPLS

EthernetEthernet


30/43


Presentation_ID.scr


Layer-2 SLA Enforcement

Site 1 Site 2

PEPE

Networkinterface

UserInterface

IP/MPLS

User interface vs networkinterface

Trust boundary on PE for userinterface

Trust boundary on accessnetwork for network interface

Trust boundary defines SLAenforcement point

Different QoS design options


Lets See how SLA enforcement is done

Layer-2 QoS User Interface

PECE

PE input and PE outputpolicies enforce SLA

Drop precedence may bemarked fo r FR / ATM /Ethernet

Output drop precedence (e.g.ATM CLP, FR DE) mark ingwhen input marking notpossible

Ethernet may supportmultiple classes (802.1p b its)

UserInterface

PEInput Policy

Policing

[Marking]

PEOutput Policy

Queuing (LLQ)

WRED

[Marking]

[shaping]


31/43


Presentation_ID.scr


Layer-2 QoS Network Interface

PECE

NetworkInterface

Access Netw orkInput Policy

Policing

[Marking]

PEInput Policy

[Marking]

Access Netw orkOutput Policy

Queuing (LLQ)

Dropping (WRED)

[Shaping]

PEOutput Policy

SP enforces SLA on accessnetwork

PE may only need simpleaggregate policies


PUSH

Encapsulation Details

Layer-2 QoS Frame Relay

Incoming traffic classified byDE or DLCI for DLCI-to-DLCImode

Input policer may exclude DE-marked frames from CIRmetering

Several classes of service maybe imp lemented

CIR (EIR=0)

CIR+EIR

CIR=EIR=0

Output DE marking when inputmarking not possible

FECN/BECN markingsuppor ted on egress PE only

Control word carries originalDE/FECN/BECN values

PE

MPLS FrameRelay

EXP

QoS Group Id

DiscardClass

InputPolicy

OutputPolicyPOP

FR DE

InputPolicy

DLCI

EXPOutputPolicy

FR DE


32/43


Presentation_ID.scr


Layer-2 QoS ATM

Incoming traffic classified by CLP

Support for all service categories(CBR, rt-VBR, nrt-VBR, ABR, UBR)

Different traffic conformancesuppor ted (CBR.1, VBR.1, VBR.2,VBR.3, UBR.1, UBR.2)

ATM TM 4.0 meter ing parametersconverted to MQC (token-bucket)policer parameters

CIR = SCR*53*8

PIR = PCR*53*8

bc/be = CDVT*(CIR+53)*8

bc = MBS*PCR/SCR

Output queuing handled by ATM

hardware Cell-relay transport f or delay

sensitive traffic

Control word carries original CLPand EFCI values

PUSH

PE

MPLS ATM

EXP

DiscardClass

InputPolicy

OutputPolicyPOP

InputPolicy CLPEXP

OutputPolicy

CLP


Layer-2 QoS Ethernet

Incoming traffic classified byCoS (802.1p) or VLAN Id for802.1Q encapsulation

Service characteristics beingproposed at the MetroEthernet Forum (BW Profile:CIR, CBS, EIR, EBS, CF, CM)

Site-to-network (point-to-cloud) SLA for VPLS

Control word does not carryany CoS (802.1p) info

PUSH

PE

MPLS Ethernet

EXP

QoS Group Id

DiscardClass

InputPolicy

OutputPolicyPOP

CoS

InputPolicy

VLAN ID

EXPOutputPolicy

CoS


33/43


Presentation_ID.scr


Layer-2 QoS PPP/HDLC

PUSH

No layer-2 marking to set orclassify on

No standard service definitionbut classes of service arepossible

PE

MPLS PPP/HDLC

EXP

QoS Group Id

DiscardClass

InputPolicy

OutputPolicyPOP

InputPolicyEXP

OutputPolicy


Coupling Layer-2 Services with MPLS TE

Tunnel Selection

Static mapping betweenpseudo-wire and TE Tunnelon PE

Implies PE-to-PE TEdeployment

TE tunnel defined aspreferred path for pseudo-wire

Traffic will fall back to peerLSP if tunnel goes down

PE

PE

PE

CE

CE

CE

IP/MPLS

TE LSP

Layer 2 Circuit

Layer 2 Circuit

CE

CE


34/43


Presentation_ID.scr


Are We There Yet?

Were prettymuch done!

MPLS QoSManagement



35/43


Presentation_ID.scr


Some Monitoring Tools Monitor ing Utilization Level (x%)

Interface MIB

MPLS LSR MIB

Cisco Class Based QoS MIB

Netflow

NetFlow BGP Next Hop TOSAggregat ion

MPLS-Aware Netflow

BGP Policy Accounting

CommunitiesAS path

IP prefix

P

P

PE

PE

POP

PE

Server Farm Server Farm

AS65001

PE

PE

PE

P

P

POP

AS65002 AS65003

Measuring internal and external traffic matrix


Cisco Class-Based Qos MIB

Primary per-link accounting mechanismfor QoS:

Classification (cbQosMatchStmtStats/cbQosClassMapStats)

Marking (cbQosClassMapStats)

Policing (cbQosPoliceStats)

Shaping (cbQosTSStats)

Congestion management(cbQosQueueingStats)

Congestion avoidance (cbQosREDClassStats)

QoS policy must be applied tointerface/PVC for accounting to happen

Read access to configuration andstatistical information for MQC

Management Station


36/43


Presentation_ID.scr


Traditional NetFlow(IP to MPLS)

Egress MPLS NetFlow(MPLS to IP)

MPLS-Aware NetFlow(MPLS to MPLS)

Output Sampled NetFlow(MPLS to IP, IP to IP)

NetFlow MPLS Features Overview

PE P PE

IP/MPLS

Lots of detailed info in session NMS-2032


AS65001

Prefix1 traffic-idx1Prefix2 traffic-idx2Prefix3 traffic-idx3

AS65000


Assign counters (traf fic-index) toIP traffic based on:

Community

AS Path

IP Prefix

Up to 64 counters (traffic-index)

Supports IPv4 and VPNv4addresses

Similar in concept/operation toQPPB, but accounting instead ofmarking

PE

PE

PE

CE

CE

CE

IP/MPLS PECE

RR

eBGP

iBGP

BGP Table

RIB

FIB

BGP Update

RxPacket

Switch and count

TxPacket

Set community65172:1

Count packets if:community 65172:1

orAS65000


37/43


Presentation_ID.scr


Round TripTime

NetworkJitter

Uni-directionalMeasurements

ConnectivityPacketLoss

FTP DNS DHCP TCPJitter ICMPPathJitter UDPDLSW HTTP

NetworkPerformanceMonitoring

Service LevelAgr eement

(SLA)Monitoring

NetworkAss essm ent

MPLSMonitoring

VoIPMonitoringAvai labi lit y

TroubleShooting

Operations

Measurement Metrics

App licat ions

SAA

SAA

SAA

IP Server

MIB Data

Acti ve Generat ed Traff ic

Destination

Source

Defined Packet Size, SpacingCOS and Protocol

Responder

Performance Monitoring Cisco IOS SAA Today

H323 RTP

Soon

LSPVoIP

MIB Data

Source


SAA Responder

1.Send train of packets withconstant Interval

2.Receive train of packets atInterval impacted by Network

3.Time stamp when RxedIncrement Rx CountDelta Time

Source

4.Compute: Per-direction OWD (one-way delay) Per-direction inter-packet delay (Jitter) Per-direction packet loss

SAA Jitter Operation Example


38/43


Presentation_ID.scr


SAA Reaction Condit ions

SAA event triggers

Connection loss / timeout

Latency (one way, round tr ip)

Jitter (one way, round tr ip)

Loss (one way, round tri p) MOS

ThresholdViolation

Thresholdviolation

ThresholdViolation

No Alert

100ms

50ms

Aler tAler t

Resolution

SAA Triggers can generate SNMP trap or another SAA probe

Trigger threshold definitions

Immediate

Average

Consecutive

X out of Y times


MPLS LSPPing/Trace

VCCV

SAA Probe

Generation

SAA MIB

Data Storage

Reaction Configuration

Thresholds

NMS

ECMP Tree Trace

Echo and Path TracingRTT, Packet Loss,Jitter Statistics

TrapsSyslog

Cisco SAA MPLS Embedded Management

Auto-Con fig / CLI / MIB

MPLS L3 VPNMPLS L2 VPN


39/43


Presentation_ID.scr


Key Cisco Partners

SAASAANetFlowNetFlow

Flow-Tools

Cisco NetFlow Collector IP Solution Center Internetworking Performance

Monitor (IPM)


IP Solution Overview

Unified mgmt for MPLS VPN, L2VPN, Security and MPLS TE


40/43


Presentation_ID.scr


ISC QoS Management Features

QoS provisioning on accesslink (both CE and PE)

Internal cons train matrixcheck software and hardwaredependencies

Support for pre-MQC QoSfunctionality

QoS provisioning onbackbone links using SmartTemplate utilit y

PE

PE

PE

CE

CE

CE

IP/MPLS

PE

CE

classificationmarkingpolicingshapingcongestion managementcongestion avoidanceLFIcRTP


Summary

Technology OverviewMPLS support of Diff Serv

MQC

Backbone InfrastructureDiffServ

TE/FRR

DS-TE

IP ServicesSLAs

DiffServ Tunneling Modes

Layer-2 ServicesFrame Relay

ATM

Ethernet

PPP/HDLC

ManagementMIBs

Netflow


SAA

EthernetEthernet

ATMATMIPIP

VPNVPN

FrameFrameRelayRelayPPPPPP IP/MPLS

InternetInternet

VoIPVoIP

IPv6IPv6

PSTNPSTN


41/43


Presentation_ID.scr

Q and A



Reference Materials

MPLS QoS Q&Ahttp://www.cisco.com/warp/public/cc/pd/iosw/tech/mpotc_qp.htm

Cisco IOS 12.0S/12.2S QoS Configuration Guideand Command Referenceshttp://www.cisco.com/

Multi-Protocol Label Switching (MPLS) Support ofDifferentiated Services RFC3270

http://www.ietf.org/rfc/rfc3270.txt


42/43


Presentation_ID.scr


Assoc iated Sessions

RST-1601 - Introduction to Multiprotocol Label Switching (MPLS)

RST-3606 - Troubleshooting MPLS VPNs

RST-2602 - Deploying MPLS VPNs

RST-2603 - Deploying MPLS Traffic Engineering

RST-2606 - Understanding Convergence in MPLS VPN Networks

RST-2T09 - Advanced Concepts and Developments in MPLS

RST-3605 - Troubleshooting MPLS Networks

RST-4607 - Advanced Topics and Future Directions in MPLS

NMS-4012 - MPLS Embedded Management Tools NMS-2032 - Netflow for Accounting, Analysis and A ttack


Recommended Reading

IP Quality of ServiceISBN 1578701163

Traffic Engineering with MPLSISBN 1587050315

MPLS and VPN ArchitecturesISBN 1587050021


43/43


Documents

Prod Presentation0900aecd8031280f