Catalyst 3750 - input errors but no breakdown?

[maybeimaleo]

This is what I pulled up:

FastEthernet2/0/26 is up, line protocol is up (connected)
Hardware is Fast Ethernet, address is 000f.f7d7.7a9e (bia 000f.f7d7.7a9e)
MTU 1500 bytes, BW 100000 Kbit, DLY 100 usec,
reliability 255/255, txload 1/255, rxload 1/255
Encapsulation ARPA, loopback not set
Keepalive set (10 sec)
Full-duplex, 100Mb/s, media type is 10/100BaseTX
input flow-control is off, output flow-control is unsupported
ARP type: ARPA, ARP Timeout 04:00:00
Last input never, output 00:00:15, output hang never
Last clearing of "show interface" counters never
Input queue: 0/75/0/0 (size/max/drops/flushes); Total output drops: 0
Queueing strategy: fifo
Output queue: 0/40 (size/max)
5 minute input rate 1000 bits/sec, 1 packets/sec
5 minute output rate 153000 bits/sec, 134 packets/sec
321710759 packets input, 3093871938 bytes, 0 no buffer
Received 11936 broadcasts (0 multicast)
0 runts, 0 giants, 0 throttles
1004 input errors, 0 CRC, 0 frame, 0 overrun, 0 ignored
0 watchdog, 0 multicast, 0 pause input
0 input packets with dribble condition detected
186365234 packets output, 2372427142 bytes, 0 underruns
0 output errors, 0 collisions, 1 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

1004 input errors - but why? I know the one interface reset is because we rebooted the server over ther weekend.

 

[Nazgulero]

Hello,

input errors are usually caused by some sort of a physical problem. I would try one of the following and see if the errors disappear:

- change the cable between your switch and your server
- connect the server to another switchport
- exchange the NIC in the server

Regards,

GP

 

[maybeimaleo]

Thanks!

I will definitly try them (in THAT order)!

 

[lambent]

You can also try updating the NIC driver b4 changing it.

 

[RookThis]

Are the numbers increasing? The output that you denoted indicates that counters have never been cleared. These could be old numbers that were caused but some previous condition. I would first ensure that you are still seeing the number increasing.

Last clearing of "show interface" counters never

 

[maybeimaleo]

Well - changed the cable and port. Already (about 30 minutes into the new connection) I see input errors (nothing was plugged into the new port).

I guess my next step is to update the driver. IF that doesn't work I will swap out the nic card (unless someone out there has any other suggestions).

 

[jneiberger]

Check for a duplex mismatch before you switch NICs. If you have a mismatch then the full duplex side will see input errors and the half duplex side will see late collisions.

John

 

[maybeimaleo]

No mismatch.

I typed sh int to look at the duplex settings. Does that just show what it negotiated at? Is there a different way to look at the negotiated speed and duplex?

 

[jneiberger]

How do you know there is no mismatch? The switch interface is running at 100/Full but you need additional information:

1. What is the interface *configured* for? Is it set to AUTO or do you have it hard-set to 100/Full?

2. What is the connected device *configured* for?

3. What is the connected device operating at? (This is different from #2)

John

 

[maybeimaleo]

How do I check what the interface on the switch is set to?

NIC on the server is set to auto. The NIC on the server is running at 100/full.

 

[jneiberger]

Show run" on the switch will show you what it is configured for. If the server NIC is set to AUTO (which it is, and should be) then make sure the switch is set to AUTO.

If the switch is manually configured to 100/Full then you probably have a hidden mismatch. I'll explain how this happens after you check the switch settings.

John

 

[maybeimaleo]

Name : Fa2/0/17
Administrative Speed: auto
Administrative Duplex: auto
Administrative Auto-MDIX: off
Administrative Power Inline: N/A
Operational Speed: 100
Operational Duplex: full
Operational Auto-MDIX: off

 

[jneiberger]

Good, both sides are set to AUTO. You would have had problems if the switch were hard-set to 100/Full, strangely enough.

I agree with the others. I would suspect a bad cable, bad NIC, or bad NIC drivers. It sounds like you've already changed the cable, so good luck with those NIC drivers!

John

 

[maybeimaleo]

Thanks - that will be my next test....