RB433AH lockups since ROS 4.17

Hardware MikroTik hardware general
1

I’ve been running an RB433AH at home for a couple years. It’s been rock-solid, and I routinely update ROS and firmware on it before deploying to the rest of the network. However, since I updated to v. 4.17, it’s hard-locked at least daily, requiring power cycle (unresponsive to ssh and Winbox). Oddly, I can still ping through it, but that’s it. It’s never been over clocked and the configuration has not changed since I updated the firmware.

Any ideas? Anyone else having a similar issue?

Thanks

/Mike

2

what kind of configuration you have on that board?
Check the memory usage on the board.

3

Configuration is pretty basic; setup as an ordinary router with an wireless access point. 109.8MB free memory of 128, and the CPU is usually only at <10%. Few of these routers have ever had it so good. :slight_smile:

4

I’m having this happen too. My 433AH is one of the first group that came out. I don’t seem to have the same problem with other 433ah’s that I use that are newer. Not sure that this is relevant, but I thought I would throw that out there.

5

Indeed, mine’s another very early one. I hesitate to deploy the 4.17 to any others right now, at least until I have a better handle on what might be happening. I have a spare board with un-updated firmware I could copy the config to, as well an a regular 433 to try as well. Nice to see a fellow Minnesotan as well.

6

please send supout.rif to the support so we could look at what is happening.

7

Just sent it. Thanks indeed.

8

Any ideas yet?

9

For the moment, I put a watchdog timer on one of my routes. That has helped already..or at least I don’t have to go out there and recycle the power. :slight_smile:

10

DeepMAGi, I’m working with a marina thats wants to know that there are other companies they work with Mikrotik in MN can you please get in touch with me.

jxpelle @ gmail.com

Thanks