Table - Error Messages and Descriptions | (Continued) | |
|
|
|
Error Message |
| Description |
|
|
|
COLD_START |
| Cisco Wireless LAN Controller may have been |
|
| rebooted. |
|
|
|
WARM_START |
| Cisco Wireless LAN Controller may have been |
|
| rebooted. |
|
|
|
Using Client Reason and Status Codes in the Trap Log
As described in Web User Interface Online Help, the Clients > Detail page lists the Reason and Status Codes you are likely to encounter when reviewing the Trap Logs. For your convenience the Reason and Status Codes and their descriptions are listed in the following sections:
•Client Reason Codes
•Client Status Codes
Client Reason Codes
The Client Reason code may be any of the following:
Table - Client Reason Code Descriptions and Meanings
Client |
|
|
|
Reason |
| Description | Meaning |
Code |
|
|
|
|
|
|
|
0 |
| noReasonCode | normal operation |
|
|
|
|
1 |
| unspecifiedReason | client associated but no longer authorized |
|
|
|
|
2 |
| previousAuthNotValid | client associated but not authorized |
|
|
|
|
3 |
| deauthenticationLeaving | the Cisco 1000 Series lightweight access point |
|
|
| went offline, deauthenticating the client |
|
|
|
|
4 |
| disassociationDueToInactivity | client session timeout exceeded |
|
|
|
|
5 |
| disassociationAPBusy | the Cisco 1000 Series lightweight access point is |
|
|
| busy, performing load balancing, for example |
|
|
|
|
6 |
| class2FrameFromNonAuthStation | client attempted to transfer data before it was |
|
|
| authenticated |
|
|
|
|
7 |
| class2FrameFromNonAssStation | client attempted to transfer data before it was |
|
| associated | |
|
|
| |
|
|
|
|
8 |
| disassociationStaHasLeft | Operating System moved the client to another |
|
|
| Cisco 1000 Series lightweight access point using |
|
|
| |
|
|
|
|
9 |
| staReqAssociationWithoutAuth | client not authorized yet, still attempting to |
|
|
| associate with an Cisco 1000 Series lightweight |
|
|
| access point |
|
|
|
|
99 |
| missingReasonCode | client momentarily in an unknown state |
|
|
|
|
|
|
|
|
5/26/05 |
|
| Troubleshooting Tips |
|
|