ArubaOS 8.6.0.

21 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
Related Documents 5
Supported Browsers 5
Terminology Change 5
Contacting Support 6

What's New 7
New Features and Enhancements 7

Supported Platforms 8
Mobility Master Platforms 8
Mobility Controller Platforms 8
AP Platforms 8

Regulatory Updates 11
Resolved Issues 12
Known Issues 22
Limitation 22
Known Issues 22

Upgrade Procedure 36
Important Points to Remember 36
Memory Requirements 37
Backing up Critical Data 37
Upgrading ArubaOS 38
Verifying the ArubaOS Upgrade 40
Downgrading ArubaOS 41
Before Calling Technical Support 43

ArubaOS 8.6.0.21 Release Notes | 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.

ArubaOS 8.6.0.21 Release Notes | Release Notes 4

 Chapter 2
Release Overview

Release Overview
This ArubaOS release notes includes the following topics:

n New Features and Enhancements

n Supported Platforms
n Regulatory Updates
n Resolved Issues
n Known Issues and Limitations
n Upgrade Procedure

For a list of terms, refer Glossary.

Related Documents
The following guides are part of the complete documentation for the Aruba user-centric network:
n ArubaOS Getting Started Guide
n ArubaOS User Guide
n ArubaOS CLI Reference Guide
n ArubaOS API Guide
n Aruba Mobility Master Licensing Guide
n Aruba Virtual Appliance Installation Guide
n Aruba AP Software Quick Start Guide

Supported Browsers
The following browsers are officially supported for use with the ArubaOS WebUI:

Web Browser Operating System

Microsoft Edge (Microsoft Edge 92.0.902.62 and n Windows 10 or later

Microsoft EdgeHTML 18.19041) or later n macOS

Firefox 107.0.1 or later n Windows 10 or later

n macOS

Apple Safari 15.4 (17613.1.17.1.13) or later nmacOS

Google Chrome 108.0.5359.71 or later n Windows 10 or later

n macOS

Terminology Change

ArubaOS 8.6.0.21 Release Notes | Release Notes 5

 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

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 ArubaOS 8.6.0.21 Release Notes | Release Notes

 Chapter 3
What's New

What's New
This chapter describes the features, enhancements, and behavioral changes introduced in this release.

New Features and Enhancements

This topic describes the features and enhancements introduced in this release.

Enhancements to show stm perf-history Command

The show stm perf-history command has been modified for a better experience. Changes include:

n Default tracking set to 5-minute snapshots for the last 24 hours for better support.
n Addition of new interval and duration CLI keywords to control the output row interval in minutes
and the number of hours that the total output covers.
n A new A2C column that displays the counts of received Up/Down/Deny List events, the Up conversion
rate, and the number of STA (RE)ASSOC-REQ retries received.

New Notification in the Controller WebUI for Live Upgrade

Live upgrades on the controller might fail if RAPs are included in the network. To avoid this problem, the
upgrade controller will now display a message on the WebUI to inform the administrator about the
presence of RAPs in the network and the potential limitations.

Support for Suite-B GCM256 Connectivity for MD-VPCN Connection

When it is Managed by Mobility Master
The ipsec-factory cert command now supports suite-b gcm128 and gcm256 and it can be configured
using vpnip command. Similarly, using masterip command, suite-b gcm128 and gcm256 can be
configured in both ipsec-custom-cert as well as ipsec-factory cert.

ArubaOS 8.6.0.21 Release Notes | Release Notes 7

 Chapter 4
Supported Platforms

Supported Platforms
This chapter describes the platforms supported in this release.

Mobility Master Platforms

The following table displays the Mobility Master platforms that are supported in this release:

Table 3: Supported Mobility Master Platforms in ArubaOS 8.6.0.21

Mobility Master
Mobility Master Model
Family

Hardware Mobility MM-HW-1K, MM-HW-5K, MM-HW-10K

Master

Virtual Mobility MM-VA-50, MM-VA-500, MM-VA-1K, MM-VA-5K, MM-VA-10K

Master

Mobility Controller Platforms

The following table displays the Mobility Controller platforms that are supported in this release:

Table 4: Supported Mobility Controller Platforms in ArubaOS 8.6.0.21

Mobility Controller Family Mobility Controller Model

7000 Series Hardware Mobility Controllers 7005, 7008, 7010, 7024, 7030

7200 Series Hardware Mobility Controllers 7205, 7210, 7220, 7240, 7240XM, 7280

9000 Series Hardware Mobility Controllers 9004

MC-VA-xxx Virtual Mobility Controllers MC-VA-50, MC-VA-250, MC-VA-1K

AP Platforms
The following table displays the AP platforms that are supported in this release:

Table 5: Supported AP Platforms in ArubaOS 8.6.0.21

AP Family AP Model

100 Series AP-104, AP-105

103 Series AP-103

ArubaOS 8.6.0.21 Release Notes | Release Notes 8

 Table 5: Supported AP Platforms in ArubaOS 8.6.0.21

AP Family AP Model

110 Series AP-114, AP-115

130 Series AP-134, AP-135

170 Series AP-175AC, AP-175AC-F1, AP-175DC, AP-175DC-F1, AP-175P, AP-175P-F1

200 Series AP-204, AP-205

203H Series AP-203H

205H Series AP-205H

207 Series AP-207

203R Series AP-203R, AP-203RP

210 Series AP-214, AP-215

220 Series AP-224, AP-225

228 Series AP-228

270 Series AP-274, AP-275, AP-277

300 Series AP-304, AP-305

303 Series AP-303, AP-303P

303H Series AP-303H

310 Series AP-314, AP-315

318 Series AP-318

320 Series AP-324, AP-325

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-377

AP-387 AP-387

500 Series AP-504, AP-505

510 Series AP-514, AP-515

530 Series AP-534, AP-535

550 Series AP-555

9 | Supported Platforms ArubaOS 8.6.0.21 Release Notes | Release Notes

 Table 5: Supported AP Platforms in ArubaOS 8.6.0.21

AP Family AP Model

RAP 3 Series RAP-3WN, RAP-3WNP

RAP 100 Series RAP-108, RAP-109

RAP 155 Series RAP-155, RAP-155P

ArubaOS 8.6.0.21 Release Notes | Release Notes Supported Platforms | 10

 Chapter 5
Regulatory Updates

Regulatory Updates
This chapter contains the Downloadable Regulatory Table (DRT) file version introduced in this release.
Periodic regulatory changes may require modifications to the list of channels supported by an AP. For a
complete list of channels supported by an AP using a specific country domain, access the controller
Command Line Interface (CLI) and execute the show ap allowed-channels country-code <country-
code> ap-type <ap-model> command.
For a complete list of countries and the regulatory domains in which the APs are certified for operation,
refer to the Downloadable Regulatory Table or the DRT Release Notes at
https://asp.arubanetworks.com/.
The following DRT file version is part of this release:
n DRT-1.0_86370

ArubaOS 8.6.0.21 Release Notes | Release Notes 11

 Chapter 6
Resolved Issues

Resolved Issues
The following issues are resolved in this release.

Table 6: Resolved Issues in ArubaOS 8.6.0.21

Reported
New Bug ID Description
Version

AOS-156661 The authentication survivability feature did not work as expected when ArubaOS 8.2.2.2
AOS-224890 the uplink was down. The fix ensures that the feature works as
expected. This issue was observed in managed devices running
ArubaOS 8.2.2.2 or later versions.

AOS-201042 A large number of packet drops were observed in a few APs. This issue ArubaOS 8.3.0.6
occurred because the AP SAP MTU datapath tunnel was set to 1514. The
fix ensures that the packets are not dropped. This issue was observed in
APs running ArubaOS 8.3.0.6 or later versions.

AOS-207080 The output of the show ap active and show ap bss-table commands ArubaOS 8.6.0.4
AOS-236501 incorrectly displayed the radio type as high efficiency enabled for non-
802.1X APs. This issue occurred when:
n Clients were connected in bridge mode.
n The managed devices act as User Anchor Controllers (UAC).
The fix ensures that the commands display the correct radio type for
non-802.1X APs. This issue was observed in managed devices ArubaOS
8.6.0.4 or later versions in a cluster setup.

AOS-209093 Some managed devices running ArubaOS 8.6.0.18 or later versions ArubaOS 8.6.0.18
AOS-210452 generated multiple AMON receiver errors. The fix ensures that the
AOS-228137 managed devices work as expected.
AOS-237034

AOS-214203 Some AP-515 access points running ArubaOS 8.6.1.7 or later versions ArubaOS 8.6.0.17
AOS-238450 crashed and rebooted unexpectedly. The log files listed the reason for
the event as BadAddr:68637469777348 PC:asap_get_acl_
name+0x28/0x1c0 [asap_mod] Warm-reset. The fix ensures that the
APs work as expected.

AOS-214531 The output of the show ap bss-table command displayed an incorrect ArubaOS 8.7.1.8
AOS-233154 channel, -36. This issue occurred after multiple channel changes on
cluster comprised of 3 or more managed devices. The fix ensures that
the show ap bss-table displays the correct channels. This issue was
observed in managed devices running ArubaOS 8.6.0.0 or later versions
in a cluster setup.

AOS-214944 The profmgr process crashed on Mobility Masters running ArubaOS ArubaOS 8.6.0.7
8.6.0.7 or later versions. This issue occurred while deleting the roles
configured for AirGroup. The fix ensures that the Mobility Masters
works as expected.

ArubaOS 8.6.0.21 Release Notes | Release Notes 12

 Table 6: Resolved Issues in ArubaOS 8.6.0.21

Reported
New Bug ID Description
Version

AOS-216942 Some AP-535 access points running ArubaOS 8.6.0.0 or later versions ArubaOS 8.7.1.10
AOS-237622 crashed and rebooted unexpectedly. The log files listed the reason for
AOS-237621 the event as kernel panic: Fatal exception in interrupt. The fix
ensures that the APs work as expected.

AOS-219192 The Dashboard > Overview > Wireless Clients page of the WebUI did ArubaOS 8.6.0.6
AOS-223549 not display any information and the error message, Error retrieving
AOS-237599 information Please try again later was displayed. The fix ensures that
the WebUI displays the information about clients. This issue was
observed in Mobility Masters running ArubaOS 8.6.0.6 or later versions.

AOS-221514 The status of the VRRP instance was changed to vrrp is not in INIT ArubaOS 8.10.0.5
state. This issue occurred when a new VLAN was added to the port-
channel interface. The fix ensures that the Mobility Master works as
expected. This issue was observed in Mobility Masters running ArubaOS
8.10.0.5 or later versions.

AOS-223221 Some AP-514 and AP-515 access points running ArubaOS 8.6.0.0 or later ArubaOS 8.7.1.4
AOS-237950 versions generated the error logs, CPU: 1 PID: 1979 at ../../../../soft-
ap/broadcom/esdk6/main/src/wl/../../src/wl/sys/wlc.c:22608 wlc_
calc_frame_time+0x12c/0x410 [wl_v6](). The fix ensures that the APs
work as expected.

AOS-226773 The MAC ACLs did not work as expected when OpenFlow was enabled. ArubaOS 8.6.0.11
The fix ensures that the MAC ACLs work as expected. This issue was
observed in managed devices running ArubaOS 8.6.0.11 or later
versions in a cluster setup.

AOS-227306 Some managed devices responded to the ARP probe frames with the ArubaOS 8.7.1.5
SRC MAC address of the clients that were not connected to the network.
The fix ensures that only intended managed devices respond to the ARP
probe frames with the SRC MAC address of the clients. This issue was
observed in managed devices running ArubaOS 8.6.0.0 or later versions.

AOS-229207 Users observed a discrepancy between the client count displayed in the ArubaOS 8.5.0.13
AOS-229888 WebUI of a Mobility Master and the CLI of a managed device. This issue
occurred because the WebUI of the Mobility Master reported the client
count, including the client entries that were retained to accommodate
temporary client disconnections. The fix ensures that the WebUI and CLI
display correct number of clients. This issue was observed in Mobility
Masters running ArubaOS 8.5.0.13 or later versions.

AOS-230044 Some AP-505H access points crashed and rebooted unexpectedly. The ArubaOS 8.6.0.18
AOS-238628 log files listed the reason for reboot as: Kernel panic - not syncing:
AOS-234556 Fatal exception. The fix ensures that the APs work as expected. This
issue was observed in AP-505H access points running ArubaOS 8.6.0.18
or later versions.

AOS-230798 The output of the show global-user-table list command displayed ArubaOS 8.7.1.8
AOS-231576 duplicate user entries for bridge-mode SSIDs. The fix ensures that the
command does not display the duplicate entries. This issue was
observed in Mobility Masters running ArubaOS 8.7.1.8 or later versions.

13 | Resolved Issues ArubaOS 8.6.0.21 Release Notes | Release Notes

 Table 6: Resolved Issues in ArubaOS 8.6.0.21

Reported
New Bug ID Description
Version

AOS-231206 The wpa3_sae process crashed or was stuck in the PROCESS_NOT_ ArubaOS 8.6.0.17
AOS-239396 RESPONDING_CRITICAL state. This issue occurred due to timer
corruption. The fix ensures that the managed devices work as expected.
This issue was observed in managed devices running ArubaOS 8.6.0.17
or later versions.

AOS-231856 A few APs running ArubaOS 8.6.0.0 or later versions crashed ArubaOS 8.7.1.8
unexpectedly. The log files listed the reason for the event as An
internal system error has occurred at file sapd_sysctl.c function
sapd_sysctl_write_param line 184 error Error writing
/proc/net/wifi0/max_eirp_per_chan : Invalid argument. This issue
occurred due to a change of channel on one or both the radios when
EIRP check was done for the new channel. The fix ensures that the EIRP
request is processed and no error logs are generated.

AOS-232124 High CPU utilization was observed in the stm process when client ArubaOS 8.8.0.3
devices utilized TSPEC signaling. The fix ensures that the Mobility
Masters work as expected. This issue was observed in Mobility Masters
running ArubaOS 8.6.0.0 or later versions.

AOS-232928 Some stand-alone controllers running ArubaOS 8.6.0.0 or later versions ArubaOS 8.7.1.9
displayed the error messages, KASan: use after free in wlc_pcb_fn_
find+0xc8/0x160 [wl_v6] at addr ffffffc034931b08 and KASan: out of
bounds access in wlc_pcb_fn_find+0xc8/0x160 [wl_v6] at addr. The
fix ensures that the controllers work as expected.
Duplicates: AOS-233808, AOS-234781, and AOS-236854

AOS-234103 Some clients experienced downstream packet disruption. The fix ArubaOS 8.6.0.17
ensures that the APs work as expected. This issue was observed in AP-
205 access points running ArubaOS 8.6.0.9 or later versions.

AOS-234265 Enet port flapping was observed on a few APs that were connected to ArubaOS 8.6.0.14
AOS-232356 the Cisco 9300 switches. As a result, the APs rebooted and clients
experienced connectivity issues. Enhancements to the wireless driver
resolved the issue. This issue was observed in AP-535 access points
running ArubaOS 8.6.0.14 or later versions.

AOS-234627 Some managed devices running ArubaOS 8.6.0.17 or later versions ArubaOS 8.6.0.17
crashed unexpectedly. This issue occurred after issuing the aaa test-
server command for a Radsec server. The fix ensures that the managed
devices work as expected.

AOS-234647 The stm process crashed on Mobility Masters running ArubaOS 8.6.0.0 ArubaOS 8.10.0.2
or later versions. This issue occurred after a VRRP failover. The fix
ensures that the Mobility Masters work as expected,

AOS-235401 Some managed devices running ArubaOS 8.6.0.17 or later versions did ArubaOS 8.6.0.17
not send the outer IPV6 address to AirWave. The fix ensures that the
managed devices send the IPV6 address correctly.

AOS-235744 Some managed devices were unable to receive any configuration from ArubaOS 8.6.0.17
AOS-235752 the Mobility Master. This issue occurred when changes to a few group
names were not synchronized on the standby Mobility Master before a
reboot. The fix ensures that the managed devices receive configurations
from the Mobility Master. This issue was observed in Mobility Masters
running ArubaOS 8.6.0.17 or later versions.

ArubaOS 8.6.0.21 Release Notes | Release Notes Resolved Issues | 14

 Table 6: Resolved Issues in ArubaOS 8.6.0.21

Reported
New Bug ID Description
Version

AOS-235810 Configuration changes to the SAP MTU value was not displayed ArubaOS 8.9.0.2
correctly. This issue occurred when the storage format of the MTU
configuration was changed and when the file was not read correctly.
The fix ensures that the managed devices work as expected. This issue
was observed in managed devices running ArubaOS 8.6.0.0 or later
versions.

AOS-235914 Some mesh APs running ArubaOS 8.6.0.0 or later versions dropped data ArubaOS 8.7.1.10
AOS-238305 packets. This issue occurred when MTU length was more than 1500
bytes. The fix ensures that the APs work as expected.

AOS-236242 The apmove command did not work as expected when the APs were ArubaOS 8.7.1.9
connected to the backup LMS controllers. The fix ensures that the users
can issue the apmove command. This issue was observed in managed
devices running ArubaOS 8.6.0.0 or later versions.

AOS-236881 After upgrading Mobility Masters to ArubaOS 8.6.0.9 or later versions, ArubaOS 8.6.0.9
the profile manager in the secondary Mobility Master stopped
responding. This issue occurred when IPv6 mode was enabled in the
secondary Mobility Master because of which it failed to download
certificates from the primary Mobility Master. The fix ensures that the
secondary Mobility Master works as expected when IPv6 mode is
enabled.

AOS-236920 Users were unable to convert a few APs to OpenConfig. This issue ArubaOS 8.6.0.18
occurred when the images on the SCP server were not provided with
Read access. The fix ensures that the APs are converted to OpenConfig
seamlessly. This issue was observed in APs running ArubaOS 8.6.0.18 or
later versions.

AOS-237052 The HTTP traffic of some users was incorrectly redirected by the captive ArubaOS 8.6.0.5
AOS-208508 portal. This issue occurred when the ACL changes were not updated on
the APs. The fix ensures that the APs work as expected. This issue was
observed in APs running ArubaOS 8.6.0.5 or later versions.

AOS-237510 Some WPA3-SAE opmode clients were unable to download user roles ArubaOS 8.6.0.18
from ClearPass Policy Manager after a successful MAC authentication.
The log file listed the reason for the event as Cannot be assigned
downloadable role, role is in error state. The fix ensures that the
clients are able to download user roles from ClearPass Policy Manager.
This issue was observed in managed devices running ArubaOS 8.6.0.18
or later versions.

AOS-237897 The Webcc logs were stored in an invalid message format and as a ArubaOS 8.7.1.9
result, the syslog server reported incorrect data. The fix ensures that
the Webcc logs are logged in a valid message format. This issue was
observed in managed devices running ArubaOS 8.0.0.0 or later versions.

AOS-238147 Some APs powered up using POE-AT incorrectly came up with r flag and ArubaOS 8.7.1.10
AOS-239823 were unable to broadcast SSIDs. The fix ensures that the APs work as
expected and broadcast SSIDs. This issue was observed in APs running
ArubaOS 8.6.0.0 or later versions.

15 | Resolved Issues ArubaOS 8.6.0.21 Release Notes | Release Notes

 Table 6: Resolved Issues in ArubaOS 8.6.0.21

Reported
New Bug ID Description
Version

AOS-238410 The httpd process crashed on Mobility Masters and managed devices ArubaOS 8.10.0.3
AOS-238939 running ArubaOS 8.6.0.17 or later versions. This issue occurred when a
AOS-238564 specific type of cURL request was sent to the controllers. The fix ensures
AOS-238487 that the managed devices and Mobility Masters work as expected.

AOS-238456 Some stand-alone controllers failed to perform IKE fragmentation for ArubaOS 8.7.1.11
AOS-238906 VIA clients. This issue occurred when VIA clients used EAP-MSCHAPv2
for authentication. The fix ensures that the controllers perform IKE
fragmentation for VIA clients. This issue was observed in stand-alone
controllers running ArubaOS 8.6.0.0 or later versions.

AOS-238954 Clients that used machine and user authentication were unable to ArubaOS 8.6.0.18
connect to SSIDs. This issue was observed when WPA3 encryption was
used. The fix ensures seamless connectivity. This issue was observed in
AP-515 access points running ArubaOS 8.6.0.18 or later versions.

AOS-238701 The authmgr, httpd, fwvisibility, ctamon, and ucm processes were ArubaOS 8.6.0.19
AOS-238934 stuck in NOT_RESPONDING or INITIALIZING state. The fix ensures that
AOS-239570 the managed devices work as expected. This issue was observed in
managed devices running ArubaOS 8.6.0.19 or later versions in a cluster
setup.

AOS-238708 Some AP-535 access points running ArubaOS8.6.0.17 or later versions ArubaOS 8.6.0.17
were showing very high interference. This may be causing the
performance degradation of AP traffic with the client. The fix ensures
that the AP performs as expected without showing very high
interference.

AOS-238557 The Management Information Base (MIB) wlsxUser6Table was not ArubaOS 8.6.0.19
returned correctly. This was observed when user table had more than
one bridge client, one client having IPv4/IPv6 enabled and the other one
having just IPv4 enabled. This fix ensures the users table is returned
correctly in this scenario. This was seen in some controllers running
ArubaOS 8.6.0.19.

AOS-238500 Clients were unable to connect to a few APs in a cluster. This issue ArubaOS 8.6.0.0
occurred when the tunnel between the AP and the managed device in
the cluster was down. The fix ensures seamless connectivity. This issue
was observed in APs running ArubaOS 8.6.0.0 or later versions.

AOS-238387 The authentication survivability feature did not work as expected and ArubaOS 8.6.0.17
hence, clients were unable to connect to the network. This issue
occurred when the RADIUS server returned a username that was
different from the Certificate Common Name (CN). The fix ensures that
the authentication survivability feature works as expected. This issue
was observed in Managed Devices running ArubaOS 8.6.0.17 or later
versions.

AOS-237975 After peak period a small number of stale users were left in the default ArubaOS 8.6.0.0
802.1x role on WPA3 VAP's. This fix enhances the clean-up of WPA3
stations. This issue was observed in Managed Devicesrunning
ArubaOS8.6.0.0 or later versions.

ArubaOS 8.6.0.21 Release Notes | Release Notes Resolved Issues | 16

 Table 6: Resolved Issues in ArubaOS 8.6.0.21

Reported
New Bug ID Description
Version

AOS-237869 Some AP-635 access points running ArubaOS 8.6.0.0 or later versions ArubaOS 8.6.0.0
displayed the error message, 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. The
fix ensures that the APs work as expected.

AOS-237549 Some controllers running ArubaOS 8.6.0.16 were filtering frames with ArubaOS 8.6.0.16
EAPOL type from client on RAP wired interface. This prevented the
packets from being forwarded to the destination. This fix ensures that
the packets are forwarded as expected.

AOS-237212 In some controllers running ArubaOS 8.6.0.21, clients stopped being ArubaOS 8.6.0.21
able connect to the 11r-enabled wireless SSID with reason Ageout AP
Denied; STA not found in STM. The fix ensures that the clients can
connect to the wireless SSID.

AOS-236841 In some Managed Devices running ArubaOS 8.6.0.0 or later versions, ArubaOS 8.6.0.0
AOS-238400 the WebUI did not display the list of VRRP VLANs (Configuration >
Services > Clusters >Add Controller). It is possible to configure the VRRP
VLAN from CLI. This fix ensures that the WebUI displays the list of VRRP
VLANs.

AOS-226017 The airmatch_recv process crashed on Mobility Master running ArubaOS 8.6.0.9
AOS-231886 ArubaOS 8.6.0.9 or later versions. The log files listed the reason for the
AOS-235947 event as Exceeded max number of packet limit. The fix ensures that the
Mobility Master work as expected.

AOS-201857 The STM process crashed on AP-115 access points running ArubaOS ArubaOS 8.6.0.3
AOS-239541 8.6.0.3 or later versions. The crash occurred with APs that use the
madwifi driver. This fix ensures the APs do not crash and perform as
expected.

AOS-240211 After a Radar detection in a particular channel, the ARM feature caused ArubaOS 8.6.0.18
access points to return to the original channel, ignoring the 30-minute
back-off period that is required after a radar detection, which led
beacons not being transmitted. The fix ensures the APs works as
expected. This issue was observed in AP-535 running ArubaOS 8.6.0.18
or later versions.

AOS-242066 The core.llpd process on AP-535 access points caused controllers to ArubaOS 8.6.0.19
crash unexpectedly. The fix ensures the process works as expected. This
issue was observed in AP-535 running ArubaOS 8.6.0.19 or later
versions.

AOS-241497 Some AP-275 access points were rebooting unexpectedly. The log file ArubaOS 8.6.0.0
list the reason for the event as: Process /aruba/bin/sapd has to many
open failes (769). This issue occurred when there was a change in the
status of the uplink interface. The fix ensures the AP works as expected.
This issue was observed in AP-275 running ArubaOS 8.6.0.0 or later
versions.

17 | Resolved Issues ArubaOS 8.6.0.21 Release Notes | Release Notes

 Table 6: Resolved Issues in ArubaOS 8.6.0.21

Reported
New Bug ID Description
Version

AOS-241434 The show running-config command could not be executed and ArubaOS 8.6.0.20
displayed an error: Module DHCP Daemon is busy. Please try later.
The fix ensures the show running-config command works as expected.
This issue was observed in managed devices running ArubaOS 8.6.0.20
or later versions.

AOS-240995 While downloading the VIA subnets, the endian conversion did not ArubaOS 8.6.0.9
happen as expected. This resulted in the VIA subnet routes getting
installed in reverse order. The fix ensures the feature works as
expected. This issue was observed in Mobility Controller running
ArubaOS 8.6.0.9 or later versions.

AOS-240958 Multiple sapd process error messages: Error ArubaOS 8.6.0.0

opening/proc/sys/net/aruba_asap/aruba001/bw_stats : No such
file or directory were observed on RAP-503H remote access points
with backup SSID configured. The fix ensures that the RAP-503H works
as expected. This issue was observed in APs running ArubaOS 8.6.0.0 or
later versions.

AOS-240920 The fpapps process crashed unexpectedly querying an unknown ifMIB ArubaOS 8.6.0.0
OID using SNMP. The fix ensures that the process fpapps does not
crash when an invalid ifMIB OID is used. It was observed in mobility
devices running ArubaOS 8.6.0.0 or later versions.

AOS-240858 The LTE upling did not come up for RAP-303H remote access points. The ArubaOS 8.6.0.0
fix ensures that LTE upling works as expected on RAP-303H remote
access points. This issue was observed in RAP-303H running ArubaOS
8.6.0.0 or later versions.

AOS-239810 In the WebUI Dashboard > Overview > Clients, Channel Health ArubaOS 8.6.0.15
Status showed intermittently as Unknown. The fix ensures WebUI
works as expected. This issue was observed in Mobility Master running
ArubaOS 8.6.0.15 or later versions.

AOS-234153 Mobility Master running ArubaOS 8.6.0.0 or later versions, displayed ArubaOS 8.6.0.0
multiple OSCP error logs. The fix ensures that the Mobility Masterworks
as expected.

AOS-232970 The MAC address of the AP was not present in the calling-station-ID of ArubaOS 8.6.0.0
the RADIUS accounting packets, when station is activated on S-UAC. It
caused the RADIUS accounting requests to be discarded. The fix
ensures the Access Points works as expected. This issue was observed
in managed devices running ArubaOS 8.6.0.0 or later versions in a
cluster setup.

AOS-232800 Some managed devices that are part of an L3 mobility domain rebooted ArubaOS 8.6.0.0
unexpectedly. The log file listed the reason for the event as: Reboot
Cause: Nanny rebooted machine - mobileip process died
(Intent:cause:register 24:86:50:2). The fix ensures that the managed
devices work as expected. This issue was observed in managed devices
running ArubaOS 8.6.0.0 or later versions

AOS-232348 The stm process crashed on AP-325 access points running ArubaOS ArubaOS 8.6.0.0
AOS-223759 8.6.0.0 or later versions. The fix ensures that the stm process works as
expected.

ArubaOS 8.6.0.21 Release Notes | Release Notes Resolved Issues | 18

 Table 6: Resolved Issues in ArubaOS 8.6.0.21

Reported
New Bug ID Description
Version

AOS-237895 Some APs crashed and rebooted unexpectedly with the reason as: ArubaOS 8.6.0.17
Kernel panic - not syncing: Take care of the TARGET ASSERT first.
The crash log indicates it was due to M3 exception. The fix ensures that
the APs works as expected. This issue was observed in AP-535 running
ArubaOS8.6.0.17 or later versions.

AOS-228996 The AMON-sender process crashed on managed devices unexpectedly. ArubaOS 8.7.1.5
AOS-238624 The fix ensures the AMON-sender process works as expected. This issue
was observed in 7240XM controllers running ArubaOS 8.6.0.18 or later
versions.

AOS-228093 Some AP-635 access points running ArubaOS 8.6.0.18 dropped traffic ArubaOS 8.10.0.0
AOS-241619 unexpectedly. The log files recorded the error as cannot find tunnel.
AOS-242797 This issue was observed while sending downstream TCP traffic to the
APs on both, 5 GHz and 6 GHz bands. The fix ensures that the APs do
not drop any traffic to clients.

AOS-236503 Some clients dropped traffic that came through Aruba GRE tunnels. This ArubaOS 8.10.0.7
AOS-239162 issue occurred due to invalid GRE flags observed while using third party
devices with IPS. The fix ensures that the clients do not drop any traffic.
This issue was observed in APs running ArubaOS 8.6.0.16 or later
versions.

AOS-235834 Some AP-535 and AP-555 access points running ArubaOS 8.6.0.19 or ArubaOS 8.6.0.19
AOS-240216 later versions crashed and rebooted unexpectedly. The log file lists the
AOS-241718 reason for reboot as: Reboot caused by kernel panic: Fatal
AOS-235832 exception in interrupt. The fix ensures that the APs work as expected.

AOS-235786 A few 7280 controllers running ArubaOS 8.6.0.17 sent system log ArubaOS 8.6.0.17
messages without the host name to the system log server. This issue
occurred when the host name was not set during the controller boot
up. The fix ensures that the controllers send system log messages with
a host name.

AOS-234315 A few APs sent PAPI messages to external IP addresses, and the logs ArubaOS 8.6.0.15
displayed a random IP address for the PAPI_Send failed error message.
This issue is observed in APs running ArubaOS 8.6.0.15 or later versions.
The fix ensures that the APs work as expected.

AOS-239498 Some AP-515 access points running ArubaOS 8.6.0.19 or later versions ArubaOS 8.6.0.19
crashed and rebooted unexpectedly. The log files listed the reason for
the event as AP Reboot reason: BadPtr:0000000f PC:wlc_get_txh_
info+0x118/0x210 [wl_v6] Warm-reset. The fix ensures that APs do not
crash, and work as expected.

AOS-239260 Some AP-505 access points running ArubaOS 8.6.0.18 or later versions ArubaOS 8.6.0.18
crashed and rebooted unexpectedly. The log files listed the reason for
the event as BadPtr:00000294 PC:tun_recv_esp2_prep+0x10c/0x15c
Warm-reset. The fix ensures that the APs work as expected.

19 | Resolved Issues ArubaOS 8.6.0.21 Release Notes | Release Notes

 Table 6: Resolved Issues in ArubaOS 8.6.0.21

Reported
New Bug ID Description
Version

AOS-238836 Clients that used MAC and user authentication were unable to connect ArubaOS 8.6.0.18
to SSIDs. This issue was observed when WPA2 encryption was used. The
fix ensures seamless connectivity. This issue was observed in APs
running ArubaOS8.6.0.18 or later versions.

AOS-239452 Some Mobility Controllers reported the wrong AP BSSID when sending ArubaOS 8.6.0.0
the wlsxNAuthServerAcctTimedOut SNMP trap. The fix ensures that
Mobility Controllers report the correct BSSID when sending a server
request timed out event. This issue was observed in Mobility Controllers
running ArubaOS 8.6.0.0 or later versions.

AOS-239341 Some AP-345 access points running ArubaOS 8.6.0.10 or later versions ArubaOS 8.6.0.10
were detecting high channel utilization while there was none. This issue
was due to the misinterpretation of the header information of ID
duration frames. The fix ensures that the interpretation of duration
frames is correct and APs work as expected.

AOS-239183 The webUI for some Mobility Controllers incorrectly applied daylight ArubaOS 8.6.0.10
savings and displayed an inaccurate time for certain time zones. This
behavior was observed in Mobility Controllers running ArubaOS 8.6.0.10
or later versions. The fix ensures the webUI displays the correct time
according to the set timezone.

AOS-238960 Some stand-alone controllers running ArubaOS 8.6.0.0 or later versions ArubaOS 8.7.1.8
crashed and rebooted unexpectedly. The log files listed the reason for
the event as Datapath timeout (SOS Assert) (Intent:cause:register
54:86:50:2). The fix ensures that the stand-alone controllers work as
expected.

AOS-238815 Some AP-515 access points showed a busy status when attempting to ArubaOS 8.6.0.18
AOS-238394 collect tech-support logs. This issue occurred during the transmission of
large packets over the devices. The fix ensures tech-support data can be
collected without the AP status showing as busy. This issue could be
observed in APs running ArubaOS 8.6.0.18 or later versions.

AOS-238768 WebUI took a long time to display the AP and client information, ArubaOS 8.6.0.0
especially when devices were running different versions of ArubaOS.
The fix ensures that the WebUI displays the AP and client information
without any delay, even in a multi-version scenario. This issue was
observed in Mobility Masters running ArubaOS 8.6.0.0 or later versions.

AOS-236595 Some AP-535 access points running ArubaOS 8.6.0.15 crashed and ArubaOS 8.7.1.9
rebooted unexpectedly. The issue occurred when the Tx chainmask was
not updated during switch mode which caused inconsistent Tx
chainmask between radio and the client's rate table. The fix ensures
that the APs work as expected.

AOS-236427 The license feature bits of a stand-alone controller were changed to ArubaOS 8.10.0.2
enabled after restoring the flash backup. The fix ensures that the status
of the license feature bits does not change after restoring the flash
backup. This issue was observed in standalone controllers running
ArubaOS 8.10.0.2 or later versions.

ArubaOS 8.6.0.21 Release Notes | Release Notes Resolved Issues | 20

 Table 6: Resolved Issues in ArubaOS 8.6.0.21

Reported
New Bug ID Description
Version

AOS-235672 Some wired clients failed to obtain IP addresses after rebooting or ArubaOS 8.6.0.9
reconnecting in RAP Split-Tunnelling mode. The issue occurred when
the AP datapath failed to add users when there was a downstream
traffic to the wired client before the client sent any packet. This issue
was observed in APs running ArubaOS 8.6.0.9 or later versions.

AOS-234480 The apflash ap31x-ap32x backup partition command did not ArubaOS 8.7.1.9
AOS-238970 upgrade the backup partition of AP-315 access points running ArubaOS
8.6.0.21 in a cluster setup. The fix ensures that the command upgrades
the backup partition of the APs.

AOS-231437 Some APs were incorrectly power restricted, and the radios got ArubaOS 8.9.0.2
AOS-232529 disabled. The fix ensures that the APs work as expected. This issue was
AOS-239101 observed in AP-505 and AP-515 access points running ArubaOS 8.6.0.0
AOS-233640 or later versions.

AOS-239564 Some AP-515 access points running ArubaOS8.6.0.19 dropped all ArubaOS8.6.0.19
AMSDU in upstream in tunnel mode, which causes degraded
performance. This fix ensures the APs perform as expected.

AOS-234783 Some AP-505, AP-504, and AP-505H access points running ArubaOS ArubaOS 8.10.0.0
8.6.0.0 or later versions were flooded with wlc_offload 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.

21 | Resolved Issues ArubaOS 8.6.0.21 Release Notes | Release Notes

 Chapter 7
Known Issues

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

Limitation
Following are the limitations observed in this release:

Port-Channel Limitation in 7280 Controllers

On 7280 controllers with all the member ports of each port-channel configured from the same NAE
(Network Acceleration Engine), if one of the member ports experiences link flap either due to a network
event or a user driven action, the rest of the port-channels also observe the link flap for less than a
second.

No Support for Unique Local Address over IPv6 Network

The IPv6 addresses for interface tunnels do not accept unique local addresses.

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

Table 7: Known Issues in ArubaOS 8.6.0.21

Old Bug Reported

New Bug ID Description
ID Version

AOS-151022 185176 The output of the show datapath uplink command ArubaOS 8.1.0.0
AOS-188417 displays incorrect session count. This issue is
observed in managed devices running ArubaOS
8.1.0.0 or later versions.

AOS-151355 185602 A few managed devices are unable to pass traffic to ArubaOS 8.0.1.0
the nexthop VPN concentrator (VPNC) using policy-
based routing. This issue is observed in managed
devices running ArubaOS 8.0.1.0 or later versions.

AOS-155404 191106 An AP is unable to establish IKE/IPsec tunnel with the ArubaOS 8.6.0.4
AOS-207878 managed device. This issue occurs when the AP is
enrolled with EST certificates. This issue is observed
in AP-515 access points running ArubaOS 8.5.0.0 or
later versions in a Mobility Master-Managed Device
topology.

AOS-156068 192100 The DDS process in a managed device running ArubaOS 8.2.1.1
ArubaOS 8.2.1.1 or later versions crashes
unexpectedly.

ArubaOS 8.6.0.21 Release Notes | Release Notes 22

 Table 7: Known Issues in ArubaOS 8.6.0.21

Old Bug Reported

New Bug ID Description
ID Version

AOS-182847 — A few users are unable to copy the WPA Passphrase ArubaOS 8.4.0.0
field and High-throughput profile to a new SSID
profile in the Configuration > System > Profiles >
Wireless LAN > SSID > <SSID_Profile> option of the
WebUI. This issue occurs when a new SSID profile is
created from an existing SSID profile using WebUI.
This issue is observed in managed devices running
ArubaOS8.4.0.0 or later versions in a Mobility
Master-Managed Device topology.

AOS-184947 — The jitter and health score data are missing from the ArubaOS 8.4.0.4
AOS-192737 Dashboard > Infrastructure > Uplink > Health
page in the WebUI. This issue is observed in Mobility
Masters running ArubaOS 8.4.0.4 or later versions.

AOS-185538 — High number of EAP-TLS timeouts are observed in ArubaOS 8.3.0.8

AOS-195334 managed devices. This issue occurs when multiple IP
addresses are assigned to each client. This issue is
observed in managed devices running ArubaOS
8.3.0.8 or later versions.

AOS-187672 — Memory leak is observed in the arci-cli-helper ArubaOS 8.3.0.6

AOS-213397 process. This issue is observed in Mobility Masters
and managed devices running ArubaOS 8.3.0.6 or
later versions.

AOS-188255 — The Dashboard > Overview page of the WebUI ArubaOS 8.3.0.8
AOS-190476 displays incorrect number of users intermittently.
AOS-190946 This issue is observed in Mobility Masters running
AOS-192725 ArubaOS 8.3.0.8 or later versions.
AOS-193586
AOS-194784
AOS-196004
AOS-200375
AOS-210787

AOS-188972 — Mobility Master displays the blacklisted clients ArubaOS 8.4.0.4

AOS-194746 although the clients were removed from the
AOS-208631 managed device. This issue is observed in Mobility
AOS-213627 Masters running ArubaOS 8.4.0.4 or later versions in
a cluster setup.

AOS-190071 — A few users are unable to access websites when ArubaOS 8.4.0.0
AOS-190372 WebCC is enabled on the user role. This issue occurs
in a Per-User Tunnel Node (PUTN) setup when the
VLAN of user role is in trunk mode. This issue is
observed in 7005 controllers running ArubaOS
8.4.0.0.
Workaround:
Perform the following steps to resolve the issue:
1.Remove web category from the ACL rules and
apply any any any permit policy.
2. Disable WebCC on the user role.
3. Change the VLAN of user role from trunk mode
to access mode.

23 | Known Issues ArubaOS 8.6.0.21 Release Notes | Release Notes

 Table 7: Known Issues in ArubaOS 8.6.0.21

Old Bug Reported

New Bug ID Description
ID Version

AOS-190621 — WebUI does not filter the names of the APs that ArubaOS 8.4.0.2
contain the special characters, +, %, and &. This issue
is observed in managed devices running ArubaOS
8.4.0.2 or later versions.

AOS-193184 — All L2 connected managed devices move to L3 ArubaOS 8.5.0.2

connected state after an upgrade. This issue is
observed in managed devices running ArubaOS
8.5.0.2 or later versions.

AOS-193231 — The Dashboard > Infrastructure > Access Devices ArubaOS 8.5.0.3
AOS-200101 page of the WebUI displays an error message, Error
AOS-207456 retrieving information. This issue is observed in
Mobility Masters running ArubaOS 8.5.0.3 or later
versions.

AOS-193278 — Users are unable to bring up the VPNC after an ArubaOS 8.4.0.4
AOS-228782 upgrade. The controller is stuck with an error
message, CONTROLLER-IP/V6 NOT SET
(00:1a:1e:05:cd:28). This issue is observed in
Mobility Masters running ArubaOS 8.4.0.4 or later
versions.

AOS-193560 — The number of APs that are DOWN are incorrectly ArubaOS 8.6.0.19
AOS-198565 displayed in the Dashboard > Overview page of the
AOS-224274 WebUI. However, the CLI displays the correct status
AOS-200262 of APs. This issue is observed in Mobility Masters
AOS-204794 running ArubaOS 8.4.0.4 or later versions.
AOS-208110
AOS-209989
AOS-212249

AOS-193775 — A mismatch of AP count and client count is observed ArubaOS 8.5.0.2

AOS-194581 between the Mobility Master and the managed
AOS-197372 device. This issue is observed in Mobility Masters
running ArubaOS 8.3.0.0 or later versions.

AOS-194080 — Some controllers display the error message, ArubaOS 8.4.0.4

Deleting a user IP=fe80::1c4d:d31f:a935:2107 with
flags=0x0 from the datapath that does not exist
in auth even if IPv6 is disabled on the managed
devices. This issue is observed in stand-alone
controllers running ArubaOS 8.2.2.10 or later
versions.

AOS-194370 — High memory utilization is observed in the cluster ArubaOS 8.4.0.2

manager process of managed devices. This issue is
observed in managed devices running ArubaOS
8.4.0.2 or later versions in a cluster setup.

AOS-194381 — Some managed devices lose the route-cache entries ArubaOS 8.3.0.7
and drop the VRRP IP addresses sporadically. This
issue is observed in managed devices running
ArubaOS 8.3.0.7 or later versions.

ArubaOS 8.6.0.21 Release Notes | Release Notes Known Issues | 24

 Table 7: Known Issues in ArubaOS 8.6.0.21

Old Bug Reported

New Bug ID Description
ID Version

AOS-194911 — Incorrect flag output is displayed for APs configured ArubaOS 8.5.0.2
with 802.1X authentication when the show ap
database command is executed. This issue is
observed in APs running ArubaOS 8.5.0.2 or later
versions.

AOS-194964 — A few users are unable to clone configurations from ArubaOS 8.5.0.2
an existing group to a new group in a Mobility
Master. This issue is observed in Mobility Masters
running ArubaOS 8.4.0.1 or later versions.
Workaround: Execute the rf dot11a-radio-profile
<profile name> command to change the operating
mode of the AP from am-mode to ap-mode.

AOS-195100 — The health status of a managed device is incorrectly ArubaOS 8.3.0.7

AOS-198302 displayed as Poor in the Dashboard >
AOS-204455 Infrastructure page of the Mobility Master's WebUI.
AOS-206735 This issue is observed in Mobility Masters running
ArubaOS 8.3.0.7 or later versions.

AOS-195089 — The DNS traffic is incorrectly getting classified as ArubaOS 8.3.0.7

Thunder and is getting blocked. This issue occurs
when the DNS traffic is blocked, and peer-peer ACL is
denied for users. This issue is observed in managed
devices running ArubaOS 8.3.0.7 or later versions.

AOS-195177 — Some managed devices frequently generate internal ArubaOS 8.3.0.7

system error logs. This issue occurs when the sapd
process reads a non-existent interface. This issue is
observed in 7220 controllers running ArubaOS
8.3.0.7 or later versions.

AOS-195434 — Some APs crash and reboot unexpectedly. The log ArubaOS 8.5.0.2
files list the reason for the event as Reboot caused
by kernel panic: Fatal exception. This issue is
observed in APs running ArubaOS 8.5.0.0 or later
versions in a Mobility Master-managed device
topology.

AOS-196457 — Clients are reporting various issues in terms of ArubaOS 8.5.0.2

performance, client connectivity, and AP showing up
high noise floor for more than 48 hours. This issue is
observed in AP-515 access points running ArubaOS
8.5.0.2 or later versions.

AOS-196590 — Some 9004 controllers running ArubaOS 8.6.0.0, and ArubaOS 8.6.0.0
later versions crash and reboot unexpectedly. This
issue is observed when an unsupported third-party
cellular modem is connected to the controller for a
cellular uplink.

25 | Known Issues ArubaOS 8.6.0.21 Release Notes | Release Notes

 Table 7: Known Issues in ArubaOS 8.6.0.21

Old Bug Reported

New Bug ID Description
ID Version

AOS-196864 — Although a new VLAN ID is successfully connected, ArubaOS 8.5.0.3

the managed device displays that the VLAN ID fails
with a different ID. This issue is observed when new
VLANs are added and the total number of VLANs are
100/101, 200/201, 300/301 and so on. This issue is
observed in managed devices running ArubaOS
8.5.0.3 or later versions.

AOS-196878 — The datapath process crashes on a managed device. ArubaOS 8.5.0.2

AOS-197216 The log file lists the reason for the event as wlan-
n09-nc1.gw.illinois.edu. This issue is observed in
managed devices running ArubaOS 8.5.0.2 or later
versions.

AOS-197023 — Mobility Master sends incorrect AP regulatory- ArubaOS 8.5.0.4

domain-profile channel changes to the managed
device during the initial configuration propagation.
This issue is observed in Mobility Masters running
ArubaOS 8.0.0.0 or later versions.
Workaround: Perform one of the following steps to
resolve the issue:
n In the CLI, execute the ap regulatory-domain-
profile command to create an AP regulatory-
domain-profile without any channel
configuration, save the changes, and later add or
delete channels as desired.
n In the WebUI, create an AP regulatory-domain-
profile with default channel selected, save the
changes, and later add or delete channels as
desired in the Configuration > AP Groups page.

AOS-193883 — A few APs are unable to use DHCP IPv6 addresses ArubaOS 8.3.0.8
AOS-197756 and option 52 for master discovery. This issue occurs
AOS-227874 when APs did not clear the previous LMS entries
AOS-239268 after an upgrade. This issue is observed in access
points running ArubaOS 8.3.0.8 or later versions.
Workaround: Delete the IPv4 addresses from the ap
system profile using the command, ap system-
profile and from high availability profiles using the
command, ha.

AOS-197494 — The show datapath debug opcode command ArubaOS 8.3.0.1

displays hexadecimal output. This issue is observed
in managed devices running ArubaOS 8.3.0.1 or later
versions.

AOS-198024 — Users are unable to access any page after the fifth ArubaOS 8.6.0.0
page using the Maintenance > Access Point page in
the WebUI. This issue is observed in stand-alone
controllers running ArubaOS 8.6.0.0 or later versions.

ArubaOS 8.6.0.21 Release Notes | Release Notes Known Issues | 26

 Table 7: Known Issues in ArubaOS 8.6.0.21

Old Bug Reported

New Bug ID Description
ID Version

AOS-198281 — The details of the Up time in Managed network > ArubaOS 8.2.2.6
Dashboard > Access Points > Access Points table
does not get updated correctly. This issue is
observed in Mobility Masters running ArubaOS
8.2.2.6 or later versions.

AOS-198382 — The output of the command, show aaa state ArubaOS 8.6.0.0
message does not display any name for opcodes
204 and 253. The issue is observed in managed
devices running ArubaOS 8.6.0.0 or later versions.

AOS-198483 — The WebUI does not have an option to map the rf ArubaOS 8.5.0.4
dot11- 60GHz-radio-profile to an AP group. This
issue is observed in Mobility Masters running
ArubaOS 8.5.0.4 or later versions.

AOS-199724 — Reverse Policy Based Routing (PBR) is not working ArubaOS 8.6.0.5
AOS-214805 when applied to the VPN tunnel’s Access Control List
(ACL) in hub and spoke setups. This issue is observed
in Mobility Controllers running ArubaOS 8.6.0.5 or
later versions.

AOS-198829 — An incomplete route cache causes the Aruba 9004 ArubaOS 8.5.0.0
AOS-199188 gateway to not learn the client’s ARP. This issue is
observed in managed devices running ArubaOS
8.5.0.0 or later versions.

AOS-198849 — Users are unable to configure 2.4 GHz radio profile in ArubaOS 8.5.0.3
AOS-198850 the Configuration > System > Profiles > 2.4 GHz
radio profile page and the WebUI displays an error
message, Feature is not enabled in the license.
This issue is observed in stand-alone controllers
running ArubaOS 8.5.0.3 or later versions.

AOS-198991 — Users are unable to add a VLAN to an existing trunk ArubaOS 8.6.0.2
port using the Configuration > Interfaces > VLANs
page of the WebUI. This issue is observed in Mobility
Masters running ArubaOS 8.6.0.1 or later versions.

AOS-199492 — Some APs do not get displayed in the show airgroup ArubaOS 8.6.0.0
aps command output and the auto-associate policy
does not work as expected. This issue occurs when
the AirGroup domain is in distributed-mode and is
not validated in a cluster deployment. This issue is
observed in managed devices running ArubaOS
8.6.0.0 or later versions.

AOS-200515 — The DDS process crashes on managed devices ArubaOS 8.3.0.10

AOS-219987 running ArubaOS 8.3.0.10 or later versions. This
issue occurs when HA is inadvertently attempted
between ArubaOS6.5.x and ArubaOS 8.x, up to
ArubaOS 8.9 where the issue is fixed.

27 | Known Issues ArubaOS 8.6.0.21 Release Notes | Release Notes

 Table 7: Known Issues in ArubaOS 8.6.0.21

Old Bug Reported

New Bug ID Description
ID Version

AOS-200733 — Some APs running ArubaOS 8.5.0.3 or later versions ArubaOS 8.5.0.3
crash and reboot unexpectedly. The log file lists the
reason for the event as kernel page fault at virtual
address 00005654, epc == c0bd7dd4, ra ==
c0bf95f8.

AOS-200765 — Some managed devices running ArubaOS 8.3.0.7 or ArubaOS 8.3.0.7

later versions in a cluster setup log the error
message, <199804> <4844> |authmgr| |cluster|
gsm_auth.c, auth_gsm_publish_ip_user_local_
section:1011: auth_gsm_publish_ip_user_local_
section: ip_user_local_flags.

AOS-201376 — The measured power, Meas. Pow column in the ArubaOS 8.5.0.6
show ap debug ble-table command does not get
updated when the TX power of an AP is changed.
This issue is observed in APs running ArubaOS
8.5.0.6 or later versions.

AOS-201439 — Some AP-303H access points running ArubaOS ArubaOS 8.5.0.5

AOS-201448 8.5.0.5 or later versions crash and reboot
unexpectedly. The log file lists the reason for the
event as PC is at skb_panic+0x5c/0x68.

AOS-202129 — The Configuration > AP groups page does not have ArubaOS 8.6.0.0
AOS-204127 the Split radio toggle button to enable the tri-radio
feature. This issue is observed in stand-alone
controllers running ArubaOS 8.6.0.0 or later versions.

AOS-202426 — Some 510 Series access points running ArubaOS ArubaOS 8.6.0.4
AOS-203652 8.6.0.4 crash and reboot unexpectedly. The log files
list the reason for the event as PC is at: wlc_phy_
enable_hwaci_28nm+0x938 - undefined
instruction: 0 [#1].

AOS-202519 — The interface tunnel with IPv6 fails to accept Unique ArubaOS 8.6.0.3
Local Address (ULA) as a valid address. This issue
was observed in managed devices running ArubaOS
8.6.0.3 or later versions.

AOS-202552 — The Dashboard > Traffic Analysis > AppRF page of ArubaOS 8.3.0.0
AOS-203990 the WebUI displays Unknown for WLANs, Roles, and
Devices. This issue is observed in Mobility Masters
running ArubaOS 8.3.0.0 or later versions.

AOS-203201 — A managed device is unable to download ArubaOS 8.2.2.6

configurations from the Mobility Master using VPNC.
This issue is observed in managed devices running
ArubaOS 8.2.2.6 or later versions.

AOS-203213 Some Mobility Controllers running ArubaOS 8.5.0.8 ArubaOS 8.5.0.8

crash and reboot in a continuous loop. This issue is
observed on upgrading to ArubaOS 8.5.0.8 or later
versions.

ArubaOS 8.6.0.21 Release Notes | Release Notes Known Issues | 28

 Table 7: Known Issues in ArubaOS 8.6.0.21

Old Bug Reported

New Bug ID Description
ID Version

AOS-203336 — The Dashboard > Infrastructure > Access Points ArubaOS 8.5.0.5
page of the WebUI and the show log command
display different values for the last AP reboot time.
This issue is observed in stand-alone controllers
running ArubaOS 8.5.0.5 or later versions.

AOS-203438 — The EIRP value configured using the WebUI is not ArubaOS 8.6.0.3
visible in stand-alone controllers running ArubaOS
8.6.0.3 or later versions.

AOS-203614 — The Mobility Master dashboard does not display the ArubaOS 8.6.0.2
AOS-209261 number of APs and clients present in the network.
This issue is observed in Mobility Masters running
ArubaOS 8.6.0.2 or later versions.

AOS-203682 — The Dashboard > WLANs page of the WebUI does ArubaOS 8.6.0.15
not display the list of all the clients and APs. This
issue is observed in Mobility Masters running
ArubaOS 8.5.0.2 or later versions.
Duplicates: AOS-195432, AOS-195433, AOS-218290,
and AOS-220829

AOS-204414 — The VLAN range configured using the ntp- ArubaOS 8.3.0.8
standalone vlan-range command is not correctly
sent to the managed devices. This issue occurs when
the user repeatedly modifies the VLAN range. This
issue occurs in Mobility Masters running ArubaOS
8.0.1.0 or later versions.
Workaround: Delete the VLAN range configured on
the Mobility Master and re-configure the ntp-
standalone vlan-range.

AOS-205319 — Some APs running ArubaOS 8.6.0.5 or later versions ArubaOS 8.6.0.5
AOS-206993 crash and reboot unexpectedly. The log file lists the
AOS-216577 reason for the event as Reboot caused by kernel
AOS-218524 panic: Fatal exception in interrupt.

AOS-206178 — System logs do not display the reason why an AP has ArubaOS 8.6.0.4
shut down. This issue is observed in Mobility Masters
running ArubaOS 8.6.0.4 or later versions.

AOS-206541 — The Maintenance > Software Management page ArubaOS 8.5.0.8

does not display the list of all managed devices that
are part of a cluster. This issue is observed in
Mobility Masters running ArubaOS 8.5.0.8 or later
versions.

AOS-206752 — The console log of 7205 controllers running ArubaOS ArubaOS 8.5.0.9
8.5.0.9 or later versions displays the ofald| |sdn|
ERRS ofconn_rx:476 <10.50.1.26:6633> socket read
failed, err:Resource temporarily unavailable(11)
message.

29 | Known Issues ArubaOS 8.6.0.21 Release Notes | Release Notes

 Table 7: Known Issues in ArubaOS 8.6.0.21

Old Bug Reported

New Bug ID Description
ID Version

AOS-206795 — A user is unable to rename a node from the Mobility ArubaOS 8.3.0.7
Master node hierarchy. This issue is observed in
Mobility Masters running ArubaOS 8.3.0.7 or later
versions.
Workaround: Restart profmgr process to rename
the node.

AOS-206902 — AirGroup users are unable to connect to Sonos ArubaOS 8.5.0.9

AOS-208241 speakers. This issue is observed in managed devices
running ArubaOS 8.5.0.9 or later versions.

AOS-207006 — APs go down and UDP 8209 traffic is sent without ArubaOS 8.6.0.4
AOS-215138 UDP 4500 traffic. This issue is observed in managed
devices running ArubaOS 8.6.0.4 or later versions.

AOS-207245 — Some managed devices running ArubaOS 8.5.0.8 or ArubaOS 8.5.0.8

later versions crash and reboot unexpectedly. The
log file lists the reason for the event as Hardware
Watchdog Reset (Intent:cause:register
53:86:0:802c).

AOS-207366 — The show advanced options menu is not available ArubaOS 8.3.0.13
in the Configuration > Access Points > Campus
APs page of the WebUI. This issue occurs when more
than one AP is selected. This issue is observed in
Mobility Masters running ArubaOS 8.3.0.13 or later
versions.

AOS-207899 — Some AP-325 access points running ArubaOS 6.5.4.0 ArubaOS 8.6.0.4
AOS-208505 are crashing and rebooting unexpectedly. The log file
lists the reason for the event as: Reboot after
image upgrade failed: 65280 shutting down
watchdog process (nanny will restart it). This
issue occurred when attempting to upgrade the AP-
325 access points to ArubaOS 8.6.0.4.

AOS-209580 — The output of the show ap database command ArubaOS 8.3.0.13

does not display the o or i flags, which indicate
whether an AP is an outdoor AP or an indoor AP. This
issue occurs when the AP installation type is not set
to default. This issue is observed in Mobility Masters
running ArubaOS 8.3.0.13 or later versions.

AOS-209888 — The Diagnostics > Tools > AAA Server Test page of ArubaOS 8.6.0.14
AOS-224884 the WebUI displays the Authentication status as 0
AOS-228474 instead of Authentication Successful. This issue is
observed in managed devices running ArubaOS
8.6.0.14 or later versions.

AOS-209912 — A few managed devices fail to filter and drop ArubaOS 8.6.0.5
spoofed ARP responses from the clients. The user
entry for the other IP address is present on the
managed devices but not in the route cache table.
This issue is observed in managed devices running
ArubaOS 8.6.0.5 or later versions.

ArubaOS 8.6.0.21 Release Notes | Release Notes Known Issues | 30

 Table 7: Known Issues in ArubaOS 8.6.0.21

Old Bug Reported

New Bug ID Description
ID Version

AOS-209977 — An SNMP query with an incorrect string fails to ArubaOS 8.5.0.10

record the offending IP address. This issue is
observed in managed devices running ArubaOS
8.5.0.10 or later versions.

AOS-210198 — The Dashboard > Security > Detected Radio page ArubaOS 8.6.0.5
of the WebUI displays incorrect number of Clients.
This issue is observed in Mobility Masters running
ArubaOS 8.6.0.5 or later versions.

AOS-210329 — Some managed devices advertise stale maxAge OSPF ArubaOS 8.5.0.10
LSA to its peers which prevents the installation of IKE
routes. This issue is observed in managed devices
running ArubaOS 8.5.0.10 or later versions.

AOS-210482 — Some managed devices running ArubaOS 8.3.0.6 or ArubaOS 8.3.0.6

later versions display the error message, Invalid set
request while configuring ESSID for a Beacon Report
Request profile.

AOS-210992 — The Mobility Master displays an error message, Flow ArubaOS 8.6.0.5
Group delete: id not found after an upgrade. This
issue occurs when logging levels are not configured
correctly. This issue is observed in Mobility Masters
running ArubaOS 8.6.0.5 or later versions.

AOS-212038 — The show memory <process-name> command ArubaOS 8.6.0.5

does not display information related to the dpagent
process. This issue is observed in managed devices
running ArubaOS 8.6.0.5 or later versions.

AOS-212255 — Some APs are stuck in Not in Progress state during ArubaOS 8.5.0.10
cluster live upgrade. This issue is observed in
managed devices running ArubaOS 8.5.0.10 or later
versions.

AOS-212772 — Some IPv6 clients are unable to access websites that ArubaOS 8.3.0.7
AOS-221882 have only IPv4 addresses. This issue is observed in
Mobility Masters running ArubaOS 8.3.0.7 or later
versions.

AOS-215852 — Mobility Masters running ArubaOS 8.6.0.6 or later ArubaOS 8.6.0.6

versions log the error message, ofa:
07765|ofproto|INFO|Aruba-SDN: 1 flow_mods 28
s ago (1 modifications). This issue occurs when
openflow is enabled and 35 seconds is configured as
UCC session idle timeout.

AOS-217890 — Some managed devices running ArubaOS 8.5.0.10 or ArubaOS 8.5.0.10

later versions crash and reboot unexpectedly. The
log file lists the reason for the event as, Datapath
timeout (SOS Assert).

31 | Known Issues ArubaOS 8.6.0.21 Release Notes | Release Notes

 Table 7: Known Issues in ArubaOS 8.6.0.21

Old Bug Reported

New Bug ID Description
ID Version

AOS-218426 — The status LED displays incorrect status. This issue is ArubaOS 8.5.0.11
observed in stand-alone controllers running
ArubaOS 8.5.0.11 or later versions.

AOS-218844 — A Mobility Master picks only 43% of the APs for ArubaOS 8.6.0.9
AOS-222351 cluster CRU. This issue is observed in Mobility
AOS-227400 Masters running ArubaOS 8.6.0.9 or later versions.
AOS-231009

AOS-219765 — Some AP-555 access points running ArubaOS ArubaOS 8.7.1.7

AOS-231995 8.6.0.15 or later versions crash and reboot
unexpectedly. The log files list the reason for the
event as AP-555 crashed: Take care of the TARGET
ASSERT first - ar_wal_tx_seq.c:3041 Assertion seq_
ctrl.

AOS-219484 — The Configuration > WLANs page of the WebUI ArubaOS 8.5.0.8
AOS-219343 does not allow users to enter new VLANs. This issue
AOS-220151 is observed in Mobility Masters running ArubaOS
AOS-220457 8.5.0.8 or later versions.

AOS-220318 — The show ap bss-table command does not display ArubaOS 8.6.0.9
the flags in alphabetical order. Also, some missing
flags are displayed in the status legend but are not
documented. This issue is observed in managed
devices running ArubaOS 8.6.0.9 or later versions.

AOS-220515 — Some managed devices running ArubaOS 8.0.0.0 or ArubaOS 8.5.0.12

later versions display the error message, |fpapps|
filling up the default gateway configuration.

AOS-220903 — The s flag indicating LACP striping is not displayed in ArubaOS 8.6.0.8
the output of the show ap database long command
even if LLDP is enabled on two uplinks. This issue is
observed in APs running ArubaOS 8.6.0.8 or later
versions.

AOS-221378 — The output of the show ap debug radio-stats ArubaOS 8.6.0.5

AOS-224143 command displays incorrect Rx data frame statistics.
This issue is observed in APs running ArubaOS
8.6.0.5 or later versions.

AOS-221882 — Some IPv6 clients are unable to access websites that ArubaOS 8.6.0.18
have only IPv4 addresses. This issue is observed in
Mobility Conductors running ArubaOS 8.3.0.7 or later
versions.

AOS-222493 — The AP group drop-down list in the Configuration > ArubaOS 8.7.1.3
Access Points > Campus APs page of the WebUI
takes a long time to load the list of available AP
groups. This issue is observed in Mobility Masters
running ArubaOS 8.0.0.0 or later versions.

ArubaOS 8.6.0.21 Release Notes | Release Notes Known Issues | 32

 Table 7: Known Issues in ArubaOS 8.6.0.21

Old Bug Reported

New Bug ID Description
ID Version

AOS-224463 — The RADIUS Radsec server does not work with TPM ArubaOS 8.6.0.0
certificates on Mobility Masters running ArubaOS
8.6.0.0 or later versions.

AOS-225070 — The AirGroup server table incorrectly displays ArubaOS 8.6.0.11

duplicate host names. This issue is observed in
managed devices running ArubaOS 8.6.0.11 or later
versions.

AOS-225214 — A few managed devices incorrectly send the VPNC IP ArubaOS 8.5.0.6
address as 0.0.0.0 to the AirWave server. This issue is
observed in managed devices running ArubaOS
8.5.0.6 or later versions.

AOS-226426 — The Mobility Master Hardware Appliances running ArubaOS 8.5.0.10

ArubaOS 8.5.0.10 or later versions display the
message DHCP WAIT and the menu options are
disabled. This issue occurs after a reboot.

AOS-226683 — The show running-config command does not ArubaOS 8.5.0.12

display information about the IP RADIUS source-
interface loopback. However, the show
configuration effective detail command displays
information about the IP RADIUS source-interface
loopback. This issue is observed in managed devices
running ArubaOS 8.5.0.12 or later versions.

AOS-226909 — The Configuration > Access Points page of the ArubaOS 8.6.0.9
AOS-229948 WebUI does not display the list of available APs. Also,
AOS-230436 the number of available APs differs between the
AOS-231548 WebUI and CLI. This issue is observed in Mobility
AOS-232192 Master running ArubaOS 8.6.0.9 or later versions.

AOS-227016 — Some users experience a delay while downloading ArubaOS 8.6.0.9

AOS-229420 the VIA VPN profile. This issue is observed in
managed devices running ArubaOS 8.6.0.9 or later
versions.

AOS-227458 — Some managed devices running ArubaOS 8.6.0.10 or ArubaOS 8.6.0.10

later versions log multiple DHCP-RELAY and Cannot
find Probe syslog messages.

AOS-227809 — The process monitor options could not be disabled ArubaOS 8.6.0.14
on the controllers running ArubaOS 8.6.0.14 or later
versions.

AOS-228356 — The detect-wireless-hosted-network and protect- ArubaOS 8.6.0.13

wireless-hosted-network parameters of the ids
unauthorized-device-profile command does not
work as expected in stand-alone controllers running
ArubaOS 8.6.0.13 or later versions.

33 | Known Issues ArubaOS 8.6.0.21 Release Notes | Release Notes

 Table 7: Known Issues in ArubaOS 8.6.0.21

Old Bug Reported

New Bug ID Description
ID Version

AOS-228799 — Some managed devices running ArubaOS 8.6.0.16 or ArubaOS 8.6.0.16

AOS-238163 later versions crash and reboot unexpectedly. The
log files list the reason for the event as Datapath
timeout (Fpapps Initiated).

AOS-229474 — The show ap database flags command does not ArubaOS 8.6.0.15
AOS-229582 filter the output based on the specified flags. This
AOS-229990 issue is observed in Mobility Masters running
ArubaOS 8.6.0.15 or later versions.

AOS-230475 — API enforcement issues are observed when DPI and ArubaOS 8.6.0.13
AOS-231207 WebCC rules coexist. This issue is observed in
managed devices running ArubaOS 8.6.0.13 or later
versions.

AOS-230508 — A few APs crash and reboot unexpectedly. The log ArubaOS 8.5.0.8
files list the reason for the event as kernel page
fault at virtual address 00000000, epc ==
8017d554, ra == c005e32c. This issue is observed
in APs running ArubaOS 8.5.0.8 or later versions.

AOS-232475 — Neither the no time-range command nor the ArubaOS 8.6.0.9

Configuration > Roles and Policies > <role> >
Time Range field of the WebUI allows users to
delete the configured time range. This issue is
observed in managed devices running ArubaOS
8.6.0.9 or later versions.

AOS-233809 — Users are unable to add GRE tunnels to a tunnel ArubaOS 8.6.0.8
group and an incorrect error message, Error: Tunnel
is already part of a different tunnel-group is
displayed. This issue is observed in managed devices
running ArubaOS 8.6.0.8 or later versions.

AOS-239498 — Some AP-515 access points running ArubaOS ArubaOS 8.6.0.19

8.6.0.19 or later versions crash and reboot
unexpectedly. The log files list the reason for the
event as AP Reboot reason: BadPtr:0000000f
PC:wlc_get_txh_info+0x118/0x210 [wl_v6] Warm-
reset.

AOS-242238 — A session established with a Guest SSID does not ArubaOS 8.6.0.9
AOS-241669 disconnect even after the session timeout. This issue
is observed in some controllers running ArubaOS
8.6.0.9 connected through a split-tunnel.

AOS-239814 — In some Controllersrunning ArubaOS 8.6.0.11, IPv4 ArubaOS 8.6.0.11

and IPv6 Accounting Messages are using the same
session ID with Passpoint. This causes multiple
Accounting Messages to be sent repeatedly.

ArubaOS 8.6.0.21 Release Notes | Release Notes Known Issues | 34

 Table 7: Known Issues in ArubaOS 8.6.0.21

Old Bug Reported

New Bug ID Description
ID Version

AOS-239521 — Users are unable to add a tunnel to a tunnel group ArubaOS 8.6.0.15
and an error message, Error: All tunnels must
have same vlan membership was displayed. This
issue occurs when the VLANs are configured in a
different order when compared to the order
configured for other tunnels in the same group. This
issue is observed in Managed Devicesrunning
ArubaOS 8.6.0.15 or later versions.

AOS-236721 — The Configuration > Roles & Policies > Roles page ArubaOS 8.6.0.16
of the WebUI does not display ACLs configured for
the role. However, the CLI displays the list of ACLs.
This issue is observed in Mobility Master running
ArubaOS8.6.0.16 or later versions.

AOS-228581 — Some Managed Devices running ArubaOS 8.6.0.20 or ArubaOS 8.6.0.20

AOS-228791 later versions crash and rebooted unexpectedly. The
log files list the reason for the event as Reboot
Cause: Datapath timeout (SOS Assert) (in ipsec_
decrypt). This issue occurs when the buffer memory
was queued in the wrong processor.

AOS-228502 — A Managed Device in a cluster was unable to pass ArubaOS 8.6.0.15

through manual SNMP Walk performed on Linux /
AirWaveserver. This issue is observed in managed
devices running ArubaOS 8.6.0.15 or later versions.

AOS-238817 — In some controllers running ArubaOS 8.6.0.19, the ArubaOS8.6.0.19

Dashboard>Security>Suspected Rogue and
Authorized section of the WebUI display an error
message: Error retrieving information. Please try
again later. This causes the list of APs to not to
populate correctly. This happens because non-UTF-8
characters are added to the backend.

AOS-208686 The Dashboard > Services > Wireless Calls page of ArubaOS 8.6.0.0
the WebUI, displays two different score types
without an appropriate header. The units are not the
same but are labelled as Score (Controller > Score-
and End-toEnd > Score) This issue is observed on
Mobility Controllers running ArubaOS 8.6.0.0 or later
versions

AOS-214846 The status of the APs is incorrectly displayed as ArubaOS 8.5.0.10

Down. This issue is observed in Mobility Masters
running ArubaOS 8.5.0.10 or later versions.

35 | Known Issues ArubaOS 8.6.0.21 Release Notes | Release Notes

 Chapter 8
Upgrade Procedure

Upgrade Procedure
This chapter details software upgrade procedures. It is recommended that you schedule a maintenance
window for the upgrade.

Read all the information in this chapter before upgrading your Mobility Master, managed device, or stand-alone
controller.

Important Points to Remember

To upgrade your managed device or Mobility Master:
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.
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:
l How many APs are assigned to each managed device? Verify this information by navigating to the
Dashboard > Access Points page in the WebUI, or by executing the show ap active or show ap
database commands.
l How are those APs discovering the managed device (DNS, DHCP Option, Broadcast)?
l What version of ArubaOS runs on your managed device?
l Are all managed devices running the same version of ArubaOS?
l What services are used on your managed device (employee wireless, guest access, Remote AP,
wireless voice)?
n Resolve any existing issues (consistent or intermittent) before you upgrade.
n If possible, use FTP to load ArubaOS images to the managed device. FTP is faster than TFTP and offers
more resilience over slow links. If you must use TFTP, ensure the TFTP server can send over 30 MB of
data.
n Always upgrade the non-boot partition first. If you encounter any issue during the upgrade, you can
restore the flash, and switch back to the boot partition. Upgrading the non-boot partition gives you a
smoother downgrade path, if required.
n Before you upgrade to this version of ArubaOS, assess your software license requirements and load
any new or expanded licenses that you might require. For a detailed description of these new license
modules, refer the Aruba Mobility Master Licensing Guide.
n Multiversion is supported in a topology where the managed devices are running the same version as
the Mobility Master, or two versions lower. For example multiversion is supported if a Mobility
Master is running ArubaOS 8.5.0.0 and the managed devices are running ArubaOS 8.5.0.0, ArubaOS
8.4.0.0, or ArubaOS 8.3.0.0.

ArubaOS 8.6.0.21 Release Notes | Release Notes 36

 Memory Requirements
All Aruba managed devices store critical configuration data on an onboard compact flash memory
module. Ensure that there is always free flash space on the managed device. Loading multiple large files
such as JPEG images for RF Plan can consume flash space quickly. Following are best practices for
memory management:
n Do not proceed with an upgrade unless 100 MB of free memory is available. Execute the show
memory command to identify the available free memory. To recover memory, reboot the managed
device. After the managed device comes up, upgrade immediately.
n Do not proceed with an upgrade unless the minimum flash space is available. Execute the show
storage command to identify the available flash space. 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 managed device to a desired location. Delete the following files
from the managed device to free some memory:
l 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 on page 37 to copy the crash.tar file to
an external server. Execute the tar clean crash command to delete the file from the managed
device.
l Flash backups: Use the procedures described in Backing up Critical Data on page 37 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 managed device.
l 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 on page 37 to copy the logs.tar file to an
external server. Execute the tar clean logs command to delete the file from the managed device.

In certain situations, a reboot or a shutdown could cause the managed device to lose the information stored in
its flash memory. To avoid such issues, it is recommended that you execute the halt command before power
cycling.

Deleting a File
You can delete a file using the WebUI or CLI.

In the WebUI
From the Mobility Master, navigate to Diagnostic > Technical Support > Delete Files and remove any
aging log files or redundant backups.

In the CLI
(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

37 | Upgrade Procedure ArubaOS 8.6.0.21 Release Notes | Release Notes

 n x.509 certificates
n Log files
n Flash backup

Backing up and Restoring Flash Memory

You can backup and restore the flash memory using the WebUI or CLI.

In the WebUI
The following steps describe how to back up and restore the flash memory:
1. In the Mobility Master node hierarchy, navigate to the Maintenance > Configuration
Management > Backup page.
2. Click Create Backup to backup the contents of the flash memory to the flashbackup.tar.gz file.
3. Click Copy Backup to copy the file to an external server.
You can copy the backup file from the external server to the flash memory using the file utility in the
Diagnostics > Technical Support > Copy Files page.
4. To restore the backup file to the flash memory, navigate to the Maintenance > Configuration
Management > Restore page and click Restore.

In the CLI
The following steps describe how to back up and restore the flash memory:
1. Execute the following command in the enable mode:
(host) #write memory
2. 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.
3. Execute either of the following command to transfer the flash backup file to an external server or
storage device.
(host) #copy flash: flashbackup.tar.gz ftp: <ftphost> <ftpusername> <ftpuserpassword>
<remote directory>

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

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

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

4. 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 ArubaOS

ArubaOS 8.6.0.21 Release Notes | Release Notes Upgrade Procedure | 38

 Upgrade ArubaOS using the WebUI or CLI.

Ensure that there is enough free memory and flash space on your Mobility Master or managed device. For
details, see Memory Requirements on page 37.

When you navigate to the Configuration tab in the WebUI, the managed device might display the Error getting
information: command is not supported on this platform message. This message is displayed ccurs when
you upgrade using the WebUI and navigate to the Configuration tab after the managed device reboots. This
message disappears after clearing the Web browser cache.

In the WebUI
The following steps describe how to upgrade ArubaOS from a TFTP server, FTP server, or local file.
1. Download the ArubaOS image from the customer support site.
2. Upload the ArubaOS image to a PC or workstation on your network.
3. Validate the SHA hash for the ArubaOS image:
a. Download the Aruba.sha256 file from the download directory.
b. Load the ArubaOS image to a Linux system and execute the sha256sum <filename>
command. Alternatively, use a suitable tool for your operating system that can generate a
SHA256 hash of a file.
c. Verify that the output produced by this command matches the hash value found on the
customer support site.

The ArubaOS image file is digitally signed and is verified using RSA2048 certificates preloaded at the factory. The
Mobility Master or managed device will not load a corrupted ArubaOS image.

4. Log in to the ArubaOS WebUI from the Mobility Master.

5. Navigate to the Maintenance > Software Management > Upgrade page.
a. Select the Local File option from the Upgrade using drop-down list.
b. Click Browse from the Image file name to navigate to the saved image file on your PC or
workstation.
6. Select the downloaded image file.
7. Choose the partition from the Partition to Upgrade option.
8. Enable the Reboot Controller After Upgrade toggle switch to automatically reboot after
upgrading. If you do not want to reboot immediately, disable this option.

The upgrade does not take effect until reboot. If you chose to reboot after upgrade, the Mobility Master or
managed device reboots automatically.

9. Select Save Current Configuration.

10. Click Upgrade.
11. Click OK, when the Changes were written to flash successfully message is displayed.

In the CLI
The following steps describe how to upgrade ArubaOS from a TFTP server, FTP server, or local file.
1. Download the ArubaOS image from the customer support site.
2. Open an SSH session to your Mobility Master.

39 | Upgrade Procedure ArubaOS 8.6.0.21 Release Notes | Release Notes

 3. Execute the ping command to verify the network connection between the Mobility Master and the
SCP server, FTP server, or TFTP server.
(host)# ping <ftphost>
or
(host)# ping <tftphost>
or
(host)# ping <scphost>
4. Execute the show image version command to check if the ArubaOS image is loaded on the flash
partition. The partition number appears in the Partition row; 0:0 is partition 0, and 0:1 is partition 1.
The active boot partition is marked as Default boot.
(host) #show image version
5. Execute the copy command to load the new image to the non-boot partition.
(host)# copy ftp: <ftphost> <ftpusername> <image filename> system: partition <0|1>
or
(host)# copy tftp: <tftphost> <image filename> system: partition <0|1>
or
(host)# copy scp: <scphost> <scpusername> <image filename> system: partition <0|1>
or
(host)# copy usb: partition <partition-number> <image filename> system: partition
<0|1>
6. Execute the show image version command to verify that the new image is loaded.
(host)# show image version
7. Reboot the Mobility Master.
(host)#reload
8. Execute the show version command to verify that the upgrade is complete.
(host)#show version

Verifying the ArubaOS Upgrade

Verify the ArubaOS upgrade in the WebUI or CLI.

In the WebUI
The following steps describe how to verify that the Mobility Master is functioning as expected:
1. Log in to the WebUI and navigate to the Dashboard > WLANs page to verify the ArubaOS image
version.
2. Verify if all the managed devices are up after the reboot.
3. Navigate to the Dashboard > Access Points page to determine if your APs are up and ready to
accept clients.
4. Verify that the number of APs and clients are as expected.
5. Test a different type of client in different locations, for each access method used.
6. Complete a backup of all critical configuration data and files on the flash memory to an external
server or mass storage facility. See Backing up Critical Data on page 37 for information on creating a
backup.

In the CLI

ArubaOS 8.6.0.21 Release Notes | Release Notes Upgrade Procedure | 40

 The following steps describe how to verify that the Mobility Master is functioning as expected:
1. Log in to the CLI to verify that all your managed devices are up after the reboot.
2. Execute the show version command to verify the ArubaOS image version.
3. Execute the show ap active command to determine if your APs are up and ready to accept
clients.
4. Execute the show ap database command to verify that the number of APs and clients are as
expected.
5. Test a different type of client in different locations, for each access method used.
6. Complete a backup of all critical configuration data and files on the flash memory to an external
server or mass storage facility. See Backing up Critical Data on page 37 for information on creating a
backup.

Downgrading ArubaOS
A Mobility Master or managed device has two partitions, 0 and 1. If the upgrade fails on one of the
partitions, you can reboot the Mobility Master or managed device from the other partition.

Pre-requisites
Before you reboot the Mobility Master or managed device with the pre-upgrade ArubaOS version,
perform the following steps:
1. Back up your Mobility Master or managed device. For details, see Backing up Critical Data on page
37.
2. Verify that the control plane security is disabled.
3. Set the Mobility Master or managed device to boot with the previously saved configuration file.
4. Set the Mobility Master or managed device to boot from the partition that contains the pre-
upgrade ArubaOS version.
When you specify a boot partition or copy an image file to a system partition, Mobility Master or
managed device checks if the ArubaOS version is compatible with the configuration file. An error
message is displayed if the boot parameters are incompatible with the ArubaOS version and
configuration files.
5. After switching the boot partition, perform the following steps:
n Restore the pre-upgrade flash backup from the file stored on the Mobility Master or managed
device. Do not restore the ArubaOS flash backup file.
n Do not import the WMS database.
n If the RF plan is unchanged, do not import it. If the RF plan was changed before switching the boot
partition, the changed RF plan does not appear in the downgraded ArubaOS version.
n If any new certificates were added in the upgraded ArubaOS version, reinstall these certificates in
the downgraded ArubaOS version.
Downgrade ArubaOS version using the WebUI or CLI.

In the WebUI
The following steps describe how to downgrade the ArubaOS version:
1. If the saved pre-upgrade configuration file is on an external FTP or TFTP server, copy the file to the
Mobility Master or managed device by navigating to the Diagnostics > Technical Support > Copy
Files page.

41 | Upgrade Procedure ArubaOS 8.6.0.21 Release Notes | Release Notes

 a. From Select source file drop-down list, select FTP or TFTP server, and enter the IP address of
the FTP or TFTP server and the name of the pre-upgrade configuration file.
b. From Select destination file drop-down list, select Flash file system, and enter a file name
(other than default.cfg).
c. Click Copy.
2. Determine the partition on which your pre-upgrade ArubaOS version is stored by navigating to the
Maintenance > Software Management > Upgrade page. If a pre-upgrade ArubaOS version is not
stored on your system partition, load it into the backup system partition by performing the following
steps:

You cannot load a new image into the active system partition.

a. Enter the FTP or TFTP server address and image file name.
b. Select the backup system partition.
c. Enable Reboot Controller after upgrade.
d. Click Upgrade.
3. Navigate to the Maintenance > Software Management > Reboot page, select Save
configuration before reboot, and click Reboot.
The Mobility Master or managed device reboots after the countdown period.
4. When the boot process is complete, verify that the Mobility Master or managed device is using the
correct ArubaOS version by navigating to the Maintenance > Software Management > About
page.

In the CLI
The following steps describe how to downgrade the ArubaOS version:
1. If the saved pre-upgrade configuration file is on an external FTP or TFTP server, use the following
command to copy it to the Mobility Master or managed device:
(host) # copy ftp: <ftphost> <ftpusername> <image filename> system: partition 1
or
(host) # copy tftp: <tftphost> <image filename> system: partition 1
2. Set the Mobility Master or managed device to boot with your pre-upgrade configuration file.
(host) # boot config-file <backup configuration filename>
3. Execute the show image version command to view the partition on which your pre-upgrade
ArubaOS version is stored.
(host) #show image version

You cannot load a new image into the active system partition.

4. Set the backup system partition as the new boot partition.

(host) # boot system partition 1
5. Reboot the Mobility Master or managed device.
(host) # reload
6. When the boot process is complete, verify that the Mobility Master or managed device is using the
correct ArubaOS version.
(host) # show image version

ArubaOS 8.6.0.21 Release Notes | Release Notes Upgrade Procedure | 42

 Before Calling Technical Support
Provide the following information when you call the Technical Support:
n The status of installation (new or existing) and recent changes to network, device, or AP
configuration. If there was a configuration change, list the exact configuration steps and commands
used.
n A detailed network topology including all the devices in the network with IP addresses and interface
numbers.
n The make and model number of the wireless device and NIC, driver date, version, and configuration
of the NIC, and the OS version including any service packs or patches.
n The logs and output of the show tech-support command.
n The syslog file at the time of the problem.
n The date and time when the problem first occurred. If the problem is reproducible, list the exact
steps taken to re-create the problem.
n Any wired or wireless sniffer traces taken during the time of the problem.
n The device site access information.

43 | Upgrade Procedure ArubaOS 8.6.0.21 Release Notes | Release Notes