Upgrading AirWave through CLI

Just an example of Airwave upgrade from 8.0.11 to 8.2.4 version. Can be realised from Internet or from local file. Upgrade example is using Internet after failing to find the local file. It tooks a loooong time to download the file. Don’t quit the SSH windows or you will have to restart upgrade process

[root@localhost mercury]# start_amp_upgrade
Enter desired AMP version: 8.2.4
Directory not specified; using /root.
Upgrade script AMP-8.2.4-amp_upgrade was not found in local cache.
Upgrade package AMP-8.2.4-x86_64-cvs.tar.gz was not found in local cache.
Preparing to connect to Aruba Support Center…
Enter your Aruba Support Center username: blablabla@coucou.com
################################################################## 100.0%
Upgrade package AMP-8.2.4-x86_64-cvs.tar.gz was not found in local cache.

After the upgrade, your system will be converted to use AMPCLI and the Linux s hell will no longer be accessible.
It is recommended that you cleanup some disk space before the upgrade by remov ing old AMP upgrade tarballs from /root directory
and/or old pre-upgrade backups from /var/airwave-backup directory.
* Do you want to continue with the upgrade? (yes/no): yes
Download upgrade package from:
1. Aruba Support Portal
2. HPE My Networking Portal
Enter your choice (1 or 2): 1
Preparing to connect to Aruba Support Portal…
################################################################## 100.0%
Validating the upgrade package…
Upgrade package is OK.
Upgrading AMP to version 8.2.4 from version 8.0.11…
Detailed log will be written to /var/log/upgrade/AMP-8.2.4-upgrade.log
STEP 1: Moving old version aside.
STEP 2: Unpacking upgrade package.
STEP 3: Checking for compatibility.
STEP 4: Stopping AMP services.
STEP 5: Installing upgrade.

Updated kernel packages that fix various security issues are now
available for your OS. To upgrade, select 'Upgrade' menu item on the AMPCLI Menu ,
and then choose 'Upgrade OS Kernel' menu item.
For more information refer to the security advisory:
https://rhn.redhat.com/errata/RHSA-2017-0036.html

Duplicate devices or devices with incomplete information exist in the AMP databa                                                                                                             se.
See /var/log/duplicate_or_incomplete_devices for details.
For additional information please contact Aruba Support at:
1-800-WiFi-LAN or http://hpe.com/support/hpesc
STEP 6: Restarting AMP services.
Setting up AMPCLI
Setting bootloader password…
Done
Generating encryption keys…
Done
Importing Official key…
Done
Fixing up post_nightly_maintenance script…
Done
Adding recovery user…
Adding recovery user: amprecovery
Done
Setting up secure accounts…
Setting admin username…
Admin Username (default 'ampadmin'): admin
Admin user is admin
Done
Setting admin password…
Admin Password:
Verify Password:
Done
Done
Removing alias for less…
Done
AMPCLI Setup completed
Your system has been converted to use AMPCLI.  You may now
log in as admin. If you lose the password for admin you
may log in as amprecovery (password recovery) on the console to reset
the admin password.
Remove any OS user accounts you may have created to complete
the securing of the system.
Once you log out, the linux shell will no longer be accessible.

Post upgrade schema check is in progress..
This may take a few minutes..


Run fix_missing_indices to fix the missing indices.

Upgrade from 8.0.11 to 8.2.4 is successful.
svn: E155007: '/root/svn/mercury' is not a working copy
-bash: [: !=: unary operator expected

Author: Kévin SAS

I am Kévin SAS and live in France. I am an engineer in network and security. I worked for a lot of customers in these domains : Wireless, LAN, Datacenter, VoIP with several brands like Cisco, HPE, Aruba, Palo Alto amongst others. Previously working for a service provider. I currently work for an integrator while giving me lots of opportunity to learn. This blog stores some technicals notes I wanted to share.

Leave a Reply

Your email address will not be published. Required fields are marked *