Solved GT-AX6000 2.5G LAN Port - only negotiating at 1G on switch

[visortgw]

I don't use that, so it doesn't affect me. Also, this is version 2.0 of the switch, so they might've fixed that issue.

Yes, mine were HW V1.OR.

 

[TheLostSwede]

Very nice setup by the way.

I also have a 10 Gbps TL-SX105 switch, as I got a NAS and my main PC hooked up to that, plus some other bits and pieces...

 

[TheLostSwede]

Yes, mine were HW V1.OR.

Zero information if there are any fixes like that between the revisions, but there's also a 1.xR revision apparently.
V 2.0R is clearly different in terms of hardware, as it's just over half the physical size at 159 vs 240 mm wide and it draws 5 W less power.

 

[shabbs]

Top left are green on both input to and output from unmanaged switch.

Ok then there is something up in my chain of connections... as we have the same order of HW from router --> unmanaged switch as far as I can tell.

I'll try a few different cables from the router to the switch as well.

 

[visortgw]

Zero information if there are any fixes like that between the revisions, but there's also a 1.xR revision apparently.
V 2.0R is clearly different in terms of hardware, as it's just over half the physical size at 159 vs 240 mm wide and it draws 5 W less power.

Yes, I spent a lot of time debugging why guest network 1 didn't work with my HW 1.0R switches — I still have them, and I use them as additional end node ports.

 

[shabbs]

You can probably see the negotiated link speed when you plug your switch into eth5 in the router's syslog.

FWIW - here's the snippet from syslog from an unplug/plug sequence of events:

Apr 14 17:09:52 kernel: eth5 (Int switch port: 6) (Logical Port: 6) (phyId: 13) Link DOWN.
Apr 14 17:09:52 kernel: br0: port 5(eth5) entered disabled state
Apr 14 17:09:57 kernel: eth5 (Int switch port: 6) (Logical Port: 6) (phyId: 13) Link Up at 2500 mbps full duplex
Apr 14 17:09:57 kernel: br0: port 5(eth5) entered blocking state
Apr 14 17:09:57 kernel: br0: port 5(eth5) entered forwarding state
Apr 14 17:10:02 kernel: eth5 (Int switch port: 6) (Logical Port: 6) (phyId: 13) Link DOWN.
Apr 14 17:10:02 kernel: br0: port 5(eth5) entered disabled state
Apr 14 17:10:13 kernel: eth5 (Int switch port: 6) (Logical Port: 6) (phyId: 13) Link Up at 2500 mbps full duplex
Apr 14 17:10:13 kernel: br0: port 5(eth5) entered blocking state
Apr 14 17:10:13 kernel: br0: port 5(eth5) entered forwarding state

 

[visortgw]

FWIW - here's the snippet from syslog from an unplug/plug sequence of events:

Apr 14 17:09:52 kernel: eth5 (Int switch port: 6) (Logical Port: 6) (phyId: 13) Link DOWN.
Apr 14 17:09:52 kernel: br0: port 5(eth5) entered disabled state
Apr 14 17:09:57 kernel: eth5 (Int switch port: 6) (Logical Port: 6) (phyId: 13) Link Up at 2500 mbps full duplex
Apr 14 17:09:57 kernel: br0: port 5(eth5) entered blocking state
Apr 14 17:09:57 kernel: br0: port 5(eth5) entered forwarding state
Apr 14 17:10:02 kernel: eth5 (Int switch port: 6) (Logical Port: 6) (phyId: 13) Link DOWN.
Apr 14 17:10:02 kernel: br0: port 5(eth5) entered disabled state
Apr 14 17:10:13 kernel: eth5 (Int switch port: 6) (Logical Port: 6) (phyId: 13) Link Up at 2500 mbps full duplex
Apr 14 17:10:13 kernel: br0: port 5(eth5) entered blocking state
Apr 14 17:10:13 kernel: br0: port 5(eth5) entered forwarding state

That matches what I see with unplug/replug:

Apr 15 11:30:44 kernel: eth5 (Int switch port: 6) (Logical Port: 6) (phyId: 13) Link DOWN.
Apr 15 11:31:03 kernel: eth5 (Int switch port: 6) (Logical Port: 6) (phyId: 13) Link Up at 2500 mbps full duplex

 

[shabbs]

That matches what I see with unplug/replug:

Apr 15 11:30:44 kernel: eth5 (Int switch port: 6) (Logical Port: 6) (phyId: 13) Link DOWN.
Apr 15 11:31:03 kernel: eth5 (Int switch port: 6) (Logical Port: 6) (phyId: 13) Link Up at 2500 mbps full duplex

Yeah - all indications on the router are that everything is fine and 2.5G is negotiated. Only the switch is reporting otherwise which is driving me nuts now. LOL!

Will update you guys later when I test with the various cables.

Very interesting... very interesting.

 

[TheLostSwede]

FWIW - here's the snippet from syslog from an unplug/plug sequence of events:

Apr 14 17:09:52 kernel: eth5 (Int switch port: 6) (Logical Port: 6) (phyId: 13) Link DOWN.
Apr 14 17:09:52 kernel: br0: port 5(eth5) entered disabled state
Apr 14 17:09:57 kernel: eth5 (Int switch port: 6) (Logical Port: 6) (phyId: 13) Link Up at 2500 mbps full duplex
Apr 14 17:09:57 kernel: br0: port 5(eth5) entered blocking state
Apr 14 17:09:57 kernel: br0: port 5(eth5) entered forwarding state
Apr 14 17:10:02 kernel: eth5 (Int switch port: 6) (Logical Port: 6) (phyId: 13) Link DOWN.
Apr 14 17:10:02 kernel: br0: port 5(eth5) entered disabled state
Apr 14 17:10:13 kernel: eth5 (Int switch port: 6) (Logical Port: 6) (phyId: 13) Link Up at 2500 mbps full duplex
Apr 14 17:10:13 kernel: br0: port 5(eth5) entered blocking state
Apr 14 17:10:13 kernel: br0: port 5(eth5) entered forwarding state

Do you know who makes the switching hardware in your switches?
The GT-AX6000 is all Broadcom and there could be some weird compatibility issue if the switch has hardware from Realtek or MaxLinear.
It shouldn't happen, but...

 

[RMerlin]

Yeah - all indications on the router are that everything is fine and 2.5G is negotiated. Only the switch is reporting otherwise which is driving me nuts now. LOL!

Could be a display issue on the switch's UI. Have you done a speed test?

 

[visortgw]

Do you know who makes the switching hardware in your switches?
The GT-AX6000 is all Broadcom and there could be some weird compatibility issue if the switch has hardware from Realtek or MaxLinear.
It shouldn't happen, but...

I'm using the exact same switch. tp-link switches, both unmanaged and managed, have been 1000% compatible with Asus routers in my experience.

 

[shabbs]

Could be a display issue on the switch's UI. Have you done a speed test?

I thought so too - but even a 2nd unmanaged switch from a different manufacturer (D-Link vs TP-Link) shows the same behaviour. @visortgw has the exact same HW in the mix and does not have the issue so there is something on my side that I need to isolate be it either a cable issue, or something the router's port etc...

Speed tests from the APs connected to that switch max out at 1Gpbs. Not exactly scientific but they all show clean 2.5G connections on the switch.

Will need to figure out a way to directly test that LAN port on it's own... don't have any sort of 2.5G ethernet on my PC unfortunately.

 

[shabbs]

OMG this is embarrassing. This is truly a self induced non-problem. LOL! Explainer below.

So, I managed to find three ethernet cables to test - Cat 5, Cat 5e and Cat 6 - figured I'd cover the bases here and see if this is a cable issue.

Pulled the gear all the way out so I could swap cables easily, saw the "1G" Cat7 cable that was giving me the fits and when I pulled it out - it was not the one going to the Router but instead, going to my Desktop machine under the desk. Which of course has a.... wait for it... 1G ethernet adapter.

It was at this moment I realized I had fracked up.

I then fully pulled the cable from the router to the 2.5G switch and it was plugged into a port that I was sure was one of the incoming 2.5G AP ports.

So... bottom line... all 2.5G connections are indeed 2.5G. I've re-labelled and re-organized the ports/layout so it's clear what goes where now...

Apologies for all the disruption this caused. Appreciate all the input and feedback.

Good thing I didn't pull the plug on the managed switch... LOL.

Will update the first post to reflect this as well.

Oh boy.

I'll blame the three PROD Deployments we had this weekend for my stupid brain moment today.

 

[L&LD]

So in the end, it was the cable!

 

[shabbs]

So in the end, it was the cable!

LOL! Technically... this is true.

 

[L&LD]

Yup, always find a way to blame the hardware. User error is never an issue.

 

[shabbs]

Yup, always find a way to blame the hardware. User error is never an issue.

Heh.

Well, I'm happy to own this one. No doubt where the blame lies here - documented in full.

 

[visortgw]

Glad to help you troubleshoot the issue! You would have done the same for me.

 

[visortgw]

Also, easily upgrade your desktop machine: UGREEN USB C to Ethernet Adapter 2.5G. This is a the newer, lower power (runs cooler) Realtek RTL8156BG chipset.

 

[shabbs]

Also, easily upgrade your desktop machine: UGREEN USB C to Ethernet Adapter 2.5G...

Well, if I do - it will likely be a PCIe card that I'll stuff in the case. Not a fan of those usb-c dongles to be honest.

Those look to be super cheap: https://www.amazon.ca/TP-Link-2-5GB-PCIe-Network-TX201/dp/B0BG685PKM/?tag=smallncom-20