hello I had a real DISASTER upgrading to 3.5 I have the very same disaster upgrading from 3.3 to 3.4 via cnmaestro. Cambium should insert in the upgrade procedure, to first REBOOT the unit, then upgrade. I had about 200 units STUCK (required power cycle for 5 minutes) after the upgrade.
When we mass-upgrade from CNMAESTRO, cambium could set by default to REBOOT the unit FIRST, then UPGRADE.
Hi,
Thank you for your feedback.
We will review your proposal and revert back to you.
It makes sense to add optional mass reboot before upgrade.
Thank you.
Thank you for your answer.
You should REBOOT the unit first, wait 5 min, then reconnect again to the CPE and perform the upgrade.
After 5 minutes the CNmaestro should verify the uptime, so it can check if the unit rebooted correctly or not. In this case, the cnmaestro should NOT perform the upgrade (see the 3.3. bugs of no reboot).
That procedure shuold avoid troubles in the upgrade procedure and the upgrade should be flawlessy.
In the last mass upgrade with 3.4 / 3.4.1 and 3.3 we had about 200 failed with powercycle needed to recover the unit with NO UPGRADE done.