Diassociation of 2802I

[AK002]

Hi Team,

Can anyone help on the AP re association issue..

 AP model : 2802 8.5.161.0 WLC : 5520

System logging:
Jun  2 20:26:06 NCI: I0: Requesting MonBand [5700, 5700] bw=20MHz/0 ant=0xbc
Jun  2 20:26:06 NCI: I0: Monitoring (cf=5700, span=20), RadioUsage=3%
Jun  2 20:26:06 NCI: I0:     dwell=20000us, update=1000ms, resBW=78126
Jun  2 20:26:06 NCI: CLEANAIR: Slot 0 enabled
Jun  2 20:26:06 NCI: I1: openSensor(slot=1)
Jun  2 20:26:08 NCI: I1: SensorApp=1.15.4
Jun  2 20:26:08 NCI: I1: SensorHdw=1.2.3.0
Jun  2 20:26:08 NCI: I1: Hardware Radio Band = [4890, 5935] MHz, BW=150625
Jun  2 20:26:08 NCI: slot=1 mode=2 chanCnt=1 cw=1
Jun  2 20:26:08 NCI: chans: 60 0 0 0 0 0 0 0 0 0 0
Jun  2 20:26:08 NCI: I1: channel map channels: in=1 cloned=1
Jun  2 20:26:08 NCI: I1: Requesting MonBand [5300, 5300] bw=20MHz/0 ant=0xbc
Jun  2 20:26:08 NCI: I1: Monitoring (cf=5300, span=20), RadioUsage=3%
Jun  2 20:26:08 NCI: I1:     dwell=20000us, update=1000ms, resBW=78126
Jun  2 20:26:08 NCI: CLEANAIR: Slot 1 enabled
Jun  2 20:26:30 kernel: [*06/02/2020 20:26:30.5327] CAPWAP HW tunnel params changed, DELETING the existing
Jun  2 20:26:31 kernel: [*06/02/2020 20:26:31.5868] HW CAPWAP tunnel is ADDED
Jun  2 20:26:59 kernel: [*06/02/2020 20:26:59.0353] CAPWAP HW tunnel params changed, DELETING the existing
Jun  2 20:27:00 kernel: [*06/02/2020 20:27:00.0895] HW CAPWAP tunnel is ADDED
Jun  2 20:27:04 kernel: [*06/02/2020 20:27:04.7446] CAPWAP HW tunnel params changed, DELETING the existing
Jun  2 20:27:05 kernel: [*06/02/2020 20:27:05.7989] HW CAPWAP tunnel is ADDED
Jun  3 02:37:20 kernel: [*06/03/2020 02:37:20.3780] Re-Tx Count=1, Max Re-Tx Value=5, SendSeqNum=197, NumofPendingMsgs=1
Jun  3 02:37:20 kernel: [*06/03/2020 02:37:20.3780]
Jun  3 02:37:23 kernel: [*06/03/2020 02:37:23.2288] Re-Tx Count=2, Max Re-Tx Value=5, SendSeqNum=198, NumofPendingMsgs=2
Jun  3 02:37:23 kernel: [*06/03/2020 02:37:23.2288]
Jun  3 02:37:28 kernel: [*06/03/2020 02:37:28.7405] Re-Tx Count=3, Max Re-Tx Value=5, SendSeqNum=198, NumofPendingMsgs=1
Jun  3 02:37:28 kernel: [*06/03/2020 02:37:28.7405]
Jun  3 02:37:31 kernel: [*06/03/2020 02:37:31.5914] Re-Tx Count=4, Max Re-Tx Value=5, SendSeqNum=198, NumofPendingMsgs=1
Jun  3 02:37:31 kernel: [*06/03/2020 02:37:31.5914]
Jun  3 02:37:34 kernel: [*06/03/2020 02:37:34.4422] Re-Tx Count=5, Max Re-Tx Value=5, SendSeqNum=198, NumofPendingMsgs=1
Jun  3 02:37:34 kernel: [*06/03/2020 02:37:34.4422]
Jun  3 02:37:37 kernel: [*06/03/2020 02:37:37.3007] Re-Tx Count=6, Max Re-Tx Value=5, SendSeqNum=198, NumofPendingMsgs=1
Jun  3 02:37:37 kernel: [*06/03/2020 02:37:37.3007]
Jun  3 02:37:37 kernel: [*06/03/2020 02:37:37.3008] Max retransmission count exceeded, going back to DISCOVER mode.
Jun  3 02:37:37 kernel: [*06/03/2020 02:37:37.3011] Flexconnect Switching to Standalone Mode!
Jun  3 02:37:37 kernel: [*06/03/2020 02:37:37.3065]
Jun  3 02:37:37 kernel: [*06/03/2020 02:37:37.3065] CAPWAP State: DTLS Teardown
Jun  3 02:37:38 NCI: CLEANAIR: Slot 0 CAPWAP down
Jun  3 02:37:38 NCI: I0: shutdownNci
Jun  3 02:37:38 NCI: CLEANAIR: Slot 1 CAPWAP down
Jun  3 02:37:38 NCI: I1: shutdownNci
Jun  3 02:37:43 kernel: [*06/03/2020 02:37:43.1233] Discovery Response from 10.130.0.110
Jun  3 02:37:43 kernel: [*06/03/2020 02:37:43.1312] Discovery Response from 10.130.0.110
Jun  3 02:37:43 kernel: [*06/03/2020 02:37:43.1389] Discovery Response from 10.130.0.110
Jun  3 02:37:43 kernel: [*06/03/2020 02:37:43.0001]
Jun  3 02:37:43 kernel: [*06/03/2020 02:37:43.0001] CAPWAP State: DTLS Setup
Jun  3 02:37:43 kernel: [*06/03/2020 02:37:43.7111]
Jun  3 02:37:43 kernel: [*06/03/2020 02:37:43.7111] CAPWAP State: Join
Jun  3 02:37:43 kernel: [*06/03/2020 02:37:43.7126] Sending Join request to 10.130.0.110 through port 5256
Jun  3 02:37:48 kernel: [*06/03/2020 02:37:48.3554] Join Response from 10.130.0.110
Jun  3 02:37:48 kernel: [*06/03/2020 02:37:48.3558]
Jun  3 02:37:48 kernel: [*06/03/2020 02:37:48.3559] CAPWAP State: Image Data
Jun  3 02:37:48 kernel: [*06/03/2020 02:37:48.3926] do NO_UPGRADE, part2 is active part
Jun  3 02:37:48 kernel: [*06/03/2020 02:37:48.3964]
Jun  3 02:37:48 kernel: [*06/03/2020 02:37:48.3964] CAPWAP State: Configure
Jun  3 02:37:48 kernel: [*06/03/2020 02:37:48.3986] DOT11_CFG[0] Radio Mode is changed from FlexConnect to FlexConnect
Jun  3 02:37:48 kernel: [*06/03/2020 02:37:48.3991] DOT11_CFG[1] Radio Mode is changed from FlexConnect to FlexConnect
Jun  3 02:37:49 kernel: [*06/03/2020 02:37:49.4298]
Jun  3 02:37:49 kernel: [*06/03/2020 02:37:49.4298] CAPWAP State: Run
Jun  3 02:37:49 kernel: [*06/03/2020 02:37:49.5272] AP has joined controller WLC1
Jun  3 02:37:49 kernel: [*06/03/2020 02:37:49.5483] Flexconnect Switching to Connected Mode!
Jun  3 02:37:51 root: SYS-COND: Retrigger fair condition, 6 power
Jun  3 02:37:54 syslog: Password for user changed
Jun  3 02:37:54 kernel: [*06/03/2020 02:37:54.2452] Password for user changed
Jun  3 02:37:54 kernel: [*06/03/2020 02:37:54.5897] /usr/sbin/capwapd: opening /click/cli_h/apr_bypass/active failed!: No such file or directory
Jun  3 02:37:54 kernel: [*06/03/2020 02:37:54.7776] save_on_failure is set to 1
Jun  3 02:37:54 kernel: [*06/03/2020 02:37:54.7779] save_on_failure is set to 1
Jun  3 02:38:18 kernel: [*06/03/2020 02:38:18.9146] set cleanair [slot0][band0] enabled
Jun  3 02:38:18 NCI: I0: openSensor(slot=0)
Jun  3 02:38:18 kernel: [*06/03/2020 02:38:18.9210] set cleanair [slot0][band1] enabled
Jun  3 02:38:18 kernel: [*06/03/2020 02:38:18.9271] set cleanair [slot1][band1] enabled
Jun  3 02:38:19 NCI: I0: SensorApp=1.15.4
Jun  3 02:38:19 NCI: I0: SensorHdw=1.2.3.0
Jun  3 02:38:19 NCI: I0: Hardware Radio Band = [4890, 5935] MHz, BW=150625
Jun  3 02:38:19 NCI: I0: Hardware Radio Band = [2400, 2500] MHz, BW=150625
Jun  3 02:38:19 NCI: slot=0 mode=2 chanCnt=1 cw=1
Jun  3 02:38:19 NCI: chans: 140 0 0 0 0 0 0 0 0 0 0
Jun  3 02:38:19 NCI: I0: channel map channels: in=1 cloned=1
Jun  3 02:38:19 NCI: I0: Requesting MonBand [5700, 5700] bw=20MHz/0 ant=0xbc
Jun  3 02:38:20 NCI: I0: Monitoring (cf=5700, span=20), RadioUsage=3%
Jun  3 02:38:20 NCI: I0:     dwell=20000us, update=1000ms, resBW=78126
Jun  3 02:38:20 NCI: CLEANAIR: Slot 0 enabled
Jun  3 02:38:20 NCI: I1: openSensor(slot=1)
Jun  3 02:38:21 NCI: I1: SensorApp=1.15.4
Jun  3 02:38:21 NCI: I1: SensorHdw=1.2.3.0
Jun  3 02:38:21 NCI: I1: Hardware Radio Band = [4890, 5935] MHz, BW=150625
Jun  3 02:38:21 NCI: slot=1 mode=2 chanCnt=1 cw=1
Jun  3 02:38:21 NCI: chans: 60 0 0 0 0 0 0 0 0 0 0
Jun  3 02:38:21 NCI: I1: channel map channels: in=1 cloned=1
Jun  3 02:38:21 NCI: I1: Requesting MonBand [5300, 5300] bw=20MHz/0 ant=0xbc
Jun  3 02:38:21 NCI: I1: Monitoring (cf=5300, span=20), RadioUsage=3%
Jun  3 02:38:21 NCI: I1:     dwell=20000us, update=1000ms, resBW=78126
Jun  3 02:38:21 NCI: CLEANAIR: Slot 1 enabled
Jun  3 02:38:46 kernel: [*06/03/2020 02:38:46.5674] CAPWAP HW tunnel params changed, DELETING the existing
Jun  3 02:38:47 kernel: [*06/03/2020 02:38:47.6219] HW CAPWAP tunnel is ADDED
Jun  3 02:39:15 kernel: [*06/03/2020 02:39:15.0674] CAPWAP HW tunnel params changed, DELETING the existing
Jun  3 02:39:16 kernel: [*06/03/2020 02:39:16.1218] HW CAPWAP tunnel is ADDED
Jun  3 02:39:20 kernel: [*06/03/2020 02:39:20.7750] CAPWAP HW tunnel params changed, DELETING the existing
Jun  3 02:39:21 kernel: [*06/03/2020 02:39:21.8298] HW CAPWAP tunnel is ADDED
Jun  3 06:12:22 kernel: [*06/03/2020 06:12:22.2423] CAPWAP HW tunnel params changed, DELETING the existing
Jun  3 06:12:23 kernel: [*06/03/2020 06:12:23.2965] HW CAPWAP tunnel is ADDED
Jun  3 06:12:27 kernel: [*06/03/2020 06:12:27.9511] CAPWAP HW tunnel params changed, DELETING the existing
Jun  3 06:12:29 kernel: [*06/03/2020 06:12:29.0085] HW CAPWAP tunnel is ADDED
Jun  3 09:10:07 kernel: [*06/03/2020 09:10:07.2891] Re-Tx Count=1, Max Re-Tx Value=5, SendSeqNum=67, NumofPendingMsgs=1
Jun  3 09:10:07 kernel: [*06/03/2020 09:10:07.2891]
Jun  3 09:12:00 kernel: [*06/03/2020 09:12:00.3515] Re-Tx Count=1, Max Re-Tx Value=5, SendSeqNum=83, NumofPendingMsgs=2
Jun  3 09:12:00 kernel: [*06/03/2020 09:12:00.3515]
Jun  3 09:12:17 kernel: [*06/03/2020 09:12:17.6468] Re-Tx Count=1, Max Re-Tx Value=5, SendSeqNum=89, NumofPendingMsgs=3
Jun  3 09:12:17 kernel: [*06/03/2020 09:12:17.6468]
Jun  3 09:12:57 kernel: [*06/03/2020 09:12:57.1788] Re-Tx Count=1, Max Re-Tx Value=5, SendSeqNum=94, NumofPendingMsgs=1
Jun  3 09:12:57 kernel: [*06/03/2020 09:12:57.1788]
Jun  3 09:14:44 kernel: [*06/03/2020 09:14:44.5767] Re-Tx Count=1, Max Re-Tx Value=5, SendSeqNum=109, NumofPendingMsgs=3
Jun  3 09:14:44 kernel: [*06/03/2020 09:14:44.5767]
Jun  3 09:15:16 kernel: [*06/03/2020 09:15:16.8863] Re-Tx Count=1, Max Re-Tx Value=5, SendSeqNum=119, NumofPendingMsgs=3
Jun  3 09:15:16 kernel: [*06/03/2020 09:15:16.8863]
Jun  3 09:16:03 kernel: [*06/03/2020 09:16:03.6404] Re-Tx Count=1, Max Re-Tx Value=5, SendSeqNum=125, NumofPendingMsgs=1
Jun  3 09:16:03 kernel: [*06/03/2020 09:16:03.6405]
Jun  3 09:17:04 kernel: [*06/03/2020 09:17:04.3424] Re-Tx Count=1, Max Re-Tx Value=5, SendSeqNum=131, NumofPendingMsgs=1
Jun  3 09:17:04 kernel: [*06/03/2020 09:17:04.3425]
Jun  3 09:17:07 kernel: [*06/03/2020 09:17:07.1933] Re-Tx Count=2, Max Re-Tx Value=5, SendSeqNum=133, NumofPendingMsgs=3
Jun  3 09:17:07 kernel: [*06/03/2020 09:17:07.1933]
Jun  3 09:18:00 kernel: [*06/03/2020 09:18:00.4094] Re-Tx Count=1, Max Re-Tx Value=5, SendSeqNum=143, NumofPendingMsgs=2
Jun  3 09:18:00 kernel: [*06/03/2020 09:18:00.4094]
Jun  3 09:21:20 kernel: [*06/03/2020 09:21:20.8104] Re-Tx Count=1, Max Re-Tx Value=5, SendSeqNum=183, NumofPendingMsgs=3
Jun  3 09:21:20 kernel: [*06/03/2020 09:21:20.8104]
Jun  3 09:23:06 kernel: [*06/03/2020 09:23:06.7814] Re-Tx Count=1, Max Re-Tx Value=5, SendSeqNum=193, NumofPendingMsgs=1
Jun  3 09:23:06 kernel: [*06/03/2020 09:23:06.7814]
Jun  3 09:23:17 kernel: [*06/03/2020 09:23:17.8048] Re-Tx Count=1, Max Re-Tx Value=5, SendSeqNum=197, NumofPendingMsgs=2
Jun  3 09:23:17 kernel: [*06/03/2020 09:23:17.8048]
Jun  3 09:23:20 kernel: [*06/03/2020 09:23:20.6556] Re-Tx Count=2, Max Re-Tx Value=5, SendSeqNum=197, NumofPendingMsgs=2
Jun  3 09:23:20 kernel: [*06/03/2020 09:23:20.6556]
Jun  3 09:23:23 kernel: [*06/03/2020 09:23:23.5065] Re-Tx Count=1, Max Re-Tx Value=5, SendSeqNum=197, NumofPendingMsgs=1
Jun  3 09:23:23 kernel: [*06/03/2020 09:23:23.5065]
Jun  3 09:23:52 kernel: [*06/03/2020 09:23:52.5853] Re-Tx Count=1, Max Re-Tx Value=5, SendSeqNum=200, NumofPendingMsgs=2
Jun  3 09:23:52 kernel: [*06/03/2020 09:23:52.5853]
Jun  3 09:24:02 kernel: [*06/03/2020 09:24:02.0881] Re-Tx Count=1, Max Re-Tx Value=5, SendSeqNum=203, NumofPendingMsgs=1
Jun  3 09:24:02 kernel: [*06/03/2020 09:24:02.0881]
Jun  3 09:25:43 kernel: [*06/03/2020 09:25:43.0085] Re-Tx Count=1, Max Re-Tx Value=5, SendSeqNum=217, NumofPendingMsgs=1
Jun  3 09:25:43 kernel: [*06/03/2020 09:25:43.0085]
Jun  3 09:26:08 kernel: [*06/03/2020 09:26:08.8564] Re-Tx Count=1, Max Re-Tx Value=5, SendSeqNum=224, NumofPendingMsgs=4
Jun  3 09:26:08 kernel: [*06/03/2020 09:26:08.8564]
Jun  3 09:27:00 kernel: [*06/03/2020 09:27:00.6002] Re-Tx Count=1, Max Re-Tx Value=5, SendSeqNum=231, NumofPendingMsgs=2
Jun  3 09:27:00 kernel: [*06/03/2020 09:27:00.6002]
Jun  3 09:27:50 kernel: [*06/03/2020 09:27:50.5854] Re-Tx Count=1, Max Re-Tx Value=5, SendSeqNum=242, NumofPendingMsgs=1
Jun  3 09:27:50 kernel: [*06/03/2020 09:27:50.5854]
Jun  3 09:29:06 kernel: [*06/03/2020 09:29:06.7202] Re-Tx Count=1, Max Re-Tx Value=5, SendSeqNum=253, NumofPendingMsgs=2
Jun  3 09:29:06 kernel: [*06/03/2020 09:29:06.7202]
Jun  3 09:30:12 kernel: [*06/03/2020 09:30:12.6419] Re-Tx Count=1, Max Re-Tx Value=5, SendSeqNum=10, NumofPendingMsgs=3
Jun  3 09:30:12 kernel: [*06/03/2020 09:30:12.6419]
Jun  3 09:31:09 kernel: [*06/03/2020 09:31:09.6590] Re-Tx Count=1, Max Re-Tx Value=5, SendSeqNum=18, NumofPendingMsgs=3
Jun  3 09:31:09 kernel: [*06/03/2020 09:31:09.6590]
Jun  3 09:36:46 kernel: [*06/03/2020 09:36:46.5699] CAPWAP HW tunnel params changed, DELETING the existing
Jun  3 09:36:47 kernel: [*06/03/2020 09:36:47.6246] HW CAPWAP tunnel is ADDED
Jun  3 11:56:58 kernel: [*06/03/2020 11:56:58.3446] hostapd:FT: invalid assoc req. (reason 1) from 6c:4d:73:ae:eb:d0
Jun  3 12:38:22 kernel: [*06/03/2020 12:38:22.3753] CAPWAP HW tunnel params changed, DELETING the existing
Jun  3 12:38:23 kernel: [*06/03/2020 12:38:23.4304] HW CAPWAP tunnel is ADDED
Jun  3 13:58:35 syslog: Password for user changed
Jun  3 13:58:35 kernel: [*06/03/2020 13:58:35.5019] Password for user changed
Jun  3 13:59:36 FIPS[32408]: *** shell: FIPS Mode = disabled ***
Jun  3 14:09:13 kernel: [*06/03/2020 14:09:13.7551]
Jun  3 14:09:13 kernel: [*06/03/2020 14:09:13.7551] Total STA List Count 1
Jun  3 14:09:13 kernel: [*06/03/2020 14:09:13.7551] | NO|              MAC|STATE|
Jun  3 14:09:13 kernel: [*06/03/2020 14:09:13.7551] -----------------------------
Jun  3 14:09:13 kernel: [*06/03/2020 14:09:13.7551] |  1|6c:4d:73:ae:eb:d0|    8|
Jun  3 14:09:13 kernel: [*06/03/2020 14:09:13.7563]
Jun  3 14:09:13 kernel: [*06/03/2020 14:09:13.7563] Total STA List Count 3
Jun  3 14:09:13 kernel: [*06/03/2020 14:09:13.7563] | NO|              MAC|STATE|
Jun  3 14:09:13 kernel: [*06/03/2020 14:09:13.7563] -----------------------------
Jun  3 14:09:13 kernel: [*06/03/2020 14:09:13.7563] |  1|38:53:9c:c4:b8:fd|    8|
Jun  3 14:09:13 kernel: [*06/03/2020 14:09:13.7563] |  2|40:83:1d: 2:7a:10|    8|

Regards,

Arun

[AK002]

Hi,

Please find below Ap summary details..

(Cisco Controller) >show ap join stats detailed 50:2f:a8:de:xx:xx

Sync phase statistics
- Time at sync request received............................ May 29 10:57:17.754
- Time at sync completed................................... May 29 10:57:17.755

Discovery phase statistics
- Discovery requests received.............................. 24
- Successful discovery responses sent...................... 24
- Unsuccessful discovery request processing................ 0
- Reason for last unsuccessful discovery attempt........... Not applicable
- Time at last successful discovery attempt................ Jun 08 13:06:49.598
- Time at last unsuccessful discovery attempt.............. Not applicable

Join phase statistics
- Join requests received................................... 8
- Successful join responses sent........................... 8
- Unsuccessful join request processing..................... 8
- Reason for last unsuccessful join attempt................ RADIUS authorization is pending for the AP
- Time at last successful join attempt..................... Jun 08 13:07:04.312
- Time at last unsuccessful join attempt................... Jun 08 13:07:04.306

Configuration phase statistics

--More-- or (q)uit
- Configuration requests received.......................... 40
- Successful configuration responses sent.................. 16
- Unsuccessful configuration request processing............ 0
- Reason for last unsuccessful configuration attempt....... Not applicable
- Time at last successful configuration attempt............ Jun 08 13:07:04.926
- Time at last unsuccessful configuration attempt.......... Not applicable

Last AP message decryption failure details
- Reason for last message decryption failure............... Not applicable

Last AP disconnect details
- Reason for last AP connection failure.................... Number of message retransmission to the AP has reached maximum
- Last AP disconnect reason................................ Unknown failure reason

Last join error summary
- Type of error that occurred last......................... Lwapp join request rejected
- Reason for error that occurred last...................... RADIUS authorization is pending for the AP
- Time at which the last join error occurred............... Jun 08 13:07:04.306

AP disconnect details
- Reason for last AP connection failure.................... Number of message retransmission to the AP has reached maximum
                                                                                                                           Ethernet Mac : 50:2f:a8:de:xx.xx  Ip Address : 10.x.x.x

yesterday we could see 10 Ap's rejoined.

Software Version 8.5.161.0
Emergency Image Version 
8.2.166.0
System Name WLC01
Up Time 14 days, 19 hours, 26 minutes
System Time 
Mon Jun  8 13:57:22 2020
Redundancy Mode 
SSO

Regards,

Ak

[Leo Laohoo]

---

@AK002 wrote:

yesterday we could see 10 Ap's rejoined.

---

Pick two of those APs that have finally joined and post the complete output to the following command: 

sh ap eventlog <AP NAME>

NOTE:  The output from each AP will be long.  Put the output in a text file and attach it.

[AK002]

Attached the event log for the AP.

[Leo Laohoo]

May 28 12:45:40 kernel: [*05/28/2020 12:45:40.3891] AP has joined controller WLC1
May 28 21:34:55 kernel: [*05/28/2020 21:34:55.6266] Re-Tx Count=1, Max Re-Tx Value=5, SendSeqNum=108, NumofPendingMsgs=3

May 29 02:08:29 kernel: [*05/29/2020 02:08:29.3653] AP has joined controller WLC1
May 29 09:03:29 kernel: [*05/29/2020 09:03:29.1533] Re-Tx Count=1, Max Re-Tx Value=5, SendSeqNum=53, NumofPendingMsgs=1

May 29 09:03:56 kernel: [*05/29/2020 09:03:56.3805] AP has joined controller WLC1
May 29 09:14:08 kernel: [*05/29/2020 09:14:08.6146] Re-Tx Count=1, Max Re-Tx Value=5, SendSeqNum=104, NumofPendingMsgs=1

May 29 09:14:45 kernel: [*05/29/2020 09:14:45.3643] AP has joined controller WLC1
May 29 10:22:00 kernel: [*05/29/2020 10:22:00.7927] Re-Tx Count=1, Max Re-Tx Value=5, SendSeqNum=167, NumofPendingMsgs=4

May 29 10:22:29 kernel: [*05/29/2020 10:22:29.3770] AP has joined controller WLC1
Jun  2 17:14:59 kernel: [*06/02/2020 17:14:59.3781] Re-Tx Count=1, Max Re-Tx Value=5, SendSeqNum=51, NumofPendingMsgs=1

Jun  8 12:00:31 kernel: [*06/08/2020 12:00:31.3826] AP has joined controller WLC1
Jun  9 01:39:47 kernel: [*06/09/2020 01:39:47.9363] Re-Tx Count=1, Max Re-Tx Value=5, SendSeqNum=134, NumofPendingMsgs=6

Jun  9 01:40:16 kernel: [*06/09/2020 01:40:16.3727] AP has joined controller WLC1
Jun  9 04:32:33 kernel: [*06/09/2020 04:32:33.3137] Re-Tx Count=1, Max Re-Tx Value=5, SendSeqNum=191, NumofPendingMsgs=3

Jun  9 07:03:36 kernel: [*06/09/2020 07:03:36.3796] AP has joined controller WLC1
Jun  9 08:41:52 kernel: [*06/09/2020 08:41:52.7437] Re-Tx Count=1, Max Re-Tx Value=5, SendSeqNum=221, NumofPendingMsgs=2

Jun  9 08:42:29 kernel: [*06/09/2020 08:42:29.3778] AP has joined controller WLC1

Have a look above.  I am seeing a pattern of a WAN congestion of some sort.  

The bit that says "AP has joined controller WLC1" is self-explanatory.  The line after that means that the AP is observing packets being dropped.  If the packets are successively dropped 6 times (out of 6) then the Flexconnect link "drops" and the AP starts searching for a WLC.  

Look at the timeline: 

1. "May 28 21:34:55" to "May 29 02:08:29", the AP is "lost".  Is there any backups happening during this time? 
2. "May 29 10:22:29" to "Jun 2 17:14:59" is the longest time the AP has joined the WLC.  May 29 is also a Friday.  Is 01 June 2020 a public holiday?
3. "Jun 9 04:32:33" to "Jun 9 07:03:36".  Same as #1.  Potentially a backup happening?

If the site is a remote site, kindly describe what the WAN link is like.  Is it DSL?  Dark fibre?  MPLS?  Radio?  Satellite?

[AK002]

Thanks Leo, let me come back with findings..

[AK002]

Hi Leo,

The WLC is based in DC and spoke sites are connected to DC via BT fibre link. There are no time correlation between the AP re association and Backup running. Also done some testing in the link for the WLC and the AP vlan don't see any drops.

Regards,AK

[Leo Laohoo]

Describe the Layer 3 setup.
If this is a BT fibre what is the WAN speed? What router is used for both ends?

[AK002]

Hi Leo,

DC and Spoke sites are connected with ISR router for L3 connectivity and each having 1gbps speed.

[Leo Laohoo]

Are you able to run a 48-hour link utilization on the WAN link?

[cae_technology]

Hi Leo, I have attached latest debug file for reference.

[AK002 · Accepted solution]

Hi Leo,

Issue resolved after upgrade to 8.7 version. Now the AP disassociation significantly reduced.

Thanks & Regards,Ak

[Rich R]

Presume you're aware that 8.7 code is end of life?
https://www.cisco.com/c/en/us/products/collateral/wireless/8500-series-wireless-controllers/bulletin-c25-742354.html
That means that code is vulnerable to any security vulnerabilities announced since the last release and bugs in that code will not get fixed. Using that code is *not* recommended.
https://www.cisco.com/c/en/us/support/docs/wireless/wireless-lan-controller-software/200046-tac-recommended-aireos.html#anc7

[AK002]

Yes Mate, We will upgrade to 8.8 or 8.10 Thanks for the information and help.  

[alfoorti]

 Hello,

Can you share a #show capwap client rcb? want to see the PMTU For CAPWAP, also it would be great to make a ping with load from the switch te APs are connected to the WLC #ping X.X.X.X size 1500 repeat 100