You should probably disable Auto Negotiation and fix it at 2.5Gbps on AX3 ether1 too...Follow up:
On CSS610 I set an S+RJ10 to forced 2.5Gb, connected to ether1 of AX3 using VLAN trunk.
Link becomes active. So far so good.
On AX3 log files I see it determines speed as being 2.5Gb, which is ok however ...nothing passes (after the facts I can see in log files what happened).
Only when I enable autonegotiation, I can get access via that link.
Am I missing something ?
When setting speed fixed on AX3 -> No Link on CSS610, both with auto and no autonegotiation.You should probably disable Auto Negotiation and fix it at 2.5Gbps on AX3 ether1 too...
Actually I believe onnoossendrijver is correct, modern ethernet controllers use standard IEEE 802.3ab auto negotiation protocol to automatically determine MDI, speed and duplex and for a practical standpoint it makes perfect sense, and once you disable auto negotiation you must use crossover cable...I understand what you say but I don't understand why that would be needed... doesn't make sense from a practical point of view.
Auto MDX is something from the previous century !
Anyhow, SUP-146041 created. Let's see what support says about it.
Confirmed on CSS610:If I go to the hosts screen... after about 20 seconds I get this at the top of the screen.
ERROR: SyntaxError: Unexpected token '{'
O..K ...it took a LOT longer then 20 seconds (just left the window open while I was doing something else).I'm not seeing that.
Edge as browser on Win11.
Your device is a dumb power consuming nothing without SwOS. So don't talk BS. And Mikrotik won't open source SwOS anyways. It wouldn't help you either way, as bugs are not fixed by just the action of publishing the source code.Most of the value is in the hardware anyway, few companies make outdoor reverse-PoE switches.
Fingers crossed...We have managed to reproduce the issue locally in our labs and look forward to fixing it on upcoming SwOS lite versions, unfortunately, I cannot provide a release date now.
I had the switch just stop passing traffic for 5 minutes.
It suddenly started working again.
I messaged Mikrotik about it... But can't send logs, as there are none.
A month later I got a message that they had reproduced the lock up. I was sent a firmware that addresses the lock up. But not the hosts table. I installed it this week and am "waiting".
The firmware they sent me appears to have addressed the lock up.
Any updates on this @Springs? We have several of these switches in production for 60Ghz P2P applications. We have our concerns and have now seen the grass is greener on the other side.... thank you.,.
It doesn't address that token thing on hosts table.A FW version which was given in november 2024 or earlier and still not released ?
Now that's odd ...
I messaged them last month about it... Nothing.I guess you need to update your support ticket as well.
Yikes... that's unacceptable. I agree - waiting on updates from MikroTik. Wonder if it's a third-party developer for this hardware.Any hope for a ping watchdog? It's a real pain to have to go and manually disconnect and reconnect all ports if something fails, or ask everyone in the building to simultaneosly turn off power.... I have 60+ 7R's on my network and adding more and more and they work really nice but there are times that the device has to be rebooted because one client does not provide sufficient power for both the 7R and the radio on the PoE out. Judt today had a radio constantly rebooting and had t ogo on site and unplug everything and plug them back in, in order to fix the issue. A ping watchdog reboot function would save downtime
We still can't get the host table to keep working.
- Request: Link Downs counter in Link or Stats - Otherwise its difficult to nail down intermittent link issues, especially now that we deploy GPeRx4 devices.
- Request: Cable Test action on supported devices to force Length/Cable Pairs update. Right now these fields just stay blank most of the time.
- Request: Cable Pairs legend (always display on Link page)
- Bug CSS: header,main{min-width:100vw} causes annoying horizontal scrollbars, and appears to be unnecessary.