Having issues keeping 2602 AP's connected to a HA pair of 5508 Controllers

[roger.goult]

HI all … I Have a Wifi Network here that consists of 2 5508 controllers in a HA pair connecting to about 260 AP's .

Mainly 2602 and 3502 AP's.

There is a small group of AP's that I am having heaps of issues with .

They continually lose their connection to the AP Controller, But not the network.

The AP's retain the DHCP provided IP address ,and are pingable and I am able to telnet to them.

This is the sort of Error I'm seeing at the AP :

Oct 19 03:46:16.039: %LWAPP-3-CLIENTERRORLOG: Switching to Standalone mode
Oct 19 03:46:16.051: %DTLS-5-SEND_ALERT: Send FATAL : Close notify Alert to 192.168.248.10:5246
Oct 19 03:46:16.051: %EVT-5-NTC: CAPWAP state change 5
Oct 19 03:46:16.063: %EVT-5-NTC: Closing connection slot 0; last packet time 0/258046
Oct 19 03:46:16.063: %EVT-5-NTC: I0: shutdownNci
Oct 19 03:46:16.063: %EVT-5-NTC: Shut down SI slot=0, CAPWAP DOWN
Oct 19 03:46:16.063: %EVT-5-NTC: Closing connection slot 1; last packet time 2/257993
Oct 19 03:46:16.063: %EVT-5-NTC: I1: shutdownNci
Oct 19 03:46:16.063: %EVT-5-NTC: Shut down SI slot=1, CAPWAP DOWN
Oct 19 03:46:16.067: %EVT-5-NTC: Nothing opened - waiting for new sockets
Oct 19 03:46:26.000: %CAPWAP-5-DTLSREQSEND: DTLS connection request sent peer_ip: 192.168.248.10 peer_port: 5246
Oct 19 03:47:25.999: %DTLS-5-SEND_ALERT: Send FATAL : Close notify Alert to 192.168.248.10:5246
Oct 19 03:47:46.000: %CAPWAP-5-DTLSREQSEND: DTLS connection request sent peer_ip: 192.168.248.10 peer_port: 5246
Oct 19 03:48:45.999: %DTLS-5-SEND_ALERT: Send FATAL : Close notify Alert to 192.168.248.10:5246
Oct 19 03:48:46.000: %CAPWAP-5-DTLSREQSEND: DTLS connection request sent peer_ip: 192.168.248.10 peer_port: 5246
Oct 19 03:49:45.999: %DTLS-5-SEND_ALERT: Send FATAL : Close notify Alert to 192.168.248.10:5246
Oct 19 03:50:06.000: %CAPWAP-5-DTLSREQSEND: DTLS connection request sent peer_ip: 192.168.248.10 peer_port: 5246
Oct 19 03:51:05.999: %DTLS-5-SEND_ALERT: Send FATAL : Close notify Alert to 192.168.248.10:5246
Oct 19 03:51:06.000: %CAPWAP-5-DTLSREQSEND: DTLS connection request sent peer_ip: 192.168.248.10 peer_port: 5246
Oct 19 03:52:05.999: %DTLS-5-SEND_ALERT: Send FATAL : Close notify Alert to 192.168.248.10:5246
Oct 19 03:52:16.000: %CAPWAP-5-DTLSREQSEND: DTLS connection request sent peer_ip: 192.168.248.10 peer_port: 5246
Oct 19 03:53:15.999: %DTLS-5-SEND_ALERT: Send FATAL : Close notify Alert to 192.168.248.10:5246
Oct 19 03:53:26.000: %CAPWAP-5-DTLSREQSEND: DTLS connection request sent peer_ip: 192.168.248.10 peer_port: 5246
Oct 19 03:54:25.999: %DTLS-5-SEND_ALERT: Send FATAL : Close notify Alert to 192.168.248.10:5246
Oct 19 03:54:26.000: %CAPWAP-5-DTLSREQSEND: DTLS connection request sent peer_ip: 192.168.248.10 peer_port: 5246
Oct 19 03:55:25.999: %DTLS-5-SEND_ALERT: Send FATAL : Close notify Alert to 192.168.248.10:5246
Oct 19 03:56:36.000: %CAPWAP-5-DTLSREQSEND: DTLS connection request sent peer_ip: 192.168.248.10 peer_port: 5246
Oct 19 03:57:35.999: %DTLS-5-SEND_ALERT: Send FATAL : Close notify Alert to 192.168.248.10:5246
Oct 19 03:57:46.000: %CAPWAP-5-DTLSREQSEND: DTLS connection request sent peer_ip: 192.168.248.10 peer_port: 5246
*** End of evtlog ***

The Ap's seem to go through a cycle or two and then reconnect for a while then drop out again.

I can reboot them by disabling and re enabling  POE and they seem to come good for a bit, but eventually drop off again .

Any suggestions ?

Cheers

[Leo Laohoo]

Reboot the controllers -- both of them.

[roger.goult]

That has only just been done , as part of the setup for the HA Pair and a firmware upgrade, and the issue is only seemingly effecting this particular group of AP's.

Uptime on the controllers is 102 days. Issue has been ongoing for 12 months or more ….

[Leo Laohoo]

Had issues about DTLS being dropped from the controllers running 8.8.125.0.  This only happens on WLC running HA SSO and only seem to affect AP2700/3700.  Reboot of the controllers "fixes" the issue for about 32 days.  

[marce1000]

            - Try latest supported software version for the 5508 (+ap), check if  the problem then persists.

 M.