I need to reboot all routers at 00:00 every day. This is because they all have Sierra Wireless MC8790 PCI-E cards inside and are connected to the base via GPRS-PPTP-VPN. The problem is that randomly these routers (RB411U) just disconnect from GPRS network (unknown reason) and wont connect back to it. They only connect after reboot, otherwise it’s just "Opening port…Connecting…Disconnecting). After reboot it works fine. I have succesfully created a script and a schedule that reboots the router at a certain time.
Now for the problem:
I’m using a RB793G as a router, to test my new script on. I have set up a schedule to reset the router every 10 mins. After 3rd or 4th reboot the router just freezes (all network ports are silent) and it needs to be unplugged from power aswell, then when plugged back it it works for 3-4 times again then freeze. All routers have FW 4.16 on installed. Any clues?
In this case you see, that there is a newer version of the Bootloader firmware available already inside your current RouterOS version. Note! New Bootloader versions come with the routerboard.npk package when you install and upgrade your router, this is why always make sure you have not forgotten to install this package.
u can try THG’s approach and also u can set a ntp server to ask the time to that server and after that u can modify the scrip to reboot the router at a specific time, because as far as I know when you reboot the router the time will change and unless u are a NTP client u will have to modify the hour everyday so the router reboot at ur specific time.
NTP client is set up and already running. The thing is that the router reboots like 3-4 times without a problem, but the 5th time it freezes. I have installed the full 4.16 package on this router so i would think that bootloader has also been updated. Am i wrong?
We had a router that was set to reboot every day at 3am. We came in one morning and found the router had shutdown but not restarted, and it had to be power cycled. Its graphs all went right up to 3am, and stopped. We are no longer letting it reboot itself, (we had found another workaround for the problem we were originally having it reboot itself for anyway, fortunately).
Thank you for the info THG, but it’s gonna be too costly for us to implant these on 100+ locations. I would love to get a response from “the staff” on when this issue is going to be fixed, since this is a really basic function and it works great on cheap routers.
Since it’s random it seems like it would make more sense to use a ping watchdog to reboot the device only when it loses it’s connection. It also means the client doesn’t need to wait until the scheduled reset if the modem goes down much before 0:00.
Bah 3 more locations just went down this night. 150km apart. The thing is, I have no problem with Ruckus router with integrated GPRS module. It never freezes, but it costs 3 times as much. But if I include all the km’s i’m gonna have to travel (and i have absolutelly no guarantee it wont freeze again) its the same price or even lower considering the time lost.
I can try that, but any solution based on RoS reset is unreliable.
According to Wiki http://wiki.mikrotik.com/wiki/Watchdog
there is a hardware watchdog in RouterBOARDs.
You should give it a try, it never failed for me.
The problem isn’t in not knowing how or when to reboot, but the reboot process itself. Instead of a reboot if randomly shuts down. The problem is very simply reproducable, I’ve experienced it on ALL routerboards i’ve come across. RB711a, RB493g, 493AH, 433AH, 750,…
All I want to say, is that ‘/system reboot’ is software function,
but watchdog is hardware-based and works different way.
As I wrote earlier, watchdog never failed for me.
I’ve been testing this for a week now. Still the same problem even with watchdog. I got 2 successul reboots on fail to ping, but the third shutdown the router.
Try to remove Sierra Wireless MC8790 from one affected router
and make some tests. Maybe router doesn’t restart properly
due to some card incompatibility.
