AirWave 8.2.15.

Release Notes
Copyright Information
© Copyright 2023 Hewlett Packard Enterprise Development LP
Open Source Code
This product includes code licensed under certain open source licenses which require source
compliance. The corresponding source for these components is available upon request. This
offer is valid to anyone in receipt of this information and shall expire three years following the
date of the final distribution of this product version by Hewlett Packard Enterprise Company. To
obtain such source code, please check if the code is available in the HPE Software Center at
https://myenterpriselicense.hpe.com/cwp-ui/software but, if not, send a written request for
specific software version and product for which you want the open source code. Along with the
request, please send a check or money order in the amount of US $10.00 to:
Hewlett Packard Enterprise Company
Attn: General Counsel
WW Corporate Headquarters
1701 E Mossy Oaks Rd Spring, TX 77389
United States of America.
 Chapter 1
Revision History

Revision History
The following table lists the revision numbers and the corresponding changes that were made in this
release:

Table 1: Revision History

Revision Change Description

Revision 01 Initial release.

AirWave 8.2.15.2 | Release Notes 3

 Chapter 2
Release Overview

Release Overview
AirWave 8.2.15.2 is a patch release that introduces new features and provides fixes to known issues.
Refer to these release notes for the most up-to-date information.
These release notes contain the following chapters:
n New Features describes new features in this release.
n Resolved Issues describes the issues we've fixed.
n Known Issues describes known issues.
n Upgrade Instructions describes how to upgrade your software.

Contacting Support
Table 2: Contact Information

Main Site arubanetworks.com

Support Site asp.arubanetworks.com

Airheads Social Forums and Knowledge community.arubanetworks.com

Base

North American Telephone 1-800-943-4526 (Toll Free)

1-408-754-1200

International Telephone arubanetworks.com/support-services/contact-support/

Software Licensing Site lms.arubanetworks.com

End-of-life Information arubanetworks.com/support-services/end-of-life/

Security Incident Response Team (SIRT) Site: arubanetworks.com/support-services/security-bulletins/

Email: [email protected]

AirWave 8.2.15.2 | Release Notes 4

 Chapter 3
New Features in AirWave 8.2.15.2

New Features in AirWave 8.2.15.2

AirWave introduces new features and fixes to issues detected in previous releases. There are no
licensing changes in this release.

For a complete list of supported products and validated firmware versions, refer to the AirWave
8.2.15.2 Supported Infrastructure Devices

Important Notes
n AirWave 8.2.15.2 is the last version that supports CentOS 7 operating system. The EOL date for CentOS
7 was announced and is set to be EOL by 30th June, 2024. For more information, refer to
https://wiki.centos.org/About/Product. Aruba recommends upgrading to AirWave 8.3.0.x, an RHEL-
based AirWave version to receive continued support for product and security updates.
n WMS Offloading feature has not been tested with newer versions of AirWave and ArubaOS.

New Features
Ethernet Port Profiles Default Option Removed
The default option wired-SetMeUp in the Groups > [specific-iap-group] > Instant Config > Assign
wired profiles to Interfaces is now removed from Enet0-port-profile. For more information, see
AirWave Instant Deployment Guide.

New Hardware Support

Following is a list of the new access points and switches supported:
n AP-503 Access Point
n AOS-CX 6200v2 Switch
n AOS-CX 8100 Switch

Support for Assigning USB Wired Port Profiles

The Groups > [specific-iap-group] > Instant Config > Assign wired profiles to Interfaces page now
displays the option to assign wired port profiles to IAPs USB ports. For more information, see AirWave
Instant Deployment Guide.

WebUI VIA Roles

The Clients > VPN Users page now displays VIA roles.

WebUI Support for Max-IPv4 Users and Deny Intra VLAN Traffic
features

AirWave 8.2.15.2 | Release Notes 5

 The Groups > [specific-iap-group] > Instant Config > Networks > Wireless > Advanced Options >
Miscellaneous page now displays a dedicated field to show Max IPv4 users and Deny Intra VLAN traffic.

6 | AirWave 8.2.15.2 | Release Notes

 Chapter 4
Resolved Issues in AirWave 8.2.15.2

Resolved Issues in AirWave 8.2.15.2

This section describes the issues resolved in this release.

Table 3: Resolved Issues in AirWave 8.2.15.2

Reported
Bug ID Description
Version

DE21682 AirWave displayed unencrypted passwords in the Devices > Audit page. AirWave 8.0.6.3

DE35555 The Upstream Device data in the Device Info tab was displayed incorrectly AirWave 8.2.13.1
in the Devices > Monitor page.

DE35667 Nightly backup failed on multiple AirWave Management Platforms randomly. AirWave 8.2.13.0

DE35751 The 802.11 radio counter table did not display any IAP information in the AirWave 8.2.14.1
Devices > Monitor > Radio Statistics page.

DE35851 The kswapd0 service used 100% of the AirWave server resources. AirWave 8.2.14.0

DE35861 AirWave was unable to push configurations to IAPs in template mode. AirWave 8.2.12.1

DE35915 AirWave triggered and displayed false, No Data Processed alerts in the AirWave 8.2.14.1
System > Alerts page.

DE35942 AirWave’s system performance was affected as the /var/log disk space was AirWave 8.2.14.1
DE36070 filled up repeatedly by incorrect Java PID files.

DE35988 AirWave displayed inconsistent client and usage graph information. AirWave 8.2.15.0

DE35996 The Devices > List > Devices List> Export as CSV option did not display AirWave 8.2.15.0
any data in the exported CSV file. However, the data was visible if exported
after 2-3 minutes.

DE36000 The Recent AMP Device Events page randomly displayed devices as Down AirWave 8.2.15.0
and the log file listed the reason for the event as, AP is no longer
associated with the controller. However, the devices are displayed as Up
in intervals of 5 to 6 minutes.

DE36001 The Devices List page displayed incorrect AP models after upgrading to AirWave 8.2.15.0
DE35947 AirWave 8.2.15.0.

DE36006 AirWave did not display the wired PC port information in the Clients page. AirWave 8.2.15.0

DE36014 The user was unable to make configuration changes in the AMP Setup > AirWave 8.2.14.1
Network tab when the 10 gigabyte interface was set to Primary network
interface.

DE36028 All the clients were incorrectly displayed on the top left corner of the AirWave 8.2.15.0
VisualRF page.

AirWave 8.2.15.2 | Release Notes 7

 Reported
Bug ID Description
Version

DE36032 The VisualRF page stopped displaying the last location of the devices even AirWave 8.2.15.0
after updating the page.

DE36051 A client number mismatch was observed between AirWave and controllers. AirWave 8.2.15.1

DE36056 The Clients > Diagnosis page displayed incorrect client details. AirWave 8.2.15.1

DE36061 Users are unable to generate the Network Wide Inventory report. AirWave 8.2.15.1

DE36070 The AirWave’s system performance was affected as the /var/log disk space AirWave 8.2.15.1
DE35942 was filled up repeatedly by incorrect Java PID files.

DE36072 The VisualRF page did not display any information and displayed 5 GHz AP- AirWave 8.2.15.0
515 Instant APs at the top left corner of the Visual RF page.

DE36084 After a successful import of the Ekahau backup, when a user clicked on any AirWave 8.2.15.1
wall of the floorplan, the value was displayed as Unknown.

8 | AirWave 8.2.15.2 | Release Notes

 Chapter 5
Known Issues in AirWave 8.2.15.2

Known Issues in AirWave 8.2.15.2

This section describes the known issues and limitations observed in this release.

Limitation
Following is the limitation observed in this release:

PEM Certificates
When .PEM certificates are uploaded to to be applied for server, web, and captive portal certificates,
they are displayed as Mismatched on all devices.

Known Issues
Following are the known issues observed in this release:

Table 4: Known Issues in AirWave 8.2.15.2

Reported
Bug ID Description
Version

DE36139 The RAPIDS > List may fail to load once the filter option is enabled. AirWave
8.2.12.0

AirWave 8.2.15.2 | Release Notes 9

 Chapter 6
Upgrade Instructions

Upgrade Instructions
This chapter provides the following information to help you with the upgrade process of the AirWave
server:
n Minimum Requirements
n Verify Current CentOS Version
n Upgrade Paths
n Upgrade from AirWave 8.2.9.x or 8.2.10.x with CentOS 6 Migration
n Upgrade from AirWave 8.2.4.3, 8.2.10.x, 8.2.11.x, 8.2.12.x, 8.2.13.x, or 8.2.14.x with CentOS 7

Minimum Requirements
Ensure that you have sufficient disk storage, memory, and relevant hardware or software versions. As
additional features are added to AirWave, increased hardware resources become necessary and
hardware requirements vary by version. For the most recent hardware requirements, refer to the latest
AirWaveServer Sizing Guide.

Verify Current CentOS Version

Before you upgrade, verify the version of CentOS currently running on your AirWave server.

1. From the AirWave command-line interface, enter 8 to select Advanced, then enter 2 to select
Enter Commands.
2. Enter the command $osrel.

The output of this command displays the version of CentOS currently in use. Use this information to
determine your upgrade path.

Upgrade Paths
Your upgrade workflow depends on your current version of AirWave and CentOS.
n To upgrade from AirWave 8.2.9.x or AirWave 8.2.10.x with CentOS 6, follow the steps in Upgrade from
AirWave 8.2.9.x or 8.2.10.x with CentOS 6 Migration .
n To upgrade from AirWave 8.2.4.3, AirWave 8.2.10.x, AirWave 8.2.11.x, AirWave 8.2.12.x, AirWave
8.2.13.x, or AirWave 8.2.14.x with CentOS 7, follow the steps in Upgrade from AirWave 8.2.4.3, 8.2.10.x,
8.2.11.x, 8.2.12.x, 8.2.13.x, or 8.2.14.x with CentOS 7.

If you are upgrading from AirWave 8.2.8.x or earlier version, contact Technical Support for help with a
multiple-step upgrade path.

AirWave 8.2.15.2 | Release Notes 10

 Upgrade from AirWave 8.2.9.x or 8.2.10.x with CentOS 6
Migration
AirWave 8.2.14.x requires an upgrade to CentOS 7. The migration process involves upgrading to
AirWave 8.2.10.1, backing up your data, exporting the backup file, performing a fresh install of AirWave
8.2.10.1 and CentOS 7 on your server, restoring the backup data onto that server, and then upgrading
to AirWave 8.2.14.x.
After you perform this upgrade, follow the steps in Upgrade from AirWave 8.2.4.3, 8.2.10.x, 8.2.11.x,
8.2.12.x, 8.2.13.x, or 8.2.14.x with CentOS 7 to upgrade to AirWave 8.2.15.2.

Upgrade to AirWave 8.2.10.1 before backing up your data. You cannot restore an AirWave 8.2.8.x,
8.2.9.x, or 8.2.10.0 (on CentOS 6) backup on an AMP server running AirWave 8.2.14.x. For more
information on creating backups of your data, refer to the System Pages section of the AirWave User
Guide. For information on performing a fresh installation of AirWave 8.2.14.x, refer to the AirWave
Installation Guide.

Upgrades from AirWave 8.2.8.x, 8.2.9.x, or 8.2.10.0 on CentOS 6 might fail with the following PuTTY
fatal error message: Server unexpectedly closed network connection when your SSH session
becomes unresponsive.
To avoid this issue, change the keep-alive interval to a low setting as follows:
1. Using a terminal console, such as PuTTY, open an SSH connection with the AMP.
2. Enter 30 to 60 seconds for sending null packets between keep-alive messages.

Before You Begin

Prior to migration, navigate to Home > License and save a copy of the license key. AirWave licenses are
associated with the server IP address. All new installations of AirWave have a 90-day grace period for
licenses.
Keep these considerations in mind when working with AirWave licenses:
n If you plan to reuse the same IP address, then apply the license key after you restore the AirWave
8.2.14.x backup.
n If you are planning to migrate data to a new server, work with Aruba support or use the license portal,
to generate the new license in advance, then follow the migration path and apply the new license key.
Keep in mind that you may have to adjust some devices (such as Instant APs and devices that send
AMON or syslog messages to AirWave ) in order for those devices to send updates to the new IP
address.

Step 1: Upgrade to AirWave 8.2.10.1

1. Log in to the AirWave server with the ampadmin user name and password. If you previously
changed the ampadmin user name and password, enter the current credentials.
2. Enter 4 to select System.
a. At the next prompt, enter 1 to select Upgrade, then enter 1 to select
UpgradeAirWaveManagement Software.

11 | AirWave 8.2.15.2 | Release Notes

 b. Select the option for 8.2.10.1.

If the 8.2.10.1 software does not appear in the list of local upgrade versions, select option 2 None
of the Above, then manually enter 8.2.10.1.

c. Enter y to enable AirWave to connect to a proxy server. Or, you can enter N to bypass this step and
go to step on page 12 to download the software. At the next prompt:
n Enter the server address and port number (for example, test.proxy.com and port 22).
n Enter y to enter the proxy user name and password (for example, testuser and password).

d. Enter 1 or 2 to log in to your customer portal with your support user name and password.

e. Follow the on-screen instructions to download the software.

Step 2: Back up your AirWave 8.2.10.x Data

1. Log in to the AirWave server with the ampadmin user name and password. If you previously
changed the ampadmin user name and password, enter the current credentials.
2. Enter 2 to select Backup.
3. Enter 1 to open the Backup menu.
4. Enter 1 to select the Backup Now option.

Step 3: Export the Backup

1. After creating your backup, enter b to return to the previous Backups menu.
2. Enter 5 to open the Users menu options, then enter 3 to add a file transfer user.
3. Enter a user name for the file transfer user, then click Enter. The user name for an AirWave image
file transfer user must be five characters or longer, and contain only lowercase letters and
numbers. To use the default file transfer user name awscp, click Enter without entering a user
name.
4. Enter a password for the file transfer user, then click Enter.The password must be eight
characters or longer, and can contain uppercase and lowercase letters, numbers, and non-
alphanumeric characters. Spaces are not allowed.
5. Enter b to go back to the main CLI menu.
6. Use SCP to connect to your remote repository and move the AirWave 8.2.10.1 backup file from
the AirWave/user directory to a remove server.

Step 4: Migrate to CentOS 7

Perform a fresh installation of AirWave 8.2.10.1 to automatically upgrade CentOS 6.x to CentOS 7.

For more information on installing a new instance of AirWave 8.2.10.1 on your server, refer to the
AirWave 8.2.10.1 Installation Guide, Pre-Installation Checklist.

Step 5: Upload the Backup

Follow one of these steps to upload the backup on the AirWave server:

AirWave 8.2.15.2 | Release Notes Upgrade Instructions | 12

 n If using SCP, enter 1-1 to open the File and Upload File menus. Provide the user name, host, and path
for an SCP server using FIPS-approved encryption.
n If using SFTP, enter 5-3 to open the User and Add File Transfer User menus. Log in from another
system using those credentials, and upload the backup.

Step 6: Restore the Data

Follow these steps to restore the backup on AirWave 8.2.10.1:

1. From the AMP CLI, enter 2-2 to open the Backups and Restore menus.
2. Enter 1 to restore the server from the uploaded backup.

Step 7: Install Certificates

In this step, you will add an SSL certificate, or generate a certificate signing request and install a signed
certificate.
To add the SSL certificate:

1. From the command-line interface, enter 3-4 to open the Configuration and Certificates menus.
2. Enter 1 to open the Add SSL Certificate menu.
3. Follow the prompt to install the SSL certificate on your AMP server. The signed certificate should
be in PKCS12 format with a *.pfx or *.p12 file extension.

To generate a CSR and install the certificate:

1. From the command-line interface, enter 3-4 to open the Configuration and Certificates menus.
2. Enter 2 to open the Generate Certificate Signing Request menu.
3. Follow the prompt to create a CSR that identifies which server will use the certificate.
4. Next, enter b to return to the previous menu,
5. Enter 1-2 to open the Files and Download File menu to download the resulting CSR.
6. Send the CSR to your certificate signer.
7. Once the certificate is signed, upload the certificate to the AirWave 8.2.10.1 server.
n If using SCP, enter 1-1 to open the File and Upload File menus. Provide the user name, host,
and path for an SCP server using FIPS-approved encryption.
n If using SFTP, enter 5-3 to open the User and Add File Transfer User menus. Log in from
another system using those credentials, and upload the backup.

8. From the WebUI, go to Device Setup > Certificates, then click Add to add a trusted root CA
certificate. To add a new certificate, provide the following information:
n Name—Name of the certificate.
n Certificate File—Click Choose File to find the certificate file on your local system, then click
Open.
n Passphrase—Select a password.
n Confirm Passphrase—Retype the passphrase to confirm.
n Format—Select the certificate format from the drop-down list.
n Type—Select the certificate type from the drop-down list.

13 | AirWave 8.2.15.2 | Release Notes

 9. From the 3-4Configuration and Certificates menu, enter 3 to open the Install Signed
Certificate menu.
10. Follow the prompts to install the certificate.

Step 8: Upgrade to Latest AirWave Version

Proceed to Upgrade from AirWave 8.2.4.3, 8.2.10.x, 8.2.11.x, 8.2.12.x, 8.2.13.x, or 8.2.14.x with CentOS 7.

Upgrade from AirWave 8.2.4.3, 8.2.10.x, 8.2.11.x, 8.2.12.x,

8.2.13.x, or 8.2.14.x with CentOS 7
An upgrade from AirWave versions 8.2.4.3, 8.2.10.x, 8.2.11.x, 8.2.12.x, 8.2.13.x, or 8.2.14.x using CentOS
7 is straightforward and does not require a CentOS migration. If you are upgrading from AirWave
versions 8.2.4.3, 8.2.10.x, 8.2.11.x, or 8.2.12.x upgrade to AirWave 8.2.13.x before upgrading to AirWave
8.2.15.2. Use the AMP CLI to install the AirWave 8.2.15.2 upgrade package on your system. If your
network does not allow AirWave to connect to the Internet, you must manually download the software
and upload the software before performing this upgrade.

You can change the existing amprecovery user name by backing up the server, reinstalling the
software, and restoring from the backup. For information about setting up the amprecovery account,
refer to Installing the Software (Phase 2) in the AirWave8.2.15.2 Installation Guide.

Follow these steps to upgrade to AirWave8.2.15.2:

1. Log in to the AirWave server with the ampadmin user name and password. If you subsequently
changed the "ampadmin" user name and password, enter the current credentials.
2. Enter 4 to select System.
a. At the next prompt, enter 1 to select Upgrade.

b. Select the option for 8.2.15.2.

If the 8.2.15.2 software does not appear in the list of local upgrade versions, select option 2 None
of the Above, then manually enter 8.2.15.2.

c. Enter y to enable AirWave to connect to a proxy server. Or, you can enter N to bypass this step and
go to step on page 12 to download the software. At the next prompt:
n Enter the server address and port number (for example, test.proxy.com and port 22).
n Enter y to enter the proxy user name and password (for example, testuser and password).

d. Enter 1 or 2 to log in to your customer portal with your support user name and password.

e. Follow the onscreen instructions to download the software.

Upgrade to AirWave 8.2.15.2 in Aruba Central (on-premises)

Server
If you are performing a fresh installation of AirWave 8.2.15.2 on Aruba Central (on-premises) servers,
interfaces on the Aruba Central (on-premises) server will always be in the following order:

AirWave 8.2.15.2 | Release Notes Upgrade Instructions | 14

 n eth0- eth3 – 1G interfaces
n eth4 and eth5 - 10G interfaces

If you are upgrading from a prior AirWave version to AirWave 8.2.15.2 on Aruba Central (on-premises)
servers, the following message is displayed.

Perform the following steps on Aruba Central (on-premises) server Gen10 server with both 1G and 10G
interfaces only.

1. Run upgrade to AirWave 8.2.15.2.

2. Post upgrade, run intfinorder, reboot, and configure network setup by entering the following
options in AMP CLI:
a. Enter option 8 - Advanced.

b. Enter option 1 - Custom Commands.

c. Enter option 2 - Enter Commands.

d. This will run the enter commands, execute $ intfinorder.

e. Click y when prompted with Do you want to continue (y/N)? : message.

3. Type exit and navigate to the CLI prompt and select option 4 - System and then, select option 4 -
Reboot System to reboot the system.

15 | AirWave 8.2.15.2 | Release Notes

 4. If you lose connection to Aruba Central (on-premises) server post step 3, login to the ILO/console
of the server and navigate to the CLI prompt, and select option 3 - configuration and option 1 -
Configure Network Settings.

5. Select the proper network interface and configure the IP address for your AMP and commit the
changes. The AMP should be reachable with the IP address configured.
This will enable reliable ordering of interfaces in upgrade scenario that is, eth0 - eth3 mapped to
1G interfaces and eth4- eth5 mapped to 10G interfaces at the end. Once interfaces are set in
proper order, future AMP upgrades will be smooth. The $ intfinorder script should be run from
the AMP CLI menu as described above for users using Aruba Central (on-premises) server after
upgrading to AirWave 8.2.15.2 build.

Manually Download the Software

You can manually download the software if your AirWave server cannot access the Internet.

1. Go to the Aruba Support Portal to download the upgrade image. This new portal replaces the
legacy Aruba support site (support.arubanetworks.com), which is currently read-only and will be
deprecated sometime in the future.
2. Click the upgrade package, then click Save and install the file later.

AirWave 8.2.15.2 | Release Notes Upgrade Instructions | 16

 3. Define a user that can transfer AirWave images, and then upload the software:

For security purposes, image file transfer users are automatically removed every night during
nightly maintenance operations.

4. From the AMP command-line interface, with the ampadmin user name and password. If you
subsequently changed the ampadmin user name and password, enter the current admin name
and password.
5. Add a file transfer user. This process varies, depending upon the version of AirWave currently
running on your system.
a. If you are upgrading from AirWave versions 8.2.10.x, 8.2.11.x, 8.2.12.x, 8.2.13.x, or 8.2.14.0, enter 5 to
open the Users menu options, then enter 3 to add a file transfer user.

b. If you are upgrading from AirWave 8.2.9.x, enter 8 to open the Advanced menu options, then enter 7
to add a file transfer user.

6. Enter a user name for the file transfer user, then click Enter. The user name for an AirWave
image file transfer user must be five characters or longer, and contain only lowercase letters and
numbers. To use the default file transfer user name awsftp, click Enter without entering a user
name.
7. Enter a password for the file transfer user, then click Enter.The password must be eight
characters or longer, and can contain uppercase and lowercase letters, numbers, and non-
alphanumeric characters. Spaces are not allowed.
8. Enter b to go back to the main CLI menu.
9. Use SFTP to connect to your remote repository and upload the AirWave8.2.15.2 upgrade file from
the remote server into the AirWave/user directory.

17 | AirWave 8.2.15.2 | Release Notes