After WLC Upgrade AP cannot connect

kdemir — Wed, 19 Apr 2023 12:16:41 GMT

Hello,

I have Cisco 2500 with 8.5.103 version and a AIR-CAP1702I-E-K9 AP on it.

I upgraded WLC to 8.5.182 with aes and ap bundle file but AP is stuck on the downloading state.

I checked the logs on WLC :

*spamApTask5: Mar 04 15:13:41.842: a8:9d:21:13:18:80 Image data Response from 172.18.7.5:64274

*spamApTask5: Mar 04 15:13:41.842: a8:9d:21:13:18:80 Sending image data block of length 1324 and msgLength = 1327

*spamApTask5: Mar 04 15:13:41.842: a8:9d:21:13:18:80 Image Data Request sent to 172.18.7.5:64274

*spamApTask5: Mar 04 15:13:41.860: a8:9d:21:13:18:80 Image data Response from 172.18.7.5:64274

*spamApTask5: Mar 04 15:13:41.860: a8:9d:21:13:18:80 Sending image data block of length 1324 and msgLength = 1327

*spamApTask5: Mar 04 15:13:41.860: a8:9d:21:13:18:80 Image Data Request sent to 172.18.7.5:64274

*spamApTask5: Mar 04 15:13:41.871: a8:9d:21:13:18:80 Image data Response from 172.18.7.5:64274

*spamApTask5: Mar 04 15:13:41.871: a8:9d:21:13:18:80 Sending image data block of length 1324 and msgLength = 1327

*spamApTask5: Mar 04 15:13:41.871: a8:9d:21:13:18:80 Image Data Request sent to 172.18.7.5:64274

*spamApTask5: Mar 04 15:13:41.889: a8:9d:21:13:18:80 Image data Response from 172.18.7.5:64274

*spamApTask5: Mar 04 15:13:41.889: a8:9d:21:13:18:80 Sending image data block of length 1324 and msgLength = 1327

*spamApTask5: Mar 04 15:13:41.889: a8:9d:21:13:18:80 Image Data Request sent to 172.18.7.5:64274

*spamApTask5: Mar 04 15:13:41.907: a8:9d:21:13:18:80 Image data Response from 172.18.7.5:64274

*spamApTask5: Mar 04 15:13:41.907: a8:9d:21:13:18:80 Sending image data block of length 1324 and msgLength = 1327

*spamApTask5: Mar 04 15:13:41.907: a8:9d:21:13:18:80 Image Data Request sent to 172.18.7.5:64274

*spamApTask5: Mar 04 15:13:41.920: a8:9d:21:13:18:80 Image data Response from 172.18.7.5:64274

*spamApTask5: Mar 04 15:13:41.921: a8:9d:21:13:18:80 Sending image data block of length 1324 and msgLength = 1327

*spamApTask5: Mar 04 15:13:41.921: a8:9d:21:13:18:80 Image Data Request sent to 172.18.7.5:64274

*spamApTask5: Mar 04 15:13:41.938: a8:9d:21:13:18:80 Image data Response from 172.18.7.5:64274

*spamApTask5: Mar 04 15:13:41.938: a8:9d:21:13:18:80 Sending image data block of length 1324 and msgLength = 1327

*spamApTask5: Mar 04 15:13:41.939: a8:9d:21:13:18:80 Image Data Request sent to 172.18.7.5:64274

*spamApTask5: Mar 04 15:13:42.138: a8:9d:21:13:18:80 Image data Response from 172.18.7.5:64274

*spamApTask5: Mar 04 15:13:42.138: a8:9d:21:13:18:80 Sending image data block of length 1324 and msgLength = 1327

*spamApTask5: Mar 04 15:13:42.138: a8:9d:21:13:18:80 Image Data Request sent to 172.18.7.5:64274

*spamApTask5: Mar 04 15:13:42.924: a8:9d:21:13:18:80 Image data Response from 172.18.7.5:64274

*spamApTask5: Mar 04 15:13:42.924: a8:9d:21:13:18:80 Sending image data block of length 1324 and msgLength = 1327

*spamApTask5: Mar 04 15:13:42.924: a8:9d:21:13:18:80 Image Data Request sent to 172.18.7.5:64274

*spamApTask5: Mar 04 15:13:42.935: a8:9d:21:13:18:80 Image data Response from 172.18.7.5:64274

*spamApTask5: Mar 04 15:13:42.935: a8:9d:21:13:18:80 Sending image data block of length 1324 and msgLength = 1327

*spamApTask5: Mar 04 15:13:42.936: a8:9d:21:13:18:80 Image Data Request sent to 172.18.7.5:64274

*spamApTask5: Mar 04 15:13:42.951: a8:9d:21:13:18:80 Image data Response from 172.18.7.5:64274

*spamApTask5: Mar 04 15:13:42.951: a8:9d:21:13:18:80 Sending image data block of length 1324 and msgLength = 1327

*spamApTask5: Mar 04 15:13:42.952: a8:9d:21:13:18:80 Image Data Request sent to 172.18.7.5:64274

*spamApTask5: Mar 04 15:13:42.962: a8:9d:21:13:18:80 Image data Response from 172.18.7.5:64274

*spamApTask5: Mar 04 15:13:42.963: a8:9d:21:13:18:80 Sending image data block of length 1324 and msgLength = 1327

*spamApTask5: Mar 04 15:13:42.963: a8:9d:21:13:18:80 Image Data Request sent to 172.18.7.5:64274

*spamApTask5: Mar 04 15:13:42.964: a8:9d:21:13:18:80 Image data Response from 172.18.7.5:64274

*spamApTask5: Mar 04 15:13:42.964: a8:9d:21:13:18:80 End of file reached while doing image read from file /bsn/ap//c3700. Bytes read in last chunk 648, ferror 0, feof 1
*spamApTask5: Mar 04 15:13:42.964: a8:9d:21:13:18:80 Sending last image data block of length 648 and msgLength = 651

*spamApTask5: Mar 04 15:13:42.964: a8:9d:21:13:18:80 Image Data Request sent to 172.18.7.5:64274

*spamApTask5: Mar 04 15:13:42.985: a8:9d:21:13:18:80 Image data Response from 172.18.7.5:64274

*spamApTask5: Mar 04 15:13:42.986: a8:9d:21:13:18:80 Image data transfer done

*spamApTask7: Mar 04 15:13:44.905: a8:9d:21:13:18:80 Capwap State Change Event (Down) from capwap_ac_sm.c 7891

*spamApTask7: Mar 04 15:13:44.905: a8:9d:21:13:18:80 apfSpamProcessStateChangeInSpamContext: Down LWAPP event for AP a8:9d:21:13:18:80 slot 0
*spamApTask7: Mar 04 15:13:44.905: a8:9d:21:13:18:80 Capwap State Change Event (Down) from capwap_ac_sm.c 7891

*spamApTask7: Mar 04 15:13:44.905: a8:9d:21:13:18:80 apfSpamProcessStateChangeInSpamContext: Down LWAPP event for AP a8:9d:21:13:18:80 slot 1
*spamApTask7: Mar 04 15:13:44.905: a8:9d:21:13:18:80 Finding DTLS connection to delete for AP (172:18:7:5/64274)
*spamApTask7: Mar 04 15:13:44.905: a8:9d:21:13:18:80 Disconnecting DTLS Capwap-Ctrl session 0x1a4551f0 for AP (172:18:7:5/64274). Notify(true)
*spamApTask7: Mar 04 15:13:44.905: a8:9d:21:13:18:80 CAPWAP State: Dtls tear down

*spamApTask7: Mar 04 15:13:44.906: a8:9d:21:13:18:80 acDtlsPlumbControlPlaneKeys: lrad:172.18.7.5(64274) mwar:10.0.3.72(5246)

*spamApTask7: Mar 04 15:13:44.906: a8:9d:21:13:18:80 DTLS keys for Control Plane deleted successfully for AP 172.18.7.5

*apfReceiveTask: Mar 04 15:13:44.908: a8:9d:21:13:18:80 Received LWAPP Down event for AP a8:9d:21:13:18:80 slot 0!
*apfReceiveTask: Mar 04 15:13:44.908: a8:9d:21:13:18:80 Received LWAPP Down event for AP a8:9d:21:13:18:80 slot 1!
*spamApTask5: Mar 04 15:13:44.911: a8:9d:21:13:18:80 DTLS connection closed event receivedserver (10.0.3.72/5246) client (172.18.7.5/64274)
*spamApTask5: Mar 04 15:13:44.911: a8:9d:21:13:18:80 Entry exists for AP (172.18.7.5/64274)
*spamApTask5: Mar 04 15:13:44.911: a8:9d:21:13:18:80 Capwap State Change Event (DeReg) from capwap_ac_sm.c 1787

*spamApTask5: Mar 04 15:13:44.911: a8:9d:21:13:18:80 apfSpamProcessStateChangeInSpamContext: Deregister LWAPP event for AP a8:9d:21:13:18:80 slot 0
*spamApTask5: Mar 04 15:13:44.911: a8:9d:21:13:18:80 Capwap State Change Event (DeReg) from capwap_ac_sm.c 1787

*spamApTask5: Mar 04 15:13:44.911: a8:9d:21:13:18:80 apfSpamProcessStateChangeInSpamContext: Deregister LWAPP event for AP a8:9d:21:13:18:80 slot 1
*spamApTask5: Mar 04 15:13:44.912: a8:9d:21:13:18:80 AP Delete request
*spamApTask5: Mar 04 15:13:44.912: a8:9d:21:13:18:80 No AP entry exist in temporary database for 172.18.7.5:64274
*apfReceiveTask: Mar 04 15:13:44.913: a8:9d:21:13:18:80 Deregister LWAPP event for AP a8:9d:21:13:18:80 slot 0
*apfReceiveTask: Mar 04 15:13:44.914: a8:9d:21:13:18:80 Deregister LWAPP event for AP a8:9d:21:13:18:80 slot 1

How can i solve this issue?

Re: After WLC Upgrade AP cannot connect

kdemir — Wed, 19 Apr 2023 12:59:17 GMT

Hi Leo,

Thank you for your answer.

I set the WLC time before Dec 2022 AP connected the WLC.

Re: After WLC Upgrade AP cannot connect

Rich R — Thu, 20 Apr 2023 16:51:13 GMT

But that is only a temporary workaround @kdemir

You need to upgrade to 8.5.182.7 - link below.

topic After WLC Upgrade AP cannot connect in Wireless

After WLC Upgrade AP cannot connect

Re: After WLC Upgrade AP cannot connect

Re: After WLC Upgrade AP cannot connect

Re: After WLC Upgrade AP cannot connect