%C4K_HWPORTMAN-4-BLOCKEDTXQUEUE on shutted switchport !?!?

hakan.topcu · ‎11-17-2010

Hi there,

one of our switches is logging the following messages:

Nov 17 13:28:44.289 UTC: %C4K_HWPORTMAN-4-BLOCKEDTXQUEUE: Blocked transmit queue HwTxQId1 on Switch Phyport Gi2/23, count=1335531
Nov 17 13:28:44.289 UTC: %C4K_HWPORTMAN-4-BLOCKEDTXQUEUE: Blocked transmit queue HwTxQId3 on Switch Phyport Gi2/23, count=1335531
Nov 17 13:32:37.285 UTC: %C4K_HWPORTMAN-4-BLOCKEDTXQUEUE: Blocked transmit queue HwTxQId0 on Switch Phyport Gi2/23, count=1286942
Nov 17 13:38:48.770 UTC: %C4K_HWPORTMAN-4-BLOCKEDTXQUEUE: Blocked transmit queue HwTxQId1 on Switch Phyport Gi2/23, count=1335645
Nov 17 13:38:48.770 UTC: %C4K_HWPORTMAN-4-BLOCKEDTXQUEUE: Blocked transmit queue HwTxQId3 on Switch Phyport Gi2/23, count=1335645
Nov 17 13:42:40.274 UTC: %C4K_HWPORTMAN-4-BLOCKEDTXQUEUE: Blocked transmit queue HwTxQId0 on Switch Phyport Gi2/23, count=1287056

Hard- and Software is the following:

Catalyst 4503

IOS Version 12.2(20)EWA4

Supervisor IV WS-X4515

Linecard: WS-X4448-GB-RJ45

Nothing special so far, because this is obviously not a new case. But curiously the message apperas also although the port is shutted and no device is connected!!! Furthermore conspicuously is, that the message appers in an about 6-4-6-4 minutes interval, two times after the 6 minutes interval and one time after the four minutes interval, repeating.

I see a lot of output drops, but they are not further counting, probably since the port is not longer in use. I have tried a shut / no shut a few times without success.

GigabitEthernet2/23 is administratively down, line protocol is down (disabled)
Hardware is Gigabit Ethernet Port, address is 0019.56c9.6516 (bia 0019.56c9.6516)
MTU 1500 bytes, BW 1000000 Kbit, DLY 10 usec,
     reliability 255/255, txload 1/255, rxload 1/255
Encapsulation ARPA, loopback not set
Keepalive set (10 sec)
Auto-duplex, Auto-speed, link type is auto, media type is 10/100/1000-TX
input flow-control is off, output flow-control is off
ARP type: ARPA, ARP Timeout 04:00:00
Last input never, output never, output hang never
Last clearing of "show interface" counters 38w5d
Input queue: 0/2000/0/0 (size/max/drops/flushes); Total output drops: 5995977
Queueing strategy: fifo
Output queue: 0/40 (size/max)
5 minute input rate 0 bits/sec, 0 packets/sec
5 minute output rate 0 bits/sec, 0 packets/sec
     5610 packets input, 979338 bytes, 0 no buffer
     Received 5610 broadcasts (25 multicast)
     0 runts, 0 giants, 0 throttles
     0 input errors, 0 CRC, 0 frame, 0 overrun, 0 ignored
     0 input packets with dribble condition detected
     1100 packets output, 101284 bytes, 0 underruns
     0 output errors, 0 collisions, 0 interface resets
     0 babbles, 0 late collision, 0 deferred
     0 lost carrier, 0 no carrier
     0 output buffer failures, 0 output buffers swapped out

I read some other threads here and also I know about the Bug CSCse29295. And of course the next step I will try ist to reset the module, or the switch. But I have not heard about a case, where this message appears on an shutted port.

Any ideas?

Thanks

Hakan

glen.grant · ‎11-17-2010

Thats probably the only way to get rid of it is to reset the switch if its really admin down .

dixho · ‎11-17-2010

the behavior is definitely a bug. However, I do not think that the problem is caused by CSCse29295 as CSCse29295 should only be seen in

12.2(25)EWA6.

Not sure if you go to the following URL:
https://www.ciscotaccc.com/kaidara-advisor/lanswitching/showcase?case=K90661803

The problem seems to be cosmetic as the port is shutted. If the error message bothers you, I suggest to consider upgrade. If you do want to upgrade, you can set the message level of logging buffer to log message with severity 1 to 3 (i.e. logging buffer error).

hakan.topcu · ‎11-17-2010

no, I didn't know K90661803. But also there is written:

"... error message is generated on a Cisco Catalyst 4500 series switch when connected to a device..."

In our case, there is no device connected and the port is down.

Well, thanks so far. I think there's no getting around to reset the module or the switch as the next step.

Thanks