MQC Class-Based Generic Traffic Shaping

As the QoS sections are pending updates at the moment, I'm on a v4 rack at the moment completing these sections from the v5 workbook.

I've configured R6 as per the solution configurtion and I've generated traffic as suggested. When I try to examine the shaping statistics using the sugested command,"show policy-map interface fastEthernet 0/0.146", I am not seeing the same output as is given in the workbook. Is this due to a difference in IOS versions or am I missing something silly? Is there another way to see the shaping queue stats?

Workbook Output

<span class="code-bold">Rack1R6#show policy-map interface fastEthernet 0/0.146</span>


  Service-policy output: SHAPE_VLAN146

    Class-map: class-default (match-any)
      65844 packets, 28003483 bytes
      5 minute offered rate 334000 bps, drop rate 0 bps
      Match: any 
      Traffic Shaping
           Target/Average   Byte   Sustain   Excess    Interval  Increment
             Rate           Limit  bits/int  bits/int  (ms)      (bytes)  
           <span class="code-highlight">384000/384000    1920   7680      7680      20</span>        960      

        Adapt  Queue     Packets   Bytes     Packets   Bytes     Shaping
        Active Depth                         Delayed   Delayed   Active
        -      <span class="code-highlight">6</span>         65838     27998907  56930     27085058  <span class="code-highlight">yes</span>
Actual Output
Rack2R6#show policy-map interface fastEthernet 0/0.146

Service-policy output: SHAPE_VLAN146

Class-map: class-default (match-any)
396088 packets, 73355658 bytes
5 minute offered rate 365000 bps, drop rate 0 bps
Match: any
queue limit 64 packets
(queue depth/total drops/no-buffer drops) 0/0/0
(pkts output/bytes output) 396088/79685327
shape (average) cir 384000, bc 7680, be 7680
target shape rate 384000


  • Hi Jimmy,

    I remember such "problems" when going over QoS section. In my opinion, what's most important is the information content, not really the way is presented in the CLI. So yes, in this case it's IOS version related issue, your's being newer than the one being used when the workbook topic was developed.

Sign In or Register to comment.