AOS-219791

AOS-248243

The ARM profile settings mistakenly enabled aggressive scanning mode by default, which was not intended for daily production use. This issue was observed in access points running AOS-10.4.0.1 or later versions.

The fix ensures that aggresive scanning is not enable after inital scanning is competed.

AOS-231206

AOS-262808

The WPA3 SAE process crashed unexpectedly for gateways running AOS-10.4.1.0 or later versions. This issue occurred due to a timer corruption, but it did not affect the connectivity of the already connected clients.

The fix ensures that the WPA3 SAE process does not crash on the gateways.

AOS-244334

AOS-247602

AOS-247934

AOS-261989

Some APs running AOS-10.4.0.2 rebooted randomly. Although the APs were connected to a POE switch via the Eth0 port, the system displayed the power source as a DC supply.

The fix ensures that the AP does not undergo a random warm reset, and the system displays the correct information about the connected power source.

AOS-245435

AOS-262007

Users were unable to upgrade gateways to AOS-10.4.1.4 or later versions. The log files listed the reason for event as, Upgrade: failed: File copied successfully. Saving file to flash: Error upgrading image: defaultkernel = 1 make this the default kernel to boot from.

The fix ensures a successful upgrade.

AOS-245985

AOS-261062

Some 605R Series access points crashed and rebooted unexpectedly. Log files listed the reason for the event as AP, Reboot reason: BadAddr: 303d7595 PC: esp_ssg_unref+0x0/0xb4 Warm-reset. This issue occurred when access to a deleted tunnel was attempted.

The issue was fixed by adding checks to ensure that a deleted tunnel is not accessed.

AOS-246514

Some AP-535 access points running AOS-10.7.1.0 or later versions crashed and rebooted with reason, QDF BUG in target_if_dbr_replenish_ring Line 1063: Failed assertion '0'.

The fix ensures that the APs do not crash.

AOS-248680

AOS-250829

Some AP-575 and AP-515 access points running (Undefined variable: Variables.ArubaOS) 10.4.1.4 or later versions crashed and rebooted with the reason, BUGSoftLockup: CPU#1 stuck for 23s! [kworker/1:3:20931] PC: __udelay+0x34/0x48 Warm-reset.

The fix ensures that the APs do not crash.

Duplicates: AOS-257826, AOS-258832, AOS-258938, AOS-259259, AOS-259303, AOS-259775, AOS-263493.

AOS-248877

The gateway management and control channel connection experienced intermittent disconnection and reconnection on gateways running AOS-10.4.0.0. The issue was linked to the fastdpi service that eventually caused channel flaps.

The fix ensures that the channel does not flap frequently.

AOS-250117

The VOIP and PS aware scan rejects counter was not incrementing on 2.4GHz, 5GHz, and 6GHz radio frequencies. This issue was observed in some AP-654 access points running AOS-10.4.0.3 or later versions.

The fix ensures that the VOIP and PS aware scan rejects counter increments correctly.

AOS-251602

AOS-255118

AOS-257207

AOS-260667

AOS-264562

The CTB Agent module crashed on 7240XM gateways running AOS-10.4.1.0 and rebooted unexpectedly. This issue occurred due to kernel panic.

The issue was resolved by handling the buffer issue.

AOS-252234

AOS-262908

Some APs running AOS-10.7.0.1 or later versions rebooted unexpectedly. The log files listed the reason for the event as TPM operation timed out, rebooting to recover. This issue occurred because the TPM chip occasionally entered a bad state, requiring a reboot to restore normal operation.

The issue is resolved by introducing a recovery mechanism that checks the TPM chip status every 60 seconds, and automatically triggers a reboot if a bad state is detected.

AOS-253595

AOS-254792

Multiple VGWs running on AOS-10.4.0.2 were offline in HPE Aruba Networking Central with EST Status as Failed and SSL connection establishment failed error. The issue occurred because of the re-enrollment date.

The issue was resolved by assigning a valid subscription keys to the VGWs.

AOS-253999

AOS-257689

AOS-259596

AOS-263311

Some APs randomly crashed and rebooted with the error message, Reboot caused by kernel panic: CPU 0 stall. This issue was observed in AP-635 and AP-655 access points running AOS-10.4.1.0 or later versions.

The fix ensures the APs do not crash.

AOS-254679

AOS-263383

The wired traffic client dropped and failed to obtain an IP from the gateway. The client's DHCP traffic dropped on the AP and was not forwarded to the ATA tunnel endpoints.

The fix ensures that DHCP traffic is forwarded through the tunnel, allowing clients to obtain IP addresses as expected.

AOS-255831

When the maximum number of CoA disconnect retries were reached, the gateway log displayed an error message. However, the error message did not include the AP name. 

The fix ensures that the AP details are displayed in the error message.

AOS-255852

AOS-260238

AOS-260241

Some APs failed to establish a connection via OOF channel running AOS-10.7.0.0 or later versions.

The fix ensures that the connection is established and work as expected.

AOS-256160

Users were unable to save the AP tech-support log for AP-515 access points. The issue was observed in APs running AOS-10.7.1.0 or later versions.

The fix ensures that tech support log collection is optimized, and users can save the logs successfully.

AOS-256243

AOS-257527

AOS-264635

In some HPE Aruba Networking 9000 Series gateways running AOS-10.4.1.7 or later versions, the CPU exhibited unpredictable behavior due to complex micro-architectural conditions.

The fix ensures that the BIOS automatically updates with the latest CPU microcode updates.

AOS-256254

Tunnel events were displayed when the bucketmap was updated after the gateways reloaded. This issue was observed in HPE Aruba Networking 7210 gateways running AOS 10.4.1.1 or later versions.

The fix ensures that the tunnel events are not displayed.

AOS-256514

AOS-262812

Some AP-635 access points running AOS-10.4.1.5 or later versions crashed and rebooted unexpectedly. The log files listed the reason for the event as, fw crash with ar_wal_tx_send.c:8488 Assertion.

The fix ensures that the APs work as expected.

AOS-256627

The WAN Summary page displayed the Usage and Throughput value as 0. The issue occurred when the gateway read only the first port-member for stats and ignored the other port members wherein the Uplink VLANS were configured over multi-ports and port-channels. This issue was observed on 9240 gateways running AOS-10.5.0.1.

The fix ensures that the WAN Summary page displays correct values.

AOS-256714

AOS-261383

A few gateways incorrectly displayed the IP address of an AP instead of the client in the authentication success logs for 802.1x SSIDs. This issue was seen in HPE Aruba Networking 7240XM gateways running AOS-10.6.0.3 or later versions.

The fix ensures that the authentication success logs display the client IP address appropriately.

AOS-256794

Some Branch Gateways with routes to passive Virtual Gateways in its routing table caused asymmetric routing issues. This issue occurred because the Branch Gateway tunnel was down.

The fix ensures that the Branch Gateways work as expected.

AOS-256820

AOS-261886

Some AP-635 and AP-655 access points running AOS-10.6.0.1 rebooted unexpectedly. The log files listed the reason for the event as Reboot caused by kernel panic: Fatal exception in interrupt.

The fix ensures that the APs do not crash.

AOS-256998

Some 7240 Branch Gateways running AOS-10.4.1.1 or later versions experienced WAN redundancy failure and the virtual uplink became unreachable. This issue occurred when the branch gateways were upgraded to AOS-10.4.1.1.

The fix ensures that WAN redundancy works as expected for the branch gateway.

AOS-257453

A router connected on the LAN side of an Aruba 9004-LTE Branch Gateway could not form an IPSEC tunnel using the LTE uplink. This issue was observed in 9004-LTE Branch Gateways running AOS-10.4.1.3.

The fix ensures that IPSEC tunnel is established from a LAN device using LTE interface.

AOS-257568

AOS-264539

Some APs running on AOS-10.7.0.2 rebooted randomly. The log files listed the reason for the reboot as InternalError: 96000210 [#1] SMP PC: phy_utils_write_phyreg_nopi+0x70.

The fix ensures that the APs work as expected.

AOS-257588

AOS-260636

AOS-260785

Some APs did not age out clients although the station ageout timer parameter was configured to the default value of 1000 seconds.

The fix ensures that the APs age out clients according to the station ageout timer parameter. This issue was observed in AP-535 access points running AOS-10.6.0.3 or later versions.

AOS-258040

AOS-260100

AOS-260111

AOS-260811

AOS-260961

AOS-261010

Some AP-577 access points, running AOS-8.10.0.9 or later versions, rebooted unexpectedly. The log files listed the reason for the reboot as, BUGSoftLockup:CPU#1 stuck for 22s! [kworker/1:3:27856] PC:wlc_bmac_suspend_mac_and_wait+0x21c/0x440 [wl_v6].

The fix ensures that the APs work as expected.

AOS-258265

AOS-261167

The Radproxy module crashed repeatedly causing authentication timeout on the 7280 gateway devices, running AOS-10.4.1.2.

The fix ensures that clients are able to connect to the network.

AOS-258287

AOS-263109

The Alerts & Events > Alerts page displayed false AP impersonation alerts under the Infrastructure Attack Detected category in HPE Aruba Networking Central. This issue occurred after enabling IDS on APs, where the APs impersonated their own BSSIDs. This issue was observed in APs running AOS-10.7.0.1 or later versions.

The fix ensures that the alerts are displayed correctly, preventing false impersonation detections.

AOS-258307

Some HPE Aruba Networking 7240XM gateways running AOS-10.4.1.0 or later versions crashed and rebooted unexpectedly. The log file listed the reason for the event as, Reboot Cause: Nanny rebooted machine - fpapps process died (Intent:cause:register 34:86:50:2). This issue was observed on gateways with an uptime of more than 100 days and that handle a large number of WLAN access points terminating on them.

The fix ensures that the gateways do not crash.

AOS-258406

Some wireless clients were randomly assigned with the default_wired_port_profile role. This issue was observed in AP-515 access points running AOS-10.4.1.4 or later versions.

The fix ensures that the APs work as expected.

AOS-258447

AOS-261443

A few APs crashed and rebooted unexpectedly when they were downgraded from AOS-10.6.0.3 to AOS-10.4.1.5. The log files listed the following reasons:

Reboot caused by kernal Panic: Fatal exception in interrupt for AP-535 and AP-555 access points

AP Reboot reason: BadAddr:a0a0a0300727d PC:bom_db_connection_match+0x0/0xb8 [bom] Warm-reset for AP-518 access points.

The fix ensures that the APs work as expected.

AOS-258467

AOS-259396

AOS-261527

Clients were unable to connect to 802.1x SSIDs on 630 Series access points running (Undefined variable: Variables.AOS)-10.6.0.3 or later versions. This issue occurred because the client was not aged out for both associated and NONE-state clients.

The fix ensures that clients are able to connect to 802.1x SSIDs.

AOS-258911

AOS-262747

The Radproxy process crashed several times when the gateway was initializing after an upgrade. The log files listed the error as, ncfg_server_getnext_load_balance. The crash occurred because TACACS server received a NULL value in the Radproxy process. This issue was observed in gateways running AOS-10.6.0.3 or later versions.

The fix ensures that the Radproxy process does not crash.

AOS-259003

AOS-260285

Some 9004 branch gateways running AOS-10.4.1.4 crashed and rebooted unexpectedly. The log files listed the reason as, Reboot Cause: Kernel Panic (Intent:cause: 86:50) . This issue is related to the IOMMU configuration in the 9000 Series.

The fix ensures that the gateways do not crash and work as expected.

AOS-259022

Executing ping ipv6 interface vlan <Link local ipv6 address> source <vlan ID> command caused CLI crash on the gateways running AOS-10.7.1.0.

The fix ensures that gateways do not crash on execution of the ping ipv6 interface vlan command.

AOS-259108

Clients passed authentication but client traffic was dropped by the gateway. The issue occurred when user-role was enabled with explicit deny and policy to action vxlan encapsulation. This issue was observed in gateways running AOS-10.7.0.0 or later versions.

The fix ensures that client traffic goes through correct pipelines and is permitted/denied correctly according to source user-role.

AOS-259178

HPE Aruba Networking 9106 gateways crashed and rebooted unexpectedly due to datapath timeout exception, with IDPS enabled.

The fix ensures that the gateways do not crash.

AOS-259202

Users were unable to establish Point-to-Point Tunneling Protocol (PPTP) connection as gateways were dropping PPTP packets. This issue occurred when Network Address Translation (NAT) was enabled on the gateway. This issue was observed on 9004 gateways running AOS-10.4.1.3 or later versions.

The fix ensures correct forwarding of PPTP packets in NAT scenarios.

AOS-259241

HPE Aruba Networking Central connection and OAP channel incorrectly showed connectivity issues even when the gateway had an active LTE uplink. This issue was observed in gateways running AOS-10.5.1.1 or later versions.

The issue was resolved by showing correct connectivity information in HPE Aruba Networking Central.

AOS-259265

Gateway LTE modem did not set PLMN setting when configured manually in LTE uplink configuration due to which Global LTE SIM was unable to switch to different vendors.

The fix ensures that the Global LTE SIM is able to switch to different vendors.

AOS-259428

AOS-261205

When NAT was enabled on user VLANs, there was an issue where WebCC ACL rule hits were incremented even if there was no traffic matching the rule.

The fix ensures that only the matching traffic increments ACL hits instead of all web traffic. This issue was observed on gateways running AOS-10.4.1.4 or later versions.

AOS-259466

AOS-261385

AP-735 access points running AOS-10.7.1.0 crashed when changes to the channel or bandwidth were made through HPE Aruba Networking Central. Additionally, there were instances where the access point did not respond to frequency or bandwidth adjustments initiated from the UI.

AOS-259604

AOS-260047

Some AP-635 access points running AOS-10.4.1.4 or later versions crashed unexpectedly. The log files listed the reason for the event as, Reboot caused by kernel panic: Take care of the TARGET ASSERT first.

The fix ensures that the APs work as expected.

AOS-259633

AOS-259710

AOS-260680

AOS-260958

AOS-261675

Some access points crashed and rebooted unexpectedly when multiple users were connected, and the PS mode was activated. The issue arose from dropped packets due to insufficient capacity in the PS queue, resulting in AP crashes. This issue was observed on APs running AOS-10.4.1.5 or later versions.

The fix ensures that the APs work as expected.

AOS-259648

AOS-264900

The gateway Go Live data continued to load, but no output was displayed in the device's WAN tab. This issue was observed in 9100 Series gateways running AOS-10.4.0.2 or later versions.

The fix ensures that the gateway Go Live data displays output correctly.

AOS-259667

AOS-259798

The Access Control Entries (ACEs) for Branch Gateways displayed under Overview > Sessions > Sessions table in HPE Aruba Networking Central UI did not match the client traffic data based on the configured policies. However, the CLI displayed accurate information in the datapath output collected from the client. This issue was observed in Branch Gateways running AOS-10.4.1.1 or later versions.

The fix ensures that HPE Aruba Networking Central UI displays accurate data for the configured policies.

AOS-259668

AOS-261408

AOS-258305

Some AP-365 access points crashed unexpectedly. The files listed the reason for the reboot as, Kernel panic: Take care of the TARGET ASSERT. This issue was observed in AP-365 access points running AOS-10.4.1.4 or later versions.

The fix ensures the APs do not crash randomly.

AOS-259713

When users upgraded the software version to AOS-10.6.0.3 or later versions, they were unable to access the www.gov.uk website if the WebCC cache-miss-drop feature was enabled. This was observed in 9004 gateways.

The fix ensures that the URL is categorized and cached correctly in Datapath.

AOS-259798

The Access Control Entries (ACEs) for Branch Gateways displayed under Overview > Sessions > Sessions table in HPE Aruba Networking Central UI did not match the client traffic data based on the configured policies. However, the CLI displayed accurate information in the datapath output collected from the client. This issue was observed in Branch Gateways running AOS-10.4.1.1 or later versions.

The fix ensures that HPE Aruba Networking Central UI displays accurate data for the configured policies.

AOS-259860

Some AP-655 access points crashed and rebooted unexpectedly. The log files listed the reason for the event as, Reboot after internal watchdog dump saved. The issue was observed in APs running AOS-10.4.1.7 or later versions.

The fix ensures that the APs work as expected.

AOS-259868

A few AP-635 access points running on AOS-10.7.0.0 rebooted unexpectedly due to kernel panic. The log files listed the reason for reboot as, Rebooting the AP. NSS FW crashed. The issue occurred because of the duplicated cookie used in rx descriptors.

The fix ensures that the access points work as expected.

AOS-259882

There was a difference in the values displayed for conductor IP and interface IP (Br0) for AOS-10 AP present in the same sub-net. This issue was seen when STM restarted because the uplink manager did not update the conductor IP when the IP address changed. The issue was observed in APs running AOS-10.4.1.7 or later versions.

The fix ensures that the same address is displayed for conductor IP and interface IP.

AOS-260096

Some AP-655 access points crashed and rebooted unexpectedly. The log files listed the reason for the event as, Reboot after internal watchdog dump saved. The issue was observed in APs running AOS-10.5.1.1 or later versions.

The fix ensures that the APs work as expected.

AOS-260223

A gaming console could not connect to a WPA3 pre-shared key SSID on 600 Series access points. The authentication failed due to a message integrity check failure. This issue occurred due to a timing issue within the station management module.

The fix ensures that the timing event does not occur and the gaming console connects as expected.

AOS-260224

The results of memory related OIDs were negative in the SNMP walk. This issue was observed in AP-735 access points running AOS-10.7.0.1 or later versions.

The fix ensures that memory-related OID results are positive in the SNMP walk.

AOS-260248

Proxy server did not accept usernames with special characters.

The fix ensures that users can leverage special characters for creating usernames for proxy servers.

AOS-260258

AOS-260383

On running show ap arm neighbor and show ap monitor ap-list commands, the output did not list the 5-GHz BSSID neighbors. This issue occurred on some AP-535 access points running AOS-10.4.0.2 and later versions.

The fix ensures that the show ap arm neighbor and show ap monitor ap-list commands display the correct output.

AOS-260293

AOS-260317

AOS-264512

AOS-264514

AOS-264516

AOS-264535

Some access points running AOS-10.7.0.1 rebooted unexpectedly. The log files listed the reason for the event as BadPtr:0000004e PC:spktq_deq+0x14/0x88 [wl_v6] Warm-reset.

The fix ensures that the APs work as expected.

AOS-260354

AOS-261752

AOS-262316

Some AP-535 access points running AOS-10.6.0.3 crashed and rebooted unexpectedly, due to memory leaks. The log file listed the reason for the event as, Reboot caused by kernel panic: MemLeak: mem low for 1800 seconds, under 102MB 1400551 times, free 43MB (2%), total 1702MB.

The fix addresses the memory issue for the AP.

AOS-260357

The APs did not send out accounting start after the client machine authentication when the AP had a machine authentication token. This issue was observed in APs running AOS-10.7.0.1 or later versions.

The fix ensures that the AP sends accounting start after client machine authentication.

AOS-260363

AOS-261914

AOS-262403

Some clients connected to 500 Series access points experienced latency and performance issues.

The fix brings back the latency and performance to the expected level for these clients. This issue was observed in access points running AOS-10.6.0.3 or later versions.

AOS-260367

AP-635 access points running AOS-10.6.0.2 crashed repeatedly. This issue occurred due to corruption in the /etc/dnsmasq.conf configuration file.

The fix ensures that APs do not crash, and work as expected.

AOS-260386

Some users intermittently disconnected from the internet and experienced DHCP timeouts from HPE Aruba Networking Central events when connected to AP-635 access points running AOS-10.6.0.1. This issue occurred when SSID in the tunnel mode and bridge mode coexisted on AP and bridge mode SSID with dynamic vlan assignment.

The fix ensures that the users are not disconnected from the network.

AOS-260391

High channel utilization (99%) and interference was observed on all 2.4 GHz channels (1,6,11). Clients were unable to connect with 2.4 GHz when channel utilization was high. This issue was observed in AP-635 access points running AOS-10.6.0.1.

The fix ensures that clients are able to connect on the 2.4 GHz channel.

AOS-260423

AOS-263539

Some access points crashed unexpectedly due to memory spikes under heavy traffic. The log files listed the reason for the crash as __efistub_memcpy+0x48/0x180. This issue was observed in APs runningAOS-10.4.1.0 or later versions.

The fix ensures APs do not encounter any memory issues.

AOS-260475

AOS-260960

A few AP-505 and AP-615 access points crashed unexpectedly after the upgrade from AOS-8 to AOS-10. The log file listed the reason for this event as, AP Reboot reason: BadPtr: 00000006 PC: fips_selftest_gcm+0x1cc/0x36c [fips_tool] Warm-reset. This issue occurred as the APs were in FIPS mode before the upgrade, which is not supported in AOS-10.

The fix ensures that the FIPS mode is disabled by default on AOS-10 versions.

AOS-260590

Data loss was observed in gateways and Zscaler tunnels when WAN redundancy was enabled.

The fix ensures that gateways work as expected. This issue was observed in gateways running AOS-10.4.1.0 or later versions.

AOS-260599

When clients connected to a Branch Gateway pinged clients on the DC side and vice versa, a 50% packet drop was observed during the switch from the backup LTE cellular uplink to the primary uplink. This issue was observed in Branch Gateways running AOS-10.4.1.5 or later versions.

The fix ensures that the IPSec map updates are processed when the LTE cellular uplink status changes to DOWN.

AOS-260853

AOS-261560

Users observed that stale client entries in the station table were not automatically cleared. This issue occurred due to a mismatch between the number of clients connected and clients terminating at the gateway. This issue is observed on 7240XM gateways running AOS-10.4.1.5 or later versions.

The fix ensures that stale client entries in the station table are automatically cleared.

AOS-260853

Users observed that stale client entries in the station table were not automatically cleared. This issue occurred due to a mismatch between the number of clients connected and clients terminating at the gateway. This issue is observed on 7240XM gateways running AOS-10.4.1.5 or later versions.

The fix ensures that the stale client entries in the station table are automatically cleared.

AOS-260858

An AOS-10 mesh point failed to forward Spanning Tree Protocol (STP) Bridge Protocol Data Units (BPDUs) to the downlink port when switches were bridged across the mesh link. The log file listed the reason for the STP BPDUs drop as, drop stp packet when mesh point && no enet0-briding mesh_auto enable:0. This issue was observed in AOS-10 mesh setups with APs running AOS-10.5.0.0 or later versions as a mesh point and mesh portal.

The fix ensures that the AOS-10 mesh setup works as expected.

AOS-260859

Some AP-635 access points rebooted with an error message, Reboot caused by kernel panic: Fatal exception in interrupt. This issue occurred in APs running AOS-10.7.1.0.

The fix ensures that the APs work as expected.

AOS-260893

The One Touch Provision (OTP) screens for both static-activate and full-setup in AOS-10 gateways display IPv6 configuration options. However, IPv6 support is not yet available in AOS-10.

Workaround: Select No when prompted with the option to configure IPv6 address.

AOS-260909

Some 9004-LTE gateways running AOS-10.6.0.2 crashed and rebooted unexpectedly. The log files listed the reason as, Nanny rebooted machine - fpapps process died (Intent:cause: 86:34). This issue occurred due to a segmentation fault in the gateways.

The fix ensures that the gateways work as expected.

AOS-260920

After changing the mesh band in an AOS-10 mesh setup, the mesh point took more than five minutes to establish a mesh link with the mesh portal. This issue was observed in AP-730 and AP-750 access points running AOS-10.7.1.0.

The fix ensures that the AOS-10 mesh setup works as expected.

AOS-260964

VLAN 1 is displayed as the default option for provisioning VLAN instead of 4086, under the static-activate and full-setup One Touch Provision (OTP) options for gateways.

Workaround: Update VLAN to 4086, to be consistent with the uplink VLAN used by HPE Aruba Networking Central wizard.

AOS-261003

Some 7205 gateways rebooted unexpectedly. Log files listed the reason for the event as Datapath timeout (SOS Assert) (Intent:cause:register 54:86:0:2c). This issue was observed in gateways running AOS-10.6.0.3 or later versions.

Fix ensures that the gateways work as expected.

AOS-261032

In a corner case scenario, when a client roamed the new host AP did not send a radius accounting start message to the gateway. As a result, the client would age-out of the gateway user-table and lose connectivity.

This fix ensures that the radius accounting start message is sent by the AP to gateway in all situations.

AOS-261039

AOS-261220

The dynamic event capture faced an issue where the AWC process crashed while processing some event data. The issue was observed in APs running AOS-10.4.1.5 or latest versions.

The fix ensures that the APs work as expected, and event are sent correctly to Central without any issues.

AOS-261047

AOS-263475

Some AP-635 access points running AOS-10.7.0.2 crashed and rebooted unexpectedly. The log file listed the reason for the event as, Reboot caused by kernel panic: Take care of the TARGET ASSERT first.

The fix ensures that the APs do not crash randomly.

AOS-261263

Some gateways randomly dropped DNS queries initiated by iPad clients when the SaaS Express application skype_teams was enabled, and iPad users accessed teams.microsoft.com through the browser. Despite stable connections, the gateway intermittently failed to process these DNS queries, impacting the iPad user’s ability to access Microsoft Teams. This issue was observed in HPE Aruba Networking 9004 gateways running AOS-10.4.0.2.

The fix ensures that iPad users are able to access Microsoft Teams when connected on 9004 gateways.

AOS-261347

AOS-262637

The UCM process crashed on some APs in a customer deployment of mixed-type APs such as AP-518, AP-555, and AP-514 running version 10.4.1.6. The issue occurred due to memory corruption that scaled across various parts of the UCM.

The fix ensures that the UCM process does not crash.

AOS-261384

AOS-250092

WPA3 SAE clients failed to re-authenticate when they roamed to a previously connected AP. This issue was seen in AP-535 access points configured with tunnel mode SSID. It occurred because PMK cache lifetime was not set and 11r was disabled.

The fix ensures that SAE clients roam as expected by setting a PMK cache lifetime of 8 hours and re-authenticate successfully.

AOS-261403

AOS-260064

Some 300 Series access points running AOS-10.7.0.0 rebooted unexpectedly. The log file listed the reason as, Reboot caused by kernel panic: MemLeak: mem low. This issue occurred because memory had been allocated repeatedly in a loop without the corresponding de-allocation, which led to increased memory usage and eventual memory loss. The fix ensures that the APs function as expected.

AOS-261411

AOS-258268

AOS-262485

Two devices experienced repeated crash and reboot. This issue was seen in HPE Aruba Networking 7210 gateway and the log files listed the reason as Reboot Cause: Datapath timeout (SOS Assert).

This fix ensures that the gateways work as expected.

AOS-261412

While enabling Branch Mesh between gateways, OTO was using STUN-learnt addresses/ports for MPLS circuits. Hence, some of the tunnel definitions received from OTO were pointing to the public IP address of the MPLS, which is the same for all sites, rather than the physical IP address of the destination gateway.

The fix ensures that OTO sends the correct IP address of the destination gateway.

AOS-261474

Intermittently, APs running on AOS-10.4.1.5 dropped the client traffic. The log files listed the reason for the drop as, drop due to not dhcp addr. ue dhcp_addr 0.0.0.0. The issue occurred when clients switched from one AP with enforce-dhcp disable to the other AP with enforce-dhcp enable and the client did not renew the IP address via DHCP during the client roaming process.

The fix ensures that the client traffic flow is not dropped while roaming between APs.

AOS-261498

AOS-258268

AOS-258269

AOS-258789

AOS-259516

Two devices experienced repeated crash and reboot. This issue was seen in HPE Aruba Networking7210 gateway and the log files listed the reason as Reboot Cause: Datapath timeout (SOS Assert).

This fix ensures that the gateways work as expected.

AOS-261536

A DHCP outage was reported on tunnel mode SSIDs in the network. This issue occurred because wireless clients failed to receive a DHCP address from the DHCP servers connected to the Branch Gateway running AOS-10.7.0.1 or later versions.

The fix ensures that DHCP allocation works as expected for wireless clients.

AOS-261554

A few OTO tunnels went down and routes were not propagated from the Branch Gateways to VPNC. This issue occurred because of a DC connection issue on Branch Gateways.

The fix ensures that the OTO tunnels are up and stable, and routes are propagating as expected.

AOS-261597

AOS-261582

AOS-263146

A few 9000 Series gateways crashed and rebooted unexpectedly. The log files listed the reason for the event as Reboot Cause: Kernel Panic (Intent:cause: 86:50). This issue was observed on gateways running AOS-10.4.1.1 or later versions.

The fix ensures that the gateways work as expected.

AOS-261610

AOS-262298

The wired clients connected to a Microbranch AP remained in a state of authentication loop. This issue occurred because the VPNC marked the client MAC address as aged out due to not receiving the accounting start.

The fix ensures that the wired clients are authenticated successfully.

AOS-261623

AOS-262233

AOS-262666

Some AP-555 access points randomly crashed and rebooted. The log files listed the reason for the crash as, Kernel panic - not syncing: Take care of the TARGET ASSERT.

The fix ensures that the APs do not crash. This issue was observed in APs running AOS-10.4.1.6.

AOS-261643

Some 9240 Branch Gateways crashed and rebooted unexpectedly. The log files listed the reason for the event as Reboot Cause: Datapath timeout (Intent:cause: 86:56). This issue was observed on gateways running AOS-10.4.1.1 or later versions.

The fix ensures that the gateways work as expected.

AOS-261677

Some AP-635 and AP-655 access points running AOS-10.7.0.1 or later versions, with the Hide SSID option enabled, incorrectly responded to the probe requests in 6G. This issue occurred because APs responded to the broadcast short SSID probe requests from clients with short SSID IE.

The fix ensures that the Hide SSID option works as expected.

AOS-261707

AOS-257551

Clients failed to connect to the Netskope server when the LTE uplink was directly plugged into the AP-605R access point, either using a USB with Skylark or a direct LTE modem. This issue was observed on APs running AOS-10.6.0.3 or later versions.

The fix ensures that clients can connect to the Netskope server using the LTE uplink.

AOS-261731

The AirGroup server cache on the APs retained the previous IPv4 address even after the server was reconnected with a new IP address. This issue was observed in the AOS-10 setup with access points running AOS-10.4.0.0 or later versions.

The fix ensures that the AirGroup records always reflect the latest IPv4 address.

AOS-261949

Some mobile devices were unable to connect to the Passpoint SSID. This issue occurred when EAP transactions were sent across different connections to the same destination IP. This issue was observed in gateways running AOS-10.4.1.6 or later versions.

The fix ensures that the devices are able to connect to the Passpoint SSID.

AOS-262038

DHCP device onboarding using Pre-Shared Key (PSK) failed for gateway devices running AOS-10-.7.1.0. The gateways were unable to connect to HPE Aruba Networking Central without manual provisioning, even when DHCP option was configured.

The fix enables AOS-10 gateways to onboard successfully through DHCP using PSK.

AOS-262062

Some 7210 gateways running AOS-10.5.0.1 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 7210 gateways work as expected.

AOS-262085

Some AP-655 access points crashed and rebooted unexpectedly. The log files listed the reason for the event as, kernel panic: Fatal exception in interrupt. The issue was observed in APs running AOS-10.4.1.6 version.

The fix ensures that the APs work as expected.

AOS-262144

Some AP-635 access points crashed and rebooted unexpectedly. The log files listed the reason for the event as, kernel panic: Fatal exception in interrupt. The issue was observed in APs running AOS-10.4.1.5 version.

The fix ensures that the APs work as expected.

AOS-262158

Some AP-515 access points randomly crashed and rebooted. The log files listed the reason for the crash as, BadPtr:00000036 PC:wlc_taf_pktfree_check+0x1b58/0x6140 [wl_v6] Warm-reset.

The fix ensures that APs do not crash randomly. This issue was observed in APs running AOS-10.7.1.0.

AOS-262160

After upgrading the 9004 gateways from version AOS-10.6 to AOS-10.7.0.1, three Web-CC categories were not available in HPE Aruba Networking Central. However, the three categories were displayed in the output of #show web-cc categories command.

The issue was resolved by removing the categories from the show command.

AOS-262233

Some AP-555 access points randomly crashed and rebooted. The log files listed the reason for the crash as, Kernel panic - not syncing: Take care of the TARGET ASSERT. This issue was observed in APs running AOS-10.4.1.6. The fix ensures that the APs do not crash.

AOS-262260

Some AP-635 access points crashed and rebooted unexpectedly. The log files listed the reason for the event as, kernel panic: Fatal exception in interrupt. The issue was observed in APs running AOS-10.6.0.1 version.

The fix ensures that the APs work as expected.

AOS-262263

Some APs generated a mini_httpd core dump file with a New core file generated in process error message, although the APs did not report a crash. This issue was observed in APs running AOS-10.4.0.0 or later versions.

The fix ensures that the APs do not generate an error message.

Duplicates: AOS-261672, AOS-262434, AOS-262436, AOS-262458, AOS-262459, AOS-262550, AOS-262559.

AOS-262291

The l3dwrap process crashed on 9240 gateways during the upgrade from AOS-10.6.0.3 or AOS-10.7.0.1 to AOS-10.7.1.0 version when L2VPN neighbors were configured. This caused the gateways to stop responding for 15 minutes.

The fix ensures that the gateways work as expected.

AOS-262315

When Captive Portal authentication failed, the custom value in Radius-reject Reply-Message attribute was not displayed in the login page. Instead, Login error. Please retry was incorrectly displayed. The fix ensures that if Radius-reject packet contains the Reply-Message attribute when Captive Portal authentication fails, the string value of that attribute is displayed in the login page. If not, the message Login error. Please retry is displayed.

AOS-262399

AOS-262396

Some APs running AOS-10.4.1.6 version crashed unexpectedly. The crash occurred when the AP received an allow or disallow role-related configuration event. When an AirGroup role changes, there is a workflow to clear the existing cache with the disallowed role. In this scenario, a missing null check caused the crash. The fix ensures that APs do not crash during AirGroup role configuration updates.

AOS-262534

AOS-259809

AOS-262047

Devices were unable to connect to MPSK (overlay + cloud auth) SSID. This issue occurred because there was no socket connection for Radproxy process to Cloud Guest server. The issue was observed on GWs running (Undefined variable: Variables.AOS)-10.4.1.5 or later versions.

The fix restores socket connectivity for Radproxy process to Cloud Guest server.

AOS-262753

Some Point of Sale (POS) devices were unable to connect with the payment gateway server. This issue occurred after replacing the primary and secondary VPN tunnels for the branch gateway, resulting in FPAPPS error messages.

The fix ensures that POS devices are able to connect with the payment gateway server.

AOS-262757

AOS-262515

Multiple access points crashed and rebooted unexpectedly. The files listed the reason as, WDO ASSERTED epc 0x899e. The underlying cause was due to an assertion, “bsscfg != ((void *)0)” failed: file “wlc_scb.c”, wlc_scbfindband(). This issue was observed in access points running AOS-10.7.1.0.

The fix ensures that the APs work as expected.

AOS-262759

AOS-264283

Some AP-515 access points sporadically sent packets out of sequence, causing the Wi-Fi adapter to stop passing traffic and disconnect. The issue occurred because the packet stayed in the suppressed queue for too long. This issue was observed in APs running AOS-10.4.1.5 or later versions.

The fix ensures that the APs work as expected and the Wi-Fi adapter is not interrupted.

AOS-262769

Some AP-555 access points randomly crashed and rebooted. The log files listed the reason for the crash as, Kernel panic - not syncing: Take care of the TARGET ASSERT.

The fix ensures that the APs do not crash. This issue was observed in APs running AOS-10.4.1.6.

Duplicates: AOS-261623, AOS-263611, AOS-262233, AOS-262666, and AOS-262769.

AOS-262781

Clients connected to a split-tunnel wired port on a Microbranch AP experienced 5-second audio disruptions every 15 minutes during Microsoft Teams calls. This issue occurred because an RTP packet from the Microsoft server was denied on the AP at regular intervals. This issue was observed in APs running AOS-10.4.1.0 or later versions.

The issue is resolved by modifying the session deletion logic to ensure that client sessions are only deleted and recreated when the role number of the client changes.

AOS-262856

Some AP-605H access points running AOS-10.7.0.2 or later versions crashed and rebooted unexpectedly. The log files listed the reason for the event as BadAddr: 001c0626 PC: skb_release_data+0xe8/0x208 Warm-reset.

The fix ensures that the APs work as expected.

AOS-263026

Some AP-677 and AP-679 access points running AOS-10.7.0.2 or later versions were incorrectly assigned the same channel, causing network performance issues. This issue occurred because the channel assignment logic selected the least interference channel due to which multiple APs chose the same channel.

The fix ensures that the channel selection process uses random assignment to reduce interference among APs.

AOS-263158

Some users were unable to access certain external sites, even when no ACLs were blocking the traffic. This issue occurred due to the IP reputation filtering feature. This issue is observed in branch gateways running AOS-10.4.1.4 or later versions.

The fix ensures that the users are able to access the sites successfully based on IP reputation threat status.

AOS-263282

Some AP-535, AP-555 and AP-635 access points crashed and rebooted unexpectedly. The log files listed the reason for the event as, Reboot caused by kernel panic: Fatal exception in interrupt. This issue was observed in APs running AOS-10.4.1.6 or later versions.

The fix ensures that the APs work as expected.

Duplicates: AOS-259401, AOS-260344, AOS-260627, AOS-260956, AOS-261623, AOS-261680, AOS-262085, AOS-262233, AOS-262264, AOS-262537, AOS-263658, AOS-263611, AOS-263661, AOS-262755

AOS-263292

Gateways reported cluster_mgr process crashed on the cluster member. This issue occurred when a cluster leader process was restarted leading to a temporary leadership change. This issue was observed in branch gateways running AOS-10.7.2.0.

The fix ensures that the process does not crash on the cluster members.

AOS-263328

Gateways reported incorrect destination ports for client sessions on all x86 architecture gateways running AOS-10.5.1.1 or later versions. This issue occurred when client sessions were aggregated by the destination ports.

The fix ensures that the gateway reports the correct destination ports to HPE Aruba Networking Central.

AOS-263362

When the user tried to deploy new sites, access to a specific resource from the data center via FTP was blocked. This issue was caused by the policy rule all_local_networks, which blocks the FTP control connection. This issue was observed in branch gateways running AOS-10.4.1.4.

The fix ensures that traffic for FTP server is allowed.

AOS-263449

WebCC failed to classify SNIs with a www. prefix due to differences in cache look up between SOS WebCC and cloud. This caused controllers to mark traffic as WEB-NOT-CLASS. The fix ensures that the WebCC will maintain correct classification of URLs. This issue was observed on devices running (Undefined variable: Variables.AOS).10.7.1.0 or later versions.

AOS-263557

HPE Aruba Networking 9240 VPNCs running AOS-10.4.1.1 experienced continuous crashes and reboots. This issue occurred due to the isakmpd process dying, causing the Nanny process to reboot. The issue occurred because QAT (QuickAssist Technology) responses were delayed for different requests, leading to crashes when the system attempted to process responses using incorrect context data.

The fix includes validation checks to ensure that responses from QAT match the requests made, thereby preventing crashes due to context mismatches.

AOS-263614

Some AP-605H access points running AOS-10.7.1.0 crashed and rebooted unexpectedly. The issue occurred in the dpimgr module leading to wireless network instability in newly deployed networks of the AP.

The fix ensures the dpimgr module remains stable.

AOS-263693

AOS-265106

AOS-265353

Some AP-515 access points crashed and rebooted unexpectedly with reason, PC is at aruba_low_txq_flush_to_psq+0xc4/0x278 [wl_v6]. This issue was observed in AP-515 access points running AOS-10.4.1.7.

The fix ensures that APs work as expected.

AOS-263823

Users generated dpimgr core files on AP-605H and AP-635 access points which resulted in a significant number of core files being created leading to client disconnections. This issue occurred by a segmentation fault in the dpimgr module with repetitive crash signatures. This issue was observed in APs running AOS-10.7.0.0.

The fix ensures that dpimgr core files are generated successfully.

AOS-263949

AOS-264454

Some clients failed to authenticate to the AP and displayed the error, DROPPED radius packet recvfrom, radius code: 1. This issue occurred because BSSID in rad_ctx was modified incorrectly. The fix ensures that radius packets are successfully received.

AOS-263985

Some AP-577 access points crashed and rebooted unexpectedly. The log files listed the reason for the event as PC: memcmp+0xd0/0x1e0; LR is at sos_uquic_analyse_padding_frame+0x6c. This issue was observed on APs running AOS-10.7.0.1 or later versions.

The fix ensures that the APs work as expected.

AOS-264412

Users noticed excessive generation of START accounting messages during client roaming between access points. This issue occurred because of a context key collision in the proxy, leading to discrepancies in accounting records.

This fix ensures that the accurate accounting and compliance is maintained.

AOS-264417

Some AP-505 access points crashed with an error message, Panic: wl0:aruba_bmac_check_process_sts:ERROR 5 sequential Missed PHYSTS, rebooting... Warm-reset. This issue occurred in APs running AOS-10.7.1.1.

The fix ensures that the APs work as expected.

AOS-264456

MacBooks equipped with M2 and M3 chips experienced intermittent connectivity issues with WPA3 SSIDs on AP-755 access points. This issue was observed during re-authentication, either after the devices wake from sleep mode or when the Wi-Fi is toggled between On and Off. This issue occurred as the AP-755 access points did not process the EAP-Logoff and EAP-Start packets properly, resulting in re-authentication failure. The fix ensures proper handling of EAP-Logoff and EAP-Start packets to restore connectivity.

AOS-264649

The TCP and UDP connections failed for wireless clients on the AP-735 when the eth0 interface was down and eth1 was up, despite other types of traffic functioning normally. The issue occurred because of an incorrect output device in the hardware offload session, which occurred under specific LACP configurations. The fix ensures proper handling of egress devices in such scenarios.

AOS-265280

BLE_daemon process crashes were observed on some AP-635 access points due to a memory corruption problem during buffer reallocation for extended advertisements. The fix ensures that the BLE_daemon process does not crash when processing extended advertisements.

AOS-265687

Some AP-535 access points rebooted with a kernel panic caused by an assertion failure. The issue occurred because the clients frequently roamed between the existing and new versions of the AP. The fix ensures the APs work as expected.

AOS-266055

During roaming, clients did not receive IP addresses from the 6 GHz band because the AP-7xx series access points randomly blocked DHCP traffic for the band. This issue occurred due to a race condition, where the pairwise key was not programmed successfully on the AP. The fix ensures that clients can successfully reconnect to the 6 GHz band during roaming.

AOS-255495

Clients associated on the 5 GHz band experienced periodic ping failures. This issue occurred because the AP kept printing ampdu_dbg logs for clients in power save (PS) mode for an extended period. This issue was observed in AP-735 access points, running AOS-10.7.0.0.

The issue was resolved by modifying the logging level and addressing the AMPDU session timeout.

AOS-248070

The HCM process crashed after several uplink failover events. This issue occurred due to the incorrect handling of HTTP probe timers during deletion, resulting in memory leakages. The issue was observed in branch gateways running AOS-10.4.1.0 or later versions. The fix ensures that the gateways work as expected.

AOS-255807

AOS-255824

AOS-263860

Clients were unable to connect to GPS-enabled APs running AOS-10.5.1.1 or later versions. The show commands executed in the CLI of the AP displayed the message, Module XXXX is busy. Please try later.

The fix ensures that clients are able to connect to GPS-enabled APs.

AOS-258275

HPE Aruba Networking Central blocked sessions even when there were no ACL restrictions under security. The issue occurred because invalid sessions had a denied flag, which was not checked during the aggregation of overflow session entries.

The fix ensures that the denied invalid sessions are not reported when no ACLs are present.

AOS-258335

On upgrading to AOS 10.6.0.3 or higher versions on the 9000 Series gateways, users experienced slow browsing speeds when the WebCC cache-miss-drop feature was enabled.

The fix ensures improvement in the loading time of the web pages at the first attempt.

AOS-258697

A few AP-635 access points running on AOS 10.4.1.4 crashed and rebooted unexpectedly. The log files listed the reason for the reboot as, Reboot caused by kernel panic: Take care of the TARGET ASSERT first.

The fix ensures that the access points work as expected due to the implementation of the target assert optimization feature.

AOS-258781

A few AP-615 and AP-635 access points running AOS-10.5.1.0 lost their default route and disconnected from HPE Aruba Networking Central. The issue occurred when APs using a static address on the uplink started the udhcpc, resulting in the loss of the default route when the uplink flapped.

The fix ensures that the udhcpc does not start when a static address is configured.

AOS-257021

A datapath crash was observed on 9114 gateways in a 5-node cluster. This issue occurred due to a failure to handle multicast group limits. This issue was observed in branch gateways running AOS-10.7.0.0 or newer versions. The fix ensures that the gateways work as expected and datapath crashes dos not occur.

AOS-261202

In some gateways, the default route was redistributed via OSPF even when the default information knob was disabled in the Routing > OSPF tab. This issue was observed in gateways running AOS-10.7.0.0 or later versions. The fix ensures that the default roles are reassigned as follows as intended.

AOS-262118

The antenna gain values for the BLE (Bluetooth Low Energy) in the AP-5xx series were inconsistent, resulting in problems with IoT configurations and suboptimal performance. This issue was observed in access points running AOS-10.7.0.0 or later versions. The fix ensures that the APs work as expected.

AOS-262247

In certain gateways, a datapath crashed when attempting to configure more than 256 multicast groups. This issue compromised network stability and caused service disruptions. The issue occurred due to a flaw in the implementation of multicast group management within the datapath module. This issue was observed in controllers running AOS-10.7.0.0 or later versions. The fix ensures that the controllers function as intended.

AOS-262553

Users have reported slow browsing when accessing specific websites, primarily due to page load times exceeding 60 seconds. This problem occurred because the Web Content Classification (WebCC) cache_miss_drop feature was enabled on the gateway. This issue was observed in gateways running AOS-10.8.0.0 or later versions. The fix ensures that the APs work as expected.

AOS-262623

The AEC process was observed sending configuration request messages to the AE every 30 seconds whenever an AP connector configuration or transport profile was detected. This issue occurred in an excessive number of configuration request messages, which increased the load on the AE system. This issue was observed in APs running AOS-10.7.2.0 or later versions. The fix ensures that the APs work as expected.

AOS-262981

Some APs crashed and rebooted unexpectedly. The logfiles listed the reason for the event as AP Reboot reason: Warm-reset, PC is at km_key_pasn_wdog+0x8c0/0x2460 [wl]. The fix ensures that the APs work as expected.

AOS-263020

The AEC process sent configuration request messages to the AE every 30 seconds whenever an AP connector configuration or transport profile was detected. This behavior resulted in an excessive number of configuration request messages, which increased the load on the AE system. This issue was observed in access points running AOS-10.7.2.0 or later versions. The fix ensures that the APs work as expected.

AOS-263221

In datapath sessions, few sessions were incorrectly classified. This misclassification occurs during traffic tests involving streaming media. The issue occurred due to a problem in the first packet classification (FPC) mechanism. This issue is observed in access points running AOS-10.7.2.0 or later versions. The fix ensures that the APs work as expected.