NOTE: This guide is designed for AOE version 16.01 and higher. If you are on an older version of AOE ( 10.01 or lower ) then please refer to the respective AOE installation guide for upgrade instructions.
Before starting any migration or upgrades to AOE, you need to know the following.
The installation directory can be changed from default. The default directory is /opt/dorado/. In this guide, I will refer to AOE's installation directory as $INSTALL_ROOT. Simply replace that term with your installation directory. If you do not know whom is the AOE Admin or the installation directory is located then run the command "cat /etc/adtran-aoe-env.conf". You can see an example of the output below.
There are two common directories that we will be changing to. The default installation directory and the scripts directory. All scripts must be ran as the AOE Admin and must be ran within the scripts folder. Listed below are common commands that will be used.
When shutting down AOE, It will ask for multiple usernames and passwords. First, it will ask for the AppServer password. By default, the password is "trustnoone". Next, it ask for the Automated Interfaces password. There is no password assigned by default so press ENTER on the keyboard to continue. Lastly, it will ask for is the MySQL Username. By default a username is not created. If you have not assigned a username and password to the MySQL database then press ENTER on the keyboard.
Please refer to the table below to see which version of AOE is compatible with CentOS for installations and upgrades.
AOE Installation Compatibility
|AOE 8.0||AOE 9.0||AOE 10.0||AOE 16.01||AOE 16.02||AOE 16.03||AOE 17.01||AOE 17.02||AOE 18.01|
|AOE 18.03||AOE 19.01||AOE 19.02|
|CentOS/RHEL 7.x (systemd ≤ 219.19)||X||X||Y||Y||Y||Y||Y||Y||Y||Y||Y||Y||Y|
|CentOS/RHEL 7.x (systemd > 219.19)||X||X||X||X||X||systemd*||Y||Y||Y||Y||Y||Y||Y|
* MUST use special systemd installer linux_deploy_AOE16.03_systemd.zip. Check via yum list installed | grep systemd
AOE Upgrade Compatibility
|AOE 8.0||AOE 9.0||AOE 10.0||AOE 16.01||AOE 16.02||AOE 16.03||AOE 17.01||AOE 17.02||AOE 18.01||AOE 18.02||AOE 18.03||AOE 19.01||AOE 19.02|
|CentOS/RHEL 7.x (systemd ≤ 219.19)||NA||NA||NA||Y||Y||Y||Y||Y||Y||Y||Y||Y||Y|
|CentOS/RHEL 7.x (systemd > 219.19)||NA||NA||NA||Y||Y||Y||Y||Y||Y||Y||Y||Y||Y|
* MUST use special systemd updater lnx_aoe16.03upd_systemd.tar.gz
When upgrading AOE, please be sure to meet the server minimum hardware requirement for the version AOE that you intend to stop at. The server minimum hardware requirement for latest AOE version is as follows,
|Server Minimum Hardware Requirement for AOE 19.02|
|Processor||Intel-based Quad Core processor at 2.06 GHz|
|Hard Drive||100 GB HDD|
|RAM||16 GB RAM|
|SWAP Space||x1 of RAM|
If the new sever has not already been deployed then please refer to the corresponding installation guide for the version of AOE necessary to be deployed. You need to make sure the newly installed AOE server is on the same version as the current AOE server.
Log into the the current AOE server with SSH as the AOE Admin and set the environment variables.. Change your directory to the scripts folder and run ./Backup.sh in your terminal window. This process can take up to 15 - 20 minutes depending on server specs and number of network elements. Once completed, there should be a new file within the scripts folder called AOEbackup. The filename for the backup will include the date the backup was ran, the timestamp of when the backup was ran, and the version of AOE the backup was created with.
Pull the backup off the server using an FTP client, such as Filezilla or WinSCP. You can use the same AOE Admin account for the FTP client in order to get access to the server.
Once you have pulled the backup off of the old server, run through the same transfer process to upload the file to the scripts folder on the new AOE server. After uploading the backup, please login to the new AOE server using SSH and set the environment variables. Change your directory to the scripts folder and run ./stopAllAOEServices.sh.
Verify that you have shut AOE down by running the ./getServerStatus.sh script. If all statuses are down, then AOE has been properly shutdown. In order for AOE to be restored on the new server we need to only have the MySQL database and OrientDB running. Start MySQL by running the ./start_mysql.sh script. This may take a couple of minutes for MySQL to start. Next, you will need to change your directory to the OrientDB folder by running the command "cd $INSTALL_ROOT/adtran3rd/orientdb/bin". In this directory, run " ./server.sh & ". Once you see the prompt that the OrientDB server is active go back to the scripts folder and run ./Restore.sh script as illustrated below. You will need to add the AOE backup filename as an argument.
Please note that once you type "AOEbackup" you can use the TAB key to auto complete the filename for the backup. When you run the script, you will be given a prompt on what you would like to restore. Select the "moc" option by typing moc and pressing ENTER on the keyboard. Custom files include templates, preferences, and server keys as part of the restoration.
Once the script has completed, we will need to shutdown the MySQL database and OrientDB before starting up AOE. You will need to run ./stop_mysql.sh and ./stop_OrientDB.sh scripts in order to shut the databases down. Once both databases are shutdown you can run the ./startAllAOEServcies.sh script. This will go through the process of starting up AOE properly. This process can take 5 - 10 minutes. When the script is finished AOE should now be up and running with the backup from the previous server.
When upgrading AOE you cannot skip a version. For example, if you are on AOE version 17.01 and wish to go to 19.01 then your upgrade path will be from 17.01 to 17.02, then to 18.01 and so on. All upgrade files can be found at adtran.com/aoegroup. You will need to log into the ADTRAN website with an account that has AOE registered with a valid Network Care Plan. Once you have downloaded the necessary update files, upload the files to the default installation directory as the AOE Admin. You will need to run the upgrade as the AOE Admin first, then as root.
Once the files are uploaded, login to the AOE server using SSH and set the environment variables. Change your directory to the scripts folder and run the ./stopAllAOEServices.sh script. Switch back to the installation directory. You will need to unzip the upgrade file. Use the command "tar zxf $UPDATE_FILE" to unzip the file. You should now have a new folder called updates. Within that folder is a secondary folder for the respective AOE version. See image below as an example.
Once you have unzipped the update, change your directory to the upgrade folder. If you are attempting to upgrade to 17.02 as per our original example then you would change your directory to $INSTALL_ROOT/updates/aoe17.02upd/. Before you start the upgrade MAKE SURE that you are the AOE Admin and you have set the environment variables. If you have done so then run the ./upd.sh script. The script will tell you who you are currently logged in as, who is the AOE Admin, and the current version installed. When you are ready to update select option "i". From here the upgrade process will begin. You will soon receive another prompt asking "Do you wish to continue?". Type in "y" or "yes" if you wish to continue. This process can take up to 30 minutes or longer.
Please note that once you have finished the update as the AOE Admin you will be prompted to rerun the ./upd.sh script again as root. Use the command "su" to change your user to root. This should allow for you to stay in the current directory. Rerun the ./upd.sh script to install the root portion of the upgrade. The final portion of the update should take 30 seconds to a minute to complete.
If you have multiple upgrades to run through then type 'exit' into your prompt to go back to the AOE Admin. Change the directory to the next upgrade folder and run the upd.sh script as previously described until you are on the desired version. Once all upgrades are completed make sure that you change back to AOE Admin. As the AOE Admin change your directory to the scripts folder. Run the script ./startAllAOEServices.sh. In about 5 - 10 minutes your AOE server should be up and running on the latest installed software version.