topic Re: AP not joining WLC in Wireless

AP not joining WLC

Nadeem Jan — Mon, 05 Jul 2021 18:14:59 GMT

Can anyone help

AP Model 1852

logs are below

Discovery Request sent to 192.168.31.10, discovery type STATIC_CONFIG(1)
[*11/05/2019 03:41:32.1193] Discovery Request sent to 255.255.255.255, discovery type UNKNOWN(0)
[*11/05/2019 03:41:32.1193] Discovery Response from 192.168.31.10
[*11/05/2019 03:41:32.1193]
[*11/05/2019 03:41:32.1193] This AP model is supported by controller version newer than 7.0.0.0!
[*11/05/2019 03:41:32.1193]
[*11/05/2019 03:41:32.1193] Discovery response from MWAR ''running version 0.0.0.0 is rejected.
[*11/05/2019 03:41:32.1193] Failed to decode discovery response.
[*11/05/2019 03:41:32.1193] CAPWAP SM handler: Failed to process message type 2 state 2.
[*11/05/2019 03:41:32.1193] Failed to handle capwap control message from controller - status 4
[*11/05/2019 03:41:32.1193] Failed to process unencrypted capwap packet from 192.168.31.10
[*11/05/2019 03:41:32.1193] Failed to send capwap message 0 to the state machine. Packet already freed.
[*11/05/2019 03:41:32.1193] wtpProcessPacketFromSocket returned 4
[*11/05/2019 03:41:32.1193] Discovery Response from 192.168.31.10
[*11/05/2019 03:41:32.1193]
[*11/05/2019 03:41:32.1193] This AP model is supported by controller version newer than 7.0.0.0!
[*11/05/2019 03:41:32.1193]
[*11/05/2019 03:41:32.1193] Discovery response from MWAR ''running version 0.0.0.0 is rejected.
[*11/05/2019 03:41:32.1193] Failed to decode discovery response.
[*11/05/2019 03:41:32.1193] CAPWAP SM handler: Failed to process message type 2 state 2.
[*11/05/2019 03:41:32.1193] Failed to handle capwap control message from controller - status 4
[*11/05/2019 03:41:32.1193] Failed to process unencrypted capwap packet from 192.168.31.10
[*11/05/2019 03:41:32.1193] Failed to send capwap message 0 to the state machine. Packet already freed.
[*11/05/2019 03:41:32.1193] wtpProcessPacketFromSocket returned 4
[*11/05/2019 03:41:32.1193] Discovery Response from 192.168.31.10
[*11/05/2019 03:41:32.1193]
[*11/05/2019 03:41:32.1193] This AP model is supported by controller version newer than 7.0.0.0!
[*11/05/2019 03:41:32.1193]
[*11/05/2019 03:41:32.1193] Discovery response from MWAR ''running version 0.0.0.0 is rejected.
[*11/05/2019 03:41:32.1193] Failed to decode discovery response.
[*11/05/2019 03:41:32.1193] CAPWAP SM handler: Failed to process message type 2 state 2.
[*11/05/2019 03:41:32.1193] Failed to handle capwap control message from controller - status 4
[*11/05/2019 03:41:32.1193] Failed to process unencrypted capwap packet from 192.168.31.10
[*11/05/2019 03:41:32.1193] Failed to send capwap message 0 to the state machine. Packet already freed.
[*11/05/2019 03:41:32.1193] wtpProcessPacketFromSocket returned 4
[*11/05/2019 03:41:32.1193] Discovery Response from 192.168.31.10
[*11/05/2019 03:41:32.1193]
[*11/05/2019 03:41:32.1193] This AP model is supported by controller version newer than 7.0.0.0!
[*11/05/2019 03:41:32.1193]
[*11/05/2019 03:41:32.1193] Discovery response from MWAR ''running version 0.0.0.0 is rejected.
[*11/05/2019 03:41:32.1193] Failed to decode discovery response.
[*11/05/2019 03:41:32.1193] CAPWAP SM handler: Failed to process message type 2 state 2.
[*11/05/2019 03:41:32.1193] Failed to handle capwap control message from controller - status 4
[*11/05/2019 03:41:32.1193] Failed to process unencrypted capwap packet from 192.168.31.10
[*11/05/2019 03:41:32.1193] Failed to send capwap message 0 to the state machine. Packet already freed.
[*11/05/2019 03:41:32.1193] wtpProcessPacketFromSocket returned 4
[*11/05/2019 03:41:32.1193] CAPWAP State: Discovery
[*11/05/2019 03:41:32.1193] Discovery Request sent to 192.168.31.10, discovery type STATIC_CONFIG(1)
[*11/05/2019 03:41:32.1193] Discovery Request sent to 192.168.31.10, discovery type STATIC_CONFIG(1)
AP7486.0B50.1820_2F#capwap ipggggggg[*11/05/2019 03:41:35.5883]

Re: AP not joining WLC

Sandeep Choudhary — Thu, 07 Nov 2019 06:00:16 GMT

i think you are running verly old software version on controller.

1852 AP need minimum SW version of 8.1.111.0 or higher to JOIN WLC.

Please paste the information:

sh version from AP

sh sysinfo from WLC

Regards

Dont forget to rate helpful posts

Re: AP not joining WLC

7919dvalle — Sun, 06 Sep 2020 21:34:26 GMT

1.- si el AP tiene precargado la versión 8.4.100.0 y al conectar al internet y direccionarlo a una wlc con cualquier otra versión se va a ver en consola lo siguiente:

Se revisa en la flash: a que paquete corresponde la versión 8.4.100.0 y se borra:

Show flash:

delete /force /recursive flash:/c3700-k9w8-mx.153-3.JE

Una vez borrado el paquete se hace reload para que arranque el ap con el banco de IOS de backup:

Generalmente se carga una versión 8.2.100.0 o si no, se carga cualquier versión de IOS borrando toda la flash: (en caso de que el ap arranque en modo rommon)

Hecho ese cambio se conecta al dhcp con salida a Internet y empieza la carga de firmware 8.5.161.0

Terminada la actualización queda actualizado el ap a la versión de la WLC:

Se continúa el proceso de comisionamiento en la WLC y quedan los aps operativos

Re: AP not joining WLC

stefannyflores7 — Sat, 29 May 2021 17:19:03 GMT

This is the output failure:

This AP model is supported by controller version newer than 7.0.0.0!
Dec 31 08:04:50 kernel: [*12/31/2019 08:04:50.5704]
Dec 31 08:04:50 kernel: [*12/31/2019 08:04:50.5704] Discovery response from MWAR ''running version 0.0.0.0 is rejected.
Dec 31 08:04:50 kernel: [*12/31/2019 08:04:50.5704] Failed to decode discovery response.
Dec 31 08:04:50 kernel: [*12/31/2019 08:04:50.5704] CAPWAP SM handler: Failed to process message type 2 state 2.
Dec 31 08:04:50 kernel: [*12/31/2019 08:04:50.5704] Failed to handle capwap control message from controller - status 4
Dec 31 08:04:50 kernel: [*12/31/2019 08:04:50.5704] Failed to process unencrypted capwap packet from 172.16.2.2
Dec 31 08:05:00 kernel: [*12/31/2019 08:05:00.0775] CAPWAP State: Discovery
Dec 31 08:05:00 kernel: [*12/31/2019 08:05:00.0775] Discovery Request sent to 172.16.2.2 with discovery type set to CAPWAP_DISCOVERY_TYPE_STATIC_CONFIG(1)
Dec 31 08:05:00 kernel: [*12/31/2019 08:05:00.0775] Discovery Response from 172.16.2.2

Dec 31 08:05:27 kernel: [*12/31/2019 08:05:27.4589] !!!!! {watchdogd} Process wcpd gone for 180s
Dec 31 08:05:28 kernel: [*12/31/2019 08:05:28.5886] Discovery Request sent to 172.16.2.2 with discovery type set to CAPWAP_DISCOVERY_TYPE_STATIC_CONFIG(1)
Dec 31 08:05:28 kernel: [*12/31/2019 08:05:28.5886] Discovery Response from 172.16.2.2
Dec 31 08:05:38 kernel: [*12/31/2019 08:05:38.1056] Discovery Request sent to 172.16.2.2 with discovery type set to CAPWAP_DISCOVERY_TYPE_STATIC_CONFIG(1)
Dec 31 08:05:38 kernel: [*12/31/2019 08:05:38.1056] Discovery Response from 172.16.2.2
Dec 31 08:05:47 kernel: [*12/31/2019 08:05:47.6026] Discovery Request sent to 172.16.2.2 with discovery type set to CAPWAP_DISCOVERY_TYPE_STATIC_CONFIG(1)
Dec 31 08:05:47 kernel: [*12/31/2019 08:05:47.6026] Discovery Response from 172.16.2.2
Dec 31 08:05:57 kernel: [*12/31/2019 08:05:57.1097] Discovery Request sent to 172.16.2.2 with discovery type set to CAPWAP_DISCOVERY_TYPE_STATIC_CONFIG(1)
Dec 31 08:05:57 kernel: [*12/31/2019 08:05:57.1097] Discovery Response from 172.16.2.2
Dec 31 08:06:06 kernel: [*12/31/2019 08:06:06.6167] Discovery Request sent to 172.16.2.2 with discovery type set to CAPWAP_DISCOVERY_TYPE_STATIC_CONFIG(1)
Dec 31 08:06:06 kernel: [*12/31/2019 08:06:06.6167] Discovery Response from 172.16.2.2
Dec 31 08:06:16 kernel: [*12/31/2019 08:06:16.1237] Discovery Request sent to 172.16.2.2 with discovery type set to CAPWAP_DISCOVERY_TYPE_STATIC_CONFIG(1)
Dec 31 08:06:16 kernel: [*12/31/2019 08:06:16.1237] Discovery Response from 172.16.2.2

LAst of

Dec 31 08:07:37 kernel: [*12/31/2019 08:07:37.5183] !!!!! {watchdogd} Process wcpd gone for 300s

the ap restart alone

**********

show version:

cisco AIR-AP1852I-N-K9 ARMv7 Processor rev 0 (v7l) with 966404/579244K bytes of memory.
Processor board ID KWC193900AZ
AP Running Image : 8.2.130.0
Primary Boot Image : 8.2.130.0
Backup Boot Image : 16.3.1.1
AP Image type : MOBILITY EXPRESS IMAGE
AP Configuration : MOBILITY EXPRESS CAPABLE
2 Gigabit Ethernet interfaces
1 802.11 Radios
Radio FW version : 5e60ea8b3f29048be1ff55e798dbabf5
NSS FW version : NSS.AK.1.0.c10-00017-E_custC-1.67978.

*************

(Cisco Controller) >show sysinfo

Manufacturer's Name.............................. Cisco Systems Inc.
Product Name..................................... Cisco Controller
Product Version.................................. 8.2.130.0

System Name...................................... APMASTER2
System Location..................................
System Contact...................................
System ObjectID.................................. 1.3.6.1.4.1.9.1.2250
IP Address....................................... 172.16.2.2
Last Reset....................................... 8: watchdog reset(wcpd)

System Up Time................................... 0 days 0 hrs 6 mins 46 secs
System Timezone Location......................... (GMT -6:00) Central Time (US and Canada)
System Stats Realtime Interval................... 5
System Stats Normal Interval..................... 180

Configured Country............................... MX - Mexico

State of 802.11b Network......................... Enabled
State of 802.11a Network......................... Enabled
Number of WLANs.................................. 2

--More-- or (q)uit
Number of Active Clients......................... 0

Burned-in MAC Address............................ 38:20:56:82:3F:C0
Maximum number of APs supported.................. 25
System Nas-Id....................................
WLC MIC Certificate Types........................ SHA1/SHA2

*******************

THANKS