I have observed a situation when two mikrotik devices are connected with a rollover serial cable and device1 is rebooted, it is subsequently unable to boot and the other device (device2) receives the following messages in terminal:
09:55:04 echo: system,error,critical login failure for user .2 via local
[admin@CRS309] >
09:55:05 echo: system,error,critical login failure for user boot over Ethernet via local
[admin@CRS309] >
09:55:06 echo: system,error,critical login failure for user What do you want to configure? via local
[admin@CRS309] >
09:55:07 echo: system,error,critical login failure for user via local
[admin@CRS309] >
09:55:08 echo: system,error,critical login failure for user boot over Ethernet via local
[admin@CRS309] >
09:55:09 echo: system,error,critical login failure for user OT-6.48.2 via local
[admin@CRS309] >
09:55:10 echo: system,error,critical login failure for user Select boot device: via local
[admin@CRS309] >
09:55:11 echo: system,error,critical login failure for user boot from NAND only via local
[admin@CRS309] >
So in order for device1 to boot, device2 has to:
- /system console disable 0
- /system serial-terminal serial0 (and type x to continue boot process)
So if I want to successfully reboot device1, i need to disable console on device2. Otherwise device1 is stuck in the boot process.
Is that a known problem? are there any configuration options that would prevent this type of behaviour?