Ok, after much frustration with the funky way Cisco implements policy-maps and policing on the 3750 I stumbled upon the rate-limit command and want to know if there is a difference in what I am doing.
Basically I have a 3X3750 stack. I want to police traffic on a guest vlan down to 1Mbs. When configuring policing I have found that you have to do the policing in a child policy-map and the only way to do a match that is legal is by input-interface. So the first attempt was to add gi1/0/1-gi3/0/12 but it says they are mismatched ports even though the switches are exactly the same. Then I was able to do multiple classes and add the policing under each class(3 classes for 3 switches matching the interfaces for each switch). This took but did not seem to police the bandwidth, viewing the vlan interface policy-map it showed match-all on the classes so I am guessing that may be why it was failing to match, although I am not sure, and there was no way to change it to match any.
To make a long story short either you have to be very creative or just lucky to get policies to work in this instance.
So while looking for stats on the vln interface a came across rate-limit stats and went to the interface and aplied a rate-limit directly on the vlan interface. It took and I am in the process of testing it now.
Now for the question, in this instance I just want to police trafic to 1 Mbs and I do not need to set dscp values for outgoing packets and such. Is there a reason not to use rate-limit here?
Policing in the 3750 is only available on ingress traffic, not egress. Policing can only be configured through MQC. This means there is no interface specific command to police the traffic. It's a limitation in the hardware.
For more information on QoS in the 3750, please see:
So are you saying that it should not have taken or that it just won't work? Because the vlan interface does show the rate-limit command in there when I do a show run but I have not had a chance to actually test that it works.
You would think that will all the errors I get with doing standard Policy maps there would at least be an error when I applied the rate-limit.
We are pleased to announce availability of Beta software for 16.6.3.
16.6.3 will be the second rebuild on the 16.6 release train targeted
towards Catalyst 9500/9400/9300/3850/3650 switching platforms. We are
looking for early feedback from customers befor...
Introduction Featured Speakers Luis Espejel is the Telecommunications
Manager of IENova, an Oil & Gas company. Currently he works with Cisco
IOS® and Cisco IOS XE platforms, and NX to some extent. He has also
worked as a Senior Engineer with the Routing P...
In this session you can learn more about Layer 3 multicast and the best
practices to identify possible threats and take security measures. It
provides an overview of basic multicast, the best security practices for
use of this technology, and recommendati...