Running CCR1009-7G-1C-1S+ with latest stable 7.16.2
Ethernet 4 port does not have the orange status led working, port seems to behave OK, links in 1gb and the link led works
When turned on not all ethernet port status leds flash.
See this pic
eth no link/status led
eth1 to 4 no status led
eth 5 and 6 both link and status leds light up
eth7 both leds light up but status led green? (expecting orange in in eth5 and 6)
furthermore there is this high pitch sound on boot, can’t really figure out where it comes from, anyone experienced similar ?
the behavior is captured in this video which shows a boot after power on https://www.youtube.com/watch?v=rfMo2g2X1d4
I really don’t care much if all status leds flash on boot, my main problem with this is that status led on eth4 does not light at all on cable plug
The rest of the ports status leds do light when cable is plugged in them
The high pitch noise on boot is also worrying me. Not sure if its a component going bad or the fans maybe before they spin?
If anyone knows anything about this I would be grateful to know too.
The release notes of the RouterOS version 7.16.2 my unit runs mention changes to led behaviors. There’s a chance those are related but I don’t know if prior upgrade these leds worked as expected since the unit was in a remote rack. I tried posting in the 7.16.2 announcement but there’s no ‘Reply’ button there so I opened this new thread.
I could try downgrading to latest stable v6 (which is newer from the stock version unit came in with so should be fine) but I prefer to have the issue addressed in the latest v7 stable.
It is worth mentioning that I did factory reset as well and checked /system/leds but didn’t see ethernet port leds listed there
Tried /interface/ethernet/blink on all interfaces and got no blinks from any leds on the unit.
Did that by first printing them and then based on their # of the print table did
The device you’re looking at is pretty old now. It’s likely that it’s starting to fail … there have been numerous cases where capacitors (both in power adapter and on device’s board) have bulged and then device experienced very random ways of misbehaviour.
It’s likely that configuration isn’t at fault. To verify that that’s 100% true, netinstall device without keeping config … and if behaviour remians the same after device is booted with no config, it’s definitely hardware. If device starts to behave after netinstalling it, then configure it from scratch (don’t use binary backup file to restore it, that method has potential to re-introduce buggy config).
Wasn’t familiar with this approach of flashing these units. Went through the netinstall manual and did netinstall of 7.16.2
Issues persisted. More then half of the ether status/activity leds do not flash on turn on
eth4 status/activity led does not light up on cable plug
netinstall of latest long term 6.49.13
Led issues persisted.
High pitch sound on startup was found out to be something in fans.
Unplugged both from boards and it disappeared. Once booted and after sys increases their RPM the high pitch sound stops but I’ll change them both with new ones nonetheless.
Capacitors on board look fine, none swollen/cracked/etc. any of the usual signs of them going bad.
Noticed that status/activity led of eth7 is little dimmer than the rest of ethernet ports so I guess its about to go out as well. Maybe this is what happened with eth4 led, it just went bad.
Interest remains on why the activity/status leds of most ethernet ports do not flash on startup, even though they light up on cable plug.
Maybe it’s something introduced inbetween the factory version and latest long term. I’ll try installing factory version via netinstall later on to see if that fixes it.
I saw that netinstall flash does not affect bootloader. Do you happen to know if its the OS containing firmware that controls these leds or its something else other that could be flashed ?
Flash is updated from within ROS via system-> routerboard submenu. ROS will always contain routerboot flash images related to ROS version (since around 6.40 onward) so you can also “downgrade” routerboot flash from within older ROS. Just beware that for booting newer ROS versions (v7 in particular IIRC) device has to run decently recent routerboot (6.48+ should be fine).
AFAIK routerboot does basic device initialization (same as BIOS/EFI on PCs) and can affect those tiny hardware details (like flashing of LEDs). I guess ROS has saying in that as well (specially so if it contains submenu to configure LED activity).
The unit reports factory ROS 6.45.9 which is not officially listed in the download section no more but with little URL tweaks I managed to get it off Mikrotik together with the netinstall software for that version. However, for now I’m staying with latest long term 6.49.13. It is my belief that eth4 status/activity led has just gone bad as
All other eth activity/status leds light up on cable connect, only eth4 does not
I’m seeing eth7 led going dim, the other eth leds are way brighter than it, so eth7 led is gonna go bad sometime soon too I’m guessing
And in regards to the majority of status/activity leds not flashing on startup I’m guessing this is an early bug. I would’ve never saw it unless I had the unit in front of me to play with.
In its previous life its been in a rack with all interfaces hooked so this behavior was never paid attention to.
Update: Just to satisfy curiosity and wrap this up, net installed the factory ROS version & the behaviors remained the same. If anyone else has the same unit version & could unplug all interfaces, shut it down and power it up & see if most ethernet ports status/activity leds do not flash on startup that would be a good finale so we know if its just my unit or it is ‘hidden feature’ in all of them.
In regards to the blink command - empirically found it only works when there’s an active (hooked to another device) cable plugged to the ethernet interface that’s being blinked.
