MLS Qos command and Service Policy input

[PacketSpartan]

Hopefully, someone can shed a bit of light on this issue we're seeing, and if it could be related to not configuring the MLS QOS command. 

We've applied a policy map to the to an interface (input) however we're not seeing any hits on any of the class maps at all. We are doing this on our 2960 and we're aware that there is a limitation regarding the limitation of applying the policy map to the egress part of an interface. 

When we the command sh policy-map interface fastEthernet 0/2
we don't see any hits at all

- Do we need to enable MLS Qos command globally for the service policy to become active 

- What changes does the MLS qos command make to the switch?

class-map match-any default-traffic
match access-group name default-traffic
class-map match-any voipAndVideo
match access-group name videoOutboud
match access-group name Video-hosts
match access-group name voip-servers
!
policy-map INBOUND-MPLS-QOS
class voipAndVideo
class default-traffic
!

[Mark Malone]

Hi
What changes does the MLS qos command make to the switch?
it turns on qos globally all interfaces ,also changes how the ASIC process packets , hardware related

if its just a 2960 i would recommend using MLS or Auto as its l2 switch , set the ports to auto qos trust DSCP and the uplink , that will ensure any traffic that is marked at the source is trusted through the switch and not removed , you can then use sh mls qos interface x/x statistics to view the buckets and queues

if you use auto qos and its supported it will actually build all the policy and class maps for you and then you can tweak them if required , i havent used MQC qos on a 2960 so i would need to test it to see what the results were , its a l2 switch so i would suggest again using MLS or Auto rather than MQC

MLS , Auto Qos and MQC are 3 different styles of QOS and can all achieve generally same thing , MQC can probably be more fine tuned that the more automated types like MSL and Auto QOS