AOS-228598

AOS-246281

The LINK/ACT LED of 9004 gateways remained off even when a working LAN cable was connected to the port. The fix ensures the LED works appropriately(solid green when link is established and blinking green when transmitting or receiving data). This issue was observed on 9004 gateways running ArubaOS 8.10.0.0 or later versions.

AOS-228764

A few AP-655 access points crashed and rebooted unexpectedly. The log files listed the reason for the event as: PC is at cnss_wait_for_cold_boot_cal_done+0xe0/0x124. The fix ensures the access points work as expected. This issue was observed in AP-655 access points running ArubaOS 8.10.0.0 or later versions.

AOS-232832

AOS-232962

AOS-233456

AOS-236010

AOS-236698

AOS-237445

AOS-240627

AOS-240765

AOS-241680

AOS-242454

AOS-242648

AOS-242649

AOS-242725

AOS-244622

AOS-245722

Some managed devices crashed and rebooted unexpectedly. The log files listed the reason of the event as, Reboot Cause: soft Watchdog reset (Intent:cause:register de:86:70:4). The fix extracts additional data from the system at the time of the crash for further analysis. This issue was observed in managed devices running ArubaOS 8.6.0.1 or later versions.

AOS-232997

Some managed devices running ArubaOS 8.7.1.9 or later versions were stuck after an upgrade and the aaa process crashed. The issue occurred due to memory corruption. The fix ensures that the managed devices work as expected.

AOS-235285

AOS-242646

Some controllers were sending commands from Central On-Premises to the APs, but the response was not received. This issue occurred since the port used by the handling process was closed for external communications. As a result, no response was received in Analyze > Tools > Commands > Device Output in Central UI. The fix ensures that the responses are received as expected. This issue was observed in controllers running ArubaOS 8.9.0.0 or later versions.

AOS-236889

AOS-243540

Some managed devices running ArubaOS 8.5.0.13 or later versions were unable to fetch user information through controller API calls. The show user command output often displayed: This operation can take a while depending on number of users. Please be patient, with no following response. The fix ensures managed devices fetch the data as expected, without displaying the error message.

AOS-237479

Some APs were unable to form standby tunnels with the cluster nodes. This issue occurred due to a race condition. The fix ensures the APs work as expected. This issue was observed in access points running ArubaOS 8.7.1.7 or later versions.

AOS-238424

AOS-247791

Some access points displayed the error, file amon.c function amon_get_ant_gain line 4223 error invalid band 2. The issue occurred when the 6 GHz radio band was disabled. The fix ensures the error is not displayed in such cases. This issue was observed in AP-635 and AP-655 access points running ArubaOS 8.10.0.7 or later versions.

AOS-238729

AOS-241593

In some APs, when the DNS traffic reached the Broadband gateway, the traffic was forwarded upstream but natting did not take place. As a result, the AP did not come online in Central. The fix ensures the APs display as expected. This issue was observed in APs running ArubaOS 8.6.0.20 or later versions.

AOS-238803

AOS-246511

Controllers running ArubaOS 8.10.0.7 or later versions logged continuous error messages such as |web_cc| Failed GSM publish web_cc_gsm_publish. The fix ensures that the controllers' web content classification functionality works as expected

AOS-239282

Clients were unable to connect to AP-505H mesh access points. The log files listed the reason for this event as UAC Down. The fix ensures seamless connectivity. This issue was observed in AP-505H mesh access points running ArubaOS 8.7.1.9 or later versions.

AOS-239417

Some AP-535 access points rebooted due a low memory condition. The reboot cause was kernel panic: softlockup: hung tasks. The fix ensures memory is handled properly. This issue was observed in AP-535 access points running ArubaOS 8.10.0.4 or later versions.

AOS-239459

AOS-248389

Mobility Conductors running ArubaOS 8.10.0.7 or later versions continuously logged multiple unnecessary errors related to the mon_serv_fwv process. The logs pre-fixed the errors as |mon_serv_fwv| mon_serv_gsm_handle_device_config_add. The fix ensures these unnecessary logs are not displayed in the CLI.

AOS-240026

AOS-236177

AOS-239232

AOS-240068

AOS-240633

Some customers were unable to access controllers through the CLI or WebUI. This issue was related to third-party monitoring tools such as Armis, which caused the CLI sessions to be kept open for a long time accumulating memory leaks, affecting the functioning of the controller. The fix ensures customers are able to access controllers as expected. This issue was observed in controllers running ArubaOS 8.6.0.18 or later versions.

AOS-241083

AOS-242823

Some access points crashed and rebooted unexpectedly. The log files listed the reason for the crash as ar_wal_tx_de.c:331 Assertion failed. The issue was related to the AP image version found in previous versions of ArubaOS. The fix contains a patch for the AP image that resolves the error. This issue was observed in APs running ArubaOS 8.10.0.5 or later versions.

AOS-241150

Branch Gateways running ArubaOS 8.10.0.0 or later versions failed to send accounting information during TACACS authentication of management users. This issue occurred because, on gateway reload, the ctrlmgt process came up after the TACACS accounting packets were sent from the auth process. As a result, the accounting information was lost during authentication. The fix resolves the timing issue between the ctrlmgt and auth processes after gateway reload.

AOS-241158

The running configuration did not match the previous configuration after upgrading from 6.5.x to 8.x versions. The fix ensures that previous configurations are retained when upgrading to 8.x versions. This issue was observed in standalone 7010 controllers running ArubaOS 8.0.0.0 or later versions.

AOS-241532

AOS-245370

Some Mobility Conductors repeatedly displayed the error message, WMS PGRES_FATAL_ERROR, which filled the logs. The fix ensures that the devices operate as expected. This issue was observed in Mobility Conductors running ArubaOS 8.10.0.5 or later versions.

AOS-241709

The auth process crashed unexpectedly when ACLs and downloadable-user roles assigned to a VIA client were configured from CPPM. The fix ensures the controller works as expected. This issue was observed in Mobility Controllers running ArubaOS 8.6.0.0 or later versions.

AOS-241833

Remote APs operating in a dual-stack environment with an IPv4 IPSEC experienced heartbeat loss after IPSEC re-key when IPv6 was inadvertently used. The fix ensures no heartbeat misses are seen on RAPs when IPSEC re-keying happens. The issue was seen on Remote AP-505H access points running ArubaOS 8.10.0.5 or later versions.

AOS-242003

Moving files from Mobility Controllers to FTP using API POST caused the error: /mm/mynode" COMMAND: -- command execution failed. The issue was fixed by adding a missing parameter in the UI mapping table. This issue was observed in Mobility Conductors running ArubaOS 8.10.0.5 or later versions.

AOS-242635

When using the Submit As button or de-selecting options, the de-selected options were not generated properly. The fix ensures the configuration works as expected. This issue was observed in devices running ArubaOS 8.0.0.0 or later versions.

AOS-242888

Users were unable to use the SSH command when the fourth octet of the IPv4 address was set to 0 or 255. The fix ensures that the SSH command works as expected. This issue was observed in Mobility Controllers running ArubaOS 8.10.0.6 or later versions.

AOS-243714

AOS-246688

The syslogdwrap process crashed when configuring the syslog server and the TLS option was not enabled. As a result, incorrect TLS flag values were set. The fix ensures that flag values are set correctly, even when TLS option is not enabled. This issue was observed in some Gateways running ArubaOS 8.9.0.0 or later versions.

AOS-243888

Some 7240XM controllers crashed and rebooted unexpectedly. The issue was related to an STM process crash when several forward-mode bridge profiles were configured. The fix ensures the STM process executes as intended. This issue was observed in 7240XM controllers running ArubaOS 8.10.0.5 or later versions.

AOS-244091

AOS-244610

AOS-246131

AOS-246450

Some AP-534 access points crashed and rebooted unexpectedly. The log files listed the reason of the event as, Reboot caused by kernel panic: Take care of the TARGET ASSERT first. It’s WLAN firmware assert at “wmi_tlv_helper.c:305 Assertion (in_tlv_len + (1 * sizeof(A_UINT32)))==attr_struct_ptr.tag_struct_size). The fix ensures the access points work as expected. This issue was observed in access points running ArubaOS 8.10.0.5 or later versions.

AOS-244167

Mobility Controllers incorrectly sent ACK messages in response to RFC-5176 Disconnect-Message Requests when in Bridge Mode, which is not supported. The fix ensures that no ACK messages for RFC-5176 are sent. This issue was observed in Mobility Controllers running ArubaOS 8.10.0.6 or later versions.

AOS-244231

Option 82 information was missing for the first DHCP discover packet in some controllers running ArubaOS 8.11.0.0 or later versions. The fix ensures that the option 82 information is tagged correctly in the first DHCP discover packet.

AOS-244384

The Windows 10 Filesharing (SMBv2) download speed was slower when connected to AP-515 access points, or 9240 controllers compared to other devices. The fix ensures an improvement in download speeds. This issue was observed in AP-515 access points and 9240 controllers running ArubaOS 8.10.0.5 or later versions.

AOS-244398

AOS-244429

AOS-244743

AOS-244767

AOS-246357

AOS-247460

The amon udp command was used to enable AirWave to allow traffic on UDP port 8211. Due to security change, PAPI drops some AMON feeds between the Mobility Conductor and Managed Devices. This issue is resolved after deprecating the amon udp command. This issue was observed in controllers running ArubaOS 8.8.0.0 or later versions.

AOS-244949

Some APs crashed and rebooted due to mismatch in Pending twt sessions count and current twt session issues. This fix will count the number of pending twt sessions properly so that mismatch does not occur during WMI event send instance. This issue was observed in AP-535 access points running ArubaOS 8.10.0.6 or later versions.

AOS-245001

The wired aaa-profile configuration disappeared after the managed device restarted due to incorrect case sensitive checks. The fix ensures that the wired aaa-profile configuration is retained when the device restarts. This issue was observed in managed devices running ArubaOS 8.10.0.6 or later versions.

AOS-245094

In some controllers running ArubaOS 8.6.0.21 or later versions, some Phone home log activity was observed although this feature was disabled. The logs were shown in the output of the phonehome now command. The fix ensures no logging activity occurs in this scenario.

AOS-245145

AOS-236547

In the WebUI, under Configuration > Roles & Policies > Role > role-name > Show Advanced View > Captive Portal, the preview button for custom HTML captive portal page was not available. The fix ensures the preview button is present. This issue was observed in some 7210 controllers running ArubaOS 8.10.0.6 or later versions.

AOS-245260

Some AP-325 access points were detecting radar signals only in 40 MHz DFS channels. No radar hits were detected when changed to 20 MHz channel. This issue occurred due to wireless interference in the environment. The fix ensures false radar signals are rejected. This issue was observed in APs running ArubaOS 8.6.0.18 or later versions.

AOS-245334

Some Remote APs were intermittently bootstrapping after a conflict with IP types received. The fix ensures IP types are checked and Remote APs perform as expected. This issue was observed in AP-503H and AP-303H Series access points running ArubaOS 8.10.0.4 or later versions.

AOS-245379

Some access points crashed and rebooted unexpectedly. The log files listed the reason as Reboot caused by kernel panic: Take care of the TARGET ASSERT first. It’s WLAN firmware crash at “wlan fw crash at sched_algo_qos.c:1530 sched_algo_choose_qos_tid_type”. The fix ensures the access points work as expected. This issue was observed in AP-534, AP-535, AP-555, AP-634, AP-635, and AP-655 access points running ArubaOS 8.10.0.6 or later versions.

AOS-245401

HE capabilities were configured on the beacon and probe response for 2.4GHz radio even though the HE setting was disabled. The fix ensures that HE capabilities are not configured on the beacon and probe response when the HE setting is disabled. This issue was observed in 500 Series access points running ArubaOS 8.9.0.0 or later versions.

AOS-245409

Some users were unable to pass traffic to the captive portal after a rebootstrap. This issue occurred when APs could not source NAT the traffic due to Back-up LMS having more DNS entries than LMS. When the AP changed LMS to Back-up LMS, the DNS ID table was not downloaded correctly. A correction of the DNS ID table resolved the issue. This issue was observed in access points in split-tunnel mode running ArubaOS 8.6.0.9 or later versions.

AOS-245516

AOS-246187

AOS-247197

AOS-247520

AOS-247521

AOS-248022

In some AP-634 access points the 5 GHz radio with traffic was continuously resetting. The unexpected number of resets may have introduced packets loss. The fix ensures the APs perform as expected. This issue was observed in devices running ArubaOS 8.10.0.7 or later versions.

AOS-245519

In some controllers running ArubaOS 8.10.0.0 or later versions, the system automatically restarted when the system was halted using the LCD menu. The fix ensures controller works as expected without restarting.

AOS-245656

In the Configuration > Interfaces > Ports page of the WebUI, selecting a port channel displayed the details, but after navigating to physical port, the configuration was not displayed.  As a result, the page had to be reloaded. The fix ensures the information is displayed as expected. This issue was observed in controllers running ArubaOS 8.10.0.7 or later versions

AOS-245657

The show airmatch optimization command incorrectly displayed a sequence of numbers, showing 4 digits instead of 5. The fix ensures that the command's output displays the correct sequence of numbers. This issue was observed in controllers running ArubaOS 8.0.0.0 or later versions.

AOS-245689

In some controllers running ArubaOS 8.10.0.7 or later versions, the HA-flags value was not shown in the output of the show ha ap table command. This fix ensures that this value is populated.

AOS-245784

The ap convert pre-validate function did not work correctly when applied to Remote APs running ArubaOS 8.10.0.0 or later versions. The fix ensures the function works as expected on Remote APs.

AOS-245853

Managed devices were ignoring Radius VSA for Aruba-Admin-Role. This issue occurred when authentication management was enabled and performing certificate authentication using the WebUI. The Controller was getting updated with wrong role, even though cppm sent the correct one. The fix ensures the role is obtained from VSA and is updated accordingly. This issue was observed in devices running ArubaOS 8.10.0.7 or later versions.

AOS-245874

AOS-246405

Some AP-503 access points crashed and rebooted unexpectedly. The log files listed the reason of the event as, Panic: MemLeak: mem low for 46593 seconds, under 0MB 927882 times, MB free 8 (1%), total 740 Warm-reset. The fix ensures the access points work as expected. This issue was observed in access points running ArubaOS 8.6.0.21 or later versions.

AOS-245931

In the Configuration > System > Logging page of the WebUI, the Duplicate combination of IP address and Category error was displayed when adding arm-user-debug entry, if arm entry already existed. The fix ensures the error message is not displayed in this scenario. This issue was observed in controllers running ArubaOS 8.10.0.7 or later versions.

AOS-245939

AOS-245445

In some controllers the ap_crash_transfer_check error log was generated when core file transfers failed using TFTP. As a result, unnecessary log files were accumulating. The fix ensures the log file is not generated in this scenario. This issue was observed in controllers running ArubaOS 8.10.0.0 or later versions.

AOS-245976

In some controllers running ArubaOS 8.10.0.4 or later versions, the admin management user entry could not be deleted on Mobility Conductors and standalone switches. The issue occurred because the deletion of the admin management user was not allowed nor supported by default. The fix ensures that the admin user can be deleted from Mobility Conductors or standalone switches, if there is at least one root user already configured.

AOS-245980

Some clients connected to AP-535 access points on the 5 GHz band experienced significant packet loss to the gateway and increased latency during calls when LACP was enabled on the controller. The issue was observed when both the GRE-Stripping IP was configured and the AP-LACP was activated on the AP. The fix ensures APs work as expected. This issue was observed in access points running ArubaOS 8.6.0.18 or later versions.

AOS-246003

Some AP-505 access points crashed and rebooted unexpectedly. The log files listed the reason for the event as: BadAddr:fecf3ca8 PC:dev_get_iflink+0x0/0x28 Warm-reset. This issue occurred in an IPsec environment, where a tunneled device was deleted after IPsec encryption. The fix ensures proper validations are made, preventing the AP crash. This issue was observed in devices running ArubaOS 8.6.0.21.

AOS-246051

Some controllers were unable to copy an image from the flash memory to the system partition. The error seen for this operation was: Error determining image version. The fix ensures the controller copies an image successfully. This issue was observed in 7200 Series controllers running ArubaOS 8.10.0.7 or later versions.

AOS-246097

Some AP-535 access points randomly disabled the ANI feature. The issue was due to an unintended trigger of the ANI periodic check, which disabled the feature. The fix ensures that the ANI feature stays enabled when configured to do so. This issue was observed in AP-535 access points running ArubaOS 8.10.0.7 or later versions.

AOS-246124

AOS-247640

In some 7240XM controllers, a Kernel crash was observed due to an incorrect memory assignment in the rt6i_node pointer. The fix converts the direct assignment of rt6i_node pointer to rcu_assign_pointer, to ensure that the pointer assignment never fails. This issue was observed in controllers running ArubaOS 8.10.0.7 or later versions.

AOS-246203

Some AP-635 access points unexpectedly rebooted. The log files listed the reason for the event as: PC is at ieee80211_get_he_bsscolor_info+0xfc/0x7a8 [umac]. The fix ensures the access points work as expected. This issue was observed in AP-635 access points running ArubaOS 8.10.0.0 or later versions.

AOS-246263

Mobility Conductors running ArubaOS 8.10.0.7 or later versions experienced an unexpected mDNS process crash. The issue was related to buffer data corruption while responding to query packets having sub-ptr records. The fix ensures the mDNS process executes as expected.

AOS-246324

AOS-252197

MongoDB experienced corruption issues after the Mobility Controller rebooted. As a result, an error message, A/C power cycle was displayed. The issue occurred due to multiple processes in INIT state, which caused the corruption issues. The fix ensures customers can run the process cleanup name dbstart_mongo command for database cleanup when needed. This issue was observed in Mobility Controllers running ArubaOS 8.10.0.8 or later versions.

AOS-246395

The 9240 controllers were not detecting SFP+ transceivers. The fix ensures the modules work as expected. This issue was observed in 9240 controllers running ArubaOS 8.10.0.0 or later versions.

AOS-246409

AOS-246862

AOS-246945

AOS-247150

AOS-248556

Some access points crashed and rebooted unexpectedly. The log files listed the reason for the crash as FW assert PC:0x4b23a454 : ar_wal_tx_send.c:16021. The issue was related to the AP image version found in previous versions of ArubaOS. The fix contains a patch for the AP image that resolves the error. This issue was observed in 500 Series APs running ArubaOS 8.10.0.7 or later versions.

AOS-246583

A 7240XM Mobility Controller experienced unexpected crashes as a result of a failure in the tnld_node_mgr process. The fix ensures the process works as expected. This issue was observed in Mobility Controllers running ArubaOS 8.10.0.7 or later versions.

AOS-246617

After upgrading to ArubaOS 8.10.0.7, some APs crashed and rebooted unexpectedly, disconnecting every 2-3 hours due to IPv6 packet synchronization problems. The crash logs listed the reason for the error as Panic:Ktrace core monitor: cpu3 hung for 45 seconds, hung cpu count: 1 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.21 or later versions.

AOS-246839

The usage of ECDSA certificates in a web-server profile caused the unavailability of the WebUI. The fix ensures the WebUI works as expected when using ECDSA certificates. This issue was observed in controllers running ArubaOS 8.10.0.7 and 8.10.0.7-FIPS or later versions.

AOS-246966

Some Mobility Conductors crashed and rebooted unexpectedly. The log files listed the reason of the event as, Reboot Cause: Datapath timeout (SOS Assert) (Intent:cause:register 54:86:50:2) Supervisor Card. The crash occurred due to the processing of a corrupted buffer, which was mistakenly interpreted as an IPv6 crypto SA, resulting in a datapath crash. The fix involves validating key parameters in the buffer before processing, thereby preventing the crash. This issue was observed in Mobility Conductors running ArubaOS 8.10.0.7 or later versions.

AOS-247718

Data traffic was not flowing through the tunnels between the APs and the controller, even though the tunnel was restored. The fix ensures data traffic seamlessly flows through the tunnels between devices. This issue was observed access points running ArubaOS 8.10.0.7 or later versions.

AOS-248121

The AVS process caused AP-577 access points to crash after recovering from low temperatures, the AVS voltage was not high enough. An increase of the AVS default voltage fixed the issue. This issue was observed in AP-577 access points running ArubaOS 8.10.0.0 or later versions.