Hi everyone,
I have a couple of 3702 AP's which have started rebooting a few days ago and are not joining the WLC (8510 running 8.0.150.0). They were fine before.
MAX number AP supported is 6000, and 3402 are currently joined.
In the few seconds they stay up, I can SSH them and the last logs I see before they reload are:
*Jan 9 05:21:08.000: %CAPWAP-5-DTLSREQSEND: DTLS connection request sent peer_ip: 10.x.x.x peer_port: 5246
*Jan 9 05:21:08.215: %CAPWAP-5-DTLSREQSUCC: DTLS connection created sucessfully peer_ip: 10.x.x.x peer_port: 5246
*Jan 9 05:21:08.215: %CAPWAP-5-SENDJOIN: sending Join Request to 10.x.x.x
AP's and WLC are not in the same VLAN but routing is ok, no FW between them.
As stated above, the other 3402 AP's are fine and can re-join the WLC after a reboot or a port bounce.
I can get some join info from the WLC for one of these AP's, but not for the other.
(Cisco Controller) >show ap join stats detailed 64:12:25:4b:xx:xx
Sync phase statistics
- Time at sync request received............................ Not applicable
- Time at sync completed................................... Not applicable
Discovery phase statistics
- Discovery requests received.............................. 100
- Successful discovery responses sent...................... 0
- Unsuccessful discovery request processing................ 100
- Reason for last unsuccessful discovery attempt........... Missing AP Manager interface
- Time at last successful discovery attempt................ Not applicable
- Time at last unsuccessful discovery attempt.............. Jan 09 15:54:37.931
Join phase statistics
- Join requests received................................... 0
- Successful join responses sent........................... 0
- Unsuccessful join request processing..................... 0
- Reason for last unsuccessful join attempt................ Not applicable
- Time at last successful join attempt..................... Not applicable
- Time at last unsuccessful join attempt................... Not applicable
Configuration phase statistics
- Configuration requests received.......................... 0
- Successful configuration responses sent.................. 0
- Unsuccessful configuration request processing............ 0
- Reason for last unsuccessful configuration attempt....... Not applicable
- Time at last successful configuration attempt............ Not applicable
- Time at last unsuccessful configuration attempt.......... Not applicable
Last AP message decryption failure details
- Reason for last message decryption failure............... Not applicable
Last AP disconnect details
- Reason for last AP connection failure.................... Not applicable
- Last AP disconnect reason................................ Not applicable
Last join error summary
- Type of error that occurred last......................... Lwapp discovery request rejected
- Reason for error that occurred last...................... Missing AP Manager interface
- Time at which the last join error occurred............... Jan 09 15:54:37.931
AP disconnect details
- Reason for last AP connection failure.................... Not applicable
Ethernet Mac : 00:00:00:00:00:00 Ip Address : 0.0.0.0
I searched for "Missing AP Manager interface" around but I couldn't find anything helpful.
The only thing I noticed is that both AP's come up with a different software, 15.3(3)JA10 and recovery 15.2(4)JB1) while others run 15.3(3)JA11.
AP running 15.3(3)JA10 is the one for which I can collect the above join info.
Do you have any idea on why they are not joining or booting the right image?
Is there a way to force booting a specific image?
These AP's are remote and I'd avoid any risky procedure unless strictly necessary.
THANKS!
fed
