RouterOS version when I got is v7.4, and I upgraded both RouterOS and RouterBOARD firmware to v7.8, then reset to factory default without keeping anything, but the problem persists.
I’d appreciate it if there’s anyone who has the RB5009 series willing to try to reproduce my issue and see if Eth2 of yours is also lit up.
It would be great if someone from MikroTik official can comment on this.
I had a similar experience on a CCR1009 where ether1 stopped working but kept lighting up with no cable plugged in. What is strange is that I could assign an ip address to it and ping that address which would respond properly but connect a cable to that port with device but no response. I could disable the port but it would still light up.
Thank you for taking the time to read and respond to my discussion regarding the issues I’ve been experiencing with my router.
I appreciate your input and suggestions for troubleshooting the problem, including performing a NetInstall using RouterOS 7.8. Unfortunately, the issue persists even after trying these steps.
The port itself is normal and working as expected.
Update: This morning I also tried powering the unit using PoE on Eth8, but the Eth2 is also lit up even without a cable plugged in.
I’ve just submitted a ticket to MikroTik support and I’m waiting for confirmation from MikroTik official that this router behaviour is normal before I put it into live use on Sunday. Could someone please confirm if the behavior I described is normal and not a sign of any potential issues? I’m sure there are other users of the RB5009Pr+S+ here who could offer some insight. Thank you all in advance for your help.
I have the non-PoE version.
Can’t say anything about the lights since it’s stored away out of sight.
Other then that, it works fabulously.
I do have seen some managed switches (1 D-Link and 1 Cisco) with a customer where I noticed similar behavior on some ports (in total on maybe 60 switches or so).
Those devices still run fine since the first time I noticed it (several years ago already).
A bit more of a challenge to find out issues but a big sticker on the device makes me aware each time I am there.
Those 2 ports where never a cause of problem (besides for not pulling their share for giving enough light in the cabinet )
Main question, when it boots ir RouterOS , does it work as expected???
I have seen several boards, usually early revisions that have different LEDs misbehaving during the RouterBOOT, some of them can be fixed by RouterBOOT upgrade, some of them are hardcoded in factory when installed. usually it is first Ehtnernet LED that is attached directly to CPU (in this case it is Ether2). So i would say it is common, nothing to worry about.
In any case when RouterOS loads, it should take over all funcionality of any LED and everything should work corretly.
Personally i do not see the reason for RMAs if it works corretly when loaded to RouterOS.
Devices with POEs have two LEDs per port. One indicates the presence of the link and the second one indicates that the POE voltage is on. Often they are in the same case with two colors.
So the glow of the first LED without a cable connected usually means that the port is out of order. The glow of the second LED has no effect on the functionality of the port. I have a hap ac lite which constantly glows red LED, while the device works normally. It just has a broken POE indication. Always on regardless of settings.
)