The AP cannot go online on the AC and the progress stops at Join.

The AC and AP versions are the same but the AP cannot go online on the AC and the progress stops at Join.

[Analysis]

1.    View the log to check theCAPWAP tunnel status of the AP. The result shows the AP has communicated withthe AC and its status after the join status is:

DTLS Teardown；

*Jan1 00:01:10: %CAPWAP-6-STATE_CHANGEpeer - 1) [1.1.1.1] capwap state changed, from <DTLS Setup> to<Join>

*Jan1 00:01:10: %CAPWAP-6-STATE_CHANGEpeer - 1) [1.1.1.1] capwap state changed, from <Join> to <DTLSTearDown>

2. After confirming the link between the AC and the AP is normal, run the showap-config summary deny-ap command. The result shows that the fault reasonis "By conflict", which means the AP name is not unique in the systemand thus the AP cannot join the AC.

3. After you restore the default settings ofthe AP or change its name, the AP goes online successfully.

[Summary]

During the go-online process of the AP, theCAPWAP tunnel status is idle-->discover-->DTLSSetup-->Join-->config-->Data Check-->Run respectively. When the CAPWAPtunnel reaches the Run status, the AP has gone online successfully.

If the progress stops when the CAPWAP tunnelreaches the Join status, run the show ap-config summary deny-ap command to display the reason for access denying(the reason is not displayed when the AC version is 11.x and the AP version is10.x due to a large version span).

The following are common causes for that theprogress stops when the CAPWAP tunnel reaches the Join status:

(1) The AP name conflicts.

(2) The versions are inconsistent.

(3) The license is incorrect.

(4)  Link failure.

(5) The AC has security restrictions, forexample, bind-ap-mac.