bandwith control policy in Catalyst 3550

[givan]

We have a problem in our network with a Catalyst Switch 3550, which has a bandwith control policy like this:

mls qos aggregate-policer port01_out_kbps 3000000 300000 exceed-action drop

mls qos aggregate-policer port01_in_kbps 3000000 300000 exceed-action drop

Recently we had experienced a physical loop (connecting to ports with a direct cable) in a TPLink switch, which is connected behind our Catalyst 3550 and the broadcast traffic reached very high values (46M) in spite of the policy set on the port of our Catalyst switch. Now, I don´t understand why this happened, why the switch did not control the traffic, as it usually does with normal ranges and normal traffic (TCP/IP). Is this happening because is broadcast? Please help me!!!

[mhussein]

How is the policy and classes configured for this policer? May be that traffic did not match the policy map, so it escaped the policer.

You can use show interfaces counters to see the unicast/multicast/broadcast packet stats.

Use storm-control broadcast level nn to control broadcast if needed:

http://www.cisco.com/univercd/cc/td/doc/product/lan/c3550/12114ea1/3550scg/swtrafc.htm#25516

Regards,

Mustafa

[givan]

These are policy and classes

mls qos aggregate-policer port01_out_kbps 3000000 300000 exceed-action drop

mls qos aggregate-policer port01_in_kbps 3000000 300000 exceed-action drop

class-map match-any class_port01_out

match ip dscp 0

Exit

class-map match-all class_port01_in

match access-group 124

Exit

policy-map policy_port01_in

class class_port01_in

police aggregate port01_in_kbps

Exit

Exit

policy-map policy_port01_out

class class_port01_out

police aggregate port01_out_kbps

Exit

Exit

Int fa 0/1

service-policy input policy_port01_in

service-policy output policy_port01_out

And, yes configure

switchport block multicast

switchport block unicast

storm-control broadcast level 0.01

storm-control multicast level 0.01

storm-control unicast level 2.00