1© 2001, cisco systems, inc. service provider qos providing e2e guarantees vijay krishnamoorthy...

1© 2001, Cisco Systems, Inc.

Service Provider QoSService Provider QoSProviding e2e GuaranteesProviding e2e Guarantees

Vijay KrishnamoorthyVijay Krishnamoorthy

Cisco IOS Technologies DivisionCisco IOS Technologies Division

April 2001April 2001


AgendaAgenda

• What is QoS?

• QoS Models

• Differentiated Services - DiffServ

• DiffServ in MPLS Networks

• MPLS Traffic Engineering

• DiffServ-Aware Traffic Engineering (DS-TE)

• DS-TE Solutions

• QoS Management

• Summary


What is Quality of Service?What is Quality of Service?ARM Your Network!ARM Your Network!

“

”

The Pragmatic Answer: QoS is Advanced Resource ManagementThe Technical Answer: The Resources!!

Set of techniques to manage:• Delay• Delay Variation (Jitter)• Bandwidth• Packet Loss


The Value Proposition!The Value Proposition!

• Offer Any to Any Differentiated Services for Profitability:

Premium-Class Service – (E.g.: VoIP, Multicast Stock Quotes, etc.)

Business-Class Service – (E.g.: SAP,Oracle,Citrix, etc.)

Best-Effort Service – (E.g.: Database Replication, Backups, etc.)

• Icing on the profitability cake Point-to-Point QoS Guarantees:

P2P guarantees for Voice over IP trunks.

P2P guarantees for highly critical data traffic.

• Revenue in addition to Basic MPLS VPN & Internet Service!


Today’s Basic Internet Access Basic Internet Access @ 768 kpbs…………

Managed Internet Access Access prioritization by user, group………...Priority access during times of congestion…Usage reporting……………………………….

Business Applications (ASP)Priority to each customer’s requirements…..

Streaming ServicesBlocking delivery of undesirable services….

VPN ServicesLow cost, software based ……………………

Monthly Revenue/Margin$500/$50

$75/$60$75/$60$75/$60

$100/$90

$50/$40

$150/$100TOTAL MARGIN POTENTIAL:$460/customer = +820%

Source: Session M16C, SuperNet 2001

Service Provider Revenue/Margin Service Provider Revenue/Margin PotentialPotential


“Money and sex, storage and bandwidth: only too much is ever enough”

•Arno Penzias - Former Head of Bell Labs, and Nobel prizewinner

“The worldwide services market is about $1 trillion US. By 2005 it will be around $5-7 trillion. Look for growth in new services.”

•Vinod Khosola - Kleiner Perkins Ventures

”According to CIMI Corporation, by 2010, 67% of transactions will be on value networks, not the

Internet”

“

”

But…but… Bandwidth…...But…but… Bandwidth…...


So, What Will Fill Up The Pipe?So, What Will Fill Up The Pipe?

Source: Internet2 QBone WG


QoS ModelsQoS Models



The IP QoS PendulumThe IP QoS Pendulum

No state

Best Effort

Per-flow state

IntServ / RSVP

Aggregatedstate

DiffServ

1. The original IP service2. First efforts at IP QoS

3. Seeking simplicity and scale

Time

4. Bandwidth Optimization & e2e SLAs ((IntServ+DiffServ+ Traffic Engineering))


PR

OV

ISIO

NIN

G &

MO

NIT

OR

ING

PR

OV

ISIO

NIN

G &

MO

NIT

OR

ING

VPNsVPNsMultimediaVideo Conference,

Collaborative Computing

MultimediaVideo Conference,

Collaborative Computing

Mission Critical Services

Mission Critical ServicesVoIPVoIP

HybridHybridMPLSMPLSDiffServDiffServIntServIntServ

Signaling Techniques (RSVP, DSCP*, ATM (UNI/NNI))Signaling Techniques (RSVP, DSCP*, ATM (UNI/NNI))

Link Efficiency Mechanisms (Compression, Fragmentation)Link Efficiency Mechanisms (Compression, Fragmentation)

Congestion Avoidance Techniques (WRED)Congestion Avoidance Techniques (WRED)

Congestion Management Techniques (WFQ, CBWFQ, LLQ)Congestion Management Techniques (WFQ, CBWFQ, LLQ)

Classification & Marking Techniques (DSCP, MPLS EXP, NBAR, etc.)Classification & Marking Techniques (DSCP, MPLS EXP, NBAR, etc.)

FrameRelay

FrameRelay

PPPHDLC

PPPHDLC SDLC

SDLCATM, POSATM, POS FE,Gig.E

10GE

FE,Gig.E 10GE

WirelessFixed,Mobile

WirelessFixed,Mobile

BroadBandCable,xDSL

BroadBandCable,xDSL

PO

LIC

Y-B

AS

ED

NETW

OR

KIN

GP

OLIC

Y-B

AS

ED

NETW

OR

KIN

G

Traffic Conditioners (Policing, Shaping)Traffic Conditioners (Policing, Shaping)

The Cisco QoS FrameworkThe Cisco QoS Framework


Differentiated Services Differentiated Services Architecture - DiffServArchitecture - DiffServ



Differentiated ServicesDifferentiated ServicesThe IETF DiffServ ModelThe IETF DiffServ Model

• Use 6 bits in IP header to sort traffic into “Behavior Aggregates”…AKA Classes!

• Defines a number of “Per Hop Behaviors - PHBs”

• Two-Ingredient Recipe:

Condition the Traffic at the Edges

Invoke the PHBs in the Core

• Use PHBs to Construct Services such as Virtual Leased Line!


VersionLengthVersionLength

ToSToS1 Byte1 ByteToSToS

1 Byte1 Byte LenLen

Standard IPV4: Bits 0-2 Called IP Precedence (Three MSB)(DiffServ Uses Six ToS bits…: Bits 0-5, with Two Reserved)Layer 3

IPV4

IDID offsetoffset TTLTTL ProtoProto FCSFCS IP-SAIP-SA IP-DAIP-DA DataData

Referred to as Packet Classification or Coloring

Layer 3 Mechanisms Provide End-to-End Classification

The Hook for IPv4 ClassificationThe Hook for IPv4 Classification


IPv4 ToS vs. DS-FieldIPv4 ToS vs. DS-Field


Defined PHBsDefined PHBs

• Expedited Forwarding (EF): RFC2598

dedicated low delay queue

Comparable to Guaranteed B/W in IntServ

• Assured Forwarding (AF): RFC2597

4 queues 3 drop preferences

Comparable to Controlled Load in IntServ

• Class Selector: Compat. with IP Prec

• Default (best effort)


AF PHB Group DefinitionAF PHB Group Definition

• 4 independently-forwarded AF classes

• Within each AF class, 3 levels of drop priority! This is very useful to protect conforming to a purchased, guarantee rate, while increasing chances of packets exceeding contracted rate being dropped if congestion is experienced in the core.

AF Class 1: 001dd0

AF Class 2: 010dd0

AF Class 3: 011dd0

AF Class 4: 100dd0

Eg. AF12 = Class 1, Drop 2, thus “001100”

dd = drop preference


The DiffServ Traffic ConditionerThe DiffServ Traffic Conditioner

•Classifier: selects a packet in a traffic stream based on the content of some portion of the packet header•Meter: checks compliance to traffic parameters (e.g., Token Bucket) and passes result to marker and shaper/dropper to trigger particular action for in/out-of-profile packets •Marker: Writes/rewrites the DSCP value•Shaper: delay some packets for them to be compliant with the profile


The DiffServ ArchitectureThe DiffServ Architecture(RFC-2475)(RFC-2475)


Cisco IOS DiffServCisco IOS DiffServ

• Cisco IOS 12.1(5)T+ & 12.2+ are fully compliant with all the Core DiffServ RFCs (RFCs: 2474,2475,2597,2598)

• Compliant Platforms*:

C36xx, C72xx, C75xx - Now

More Platforms in the Near Future...


An Application NoteAn Application Note



Source PredictabilitySource Predictability

• TCP will keep at most a certain amount of traffic in flight

We say it is “elastic”—rate is proportional to latency

• Voice will send only and exactly as fast as the coding algorithm permits (Also Video to an extent)

We say it is “inelastic”


TCP Flow StatisticsTCP Flow Statistics

• >90% of sessions have ten packets each way or less

Transaction mode (mail, small web page)

• >80% of all TCP traffic results from <10% of the sessions, in highrate bursts

It is these that we worry about managing


Behavior of a High-Throughput / Behavior of a High-Throughput / Bulk-Transfer TCP SessionBulk-Transfer TCP Session

0

5

10

15

20

25

30

35

40

45

0 10 20 30 40 50

Slow StartExponential Growth

Congestion Avoidance PhaseLinear Growth


VoIP Delay BudgetVoIP Delay Budget

Cumulative Transmission Path Delay

Time (msec)Time (msec)Time (msec)Time (msec)

0000 100100100100 200200200200 300300300300 400400400400

Satellite QualitySatellite Quality

Fax Relay, BroadcastFax Relay, BroadcastHigh QualityHigh Quality

Delay Target (max)Delay Target (max)Delay Target (max)Delay Target (max)

500500500500 600600600600 700700700700 800800800800

ITU’s G.114 Recommendation = 0–150 msec 1-Way Delay


Application QoS RequirementsApplication QoS Requirements

VoiceVoice FTPFTP ERP andMission-Critical

ERP andMission-Critical

BandwidthBandwidth Low toModerateLow toModerate

Moderateto HighModerateto High

LowLow

Random Drop SensitiveRandom Drop Sensitive LowLow HighHigh ModerateTo HighModerateTo High

Delay SensitiveDelay Sensitive HighHigh LowLow Low toModerateLow toModerate

Jitter SensitiveJitter Sensitive HighHigh LowLow ModerateModerate


DiffServ & MPLSDiffServ & MPLS



DiffServ Scalability via DiffServ Scalability via AggregationAggregation

1000’s of flows

Diff-Serv:

Aggregated Processing in Core

Scheduling/Dropping (PHB) based on DSCP

Diff-Serv:


Scheduling/Dropping (PHB) based on DSCP

Diff-Serv:

Aggregation on Edge

Many flows associated with a Class (marked with DSCP)

Diff-Serv:

Aggregation on Edge

Many flows associated with a Class (marked with DSCP)

DiffServ scalability comes from:- aggregation of traffic on Edge- processing of Aggregate only in Core


MPLS Scalability via AggregationMPLS Scalability via Aggregation

1000’s of flows

MPLS:


Forwarding based on label

MPLS:


Forwarding based on label

MPLS:

Aggregation on Edge

Many flows associated with a Forwarding Equivalent Class (marked with label)

MPLS:

Aggregation on Edge

Many flows associated with a Forwarding Equivalent Class (marked with label)

MPLS scalability comes from:- aggregation of traffic on Edge- processing of Aggregate only in Core


MPLS & DiffServ - The Perfect MPLS & DiffServ - The Perfect Match!Match!

1000’s of flows

MPLS: flows associated with FEC, mapped into one label

MPLS: flows associated with FEC, mapped into one label

MPLS: Switching based on Label

MPLS: Switching based on Label

DS: Scheduling/Dropping based on DSCP

DS: Scheduling/Dropping based on DSCP

DS: flows associated with Class, mapped to DSCP

DS: flows associated with Class, mapped to DSCP

Because of same scalability goals, both models do:- aggregation of traffic on Edge- processing of Aggregate only in Core


• DSCP field is not directly visible to MPLS Label Switch Routers (they forward based on MPLS Header)

• Information on DiffServ must be made visible to LSR in MPLS Header (using EXP field / Label)

0 1 2 30 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| TTL |

DSCP

IPv4 Packet MPLS Header

Non-MPLS Diff-Serv Domain

MPLS Diff-Serv Domain

DSCP

MPLS - So What’s New?MPLS - So What’s New?The Shim Header!!The Shim Header!!


DiffServ DiffServ oo MPLS : “Coloring” MPLS : “Coloring” MPLS FramesMPLS Frames

• This describes how “DiffServ” information is conveyed to LSRs in MPLS Header

• Two methods:

– E-LSP {{ Cisco IOS 12.1(5)T, 12.0(11)ST }}

“Queue” inferred from Label and EXP field

“Drop priority” inferred from label and EXP field

– L-LSP {{ Planned, once an RFC }}“Queue” inferred exclusively from Label

“Drop priority” inferred from EXP field


• E-LSPs can be established by various label binding protocols (LDP or RSVP)…no new Signalling Needed.

• Example above illustrates support of EF and AF1 on a single E-LSP (Note: This is the plain old LSP established for MPLS Switching)

Note: EF and AF1 packets travel on single LSP (single label) but are enqueued in different queues (different EXP values)

• Queue & Drop Precedence is selected based on EXP

E-LSP

LSRLDP/RSVP LDP/RSVP

EF

AF1

The E-LSP Story...The E-LSP Story...


• L-LSPs can be established by various label binding protocols (LDP or RSVP)…EXTENSIONS REQUIRED!

• Example above illustrates support of EF and AF1 on separate L-LSPs

– EF and AF1 packets travel on separate LSPs and are enqueued in different queues (different label values)

– Queue selected based on Label, Drop Precedence Selected with Optional EXP field.

L-LSPs

LSR

LDP/RSVP LDP/RSVP

L- LSP Example (Tomorrow)L- LSP Example (Tomorrow)Supporting 64 Classes!Supporting 64 Classes!


Cisco DiffServCisco DiffServ o o MPLSMPLS

• Cisco IOS 12.1(5)T

• C72xx, C75xx, C12xxx [12.0(ST)]

• MPLS QoS Enhancements*

• Operate exclusively on EXP bits

• Leave the IP ToS Byte Untouched

• QoS is QoS!

– Some New Stuff, But Same Goals!

– Service the Applications!!


The QoS is In the Details!The QoS is In the Details!

• So, What’s Changed?:

Can Classify based on the EXP bits (MQC/CAR)

Can Mark the EXP bits (MQC/Policer/CAR)

WRED & WFQ & MDRR act on EXP bits (instead of Precedence/DSCP)


A Note on CoS Translation…A Note on CoS Translation…(Preservation of Classification e2e)(Preservation of Classification e2e)

• Developed as flexible translation:• CoS = {IP Prec., DSCP, EXP, ATM CLP, F.Relay DE-Bit, 802.1Q/p}• CoS translation = Translation from Any (Except ATM CLP) to Any

• Extensions to the “Modular QoS CLI”:1) Extended “matches” for “class-maps”:

match fr-de match cos <0-7>match ip precedence nmatch ip dscp nmatch mpls exp <0-7>

2) Extended “sets” for “policy-maps”:

set atm-clpset fr-deset cos <0-7> set ip precedence nset ip dscp nset mpls exp n


IP

MQC CoS Translation: An MQC CoS Translation: An ExampleExample

class-map inputc match ip prec ppolicy-map inputp

class inputcset qos-group q

Incoming interface> service-policy input inputp

LSP

LSRLDP LDP

MPLS

Incoming IP packets with Prec=p to be transmitted with EXP=e

class-map outputc match qos-group qpolicy-map outputp

class outputcset mpls exp e

Outgoing interface> service policy output outputp


MPLS Traffic EngineeringMPLS Traffic Engineering



The “Fish” ProblemThe “Fish” Problem

R8

R1

R5

R2

R3R4

R7R6

•IP Uses Shortest Path Destination-Based Routing•Shortest Path May Not Be the only path•Alternate Paths May Be under-Utilized while the shortest Path Is over-Utilized


An LSP TunnelAn LSP Tunnel (A (A ConstrainedConstrained MPLS Label Switched Path) MPLS Label Switched Path)

R8

R1

R5

R2

R3R4

R7R6

Labels, Like VCIs (ATM) Can Be Used to Establish Virtual CircuitsNormal Route R1->R2->R3->R4->R5Tunnel: R1->R2->R6->R7->R4


LSP Tunnel SetupLSP Tunnel Setup(a.k.a Traffic Engineering [TE] Tunnel)(a.k.a Traffic Engineering [TE] Tunnel)

22

4917

R8

R2

R6

R3

R4

R7

R1R5

R9

Setup: Path (R1->R2->R6->R7->R4->R9) Tunnel ID 5, Path ID 1Setup: Path (R1->R2->R6->R7->R4->R9) Tunnel ID 5, Path ID 1Setup: Path (R1->R2->R6->R7->R4->R9) Tunnel ID 5, Path ID 1Setup: Path (R1->R2->R6->R7->R4->R9) Tunnel ID 5, Path ID 1

Reply: Communicates Labels and Label OperationsReply: Communicates Labels and Label OperationsReserves Bandwidth on Each LinkReserves Bandwidth on Each Link

Reply: Communicates Labels and Label OperationsReply: Communicates Labels and Label OperationsReserves Bandwidth on Each LinkReserves Bandwidth on Each Link

PopPop

32


Real-World MPLS TE Use!Real-World MPLS TE Use!

POP4

POP

POPPOP

POP2

POP1

WAN area

Find route & set-up tunnel for 10 Mb/s from POP2 to POP4



MPLS TE & QoS – MPLS TE & QoS – The RelationshipThe Relationship

• MPLS TE designed as tool to improve backbone efficiency independently of core QoS techniques:

MPLS TE compute routes for aggregates across all PHBs.

A Single Chunk of Bandwidth requested for the Tunnel

MPLS TE performs admission control over a global b/w pool.

Un-aware of bandwidth allocated to each Class / PHB

• MPLS TE and MPLS DiffServ:

Can run simultaneously in a network.

Can provide their own individual benefits

TE distributes aggregate load

DiffServ provides differentiation)

Are unaware of each other


DiffServ-Aware DiffServ-Aware Traffic EngineeringTraffic Engineering



Delay/Load Trade-OffDelay/Load Trade-Off

PercentagePriorityTraffic

Delay

0% 100% %

VoiceTarget

DataPremiumTarget

GoodBest-EffortTarget

If I can keep EF traffic < % , I will keep EF delay under M1 msIf I can keep AF1 traffic < % , I will keep AF1 delay under M2 ms

%


Motivation for DiffServ-Aware TEMotivation for DiffServ-Aware TE(DS-TE)(DS-TE)

• Thus, with DiffServ, there are additional constraints to ensure the QoS of each class:

- Good EF behavior requires that aggregate EF traffic is less than small % of link

- Good AF behaviors requires that aggregate AF traffic is less than reasonable % of link

• =>Cannot be enforced by current Aggregate TE

• => Requires DiffServ-Aware TE

• - Constraint Based Routing per Class with different bandwidth constraints

• - Admission Control per Class over different bandwidth pools (ie bandwidth allocated to class queue)


The Trouble With DiffServThe Trouble With DiffServ(We Want it All, We Want it Now!)(We Want it All, We Want it Now!)

• As currently formulated, DiffServ is strong on simplicity and weak on guarantees

• Virtual Leased Line using EF is quite firm, but how much can be deployed?

No topology-aware admission control mechanism

• Example: How do I reject the “last straw” VoIP TRUNK that will degrade service of calls & trunks currently active?


DiffServ-Aware TE:DiffServ-Aware TE:Protocol ComponentsProtocol Components

• Current IGP(*) extensions for TE:

advertise “unreserved TE bandwidth” (at each preemption level)

• Proposed IGP(*) extensions for DS aware TE:

Class-Types= group of DiffServ classes sharing the same bandwidth constraint (e.g. AF1x and AF2x)

advertise “unreserved TE bandwidth” (at each preemption level) for each Class-Type

(*) OSPF and ISIS


DiffServ-Aware TE:DiffServ-Aware TE:Protocol ComponentsProtocol Components

• Current LSP-signalling (*) extensions for TE:

at LSP establishment signal TE tunnel parameters (label, explicit route, affinity , preemption,…)

• Proposed LSP-signalling (*) extensions for DS aware TE:

also signal the Class-Type

perform Class-Type aware CAC

(*) RSVP-TE and CR-LDP


DiffServ - Aware TE:DiffServ - Aware TE:Protocol ComponentsProtocol Components

• Current Constraint Based Routing for TE:

compute a path such that on every link :

- there is sufficient “unreserved TE bandwidth”

• Proposed Constraint Based Routing for DS aware TE:

same CBR algorithm but satisfy bandwidth constraint over the “unreserved bandwidth for the relevant Class-Type” (instead of aggregate TE bandwidth)


DS-TE Standardization StatusDS-TE Standardization Status

• Standardization effort initiated 2 IETFs ago

• Internet Drafts submitted at Dec 2000 IETF:

draft-ietf-mpls-diff-te-reqts-01.txt

draft-ietf-mpls-diff-te-ext-00.txt

draft-lefaucheur-diff-te-ospf-00.txt

draft-lefaucheur-diff-te-isis-00.txt


Aggregate TE in a Best Effort Aggregate TE in a Best Effort NetworkNetwork

POP4

POP

POPPOP

POP2

POP1

WAN area




Aggregate TE in a DiffServ Aggregate TE in a DiffServ NetworkNetwork

POP4

POP

POPPOP

POP2

POP1

WAN area

Find route & set-up tunnel for 20 Mb/s (aggregate) from POP1 to POP4

Find route & set-up tunnel for 10 Mb/s (aggregate) from POP2 to POP4


DiffServ-Aware Traffic DiffServ-Aware Traffic EngineeringEngineering

POP4

POP

POPPOP

POP2

POP1

WAN area

Find route & set-up tunnel for 5 Mb/s of EF from POP1 to POP4


Find route & set-up tunnel for 15 Mb/s of BE from POP1 to POP4



DS-TE ApplicationsDS-TE Applications

Guaranteed Bandwidth ServicesGuaranteed Bandwidth Services



DiffServ-Aware Traffic DiffServ-Aware Traffic EngineeringEngineering

POP4

POP

POPPOP

POP2

POP1

WAN area






MPLS Guaranteed BandwidthMPLS Guaranteed Bandwidth

• Combining MPLS DiffServ & DS-TE to achieve strict point-to-point QoS guarantees

• A new “sweet-spot” on the QoS Spectrum

No state

Best effort

Per-flow state

RSVP v1/Intserv

Aggregatedstate

DiffServ

MPLS DiffServ + MPLS DS-TE

Aggregated State (DiffServ)Aggregate Admission Control (DS-TE)

Aggregate Constraint Based Routing (DS-TE)

MPLS guaranteed bandwidth


MPLS Guaranteed Bandwidth MPLS Guaranteed Bandwidth

• “Guaranteed QoS” is a unidirectional point-to-point bandwidth guarantee from Site-Sx to Site-Sy: Point-to-Point

• “Site” may include a single host, a “pooling point”, etc.

10.2

10.1

11.5

11.6

CE

CE

CE

CE

N1 Mb/s guarantee

N2 Mb/s guarantee


MPLS Guaranteed Bandwidth MPLS Guaranteed Bandwidth

• “Guaranteed QoS” is a unidirectional point-to-point bandwidth guarantee from Site-Sx to Site-Sy

• “Site” may include a single host, a “pooling point”, etc.

10.2

10.1

11.5

11.6

CE

CE

CE

CE

N1 Mb/s guarantee

N2 Mb/s guarantee

DS-TE LSP for AF or EF, used to transport guaranteed bandwidth traffic edge-to-edge


DS-TE ApplicationsDS-TE Applications

Voice over MPLS TrunksVoice over MPLS Trunks



Target ApplicationsTarget Applications

• Voice Trunking

Solution 1: Toll Bypass with Voice Network

Solution 2: Toll Bypass with Voice/Data Converged Network

Solution 3: Toll Bypass with VoIP Network

• Virtual Leased Lines

Solution 4: Virtual Leased Lines – Serial Links

Solution 5: Virtual Leased Lines – Frame Relay

Solution 6: Virtual Leased Lines – ATM


Solution 1: Toll Bypass with Voice Solution 1: Toll Bypass with Voice NetworkNetwork

PE

PBX with

Packet Interfac

e

PBX with Packet

Interface

PSTN – Traditional

TDM Network

Traditional

Telephony

Traditional

Telephony Toll Bypass

QoS on PE Router

Solution Requirements

Mapping Traffic to Tunnels

Diffserv Aware Traffic Engineering

QoS on Core Routers

PEGB Tunnel

+ + =

Class 5legacy

switches


Solution 2: Toll Bypass with Voice/Data Solution 2: Toll Bypass with Voice/Data Converged NetworkConverged Network

PE

CE


TDM Network

Enterprise LAN

Enterprise LAN

Toll Bypass

QoS on PE Router




QoS on Core Routers

CE

QoS on CE Router

PEGB Tunnel

PBX with Circuit Emulation Interface

+ + + =

Class 5legacy

switches


Solution 3: Toll Bypass with VoIP Solution 3: Toll Bypass with VoIP NetworkNetwork

PE

CE

IP Phone


TDM Network

Enterprise LAN

Enterprise LAN

Toll Bypass

QoS on PE Router




QoS on Core Routers

CE

QoS on CE Router

Multi-Service Switch

Multi-Service Switch

IP Phone

PEGB Tunnel

+ + + =

Class 5legacy

switches


Voice Trunking - SummaryVoice Trunking - Summary

PE

Central OfficeCentral

OfficeTradition

al Telephon

y

Traditional

Telephony

Toll Bypass

PEGB Tunnel

VoIP Gatewa

y

VoIP Gateway

MPLS Network

PE

PE

Regular TE Tunnel

CE

Enterprise LAN

CE

Enterprise LAN

PEPE

Voice Trunking

VPN Service

Internet Service Enterprise LAN

Internet Access Router

Internet Access RouterEnterpris

e LAN


TDM Network

Class 5legacy

switches


Solution 4: Virtual Leased Lines – Solution 4: Virtual Leased Lines – Serial LinksSerial Links

PE

MPLS Backbone

Serial IP or PPP or

HDLC over MPLS

PEDS-TE Tunnel

CE CE

Serial IP or PPP or

HDLC over MPLS

Serial Link Serial

Link

Virtual Leased Line

(DS-TE + QoS)


Solution 5: Virtual Leased Lines – Solution 5: Virtual Leased Lines – FR NetworksFR Networks

PE

MPLS Backbone

PE

Frame Relay

CPE Router, FRAD

Frame Relay

CPE Router, FRAD

Frame Relay DLCI

Any Transport over MPLS

(AToM) Tunnel

DS-TE TunnelVirtual Leased Line (DS-TE + QoS)


Solution 6: Virtual Leased Lines – Solution 6: Virtual Leased Lines – ATM NetworksATM Networks

PE

MPLS Backbone

PE

ATM

CPE Router

ATM

CPE Router

ATM Virtual Circuits

Any Transport over MPLS

(AToM) Tunnel

DS-TE TunnelVirtual Leased Line (DS-TE + QoS)


QoS ManagementQoS Management



Network servicelevel verification

CW2000 SMSCW2000 SMS

Complete Service ManagementComplete Service ManagementCONFIGURECONFIGURE VERIFICATION VERIFICATION TROUBLESHOOT TROUBLESHOOT

Qos networkpolicy configuration

Per-device trafficclass monitoring

Per-device traffic class configuration

Dev

ice

Net

wo

rk W

ide

Dev

ice

Net

wo

rk W

ide XML

Service leveltroubleshooting

XML

QDM, ...QDM, ... QDM, ...QDM, ...

QPMQPM CW2000 RWAN(IPM)

CW2000 RWAN(IPM)


Data Collector

AggregatorME1100

http

interface

Data Collector

AggregatorME1100

http

interface

ServerStore

CW2000 SMSSLM Server

http XML

http XML

The Service Level Management The Service Level Management ArchitectureArchitecture

LocalStore

Third PartyApplicationThird Party

ApplicationThird PartyApplication

LocalStore

SNMP

SNMP

SDK

HT

TP

Interface

http XML

http

http

http

XM

L

A proven architecture


SummarySummary



How to Build How to Build A “Point-to-Cloud” Service?A “Point-to-Cloud” Service?

• Scenario 1:

– Constrained Access

– Unconstrained Backbone

MPLS VPN

DiffServ o IP DiffServ o IP

Best-Effort o MPLS



• Scenario 2:


– Constrained Backbone

MPLS VPN

DiffServ o IP DiffServ o IP

DiffServ o MPLS



• Scenario 3:


– Constrained Backbone

– Optimised Backbone (Traffic Eng.)

DiffServ o IP DiffServ o IPMPLS VPN

DiffServ o MPLS, GB-TE

1© 2001, cisco systems, inc. service provider qos providing e2e guarantees vijay krishnamoorthy...

Documents

cisco systems

services diffserv diffserv

service provider qos

differentiated services

qos models

streaming services

new services

effort service