As the title says, I'm currently busy with the migration of AP's to our new WLC, virtual 9800 wlc.
The model of the AP is AIR-CAP2702I-E-K9 and was previously registered to a different WLC.
On manually entering the controller ip command,:
*Jun 21 08:55:34.000: %CAPWAP-5-DTLSREQSEND: DTLS connection request sent peer_ip: x.x.x.x. peer_port: 5246
*Jun 21 08:55:34.263: %CAPWAP-5-DTLSREQSUCC: DTLS connection created sucessfully peer_ip: x.x.x.x. peer_port: 5246
*Jun 21 08:55:34.267: %CAPWAP-5-SENDJOIN: sending Join Request to x.x.x.x
*Jun 21 08:56:09.283: %LWAPP-3-CLIENTERRORLOG: Switching to Standalone mode
*Jun 21 08:56:09.303: %DTLS-5-SEND_ALERT: Send FATAL : Close notify Alert to x.x.x.x:5246
*Jun 21 09:01:31.391: %CAPWAP-3-STATIC_TO_DHCP_IP: Could not discover WLC using static IP. Forcing AP to use DHCP.
I have literally tried everything
correct time settings on both WLC and the AP
only relevant debug information i get from the WLC is the following:
Maximum retries for sending CAPWAP message reached. Close CAPWAP DTLS session
Tried this with 2 other different AP's of different models, on the same port, with the same IP, they both gave 0 problems and remained joined.
How did you manually reset the AP?
Did you hold the mode button while it was off then power it on or plug on to PoE port?
Do you have dhcp configured or did you statically assign an ip on the AP?
It seems that AP nvram is still not cleared.
Yes, I'm resetting it on a POE port with the mode button,but the button does not really want to work.
It does register it is pressed but then responds with mode button being disabled and recovery process breaking off.
In production it is by dhcp but for now it's setup with a static IP.
And yes nvram is not being cleared even though i gave it this command.
erase /all nvram: