12-28-2009 07:21 AM - edited 03-06-2019 09:05 AM
In IOS release 12.4(20)T and later the "show policy-map interface X" command no longer displays packets delayed and bytes delayed. Is there a new method to view the traffic shaping statistics?
I found this information at this link: http://www.cisco.com/en/US/docs/ios/qos/command/reference/qos_s4.html#wp1084023
Solved! Go to Solution.
01-04-2010 11:52 AM
Hello Romey,
I tried to look at command reference and HQF introduction but I couldn't find a new show for seeing shaping statistics.
however, if we look at examples reported in HQF introduction
http://www.cisco.com/en/US/docs/ios/qos/configuration/guide/qos_frhqf_support.html#wp1089229
Service-policy output: shape
Class-map: class-default (match-any)
2203 packets, 404709 bytes
30 second offered rate 74000 bps, drop rate 14000 bps
Match: any
Queueing
queue limit 64 packets
(queue depth/total drops/no-buffer drops) 64/354/0
(pkts output/bytes output) 1836/337280
shape (average) cir 128000, bc 1000, be 1000
target shape rate 128000
lower bound cir 0, adapt to fecn 0
you can see that shaping information is still reported but in a different form, so sh policy-map int should still be the show to be used.
Hope to help
Giuseppe
01-07-2010 07:45 AM
Hi,
With HQF, the QoS architecture changed - including that of shaping. Shaping is no longer based on the traditional token bucket algorithm and that's the reason why HQF codes do not have the packets delayed / bytes delayed statistics in the MQC output.
- Abhi
01-04-2010 11:52 AM
Hello Romey,
I tried to look at command reference and HQF introduction but I couldn't find a new show for seeing shaping statistics.
however, if we look at examples reported in HQF introduction
http://www.cisco.com/en/US/docs/ios/qos/configuration/guide/qos_frhqf_support.html#wp1089229
Service-policy output: shape
Class-map: class-default (match-any)
2203 packets, 404709 bytes
30 second offered rate 74000 bps, drop rate 14000 bps
Match: any
Queueing
queue limit 64 packets
(queue depth/total drops/no-buffer drops) 64/354/0
(pkts output/bytes output) 1836/337280
shape (average) cir 128000, bc 1000, be 1000
target shape rate 128000
lower bound cir 0, adapt to fecn 0
you can see that shaping information is still reported but in a different form, so sh policy-map int should still be the show to be used.
Hope to help
Giuseppe
01-07-2010 07:45 AM
Hi,
With HQF, the QoS architecture changed - including that of shaping. Shaping is no longer based on the traditional token bucket algorithm and that's the reason why HQF codes do not have the packets delayed / bytes delayed statistics in the MQC output.
- Abhi
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