queue length zero

[Dennis Olvany]

In the course of troubleshooting some transmit discards I noticed something peculiar. The output queue length on the discarding interfaces is 0. Shouldn't this be the default length of 40?

GigabitEthernet0/18 is up, line protocol is up (connected)
  input flow-control is off, output flow-control is unsupported
  Last input 00:00:06, output 00:00:11, output hang never
  Input queue: 0/75/0/0 (size/max/drops/flushes); Total output drops: 304756
  Output queue: 0/0 (size/max)
  5 minute output rate 49701000 bits/sec, 5580 packets/sec
     3334146093 packets output, 3193609832897 bytes, 0 underruns
     0 output errors, 0 collisions, 1 interface resets
     0 lost carrier, 0 no carrier, 0 PAUSE output
     0 output buffer failures, 0 output buffers swapped out

[ranraju]

Hi Dennis,

Yes the max size of the output queue is 40. And from the show interface output you are seeing 0/0 - which is incorrect and its a cosmetic issue. Its a buggy behavior, and there are also known bugs for this issue. You see drops incremeting only in "show int", but in "show platform port-asic stats drops" you will not see these drops, as these are the outputs from the hardware. To get a resolution for this issue, upgrade to the lastest available version in that platform.

Hope this answers your query on the post.

(please rate helpful posts)

Regards,

ranraju

[Dennis Olvany]

Thanks for the info. I don't suppose you would know the bug id. I didn't find a match in the toolkit.

[ranraju]

what platform is this? also tell me the version of code that you are running, will see if i can find the bug ID. But however, eventually you have to upgrade the switch, and upgrading it to the latest version available is always a good idea, as a lot of bugs would already be fixed in it.

Hope this answers your query on the post.

(please rate helpful posts)

Regards,

ranraju

[Dennis Olvany]

Cat3560 and cbs3020 both running 12.2.50se3.

[ranraju]

You might want to take a look at this bug, CSCsz61947.

It was seen on 3750, with version 12.2(50)SE or 12.2(50)SE1.

The fix is in 12.2(52)SE, so you could either upgrade to this version, or as i mentioned to the latest available version.

Hope this answers your query on the post.

(please rate helpful posts)

Regards,

ranraju

[Dennis Olvany]

Thanks, I am going to upgrade the ios. I'll let you know the results.