07-02-2018 02:06 PM
We have firewalls in place, so the online instance changes to a new server and gets a new IP and Hostname?, when will we be notified of this? this is something we need as much heads up on as possible, to get all the necessary changes implemented in a timely manner, thanks.
Solved! Go to Solution.
07-10-2018 02:16 PM
Hi Richard,
The IP/Hostname won't be determined until the Upgrade is Complete. I'm not certain about email notifications for the auto-upgrade, as it hasn't started yet.
What I am certain about: if you upgrade manually, you'll know the new IP/Hostname first, as soon as the upgrade is complete (typically 30 minutes), then you can adjust the firewall.
Hope this helps,
David Souri
HiveCommunity Moderator
07-10-2018 02:37 PM
07-10-2018 02:16 PM
Hi Richard,
The IP/Hostname won't be determined until the Upgrade is Complete. I'm not certain about email notifications for the auto-upgrade, as it hasn't started yet.
What I am certain about: if you upgrade manually, you'll know the new IP/Hostname first, as soon as the upgrade is complete (typically 30 minutes), then you can adjust the firewall.
Hope this helps,
David Souri
HiveCommunity Moderator
07-10-2018 02:01 PM
07-02-2018 03:52 PM
Hello,
You always have the option to Upgrade ahead of the Auto-Upgrade date, from Home -> Administration -> Hivemanager Operations -> Upgrade Software
With any Hivemanager Software upgrade, the Hivemanager Classic instance will move to a new Server, and will have a new IP Address/Hostname.
In a network setup with "No firewall", the APs will reconnect to the new Hivemanager Classic Instance on it's new server.
If you have Firewall rules that Specifically allow Aerohive devices to communicate with HM-Classic, you may need to modify those rules to reflect the new IP/Hostname.
Here are the Services/Protocols/Ports that Aerohive devices and HM-Classic use:
https://docs.aerohive.com/330000/docs/help/english/8.2r2/hm/full/Content/ref/services.htm
The above information only applies to you as the Network Administrator.
End-Users with their Client-Devices won't notice the switch at all. This is due to our "Controller-Less" design, having configuration distributed on each Device.
It always good to send a Complete-Config Update to all Hive Connected devices after a Hivemanager upgrade.
Alternatively, if a reboot is not possible right away, a Delta-Configuration will suffice.
Finally, once HM-Classic is up to date, I would recommend starting the process of Updating firmware on all devices in the Hive.
I am also happy to answer any questions along the way,
Hope this helps,
David Souri
HiveCommunity Moderator