topic Re: 2800 AP diassociating to WLC oftenly after upgrade. in Wireless

2800 AP diassociating to WLC oftenly after upgrade.

AK002 — Mon, 05 Jul 2021 16:00:44 GMT

Hi,

Can Someone help me on the Issue in the 2800 Access points which is integrated with 5520 controller.

All AP's in the WLC randomly re-joining with the controller and giving the below error in the AP logs. Below logs are repeating many times in a day and getting alarm for re-joining. Issue in both Flex and local mode AP's.

WLC version : 8.5.131.0

Aug 21 11:06:43 kernel: [*08/21/2018 11:06:43.8012] Warning, unencrypted data keepalive failed
Aug 21 11:06:43 kernel: [*08/21/2018 11:06:43.8013] Failed to receive data keepalive
Aug 21 11:06:43 kernel: [*08/21/2018 11:06:43.8013]
Aug 21 11:06:43 kernel: [*08/21/2018 11:06:43.8013] Lost connection to the controller, going to restart CAPWAP...
Aug 21 11:06:43 kernel: [*08/21/2018 11:06:43.8013]
Aug 21 11:06:43 kernel: [*08/21/2018 11:06:43.8013] Restarting CAPWAP State Machine.
Aug 21 11:06:43 kernel: [*08/21/2018 11:06:43.9069]
Aug 21 11:06:43 kernel: [*08/21/2018 11:06:43.9069] CAPWAP State: DTLS Teardown
Aug 21 11:06:44 NCI: CLEANAIR: Slot 0 CAPWAP down
Aug 21 11:06:44 NCI: I0: shutdownNci
Aug 21 11:06:44 NCI: CLEANAIR: Slot 1 CAPWAP down
Aug 21 11:06:44 NCI: I1: shutdownNci
Aug 21 11:06:44 kernel: [*08/21/2018 11:06:44.9164] Dropping dtls packet since session is not established. Peer 10.130.208.101-
5246, Local 10.130.20.71-5272, conn (nil)
Aug 21 11:06:44 kernel: [*08/21/2018 11:06:44.9165] Dropping dtls packet since session is not established. Peer 10.1.1.1.-
5246, Local 10.130.20.71-5272, conn (nil)
Aug 21 11:06:49 kernel: [*08/21/2018 11:06:49.6079]
Aug 21 11:06:49 kernel: [*08/21/2018 11:06:49.6079] CAPWAP State: Discovery
Aug 21 11:06:49 kernel: [*08/21/2018 11:06:49.6103] Discovery Request sent to 10.1.1.1, discovery type STATIC_CONFIG(1)
Aug 21 11:06:49 kernel: [*08/21/2018 11:06:49.6105] IP DNS query for CISCO-CAPWAP-CONTROLLER
Aug 21 11:06:49 kernel: [*08/21/2018 11:06:49.6128] DNS resolved CISCO-CAPWAP-CONTROLLER
Aug 21 11:06:49 kernel: [*08/21/2018 11:06:49.6128] DNS discover IP addr: 10.1..1.1
Aug 21 11:06:49 kernel: [*08/21/2018 11:06:49.6157] Discovery Request sent to 10.1.1.1, discovery type STATIC_CONFIG(1)
Aug 21 11:06:49 kernel: [*08/21/2018 11:06:49.6168] Discovery Request sent to 255.255.255.255, discovery type UNKNOWN(0)
Aug 21 11:06:49 kernel: [*08/21/2018 11:06:49.6293] Discovery Response from 10.1.1.1
Aug 21 11:06:49 kernel: [*08/21/2018 11:06:49.6377] Discovery Response from 10.1.1.1
Aug 21 11:06:59 kernel: [*08/21/2018 11:06:59.0000]
Aug 21 11:06:59 kernel: [*08/21/2018 11:06:59.0000] CAPWAP State: DTLS Setup
Aug 21 11:06:59 kernel: [*08/21/2018 11:06:59.7361]
Aug 21 11:06:59 kernel: [*08/21/2018 11:06:59.7361] CAPWAP State: Join
Aug 21 11:06:59 kernel: [*08/21/2018 11:06:59.7390] Sending Join request to 10.1.1.1 through port 5272
Aug 21 11:06:59 kernel: [*08/21/2018 11:06:59.7611] Join Response from 10.1.1.1
Aug 21 11:06:59 kernel: [*08/21/2018 11:06:59.8475] HW CAPWAP tunnel is ADDED
Aug 21 11:07:00 kernel: [*08/21/2018 11:07:00.8892]
Aug 21 11:07:00 kernel: [*08/21/2018 11:07:00.8892] CAPWAP State: Image Data
Aug 21 11:07:00 kernel: [*08/21/2018 11:07:00.9262] do NO_UPGRADE, part1 is active part
Aug 21 11:07:00 kernel: [*08/21/2018 11:07:00.9300]
Aug 21 11:07:00 kernel: [*08/21/2018 11:07:00.9300] CAPWAP State: Configure
Aug 21 11:07:00 kernel: [*08/21/2018 11:07:00.9322] DOT11_CFG[0] Radio Mode is changed from FlexConnect to FlexConnect
Aug 21 11:07:00 kernel: [*08/21/2018 11:07:00.9330] DOT11_CFG[1] Radio Mode is changed from FlexConnect to FlexConnect
Aug 21 11:07:01 kernel: [*08/21/2018 11:07:01.2748] CAPWAP HW tunnel params changed, DELETING the existing
Aug 21 11:07:02 kernel: [*08/21/2018 11:07:02.3321] HW CAPWAP tunnel is ADDED
Aug 21 11:07:03 kernel: [*08/21/2018 11:07:03.5692] Discarding msg CAPWAP_WTP_EVENT_REQUEST(type 9) in CAPWAP state: Configure(
8).
Aug 21 11:07:03 kernel: [*08/21/2018 11:07:03.5693] Discarding msg CAPWAP_WTP_EVENT_REQUEST(type 9) in CAPWAP state: Configure(
8).
Aug 21 11:07:03 kernel: [*08/21/2018 11:07:03.5693] Discarding msg CAPWAP_WTP_EVENT_REQUEST(type 9) in CAPWAP state: Configure(
8).
Aug 21 11:07:03 kernel: [*08/21/2018 11:07:03.5694] Discarding msg CAPWAP_WTP_EVENT_REQUEST(type 9) in CAPWAP state: Configure(
8).
Aug 21 11:07:03 kernel: [*08/21/2018 11:07:03.5694] Discarding msg CAPWAP_WTP_EVENT_REQUEST(type 9) in CAPWAP state: Configure(
8).
Aug 21 11:07:03 kernel: [*08/21/2018 11:07:03.5695] Discarding msg CAPWAP_WTP_EVENT_REQUEST(type 9) in CAPWAP state: Configure(
8).
Aug 21 11:07:03 kernel: [*08/21/2018 11:07:03.5696] Discarding msg CAPWAP_WTP_EVENT_REQUEST(type 9) in CAPWAP state: Configure(
8).
Aug 21 11:07:04 kernel: [*08/21/2018 11:07:04.0322]
Aug 21 11:07:04 kernel: [*08/21/2018 11:07:04.0323] CAPWAP State: Run
Aug 21 11:07:04 kernel: [*08/21/2018 11:07:04.0641] CAPWAP HW tunnel params changed, UPDATING the existing
Aug 21 11:07:05 kernel: [*08/21/2018 11:07:05.1593] AP has joined controller WLC1
Aug 21 11:07:05 kernel: [*08/21/2018 11:07:05.1722] Flexconnect Switching to Connected Mode!
Aug 21 11:07:06 syslog: Password for xxx changed
Aug 21 11:07:06 kernel: [*08/21/2018 11:07:06.0844] Password for xx changed
Aug 21 11:07:06 kernel: [*08/21/2018 11:07:06.9100] save_on_failure is set to 1
Aug 21 11:07:06 kernel: [*08/21/2018 11:07:06.9103] save_on_failure is set to 1
Aug 21 11:07:07 root: SYS-COND: Retrigger fair condition, 6 power
Aug 21 11:07:34 kernel: [*08/21/2018 11:07:34.1928] set cleanair [slot0][band0] enabled
Aug 21 11:07:34 NCI: I0: openSensor(slot=0)
Aug 21 11:07:34 kernel: [*08/21/2018 11:07:34.2123] set cleanair [slot0][band1] enabled
Aug 21 11:07:34 kernel: [*08/21/2018 11:07:34.2318] set cleanair [slot1][band1] enabled
Aug 21 11:07:35 NCI: I0: SensorApp=1.15.4
Aug 21 11:07:35 NCI: I0: SensorHdw=1.2.3.0
Aug 21 11:07:35 NCI: I0: Hardware Radio Band = [4890, 5935] MHz, BW=150625
Aug 21 11:07:35 NCI: I0: Hardware Radio Band = [2400, 2500] MHz, BW=150625
Aug 21 11:07:35 NCI: slot=0 mode=2 chanCnt=1 cw=1
Aug 21 11:07:35 NCI: chans: 36 0 0 0 0 0 0 0 0 0 0
Aug 21 11:07:35 NCI: I0: channel map channels: in=1 cloned=1
Aug 21 11:07:35 NCI: I0: Requesting MonBand [5180, 5180] bw=20MHz/0 ant=0xbc
Aug 21 11:07:35 NCI: I0: Monitoring (cf=5180, span=20), RadioUsage=3%
Aug 21 11:07:35 NCI: I0: dwell=20000us, update=1000ms, resBW=78126
Aug 21 11:07:35 NCI: CLEANAIR: Slot 0 enabled
Aug 21 11:07:35 NCI: I1: openSensor(slot=1)
Aug 21 11:07:36 NCI: I1: SensorApp=1.15.4
Aug 21 11:07:36 NCI: I1: SensorHdw=1.2.3.0
Aug 21 11:07:36 NCI: I1: Hardware Radio Band = [4890, 5935] MHz, BW=150625
Aug 21 11:07:36 NCI: slot=1 mode=2 chanCnt=1 cw=1

Re: 2800 AP diassociating to WLC oftenly after upgrade.

Sandeep Choudhary — Tue, 21 Aug 2018 13:40:38 GMT

1. are AP and WLC in same subnet !

2. check your connection between AP subnet and WLC subnet!

Regards

Dont forget to arte helpful posts

Re: 2800 AP diassociating to WLC oftenly after upgrade.

AK002 — Tue, 21 Aug 2018 14:12:37 GMT

Hi Sandeep,

Local mode Ap's in same subnet and Flex Ap's are in different Subnets.. But both are having issues.

Regards,AK

Re: 2800 AP diassociating to WLC oftenly after upgrade.

Leo Laohoo — Tue, 21 Aug 2018 23:13:35 GMT

What version did you upgrade from? 8.2?
Have you tried rebooting the AP?

Re: 2800 AP diassociating to WLC oftenly after upgrade.

AK002 — Wed, 22 Aug 2018 09:39:20 GMT

Hi Leo,

Upgraded from 8.3.133.0 to 8.5.131.0

Not tried any AP reboot, As we see this issue in all the AP's in the WLC. Most of the AP's are 2800 model.

Regards,

Arun

Re: 2800 AP diassociating to WLC oftenly after upgrade.

pieterh — Wed, 22 Aug 2018 09:46:12 GMT

check you time sync environment
Aug 21 11:07:06 syslog: Password for xxx changed
Aug 21 11:07:06 kernel: [*08/21/2018 11:07:06.0844] Password for xx changed
may suggest the periodic changing of the key between AP and WLC is not synchronized properly.

Re: 2800 AP diassociating to WLC oftenly after upgrade.

AK002 — Wed, 22 Aug 2018 10:21:54 GMT

Hi, How to do that time Sync.

All AP's generally in UTC 0 and it will get sync from WLC only.

Do you need to check show clock/time.

Regards,AK

Re: 2800 AP diassociating to WLC oftenly after upgrade.

AK002 — Wed, 22 Aug 2018 11:15:02 GMT

Hi,

WLC NTP server is in sync only.

Cisco Controller) >show time

Time............................................. Wed Aug 22 11:30:03 2018

Timezone delta................................... 0:0
Timezone location................................ (GMT) London, Lisbon, Dublin, Edinburgh

NTP Servers
NTP Version.................................. 3
NTP Polling Interval......................... 3600

     Index     NTP Key Index                  NTP Server                Status          NTP Msg Auth Status
    ------- ---------------------------------------------------------------------
       1              0                               10.11.1.2                In Sync              AUTH DISABLED

AP Clock:

***** show clock *****
*13:04:51 UTC Mon Aug 20 2018

Re: 2800 AP diassociating to WLC oftenly after upgrade.

AK002 — Thu, 23 Aug 2018 08:02:16 GMT

Hi,

Can anyone please help on this error..

Re: 2800 AP diassociating to WLC oftenly after upgrade.

Leo Laohoo — Thu, 23 Aug 2018 08:15:36 GMT

Upgrade to 8.5.135.0.

Re: 2800 AP diassociating to WLC oftenly after upgrade.

Vivek_Shukla — Tue, 11 Sep 2018 09:37:23 GMT

I have exactly same setup and hitting the same bug after upgrade from 8.3.133 to 8.5.131 . I have a TAC case open for the same and as suggested by TAC, upgraded to 8.5.135 ..

I can confirm upgrading to new code is of NO USE.

TAC is still investigating but I am planning on removing LAG from the APs to see if this helps with disconnections.

Re: 2800 AP diassociating to WLC oftenly after upgrade.

Vivek_Shukla — Tue, 11 Sep 2018 09:43:50 GMT

Arun, have you found any solution to this.

Re: 2800 AP diassociating to WLC oftenly after upgrade.

cae_technology — Thu, 13 Sep 2018 08:35:43 GMT

Same the TAC is suggested to remove the LAG from the 2800/3800 Model access points. Also try to upgrade to 8.5.135.

Please remove LAG from the AP's in order to stop random channel change in the 5ghz..Also change the AP Re-transmit Config Parameters from 5/3 to 8/5 to stop the AP random disassociation.

Re: 2800 AP diassociating to WLC oftenly after upgrade.

Vivek_Shukla — Thu, 13 Sep 2018 08:58:27 GMT

Removed LAG from few APs in our environment yesterday. Since then those APs are stable. As per TAC this issue is resolved in version 8.5.137 which will be release in next month.

Re: 2800 AP diassociating to WLC oftenly after upgrade.

Vivek_Shukla — Wed, 19 Sep 2018 10:22:05 GMT

Just a quick reply for everyone. I removed LAG from all of the APs in our env and since then all APs are stable. No more disconnections or channel changes. 🙂

Re: 2800 AP diassociating to WLC oftenly after upgrade.

AK002 — Thu, 04 Oct 2018 13:19:19 GMT

Yes After removing the LAG the access points are stable.

Regards,

Re: 2800 AP diassociating to WLC oftenly after upgrade.

chakao1220 — Mon, 07 Jan 2019 00:51:58 GMT

Did Cisco release the bug fix version?

Re: 2800 AP diassociating to WLC oftenly after upgrade.

.Jaidev Hattiangadi. — Tue, 08 Jan 2019 12:02:42 GMT

The bug is CSCvh58148. still unresolved

Re: 2800 AP diassociating to WLC oftenly after upgrade.

AK002 — Wed, 03 Jun 2020 16:06:54 GMT

AP model : 2802I WLC model : 5520 Code : 8.5.161.0

Same error like AP's are disassociating randomly and joining back again.. Any help most appreciated.

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 DC1P-NETWLCPR01
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|

Re: 2800 AP diassociating to WLC oftenly after upgrade.

pieterh — Thu, 04 Jun 2020 11:12:53 GMT

in your old post i found: Peer 10.130.208.101
in your new post: Discovery Response from 10.130.0.110

do you have multiple controllers ? and are they running different software version?