remote reboot = dangerous?

RouterOS General
1

I had a thread that has now been locked describing how i can not remote reboot my RB 112 at an install bc it always freezes on starup requring a power cycle.

at another install i have 19 Wrap 2e’s…each with 8602 radios…MT 2.9.27..

you CAN NOT restart any of these…THEY all will crash…i have to log in to my PoE switch and power cycle them (thank god for that poe switch)


I updated one to 2.9.35 and it still can not be rebooted…

whats the deal?? this means you can not remote upgrade or reboot Wrap Boards?

2

You really should try using the search…the fix has been mentioned many times.

3

You are not talking about having the Routerboard Package enabled to be able to reboot?

4

This is for the WRAP:

MikroTik RouterOS
Please request the latest BIOS version from PC Engines when using RouterOS.
Set console baud rate to 9600.
WRAP does not include a keyboard controller. To ensure clean restart, please install the package
routerboard.npk
from
http://www.mikrotik.com/download.html#v2 > → all_packages.zip
The package is designed for MikroTik’s RouterBOARD, but will also work for WRAP. Source:
MikroTik technical support.
RouterBOARD, RouterOS and MikroTik are trademarks of MikroTik.

Taken from PC Engines website, the creators of WRAP. In essence you have to flash the latest BIOS and use the routerboard version of ROS. This is how our WRAP devices are set and never need power cycling, as the watchdog and reboot features work fine.

5

Regarding WRAPs, the x86 package includes routerboard.npk. We have found a newly flashed WRAP will hang -once- when first setup requiring a manual power cycle then no problem with reboots.

6

This could very well be an issue for the WRAP manufactures, We have many WRAP 2C, 2E and 1E-2 boards running 2.9 ROS with no install hangs. Is the power supply grunty enough? we have found that anything below 12v 3A your asking for trouble (can blank CF cards etc on reboots, forget to initialize Wireless cards etc.)

7

Yeah, 18V 1.5A but never a problem later on…

8

Same here, got plenty kicking around that have no problems with field resets as long as the routerboard package is installed.

9

The key indeed is having the routerboard package installed (and activated).

The first reboot during installation cannot work, because the modified reset code from the routerboard package (which is needed for correctly resetting a WRAP by software) is not active at that point.

But I have never ever seen problems rebooting a WRAP that is in service and has the routerboard package installed in several years now.

Best regards,
Christian Meis