We are in the middle of a Hivemanager NG VA implementation.
One of our implementation teams has used by mistake the entitlement key destined to one site (let's call it Site 😎 implementation into another site (let's call it Site A). Both sites requires a different number of AP.
On site A we have used: hmva-signed-220.127.116.11-NGVA-2018-04-10-dell.ova
On site B we want to deploy : hmva-signed-18.104.22.168-NGVASEP18-2018-09-19-dell.ova
We want to explore the options we have in order to fix this issue:
1.- Load the right entitlement on site A (which is operational right now) and remove the entitlement key that corresponds to site B in order to install it on that site.
2.- Upgrade the Hivemanager VA on site A from 22.214.171.124 to 126.96.36.199 and move this VA from Site A to site B. Perform a fresh implementation of the VA on site A with the right entitlement key and re-associate the all the implemented APs (bear in mind this implementation is operational right now).
3.- Open a case with tech support in order to fix the issue.
Please give us your feedback about the right way to fix this issue,
Thanks in advance
For HiveManager Virtual appliances that have a key we need to remove, we'd need to reach the shell of the VA to remove the key from there. You'd want to open a technical support case for this as you'll need a shell password that a technician will have to generate for you.
Thank you for the feedback Sam, asI understand TS is the only one qualified to intervene the shell. That's correct?
That is correct.
Thank you again Sam.
These operations of removal and installation of entitlement keys can affect the services of the WLAN network?
Do we need a maintenance window in order to reassign the APs to the new entitlement key?
Hi Ricardo, I hope you had a good Holiday! The process to remove the entitlement key won't interrupt the HiveManager or AP functionality. The APs are controlerless regardless, so even if the HiveManager goes down completely on any given day, the APs will continue to pass client traffic as normal.
It's important to know that the entitlement keys are not attached to any particular AP. The entitlement key does not even distinguish between an AP, a route,r or a switch. It only cares about the total number of devices in the HiveManager at one time.
So overall, no maintenance window is needed, just a time when we will have access to the CLI of the HiveManager.
Thank you very much Sam. I hope you have had a great holiday.
I wish you the best to you and your team in this new year to come.
Contact Us:Sam PirokCommunity@extremenetworks.com