ArubaOS 8.9.0.0 Release Notes
File info: application/pdf · 47 pages · 293.35KB
ArubaOS 8.9.0.0 Release Notes
Contents Contents Contents 3 RevisionHistory 5 ReleaseOverview 6 Related 6 SupportedBrowsers 6 GuidelinesBeforeUpgrading7000SeriesControllerstoArubaOS8.9.0.0 7
Full PDF Document
If the inline viewer fails, it will open the original document in compatibility mode automatically. You can also open the file directly.
Extracted Text
ArubaOS 8.9.0.0 Release Notes Copyright Information � Copyright 2021 Hewlett Packard Enterprise Development LP. Open Source Code This product includes code licensed under the GNU General Public License, the GNU Lesser General Public License, and/or certain other open source licenses. A complete machine-readable copy of the source code corresponding to such code 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, send a check or money order in the amount of US $10.00 to: Hewlett Packard Enterprise Company 6280 America Center Drive San Jose, CA 95002 USA Contents Contents Contents 3 Revision History 5 Release Overview 6 Related Documents 6 Supported Browsers 6 Guidelines Before Upgrading 7000 Series Controllers to ArubaOS 8.9.0.0 7 Terminology Change 7 Contacting Support 7 New Features and Enhancements in ArubaOS 8.9.0.0 9 Configuring Default Gateway on 7280 Controllers 9 Dashboard Monitoring 9 Displaying the Name for Assa Abloy Door Locks 9 Enhancement to Serial Data Transport Profiles 9 Exporting IDS Logs from WebUI 9 New IoT Generic Filtering options 9 Configuring Wireless Containment Deauth 9 Upgrade to Vendor QOSMOS Code 10 Mesh Support on Wi-Fi 6E Access Points 10 Support for Azure Southbound Action for BLE Devices 10 Support for UTB 10 Increase in Maximum Supported BLE and Zigbee TX Power Values 10 Support for 512 Clients on Wi-Fi 6E Access Points 10 Support for Air Slice on Wi-Fi 6E Access Points 10 Support for New Channel Representation on Wi-Fi 6E Access Points 10 Support for New AP Platform 11 Support for Hotspot on Wi-Fi 6E Access Points 11 Support for Multiple BSSID on Wi-Fi 6E Access Points 11 Configuring 6 GHz Radio Band on AP-635 Access Points 11 Support for Wi-Fi 6E ARM 12 Support for Wi-Fi 6E AirMatch 12 Support for Wi-Fi 6E Air Management 12 Support for Wi-Fi 6E Air Management Activity Detection 12 Support for Wi-Fi 6E Air Management Information Element Parsing 12 Scanning Enhancements for Wi-Fi 6E Access Points 12 Support for 6 GHz Radio 12 Support Regulatory Domain Profile for 6 GHz Radio 12 Support for Client Match for 6 GHz Radio 12 Support for EN302502 and EN301893 in UNI3 Bands 13 Support for GCM Ciphers on AP-555 Access Point 13 Support for Dropbear SSH 13 Client Match Support for 802.11v 13 Enhancements to Multicast Group Limit 13 Enabling TLS Method for an External Logging Server 13 Encrypt Private Key in the Flash 13 Enhancements to number of PVST+ instances 13 Increase in Number of Tunneled Networks in VIA 13 ArubaOS 8.9.0.0 Release Notes | Release Notes 3 Upgrade Notification for a Cluster Upgrade 13 Supported Platforms in ArubaOS 8.9.0.0 14 Mobility Conductor Platforms 14 Mobility Controller Platforms 14 AP Platforms 14 Regulatory Updates in ArubaOS 8.9.0.0 16 Resolved Issues in ArubaOS 8.9.0.0 17 Known Issues in ArubaOS 8.9.0.0 30 Limitation 30 Known Issues 30 Upgrade Procedure 35 Important Points to Remember 35 Memory Requirements 36 Low Free Flash Memory 36 Backing up Critical Data 40 Upgrading ArubaOS 42 Verifying the ArubaOS Upgrade 43 Downgrading ArubaOS 45 Before Calling Technical Support 47 4 | Contents ArubaOS 8.9.0.0 Release Notes | Release Notes Chapter 1 Revision History Revision History The following table lists the revision numbers and the corresponding changes that were made in this release: Table 1: Revision History Revision Change Description Revision 01 Initial release. ArubaOS 8.9.0.0 Release Notes | Release Notes 5 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 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 Conductor 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: n Microsoft Internet Explorer 11 on Windows 7 and Windows 8 n Microsoft Edge (Microsoft Edge 38.14393.0.0 and Microsoft EdgeHTML 14.14393) on Windows 10 n Mozilla Firefox 48 or later on Windows 7, Windows 8, Windows 10, and macOS n Apple Safari 9.0 or later on macOS n Google Chrome 67 on Windows 7, Windows 8, Windows 10, and macOS ArubaOS 8.9.0.0 Release Notes | Release Notes 6 Guidelines Before Upgrading 7000 Series Controllers to ArubaOS 8.9.0.0 Customers with deployments containing the following 7000 Series controllers should read the Low Free Flash Memory requirements prior to attempting an upgrade of the 7000 Series controllers to ArubaOS 8.9.0.0: n 7005 n 7008 n 7010 If you are unable to free up sufficient flash memory, contact Technical Support. Do not reboot the controller. Terminology Change As part of advancing HPE's commitment to racial justice, we are taking a much-needed step in overhauling HPE engineering terminology to reflect our belief system of diversity and inclusion. Some legacy products and publications may continue to include terminology that seemingly evokes bias against specific groups of people. Such content is not representative of our HPE culture and moving forward, Aruba will replace racially insensitive terms and instead use the following new language: Usage 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/ 7 | Release Overview ArubaOS 8.9.0.0 Release Notes | Release Notes Software Licensing Site End-of-life Information Security Incident Response Team lms.arubanetworks.com arubanetworks.com/support-services/end-of-life/ Site: arubanetworks.com/support-services/security-bulletins/ Email: aruba-sirt@hpe.com ArubaOS 8.9.0.0 Release Notes | Release Notes Release Overview | 8 Chapter 3 New Features and Enhancements in ArubaOS 8.9.0.0 New Features and Enhancements in ArubaOS 8.9.0.0 This chapter describes the features and enhancements introduced in this release. Configuring Default Gateway on 7280 Controllers ArubaOS supports configuring the default gateway for dedicated OOB management Ethernet port on 7280 controllers by using the ip default-gateway mgmt <nexthop> command. Dashboard Monitoring A search option is introduced in the Campus AP Allowlist and Remote AP Allowlist tables of the Configuration > Access Points > Allowlist page in the WebUI. Displaying the Name for Assa Abloy Door Locks The Assa Abloy door locks will now be displayed using a name in the output of the show ap debug zigbee client-table command. This enhancement is helpful in identifying and debugging issues related to a specific Assa Abloy door lock connected to the system. Enhancement to Serial Data Transport Profiles A new CLI parameter usbSerialDeviceTypeFilter <filter> is added to the IoT transport profile configuration to allow users to filter serial data based on the USB dongle type. Exporting IDS Logs from WebUI Starting from ArubaOS8.9.0.0, a user has the option of exporting IDS logs as a CSV file from the WebUI. New IoT Generic Filtering options The following generic filtering parameters are introduced in the IoT Transport Profile configuration: n usbSerialDeviceTypeFilter <filter> n companyIdentifierFilter <filter> n serviceUUIDFilter <filter> n macOuiFilter <filter> n localNameFilter <filter> Configuring Wireless Containment Deauth A new parameter Wireless Containment Deauth is introduced to enable users to set an unique reason code in the deauth frame. This unique reason code identifies if the deauths are originating from the WIPs solution. ArubaOS 8.9.0.0 Release Notes | Release Notes 9 Upgrade to Vendor QOSMOS Code The vendor QOSMOS code is upgraded to ProtoBundle-1.530.1-25 for ArubaOS 8.9.0.0 release. Mesh Support on Wi-Fi 6E Access Points ArubaOS provides support for mesh deployment and WPA3-SAE-AES opmode on Wi-Fi 6E access points. Support for Azure Southbound Action for BLE Devices The Asynchronous Cloud to Device (C2D) messages are added to support Azure southbound action on BLE devices. Support for UTB A new parameter utb_filter_block is introduced to control the band on which the Ultra Tri-Band (UTB) limitation is applied in the regulatory-domain-profile. The UTB filter supports channel band on both 5 GHz and 6 GHz in ArubaOS 8.9.0.0 release. Increase in Maximum Supported BLE and Zigbee TX Power Values The maximum configurable transmission (Tx) power rate in an IoT radio profile is increased to 20 dBm. Support for 512 Clients on Wi-Fi 6E Access Points ArubaOS supports 512 clients for each radio band on Wi-Fi 6E access points. Support for Air Slice on Wi-Fi 6E Access Points ArubaOS supports Air Slice on Wi-Fi 6E access points for 5 GHz radio band only. Support for New Channel Representation on Wi-Fi 6E Access Points ArubaOS represents the channels on 6 GHz band as four separate fields for Wi-Fi 6E access points. The four separate fields are as follows: n Pri-Channel n Sec-Channel n Band n Bandwidth ArubaOS also modifies the following AMON messages to include the four separate fields for each 6 GHz radio channel: n RADIO_STATS n RADIO_iNFO n AMON_TAG 10 | New Features and Enhancements in ArubaOS 8.9.0.0 ArubaOS 8.9.0.0 Release Notes | Release Notes n UCM_SESSION_UPDATE n SPEC_DEV_DETAILS n AG_SVC_SESSION_UPDATE Support for New AP Platform The Aruba 630 Series access points (AP-635) are high performance, tri-radio, indoor access points that can be deployed in either controller-based (ArubaOS) or controller-less (Aruba Instant) network environments. These APs deliver high performance concurrent 2.4 GHz, 5 GHz, and 6 GHz 802.11ax Wi-Fi (Wi-Fi 6E) functionality with MIMO radios (2x2 in 2.4 GHz, 5 GHz, and 6 GHz), while also supporting 802.11a, 802.11b, 802.11g, 802.11n, and 802.11ac wireless services. Containment does not work on the 6 GHz radio when WPA3 with Management Frame Protection (MFP) is enabled. Additional features include: n IEEE 802.11a, IEEE 802.11b, IEEE 802.11g, IEEE 802.11n, IEEE 802.11ac, and IEEE 802.11ax operation as a wireless access point. n IEEE 802.11a, IEEE 802.11b, IEEE 802.11g, IEEE 802.11n, IEEE 802.11ac, and IEEE 802.11ax spectrum monitor. n Two Ethernet ports, ENET0 and ENET1, capable of data rates up to 2.5 Gbps. n Compatible with IEEE 802.3bt, IEEE 802.3at, and IEEE 802.3af PoE standards on both Ethernet ports. n Thermal management. n Support for OFDMA. For complete technical details and installation instructions, see Aruba 630 Series Access Points Installation Guide. Support for Hotspot on Wi-Fi 6E Access Points ArubaOS supports Hotspot 2.0 on the 2.4 GHz and 5 GHz radio bands of Wi-Fi 6E access points. Support for Multiple BSSID on Wi-Fi 6E Access Points ArubaOS supports Multiple BSSID feature on Wi-Fi 6E access points. Multiple BSSID feature supports multiple virtual APs of a radio and advertises information for multiple BSSIDs by using a single beacon or probe response frame instead of multiple beacon or probe response frames, each corresponding to a single BSSID. Configuring 6 GHz Radio Band on AP-635 Access Points Following are the guidelines to ensure a successful deployment of AP-635 access points by configuring the 6 GHz radio band: n The virtual APs for 6 GHz radio band are disabled by default and must be enabled manually in the WLAN SSID settings of the virtual APs. To configure the WLAN SSID settings in the WebUI, navigate to Configuration > System > Profiles and select Wireless LAN> Virtual AP under All Profiles list, and enable the Allow 6GHz Band parameter. You can also enable the allowed-band-6ghz parameter in the wlan virtual-ap <profile> command. n To allow the 6 GHz clients to connect to the 6 GHz WLAN SSID, Aruba recommends the following steps: ArubaOS 8.9.0.0 Release Notes | Release Notes New Features and Enhancements in ArubaOS 8.9.0.0 | 11 a. Navigate to Configuration > System > Profiles and select Wireless LAN > Virtual AP under All Profiles list, and select none from the Allowed band drop-down list and enable the Allow 6GHz Band check box. You can also set the allowed-band parameter to none and enable the allowedband-6ghz parameter in the wlan virtual-ap <profile> command. b. Create an alternate WLAN SSID virtual AP on 2.4 GHz and 5 GHz radio bands. Navigate to Configuration > System > Profiles and select Wireless LAN> Virtual AP under All Profiles list, and select all from the Allowed Band drop-down list, and disable the Allow 6GHz Band check box. You can also set the allowed-band parameter to all and allowed-band-6ghz parameter to none in the wlan virtual-ap <profile> command. This allows 6 GHz clients to locate 6 GHz APs through Reduced Neighbor Report (RNR) in 2.4 GHz and 5 GHz beacons. For more information, refer to the ArubaOS 8.9.0.0 User Guide. Support for Wi-Fi 6E ARM ArubaOS supports ARM on Wi-Fi 6E access points. Support for Wi-Fi 6E AirMatch ArubaOS supports AirMatch on Wi-Fi 6E access points. Support for Wi-Fi 6E Air Management ArubaOS supports Air Management on Wi-Fi 6E access points. Support for Wi-Fi 6E Air Management Activity Detection ArubaOS supports Wi-Fi 6E Air Management activity detection on 6 GHz channels. Support for Wi-Fi 6E Air Management Information Element Parsing ArubaOS supports Wi-Fi 6E Air Management information element parsing on 6 GHz channels. Scanning Enhancements for Wi-Fi 6E Access Points Air Monitoring is enhanced to support scanning in the new Wi-Fi 6E AP-635 access points. Support for 6 GHz Radio ArubaOS supports configuration of the 6 GHz radio in the applicable access points. The 6 GHz radio can be configured in the RF management profile. Support Regulatory Domain Profile for 6 GHz Radio ArubaOS supports configuration of the regulatory domain profile for the 6 GHz radio. Support for Client Match for 6 GHz Radio 12 | New Features and Enhancements in ArubaOS 8.9.0.0 ArubaOS 8.9.0.0 Release Notes | Release Notes ArubaOS supports configuration of the client match for the 6 GHz radio. Support for EN302502 and EN301893 in UNI3 Bands The AP-374 outdoor access point supports EN302502 and EN301893 for DFS in UNI3 bands. Support for EN302502 allows the usage of higher power in the UNI3 band in ETSI and support for EN301893 allows radar detection. Support for GCM Ciphers on AP-555 Access Point AP-555 access point supports GCM ciphers. Support for Dropbear SSH ArubaOS supports Dropbear SSH version 2019.78. Client Match Support for 802.11v The Client Match process sends only the fields that are relevant to it in the protobuf format and the AP station management process populates the rest of the message. Enhancements to Multicast Group Limit Starting from ArubaOS 8.9.0.0, the multicast group limit per managed device is increased from 8 to 32. Enabling TLS Method for an External Logging Server Starting from ArubaOS 8.9.0.0, a new sub-parameter is introduced to enable TLS method defined in RFC5425. It can be used to secure log messages sent to an external logging server. Encrypt Private Key in the Flash Starting from ArubaOS, private key and passphrase are encrypted using TPM keys. Enhancements to number of PVST+ instances ArubaOS supports 128 PVST+ instances. Increase in Number of Tunneled Networks in VIA Starting from ArubaOS 8.9.0.0, VIA split tunnel network limit is increased to 256. Upgrade Notification for a Cluster Upgrade Starting from ArubaOS 8.9.0.0, the Maintenance > Software Management page in the Managed Network node hierarchy displays RAPs are present, upgrade may take longer time message when a cluster with Remote APs are upgraded. ArubaOS 8.9.0.0 Release Notes | Release Notes New Features and Enhancements in ArubaOS 8.9.0.0 | 13 Chapter 4 Supported Platforms in ArubaOS 8.9.0.0 Supported Platforms in ArubaOS 8.9.0.0 This chapter describes the platforms supported in this release. Mobility Conductor Platforms The following table displays the Mobility Conductor platforms that are supported in this release: Table 3: Supported Mobility Conductor Platforms Mobility Conductor Family Mobility Conductor Model Hardware Mobility Conductor MM-HW-1K, MM-HW-5K, MM-HW-10K Virtual Mobility Conductor 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 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, 9012 MC-VA-xxx Virtual Mobility Controllers MC-VA-10, 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 AP Family AP Model 200 Series AP-204, AP-205 203H Series AP-203H 203R Series AP-203R, AP-203RP 205H Series AP-205H ArubaOS 8.9.0.0 Release Notes | Release Notes 14 Table 5: Supported AP Platforms AP Family AP Model 207 Series AP-207 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, AP-303HR 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 370EX Series AP-375EX, AP-377EX, AP-375ATEX AP-387 AP-387 500 Series AP-504, AP-505 500H Series AP-505H 510 Series 530 Series 550 Series 560 Series 570 Series 635 Series AP-514, AP-515, AP-518 AP-534, AP-535 AP-555 AP-565, AP-567 AP-574, AP-575, AP-577 AP-635 15 | Supported Platforms in ArubaOS 8.9.0.0 ArubaOS 8.9.0.0 Release Notes | Release Notes Chapter 5 Regulatory Updates in ArubaOS 8.9.0.0 Regulatory Updates in ArubaOS 8.9.0.0 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_80922 ArubaOS 8.9.0.0 Release Notes | Release Notes 16 Chapter 6 Resolved Issues in ArubaOS 8.9.0.0 Resolved Issues in ArubaOS 8.9.0.0 This chapter describes the resolved issues in this release. Table 6: Resolved Issues in ArubaOS 8.9.0.0 New Bug ID Old Bug ID Description Reported Version AOS-200515 AOS-219987 -- The DDS process crashed on managed devices ArubaOS running ArubaOS 8.3.0.10 or later versions. The fix 8.3.0.10 ensures that the managed devices work as expected. AOS-209352 -- Some managed devices terminating VIA connection ArubaOS displayed the error message, httpd[30106]: Reached 8.6.0.5 session limit: 64. The fix ensures that the managed devices work as expected. This issue was observed in managed devices running ArubaOS 8.6.0.5 or later versions. AOS-211545 AOS-217654 -- Some APs crashed and rebooted unexpectedly. The log ArubaOS files listed the reason for the event as, Reboot caused 8.5.0.10 by kernel panic: Fatal exception in interrupt. The fix ensures that the APs work as expected. This issue was observed in APs running ArubaOS 8.5.0.10 or later versions. AOS-212386 -- The Configuration > Licensing tab of the WebUI did ArubaOS not display any data. The fix ensures that the WebUI 8.3.0.0 displays the licensing details. This issue occurred when high availability was configured. This issue was observed in Mobility Conductors running ArubaOS 8.3.0.0 or later versions. AOS-212755 -- Some users connecting to AP-505 access points ArubaOS running ArubaOS 8.7.0.0 were unable to pass traffic 8.7.0.0 intermittently. The fix ensures that clients are able to pass traffic. AOS-213337 -- A few AP-325 access points running ArubaOS 8.5.0.10 ArubaOS or later versions crashed unexpectedly. The log files 8.5.0.10 list the reason for the event as Reboot caused by kernel panic: Fatal exception in interrupt. The fix ensures that the APs work as expected. AOS-214391 AOS-217130 AOS-217832 -- The STM process crashed on 7240XMcontrollers. The ArubaOS fix ensures that the controllers work as expected. This 8.4.0.0 issue was observed in 7240XMcontrollers running ArubaOS 8.4.0.0 or later versions. ArubaOS 8.9.0.0 Release Notes | Release Notes 17 Table 6: Resolved Issues in ArubaOS 8.9.0.0 New Bug ID Old Bug ID Description Reported Version AOS-214416 -- Some stand-alone controllers running ArubaOS 8.6.0.6 ArubaOS or later versions displayed the error message, An 8.6.0.6 internal system error has occurred at file main.c function rx_handler line 1517 error sxdr_read_str_ safe szFunctionName failed. The fix ensures that the stand-alone controllers work as expected. AOS-214510 AOS-219139 -- A few clients were disconnected from the network. The ArubaOS log files listed the reason for the event as Wlan driver 8.6.0.5 excessive tx fail quick kickout. The fix ensures seamless connectivity. This issue was observed in managed devices running ArubaOS 8.6.0.5 or later versions. AOS-214846 -- The status of the APs was incorrectly displayed as ArubaOS down. The fix ensures that the Mobility Conductors 8.5.0.9 display the correct status of APs. This issue was observed in Mobility Conductors running ArubaOS 8.5.0.9 or later versions. AOS-215669 -- Some managed devices running ArubaOS 8.6.0.7 or ArubaOS later versions crashed and rebooted unexpectedly. The 8.6.0.7 log file listed the reason for the event as Datapath timeout (Heartbeat Initiated) (Intent:cause:register 53:86:50:4). The fix ensures that the managed devices work as expected. AOS-216536 AOS-220630 -- Some managed devices running ArubaOS 8.5.0.11 or ArubaOS later versions are unable to come up on the Mobility 8.5.0.11 Conductor. This issue occurs when the managed devices get the branch IP address as the controller IP address in a VPNC deployment. AOS-216777 -- The Mobility Conductor was unable to recover. This ArubaOS issue was observed when the flash memory was 100% 8.9.0.0 used in the Mobility Conductor. Once the flash space is increased as per SKU requirements, the Mobility Conductor recovers. This issue is observed in ArubaOS 8.9.0.0 version. AOS-215852 -- Mobility Conductors running ArubaOS 8.6.0.6 or later ArubaOS versions log the error message, ofa: 8.6.0.6 07765|ofproto|INFO|Aruba-SDN: 1 flow_mods 28 s ago (1 modifications). This issue occurs when openflow is enabled and when 35 seconds is configured as UCC session idle timeout. AOS-216145 -- Mobility Conductors running ArubaOS 8.5.0.8 or later ArubaOS versions sent continuous DNS requests to the 8.5.0.8 managed devices. This issue occurred when a folder that was not available on the /mm node was trying to get synchronized on the managed devices. The fix ensures that the Mobility Conductors do not send continuous DNS requests to the Managed Devices. 18 | Resolved Issues in ArubaOS 8.9.0.0 ArubaOS 8.9.0.0 Release Notes | Release Notes Table 6: Resolved Issues in ArubaOS 8.9.0.0 New Bug ID Old Bug ID Description Reported Version AOS-216536 AOS-220630 -- Some managed devices running ArubaOS 8.5.0.11 or ArubaOS later versions were unable to come up on the Mobility 8.5.0.11 Conductor. This issue occurred when the managed devices received the branch IP address as the controller IP address in a VPNC deployment. The fix ensures that the managed devices are able to come up on the Mobility Conductor. AOS-217104 AOS-219159 -- The ESI redirect failed and traffic was forwarded to the ArubaOS default gateway. The fix ensures that the managed 8.6.0.6 devices work as expected. This issue was observed in managed devices running ArubaOS 8.6.0.6 or later versions. AOS-151022 AOS-188417 185176 The output of the show datapath uplink command displayed incorrect session count. The fix ensures that the the show datapath uplink command displays correct session count. This issue was observed in managed devices running ArubaOS 8.1.0.0 or later versions. ArubaOS 8.1.0.0 AOS-193231 AOS-200101 AOS-207456 -- The Dashboard > Infrastructure > Access Devices ArubaOS page of the WebUI displayed an error message, Error 8.5.0.3 retrieving information. The fix ensures that the WebUI displays the list of access devices. This issue was observed in Mobility Conductors running ArubaOS 8.5.0.3 or later versions. AOS-209093 AOS-210452 -- Some managed devices running ArubaOS 8.7.0.0 or ArubaOS later versions generated multiple AMON receiver 8.7.0.0 errors. The fix ensures that the managed devices work as expected. AOS-210198 -- The Dashboard > Security > Detected Radio page of ArubaOS the WebUI displayed incorrect number of Clients. The 8.6.0.5 fix ensures that the WebUI displays correct number of Clients. This issue was observed in Mobility Conductors running ArubaOS 8.6.0.5 or later versions. AOS-213011 AOS-219946 -- Packet loss was observed for a few clients during a ArubaOS cluster failover. This issue was observed in managed 8.5.0.10 devices running ArubaOS 8.0.0.0 or later versions. The fix ensures that the managed devices work as expected. AOS-214977 AOS-220420 -- Memory leak was observed in arci-cli-helper process. ArubaOS This issue occurred while running an API script. The fix 8.5.0.8 ensures that the APs work as expected. This issue was observed in APs running ArubaOS 8.5.0.8 or later versions. ArubaOS 8.9.0.0 Release Notes | Release Notes Resolved Issues in ArubaOS 8.9.0.0 | 19 Table 6: Resolved Issues in ArubaOS 8.9.0.0 New Bug ID Old Bug ID Description Reported Version AOS-215303 -- Users were unable to view file names in the ArubaOS Diagnostic > Technical Support > Copy Files page 8.5.0.11 of the WebUI. This issue occurred when Flash file system was selected as the source file. The fix ensures that users are able to view the file names in the Diagnostic > Technical Support > Copy Files page of the WebUI. This issue was observed in managed devices running ArubaOS 8.5.0.11 or later versions. AOS-215498 -- Some AP-535 access points running ArubaOS 8.5.0.11 ArubaOS or later versions detected false radar. The fix ensures 8.5.0.11 that the APs work as expected. AOS-215712 -- Mobility Conductors running ArubaOS 8.7.0.0 or later ArubaOS versions forwarded all syslog messages with severity 8.7.0.0 level marked as debug. This issue occurred when CEF format was enabled on the Mobility Conductor. The fix ensures that the Mobility Conductors work as expected. AOS-216512 -- The DHCP client / station related AMON message sent ArubaOS the mask, server IP address, and client IP address in a 8.6.0.6 reverse order to the AirWave server. The fix ensures that the Mobility Conductors work as expected. This issue was observed in Mobility Conductors running ArubaOS 8.6.0.6 or later versions. AOS-216622 -- A few APs running ArubaOS 8.7.0.0 or later versions ArubaOS incorrectly displayed the restricted flag, p = 8.7.0.0 Restriction mode in POE-AF/AT in the AP database even if the Ethernet port was disabled. The fix ensures that the APs work as expected. AOS-216764 -- Users were not redirected to the captive portal page. ArubaOS The fix ensures that the captive portal works as 8.7.1.0 expected. This issue was observed in managed devices running ArubaOS 8.7.1.0 or later versions in a cluster setup. AOS-216766 -- Some APs generated sapd coredump. The fix ensures ArubaOS that the APs work as expected. This issue was 8.5.0.11 observed in APs running ArubaOS 8.5.0.11 or later versions. AOS-216874 AOS-219841 -- Some users were unable to access the network and a ArubaOS network outage was also observed. This issue 8.5.0.11 occurred when the VRRP IP was removed from the datapath bridge table. The fix ensures that the managed devices work as expected. This issue was observed in managed devices running ArubaOS 8.5.0.11 or later versions. 20 | Resolved Issues in ArubaOS 8.9.0.0 ArubaOS 8.9.0.0 Release Notes | Release Notes Table 6: Resolved Issues in ArubaOS 8.9.0.0 New Bug ID Old Bug ID Description Reported Version AOS-216972 -- Some managed devices running ArubaOS 8.6.0.7 or ArubaOS later versions forwarded data frames that are larger 8.6.0.7 than the configured IPsec tunnel MTU value. The fix ensures that the managed devices do not forward data frames that are larger than the configured IPsec tunnel MTU value. AOS-217106 -- The no valid parameter of the ap regulatory- ArubaOS domain-profile command did not work while creating 8.6.0.7 a new regulatory profile. The fix ensures that the no valid parameter of the ap regulatory-domain-profile command works as expected. This issue was observed in controllers running ArubaOS 8.0.0.0 or later versions. AOS-217807 -- Some Remote APs took a long time to come up on a ArubaOS managed device. This issue occurred due to a delay in 8.6.0.5 allowlist-db synchronization between the Mobility Conductor and managed devices and when external authentication was enabled for Remote APs. The fix ensures that the Remote APs do not take a long time to come up on a managed device. This issue was observed in managed devices running ArubaOS 8.6.0.5 or later versions in a cluster setup. AOS-218012 -- The Maintenance tab of the WebUI displayed a list of ArubaOS clusters that were not configured for that particular 8.5.0.9 node. The fix ensures that the WebUI does not display clusters that are not configured for a particular node. This issue was observed in Mobility Conductors running ArubaOS 8.5.0.9 or later versions. AOS-218231 AOS-216177 -- Wireless users were unable to find a few wired clients. ArubaOS The fix ensures that the wireless users are able to find 8.7.1.1 the wired clients. This issue was observed in controllers running ArubaOS 8.7.1.1 or later versions. AOS-218622 -- Some APs running ArubaOS 8.6.0.6 or later versions ArubaOS crashed unexpectedly. The log files listed the reason 8.7.1.1 for the event as PC:aruba_wlc_ratesel_ getcurrate+0x24/0xd0 [wl_v6] Warm-reset. The fix ensures that the APs work as expected. AOS-218795 -- Downloadable user roles were not downloaded and ArubaOS hence, user roles were not assigned to the tunnel-node 8.7.1.2 users. The fix ensures that the user roles are assigned to the tunnel-node users. This issue was observed in managed devices running ArubaOS 8.7.1.2 or later versions. AOS-218822 -- High flash memory utilization was observed in Mobility ArubaOS Conductors running ArubaOS 8.5.0.10 or later 8.5.0.10 versions. The fix ensures that the Mobility Conductors work as expected. ArubaOS 8.9.0.0 Release Notes | Release Notes Resolved Issues in ArubaOS 8.9.0.0 | 21 Table 6: Resolved Issues in ArubaOS 8.9.0.0 New Bug ID Old Bug ID Description Reported Version AOS-219098 AOS-219914 -- Some devices were unable to connect to the network. ArubaOS The fix ensures seamless connectivity. This issue was 8.7.1.1 observed in APs running ArubaOS 8.7.1.1 or later versions. AOS-219098 AOS-219914 -- Some devices were unable to connect to the network. ArubaOS The fix ensures seamless connectivity. This issue was 8.7.1.1 observed in APs running ArubaOS 8.7.1.1 or later versions. AOS-219178 -- Clients connected to the anchor controller were unable ArubaOS to receive IP addresses. The fix ensures that the clients 8.3.0.7 are able to receive IP addresses. This issue was observed in managed devices running ArubaOS 8.3.0.7 or later versions. AOS-219214 -- The valid user ACL was reordered in stand-alone ArubaOS controllers running ArubaOS 8.6.0.8 or later versions. 8.6.0.8 The fix ensures that the ACL is not reordered. AOS-219328 -- SNMP configurations failed and the error message, ArubaOS Error: User (itam_net) should be created before 8.5.0.11 adding to the trap host was displayed. This issue occurred when the SNMP server v3 trap host which had the engine-id same as the engine-id of the controller was removed and added again. The fix ensures that the SNMP configurations do not fail. This issue was observed in managed devices running ArubaOS 8.5.0.11 or later versions. AOS-219365 -- Some APs running ArubaOS 8.7.0.0 or later versions ArubaOS rebooted sporadically. This issue occurred when the 8.7.1.1 smart antenna feature was enabled. The fix ensures that the APs work as expected. AOS-219376 -- Some users were unable to add VIA server details if ArubaOS the domain name exceeded 32 characters. The fix 8.7.1.2 ensures that the users are able to add VIA server details. This issue was observed in Mobility Conductors running ArubaOS 8.7.1.2 or later versions. AOS-219384 -- Some APs running ArubaOS 8.7.1.1 or later versions ArubaOS crashed unexpectedly. The log files listed the reason 8.7.1.1 for the event as PC is at wlc_nar_dotxstatus+0x450. The fix ensures that the APs work as expected. AOS-219390 -- The datapath process crashed on stand-alone ArubaOS controllers running ArubaOS 8.7.1.1 or later versions. 8.7.1.1 The log files listed the reason for the event as Reboot Cause: Datapath timeout (SOS Assert) (Intent:cause:register 54:86:50:2). This issue occurred when the op mode of the SSID profile was changed from WPA3-AES-CCM-128 to WPA3-CNSA. The fix ensures that the stand-alone controllers work as expected. 22 | Resolved Issues in ArubaOS 8.9.0.0 ArubaOS 8.9.0.0 Release Notes | Release Notes Table 6: Resolved Issues in ArubaOS 8.9.0.0 New Bug ID Old Bug ID Description Reported Version AOS-219627 AOS-218851 -- Clients were unable to connect to 2.4 GHz SSID of ArubaOS some APs. This issue occurred when the MAC address 8.7.1.1 of the Radio 1 was incorrect. The fix ensures seamless connectivity. This issue was observed in APs running ArubaOS 8.7.1.1 or later versions. AOS-219725 -- Some APs running ArubaOS 8.7.1.1 or later versions ArubaOS crashed unexpectedly. The log files listed the reason 8.7.1.1 for the event as PC is at wlc_nar_detach+0x8c. The fix ensures that the APs work as expected. AOS-219936 -- The stand-alone controller displayed the error ArubaOS message, Module Profile Manager is busy. Please 8.7.1.1 try later while configuring netdestination. The fix ensures that the stand-alone controllers work as expected. This issue was observed in stand-alone controllers running ArubaOS 8.7.1.1 or later versions. AOS-219978 AOS-220568 -- A few iPhone 12 Pro users experienced poor upstream ArubaOS network performance. This issue occurred when APs 8.7.1.2 operated in tunnel mode. The fix ensures optimal network performance. This issue was observed in APs running ArubaOS 8.6.0.9 or later versions in tunnel mode. AOS-220053 -- Some Remote APs went down on managed devices ArubaOS running ArubaOS 8.6.0.5 or later versions. This issue 8.6.0.5 occurred after a failover. The fix ensures that the Remote APs work as expected. AOS-220108 -- The OFA process crashed on Mobility Conductor ArubaOS Virtual Appliances running ArubaOS 8.6.0.6 or later 8.6.0.6 versions. This issue occurred when the show openflow debug ports command was executed. The fix ensures that the Mobility Conductor Virtual Appliances work as expected. AOS-220552 -- The Configuration > Services > Clusters page of the ArubaOS WebUI did not display the status of live upgrade. This 8.6.0.9 issue occurred when the cluster profile name had blank spaces. The fix ensures that the WebUI displays the status of live upgrade. This issue was observed in Mobility Conductors running ArubaOS 8.6.0.9 or later versions. AOS-221005 -- Some stand-alone controllers running ArubaOS 8.7.1.2 ArubaOS or later versions were stuck in reboot loop. The log 8.7.1.2 files listed the reason for the event as Nanny rebooted machine - fpapps process died (Intent:cause:register 34:86:50:2). The fix ensures that the stand-alone controllers work as expected. ArubaOS 8.9.0.0 Release Notes | Release Notes Resolved Issues in ArubaOS 8.9.0.0 | 23 Table 6: Resolved Issues in ArubaOS 8.9.0.0 New Bug ID Old Bug ID Description Reported Version AOS-221429 -- Downloadable user role was not applied correctly to ArubaOS the first user connecting in the split tunnel mode. The 8.6.0.9 fix ensures that the downloadable user role are applied correctly. This issue was observed in stand- alone controllers running ArubaOS 8.6.0.9 or later versions. AOS-221666 AOS-222708 -- Some Remote APs running ArubaOS 8.6.0.9 or later ArubaOS versions crashed and rebooted unexpectedly. The log 8.6.0.9 file listed the reason for the event as, Kernel panic - not syncing. The fix ensures that the Remote APs work as expected. AOS-224186 -- The show tech-support command did not display any ArubaOS information about the kernel crash and an error 8.6.0.9 message, No kernel crash information available was displayed. The fix ensures that the show tech support command displays crash related information. This issue was observed in stand-alone controllers running ArubaOS 8.6.0.9 or later versions. AOS-223839 -- The output of the show ap active command did not ArubaOS display any value for Outer IP. The fix ensures that the 8.6.0.9 command displays the Outer IP value. This issue was observed in Mobility Conductors running ArubaOS 8.6.0.9 or later versions. AOS-223797 -- The show ap remote auth-trace-buf command did ArubaOS not display any output. The fix ensures that the 8.6.0.9 command displays the output. This issue was observed in stand-alone controllers running ArubaOS 8.6.0.9 or later versions. AOS-222931 -- Some APs did not form active tunnels with the AAC. ArubaOS The fix ensures that the APs form tunnels with the AAC. 8.7.1.4 This issue was observed in managed devices running ArubaOS 8.7.1.4 or later versions. AOS-222904 -- A few USB clients connected to an Instant AP became ArubaOS inactive when the Instant AP was rebooted. The fix 8.6.0.6 ensures that the APs work as expected. This issue was observed in APs running ArubaOS 8.6.0.6 or later versions. AOS-222771 -- Some managed devices running ArubaOS 8.5.0.12 or ArubaOS later versions did not send SNMPv3 information to the 8.5.0.12 AirWave server. The fix ensures that the managed devices send SNMPv3 information to the AirWave server. 24 | Resolved Issues in ArubaOS 8.9.0.0 ArubaOS 8.9.0.0 Release Notes | Release Notes Table 6: Resolved Issues in ArubaOS 8.9.0.0 New Bug ID Old Bug ID Description Reported Version AOS-222754 -- The SNMP walk to managed devices failed when the ArubaOS SNMP requests had the IPv6 address of the controller. 8.4.0.1 This issue occurred when the primary managed device had VRRP IPv6 address configured. The fix ensures that the SNMP walk to managed devices do not fail. This issue was observed in managed devices running ArubaOS 8.4.0.1 or later versions. AOS-222540 AOS-224221 -- Some APs dropped EAPOL packets from the bridge ArubaOS mode wired port. The fix ensures that the APs do not 8.6.0.9 drop the EAPOL packets. This issue was observed in APs running ArubaOS 8.6.0.9 or later versions. AOS-221938 -- Some users were unable to download the VIA profile ArubaOS and were redirected to an incorrect link. This issue 8.5.0.0 occurred when users accessed VIA from a public network. The fix ensures that the users are able to download the VIA profile. This issue was observed in Mobility Conductors running ArubaOS 8.5.0.0 or later versions. AOS-221726 AOS-223220 -- Some managed devices running ArubaOS 8.7.1.1 or ArubaOS later versions were unable to form L2 clusters with its 8.7.1.1 peers. The fix ensures that the managed devices are able to form L2 clusters. AOS-221478 AOS-221569 AOS-221572 -- The auth process crashed on managed devices ArubaOS running ArubaOS 8.5.0.9 or later versions. This issue 8.5.0.9 occurred when the show auth-tracebuf mac command was executed. The fix ensures that the managed devices work as expected. AOS-221352 -- Some mesh links reported incorrect RSSI values. The ArubaOS fix ensures that the mesh links report correct RSSI 8.7.0.0 values. This issue was observed in APs running ArubaOS 8.7.0.0 or later versions. AOS-221225 -- Some AP-387 access points running ArubaOS 8.7.1.1 ArubaOS or later versions rebooted unexpectedly. The log files 8.7.1.1 listed the reason for the event as Reboot caused by kernel panic: Fatal exception. The fix ensures that the APs work as expected. AOS-221222 -- Some APs came up with the IDe flag and the show ap ArubaOS database command displayed the e flag even when 8.8.0.0 EST was not configured. This issue occurred when an external allowlist authentication was configured on the managed devices and also when CPsec enabled APs were brought up on the managed devices. The fix ensures that the APs work as expected. This issue was observed in managed devices running ArubaOS 8.8.0.0. ArubaOS 8.9.0.0 Release Notes | Release Notes Resolved Issues in ArubaOS 8.9.0.0 | 25 Table 6: Resolved Issues in ArubaOS 8.9.0.0 New Bug ID Old Bug ID Description Reported Version AOS-221144 -- ARP packets were not forwarded to the uplink switch ArubaOS when bcmc-optimization was enabled on the 8.5.0.9 controllers. This issue was observed in Mobility Conductors and managed devices running ArubaOS 8.5.0.9 or later versions. The fix ensures that the Mobility Conductors and managed devices work as expected. AOS-221018 AOS-220919 -- Some users were unable to connect to SSIDs. This ArubaOS issue occurred in 802.11r and MultiZone enabled 8.5.0.11 configurations. The fix ensures seamless connectivity. This issue was observed in APs running ArubaOS 8.5.0.11 or later versions. AOS-220903 -- The s flag indicating LACP striping was not displayed in ArubaOS the output of the show ap database long command 8.6.0.8 even when LLDP was enabled on two uplinks. The fix ensures that the show ap database long command displays the s flag when LLDP is enabled. This issue is observed in APs running ArubaOS 8.6.0.8 or later versions. AOS-220704 -- Some APs were incorrectly displayed under different ArubaOS clusters. The fix ensures that the APs are not displayed 8.5.0.11 under different clusters. This issue was observed in managed devices running ArubaOS 8.5.0.11 or later versions. AOS-224336 -- The IoT transport profile authentication failed. This ArubaOS issue occurred when a remote server was used. The fix 8.8.0.1 ensures successful authentication. This issue was observed in Mobility Conductors running ArubaOS 8.8.0.1 or later versions. AOS-223656 -- Some Remote APs are unable to come up on managed ArubaOS devices after a reboot. The fix ensures that the Remote 8.7.1.4 APs are able to come up on the managed devices. This issue was observed in managed devices running ArubaOS 8.7.1.4 or later versions. AOS-221093 AOS-222773 -- Mobility Conductors running ArubaOS 8.0.1.0 or later ArubaOS versions took a long time to process templates that 8.0.1.0 were sent to the managed devices. The fix ensures that the Mobility Conductors work as expected. AOS-222776 -- Some managed devices running ArubaOS 8.0.1.0 or ArubaOS later versions established IPsec tunnels with stale WAN 8.0.1.0 IP addresses. The fix ensures that the managed devices work as expected. AOS-220515 -- Some managed devices running ArubaOS 8.5.0.12, or ArubaOS later versions displayed the error message, |fpapps| 8.5.0.12 filling up the default gateway configuration. The fix ensures that the managed devices work as expected. 26 | Resolved Issues in ArubaOS 8.9.0.0 ArubaOS 8.9.0.0 Release Notes | Release Notes Table 6: Resolved Issues in ArubaOS 8.9.0.0 New Bug ID Old Bug ID Description Reported Version AOS-220398 -- A few clients in bridge mode were unable to connect to ArubaOS wpa2-psk SSIDs. The fix ensures that the clients in 8.6.0.8 bridge mode are able to connect to wpa2-psk SSIDs. This issue was observed in stand-alone controllers running ArubaOS 8.6.0.8 or later versions. AOS-220251 -- Some users experienced connectivity issues. This issue ArubaOS occurs when APs did not respond to the authentication 8.5.0.4 frames in MultiZone networks that had non-cluster zones and dot11r enabled Virtual APs. The fix ensures that the APs work as expected. This issue was observed in stand-alone controllers running ArubaOS 8.5.0.4 or later versions. AOS-220179 -- A few clients were unable to complete the SAE ArubaOS handshake. This issue occurred when the password of 8.8.0.0 an SSID profile was modified to a length greater than the existing password. The fix ensures that the SAE handshake is not interrupted. This issue was observed in APs running ArubaOS 8.8.0.0. AOS-218328 AOS-220026 AOS-223535 -- VRRP flapping was observed on managed devices ArubaOS running ArubaOS 8.6.0.4 or later versions and hence, 8.6.0.4 clients faced connectivity issues. The fix ensures that the managed devices work as expected. AOS-219803 -- XML query done on a non-existing user resulted in an ArubaOS invalid response. The fix ensures that the controller 8.7.1.2 responds as expected. This issue was observed in Controllers running ArubaOS 8.7.1.2 or later versions. AOS-219769 -- The rap-gre-mtu parameter of the ap system-profile ArubaOS command did not work as expected. The fix ensures 8.8.0.0 that the rap-gre-mtu parameter works as expected. This issue was observed in Mobility Conductors running ArubaOS 8.8.0.0 or later versions. AOS-219385 -- Some APs took a long time to come up on the backup ArubaOS data center after primary data center failover. The fix 8.5.0.10 ensures that the APs work as expected. This issue was observed in APs running ArubaOS 8.5.0.10 or later versions. AOS-219112 -- UBT clients hopped between VLANs. The fix ensures ArubaOS that the managed devices work as expected. This issue 8.7.1.1 was observed in managed devices running ArubaOS 8.7.1.1 or later versions. AOS-218661 -- The AP process crashed on managed devices running ArubaOS ArubaOS 8.7.1.1 or later versions. The fix ensures that 8.7.1.1 the managed devices work as expected. ArubaOS 8.9.0.0 Release Notes | Release Notes Resolved Issues in ArubaOS 8.9.0.0 | 27 Table 6: Resolved Issues in ArubaOS 8.9.0.0 New Bug ID Old Bug ID Description Reported Version AOS-218646 -- Some users connected to AP-515 access points ArubaOS running ArubaOS 8.6.0.7 or later versions experienced 8.6.0.7 degraded audio quality. The fix ensures that the clients do not experience degraded audio quality. AOS-218642 -- Some users were unable to access the internet. This ArubaOS issue occurred when client entries were not removed 8.5.0.11 by the managed devices even when CoA disconnect was triggered for the clients. The fix ensures that the clients are able to access the internet as expected. This issue was observed in managed devices running ArubaOS 8.5.0.11 or later versions. AOS-218488 AOS-219694 -- The management VLAN address of the Mobility ArubaOS Conductor was pointed to the Remote AP tunnel. The 8.3.0.0 fix ensures that the management VLAN address is not available in the Remote AP tunnel. This issue was observed in Mobility Conductors running ArubaOS 8.3.0.0 or later versions. AOS-219806 -- Some APs running ArubaOS 8.8.0.0 or later versions ArubaOS did not have the support for H2E advertisement. The 8.8.0.0 fix ensures that the APs support H2E advertisement in beacon and probe responses. AOS-218322 -- Some managed devices running ArubaOS 8.5.0.5 or ArubaOS later versions did not send SSID related information 8.5.0.5 during data collection. The fix ensures that the managed devices send SSID related information during data collection. AOS-214428 AOS-218277 -- The auth process crashed on managed devices ArubaOS running ArubaOS 8.5.0.11 or later versions. Hence, the 8.5.0.11 Remote APs rebooted and VIA users faced connectivity issues. The fix ensures that the managed deviceswork as expected. AOS-216152 AOS-218208 AOS-222478 -- Some clients were unable to connect to APs. The log ArubaOS file listed the reason for the event as, AP is resource 8.5.0.8 constrained. The fix ensures seamless connectivity. This issue was observed in APs running ArubaOS 8.5.0.8 or later versions. AOS-218162 -- The wired Ethernet port did not form GRE tunnel with ArubaOS the managed device. The fix ensures that the wired 8.7.1.1 Ethernet port forms GRE tunnel with the managed device. This issue was observed in managed devices running ArubaOS 8.7.1.1 or later versions. AOS-218117 AOS-219179 AOS-224575 -- The show ntp servers and show ntp status ArubaOS commands displayed the error message, Address 8.6.0.7 family for hostname not supported. However, the WebUI displayed the NTP servers. The fix ensures that the commands do not display the error message. This issue was observed in managed devices running ArubaOS 8.6.0.7 or later versions. 28 | Resolved Issues in ArubaOS 8.9.0.0 ArubaOS 8.9.0.0 Release Notes | Release Notes Table 6: Resolved Issues in ArubaOS 8.9.0.0 New Bug ID Old Bug ID Description AOS-217890 AOS-217741 AOS-217678 AOS-218131 AOS-217539 AOS-219010 AOS219952 AOS-220918 AOS-221298 -- A managed device running ArubaOS 8.5.0.10 or later versions crashed and rebooted unexpectedly. The log file listed the reason for the event as Reboot Cause: Datapath timeout (SOS Assert) (Intent:cause:register 54:86:50:2). The fix ensures that the managed devices work as expected. -- Mobility Conductors experienced timeout and did not send SNMP response to the AirWave server. The fix ensures that the Mobility Conductors work as expected. This issue was observed in Mobility Conductors running ArubaOS 8.5.0.11 or later versions. -- Some APs running ArubaOS 8.6.0.7 or later versions did not honor the user alias route src-nat ACL and tunnelled the traffic to managed devices. The issue occurred when a netdestination alias is configured in the ACL. The fix ensures that the APs work as expected. -- The auth process crashed in managed devices running ArubaOS 8.7.0.0 or later versions. The fix ensures that the managed devices work as expected. Reported Version ArubaOS 8.5.0.10 ArubaOS 8.5.0.11 ArubaOS 8.6.0.7 ArubaOS 8.7.0.0 ArubaOS 8.9.0.0 Release Notes | Release Notes Resolved Issues in ArubaOS 8.9.0.0 | 29 Chapter 7 Known Issues in ArubaOS 8.9.0.0 Known Issues in ArubaOS 8.9.0.0 This chapter describes the known issues and limitations observed in this release. Limitation Following is the limitation observed in this release. 6 GHz Channel Information in Regulatory Domain Profile ArubaOS does not display the 6 GHz channel information in the existing regulatory domain profile of Wi-Fi 6E APs by default. To include 6 GHz channel information, ensure that you change the country code to a different country code, apply the change, and then revert it to the original country code. Another option is to create a new regulatory domain profile that includes the 6 GHz channel information by default, or copy the existing regulatory domain profile into a new regulatory domain profile to save the configuration. The following example configures a regulatory domain profile and specifies a valid 6 GHz band. host) [mynode](config) #ap regulatory-domain-profile reg-635 host) [mynode] (Regulatory Domain profile "reg-635") #country-code US host) [mynode] (Regulatory Domain profile "reg-635") #valid-6ghz-channel 165 Known Issues Following are the known issues observed in this release. Table 7: Known Issues in ArubaOS 8.9.0.0 New Bug ID Old Bug ID Description Reported Version AOS- -- Mobility Conductor picks only 43% of the APs for cluster ArubaOS 218844 CRU. This issue is observed in Mobility Conductor 8.8.0.0 running ArubaOS 8.8.0.0. AOS- -- The VLAN configuration as part of conductorip or ArubaOS 219249 conductoripv6 command is not pushed from the 8.8.0.0 Mobility Conductor to a managed device after the zero touch provisioning process. This issue is observed on a managed device running ArubaOS 8.8.0.0. AOS- -- Mobility Conductors running ArubaOS 8.7.0.0 or later ArubaOS 222200 versions are unable to classify webrtc traffic. This issue 8.9.0.0 is observed during conference calls. ArubaOS 8.9.0.0 Release Notes | Release Notes 30 Table 7: Known Issues in ArubaOS 8.9.0.0 New Bug ID Old Bug ID Description Reported Version AOS- -- Some stand-alone controllers running in ArubaOS ArubaOS 223354 8.9.0.0 display the error message, Error upgrading 8.9.0.0 image: Basic image verification failed on Ancillary Image during the upgrade. Workaround: Issue the show storage command to ensure that the controller has enough flash storage. AOS- -- OpenFlow connection flaps between Mobility Conductor ArubaOS 223199 and managed devices. This issue occurs when the IPSec 8.9.0.0 tunnel MTU is set to a value lesser than 1500. This issue is observed in Mobility Conductors running ArubaOS 8.9.0.0. AOS- -- Datapath categorization does not work as expected for ArubaOS 223012 Skype4B calls. This issue occurs in Remote APs 8.9.0.0 operating in split-tunnel mode. This issue is observed in Mobility Conductors running ArubaOS 8.9.0.0. AOS- -- The inet_frag_secret_rebuild: hashfn ArubaOS 223807 (ffffffffc17679b8/ip6_hashfn) kernel debug messages 8.8.0.2 are observed on 7280 controllers running ArubaOS 8.8.0.2. This issue occurs during upgrade of the 7280 controllers. AOS- -- A few APs experience packet drop when clients roam ArubaOS 224042 between the APs. This issue is observed in APs running 8.9.0.0 ArubaOS 8.9.0.0. AOS- -- An rsync failure occurs on a managed device. This issue ArubaOS 224867 occurs during boot when the DHCP process wrongly 8.9.0.0 derives the switch IP as IP address of the Mobility Conductor. The IP address of the Mobility Conductor is subsequently configured as a FQDN in configuration. This issue is observed in a managed device running ArubaOS 8.9.0.0. AOS- -- A few Intel AX210 clients face connectivity issue while ArubaOS 222699 connecting to AP-635 access points operating in 6 GHz 8.9.0.0 AOS- band. This issue occurs when an existing non-Tx VAP is 223281 changed to Tx VAP. This issue is observed in AP-635 AOS- access points running ArubaOS 8.9.0.0. 223640 AOS- -- Both WebUI and CLI display incorrect logging severity. ArubaOS 222662 The output of the show logging server command 8.9.0.0 displays All as logging severity and the Syslog Servers table in the Configuration > System > Logging page displays the severity as Warning. This issue occurs only when logging severity is not configured. This issue is observed in Mobility Conductors running ArubaOS 8.9.0.0. 31 | Known Issues in ArubaOS 8.9.0.0 ArubaOS 8.9.0.0 Release Notes | Release Notes Table 7: Known Issues in ArubaOS 8.9.0.0 New Bug ID Old Bug ID Description Reported Version AOS- -- The Syslog Servers table in the Configuration > ArubaOS 222661 System > Logging page of the WebUI does not display 8.9.0.0 the port number. This issue occurs when port numbers are not configured. This issue is observed in Mobility Conductors running ArubaOS 8.9.0.0. AOS- -- The show logging server command does not display ArubaOS 222660 the status of BSD as enabled even if the TLS option is 8.9.0.0 enabled. This issue is observed in Mobility Conductors running ArubaOS 8.9.0.0. AOS- -- When Intel AX210 client is connected to TX VAP in 6GHz ArubaOS 221676 radio of 635 Series, it shows 70% or more ping drops 8.9.0.0 and keeps getting disconnected with reason "Wlan driver wireless client out of range (seq num 0)". This is an existing Intel driver side issue and known to occur in version 22.70.x.x or lower if used with AX210 chipsets. AOS- -- Some Intel AX clients face connectivity issues. This issue ArubaOS 220557 is observed in ArubaOS version 8.7.1.3 or later versions 8.9.0.0 in 635 Series, AP-555, AP-535. AOS- -- The Datapath process crashes on Mobility Conductors ArubaOS 220125 running ArubaOS 8.9.0.0. This issue occurs when the 8.9.0.0 packet size is larger than the configured IPsec tunnel MTU value. AOS- -- When Service AP is configured with PSK SSID, AP brings ArubaOS 219048 up the controller and configures Provision AP as WIFIUplink profile. The Service AP becomes unstable in the 8.9.0.0 controller. The AP's uplink is disconnected, resulting in loss of connection with the controller. This issue is observed in AP-335. AOS218578 In a dual stack setup, when there is a scheduled upgrade in MM, the upgrade fails consistently. This issue is observed in controllersMM-MD and Controller Build is ArubaOS70xx_8.8.0.0_79405. ArubaOS 8.9.0.0 AOS218219 A Microsoft Teams call with an external client does not get classified and prioritized.. This MS-Teams call is not classified and prioritized by UCC. This issue is observed in ArubaOS 8.8.0.0 or later versions. ArubaOS 8.9.0.0 AOS215989 Some APs running ArubaOS 8.8.0.0 or later versions experience low throughput. This issue occurs when the number of VAPs is increased. This issue occurs when HE MU-OFDMA parameters are enabled. This affects only HE MU-OFDMA capable client devices. ArubaOS 8.9.0.0 AOS213507 Some managed devices running ArubaOS 8.5.0.10 or later versions crash unexpectedly. The log files list the reason for the event as, Reboot Cause: Soft Watchdog reset ArubaOS 8.9.0.0 ArubaOS 8.9.0.0 Release Notes | Release Notes Known Issues in ArubaOS 8.9.0.0 | 32 Table 7: Known Issues in ArubaOS 8.9.0.0 New Bug ID Old Bug ID Description Reported Version AOS- -- The Upgrademgr process does not provide FQDN ArubaOS 213428 support for image servers. This issue is observed in 8.8.0.0 Mobility Conductors running ArubaOS 8.8.0.0 or later versions. AOS- -- The output of the show ap image-preload status ArubaOS 213345 <summary/all/list> command does not display the list 8.8.0.0 of APs. This issue is observed in managed devices in a cluster setup running ArubaOS 8.8.0.0 or later versions. AOS- -- The Maintenance > Software Management > Upload ArubaOS 212858 AOS image for controller page of the WebUI does not 8.8.0.0 allow users to delete multiple images simultaneously. This issue is observed in Mobility Conductors running ArubaOS 8.8.0.0 or later versions. AOS- -- The Maintenance > Software Management > Upload ArubaOS 212847 AOS image for controller page of the WebUI does not 8.8.0.0 allow users to upload multiple images simultaneously This issue is observed in Mobility Conductors running ArubaOS 8.8.0.0 or later versions. AOS- -- The status of the managed devices are displayed as ArubaOS 212288 UKN after an L2 fail over. This issue is observed in 8.8.0.0 Mobility Conductors and managed devices running ArubaOS 8.8.0.0 or later versions. AOS- -- Some clients are unable to roam between APs when co- ArubaOS 211655 ex is enabled. This issue is observed in AP-514 access 8.8.0.0 points running ArubaOS 8.8.0.0 or later versions. AOS- -- A Mobility Conductor fails to perform version check of ArubaOS 213157 managed devices during the image upgrade process. 8.8.0.0 This issue is observed in Mobility Conductors in a cluster setup running ArubaOS 8.8.0.0 or later versions. AOS- -- The newly configured VLANs are not displayed when the ArubaOS 212941 show vlan command is executed. This issue occurs 8.8.0.0 after a flash backup restore. This issue is observed in managed devices running ArubaOS 8.8.0.0 or later versions. AOS- -- The Controller field is not updated in the Dashboard> ArubaOS 211634 Services page of the WebUI. This issue occurs when a 8.8.0.0 cluster-failover happens during an ongoing Microsoft Teams call. This issue is observed in managed device running ArubaOS 8.8.0.0 or later versions. AOS- -- Microsoft Teams conference call is not supported. This ArubaOS 211453 issue is observed in managed devices running ArubaOS 8.8.0.0 8.8.0.0 or later versions. 33 | Known Issues in ArubaOS 8.9.0.0 ArubaOS 8.9.0.0 Release Notes | Release Notes Table 7: Known Issues in ArubaOS 8.9.0.0 New Bug ID Old Bug ID Description Reported Version AOS- -- The Cluster Members pop-up window in the ArubaOS 210383 Dashboard > Infrastructure > Clusters page of the 8.8.0.0 WebUI does not display any value for Hostname, Role, and Reachable fields. This issue occurs when the user configures IPv6 cluster in the WebUI. This issue is observed in Mobility Conductors running ArubaOS 8.8.0.0 or later versions in a Mobility Conductor- Managed Device topology. AOS- -- A few high efficiency clients experience poor ArubaOS 208640 performance with AP-505 access points running 8.7.1.0 AOS- ArubaOS 8.7.1.0 or later versions. This issue occurs 215865 when HE MU-OFDMA parameters are enabled. AOS- 219181 AOS- -- After a live upgrade is initiated, users are unable to stop ArubaOS 202352 the upgrade as the Cancel button in the Maintenance > 8.7.0.0 AOS- Software Management > Controllers and Clusters 202531 page of the WebUI does not work. This issue is observed managed devices running ArubaOS 8.7.0.0 or later versions. AOS- -- WPA3-AES-CCM-128 authentication fails for a few ArubaOS 222554 clients. This issue occurs in APs operating in 6 GHz 8.9.0.0 AOS- channels. This issue is observed in APs running ArubaOS 222612 8.9.0.0. AOS- -- Cluster live upgrade fails and the WebUI displays an ArubaOS 211070 error message, Controller <IP adrress > is down. This 8.8.0.0 issue occurs when an IPv6 enabled managed device establishes an IPv4 connection with the Mobility Conductor. This issue is observed in Mobility Conductors running ArubaOS 8.8.0.0 or later versions. AOS- -- A Mobility Conductor does not accept applying a valid ArubaOS 223903 XML file that is generated in Python for IPv6 relay-option 8.9.0.0 and IPv4 option 82. The Mobility Conductor displays the Filename <sample.xml> has invalid keywords error. This issue is observed in a Mobility Conductor running ArubaOS 8.9.0.0. AOS- -- When a policy has both WebCC and AppRF rules, the ArubaOS 221963 Mobility Controller classifies all traffic as ssl, https or 8.9.0.0 http2. This issue is observed in Mobility Controllers running ArubaOS 8.9.0.0. AOS- -- The scheduled upgrade information of cluster and ArubaOS 225201 managed device is not displayed in the WebUI and CLI. 8.9.0.0 This issue is observed in Mobility Conductor running ArubaOS 8.9.0.0. ArubaOS 8.9.0.0 Release Notes | Release Notes Known Issues in ArubaOS 8.9.0.0 | 34 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 Conductor, managed device, or standalone controller. Important Points to Remember To upgrade your managed device or Mobility Conductor: 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 Conductor Licensing Guide. n Multiversion is supported in a topology where the managed devices are running the same version as the Mobility Conductor, or two versions lower. For example multiversion is supported if a Mobility Conductor 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.9.0.0 Release Notes | Release Notes 35 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 in Table 8 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 the 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 Conductor, navigate to Diagnostic > Technical Support > Delete Files and remove any aging log files or redundant backups. In the CLI (host) #delete filename <filename> Low Free Flash Memory Sometimes, after extended use, the flash memory might get used up for logs and other files. The ArubaOS image has increased in size and this may cause issues while upgrading to newer ArubaOS images without cleaning up the flash memory. Prerequisites Before you proceed with the freeing up the flash memory: n Ensure to always backup the configuration and flash memory. Issue the backup configuration and backup flash commands to backup the configuration and flash. 36 | Upgrade Procedure ArubaOS 8.9.0.0 Release Notes | Release Notes n Copy the flashbackup.tar.gz and configbackup.tar.gz files out of the controller. Then delete the flashbackup.tar.gz and configbackup.tar.gz files from the flash memory of the controller. n Use only one partition for the upgrade activity and keep the other partition unchanged. If you use the WebUI to perform an upgrade, a banner on the Maintenance page provides the following reminder to have sufficient free flash memory before initiating an upgrade. For a healthy and stable system it requires free space of 360 MB for AOS v8.3 and 8.5, 570 MB for AOS 8.6 and 8.7 and 450 MB for AOS 8.8 and higher version in the /flash directory. Please make sure minimum required memory is available in /flash before upgrading to newer version. Freeing up Flash Memory The following steps describe how to free up the flash memory before upgrading to ArubaOS 8.9.0.0: 1. Check if the available memory in /flash is greater than the limits listed in Table 8 for all supported controller models: Table 8: Flash Memory Requirements Upgrading from Upgrading to 8.3.x 8.9.x 8.5.x 8.9.x 8.6.x 8.9.x 8.7.x 8.9.x 8.8.x 8.9.x 8.9.x 8.9.x Minimum Required Free Flash Memory Before Initiating an Upgrade 360 MB 360 MB 570 MB 570 MB 450 MB 450 MB To check the available free flash memory, issue the show storage command. Following is the sample output from a controller with low free flash memory: (host) [mynode] #show storage Filesystem Size Available Use % Mounted on /dev/usb/flash3 1.4G 1014.2M 386.7M 72% /flash 2. If the available free flash memory is less than the limits listed in Table 8, issue the following commands to free up more memory. n tar crash n tar clean crash n tar clean logs n tar clean traces 3. Issue the show storage command again to check if the available space in /flash is more than the minimum space required for ArubaOS upgrade as listed in Table 8 4. If sufficient flash memory is available, proceed with the standard ArubaOS upgrade. See Upgrading ArubaOS. ArubaOS 8.9.0.0 Release Notes | Release Notes Upgrade Procedure | 37 5. If a reboot was performed, you may see some of the following errors. Follow the directions below: n Upgrade using standard procedure. You may see some of the following errors: Error upgrading image: Ancillary unpack failed with tar error ( tar: Short header ). Please clean up the /flash and try upgrade again. Error upgrading image: Ancillary unpack failed with tar error ( tar: Invalid tar magic ). Please clean up the /flash and try upgrade again. Error upgrading image: Need atleast XXX MB space in /flash for image upgrade, please clean up the /flash and try upgrade again. Failed updating: [upgradeImageNew.c] extractAncTar (dev: /dev/usb/flash1 imgLoc: /flash/config/ArubaOS_70xx_8.8.0.0-mm-dev_78066 n If any of the above errors occur, issue the show image version command to check for the default boot partition. The partition which was upgraded should become the default partition. Following is the sample output of the show image version command: (host) [mynode] #show image version ---------------------------------- Partition : 0:0 (/dev/usb/flash1) **Default boot** Software Version : ArubaOS 8.9.0.0 (Digitally Signed SHA1/SHA256 - Production Build) Build number : 81046 Label : 81046 Built on : Thu Aug 5 22:54:49 PDT 2021 ---------------------------------- Partition : 0:1 (/dev/usb/flash2) Software Version : ArubaOS 8.7.0.0-2.3.1.0 (Digitally Signed SHA1/SHA256 - Developer/Internal Build) Build number : 0000 Label : arpitg@sdwan-2.3_arpitg-3-ENG.0000 Built on : Tue Aug 10 15:02:15 IST 2021 n If the default boot partition is not the same as the one where you performed the upgrade, change the default boot partition. Issue the boot system partition <part_number> command to change the default boot partition. Enter 0 or 1 for part_number representing partition 0:0 or partition 0:1, respectively. n Reload the controller. If any of the errors listed in step 4 were observed, the following errors might occur while booting ArubaOS 8.9.0.0. Sample error: [03:17:17]:Installing ancillary FS [ OK ] Performing integrity check on ancillary partition 1 [ FAIL : Validating new ancillary partition 1...Image Integrity check failed for file /flash/img1/mswitch/sap/arm32.ari. Digest Mismatch] Extracting Webui files..tar: Short read chown: /mswitch/webui/*: No such file or directory chmod: /mswitch/webui/wms/wms.cgi: No such file or directory n After the controller reboots, the login prompt displays the following banner: ******************************************************************** * WARNING: An additional image upgrade is required to complete the * * installation of the AP and WebUI files. Please upgrade the boot * * partition again and reload the controller. * ******************************************************************** n Repeat steps 1 through 5. If sufficient free flash memory is available, proceed with the standard ArubaOS upgrade procedure. See Upgrading ArubaOS. n If sufficient free flash memory is not available, issue the dir and dir flash commands to identify large files occupying the flash memory. 38 | Upgrade Procedure ArubaOS 8.9.0.0 Release Notes | Release Notes Exercise caution while deleting files. Contact Technical Support if you are not sure which large files in the /flash directory could be safely deleted to free up the required space. n Issue the delete filename <filename> command to delete large files to free more flash memory. n Check if sufficient flash memory is free as listed in Table 8. n Proceed with the standard ArubaOS upgrade procedure in the same partition. See Upgrading ArubaOS. ArubaOS 8.8.0.0 and 8.8.0.1 The following steps describe how to free up the flash memory before upgrading to ArubaOS 8.8.0.0 or 8.8.0.1: 1. Follow the steps 1 through 4 listed in Freeing up Flash Memory before upgrading to ArubaOS 8.8.0.0 or 8.8.0.1. 2. If sufficient flash memory is still not available, issue the dir to identify large files occupying the flash memory. Exercise caution while deleting files. Contact Technical Support if you are not sure which large files in the /flash directory could be safely deleted to free up the required space. 3. Issue the delete filename <filename> command to delete large files to free more memory. 4. Check if sufficient flash memory is free as listed in Table 8. 5. If sufficient flash memory is not available, do not proceed with the upgrade. Contact Technical Support. ArubaOS 8.9.0.0 Release Notes | Release Notes Upgrade Procedure | 39 Backing up Critical Data It is important to frequently back up all critical configuration data and files on the flash memory to an external server or mass storage device. You should include the following files in these frequent backups: n Configuration data n WMS database n Local user database n Licensing database n Custom captive portal pages n x.509 certificates n Log files n Flash backup 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 Conductor 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: 40 | Upgrade Procedure ArubaOS 8.9.0.0 Release Notes | Release Notes (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. ArubaOS 8.9.0.0 Release Notes | Release Notes Upgrade Procedure | 41 Upgrading ArubaOS Upgrade ArubaOS using the WebUI or CLI. Ensure that there is enough free memory and flash space on your Mobility Conductor or managed device. For details, see Memory Requirements on page 36. 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 Conductor or managed device will not load a corrupted ArubaOS image. 4. Log in to the ArubaOS WebUI from the Mobility Conductor. 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 Conductor 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. 42 | Upgrade Procedure ArubaOS 8.9.0.0 Release Notes | Release Notes 2. Open an SSH session to your Mobility Conductor. 3. Execute the ping command to verify the network connection between the Mobility Conductor 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 Conductor. (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 Conductor 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. ArubaOS 8.9.0.0 Release Notes | Release Notes Upgrade Procedure | 43 In the CLI The following steps describe how to verify that the Mobility Conductor 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. 44 | Upgrade Procedure ArubaOS 8.9.0.0 Release Notes | Release Notes Downgrading ArubaOS A Mobility Conductor or managed device has two partitions, 0 and 1. If the upgrade fails on one of the partitions, you can reboot the Mobility Conductor or managed device from the other partition. Pre-requisites Before you reboot the Mobility Conductor or managed device with the pre-upgrade ArubaOS version, perform the following steps: 1. Back up your Mobility Conductor 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 Conductor or managed device to boot with the previously saved configuration file. 4. Set the Mobility Conductor 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 Conductor 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 Conductor 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 Conductor or managed device by navigating to the Diagnostics > Technical Support > Copy Files page. 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. ArubaOS 8.9.0.0 Release Notes | Release Notes Upgrade Procedure | 45 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 Conductor or managed device reboots after the countdown period. 4. When the boot process is complete, verify that the Mobility Conductor 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 Conductor 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 Conductor 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 Conductor or managed device. (host) # reload 6. When the boot process is complete, verify that the Mobility Conductor or managed device is using the correct ArubaOS version. (host) # show image version 46 | Upgrade Procedure ArubaOS 8.9.0.0 Release Notes | Release Notes 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. ArubaOS 8.9.0.0 Release Notes | Release Notes Upgrade Procedure | 47