Cloud Managed Networks

We have an older AirWave installation that is currently running v 8.2.15.1 on a HyperV host. The goal is to (as transparently as possible) upgrade from the old unsupported version to the new version.

It is our intent to:

1. Upgrade to v 8.2.15.2 and leave online until migration is complete
2. Create a NEW VM on the HyperV host
3. Perform an offline clean installation of v 8.3.0.4 using the same IP address and configuration of the existing AirWave server
   1. Note: We'll be reusing our license from the old server.
4. Backup our current configuration and devices on the v 8.2.x AirWave
5. Import that backup into the 8.3.0.4 instance
6. Flip the virtual switch from the 8.2.x VM to the 8.3.x VM

Can anyone with experience and knowledge see any issues with this as a plan of action?

Thanks in advance for any thoughts or issues that anyone and everyone brings to the table.

That's not a valid upgrade path.

https://arubanetworking.hpe.com/techdocs/AirWave/Consolidated_RN/Content/8.3.0/4/UpgradeProcedure_8304.htm

We have an older AirWave installation that is currently running v 8.2.15.1 on a HyperV host. The goal is to (as transparently as possible) upgrade from the old unsupported version to the new version.

It is our intent to:

1. Upgrade to v 8.2.15.2 and leave online until migration is complete
2. Create a NEW VM on the HyperV host
3. Perform an offline clean installation of v 8.3.0.4 using the same IP address and configuration of the existing AirWave server
   1. Note: We'll be reusing our license from the old server.
4. Backup our current configuration and devices on the v 8.2.x AirWave
5. Import that backup into the 8.3.0.4 instance
6. Flip the virtual switch from the 8.2.x VM to the 8.3.x VM

Can anyone with experience and knowledge see any issues with this as a plan of action?

Thanks in advance for any thoughts or issues that anyone and everyone brings to the table.

We have an older AirWave installation that is currently running v 8.2.15.1 on a HyperV host. The goal is to (as transparently as possible) upgrade from the old unsupported version to the new version.

It is our intent to:

1. Upgrade to v 8.2.15.2 and leave online until migration is complete
2. Create a NEW VM on the HyperV host
3. Perform an offline clean installation of v 8.3.0.4 using the same IP address and configuration of the existing AirWave server
   1. Note: We'll be reusing our license from the old server.
4. Backup our current configuration and devices on the v 8.2.x AirWave
5. Import that backup into the 8.3.0.4 instance
6. Flip the virtual switch from the 8.2.x VM to the 8.3.x VM

Can anyone with experience and knowledge see any issues with this as a plan of action?

Thanks in advance for any thoughts or issues that anyone and everyone brings to the table.

You have to make sure that the new VM on Hyper-V has the NIC Adapter disconnected because you can potentially do an IP Address Conflict (if the same ip address is being used).

While doing the restore of the backup, you  will restore only the configs and noting else, which shouldn't be a problem.

If 8.2.15.2 is on RH you can upgrade to 8.3.0.4 directly but if 8.2.15.2 is on CentOS you have to install 8.3.0.3 AirWave with RHEL and restore 8.2.15.2 backup file and it should work.

There is a thread related to this which can be helpful: https://community.arubanetworks.com/discussion/airwave-backup-inlcuding-ip

We have an older AirWave installation that is currently running v 8.2.15.1 on a HyperV host. The goal is to (as transparently as possible) upgrade from the old unsupported version to the new version.

It is our intent to:

1. Upgrade to v 8.2.15.2 and leave online until migration is complete
2. Create a NEW VM on the HyperV host
3. Perform an offline clean installation of v 8.3.0.4 using the same IP address and configuration of the existing AirWave server
   1. Note: We'll be reusing our license from the old server.
4. Backup our current configuration and devices on the v 8.2.x AirWave
5. Import that backup into the 8.3.0.4 instance
6. Flip the virtual switch from the 8.2.x VM to the 8.3.x VM

Can anyone with experience and knowledge see any issues with this as a plan of action?

Thanks in advance for any thoughts or issues that anyone and everyone brings to the table.

Yeah. You've hit upon the crux of the problems.

1. We have to do the install with the VM 'physically' disconnected (but using the same IP)
2. Then disconnect the old VM from the virtual switch
3. Then connect the new VM to the virtual switch

We must do a clean install, because we're not on Funky 'cold' Fedora (or whatever RHEL is called). ;) 

Hence the need for a clean install.

I guess that we're out of luck on the import directly into 8.3.0.4 from the 8.2.0.x backup.

Thanks for your input/help. :)

You have to make sure that the new VM on Hyper-V has the NIC Adapter disconnected because you can potentially do an IP Address Conflict (if the same ip address is being used).

While doing the restore of the backup, you  will restore only the configs and noting else, which shouldn't be a problem.

If 8.2.15.2 is on RH you can upgrade to 8.3.0.4 directly but if 8.2.15.2 is on CentOS you have to install 8.3.0.3 AirWave with RHEL and restore 8.2.15.2 backup file and it should work.

There is a thread related to this which can be helpful: https://community.arubanetworks.com/discussion/airwave-backup-inlcuding-ip

We have an older AirWave installation that is currently running v 8.2.15.1 on a HyperV host. The goal is to (as transparently as possible) upgrade from the old unsupported version to the new version.

It is our intent to:

1. Upgrade to v 8.2.15.2 and leave online until migration is complete
2. Create a NEW VM on the HyperV host
3. Perform an offline clean installation of v 8.3.0.4 using the same IP address and configuration of the existing AirWave server
   1. Note: We'll be reusing our license from the old server.
4. Backup our current configuration and devices on the v 8.2.x AirWave
5. Import that backup into the 8.3.0.4 instance
6. Flip the virtual switch from the 8.2.x VM to the 8.3.x VM

Can anyone with experience and knowledge see any issues with this as a plan of action?

Thanks in advance for any thoughts or issues that anyone and everyone brings to the table.