Re: QOS service policy problem

Hi,

Did you include qos pre-classify under the tunnel interface?

http://www.cisco.com/en/US/tech/tk543/tk545/technologies_tech_note09186a008017405e.shtml

Rgds, VJ

On Wed, 2009-08-26 at 23:16 +0800, Andy Reid wrote:
> In addition I have added a WEB policy that classifies traffic to port
> 80. This is also working as expected (along with the voice signaling
> classification and marking).
>
> Additional configuration:
>
> ip access-list extended WEB
> permit tcp any any eq 80
> exit
>
> class-map match-all WEB-IN
> match access-group name WEB
> exit
>
> class-map match-all WEB-OUT
> match ip dscp af21
> exit
>
> policy-map TO-BE-CLASSIFIED
> class WEB-IN
> set ip dscp af21
> exit
> exit
>
> policy-map CLASSIFIED
> class WEB-OUT
> bandwidth percent 30
> exit
> exit
>
> lab#show policy-map interface vlan 10
> Vlan10
> Service-policy input: TO-BE-CLASSIFIED
> Class-map: WEB-IN (match-all)
> 259 packets, 66239 bytes
> 30 second offered rate 9000 bps, drop rate 0 bps
> Match: access-group name WEB
> QoS Set
> dscp af21
> Packets marked 259
>
> lab#show policy-map interface tunnel 1
> Tunnel1
> Service-policy output: PARENT-CLASSIFIED
> Service-policy : CLASSIFIED
> Class-map: WEB-OUT (match-all)
> 251 packets, 69086 bytes
> 30 second offered rate 9000 bps, drop rate 0 bps
> Match: ip dscp af21 (18)
> Queueing
> queue limit 64 packets
> (queue depth/total drops/no-buffer drops) 0/0/0
> (pkts output/bytes output) 0/0
> bandwidth 30% (16 kbps)
>
>
> Blogs and organic groups at http://www.ccie.net
>
> _______________________________________________________________________
> Subscription information may be found at:
> http://www.groupstudy.com/list/CCIELab.html

Blogs and organic groups at http://www.ccie.net
Received on Wed Aug 26 2009 - 20:57:12 ART