...
BugZero updated this defect 38 days ago.
A wireless client automatically associates, but after a few seconds, it is no longer able to ping its default gateway. If, at that time, the following output from the AP CLI is examined: 1. show controllers dot11Radio 0 client 2. show controllers dot11Radio 1 client 2. show controllers nss status The client MAC address is present in the "show controllers dot11 0[ or 1] client"output and NOT present in "show controllers nss status" - this is the footprint of this bug.
Problem is seen on 2800/3800/1560 series access points, not on IOS APs nor on other AP-COS AP models (1800, 1540 series.) Problem is seen regardless of client type.
Have the client reassociate to the SSID.
Although this fix CSCve57121 is committed to 8.3.140.0, the symptoms described in this bug DO NOT actually affect any 8.3 release.
7.5
ISE Evaluate OpenSSH CVE-2024-6387 "regreSSHion"7.5
Auth Step latency for policy evaluation due to Garbage Collection activity.7.5
Cisco 2800, 3800 and 1560 series APs fail to pass traffic7.5
M500IT Model Solid State Drives on 4100/9300 may go unresponsive after 3.2 Years in service7.5
Access Points stuck in bootloop due to image checksum verification failed7.5
ISE Evaluate OpenSSH CVE-2024-6387 "regreSSHion"7.5
Auth Step latency for policy evaluation due to Garbage Collection activity.7.5
Cisco 2800, 3800 and 1560 series APs fail to pass traffic7.5
M500IT Model Solid State Drives on 4100/9300 may go unresponsive after 3.2 Years in service7.5
Access Points stuck in bootloop due to image checksum verification failed