From: lg01 (lg01@myway.com)
Date: Sun May 25 2003 - 09:28:32 GMT-3
Hi Team,
Can someone please explain to me, for policy map, when should one just use the "police" command, and when should we use the "aggregate policer" command?
Or is there any particular "wording" that hints when I should use each?
In my exercise that I'm working on, it goes like "Police port 0/13 of switch1. Limit the speed on this port to 1Mbps, with burst set to 32kps. Drop all packets that exceed this policy"... and the answer ended up using "aggregate policer".
As an e.g., for the "police" command...
mls qos
!
class-map match-all class1
match access-group 102
!
!
policy-map pol1
class class1
police 1000000 32000 exceed-action drop
!
interface FastEthernet0/13
switchport access vlan 813
no ip address
service-policy input pol1
!
access-list 102 permit ip any any
Just for completeness, here comes the "aggregate policer" e.g.
mls qos
!
mls qos aggregate-policer PolicyA 1000000 32000 exceed-action drop
!
class-map match-all All
match access-group 102
!
!
policy-map Test
class All
police aggregate PolicyA
interface FastEthernet0/12
switchport access vlan 800
switchport mode access
no ip address
service-policy input Test
spanning-tree portfast
access-list 102 permit ip any any
And one last question I have got for you guys before heading to bed.
For police OR aggregate-policer, does it work like CAR where the burst value is in bytes? (rather than in bits)
Meaning should my command become.. (to change 32000bits into bytes?)
mls qos aggregate-policer PolicyA 1000000 4000 exceed-action drop
Any help would be greatly appreciated.
Regards,
Hunt
This archive was generated by hypermail 2.1.4 : Mon Jun 02 2003 - 15:13:47 GMT-3