3.5.1 Locking Up After 200+ Days of Uptime

I'm having SMs, which are running 3.5.1, lock up after having an uptime of 211-240 days.  I didn't see anything in the 3.5.2 release notes about this.

Thanks,

Dan

Sorry, I should mention that the behavior of the SM after they have "locked up" is that while they are still connected to the AP, pingable and show online in cnMaestro; SSH, SNMP and HTTP access are non-functional and they also do not pass user traffic (customer's end up calling in stating they have no internet access).

Thanks,

3.5.2 has been out for a while and seems stable. Why not give it a try?

I am running it on some devices, but I’d rather not upgrade thousands of devices just to wait 200 days for them to potentially lock up again. I’m looking for some feedback from Cambium in the issue.

You’d want to submit a ticket. I have units up 200+ days on 3.5.2 no issue.

1 Like

Yep, posted here to see if I was the only one seeing this, or if others had longer uptimes without issue. Also to make others aware of the potential issue so they can proactively reboot radios prior to having them lock.

We've never seen this happen... although we're running 100% 3.5.2

1 Like