Error Message %CAPWAP-3-AP_DB_ERR1: Unable to find AP
[hex]:[hex]:[hex]:[hex]:[hex]:[hex] entry in the database, could not process
[chars]

Explanation The operation that is being performed for the AP failed because the internal entry for the AP was not found. It is possible that the AP has been removed from the controller.

Recommended Action Use the show ap summary command to determine if the AP is still joined to the controller. If it is not, the message may be ignored. If it is still joined, restart the AP to ensure that it has the latest configuration.

Error Message %CAPWAP-3-DB_CREATOR_ERR: Database entry for AP
[dec]:[dec]:[dec]:[dec] is created in LWAPP, could not process [chars]

Explanation The operation that is being performed for the AP failed because the internal entry for the AP was created in LWAPP, and the message was received in CAPWAP.

Recommended Action Use the show ap summary command to determine if the AP is still joined to the controller. If it is not, the message may be ignored. If it is still joined, restart the AP to ensure that it will join in either CAPWAP or LWAPP.

Explanation A discovery response could not be sent to an AP because the controller was not able to obtain the IP address of the AP manager interface.

Recommended Action Correct the AP manager interface configuration.

Error Message %CAPWAP-3-DISC_BCAST_ERR: Ignoring a discovery request from AP
[hex]:[hex]:[hex]:[hex]:[hex]:[hex] via broadcast AP (IP =
[dec].[dec].[dec].[dec]) is not in the same subnet as the controller

Explanation The controller ignored a broadcast discovery request from an AP because the AP is not on the same subnet as the controller.

Explanation Due to an internal error, the time at which the AP discovery request was received was not recorded. The AP might join the controller and function normally, but monitoring of the APs presence or absence might not work as expected.

Recommended Action No action is required.

Error Message %CAPWAP-3-DISC_VLAN_ERR: Received a discovery request from AP
[hex]:[hex]:[hex]:[hex]:[hex]:[hex] on an unsupported VLAN ([int]), dropping the
request

Explanation A discovery request was received on a port on which no interface was created.

Recommended Action Check the network configuration to ensure that packets from the AP are correctly routed.

Explanation The system is Ignoring the image download request from the AP because the maximum number of concurrent image download requests are in progress. This condition is temporary. Future attempts by the AP might succeed.

Explanation The CAPWAP process might be busy. If this condition persists, it could lead to losing CAPWAP packets and dropping of AP connections. Also, APs might not getting configuration changes from the controller.

Explanation A discovery request from an AP was rejected because the maximum number of concurrent DTLS handshake sessions is already in progress. The AP might successfully join the controller on a later attempt.

Recommended Action No action is required.

Error Message %CAPWAP-2-SOCK_ERR: Error [chars] CAPWAP socket

Explanation An internal error has occurred. The CAPWAP subsystem could not be initialized.

Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the information you have gathered.

Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the information you have gathered.