I would like to apply a Service Policy Input on some Gigabit ports on Cat4500 platform for the following action:
Is this working??? I'm pretty sure that I can do both packet classification and marking but what about Policing/Shaping? Is this possible?
Otherwise how can I achieve that results considering that I've to apply this limit in input on some ports?
Thanks for a feedback
Classification, marking and policing should be supported on the ingress direction. Shaping is usually on the egress direction, probably not supported. What sup do you use?
I've SUP7L-E with IOS XE 3.4.0SG and at the ingress port the Service Policy is doing classification, marking but is not working on limiting the Bandwidth using the following configuration (the class-map is based on a ACL):
set dscp ef
police 2000000 conform-action transmit exceed-action transmit
set dscp cs4
police 20000000 conform-action transmit exceed-action drop
set dscp default
police 11000000 conform-action transmit exceed-action drop
So you are saying the switch took the command, but policer doesnt work as expected? How did you test it?
Yes the switch took the command and it's on the config... since on the same port we've a similar OUTPUT Policy we 've done some initial test using a speed test with a device that was classified on the class DATA and we've noticed the following results:
- INPUT POLICY traffic was not blocked to 11MB and reach always more speed around 100MB
- OUTPUT POLICY traffic was correctly blocked around 10-11MB max.
like this one:
class-map match-all DATA
match access-group name ACL_IN
where the ACL syntax is the following:
ip access-list extended ACL_IN
permit ip 10.X.X.X 0.X.X.X any
the source IP subnet 10.X.X.X is a VLAN where all these ports belongs, but I would like to been able to give to each port the same BW.
Thnaks a lot for your support!
I thought me too it wasd working :-)))... but in fact the traffic in input is not limited
the Service Policy input is applied to each Physical Interface
I thought it could be a bug... It's difficult to test/prove it since all the switches are in production and if I'll do an upgrade it is because I'm sure this will solve the problem...BTW the only SW available would be the XE3.5.0...