AP's don't join a remote WLC

[Claudio Battan]

Another case of AP's not joing at the WLC ...

The WLC is remote, virtual, 8.3.150.0 (but not upgradable due to some old ruins still present)
All the other branches work fine, but from this one this can't
I just attach a couple of debugs, if someone more skilled than me can find out WHAT is wrong ...
I don't know where to beat my head anymore ...

Thanks for any suggestion that works

[Leo Laohoo]

---

@Claudio Battan wrote:

*Mar  1 00:01:37.251: AP has SHA2 MIC certificate - Using SHA2 MIC certificate for DTLS.
*Mar  2 16:47:08.000: %CAPWAP-5-DTLSREQSEND: DTLS connection request sent peer_ip: 192.168.99.15 peer_port: 5246

---

Look at the time and date of the logs. 

The time and date went from Mar 1 00:01 to Mar 2 16:47.  This means the AP can "see" the controller but the controller has the wrong time and date.  

[Claudio Battan]

Sorry Leo, but you don't think this is the problem:
> at the boot, the AP time starts at 0:00:00
> the WLC has the right time, synchronized NTP 
> if you look a little further in the LOG, you will see that the AP has synchronized with the WLC time:

*Mar 2 15:57:14.999: AP has SHA2 MIC certificate - Using SHA2 MIC certificate for DTLS.

[Leo Laohoo]

I have peered into the logs for the 1700 and the 1852 and both are showing the logs to have the wrong time-and-date. 

1700 AP is going to a controller with an IP address of "192.168.99.15".  I do not see the 1852 making any attempts to find a controller.

Post the complete output to the following WLC output: 

1. sh sysinfo
2. sh time

[marce1000]

     - Check for sufficient licenses with : show license summary

 M.

[Flavio Miranda]

The Access Point is trying to join  192.168.99.15 peer_port: 5246 but on the TLS logs we see "with Local 172.16.102.15:5246"

One Access Points does not start capwap join process or the logs collected was something else.