WLC and Air 1231G

[jimcalano]

I have a 4402 WLC configured on the management VLAN and 9 AP's that were converted to LWAPP. When the AP's attempt to connect to the WLC, they download the image then display the following error. "No more AP manager IP addresses remain." The AP's then reboot and go through the whole process again. It doesn't matter if I assign static IP's or set them to DHCP, the same error appears.

[Leo Laohoo · Accepted solution]

Hi,

Go through the following links:

http://www.cisco.com/en/US/products/ps6366/products_tech_note09186a00808f8599.shtml#p5

http://www.cisco.com/en/US/products/ps6366/products_tech_note09186a00808f8599.shtml#P13

Hope this helps.

[jimcalano]

I tried both suggestions without success. The same thing continues to happen.

Looking at the logs, I see that APs are associating then immediately disassociating. If it helps here are 15 minutes or so of message logs from the WLC.

Jun 04 09:11:04.996 spam_lrad.c:4306 LWAPP-3-HDR_ENCAP_ERR: Unable to encapsulate LWAPP header for discovery response; AP 00:24:14:11:50:c0

Jun 04 09:11:04.996 apf_net.c:807 APF-3-PDU_ENCAP_FAILED: Failed to encapsulate a PDU for transmission to station00:00:00:00:00:00. Destination IP address not set in L3 mode.

Jun 04 09:10:59.321 spam_lrad.c:4306 LWAPP-3-HDR_ENCAP_ERR: Unable to encapsulate LWAPP header for discovery response; AP 00:24:14:11:4c:00

Jun 04 09:10:59.321 apf_net.c:807 APF-3-PDU_ENCAP_FAILED: Failed to encapsulate a PDU for transmission to station00:00:00:00:00:00. Destination IP address not set in L3 mode.

Jun 04 09:10:57.869 spam_lrad.c:4306 LWAPP-3-HDR_ENCAP_ERR: Unable to encapsulate LWAPP header for discovery response; AP 00:24:14:11:4d:40

Jun 04 09:10:57.869 apf_net.c:807 APF-3-PDU_ENCAP_FAILED: Failed to encapsulate a PDU for transmission to station00:00:00:00:00:00. Destination IP address not set in L3 mode.

Jun 04 09:03:41.137 spam_lrad.c:4306 LWAPP-3-HDR_ENCAP_ERR: Unable to encapsulate LWAPP header for discovery response; AP 00:24:14:11:50:c0

Jun 04 09:03:41.137 apf_net.c:807 APF-3-PDU_ENCAP_FAILED: Failed to encapsulate a PDU for transmission to station00:00:00:00:00:00. Destination IP address not set in L3 mode.

Jun 04 09:03:35.676 spam_lrad.c:4306 LWAPP-3-HDR_ENCAP_ERR: Unable to encapsulate LWAPP header for discovery response; AP 00:24:14:11:4c:00

Jun 04 09:03:35.676 apf_net.c:807 APF-3-PDU_ENCAP_FAILED: Failed to encapsulate a PDU for transmission to station00:00:00:00:00:00. Destination IP address not set in L3 mode.

Jun 04 09:03:33.689 spam_lrad.c:4306 LWAPP-3-HDR_ENCAP_ERR: Unable to encapsulate LWAPP header for discovery response; AP 00:24:14:11:4d:40

Jun 04 09:03:33.689 apf_net.c:807 APF-3-PDU_ENCAP_FAILED: Failed to encapsulate a PDU for transmission to station00:00:00:00:00:00. Destination IP address not set in L3 mode.

Jun 04 08:57:44.898 acl.c:244 ACL-3-ENTRY_DONOT_EXIST: Unable to find an ACL by name "".

Jun 04 08:54:59.294 spam_radius.c:105 LWAPP-3-RADIUS_ERR: Could not send join reply, AP authorization failed; AP:00:24:14:11:4c:00

Jun 04 08:54:34.373 spam_radius.c:105 LWAPP-3-RADIUS_ERR: Could not send join reply, AP authorization failed; AP:00:24:14:11:50:c0

Jun 04 08:54:26.790 spam_radius.c:105 LWAPP-3-RADIUS_ERR: Could not send join reply, AP authorization failed; AP:00:24:14:11:4d:40

Jun 04 08:54:01.664 spam_radius.c:105 LWAPP-3-RADIUS_ERR: Could not send join reply, AP authorization failed; AP:00:24:14:11:4c:70

Jun 04 08:53:56.648 spam_radius.c:105 LWAPP-3-RADIUS_ERR: Could not send join reply, AP authorization failed; AP:00:24:14:11:4c:70

Jun 04 08:52:28.307 spam_radius.c:105 LWAPP-3-RADIUS_ERR: Could not send join reply, AP authorization failed; AP:00:24:14:11:50:c0

Jun 04 08:52:21.897 spam_radius.c:105 LWAPP-3-RADIUS_ERR: Could not send join reply, AP authorization failed; AP:00:24:14:11:4c:00

Jun 04 08:52:20.498 spam_radius.c:105 LWAPP-3-RADIUS_ERR: Could not send join reply, AP authorization failed; AP:00:24:14:11:4d:40

Jun 04 08:50:22.411 spam_radius.c:105 LWAPP-3-RADIUS_ERR: Could not send join reply, AP authorization failed; AP:00:24:14:11:50:c0

Jun 04 08:50:16.030 spam_radius.c:105 LWAPP-3-RADIUS_ERR: Could not send join reply, AP authorization failed; AP:00:24:14:11:4c:00

Jun 04 08:50:15.042 spam_radius.c:105 LWAPP-3-RADIUS_ERR: Could not send join reply, AP authorization failed; AP:00:24:14:11:4d:40

Jun 04 08:48:16.760 spam_radius.c:105 LWAPP-3-RADIUS_ERR: Could not send join reply, AP authorization failed; AP:00:24:14:11:50:c0

[jimcalano]

Thank you. It was a duplicate IP address. *sigh*

One of the reasons for this error message is when there is a duplicate IP address on the network that matches the AP manager IP address. In such a case, the LAP keeps power cycling and cannot join the controller.

[Leo Laohoo]

Error Message %LWAPP-3-HDR_ENCAP_ERR: Unable to encapsulate LWAPP header for [chars]; AP [hex]:[hex]:[hex]:[hex]:[hex]:[hex]

Explanation Could not send the LWAPP packet due to an internal error in encapsulating the packet. AP may not function as expected.

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://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. 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.

[Leo Laohoo]

Thanks for the rating Jim.