Tek-Tips is the largest IT community on the Internet today!

Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!

  • Congratulations Shaun E on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

LINK-4-ERROR

Status
Not open for further replies.

papad

Technical User
Oct 3, 2003
9
NL
Hi,

I have a problem on a 3550 switch. On almost all I get the message: Link-4-error: the interface is experiencing errors. With sh interface I see input errors and cdr-errors. I changed the cables, and the switch. The problem remains the same. Any suggestions?
Thanks,
papad
 
Check the duplex status on both ends. Also by "cdr-errors" you mean CRC errors or what?

Peter Mesjar
CCNP, A+ certified
pmesjar@centrum.sk

"The only true wisdom is in knowing you know nothing.
 
Hi,
The duplex status is OK. Yes, I mean crc-errors. I have input and crc-errors on almoast all f interfaces.
Thanks again,
papad
 
High number of input and crc errors are almost always related to duplex mismatch - are you absolutely sure your duplex is set to same value on both ends of the link? You may try to hardcode the duplex setting on both ends and don't let the switch and hosts autosense. Also, have you considered replacing NICs in hosts?

Peter Mesjar
CCNP, A+ certified
pmesjar@centrum.sk

"The only true wisdom is in knowing you know nothing.
 
I have thin-clients on the switchports. I checked the duplex status. The switch-ports are full duplex and the thin-client autonegotiating. I tested with a thin-client with full duplex. The errors are the same...
 
You really have to fix the speed and duplex at both ends. It is not worth the hassle of leaving autonegotiate on - it leads to problems, by fixing it you can rule it out.

What NICs are you using in your clients? 3-Com's have many options which can cause crc errors if not set correctly, for example a common problem i have had with such cards is "auto polarity", try setting this to off and check your port errors again.

Cheers,
Fil.

If everything is coming your way then you're in the wrong lane.
 
If you switch is setup to full-duplex and your clients are auto, then you'll clients will set themselves to half-duplex and cause your errors.

Either set the switchports to auto or hardset both the switch and the clients to their desired speed and duplex settings.
 
The hosts are Neoware thin-clients and they have an integrated netwerk-adapter. The netw chip is: Realtek RTL 8139C.
Any experience whith this chip above in comb with 3500 switches?

Cheers
 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top