cancel
Showing results for 
Search instead for 
Did you mean: 
cancel
756
Views
2
Helpful
10
Replies

RJ45 Connectors issue after cisco switch replacement

Erfan7
Level 1
Level 1

I have experienced multiple times whenever switch got faulty and replaced, multiple cisco WiFi devices didnt come up, as switch ports didn't up, after replacing the connectors from either switch end or device end, ports come up, so my question is have you ever experienced this issue and what could be the possible reason.

1 Accepted Solution

Accepted Solutions


@Erfan7 wrote:

Joseph my question is why devices were fine with old switch, and why some didn't come up with new switch, as from device end nobody touched the cables/connectors only cables were reconnected to new switch in IDF, when connectors were made from device end they came up, let me tell you this was happened many times, and I also know issue was with connectors as you said internal connection was marginal.


Two possibilities come to mind.

First possibility, the link, end-to-end, never met spec, due to one or both RJ45 connectors not meeting spec, and the replacement switch isn't as tolerant of the link being out of spec as the earlier switch was.

If this is happening, why the two switches don't use the same Ethernet tolerances is a fair question, but that's a whole different line of inquiry vs. that they do.

Again, if the newer switch isn't as tolerant, the reconnected link fails, even though, it (the link), hasn't changed at all.

Thinking about this possibility, it might be the most likely, even over any possible issues caused by disconnecting and reconnecting the switch end RJ45.  It can also explain why either end, or both ends, RJ45, not meeting spec, would be an issue on the replacement switch.

The second possibility, is a bit more exotic.  So, you pull the switch end RJ45, swap switches, insert the switch end RJ45, and have a connectivity issue.  Then what do you do?  I.e. how did you "find" replacing the far side RJ45 to be a fix?  I would think, your first action would be to first replace the switch side RJ45, and only if that did not fix the issue, then try replacing the far side RJ45.  So, if that's what you've been doing, it would imply, the switch end RJ45 wasn't the problem, only the far side RJ45, but that side, hasn't been touched yet, so it couldn't be the problem, right?

Well, the forgoing assumes the replaced switch side RJ45 performs as well as or better than the RJ45 it replaced.  But if it didn't at least match the replaced RJ45 performance, and the far side is sub marginal, the combination of replaced near side, and far side sub marginal RJ45, precludes link working until far side is replaced with a "better" performing RJ45, whose improvement, is enough to allow end-to-end connectivity.

The only way I can see narrowing down this issue, to root cause, would be to use an end-to-end cable tester and/or after a reconnected RJ45, switch side, link failure, reconnect to prior switch (the latter not possible if being replaced after actual switch failure, not just for switch replacement for a newer switch).

BTW, hardware device tolerances are sometimes better than what a spec allows for, but usually no one complains about being able to exceed spec, until you bump into a case where suddenly meeting spec becomes a problem.

For example, we all know the copper Ethernet specs usually calls for a 100 meter distance limitation, but have you ever tried running 101 meters?  Do you think 101 meters will definitely not work, or there's some chance it will?  If some chance it will, what about 110 meters, 120 meters, 150 meters?  What about the "quality" of the cable itself?  Do you think some cables might just go a bit longer than 100 meters then other cables?  How/why is there a 100 meter limitation, how does a host know or detect cable is too long?  Could different host NICs have different allowance for how far 100 meters might be exceeded?

Per chance, were older switches using 10/100 and newer 10/100/1000 ports?  What speeds are you running at, and what Cat level cable is being used?

Can you tell us, that before a failed switch was replaced, its ports show zero L1 errors?

In other words, good chance, as @liviu.gheorghe notes in a recent reply, your cabling plant is "poor quality" and if so, and if newer switches are less tolerant, you would see the continuous issues as you replace switches, for whatever reason.

If the problem often is resolved by replacing RJ45 connectors, then, most likely, most might be sub spec.

Again, as I noted earlier, things like device vibrations and/or manually manipulating cables, might impact their operational capability, but this, and newer switch tolerance differences, aren't mutually exclusive.

View solution in original post

10 Replies 10

Mancunian
Spotlight
Spotlight

Inspect Connectors and Cables: Look for visible damage or wear.
Replace Problematic Components: Use new, certified connectors and cables.
Verify Port Configurations: Confirm speed, duplex, VLAN, and PoE settings match the requirements of the Wi-Fi devices.
Test with Other Devices: Check if the switch ports work with other devices to rule out hardware issues.
Update Firmware: Ensure the switch is running the latest firmware, as some issues might stem from software bugs.
Monitor Logs: Check the switch logs for errors when connecting devices (e.g., spanning tree, PoE negotiation, or port flapping issues).

I would add using a cable tester. Check the small/simple stuff first. I always liked the adage "inside every big problem is a little problem dying to get out". I have not found cables going bad to be a frequent thing. I would also add plugging a device directly into the switch port to see if it is the cable plant going to the end device.

Joseph W. Doherty
Hall of Fame
Hall of Fame

I haven't seen that with RJ45 connectors but have bumped into it on other cable connectots.

I was told, by a hardware tech, if the internal connection isn't quite right (or marginal), over time, vibrations to the cable can lead to failure.  Plus, in your case, you mentioned problem often appears when you replaced switch, which at least on that end, means connector was (slightly) stressed by removing and reinserting RJ45 into port, i.e. possibly causing a marginal connection to become sub marginal.

Do you attach the RJ45 connectors yourself?  Whether you do, or a professional cable installer does, are the cables then tested, or connected and if device comes on-line, all assumed good?

Again, I haven't seen this issue with RJ45, but I generally worked in large operations where issues of the cabling plant wouldn't be made known to me and where "professional" cable installers were used.

Joseph my question is why devices were fine with old switch, and why some didn't come up with new switch, as from device end nobody touched the cables/connectors only cables were reconnected to new switch in IDF, when connectors were made from device end they came up, let me tell you this was happened many times, and I also know issue was with connectors as you said internal connection was marginal.

 

 - @Erfan7  Are you sure that the new switch was correctly configured and provisioned to be able to play a replacement role
                   in topics, such as configuration , port access settings ,vlan, VTP,....

  M.



-- Each morning when I wake up and look into the mirror I always say ' Why am I so brilliant ? '
    When the mirror will then always repond to me with ' The only thing that exceeds your brilliance is your beauty! '

@Erfan7 - replacing a switch involves taking out patch cables connected to it and connecting them to the new switch along with some pulling and twisting the cables when taking out the old switch and putting it the new one.

This kind of operations is what @Joseph W. Doherty is referring to in his post.

Have you tried replacing only the switch end patch cable and seeing if the problem is solved. I'm asking because it makes sense replacing the switch end cable because the far end - the one to the WiFi AP - was not touched.

HTH

Regards, LG
*** Please Rate All Helpful Responses ***

Instead changing the patch cords I by-pass the patch panels and also in 1st attempt We make the connectors from switch end, when devices don't come up, after making the connectors from devices end ports come up.

It looks like your cables that run from the patch panels to the end devices are either very old or of poor quality. 

Another option could be that the cables are longer than the 100 meters recommended for UTP cables. 

What you can do is measure the cables and get a detailed report on the quality of the cables.

Regards, LG
*** Please Rate All Helpful Responses ***


@Erfan7 wrote:

Joseph my question is why devices were fine with old switch, and why some didn't come up with new switch, as from device end nobody touched the cables/connectors only cables were reconnected to new switch in IDF, when connectors were made from device end they came up, let me tell you this was happened many times, and I also know issue was with connectors as you said internal connection was marginal.


Two possibilities come to mind.

First possibility, the link, end-to-end, never met spec, due to one or both RJ45 connectors not meeting spec, and the replacement switch isn't as tolerant of the link being out of spec as the earlier switch was.

If this is happening, why the two switches don't use the same Ethernet tolerances is a fair question, but that's a whole different line of inquiry vs. that they do.

Again, if the newer switch isn't as tolerant, the reconnected link fails, even though, it (the link), hasn't changed at all.

Thinking about this possibility, it might be the most likely, even over any possible issues caused by disconnecting and reconnecting the switch end RJ45.  It can also explain why either end, or both ends, RJ45, not meeting spec, would be an issue on the replacement switch.

The second possibility, is a bit more exotic.  So, you pull the switch end RJ45, swap switches, insert the switch end RJ45, and have a connectivity issue.  Then what do you do?  I.e. how did you "find" replacing the far side RJ45 to be a fix?  I would think, your first action would be to first replace the switch side RJ45, and only if that did not fix the issue, then try replacing the far side RJ45.  So, if that's what you've been doing, it would imply, the switch end RJ45 wasn't the problem, only the far side RJ45, but that side, hasn't been touched yet, so it couldn't be the problem, right?

Well, the forgoing assumes the replaced switch side RJ45 performs as well as or better than the RJ45 it replaced.  But if it didn't at least match the replaced RJ45 performance, and the far side is sub marginal, the combination of replaced near side, and far side sub marginal RJ45, precludes link working until far side is replaced with a "better" performing RJ45, whose improvement, is enough to allow end-to-end connectivity.

The only way I can see narrowing down this issue, to root cause, would be to use an end-to-end cable tester and/or after a reconnected RJ45, switch side, link failure, reconnect to prior switch (the latter not possible if being replaced after actual switch failure, not just for switch replacement for a newer switch).

BTW, hardware device tolerances are sometimes better than what a spec allows for, but usually no one complains about being able to exceed spec, until you bump into a case where suddenly meeting spec becomes a problem.

For example, we all know the copper Ethernet specs usually calls for a 100 meter distance limitation, but have you ever tried running 101 meters?  Do you think 101 meters will definitely not work, or there's some chance it will?  If some chance it will, what about 110 meters, 120 meters, 150 meters?  What about the "quality" of the cable itself?  Do you think some cables might just go a bit longer than 100 meters then other cables?  How/why is there a 100 meter limitation, how does a host know or detect cable is too long?  Could different host NICs have different allowance for how far 100 meters might be exceeded?

Per chance, were older switches using 10/100 and newer 10/100/1000 ports?  What speeds are you running at, and what Cat level cable is being used?

Can you tell us, that before a failed switch was replaced, its ports show zero L1 errors?

In other words, good chance, as @liviu.gheorghe notes in a recent reply, your cabling plant is "poor quality" and if so, and if newer switches are less tolerant, you would see the continuous issues as you replace switches, for whatever reason.

If the problem often is resolved by replacing RJ45 connectors, then, most likely, most might be sub spec.

Again, as I noted earlier, things like device vibrations and/or manually manipulating cables, might impact their operational capability, but this, and newer switch tolerance differences, aren't mutually exclusive.

Erfan7
Level 1
Level 1

First possibility, the link, end-to-end, never met spec, due to one or both RJ45 connectors not meeting spec, and the replacement switch isn't as tolerant of the link being out of spec as the earlier switch was...

Well, the forgoing assumes the replaced switch side RJ45 performs as well as or better than the RJ45 it replaced.  But if it didn't at least match the replaced RJ45 performance, and the far side is sub marginal, the combination of replaced near side, and far side sub marginal RJ45, precludes link working until far side is replaced with a "better" performing RJ45, whose improvement, is enough to allow end-to-end connectivity

Joseph very comprehensive reply, Thank You very much