--- On Fri, 4/2/11, Michael Crilly <[email protected]> wrote:
> After some playing around, I am
> getting this output from the 'mls qos int gi0/2 stat'
> command:
>
As another poster pointed out it doesn't look like you have the policy-map
applied to the interface.
If the QoS WAS working, then you would see stats that reflect packets having
the DSCP value changed on ingress. These show up in the "classified" column.
EG.
#show mls qos int fa0/3 stat
FastEthernet0/3
Ingress
dscp: incoming no_change classified policed dropped (in pkts)
0 : 2060620 1127162 119850 0 0
8 : 0 0 0 0 0
16: 0 0 0 0 0
24: 0 0 0 0 0
32: 0 0 0 0 0
40: 0 0 0 0 0
46: 0 0 186796526 0 0
56: 119850 0 0 0 0
Others: 185863068 0 0 0 0
In this example there has been 186796526 inbound packets that have been
classified as DSCP-46 by the QoS policy. This is the number that you need to
see incrementing if your QoS policy is working. If a packet enters that already
is marked as DSCP-46 and it matches your QoS policy to tag it as DSCP-46 too,
then it should go into the "no change" column.
regards,
Tony.
_______________________________________________
cisco-nsp mailing list [email protected]
https://puck.nether.net/mailman/listinfo/cisco-nsp
archive at http://puck.nether.net/pipermail/cisco-nsp/
