求助，AP2802注册不到控制器3504？

[han120403]

3504控制器版本8.5.131.0，AP2802-H版本ap3g3-k9w8-tar.153-3.JF7.tar（兼容列表匹配的版本），时间为当前时间，国家码cn。注册不到控制器
AP show version版本：
AP Running Image : 8.5.131.0
Primary Boot Image : 8.5.131.0
Backup Boot Image : 8.3.143.0
2 Gigabit Ethernet interfaces
2 802.11 Radios
Radio Driver version : 9.0.5.5-W8964
Radio FW version : 9.1.8.1
NSS FW version : 2.4.24
debug控制器端报错如下：
Cisco Controller) >debug capwap events enable
(Cisco Controller) >*spamApTask6: Oct 12 10:05:13.513: f4:db:e6:95:26:d2 acDtlsPlumbControlPlaneKeys: lrad:192.168.62.236(5256) mwar:192.168.62.200(5246)
*spamApTask6: Oct 12 10:05:13.514: f4:db:e6:95:26:d2 Allocated index from main list, Index: 33
*spamApTask6: Oct 12 10:05:13.514: f4:db:e6:95:26:d2 Reserved LCB index for 192.168.62.236:33
*spamApTask6: Oct 12 10:05:13.514: f4:db:e6:95:26:d2 Using CipherSuite AES128-SHA
*spamApTask6: Oct 12 10:05:13.514: f4:db:e6:95:26:d2 DTLS keys for Control Plane are plumbed successfully for AP 192.168.62.236. Index 34
*spamApTask6: Oct 12 10:05:13.514: f4:db:e6:95:26:d2 DTLS Session established server (192.168.62.200:5246), client (192.168.62.236:5256)
*spamApTask6: Oct 12 10:05:13.514: f4:db:e6:95:26:d2 Starting wait join timer for AP: 192.168.62.236:5256
*spamApTask6: Oct 12 10:05:13.528: f4:db:e6:95:e6:00 Join Request from 192.168.62.236:5256
*spamApTask6: Oct 12 10:05:13.528: f4:db:e6:95:e6:00 using already alloced index 33
*spamApTask6: Oct 12 10:05:13.528: f4:db:e6:95:e6:00 Unable to get Ap mode in Join request
*spamApTask6: Oct 12 10:05:13.528: f4:db:e6:95:e6:00 Allocate database entry for AP 192.168.62.236:5256, already allocated index 33
*spamApTask6: Oct 12 10:05:13.528: f4:db:e6:95:e6:00 AP Allocate request at index 21
*spamApTask6: Oct 12 10:05:13.528: f4:db:e6:95:e6:00 Failed to allocate database entry for AP 192.168.62.236:5256
*spamApTask6: Oct 12 10:05:13.528: f4:db:e6:95:e6:00 Failed to add database entry for 192.168.62.236:5256
*spamApTask6: Oct 12 10:05:13.528: f4:db:e6:95:e6:00 Join Request failed!
*spamApTask6: Oct 12 10:05:13.528: f4:db:e6:95:e6:00 State machine handler: Failed to process msg type = 3 state = 0 from 192.168.62.236:5256
*spamApTask6: Oct 12 10:05:13.528: f4:db:e6:95:26:d2 Failed to parse CAPWAP packet from 192.168.62.236:5256
*osapiBsnTimer: Oct 12 10:05:16.955: Same gateway prevails
*spamApTask6: Oct 12 10:05:18.195: f4:db:e6:95:e6:00 Join Request from 192.168.62.236:5256
*spamApTask6: Oct 12 10:05:18.195: f4:db:e6:95:e6:00 using already alloced index 33
*spamApTask6: Oct 12 10:05:18.195: f4:db:e6:95:e6:00 Unable to get Ap mode in Join request
*spamApTask6: Oct 12 10:05:18.195: f4:db:e6:95:e6:00 Allocate database entry for AP 192.168.62.236:5256, already allocated index 33
*spamApTask6: Oct 12 10:05:18.195: f4:db:e6:95:e6:00 AP Allocate request at index 21
*spamApTask6: Oct 12 10:05:18.195: f4:db:e6:95:e6:00 Failed to allocate database entry for AP 192.168.62.236:5256
*spamApTask6: Oct 12 10:05:18.195: f4:db:e6:95:e6:00 Failed to add database entry for 192.168.62.236:5256
*spamApTask6: Oct 12 10:05:18.195: f4:db:e6:95:e6:00 Join Request failed!
*spamApTask6: Oct 12 10:05:18.195: f4:db:e6:95:e6:00 State machine handler: Failed to process msg type = 3 state = 0 from 192.168.62.236:5256
*spamApTask6: Oct 12 10:05:18.195: f4:db:e6:95:26:d2 Failed to parse CAPWAP packet from 192.168.62.236:5256

[HaifengLi]

我觉得你的license可能有问题

[Rockyw]

楼主可以参考一下下面的文档
Troubleshoot a Lightweight Access Point Not Joining a Wireless LAN Controller
https://www.cisco.com/c/en/us/support/docs/wireless/5500-series-wireless-controllers/119286-lap-notjoin-wlc-tshoot.html
LAP Does Not Join the Controller, Why?
Check the Basics First
Can the AP and the WLC communicate?
Make sure the AP is getting an address from DHCP (check the DHCP server leases for the AP's MAC address).
Try pinging the AP from the controller.
Check if the STP configuration on the switch is done right so that packets to the VLANs are not blocked.
If pings are successful, ensure the AP has at least one method by which to discovery at least a single WLC Console or telnet/ssh into the controller to run debugs.
Each time the AP reboots, it initiates the WLC discovery sequence and tries to locate the AP. Reboot the AP and check if it joins the WLC.
"AP fails to join controller" - LAP fails to join Wireless LAN controller (WLC)
https://community.cisco.com/t5/wireless-mobility-documents/quot-ap-fails-to-join-controller-quot-lap-fails-to-join-wireless/ta-p/3129919
Re: 2602i does not join 1852i / mobility express
https://community.cisco.com/t5/wireless-and-mobility/2602i-does-not-join-1852i-mobility-express/m-p/3723418#M103823

[Rps-Cheers]

这个问题请问解决了麽

[mis0000016]

看了日志，有一个AP mode模式可能有问题，你看一下AP的mode模式。一般为local model。