16.11.0024

257491

YC

Symptom: Deleting any tagged port from a VLAN using WebUI removes the port from other VLANs.

Scenario: This issue occurred when a port is configured as untagged in a VLAN and the tagged VLANs are modified from this port using WebUI. The port is then subsequently no longer in untagged VLAN, but is present in default VLAN.

Workaround: Use CLI commands to update VLAN configurations.

16.11.0024

257502

YC

Symptom/Scenario: The switch reboots itself during a power outage. However, routing convergence issues with the RIP protocol may be observed after the reboot.

Workaround: Use NTP/SNTP servers, instead of Activate, to establish time sync.

16.11.0024

257513

YC

Symptom: The role under User Details in WebUI displays the incorrect role during the first login attempt. There was no impact on the functionality.

Scenario: This issue occurred when the authorization attribute for a user was changed on the radius server.

Workaround: Logout from the webUI and login again.

16.11.0023

257379

YC

Symptom: Some users experience unsuccessful file transfers.

Scenario: This issue occurred when source interface was configured in Central.

Workaround: Remove the ip sourceinterface configuration.

16.11.0023

257462

YC

Symptom: Some switches that are managed by Central encounter stale backup configuration file named CentralBkupConfig which in turn may cause a rollback of configuration in the switch.

Scenario: This issue occurred when the switch was managed by Central and a configuration push was triggered from Central while a parallel firmware image or configuration update was processed via TFTP.

Workaround: Delete the stale backup file using CLI.

16.11.0023

257482

YC

Symptom: Some switches experience module crash when VXLAN is enabled.

Scenario: This issue occurred when VXLAN was enabled in multiple VLANs in order to create VXLAN tunnels.

16.11.0023

257492

YC

Symptom: Users encounter inconsistent wording of WebUI in the event logs for a web session. For example, instances of both WEB_UI and WEB-UI is available in the logs.

Scenario: This issue occurred when users tried to log in and out using valid and invalid credentials.

16.11.0022

-

YC

Version 16.11.0022 is unavailable for download.

16.11.0021

257271

YC

Symptom/Scenario: Switch intermittently fails to forward packets from clients even when the clients are successfully on-boarded and authenticated.

Workaround:Flap the switch port to fix the issue.

16.11.0021

257322

YC

Symptom: Some switches are stuck in a high CPU utilization state due to eDhcpdProto task found in running state.

Scenario: The issue occurred when the switch received a high amount of DHCP traffic.

Workaround:Enabling and disabling DHCP will clear the CPU usage for the switch.

16.11.0021

257330

YC

Symptom/Scenario: Clients are unable to on-board with specific downloadable user-roles (DUR). This issue was observed intermittently.

16.11.0021

257377

YC

Symptom/Scenario: Some users are able to apply a ACL to a management VLAN when it is not allowed.

Workaround: Remove the ACL configuration for the management VLAN using CLI.

16.11.0021

257381

YC

Symptom: Switch crashes and restarts when Qualys scans are initiated.

Scenario:This issue occurred when the Qualys VMDR (Vulnerability Management, Detection and Response) scan was initiated.

16.11.0021

257385

YC

Symptom: Some switches crash with the following message: out of memory.

Scenario: This issue occurred due to slow memory leakage and exhaustion.

16.11.0021

257396

YC

Symptom: Clients are unable to on-board and the following error message is logged when the user attempts to assign a downloadable user-roles (DUR) to a port:

ACL error - unable to create ACL entry

Scenario: This issue was observed when a client placed in critical role was moved to a regular role.

16.11.0021

257408

YC

Symptom: Switch crashes with the following message:

Software exception at wma_ctrl_sm.c:283 – in 'mWebAuth'

Scenario: This issue occurred when user role, authentication order and server timeout was configured and the radius server was unreachable.

16.11.0021

257432

YC

Symptom: Some users do not receive HTTP response from the switch.

Scenario:This issue occurred when HTTP requests were sent using Ansible scripts and the Ansible client interface experienced connection failures.

Workaround:Use Curl instead of Ansible to send HTTP requests.

16.11.0020

257397

YC

Symptom Users were unable to upgrade the switches from AOS-S 16.11.0018 to AOS-S 16.11.0019 version and an error message, Firmware image signature is not valid was displayed.

Scenario: This issue occurred when users upgraded the switches using the WebUI.

16.11.0020

257382

YC

Symptom: Manual SSH failed when the switch was acting as a server and AirWave Zero Touch Provisioning (ZTP) workflow was also affected.

Scenario: This issue occurred when an SSH client running OpenSSH 8.0P1 or later version was used to establish an SSH connection with a factory default AOS-S switch.

16.11.0019

-

YC

No fixes in 16.11.0019.

16.11.0018

257222

YC

Symptom: Switch fails to learn the MAC address of the firewall after the version upgrade.

Scenario: This issue occurred in switches with QinQ enabled and service VLANs configured.

16.11.0018

257275

YC

Symptom: Users experience random connectivity issues and packet processing failure. ARP entries are not resolved in the switch.

Scenario: This issue occurred when an ICMPv6 NS (Neighbor Solicitation) packet with 'Anycast' as the destination address was sent from an IPv6 node.

Workaround: Disable IPv6.

16.11.0018

257282

YC

Symptom/Scenario: Switch crashes when show commands are configured with a backslash "\".

16.11.0018

257262

YC

Symptom: Switch crashes when Qualys scans are executed.

Scenario:This issue occurred when the Qualys VMDR (Vulnerability Management, Detection and Response) scan was executed.

16.11.0018

257302

YC

Symptom: Switch crashes with the following error message: Health Monitor: Read Error Restr Mem Access” for task “mIpAdMUpCt

Scenario: This issue occurred when two stack switches were connected with OSPF point-to-point links and VXLAN was enabled.

16.11.0017

-

YC

Version 16.11.0017 is unavailable for download.

16.11.0016

257226

YC

Symptom: Switch crashes in SSH remote port forwarding scenarios.

Scenario: This issue occurred when the switch was acting as an SSH server and the ssh -R 6000:127.0.0.1:6000 manager@10.0.0.1 command was configured from an SSH client.

16.11.0015

257221

Symptom: The switch fails to stay in sync with Central.

Scenario: This issue occurred when ip igmp forward configuration pushed from Central did not get reflected in the switch.

16.11.0015

257229

Symptom/Scenario: The switch crashed immediately after configuring logging filter <> command options.

16.11.0015

257233

Symptom/Scenario: The message Authentication is not triggered appears both as debug log and throttled RMON log.

16.11.0014

257076

YC

Symptom: Affected ports do not come with the LED blinking amber. Self test failure will be reported for the ports in the event log.

Scenario: This issue occurred when the switch or the line card was rebooted with some SPF+ ports having 1G transceivers.

Workaround: Reboot the switch or the reload the module.

16.11.0014

257001

YC

Symptom/Scenario: Cold/Warm start trap are not seen intermittently in the customer setup when the switch is cold/warm booted.

16.11.0014

257114

YC

Symptom: Switch crashes with the following message: Task='eDhcpv6Rly'

Scenario: This issue occured when the dhcpv6 relay command was configured with corrupted number of sockets causing the crash.

Workaround: Disable the dhcpv6 relay command.

16.11.0014

257077

YC

Symptom: DHCP clients did not receive their IP addresses. The DHCP lease time is decremented to zero and is still available in the binding table.

Scenario: This issue occurred when multiple clients were connected to the server with a lease time of four minutes and ran the dhcp client command from the client device.

16.11.0013

257138

YC

Symptom: A configuration template push from Aruba Central fails.

Scenario: This issue occured when the configuration template is updated to dhcp-snooping vlan <vlanid rnage> from dhcp-snooping vlan <vlan>.

16.11.0013

257136

YC

Symptom: The switch sends cold start trap instead of warm start trap after rebooting.

Scenario: This issue occurred when the switch was rebooted with the boot system/reload/reboot command.

16.11.0013

257133

YC

Symptom: Switch crashes with the following error message:

Software exception at vls_xmit.c:161 – in 'mBonjourCtrl'

Scenario: This issue occurred when an MDNS profile was configured with a corrupted MDNS packet causing the crash.

16.11.0013

257073

YC

Symptom: Some DHCP client's DHCP offers are dropped by DHCP snooping.

Scenario: This issue occurred when the server pool is configured with different subnet masks wider than /24 and when the client requests an unicast DHCP offer packet.

Workaround: Configure multiple ranges in the pool excluding the following IP addresses:

• x.x.x.255

• x.x.x.0

16.11.0013

257098

YC

Symptom:The switch is unable to connect to Aruba Central.

Scenario: This issue occurred when the proxy server was configured on the switch and the activate-provision-force command was initiated.

16.11.0013

257089

YC

Symptom: Some switches are unable to connect to Aruba Central. The switch crashed with the following error message:

Internal error : HTTP/1.1 protocol missing. Please contact Aruba support.

Scenario: This crash occurred due to a rare timing issue.

Workaournd: Disable and enable Aruba Central.

16.11.0013

257088

YC

Symptom: A configuration template push of timesync with ntp from Aruba Central fails.

Scenario: This issue occurred when timesync <> configuration was pushed from Aruba Central when NTP was enabled.

16.11.0013

257082

YC

Symptom: NTP server authentication fails in Aruba Central.

Scenario: This issue occurred when the NTP key was validated with encrypt-credential enabled in Aruba Central.

Workaround: Reboot the switch after pushing the configurations.

16.11.0013

257070

YC

Symptom: The switch crashed and reboots while accessing the WebUI.

Scenario: This issue occurred when LLDP packets were sent with a system name TLV length of 255 by neighbour device.

Workaround: Disable LLDP on the port which is connected to a device sending LLDP packets with the values mentioned above.

16.11.0013

257063

YC

Symptom: The output of the command show power-over-ethernet <port> displays PD Power Draw value in decimals while the corresponding REST API truncates it to a whole number.

Scenario: This issue occurred when the REST API GET /ports/<port>/poe/stat command was configured.

16.11.0013

257049

YC

Symptom: Manager or operator credentials are lost after rebooting the switch.

Scenario: This issue occurred when the command include-credentials was enabled and the switch was power cycled.

Workaround: Save the switch configuration details after enabling include-credentials.

16.11.0012

256928

YC

Symptom: The interface module of the switch crashes with either of the following signatures.

• Ports 1-24,A subsystem went down: 12/15/22 08:31:08 KB.16.10.0020 646Software exception in kernel context at ghsException.c:1539-> Internal system error at 0x869e034

• Ports 1-24,A subsystem went down: 12/11/22 02:42:10 KB.16.10.0020 646Health Monitor: Write Error Restr Mem AccessHW Addr=0xc04e1c18 IP=0x882bfbc Task='mPmSlvCtrl' Task ID=0x6bce41c0Bus Err Data=0x00000000 Bus Err Status=0x100008d1 Status=0xb0000001 Bus Err Addr=0xec020f4

• Ports 9-16 subsystem went down: 12/08/22 01:09:01 KB.16.10.0020 646Health Monitor: Read Error Restr Mem AccessHW Addr=0xe0200410 IP=0x8800c74 Task='mIpAdMUpCt' Task ID=0x6bccc140Bus Err Data=0x00000000 Bus Err Status=0x100008d1 Status=0xb0000001 Bus Err Addr=0xec02f540

16.11.0012

257033

YC

Symptom: The switch logs the event

: Unsolicited Echo Reply from <ip address>.

Scenario: This issue occurred when the DHCP server was enabled on the switch and the DHCP client connected to the switch for the first time.

16.11.0012

257023

YC

Symptom: amp-server secret is not encrypted even after configuring encrypt-credentials.

Scenario: This problem occurred when the amp-server secret was configured, followed by encrypt-credentials, but the amp-server secret was not encrypted and appeared as plain-text under show running-config.

16.11.0012

257025

YC

Symptom: User role download from ClearPass fails.

Scenario: This issue occurred when the RADIUS server was reachable via OOBM interface and the Downloadable User Role feature was enabled.

Workaround: RADIUS server must be reachable via a non OOBM interface.

16.11.0012

257005

YC

Symptom: SSH session from the switch to AP505 does not close sometimes when the exit command is executed.

Scenario: This issue occurred when the SSH session is established from the switch to AP 505. execute the command exit.

Workaround: Use the key sequence ~.

16.11.0011

256995

YC

Symptom: Unable to get the LAG MIB information through SNMP in the operator mode.

Scenario: This issue occurred when the LACP and SNMP server community were configured in the operator mode and SNMP Walk was performed.

16.11.0011

256991

YC

Symptom: The switch fails to come online.

Scenario: This issue occurred when the netservice and netdestination was configured with ip access-list on the switch.

Workaround: Remove the netservice configuration.

16.11.0011

256958

YC

Symptom: The top interface metric is empty in the dashboard page of WebUI.

Scenario: This issue occurred when the WebUI was accessed 18 times or more with the duration of each access lasting more than a minute.

Workaround: Reboot the switch.

16.11.0011

256987

YC

Symptom: The switch crashes while connecting to Aruba Central.

Scenario: This issue occurred when the switch running AOS-S16.07 or older version was upgraded to AOS-S 16.08 or a later version and attempted to connect to Aruba Central. This issue has a very low probability of occurrence.

Workaround: Power cycle the switch one more time after the upgrade.

16.11.0011

256927

YC

Symptom: The devices that are not directly connected to the switch show up in the LLDP neighbour table.

Scenario: This issue occurred when the device sent LLDPDUs with the STP multicast destination MAC address and STP was disabled in the switch.

Workaround: Configure an ACL on the interface connected to the device to drop the packets with STP multicast destination MAC address.

16.11.0011

256905

YC

Symptom: The switch passwords are not erased after erase all command is executed.

Scenario: This issue occurred when the passwords were configured on the switch and then the erase all command was executed.

Workaround: Execute no password manager/no password operator commands prior to the erase all command.

16.11.0010

256651

YC

Symptom: System memory depletes and the switch reboots after a few months of runtime.

Scenario: This issue occurred when the switch was connected to AirWave, and the AirWave was polling certain MIBs including ieee8021SpanningTreeDesignatedRoot and hpicfXpsSwitchModType.

16.11.0010

256898

YC

Symptom: Authentication fails due to an insufficient ACL resources error.

Scenario: This issue occurred when the client was authenticated using a user role with a classifier configuration having a VLAN which was not configured on the switch.

Workaround: Make sure that the VLANs used in classifier configuration is present in the switch.

16.11.0010

256872

YC

Symptom: The switch crashes with the message similar to:NMI event SW:IP=0x0ea80030 MSR:0x02029200 LR:0x0ea800cccr: 0x42000400 sp:0x1f5d46e8 xer:0x00000000Task='mDsnoopCtrl' Task ID=0x1f5d13a8.

Scenario: This issue can occur if the DHCP snooping is enabled and the switch is processing continuous DHCP packets.

Workaround: Disable the DHCP snooping.

16.11.0010

256812

YC

Symptom: The simultaneous execution of Show Tech from the switch CLI and from Aruba Central may cause the switch to crash.

Scenario: This issue occurred when the user executed the Show Tech command in CLI and Aruba Central in parallel.

16.11.0010

256935

YC

Symptom: The switch crashed with a message similar to Software exception at wma_ctrl_sm.c:283 – in 'mWebAuth'.

Scenario: This issue occurred when the User Role, Auth order, and Server timeout were configured on the switch, and RADIUS server was unreachable.

16.11.0009

-

YC

Version 16.11.0009 is unavailable for download.

16.11.0008

256574

YC

Symptom: The switch crashes if the ip tcp randomize-timestamp configuration is present on the switch.

Scenario: This issue occurred when the switch had the ip tcp randomize-timestamp configuration and SSH/Telnet/Web UI was established on the switch.

Workaround: Remove the ip tcp randomize-timestamp configuration.

16.11.0008

256762

YC

Symptom: The switch configuration fails with an invalid oobm or 400 bad response error when the RADIUS server is updated with is_oobm or is_tls_oobm and the value is updated from False to False.

Scenario: This issue occurred when the PUT request was sent to the RADIUS server with is_oobm or is_tls_oobm and the value was updated from False to False (no change).

16.11.0007

256543

YC

Symptom: IPTV stream freezes on a periodic basis as the querier information is lost.

Scenario: This issue occurred when IGMPv3 query was sent with a QQIC value lower than IGMPv2 config.

Workaround: Change the querier interval value configured for IGMPv2 to value higher than 60 seconds (default IGMPv2 querier interval).

16.11.0007

256613

YC

Symptom/Scenario: Some IP addresses for save config and config change in the traps will not be displayed in AirWave.

16.11.0007

256575

YC

Symptom: The switch will stop responding to valid SNMP packets.

Scenario: This issue occurred when UDP packets were sent without any data. After 65 packets, the switch will stop responding to valid packets.

16.11.0007

256600

YC

Symptom: Client will not be in authenticated state until cached-reauth period.

Scenario: This issue occurred when 802.1x authentication was configured with cached-reauth.

Workaround:

• First, enable the user-role authentication and then configure the critical user-role for the authentication port.

• Critical user-role should not have the reauth-period attribute and auth-order should be removed for the authentication port.

16.11.0007

256732

YC

Symptom: Local-user with group cannot be configured via SNMP.

Scenario: This issue occurred when local-user with group using SNMP was configured.

Workaround: User can configure local-user with group using CLI configuration.

16.11.0006

256590

YC

16.11.0006

256491

YC

Scenario: This issue occurred when multiple clients were connected to the same access switch (the access layer with AOS-S switches and distribution/core layer with CX switches) receiving the same multicast stream, and one of the clients sent an IGMP leave.

NOTE: This fix is only specific to IGMPv2.

16.11.0006

256372

YC

Scenario: This issue occurred when there was a tagged trunk port in the secondary VLAN and the switch was rebooted.

Workaround: Remove the tagged trunk configuration from the secondary VLAN and re-add the tagged trunk configuration to the secondary VLAN.

16.11.0006

256485

YC

Scenario: This issue occurred when a GET request with an empty JSON payload was sent.

Workaround: Replace the empty JSON payload with None in the GET request.

16.11.0006

256358

YC

Scenario: This issue occurred when a banner and a manager password were configured but not an operator password.

Workaround: Remove the banner configuration.

16.11.0005

256366

YC

Symptom/Scenario: The switch crashes with a message similar to the following: Software exception at multMgmtUtil.c:259 – in 'mOobmCtrl' -> Internal error.

16.11.0005

256420

YC

Workaround: Use an interval value greater than 2 when configuring ip-recv-mac-address.

16.11.0005

256406

YC

Scenario: This issue occurred when the switch had both Layer 2 and Layer 3 VLANs and IP client tracker was enabled.

Workaround: Disable the IP client tracker.

Note: The IP address of silent clients being tracked may not be learnt unless a port bounce is performed after a redundancy failover.

16.11.0005

256122

YC

Scenario: This issue occurred when the port was configured to be a member of the trunk and subsequently removed from the trunk when the port was down. The issue will be seen when a client is connected to the port.

Workaround: Configure the trunk while the port is up.

16.11.0005

256069

YC

Scenario: This issue occurred when the 3810 stack rebooted with SFP+ flex modules and J8177D transceivers.

16.11.0004

256274

YC

Symptom/Scenario: VSF Stack Member crashed with a message similar to the following:

Software exception at lava_chassis_slot_sm.c:3626 – in 'eChassMgr', task ID = 0x37b07bc0.

16.11.0004

256257

YC

Symptom/Scenario: Certain transceivers had link issues in unsupported transceiver mode.

16.11.0004

256234

YC

Symptom: The show rmon statistics <port no> command returns the wrong counter values.

Scenario: This issue occurred when the clear statistics global or clear statistics <port no> was executed first and then show rmon statistics <port no>.

16.11.0004

256233

YC

Scenario: This issue can occur when multiple clients from different ports subscribed to the same group, which streams using HD channels requiring high bandwidth. TX drops can occur when several clients change channels simultaneously.

Workaround: Lower the bandwidth of the video streams to below 500 Mbps in order to avoid over-subscription of ports.

16.11.0004

256205

YC

Symptom: A configuration template push from Aruba Central fails.

Scenario: This issue occurred when the end devices are connected to ports that are configured with port-security learn-mode static.

16.11.0004

256121

YC

Symptom: Web authentication fails when the switch is managed by Aruba Central (aruba-central support-mode disable).

Scenario: This issue occurred when the switch connects to Aruba Central and aruba-central support-mode is disabled.

Workaround: Execute aruba-central support-mode enable command so the switch is no longer managed by Aruba Central.

16.11.0003

256037

YC

Symptom: Clients are not authenticated on a switch port.

Scenario: This issue occurred when multiple clients were connected to a single port (for example, a Personal Computer (PC) was connected to a phone), both MAC authentication and 802.1X authentication methods were attempted at the same time on the PC, and both the authentication methods used the same user role attribute.

Workaround: Configure the auth-order parameter first with authenticator, and then with mac-based.

16.11.0003

255940

YC

Symptom: A switch crashes with a message similar to the following:

Software exception at svc_misc.c:1088 – in 'mDHCPClint'

-> Failed to malloc 9202 bytes

Scenario: This issue occurred when the switch attempted to reconnect to Aruba Central.

16.11.0003

255928

YC

Symptom/Scenario: A switch is unable to connect to Aruba Central.

16.11.0003

255995

YC

Symptom: A switch crashes when the show port-access clients command is issued or when an SNMP GET operation is performed to get the MIB object hpicfUsrAuthMacAuthSessionStatsEntry.

Scenario: The switch crashed when a MAC-authenticated client had a username of more than 40 characters.

16.11.0003

256016

YC

Symptom: When a private VLAN is configured on a switch, the traffic from the secondary VLAN does not reach the primary VLAN.

Scenario: This issue occurred when the switch was rebooted, and the secondary VLAN contained a tagged trunk or Link Aggregation Control Protocol (LACP) port.

Workaround: Remove and add the tagged trunk or LACP configuration to the secondary VLAN.

16.11.0003

256034

YC

Symptom: SNMP MIB files are not reachable, and the MIB file returns some errors.

Scenario: This issue occurred when the customer used an SNMP monitoring tool to read or parse the MIB files.

16.11.0003

256050

YC

Symptom: A switch crashes when the WebUI Security > Clientspage is accessed.

Scenario: The switch crashed when a MAC-authenticated client had a username of more than 40 characters.

16.11.0002

255888

YC

Symptom/Scenario: When a proxy server is configured on the switch, the switch does not onboard into Aruba Central or Activate.

16.11.0002

255799

YC

Symptom: The user is unable to copy a configuration file to the switch using Secure File Transfer Protocol (SFTP) and the following error message is displayed.

Invalid input: grep usage error

Scenario: This issue occurred when the pipe character ( | ) was used as a part of the command input for some configuration commands, such as the banner motd and snmpv3 user commands.

Workaround: Do not use the pipe character (|) in the command input for the configuration commands.

16.11.0002

255825

YC

Symptom/Scenario: When a switch is rebooted through an SSH session, the show boot-history, show logging, and boot command outputs include the Operator cold reboot from TELNET session message instead of the Operator cold reboot from SSH session message.