Preview Tool

Cisco Bug: CSCvj14972 - Enable AID audit by default

Last Modified

Feb 05, 2019

Products (1)

  • Cisco 5500 Series Wireless Controllers

Known Affected Releases

8.3(140.0) 8.5(110.0) 8.7(102.0)

Description (partial)

After some time of operation, all association attempts to a given AP radio will be rejected with a status code 17.
The msglog will show an error similar to the following:

*apfMsConnTask_3: Jun 29 09:02:24.301: %LWAPP-3-INVALID_SLOT: spam_api.c:1636 The system detects an invalid slot identifier (1) - All the AIDs are in use. Could not allocate association identifier; AP 00:11:22:33:44:50

"debug client" will show output similar to the following:

apfMsConnTask_3: Jun 29 10:48:43.339: 00:22:44:66:88:00 Sending assoc-resp with status 17 station:00:22:44:66:88:00 AP:00:11:22:33:44:50-01 on apVapId 7
*apfMsConnTask_3: Jun 29 10:48:43.339: 00:22:44:66:88:00 Sending Assoc Response to station on BSSID 00:11:22:33:44:59 (status maximum station reached) ApVapId 7 Slot 1

If using FlexConnect local switching, the msglog may show messages similar to:

*apfMsConnTask_0: Jun 06 13:25:27.175: %APF-3-AID_UPDATE_FAILED: apf_80211.c:7631 Error updating Association ID for REAP AP Client00:11:22:33:44:55 - AID 2
*apfMsConnTask_0: Jun 06 13:25:27.175: %LWAPP-3-INVALID_AID2: spam_api.c:1791 Association identifier 2 for client 00:11:22:33:44:55 is already in use by 00:22:44:66:88:aa  for AP 00:40:96:00:01:00 slot 0 vap 1

AP has experienced numerous associations, since last reload.
Bug details contain sensitive information and therefore require a account to be viewed.

Bug Details Include

  • Full Description (including symptoms, conditions and workarounds)
  • Status
  • Severity
  • Known Fixed Releases
  • Related Community Discussions
  • Number of Related Support Cases
Bug information is viewable for customers and partners who have a service contract. Registered users can view up to 200 bugs per month without a service contract.