MQC QoS

2009 Cisco Systems, Inc. All rights reserved.
Cisco Public BRKRST-2504_c2 1

Hierarchical QoS and Policies
Aggregation
BRKRST-2504
2009 Cisco Systems, Inc. All rights reserved. Cisco Public BRKRST-2504_c2 2
Agenda
Hierarchical QoS overview
QoS general concepts
HQoS Deployments examples
Traditional MQC HQoS
MQC and HQF overview, restrictions
HQF IOS and platforms support
Evolution : Policies Aggregation
Drivers behind policies aggregation: economy class
Policies Aggregation deep dive with QFP overview
3 level Hierarchical QoS with policies aggregation
Future: 4 level policies and policies aggregation
Summary
QoS General Concepts
Why Quality of Service (QoS)
Bandwidth optimization for voice, video and data
applications
VoIP and Video needs to meet strict SLA on delay and jitter
Critical customers and/or applications prioritization
Enhance delivery and productivity
Financial transactions
More Bandwidth is available but
Branch/Hubs/subscribers bottlenecks still exist
Bandwidth sharing is still needed
Why Hierarchical QoS
Different policies at different levels ( branch, HQ, etc)
Traffic aggregation
Bandwidth Optimization
Originally associated with Metro Ethernet, basic
concept has been used since ATM and FR days
Ethernet WAN
Service Provider
QFP
!!! !!!
QoS Components
Classification
Policing
Marking
Shaping*
Queuing*
Link Efficiency (cRTP, fragmentation, etc.)
Congestion management and
Scheduling
Scheduling and QoS
A Qos scheduler determines when a packet will be
serviced or dequeued
Dequeuing times can be relative or absolute
Relative packet dequeue times packet dequeue orders
e.g. Low Latency Queuing
Absolute packet dequeue times shaping
Queuing Parameters
Priority (priority)
Packets serviced before any other class
Two levels of priority queuing are possible in certain platforms
Min Bandwidth (bandwidth)
Packets are serviced in the order determined by configured
bandwidth
Max Bandwidth (Shape)
Packets are service at the configured max rate
Excess Bandwidth (bandwidth remaining)
Excess packets are service in the order determined by
remaining rate
QoS Hierarchical Levels
Each level could represent a branch, type of traffic, etc
and each one requires a different level of service or
distinctive action
2
nd
Level
Priority
Traffic
Best Effort
Data Traffic
1
st
Level
3rd Level
Typical Single-Level Scheduler
Single level scheduler,
i.e. no hierarchy
Scheduler determines order
of packets dequeued
Physical interface enforces
max aggregate rate across
all classes
Backpressure from interface
determines when packets
are sent
priority
Control
Data
Traffic
Physical
Interface
1
st
Level
Two-Level Scheduler
1st layer
Parent level scheduler
enforces max aggregate rate
or excess bw
Determines when
packets are sent
2nd layer
Child queuing policy
determines order in which
packets are sent
1
st
Level
Multiple
priority
traffic
Best
Effort
Data
Traffic Interface
2
nd
Level
Service Propagation
Behavior defined at one layer in the hierarchy
propagates through to upper layers, enforcing SLA at
all levels
Service propagation helps overcome the issues of
conventional scheduling implementations
Priority Propagation:
Parent Scheduler knows that a packet was scheduled from a
Priority Entry Preserves Priority Through Hierarchy
Available in software based platforms, until CPU utilization
or congestion is too high. Only specialized hardware can
really deliver priority at a very high throughput
Typical Hierarchical QoS Deployments
Traditional WAN Aggregation
with HQoS
HQ aggregates branches
( FR, LL, ATM)
From HQ, each branch is
shaped down to a
contracted rate, in which
VoIP or applications are
prioritized
Same applies from each
Branch towards HQ
BRANCH
CPE
Service Provider
HEADQUARTER
Ethernet WAN with HQoS
Same as before + few
extras
Branches can subdivide
BW and share among
different services or dpts
HQoS can be applied to
VLAN or Sessions
directly BRANCH
CPE
Service Provider
HEADQUARTER
DMVPN HQoS
Provides full meshed and
secured connectivity with
simple configuration of
hub and spoke
Same as before, each
spoke ( GRE tunnel ) or
SA has to be shaped
down
Classification can be
done based pre
GRE+IPSec
encapsulation
Spoke n
Traditional Static Tunnels
DMVPN Tunnels
Static Known IP Addresses
Dynamic Unknown IP Addresses
Hub
VPN
Spoke 1
Spoke 2
Secure On-Demand Meshed Tunnels
Typical BRAS Deployments with HQoS
Subscriber session could
be represented by:
VLANs
PPP session
IP session
Subscriber gets an X
Mbps service plus Voice
or Video
IP/MPLS Core
Aggregation
Internet
Residence
C
P
E
Residence
C
P
E
PE
BRAS
PE
PE
BRAS for PTA
IP/MPLS
Core
Aggregation
ISP 1
Residence
CPE
Residence
CPE
ISP 2
LNS LNS
LAC
LAC/LNS
MQC/HQF Overview
QoS with IOS Modular QoS CLI (MQC)
Cisco IOS command syntax for QoS
Template-based syntax
Separates classification engine from
the policy
Uniform CLI for QoS features
Cisco Platform independent
Hierarchical Policies are basically configured by calling
a child policy from within a parent policy, etc
Basic Hierarchical QoS with IOS MQC
EF
AF1
Default
Gig 0/1.1001
200 Mbps
Service
Level
Policy-map PARENT
class class-default
shape average 200000000
service-policy output CHILD
Policy-map CHILD
class EF
priority level 1
class AF4
priority level 2
class AF1
bandwidth remaining ratio 9
class class-default
Interface gigabitethernet 0/1.1001
service-policy output PARENT
Two MQC Levels
AF4
FRTS with Hierarchical QoS
AF4
AF1
Default
Ser 0/0.1
128 Kbps
Service
Level
Policy-map PARENT
class class-default
Policy-map CHILD
class EF
priority percent 5
class AF4
bandwidth percent 45
class AF1
class class-default
Map-class frame-relay Hshape
Interface serial 0/0.1 point-to-point
frame-relay interface-dlci 100
class HShape
Two MQC Levels
EF
Three-Level Hierarchical MQC Policies
Supported on Cisco 7200 and 7500 Series Routers, and Low-End
Routers, Since Cisco IOS Software Release 12.2(8)T ( NON HQF)
policy-map GRANDCHILD
class BUSINESS-NO-MGMT
police cir 128000
conform-action transmit
exceed-action set-frde-transmit
!
policy-map CHILD
class VOICE
priority percent 25
class BUSINESS
bandwidth remaining percent 66
service-policy GRANDCHILD
!
policy-map PARENT
class class-default
service-policy CHILD
OUT-POLICE
BUSINESS
VOICE
Ser 0/0.1
512 Kbps
Service
Level
Basic Hierarchical QoS over GRE
EF and
AF4
AF1
Default
Gig 0/1.1001
20 Mbps
Service
Level =
Tunnel
Policy-map PARENT
class class-default
Policy-map CHILD
class EF
priority level 1
class AF4
priority level 2
class AF1
class class-default
Interface Tunnel 0
Two MQC Levels
DMVPN HQoS
Spoke n
Traditional Static Tunnels
DMVPN Tunnels
Static Known IP Addresses
Dynamic Unknown IP Addresses
Hub
VPN
Spoke 1
Spoke 2
Secure On-Demand Meshed Tunnels
Policy-map PARENT
class Tunnel 1
description match any-to-campus
.
class Tunnel 500
Policy-map CHILD
class VOICE
priority 100
class CONTROL
bandwidth percent 5
class DATA
class class-default
Interface GigabitEthernet 0/0
Interface Tunnel 0
qos preclassify
QoS Preclassify Review
The use of qos-preclassify depends on which header
you need to use for classification and where to apply
the QoS Policy
Apply the QoS policy to the tunnel interface without qos-
preclassify when you want to classify packets based on the pre-
tunnel header.
Apply the QoS policy to the physical interface without qos-
preclassify when you want to classify packets based on the post-
tunnel header. In addition, apply the policy to the physical
interface when you want to shape or police all traffic belonging to
a tunnel, and the physical interface supports several tunnels.
Apply the QoS policy to a physical interface and enable qos-
preclassify on a tunnel interface when you want to classify
packets based on the pre-tunnel header.
BRAS Hierarchical Queuing
Example
Hierarchical policy is attached to the
subscriber session relationship with
physical interface is automatically
created. Not visible in running config.
Attached via RADIUS attribute or on the
virtual-template which is referenced in
the bba-group or vpdn-group.Can also
be attached as a service policy for ISG
cases (including IP sessions)
policy-map sub-3play-out
class voice
priority level 1
police cir 128000
class video
priority level 2
police cir 1000000
class gaming
class class-default
policy-map 1.5mbps_subscriber
class class-default
service policy sub-3play-out
interface Virtual-Template1
ip unnumbered Loopback1
ppp authentication chap PTA_AUTH
ppp authorization PTA_AUTH
ppp accounting PTA_AUTH
ppp ipcp address required
service-policy output 1.5mbps_subscriber
IP/MPLS Core
Aggregation
Internet
Residence
C
P
E
Residence
C
P
E
PE
BRAS
PE
PE
BRAS for PTA
Ethernet Hierarchical Scheduling
Example (2)
Hierarchical policy is attached to the
subscriber session relationship with
physical and VLAN subinterface is
automatically created. Not visible in
running config
Attached via RADIUS attribute or on the
virtual-template which is referenced in
the bba-group or vpdn-group. Can also
be attached as a service policy for ISG
cases (including IP sessions)
policy-map sub-3play-out
class voice
priority level 1
police 128000
class video
priority level 2
police 1000000
class gaming
class class-default
!
policy-map 1.5mbps_subscriber
class class-default
service policy sub-3play-out
!
policy-map 50mbps_dslam
class class-default
!
interface GigabitEthernet0/0/0.1
encapsulation dot1q 2
service-policy output 50mbps_dslam
IP/MPLS Core
Aggregation
Internet
Residence
C
P
E
Residence
C
P
E
PE
BRAS
PE
PE
Ethernet
Bandwidth Remaining Ratio
Supported in 12.2(31)SB, 12.2(33)SRD and IOS XE 2.1
Available at both child and parent level
Total Bandwidth = 100 Mbps ( parent
shaper)
Remaining Bandwidth = 100- EF = 95 Mbps
AF Bandwidth = (50/95)*95 = 50 Mbps
Default Bandwidth = (45/95)*95 = 45 Mbps
Policy child-output
class EF
priority
class AF
class class-default
Policy parent-output
class class-default
service-polcy child-output
BRR
Parameter is unitless
Part of ratio that changes with
addition of classes
Inconvenient when trying to
figure out % for each class
Convenient with a very
dynamic class configuration
Convenient with dynamic
configurations with more than
100 vlans/classes
BRP
Parameter is a percentage
Total % for all classes/levels
cant be more than 100%
Convenient when a class must
always get same %
Inconvenient with a very
dynamic class configuration
Convenient with traditional
configurations with few and
very static vlans/classes
MQC/HQF Available Combinations
Allowed in ( class-default )
Parent policy
Allowed in Child policy
Policer Yes Yes
Shape Yes Yes
Bandwidth Yes Yes
Bandwidth remaining Yes Yes
Priority Yes ( if child policy is non
queuing)
Yes
WRED Yes (if there are other queuing
in same class)
Yes
Hierarchical Queuing Framework (HQF)
Cisco has developed a new way of handling queuing
Supported since IOS 12.0(26)S, 12.2(28)SB, IOS XE 2.1 and
just recently 12.4(20)T
The objective is to handle hierarchical QoS policies
more efficiently and consistently across Cisco platforms
With HQF customers, using any of the IOS releases
and specific platforms, will have:
The ability to provide multiple levels of packet scheduling
The ability to support integrated class-based shaping and
queuing
Hierarchical Queuing Framework (HQF)
Platforms may implement the framework with different
levels of hierarchy and algorithms, with different
resulting capabilities and behaviors
J ust because two platforms both support HQF does not mean
they support the same underlying functionality!!
Bottom line is that HQF is as consistent as possible
given the underlying hardware
Next slides are some of the most important HQF
enhancements, which as mentioned before, are
available since IOS 12.0(26)S, 12.2(28)SB, IOS XE 2.1
and just recently 12.4(20)T
HQF Major Enhancements
Hierarchical Policy with Queuing Features at Every
Level
You can apply class-based queuing to any traffic class in the
parent or child level of a hierarchical policy
policy-map child
class child-c1
bandwidth 400
class child-c2
bandwidth 400
policy-map parent
class parent-c1
bandwidth 1000
service-policy child
class parent-c2
bandwidth 2000
service-policy child
Over-Subscription Support for Multiple Policies on
Logical Interfaces
When you attach a shaping policy to multiple logical interfaces
including a subinterface, and the sum of shape rate exceeds the
physical interface bandwidth, congestion at the physical interface
results in backpressure to each logical interface policy. This
backpressure causes each policy to reduce the output rate down
to its fair share of the interface bandwidth.
Example: 10 subint policies each shaped to 2Mbps, physical
int has 10Mbps bandwidth (2:1 oversubscription), when all
10 subint are sending at 2Mbps, each subint gets a
throughput of 1Mbps (10 Mbps / 10 subint
Shaping in an ATM PVC Policy
You can apply class-based shaping within an ATM PVC as
shown in the following example
Fair Queue in an MQC class
You can apply the fair-queue command to a user-defined class
policy-map p1
class c1
class c2
interface atm1/0.1
pvc 1/100
service-policy output p1
Child Policy in a Priority Class
You can apply a child policy to a class with priority enabled. The
child policy can contain police or set features, but not queuing
features
Strict Priority with No Policing Rate
Only one class is allowed strict priority configuration. Other
classes cannot have priority or bandwidth configuration. If
minimum bandwidth is required by one of the other classes the
bandwidth remaining percent command must be used
Some platforms support multiple levels of priority queuing
:priority level 1 and priority level 2
HQF Behavioral Changes
Major Differences in Existing QoS Commands
Flow-Based Fair-Queuing Support in Class-Default
The fair-queuing behavior for the class-default class is flow-based. This
is a change from the WFQ behavior in previous releases. With flow-
based fair queuing, the flow queues in the class-default class are
scheduled equally instead of by weight based on the IP Prec. Better to
use separate class if you have application or user flow w/special
needs
Default Queuing Implementation for Class-Default
When you do not explicitly configure the class-default class in a policy
map, its default queuing behavior is FIFO. You can configure the
bandwidth, fair-queue, or service-policy commands in the class-
default class to achieve different queuing behaviors.
Default Queuing Implementation for Shape Class
When you configure the shape command in a class, the default
queuing behavior for the shape queue is FIFO instead of
weighted fair queuing (WFQ). You can configure the bandwidth,
fair-queue, or service-policy commands in shape class to
achieve different queuing behaviors.
Class-Default and Bandwidth
The bandwidth assigned to the class-default class is the unused
interface bandwidth not consumed by user-defined classes. By
default, the class-default class receives a minimum of 1% of the
interface bandwidth.
Policy Map and Interface Bandwidth
In HQF, a policy map can reserve up to 100% of the interface
bandwidth. If you do not assign an explicit bandwidth guarantee
to the class-default class, you can assign a maximum of 99% of
the interface bandwidth to user-defined classes and reserve the
other 1% for the class-default class.
The command max-reserved-bandwidth is not longer
needed
Per-Flow Queue Limit in Fair Queue
In HQF, when you enable fair queuing, the default per-flow
queue limit is of the class queue limit. If you do not enable the
queue limit in a class, the default per-flow queue limit is 16
packets (1/4 of 64).
Shaping Behavior on GRE Tunnel
In HQF, shaping on GRE tunnel is done after encapsulation. This
means the shape rate is based on packets with tunnel
encapsulation and L2 encapsulation. If you configure IPSEC on
the GRE tunnel, shaping occurs after encryption.
Only absolute parent shapers are supported at this time and for
the support of GRE and physical policy, see next slide
Change in FRF.12 and FRF.9 Behavior
when you enable (FRF.12) on an FR PVC or FR main interface,
priority class packets are no longer subject to fragmentation.
Priority packets, regardless of the packet size, always interleave
among data fragments. When you enable (FRF.9) on an FR PVC
or main interface, priority class packets are no longer
compressed.
HQFGRE Multiple Policy (MPOL)
Gig 0/1.1001
20 Mbps
Service
Level =
GRE Traffic
Policy-map PARENT
class class-default
Policy-map CHILD
class EF
priority
class AF1
class class-default
Interface Tunnel 0
Interface Ethernet 0
HQF GRE MPOL Supported Only in 12.4(22)T
20 Mbps
Service
Level =
Non GRE
Traffic
HQF Behavioral Changes Highlights
HQF QoS NEW Behavior Classic QoS Behavior
Flow-Based Fair-Queuing
Support in Class-Default
Flow basedand all flows are equal WFQBased on IP prec
Default Queuing
Implementation for Class-
Default
FIFO WFQ
Default Queuing
Implementation for Shape
Class
FIFO WFQ
Class-Default and Bandwidth
Default 1%, otherwise remaining
from other classes or assigned
Default 25% but not guaranteed,
otherwise remaining from other
classes or assigned
Policy Map and Interface
Bandwidth
100% can be assigned to MQC
classes. max-reserved-bandwidth
is NOT needed
max-reserved-bandwidth is need to
reserve morethen 75% to MQC
classes
Per-Flow Queue Limit in Fair
Queue
Per flow queuelimit is of the
class
N/A
HQF Commands Changes
New random-detect Option Support
The random-detect command supports the atm-clp-based,
cos-based, and byte-based options to calculate the probability
of dropping a packet
Commands not needed/supported
random-detect prec-based replacedby random-detect
precedence-based
shape max-buffers replacedby queue-limit
max-reserved-bandwidth not needed
show queuing and show queue Commands replacedby show
policy-map interface
shape average Tc is 4 ms by default
HQF IOS and Platforms Support
HQF Platform Support
With 12.0(26)S, 12k and 7200VXR ,7500*
With 12.2(31)SB, 7200VXR,7304 and c10k
With 12.2()SRA, 7600 SIP400
With 12.2(33)SRC, 7200VXR, ES20
With 12.4(20)T, all ISR and 7200VXR
With IOS XE 2.1, ASR1000
Please Work with Your AT and/or Cisco.com
Documentation to Verify Each Platform Capabilities
Hardware-Based Platform and HQF
Software based platforms do support HQoS rules and
configurations, as long as congestion is not high
enough to overload CPU and Tx-ring
As mentioned before several platforms support HQF
based on each platforms capabilities
12000 Eng 3
7600 SIP400, ES and ES+
C10000 PRE3/4
7304 NSE150
ASR1000
DMVPN HQoS Performance Comparison
Platform Number of
Tunnels,
QoS conf
and shape
rate
VoIP
Drop%
Jitter
Delay
VoIP G.729
Calls
Data Total PPS Total
Mbps
7200
G2/VSA
30
mGRE QoS
4 Mbps
0%
1.3 ms
2.7 ms
454
40550 pps
81259 pps 58 Kpps 124 Mbps
7600
SIP400
240
per class-
per vlan
4 Mbps
0.22 %
0.6 ms
2.1 ms
4009
400,900 pps
53,951 pps 455 Kpps 1002 Mbps
ASR 1000
ESP10
RP1
240
per class-
per vlan
4 Mbps
0.25 %
2.5 ms
2.6 ms
4055
400,550 pps
81,259 pps 487 Kpps 953 Mbps
ASR 1000 QFP Introduction
RP (Route Processor)
Handles control plane traffic
Manages system
ESP (Forwarding Processor)
Handles forwarding plane traffic
Quantum Flow Processor
(QFP)
Consists of two subsystems:
QFP TM ( Traffic Manager)
QFP PPE ( Packet Proccesors)
SPA Interface Processor (SIP)
Houses the SPAs ( Shared PA)
Forwarding
Processor
ESP
CPU
Interconn.
QFP
Crypto
assist
Midplane
Route
Processor
RP
Interconn.
SPA SPA
SIP
CPU
SPA
Agg.
Interconn.
SPA SPA
SIP
CPU
SPA
Agg.
Interconn.
ASR 1000 QFP and Hierarchical QoS
ASR1000s QFP was designed specifically to support
several scheduling levels
in and outside MQC
QFPs PPEs are fully dedicated to MQC classification,
policing, marking, etc
QFP TM is fully dedicated for Hierarchical Queuing
MQC policies are mapped into QFP TM scheduler
Two level of high priority traffic and priority propagation
This capabilities allows the ASR1000 to delivery HQF
policies at very high throughput while maintaining LLQ
QFP, How Many Levels of Scheduling?
Getting back to the topic
of scheduling levels
This assumes scheduling of
all traffic for a particular
physical interface
The ASR1000 uses an extra
level since scheduling is
centralized on ESP
This level represents the SIP
slot
Therefore a typical 3-level
scheduling example is
actually 4 levels on the
ASR 1000
EF and
AF4
AF1
Default
SIP
Interface
Service
Level
Basic Hierarchical QoS with IOS MQC
AF4
AF1
Default
Gig 0/1.1001
200 Mbps
Service
Level
Policy-map PARENT
class class-default
Policy-map CHILD
class EF
priority level 1
class AF4
priority level 2
class AF1
class class-default
Interface gigabitethernet 0/1.1001
Two MQC Levels
EF
Basic Hierarchical QoS in QFP TM
Priority 1 and Priority 2 Passes

AF1 and Class-Default
for AF1 and Default
Performed Here
Shape Average <parent policy
>Enforced Here
2 Level (Class + VLAN) + Non-MQC Physical Level

Evolution: Policies Aggregation
Why Policies Aggregation
Existing 3-level hierarchy could not handle it
No way to aggregate only data traffic at interface level interface shaper would shape ALL
traffic
Shaper at VLAN level would shape ALL subscriber traffic (Voice/Video/Data), adding extra
latency when oversubscribed
Priority queues need to be separated from the Data queues in the
hierarchy
Benefit: Priority traffic ( +oversubscribed data) is not capped by logical interface shaper
Introduces the concept of an Economy Class Rate
Think of airline model: data traffic stays within its assigned class of service all through the
hierarchy
First class traffic (like voice/video) is not affected by this rate
Physical & logical interface policies linked via new fragment CLI
Benefit: Data classes can be linked together to provide both VLAN level and aggregate level
service
ASR 1000 Policies Aggregation
Priority
Data
Default
Gig 0/1.1001
200 Mbps
Service Level
Priority Queues Need to Be Separated from the Data
Queues in the Hierarchy
Policies Aggregation with QFP TM
4 Level Hierarchy:
1. Class -> MQC defined
2. Logical -> MQC VLAN
3. Aggregate -> MQC
Fragment CLI
4. Physical -> ASR 1000
SIP
2 Level (Class + VLAN) + Non-MQC Physical Level

Policies Aggregation
MQC CLI
Policy-map main-interface
Class data service-fragment Economy
policy-map Department2 (VLAN200)
class VoIP
priority level 1
class McastTV
priority level 2
class class-default fragment Economy
shape average 150 Mbps
service-policy AF1plusDefault
policy-map AF1plusDefault
class PremiumData
class class-default
policy-mapSubscriber(VLAN100)
class VoIP
priority level 1
class McastTV
priority level 2
class class-default fragment Economy
shape average 150 Mbps
service-policy AF1plusDefault
policy-map AF1plusDefault
class PremiumData
class class-default
These queues are not
shaped at main
interface
These queues are not
shaped at main
interface
LINKED
Access SW
IPv4/ IPv6Dual Core Residence
CPE NT
AAA/
DHCP
Content
Servers
SBC
MG
Access SW
Applications
RACS
H.248
Control
LNS
G
q

D
i
a
m
e
t
e
r
ASR1000 in Distributed Integrated Service Edge
Voice & Video Telephony (SBC, v4/v6)
POTS
VV
VoIP
Operators
IPTV VoD (SBC, HDTV, v6)
Internet Access (BB, LAC, PPPoE, v4)
IPTV Bcast TV (Multicast, SDTV/HDTV, v6)
Access Network
(DSL, PON)
ASR1000 Policies Aggregation
Applications
Ethernet WAN with Three Level HQoS
Branches can
subdivide Sub gig
BW,and share it
among different dept
This requires 3 level
Policy:
Physical
VLAN
Class
Dept/VLAN1
CPE
Service Provider
Dept 2
Dept 3
ASR 1000 Three Level Policies
Aggregation
ASR1000/QFP scheduler is flexible to enough
to accommodate this change
Multiple priority
Class
Data Class
Best Effort
Class
Aggregate BW
VLAN Available
BW
Service Level
Gig Interface
ASR 1000 Three Level Policies
Aggregation
Policy-map main-interface
Class data service-fragment ALL-P
class class-default fragment ALL-P
service-policy ALL-CHILD
policy-map ALL-CHILD
class EF
priority
class AF4
class AF41
class class-default
L
I
N
K
E
D
class class-default fragment ALL-P
service-policy ALL-CHILD
policy-map ALL-CHILD
class EF
priority
class AF4
class AF41
class class-default
This queue is shaped at
main interface
Policies Aggregation Restrictions
Only the default class in a policy map can be configured as a
fragment.
Fragments only work when multiple policy maps are attached to
the same physical interface.
Only queuing features are allowed in classes where the fragment
keyword is entered, and at least one queuing feature must be
entered in classes where the fragment keyword is used.
A policy map with a class using the fragment keyword can only be
applied to egress traffic.
The fragment keyword cannot be entered in a child policy map.
Fragment aggregate counters are only absolute ( not bps )
Future: Four Level MQC Policies
Several Scenarios
deployments require
scheduling at additional levels
Shape or BRR at the
Aggregate Level for a VLANs
or EVCs
Shape at the Interface Level
for a 3 level policy applies to a
VT or GRE
All of these are possible with
specialized scheduling
hardware such as the QFP or
ES+
Service
Level
Aggregate
Service
Level
Interface
EVC or
VLAN
Future: Policies Aggregation
All Non-default queuing happens at the aggregate level
Premier data is not longer mixed with default traffic and not subject
to vlan shaper
Priority Traffic
Premier Data
Default
Service Level
Gig 0/1.1001
200 Mbps
Summary
Summary HQoS and Policies
Aggregation
Hierarchical QoS gives you great flexibility to distribute
and manage bandwidth
Service Providers can overprovision, and basically resell the
same bandwidth
Enterprises can redistribute bandwidth according each campus,
user or application usage
HQF establishes the foundation to deliver a much more
uniform and consistent QoS scheduling behavior
Cisco ASR1000, QFP and its Policies Aggregation,
allows for even a greater flexibility in order to satisfy a
diverse set of requirements.
HQoS and Policies Aggregation Doc
HQF documentation
http://www.cisco.com/en/US/prod/collateral/iosswrel/ps6537/ps6
558/white_paper_c11-481499.html
Policies Aggregation documentation
http://www.cisco.com/en/US/docs/ios/ios_xe/qos/configuration/g
uide/qos_policies_agg_xe_ps9587_TSD_Products_Configuratio
n_Guide_Chapter.html
Network Infrastructure and Systems
NS1 Cisco Catalyst Series: Optimize and
Virtualize
NS2 Cisco Catalyst Series: Fueling
Collaboration
NS3 Cisco ISR: Application Integration at
Branch
NS4 Enhance Collaboration with Cisco
WebEx Node
NS5 Optimize the WAN with Cisco ASR
1000 Series
NS6 Pedal Power for the Cisco Catalyst
4500
Please Visit the Cisco Booth in the
World of Solutions
See the technology in action
Recommended Reading
End-to-End QoS Network Design:
Quality of Service in LANs,
WANs, and VPNs,
ISBN: 1-58705-176-1
Cisco Catalyst QoS: Quality of
Service in Campus Networks,
ISBN: 1587051206
QoS for IP/MPLS Networks,
ISBN: 1-58705-233-4
Complete Your Online
Session Evaluation
Give us your feedback and you
could win fabulous prizes.
Winners announced daily.
Receive 20 Passport points for
each session evaluation you
complete.
Complete your session evaluation
online now (open a browser
through our wireless network to
access our portal) or visit one of
the Internet stations throughout
the Convention Center.
Dont forget to activate your
Cisco Live Virtual account for access to
all session material, communities, and
on-demand and live activities throughout
the year. Activate your account at the
Cisco booth in the World of Solutions or visit
www.ciscolive.com.

MQC QoS

Diunggah oleh

Informasi Dokumen

Deskripsi Asli:

Hak Cipta

Format Tersedia

Bagikan dokumen Ini

Bagikan atau Tanam Dokumen

Opsi Berbagi

Apakah menurut Anda dokumen ini bermanfaat?

Apakah konten ini tidak pantas?

Hak Cipta:

Format Tersedia

MQC QoS

Diunggah oleh

Hak Cipta:

Format Tersedia

2009 Cisco Systems, Inc. All rights reserved.

Cisco Public BRKRST-2504_c2 1

Priority 1 and Priority 2 Passes

2 Level (Class + VLAN) + Non-MQC Physical Level

2 Level (Class + VLAN) + Non-MQC Physical Level

Anda mungkin juga menyukai