Select Version
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.
|
Version |
Bug ID |
Software |
Description |
Category |
|---|---|---|---|---|
|
16.08.0014 |
247843 |
KB |
Symptom: The switch unintentionally reboots after configuration changes. Scenario: When configuration changes are applied to a switch managed by AirWave over the OOBM port and a redundancy switchover event occurs, any subsequent switch configurations applied from AirWave cause a switch reboot, although the applied configuration changes do not require a reboot. Workaround: Use the boot or reload commands in place of the redundancy switchover command to trigger the switchover. |
AirWave |
|
16.08.0014 |
247648 |
KB |
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 |
|
16.08.0014 |
247936 |
KB |
Symptom: Under certain scenarios, the switch fails to display the VLAN name in the output of the show ip command. Scenario: After a switch configuration is restored using AirWave cfg-restore over the switch OOBM interface and the switch has already configured VLAN names, the switch fails to display the VLAN name in the output of the show ip command. Workaround: Use the commands show vlan or show running-config vlan to display the VLAN names. |
Config restore |
|
16.08.0014 |
246466 |
KB |
Symptom: The switch denies access to already-authenticated clients. Scenario: If the number of authenticated clients with applied user roles policies is greater than 256, the already authenticated users may be placed into "deny all" state after adding a new ACE to an existing role. Workaround: Force a user re-authentication from the CLI or disable/re-enable the ports. To avoid the issue, it is recommended to configure the Initial Role with a shortened re-authentication period (example 60 seconds). |
User Roles |
Search Results
