Xmit-Err on all cisco catalyst 3550

Unanswered Question
Jul 29th, 2008

Hello,

I have a lot of Xmit-Err on all catalyst 3550 when I make an SHOW INT COUNTERS ERROR.

I have upgrade the IOS 1 month ago in version c3550-ipbasek9-mz.122-44.SE2.bin.

This message "Xmit-Err" indicate that the internal transmit is full.

Is there any bug in this version about "Xmit-Err" ?

Is there a network problem on this LAN ? Some time we have bad perform on this network....

All interface are in a-100Mb/a-Full.

Any information about this problem ?

Thanks

Hervé

Attachment: 
I have this problem too.
0 votes
  • 1
  • 2
  • 3
  • 4
  • 5
Overall Rating: 0 (0 ratings)
Loading.
garytayl Tue, 07/29/2008 - 07:41

From documentation:

Xmit Error

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

This is an indication that the internal send (Tx) buffer is full.

Common Causes: A common cause of Xmit-Err might be traffic from a high bandwidth link

being switched to a lower bandwidth link, or traffic from multiple inbound links being

switched to a single outbound link. For example, if a large amount of bursty traffic comes

in on a gigabit interface and is switched out to a 100Mbps interface, this might cause

Xmit-Err to increment on the 100Mbps interface. This is because the interface's output

buffer is overwhelmed by the excess traffic due to the speed mismatch between the incoming

and outgoing bandwidths.

Do you have buffer failures under the show int? If yes, you may want to consider a possible workaround (not a fix), buffer tuning by Configuring Minimum-Reserve Levels as explained under:

http://www.cisco.com/en/US/docs/switches/lan/catalyst3550/software/release/12.2_44_se/configuration/guide/swqos.html#wp1130547

rherve Tue, 07/29/2008 - 07:56

Yes I have buffer failures under the show interface.

1154988 output buffer failures, 0 output buffers swapped out

Thanks for our help

Herve

garytayl Tue, 07/29/2008 - 08:14

Well, in that case try to configure something like the following in one port only, so you can test it. Remember to clear the counters at least for that specific interface so you can monitor.

Enable Qos:

switch # mls qos

## Assigning Level 8 to buffer size 170.

Switch(config)#mls qos min-reserve 8 170

## Configure a port for testing purposes.

Switch(config)#interface fastethernet

## Mapping Q-1-2-3-4 to level 8.

Switch(config-if)#wrr-queue min-reserve 1 8

Switch(config-if)#wrr-queue min-reserve 2 8

Switch(config-if)#wrr-queue min-reserve 3 8

Switch(config-if)#wrr-queue min-reserve 4 8

angedibartolo Fri, 08/01/2008 - 00:12

Hi Gary,

Thanks for your reply.

I work with Hervé on this problem.

I tried your workaround on an interface but the counters still increased on this one..

Do you think that this issue provided from a broadcast storm or something like that?

Thanks,

Angelique

garytayl Fri, 08/01/2008 - 08:20

It might be. Only way to be 100% sure is using a sniffer.

Actions

This Discussion