Upgraded several customer radios from 2.6.1 to 3.2.1 and though they were still passing traffic I could no longer access 4 of them. Customers have power cycled 3 of them and I was able to access them after that though one took several times power cycling it. I have also upgraded several radios on the bench that would give the "Board in reboot state" until power cycled , a couple took several times power cycling it.
I still have one customer radio that I can not access and it is of course out in the woods powered by solor and running a camera for a customer. So the only way it's getting power cycled is if I drive out there..
SNMP doesn't respond at all
http gives the "Board in reboot state"
I can SSL in and even log in but when I issue "reboot" it sets there for a little bit and then responds "Timeout: No Response from localhost".
Though I can log into the device, will not accept reboot command, SSH is accessable and I can perfomr config show etc, but it does not accept the reboot command there either. SNMP does not work either.
The only way I can reboot this AP is by driving to the site.
The only way I could reboot it was through cnMaestro, maybe this will work for you Brubble1 for the one you have no easy access too?
I'm having the same issue. Tried accessing the page you provided and would not let me log on. Need privelages or something like that.
You need to sign up for the beta program here https://support.cambiumnetworks.com/beta. If you are not interested in a beta release, 3.2.2 will be officially released early next week.
Just confirming that I"m seeing the "board still in reboot state" on about 9 of my 3.2.2 devices. Showing as offline in cnMaestro as well. Happens after entering login credentials via the web GUI. SSH will connect, but not allow any commands to be run.
Second one, I can assume this topic was created for, does not have simple workaround.
And we don't have reproduce for it in our lab.
If I understand you correctly the only workaround is hard device reboot through the power feeding.
We are working with one of the customers regarding this issue now.
Hard reboots are the ones that have affected us, anytime I can not access a unit I try a different browser, catches out the ones with that issue.
I am performing more updates tonight from 3.2 to 3.2.2 seems 3.2.2 is the lesser of the evils.
If I have any issues I will post them. Would you like these emailed in? if so to what address?
On a side note if you update a unit, even after refreshing the page it sometimes shows the wrong firmware, so the browser must also be caching it. Open in a new browser and it refects the true version.
What is the resolution? The AP (in this case a Force ePMP-300) is up a pole at the far end of an aerofield. If I ssh to the device, and issue a "reboot" command, I get:
Timeout: No Response from localhost
What is the resolution other than a hard reboot here???
The other thing we’ve found chimera, is really with any equipment brand, and with any pre-release or work-in-progress firmware (like the Force300), if possible we like to remote-reboot the gear before doing a firmware upgrade. That way, if memory has been used up, or if some bug has the board in distress, that usually clears it up before also giving it a firmware upgrade to deal with.