06-28-2018 12:02 PM
I need to know if the server will change or what I will need to do on my end to make sure customers are not effected at all.
Solved! Go to Solution.
06-28-2018 03:45 PM
Hello Jeremiah,
With the 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
06-28-2018 03:52 PM
06-28-2018 03:50 PM
Hi Jeremiah,
I looked up your instance, and since you are on the Latest HM-Classic version 8.2r2, nothing will change for you.
I believe the email went out to everyone.
Hope this helps,
David Souri
HiveCommunity Moderator
06-28-2018 03:48 PM
06-28-2018 03:45 PM
Hello Jeremiah,
With the 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