Can output drops on a switch cause input/output errors on a server interface?

[Blackschwanzer]

Hello.

A Unix server, directly connected to a int GigabitEthernet13/41 on a Cisco switch, is displaying RX and TX errors (hundreds of thousands of them).

On the switch int GigabitEthernet13/41, there are no errors of any kind (counters cleared +1 year ago), but there are Total output drops: 13969996.

Is there any possibility that these output drops could somehow cause input/output errors on the server?

The cabling and server's NIC was replaced, but the errors on the server interface remain.

Thank you

[Leo Laohoo]

Kindly post the complete output to the command "sh int Gi 13/41".

[Blackschwanzer · Accepted solution]

Here's the output:

SWITCH#sh int GigabitEthernet13/41 
GigabitEthernet13/41 is up, line protocol is up (connected) 
Hardware is C6k 1000Mb 802.3, address is 0111.843e.abc8 (bia 0111.843e.abc8) 
Description: xxxx
MTU 1500 bytes, BW 1000000 Kbit, DLY 10 usec, 
reliability 245/255, txload 1/255, rxload 1/255 
Encapsulation ARPA, loopback not set 
Keepalive set (10 sec) 
Full-duplex, 1000Mb/s 
input flow-control is off, output flow-control is off 
Clock mode is auto 
ARP type: ARPA, ARP Timeout 04:00:00 
Last input 00:00:10, output 00:00:17, output hang never 
Last clearing of "show interface" counters 1y13w 
Input queue: 0/2000/0/0 (size/max/drops/flushes); Total output drops: 13969996 
Queueing strategy: fifo 
Output queue: 0/40 (size/max) 
5 minute input rate 0 bits/sec, 0 packets/sec 
5 minute output rate 3000 bits/sec, 6 packets/sec 
243921725 packets input, 85974891572 bytes, 0 no buffer 
Received 851739 broadcasts (524765 multicasts) 
0 runts, 0 giants, 0 throttles 
0 input errors, 0 CRC, 0 frame, 0 overrun, 0 ignored 
0 watchdog, 0 multicast, 0 pause input 
0 input packets with dribble condition detected 
338112958 packets output, 56521487590 bytes, 0 underruns 
6984998 output errors, 0 collisions, 0 interface resets 
0 babbles, 0 late collision, 0 deferred 
0 lost carrier, 0 no carrier, 0 PAUSE output 
0 output buffer failures, 0 output buffers swapped out

[Leo Laohoo]

---

@Blackschwanzer wrote:

reliability 245/255

---

Thanks.  The output is very helpful. 

The output error is caused by a Layer 1 issue.  The value (above) should always be "255/255".  Any other value is always indicative of a cable issue.

[Blackschwanzer]

Thank you, Leo.