Thanks Phil! You're right about it not being support...silly that it
still let's you configure things but that's another argument.
I've managed to police the vlan like this now:
class-map match-any test
match any
!
policy-map test
class test
police cir 3000000
conform-action transmit
exceed-action drop
trust cos
!
interface Vlan888
no ip address
load-interval 30
service-policy input test
!
interface GigabitEthernet1/31
mls qos vlan-based
!
Traffic generator confirms that the traffic leaving the 6524 is 3Mbps
when sending 5Mbps through it.
Jose
On 3/8/2011 10:49 AM, Phil Mayers wrote:
On 08/03/11 15:43, Phil Mayers wrote:
On 08/03/11 15:33, Lobo wrote:
I've configured "mls qos vlan-based" on the two physical interfaces
just like we do on our 3750s. ME-6524 is running 12.2(33)SXH6 Advanced
IP Services. Not sure what else I can do considering that the specs
state that this feature is support on this platform.
Are you sure it supports "match interface" for input service policy? I
don't recall that being a supported feature on EARL7 (PFC3) platforms.
In fact:
http://www.cisco.com/en/US/docs/switches/lan/catalyst6500/ios/12.2SX/configuration/guide/qos.html#wp1481044
"""
PFC QoS does not support these class map commands:
...
–match input-interface
"""
_______________________________________________
cisco-nsp mailing list [email protected]
https://puck.nether.net/mailman/listinfo/cisco-nsp
archive at http://puck.nether.net/pipermail/cisco-nsp/
_______________________________________________
cisco-nsp mailing list [email protected]
https://puck.nether.net/mailman/listinfo/cisco-nsp
archive at http://puck.nether.net/pipermail/cisco-nsp/
