- Cisco Community
- Technology and Support
- Networking
- Routing
- Nested QoS Policy
- Subscribe to RSS Feed
- Mark Topic as New
- Mark Topic as Read
- Float this Topic for Current User
- Bookmark
- Subscribe
- Mute
- Printer Friendly Page
Nested QoS Policy
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
06-05-2011 11:48 PM - edited 03-04-2019 12:36 PM
I have a traditional network with a single head office and multiple branches (28) connected via a carrier IPWAN. The head office bandwidth into the IPWAN cloud is policed by the carrier to 20Mb and branches have varying bandwidth provided in the range of .5 - 6Mb.
Wanting to place some QoS at my head office link with the aim to
- Police outbound traffic to a maximum of 20Mb
- Shape outbound traffic to branches to the speed of the link at the branch
- Assign bandwidth to traffic classes
I just want to confirm that the following config does what i think it should do. Also i have some questions.
How does the allocated bandwidth from my policy-map QUEUING get applied to each site class? Does the bandwidth simply get divided by the amount of classes or does the shape-average under each class of the policy-map shapeToBranches change the available bandwidth. Obiosuly i don't need and can't use 6M for my class MulitmediaLOW for a site which only has a 512K link.
My reasoning is
•That I would rather see the drops on my interface, rather than have the carrier drop my traffic,
•I do not want to flood branches with greater amounts of traffic than they can handle and have the carrier drop this at the branch PE.
•Prioritise certain traffic types
policy-map QUEUING
class MultimediaHIGH
set ip dscp ef
priority 340
class MultimediaLOW
set ip dscp af41
priority remaining percent 40 40% of reaming bandwidth = .4*((20M * .75)-340) = 6008kbps
random-detect dscp-based
class InteractiveHIGH
set ip dscp af31
bandwidth remaining percent 30 30% of reaming bandwidth = .3*((20M * .75)-340) = 4506kbps
random-detect dscp-based
class class-default Default 25% remaining
fair-queue
random-detect dscp-based
!!
!
policy-map shapeToBranches
class traffictoAdelaide
shape average 512000
service-policy QUEUING
class traffictoAlbury
shape average 512000
service-policy QUEUING
class traffictoBendigo
shape average 1024000
service-policy QUEUING
class traffictoCairns
shape average 512000
service-policy QUEUING
class traffictoCampbelltown
shape average 1536000
service-policy QUEUING
class traffictoCardiff
shape average 1024000
service-policy QUEUING
class traffictoChatswood
shape average 4096000
service-policy QUEUING
class traffictoCoffsHarbour
shape average 512000
service-policy QUEUING
class traffictoCrestmead
shape average 4096000
service-policy QUEUING
class traffictoDarwin
shape average 512000
service-policy QUEUING
class traffictoErskinePark
shape average 4096000
service-policy QUEUING
class traffictoCairnsGW
shape average 512000
service-policy QUEUING
class traffictoHobart
shape average 512000
service-policy QUEUING
class traffictoKilsyth
shape average 1024000
service-policy QUEUING
class traffictoKnoxfield
shape average 4096000
service-policy QUEUING
class traffictoLaunceston
shape average 512000
service-policy QUEUING
class traffictoMackay
shape average 512000
service-policy QUEUING
class traffictoMaddington
shape average 2048000
service-policy QUEUING
class traffictoMaryborough
shape average 512000
service-policy QUEUING
class traffictoMurwillumbah
shape average 512000
service-policy QUEUING
class traffictoOrange
shape average 512000
service-policy QUEUING
class traffictoQueanbeyan
shape average 512000
service-policy QUEUING
class traffictoRockhampton
shape average 512000
service-policy QUEUING
class traffictoRydalmere
shape average 1024000
service-policy QUEUING
class traffictoStLeonardsDR
shape average 6144000
service-policy QUEUING
class traffictoSunshineCoast
shape average 512000
service-policy QUEUING
class traffictoTownsville
shape average 512000
service-policy QUEUING
class traffictoUnderwood
shape average 512000
service-policy QUEUING
policy-map QOS-OUT
class class-default
shape average 20480000
service-policy shapeToBranches
!
interface GigabitEthernet0/1
bandwidth 20480
service-policy output QOS-OUT
- Labels:
-
Routing Protocols
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
06-06-2011 04:48 AM
BUMP
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
06-06-2011 06:07 AM
Hi,
I recommend to design QoS at hub and branch sites accordingly with site specific basis. You can apply shaping at branch level including classes at branch site itself instead of configuring at hub router. You can do shaping at Hub site for overall aggregate bandwidth usage at class level.
Regards...
-Ashok.
With best regards...
Ashok
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
06-06-2011 05:24 PM
HI Ashok,
Thanks for your reply. i have configured QoS at the Branch office, please see below. Can you please clarify what you mean by the last sentence?
I've been reading quite a bit on QoS and have seen a few examples of the above config. i just want to understand exactly how each branch class will use the allocated bandwidth configured on policy-map QUEUING.
Cheers.
Branch Config:
class-map match-any DataTransferHIGH
match ip dscp cs1
match ip dscp af11
match ip dscp af12
match ip dscp af13
class-map match-any InteractiveLOW
match ip dscp cs2
match ip dscp af21
match ip dscp af22
match ip dscp af23
class-map match-any MultimediaHIGH
match protocol rtp audio
match ip dscp ef
match ip dscp cs5
match ip dscp cs6
match ip dscp cs7
class-map match-any peer2peer
match protocol bittorrent
match protocol edonkey
match protocol fasttrack
match protocol gnutella
match protocol novadigm
class-map match-any InteractiveHIGH
match protocol h323
match protocol skinny
match protocol sip
match protocol telnet
match ip dscp cs3
match ip dscp af31
match ip dscp af32
match ip dscp af33
class-map match-any MultimediaLOW
match access-group name Citrix_Traffic
match ip dscp cs4
match ip dscp af41
match ip dscp af42
match ip dscp af43
!
!
policy-map ShapeandQueue
class MultimediaHIGH
priority 64
set ip dscp ef
class MultimediaLOW
priority 200
set ip dscp af41
class InteractiveHIGH
bandwidth 64
class class-default
fair-queue
random-detect dscp-based
policy-map QOS-OUT
class class-default
shape average 512000
service-policy ShapeandQueue
policy-map drop-peer2peer
class peer2peer
drop
!
interface FastEthernet0/0
service-policy input drop-peer2peer
!
interface FastEthernet0/1
bandwidth 512
service-policy output QOS-OUT
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
06-06-2011 04:55 PM
Disclaimer
The Author of this posting offers the information contained within this posting without consideration and with the reader's understanding that there's no implied or expressed suitability or fitness for any purpose. Information provided is for informational purposes only and should not be construed as rendering professional advice of any kind. Usage of this posting's information is solely at reader's own risk.
Disclaimer
In no event shall Author be liable for any damages whatsoever (including, without limitation, damages for loss of use, data or profit) arising out of the use or inability to use the posting's information even if Author has been advised of the possibility of such damage.
Posting
I believe CBWFQ didn't support the type of policy implementation you've listed, but perhaps a newer version does.
If the policy is accepted, if you show the policy, it, depending on IOS version(?), might show bandwidth allocations, that would answer your question about what bandwidth percentages the child polices would use.
PS:
Advise against using random-detect unless you really, really understand it.
On many platforms that don't support HQF, FQ in class-default might distort bandwidth guaranteed to defined classes.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
06-06-2011 06:07 PM
Hi Joseph,
Policy is accepted on 2821 (c2800nm-adventerprisek9_ivs-mz.124-24.T5.bin).
Below is the output of show policy-map int gi0/1
Thanks for the tips on random-detect and fair que.
As mentioned before what i really want to know is how each class in the Policy Map shapeToBranches will use the bandwidth allocation in the policy-map QUEUING. A prioirity bandwidth of 340K for voice is ok for a remote Branch which has a WAN link of 4M but not ideal for a site which only has a 512K link.
Marked in red is bandwidth which will be allocated to each class within the 2nd level child policy (remote branch class). How are these bandwidths calculated?
CUCME_Lab#sho policy-map int gi0/1
GigabitEthernet0/1
Service-policy output: QOS-OUT
Class-map: class-default (match-any)
182 packets, 10971 bytes
5 minute offered rate 0 bps, drop rate 0 bps
Match: any
Queueing
queue limit 64 packets
(queue depth/total drops/no-buffer drops) 0/0/0
(pkts output/bytes output) 183/11031
shape (average) cir 20480000, bc 81920, be 81920
target shape rate 20480000
Service-policy : shapeToBranches
Class-map: traffictoAlbury (match-all)
0 packets, 0 bytes
5 minute offered rate 0 bps, drop rate 0 bps
Match: access-group name traffictoAlbury
Queueing
queue limit 64 packets
(queue depth/total drops/no-buffer drops) 0/0/0
(pkts output/bytes output) 0/0
shape (average) cir 512000, bc 2048, be 2048
target shape rate 512000
Service-policy : QUEUING
queue stats for all priority classes:
queue limit 64 packets
(queue depth/total drops/no-buffer drops) 0/0/0
(pkts output/bytes output) 0/0
Class-map: MultimediaHIGH (match-any)
0 packets, 0 bytes
5 minute offered rate 0 bps, drop rate 0 bps
Match: protocol rtp audio
0 packets, 0 bytes
5 minute rate 0 bps
Match: ip dscp ef (46)
0 packets, 0 bytes
5 minute rate 0 bps
Match: ip dscp cs5 (40)
0 packets, 0 bytes
5 minute rate 0 bps
Match: ip dscp cs6 (48)
0 packets, 0 bytes
5 minute rate 0 bps
Match: ip dscp cs7 (56)
0 packets, 0 bytes
5 minute rate 0 bps
QoS Set
dscp ef
Packets marked 0
Priority: 340 kbps, burst bytes 8500, b/w exceed drops: 0
Class-map: MultimediaLOW (match-any)
0 packets, 0 bytes
5 minute offered rate 0 bps, drop rate 0 bps
Match: access-group name Citrix_Traffic
0 packets, 0 bytes
5 minute rate 0 bps
Match: ip dscp cs4 (32)
0 packets, 0 bytes
5 minute rate 0 bps
Match: ip dscp af41 (34)
0 packets, 0 bytes
5 minute rate 0 bps
Match: ip dscp af42 (36)
0 packets, 0 bytes
5 minute rate 0 bps
Match: ip dscp af43 (38)
0 packets, 0 bytes
5 minute rate 0 bps
Queueing
queue limit 64 packets
(queue depth/total drops/no-buffer drops) 0/0/0
(pkts output/bytes output) 0/0
QoS Set
dscp af41
Packets marked 0
bandwidth remaining 40% (68 kbps)
Class-map: InteractiveHIGH (match-any)
0 packets, 0 bytes
5 minute offered rate 0 bps, drop rate 0 bps
Match: protocol h323
0 packets, 0 bytes
5 minute rate 0 bps
Match: protocol skinny
0 packets, 0 bytes
5 minute rate 0 bps
Match: protocol sip
0 packets, 0 bytes
5 minute rate 0 bps
Match: protocol telnet
0 packets, 0 bytes
5 minute rate 0 bps
Match: ip dscp cs3 (24)
0 packets, 0 bytes
5 minute rate 0 bps
Match: ip dscp af31 (26)
0 packets, 0 bytes
5 minute rate 0 bps
Match: ip dscp af32 (28)
0 packets, 0 bytes
5 minute rate 0 bps
Match: ip dscp af33 (30)
0 packets, 0 bytes
5 minute rate 0 bps
Queueing
queue limit 64 packets
(queue depth/total drops/no-buffer drops) 0/0/0
(pkts output/bytes output) 0/0
QoS Set
dscp af31
Packets marked 0
bandwidth remaining 30% (51 kbps)
Exp-weight-constant: 9 (1/512)
Mean queue depth: 0 packets
dscp Transmitted Random drop Tail drop Minimum Maximum Mark
pkts/bytes pkts/bytes pkts/bytes thresh thresh prob
Class-map: class-default (match-any)
0 packets, 0 bytes
5 minute offered rate 0 bps, drop rate 0 bps
Match: any
Queueing
queue limit 64 packets
(queue depth/total drops/no-buffer drops/flowdrops) 0/0/0/0
(pkts output/bytes output) 0/0
Fair-queue: per-flow queue limit 16
Exp-weight-constant: 9 (1/512)
Mean queue depth: 0 packets
dscp Transmitted Random drop Tail/Flow drop Minimum Maximum Mark
pkts/bytes pkts/bytes pkts/bytes thresh thresh prob
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
06-06-2011 10:02 PM
Hi,
It's working as per your configuration. Let's take your example.
In case of Albury, you have configured the class "traffictoAlbury" with shaped rate 512Kbps. The child policy "Queuing" works on taking 512Kbps as the refernece bandwidth for calculations for this specific class.
So, for MultimediaHIGH, you have provided absolute figure in QUEUING class as 340Kbps.
for MultimediaLOW, you have provided as 40% of remaining bandwidth = 0.4 * (512-340) = 68.8Kbps
for InteractiveHIGH, you have provied as 30% of remaining bandwidth = 0.3 * (512-340) = 51Kbps -> Pls note that "bandwidth remaining percent" considers only the reservations towards Priority class to deduct so that it will obtain the Available bandwidth.
Here is a great link....
Hope it helps...
Regards...
-Ashok.
policy-map shapeToBranches
class traffictoAlbury
shape average 512000
service-policy QUEUING
policy-map QUEUING
class MultimediaHIGH
set ip dscp ef
priority 340
class MultimediaLOW
set ip dscp af41
priority remaining percent 40 40% of reaming bandwidth = .4*((20M * .75)-340) = 6008kbps
random-detect dscp-based
class InteractiveHIGH
set ip dscp af31
bandwidth remaining percent 30 30% of reaming bandwidth = .3*((20M * .75)-340) = 4506kbps
random-detect dscp-based
class class-default Default 25% remaining
fair-queue
random-detect dscp-based
!!
With best regards...
Ashok
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
06-07-2011 12:28 AM
Thanks Ashok, i was was playing around with the bandwidth and priority parameters and i finally saw what you explained above.
But here is some strange results: The policy-map which has a class with a shape average of 4096000 doesn't provide correct percentages as per a site which is configured with shape average 512000. IOS Bug?
policy-map QUEUING
class MultimediaHIGH
set dscp ef
priority percent 14
class MultimediaLOW
set dscp af41
bandwidth percent 40
class InteractiveHIGH
set dscp af31
bandwidth percent 14
class class-default
set dscp af11
fair-queue
random-detect dscp-based
Class-map: traffictoAlbury (match-all)
0 packets, 0 bytes
5 minute offered rate 0 bps, drop rate 0 bps
Match: access-group name traffictoAlbury
Queueing
queue limit 64 packets
(queue depth/total drops/no-buffer drops) 0/0/0
(pkts output/bytes output) 0/0
shape (average) cir 512000, bc 2048, be 2048
target shape rate 512000
Service-policy : QUEUING
queue stats for all priority classes:
queue limit 64 packets
(queue depth/total drops/no-buffer drops) 0/0/0
(pkts output/bytes output) 0/0
Class-map: MultimediaHIGH (match-any)
0 packets, 0 bytes
5 minute offered rate 0 bps, drop rate 0 bps
Match: protocol rtp audio
0 packets, 0 bytes
5 minute rate 0 bps
Match: ip dscp ef (46)
0 packets, 0 bytes
5 minute rate 0 bps
Match: ip dscp cs5 (40)
0 packets, 0 bytes
5 minute rate 0 bps
Match: ip dscp cs6 (48)
0 packets, 0 bytes
5 minute rate 0 bps
Match: ip dscp cs7 (56)
0 packets, 0 bytes
5 minute rate 0 bps
QoS Set
dscp ef
Packets marked 0
Priority: 14% (71 kbps), burst bytes 1750, b/w exceed drops: 0
Class-map: MultimediaLOW (match-any)
0 packets, 0 bytes
5 minute offered rate 0 bps, drop rate 0 bps
Match: access-group name Citrix_Traffic
0 packets, 0 bytes
5 minute rate 0 bps
Match: ip dscp cs4 (32)
0 packets, 0 bytes
5 minute rate 0 bps
Match: ip dscp af41 (34)
0 packets, 0 bytes
5 minute rate 0 bps
Match: ip dscp af42 (36)
0 packets, 0 bytes
5 minute rate 0 bps
Match: ip dscp af43 (38)
0 packets, 0 bytes
5 minute rate 0 bps
Queueing
queue limit 64 packets
(queue depth/total drops/no-buffer drops) 0/0/0
(pkts output/bytes output) 0/0
QoS Set
dscp af41
Packets marked 0
bandwidth 40% (204 kbps)
Class-map: InteractiveHIGH (match-any)
0 packets, 0 bytes
5 minute offered rate 0 bps, drop rate 0 bps
Match: protocol h323
0 packets, 0 bytes
5 minute rate 0 bps
Match: protocol skinny
0 packets, 0 bytes
5 minute rate 0 bps
Match: protocol sip
0 packets, 0 bytes
5 minute rate 0 bps
Match: protocol telnet
0 packets, 0 bytes
5 minute rate 0 bps
Match: ip dscp cs3 (24)
0 packets, 0 bytes
5 minute rate 0 bps
Match: ip dscp af31 (26)
0 packets, 0 bytes
5 minute rate 0 bps
Match: ip dscp af32 (28)
0 packets, 0 bytes
5 minute rate 0 bps
Match: ip dscp af33 (30)
0 packets, 0 bytes
5 minute rate 0 bps
Queueing
queue limit 64 packets
(queue depth/total drops/no-buffer drops) 0/0/0
(pkts output/bytes output) 0/0
QoS Set
dscp af31
Packets marked 0
bandwidth 14% (71 kbps)
Class-map: traffictoChatswood (match-all)
0 packets, 0 bytes
5 minute offered rate 0 bps, drop rate 0 bps
Match: access-group name traffictoChatswood
Queueing
queue limit 64 packets
(queue depth/total drops/no-buffer drops) 0/0/0
(pkts output/bytes output) 0/0
shape (average) cir 4096000, bc 16384, be 16384
target shape rate 4096000
Service-policy : QUEUING
queue stats for all priority classes:
queue limit 64 packets
(queue depth/total drops/no-buffer drops) 0/0/0
(pkts output/bytes output) 0/0
Class-map: MultimediaHIGH (match-any)
0 packets, 0 bytes
5 minute offered rate 0 bps, drop rate 0 bps
Match: protocol rtp audio
0 packets, 0 bytes
5 minute rate 0 bps
Match: ip dscp ef (46)
0 packets, 0 bytes
5 minute rate 0 bps
Match: ip dscp cs5 (40)
0 packets, 0 bytes
5 minute rate 0 bps
Match: ip dscp cs6 (48)
0 packets, 0 bytes
5 minute rate 0 bps
Match: ip dscp cs7 (56)
0 packets, 0 bytes
5 minute rate 0 bps
QoS Set
dscp ef
Packets marked 0
Priority: 14% (102 kbps), burst bytes 2550, b/w exceed drops: 0
Class-map: MultimediaLOW (match-any)
0 packets, 0 bytes
5 minute offered rate 0 bps, drop rate 0 bps
Match: access-group name Citrix_Traffic
0 packets, 0 bytes
5 minute rate 0 bps
Match: ip dscp cs4 (32)
0 packets, 0 bytes
5 minute rate 0 bps
Match: ip dscp af41 (34)
0 packets, 0 bytes
5 minute rate 0 bps
Match: ip dscp af42 (36)
0 packets, 0 bytes
5 minute rate 0 bps
Match: ip dscp af43 (38)
0 packets, 0 bytes
5 minute rate 0 bps
Queueing
queue limit 64 packets
(queue depth/total drops/no-buffer drops) 0/0/0
(pkts output/bytes output) 0/0
QoS Set
dscp af41
Packets marked 0
bandwidth 40% (292 kbps)
Class-map: InteractiveHIGH (match-any)
0 packets, 0 bytes
5 minute offered rate 0 bps, drop rate 0 bps
Match: protocol h323
0 packets, 0 bytes
5 minute rate 0 bps
Match: protocol skinny
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
06-07-2011 01:04 AM
Hi,
It's pretty strange behavior. Not able to correlate any way with shape rate as the shape rate taken into consideration is resulting as 730Kbps instead of 4096Kbps if I work back.
It may be probably IOS bug. Is this happening to any other branch like shape average with 1 or 2Mbps?
Regards...
-Ashok.
With best regards...
Ashok
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
06-08-2011 06:41 PM
Hi Ashok,
i've upgraded my lab to customers IOS (ipbasek9-mz.151-2.T1.bin) and i sill seem to have the same issue, loks like site shaped at 1M, 2M and 4M all get the same bandwidth. Any ideas?
Class-map: traffictoBendigo (match-all)
0 packets, 0 bytes
5 minute offered rate 0 bps, drop rate 0 bps
Match: access-group name traffictoBendigo
Queueing
queue limit 64 packets
(queue depth/total drops/no-buffer drops) 0/0/0
(pkts output/bytes output) 0/0
shape (average) cir 1024000, bc 4096, be 4096
target shape rate 1024000
Service-policy : QUEUING
queue stats for all priority classes:
queue limit 64 packets
(queue depth/total drops/no-buffer drops) 0/0/0
(pkts output/bytes output) 0/0
Class-map: MultimediaHIGH (match-any)
0 packets, 0 bytes
5 minute offered rate 0 bps, drop rate 0 bps
Match: protocol rtp audio
0 packets, 0 bytes
5 minute rate 0 bps
Match: ip dscp ef (46)
0 packets, 0 bytes
5 minute rate 0 bps
Match: ip dscp cs5 (40)
0 packets, 0 bytes
5 minute rate 0 bps
Match: ip dscp cs6 (48)
0 packets, 0 bytes
5 minute rate 0 bps
Match: ip dscp cs7 (56)
0 packets, 0 bytes
5 minute rate 0 bps
QoS Set
dscp ef
Packets marked 0
Priority: 15% (105 kbps), burst bytes 2600, b/w exceed drops: 0
Class-map: MultimediaLOW (match-any)
0 packets, 0 bytes
5 minute offered rate 0 bps, drop rate 0 bps
Match: access-group name Citrix_Traffic
0 packets, 0 bytes
5 minute rate 0 bps
Match: ip dscp cs4 (32)
0 packets, 0 bytes
5 minute rate 0 bps
Match: ip dscp af41 (34)
0 packets, 0 bytes
5 minute rate 0 bps
Match: ip dscp af42 (36)
0 packets, 0 bytes
5 minute rate 0 bps
Match: ip dscp af43 (38)
0 packets, 0 bytes
5 minute rate 0 bps
Queueing
queue limit 64 packets
(queue depth/total drops/no-buffer drops) 0/0/0
(pkts output/bytes output) 0/0
QoS Set
dscp af41
Packets marked 0
bandwidth 40% (282 kbps)
Class-map: InteractiveHIGH (match-any)
0 packets, 0 bytes
5 minute offered rate 0 bps, drop rate 0 bps
Match: protocol h323
0 packets, 0 bytes
5 minute rate 0 bps
Match: protocol skinny
0 packets, 0 bytes
5 minute rate 0 bps
Match: protocol sip
0 packets, 0 bytes
5 minute rate 0 bps
Match: protocol telnet
0 packets, 0 bytes
5 minute rate 0 bps
Match: ip dscp cs3 (24)
0 packets, 0 bytes
5 minute rate 0 bps
Match: ip dscp af31 (26)
0 packets, 0 bytes
5 minute rate 0 bps
Match: ip dscp af32 (28)
0 packets, 0 bytes
5 minute rate 0 bps
Match: ip dscp af33 (30)
0 packets, 0 bytes
5 minute rate 0 bps
Queueing
queue limit 64 packets
(queue depth/total drops/no-buffer drops) 0/0/0
(pkts output/bytes output) 0/0
QoS Set
dscp af31
Packets marked 0
bandwidth 13% (91 kbps)
Class-map: class-default (match-any)
0 packets, 0 bytes
5 minute offered rate 0 bps, drop rate 0 bps
Match: any
Queueing
queue limit 64 packets
(queue depth/total drops/no-buffer drops/flowdrops) 0/0/0/0
(pkts output/bytes output) 0/0
QoS Set
dscp af11
Packets marked 0
Fair-queue: per-flow queue limit 16
Exp-weight-constant: 9 (1/512)
Mean queue depth: 0 packets
dscp Transmitted Random drop Tail/Flow drop Minimum Maximum Mark
pkts/bytes pkts/bytes pkts/bytes thresh thresh prob
Class-map: traffictoMaddington (match-all)
0 packets, 0 bytes
5 minute offered rate 0 bps, drop rate 0 bps
Match: access-group name traffictoMaddington
Queueing
queue limit 64 packets
(queue depth/total drops/no-buffer drops) 0/0/0
(pkts output/bytes output) 0/0
shape (average) cir 2048000, bc 8192, be 8192
target shape rate 2048000
Service-policy : QUEUING
queue stats for all priority classes:
queue limit 64 packets
(queue depth/total drops/no-buffer drops) 0/0/0
(pkts output/bytes output) 0/0
Class-map: MultimediaHIGH (match-any)
0 packets, 0 bytes
5 minute offered rate 0 bps, drop rate 0 bps
Match: protocol rtp audio
0 packets, 0 bytes
5 minute rate 0 bps
Match: ip dscp ef (46)
0 packets, 0 bytes
5 minute rate 0 bps
Match: ip dscp cs5 (40)
0 packets, 0 bytes
5 minute rate 0 bps
Match: ip dscp cs6 (48)
0 packets, 0 bytes
5 minute rate 0 bps
Match: ip dscp cs7 (56)
0 packets, 0 bytes
5 minute rate 0 bps
QoS Set
dscp ef
Packets marked 0
Priority: 15% (105 kbps), burst bytes 2600, b/w exceed drops: 0
Class-map: MultimediaLOW (match-any)
0 packets, 0 bytes
5 minute offered rate 0 bps, drop rate 0 bps
Match: access-group name Citrix_Traffic
0 packets, 0 bytes
5 minute rate 0 bps
Match: ip dscp cs4 (32)
0 packets, 0 bytes
5 minute rate 0 bps
Match: ip dscp af41 (34)
0 packets, 0 bytes
5 minute rate 0 bps
Match: ip dscp af42 (36)
0 packets, 0 bytes
5 minute rate 0 bps
Match: ip dscp af43 (38)
0 packets, 0 bytes
5 minute rate 0 bps
Queueing
queue limit 64 packets
(queue depth/total drops/no-buffer drops) 0/0/0
(pkts output/bytes output) 0/0
QoS Set
dscp af41
Packets marked 0
bandwidth 40% (282 kbps)
Class-map: InteractiveHIGH (match-any)
0 packets, 0 bytes
5 minute offered rate 0 bps, drop rate 0 bps
Match: protocol h323
0 packets, 0 bytes
5 minute rate 0 bps
Match: protocol skinny
0 packets, 0 bytes
5 minute rate 0 bps
Match: protocol sip
0 packets, 0 bytes
5 minute rate 0 bps
Match: protocol telnet
0 packets, 0 bytes
5 minute rate 0 bps
Match: ip dscp cs3 (24)
0 packets, 0 bytes
5 minute rate 0 bps
Match: ip dscp af31 (26)
0 packets, 0 bytes
5 minute rate 0 bps
Match: ip dscp af32 (28)
0 packets, 0 bytes
5 minute rate 0 bps
Match: ip dscp af33 (30)
0 packets, 0 bytes
5 minute rate 0 bps
Queueing
queue limit 64 packets
(queue depth/total drops/no-buffer drops) 0/0/0
(pkts output/bytes output) 0/0
QoS Set
dscp af31
Packets marked 0
bandwidth 13% (91 kbps)
Class-map: class-default (match-any)
0 packets, 0 bytes
5 minute offered rate 0 bps, drop rate 0 bps
Match: any
Queueing
queue limit 64 packets
(queue depth/total drops/no-buffer drops/flowdrops) 0/0/0/0
(pkts output/bytes output) 0/0
QoS Set
dscp af11
Packets marked 0
Fair-queue: per-flow queue limit 16
Exp-weight-constant: 9 (1/512)
Mean queue depth: 0 packets
dscp Transmitted Random drop Tail/Flow drop Minimum Maximum Mark
pkts/bytes pkts/bytes pkts/bytes thresh thresh prob
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
06-07-2011 02:15 AM
Disclaimer
The Author of this posting offers the information contained within this posting without consideration and with the reader's understanding that there's no implied or expressed suitability or fitness for any purpose. Information provided is for informational purposes only and should not be construed as rendering professional advice of any kind. Usage of this posting's information is solely at reader's own risk.
Disclaimer
In no event shall Author be liable for any damages whatsoever (including, without limitation, damages for loss of use, data or profit) arising out of the use or inability to use the posting's information even if Author has been advised of the possibility of such damage.
Posting
jjcollaguazo wrote:
Hi Joseph,
Policy is accepted on 2821 (c2800nm-adventerprisek9_ivs-mz.124-24.T5.bin).
Below is the output of show policy-map int gi0/1
Thanks for the tips on random-detect and fair que.
As mentioned before what i really want to know is how each class in the Policy Map shapeToBranches will use the bandwidth allocation in the policy-map QUEUING. A prioirity bandwidth of 340K for voice is ok for a remote Branch which has a WAN link of 4M but not ideal for a site which only has a 512K link.
Marked in red is bandwidth which will be allocated to each class within the 2nd level child policy (remote branch class). How are these bandwidths calculated?
Ah, you are running, I believe, an IOS that support HQF, likely why your multi-level policy is accepted.
BTW, on this version, if I've correctly identified it, FQ works differently. No issue using it in class-default; HQF supports it in any class (which I highly recommend).
Saw your latter posting, which I believe, answers your question about how the child policy inherits parent policy's shaper bandwidth (as we desire); except when it doesn't. The latter could indeed be a bug, might be cosmetic. You might try upgrading to a later release, or even moving off the T version to the next mainline version, now that it's available for 12.4T.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
06-16-2011 08:15 PM
@jjcollaguazo You might get better results if you make a few versions of the QUEUEING policy corresponding to the different speeds at the remote site. then you could configure a smaller amount of priority traffic for the smaller sites.
that is have
policy-map shapeToBranches
class traffictoAdelaide
shape average 512000
service-policy QUEUING-512k
class traffictoBendigo
shape average 1024000
service-policy QUEUING-1024k
etc.
Discover and save your favorite ideas. Come back to expert answers, step-by-step guides, recent topics, and more.
New here? Get started with these tips. How to use Community New member guide