07-18-2013 06:23 AM - edited 07-04-2021 12:27 AM
Hi all,
we have a lot of problem in joining AP 1600e lightw to a vWLC.
Following the details:
- vWLC: 7.4.100 (with SSC disabled)
- AP: ap1g2-rcvk9w8-tar.152-2.JB
We followed these steps:
- AP directly to vWLC: results: DTLS Error
"*spamApTask3: Jul 18 13:16:26.389: #DTLS-3-HANDSHAKE_FAILURE: openssl_dtls.c:681 Failed to complete DTLS handshake with peer 10.143.174.200"
- AP to a 7.4 5508 WLC and then to vWLC: results as per previous point
Any clue?
Thanks in advance
Luciano
07-18-2013 08:13 AM
Hi Luciano,
Connect to the AP1602 via console cable and issue these commands:
#test capwap erase
#test capwap restart
Turn off and turn on the AP. It should successfully join your vWLC now.
07-18-2013 09:07 AM
Ciao,
sorry but I don't have those commands on the AP (we are via console cable):
AP0006.f6d6.05fc#test capwap ?
am CAPWAP KAM-AP test commands
controller Configuring AP's controller
dtls dtls enable/disable
ids LWAPP IDS test commands
message Send CAPWAP message to AC
pppoe Change AP sub-mode to PPPoE
rm CAPWAP RM test commands
Tnx!
Luciano
07-18-2013 09:53 AM
OK,
they are hidden command.
After that we see that this AP is going to reach the 5508 WLC (which is in another net) and not the local vWLC (10.143.174.196) ... it is still try the 5508 WLC even after a capwap ap controlle ip command and a reload ...
07-18-2013 10:18 AM
After:
#test capwap erase
#test capwap restart
You turned off AP, then turned it on, and it still tries to reach 5508? Can you ping your vWLC from AP? Can vWLC ping AP?
07-18-2013 10:50 AM
After both commands I restard the AP by shutting down the poe switch port. And yes I can ping each others. The strange thing is that when I reload tha AP it goes directly to the 5508 :(
Sent from Cisco Technical Support Android App