Hi,
I have RB260GSP which is powering 3 SXT devices.
1 x SXT 5HPnD
2 x SXT G-2HnD
Power consumption is low, so there is no problem with that part.
It was working for 8 months with no problems. At the moment one SXT G-2HnD can’t auto negotiate link with RB260GSP.
It works only if I disable auto-negotiation and put speed to 10Mbit/s. It doesn’t work on 100 or 1000 Mbit/s. Once in a while link on appears on the switch, but very temporarely. Flow control or full duplex have no effect it works only on 10 Mbit/s.
Both SXT G-2HnD are rather close to one another but are orientated in different directions. So the cables are going nearly on the same route. There is no problem with other SXT G-2HnD and there wasn’t a problem with this one now.
I’ve changed auto negotiation just on the switch. Since it’s remote location I’m affraid I’ll lose connnection to SXT if I disable the autonegotiation on the device.
Can somebody advise what to try and where would be the problem?
SwOS 1.14?
I’d try swapping ports between SXT G-2HnD, maybe a port got damaged by ESD, either on the RB260 or the SXT.
yes and try doing cable test with a router os device
+1 with the idea of interchange cable between sxt´s
Yes, SwOS 1.14.
Unfortunately the site is rather far away and SXTs and switch are mounted in a place where you can’t reach it easily so there is no chance someone can do cable interchange instead of me.
That’s why I would try all the things I can do remotely.
What kind of cable test did you have in mind?
There is calibration test in the switch.
I’d bet the problem is physical, either damaged ethernet ports, or faulty cable.
That’s why I suggested swapping out, to rule out possibilities and isolate where the problem comes from:
Lets say SXT A is the one not auto-negotiating.
(On the rb260gsp side)
If when swapping SXT A cable to the ether port SXT B was in the RB260GSP:
-
- Now is SXT B the one not auto-negotiating, and A does: the problem is the rb260gsp port.
- If the problem persists, (SXT A still doesn’t auto-negotiate, but B does) then the problem isn’t the rb260gsp port.
In such case, proceed in Increasing Order of Annoyance:
Crimp again the cable just on the rb260gsp side, and re-test. If problem goes away, you can call yourself lucky! 
If it persists you’ll have to climb, and swap cables.
- If the problem moves to the other SXT the problem is the cable.
If the problem persists, the SXT port is where the fault comes from.
(If the problem is the cable, tell your technician to unplug the rb260gsp side prior to cut and re-crimp!!!)