topic Re: access point associate & disassociate from WLC in Wireless

access point associate & disassociate from WLC

lalitkumar88551 — Fri, 29 Apr 2022 07:37:47 GMT

Hi Team ,

Please help & suggest, i am facing issue AP join & unjoin form cisco1852i mobility express controller after upgrade firmware 8.8.120.0 to 8.10.151.0.

WLC log:

Burned-in MAC Address............................ 4C:BC:48:34:3E:A0
Maximum number of APs supported.................. 50
System Information
Manufacturer's Name.............................. Cisco Systems Inc.
Product Name..................................... Cisco Controller
Product Version.................................. 8.10.151.0
OUI File Last Update Time........................ N/A

System Name...................................... inchenprdwlc01
System Location..................................
System Contact...................................
System ObjectID.................................. 1.3.6.1.4.1.9.1.2250
IP Address....................................... 10.X.X.X
Last Reset....................................... 1: reload command

System Up Time................................... 2 days 2 hrs 3 mins 49 secs
System Timezone Location......................... (GMT +5:30) Colombo, New Delhi, Chennai, Kolkata
System Stats Realtime Interval................... 5
System Stats Normal Interval..................... 180

Configured Country............................... IN - India

State of 802.11b Network......................... Enabled
State of 802.11a Network......................... Enabled
Number of WLANs.................................. 5
Number of Active Clients......................... 22

message log

*CAPWAP DATA: Apr 25 16:24:43.758: %LOG-3-Q_IND: rrmClient.c:1362 RRM LOG: iapp chd, Unable to find AP 4c:bc:48:35:38:00
*CAPWAP DATA: Apr 25 16:24:39.193: %RRM-3-RRM_LOGMSG: rrmClient.c:1362 RRM LOG: iapp chd, Unable to find AP 4c:bc:48:35:38:00
*CAPWAP DATA: Apr 25 16:24:24.863: %RRM-3-RRM_LOGMSG: rrmClient.c:1717 RRM LOG: iapp u3 client stat, unable to find AP 4c:bc:48:35:38:00
*spamApTask0: Apr 25 16:24:10.863: %LWAPP-3-AP_DEL: spam_lrad.c:6088 4c:bc:48:35:38:00: Entry deleted for AP: 10.129.44.202 (5248) reason : Normal Termination.
*CAPWAP DATA: Apr 25 16:07:29.101: %RRM-3-RRM_LOGMSG: rrmClient.c:1599 RRM LOG: iapp chd client stat , Unable to find AP 4c:bc:48:35:38:00
*CAPWAP DATA: Apr 25 16:07:29.101: %LOG-3-Q_IND: rrmClient.c:1230 RRM LOG: IAPP AGGR Neigh, Unable to find AP 4c:bc:48:35:38:00
*CAPWAP DATA: Apr 25 16:07:26.630: %RRM-3-RRM_LOGMSG: rrmClient.c:1230 RRM LOG: IAPP AGGR Neigh, Unable to find AP 4c:bc:48:35:38:00
*spamApTask0: Apr 25 16:06:49.104: %LWAPP-3-AP_DEL: spam_lrad.c:6088 4c:bc:48:35:38:00: Entry deleted for AP: 10.129.44.202 (5248) reason : Normal Termination.
*Dot1x_NW_MsgTask_0: Apr 25 15:47:15.223: %LOG-3-Q_IND: rrmClient.c:1362 RRM LOG: iapp chd, Unable to find AP 4c:bc:48:35:38:00
*CAPWAP DATA: Apr 25 15:47:09.102: %RRM-3-RRM_LOGMSG: rrmClient.c:1362 RRM LOG: iapp chd, Unable to find AP 4c:bc:48:35:38:00
*CAPWAP DATA: Apr 25 15:46:52.766: %RRM-3-RRM_LOGMSG: rrmClient.c:1717 RRM LOG: iapp u3 client stat, unable to find AP 4c:bc:48:35:38:00
*spamApTask0: Apr 25 15:46:32.115: %LWAPP-3-AP_DEL: spam_lrad.c:6088 4c:bc:48:35:38:00: Entry deleted for AP: 10.129.44.202 (5248) reason : Normal Termination.
*spamApTask0: Apr 25 15:44:12.758: %LWAPP-3-AP_DEL: spam_lrad.c:6088 4c:bc:48:35:38:00: Entry deleted for AP: 10.129.44.202 (5248) reason : Normal Termination.
*CAPWAP DATA: Apr 25 15:42:22.586: %RRM-3-RRM_LOGMSG: rrmClient.c:1717 RRM LOG: iapp u3 client stat, unable to find AP 4c:bc:48:35:38:00

--More-- or (q)uit
*CAPWAP DATA: Apr 25 15:41:57.550: %RRM-3-RRM_LOGMSG: rrmClient.c:1599 RRM LOG: iapp chd client stat , Unable to find AP 4c:bc:48:35:38:00
*spamApTask0: Apr 25 15:41:32.987: %LWAPP-3-AP_DEL: spam_lrad.c:6088 4c:bc:48:35:38:00: Entry deleted for AP: 10.129.44.202 (5248) reason : Normal Termination.
*CAPWAP DATA: Apr 25 15:40:26.703: %RRM-3-RRM_LOGMSG: rrmClient.c:1599 RRM LOG: iapp chd client stat , Unable to find AP 4c:bc:48:35:38:00
*spamApTask0: Apr 25 15:40:09.603: %LWAPP-3-AP_DEL: spam_lrad.c:6088 4c:bc:48:35:38:00: Entry deleted for AP: 10.129.44.202 (5248) reason : Normal Termination.
*CAPWAP DATA: Apr 25 15:37:26.520: %RRM-3-RRM_LOGMSG: rrmClient.c:1599 RRM LOG: iapp chd client stat , Unable to find AP 4c:bc:48:35:38:00

AP log:

Apr 25 17:21:32 kernel: [*04/25/2022 11:51:32.2264] Setting gPreDownloadComplete=0
Apr 25 17:21:32 kernel: [*04/25/2022 11:51:32.2264] Discarding msg CAPWAP_WTP_EVENT_REQUEST(type 9) in CAPWAP state: DTLS Teardown(4).
Apr 25 17:21:32 kernel: [*04/25/2022 11:51:32.2264] Discarding msg CAPWAP_WTP_EVENT_REQUEST(type 9) in CAPWAP state: DTLS Teardown(4).
Apr 25 17:21:36 kernel: [*04/25/2022 11:51:36.7250] DTLS session cleanup completed. Restarting capwap state machine.
Apr 25 17:21:36 kernel: [*04/25/2022 11:51:36.7650] Restarting WLC Discovery
Apr 25 17:21:36 kernel: [*04/25/2022 11:51:36.7650] Starting Discovery.
Apr 25 17:21:46 kernel: [*04/25/2022 11:51:46.8018] Discovery Request sent to FlexME 10.129.44.237
Apr 25 17:21:46 kernel: [*04/25/2022 11:51:46.8118] Dropping TLV_AP_EWLC_TAGS_PAYLOAD. No info available
Apr 25 17:21:46 kernel: [*04/25/2022 11:51:46.8118] Discovery Request sent to 10.129.44.237, discovery type STATIC_CONFIG(1)
Apr 25 17:21:46 kernel: [*04/25/2022 11:51:46.8118] Discovery Request sent to FlexME ::
Apr 25 17:21:46 kernel: [*04/25/2022 11:51:46.8118] Not sending discovery request to the invalid AC address
Apr 25 17:21:46 kernel: [*04/25/2022 11:51:46.9018] systemd[1]: Starting dhcpv6 client watcher...
Apr 25 17:21:46 kernel: [*04/25/2022 11:51:46.9218] systemd[1]: Stopping DHCPv6 client...
Apr 25 17:21:47 kernel: [*04/25/2022 11:51:46.9918] systemd[1]: Starting DHCPv6 client...
Apr 25 17:21:47 kernel: [*04/25/2022 11:51:47.1217] systemd[1]: Started DHCPv6 client.
Apr 25 17:21:47 kernel: [*04/25/2022 11:51:47.2317] systemd[1]: Started dhcpv6 client watcher.
Apr 25 17:21:56 kernel: [*04/25/2022 11:51:56.1289] Could not discover any WLC. Count:[1]
Apr 25 17:22:06 kernel: [*04/25/2022 11:52:06.1258] Starting Discovery.
Apr 25 17:22:06 sshd[13429]: error: Could not get shadow information for netbackup
Apr 25 17:22:06 sshd[13429]: Accepted password for netbackup from port 60715 ssh2
Apr 25 17:22:06 kernel: [*04/25/2022 11:52:06.3557] systemd[1]: Starting dhcpv6 client watcher...
Apr 25 17:22:06 kernel: [*04/25/2022 11:52:06.3757] systemd[1]: Stopping DHCPv6 client...
Apr 25 17:22:06 kernel: [*04/25/2022 11:52:06.4457] systemd[1]: Starting DHCPv6 client...
Apr 25 17:22:06 kernel: [*04/25/2022 11:52:06.5657] systemd[1]: Started DHCPv6 client.
Apr 25 17:22:06 kernel: [*04/25/2022 11:52:06.6856] systemd[1]: Started dhcpv6 client watcher.
Apr 25 17:22:08 FIPS[13480]: *** shell: FIPS Mode = disabled ***
Apr 25 17:22:16 kernel: [*04/25/2022 11:52:16.1627] Discovery Request sent to FlexME 10.129.44.237
Apr 25 17:22:16 kernel: [*04/25/2022 11:52:16.1727] Dropping TLV_AP_EWLC_TAGS_PAYLOAD. No info available
Apr 25 17:22:16 kernel: [*04/25/2022 11:52:16.1727] Discovery Request sent to 10.129.44.237, discovery type STATIC_CONFIG(1)
Apr 25 17:22:16 kernel: [*04/25/2022 11:52:16.1727] Discovery Request sent to FlexME ::
Apr 25 17:22:16 kernel: [*04/25/2022 11:52:16.1727] Not sending discovery request to the invalid AC address
Apr 25 17:22:16 kernel: [*04/25/2022 11:52:16.1727] Discovery Response from 10.129.44.237
Apr 25 17:22:16 kernel: [*04/25/2022 11:52:16.1727] AC IPv4 10.129.44.237, load 15, count 1
Apr 25 17:22:16 kernel: [*04/25/2022 11:52:16.2526] systemd[1]: Starting dhcpv6 client watcher...
Apr 25 17:22:16 kernel: [*04/25/2022 11:52:16.2726] systemd[1]: Stopping DHCPv6 client...
Apr 25 17:22:16 kernel: [*04/25/2022 11:52:16.3326] systemd[1]: Starting DHCPv6 client...
Apr 25 17:22:16 kernel: [*04/25/2022 11:52:16.4526] systemd[1]: Started DHCPv6 client.
Apr 25 17:22:16 kernel: [*04/25/2022 11:52:16.6025] systemd[1]: Started dhcpv6 client watcher.
Apr 25 17:22:17 kernel: [*04/25/2022 11:52:17.4323] Discarding msg CAPWAP_WTP_EVENT_REQUEST(type 9) in CAPWAP state: Discovery(2).
Apr 25 17:22:25 kernel: [*04/25/2022 11:52:25.5997] Calling wtpGetAcToJoin from timer expiry.
Apr 25 17:22:25 kernel: [*04/25/2022 11:52:25.5997] DiscRep[0]: addr 10.129.44.237, apMgrCount 1
Apr 25 17:22:25 kernel: [*04/25/2022 11:52:25.5997] Selected MWAR 'inchenprdwlc01' 10.129.44.237 (index 0).
Apr 25 17:22:25 kernel: [*04/25/2022 11:52:25.5997] apMgrCount 1, index 0
Apr 25 17:22:25 kernel: [*04/25/2022 11:52:25.5997] Adding Ipv4 AP manager 10.129.44.237 to least load
Apr 25 17:22:25 kernel: [*04/25/2022 11:52:25.5997] WLC: inchenprdwlc01 ApMgr count 1, ipTransportTried 0, prefer-mode 1, isIpv4OrIpv6Static 2
Apr 25 17:22:25 kernel: [*04/25/2022 11:52:25.5997] IPv4 Pref mode. Choosing AP Mgr with index 0, IP 10.129.44.237, load 15, AP ip: (10.129.44.202)
Apr 25 17:22:25 kernel: [*04/25/2022 11:52:25.5997] capwapSetTransportAddr returning: index 0, apMgrCount 0
Apr 25 17:22:25 kernel: [*04/25/2022 11:52:25.5997]
Apr 25 17:22:25 kernel: [*04/25/2022 11:52:25.5997]
Apr 25 17:22:25 kernel: [*04/25/2022 11:52:25.5997] CAPWAP State: DTLS Setup
Apr 25 17:22:25 kernel: [*04/25/2022 11:52:25.5997] dtls_cssl_msg_cb: Received >>> DTLS Header [Length 000d]
Apr 25 17:22:25 kernel: [*04/25/2022 11:52:25.5997] dtls_cssl_msg_cb: Received >>> DTLS 1.2 Handshake [Length 00ac] ClientHello
Apr 25 17:22:25 kernel: [*04/25/2022 11:52:25.5997] dtls_connectionDB_add_connection: Added Connection 0x2a6baa00 Server [10.129.44.237]:5246 Client [10.129.44.202]:5248
Apr 25 17:22:25 kernel: [*04/25/2022 11:52:25.5997]
Apr 25 17:22:25 kernel: [*04/25/2022 11:52:25.5997] create_dtls_connection: Creating DTLS Ctrl Connection 0x2a6baa00
Apr 25 17:22:25 kernel: [*04/25/2022 11:52:25.5997] DTLS connection created sucessfully local_ip: 10.129.44.202 local_port: 5248 peer_ip: 10.129.44.237 peer_port: 5246
Apr 25 17:22:25 kernel: [*04/25/2022 11:52:25.6097] local_in_addr_comp: Client and server addresses/port/version of 2 nodes are [10.129.44.202]:5248(0)--[10.129.44.237]:5246(0) [10.129.44.202]:5248--[10.129.44.237]:5246
Apr 25 17:22:25 kernel: [*04/25/2022 11:52:25.6097] dtls_connection_find_using_link_info: Searching connection [10.129.44.202]:5248--[10.129.44.237]:5246, result 0x2a6baa00
Apr 25 17:22:25 kernel: [*04/25/2022 11:52:25.6097] dtls_cssl_msg_cb: Sent <<< DTLS Header [Length 000d]
Apr 25 17:22:25 kernel: [*04/25/2022 11:52:25.6097] dtls_cssl_msg_cb: Sent <<< DTLS 1.2 Handshake [Length 002f] HelloVerifyRequest
Apr 25 17:22:25 kernel: [*04/25/2022 11:52:25.6097] dtls_cssl_msg_cb: Received >>> DTLS Header [Length 000d]
Apr 25 17:22:25 kernel: [*04/25/2022 11:52:25.6097] dtls_cssl_msg_cb: Received >>> DTLS 1.2 Handshake [Length 00cc] ClientHello
Apr 25 17:22:25 kernel: [*04/25/2022 11:52:25.6097] dtls_process_packet: SSL get error rc 5
Apr 25 17:22:25 kernel: [*04/25/2022 11:52:25.6097] local_in_addr_comp: Client and server addresses/port/version of 2 nodes are [10.129.44.202]:5248(0)--[10.129.44.237]:5246(0) [10.129.44.202]:5248--[10.129.44.237]:5246
Apr 25 17:22:25 kernel: [*04/25/2022 11:52:25.6097] dtls_connection_find_using_link_info: Searching connection [10.129.44.202]:5248--[10.129.44.237]:5246, result 0x2a6baa00
Apr 25 17:22:25 kernel: [*04/25/2022 11:52:25.6097] dtls_cssl_msg_cb: Sent <<< DTLS Header [Length 000d]
Apr 25 17:22:25 kernel: [*04/25/2022 11:52:25.6097] dtls_cssl_msg_cb: Sent <<< DTLS 1.2 Handshake [Length 005e] ServerHello
Apr 25 17:22:25 kernel: [*04/25/2022 11:52:25.6097] dtls_cssl_msg_cb: Sent <<< DTLS Header [Length 000d]
Apr 25 17:22:25 kernel: [*04/25/2022 11:52:25.6097] dtls_process_packet: SSL get error rc 5
Apr 25 17:22:25 kernel: [*04/25/2022 11:52:25.6097] local_in_addr_comp: Client and server addresses/port/version of 2 nodes are [10.129.44.202]:5248(0)--[10.129.44.237]:5246(0) [10.129.44.202]:5248--[10.129.44.237]:5246
Apr 25 17:22:25 kernel: [*04/25/2022 11:52:25.6097] dtls_connection_find_using_link_info: Searching connection [10.129.44.202]:5248--[10.129.44.237]:5246, result 0x2a6baa00
Apr 25 17:22:25 kernel: [*04/25/2022 11:52:25.6097] dtls_cssl_msg_cb: Sent <<< DTLS Header [Length 000d]
Apr 25 17:22:25 kernel: [*04/25/2022 11:52:25.6097] dtls_process_packet: SSL get error rc 5
Apr 25 17:22:25 kernel: [*04/25/2022 11:52:25.6097] local_in_addr_comp: Client and server addresses/port/version of 2 nodes are [10.129.44.202]:5248(0)--[10.129.44.237]:5246(0) [10.129.44.202]:5248--[10.129.44.237]:5246
Apr 25 17:22:25 kernel: [*04/25/2022 11:52:25.6097] dtls_connection_find_using_link_info: Searching connection [10.129.44.202]:5248--[10.129.44.237]:5246, result 0x2a6baa00
Apr 25 17:22:25 kernel: [*04/25/2022 11:52:25.6097] dtls_cssl_msg_cb: Sent <<< DTLS Header [Length 000d]
Apr 25 17:22:25 kernel: [*04/25/2022 11:52:25.6097] dtls_cssl_msg_cb: Sent <<< DTLS 1.2 Handshake [Length 0485] Certificate
Apr 25 17:22:25 kernel: [*04/25/2022 11:52:25.6097] dtls_cssl_msg_cb: Sent <<< DTLS Header [Length 000d]
Apr 25 17:22:25 kernel: [*04/25/2022 11:52:25.6097] dtls_cssl_msg_cb: Sent <<< DTLS 1.2 Handshake [Length 0067] CertificateRequest
Apr 25 17:22:25 kernel: [*04/25/2022 11:52:25.6097] dtls_cssl_msg_cb: Sent <<< DTLS Header [Length 000d]
Apr 25 17:22:25 kernel: [*04/25/2022 11:52:25.6097] dtls_cssl_msg_cb: Sent <<< DTLS 1.2 Handshake [Length 000c] ServerHelloDone
Apr 25 17:22:25 kernel: [*04/25/2022 11:52:25.6097] dtls_cssl_msg_cb: Received >>> DTLS Header [Length 000d]
Apr 25 17:22:25 kernel: [*04/25/2022 11:52:25.6097] dtls_cssl_msg_cb: Received >>> DTLS Header [Length 000d]
Apr 25 17:22:25 kernel: [*04/25/2022 11:52:25.6197] dtls_cssl_msg_cb: Received >>> DTLS Header [Length 000d]
Apr 25 17:22:25 kernel: [*04/25/2022 11:52:25.6197] dtls_cssl_msg_cb: Received >>> DTLS 1.2 Handshake [Length 0485] Certificate
Apr 25 17:22:25 kernel: [*04/25/2022 11:52:25.6497] dtls_cssl_msg_cb: Received >>> DTLS Header [Length 000d]
Apr 25 17:22:25 kernel: [*04/25/2022 11:52:25.6497] dtls_cssl_msg_cb: Received >>> DTLS 1.2 Handshake [Length 010e] ClientKeyExchange
Apr 25 17:22:25 kernel: [*04/25/2022 11:52:25.6597] dtls_cssl_msg_cb: Received >>> DTLS Header [Length 000d]
Apr 25 17:22:25 kernel: [*04/25/2022 11:52:25.6597] dtls_cssl_msg_cb: Received >>> DTLS 1.2 Handshake [Length 0110] CertificateVerify
Apr 25 17:22:25 kernel: [*04/25/2022 11:52:25.6597] dtls_cssl_msg_cb: Received >>> DTLS Header [Length 000d]
Apr 25 17:22:25 kernel: [*04/25/2022 11:52:25.6597] dtls_cssl_msg_cb: Received >>> DTLS 1.2 ChangeCipherSpec [Length 0001]
Apr 25 17:22:25 kernel: [*04/25/2022 11:52:25.6597] dtls_cssl_msg_cb: Received >>> DTLS Header [Length 000d]
Apr 25 17:22:25 kernel: [*04/25/2022 11:52:25.6597] dtls_cssl_msg_cb: Received >>> DTLS 1.2 Handshake [Length 0018] Finished
Apr 25 17:22:25 kernel: [*04/25/2022 11:52:25.6597] dtls_process_packet: SSL get error rc 5
Apr 25 17:22:25 kernel: [*04/25/2022 11:52:25.6897] local_in_addr_comp: Client and server addresses/port/version of 2 nodes are [10.129.44.202]:5248(65277)--[10.129.44.237]:5246(65277) [10.129.44.202]:5248--[10.129.44.237]:5246
Apr 25 17:22:25 kernel: [*04/25/2022 11:52:25.6897] dtls_connection_find_using_link_info: Searching connection [10.129.44.202]:5248--[10.129.44.237]:5246, result 0x2a6baa00
Apr 25 17:22:25 kernel: [*04/25/2022 11:52:25.6897] dtls_cssl_msg_cb: Sent <<< DTLS Header [Length 000d]
Apr 25 17:22:25 kernel: [*04/25/2022 11:52:25.6897] dtls_cssl_msg_cb: Sent <<< DTLS 1.2 ChangeCipherSpec [Length 0001]
Apr 25 17:22:25 kernel: [*04/25/2022 11:52:25.6897] dtls_cssl_msg_cb: Sent <<< DTLS Header [Length 000d]
Apr 25 17:22:25 kernel: [*04/25/2022 11:52:25.6897] dtls_cssl_msg_cb: Sent <<< DTLS 1.2 Handshake [Length 0018] Finished
Apr 25 17:22:25 kernel: [*04/25/2022 11:52:25.8296] dtls_load_ca_certs: LSC not enabled
Apr 25 17:22:25 kernel: [*04/25/2022 11:52:25.8296]
Apr 25 17:22:25 kernel: [*04/25/2022 11:52:25.8296] dtls_verify_con_cert: serverAuth not set in Controller certificate!
Apr 25 17:22:25 kernel: [*04/25/2022 11:52:25.8296] dtls_verify_con_cert: Certificate Subject Name: /C=US/ST=California/L=San Jose/O=Cisco Systems/CN=AP1G4-4CBC48343EB0/emailAddress=support@cisco.com
Apr 25 17:22:25 kernel: [*04/25/2022 11:52:25.8296] dtls_verify_con_cert: Subject CN: AP1G4-4CBC48343EB0
Apr 25 17:22:25 kernel: [*04/25/2022 11:52:25.8496] dtls_connection_established: Connection established!
Apr 25 17:22:25 kernel: [*04/25/2022 11:52:25.8496] Dtls Session Established with the AC 10.129.44.237, port 5246
Apr 25 17:22:25 kernel: [*04/25/2022 11:52:25.8496]
Apr 25 17:22:25 kernel: [*04/25/2022 11:52:25.8496] CAPWAP State: Join
Apr 25 17:22:25 kernel: [*04/25/2022 11:52:25.8596] Dropping TLV_AP_EWLC_TAGS_PAYLOAD. No info available
Apr 25 17:22:25 kernel: [*04/25/2022 11:52:25.8596] local_in_addr_comp: Client and server addresses/port/version of 2 nodes are [10.129.44.202]:5248(65277)--[10.129.44.237]:5246(65277) [10.129.44.202]:5248--[10.129.44.237]:5246
Apr 25 17:22:25 kernel: [*04/25/2022 11:52:25.8596] dtls_connection_find_using_link_info: Searching connection [10.129.44.202]:5248--[10.129.44.237]:5246, result 0x2a6baa00
Apr 25 17:22:25 kernel: [*04/25/2022 11:52:25.8596] local_in_addr_comp: Client and server addresses/port/version of 2 nodes are [10.129.44.202]:5248(65277)--[10.129.44.237]:5246(65277) [10.129.44.202]:5248--[10.129.44.237]:5246
Apr 25 17:22:25 kernel: [*04/25/2022 11:52:25.8596] dtls_connection_find_using_link_info: Searching connection [10.129.44.202]:5248--[10.129.44.237]:5246, result 0x2a6baa00
Apr 25 17:22:25 kernel: [*04/25/2022 11:52:25.8596] local_in_addr_comp: Client and server addresses/port/version of 2 nodes are [10.129.44.202]:5248(65277)--[10.129.44.237]:5246(65277) [10.129.44.202]:5248--[10.129.44.237]:5246
Apr 25 17:22:25 kernel: [*04/25/2022 11:52:25.8596] dtls_connection_find_using_link_info: Searching connection [10.129.44.202]:5248--[10.129.44.237]:5246, result 0x2a6baa00
Apr 25 17:22:25 kernel: [*04/25/2022 11:52:25.8596] Sending Join request to 10.129.44.237 through port 5248
Apr 25 17:22:25 kernel: [*04/25/2022 11:52:25.8596] local_in_addr_comp: Client and server addresses/port/version of 2 nodes are [10.129.44.202]:5248(65277)--[10.129.44.237]:5246(65277) [10.129.44.202]:5248--[10.129.44.237]:5246
Apr 25 17:22:25 kernel: [*04/25/2022 11:52:25.8596] dtls_connection_find_using_link_info: Searching connection [10.129.44.202]:5248--[10.129.44.237]:5246, result 0x2a6baa00
Apr 25 17:22:25 kernel: [*04/25/2022 11:52:25.8596] dtls_cssl_msg_cb: Received >>> DTLS Header [Length 000d]
Apr 25 17:22:25 kernel: [*04/25/2022 11:52:25.8596] wtpDtlsCallback: DTLS-Ctrl Connection 0x2a6baa00 established
Apr 25 17:22:25 kernel: [*04/25/2022 11:52:25.8596] dtls_process_packet: dtls connection established, reset harsa_retry_count
Apr 25 17:22:25 kernel: [*04/25/2022 11:52:25.8696] local_in_addr_comp: Client and server addresses/port/version of 2 nodes are [10.129.44.202]:5248(65277)--[10.129.44.237]:5246(65277) [10.129.44.202]:5248--[10.129.44.237]:5246
Apr 25 17:22:25 kernel: [*04/25/2022 11:52:25.8696] dtls_connection_find_using_link_info: Searching connection [10.129.44.202]:5248--[10.129.44.237]:5246, result 0x2a6baa00
Apr 25 17:22:25 kernel: [*04/25/2022 11:52:25.8696] dtls_cssl_msg_cb: Sent <<< DTLS Header [Length 000d]
Apr 25 17:22:25 kernel: [*04/25/2022 11:52:25.8696] Join Response from 10.129.44.237
Apr 25 17:22:25 kernel: [*04/25/2022 11:52:25.8696] AC accepted join request with result code: 0
Apr 25 17:22:25 kernel: [*04/25/2022 11:52:25.8696] AC IPv4 10.129.44.237, load 16, count 1
Apr 25 17:22:25 kernel: [*04/25/2022 11:52:25.8696] Received wlcType 1, timer 120
Apr 25 17:22:25 kernel: [*04/25/2022 11:52:25.9696] CAPWAP data tunnel UPDATE to forwarding SUCCEEDED
Apr 25 17:22:25 kernel: [*04/25/2022 11:52:25.9796] Starting Post Join timer
Apr 25 17:22:25 kernel: [*04/25/2022 11:52:25.9796]
Apr 25 17:22:25 kernel: [*04/25/2022 11:52:25.9796] CAPWAP State: Image Data
Apr 25 17:22:25 kernel: [*04/25/2022 11:52:25.9796] AP image version 8.10.151.0 backup 8.8.120.0, Controller 8.10.151.0
Apr 25 17:22:25 kernel: [*04/25/2022 11:52:25.9796] Version is the same, do not need update.
Apr 25 17:22:26 upgrade: Script called with args:[NO_UPGRADE]
Apr 25 17:22:26 kernel: [*04/25/2022 11:52:26.0296] Script called with args:[NO_UPGRADE]
Apr 25 17:22:26 kernel: [*04/25/2022 11:52:26.0596] do NO_UPGRADE, part2 is active part
Apr 25 17:22:26 kernel: [*04/25/2022 11:52:26.0696]
Apr 25 17:22:26 kernel: [*04/25/2022 11:52:26.0696] CAPWAP State: Configure
Apr 25 17:22:26 syslog: Disabled LAG load balance
Apr 25 17:22:26 kernel: [*04/25/2022 11:52:26.2795] configuration status request part 0 encodeLen = 2255 len = 8.
Apr 25 17:22:26 kernel: [*04/25/2022 11:52:26.2795] local_in_addr_comp: Client and server addresses/port/version of 2 nodes are [10.129.44.202]:5248(65277)--[10.129.44.237]:5246(65277) [10.129.44.202]:5248--[10.129.44.237]:5246
[10.129.44.237]:5246

Re: access point associate & disassociate from WLC

Flavio Miranda — Fri, 29 Apr 2022 09:06:33 GMT

In this situation, I´d consider fallback to the older version or try a different version. You may hit a bug. Unless you are looking for a feature that only exist on the new version, I´d prefer keep my devices on the versrion they work fine.

Re: access point associate & disassociate from WLC

Mark Elsen — Fri, 29 Apr 2022 11:55:06 GMT

- FYI : https://bst.cloudapps.cisco.com/bugsearch/bug/CSCvy37953

Re: access point associate & disassociate from WLC

lalitkumar88551 — Fri, 29 Apr 2022 13:36:16 GMT

I also saw error of bug, then i thought to take suggestion from experts. can you suggest good way to resolve the issue without network interrupt.

Re: access point associate & disassociate from WLC

MHM Cisco World — Sat, 30 Apr 2022 11:26:49 GMT

https://bst.cloudapps.cisco.com/bugsearch/bug/CSCvc74876

Re: access point associate & disassociate from WLC

Rich R — Mon, 02 May 2022 09:11:23 GMT

If you must go to 8.10 then I'd recommend 8.10.171.0

https://software.cisco.com/download/home/286285803/type/286289839/release/8.10.171.0

It's already the suggested release for WLC - I think they just haven't got round to updating it for ME yet.

Otherwise like Flavio said you'll have to consider rollback.

There is no option to fix this without some disruption unfortunately, and the workaround on that bug is to reload the AP.

Re: access point associate & disassociate from WLC

lalitkumar88551 — Tue, 03 May 2022 11:13:06 GMT

Hi rrudling,

i had upgrade to 8.10.162.0 but nothing change same issue still associate & disassociate from WLC & it is continue try to join & then few minutes later again disconnect & again join.

System Information
Manufacturer's Name.............................. Cisco Systems Inc.
Product Name..................................... Cisco Controller
Product Version.................................. 8.10.162.0
OUI File Last Update Time........................ N/A

System Name...................................... iwlc
System Location..................................
System Contact...................................
System ObjectID.................................. 1.3.6.1.4.1.9.1.2250
IP Address....................................... 10.128.X.X
Last Reset....................................... 1: reload command

System Up Time................................... 0 days 0 hrs 32 mins 45 secs
System Timezone Location......................... (GMT +5:30) Colombo, New Delhi, Chennai, Kolkata
System Stats Realtime Interval................... 5
System Stats Normal Interval..................... 180

Configured Country............................... IN - India

Re: access point associate & disassociate from WLC

MHM Cisco World — Tue, 03 May 2022 11:40:07 GMT

reload one AP and see if this will fix your issue.

https://bst.cloudapps.cisco.com/bugsearch/bug/CSCvy37953

Re: access point associate & disassociate from WLC

lalitkumar88551 — Thu, 05 May 2022 13:05:49 GMT

Hi MHM,

already try to reboot one AP and see the issue not resolved & I also upgraded 8.10.162.0 but issue is same.

Re: access point associate & disassociate from WLC

Rich R — Thu, 05 May 2022 13:26:16 GMT

Like I already said if you're going to upgrade then you should try 8.10.171.0 not 8.10.162.0

Re: access point associate & disassociate from WLC

Paolo Moserle — Thu, 15 Jun 2023 08:44:37 GMT

Hi, same issue with ME on 8.10.182.0, someone was fixed it ? tnx

Re: access point associate & disassociate from WLC

Rich R — Thu, 15 Jun 2023 12:25:58 GMT

This thread is quite old now!
Your first action should be to update to latest release as per TAC recommended below - currently 8.10.185.0 - to eliminate any known bugs which have been fixed.

If you still see the problem after upgrade then best to open a new thread with complete details of the problem you're seeing and the troubleshooting you have done.
Also provide details of AP model(s) and software version and any relevant logs from AP and/or ME.