Issues and Workarounds

The following are known open issues with this branch of the software.

The Symptom statement describes what a user might experience if this is seen on the network. The Scenario statement provides additional environment details and trigger summaries. When available, the Workaround statement provides a workaround to the issue.

Table 1: Known Issues

Version

Bug ID

Software

Description

Category

16.10.0023

256631

WC

Symptom/Scenario: Client connected to a particular port will not be able to tunnel any traffic although it will appear to be in tunnel established state from the show commands.

Workaround: Disable or Enable UBT client port or tunneled-node globally (no tunneled-node-server enable/tunneled-node-server enable).

Tunneled Node

16.10.0022

256681

WC

Symptom: Loop protect does not block the PBT enabled port in tunnel established/establishing state.

Scenario: This issue occurred when the loop protect was enabled or configured for a PBT-enabled port in the tunnel-established state.

Workaround: Disable or enable PBT for the affected ports.

NOTE: When using PBT, it is recommended to use STP instead of loop protect. If inevitable, loop protect must be enabled first and then the PBT on the port.

Tunneled node

16.10.0022

256681

WC

Symptom: A PBT tunnel is formed for an MSTP-blocked port.

Scenario: This issue occurred when a PBT-enabled port was in a forwarding state for even one MSTP instance.

Workaround: Configure a single instance STP.

Tunneled node

16.10.0016

255646

WC

Symptom: The show statistics aclv4 <ACL-NAME-STR> vlan <VLAN-ID> out command displays lesser HitCounts for ACL for deny rule.

Scenario: The routed traffic is denied even before the egress Access control list (ACL) when the ACL contains a deny rule, and it is applied in the VLAN egress direction.

ACL

16.10.0015

255554

WC

Symptom: Aruba 2930F switches fail to connect to Aruba Central during the ZTP process.

Scenario: This issue occurs when the Simple Network Time Protocol (SNTP) or any other time protocol is not configured on the network.

Workaround: Use one of the following workarounds to fix this issue:

  • Manually configure the system time.
    • Set the current date and time using the time [HH:MM:SS] [MM/DD/YYYY] command.
    • Force connection to Aruba Central using the aruba-central disable and aruba-central enable commands.
  • Execute any reboot command that gracefully reboot the switch. The following are some of the commands that gracefully reboot the switch:
    • boot system flash {<primary | secondary>}
    • reboot
    • reset saved-configuration
  • Enable SNTP on the network.
    • By default, SNTP updates the system time. This issue does not occur when the SNTP server is enabled on the network.

Central

16.08.0009

247648

WC

Symptom: The switch fails to bypass authentication for random devices.

Scenario: When the CDP/LLDP bypass is enabled on a switch configured in VSF, the switch fails to bypass authentication for random devices after a redundancy switchover event.

Workaround: Disable and re-enable the affected port to re-enforce CDP/LLDP bypass on the port.

CDP/LLDP Bypass