After migration of Aerohive AP's from one instance to another we are facing few issues with some AP's. The AP's are being factory reset or they are loosing connectivity to the hive manager. Please suggest what all can be the reasons?

[vsirpurker]

After migration of Aerohive AP's from one instance to another we are facing few issues with some AP's. The AP's are being factory reset or they are loosing connectivity to the hive manager. Please suggest what all can be the reasons?

[bruce_stahlin]

Below are the steps a device takes to establish capwap. If the APs are on the same VLAN as HM (point 2), the only option is to override with manual configuration. Otherwise, check your DHCP and DNS for any entries for the old HM instance and point them to the new.

HiveAPs use the CAPWAP protocol for management, and perform the following steps for HiveManager discovery:

1. Manual Configuration - Manually configure the HiveManger IP address or domain name through the AP command line interface. Login to the AP via console using the default username "admin" and password "aerohive". Configure the HiveManager with the command "capwap client server name ".
2. Layer 2 Broadcast - HiveAPs broadcast within the layer 2 domain (subnet) for a HiveManager appliance or Virtual HiveManager (VHM) appliance.
3. DHCP Options 225 & 226 - Specify the HiveManager server in a DHCP option returned to the AP. Option 225 specifies a domain name and option 226 specifies an IP address. Only one option is required.
4. DNS Resolution - If no HiveManager server was specified by DHCP options, then the HiveAP attempts to resolve "hivemanager.localdomain", where the local domain name assigned through DHCP is appended. If this name resolves to a valid IP address the HiveAP attempts to join the HiveManger at that address.
5. HMOL Staging Server - HiveAPs attempt to reach the HMOL Staging server at staging.aerohive.com<>. If the staging server has the AP registered, it will redirect the AP to the configured HiveManager server. If the client is using a VHM cloud appliance then the AP is redirected to hm-online.aerohive.com<>.

[vsirpurker]

Hi,

The old Hive Manager is running.

we even pointed the DNS server to new Hivemanager for the sites moving.

even though we are seeing when the AP looses the connection with new Hive Manager it is trying to connect with the old one.

Please suggest

[sderikonja1]

Do you run on prem HiveManager?

Is the old HiveManager still up and running?

Have you changed DNS to point at new HiveManager?

[bruce_stahlin]

When migrating to a new VHM, the devices will resort to factory default. If you're a cloud customer, your best option is to build up your policies and locations, then when you onboard your devices, use the advanced option and assign them to the appropriate location and policy so they will receive the correct configuration.