topic Re: 1852 AP Unable to join controller in Wireless

1852 AP Unable to join controller

niketan sutar — Fri, 02 Jul 2021 22:48:56 GMT

Hi,

I am experiencing a peculiar issue:

i have a 2504 running 8.0.120.0. I am trying to get a new 1850 running ap1g4-k9w8-tar.153-3.JD.tar. ver however whenever i try to get it to join to the controller i get a series of messages listed below.

i have tried upgrading and downgading the AP, tried doing a factory reset but none has worked for me so far.

This AP model is supported by controller version newer than 7.0.0.0!
Discovery response from MWAR ''running version 0.0.0.0 is rejected.
Failed to decode discovery response.
CAPWAP SM handler: Failed to process message type 2 state 2.
Failed to handle capwap control message from controller - status 4
Failed to process unencrypted capwap packet from 192.168.1.200
Failed to send capwap message 0 to the state machine. Packet already freed.
wtpProcessPacketFromSocket returned 4
Discovery Response from 192.168.1.200

wcp/RadDrv1 :: Dot11BaseDriver get_vap_if_index ioctl SIOCGIFINDEX failed for apr1v0 error No such device
[*07/29/2016 03:59:10.0181] wcpd: /local/build/JENKINS/workspace/Nightly-Cheetah-corsica-c8_3_throttle-FC3-CCO/base/../elts-meraki/elements/wcp/wcp_db.cc: 1184: void WcpDb::populate_if_index_table(): Assertion `if_index >= 0 && if_index < 64' failed.
[*07/29/2016 03:59:24.3136] ethernet_port wired0, ip 192.168.1.152, netmask 255.255.255.0, gw 192.168.1.1, mtu 1500, bcast 192.168.1.255, dns1 192.168.1.51, dns2 192.168.1.61, domain cgc.co
[*07/29/2016 03:59:37.4096] !!!!! {watchdogd} Process wcpd gone for 60s

this wcpd goes on increasing to 120/180/240 and so on till the AP resets.

Please help.

Hi,

Sandeep Choudhary — Wed, 17 Aug 2016 09:29:24 GMT

Hi,

1852 AP needs the minimum SW version of 8.1.111.0 on Cisco WLC to join.

Here is the compatibility matrix: http://www.cisco.com/c/en/us/td/docs/wireless/compatibility/matrix/compatibility-matrix.html

Please upgrade the SW on WLC and try again.

Regards

Dont forget to rate helpful posts

i have upgraded my Controller

niketan sutar — Thu, 18 Aug 2016 07:24:22 GMT

i have upgraded my Controller to 8.2.100.0... i am still facing the same issue.

paste the output of these

Sandeep Choudhary — Thu, 18 Aug 2016 10:58:37 GMT

paste the output of these commands:

from AP: sh version

From WLC: sh sysinfo

Also paste the boot-up process from cisco AP console.

Regards

Dont forget to rate helpful posts

Re: 1852 AP Unable to join controller

Rps-Cheers — Mon, 26 Mar 2018 03:29:57 GMT

Hi niketan sutar
Weather you have resolved the issue?Could you tell how to resolved this issue,because of i also face the problem,thanks~

Re: 1852 AP Unable to join controller

dhshukla — Tue, 27 Mar 2018 11:40:38 GMT

Hi ,

Kindly post the below output from WLC.

debug mac <AP ethernet mac>

debug pm pki enable

debug capwap errors enable

From AP side :-

show version

Need AP console logs please

Additionally post below debug logs

debug capwap client error
debug capwap client event

You mentioned that you have upgraded the AP but didn't help . May I know which version were you upgraded to ?

Many thanks !

Re: 1852 AP Unable to join controller

Rps-Cheers — Tue, 27 Mar 2018 12:05:53 GMT

HI dhshukla:
Thanks your feed back.
But,thesedays,i can't get the debug info.I remember some detail,that is below:
this AP model is supported by controller version newer than 7.0.0.0!
Discovery response from MWAR ''running version 0.0.0.0 is rejected.
Failed to decode discovery response.
CAPWAP SM handler: Failed to process message type 2 state 2.
Failed to handle capwap control message from controller - status 4

I have upgraded the WLC to 8.3.133,but it doesn't well,and then trying to join another WLC,there is also having same issue.I have found out there is a bug about AP1562 which is CSCvf71074;and another bug about AP2800 which is CSCvc32590.
Do you know that problem?Even though i issue debug command on wlc,there is always have same debug info,just like it that i give just now.

Thanks~

Re: 1852 AP Unable to join controller

rgmamaril — Wed, 02 May 2018 04:31:47 GMT

Hi All,

good day!

I also encounter the same issue. May we request to share your resolution for this issue.

05/01/2018 10:53:26.9135] waiting for WCP to initialize
[*05/01/2018 10:53:26.9135] waiting for WCP to initialize
[*05/01/2018 10:53:26.9135] waiting for WCP to initialize
[*05/01/2018 10:53:26.9135] waiting for WCP to initialize
[*05/01/2018 10:53:26.9135] waiting for WCP to initialize
[*05/01/2018 10:53:26.9135] waiting for WCP to initialize
[*05/01/2018 10:53:26.9135] waiting for WCP to initialize
[*05/01/2018 10:53:26.9135] waiting for WCP to initialize
[*05/01/2018 10:53:26.9135] waiting for WCP to initialize
[*05/01/2018 10:53:26.9135] waiting for WCP to initialize
[*05/01/2018 10:53:26.9135] waiting for WCP to initialize
[*05/01/2018 10:53:26.9135] Socket Invalid Element wcp/wcp_db Handler has_rlan Data 0 Length 10
[*05/01/2018 10:53:26.9135] CAPWAP State: Discovery
[*05/01/2018 10:53:26.9135] Discovery Request sent to 192.168.25.11, discovery type STATIC_CONFIG(1)
[*05/01/2018 10:53:26.9135] Discovery Request sent to 192.168.25.1, discovery type STATIC_CONFIG(1)
[*05/01/2018 10:53:26.9135] Discovery Request sent to 192.168.25.11, discovery type STATIC_CONFIG(1)
[*05/01/2018 10:53:26.9135] Discovery Request sent to 192.168.25.1, discovery type STATIC_CONFIG(1)
[*05/01/2018 10:53:26.9235] Discovery Request sent to 255.255.255.255, discovery type UNKNOWN(0)
[*05/01/2018 10:53:26.9235] CAPWAP State: Init
[*05/01/2018 10:53:26.9235] CAPWAP State: Discovery
[*05/01/2018 10:53:27.9231] Discovery Response from 192.168.25.11
[*05/01/2018 10:53:27.9231]
[*05/01/2018 10:53:27.9231] This AP model is supported by controller version newer than 7.0.0.0!
[*05/01/2018 10:53:27.9231]
[*05/01/2018 10:53:27.9231] Discovery response from MWAR ''running version 0.0.0.0 is rejected.
[*05/01/2018 10:53:27.9231] Failed to decode discovery response.
[*05/01/2018 10:53:27.9231] CAPWAP SM handler: Failed to process message type 2 state 2.
[*05/01/2018 10:53:27.9231] Failed to handle capwap control message from controller - status 4
[*05/01/2018 10:53:27.9231] Failed to process unencrypted capwap packet from 192.168.25.11
[*05/01/2018 10:53:27.9231] Failed to send capwap message 0 to the state machine. Packet already freed.
[*05/01/2018 10:53:27.9231] wtpProcessPacketFromSocket returned 4
[*05/01/2018 10:53:27.9231] Discovery Response from 192.168.25.11
[*05/01/2018 10:53:27.9231]
[*05/01/2018 10:53:27.9231] This AP model is supported by controller version newer than 7.0.0.0!
[*05/01/2018 10:53:27.9231]
[*05/01/2018 10:53:27.9231] Discovery response from MWAR ''running version 0.0.0.0 is rejected.
[*05/01/2018 10:53:27.9231] Failed to decode discovery response.
[*05/01/2018 10:53:27.9231] CAPWAP SM handler: Failed to process message type 2 state 2.
[*05/01/2018 10:53:27.9231] Failed to handle capwap control message from controller - status 4
[*05/01/2018 10:53:27.9231] Failed to process unencrypted capwap packet from 192.168.25.11
[*05/01/2018 10:53:27.9231] Failed to send capwap message 0 to the state machine. Packet already freed.
[*05/01/2018 10:53:27.9231] wtpProcessPacketFromSocket returned 4
[*05/01/2018 10:53:27.9231] Discovery Response from 192.168.25.11
[*05/01/2018 10:53:27.9231]
[*05/01/2018 10:53:27.9231] This AP model is supported by controller version newer than 7.0.0.0!
[*05/01/2018 10:53:27.9231]
[*05/01/2018 10:53:27.9231] Discovery response from MWAR ''running version 0.0.0.0 is rejected.
[*05/01/2018 10:53:27.9231] Failed to decode discovery response.

thank you.

Rey

Re: 1852 AP Unable to join controller

Rps-Cheers — Wed, 02 May 2018 04:45:39 GMT

HI rgmamaril
I have made a RMA for that bad AP,then,the issue have been fixed.

Re: 1852 AP Unable to join controller

rgmamaril — Wed, 02 May 2018 05:59:11 GMT

Hi Moments,

Thank you very much for the answer. This helps a lot.

Regards,

Rey

Re: 1852 AP Unable to join controller

rgmamaril — Wed, 02 May 2018 06:58:05 GMT

Hi Moments,

good day!

is there any specific details from tac or documents that the issue is because of hardware failure?

thank you.

Rey

Re: 1852 AP Unable to join controller

Rps-Cheers — Wed, 02 May 2018 08:07:41 GMT

Hi rgmamaril
I have tried to upgraded and downgraded the wlc,but the issue was the same as before.
I cannot fixed it by command ，or change the software version,so,i decided to run a RMA.Then,the issue have beed fixed.
thanks~

Re: 1852 AP Unable to join controller

rgmamaril — Wed, 02 May 2018 08:10:06 GMT

Thank you very much Moments. 🙂

Re: 1852 AP Unable to join controller

sbhadrav@cisco.com — Wed, 16 May 2018 08:10:12 GMT

If you face issues with converting the AP software to a Cisco Mobility Express software, upgrade the AP
CAPWAP software to the latest AP software version ap1g4-k9w8-tar.153-3.JD.tar. Now, you can convert
the CAPWAP software to the Cisco Mobility Express software AIR-AP2800-K9-ME-8-3-102-0.tar.
This issue occurs in Mobility Express-capable APs shipped with default images or a version of the images
prior to Cisco Wireless Release 8.3. This is due to insufficient space in the AP’s memory or because the
AP has been started in U-boot mode where the image is not found in flash.
The following procedure shows a conversion from the 8.1.122.0 Lightweight APrelease on an 1850 series
AP, and hence uses the corresponding software file. Ensure that you use the appropriate software file
depending on the release you are converting from and the AP model.
• Your AP is either a Cisco 1850 Series or a 1830 Series AP with Lightweight AP software Release
15.3.3-JBB5, for Cisco Wireless Controller Software Release 8.1.122.0, or a newer software.
• A TFTP server and a DHCP server should be configured and accessible.
• Ensure that there are no Cisco WLCs, physical or virtual, in the network while you are performing this
upgrade. The AP must not interface with any other wireless controller while you are performing this
upgrade.
Step 1 Download the AIR-AP1850-K9-8.1.122.0.tar software file from Cisco.com to the TFTP server.
On the Download Software page, for a given release, this .TAR file is labeled, 'Software to be used for conversion from
Lightweight Access Points only'.
Step 2 Connect to the console port of the AP.
Step 3 Log in to the AP using the username Cisco and password Cisco. Both are case-sensitive.
This is the default factory-shipped username and password on all Cisco Aironet APs.
Step 4 To convert the AP from CAPWAP lightweight AP software to Cisco Mobility Express software, use the ap-type
mobility-express tftp://<tftp server ip-address>/<filename of TAR file with path from root on the TFTP server>
command.
The software file is downloaded to the AP, and is written to the AP's flash memory. The AP reboots with a Mobility
Express-capable configuration and starts broadcasting the CiscoAirProvison SSI

Re: 1852 AP Unable to join controller

Leo Laohoo — Wed, 16 May 2018 21:04:13 GMT

@rgmamaril wrote:

[*05/01/2018 10:53:27.9231] This AP model is supported by controller version newer than 7.0.0.0!

What firmware is the controller running on?

Re: 1852 AP Unable to join controller

DavidZhang47328 — Tue, 09 Nov 2021 08:15:46 GMT

Hi Rps-Cheers,

Hope you are doing well.

I have this problem now, as you said this should be a software bug, have you tried to upgrade the version of WLC? Or you just runs the RMA, and the problems didn't happen again?

Looking forward to your reply.

Many thanks

David