Tried:
Hold this button during boot time until the user LED light starts flashing, and release the button to reset the RouterOS configuration.
Did not do it’s thing. All ports death eth1 - eth8 and sfp+ 1 and sfp+2
Tried:
Keep holding the button for 5 more seconds or until the user LED turns off, then release it to make the RouterBOARD look for Netinstall servers. The first Ethernet port is used for the Netinstall process.
.
Netinstall did not work. Port 1 stays dead.
Will try:
Regardless of the above option used, the system will load the backup RouterBOOT loader if the button is pressed before power is applied to the device. Release the button before LED begins to flash, to only load the backup RouterBOOT without resetting. This is useful for RouterBOOT debugging and recovery.
Will let know.
My seller wants me to send device back to warehouse. And does not acknowledge until they receive it, it is defective. I do not know if this is a standard practice, but this makes me worried about waranty at all and use Mikrotik in a business environment.
Ok, i started over and did use different setup with a small switch between my USB network adapter and Mikrotik Switch Port 1. And surprisingly, it did reboot and was seen with netinstall. So the switch is functioning.
I don’t understand why all ports are dead, lucky had a configuration backup and all ports worked fine with new firmware. Now it is in stability test to see what goes on.
The strange thing, it died exact at 12:00 PM.
Now I still have to figure out what happened and why the switch died. I disabled the automatic firmware update so that is not going to be an issue.
There are many possible reasons for device to misbehave. Unfortunately one of them is (invisible) configuration corruption which is also saved in binary backup. If such backup is restored on (newly installed) device, corrupt setup is back in place and waiting to screw things. So if the problem will show again, the best way round it is to create textual export of config (command /export show-sensitive file=anynameyouwish), fetch file off device, netinstall it and then apply config via CLI (or GUI, translating config items to many mouse clicks). Textual export doesn’t contain user data, certificates and SSH keys (possibly few more things), you’ll have to re-create those things in different ways.
I always make an export backup, because I like it to have a readable version of it.
I started to donor that way because I had issues with ASUS where restore settings after upgrade really bricked stuff. Also from a professional point of view it is handy when you want to document things why you do things you did.
Now my home setup is to small to put things in Git to make version history so I stick with just text based config backup.
So far so good it is still running. But I still wonder what went wrong. And sadly nothing logged of interest on my SYSLOG server.
Sometimes people plug in power, check led to confirm working device and disconnect it. If you have extremely unlucky timing and unplug it during the first boot, when it applies default settings and writes this configuration to disc it could corrupt configuration. But it happening exactly at 12:00 on its own, sounds like something time dependent was involved. Maybe a script or power switch-over?
I’d also check license with /system license print
With corrupted installation this can be corrupted as well and demo times out after 24h. If RouterOS time was not set timeout would happen at 1200.
I checked the license and the config. All looks great but I think some settings I had where not well for the device, although it might be a firmware bug or so. For now the device is stable.
My device is behind an UPS (which works well) and my home is behind an off-grid hub (with battery and solar) so no power interruptions happening
But I have to admit that I do not always did a shutdown of the device gracefully because it is never needed with the Cisco and Aruba stuff as long as you do a write config.
I checked the license and the config. All looks great but I think some settings I had where not well for the device, although it might be a firmware bug or so. For now the device is stable.
My device is behind an UPS (which works well) and my home is behind an off-grid hub (with battery and solar) so no power interruptions happening
But I have to admit that I do not always did a shutdown of the device gracefully because it is never needed with the Cisco and Aruba stuff as long as you do a write config.
