BUG搬运工-Clients fails to connect to AP with message as All AIDs are in use when the AP is in Local mode
Clients fails to connect to AP with message as All AIDs are in use when the AP is in Local mode
CSCve81314
Symptom:
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
Note: an Assoc Response with status 17 may be sent for a variety of reasons.
Conditions:
AP has experienced numerous associations, since last reload.
Running AireOS with the CSCvd27365 fix.
IOS, not AP-COS APs.
APs in local mode, not FlexConnect mode (track CSCve81269 for similar symptoms in FlexConnect)
Clients roaming.
Workaround:
Reload AP.
Further Problem Description:
This bug will address AID problems with local mode APs. For fixes to AID problems with FlexConnect local switching, track CSCve81269.
This bug is a regression caused by the commit of an earlier attempted fix of AID problems, CSCuz49804, in 8.0.150.0, 8.3.140.0 and in 8.4.100.0. Since CSCuz49804 was not committed to 8.2, this bug CSCve81314 does not affect any 8.2 release.
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
Note: an Assoc Response with status 17 may be sent for a variety of reasons.
Conditions:
AP has experienced numerous associations, since last reload.
Running AireOS with the CSCvd27365 fix.
IOS, not AP-COS APs.
APs in local mode, not FlexConnect mode (track CSCve81269 for similar symptoms in FlexConnect)
Clients roaming.
Workaround:
Reload AP.
Further Problem Description:
This bug will address AID problems with local mode APs. For fixes to AID problems with FlexConnect local switching, track CSCve81269.
This bug is a regression caused by the commit of an earlier attempted fix of AID problems, CSCuz49804, in 8.0.150.0, 8.3.140.0 and in 8.4.100.0. Since CSCuz49804 was not committed to 8.2, this bug CSCve81314 does not affect any 8.2 release.
好好学习，天天向上！
