AP is not joining the WLC

[kingofzamunda]

Hello,

I'm using WLC 2504 with one access point and and spectrum cable modem.  The AP and WLC are connected to a switch, the switch is connected to the spectrum cable which is used for DHCP. The AP is getting an IP but not joining the WLC.  I'm only using one VLAN which is the management .  The SSID box is checked but it is not broadcasted.  below is the error that im getting: I have created a trunk port from the switch to the WLC

May 11 16:02:22.000: %DTLS-5-SEND_ALERT: Send FATAL : Close notify Alert to 192.168.0.50:5246
*May 11 16:02:22.000: %DTLS-5-SEND_ALERT: Send FATAL : Close notify Alert to 192.168.0.50:5246

*May 11 16:09:47.000: %DTLS-5-SEND_ALERT: Send FATAL : Close notify Alert to 192.168.0.50:5246
*May 11 16:09:47.000: %DTLS-5-SEND_ALERT: Send FATAL : Close notify Alert to 192.168.0.50:5246
*May 11 16:10:52.000: %CAPWAP-5-DTLSREQSEND: DTLS connection request sent peer_ip: 192.168.0.50 peer_port: 5246
*May 11 16:10:52.239: %CAPWAP-5-DTLSREQSUCC: DTLS connection created sucessfully peer_ip: 192.168.0.50 peer_port: 5246
*May 11 16:10:52.239: %CAPWAP-5-SENDJOIN: sending Join Request to 192.168.0.50
*May 11 16:10:52.242: %DTLS-5-SEND_ALERT: Send FATAL : Close notify Alert to 192.168.0.50:5246

I have another message after i troubleshoot the packet:

*May 11 17:13:24.003: %CAPWAP-3-EVENTLOG: Could not discover any MWAR.
*May 11 17:13:24.003: %CAPWAP-3-EVENTLOG: Starting Discovery. Initializing discovery latency in discovery responses.
*May 11 17:13:24.003: %CAPWAP-3-EVENTLOG: CAPWAP State: Discovery.
*May 11 17:13:24.003: %CAPWAP-3-EVENTLOG: spamResolveStaticGateway - gateway found 192.168.0.1
*May 11 17:13:24.003: %CAPWAP-3-EVENTLOG: spamResolveStaticGateway - gateway found 192.168.0.1
*May 11 17:13:24.003: %CAPWAP-3-EVENTLOG: Discovery Request sent to 255.255.255.255 with discovery type set to 0
*May 11 17:13:24.003: %CAPWAP-3-EVENTLOG: Send broadcast discovery request
*May 11 17:13:24.003: %CAPWAP-3-EVENTLOG: Not sending discovery request to FF01::18C. Reason: Bridge mode AP
*May 11 17:13:24.522: %CAPWAP-3-EVENTLOG: CAPWAP state not up. Abort sending channel and power levels info. 192.168.0.50

*May 11 17:13:26.542: %CAPWAP-3-EVENTLOG: CAPWAP state not up. Abort sending channel and power levels info. 192.168.0.50

*May 11 17:13:26.548: %CAPWAP-3-EVENTLOG: CAPWAP state not up. Abort sending channel and power levels info. 192.168.0.50

*May 11 17:13:28.561: %CAPWAP-3-EVENTLOG: CAPWAP state not up. Abort sending channel and power levels info. 192.168.0.50

*May 11 17:13:28.567: %CAPWAP-3-EVENTLOG: CAPWAP state not up. Abort sending channel and power levels info. 192.168.0.50

*May 11 17:13:30.581: %CAPWAP-3-EVENTLOG: CAPWAP state not up. Abort sending channel and power levels info. 192.168.0.50

*May 11 17:13:30.587: %CAPWAP-3-EVENTLOG: CAPWAP state not up. Abort sending channel and power levels info. 192.168.0.50

*May 11 17:13:32.600: %CAPWAP-3-EVENTLOG: CAPWAP state not up. Abort sending channel and power levels info. 192.168.0.50

*May 11 17:13:32.607: %CAPWAP-3-EVENTLOG: CAPWAP state not up. Abort sending channel and power levels info. 192.168.0.50

[marce1000]

 - Which AP-model are you talking about - and or check compatibility notes from here :

               https://www.cisco.com/c/en/us/td/docs/wireless/compatibility/matrix/compatibility-matrix.html

  M.

[kingofzamunda]

I was able to get it to connect and login but the clients are not getting any IP

[Rafael E]

what AP model? 

is this a bridge AP? 

From logs:  Reason: Bridge mode AP

If this is a bridge AP you need to add its ethernet mac address to the AP policies WLC list. 

[kingofzamunda]

should I add it on <security>local policies and create a new one?

Also I noticed WLC is not syching with the my local router which is the NTP

[kingofzamunda]

actually this is solved. I fixed it. the problem was to change to mode from bridge to local and changed the ip of the dhcp. all is working

[7919dvalle]

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