Re: "unsupported classification" when using extended acl - 3560

Hi,

The only classification method supported in 2nd-level policy-maps on
the 3560 is "match input-interface" and you typically use nested
policing to enforce per-port policing rates. You can still use
extended classification in the first-level policy map. Some time ago I
made a brief comparison of policing features in 3550/3560 here:
http://blog.ine.com/2008/09/11/comparing-traffic-policing-features-in-the-3550-and-3560-switches/

HTH,

Petr

2010/9/19 Ladee Geek <ladeegeek_at_gmail.com>:
> humm....thought I could match an extended acl and use it for MQC. Not sure
> why I am getting the error noted below on an SVI. Any ideas?
>
> mls qos
>
> class-map match-any tcp-ssh-numb
> match access-group 100
> match access-group 101
>
> policy-map tel-ssh-bw
> class tel-ssh-bw
> police 50000000 8000 exceed-action drop
>
> policy-map parent-numb
> class tcp-ssh-numb
> set dscp af13
> service-policy tel-ssh-bw
>
> interface FastEthernet0/23
> switchport trunk encapsulation dot1q
> switchport trunk allowed vlan 20-22,61
> switchport mode dynamic desirable
> *mls qos vlan-based
> * channel-group 34 mode desirable
>
> SW3(config-pmap-c)#int vl 22
> SW3(config-if)#service-policy in parent-numb
> QoS: class(tcp-ssh-numb) Unsupported classification [Vlan22]
> --
> r/
> LG
>
>
> 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 Sun Sep 19 2010 - 11:41:07 ART