Question Solved (cause I was dumb) -- Debugging Switches Connected Over Cat6A Keystone Cable

Aug 27, 2019
2
0
10
Hi --

I have two NETGEAR managed switches (XS708Ev2 <-> GS110EMX) connected over Cat6A cable. When I connect them directly using a straight-through T568B cable, all is well.

I am running into problems because our installation requires them to be connected at either end of a 70 meter cable run terminated at either end with T568B Keystone Jacks. I have checked that cable, and it works fine when connecting a switch and router / switch and pc.

I have also replicated this bug using a shorter (5 meter) length of the same cable (also confirmed working). The patch cables at either end of the cable are all fresh from the factory and confirmed working (I've also tried testing with homemade & tested T568B patch cables).

So far I have tried rewiring with every combination of the three cables as crossover (including the keystone cable running through the walls, even though I know that's not recommended for future-debugging purposes) with no luck.

My switches don't give me the option to specify uplink ports, but given what I've found from moving around the single patch cable, I'm getting the impression that they're both handling it through Auto-MDIX?

Up until now, all my experience has been limited to the code/config end of things, and I've sort of found myself dropped into this role by default -- any help of what to try next, or what I should be testing/looking for would be hugely appreciated!

Thanks!
 
OK u got a longish post there and yet I don't read a THIS IS THE PROBLEM UNDER THIS CONDITION. So I have no idea what the exact problem is.

Ethernet 100m is the theoretical max and we know about theory, so to me, in real life 70m is kinda borderline viable.

If these switches are 1-5 years old they should come with auto-MDIX. Anywoo, switches that require crossover cables will either work or don't work, there is no in-between.

Managed switches may require that u use a specific uplink port but since u say it doesn't have any...
 
@jsmithepa - thanks for jumping on this thread so quick.

Almost right after I posted, I thought to do an idiot check... this was all a VLAN/pvid issue. D'oh.

.....At least I got a lot of practice wiring RJ45 Adaptors.