CRC errors on FE

[dimitri.kim]

Hello there,

What is the most common problem for apprearing input CRC, overrun on a fast ethernet switch(C3500XL-C3H2S-M, Version 12.0(5.2)XU).

The interface of the other end-point is Intel Pro/1000MT Dual Port Server Adapter. I set both switch and Intel to 100-FD and Auto, but the result was same.

"294 input errors, 294 CRC, 0 frame, 314 overrun, 314 ignored"

One more question, is there any way to analyze CRC errors like sniffer?

Thanks in advance.

[deilert]

dimitri these are geerally caused by some kind of layer 2 issue on the LAN, broadcast storm, a device not particpiating in STP iss plugged in somewhere.

these usually go hand in hand with duplicate ip address messages sourced from the HSRP mac.

Look for a rogue Linsys on the Lan

[dimitri.kim]

Hello Deilert,

Could you explain the below meaning little more in detail?

>>> these usually go hand in hand with duplicate ip address messages sourced from the HSRP mac. <<<

Thanks in advance.

[deilert]

Because of the layer 2 loop on the lan, you will end up learning your own mac address inbound from the Lan. The message is something like"STANDBY-3-DUPADDR"

See

http://www.ciscotaccc.com/kaidara-advisor/iprout/showcase?case=K59898346

[b.petronio]

Try to check/change cable, and try to set up the same speed/duplex at the both side.

If u have a network cable structure, try to simulate just in front of the switch with the same PC. (Isolate cable invironment)

Hope it helps,

Petr?nio

[seesquinaldo]

Be sure to also check the NIC on the server. I've found a few that were tempermental. If it has 2 NICs try the other or swap NICs from a known good server.

[dave.keith]

There is a Field Notice on some 3500XL units. I recall the problem for some serial numbered units was bad capacitors. We had to replace about 15 of our 3500XLs because of this problem. See fn26174 for details.

Dave

[b.petronio]

Workaround for that Field Notice problem... Forcing 10Mbps/Half Duplex, with the subject consequencies.

Petr?nio