- A virtual community of network engineers
 Home  BookStore  StudyNotes  Links  Archives  StudyRooms  HelpWanted  Discounts  Login
RE: 3550 policing posted 07/11/2007
[Chronological Index] [Thread Index] [Top] [Date Prev][Date Next] [Thread Prev][Thread Next]

The command "show policy-map interface" is not supported in the 3550/3560's.

You should use "sh mls qos int fx/x policers" and "sh mls qos int fx/x

" Do not use the show policy-map interface privileged EXEC command to
display classification information for incoming traffic. The interface
keyword is not supported, and you should ignore the statistics shown in the
display. Instead, you should specify the DSCPs to be monitored by using the
mls qos monitor dscp dscp1 ... dscp8 interface configuration command, and
then you should use the show mls qos interface interface-id statistics
privileged EXEC command. For more information about these commands, see the
command reference for this release. " 

By the way, the Catalyst 3550 12.2.25SEE documentation was removed from the
DocCD and moved to the CCO :(

-----Original Message-----
From: nobody@xxxxxxxxxxxxxx [mailto:nobody@xxxxxxxxxxxxxx] On Behalf Of
Carlos G Mendioroz
Sent: quarta-feira, 11 de Julho de 2007 20:34
To: ccielab@xxxxxxxxxxxxxx
Subject: 3550 policing

I'm trying to apply some rate limits to some traffic that goes across a

Reading 3550 features, it's kind of clear that you should be able to do that
using MQC, using classes with only one match.
There are some restrictions, but it seems that 1 access group based class
(ip access list) with a police statement, applied to an port in the ingress

But it's not working. mls qos enabled, the policy is accepted, but no
traffic gets dropped. Actually, a show policy interface shows 0 packets
conforming to the class, but I know that is not the case.
It seems I'm missing something...

Any ideas ?
Carlos G Mendioroz  <tron@xxxxxxxxxxx>  LW7 EQI  Argentina

Subscription information may be found at: