We have a problem with one of our switches that is showing collision or loop in an unusual manner. Normally when it shows a collision in a switch or a hub the collision or loop light blinks, but here the case was totally different.
The port was showing a green light (which it should). After some time it started turning orange and then back to green. This was due to an output that was going to another part of my network. When I took that output out then there was no collision, and as soon as I put it in the same thing would happen. Could you tell me what exactly is the problem?
It is very difficult to make an adequate diagnosis on the basis of the information provided. But is sounds suspiciously like a duplex mismatch. That is, under load, collisions take place that otherwise would not appear during quiet times.
Do you manually hardset all your interfaces to full (or half) duplex? Or do you use auto-negotiation? DO NOT TRUST AUTO-NEGOTIATION. Always hardset your ports. As troublesome as that can be, it will save you a lot of time in the long run.
Dig Deeper on Network Infrastructure
Ethernet used to be found only in corporate LANs but is now proliferating into the carrier network, from access and metro area networks to the backbone. It has some pesky problems you need to know about: For instance, what is duplex, and what is the difference between half and full duplex? What is a duplex mismatch? How can auto-negotiation help or hurt your network? How can you resolve duplex conflicts? Here's some help.
Related Q&A from Loki Jorgenson
Have a question for an expert?
Please add a title for your question
Get answers from a TechTarget expert on whatever's puzzling you.