Can anybody explain how to rate limit on a physical port on a Cisco 3560 for egress? Cisco must have hired Microsoft idiots to create their latest products, because the 3550 was much better and more straight forward to configure, and it was easier to understand what each image was licensed to do.
In software releases earlier than Cisco IOS Release 12.2(25)SE, you can configure policing only on a physical port. You can configure the trust state, set a new DSCP or IP precedence value in the packet, or define an individual or aggregate policer. For more information, see the "Policing on Physical Ports" section.
In Cisco IOS Release 12.2(25)SE or later, you can configure policing on a physical port or an SVI. For more information about configuring policing on physical ports, see the "Policing on Physical Ports" section. When configuring policy maps on an SVI, you can create a hierarchical policy map and can only define an individual policer in the secondary interface-level policy map. For more information, see the "Policing on SVIs" section.
It's really the same on both switch models if you have the same IOS version/feature set. Doing a show ver or dir at the CLI will show what you're running.
So what Cisco has essentially done is make bi-directional QOS support something that is much more costly than it was in the 3550 if you want true granularity. Setting the bandwidth for the Egress srr-queue is useless for what we do.
Just like Microsoft. Pure cheeze.