<?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: Weird APSP3 behavior with 17.15.3 in Wireless</title>
    <link>https://community.cisco.com/t5/wireless/weird-apsp3-behavior-with-17-15-3/m-p/5297630#M283954</link>
    <description>&lt;P&gt;You &lt;STRONG&gt;can&lt;/STRONG&gt; do APSP pre-download - after doing APSP install add - but only from CLI (not possible from GUI).&lt;BR /&gt;But agreed with Pat - you cannot install new image version and APSP at the same time.&lt;BR /&gt;APSP can only be installed after the new version is running.&lt;/P&gt;
&lt;P&gt;As to the original question I found that&amp;nbsp;add_activate_commit didn't work for APSP but that doing it in separate steps did?&lt;BR /&gt;Are you sure you were performing the same action in GUI&amp;nbsp;&lt;a href="https://community.cisco.com/t5/user/viewprofilepage/user-id/323352"&gt;@patoberli&lt;/a&gt;&amp;nbsp;?&lt;/P&gt;
&lt;P&gt;However that doesn't explain why your separate activate didn't work - that does look more like the corrupt install database problem.&amp;nbsp; Did you try the one-shot or separate steps after clearing the database?&lt;/P&gt;
&lt;P&gt;I've had trouble trying to manually delete the images folders before (lack of permissions) but install remove inactive does remove them.&amp;nbsp; But be careful - 17.15.x install remove inactive sometimes wants to delete your active running images!&amp;nbsp; I reported this in beta but they've not done anything about fixing it because I've seen the released images do exactly the same.&lt;/P&gt;
&lt;P&gt;This is a continuation of the saga of the dreadfully unreliable install script!&amp;nbsp; How difficult can it be?!!!&lt;/P&gt;
&lt;P&gt;ps: I've only installed APSP3 on 9800-80 so far as my lab 9800-CL is out of service while lab gets re-arranged (out of my control) so I haven't tested this on 9800-CL specifically.&lt;/P&gt;</description>
    <pubDate>Sun, 08 Jun 2025 16:24:25 GMT</pubDate>
    <dc:creator>Rich R</dc:creator>
    <dc:date>2025-06-08T16:24:25Z</dc:date>
    <item>
      <title>Weird APSP3 behavior with 17.15.3</title>
      <link>https://community.cisco.com/t5/wireless/weird-apsp3-behavior-with-17-15-3/m-p/5296061#M283805</link>
      <description>&lt;P&gt;Hi All&lt;/P&gt;&lt;P&gt;I'm running for testing a 9800-CL in VMware Workstation with 17.15.3 (initially installed with 17.9.6).&amp;nbsp;&lt;/P&gt;&lt;P&gt;There are no APs attached to it and just the absolute minimum configuration (web gui setup wizard, NTP and a valid user).&lt;/P&gt;&lt;P&gt;When I now try to install add file ... the APSP3 via CLI, I get an Error message shown in the wording like:&amp;nbsp;&lt;BR /&gt;&lt;SPAN&gt;%INSTALL-3-OPERATION_ERROR_MESSAGE: R0/0: install_mgr: Failed to install add package bootflash:/...SPA.bin, Error: No error or error string&lt;/SPAN&gt;&lt;BR /&gt;This error is only visible in the Console and not in "show install log" or "show logg".&amp;nbsp;&lt;/P&gt;&lt;P&gt;Via SSH I only get the error:&lt;BR /&gt;wlc-test#install add file bootflash:C9800-CL-universalk9.17.15.03.CSCwp18505.SPA.apsp.bin activate commit&lt;BR /&gt;install_add_activate_commit: START Tue Jun 03 07:24:59 Central 2025&lt;BR /&gt;install_add: START Tue Jun 03 07:24:59 Central 2025&lt;BR /&gt;install_add: Adding IMG&lt;BR /&gt;FAILED: add_activate_commit /bootflash/C9800-CL-universalk9.17.15.03.CSCwp18505.SPA.apsp.bin Tue Jun 03 07:25:16 Central 2025&lt;/P&gt;&lt;P&gt;Now to the very weird part. If I try exactly the same via Web GUI with the file already on the bootflash, it works fine without any error. Any ideas?&lt;BR /&gt;I tend to say it's somewhat connected with&amp;nbsp;&lt;A href="https://bst.cisco.com/bugsearch/bug/CSCwn42968?rfs=qvred," target="_blank" rel="noopener"&gt;https://bst.cisco.com/bugsearch/bug/CSCwn42968?rfs=qvred,&lt;/A&gt;&amp;nbsp;but the workaround didn't work, as I was unable to delete that directory:&lt;BR /&gt;wlc-test#delete /recu /for bootflash:/.images/&lt;BR /&gt;wlc-test#delete /rec bootflash:/.images/17.15.03.0.5635.1742971448&lt;BR /&gt;Delete filename [/.images/17.15.03.0.5635.1742971448]?&lt;BR /&gt;Examine files in directory bootflash:/.images/17.15.03.0.5635.1742971448? [confirm]&lt;BR /&gt;%Error deleting bootflash:/.images/17.15.03.0.5635.1742971448/C9800-CL-rpboot.17.15.03.SPA.pkg.lnk (No such file or directory)&lt;BR /&gt;wlc-test#&lt;/P&gt;&lt;P&gt;On a separate note, it's still not possible to add an APSP at the same time while doing an IOS XE upgrade?&lt;BR /&gt;So let's say, going from 17.9.5 -&amp;gt; 17.15.3 with APSP3 in one ap image pre-download instead of rebooting the APs after first 17.15.3 and then, after the WLC is upgraded, install APSP3?&lt;/P&gt;&lt;P&gt;Thanks&lt;BR /&gt;Patrick&lt;/P&gt;</description>
      <pubDate>Tue, 03 Jun 2025 07:41:13 GMT</pubDate>
      <guid>https://community.cisco.com/t5/wireless/weird-apsp3-behavior-with-17-15-3/m-p/5296061#M283805</guid>
      <dc:creator>patoberli</dc:creator>
      <dc:date>2025-06-03T07:41:13Z</dc:date>
    </item>
    <item>
      <title>Re: Weird APSP3 behavior with 17.15.3</title>
      <link>https://community.cisco.com/t5/wireless/weird-apsp3-behavior-with-17-15-3/m-p/5296077#M283807</link>
      <description>&lt;P&gt;Next time, try this:&amp;nbsp;&lt;/P&gt;
&lt;LI-CODE lang="markup"&gt;conf t
 service internal
end
clear install state&lt;/LI-CODE&gt;
&lt;P&gt;The last command will cause the WLC, router or switch to reboot.&amp;nbsp; After the reboot,&amp;nbsp;re-install the APSP/SMU again.&lt;/P&gt;</description>
      <pubDate>Tue, 03 Jun 2025 08:15:46 GMT</pubDate>
      <guid>https://community.cisco.com/t5/wireless/weird-apsp3-behavior-with-17-15-3/m-p/5296077#M283807</guid>
      <dc:creator>Leo Laohoo</dc:creator>
      <dc:date>2025-06-03T08:15:46Z</dc:date>
    </item>
    <item>
      <title>Re: Weird APSP3 behavior with 17.15.3</title>
      <link>https://community.cisco.com/t5/wireless/weird-apsp3-behavior-with-17-15-3/m-p/5296083#M283808</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/323352"&gt;@patoberli&lt;/a&gt;&amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp;You cannot combine APSP installation(s) with AP pre-image download&lt;/P&gt;
&lt;P&gt;&amp;nbsp;M.&lt;/P&gt;</description>
      <pubDate>Tue, 03 Jun 2025 08:38:30 GMT</pubDate>
      <guid>https://community.cisco.com/t5/wireless/weird-apsp3-behavior-with-17-15-3/m-p/5296083#M283808</guid>
      <dc:creator>Mark Elsen</dc:creator>
      <dc:date>2025-06-03T08:38:30Z</dc:date>
    </item>
    <item>
      <title>Re: Weird APSP3 behavior with 17.15.3</title>
      <link>https://community.cisco.com/t5/wireless/weird-apsp3-behavior-with-17-15-3/m-p/5296129#M283813</link>
      <description>&lt;P&gt;Might retry this again, I did create a snapshot while still on the initial 17.9.6 version. What I don't understand, why does it work in the web UI and not CLI.&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Tue, 03 Jun 2025 10:20:01 GMT</pubDate>
      <guid>https://community.cisco.com/t5/wireless/weird-apsp3-behavior-with-17-15-3/m-p/5296129#M283813</guid>
      <dc:creator>patoberli</dc:creator>
      <dc:date>2025-06-03T10:20:01Z</dc:date>
    </item>
    <item>
      <title>Re: Weird APSP3 behavior with 17.15.3</title>
      <link>https://community.cisco.com/t5/wireless/weird-apsp3-behavior-with-17-15-3/m-p/5296136#M283814</link>
      <description>&lt;P&gt;No go, even after doing the clear:&lt;/P&gt;&lt;PRE&gt;wlc-test#install add file bootflash:C9800-CL-universalk9.17.15.03.CSCwp18505.SPA.apsp.bin&lt;BR /&gt;install_add: START Tue Jun 03 10:46:44 Central 2025&lt;BR /&gt;install_add: Adding IMG&lt;BR /&gt;--- Starting initial file syncing ---&lt;BR /&gt;Copying bootflash:C9800-CL-universalk9.17.15.03.CSCwp18505.SPA.apsp.bin from Chassis 1/R0 to Chassis 1/R0&lt;BR /&gt;Info: Finished copying to the selected Chassis&lt;BR /&gt;Finished initial file syncing&lt;BR /&gt;&lt;BR /&gt;--- Starting SMU Add operation ---&lt;BR /&gt;Performing SMU_ADD on all members&lt;BR /&gt;Checking status of SMU_ADD on [1/R0]&lt;BR /&gt;SMU_ADD: Passed on [1/R0]&lt;BR /&gt;Finished SMU Add operation&lt;BR /&gt;&lt;BR /&gt;SUCCESS: install_add /bootflash/C9800-CL-universalk9.17.15.03.CSCwp18505.SPA.apsp.bin Tue Jun 03 10:47:21 Central 2025&lt;BR /&gt;wlc-test#insta&lt;BR /&gt;wlc-test#install act&lt;BR /&gt;wlc-test#install activate&lt;BR /&gt;install_activate: START Tue Jun 03 10:47:31 Central 2025&lt;BR /&gt;install_activate: Activating IMG&lt;BR /&gt;Following packages shall be activated:&lt;BR /&gt;&lt;BR /&gt;This operation may require a reload of the system. Do you want to proceed? [y/n]y&lt;BR /&gt;&lt;BR /&gt;--- Starting Activate ---&lt;BR /&gt;Performing Activate on all members&lt;BR /&gt;[1] Failed Activate on Chassis 1/R0&lt;BR /&gt;Checking status of Activate on [1/R0]&lt;BR /&gt;Activate: Passed on []. Failed on [1/R0]&lt;BR /&gt;Finished Activate&lt;BR /&gt;&lt;BR /&gt;FAILED: install_activate Tue Jun 03 10:47:35 Central 2025&lt;BR /&gt;wlc-test#&lt;/PRE&gt;</description>
      <pubDate>Tue, 03 Jun 2025 10:48:56 GMT</pubDate>
      <guid>https://community.cisco.com/t5/wireless/weird-apsp3-behavior-with-17-15-3/m-p/5296136#M283814</guid>
      <dc:creator>patoberli</dc:creator>
      <dc:date>2025-06-03T10:48:56Z</dc:date>
    </item>
    <item>
      <title>Re: Weird APSP3 behavior with 17.15.3</title>
      <link>https://community.cisco.com/t5/wireless/weird-apsp3-behavior-with-17-15-3/m-p/5296138#M283815</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/323352"&gt;@patoberli&lt;/a&gt;&amp;nbsp; &amp;nbsp; &amp;nbsp; &lt;EM&gt;&amp;nbsp;&amp;gt;...&lt;/EM&gt;&lt;SPAN&gt;&lt;EM&gt;What I don't understand, why does it work in the web UI &lt;FONT color="#FF6600"&gt;and not &lt;STRONG&gt;CLI.&amp;nbsp;&lt;/STRONG&gt;&lt;/FONT&gt;&lt;/EM&gt;&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; You could for instance &lt;STRONG&gt;CLIcatcher&lt;/STRONG&gt; (applet) as explained in :&amp;nbsp;&lt;A href="https://goodwi.fi/posts/2025/01/find-9800-cli-cmd/" target="_blank"&gt;https://goodwi.fi/posts/2025/01/find-9800-cli-cmd/&lt;/A&gt;&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;&lt;STRONG&gt; &amp;nbsp; CLIcatcher&lt;/STRONG&gt; will log all CLI commands for GUI operations executed in the controller logs.&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;&lt;EM&gt; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp;You can the compare those&amp;nbsp; against your own CLI commands&lt;/EM&gt;&lt;/SPAN&gt;&lt;/P&gt;
&lt;P&gt;&lt;SPAN&gt;&amp;nbsp; M.&lt;/SPAN&gt;&lt;/P&gt;</description>
      <pubDate>Tue, 03 Jun 2025 10:55:08 GMT</pubDate>
      <guid>https://community.cisco.com/t5/wireless/weird-apsp3-behavior-with-17-15-3/m-p/5296138#M283815</guid>
      <dc:creator>Mark Elsen</dc:creator>
      <dc:date>2025-06-03T10:55:08Z</dc:date>
    </item>
    <item>
      <title>Re: Weird APSP3 behavior with 17.15.3</title>
      <link>https://community.cisco.com/t5/wireless/weird-apsp3-behavior-with-17-15-3/m-p/5297630#M283954</link>
      <description>&lt;P&gt;You &lt;STRONG&gt;can&lt;/STRONG&gt; do APSP pre-download - after doing APSP install add - but only from CLI (not possible from GUI).&lt;BR /&gt;But agreed with Pat - you cannot install new image version and APSP at the same time.&lt;BR /&gt;APSP can only be installed after the new version is running.&lt;/P&gt;
&lt;P&gt;As to the original question I found that&amp;nbsp;add_activate_commit didn't work for APSP but that doing it in separate steps did?&lt;BR /&gt;Are you sure you were performing the same action in GUI&amp;nbsp;&lt;a href="https://community.cisco.com/t5/user/viewprofilepage/user-id/323352"&gt;@patoberli&lt;/a&gt;&amp;nbsp;?&lt;/P&gt;
&lt;P&gt;However that doesn't explain why your separate activate didn't work - that does look more like the corrupt install database problem.&amp;nbsp; Did you try the one-shot or separate steps after clearing the database?&lt;/P&gt;
&lt;P&gt;I've had trouble trying to manually delete the images folders before (lack of permissions) but install remove inactive does remove them.&amp;nbsp; But be careful - 17.15.x install remove inactive sometimes wants to delete your active running images!&amp;nbsp; I reported this in beta but they've not done anything about fixing it because I've seen the released images do exactly the same.&lt;/P&gt;
&lt;P&gt;This is a continuation of the saga of the dreadfully unreliable install script!&amp;nbsp; How difficult can it be?!!!&lt;/P&gt;
&lt;P&gt;ps: I've only installed APSP3 on 9800-80 so far as my lab 9800-CL is out of service while lab gets re-arranged (out of my control) so I haven't tested this on 9800-CL specifically.&lt;/P&gt;</description>
      <pubDate>Sun, 08 Jun 2025 16:24:25 GMT</pubDate>
      <guid>https://community.cisco.com/t5/wireless/weird-apsp3-behavior-with-17-15-3/m-p/5297630#M283954</guid>
      <dc:creator>Rich R</dc:creator>
      <dc:date>2025-06-08T16:24:25Z</dc:date>
    </item>
  </channel>
</rss>

