The documentation set for this product strives to use bias-free language. For the purposes of this documentation set, bias-free is defined as language that does not imply discrimination based on age, disability, gender, racial identity, ethnic identity, sexual orientation, socioeconomic status, and intersectionality. Exceptions may be present in the documentation due to language that is hardcoded in the user interfaces of the product software, language used based on RFP documentation, or language that is used by a referenced third-party product. Learn more about how Cisco is using Inclusive Language.
THIS FIELD NOTICE IS PROVIDED ON AN "AS IS" BASIS AND DOES NOT IMPLY ANY KIND OF GUARANTEE OR WARRANTY, INCLUDING THE WARRANTY OF MERCHANTABILITY. YOUR USE OF THE INFORMATION ON THE FIELD NOTICE OR MATERIALS LINKED FROM THE FIELD NOTICE IS AT YOUR OWN RISK. CISCO RESERVES THE RIGHT TO CHANGE OR UPDATE THIS FIELD NOTICE AT ANY TIME.
Clients fails to connect to AP with message as All AIDs are in use when the AP is in Local mode
After some time of operation, all association attempts to a given access point (AP) radio are rejected with Association Response status 17 and one of these error messages:
In local mode: 'All the AIDS are in use'
In FlexConnect mode: 'Association identifier...is already in use'
Note: Association Response status 17 can occur for a variety of reasons.
Each AP radio has an Association ID (AID) table that contains an entry for each client. The WLC maintains a table that corresponds to the AID table. The AID table and the WLC table can sometimes become out of sync with each other. If the tables become out of sync, all association attempts to the affected radio will fail until the AP is reloaded.
After some time of operation, all association attempts to a given AP radio are rejected with Association Response status 17. In addition, the WLC message log (msglog) shows an error message similar to one of these examples:
In local mode:
*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:53:00:33:44:50
In FlexConnect mode:
*apfMsConnTask_0: Jun 06 13:25:27.175: %APF-3-AID_UPDATE_FAILED: apf_80211.c:7631 Error updating Association ID for REAP AP Client 00:53:ff: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:53:ff:33:44:55 is already in use by 00:53:ee:06:08:0a for AP 00:53:00:33:44:50 slot 0 vap 1
Note: Association Response status 17 can be sent for a variety of other reasons. In order to confirm this problem, look in the message text for either of these phrases:
In local mode: "All the AIDs are in use"
In FlexConnect mode: "Association identifier...is already in use"
Reload each affected AP in order to resolve the problem temporarily.
Upgrade to software that includes the fixes for Cisco bug IDs CSCve81314 and CSCve81269:
8.0MR5esc (available from the Cisco Technical Assistance Center)
126.96.36.199 and later
188.8.131.52 and later
8.6 and later
How to Identify Affected Products
This issue affects Cisco IOS® APs such as the 3500, 2600, 3600, 2700, and 3700 series. This issue can affect APs that run in local mode or in FlexConnect mode.
The issue does not affect Cisco IOS APs that run in autonomous mode.
This issue does not affect AP-COS APs such as the 1800, 2800, or 3800 series.
Clarified That AireOS 7.6, 8.0 Except for .150 and .152, 8.1, and 8.3 Are Not Affected by the Documented Defects
For More Information
For further assistance or for more information about this field notice, contact the Cisco Technical Assistance Center (TAC) using one of the following methods:
Receive Email Notification About New Field Notices
To receive email updates about Field Notices (reliability and safety issues), Security Advisories (network security issues), and end-of-life announcements for specific Cisco products, set up a profile in My Notifications