Is possible to make a downgrade of HM from 6.2r1 to 6.1r6 without any downtime in my wifi network?

  • 1
  • Question
  • Updated 3 years ago
  • Answered
  • (Edited)
Hi, our wifi networks starts with APs 141 and HiveOS 6.1r6 with HM 6.1r6, then after few moth we bought new AP230 and all were upgrada to HiveOS 6.1r6, but the HM was update to 6.2r1. Then actually our HM is with 6.2r1 and the all APs are with HiveOS 6.1r6.

The problem is that when any person connected to ou wifi trying download a file in our local network with laptop with 802.11g technology, the maximun transfers was 60KB/s, with 802.11n or 802.11ac we don ́t any evidence about this issue.

This situation didn ́t happed when we had the HM in 6.1r6... now can we downgrade without any downtime in our local wifi network?

Thanks for you help

Fabian
Photo of Fabian

Fabian

  • 12 Posts
  • 0 Reply Likes

Posted 3 years ago

  • 1
Photo of Brian Powers

Brian Powers, Champ

  • 396 Posts
  • 92 Reply Likes
To change the firmware on the devices, they will have to be rebooted.  The easiest approach I feel would be to just to a "reboot backup" to the devices.  That would have them boot up to their backup image which should be housing the previous 6.1r6 code.  You can verify this by doing a show ver detail to look at the image version on the primary image and the back up image.
Photo of Fabian

Fabian

  • 12 Posts
  • 0 Reply Likes
Thank for your comments, however i'm referring the version of the HiveManager, not the APs.
Photo of Brian Powers

Brian Powers, Champ

  • 396 Posts
  • 92 Reply Likes
Apologizies.  You can do that from the CLI or within the HM GUI itself.  Under Home -> Administration -> HiveManager Operations and Reboot Appliance.  You can choose the backup image of the HM as well and it should roll back to the previous code you had on it.
Photo of Nick Lowe

Nick Lowe, Official Rep

  • 2491 Posts
  • 451 Reply Likes
HiveManager is largely decoupled and out-of-band to HiveOS. The APs run independently with no dependency on HiveManager for full operation.

It is very unlikely therefore that the issue you're experiencing will be causally related to having updated HiveManager from 6.1r6 to 6.2r1.

You would be best doing a root cause analysis of the issue rather than relying on anecdotal correlation. I strongly suspect that you'll find the cause is elsewhere.
(Edited)