AOS 10.4.0.

1
Release Notes
Copyright Information
© Copyright 2023 Hewlett Packard Enterprise Development LP.
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.
 Contents

Contents

Contents 3
Revision History 4
Release Overview 5
Terminology Change 5
Contacting Support 6

What's New 7
New Features 7
Enhancements 7
Supported Hardware Platforms 8
Supported Aruba APs 8
Supported Aruba Gateways 9

End-of-Support 9
Regulatory Updates 10
Resolved Issues 11
Known Issues 15
Upgrading to AOS 10.x 16
Important Points to Remember 16
Memory Requirements 17
Backing up Critical Data 17
Upgrading a Single Device or Multiple Devices 18
Upgrading Devices using Upgrade All Option 19

AOS 10.4.0.1 | Release Notes 3

 Chapter 1
Revision History

Revision History
The following table provides the revision history of this document.

Table 1: Revision History

Revision Change Description

Revision 01 Initial release.

AOS 10.4.0.1 | Release Notes 4

 Chapter 2
Release Overview

Release Overview
This AOS 10.4.0.1 release notes includes the following topics:

n What's New
n Supported Hardware Platforms
n Regulatory Updates
n Resolved Issues
n Known Issues

For the list of terms, refer Glossary.

Terminology Change
As part of advancing HPE's commitment to racial justice, we are taking a much-needed step in
overhauling HPE engineering terminology to reflect our belief system of diversity and inclusion. Some
legacy products and publications may continue to include terminology that seemingly evokes bias
against specific groups of people. Such content is not representative of our HPE culture and moving
forward, Aruba will replace racially insensitive terms and instead use the following new language:

Usage Old Language New Language

Campus Access Points + Master-Slave Conductor-Member

Controllers

Instant Access Points Master-Slave Conductor-Member

Switch Stack Master-Slave Conductor-Member

Wireless LAN Controller Mobility Master Mobility Conductor

Firewall Configuration Blacklist, Whitelist Denylist, Allowlist

Types of Hackers Black Hat, White Hat Unethical, Ethical

AOS 10.4.0.1 | Release Notes 5

 Contacting Support
Table 2: Contact Information

Main Site arubanetworks.com

Support Site https://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 Site: arubanetworks.com/support-services/security-bulletins/

Email: [email protected]

6 | Release Overview AOS 10.4.0.1 | Release Notes

 Chapter 3
What's New

What's New
This chapter describes the new features and enhancements introduced in AOS 10.4.0.1. For more
information, see Aruba Central Help Center.

New Features
There are no new features introduced in this release.

Enhancements
There are no new enhancements introduced in this release.

AOS 10.4.0.1 | Release Notes 7

 Chapter 4
Supported Hardware Platforms

Supported Hardware Platforms

This chapter lists the hardware that is supported in this release.

Supported Aruba APs

The following table displays the supported Aruba AP models:

Table 3: Supported APs

AP Family AP Model

300 Series AP-303, AP-303H, AP-303P, AP-304, AP-305

310 Series AP-314, AP-315, AP-318

320 Series AP-324, AP-325

NOTE: The 320 Series AP models with 256 MB of SDRAM, manufactured

between August 2015 and January 2016, are not supported with AOS 10.x.
These 320 Series AP models have a serial number that begins with DD (for
example, DD0003824).

330 Series AP-334, AP-335

340 Series AP-344, AP-345

360 Series AP-365, AP-367

370 Series AP-374, AP-375, AP-375EX, AP-375ATEX, AP-377, AP-377EX, AP-387

500 Series AP-503H, AP-504, AP-505, AP-505H

510 Series AP-514, AP-515, AP-518

530 Series AP-534, AP-535

550 Series AP-555

560 Series AP-565, AP-565EX, AP-567, AP-567EX

570 Series AP-574, AP-575, AP-575EX, AP-577, AP-577EX

580 Series AP-584, AP-585, AP-585EX, AP-587, AP-587EX

630 Series AP-635

650 Series AP-655

AOS 10.4.0.1 | Release Notes 8

 Supported Aruba Gateways
The following table displays the supported Aruba Gateway models:

Table 4: Supported Aruba Gateways

Gateway Family Gateway Model

7000 Series 7005, 7008, 7010, 7024, 7030

7200 Series 7205, 7210, 7220, 7240XM, 7280

9000 Series 9004, 9004-LTE, 9012

9200 Series 9240

End-of-Support
This section provides information on the Aruba products that are not supported for a particular release.
AOS 10.4.x.x is the last release that supports the following AP platforms:

n 320 Series
n 330 Series
n 340 Series
n AP-387

9 | End-of-Support AOS 10.4.0.1 | Release Notes

 Chapter 5
Regulatory Updates

Regulatory Updates
There are no regulatory updates in this release.

AOS 10.4.0.1 | Release Notes 10

 Chapter 6
Resolved Issues

Resolved Issues
This chapter describes the resolved issues in this release.

Table 5: Resolved Issues in AOS 10.4.0.1

Reported
Bug ID Description
Version

AOS-156661 The authentication survivability feature did not work as expected AOS 10.3.1.0
AOS-224890 when the uplink was down. This issue occurred because the
Survival Server was not used when the server was unreachable.
The fix ensures that the Survival server is used when network is
unreachable. This issue was observed on devices running AOS
10.3.1.0 or later versions.

AOS-218161 The output of the show running-config command displayed the AOS 10.4.0.0
error message, An internal system error has occurred at file
amapi_common.c function deserializeCommandList line 940
error sxdr_read_u32_safe &numEntries failed.
The fix ensures that the output of the command does not display
the error message.

AOS-231019 Some Microbranch APs failed to reconnect after an LTE outage. AOS 10.3.1.0
AOS-232063 The output of the show cell status command was missing
information.
The fix ensures that the APs work as expected.

AOS-234783 Some AP-505H access points got flooded with wlc_offload AOS 10.3.1.0
PhyRxSts Circular Buffer Control logs and crashed
unexpectedly. The log files listed the reason for the event as
Kernel panic - not syncing: Ktrace core monitor: cpu0 hung
for 45 seconds, hung cpu count: 1.
The fix ensures that the APs work as expected.

AOS-235720 The entries of AWDL protocol flooded the IDS table due to which AOS 10.3.1.0
IDS was not able to detect threats until the AWDL entries aged
out.
The fix ensures that the AWDL entries do not reach the IDS table.
This issue was observed in Aruba gateways running AOS 10.3.1.0
or later versions.

AOS-237869 Some AP-635 access points displayed the error message, AOS 10.4.0.0
Unexpected stm (Station management) runtime error at
stm_sysctl_read_param, 13937, Error opening
/proc/sys/net/aruba103/max_clients : No such file or
directory. This issue occurred because max-client sysctl path was
incorrect.
The fix ensures that max-clients is read correctly by stm_sysctl_
read_param.

AOS-238571 Radproxy process crashed repeatedly when more than 12 VRRP AOS 10.3.1.1
IPs were configured. This issue occurred because amon_user_
updates array was overwritten by vrrp_master_ip_pool.

AOS 10.4.0.1 | Release Notes 11

 Reported
Bug ID Description
Version

The fix prevents memory corruption to the next variable, in this

case—amon_user_updates. Additionally, debugs are added to
capture logs in case more than 12 entries are sent through the
GSM channel.

AOS-238656 Some APs crashed and rebooted unexpectedly with the reason for AOS 10.3.1.0
AOS-239832 the event as: Kernel panic - not syncing: Take care of the
AOS-240893 TARGET ASSERT first. The crash-info showed that AP firmware
was asserted at ratectrl.c:999.
The fix ensures that the APs work as expected. This issue was
observed on AP-535 access points running AOS 10.3.1.0 and AOS
10.3.1.1 versions.

AOS-238808 Some Microbranch APs were unable to form mesh link at 60 GHz AOS 10.3.1.0
and were denylisted.
The fix ensures that the 60 GHz connection is formed by default.
This issue was observed on AP-387 access points.

AOS-239321 Some APs crashed and rebooted unexpectedly with the reason for AOS 10.4.0.0
AOS-240598 the event as: kernel panic: Take care of the TARGET ASSERT
first. The crash-info showed that AP firmware was asserted at
whal_recv.c:1656.
The fix ensures that the APs work as expected. This issue was
observed on AP-635 access points.

AOS-239328 Some APs crashed and rebooted unexpectedly with the reason for AOS 10.4.0.0
AOS-239828 the event as: Reboot caused by kernel panic: Take care of the
TARGET ASSERT first. The crash-info showed that AP firmware
was asserted at whal_recv.c:1656.
The fix ensures that the APs work as expected. This issue was
observed on AP-535 access points.

AOS-239341 Some clients were unable to connect to AP-345 access points AOS 10.3.1.0
running AOS 10.3.1.0 or later versions.
The fix ensures that the APs work as expected.

AOS-239662 Some clients experienced issues with audio transmission during AOS 10.4.0.0
Skype and Microsoft Teams calls.
The fix ensures that the clients do not experience issues with
audio transmission.

AOS-240780 The PI flag of the route-cache entry was not cleared for the AP AOS 10.4.0.0
tunnel after IP compression was disabled in Aruba Central or the
clear crypto ipsec sa command was issued, and the tunnels
were brought down.
The fix ensures that the route-cache entries are updated when the
tunnels are brought down.

AOS-240901 When the host name for AP was changed, '\n' was appended to AOS 10.4.0.0
the host name in the discover packet due to which the DHCP
server could not create, or update the record on the DNS Server.
The fix ensures that a newline character is not appended when
the host name is changed.

AOS-240920 fpapps crashed randomly when querying an ifMIB OID with AOS 10.3.1.0
unknown index value using SNMP.

12 | Resolved Issues AOS 10.4.0.1 | Release Notes

 Reported
Bug ID Description
Version

The fix ensures that fappps does not crash when an invalid index
value is used.

AOS-240926 Some Microbranch APs crashed and rebooted unexpectedly. The AOS 10.3.1.0
log files listed the reason for the event as: kernel panic: Fatal
exception in interrupt (asap_mcast_mld_snoop+0x27c/0x3f8).
The fix ensures that the APs work as expected. This issue was
observed on access points running AOS 10.3.1.0 or later versions

AOS-241197 APs that worked as mesh points generated sapd core during boot AOS 10.4.0.0
up with JP3 country code.
The fix ensures that AP-reboot does not generate sapd core
under such condition. This issue was observed in AP-575 access
points.

AOS-241202 A 100% packet loss was observed for SLA traffic on Zscaler tunnel AOS 10.3.1.3
on Branch Gateway.
The fix ensures that the gateways work as expected when SLA is
configured for the Zscaler tunnels.

AOS-241203 High memory utilization was observed on some APs. This issue AOS 10.3.1.3
AOS-242599 occurred because the AWC process was consuming high memory.
The fix ensures that the APs work as expected.

AOS-241395 Some Microbranch APs repeatedly formed a connection with PAN AOS 10.4.0.0
firewall despite there being no user connected to the APs. This
issue occurred because the length of the API key sent by PAN
exceeded the buffer limit for the API key on the AP.
The fix extends the PAN API key buffer limit to 512 bytes.

AOS-241448 A 100% packet loss was observed for cloud-security probes on AOS 10.3.1.3
Branch Gateway. This issue occurred when DNS address of the
new URI changed at a later time and the Gateways did not re-
resolve the URI to get the new IP address.
The fix ensures that the gateways now re-resolve the Probe URI
periodically.

AOS-241550 Multiple AP-535 access points crashed unexpectedly with Kernel AOS 10.3.1.0
panic error. The log files listed the reason for the event as: Kernel
panic - not syncing: Take care of the TARGET ASSERT at ru_
allocator.c:3166 Assertion (((rt_tbl))->info[((rix))].phy ==
WHAL_MOD_IEEE80211_T_HE_20.
The fix ensures that the APs work as expected. This issue was
observed in AP-535 access points running AOS 10.3.1.0 and AOS
10.3.1.1 versions.

AOS-241717 Some APs reported high memory utilization due to which clients AOS 10.4.0.0
AOS-242136 were unable to connect to the APs. This issue occurred because
the received IPv6 multicast RA packets were flooded to all SSIDs
when:
n unicast-ipv6-ra was enabled in the first SSID and disabled in
another SSID
n The first SSID did not have any active clients and another SSID
had active clients

AOS 10.4.0.1 | Release Notes Resolved Issues | 13

 Reported
Bug ID Description
Version

The fix ensures that memory leak does not occur and APs work as
expected.

AOS-241757 The Discover packets sent from the client were not relayed to the ArubaOS 8.7.0.0-
DHCP server through the IPSEC tunnel. This issue occurred
2.3.0.8
because the destination id sent to the datapath was 0 which
resulted in the removal of CP flag from datapath. Hence, packets
were not sent from datapath to control plane for that VLAN.
The fix ensures that the destination id sent to the datapath is not
0. This issue was observed on Aruba9004 Branch Gateways
running ArubaOS 8.7.0.0-2.3.0.8 version.

AOS-242012 Under certain circumstances, the show wan ip-sla-stats AOS 10.3.1.4
command did not display all the applicable tunnels. This issue
occurred because the VLAN ID was not updated correctly upon
uplink update.
The fix ensures that the correct VLAN ID is sent to the policymgr
and HCM modules.

AOS-242017 The peer-ip "I" route is not updated when peer-ip is changed AOS 10.3.1.4
through an update from Aruba Central. This issue occurred
because FPAPPS and L3d does not support spontaneous IP
change for gateways.
The fix ensures that FPAPPS and L3d detects gateway IP change
spontaneously.

AOS-242091 The Policy Manager module crashed on Branch Gateway running AOS 10.3.1.4
AOS 10.3.1.4. This issue occurred because an empty index in the
NHL (caused by deletion of an existing nexthop) was not handled
correctly while publishing the IPSLA results for the nexthops.
The fix ensures that:
n The correct nexthop is found using the nexthop type when an
existing nexthop has to be deleted in the NHL.
n The empty index in the NHL is handled correctly while
publishing the IPSLA results for the nexthops.

AOS-242346 In overlay mode, DHCP request was not forwarded to the gateway AOS 10.4.0.0
AOS-243055 when associated to 2.4/5 GHz OWE BSSID.
The fix ensures that the gateways work as expected.

AOS-242397 Some APs redirected the client to a placeholder page configured AOS 10.4.0.0
in the external captive portal profile instead of the URL received
through VSA. This issue occurred when the client roamed between
multiple APs.
The fix ensures that the VSA value is sent to the new AP during
roaming.

AOS-242473 Azure Virtual Gateway failed to resolve DNS and could not reach AOS 10.4.0.0
Aruba Central following an upgrade to AOS 10.4.0.0. This issue
occurred because of incorrect route and firewall rules that were
attached to mgmt interface to prevent unwanted traffic.
The fix ensures that the DNS resolution works correctly on Azure
Virtual Gateways.

14 | Resolved Issues AOS 10.4.0.1 | Release Notes

 Chapter 7
Known Issues

Known Issues
This chapter describes the known issues in this release.

Table 6: Known Issues in AOS 10.4.0.1

Reported
Bug ID Description
Version

AOS-238397 User-role policies are not applied on user IPs generated by static AOS 10.3.1.1
Network Address Translation (NAT).
This issue occurs because the Access Control List (ACL) is applied
only if the pre-NAT IP is a user IP, and is not applied if the post-
NAT IP is a user IP. This issue is observed in managed devices
running AOS 10.3.1.1 version.

AOS-239309 Client throughput does not exceed 200 Mbps when the APs are in AOS 10.3.1.2
Production group. This issue occurs when url-visibility is enabled
but dpi is not enabled.
Workaround: If url-visibility is enabled, then enable dpi also.

AOS-240396 The CLI output of the show clients debug command shows an AOS 10.3.1.2
incorrect (duplicate) IPv6 address for different clients.

AOS-242470 The PBR forwarding action—redirect to ipsec-map, is not AOS 10.3.1.3

working when traffic is initiated from the DC side.
Workaround: Use PBR with nexthop-list configured with ipsec-
map nexthop(s).

AOS-242507 Gateway does not use Branch-HA peer-learned dns-server for CP AOS 10.3.1.4
traffic, even when Wired uplink is out of service.

AOS-242528 Floorplans are not showing in multiple sites in the Aruba Central AOS 10.3.0.0
dashboard.
This issue occurs because of a high number of DHCP requests
sent for the same clients within a few seconds.

AOS-242688 Aruba 9004-LTE Gateway device reboots multiple times with the AOS 10.3.1.4
reason Kernel Panic (Intent:cause: 86:50).

AOS-242749 Some AP-515 access points running AOS 10.3.1.3 version stop AOS 10.3.1.3
broadcasting all the tunnel SSIDs.

AOS-242781 Some APs cannot connect to Aruba Central. The log files list the AOS 10.3.1.2
reason for the event as: Failed to create signature TPM.

AOS-242873 Tunnel for Microbranch APs to VPNC goes down randomly. AOS 10.3.1.1
Workaround: Reboot the VPNC.

AOS-243283 Some Aruba Branch Gateways are unable to pass traffic through AOS 10.3.1.4
the IPSEC tunnel to Zscaler.

AOS 10.4.0.1 | Release Notes 15

 Chapter 8
Upgrading to AOS 10.x

Upgrading to AOS 10.x

This section describes the procedure to upgrade AOS 10.x devices.

This section only applies to devices that are running AOS 10.x. If your device is running ArubaOS 8.x, you will have
to first migrate to AOS 10.x either manually or as part of the Aruba Central Firmware Compliance Policy, before
attempting an upgrade.

This chapter includes the following topics:

n Important Points to Remember

n Memory Requirements
n Backing up Critical Data
n Upgrading a Single Device or Multiple Devices
n Upgrading Devices using Upgrade All Option

Important Points to Remember

To upgrade your Gateway or AP:

n Schedule the upgrade during a maintenance window and notify your community of the planned
upgrade. This prevents users from being surprised by a brief wireless network outage during the
upgrade. These steps are not required if the upgrade type is a live upgrade.
n Avoid making any changes to your network, such as configuration changes, hardware upgrades, or
changes to the rest of the network during the upgrade. This simplifies troubleshooting.
n Know your network and verify the state of the network by answering the following questions:
o How many Gateways and APs are present in the group you are upgrading?
To view the number of devices in each group, complete the following steps in Aruba Central:
1. In the Aruba Central app, set the filter to an AP group.
2. Under Manage, click Devices.
By default, the Access Points device page is displayed.
o What version of AOS runs on your Gateways or APs?
o Ensure all the devices are assigned a license such as foundation or advanced. If the upgrade type
is live upgrade, ensure all the APs are assigned with an advanced license. For more information,
see Overview of Aruba Central Foundation and Advanced Licenses.
n Resolve any existing issues (consistent or intermittent) before you upgrade.
n Ensure the devices are reachable to public networks and the uplinks have sufficient bandwidth to
download the image from the Aruba Activate Server.
n Multiversion is supported within the Gateway cluster. The Gateways and the APs can be in different
AOS versions.

AOS 10.4.0.1 | Release Notes 16

 Memory Requirements
All Aruba Gateways store critical configuration data on an onboard compact flash memory module.
Ensure that there is always free flash space on the Gateways. Loading multiple large files such as JPEG
images for RF Plan can consume flash space quickly. Following are best practices for memory
management:

n Ensure sufficient memory and flash space is available in the Gateways before proceeding with the
upgrade.
n Execute the show memory command to identify the available free memory.
n Execute the show storage command to identify the available flash space.
n If the output of the show storage command indicates that there is insufficient flash memory, free
some used memory. Copy any log files, crash data, or flash backups from your Gateways to a desired
location. Delete the following files from the APs to free some memory:
o Crash data: Execute the tar crash command to compress crash files to a file named crash.tar.
Use the procedures described in Backing up Critical Data to copy the crash.tar file to an external
server. Execute the tar clean crash command to delete the file from the Gateway.
o Flash backups: Use the procedures described in Backing up Critical Data to back up the flash
directory to a file named flash.tar.gz. Execute the tar clean flash command to delete the file
from the Gateway.
o Log files: Execute the tar logs command to compress log files to a file named logs.tar. Use the
procedures described in Backing up Critical Data to copy the logs.tar file to an external server.
Execute the tar clean logs command to delete the file from the Gateway.
n The show commands are available under Analyze > Tool > Commands section of Aruba Central.

The device CLI can be accessed from Aruba Central. Select the device, Overview > Summary > Actions >
Console.

Deleting a File
You can delete a file using the following command:
(host) #delete filename <filename>

Backing up Critical Data

It is important to frequently back up all critical configuration data and files on the flash memory to an
external server or mass storage device. You should include the following files in these frequent
backups:

n Configuration data
n WMS database
n Local user database
n Licensing database
n Custom captive portal pages
n x.509 certificates
n Log files
n Flash backup

17 | Upgrading to AOS 10.x AOS 10.4.0.1 | Release Notes

 Backing up and Restoring Flash Memory
You can backup and restore the flash memory using the CLI.

The device CLI can be accessed from Aruba Central. Select the device, Overview > Summary > Actions >
Console.

The following steps describe how to back up and restore the flash memory:

1. Execute the following command to back up the contents of the flash memory to the
flashbackup.tar.gz file.
(host) #backup flash
Please wait while we take the flash backup.......
File flashbackup.tar.gz created successfully on flash.
Please copy it out of the controller and delete it when done.
2. Execute either of the following commands to transfer the flash backup file to an external server
or storage device.
(host) #copy flash: flashbackup.tar.gz ftp: <ftphost> <ftpuser> <remote-directory>
<destinationfilename> <ftpuserpassword>

(host) #copy flash: flashbackup.tar.gz usb: partition <partition-number>

<destinationfilename>
You can transfer the flash backup file from the external server or storage device to the flash
memory by executing either of the following commands:
(host) #copy tftp: <tftphost> <filename> flash: flashbackup.tar.gz

(host) #copy usb: partition <partition-number> <filename> flash:

flashbackup.tar.gz
3. Execute the following command to untar and extract the flashbackup.tar.gz file to the flash
memory.
(host) #restore flash
Please wait while we restore the flash backup........
Flash restored successfully.
Please reload (reboot) the controller for the new files to take effect.

Upgrading a Single Device or Multiple Devices

To upgrade a single device or multiple devices, complete the following steps:

1. In the Aruba Central app, select one of the following options:

a. To select a group, site or global in the filter:
n Set the filter to one of the options under Group or Sites. For all devices, set the filter to

Global. The dashboard context for the selected filter is displayed.

n Under Maintain, click Firmware.
n Select one or more devices from the device list and click the Upgrade icon at the bottom
of the page or hover over one of the selected device and click the Upgrade icon. The
Upgrade <Device> Firmware pop-up window opens.
b. To select a device in the filter:
n Set the filter to Global.

n Under Manage, click Devices, and then click Access Points, Switches, or Gateways. A list
of devices is displayed.

AOS 10.4.0.1 | Release Notes Upgrading to AOS 10.x | 18

 n Click a device listed under Device Name. The dashboard context for the device is
displayed.
n Under Maintain, click Firmware and click Upgrade in the Firmware Details window. The
Upgrade <Device> Firmware pop-up window opens.

2. In the Upgrade <Device> Firmware pop-up window, select the desired firmware version.
You can either select a recommended version or manually choose a specific firmware version.

n To obtain custom build details, contact Aruba Technical Support.

n The recommended firmware versions can be different for different devices and depends
on the device model and software architecture.

3. Select one of the following radio buttons to specify if the compliance must be carried out
immediately or at a later date and time:
n Now—Allows you to set the compliance to be carried out immediately.
n Later Date—Allows you to set the compliance to be carried out at the later date and time.
Select a specific time zone from the Select Zone drop-down options to schedule the firmware
compliance in a specific time zone.

Steps 4 and 5 are applicable only if you are upgrading Aruba Switches, Aruba CX Switches, and
Branch Gateways. If you are upgrading an Access Point, proceed to step 6.

4. From the Install On drop-down, select any one of the following partition options:
n Primary partition—Select this if you want to install the firmware version in the primary
partition.
n Secondary partition— Select this if you want to install the firmware version in the secondary
partition.
5. Select the check box if you want Aruba Central to automatically reboot after device upgrade.
6. Click Upgrade. The device downloads the image from the server, saves it to flash, and reboots.
Depending on the progress and success of the upgrade, one of the following messages is
displayed:
n Upgrading—While image upgrade is in progress.
n Upgrade failed—When the upgrade fails.
7. If the upgrade fails, retry upgrading your device.

After upgrading a switch, click Reboot.

Upgrading Devices using Upgrade All Option

To upgrade multiple devices using the Upgrade All option, complete the following steps:

1. In the Aruba Central app, set the filter to one of the options under Group or Sites.
For all devices, set the filter to Global. The dashboard context for the selected filter is displayed.

19 | Upgrading to AOS 10.x AOS 10.4.0.1 | Release Notes

 2. Under Maintain, click Firmware. 
The firmware dashboard for Access Points is displayed by default.
3. Click Upgrade All.
The Upgrade <Device> Firmware pop-up window opens.
4. In the Upgrade <Device> Firmware pop-up window, select the specific site or multiple sites
from the Sites drop-down list.
This option is available only at the global context.
5. Select the desired firmware version (for Access points and Gateways) and AOS-S firmware version
and CX firmware version (for Aruba Switches and Aruba CX Switches) from their respective drop-
down list.
You can either select a recommended version or manually choose a specific firmware version.

n To obtain custom build details, contact Aruba Technical Support.

n The recommended firmware versions can be different for different devices and depends on
the device model and software architecture.

6. In the Upgrade Type, select one of the following options:

n Standard
n Live

n Live upgrade is only supported for APs and gateways in cluster mode.
n Live upgrade operation requires the devices to be assigned with Advanced license. On the
group dashboard, live upgrade is not initiated for the group if any of the device within the
group is assigned with Foundation license. Aruba Central recommends that you create a
group with devices that are assigned with Advanced license for seamless operation.

7. Select one of the following radio buttons to specify if the compliance must be carried out
immediately or at a later date and time:
n Now—Allows you to set the compliance to be carried out immediately.
n Later Date—Allows you to set the compliance to be carried out at the later date and time.
Select a specific time zone from the Select Zone drop-down options to schedule the firmware
compliance in a specific time zone.

Steps 8 and 9 are applicable only if you are upgrading Aruba Switches, Aruba CX Switches, and
Branch Gateways. If you are upgrading an Access Point, proceed to step 10.

8. From the Install On drop-down, select any one of the following partition options:
n Primary partition—Select this if you want to install the firmware version in the primary
partition.
n Secondary partition— Select this if you want to install the firmware version in the secondary
partition.

AOS 10.4.0.1 | Release Notes Upgrading to AOS 10.x | 20

 9. Select the check box if you want Aruba Central to automatically reboot after device upgrade..

The Install On drop-down option and auto reboot check box option is available only for Aruba
Switches, Aruba CX Switches, and Branch Gateways.

10. Click Upgrade.

The device downloads the image from the server, saves it to flash, and reboots. Depending on
the progress and success of the upgrade, one of the following messages is displayed:
n Upgrading—While image upgrade is in progress.
n Upgrade failed—When the upgrade fails.
11. If the upgrade fails, retry upgrading your device.

After upgrading a switch, click Reboot.

21 | Upgrading to AOS 10.x AOS 10.4.0.1 | Release Notes