3 дня назад — ... guides are part of the complete documentation for the Aruba user-centric network: ▫. ArubaOS Getting Started Guide. ▫. ArubaOS User Guide. ▫. ArubaOS CLI ...
ArubaOS 8.6.0.3 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 New Features and Enhancements in ArubaOS 8.6.0.3 7 CLI 7 IPv6 7 LLDP 7 Supported Platforms in ArubaOS 8.6.0.3 8 Mobility Master Platforms 8 Mobility Controller Platforms 8 AP Platforms 8 Regulatory Updates in ArubaOS 8.6.0.3 11 Resolved Issues in ArubaOS 8.6.0.3 12 Known Issues in ArubaOS 8.6.0.3 30 Limitation 30 Known Issues 30 Upgrade Procedure 39 Important Points to Remember 39 Memory Requirements 40 Backing up Critical Data 40 Upgrading ArubaOS 41 Verifying the ArubaOS Upgrade 43 Downgrading ArubaOS 44 Before Calling Technical Support 46 ArubaOS 8.6.0.3 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 16 Added limitation on Airtime Fairness Mode. Revision 15 The bug AOS-153742 has been removed from the Known Issues section. Revision 14 The bug AOS-198306 has been added to the Resolved Issues chapter. Revision 13 AP-303P has been added to the list of Supported Platforms. Revision 12 The bug, AOS-192568 has been removed from the Known Issues and Limitations section. Revision 11 Moved AOS-187448 from the Known Issues table to the Limitations section. Revision 10 Added AOS-207237 as a known issue. Revision 09 Added AOS-187448 as a known issue. Revision 08 Updated the Important Points to Remember section. Revision 07 The bug AOS-155037 has been removed from the Known Issues and Limitations chapter. Revision 06 The bug AOS-183743 has been removed from the Known Issues and Limitations chapter. Revision 05 Removed the Migrating from ArubaOS 6.x to ArubaOS 8.x section from Upgrade Procedure as the Migration Tool is no longer supported. Revision 04 AOS-202577 has been added as a known issue. Revision 03 A note has been added to the bug, AOS-190230. Revision 02 WPA and WPA2 Disassociation Vulnerability has been added to the Resolved issues section. Revision 01 Initial release. ArubaOS 8.6.0.3 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 Microsoft Edge (Microsoft Edge 92.0.902.62 and Microsoft EdgeHTML 18.19041) or later Firefox 107.0.1 or later Apple Safari 15.4 (17613.17.1.13) or later Google Chrome 108.0.5359.71 or later Operating System n Windows 10 or later n macOS n Windows 10 or later n macOS n macOS n Windows 10 or later n macOS Terminology Change ArubaOS 8.6.0.3 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 Campus Access Points + Controllers Instant Access Points Switch Stack Wireless LAN Controller Firewall Configuration Types of Hackers Old Language Master-Slave Master-Slave Master-Slave Mobility Master Blacklist, Whitelist Black Hat, White Hat New Language Conductor-Member Conductor-Member Conductor-Member Mobility Conductor Denylist, Allowlist 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: aruba-sirt@hpe.com 6 | Release Overview ArubaOS 8.6.0.3 Release Notes | Release Notes Chapter 3 New Features and Enhancements in ArubaOS 8.6.0.3 New Features and Enhancements in ArubaOS 8.6.0.3 This chapter describes the features and enhancements introduced in this release. CLI A new parameter, network is added to the airgroupprofile command. The networkdefault is enabled whenever an airgroupprofile is configured in either distributed or centralized mode. This parameter allows the users to, n Block or blacklist the client or server based on the MAC address or MAC OUI. n Limit the number of maximum allowed IP addresses per server. n Limit the number of maximum tokens allowed per server or client. The following are the limitation of the networkdefault parameter: n User defined network profile is not supported. n The default network profile is always enabled and cannot be disabled when any airgroupprofile is activated. n The default network profile can be modified only from /md hierarchy node. n In case of multiple islands, the network profile is activated only to the island where the airgroupprofile is activated. (host) [md] (config) #airgroupprofile network default (host) [md] (Network profile "default") #blacklist-mac <macaddr> (host) [md] (Network profile "default") #max-ip-per-device <number of ip addresses> (host) [md] (Network profile "default") #max-tokens-per-device <number of tokens> IPv6 Network Advertisement Starting from ArubaOS 8.6.0.3, a stand-alone controller sends the network advertisement to the MAC address available in Source Link-Layer Address option. LLDP Starting from ArubaOS 8.6.0.3, when an AP is in active-standby mode, LLDP packets transmitted from eth1 interface will use eth1's hardware address as Layer-2 source MAC address. ArubaOS 8.6.0.3 Release Notes | Release Notes 7 Chapter 4 Supported Platforms in ArubaOS 8.6.0.3 Supported Platforms in ArubaOS 8.6.0.3 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.3 Mobility Master Family Hardware Mobility Master Mobility Master Model MM-HW-1K, MM-HW-5K, MM-HW-10K Virtual Mobility Master MM-VA-50, MM-VA-500, MM-VA-1K, MM-VA-5K, MM-VA-10K 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.3 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.2 AP Family AP Model 100 Series AP-104, AP-105 103 Series AP-103 ArubaOS 8.6.0.3 Release Notes | Release Notes 8 Table 5: Supported AP Platforms in ArubaOS 8.6.0.2 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 in ArubaOS 8.6.0.3 ArubaOS 8.6.0.3 Release Notes | Release Notes Table 5: Supported AP Platforms in ArubaOS 8.6.0.2 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.3 Release Notes | Release Notes Supported Platforms in ArubaOS 8.6.0.3 | 10 Chapter 5 Regulatory Updates in ArubaOS 8.6.0.3 Regulatory Updates in ArubaOS 8.6.0.3 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 <countrycode> 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_74492 ArubaOS 8.6.0.3 Release Notes | Release Notes 11 Chapter 6 Resolved Issues in ArubaOS 8.6.0.3 Resolved Issues in ArubaOS 8.6.0.3 This release includes fix for WPA and WPA2 Disassociation Vulnerability documented in CVE-201915126. This vulnerability affects 200 Series, 340 Series , 500 Series, and 510 Series access points. Also, the following issues are resolved in this release. Table 6: Resolved Issues in ArubaOS 8.6.0.3 New Bug ID AOS-137577 AOS-139523 AOS-145692 AOS-196723 AOS-156424 AOS-156777 AOS-185158 AOS-193880 AOS-198034 AOS-198568 AOS-157882 AOS-200009 Old Bug ID 167045 169550 177729 192581 193081 Description The authentication process in a Mobility Master crashed and the WebUI of the Mobility Master was inaccessible. This issue occurred when the show global-usertable command was executed. The fix ensures that the Mobility Master works as expected. This issue was observed in Mobility Masters running ArubaOS 8.3.0.0 or later versions. Invalid SSIDs were displayed in the Dashboard > WLAN page in the WebUI. This issue occurred when a few APs were broadcasting invalid SSIDs. The fix ensures that the WebUI displays only the valid SSIDs. This issue was observed in managed devices running ArubaOS 8.2.2.0 or later versions. Reported Version ArubaOS 8.3.0.0 ArubaOS 8.2.2.0 194655 The Dashboard > Overview > Clients page displayed incorrect roles for wired clients connected to a Remote AP. The fix ensures that the WebUI displays the correct role for wired clients. This issue was observed in stand-alone controllers running ArubaOS 8.4.0.0 or later versions. ArubaOS 8.4.0.0 AOS-182579 AOS-195790 AOS-196493 AOS-197868 AOS-197989 -- APs and clients got disconnected frequently from the ArubaOS managed device. This issue occurred when heartbeats 8.3.0.2 were randomly missed on the managed device. The fix ensures seamless connectivity. This issue was observed in managed devices running ArubaOS 8.3.0.2 or later versions in a cluster setup. AOS-185212 AOS-185375 -- The Authentication process crashed in a 7240 ArubaOS standalone controller running ArubaOS 8.3.0.0 or later 8.3.0.0 versions. The fix ensures that the controller works as expected. This issue was observed in 7240 controllers running ArubaOS 8.3.0.0 or later versions. AOS-188271 AOS-196680 AOS-197718 -- A few AP-515 access points running ArubaOS 8.5.0.0 or ArubaOS later versions crashed and rebooted unexpectedly. 8.5.0.0 The fix ensures that the access points work as expected. ArubaOS 8.6.0.3 Release Notes | Release Notes 12 Table 6: Resolved Issues in ArubaOS 8.6.0.3 New Bug ID Old Bug ID Description Reported Version AOS-188360 -- The show configuration effective detail command ArubaOS displayed incorrect device level configuration 8.3.0.0 hierarchy. The fix ensures that the correct device level configuration hierarchy is displayed. This issue was observed in Mobility Masters running ArubaOS 8.3.0.7 or later versions. AOS-189118 AOS-200233 -- VIA clients running ArubaVIA version 3.2 and 3.4 were ArubaOS unable to establish connection with the controller 8.3.0.1 through SSL fallback mode and the following error messages were displayed: n Controller is not responding n UDP packets are dropped n SSL tunneling could not be turned on This issue occurred when UDP port 4500 was blocked. The fix ensures that the clients can establish connection with the controller through SSL fallback mode. This issue was observed in Mobility Masters running ArubaOS 8.3.0.1 or later versions. AOS-189476 AOS-192948 -- The managed device displayed the error message ArubaOS authmgr[8721]: <522349> <8721> <DBUG> 8.5.0.1 |authmgr| MAC 04:bd:88:c4:d7:6a IP 10.128.10.45: drop pkt non-DHCP pkt, Option-12 hostname needed for accounting while configuring aaa profile user name with dhcp option 12 flag enabled and the user-table was also not updated. The fix ensures that the user table is updated and the managed device does not show the error message. This issue was observed in managed devices running ArubaOS 8.5.0.0 or later versions. AOS-190230 AOS-194760 -- A few Remote APs failed to come up on the managed ArubaOS device after an AP reboot. These Remote APs were 8.4.0.0 assigned the same inner IP addresses which were already assigned to other Remote APs. This issue occurred when most of the Remote AP whitelist database entries were deleted from the Mobility Master. The fix ensures that the Remote APs work as expected. This issue was observed in APs running ArubaOS 8.4.0.0 or later versions. NOTE: Aruba recommends that you reconfigure lcrap-pool on /mm node or purge whitelist database entries on Mobility Master and managed device before upgrading to the latest version. AOS-190380 AOS-196361 -- A few users were unable to connect to VIA server from ArubaOS the guest account. This issue occurred when PBR was 8.0.0.0 not applied to data packets from UDP port 4500 . As a result, the client traffic was not forwarded correctly. The fix ensures that the users are able to connect to the VIA server. This issue was observed in managed devices running ArubaOS 8.0.0.0 or later versions. 13 | Resolved Issues in ArubaOS 8.6.0.3 ArubaOS 8.6.0.3 Release Notes | Release Notes Table 6: Resolved Issues in ArubaOS 8.6.0.3 New Bug ID Old Bug ID Description Reported Version AOS-190927 AOS-192132 -- A few managed devices running ArubaOS 8.4.0.4 or ArubaOS later versions became unresponsive without console 8.4.0.4 access. This issue was observed due to STM process memory leak. The fix ensures that the managed devices work as expected. AOS-191348 -- Client was unable to load the captive portal page. This ArubaOS issue occurred in a system with proxy settings. The fix 8.3.0.7 ensures that the captive portal page loads without any issue. This issue was observed in managed devices running ArubaOS 8.3.0.7 or later versions. AOS-191549 -- Users were unable to discover Apple TV. The issue ArubaOS occurred when AirGroup was enabled in Centralized 8.4.0.3 mode. The fix ensures that users are able to discover Apple TV. This issue was observed in the Mobility Masters running ArubaOS 8.4.0.3 or later versions. AOS-192005 -- A managed device was in CONFIG FAILURE state and ArubaOS displayed the error message, Module CERT 8.4.0.4 DOWNLOAD MANAGER PORT is busy. Please try later. This issue occurred while uploading server certificate for captive portal authentication. The fix ensures that the managed device works as expected. This issue was observed in managed devices running ArubaOS 8.4.0.4 or later versions. AOS-192163 -- A managed device crashed and rebooted ArubaOS unexpectedly. The log file listed the reason for this 8.3.0.4 event as Datapath timeout (SOS Assert) (Intent:cause:register 54:86:50:2). The fix ensures that the managed device works as expected. This issue was observed in managed devices running ArubaOS 8.3.0.4 or later versions. AOS-192274 -- The command show running-config did not display ArubaOS LACP related information. The fix ensures that the 8.3.0.8 show running-config command display LACP related information. This issue was observed in Mobility Masters running ArubaOS 8.3.0.8 or later versions. AOS-192814 AOS-199107 -- The Auto Associate feature of AirGroup did not work ArubaOS as expected and AP related information on AirGroup 8.3.0.7 server was incorrect when clients roamed between different managed devices.The fix ensures that the feature works as expected. This issue occurred when GSM entries were not updated. This issue was observed in managed devices running ArubaOS 8.3.0.7 or later versions in centralized or distributed mode. AOS-193046 AOS-196703 -- Master IP configuration details were missing on the ArubaOS managed device and the managed device acted as a 8.3.0.0 stand-alone controller. The fix ensures that the managed device works as expected. This issue was observed in managed devices running ArubaOS 8.3.0.0 or later devices. ArubaOS 8.6.0.3 Release Notes | Release Notes Resolved Issues in ArubaOS 8.6.0.3 | 14 Table 6: Resolved Issues in ArubaOS 8.6.0.3 New Bug ID Old Bug ID Description Reported Version AOS-193320 -- Aruba SFP J8177D transceiver did not work with ArubaOS 7205controllers. The fix ensures that the SFP J8177D 8.3.0.7 transceiver works with 7205controllers. This issue was observed in 7205controllers running ArubaOS 8.3.0.7 or later versions. AOS-193362 AOS-198030 -- A Mobility Master was unable to establish connection ArubaOS with AirWave. This issue occurred when AirWave was 8.3.0.7 not reachable from the management interface. The fix ensures that the Mobility Master works as expected. This issue was observed in Mobility Master Hardware Appliance running ArubaOS 8.3.0.7 or later versions. AOS-193425 -- GSM entries were missing on the Mobility Master for ArubaOS some wireless users. The fix ensures that the GSM 8.3.0.7 entries are available for the wireless users. This issue was observed in managed devices running ArubaOS 8.3.0.7 or later versions in a cluster setup. AOS-193744 AOS-198906 -- The mcell process was in PROCESS_NOT_ ArubaOS RESPONDING state after configuring master- 8.5.0.2 redundancy on a standby Mobility Master. This issue occurred due to connectivity issue between active Mobility Master and the standby Mobility Master. The fix ensures that the process work as expected. This issue was observed in Mobility Masters running ArubaOS 8.5.0.2 or later versions. AOS-193888 -- A few APs rebooted unexpectedly. This issue occurred ArubaOS when the controller IP address was incorrect in a non- 8.5.0.1 cluster datazone setup. The fix ensures that the APs work as expected. This issue was observed in access points running ArubaOS 8.5.0.1 or later versions. AOS-193976 -- APs rebooted unexpectedly. The log file listed the ArubaOS reason for the event as Critical process 8.5.0.1 /aruba/bin/sapd [pid XXXX] DIED, process marked as RESTART. This issue occurred when the AP fails over to HA standby. The fix ensures that the APs work as expected. This issue was observed in access points running ArubaOS 8.1.0.0 or later versions. AOS-194052 -- A few clients were unable to obtain IP addresses. This ArubaOS issue occurred when High Efficiency was enabled on 8.5.0.2 the WPA2-PSK SSID profile of the APs. The fix ensures that the clients are able to obtain the IP addresses. This issue was observed in Mobility Controller Virtual Appliances running ArubaOS 8.5.0.0 or later versions. 15 | Resolved Issues in ArubaOS 8.6.0.3 ArubaOS 8.6.0.3 Release Notes | Release Notes Table 6: Resolved Issues in ArubaOS 8.6.0.3 New Bug ID Old Bug ID Description Reported Version AOS-194146 -- A managed device did not display any warning ArubaOS message when the cluster profile name contained 8.5.0.2 more than 32 characters. The fix ensures that the managed device displays a warning message when the cluster profile name exceeds 32 characters. This issue was observed in managed devices running ArubaOS 8.5.0.2 or later versions in a cluster setup. AOS-194201 -- The value of Tx data bytes transmitted for 5 GHz radio ArubaOS was lesser than the actual transmitted value. The fix 8.3.0.0 ensures that the actual values are transmitted for 5 GHz radio. This issue was observed in AP-205 access points running ArubaOS 8.3.0.0 or later versions. AOS-194250 -- The Configuration > Interfaces > VLANs page did ArubaOS not display the list of VLANs. This issue occurred when 8.5.0.2 a new VLAN ID was configured using the WebUI. The fix ensures that the WebUI displays the list of VLANs configured. This issue was observed in managed devices running ArubaOS 8.5.0.2 or later versions. AOS-194325 AOS-194579 -- The datapath process in a managed device crashed ArubaOS multiple times. The fix ensures that the managed 8.3.0.7 device works as expected. This issue was observed in managed devices running ArubaOS 8.3.0.0 or later versions in a Mobility Master-Managed Device topology. AOS-194706 -- A managed device crashed and rebooted ArubaOS unexpectedly. The log files listed the reason for the 8.5.0.2 event as Reboot Cause: Datapath timeout (SOS Assert) (Intent:cause:register 54:86:50:4). The fix ensures that the managed device works as expected. This issue was observed in managed devices running ArubaOS 8.5.0.2 or later versions in a Mobility Master- Managed Device topology. AOS-194727 -- An AP sent RTS requests continuously to one client ArubaOS only and this resulted in a delay or packet drop to 8.3.0.7 other clients. This issue was observed in 340 Series access points running ArubaOS 8.3.0.7 or later versions. AOS-194785 -- AP was unable to failover to a backup LMS controller ArubaOS and the AP rebooted with the error, Unable to set up 8.3.0.8 IPSec tunnel after 24 tries. The fix ensures that the APs work as expected. This issue was observed in AP- 375 access points connected to stand-alone controllers running ArubaOS 8.3.0.8 or later versions. ArubaOS 8.6.0.3 Release Notes | Release Notes Resolved Issues in ArubaOS 8.6.0.3 | 16 Table 6: Resolved Issues in ArubaOS 8.6.0.3 New Bug ID Old Bug ID Description Reported Version AOS-194795 AOS-197097 AOS-201048 -- A managed device did not perform RADIUS ArubaOS authentication. The log file listed the reason for the 8.3.0.0 event as Failed to send the radius request for Station. The fix ensures that the managed device works as expected. This issue was observed in managed devices running ArubaOS 8.3.0.0 or later versions. AOS-194813 AOS-198001 AOS-199579 AOS-200149 AOS-200648 AOS-201658 -- The mDNS process crashed and rebooted on a ArubaOS Mobility Master Virtual Appliance unexpectedly. This 8.3.0.8 issue occurred due to memory leak. The fix ensures that the Mobility Master Virtual Appliance works as expected. This issue was observed in Mobility Master Virtual Appliance running ArubaOS 8.3.0.8 or later versions. AOS-194874 -- High temperature was observed in CPU sensors. The ArubaOS fix ensures that the Mobility Master Hardware 8.3.0.4 Appliance works as expected. This issue was observed in Mobility Master Hardware Appliances running ArubaOS 8.3.0.4 or later versions. AOS-194962 -- Some clients were unable to connect to the 2.4 GHz ArubaOS radio channel. This issue occurred when clients 8.3.0.0 disabled the 2.4 GHz radio and enabled it again, causing the 802.11r SSID profile to get disabled between connections. The fix ensures that the clients can connect to the 2.4 GHz radio channel. This issue was observed in APs running ArubaOS 8.3.0.0 or later versions. AOS-195000 -- A few APs crashed unexpectedly. The log files listed ArubaOS the reason for the event as Kernel panic: softlockup 8.5.0.1 - hung tasks. The fix ensures that the APs work as expected. This issue was observed in AP-515 access points running ArubaOS 8.5.0.1 or later versions. AOS-195036 -- The authentication process in a managed device ArubaOS crashed unexpectedly. The fix ensures that the 8.3.0.6 managed device works as expected. This issue was observed in managed devices running ArubaOS 8.3.0.0 or later versions. AOS-195146 -- Allowed vlan did not work when wired-ap profile is ArubaOS enabled with the ports set to trunk mode. This issue 8.6.0.0 was observed in 530 Series and 550 Series access points running ArubaOS 8.6.0.0 or later versions. 17 | Resolved Issues in ArubaOS 8.6.0.3 ArubaOS 8.6.0.3 Release Notes | Release Notes Table 6: Resolved Issues in ArubaOS 8.6.0.3 New Bug ID Old Bug ID Description Reported Version AOS-195162 -- The WebUI was unresponsive and the licenses were ArubaOS not visible in the Mobility Master > Configuration > 8.5.0.1 Licenses page in the WebUI. This issue occurred when 29 non-default pools were configured and enabled. The fix ensures that the WebUI is responsive and the licenses are visible. This issue was observed in Mobility Masters running ArubaOS 8.5.0.1 or later versions. AOS-195163 AOS-197980 -- The ofc_cli_agent process in a Mobility Master ArubaOS crashed unexpectedly. This issue occurred due to 8.5.0.4 mongo database buffer corruption. The fix ensures that the Mobility Master works as expected. This issue was observed in Mobility Masters running ArubaOS 8.5.0.4 or later versions. AOS-195265 -- A managed device crashed and rebooted ArubaOS unexpectedly. The log files listed the reason for the 8.5.0.3 event as Datapath timeout (SOS Assert) (Intent:cause:register 54:86:50:2). This issue occurred due to ACL corruption. The fix ensures that the managed device works as expected. This issue was observed in managed devices running ArubaOS 8.5.0.0 or later versions. AOS-195322 AOS-198279 -- The authentication module crashed on a managed ArubaOS device. This issue occurred due to memory leak. The 8.3.0.7 fix ensures that the managed device works as expected. This issue was observed in managed devices running ArubaOS 8.3.0.7 or later versions. AOS-195414 AOS-198954 -- The profmgr process crashed on a controller. This ArubaOS issue occurred when interface access mode was 8.3.0.10 configured on the Mobility Master. The fix ensures that the Mobility Master works as expected. This issue was observed in 7008 controllers running ArubaOS 8.3.0.10 or later versions. AOS-195444 -- A managed device crashed and rebooted ArubaOS unexpectedly. The log file listed the reason for the 8.5.0.1 event as Datapath timeout (Fpapps Initiated) (Intent:cause:register 51:86:50:60). This issue occurred due to high CPU utilization. The fix ensures that the managed device works as expected. This issue was observed in managed devices running ArubaOS 8.5.0.1 or later versions. ArubaOS 8.6.0.3 Release Notes | Release Notes Resolved Issues in ArubaOS 8.6.0.3 | 18 Table 6: Resolved Issues in ArubaOS 8.6.0.3 New Bug ID Old Bug ID Description Reported Version AOS-195525 -- A few managed devices that were visible in the ArubaOS Services > Clusters page in the WebUI were not 8.5.0.3 visible when the upgrade cluster task is performed using Configuration > Tasks > Upgrade Cluster page. The fix ensures that the WebUI displays the managed devices in the Configuration > Tasks > Upgrade Cluster page. This issue was observed in managed devices running ArubaOS 8.5.0.3 or later versions. AOS-195546 AOS-199490 AOS-199985 -- Memory leak was observed in mDNS process. This ArubaOS issue occurred when AirGroup was enabled in 8.5.0.5 distributed mode. The fix ensures that the process works as expected. This issue was observed in managed devices running ArubaOS 8.5.0.5 or later versions. AOS-195589 AOS-196087 -- Profmgr process crashed unexpectedly in a Mobility ArubaOS Master. This issue occurred when the VLAN 8.3.0.4 commands entered exceeded 256 characters. The fix ensures that the Mobility Master process works as expected. This issue was observed in Mobility Masters running ArubaOS 8.3.0.4 or later versions in a cluster- setup. AOS-195968 -- Remote APs could not connect to the managed device ArubaOS after a failover. This issue occurred when PSK 8.3.0.8 authentication was used to provision a Remote AP. The fix ensures that the Remote APs are able to connect to the managed device seamlessly. This issue was observed in managed devices running ArubaOS 8.3.0.8 or later versions. AOS-195600 -- Users were unable to discover Apple TV. The issue ArubaOS occurred because AirGroup mDNS packet sessions 8.3.0.8 were flagged with 'o' flags during a Skype call initiation by UCC when AirGroup was enabled in Centralized mode. The fix ensures that users are able to discover Apple TV. This issue was observed in the Mobility Masters running ArubaOS 8.3.0.8 or later versions. Duplicates: AOS-197877, AOS-199006, AOS-199741, AOS-199284, AOS-200095, AOS-200188, and AOS- 200406 AOS-195677 AOS-196311 -- The airmatch_recv process crashed unexpectedly in a ArubaOS Mobility Master. The fix ensures that the Mobility 8.3.0.7 Master works as expected. This issue was observed in Mobility Masters running ArubaOS 8.3.0.0 or later versions in a Mobility Master-Managed Device topology. 19 | Resolved Issues in ArubaOS 8.6.0.3 ArubaOS 8.6.0.3 Release Notes | Release Notes Table 6: Resolved Issues in ArubaOS 8.6.0.3 New Bug ID Old Bug ID Description Reported Version AOS-195688 -- Some APs frequently detected wrong radars in a high ArubaOS density deployment. The issue was observed only on 8.3.0.0 JP3 regulatory domain. Enhancements to the wireless driver resolved this issue. This issue was observed in AP-325 access points running ArubaOS 8.3.0.0 or later versions. AOS-195749 AOS-195940 AOS-199401 AOS-200278 -- The mDNS module crashed on a Mobility Master. The ArubaOS fix ensures that the Mobility Master works as 8.5.0.3 expected. This issue was observed in Mobility Masters running ArubaOS 8.5.0.3 or later versions. AOS-195789 -- An AP reported high channel usage on 5Ghz radio. ArubaOS This issue occurred due to a configuration error. The 8.4.0.1 fix ensures that the access points work as expected. This issue was observed in AP-377 access points running ArubaOS 8.4.0.1 or later versions. AOS-195835 -- The CLI command firewall attack-rate arp did not ArubaOS allow the users to configure attack rate with any value 8.4.0.4 higher than 1024. The fix ensures that users can configure any value between 1-16384. This issue was observed in managed devices running ArubaOS 8.4.0.4 or later versions. AOS-195839 -- A VIA client could not auto-upgrade. This issue ArubaOS occurred when the VIA client was terminated to a 8.3.0.0 Mobility Controller Virtual Appliance. The fix ensures that the auto-upgrade feature works as expected. This issue was observed in managed devices running ArubaOS 8.0.0.0 or later versions. AOS-195947 -- APs crashed and rebooted unexpectedly. The log file ArubaOS listed the reason for the event as Kernel panic - not 8.6.0.0 syncing: Take care of the TARGET ASSERT first. This issue occurred due to kernel buffer. This issue was observed in tri-radio enabled AP-555 access points running ArubaOS 8.6.0.0 or later versions. AOS-196043 -- A mismatch of 802.11r configuration was observed ArubaOS between a Mobility Master and the managed devices, 8.4.0.4 as well as between the WebUI and the CLI in a cluster. This issue occurred because 802.11r was not supported in split-tunnel forwarding mode. The fix ensures that 802.11r configuration is consistent across the Mobility Master and managed devices. This issue was observed in Mobility Masters and managed devices running ArubaOS 8.2.0.0 or later versions. AOS-196101 AOS-197335 -- Access points crashed and rebooted unexpectedly. ArubaOS The log file listed the reason for the event as external 8.3.0.10 watchdog reset. The fix ensures that the access points work as expected. This issue was observed in AP-203H access points running ArubaOS 8.3.0.10 or later versions. ArubaOS 8.6.0.3 Release Notes | Release Notes Resolved Issues in ArubaOS 8.6.0.3 | 20 Table 6: Resolved Issues in ArubaOS 8.6.0.3 New Bug ID Old Bug ID Description Reported Version AOS-196176 AOS-196945 -- The Dashboard > Security page didn't load the ArubaOS Detected Radios and displayed the error message, 8.5.0.4 Error retrieving information. Please try again later. The fix ensures that the WebUI displays the list of detected radios. This issue was observed in Mobility Masters running ArubaOS 8.5.0.4 or later versions. AOS-196215 AOS-199712 -- Some clients were unable to manage multiple clusters ArubaOS using a single Mobility Master. This issue occurred 8.5.0.3 when the Mobility Master assumed that the clusters are on the same VLAN and cannot reuse the same VRRP ID in the cluster profile. The fix ensures that the Mobility Master works as expected. This issue was observed in Mobility Masters running ArubaOS 8.5.0.3 or later versions. AOS-196312 AOS-199450 AOS-199937 AOS-200235 -- Access points were unable to connect to a cluster. This ArubaOS issue occurred because the ap_move flag was not 8.3.0.0 cleared after the apmove command was executed. The fix ensures that the ap_move flag is cleared after the apmove command is executed. This issue was observed in 340 Series access points running ArubaOS 8.3.0.0 or later versions. AOS-196325 AOS-200875 -- Mobility Master rebooted unexpectedly. This issue ArubaOS occurred due to high memory consumption. The fix 8.5.0.2 ensures that the Mobility Master works as expected. This issue was observed in Mobility Masters running ArubaOS 8.5.0.2 or later versions. AOS-196455 AOS-198499 AOS-200025 -- Mobility Master sent incorrect AP regulatory-domain- ArubaOS profile channel changes to the managed device during 8.5.0.4 the initial configuration propagation. The fix ensures that the Mobility Masters work as expected. This issue was observed in Mobility Masters running ArubaOS 8.0.0.0 or later versions. AOS-196479 -- Managed devices dropped bcast or mcast traffic on ArubaOS VLANs randomly. This issue occurred because the 8.3.0.6 clients were not getting IP addresses. The fix ensures that the bcast or mcast traffic is not dropped. This issue was observed in managed devices running ArubaOS 8.2.0.0 or later versions. AOS-196489 AOS-199172 -- GSM entries for AirGroup servers were not updated ArubaOS when MAC authenticated clients moved between APs. 8.6.0.0 The fix ensures that the GSM entries are updated with new bssid of the APs. This issue was observed in managed devices running ArubaOS 8.6.0.0 or later versions. AOS-196499 -- An AP rebooted multiple times. The fix ensures that ArubaOS the access point works as expected. This issue was 8.5.0.3 observed in AP-535 access points running ArubaOS 8.5.0.3 or later versions. 21 | Resolved Issues in ArubaOS 8.6.0.3 ArubaOS 8.6.0.3 Release Notes | Release Notes Table 6: Resolved Issues in ArubaOS 8.6.0.3 New Bug ID Old Bug ID Description Reported Version AOS-196528 -- Users were unable to remove port-channel using the ArubaOS no port monitor port-channel command and CLI 8.5.0.2 displayed the error message, Illegal operation: port- channel not being monitored. The fix ensures that the users are able to remove port-channel from port monitor. This issue was observed in managed devices running ArubaOS 8.0.0.0 or later versions. AOS-196560 AOS-197671 AOS-198844 AOS-199170 AOS-199375 AOS-200690 -- APs crashed and rebooted unexpectedly. The log files ArubaOS listed the reason for the event as Reboot caused by 8.6.0.0 kernel panic, aruba_am_tx_elem_handler+0x404. The fix ensures that the access points work as expected. This issue is observed in AP-534, AP-535 and AP-555 access points running ArubaOS 8.6.0.0 or later versions. AOS-196220 AOS-201396 -- An AP displayed the error message, wlan: ArubaOS [0:E:BSSCOLOR] ol_ath_offload_bcn_tx_status_ 8.6.0.2 event_handler: beacon tx failed. The fix ensures that the AP work as expected. This issue was observed in access points running ArubaOS 8.6.0.0 or later versions. AOS-196678 -- APs did not generate wireless containment frames and ArubaOS IDS protection was not applied. Hence, clients were 8.5.0.0 not deauthenticated from non-valid APs. This issue occurred when the radio operated in AM mode. The fix ensures that the APs generate wireless containment frames and clients are deauthenticated from non-valid APs. This issue was observed in AP-535 and AP-555 access points running ArubaOS 8.5.0.0 or later versions. AOS-196683 -- Access points came up without standby APs. This issue ArubaOS occurred in a cluster when AP channel scanning 8.5.0.3 detects an invalid AP and skips scanning the remaining APs. The fix ensures that the APs work as expected. This issue was observed in managed devices running ArubaOS 8.5.0.3 or later versions. AOS-196699 AOS-196870 -- Access points crashed and rebooted unexpectedly. ArubaOS The log file listed the reason for the event as rebooted 8.6.0.0 due to warm-reset [ BadAddr:480d5c0001e890 PC:wlc_mutx_bw_policy_update+0x1afc/0x28b8 [wl_ v6] Warm-reset]. The fix ensures that the APs work as expected. This issue was observed in AP-515 access points running ArubaOS 8.6.0.0 or later versions. AOS-196728 -- A Mobility Master Virtual Appliance crashed ArubaOS unexpectedly. The fix ensures that the Mobility Master 8.3.0.8 Virtual Appliance works as expected. This issue was observed in Mobility Master Virtual Appliances ArubaOS 8.3.0.0 or later versions in a cluster setup. ArubaOS 8.6.0.3 Release Notes | Release Notes Resolved Issues in ArubaOS 8.6.0.3 | 22 Table 6: Resolved Issues in ArubaOS 8.6.0.3 New Bug ID Old Bug ID Description Reported Version AOS-196788 -- The OFA process crashed unexpectedly. This issue ArubaOS occurred due to frequent reboot of APs. The fix 8.4.0.4 ensures that the managed device works as expected. This issue was observed in managed devices running ArubaOS 8.4.0.4 or later versions. AOS-196805 -- The command show ap debug client-stats displayed ArubaOS lower rates for management frames. The fix ensures 8.3.0.6 that the show ap client-stats command displays the correct rates for management frames. This issue was observed in access points running ArubaOS 8.3.0.6 or later versions. AOS-196847 AOS-196941 AOS-198485 AOS-201783 -- The Dashboard > Infrastructure > Controller page ArubaOS did not display the list of available controllers. The fix 8.5.0.3 ensures that the WebUI displays the list of controllers. This issue was observed in Mobility Masters running ArubaOS 8.5.0.3 or later versions. AOS-196852 -- APs running ArubaOS 8.4.0.4 or later versions crashed ArubaOS and rebooted unexpectedly. The fix ensures that the 8.4.0.4 access points work as expected. AOS-196879 -- APs crashed unexpectedly. The log file listed the ArubaOS reason for the event as PC is at aruba_am_tx_pkt_ 8.3.0.10 handler_data_ol. This issue occurred after upgrading the APs to ArubaOS 8.3.0.10. The fix ensures that the APs work as expected. This issue was observed in AP- 315 access points running ArubaOS 8.3.0.10 or later versions. AOS-196881 -- Server configuration rules were not pushed to the ArubaOS managed devices. The fix ensures that the managed 8.3.0.7 devices work as expected. This issue was observed in managed devices running ArubaOS 8.3.0.7 or later versions. AOS-196887 AOS-196959 -- WPA3-SAE-AES Opmode enabled clients were unable ArubaOS to connect to the AP and the AP sent 8.5.0.5 Deauthentication Reason Code: 49 Invalid pairwise masterkey identifier (PMKI) [24-25] deauthentication code. The fix ensures that the AP works as expected. This issue was observed in APs running ArubaOS 8.5.0.5 or later versions in a cluster setup. AOS-196896 AOS-197050 AOS-200076 AOS-200077 -- APs crashed and rebooted unexpectedly. This issue ArubaOS occurred during the stm process crash when more 8.5.0.3 than 256 clients connected to a Remote AP or Campus AP on bridge mode got deleted. The fix ensures that the APs work as expected. This issue was observed in AP-325 access points running ArubaOS 8.5.0.3 or later versions. 23 | Resolved Issues in ArubaOS 8.6.0.3 ArubaOS 8.6.0.3 Release Notes | Release Notes Table 6: Resolved Issues in ArubaOS 8.6.0.3 New Bug ID Old Bug ID Description Reported Version AOS-196911 AOS-198963 -- Users were unable to connect to APs. Enhancement to ArubaOS the wireless driver fixed the issue. This issue was 8.5.0.4 observed in AP-555 access points running ArubaOS 8.5.0.4 or later versions. AOS-196928 AOS-196066 AOS-196943 AOS-197742 AOS-198048 AOS-198328 AOS-198682 AOS-199156 -- Users were unable to discover the wired AirGroup ArubaOS server and experienced packet drops when a UCC 8.5.0.3 Skype call was initiated. This issue occurred when AirGroup was enabled in centralized mode. The fix ensures that the users are able to discover the wired AirGroup servers. This issue was observed in Mobility Masters running ArubaOS 8.5.0.3 or later versions. AOS-197122 -- Managed devices did not send SNMPv3 information to ArubaOS AirWave. The fix ensures that the managed devices 8.3.0.6 send the SNMPv3 information to AirWave. This issue was observed in managed devices running ArubaOS 8.3.0.6 or later versions. AOS-197160 AOS-198571 AOS-200427 AOS-201607 -- Managed devices crashed and rebooted unexpectedly. ArubaOS The log file listed the reason for the event as Reboot 8.3.0.8 Cause: Datapath timeout (SOS Assert) (Intent:cause:register 54:86:50:2. This issue occurred due to corrupt ACL entries. The fix ensures that the managed device works as expected. This issue was observed in managed devices running ArubaOS 8.3.0.8 in a cluster-setup. AOS-197262 -- The command show crashinfo did not display the ArubaOS crash information even when the crash symbol was 8.2.2.6 displayed. The fix ensures that the show crashinfo command displays the correct crash information. This issue was observed in managed devices running ArubaOS 8.2.2.6 or later versions. AOS-197310 -- WebUI did not list the available cluster profiles in the ArubaOS Configuration > Services > Cluster > Cluster group- 8.3.0.5 membership drop-down list. The fix ensures that the WebUI lists the available cluster profiles. This issue was observed in managed devices running ArubaOS 8.3.0.5 or later versions in a cluster setup. AOS-197393 AOS-200407 -- Radios experienced high number of resets and packet ArubaOS drops were also observed on APs. The fix ensures that 8.5.0.5 the APs work as expected. This issue was observed in 340 Series access points running ArubaOS 8.5.0.5 or later versions. AOS-197536 AOS-198286 AOS-200371 -- Many clients got disconnected from APs. This issue ArubaOS occurred when a new VLAN was added. The fix 8.5.0.0 ensures seamless connectivity. This issue was observed in access points running ArubaOS 8.3.0.0 or later versions. ArubaOS 8.6.0.3 Release Notes | Release Notes Resolved Issues in ArubaOS 8.6.0.3 | 24 Table 6: Resolved Issues in ArubaOS 8.6.0.3 New Bug ID Old Bug ID Description Reported Version AOS-197939 AOS-198087 -- After configuring the heartbeat threshold in the ArubaOS WebUI, the VRRP IDs got reset to the default values. 8.5.0.3 The fix ensures that the VRRP Ids are not reset to the default values. This issue was observed in Mobility Masters running ArubaOS 8.5.0.3 or later versions. AOS-197977 AOS-198348 AOS-198349 -- High memory consumption was observed in dot1x1 ArubaOS and dot1x2 processes. This issue occurred due to 8.5.0.1 memory leak when the EAP-fragmentation feature was enabled. The fix ensures dot1x1 and dot1x2 process do not consume high memory. This issue was observed in Mobility Masters running ArubaOS 8.4.0.0 or later versions. AOS-197993 AOS-198889 -- A managed device crashed unexpectedly and high ArubaOS CPU utilization was also observed on the managed 8.5.0.1 device. The fix ensures that the managed device works as expected. This issue was observed in managed devices running ArubaOS 8.5.0.1 or later versions. AOS-198003 -- Network firewall dropped fragmented packets and ArubaOS hence clients faced connectivity issues. The fix ensures 8.3.0.0 seamless connectivity. This issue was observed in Mobility Masters running ArubaOS 8.3.0.0 or later versions. AOS-198110 -- The configuration device move to command ArubaOS displayed the error message, trusted Illegal 8.3.0.9 Operation: There is Session ACL Defined. Cannot make the port untrusted. This issue occurred when the trusted command was executed before and after configuring the session ACL. The fix ensures that the error message is not displayed. This issue was observed in Mobility Masters running ArubaOS 8.3.0.9 or later versions. AOS-198112 -- WebUI displayed an error message Invalid IPv4 when ArubaOS users tried to configure AirWave IPv6 address under 8.5.0.3 Configuration > System > AirWave in the Mobility Master node hierarchy. The fix ensures that the AirWave IPv6 address can be configured using the WebUI. This issue was observed in Mobility Masters running ArubaOS 8.5.0.3 or later versions. AOS-198232 -- A managed device was unable to forward RADIUS ArubaOS server statistics through SNMP walk. This issue was 8.5.0.5 resolved by combining the RADIUS server statistics of 802.1X and authentication processes. This issue was observed in managed devices running ArubaOS 8.4.0.0 or later versions. 25 | Resolved Issues in ArubaOS 8.6.0.3 ArubaOS 8.6.0.3 Release Notes | Release Notes Table 6: Resolved Issues in ArubaOS 8.6.0.3 New Bug ID Old Bug ID Description Reported Version AOS-198290 AOS-198836 -- The show ip interface brief command displayed ArubaOS incorrect radio channel information for AAC and non 8.3.0.10 S-AAC managed devices. The fix ensures that the show ip interface brief command displays the correct radio channel information. This issue was observed in managed devices running ArubaOS 8.3.0.10 or later versions. AOS-198306 -- Users were unable to add a new CoA VRRP controller ArubaOS an existing cluster that already had CoA VRRP 8.6.0.0 controllers and the error message, Error: VRRP IP or VLAN cannot be changed when cluster group- membership is enabled. Disable cluster group- membership on all nodes and try again was displayed. The fix ensures that users are able to add a new CoA VRRP controller to an existing VRRP cluster profile without disabling cluster group-membership on all nodes. This issue was observed in managed devices running ArubaOS 8.5.0.0 or later versions. AOS-198360 -- The word switches was misspelled in the show ArubaOS airgroup command output. The fix ensures that the 8.5.0.5 word switches is spelled correctly. This issue was observed in Mobility Masters running ArubaOS 8.5.0.5 or later versions. AOS-198370 -- The Managed network > Configuration > Task > ArubaOS Bulk configuration upload page displayed an error 8.5.0.5 message, Incorrect header field(Controller VLAN) while uploading the bulk edit configuration. The fix ensures that the WebUI does not display the error message. This issue was observed in Mobility Masters running ArubaOS 8.5.0.5 or later versions. AOS-198527 AOS-198824 -- The output of show switches command displayed the ArubaOS configuration state of the managed device as NO MM 8.6.0.0 License. This issue occurred due to license synchronization failure. The fix ensures that the Mobility Master works as expected. This issue was observed in Mobility Masters running ArubaOS 8.6.0.0 or later versions. AOS-198669 AOS-198885 -- All rules configured using aaa server-group ArubaOS command were displayed in lowercase. The fix 8.5.0.3 ensures that the rules are displayed in the correct letter cases. This issue was observed in Mobility Masters running ArubaOS 8.5.0.3 or later versions. AOS-198670 -- Forward slash (/) did not search for the next hit in CLI ArubaOS output. The fix ensures that the forward slash leads to 8.3.0.8 the next hit in CLI output. This issue was observed in managed devices running ArubaOS 8.0.0.0 or later versions. ArubaOS 8.6.0.3 Release Notes | Release Notes Resolved Issues in ArubaOS 8.6.0.3 | 26 Table 6: Resolved Issues in ArubaOS 8.6.0.3 New Bug ID Old Bug ID Description Reported Version AOS-198699 -- ZTP feature did not work on Huawei 4G dongle with ArubaOS model number E3372h-607. The fix ensures that ZTP 8.5.0.0 works on the modem. This issue was observed in 7005controllers running ArubaOS 8.5.0.0 or later versions. AOS-198738 -- Users were unable to access CLI using SSH. This issue ArubaOS occurred in an IPv6 network when the multicast 8.5.0.1 packets were not sent to the Mobility Master Virtual Appliance. The fix ensures that the users can access CLI using SSH. This issue was observed in Mobility Master Virtual Appliance running ArubaOS 8.5.0.1 or later versions. AOS-198741 -- Users were unable to configure IPsec tunnels on a few ArubaOS of third party VPN peers and the controller sent the 8.5.0.4 error message, INVALID SYNTAX. This issue occurred when the third-party VPN peers propose IKEV2_ FRAGMENTATION_SUPPORTED notify payload but did not send the IKE_AUTH payload as fragments. The fix ensures that the users are able to configure IPsec tunnels. This issue was observed in stand-alone controllers running ArubaOS 8.5.0.4 or later versions. AOS-198743 -- A few IPv6 enabled Remote APs rebooted ArubaOS unexpectedly. This issue occurred when the Mobility 8.5.0.5 Master was configured with VRRP IP. The fix ensures that the APs work as expected. This issue was observed in Remote APs running ArubaOS 8.5.0.5 or later versions. AOS-198817 -- APs failed to perform 802.1x authentication. This issue ArubaOS occurred when dot1x authenticated access points 8.6.0.1 were upgraded to ArubaOS 8.6.0.1. The fix ensures that the APs work as expected. This issue was observed in AP-105 access points running ArubaOS 8.6.0.1 or later versions. AOS-198828 -- APs did not send temperature values to the server. ArubaOS This issue occurred when the APs did not properly 8.5.0.4 relay RTLS Aeroscout tag to the server. The fix ensures that the access points work as expected. This issue was observed in AP-535 and AP-555 access points running ArubaOS 8.5.0.4 or later versions. AOS-199217 AOS-199709 -- Cluster heartbeats were randomly missed on ArubaOS managed devices. The fix ensures that the managed 8.3.0.10 devices work as expected. This issue was observed in managed devices running ArubaOS 8.3.0.10 or later versions in a cluster setup. 27 | Resolved Issues in ArubaOS 8.6.0.3 ArubaOS 8.6.0.3 Release Notes | Release Notes Table 6: Resolved Issues in ArubaOS 8.6.0.3 New Bug ID Old Bug ID Description Reported Version AOS-199237 -- Users were unable to establish connection with a ArubaOS managed device using the mdconnect and logon 8.5.0.5 commands. This issue occurred when master-ssh-pub- cert was not downloaded during the initial boot-up after ZTP. The fix ensures that the commands work as expected. This issue was observed in managed devices running ArubaOS 8.5.0.5 or later versions. AOS-199238 -- A managed device displayed the error log, ctamon_ ArubaOS gsm_update_section_intf_stats: Failed to Update 8.4.0.4 GSM section intf_stats for , intf_num:0x40e3d6e0, error 43, error_htbl_key_not_found. The fix ensures that the managed device works as expected. This issue was observed in managed devices running ArubaOS 8.4.0.4 or later versions. AOS-199667 AOS-199736 -- The system was unresponsive when the show tech- ArubaOS support command was executed. This issue occurred 8.3.0.0 when the show datapath dhcp binding command duplicated the output entries. The fix ensures that the command works as expected. This issue was observed in managed devices running ArubaOS 8.3.0.0 or later versions. AOS-199696 -- Managed devices failed to establish connection with ArubaOS IF-MAP enabled ClearPass Policy Manager. This issue 8.5.0.5 occurred when same certificates were added using different names. The fix ensures that the managed devices work as expected. This issue was observed in managed devices running ArubaOS 8.5.0.5 or later versions. AOS-199707 -- A managed device crashed and rebooted ArubaOS unexpectedly. The log file listed the reason for the 8.6.0.0 event as Reboot Cause: Datapath timeout (SOS Assert) (Intent:cause:register 54:86:0:20. The fix ensures that the managed device works as expected. This issue was observed in managed devices running ArubaOS 8.6.0.0 or later versions. AOS-199739 AOS-201390 -- A managed device crashed and rebooted ArubaOS unexpectedly. The log file listed the reason for the 8.6.0.2 event as Reboot Cause: Datapath timeout (SOS Assert) (Intent:cause:register 54:86:50:2). This issue occurred after upgrading the managed device to ArubaOS 8.6.0.2 version. The fix ensures that the managed device works as expected. This issue was observed in managed devices running ArubaOS 8.6.0.2 or later versions. ArubaOS 8.6.0.3 Release Notes | Release Notes Resolved Issues in ArubaOS 8.6.0.3 | 28 Table 6: Resolved Issues in ArubaOS 8.6.0.3 New Bug ID Old Bug ID Description Reported Version AOS-200002 AOS-200649 -- A managed device crashed and rebooted ArubaOS unexpectedly. The log file listed the reason for the 8.5.0.5 event as crashed and rebooted due to Datapath timeout (Heartbeat Initiated) (Intent:cause:register 53:86:0:2c). This issue occurred due to high CPU utilization. The fix ensures that the managed device works as expected. This issue was observed in managed devices running ArubaOS 8.5.0.5 or later versions. AOS-200102 AOS-200779 -- Clients took a long time to failover to another ArubaOS managed device in a cluster. The fix ensures that the 8.5.0.5 clients failover seamlessly. This issue was observed in managed devices running ArubaOS 8.5.0.0 or later versions in a cluster setup. AOS-200146 -- The STM process on an AP crashed. The fix ensures ArubaOS that the access point works as expected. This issue 8.6.0.0 was observed in AP-535 access points running ArubaOS 8.4.0.0 or later versions. AOS-200165 -- AP-515 access points running ArubaOS 8.5.0.6 or later ArubaOS versions crashed and rebooted unexpectedly. The log 8.5.0.6 file listed the reason for the event as rebooted caused by BadPtr:00000010 PC:aruba_periodic_ measurements+0x1b10/0x2748 [wl_v6] Warm- reset. The fix ensures that the APs work as expected. AOS-200420 -- Data traffic from VPNC concentrator was not routed ArubaOS back to the managed device. The fix ensures that the 8.5.0.5 managed device works as expected. This issue occurred when the managed device was provisioned with two uplinks. This issue was observed in branch office controllers running ArubaOS 8.5.0.5 or later versions. 29 | Resolved Issues in ArubaOS 8.6.0.3 ArubaOS 8.6.0.3 Release Notes | Release Notes Chapter 7 Known Issues in ArubaOS 8.6.0.3 Known Issues in ArubaOS 8.6.0.3 This chapter describes the known issues and limitations observed in this release. Limitation Following is the limitation observed in this release: Airtime Fairness Mode Airtime Fairness Mode is not supported in 802.11ax access points. 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. Known Issues Following are the known issues observed in this release. Table 7: Known Issues in ArubaOS 8.6.0.3 New Bug ID AOS-151022 AOS-188417 AOS-151355 AOS-182847 Old Bug ID 185176 185602 -- Description Reported Version The output of the show datapath uplink command displays incorrect session count. This issue is observed in managed devices running ArubaOS 8.1.0.0 or later versions. ArubaOS 8.1.0.0 A few managed devices are unable to pass traffic to the nexthop VPN concentrator (VPNC) using policybased routing. This issue is observed in managed devices running ArubaOS 8.0.1.0 or later versions. ArubaOS 8.0.1.0 A few users are unable to copy the WPA Passphrase 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 in the WebUI. This issue is observed in managed devices running ArubaOS 8.4.0.0 in a Mobility Master-Managed Device topology. ArubaOS 8.4.0.0 ArubaOS 8.6.0.3 Release Notes | Release Notes 30 Table 7: Known Issues in ArubaOS 8.6.0.3 New Bug ID Old Bug ID Description Reported Version AOS-184947 AOS-192737 -- The jitter and health score data are missing from the ArubaOS Dashboard > Infrastructure > Uplink > Health page 8.4.0.4 in the WebUI. This issue is observed in Mobility Master running ArubaOS 8.4.0.4 or later versions. AOS-184977 AOS-188242 AOS-188378 AOS-197491 -- The output of basic commands such as show version, ArubaOS show clock, and show image version are unable to 8.4.0.0 display any information and the default gateway details are missing in a managed device. This issue occurs when the /tmp directory runs out of memory because of too many logs from the Policy Manager. This issue is observed in managed devices running ArubaOS 8.4.0.0 or later versions. AOS-188090 AOS-196004 AOS-199152 -- The Dashboard > Overview > Clients page of the ArubaOS WebUI displays incorrect usage values intermittently. 8.4.0.0 This issue is observed in Mobility Master Virtual Appliances running ArubaOS 8.4.0.0 or later versions. AOS-188527 AOS-193897 -- The IP address of the NAT configured managed device ArubaOS is visible in the HTTP header of the web server. This 8.3.0.0 issue is observed in managed devices running ArubaOS 8.3.0.0 or later versions. AOS-188898 AOS-198730 AOS-200227 -- The postgres module crashes on a controller. This ArubaOS issue is observed in managed devices running 8.2.2.6 ArubaOS 8.2.1.0 or later versions. AOS-190071 AOS-190372 -- A few users are unable to access the websites when ArubaOS WebCC is enabled on the user role. This issue occurs 8.4.0.0 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: n Remove web category from the ACL rules and apply any any any permit policy. n Disable WebCC on the user role. n Change the VLAN of user role from trunk mode to access mode. AOS-191216 AOS-196523 AOS-199160 -- A managed device crashes and reboots unexpectedly. ArubaOS The log file lists the reason for the event as Reboot 8.5.0.4 Cause: Kernel Panic (Intent:cause:register 12:86:e0:2). This issue is observed in managed devices running ArubaOS 8.5.0.4 or later versions. AOS-191394 -- APs crash and reboot unexpectedly. The log file lists ArubaOS the reason for the event as Reboot caused by kernel 8.6.0.0 panic: Take care of the TARGET ASSERT first. This issue is observed in 500 Series access points running ArubaOS 8.6.0.0 or later versions. 31 | Known Issues in ArubaOS 8.6.0.3 ArubaOS 8.6.0.3 Release Notes | Release Notes Table 7: Known Issues in ArubaOS 8.6.0.3 New Bug ID Old Bug ID Description Reported Version AOS-191612 -- The MAC address of users connected using VIA is not ArubaOS sent to ClearPass Policy Manager for authentication. 8.5.0.1 This issue is observed when IKE V2 with EAP-FTC is used for VIA authentication. This issue is observed in Mobility Masters running ArubaOS 8.5.0.1 or later versions. AOS-192725 AOS-190476 AOS-196004 -- The Dashboard > Overview page of the WebUI ArubaOS displays incorrect number of users intermittently. This 8.3.0.8 issue is observed in Mobility Masters running ArubaOS 8.3.0.8 or later versions. AOS-192738 AOS-197047 -- The Mobility Master list in the WebUI incorrectly ArubaOS displays the mac address of the primary Mobility 8.3.0.10 Master for the secondary Mobility Master. This issue is observed in Mobility Masters running ArubaOS 8.3.0.10 or later versions. AOS-193184 -- L2 connected managed devices move to L3 connected ArubaOS state after upgrade. This issue is observed in managed 8.5.0.2 devices running ArubaOS 8.5.0.2 or later versions. AOS-193775 AOS-194581 AOS-197372 -- A mismatch of AP count and client count is observed ArubaOS between the Mobility Master and the managed device. 8.5.0.2 This issue is observed in Mobility Masters running ArubaOS 8.3.0.0 or later versions. AOS-193840 -- The managed device loses connectivity to IPv6 ArubaOS gateway intermittently. This issue is observed in 8.3.0.6 managed devices running ArubaOS 8.3.0.6 or later versions. AOS-193883 AOS-197756 -- A few APs are unable to use DHCP IPv6 addresses and ArubaOS option 52 for master discovery. This issue occurs when 8.3.0.8 the APs do not clear the previous LMS entries after the upgrade. This issue is observed in access points running ArubaOS 8.3.0.8 or later versions. Workaround: Delete the IPv4 addresses from ap system profile using the command, ap system-profile and from high availability profiles using the command, ha. AOS-194846 -- The commands show ap arm history and show ArubaOS airmatch debug optimization do not display the 8.3.0.7 output. This issue is observed in Mobility Masters running ArubaOS 8.3.0.7 or later versions. AOS-194911 -- Incorrect flag output is displayed for APs configured ArubaOS with 802.1X authentication when the show ap 8.5.0.2 database command is executed. This issue is observed in APs running ArubaOS 8.5.0.2 or later versions. ArubaOS 8.6.0.3 Release Notes | Release Notes Known Issues in ArubaOS 8.6.0.3 | 32 Table 7: Known Issues in ArubaOS 8.6.0.3 New Bug ID Old Bug ID Description Reported Version AOS-194964 -- A few users are unable to clone the configuration from ArubaOS an existing group to a new group in a Mobility Master. 8.5.0.2 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-195177 -- Managed devices frequently generate internal system ArubaOS error logs. This issue occurs when the sapd process 8.3.0.7 reads a non-existent interface. This issue is observed in 7220controllers running ArubaOS 8.3.0.7 or later versions. AOS-195228 -- The device status is always displayed as inactive when ArubaOS SNMP walk is performed. This issue is observed in 8.5.0.2 stand-alone controllers running ArubaOS 8.5.0.2 or later versions. AOS-195434 -- An AP crashes and reboots unexpectedly. The log files ArubaOS list the reason for the event as Reboot caused by 8.5.0.2 kernel panic: Fatal exception. This issue is observed in APs running ArubaOS 8.5.0.0 o or later versions in a Mobility Master-Managed Device topology. AOS-195526 -- Some clients are unable to get the DHCP address. This ArubaOS issue occurs because the ACE entries of the logon role 8.3.0.8 ACL changes to Deny all when the PEFNG feature is disabled. This issue is observed in managed devices running ArubaOS 8.3.0.8 or later versions. AOS-195939 -- UBT users are assigned logon role when they receive ArubaOS the same IP addresses. This issue is observed in 8.5.0.2 managed devices running ArubaOS 8.5.0.2 or later versions. AOS-196115 -- Users are unable to configure untrusted VLAN in the ArubaOS Configuration > Interfaces > Ports page of the 8.5.0.0 WebUI. This issue is observed in Mobility Masters running ArubaOS 8.5.0.0 or later versions. AOS-196457 -- High radio noise floor is observed on APs. This issue is ArubaOS observed on AP-515 access points running ArubaOS 8.5.0.2 8.5.0.2 or later versions. AOS-196593 -- APs crash and reboot unexpectedly. The log file lists ArubaOS the reason for the event as reboot caused by Kernel 8.3.0.8 panic - not syncing: Fatal exception in interrupt PC is at 0x000C7461. This issue is observed in AP-335 access points running ArubaOS 8.3.0.8 or later versions. 33 | Known Issues in ArubaOS 8.6.0.3 ArubaOS 8.6.0.3 Release Notes | Release Notes Table 7: Known Issues in ArubaOS 8.6.0.3 New Bug ID Old Bug ID Description Reported Version AOS-196697 AOS-199833 -- APs crash and reboot unexpectedly. The log file lists ArubaOS the reason for the event as PC is at wlc_apps_ 8.3.0.8 psq+0xc/0x6ec [wl_v6];LR is at wlc_apps_release_ count+0xb4/0x164 [wl_v6]. This issue is observed in AP-505 access points running ArubaOS 8.3.0.8 or later versions. AOS-196864 -- Adding a new VLAN ID connects L3 but displays that ArubaOS the connected VLAN ID fails with a different ID. This 8.5.0.3 issue is observed when new VLANs are added and the total number of VLANs are 100/101,200/201,300/301 and likewise. This issue is observed in managed devices running ArubaOS 8.5.0.3 or later versions. AOS-196878 AOS-197216 -- The Datapath process crashes on a managed device. ArubaOS The log file lists the reason for the event as wlan-n09- 8.5.0.2 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-domain- ArubaOS profile channel changes to the managed device during 8.5.0.4 the initial configuration propagation. This issue is observed in Mobility Masters running ArubaOS 8.0.0.0 or later versions. Workaround: The following are recommended: In the CLI, create an AP regulatory-domain- profile without any channel configuration, save the changes and later add or delete channels as desired. In the WebUI, create an AP regulatory-domain- profile with default channel selected, save the changes and later add or delete channels as desired. AOS-197215 -- Users are unable to delete the Weekend entry under ArubaOS Start Day of Time range field in the WebUI. This issue 8.2.2.6 occurs when the users create a new policy rule in the Configuration > Roles & Policies > Policies > <policy_name> > <new_policy_rule> page, and select Access control radio button in the Rule type field of the WebUI. This issue is observed in Mobility Masters running ArubaOS 8.2.2.6 or later versions. AOS-197565 -- APs crash and reboot unexpectedly. The log file lists ArubaOS the reason for the event as Dump capture kernel:AP 8.5.0.2 rebooted caused by cold HW reset(power loss). This issue is observed in access points running ArubaOS 8.5.0.0 or later versions. AOS-197631 -- Policy-based routing is not applied when IPsec map is ArubaOS configured as nexthop. This issue is observed in 8.6.0.0 managed devices running ArubaOS 8.6.0.0 or later versions. ArubaOS 8.6.0.3 Release Notes | Release Notes Known Issues in ArubaOS 8.6.0.3 | 34 Table 7: Known Issues in ArubaOS 8.6.0.3 New Bug ID Old Bug ID Description Reported Version AOS-197912 -- Multicast traffic is not forwarded to the clients when ArubaOS UAC and AAC are different. This issue occurs when the 8.3.0.7 VLANs assigned by radius server are different from the VLANs configured in the virtual-ap profile. This issue is observed in managed devices running ArubaOS 8.3.0.7 or later versions. AOS-197945 -- Access points crash and reboot unexpectedly. The log ArubaOS file lists the reason for the events as, 8.5.0.3 BadAddr:ffff00000010 PC:wlc_dump_ aggfifo+0x1160/0x12b0 [wl_v6] Warm-reset. This issue occurs due to memory corruption. This issue is observed in AP-514 and AP-515 access points running ArubaOS 8.5.0.3 or later versions. AOS-198007 -- APs are unable to ping managed devices and the APs ArubaOS keep switching between clusters. This issue is 8.3.0.8 observed in access points running ArubaOS 8.3.0.8 or later versions. AOS-198024 -- Users are unable to access any page after the fifth ArubaOS page using the Maintenance > Access Point page in 8.6.0.0 the WebUI. This issue is observed in stand-alone controllers running ArubaOS 8.6.0.0 or later versions. AOS-198157 -- A stand-alone controller crashes and reboots ArubaOS unexpectedly. The log file lists the reason for the event 8.6.0.0 as Reboot Cause: Datapath timeout (Intent:cause: 86:56). This issue is observed in stand-alone controllers running ArubaOS 8.6.0.0 or later versions. AOS-198218 -- After reboot, the GRE tunnel of a standby controller is ArubaOS UP instead of DOWN in a VRRP instance and this 8.5.0.3 results in network loop. This issue is observed in managed devices running ArubaOS 8.5.0.3 or later versions. AOS-198266 -- MAC authenticated clients are unable to ArubaOS reauthenticate even after enabling reauthentication. 8.5.0.5 This issue is observed in stand-alone controllers running ArubaOS 8.5.0.5 or later versions. AOS-198475 -- Users are unable to upgrade the Mobility Master ArubaOS Virtual Appliance to ArubaOS 8.5.0.0 or later versions. 8.5.0.5 This issue is observed in Mobility Master Virtual Appliance running ArubaOS 8.5.0.5 or later versions. AOS-198483 -- WebUI does not have an option to map the rf dot11- ArubaOS 60GHz-radio-profile to an AP group. This issue is 8.5.0.4 observed in Mobility Masters running ArubaOS 8.5.0.4 or later versions. 35 | Known Issues in ArubaOS 8.6.0.3 ArubaOS 8.6.0.3 Release Notes | Release Notes Table 7: Known Issues in ArubaOS 8.6.0.3 New Bug ID Old Bug ID Description Reported Version AOS-198834 AOS-200088 AOS-200555 AOS-201312 -- Managed devices crash and reboot unexpectedly. The ArubaOS log file lists the reason for the event as rebooted due 8.3.0.10 to Soft Watchdog reset (Intent:cause:register de:86:70:4). This issue is observed in 7240XM controllers running ArubaOS 8.3.0.10 or later versions. AOS-198849 AOS-198850 -- Users are unable to configure 2.4 GHz radio profile in ArubaOS the Configuration > System > Profiles > 2.4 GHz 8.5.0.3 radio profile page and the WebUI displays the 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-198787 AOS-198929 -- A Remote AP does not come up on a managed device ArubaOS when Verizon U730L modem is used. This issue is 8.6.0.0 observed in managed devices running ArubaOS 8.6.0.0 or later versions. AOS-198991 -- Users are unable to add VLAN to an existing trunk port ArubaOS using the Configuration > Interfaces >VLANs page 8.6.0.2 of the WebUI. This issue is observed in Mobility Masters running ArubaOS 8.6.0.1 or later versions. AOS-199012 AOS-198865 -- A managed device crashes and reboots unexpectedly. ArubaOS The log file lists the reason for the event as Reboot 8.4.0.4 Cause: Datapath timeout (SOS Assert) (Intent:cause:register 54:86:50:4). This issue is observed in managed devices running ArubaOS 8.4.0.4 or later versions. AOS-199381 -- Users are unable to connect to the backup SSID of a ArubaOS Remote AP. This issue occurs when the users try to 8.6.0.2 connect after AP reboot. This issue is observed in Remote APs running ArubaOS 8.6.0.1 or later versions. AOS-199420 -- ClientMatch steered clients to APs that are deployed in ArubaOS different clusters. This issue is observed in access 8.2.2.2 points running ArubaOS 8.2.2.2 or later versions. AOS-199423 -- Some L3 redundant Mobility Masters witness profmgr ArubaOS error logs. This issue occurs when the Mobility Master 8.5.0.5 is upgraded to a later version of ArubaOS. This issue is observed in Mobility Masters running ArubaOS 8.5.0.5- FIPS. AOS-199492 -- A few APs do not get displayed in the show airgroup ArubaOS aps command output and the auto-associate policy 8.6.0.0 stops working 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. ArubaOS 8.6.0.3 Release Notes | Release Notes Known Issues in ArubaOS 8.6.0.3 | 36 Table 7: Known Issues in ArubaOS 8.6.0.3 New Bug ID Old Bug ID Description Reported Version AOS-199539 -- All the profiles listed under an AP group get marked as ArubaOS default except the VAP profile. This issue is observed 8.5.0.4 in managed devices running ArubaOS 8.5.0.4 or later versions. Workaround: Run ccm-debug full-config-sync command on the effected managed device. AOS-199878 AOS-198897 AOS-200006 AOS-200080 -- An AP crashes and reboots unexpectedly. The log file ArubaOS lists the reason for this event as Reboot caused by 8.5.0.4 kernel panic: CPU stall. This issue is observed in AP- 303H access points running ArubaOS 8.5.0.4 or later versions. AOS-200071 AOS-201068 -- Some clients are getting U-APSD disabled in ArubaOS association response though they are able to connect 8.6.0.2 to an SSID without any issues. This issue does not allow the client to enter power saving mode and reduces the talk time from 12 hours to 3 hours. This issue is observed in access points running ArubaOS 8.3.0.0 or later versions. Workaround: Disable the 802.11r profile in the configurations using the no dot11r command. AOS-200187 -- Mobility Master is assigning duplicate IP addresses to ArubaOS Branch office Controllers from the VLAN pool. This 8.5.0.5 issue is observed in Mobility Masters running ArubaOS 8.5.0.5 or later versions. AOS-201171 -- Clients are unable to receive traffic from APs. This ArubaOS issue occurs when large number of clients are 8.6.0.3 associated to APs and when aggressive power saving transitions are observed on the associated clients. This issue is observed in access points ArubaOS 8.6.0.3. AOS-201463 -- An AP is unable to receive IPv6 address from IPv6 RA. ArubaOS This issue occurs when static IPv4 addresses are 8.6.0.3 configured on LACP enabled APs. This issue is observed in access points running ArubaOS 8.6.0.3. Workaround: Do not configure static IPv4 addresses for LACP enabled APs. AOS-201681 -- Data traffic to clients on radio 2 fails. This issue occurs ArubaOS due to cluster failover. This issue is observed in tri- 8.6.0.3 radio enabled AP-555 access points running ArubaOS 8.6.0.3. Workaround: The following are recommended: n Disable the tri-radio mode. n Associate the clients to Radio 0. AOS-202577 -- AirGroup stops working on managed devices running ArubaOS ArubaOS 8.6.0.3 in a cluster setup. 8.6.0.3 AOS-207237 -- Clients are unable to obtain IP addresses. This issue is ArubaOS observed in 5 GHz radio mode enabled APs running 8.6.0.0 ArubaOS 8.6.0.0 or later versions. 37 | Known Issues in ArubaOS 8.6.0.3 ArubaOS 8.6.0.3 Release Notes | Release Notes Table 7: Known Issues in ArubaOS 8.6.0.3 New Bug ID Old Bug ID Description Workaround: Disable 5 GHz radio mode on APs. Duplicates: AOS-203038, AOS-209048, AOS-209237, AOS-209443, AOS-210038, AOS-210641, AOS-210664, AOS-212228, and AOS-212388 Reported Version ArubaOS 8.6.0.3 Release Notes | Release Notes Known Issues in ArubaOS 8.6.0.3 | 38 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.3 Release Notes | Release Notes 39 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 40 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 40 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 40 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 40 | Upgrade Procedure ArubaOS 8.6.0.3 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.3 Release Notes | Release Notes Upgrade Procedure | 41 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 40. 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. 42 | Upgrade Procedure ArubaOS 8.6.0.3 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 40 for information on creating a backup. In the CLI ArubaOS 8.6.0.3 Release Notes | Release Notes Upgrade Procedure | 43 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 40 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 40. 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 preupgrade 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. 44 | Upgrade Procedure ArubaOS 8.6.0.3 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.3 Release Notes | Release Notes Upgrade Procedure | 45 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. 46 | Upgrade Procedure ArubaOS 8.6.0.3 Release Notes | Release Notesmadbuild