Advanced Traffic Management (QOS) Concepts

319 1056_05F9_c2
1999, Cisco Systems, Inc.
Advanced Traffic Management and QoS Concepts

Session 319
319 1056_05F9_c2
Copyright 1998, Cisco Systems, Inc. All rights reserved. Printed in USA. Presentation_ID.scr
Introduction
Traffic Management Applications and Transports So what Are the Issues for
TCP Voice on IP Video (Broadcast and Teleconferencing)
319 1056_05F9_c2
Let's Talk about Traffic Management

Why it is a concern What the guiding principles are What tools are available What can be accomplished using those tools What cannot be accomplished
319 1056_05F9_c2
Why Traffic Management Is a Concern
Needs of certain applications

Mail? Web? Transaction processing?
Opportunities with certain transports
319 1056_05F9_c2
Guiding Principles for Traffic Management

We want to achieve
Predictability Reliability Availability
In a network that
Keeps intelligence at the edges Scales to necessary sizes and bandwidths Minimizes complexity Uses cost-effective technologies
319 1056_05F9_c2
What Tools Are Available for Traffic Management
Traffic path control Queue depth management Queue rate management Permission to use a link
319 1056_05F9_c2
How Well Will Traffic Management Do?
We know we can do this:

Management of latency Management of bandwidth
What cannot be accomplished

Creation of bandwidth that otherwise would not be there
319 1056_05F9_c2
Primarily a WAN IP Talk

IP is the dominant internet protocol TCP is the dominant data transport
95% of Internet traffic uses TCP
80% 70% 60% 50% 40% 30% 20% 10% 0% 1994 1996 1998E 2000E
WAN Protocol Breakdown

IP
Voice is a growing market

But beware of hype
2002E
Heterogeneous link layers

Source: Gartner
319 1056_05F9_c2
IP SNA IPX Others RFC 1490
Group Study, March 1997

9
Making Networks Predictable

The Grail
319 1056_05F9_c2
10
This Is what You Need to Understand:
TCP-based applications, voice, and video can be managed well with a little planning
319 1056_05F9_c2
11
Parekh and Gallaghers Paper

INFOCOMM 93 One must have at most a predictable amount of traffic in the network One must have predictable traffic delay in each network element Given these, end-to-end delay of a host to host message is predictable
319 1056_05F9_c2
12
Definition of Predictable
Does not mean

Fixed, Invariant, or Zero
Means that it has a

Mean value Statistical distribution Upper bound
319 1056_05F9_c2
13
Predictable Amount of Traffic in the Network

The source must pace traffic initiation so that standing queues are bounded
Queues form when arrival rate exceeds departure rate
When congestion (too many messages in one queue) sets in:

Sources must not increase their rate Ideally, sources decrease their rate
319 1056_05F9_c2
14
Examples of Source Predictability
TCP will keep at most a certain amount of traffic in flight

We say it is elasticrate is proportional to latency
Voice will send only and exactly as fast as the coding algorithm permits
We say it is inelastic
319 1056_05F9_c2
15
Predictable Packet Treatment in Routers and Switches

Transit latency must be within limits acceptable to the application Variation in transit latency must be within limits acceptable to the application No stream may be locked out apart from administrative policy Applicable policy must be observed
319 1056_05F9_c2
16
Examples of Unpredictability
Queues change rapidly enough that the distribution cannot be described Discards happen frequently enough that there is effectively no upper bound on delivery time
319 1056_05F9_c2
17
Examples of Predictability
Classes of queues get sufficient service that ultimate arrival is timely and normal
Timely is an application concept
319 1056_05F9_c2
18
Quality of Service Issues in Traffic Management
Predominantly TCP traffic Some specific applications Voice/video traffic
319 1056_05F9_c2
19
Managing TCP Traffic

Moving Mountains of Data Without Incurring the World Wide Wait
319 1056_05F9_c2
20
10
Backbone Traffic Mix

Transport Breakout TCP Applications
319 1056_05F9_c2
Source: MCI/NSF OC-3MON via http://www.nlanr.net, 1998

21
TCP Technology Issues
Single drops communicate from network to sending host

You need to slow down
Multiple drops in round trip trigger time-outs

Something bad happened out here
319 1056_05F9_c2
22
11
Behavior of a TCP Sender

Sends as much as credit allows Starts credit small
Avoid overloading network queues
N N+ N+ 1 2 N+ 3
Increases credit exponentially

To gauge network capability
319 1056_05F9_c2
23
Behavior of a TCP Receiver

N N+ N+ 1 2 N+ 3
When in receipt of next message, schedules an ACK When in receipt of something else, acknowledges all it can immediately
319 1056_05F9_c2
+1 kN Ac 1 + kN Ac 1 N+ ck A
24
12
Sender Response to ACK

If ACK acknowledges something
Update credit and send
N N+ N+ 1 2 N+ 3
If not, presume it indicates a lost packet

Send first unacknowledged message right away Halve current credit Increase linearly to gauge network throughput
319 1056_05F9_c2
N+ 1
+1 kN Ac 1 + kN Ac +1 kN Ac
+4 kN Ac
25
Multiple Drops in TCP

In the event of multiple drops within the same session:
Current TCPs wait for time-out Selective acknowledge may work around (but see INFOCOM 98) New Reno fast retransmit phase takes several RTTs to recover
319 1056_05F9_c2
N N+ N+1 2 N+ 3 +1 N+ 4 ck N A +1 kN Ac +1 kN Ac N+ 1
4 N+ ck A
N+ 4
World Wide Wait!
5 N+ ck A
26
13
Remember Parekh and Gallagher
One must have at most a predictable amount of traffic in the network One must have predictable traffic delay in each network element Given these, end-to-end delay of a host to host message is predictable
319 1056_05F9_c2
27
How Can We Make TCP in a Network Act Predictably?

Predictable amount of traffic in the network:
Well-written TCP implementations manage their rates to the available bandwidth
Router needs to
Provide predictable treatment of packets Queue delay and drop characteristics
319 1056_05F9_c2
28
14
Fundamental FIFO Queue Management Technologies

Tail drop
Network standard behavior Causes session synchronization when waves of traffic experience correlated drops
Random Early Detection (RED)

Random drops used to desynchronize TCP sessions and control rates
319 1056_05F9_c2
29
Session Synchronization
Session synchronization results from synchronized losses Tail drop from waves of traffic synchronizes losses
319 1056_05F9_c2
30
15
Effect of Random Early Detection
Courtesy of Sean Doran, Ebone
RED Enabled
One day, below 100% throughput

Simple FIFO with tail drop
Starting 10:00 second day, 100% throughput

Random Early Detection enabled
319 1056_05F9_c2
31
Was that a Fluke?
Courtesy of Sean Doran, Ebone
RED Enabled
No, heres what happened that week Session synchronization reduced throughput until RED enabled
319 1056_05F9_c2
32
16
FIFO Traffic Timings

400
350
300
250
200
150
100
Mean Latency Correlates with Maximum Queue Depth
Ns RTT
50
0 Elapsed Time Mean RTT Min RTT Max RTT STD DEV
319 1056_05F9_c2
33
RED Traffic Timings

400
350
300
250
Additional Capacity to Absorb Bursts Mean Latency Correlates with Minimum Drop Threshold
Elapsed Time Mean RTT Min RTT Max RTT STD DEV
Ms RTT
200
150
100
50
319 1056_05F9_c2
34
17
ThereforeTCP QoS Definition:
Normally at most one drop per round trip Mean variation in latency bounded by predictable network
319 1056_05F9_c2
35
TCP 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 high rate bursts
It is these that we worry about managing
319 1056_05F9_c2
36
18
An Interesting Common Fallacy about RED:

RED means you will have more drops
Statement derives from observed statistics
RED means that you will have

Closer to 100% utilization of your line Less average delay per packet
But queuing theory?

As a line approaches 100% utilization, drops will increase, even though served load increases
319 1056_05F9_c2
37
TCP Traffic Management Issues
Applications
Often have site-specific policy associated with them Traffic often identifiable by port numbers
Sites
Generally identifiable by address prefix or interface traffic is received on
319 1056_05F9_c2
38
19
TCP Bandwidth Policy Questions to Answer
Particular site or application wants at least a certain bandwidth Particular site or application wants at most a certain bandwidth Particular site or application wants to average about a certain bandwidth
319 1056_05F9_c2
39
This Is Where Classes Come in

Classes can be for:
Voice Important application/site Unimportant application/site Assuring at least a rate Limiting to a rate
319 1056_05F9_c2
Classifier
Queues
Interface
40
20
Some Class of Traffic Wants at Least a Certain Bandwidth

ICU Left UC Me U Betcha Right
Managed Link
Example:
Several organizations share cost of link Distribute bandwidth proportional to fiscal responsibility
319 1056_05F9_c2
41
Class of Traffic Wants at Most a Certain Bandwidth

Traffic shaping Similar queuing technology to classbased weighted fair queuing Rate assigned to
Interface or sub-interface Frame Relay circuit ATM virtual channel (in hardware)
319 1056_05F9_c2
42
21
Examples of Rate Control

Frame Relay network
Access rate exceeds PVC ratelimit rate to rate of PVC
Intranet exposure
Limit rate of web surfing outside the company
T-1
64 KBPS
319 1056_05F9_c2
43
Some Class of Traffic Wants to Average a Certain Bandwidth
Service provider or large enterprise model Designed for

Cost containment Managed response to conflicting demands
319 1056_05F9_c2
44
22
Marking TCP Traffic at Edge

A useful technique: Mark traffic at a network edge with simple classifier This allows network to
Do the right thing without having to fully classify everywhere Use more effective markings
319 1056_05F9_c2
45
Serving TCP Traffic with the Assured Service

Presumes service level agreement
Flat rate for traffic meeting a rate/burst profile Usage charging for traffic out of profile
Drop management (weighted RED)

All traffic subject to loss Traffic out of profile much more subject to loss Enhances ISP traffic engineering (Good for service provider and consumer)
319 1056_05F9_c2
46
23
Structure of Presumed Service Level Agreement

Up to rate over interval is in profile Traffic within profile gets some guarantees Traffic out of profile has no guarantees
Potentially dropped by WRED at bottleneck Usage pricing of overage
319 1056_05F9_c2
Assured Service
70% 60%
Usage
50% 40% 30% 20% 10% 0%
0 10 20 30 40 50 60 70 80 90
Time
47
Best Effort Service in Simple IP Networks
Line Congested? Drop at Some Rate!
319 1056_05F9_c2
48
24
Assured Service in Simple IP Networks
Line Congested and Packet Out of Profile? Profile Drop at Some Rate!
319 1056_05F9_c2
49
Best effort Service in an ATM-Based Network
319 1056_05F9_c2
50
25
Assured Service in an ATM-Based Network
319 1056_05F9_c2
51
So, for TCP
Traffic can be contained to a rate in a manner consistent with good quality of service Traffic can be managed well with a little foresight and planning
319 1056_05F9_c2
52
26
Convergence with Voice Networks

Its about Internet Telephony!
319 1056_05F9_c2
53
Again, the Premise:
TCP-based applications, voice, and video can be voice managed well with a little planning
319 1056_05F9_c2
54
27
Changing Corporate Network Application Predominance

Numbers in Percent
100 80 60
2% 7% 27% 28% 27% 15% 2% 7% 13%
Multimedia Dynamic WWW Static WWW FTP and Telnet Email and News Other
40 20 0
319 1056_05F9_c2
39%
39% 17% 8%
12% 17% 14%
17% 8%
1996
Source: The Yankee Group, 1996
1998
2000
55
Growth of IP Traffic
Email Information search/access Subscription services/Push Conferencing/ multimedia Video/imaging
From 2000 on, 80% of Service Provider Profits Will Be Derived from IP-Based Services. Source: CIMI Corp.
319 1056_05F9_c2
Rel. Bit Volume 250 200 150 100 50
Traffic Projections for Voice and Data

Data (IP) Circuit Switched Voice
1997
1998
1999
2000
2001
56
Source: Multiple IXC Projections

28
High End IP Transport Alternatives

B-ISDN IP or Voice ATM SONET/SDH Optical IP or Voice ATM Optical IP SONET/SDH Optical Voice IP Optical IP or Voice over ATM IP over SONET/SDH IP over Optical
Multiplexing, Protection and Management at Every Layer
Lower Cost, Complexity and Overhead

319 1056_05F9_c2
57
H.323 Voice/Video
Voice
Constant bit rate when sending Relatively small messages (44-170 bytes)
Video
Generally high variable bit rate Controlled by codec efficiency on picture Message size is generally the MTU
319 1056_05F9_c2
58
29
Video: Traffic Pattern
Key Frame
Key Frame
Delta Frames
319 1056_05F9_c2
59
Video: Effect of Delay
Key Frame
Key Frame
Delta Frames
319 1056_05F9_c2
60
30
Video: Playback Point

Transmission Time Typical Delivery Playback Point
Preferred Delivery Interval Application Buffers Data to Ensure Consistency
Unless its Too Late
Distribution of Deliveries in Time

319 1056_05F9_c2 61
Synchronization of Voice and Video
McGurk effect: voice can sound garbled to human ear when not synchronized with video Therefore, we have to synchronize these
319 1056_05F9_c2
62
31
QoS Definition for Voice:
Low loss rate Low absolute delay in two-way situations

Broadcast voice doesnt have this problem
Low variation in delay

319 1056_05F9_c2
63
Key Issue for Voice QoS:
Silent periods must not be randomly inserted or removed so as to make other sounds unintelligible End to end delay must be comprehended by human listener
319 1056_05F9_c2
64
32
QoS Definition for Video:
Low loss rate Low absolute delay in two-way situations Low variation in delay
319 1056_05F9_c2
65
Key Issues for Video:
All packets that comprise a video frame must arrive during the same frame interval
OK if its the last millisecond of that interval
Audio and video must be synchronized when shown to user

319 1056_05F9_c2
66
33
How Can We Make Internet Voice Act Predictably?
Predictable amount of traffic in the network Predictable treatment of packets in routers and switches Planning to support these aspects results in a predictable network
319 1056_05F9_c2
67
Voice/Video Traffic Management Issues
The fundamental problems with Voice/video traffic are

It doesnt slow down in response to delay or loss It requires minimal variation in delay
319 1056_05F9_c2
68
34
Predictable Amount of Traffic in the Network

The implication is that we have to control used capacity
Capacity that individual calls consume If you experience poor quality, use a more compact encoding or a lower frame rate Capacity that total call volume can consume If there isnt capacity, refuse new calls
319 1056_05F9_c2
69
Predictable Treatment of Packets in Routers and Switches
We have to place voice in queues that give it high priority

Maintain tight delay budgets Application of class-based WFQ
319 1056_05F9_c2
70
35
Planning for a Predictable Network

Enable CBWFQ on all relevant links
Configure voice queue with more bandwidth than traffic will need, or For low bandwidth, priority queue [12.0(6)T]
Low speed links should use

Link Fragmentation or FRF.12 RTP compression for voice
Enable RSVP call negotiation

Refuse excess calls
319 1056_05F9_c2
71
FRF.12, and Link Fragmentation and Interleaving
Premise:
Reducing voice packet size reduces session requirements on network So compress out IP, UDP, and RTP headers as much as possible
Limits jitter on lower bandwidth links

319 1056_05F9_c2
72
36
Resource Reservation
Current deployment Current extensions Extensions being developed
319 1056_05F9_c2
73
Current Deployment
RSVP version 1
Call control for individual sessions Deployed Cisco 11.2 Microsoft Windows 98 (service pack) Microsoft Windows NT 2000
Appropriate to edge networks

319 1056_05F9_c2
74
37
Current Extensions
Policy management via COPS LAN management via subnet bandwidth manager
319 1056_05F9_c2
75
Policy Management Via COPS

Local or central policy server can authorize decisions Local policy:
Simple policies
Central policy server:

Certificates, Complex policies
319 1056_05F9_c2
76
38
LAN Management Via Subnet Bandwidth Manager
Subnet bandwidth manager is RSVP in a switch Controls aggregate reservations on a LAN
319 1056_05F9_c2
77
Extensions Being Developed
Rapid deployment of calls Aggregate classification in edge networks Aggregate classification and admission in service provider networks
319 1056_05F9_c2
78
39
Rapid Deployment of Calls
Problem: need acknowledged reservation installation Solution: acknowledge it
319 1056_05F9_c2
79
Aggregate Classification in Edge Networks
PSTN
Use differentiated services code points to identify traffic

Rather than specific flows
PSTN
319 1056_05F9_c2
80
40
Aggregate Classification in Edge Networks

Reservation requested by host in the usual way (RFC 2205) Flow classification and policing at first hop router Flow admission along end to end path Aggregate classification and policing at subsequent routers
319 1056_05F9_c2
81
Aggregate Classification and Admission Across Service Provider Networks

Voice/video calls
Placed across aggregation domain boundary
Aggregate reservations
Placed from ingress to egress for DSCP used Use expedited forwarding service Limited rate of change
319 1056_05F9_c2
Why?
Otherwise, you dont know that bandwidth exists on a path
82
41
Solving Voice/Video Issues Using the Expedited Forwarding Service Rate control
Application at source Reservation in network
Jitter control
WFQs priority queue (low speed) Statistically empty queue (CB-WFQ)
319 1056_05F9_c2
83
The Implications for Voice and Video

We can control call volume
And therefore traffic volume
We can scalably prioritize traffic in the system

And therefore deliver on latency issues
So, voice and video can be managed well with a little planning
319 1056_05F9_c2
84
42
Traffic Path Control

What if IP Routing Isnt Quite Good Enough for Your Traffic?
319 1056_05F9_c2
85
Traffic Engineering
Historical approaches
Load sharing Routing metrics
A new one
Label switching
319 1056_05F9_c2
86
43
Load Sharing
Multipath routing
Equal and unequal cost
Multilink PPP
319 1056_05F9_c2
87
Routing
Administrative metrics
Designed to move traffic to statistically low volume links
Load sensitive metrics

Designed to move data away from congested links Tendency towards oscillation
319 1056_05F9_c2
88
44
Utility of These:
While they basically work, they are

Not deterministic, and Tend to be hard to predict
319 1056_05F9_c2
89
Multi-Protocol Label Switching
MPLS traffic engineering

VPNs and general engineering
MPLS routing for resource reservation

In the direction of QoS routing
319 1056_05F9_c2
90
45
Principles of Label Switching

Labeled paths:
Multiple enumerated point to point relationships between pairs of routers Sets of pair-wise relationships create a labeled tunnel
Conceptually similar to ATM VCs or Frame Relay DLCs, but

Interface independent Used to model network layer constructs Variable length packets
319 1056_05F9_c2
91
Network Layer Constructs

Types of traffic streams
Destination routes Source-destination routes AS pairs BGP community pairs
Notice: Two Labels on One Interface, Distinguishing Routes
Tunnels can create

Any routing that meets engineering needs
319 1056_05F9_c2
92
46
Using Labeled Tunnels to Create Virtual Private Networks

Imagine edge network with private address space Stretch labeled tunnels across the network Now, do it again Disjoint networks
Same address space Separate routing
319 1056_05F9_c2
93
MPLS Traffic Engineering
Same technology can drag specific routes around

Several less-used paths vs a few denser paths
Initially seen as off-line engineering Can use either LDP or RSVP to install routes
319 1056_05F9_c2
94
47
CoS in MPLS Networks

Class of Service
Roughly similar to diff-serv code point Eight values, not sixty-four
Implements similar drop/delay management within labeled tunnels Therefore, MPLS networks have fundamental TCP QoS support
319 1056_05F9_c2
95
The Obvious Hole
Wouldnt it be nice if engineered labeled tunnels could

Have specific bandwidths guaranteed? Recover from network events quickly and automatically using reasonable if not optimal routes?
319 1056_05F9_c2
96
48
MPLS Routing for Resource Reservation

Use OSPF/IS-IS to distribute bandwidth availability information Edge router does SPF calculation when needed RSVP used to install labeled tunnel while checking for race events CoS field used to identify traffic for queued rate support
319 1056_05F9_c2
97
Automated Reinstallation of Labeled Tunnels

RSVP tears down affected tunnels Edge devices recalculate routes RSVP used to re-install tunnels Bandwidth checks result in retry
319 1056_05F9_c2
98
49
Q.E.D. MPLS
Traffic engineering for network layer traffic can be managed well with a little planning
319 1056_05F9_c2
99
So, What Are You to Do about It?

Here the Rubber Meets the Road
319 1056_05F9_c2
100
50
Plan Your Network for Predictability
Network engineering Assured forwarding service

TCP
Expedited forwarding service

Voice, implies some form of admission
319 1056_05F9_c2 101
Network Engineering
Capacity engineering
Engineered IP routes?
May involve traffic engineering

Labeled tunnels?
319 1056_05F9_c2
102
51
Assured Forwarding Service

Designed for TCP
Classes control rates for SLAs Drop controls trace effects back to sources
Implement using
Committed access rate, Weighted Random Early Detection,
319 1056_05F9_c2
Class-based weighted fair queuing

103
Expedited Forwarding Service
Appropriate to voice/video Requires

Under-subscribed traffic classes Reservation of bandwidth Policing
319 1056_05F9_c2
104
52
Guiding Principles for Predictability
One must have at most a predictable amount of traffic in the network One must have predictable traffic delay in each network element Given these, end-to-end delay of a host to host message is predictable
319 1056_05F9_c2
105
In Your Network
TCP-based applications, voice, and videoand your bandwidthcan be managed well with a little planning
319 1056_05F9_c2
106
53
Please Complete Your Evaluation Form

Session 319
319 1056_05F9_c2
107
319 1056_05F9_c2
108
54

Advanced Traffic Management (QOS) Concepts

Uploaded by

Document Information

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

Advanced Traffic Management (QOS) Concepts

Uploaded by

Copyright:

Available Formats

319 1056_05F9_c2

1999, Cisco Systems, Inc.

Advanced Traffic Management and QoS Concepts

1999, Cisco Systems, Inc.

Let's Talk about Traffic Management

Why Traffic Management Is a Concern

Needs of certain applications

Opportunities with certain transports

1999, Cisco Systems, Inc.

Guiding Principles for Traffic Management

1999, Cisco Systems, Inc.

What Tools Are Available for Traffic Management

1999, Cisco Systems, Inc.

How Well Will Traffic Management Do?

We know we can do this:

What cannot be accomplished

Primarily a WAN IP Talk

WAN Protocol Breakdown

Voice is a growing market

Heterogeneous link layers

IP SNA IPX Others RFC 1490

Group Study, March 1997

1999, Cisco Systems, Inc.

Making Networks Predictable

1999, Cisco Systems, Inc.

This Is what You Need to Understand:

1999, Cisco Systems, Inc.

Parekh and Gallaghers Paper

Does not mean

Means that it has a

Predictable Amount of Traffic in the Network

When congestion (too many messages in one queue) sets in:

Examples of Source Predictability

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

Predictable Packet Treatment in Routers and Switches

1999, Cisco Systems, Inc.

1999, Cisco Systems, Inc.

Quality of Service Issues in Traffic Management

Predominantly TCP traffic Some specific applications Voice/video traffic

1999, Cisco Systems, Inc.

Managing TCP Traffic

Backbone Traffic Mix

Source: MCI/NSF OC-3MON via http://www.nlanr.net, 1998

TCP Technology Issues

Single drops communicate from network to sending host

Multiple drops in round trip trigger time-outs

Behavior of a TCP Sender

Increases credit exponentially

Behavior of a TCP Receiver

Sender Response to ACK

If not, presume it indicates a lost packet

Multiple Drops in TCP

World Wide Wait!

Remember Parekh and Gallagher

How Can We Make TCP in a Network Act Predictably?

Fundamental FIFO Queue Management Technologies

Random Early Detection (RED)

Effect of Random Early Detection

Courtesy of Sean Doran, Ebone

One day, below 100% throughput

Starting 10:00 second day, 100% throughput

Was that a Fluke?

Courtesy of Sean Doran, Ebone

FIFO Traffic Timings