Monitoring, Management & Location Tracking

Migrating Airwave to new HPE servers
Requirement:

Migration of existing AMP to new HPE servers.

 

- Existing AMP servers or VM infrastructure.

- New HPE AMP server



Solution:

All new HPE AMP servers which will be shipped will be pre loaded with AMP version 8.2.0.2

Scenario 1:

Existing server or VM server with any version prior to 8.2.0.2, should be upgraded to 8.2.0.2 version by

# start_amp_upgrade -v 8.2.0.2

Take backup of existing server by below command. The backup will be stored under /alternative folder as databackup.tar.gz

# amp_backup

Restore the backup on new HW by copying the backup file under /tmp location

# amp_restore -d /tmp/datbacakup.tar.gz

 

 

Scenario 2:

Existing AMP server or VM server with version greater than 8.2.0.2, new HPE server should be upgraded to same version as existing server by

# start_amp_upgrade -v <Existing AMP version>

Take backup of existing server by below command. The backup will be stored under /alternative folder as databackup.tar.gz

# amp_backup

Restore the backup on new HW by copying the backup file under /tmp location

# amp_restore -d /tmp/datbacakup.tar.gz

 

 

 

 

 



Configuration:

1. Always make sure, we run the commands from /root/svn/mercury/ folder on AMP CLI.

2. Please use 'Screen' mode on CLI to ensure upgrades, restore or backups will run smoothly even if CLI times out or closed by mistake

# screen

Below link will explain the usage of screen mode in Linux terminals.

http://www.tecmint.com/screen-command-examples-to-manage-linux-terminals/

https://www.rackaid.com/blog/linux-screen-tutorial-and-how-to/

3. If AMP server cannot reach internet for online upgrades, please copy the upgrade image to /root folder and run the upgrade commands from /root/svn/mercury directory.

 



Verification

1. To ensure upgrade is completed, please check the upgrade log under /var/log/upgrade directory.

2. to ensure, backup restore is completed, verify the restore log under /var/log directory

3. Always check mdf5sum of the upgrade image or backup taken to ensure the files are intact. to check md5sum in aMP, run

# md5sum <file name>

ex: # md5sum databackaup.tar.gz
4. Once the migration is done, make sure to login to UI and verify if the AP count is fine and VisualRF working fine

 

 

Version history
Revision #:
2 of 2
Last update:
‎05-05-2016 01:09 PM
Updated by:
 
Labels (1)
Contributors
Search Airheads
Showing results for 
Search instead for 
Did you mean: 
Is this a frequent problem?

Request an official Aruba knowledge base article to be written by our experts.