 ]--] class class-default shape average 150000000 service-policy - Police-CoS Traffic-Shaping Scenarios Of course, you would need to have a Police-CoS policy map in place. Such a solution would apply if you had an Ethernet handoff to an MPLS cloud with QoS levels in place. Let's take that a step further and look at what the CoS policy map might look like. Remember, though, this has nothing to do with traffic shaping, but it is part of a real- world solution. Here, I have a simple policy map adhering to the levels of service given by the provider. In this case, the levels are: Priority queue: 60 percent Secondary queue: 20 percent Tertiary queue: 10 percent Best effort: remaining 10 percent This code outlines the policy and class maps necessary to accomplish those stats: class-map match-any CoS1 match dscp ef class-map match-any CoS2 match dscp af31 match dscp af32 class-map match-any CoS3 match dscp af21 match dscp af22 policy-map Police-CoS class CoS1 set dscp ef priority percent 60 class CoS2 bandwidth remaining percent 60 class CoS3 bandwidth remaining percent 30 class class-default fair-queue Now you just need to apply this policy map to the interface with the service-policy command: interface GigabitEtherneto/o description Provider MPLS Ethernet 150M bandwidth 150000 ip address 10.10.10.1 255.255.255.252 duplex auto speed auto media-type sfp no negotiation auto service-policy - output Provider-Outbound With all this code in place, we're now traffic shaping, SO let's take a look at the output using the show policy-map interface int-name command: Router# sho policy-map interface g0/0 GigabitEtherneto/a Chapter 32: Designing QoS Service-policy output: Provider-Outbound Class-map: class-default (match-any) 2989747764 packets, 2763665319444 bytes 5 minute offered rate 83672000 bps, drop rate 0 bps Match: any Traffic Shaping Target/Average Sustain Excess Interval Increment Limit bits/int bits/int (bytes) 150000000/150000000 937500 3750000 3750000 468750 Adapt Queue Packets Bytes Packets Bytes Shaping Active Depth 