topic LAP AIR-LAP1131G-E-K9 can't connect to controller in Wireless

LAP AIR-LAP1131G-E-K9 can't connect to controller

Radoslav Ivanov — Sun, 04 Jul 2021 06:37:14 GMT

Hi,

I have a problem with AIR-LAP1131G-E-K9 (Boot version 12.3.8.0) access point.

It can't connect to controller (WLC on SRE v.7.0.240.0) with error:

*spamReceiveTask: Feb 26 07:32:31.197: %LWAPP-3-PAYLOAD_MISSING: spam_lrad.c:5516 Join request does not contain BOARD_DATA payload.

do i need to do something manually with this access points?

I have 10 AIR-CAP3502I-R-K9, and they are working fine with controller.

Re: LAP AIR-LAP1131G-E-K9 can't connect to controller

Scott Fella — Tue, 26 Feb 2013 12:45:22 GMT

Make sure the country code for that AP is set also on then WLC. I'm also assuming that you have enough AP license.

Sent from Cisco Technical Support iPhone App

Re: LAP AIR-LAP1131G-E-K9 can't connect to controller

Radoslav Ivanov — Tue, 26 Feb 2013 13:01:11 GMT

Thank for your response.

Yes i have 25 AP lisence on the controller.

Country code on the controller is RU.

And as i mentioned before APs with 'R' are working fine.

here are the country code settings:

Regulatory Domain 802.11a: -AER

802.11bg: -AER

Re: LAP AIR-LAP1131G-E-K9 can't connect to controller

Scott Fella — Tue, 26 Feb 2013 13:14:25 GMT

No... You would have to use a country code that also uses 'E'. Make sure it's legal in the country your putting that Ap so you don't get in trouble.

Sent from Cisco Technical Support iPhone App

Re: LAP AIR-LAP1131G-E-K9 can't connect to controller

Radoslav Ivanov — Tue, 26 Feb 2013 13:18:43 GMT

I am sorry, just to be clear.

Is my current setup correct for AIR-LAP1131G-E-K9 APs:

Country code on the controller: RU.

Regulatory Domain 802.11a: -AER

802.11bg: -AER

AS I understand with 'RU' I can use access points with 'A', 'E' and 'R'?

Re: LAP AIR-LAP1131G-E-K9 can't connect to controller

Scott Fella — Tue, 26 Feb 2013 13:28:03 GMT

Look at this link as it will show what country uses 'E'. Then pick one and see if the AP joins

http://www.cisco.com/en/US/prod/collateral/wireless/ps5679/ps5861/product_data_sheet0900aecd80537b6a_ps10981_Products_Data_Sheet.html

Sent from Cisco Technical Support iPhone App

Re: LAP AIR-LAP1131G-E-K9 can't connect to controller

Radoslav Ivanov — Tue, 26 Feb 2013 13:49:32 GMT

even if I choose different region where only 1131 are supported, i've got the same error:

*spamReceiveTask: Feb 26 13:46:01.348: %LWAPP-3-PAYLOAD_MISSING: spam_lrad.c:5516 Join request does not contain BOARD_DATA payload

btw 3502 went to disable state due to region change...

Re: LAP AIR-LAP1131G-E-K9 can't connect to controller

maldehne — Tue, 26 Feb 2013 21:30:03 GMT

The error message you have listed id not enough to isolate the issue.

The AP Board Data message element is sent by the AP to WLC and contains information about the HW present.

To get a brief direct reason for not being able to associate , go to Monitor --> statistics --> AP join

click the AP and see why it is not able to join the WLC.

In the meantime you can collect the output of the following debugs on the controller:

debug mac addr < AP mac addr >

debug capwap event enable

debug capwap error enable

debug pm pki enable

from your ap console get the following:

debug capwap client event

debug capwap client error

show capwap client config

show capwap client rcb

-----------------------------------------------------------

Pleae Don't forget to rate correct answers

LAP AIR-LAP1131G-E-K9 can't connect to controller

Radoslav Ivanov — Thu, 28 Feb 2013 11:49:57 GMT

Thank you very much for debugging tips.

so on the controller i can see this access point for minute in Joined state, then it disconnects and try to connect again, here is the error log on the Web iface:

Lwapp join request rejected

RADIUS authorization is pending for the AP

on the console i see:

*spamReceiveTask: Feb 28 10:57:44.974: Could not find BoardDataPayload

*spamReceiveTask: Feb 28 10:57:44.977: 44:2b:03:eb:34:4c AP AP442b.03eb.344c: txNonce 00:00:00:00:00:00 rxNonce 00:00:00:00:00:00

*spamReceiveTask: Feb 28 10:57:44.977: 44:2b:03:eb:34:4c LWAPP Join Request MTU path from AP 44:2b:03:eb:34:4c is 1500, remote debug mode is 0

*spamReceiveTask: Feb 28 10:57:45.025: 44:2b:03:eb:34:4c Successful transmission of LWAPP Join Reply to AP 44:2b:03:eb:34:4c

*spamReceiveTask: Feb 28 10:57:45.026: 44:2b:03:eb:34:4c spam_lrad.c:1918 - Operation State 0 ===> 4

and no errors with the certificates, only this message:

*sshpmLscTask: Feb 28 11:42:25.627: sshpmLscTask: LSC Task received a message 4

right after AP disconnects and try to connect again.

i found similar problem (https://supportforums.cisco.com/thread/2159564) with no answer...

LAP AIR-LAP1131G-E-K9 can't connect to controller

maldehne — Thu, 28 Feb 2013 11:59:38 GMT

In the meantime please check the following

security --> AP Policies

Do you have Authorize MIC APs against auth-list or AAA checked

If so make sure to add the mac address of the AP and see how it goes.

LAP AIR-LAP1131G-E-K9 can't connect to controller

Radoslav Ivanov — Thu, 28 Feb 2013 12:05:48 GMT

nope, here is my setup

just fot test, i've added AP to auth list and check Auth MIC APs checkbox, all debugging is same...

LAP AIR-LAP1131G-E-K9 can't connect to controller

maldehne — Thu, 28 Feb 2013 12:12:49 GMT

can you provide the outputs for:

show capwap client config

show capwap client rcb

LAP AIR-LAP1131G-E-K9 can't connect to controller

Radoslav Ivanov — Thu, 28 Feb 2013 12:18:18 GMT

unfortunately i am not able to connect to AP, i will have console to it tomorrow.

Re: LAP AIR-LAP1131G-E-K9 can't connect to controller

Scott Fella — Thu, 28 Feb 2013 12:24:16 GMT

You probably have a corrupt image in the AP. you would need a console cable to do that though or use the mode button to automatically transfer the image.

http://www.cisco.com/en/US/docs/wireless/access_point/12.2_15_JA/configuration/guide/s15trb.html#wp1038660

Sent from Cisco Technical Support iPhone App

LAP AIR-LAP1131G-E-K9 can't connect to controller

Radoslav Ivanov — Thu, 28 Feb 2013 12:37:00 GMT

My company bought 10 APs pack (of these 1131 APs), I've tested 3 of them, and all have same errors. And as i expected new images on the Cisco site are under service contract...

Anyway i will try to gather more info from the access point as soon as I have console access.

LAP AIR-LAP1131G-E-K9 can't connect to controller

maldehne — Thu, 28 Feb 2013 12:45:34 GMT

Yeah Radoslav collect more to know more

LAP AIR-LAP1131G-E-K9 can't connect to controller

Radoslav Ivanov — Mon, 04 Mar 2013 08:40:39 GMT

Huh, things aren't getting better

After a couple of days fighting with console, I don't know what to do...

Looks like console doesn't work at all, i've tried different console cables, 2 APs, different speeds in connection settings, but all output i get from it is (and i get this output only if i try to type something):

But if i connect the console cable to router or switch it works fine...

Re: LAP AIR-LAP1131G-E-K9 can't connect to controller

Scott Fella — Mon, 04 Mar 2013 13:04:38 GMT

Might be better to RMA the APs than trying to figure out what's wrong. If you can console into any access points fine but not into another AP, that would be a good test. There are others in this forum that also had issues with the USB to serial adapters to. They are able to connect to the router and switches fine but not the AP. if you do have a good AP, console to that and see if it works or not.

Sent from Cisco Technical Support iPhone App

Re: LAP AIR-LAP1131G-E-K9 can't connect to controller

mkdickinson — Tue, 05 Mar 2013 18:16:25 GMT

I had similar problems when I tried to add some 1131's. For some unknown reason the AP's reset to bridge mode. I added their Mac Address to the AP authorization list, then when they re-joined, change them back to Local from Mesh. Then I could remove thier Mac, and they worked normally.

Re: LAP AIR-LAP1131G-E-K9 can't connect to controller

mkdickinson — Tue, 05 Mar 2013 18:19:46 GMT

How I saw it was I found references to MESH in the logs from the console of the AP's, when they should have been in local mode.

*Mar 1 00:00:51.326: %MESH-6-ADJACENCY_STATE_MACHINE_STARTED: Mesh adjacency st

ate machine started*Mar 1 00:00:51.326: %MESH-6-ADJACENCY_STATE_MACHINE_STARTED: Mesh adjacency st
ate machine started

*Mar 1 00:01:39.982: %MESH-6-CAPWAP_RESTART: Mesh Capwap re-started