Solved: QoSwhat is queue 0-3 on qos statistics?

netone.cisco · ‎02-08-2012

Hi everyone,

I'm following a QoS project implementation of a VoIP QoS project and dont have much experience. Voice packets are being marked 5 (COS) and EF (DSCP. Because of a bug on some devices some voice packets are being marked with 6 on COS but still EF on DSCP.

My question is: we configure queues 1-4 but the "show mls qos int statistics" I see queues 0-3 and a lot of packets on queue 1. Why? what is the correspondence from 03- to 1-4?

below a config of one of the switches interfaces, queueing configuration and the show mls qos int statistics

Cisco IOS Software, C2960 Software (C2960-LANBASEK9-M), Version 12.2(58)SE1,

!

interface FastEthernet0/23

description ...

switchport trunk allowed vlan 250,610,611

switchport mode trunk

duplex full

priority-queue out

mls qos trust dscp

storm-control broadcast level bps 1m 800k

storm-control multicast level bps 1m 800k

spanning-tree guard loop

end

#show run | i mls qos

mls qos map cos-dscp 0 8 16 24 32 40 46 56

mls qos srr-queue input cos-map queue 1 threshold 2 1

mls qos srr-queue input cos-map queue 1 threshold 3 0

mls qos srr-queue input cos-map queue 2 threshold 1 2

mls qos srr-queue input cos-map queue 2 threshold 2 4 6 7

mls qos srr-queue input cos-map queue 2 threshold 3 3 5

mls qos srr-queue output cos-map queue 1 threshold 3 5

mls qos srr-queue output cos-map queue 2 threshold 3 3 6 7

mls qos srr-queue output cos-map queue 3 threshold 3 2 4

mls qos srr-queue output cos-map queue 4 threshold 3 0

no mls qos rewrite ip dscp

...

#show mls qos int fa0/23 statistics

FastEthernet0/23 (All statistics are in packets)

dscp: incoming

-------------------------------

0 - 4 : 3844581514 0 81121 0 1154

5 - 9 : 0 0 0 0 0

10 - 14 : 0 0 0 0 251

15 - 19 : 0 3236 0 0 0

20 - 24 : 0 0 0 0 0

25 - 29 : 0 0 0 0 0

30 - 34 : 0 0 2 0 0

35 - 39 : 0 0 0 0 0

40 - 44 : 0 0 0 0 0

45 - 49 : 0 4776323 0 89278 0

50 - 54 : 0 0 0 0 0

55 - 59 : 0 0 0 0 0

60 - 64 : 0 0 0 9090345

dscp: outgoing

-------------------------------

0 - 4 : 3123062836 0 0 0 487

5 - 9 : 0 0 0 0 0

10 - 14 : 0 0 0 0 9414

15 - 19 : 0 177928 0 14155837 0

20 - 24 : 0 0 0 0 147268

25 - 29 : 0 38468 0 0 0

30 - 34 : 0 0 1265294 0 89545

35 - 39 : 0 0 0 0 0

40 - 44 : 0 0 0 0 0

45 - 49 : 0 7821678 0 7567489 0

50 - 54 : 0 0 0 0 0

55 - 59 : 0 0 0 0 0

60 - 64 : 0 0 0 296022

cos: incoming

-------------------------------

0 - 4 : 3854791191 0 0 0 0

5 - 7 : 4175630 86010 632361

cos: outgoing

-------------------------------

0 - 4 : 3130198952 26644 14179423 185736 602320

5 - 7 : 7610569 1834695 43223

output queues enqueued:

queue: threshold1 threshold2 threshold3

-----------------------------------------------

queue 0: 7610586 0 0

queue 1: 560730134 288126 677882

queue 2: 14365159 0 410288

queue 3: 1457842 0 2569496253

output queues dropped:

queue: threshold1 threshold2 threshold3

-----------------------------------------------

queue 0: 0 0 0

queue 1: 0 0 0

queue 2: 3 0 0

queue 3: 0 0 0

Policer: Inprofile: 0 OutofProfile: 0

Thanks

Axel Luttgens · ‎02-08-2012

Hello,

Yes, it's a bit annoying: there are four output queues, but some commands expect (display) a zero-based numbering, while others start counting from one.

Go figure... ;-)

Axel

View solution in original post

Axel Luttgens · ‎02-08-2012

Hello,

Yes, it's a bit annoying: there are four output queues, but some commands expect (display) a zero-based numbering, while others start counting from one.

Go figure... ;-)

Axel

netone.cisco · ‎02-08-2012

Luttgens thanks for the reply,

The really strange thing is the statistics show huge amount of packets on queue 1 which according to what you say corresponds to queue 2 (configuration). but I did a SPAN session on the switch port capturing 100K packets and the statistics were:

vlan prio 5: 26 packets

vlan prio 6: 32 packets

vlan prio 7: 98 packets

vlan prio 1: 99842 packets!

so I cant see how that many packets end up in queue 1 (or 2 on configuration).

below the show mls qos statistics after zeroing before capture. as you can see there arent that many packets for queue 1/2

dscp: incoming

-------------------------------

0 - 4 : 195732 0 0 0 0

5 - 9 : 0 0 0 0 0

10 - 14 : 0 0 0 0 0

15 - 19 : 0 0 0 0 0

20 - 24 : 0 0 0 0 0

25 - 29 : 0 0 0 0 0

30 - 34 : 0 0 0 0 0

35 - 39 : 0 0 0 0 0

40 - 44 : 0 0 0 0 0

45 - 49 : 0 61 0 17 0

50 - 54 : 0 0 0 0 0

55 - 59 : 0 0 0 0 0

60 - 64 : 0 0 0 84

dscp: outgoing

-------------------------------

0 - 4 : 147980 0 0 0 0

5 - 9 : 0 0 0 0 0

10 - 14 : 0 0 0 0 0

15 - 19 : 0 0 0 390 0

20 - 24 : 0 0 0 0 108

25 - 29 : 0 59 0 0 0

30 - 34 : 0 0 8 0 2

35 - 39 : 0 0 0 0 0

40 - 44 : 0 0 0 0 0

45 - 49 : 0 16753 0 108 0

50 - 54 : 0 0 0 0 0

55 - 59 : 0 0 0 0 0

60 - 64 : 0 0 0 7

cos: incoming

-------------------------------

0 - 4 : 195792 0 0 0 0

5 - 7 : 61 17 224

cos: outgoing

-------------------------------

0 - 4 : 165281 0 0 0 6

5 - 7 : 51 71 7

output queues enqueued:

queue: threshold1 threshold2 threshold3

-----------------------------------------

queue 0: 51 0 0

queue 1: 88627 0 108

queue 2: 0 0 0

queue 3: 94 0 76709

output queues dropped:

queue: threshold1 threshold2 threshold3

-----------------------------------------

queue 0: 0 0 0

queue 1: 0 0 0

queue 2: 0 0 0

queue 3: 0 0 0

Policer: Inprofile: 0 OutofProfile: 0

Axel Luttgens · ‎02-08-2012

I'm lost now...

Are you still considering interface fa0/23, as in your original post?

The one that is configured to trust dscp?

Also, could you post the output of "sh mls qos maps"?

Axel

netone.cisco · ‎02-09-2012

Luttgens,

The new capture was done on another switch/interface that I have physical access to but configs are exactly the same regarding queues and trust dscp. Also 2960 LAN BASE. But the symptoms are the same on the first. Lots of traffic on queue 1 (show mls qos stats command).

below the "show mls qos maps"

Policed-dscp map:

d1 : d2 0 1 2 3 4 5 6 7 8 9

---------------------------------------

0 : 00 01 02 03 04 05 06 07 08 09

1 : 10 11 12 13 14 15 16 17 18 19

2 : 20 21 22 23 24 25 26 27 28 29

3 : 30 31 32 33 34 35 36 37 38 39

4 : 40 41 42 43 44 45 46 47 48 49

5 : 50 51 52 53 54 55 56 57 58 59

6 : 60 61 62 63

Dscp-cos map:

d1 : d2 0 1 2 3 4 5 6 7 8 9

---------------------------------------

0 : 00 00 00 00 00 00 00 00 01 01

1 : 01 01 01 01 01 01 02 02 02 02

2 : 02 02 02 02 03 03 03 03 03 03

3 : 03 03 04 04 04 04 04 04 04 04

4 : 05 05 05 05 05 05 05 05 06 06

5 : 06 06 06 06 06 06 07 07 07 07

6 : 07 07 07 07

Cos-dscp map:

cos: 0 1 2 3 4 5 6 7

--------------------------------

dscp: 0 8 16 24 32 40 46 56

IpPrecedence-dscp map:

ipprec: 0 1 2 3 4 5 6 7

--------------------------------

dscp: 0 8 16 24 32 40 48 56

Dscp-outputq-threshold map:

d1 :d2 0 1 2 3 4 5 6 7 8 9

------------------------------------------------------------

0 : 02-01 02-01 02-01 02-01 02-01 02-01 02-01 02-01 02-01 02-01

1 : 02-01 02-01 02-01 02-01 02-01 02-01 03-01 03-01 03-01 03-01

2 : 03-01 03-01 03-01 03-01 03-01 03-01 03-01 03-01 03-01 03-01

3 : 03-01 03-01 04-01 04-01 04-01 04-01 04-01 04-01 04-01 04-01

4 : 01-01 01-01 01-01 01-01 01-01 01-01 01-01 01-01 04-01 04-01

5 : 04-01 04-01 04-01 04-01 04-01 04-01 04-01 04-01 04-01 04-01

6 : 04-01 04-01 04-01 04-01

Dscp-inputq-threshold map:

d1 :d2 0 1 2 3 4 5 6 7 8 9

------------------------------------------------------------

0 : 01-01 01-01 01-01 01-01 01-01 01-01 01-01 01-01 01-01 01-01

1 : 01-01 01-01 01-01 01-01 01-01 01-01 01-01 01-01 01-01 01-01

2 : 01-01 01-01 01-01 01-01 01-01 01-01 01-01 01-01 01-01 01-01

3 : 01-01 01-01 01-01 01-01 01-01 01-01 01-01 01-01 01-01 01-01

4 : 02-01 02-01 02-01 02-01 02-01 02-01 02-01 02-01 01-01 01-01

5 : 01-01 01-01 01-01 01-01 01-01 01-01 01-01 01-01 01-01 01-01

6 : 01-01 01-01 01-01 01-01

Cos-outputq-threshold map:

cos: 0 1 2 3 4 5 6 7

------------------------------------

queue-threshold: 4-3 2-1 3-3 2-3 3-3 1-3 2-3 2-3

Cos-inputq-threshold map:

cos: 0 1 2 3 4 5 6 7

------------------------------------

queue-threshold: 1-3 1-2 2-1 2-3 2-2 2-3 2-2 2-2

Dscp-dscp mutation map:

Default DSCP Mutation Map:

d1 : d2 0 1 2 3 4 5 6 7 8 9

---------------------------------------

0 : 00 01 02 03 04 05 06 07 08 09

1 : 10 11 12 13 14 15 16 17 18 19

2 : 20 21 22 23 24 25 26 27 28 29

3 : 30 31 32 33 34 35 36 37 38 39

4 : 40 41 42 43 44 45 46 47 48 49

5 : 50 51 52 53 54 55 56 57 58 59

6 : 60 61 62 63

netone.cisco · ‎02-09-2012

I saw a light!!!..

If we use "mls qos trust dscp" on the packet input interface does it mean it uses dscp-output-q map? and instead of using "mls qos srr-queue output cos-map ..." i should user "mls qos srr-queue output dscp-map..."??

Axel Luttgens · ‎02-09-2012

Hello,

Yes, something like that could be considered...

According to your maps, paquets liable to enter output queue 2 (counting from 1) are those with a DSCP value between 0 and 15, or a CoS value equal to 1, 3, 6 or 7 (your mutation maps are null maps).

Since you are trusting dscp, the DSCP value is the one that is considered for IP traffic.

For non IP traffic,if any, the CoS value may be used if there is one (this should be the majority, given your config excerpt) or a default CoS value (usually 0, if not changed by config), subject to the Cos-dscp map.

HTH,

Axel

netone.cisco · ‎02-17-2012

Luttgens,

Thanks very much. I have been reading and reading after your very helpful posts. My tests revealed that the dscp trust was indeed the cause for that many packets in queue 2.

From my tests I came across another question which is bugging me.

https://supportforums.cisco.com/thread/2132565

MP

Axel Luttgens · ‎02-18-2012

Hello Mario,

Thanks for having let me know I managed to be of some help. :-)

Wishing you good luck and a lot of fun (?) with your QoS project,

Axel