Known Issues in ArubaOS 8.10.0.5

This topic describes the known issues and limitations observed in this release.

Limitations

Following are the limitations observed in this release.

IP Default-Gateway Management Address

Aruba recommends to not configure the IP default-gateway management address for 7010, 7024, 7205, and 7280 controllers running ArubaOS 8.10.0.0.

650 Series and 630 Series Access Points

The 650 Series and 630 Series access points have the following limitations:

  • No spectrum analysis on any radio
  • No Zero-Wait DFS
  • No Hotspot and Air Slicesupport on the 6 GHz radio
  • No 802.11mc responder and initiator functionality on any radio
  • Only 4 VAPs on the 6 GHz radio instead of 16
  • Maximum of 512 associated clients on any radio, instead of 1024

6 GHz Channel Information in Regulatory Domain Profile

ArubaOS does not display the 6 GHz channel information in the existing regulatory domain profile of Wi-Fi 6E APs by default.

To include 6 GHz channel information, ensure that you change the country code to a different country code, apply the change, and then revert it to the original country code. Another option is to create a new regulatory domain profile that includes the 6 GHz channel information by default, or copy the existing regulatory domain profile into a new regulatory domain profile to save the configuration.

The following example configures a regulatory domain profile and specifies a valid 6 GHz band.

host) [mynode](config) #ap regulatory-domain-profile reg-635 host) [mynode] (Regulatory Domain profile "reg-635") #country-code US host) [mynode] (Regulatory Domain profile "reg-635") #valid-6ghz-channel 165

Air Slice

Air Slice is partially enabled on 500 Series access points and 510 Series access points. However, WMM boost will be functional even if Air Slice high-priority queuing is disabled.

Airtime Fairness Mode

Airtime Fairness Mode is not supported in 802.11ax access points.

7000 Series and 7200 Series Controllers

The cpboot command does not upgrade the ArubaOS software version of 7000 Series and 7200 Series controllers.

Known Issues

Following are the known issues observed in this release.

Table 1: Known Issues in ArubaOS 8.10.0.5

New Bug ID

Description

Reported Version

AOS-151022

AOS-188417

The output of the show datapath uplink command displays an incorrect session count. This issue is observed in managed devices running ArubaOS 8.1.0.0 or later versions.

Old Bug ID: 185176

ArubaOS 8.1.0.0

AOS-156537

Multicast streaming fails when broadcast and multicast optimization is enabled on the user VLAN. This issue is observed in managed devices running ArubaOS 8.7.1.4 or later versions.

ArubaOS 8.7.1.4

AOS-190071

AOS-190372

A few users are unable to access websites when WebCC is enabled on the user role. This issue occurs in a Per User Tunnel Node (PUTN) setup when the VLAN of the user role is in trunk mode. This issue is observed in 7005 controllers running ArubaOS 8.4.0.0.

Workaround:

Perform the following steps to resolve the issue:

1. Remove web category from the ACL rules and apply any any any permit policy.

2. Disable WebCC on the user role.

3. Change the VLAN of user role from trunk mode to access mode.

ArubaOS 8.4.0.0

AOS-195434

Some APs crash and reboot unexpectedly. The log files list the reason for the event as Reboot caused by kernel panic: Fatal exception. This issue is observed in APs running ArubaOS 8.5.0.0 or later versions.

ArubaOS 8.5.0.2

AOS-205650

AOS-231536

DHCP traffic from relay agent is not forwarded through the next-hop list configured in Layer 3 GRE tunnel. This issue is observed in managed devices running ArubaOS 8.6.0.15 or later versions.

ArubaOS 8.6.0.15

AOS-209580

The output of the show ap database command does not display the o or i flags, which indicate whether an AP is an outdoor AP or an indoor AP. This issue occurs when the AP installation type is not set to default. This issue is observed in Mobility Conductors running ArubaOS 8.3.0.13 or later versions.

ArubaOS 8.3.0.13

AOS-215495

Some APs display the error message, ARM Channel 40 Physical_Error_Rate 0 MAC_Error_Rate 84 Frame_Retry_Rate 0 arm_error_rate_threshold 70 arm_error_rate_wait_time 90. This issue is observed in AP-535 access points running ArubaOS 8.5.0.5 or later versions.

ArubaOS 8.5.0.5

AOS-216536

AOS-220630

Some managed devices running ArubaOS 8.5.0.11 or later versions are unable to come up on the Mobility Conductor. This issue occurs when the managed devices receive the branch IP address as the controller IP address in a VPNC deployment.

ArubaOS

8.5.0.11

AOS-218844

AOS-227400

AOS-231009

Some APs fail to preload image during cluster live upgrade. This issue is observed in APs running ArubaOS 8.6.0.9 or later versions in a cluster setup.

ArubaOS 8.6.0.9

AOS-219150

Mobility Conductor fails to push the SRC NAT pool configuration to the managed devices. This issue occurs when the ESI redirect ACL is configured using the WebUI. This issue is observed in Mobility Conductors running ArubaOS 8.7.1.1 or later versions.

 ArubaOS 8.7.1.1

AOS-219423

Honeywell Handheld 60SL0 devices are unable to connect to 802.1X SSIDs. This issue is observed in managed devices running ArubaOS 8.6.0.8 or later versions.

ArubaOS 8.6.0.8

AOS-219791

The aggressive scanning mode under ARM profile settings is enabled by default. This issue is observed in APs running ArubaOS 8.7.1.3 or later versions.

ArubaOS 8.7.1.3

AOS-221308

The execute-cli command does not work as expected for a few show commands. This issue is observed in Mobility Conductors running ArubaOS 8.7.1.4 or later versions.

ArubaOS 8.7.1.4

AOS-223221

AOS-237950

Some AP-514 and AP-515 access points running ArubaOS 8.7.1.4 or later versions generate 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]().

 ArubaOS 8.7.1.4

AOS-225263

AOS-232589

L2 database synchronization fails on standby controllers. This issue is observed in stand-alone controllers running ArubaOS 8.8.0.1 or later versions.

ArubaOS 8.8.0.1

AOS-226017

AOS-231886

AOS-235947

The airmatch_recv process crashes on Mobility Conductors running ArubaOS 8.6.0.9 or later versions. The log files list the reason for the event as Exceeded max number of packet limit.

ArubaOS 8.6.0.9

AOS-226361

AOS-226850

AOS-227154

Mobility Conductors running ArubaOS 8.7.1.5 or later versions incorrectly route traffic to different ports.

ArubaOS 8.7.1.5

AOS-227981

A few 7010, 7024, 7205, and 7280 controllers running ArubaOS 8.0.0.0 or later versions incorrectly route the incoming external subnet traffic on management port to data ports.

ArubaOS 8.7.1.6

AOS-228581

A VPNC crashes and reboots unexpectedly. The log files list the reason for the event as Reboot Cause: Datapath timeout (SOS Assert) (in ipsec_decrypt). This issue occurs when the buffer memory is queued in the wrong processor. This issue is observed in VPNCs running ArubaOS 8.6.0.4 or later versions.

ArubaOS 8.6.0.4

AOS-229024

Some AP-505 access points running ArubaOS 8.7.1.5 or later versions crash and reboot unexpectedly. The log files list the reason for the event as PC is at wlc_mbo_parse_ie+0x15c/0x2b0 [wl_v6].

ArubaOS 8.7.1.5

AOS-229190

AOS-229798

AOS-230295

The Dashboard > Overview > Clients page of the WebUI does not display active and standby controller information. This issue is observed in Mobility Conductors running ArubaOS 8.10.0.0 or later versions.

ArubaOS 8.10.0.0

AOS-229828

Some managed devices face issues while supporting weak ciphers during SSL/TLS negotiations. This issue is observed in managed devices running ArubaOS 8.7.1.6 or later versions.

ArubaOS 8.7.1.6

AOS-230900

AOS-231081

AOS-234940

Some 530 Series and 550 Series access points running ArubaOS 8.6.0.0 or later versions crash and reboot unexpectedly. The log files list the reason for reboot as Reboot caused by kernel panic: Take care of the TARGET ASSERT first.

ArubaOS 8.7.1.7

AOS-231283

The log files of a few Wi-Fi 6E APs (630 Series and 650 Series access points) running ArubaOS 8.10.0.0 or later versions incorrectly display the 6G radio 2 disabled due to mfg configuration message during reboot of the APs, even though the 6 GHz radio is not disabled when the APs boot up.

ArubaOS 8.10.0.0

AOS-231473

The Dashboard > Overview > Wired Clients page of the WebUI does not display the details of the APs to which clients are connected. This issue occurs in a pure IPv6 deployment. This issue is observed in Mobility Conductors running ArubaOS 8.8.0.2 or later versions.

ArubaOS 8.8.0.2

AOS-231856

A few APs running ArubaOS 8.6.0.0 or later versions crash unexpectedly. The log files list 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 occurs due to change of channel on one or both the radios when EIRP check is done for the new channel.

ArubaOS 8.7.1.8

AOS-231990

The Dashboard > Infrastructure page displays an incorrect Last Reboot time. This issue is observed in managed devices running ArubaOS 8.6.0.0 or later versions.

ArubaOS 8.7.1.8

AOS-232378

The pim process crashes on managed devices running ArubaOS 8.7.1.8 or later versions. This issue occurs due to invalid memory access.

ArubaOS 8.7.1.8

AOS-232443

Server derivation rules are not assigned correctly and an error message, Missing server in attribute list is displayed. This issue occurs when there is a delay in response from the RADIUS server. This issue is observed in stand-alone controllers running ArubaOS 8.7.1.3 or later versions.

ArubaOS 8.7.1.3

AOS-232493

The entries of denylisted clients are not synchronized between the managed devices. This issue is observed in managed devices running ArubaOS 8.6.0.15 or later versions in a cluster setup.

ArubaOS 8.6.0.15

AOS-232620

A discrepancy is observed between the total number of APs and the total number of AP BLE devices reported. This issue is observed in stand-alone controllers running ArubaOS 8.0.0.0 or later versions.

ArubaOS 8.8.0.2

AOS-232897

The wlan ht-ssid-profile command overrides the radio frequencies from 80 MHz to 40 MHz, although the show ap bss-table command displays the radio frequencies as 80 MHz. This issue is observed in AP-515 and AP-535 access points running ArubaOS 8.7.1.9 and ArubaOS 8.10.0.0 versions.

ArubaOS 8.7.1.9

AOS-232997

Some managed devices running ArubaOS 8.7.1.9 or later versions are stuck after an upgrade and the aaa process crashes.

ArubaOS 8.7.1.9

AOS-233582

The licensing server fails to update the IP address of the secondary Mobility Conductor. This issue occurs when the secondary Mobility Conductor becomes the primary Mobility Conductor. This issue is observed in managed devices running ArubaOS 8.6.0.11 or later versions.

ArubaOS 8.6.0.11

AOS-233809

Users are unable to add GRE tunnels to a tunnel group and an incorrect error message, Error: Tunnel is already part of a different tunnel-group is displayed. This issue is observed in managed devices running ArubaOS 8.6.0.8 or later versions.

ArubaOS 8.6.0.8

AOS-234103

Some clients experience downstream packet disruption. This issue is observed in APs running ArubaOS 8.6.0.9 or later versions.

ArubaOS 8.6.0.17

AOS-234315

A few APs sent PAPI messages to external IP addresses, and the logs displayed a random IP address for the PAPI_Send failed error message. This issue is observed in APs running ArubaOS 8.6.0.15 or later versions.

ArubaOS 8.6.0.15

AOS-234783

Some AP-505H access points running ArubaOS 8.10.0.0 or later versions are flooded with wlc_offload PhyRxSts Circular Buffer Control logs and crash unexpectedly. The log files list the reason for the event as Kernel panic - not syncing: Ktrace core monitor: cpu0 hung for 45 seconds, hung cpu count: 1.

ArubaOS 8.10.0.0

AOS-235744

AOS-235752

Some managed devices are unable to receive any configuration from the Mobility Conductor. This issue occurs when changes to a few group names are not synchronized on the standby Mobility Conductor before a reboot. This issue is observed in Mobility Conductors running ArubaOS 8.6.0.17 or later versions.

ArubaOS 8.6.0.17

AOS-235820

The wms process crashes on Mobility Conductors running ArubaOS 8.10.0.2 or later versions. This issue occurs when the wms process exceeds the virtual memory limit of 2 GB.

ArubaOS 8.10.0.2

AOS-236200

Some AP-374 access points configured as mesh APs crash unexpectedly. The log file list the reason for the crash as kernel panic: Fatal exception. This issue is observed in AP-374 access points running ArubaOS 8.7.1.9 or later versions.

ArubaOS 8.7.1.9

AOS-236462

A few Remote APs go down unexpectedly. This issue occurs when the IPv6 address of the AP is changed. This issue is observed in Remote APs running ArubaOS 8.5.0.13 or later versions.

ArubaOS 8.5.0.13

AOS-236577

Some AP-215 access points running ArubaOS 8.7.1.9 or later versions display the error log, wlc_dpc: 43 callbacks suppressed.

 ArubaOS 8.7.1.9

AOS-236728

Some AP-535 access points running ArubaOS 8.9.0.3 crash and reboot unexpectedly. The log files list the reason for the event as Reboot caused by kernel panic: softlockup: hung tasks.

ArubaOS 8.9.0.3

AOS-236813

Mobility Conductors running ArubaOS 8.10.0.2 or later versions generate multiple log messages, switch_daemon.0x204c03b68f82[8050]: <310322> <8050> |switch.10.143.242.6:58000| |ofc-switch-manager| Unknown message type 12.

ArubaOS 8.10.0.2

AOS-236841

AOS-238400

The Configuration > Services > Clusters >Add Controller page of the WebUI does not display the list of VRRP VLANs. This issue is observed in managed devices running ArubaOS 8.7.1.9 or later versions.

ArubaOS 8.7.1.9

AOS-236881

After upgrading Mobility Conductors to ArubaOS 8.7.1.8 or later versions, the profile manager in the secondary Mobility Conductor stops responding. This issue occurs when IPv6 mode is enabled on the secondary Mobility Conductor, because of which it failed to download certificates from the primary Mobility Conductor.

ArubaOS 8.7.1.8

AOS-237113

High latency and jitter are observed on stand-alone controllers running ArubaOS 8.7.1.9 or later versions.

ArubaOS 8.7.1.9

AOS-237174

Some 9240 controllers record informational logs, even though the system log level is configured as warning. This issue is observed in 9240 controllers running ArubaOS 8.10.0.2 or later versions.

ArubaOS 8.10.0.2

AOS-237203

Some stand-alone controllers with IAP-VPN tunnels generate multiple error logs. This issue is observed in stand-alone controllers running ArubaOS 8.10.0.2 or later versions.

ArubaOS 8.10.0.2

AOS-237348

Some AP-535 access points running ArubaOS 8.9.0.3 or later versions crash and reboot unexpectedly. The log files list the reason for the reboot as Reboot caused by kernel panic: Take care of the TARGET ASSERT first at whal_recv.c:1656 Assertion.

 ArubaOS 8.9.0.3

AOS-237510

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

 ArubaOS 8.6.0.18

AOS-237897

The webcc logs are logged in an invalid message format and as a result, the syslog server reports incorrect data. This issue is observed in managed devices running ArubaOS 8.0.0.0 or later versions.

 ArubaOS 8.7.1.9

AOS-238205

Some 9240 controllers running ArubaOS 8.10.0.3 or later versions do not respond to the SNMP GET request to OID WLSX-SYSTEMEXT MIB::sysExtFanStatus.

ArubaOS 8.10.0.3

AOS-238218

The mongo database takes up a lot of flash space. This issue is observed in Mobility Conductors running ArubaOS 8.9.0.3 or later versions.

ArubaOS 8.9.0.3

AOS-238410

AOS-238939

AOS-238564

AOS-238487

The httpd process crashes on Mobility Conductors and managed devices and running ArubaOS 8.10.0.3 or later versions. This issue occurs when a specific type of cURL request is sent to the controllers.

ArubaOS 8.10.0.3

AOS-238848

Some managed devices running ArubaOS 8.10.0.2 or later versions display an error message, Different SNMP hosts should not have same engine-id value, while configuring the SNMPv3 trap host. This issue occurs when the same SNMP engine-id is configured for multiple SNMPv3 trap hosts.

ArubaOS 8.10.0.2