<?xml version="1.0" encoding="UTF-8"?>
<rss xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:taxo="http://purl.org/rss/1.0/modules/taxonomy/" version="2.0">
  <channel>
    <title>topic Re: C91xx series ap stuck dowloading state in Wireless</title>
    <link>https://community.cisco.com/t5/wireless/c91xx-series-ap-stuck-dowloading-state/m-p/5368168#M288500</link>
    <description>&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;-&amp;nbsp;&lt;a href="https://community.cisco.com/t5/user/viewprofilepage/user-id/1263945"&gt;@pengus&lt;/a&gt;&amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp;&lt;STRONG&gt; &amp;nbsp;Power cycle&lt;/STRONG&gt; one of those problematic access points (start with one for starters) and check if&lt;BR /&gt;&amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp;that makes a difference ; usually when POE is used that can be done with a &lt;EM&gt;shutdown&lt;/EM&gt; followed&lt;BR /&gt;&amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp;by '&lt;EM&gt;no shutdown&lt;/EM&gt;' of the particular interface where the access point is connected to.&lt;/P&gt;
&lt;P&gt;&amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp;If it does not help look into :&amp;nbsp;&lt;A href="https://logadvisor.cisco.com/logadvisor/wireless/9800/9800APJoin" target="_blank"&gt;https://logadvisor.cisco.com/logadvisor/wireless/9800/9800APJoin&lt;/A&gt;&lt;/P&gt;
&lt;P&gt;&amp;nbsp; M.&lt;/P&gt;</description>
    <pubDate>Fri, 06 Feb 2026 13:28:29 GMT</pubDate>
    <dc:creator>Mark Elsen</dc:creator>
    <dc:date>2026-02-06T13:28:29Z</dc:date>
    <item>
      <title>C91xx series ap stuck dowloading state</title>
      <link>https://community.cisco.com/t5/wireless/c91xx-series-ap-stuck-dowloading-state/m-p/5368021#M288494</link>
      <description>&lt;P&gt;After upgrading my C9800-80 controller from version 17.12.4 to 17.12.6a, some access points remain stuck in the “Downloading” state. The following logs are present on the access points.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Feb 6 00:15:58 kernel: [*02/06/2026 03:15:58.5390] CAPWAP State: Image Data&lt;BR /&gt;Feb 6 00:15:58 kernel: [*02/06/2026 03:15:58.5400] AP image version 17.9.5.205 backup 17.12.4.22, Controller 17.12.6.203&lt;BR /&gt;Feb 6 00:15:58 kernel: [*02/06/2026 03:15:58.5400] Version does not match.&lt;BR /&gt;Feb 6 00:15:58 kernel: [*02/06/2026 03:15:58.5400] Request to close the file..&lt;BR /&gt;Feb 6 00:15:58 kernel: [*02/06/2026 03:15:58.5400] wtpOpenImgFile: image file closed, dcb-&amp;gt;fd set to -1.&lt;BR /&gt;Feb 6 03:15:58 upgrade: Script called with args:[PRECHECK]&lt;BR /&gt;Feb 6 00:15:58 kernel: [*02/06/2026 03:15:58.5790] status 'upgrade.sh: Script called with args:[PRECHECK]'&lt;BR /&gt;Feb 6 00:15:58 kernel: [*02/06/2026 03:15:58.6230] do PRECHECK, part2 is active part&lt;BR /&gt;Feb 6 03:15:58 upgrade: Cleanup tmp files ...&lt;BR /&gt;Feb 6 00:15:58 kernel: [*02/06/2026 03:15:58.6360] status 'upgrade.sh: Cleanup tmp files ...'&lt;BR /&gt;Feb 6 03:15:58 upgrade: /tmp space: OK available 96532, required 50000&lt;BR /&gt;Feb 6 00:15:58 kernel: [*02/06/2026 03:15:58.6850] status 'upgrade.sh: /tmp space: OK available 96532, required 50000 '&lt;BR /&gt;Feb 6 00:15:58 kernel: [*02/06/2026 03:15:58.6860] wtpOpenImgFile: request ap1g7, local /tmp/part.tar&lt;BR /&gt;Feb 6 00:15:58 kernel: [*02/06/2026 03:15:58.6860] wtpOpenImgFile: open (/tmp/part.tar) image file success&lt;BR /&gt;Feb 6 00:15:58 kernel: [*02/06/2026 03:15:58.6860] Using fd(367571332096) for image writing to file(/tmp/part.tar)&lt;BR /&gt;Feb 6 00:15:58 kernel: [*02/06/2026 03:15:58.6920] Image Data Request sent to x.x.x.x, fileName [ap1g7], replicaStatus 1&lt;BR /&gt;Feb 6 00:15:58 kernel: [*02/06/2026 03:15:58.6930] Image Data Response from x.x.x.x&lt;BR /&gt;Feb 6 00:15:58 kernel: [*02/06/2026 03:15:58.6930] AC accepted previous sent request with result code: 0&lt;BR /&gt;Feb 6 00:16:12 kernel: [*02/06/2026 03:15:58.6940] &amp;lt;Discarding msg CAPWAP_WTP_EVENT_REQUEST(type 9) in CAPWAP state: Image Data(10).&lt;BR /&gt;Feb 6 00:16:20 kernel: [*02/06/2026 03:16:20.4190] Discarding msg CAPWAP_WTP_EVENT_REQUEST(type 9) in CAPWAP state: Image Data(10).&lt;BR /&gt;Feb 6 00:16:20 kernel: [*02/06/2026 03:16:20.4190] Discarding msg CAPWAP_WTP_EVENT_REQUEST(type 9) in CAPWAP state: Image Data(10).&lt;BR /&gt;Feb 6 00:16:20 kernel: [*02/06/2026 03:16:20.4190] Discarding msg CAPWAP_WTP_EVENT_REQUEST(type 9) in CAPWAP state: Image Data(10).&lt;BR /&gt;Feb 6 00:16:49 kernel: [*02/06/2026 03:16:30.0340] .Discarding msg CAPWAP_WTP_EVENT_REQUEST(type 9) in CAPWAP state: Image Data(10).&lt;BR /&gt;Feb 6 00:16:50 kernel: [*02/06/2026 03:16:50.1860] Discarding msg CAPWAP_WTP_EVENT_REQUEST(type 9) in CAPWAP state: Image Data(10).&lt;BR /&gt;Feb 6 00:17:05 kernel: [*02/06/2026 03:16:54.0440] .Discarding msg CAPWAP_WTP_EVENT_REQUEST(type 9) in CAPWAP state: Image Data(10).&lt;BR /&gt;Feb 6 03:17:52 sensord: sensord psage_base init: RHB Sage base ptr a1030000&lt;BR /&gt;Feb 6 00:17:52 kernel: [*02/06/2026 03:17:10.0740] .Invalid event 58 &amp;amp; state 10 combination.&lt;BR /&gt;Feb 6 00:17:52 kernel: [*02/06/2026 03:17:52.5000] SM handler: Failed to process timer message. Event 58, state 10&lt;BR /&gt;Feb 6 00:17:52 kernel: [*02/06/2026 03:17:52.5000] Failed to handle timer message.&lt;BR /&gt;Feb 6 00:17:52 kernel: [*02/06/2026 03:17:52.5000] FSM failure while processing message with id: 1&lt;BR /&gt;Feb 6 03:17:54 eeprom_api[5141]: FW: SAgE phys_buff=0xA2600000 / 3ffac00&lt;BR /&gt;Feb 6 03:17:54 eeprom_api[5141]: FW: SAgE virt_buff=0x7f74683000&lt;BR /&gt;Feb 6 03:17:54 eeprom_api[5141]: sensord split_glue psage_base: RHB Sage base ptr a1030000&lt;BR /&gt;Feb 6 03:17:54 eeprom_api[5141]: sensord split_glue sage_addr: RHB Sage base ptr a1030000&lt;BR /&gt;Feb 6 03:17:54 eeprom_api[5141]: System page_size=4096, mask=FFFFFFFFFFFFF000&lt;BR /&gt;Feb 6 03:17:54 eeprom_api[5141]: Closing dummy socket&lt;BR /&gt;Feb 6 03:17:54 eeprom_api[5141]: sensord crim: RHB Sage base ptr a1030000&lt;BR /&gt;Feb 6 03:17:54 eeprom_api[5141]: read 0 bytes from eeprom: 6 0 f 1&lt;BR /&gt;Feb 6 03:17:54 eeprom_api[5141]: read 0 bytes from eeprom: ffffffff 5 6 ffffffff&lt;BR /&gt;Feb 6 03:17:54 eeprom_api[5141]: read 0 bytes from eeprom: 23 15 e 24&lt;BR /&gt;Feb 6 03:17:54 eeprom_api[5141]: I_SKU: Hardware ID = C401&lt;BR /&gt;Feb 6 03:17:54 eeprom_api[5141]: read 0 bytes from eeprom: 6 0 f 1&lt;BR /&gt;Feb 6 03:17:54 eeprom_api[5141]: I_SKU: Hardware ID = C401&lt;BR /&gt;Feb 6 03:17:54 eeprom_api[5141]: read 0 bytes from eeprom: 6 0 f 1&lt;BR /&gt;Feb 6 03:17:54 eeprom_api[5141]: I_SKU: Hardware ID = C401&lt;BR /&gt;Feb 6 00:17:55 kernel: [*02/06/2026 03:17:55.5810] Discarding msg CAPWAP_WTP_EVENT_REQUEST(type 9) in CAPWAP state: Image Data(10).&lt;BR /&gt;Feb 6 00:18:53 kernel: [*02/06/2026 03:18:14.0840] ..Discarding msg CAPWAP_WTP_EVENT_REQUEST(type 9) in CAPWAP state: Image Data(10).&lt;BR /&gt;Feb 6 00:19:42 kernel: [*02/06/2026 03:19:26.1170] .Discarding msg CAPWAP_WTP_EVENT_REQUEST(type 9) in CAPWAP state: Image Data(10).&lt;BR /&gt;Feb 6 00:19:49 kernel: [*02/06/2026 03:19:46.2220] .Discarding msg CAPWAP_WTP_EVENT_REQUEST(type 9) in CAPWAP state: Image Data(10).&lt;BR /&gt;Feb 6 00:19:50 kernel: [*02/06/2026 03:19:50.1870] Discarding msg CAPWAP_WTP_EVENT_REQUEST(type 9) in CAPWAP state: Image Data(10).&lt;BR /&gt;Feb 6 00:20:37 kernel: [*02/06/2026 03:20:18.1330] .Discarding msg CAPWAP_WTP_EVENT_REQUEST(type 9) in CAPWAP state: Image Data(10).&lt;BR /&gt;Feb 6 00:21:34 kernel: [*02/06/2026 03:20:42.1650] ...Discarding msg CAPWAP_WTP_EVENT_REQUEST(type 9) in CAPWAP state: Image Data(10).&lt;BR /&gt;Feb 6 00:22:32 kernel: [*02/06/2026 03:22:06.1290] .Discarding msg CAPWAP_WTP_EVENT_REQUEST(type 9) in CAPWAP state: Image Data(10).&lt;BR /&gt;Feb 6 00:22:49 kernel: [*02/06/2026 03:22:46.1520] .Discarding msg CAPWAP_WTP_EVENT_REQUEST(type 9) in CAPWAP state: Image Data(10).&lt;BR /&gt;Feb 6 00:22:50 kernel: [*02/06/2026 03:22:50.1870] Discarding msg CAPWAP_WTP_EVENT_REQUEST(type 9) in CAPWAP state: Image Data(10).&lt;BR /&gt;Feb 6 00:23:21 kernel: [*02/06/2026 03:23:21.8660] Discarding msg CAPWAP_WTP_EVENT_REQUEST(type 9) in CAPWAP state: Image Data(10).&lt;BR /&gt;Feb 6 00:23:37 kernel: [*02/06/2026 03:23:37.6460] Re-Tx Count=1, Max Re-Tx Value=5, SendSeqNum=17, NumofPendingMsgs=1&lt;BR /&gt;Feb 6 00:23:37 kernel: [*02/06/2026 03:23:37.6460]&lt;BR /&gt;Feb 6 00:23:40 kernel: [*02/06/2026 03:23:40.4970] Re-Tx Count=2, Max Re-Tx Value=5, SendSeqNum=17, NumofPendingMsgs=1&lt;BR /&gt;Feb 6 00:23:40 kernel: [*02/06/2026 03:23:40.4970]&lt;BR /&gt;Feb 6 00:23:43 kernel: [*02/06/2026 03:23:43.3480] Re-Tx Count=3, Max Re-Tx Value=5, SendSeqNum=17, NumofPendingMsgs=1&lt;BR /&gt;Feb 6 00:23:43 kernel: [*02/06/2026 03:23:43.3480]&lt;BR /&gt;Feb 6 00:23:46 kernel: [*02/06/2026 03:23:46.1980] Re-Tx Count=4, Max Re-Tx Value=5, SendSeqNum=17, NumofPendingMsgs=1&lt;BR /&gt;Feb 6 00:23:46 kernel: [*02/06/2026 03:23:46.1980]&lt;BR /&gt;Feb 6 00:23:46 kernel: [*02/06/2026 03:23:46.5780] Image download interrupted for 30 seconds.&lt;BR /&gt;Feb 6 00:23:46 kernel: [*02/06/2026 03:23:46.5780]&lt;BR /&gt;Feb 6 00:23:46 kernel: [*02/06/2026 03:23:46.5780] Going to restart CAPWAP (reason : image download interrupted.)...&lt;BR /&gt;Feb 6 00:23:46 kernel: [*02/06/2026 03:23:46.5780]&lt;BR /&gt;Feb 6 00:23:46 kernel: [*02/06/2026 03:23:46.5780] Restarting CAPWAP State Machine.&lt;BR /&gt;Feb 6 00:23:46 kernel: [*02/06/2026 03:23:46.5790] OOBImageDnld: OOBImageDownloadTimer expired for image download..&lt;BR /&gt;Feb 6 00:23:46 kernel: [*02/06/2026 03:23:46.5790] OOBImageDnld: Do common error handler for OOB image download..&lt;BR /&gt;Feb 6 00:23:46 kernel: [*02/06/2026 03:23:46.5860] systemd[1]: Starting dhcpv6 client watcher...&lt;BR /&gt;Feb 6 00:23:46 kernel: [*02/06/2026 03:23:46.6170] OOBImageDnld: OOBImageDownloadTimer expired for image download..&lt;BR /&gt;Feb 6 00:23:46 kernel: [*02/06/2026 03:23:46.6170] OOBImageDnld: Do common error handler for OOB image download..&lt;BR /&gt;Feb 6 00:23:46 kernel: [*02/06/2026 03:23:46.6170] systemd[1]: Stopping DHCPv6 client...&lt;BR /&gt;Feb 6 00:23:46 kernel: [*02/06/2026 03:23:46.6250] systemd[1]: Starting DHCPv6 client...&lt;BR /&gt;Feb 6 00:23:46 kernel: [*02/06/2026 03:23:46.6510]&lt;BR /&gt;Feb 6 00:23:46 kernel: [*02/06/2026 03:23:46.6510] CAPWAP State: DTLS Teardown&lt;BR /&gt;Feb 6 00:23:46 kernel: [*02/06/2026 03:23:46.6700] Terminating image download(0x0): Dtls cleanup, ap1g7&lt;BR /&gt;Feb 6 00:23:46 kernel: [*02/06/2026 03:23:46.6760] systemd[1]: Started DHCPv6 client.&lt;BR /&gt;Feb 6 00:23:46 kernel: [*02/06/2026 03:23:46.6820] OOBImageDnld: Do common error handler for OOB image download..&lt;BR /&gt;Feb 6 00:23:46 kernel: [*02/06/2026 03:23:46.7030] systemd[1]: Started dhcpv6 client watcher.&lt;BR /&gt;Feb 6 03:23:46 upgrade: Script called with args:[CANCEL]&lt;BR /&gt;Feb 6 00:23:46 kernel: [*02/06/2026 03:23:46.7690] status 'upgrade.sh: Script called with args:[CANCEL]'&lt;BR /&gt;Feb 6 03:23:46 upgrade: Cleanup tmp files ...&lt;BR /&gt;Feb 6 00:23:46 kernel: [02/06/2026 03:23:46.7990] audit_log_lost: 36 callbacks suppressed&lt;BR /&gt;Feb 6 00:23:46 kernel: [02/06/2026 03:23:46.8770] audit: audit_lost=47 audit_rate_limit=100 audit_backlog_limit=8192&lt;BR /&gt;Feb 6 00:23:46 kernel: [*02/06/2026 03:23:46.8170] do CANCEL, part2 is active part&lt;BR /&gt;Feb 6 00:23:46 kernel: [*02/06/2026 03:23:46.8420] status 'upgrade.sh: Cleanup tmp files ...'&lt;BR /&gt;Feb 6 00:23:46 kernel: [*02/06/2026 03:23:46.8680] Discarding msg CAPWAP_IMAGE_DATA_REQUEST(type 15) in CAPWAP state: DTLS Teardown(4).&lt;BR /&gt;Feb 6 00:23:46 kernel: [*02/06/2026 03:23:46.8680] Image Data Request sent to x.x.x.x, fileName [ap1g7], replicaStatus 0&lt;BR /&gt;Feb 6 00:23:46 kernel: [*02/06/2026 03:23:46.8680] Discarding msg CAPWAP_WTP_EVENT_REQUEST(type 9) in CAPWAP state: DTLS Teardown(4).&lt;BR /&gt;Feb 6 00:23:46 kernel: [*02/06/2026 03:23:46.8680] Discarding msg CAPWAP_WTP_EVENT_REQUEST(type 9) in CAPWAP state: DTLS Teardown(4).&lt;BR /&gt;Feb 6 00:23:47 kernel: [02/06/2026 03:23:46.9760] audit: rate limit exceeded&lt;BR /&gt;Feb 6 00:23:51 kernel: [*02/06/2026 03:23:51.3630] OOBImageDnld: OOBImageDownloadTimer expired for image download..&lt;BR /&gt;Feb 6 00:23:51 kernel: [*02/06/2026 03:23:51.3630] OOBImageDnld: Do common error handler for OOB image download..&lt;BR /&gt;Feb 6 00:23:51 kernel: [*02/06/2026 03:23:51.3800] Terminating image download(0x0): Dtl session deleted, ap1g7&lt;BR /&gt;Feb 6 00:23:51 kernel: [*02/06/2026 03:23:51.3890] OOBImageDnld: Do common error handler for OOB image download..&lt;BR /&gt;Feb 6 03:23:51 upgrade: Script called with args:[CANCEL]&lt;BR /&gt;Feb 6 00:23:51 kernel: [*02/06/2026 03:23:51.4670] status 'upgrade.sh: Script called with args:[CANCEL]'&lt;BR /&gt;Feb 6 00:23:51 kernel: [*02/06/2026 03:23:51.5110] do CANCEL, part2 is active part&lt;BR /&gt;Feb 6 03:23:51 upgrade: Cleanup tmp files ...&lt;BR /&gt;Feb 6 00:23:51 kernel: [*02/06/2026 03:23:51.5290] status 'upgrade.sh: Cleanup tmp files ...'&lt;BR /&gt;Feb 6 00:23:51 kernel: [*02/06/2026 03:23:51.5550] dtls_queue_first: Nothing to extract!&lt;BR /&gt;Feb 6 00:23:51 kernel: [*02/06/2026 03:23:51.5550]&lt;BR /&gt;Feb 6 00:23:52 kernel: [*02/06/2026 03:23:52.5560] ipv6 gw config loop in Ac discovery&lt;BR /&gt;Feb 6 00:23:54 kernel: [*02/06/2026 03:23:54.5560] ipv6 gw config loop in Ac discovery&lt;BR /&gt;Feb 6 00:23:56 kernel: [*02/06/2026 03:23:56.5560] ipv6 gw config loop in Ac discovery&lt;BR /&gt;Feb 6 00:23:58 kernel: [*02/06/2026 03:23:58.5560] ipv6 gw config loop in Ac discovery&lt;BR /&gt;Feb 6 00:24:00 kernel: [*02/06/2026 03:24:00.5570] ipv6 gw config loop in Ac discovery&lt;BR /&gt;Feb 6 00:24:01 kernel: [*02/06/2026 03:24:01.5660]&lt;BR /&gt;Feb 6 00:24:01 kernel: [*02/06/2026 03:24:01.5660] CAPWAP State: Discovery&lt;BR /&gt;Feb 6 00:24:01 kernel: [*02/06/2026 03:24:01.5660] Got WLC address x.x.x.x from DHCP.&lt;BR /&gt;Feb 6 00:24:01 kernel: [*02/06/2026 03:24:01.5670] IP DNS query for CISCO-CAPWAP-CONTROLLER.cc.itu.edu.tr&lt;BR /&gt;Feb 6 00:24:01 kernel: [*02/06/2026 03:24:01.5680] systemd[1]: Starting dhcpv6 client watcher...&lt;BR /&gt;Feb 6 00:24:01 kernel: [*02/06/2026 03:24:01.5750] Discovery Request sent to x.x.x.x, discovery type STATIC_CONFIG(1)&lt;BR /&gt;Feb 6 00:24:01 kernel: [*02/06/2026 03:24:01.5820] Discovery Request sent to x.x.x.x, discovery type STATIC_CONFIG(1)&lt;BR /&gt;Feb 6 00:24:01 kernel: [*02/06/2026 03:24:01.5840] Discovery Request sent to x.x.x.x, discovery type STATIC_CONFIG(1)&lt;BR /&gt;Feb 6 00:24:01 kernel: [*02/06/2026 03:24:01.5890] Discovery Request sent to 255.255.255.255, discovery type UNKNOWN(0)&lt;BR /&gt;Feb 6 00:24:01 kernel: [*02/06/2026 03:24:01.5890] Discovery Response from x.x.x.x&lt;BR /&gt;Feb 6 00:24:01 kernel: [*02/06/2026 03:24:01.5890] Discovery Response from x.x.x.x&lt;BR /&gt;Feb 6 00:24:01 kernel: [*02/06/2026 03:24:01.5920] systemd[1]: Stopping DHCPv6 client...&lt;BR /&gt;Feb 6 00:24:01 kernel: [*02/06/2026 03:24:01.5980] systemd[1]: Starting DHCPv6 client...&lt;BR /&gt;Feb 6 00:24:01 kernel: [*02/06/2026 03:24:01.6410] systemd[1]: Started DHCPv6 client.&lt;BR /&gt;Feb 6 00:24:01 kernel: [*02/06/2026 03:24:01.6610] systemd[1]: Started dhcpv6 client watcher.&lt;BR /&gt;Feb 6 00:24:10 kernel: [*02/06/2026 03:24:10.0000] Started wait dtls timer (60 sec)&lt;BR /&gt;Feb 6 00:24:10 kernel: [*02/06/2026 03:24:10.0060]&lt;BR /&gt;Feb 6 00:24:10 kernel: [*02/06/2026 03:24:10.0060] CAPWAP State: DTLS Setup&lt;BR /&gt;Feb 6 00:24:10 kernel: [*02/06/2026 03:24:10.0350] dtls_verify_server_cert: Controller certificate verification successful&lt;BR /&gt;Feb 6 00:24:10 kernel: [*02/06/2026 03:24:10.4120]&lt;BR /&gt;Feb 6 00:24:10 kernel: [*02/06/2026 03:24:10.4120] CAPWAP State: Join&lt;BR /&gt;Feb 6 00:24:11 kernel: [*02/06/2026 03:24:11.3180] OOBImageDnld: OOB Image Download in ap_cap_bitmask(2)&lt;BR /&gt;Feb 6 00:24:11 kernel: [*02/06/2026 03:24:11.3180] Sending Join request to x.x.x.x through port 5261, packet size 1376&lt;BR /&gt;Feb 6 00:24:11 kernel: [*02/06/2026 03:24:11.3220] Join Response from x.x.x.x, packet size 1397&lt;BR /&gt;Feb 6 00:24:11 kernel: [*02/06/2026 03:24:11.3220] AC accepted previous sent request with result code: 0&lt;BR /&gt;Feb 6 00:24:11 kernel: [*02/06/2026 03:24:11.3220] Received wlcType 0, timer 30&lt;BR /&gt;Feb 6 00:24:11 kernel: [*02/06/2026 03:24:11.3520]&lt;BR /&gt;Feb 6 00:24:11 kernel: [*02/06/2026 03:24:11.3520] CAPWAP State: Image Data&lt;BR /&gt;Feb 6 00:24:11 kernel: [*02/06/2026 03:24:11.3520] AP image version 17.9.5.205 backup 17.12.4.22, Controller 17.12.6.203&lt;BR /&gt;Feb 6 00:24:11 kernel: [*02/06/2026 03:24:11.3520] Version does not match.&lt;BR /&gt;Feb 6 00:24:11 kernel: [*02/06/2026 03:24:11.3520] Request to close the file..&lt;BR /&gt;Feb 6 00:24:11 kernel: [*02/06/2026 03:24:11.3530] wtpOpenImgFile: image file closed, dcb-&amp;gt;fd set to -1.&lt;BR /&gt;Feb 6 03:24:11 upgrade: Script called with args:[PRECHECK]&lt;BR /&gt;Feb 6 00:24:11 kernel: [*02/06/2026 03:24:11.3940] status 'upgrade.sh: Script called with args:[PRECHECK]'&lt;BR /&gt;Feb 6 00:24:11 kernel: [*02/06/2026 03:24:11.4370] do PRECHECK, part2 is active part&lt;BR /&gt;Feb 6 03:24:11 upgrade: Cleanup tmp files ...&lt;BR /&gt;Feb 6 00:24:11 kernel: [*02/06/2026 03:24:11.4510] status 'upgrade.sh: Cleanup tmp files ...'&lt;BR /&gt;Feb 6 03:24:11 upgrade: /tmp space: OK available 96392, required 50000&lt;BR /&gt;Feb 6 00:24:11 kernel: [*02/06/2026 03:24:11.5010] status 'upgrade.sh: /tmp space: OK available 96392, required 50000 '&lt;BR /&gt;Feb 6 00:24:11 kernel: [*02/06/2026 03:24:11.5010] wtpOpenImgFile: request ap1g7, local /tmp/part.tar&lt;BR /&gt;Feb 6 00:24:11 kernel: [*02/06/2026 03:24:11.5010] wtpOpenImgFile: open (/tmp/part.tar) image file success&lt;BR /&gt;Feb 6 00:24:11 kernel: [*02/06/2026 03:24:11.5020] Using fd(367570649088) for image writing to file(/tmp/part.tar)&lt;BR /&gt;Feb 6 00:24:11 kernel: [*02/06/2026 03:24:11.5030] Image Data Request sent to x.x.x.x, fileName [ap1g7], replicaStatus 1&lt;BR /&gt;Feb 6 00:24:11 kernel: [*02/06/2026 03:24:11.5040] Image Data Response from x.x.x.x&lt;BR /&gt;Feb 6 00:24:11 kernel: [*02/06/2026 03:24:11.5040] AC accepted previous sent request with result code: 0&lt;BR /&gt;Feb 6 00:24:15 kernel: [*02/06/2026 03:24:14.0170] .Discarding msg CAPWAP_WTP_EVENT_REQUEST(type 9) in CAPWAP state: Image Data(10).&lt;BR /&gt;Feb 6 00:25:09 kernel: [*02/06/2026 03:24:18.1650] ...Discarding msg CAPWAP_WTP_EVENT_REQUEST(type 9) in CAPWAP state: Image Data(10).&lt;BR /&gt;Feb 6 00:25:48 kernel: [*02/06/2026 03:25:30.0230] .Discarding msg CAPWAP_WTP_EVENT_REQUEST(type 9) in CAPWAP state: Image Data(10).&lt;BR /&gt;Feb 6 00:25:49 kernel: [*02/06/2026 03:25:49.2480] Discarding msg CAPWAP_WTP_EVENT_REQUEST(type 9) in CAPWAP state: Image Data(10).&lt;BR /&gt;Feb 6 00:26:05 kernel: [*02/06/2026 03:26:05.3500] Invalid event 58 &amp;amp; state 10 combination.&lt;BR /&gt;Feb 6 00:26:05 kernel: [*02/06/2026 03:26:05.3500] SM handler: Failed to process timer message. Event 58, state 10&lt;BR /&gt;Feb 6 00:26:05 kernel: [*02/06/2026 03:26:05.3500] Failed to handle timer message.&lt;BR /&gt;Feb 6 00:26:05 kernel: [*02/06/2026 03:26:05.3500] FSM failure while processing message with id: 1&lt;BR /&gt;Feb 6 00:26:08 kernel: [*02/06/2026 03:26:06.0500] .Discarding msg CAPWAP_WTP_EVENT_REQUEST(type 9) in CAPWAP state: Image Data(10).&lt;BR /&gt;Feb 6 00:26:59 kernel: [*02/06/2026 03:26:46.0240] .Discarding msg CAPWAP_WTP_EVENT_REQUEST(type 9) in CAPWAP state: Image Data(10).&lt;BR /&gt;Feb 6 00:27:51 kernel: [*02/06/2026 03:27:18.0780] ..Discarding msg CAPWAP_WTP_EVENT_REQUEST(type 9) in CAPWAP state: Image Data(10).&lt;BR /&gt;Feb 6 00:28:46 kernel: [*02/06/2026 03:27:54.0420] ..Discarding msg CAPWAP_WTP_EVENT_REQUEST(type 9) in CAPWAP state: Image Data(10).&lt;BR /&gt;Feb 6 00:28:48 kernel: [*02/06/2026 03:28:48.1010] Discarding msg CAPWAP_WTP_EVENT_REQUEST(type 9) in CAPWAP state: Image Data(10).&lt;BR /&gt;Feb 6 00:28:49 kernel: [*02/06/2026 03:28:49.2490] Discarding msg CAPWAP_WTP_EVENT_REQUEST(type 9) in CAPWAP state: Image Data(10).&lt;BR /&gt;Feb 6 00:29:44 kernel: [*02/06/2026 03:28:58.0270] ..Discarding msg CAPWAP_WTP_EVENT_REQUEST(type 9) in CAPWAP state: Image Data(10).&lt;BR /&gt;Feb 6 00:30:32 kernel: [*02/06/2026 03:30:22.0450] .Discarding msg CAPWAP_WTP_EVENT_REQUEST(type 9) in CAPWAP state: Image Data(10).&lt;BR /&gt;Feb 6 00:31:23 kernel: [*02/06/2026 03:31:10.1010] .Discarding msg CAPWAP_WTP_EVENT_REQUEST(type 9) in CAPWAP state: Image Data(10).&lt;BR /&gt;Feb 6 00:31:48 kernel: [*02/06/2026 03:31:46.0880] .Discarding msg CAPWAP_WTP_EVENT_REQUEST(type 9) in CAPWAP state: Image Data(10).&lt;BR /&gt;Feb 6 00:31:49 kernel: [*02/06/2026 03:31:49.2490] Discarding msg CAPWAP_WTP_EVENT_REQUEST(type 9) in CAPWAP state: Image Data(10).&lt;BR /&gt;Feb 6 00:32:18 kernel: [*02/06/2026 03:32:18.1430] Discarding msg CAPWAP_WTP_EVENT_REQUEST(type 9) in CAPWAP state: Image Data(10).&lt;BR /&gt;Feb 6 00:33:09 kernel: [*02/06/2026 03:32:22.0450] .Discarding msg CAPWAP_WTP_EVENT_REQUEST(type 9) in CAPWAP state: Image Data(10).&lt;BR /&gt;Feb 6 00:34:02 kernel: [*02/06/2026 03:33:10.0480] ..Discarding msg CAPWAP_WTP_EVENT_REQUEST(type 9) in CAPWAP state: Image Data(10).&lt;BR /&gt;Feb 6 00:34:48 kernel: [*02/06/2026 03:34:34.1210] .Discarding msg CAPWAP_WTP_EVENT_REQUEST(type 9) in CAPWAP state: Image Data(10).&lt;BR /&gt;Feb 6 00:34:49 kernel: [*02/06/2026 03:34:49.2490] Discarding msg CAPWAP_WTP_EVENT_REQUEST(type 9) in CAPWAP state: Image Data(10).&lt;BR /&gt;Feb 6 00:35:01 kernel: [*02/06/2026 03:35:01.3880] Discarding msg CAPWAP_WTP_EVENT_REQUEST(type 9) in CAPWAP state: Image Data(10).&lt;/P&gt;</description>
      <pubDate>Fri, 06 Feb 2026 00:40:41 GMT</pubDate>
      <guid>https://community.cisco.com/t5/wireless/c91xx-series-ap-stuck-dowloading-state/m-p/5368021#M288494</guid>
      <dc:creator>pengus</dc:creator>
      <dc:date>2026-02-06T00:40:41Z</dc:date>
    </item>
    <item>
      <title>Re: C91xx series ap stuck dowloading state</title>
      <link>https://community.cisco.com/t5/wireless/c91xx-series-ap-stuck-dowloading-state/m-p/5368168#M288500</link>
      <description>&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;-&amp;nbsp;&lt;a href="https://community.cisco.com/t5/user/viewprofilepage/user-id/1263945"&gt;@pengus&lt;/a&gt;&amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp;&lt;STRONG&gt; &amp;nbsp;Power cycle&lt;/STRONG&gt; one of those problematic access points (start with one for starters) and check if&lt;BR /&gt;&amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp;that makes a difference ; usually when POE is used that can be done with a &lt;EM&gt;shutdown&lt;/EM&gt; followed&lt;BR /&gt;&amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp;by '&lt;EM&gt;no shutdown&lt;/EM&gt;' of the particular interface where the access point is connected to.&lt;/P&gt;
&lt;P&gt;&amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp;If it does not help look into :&amp;nbsp;&lt;A href="https://logadvisor.cisco.com/logadvisor/wireless/9800/9800APJoin" target="_blank"&gt;https://logadvisor.cisco.com/logadvisor/wireless/9800/9800APJoin&lt;/A&gt;&lt;/P&gt;
&lt;P&gt;&amp;nbsp; M.&lt;/P&gt;</description>
      <pubDate>Fri, 06 Feb 2026 13:28:29 GMT</pubDate>
      <guid>https://community.cisco.com/t5/wireless/c91xx-series-ap-stuck-dowloading-state/m-p/5368168#M288500</guid>
      <dc:creator>Mark Elsen</dc:creator>
      <dc:date>2026-02-06T13:28:29Z</dc:date>
    </item>
    <item>
      <title>Re: C91xx series ap stuck dowloading state</title>
      <link>https://community.cisco.com/t5/wireless/c91xx-series-ap-stuck-dowloading-state/m-p/5368176#M288501</link>
      <description>&lt;P&gt;This didn’t work. I was only able to rejoin the AP by changing its boot path via SSH. I configured the boot partition to 1/0 (different from the current path) and then reloaded the AP.&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Fri, 06 Feb 2026 13:41:54 GMT</pubDate>
      <guid>https://community.cisco.com/t5/wireless/c91xx-series-ap-stuck-dowloading-state/m-p/5368176#M288501</guid>
      <dc:creator>pengus</dc:creator>
      <dc:date>2026-02-06T13:41:54Z</dc:date>
    </item>
    <item>
      <title>Re: C91xx series ap stuck dowloading state</title>
      <link>https://community.cisco.com/t5/wireless/c91xx-series-ap-stuck-dowloading-state/m-p/5368186#M288503</link>
      <description>&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;&amp;nbsp; &amp;nbsp;-&amp;nbsp;&lt;a href="https://community.cisco.com/t5/user/viewprofilepage/user-id/1263945"&gt;@pengus&lt;/a&gt;&amp;nbsp; &amp;nbsp; &lt;EM&gt;Good work&lt;/EM&gt;, could you share the exact SSH commands which were used to accomplish that ?&lt;/P&gt;
&lt;P&gt;&amp;nbsp; M.&lt;/P&gt;</description>
      <pubDate>Fri, 06 Feb 2026 13:54:05 GMT</pubDate>
      <guid>https://community.cisco.com/t5/wireless/c91xx-series-ap-stuck-dowloading-state/m-p/5368186#M288503</guid>
      <dc:creator>Mark Elsen</dc:creator>
      <dc:date>2026-02-06T13:54:05Z</dc:date>
    </item>
    <item>
      <title>Re: C91xx series ap stuck dowloading state</title>
      <link>https://community.cisco.com/t5/wireless/c91xx-series-ap-stuck-dowloading-state/m-p/5368200#M288505</link>
      <description>&lt;P&gt;Hi,&lt;/P&gt;
&lt;P&gt;&lt;a href="https://community.cisco.com/t5/user/viewprofilepage/user-id/1263945"&gt;@pengus&lt;/a&gt;&amp;nbsp;Since it doesn't seem that you're hitting any of the following well-known unfortunate cases, even if you made it work, to ensure the AP is working as expected long-term and on next upgrade you don't run into same problem or even more serious challenges, I strongly suggest opening a TAC case:&lt;/P&gt;
&lt;P&gt;&lt;A href="https://www.cisco.com/c/en/us/support/docs/wireless/wireless-lan-controller-software/221869-safely-upgrade-access-points-avoiding-i.html" target="_blank"&gt;https://www.cisco.com/c/en/us/support/docs/wireless/wireless-lan-controller-software/221869-safely-upgrade-access-points-avoiding-i.html&lt;/A&gt;&lt;/P&gt;
&lt;P&gt;&lt;A href="https://www.cisco.com/c/en/us/support/docs/wireless/catalyst-9800-series-wireless-controllers/220443-how-to-avoid-boot-loop-due-to-corrupted.html" target="_blank"&gt;https://www.cisco.com/c/en/us/support/docs/wireless/catalyst-9800-series-wireless-controllers/220443-how-to-avoid-boot-loop-due-to-corrupted.html&lt;/A&gt;&lt;/P&gt;
&lt;P&gt;&lt;A href="https://bst.cloudapps.cisco.com/bugsearch/bug/CSCvr28291" target="_blank"&gt;https://bst.cloudapps.cisco.com/bugsearch/bug/CSCvr28291&lt;/A&gt;&lt;/P&gt;
&lt;P&gt;Also, recommend to perform some additional checks for the now functional AP's, using following:&lt;/P&gt;
&lt;P&gt;&lt;A href="https://www.cisco.com/c/en/us/support/docs/wireless/mobility-express-aironet-3800/225126-troubleshoot-cos-ap-boot-issues-and-ap.html" target="_blank"&gt;https://www.cisco.com/c/en/us/support/docs/wireless/mobility-express-aironet-3800/225126-troubleshoot-cos-ap-boot-issues-and-ap.html&lt;/A&gt;&lt;/P&gt;
&lt;P&gt;Thanks,&lt;/P&gt;
&lt;P&gt;Cristian.&lt;/P&gt;</description>
      <pubDate>Fri, 06 Feb 2026 14:25:17 GMT</pubDate>
      <guid>https://community.cisco.com/t5/wireless/c91xx-series-ap-stuck-dowloading-state/m-p/5368200#M288505</guid>
      <dc:creator>Cristian Matei</dc:creator>
      <dc:date>2026-02-06T14:25:17Z</dc:date>
    </item>
    <item>
      <title>Re: C91xx series ap stuck dowloading state</title>
      <link>https://community.cisco.com/t5/wireless/c91xx-series-ap-stuck-dowloading-state/m-p/5368216#M288506</link>
      <description>&lt;P&gt;Hi, you can use those step to repair it and put it back to your network.&lt;/P&gt;&lt;P&gt;&lt;A href="https://www.cisco.com/c/en/us/support/docs/wireless/catalyst-9120axi-access-point/217537-repairing-c9120-c9115-access-points-from.html" target="_blank"&gt;Repair C9120/C9115 Access Points from U-boot - Cisco&lt;/A&gt;&lt;/P&gt;</description>
      <pubDate>Fri, 06 Feb 2026 15:35:22 GMT</pubDate>
      <guid>https://community.cisco.com/t5/wireless/c91xx-series-ap-stuck-dowloading-state/m-p/5368216#M288506</guid>
      <dc:creator>HLB</dc:creator>
      <dc:date>2026-02-06T15:35:22Z</dc:date>
    </item>
    <item>
      <title>Re: C91xx series ap stuck dowloading state</title>
      <link>https://community.cisco.com/t5/wireless/c91xx-series-ap-stuck-dowloading-state/m-p/5368653#M288526</link>
      <description>&lt;P&gt;Actually, I performed the upgrade to avoid being affected by the CSCwf25731 and CSCwf37271 bugs. Although there was no explicit indication that the 9115 series access points were impacted, I still followed Option 1: Partition Swap in the document below. By doing so, the access points were able to rejoin successfully.&lt;BR /&gt;&lt;BR /&gt;&lt;A href="https://www.cisco.com/c/en/us/support/docs/wireless/wireless-lan-controller-software/225443-validate-and-recover-catalyst-aps-on.html" target="_blank"&gt;https://www.cisco.com/c/en/us/support/docs/wireless/wireless-lan-controller-software/225443-validate-and-recover-catalyst-aps-on.html&lt;/A&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Mon, 09 Feb 2026 08:52:17 GMT</pubDate>
      <guid>https://community.cisco.com/t5/wireless/c91xx-series-ap-stuck-dowloading-state/m-p/5368653#M288526</guid>
      <dc:creator>pengus</dc:creator>
      <dc:date>2026-02-09T08:52:17Z</dc:date>
    </item>
  </channel>
</rss>

