Network Management


Migrating to new airwave server

We're in the process of migrating to a new Airwave hardware platform. THe new hardware will end up with the same IP address as the current server  So...


1). current server (Centos 6) does nightly backups which are transferred to our filestore

2). Server upgraded to so backup of correct version.

3). New server buiult using image and is up and running on different IP address with self signed cert

4). Have backed up all licenses from existing server


Is the following appropriate


1). Restore backup onto new server

1a). Generate file trasfer user on  new server

1b). From a remote host scp the backup file onto the new box

1c). Use the restore command to restore the backup file onto the new server.

2). Shutdown the old server

3). Assign the old server ip address to the new server

4). Apply old licenses to new server (or are these restored from the backup)

5). Apply valid https cert to new server

6). Upgrade to


Would that be it ?





MVP Expert

Re: Migrating to new airwave server

Looks like a good plan

Thank you

Victor Fabian

Pardon typos sent from Mobile
Thank you

Victor Fabian
Lead Mobility Architect @WEI

Re: Migrating to new airwave server

Looks good. Backup will have the license key, so restoring the backup will have the license updated as well. Only thing is updating the right IP.


If my post helped you, don't forget to give kudos ;)

Re: Migrating to new airwave server

So almost worked.


1). Theres a note in the release notes for about ssh being disconnected and to send NUL chars every 30 secs ... you got bitten by that


2). By default /var/log is set to 20G on a new server . We had a .GZ file that was 11G so restore complained that not enough space in /var/log. Turnes out that ther is a kernel log in the backup file. Had to have a TAC call to "strip" this out of the backup file and it all went through.


3). Just need to insall a new https cert


Re: Migrating to new airwave server

So next issue was


Hardware different to original server. From the CLI confiured the static IP address and routing info for the correct interface (eth3)


Did a restore of data onto the server  and everything seemed to work .. excepot from the gui there was no local ip address defined and it appeared that although we were receiving data from controllers, airwave thought they were down. Adding a  (local) ip/router set of into from the gui fixed that .


Only outstanding thing now is , from the CLI, we seem to  have the static ip address on both eth0 and eth3 .. eth0 is not connected to anything

Search Airheads
Showing results for 
Search instead for 
Did you mean: