I made a biggest mistake ever. Tried to upgrade a perfectly working RB433AH on distant node from 4.17 to 5.2 because of some reason after upgrading to 4.17 our cacti wireless signal graphs stopped working. The node is pretty far. Is this some common issue or just mine ? Does any experienced the same result ? Thanks.
Update: router does not have any wireless interfaces, just ethernet vlans. Upgraded via ftp.

did the routerboard stop working, or the cacti graphs stopped working ?

did the routerboard stop working, or the cacti graphs stopped working ?

Nope, lets better clarify. At first I upgraded to 4.17 few days ago. Than I found out that some of our cacti graphs stopped working. I didn't want to downgrade so I tried upgrate to 5.2. After reboot the RB is no longer available. I'm quite mad, because it will take so much effort to go there. The place is secured. I need to contact another person with access and meanwhile 100 people have no internet. aggggr. I'm not sure if I would have to replace the RB, or just reboot or what...

The board probably upgraded fine. Some series of boards had issues with 4.15-4.17 I believe where they wouldn't always shut down properly upon a reboot, so require a power cycle when they don't come back. Get someone to power cycle it physically and it should come back up with 5.2 installed.

The board probably upgraded fine. Some series of boards had issues with 4.15-4.17 I believe where they wouldn't always shut down properly upon a reboot, so require a power cycle when they don't come back. Get someone to power cycle it physically and it should come back up with 5.2 installed.

Yea, you're right. I had to go there and power cycle the board. 3 hours wasted, but it works.

The board probably upgraded fine. Some series of boards had issues with 4.15-4.17 I believe where they wouldn't always shut down properly upon a reboot, so require a power cycle when they don't come back. Get someone to power cycle it physically and it should come back up with 5.2 installed.

Yea, you're right. I had to go there and power cycle the board. 3 hours wasted, but it works.

I think with reboot becoming a shutdown with 4.16 upwards, my solution will be power relays toggle the normally closed to open and then back to close via gsm module, had to go to site just to reboot a router (4.16) could not gain access by remote as it was locked up?

There are several people that make switched PDU's for reasonable prices depending on your needs. Some of them have serial ports you can connect to a modem, most will have an Ethernet interface and will ping given IP addresses and if they don't get a response power cycle an outlet.

With that being said, the reboot problem has been fixed in 5.x
http://www.mikrotik.com/download/CHANGELOG_5

Hello, I had few sudden deaths on RB433AH after upgrade on 6.12. routerOS. Can anybody tell me if there is way to make it works via serial cable or sth else. ? It boots, beeps but ethernets and wlans wont work ??

We use DLI products. Their Web Power Switch and PoE Switch POER24.

http://www.digital-loggers.com/

Great products and will autoping devices and cycle power to specific ports on loss of ping.

Whenever I remote upgrade a router I ALWAYS setup an autoping to it just in case the router doesn't come back up.

You didn't have this issue with 433AH ?