AOS-156661

AOS-224890

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

AOS-214944

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

AOS-221514

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

AOS-224618

AOS-224619

AOS-224620

AOS-227759

The datapath process crashed on 9004 controllers and the controllers rebooted unexpectedly. The log files listed the reason for the reboot as Reboot Cause: Kernel Panic (Intent:cause: 86:50). The fix ensures that the controllers work as expected. This issue was observed in 9004 controllers running AOS-8.10.0.0 or later versions.

AOS-218844

AOS-227400

AOS-231009

Some APs failed to preload image during cluster live upgrade. The fix ensures that the APs preload image during an upgrade. This issue was observed in APs running AOS-8.6.0.9 or later versions in a cluster setup.

AOS-219315

Some 9004 controllers running AOS-8.7.1.10 or later versions crashed and rebooted unexpectedly. The log files listed the reason for the event as Reboot Cause: Kernel Panic (Intent:cause: 86:50). The fix ensures that the controllers work as expected.

Duplicates: AOS-223786, AOS-223787, AOS-240010, AOS-234981, and AOS-220422

AOS-221011

High channel utilization was observed in AP-515 access points running AOS-8.6.0.0 or later versions. Enhancements to the wireless driver resolved the issue.

AOS-223221

AOS-237950

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

AOS-226017

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

Duplicates: AOS-231886, AOS-235947, AOS-238770, AOS-239637

AOS-238025

Some AP-615 access points running AOS-8.11.0.0 or later versions crashed and rebooted unexpectedly. The log files listed the reason for the event as AP Reboot reason: BadPtr: 00000004 PC: __kmalloc_track_caller+0x84/0x17c Warm-reset. The fix ensures that the APs work as expected.

AOS-228371

Users were unable to delete a RADIUS server even when the server was not in use and an error message, RADIUS Server In use was displayed. The fix ensures that users can delete a RADIUS server that is not in use. This issue was observed in Mobility Conductors running AOS-8.7.1.5 or later versions.

AOS-228581

AOS-228791

Some managed devices running AOS-8.8.0.0 or later versions crashed and rebooted unexpectedly. The log files listed the reason for the event as Reboot Cause: Datapath timeout (SOS Assert) (in ipsec_decrypt). This issue occurred when the buffer memory was queued in the wrong processor. The fix ensures that the managed devices work as expected.

AOS-229207

AOS-229888

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

AOS-231856

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

AOS-231990

The Dashboard > Infrastructure page of the WebUI displayed incorrect Last Reboot time. The fix ensures that the WebUI displays the correct Last Reboot time. This issue was observed in managed devices running AOS-8 8.6.0.0 or later versions.

AOS-232378

The pim process crashed on managed devices running AOS-8.7.1.8 or later versions. This issue occurred due to invalid memory access. The fix ensures that the managed devices work as expected.

AOS-232970

The AP MAC address was not present in the calling station ID of the RADIUS accounting packets and hence, the RADIUS accounting requests were discarded. The fix ensures that the MAC address is present in the calling station ID. This issue was observed in managed devices running AOS-8.7.1.6 or later versions in a cluster setup.

AOS-234103

AOS-240610

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

AOS-234480

AOS-238970

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

AOS-234747

AOS-235575

A high number of TX retransmissions was observed on a few APs. The fix ensures that the APs work as expected. This issue was observed in AP-535 and AP-565 access points running AOS-8.6.0.17 or later versions.

AOS-234782

A few AP-505H access points running AOS-8.10.0.0 or later versions crashed and rebooted unexpectedly. The log file listed the reason for the event as skb double free detected!” at (“file-name/line-number/function-name” ) net/core/skbuff.c:1849/consume_skb(). The fix ensures that the APs work as expected.

AOS-234783

Some access points running AOS-8.10.0.0 or later versions were flooded with wlc_offload PhyRxSts Circular Buffer Control logs and crashed unexpectedly. The log files listed the reason for the event as Kernel panic - not syncing: Ktrace core monitor: cpu0 hung for 45 seconds, hung cpu count: 1. The fix ensures that the APs detect the issue and can recover from the hung state through a reboot that displays the message Panic: wl1:aruba_bmac_check_process_sts:ERROR 5 sequential Missed PHYSTS, rebooting... Warm-reset.

AOS-235242

AOS-235777

The auth process crashed and an error message, auth module busy was displayed. This issue occurred when the show run command was issued. The fix ensures that the users are able to issue the show run command. This issue was observed in managed devices running AOS-8.6.0.17 or later versions.

AOS-235672

Some wired clients received IP addresses even before a successful 802.1X authentication. The fix ensures that the clients receive IP addresses only after a successful authentication. This issue was observed in APs running AOS-8.6.0.9 or later versions.

AOS-235744

AOS-235752

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

AOS-235820

AOS-239962

The wms process crashed on Mobility Conductors running AOS-8.10.0.2 or later versions. This issue occurred when the wms process exceeded the virtual memory limit of 2 GB. The fix ensures that the Mobility Conductors work as expected.

AOS-235834

AOS-240216

AOS-236170

AOS-239298

The Dashboard > Overview > Wireless Clients page of the WebUI did not display any information for Retried Frames. The fix ensures that the WebUI displays the information about retried frames. This issue was observed in Mobility Conductors running AOS-8.10.0.4 or later versions.

AOS-236225

AOS-234379

Some 630 Series and 650 Series access points running AOS-8.9.0.1 or later versions experienced issues with the Draeger medical devices. The fix ensures that the APs work as expected.

AOS-236242

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

AOS-236427

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

AOS-236445

AOS-238079

Some users were unable to add or allocate licenses using the WebUI. The fix ensures that users are able to add or allocate licenses using the WebUI. This issue was observed in Mobility Conductors running AOS-8.10.0.2 or later versions.

AOS-236728

Some AP-535 access points running AOS-8.9.0.3 crashed and rebooted unexpectedly. The log files listed the reason for the event as Reboot caused by kernel panic: softlockup: hung tasks. The fix ensures that the APs work as expected.

AOS-236813

Mobility Conductors running AOS-8.10.0.2 or later versions generated multiple log messages, switch_daemon.0x204c03b68f82[8050]: <310322> <8050> |switch.10.143.242.6:58000| |ofc-switch-manager| Unknown message type 12. The fix ensures that the Mobility Conductors work as expected.

AOS-236841

AOS-238400

The Configuration > Services > Clusters >Add Controller page of the WebUI did not display the list of VRRP VLANs. The fix ensures that the WebUI displays the list of VRRP VLANs. This issue was observed in managed devices running AOS-8.7.1.9 or later versions.

AOS-236881

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

AOS-237113

High latency and jitter were observed on stand-alone controllers running AOS-8.7.1.9 or later versions. The fix ensures that the stand-alone controllers work as expected.

AOS-237203

Some stand-alone controllers with IAP-VPN tunnels generated multiple error logs. The fix ensures that the controllers do not generate error logs. This issue was observed in stand-alone controllers running AOS-8.10.0.2 or later versions.

AOS-237386

The packetin_dispatcher process crashed unexpectedly on a Mobility Conductor running AOS-8.10.0.2 or later versions. The fix ensures that the Mobility Conductors work as expected.

AOS-237473

AOS-238104

The core files of the nanny process were not collected by the Mobility Conductor. The fix ensures that the Mobility Conductor collects the core files of the nanny process. This issue was observed in Mobility Conductor running AOS-8.7.1.9 or later versions.

AOS-237510

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

AOS-237815

Mobility Conductors running AOS-8.6.0.19 did not have sufficient free flash space. This issue occurred when the AP image files took excessive flash space. The fix ensures that the Mobility Conductors work as expected.

AOS-237851

Some AP-535 access points running AOS-8.10.0.2 or later versions crashed and rebooted unexpectedly. The log files listed the reason for the event as Reboot caused by kernel panic: Take care of the TARGET ASSERT first (phyrf_ani.c:718). The fix ensures that the APs work as expected.

AOS-237897

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

AOS-238205

Some 9240 controllers running AOS-8.10.0.3 or later versions did not respond to the SNMP GET request to OID WLSXSYSTEMEXT MIB::sysExtFanStatus. The fix ensures that the controllers respond to the SNMP GET request.

AOS-238218

AOS-239882

AOS-241230

The mongo database took up a lot of flash space. This issue was observed in Mobility Conductors running AOS-8.9.0.3 or later versions. The fix ensures that the Mobility Conductors work as expected.

AOS-238387

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

AOS-238410

AOS-238939

AOS-238564

AOS-238487

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

AOS-238500

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

AOS-238519

AOS-240280

The BSS table of the Remote AP was reset unexpectedly. This issue occurred after a reboot of the Mobility Conductor. The fix ensures that the AP BSS table does not reset after a reboot of the Mobility Conductor. This issue was observed in Mobility Conductors running AOS-8.10.0.2 or later versions.

AOS-238578

AOS-238575

AOS-238576

The halt command did not save the audit-trail logs of the stand-alone controllers. As a result, the show audit-trail history command did not display the configuration changes done before a reboot. The fix ensures that the halt command saves the audit-trail logs of the controllers. This issue was observed in stand-alone controllers running AOS-8.10.0.3 or later versions.

AOS-238589

AOS-239319

The impystart process crashed on Mobility Conductor Virtual Appliances running AOS-8.10.0.2 or later versions. The fix ensures that the Mobility Conductor Virtual Appliances work as expected.

AOS-238681

The RADIUS request access packets contained the IP address of the Mobility Conductor as the NAS IP address instead of the CoA VRRP IP address of the managed device. Hence, clients experienced connectivity issues. The fix ensures that the RADIUS request access packets contain the correct NAS IP address. This issue was observed in managed devices running AOS-8.9.0.1 or later versions in a cluster setup.

AOS-238701

AOS-238934

AOS-239570

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

AOS-238768

WebUI took a long time to display the AP and client information. The fix ensures that the WebUI displays the AP and client information without any delay. This issue was observed in Mobility Conductors running AOS-8.10.0.2 or later versions.

AOS-238836

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

AOS-238848

Some managed devices running AOS-8.10.0.2 or later versions displayed an error message, Different SNMP hosts should not have same engine-id value, while configuring the SNMPv3 trap host. This issue occurred when the same SNMP engine-id was configured for multiple SNMPv3 trap hosts. The fix ensures that the managed devices work as expected.

AOS-238853

The health report sent to the Azure IoT Hub did not contain all the required information about the AP. The fix ensures that the health report contains the necessary information. This issue was observed in APs running AOS-8.10.0.0 or later versions.

AOS-238918

The Configuration > IoT > Zigbee Services page of the WebUI did not allow users to delete the Zigbee service profile. The fix ensures that users can delete the Zigbee service profile using the WebUI. This issue was observed in Mobility Conductors running AOS-8.10.0.2 or later versions.

AOS-238921

AOS-241183

Some 7240XM controllers running AOS-8.10.0.2 or later versions crashed and rebooted unexpectedly. 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 IPv6 DNS response was received. The fix ensures that the controllers work as expected.

AOS-238954

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

AOS-238960

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

AOS-238968

Some APs failed to send the IDS deauthentication frames even when the protect valid station parameter was enabled. This issue occurred when APs were connected in AM mode on 5 GHz channel. The fix ensures that the APs send the deauthentication frames when the valid station parameter is enabled. This issue was observed in AP-515 and AP-505 access points running AOS-8.10.0.2 or later versions.

AOS-239067

Some AP-535 access points running AOS-8.10.0.0 or later versions crashed and rebooted 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 APs work as expected.

AOS-239202

AOS-240267

The ble_daemon process consumed high memory and data packets were also dropped. This issue occurred when the BLE operation mode was enabled on the APs. The fix ensures that the APs work as expected. This issue was observed in APs running AOS-8.10.0.2 or later versions.

AOS-239260

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

AOS-239289

The output of the show datapath cluster details command displayed an incorrect time stamp. This issue occurred when the managed devices were up for more than 49 days. The fix ensures that the command displays the correct timestamp. This issue was observed in managed devices running AOS-8.10.0.2 or later versions in a cluster setup.

AOS-239327

The OSPF process crashed on managed devices running AOS-8.10.0.2 or later versions in a VPNC topology. The fix ensures that the managed devices work as expected.

AOS-239329

AOS-240018

AOS-241151

Some APs displayed an error message, sapd_sysctl_An internal system error has occurred at file sapd_sysctl.c function sapd_sysctl_write_param line 180 error Error opening /proc/sys/dev/wifi0/rts_mode : No such file or directory. 0. The fix ensures that the APs do not display the error message. This issue was observed in 200 Series, 203H Series, 203R Series, 205H Series, 210 Series, 220 Series, 228 Series, 270 Series, and AP-345 access points running AOS-8.10.0.5.

AOS-239341

Some clients were unable to connect to AP-345 access points running AOS-8.6.0.10 or later versions. The fix ensures seamless connectivity.

AOS-239487

The PCAP files of some APs were incorrectly sent to the default folder of the dump server and not to the user-defined folder. This issue was caused due to the defined dump-server settings not being honoured. The fix ensures that the PCAP files are sent following all the user-defined dump-server settings and will use SCP if that is what has been configured. This issue was observed in APs running AOS-8.10.0.4 or later versions.

AOS-239165

Some AP-635 access points running AOS-8.10.0.2 or later versions crashed and rebooted unexpectedly. The log files listed the reason for the event as Reboot caused by kernel panic with "sched_algo_qos.c:3794 Assertion (rtxop > 0) failed". The fix ensures that the APs work as expected.

AOS-239662

Some clients experienced issues with audio transmission during Skype and Microsoft Teams calls. The fix ensures that the clients do not experience issues with audio transmission. This issue was observed in APs running AOS-8.10.0.4 or later versions.

AOS-240057

The uplink VLAN did not work as expected. This issue occurred when an Instant Access Point was converted to a Remote AP. The fix ensures that the uplink VLAN works as expected. This issue was observed in AP-635 access points running AOS-8.10.0.4 or later versions.

AOS-240199

Users were unable to establish connection with a managed device using the mdconnect and logon commands. The fix ensures that the commands work as expected. This issue was observed in managed devices running AOS-8.7.1.11 or later versions.

AOS-240300

AirMatch assigned incorrect power levels to AP-277 access points running AOS-8.10.0.4 or later versions. The fix ensures that AirMatch assigns correct power levels for APs.

AOS-240347

Users were unable to collect the tech support logs of the Mobility Conductor. The fix ensures that the tech support logs of the Mobility Conductor are available for the users. This issue was observed in Mobility Conductors running AOS-8.10.0.4 or later versions.

AOS-240371

The 802.1X authentication failed for a few clients. This issue occurred when AP-635 access points were configured as Remote AP. The fix ensures successful authentication. This issue was observed in AP-635 access points running AOS-8.10.0.4 or later versions.