<?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 2600 series boot problem upon controller upgrade in Wireless</title>
    <link>https://community.cisco.com/t5/wireless/2600-series-boot-problem-upon-controller-upgrade/m-p/2348907#M78884</link>
    <description>&lt;P&gt; - I recently (tried) upgrading a 5508-wlc&amp;nbsp; from release 7.4.100.0 to 7.4.110.0 ; which worked but some&lt;BR /&gt;2600 series ap could not boot. The following output was observed :&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;EM&gt;Ethernet speed is 1000 Mb - FULL Duplex&lt;/EM&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;EM&gt;Loading "flash:/ap3g2-k9w8-mx.152-2.JA1/ap3g2-k9w8-mx.152-2.JA1"...flash:/ap3g2-k9w8-mx.152-2.JA1/ap3g2-k9w8-mx.152-2.JA1: no such file or directory&lt;/EM&gt;&lt;/P&gt;&lt;P&gt;&lt;EM&gt; &lt;SPAN style="font-size: 10pt;"&gt;Error loading "flash:/ap3g2-k9w8-mx.152-2.JA1/ap3g2-k9w8-mx.152-2.JA1"&lt;/SPAN&gt;&lt;/EM&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;EM&gt;Loading "flash:/ap3g2-k9w8-mx.152-2.JB/ap3g2-k9w8-xx.152-2.JB"...uncompress: Unknown mzip segment type: 2&lt;/EM&gt;&lt;/P&gt;&lt;P&gt;&lt;EM&gt; &lt;SPAN style="font-size: 10pt;"&gt;Error loading "flash:/ap3g2-k9w8-mx.152-2.JB/ap3g2-k9w8-xx.152-2.JB"&lt;/SPAN&gt;&lt;/EM&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;EM style="font-size: 10pt; "&gt;Interrupt within 5 seconds to abort boot process.&lt;/EM&gt;&lt;/P&gt;&lt;P&gt;&lt;EM style="font-size: 10pt; "&gt;Boot process failed...&lt;/EM&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt; &lt;SPAN style="font-size: 10pt;"&gt;If you manually boot :&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN style="font-size: 10pt;"&gt;flash:/ap3g2-k9w8-mx.152-2.JB/&lt;/SPAN&gt;&lt;STRONG style="font-size: 10pt;"&gt;ap3g2-k9w8-mx.152-2.JB&lt;/STRONG&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN style="font-size: 10pt;"&gt;then the AP can boot, Note the subtle difference in the image names :&amp;nbsp; &lt;/SPAN&gt;&lt;STRONG style="font-size: 10pt;"&gt; &lt;/STRONG&gt;&lt;SPAN style="font-size: 10pt;"&gt;ap3g2-k9w8-&lt;/SPAN&gt;&lt;SPAN style="text-decoration: underline;"&gt;mx&lt;/SPAN&gt;&lt;SPAN style="font-size: 10pt;"&gt;.152-2.JB versus ap3g2-k9w8-&lt;/SPAN&gt;&lt;SPAN style="text-decoration: underline;"&gt;xx&lt;/SPAN&gt;&lt;SPAN style="font-size: 10pt;"&gt;.152-2.JB&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Anyone else seen such issues, it's harsh because the AP needs to be serviced from FAB-locations. Simply power cycling does not&lt;BR /&gt;help and console access is needed. Are there any subtle tricks to get the AP sooner online ... ?&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;M. &lt;/P&gt;</description>
    <pubDate>Sun, 04 Jul 2021 07:41:22 GMT</pubDate>
    <dc:creator>Mark Elsen</dc:creator>
    <dc:date>2021-07-04T07:41:22Z</dc:date>
    <item>
      <title>2600 series boot problem upon controller upgrade</title>
      <link>https://community.cisco.com/t5/wireless/2600-series-boot-problem-upon-controller-upgrade/m-p/2348907#M78884</link>
      <description>&lt;P&gt; - I recently (tried) upgrading a 5508-wlc&amp;nbsp; from release 7.4.100.0 to 7.4.110.0 ; which worked but some&lt;BR /&gt;2600 series ap could not boot. The following output was observed :&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;EM&gt;Ethernet speed is 1000 Mb - FULL Duplex&lt;/EM&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;EM&gt;Loading "flash:/ap3g2-k9w8-mx.152-2.JA1/ap3g2-k9w8-mx.152-2.JA1"...flash:/ap3g2-k9w8-mx.152-2.JA1/ap3g2-k9w8-mx.152-2.JA1: no such file or directory&lt;/EM&gt;&lt;/P&gt;&lt;P&gt;&lt;EM&gt; &lt;SPAN style="font-size: 10pt;"&gt;Error loading "flash:/ap3g2-k9w8-mx.152-2.JA1/ap3g2-k9w8-mx.152-2.JA1"&lt;/SPAN&gt;&lt;/EM&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;EM&gt;Loading "flash:/ap3g2-k9w8-mx.152-2.JB/ap3g2-k9w8-xx.152-2.JB"...uncompress: Unknown mzip segment type: 2&lt;/EM&gt;&lt;/P&gt;&lt;P&gt;&lt;EM&gt; &lt;SPAN style="font-size: 10pt;"&gt;Error loading "flash:/ap3g2-k9w8-mx.152-2.JB/ap3g2-k9w8-xx.152-2.JB"&lt;/SPAN&gt;&lt;/EM&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;EM style="font-size: 10pt; "&gt;Interrupt within 5 seconds to abort boot process.&lt;/EM&gt;&lt;/P&gt;&lt;P&gt;&lt;EM style="font-size: 10pt; "&gt;Boot process failed...&lt;/EM&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt; &lt;SPAN style="font-size: 10pt;"&gt;If you manually boot :&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN style="font-size: 10pt;"&gt;flash:/ap3g2-k9w8-mx.152-2.JB/&lt;/SPAN&gt;&lt;STRONG style="font-size: 10pt;"&gt;ap3g2-k9w8-mx.152-2.JB&lt;/STRONG&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN style="font-size: 10pt;"&gt;then the AP can boot, Note the subtle difference in the image names :&amp;nbsp; &lt;/SPAN&gt;&lt;STRONG style="font-size: 10pt;"&gt; &lt;/STRONG&gt;&lt;SPAN style="font-size: 10pt;"&gt;ap3g2-k9w8-&lt;/SPAN&gt;&lt;SPAN style="text-decoration: underline;"&gt;mx&lt;/SPAN&gt;&lt;SPAN style="font-size: 10pt;"&gt;.152-2.JB versus ap3g2-k9w8-&lt;/SPAN&gt;&lt;SPAN style="text-decoration: underline;"&gt;xx&lt;/SPAN&gt;&lt;SPAN style="font-size: 10pt;"&gt;.152-2.JB&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Anyone else seen such issues, it's harsh because the AP needs to be serviced from FAB-locations. Simply power cycling does not&lt;BR /&gt;help and console access is needed. Are there any subtle tricks to get the AP sooner online ... ?&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;M. &lt;/P&gt;</description>
      <pubDate>Sun, 04 Jul 2021 07:41:22 GMT</pubDate>
      <guid>https://community.cisco.com/t5/wireless/2600-series-boot-problem-upon-controller-upgrade/m-p/2348907#M78884</guid>
      <dc:creator>Mark Elsen</dc:creator>
      <dc:date>2021-07-04T07:41:22Z</dc:date>
    </item>
    <item>
      <title>Re: 2600 series boot problem upon controller upgrade</title>
      <link>https://community.cisco.com/t5/wireless/2600-series-boot-problem-upon-controller-upgrade/m-p/2348908#M78885</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;The devices that could not boot share same part number with APs that worked correctly after the upgrade?&lt;/P&gt;&lt;P&gt;I think if you can just remove the bad image from the flash that may help. The AP will have only one image then on the flash from which it boots.&lt;/P&gt;&lt;P&gt;You can also try to rest the AP to factory default from the WLC and see if that helps.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;HTH&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Amjad&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN style="color: blue;"&gt;Rating useful replies is more useful than saying &lt;SPAN style="color: green;"&gt; "&lt;SPAN style="text-decoration: underline;"&gt;Thank you&lt;/SPAN&gt;"&lt;/SPAN&gt;&lt;/SPAN&gt;&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Wed, 21 Aug 2013 11:13:53 GMT</pubDate>
      <guid>https://community.cisco.com/t5/wireless/2600-series-boot-problem-upon-controller-upgrade/m-p/2348908#M78885</guid>
      <dc:creator>Amjad Abdullah</dc:creator>
      <dc:date>2013-08-21T11:13:53Z</dc:date>
    </item>
    <item>
      <title>Re: 2600 series boot problem upon controller upgrade</title>
      <link>https://community.cisco.com/t5/wireless/2600-series-boot-problem-upon-controller-upgrade/m-p/2348909#M78886</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Well if the AP's can't boot and join the wlc, then you are really in a bad spot. You would have to console into the AP and make the changes.&lt;BR /&gt;&lt;BR /&gt;Sent from Cisco Technical Support iPhone App&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Wed, 21 Aug 2013 12:23:36 GMT</pubDate>
      <guid>https://community.cisco.com/t5/wireless/2600-series-boot-problem-upon-controller-upgrade/m-p/2348909#M78886</guid>
      <dc:creator>Scott Fella</dc:creator>
      <dc:date>2013-08-21T12:23:36Z</dc:date>
    </item>
    <item>
      <title>2600 series boot problem upon controller upgrade</title>
      <link>https://community.cisco.com/t5/wireless/2600-series-boot-problem-upon-controller-upgrade/m-p/2348910#M78887</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt; - True, what interests me more, is how did the ap ever get into this 'configuration' ; I would like to avoid it&lt;/P&gt;&lt;P&gt;for future ap resets (let alone upgrades).&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Marc.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Wed, 21 Aug 2013 13:03:09 GMT</pubDate>
      <guid>https://community.cisco.com/t5/wireless/2600-series-boot-problem-upon-controller-upgrade/m-p/2348910#M78887</guid>
      <dc:creator>Mark Elsen</dc:creator>
      <dc:date>2013-08-21T13:03:09Z</dc:date>
    </item>
    <item>
      <title>2600 series boot problem upon controller upgrade</title>
      <link>https://community.cisco.com/t5/wireless/2600-series-boot-problem-upon-controller-upgrade/m-p/2348911#M78888</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Depends... could be a corrupt image on the WLC base code or if you did a pre image upload to the ap that might of caused it also.&amp;nbsp; If you didn't do a pre image upload, maybe that is something you need to test and then when the code is uploaded to the AP, you can verify that the image is in flash.&amp;nbsp; If this happens to all 2600 ap's, maybe you need to upload the firmware on the WLC again as the code has the specific image for the 2600.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Thanks, &lt;BR /&gt; &lt;BR /&gt;Scott &lt;BR /&gt; &lt;BR /&gt;Help out other by using the rating system and marking answered questions as "Answered"&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Wed, 21 Aug 2013 13:33:57 GMT</pubDate>
      <guid>https://community.cisco.com/t5/wireless/2600-series-boot-problem-upon-controller-upgrade/m-p/2348911#M78888</guid>
      <dc:creator>Scott Fella</dc:creator>
      <dc:date>2013-08-21T13:33:57Z</dc:date>
    </item>
    <item>
      <title>2600 series boot problem upon controller upgrade</title>
      <link>https://community.cisco.com/t5/wireless/2600-series-boot-problem-upon-controller-upgrade/m-p/2348912#M78889</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt; I did do some image pre-loading in the past. It could be related to this activity. It then remains to be seen&lt;BR /&gt;wether the problem, in the end,could be tracked to a cisco bug or some mis-activity on my part. As you point out it would&lt;/P&gt;&lt;P&gt;be very harsh to trace back, when and how the ap got into this state. For the moment I 'repair'(ed) the ap&lt;/P&gt;&lt;P&gt;by manually booting the correct image.Also afterwards a controller upgrade was executed which downloads&lt;/P&gt;&lt;P&gt;a new image to the AP and then the boot var is being set correctly for new boots,(by the upgrade process).&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; Hence the AP can again operate after resets (too).&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Marc.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Thu, 22 Aug 2013 05:26:02 GMT</pubDate>
      <guid>https://community.cisco.com/t5/wireless/2600-series-boot-problem-upon-controller-upgrade/m-p/2348912#M78889</guid>
      <dc:creator>Mark Elsen</dc:creator>
      <dc:date>2013-08-22T05:26:02Z</dc:date>
    </item>
    <item>
      <title>2600 series boot problem upon controller upgrade</title>
      <link>https://community.cisco.com/t5/wireless/2600-series-boot-problem-upon-controller-upgrade/m-p/2348913#M78890</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;I've seen this before.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;My only choice was to delete the full IOS.&amp;nbsp;&amp;nbsp; In your case, "delete /f /r flash:/ap3g2-k9w8-mx.152-2.JB" and get the AP to download the IOS again.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Thu, 22 Aug 2013 05:32:53 GMT</pubDate>
      <guid>https://community.cisco.com/t5/wireless/2600-series-boot-problem-upon-controller-upgrade/m-p/2348913#M78890</guid>
      <dc:creator>Leo Laohoo</dc:creator>
      <dc:date>2013-08-22T05:32:53Z</dc:date>
    </item>
    <item>
      <title>2600 series boot problem upon controller upgrade</title>
      <link>https://community.cisco.com/t5/wireless/2600-series-boot-problem-upon-controller-upgrade/m-p/2348914#M78891</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt; How is the latter (get the AP to download the IOS again) achieved&amp;nbsp; when all local OS IOS are deleted ?&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;M.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Thu, 22 Aug 2013 05:42:39 GMT</pubDate>
      <guid>https://community.cisco.com/t5/wireless/2600-series-boot-problem-upon-controller-upgrade/m-p/2348914#M78891</guid>
      <dc:creator>Mark Elsen</dc:creator>
      <dc:date>2013-08-22T05:42:39Z</dc:date>
    </item>
    <item>
      <title>2600 series boot problem upon controller upgrade</title>
      <link>https://community.cisco.com/t5/wireless/2600-series-boot-problem-upon-controller-upgrade/m-p/2348915#M78892</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;PRE __jive_macro_name="quote" class="jive_text_macro jive_macro_quote"&gt;How is the latter (get the AP to download the IOS again) achieved&amp;nbsp; when all local OS IOS are deleted ?&lt;/PRE&gt;&lt;P&gt;Hold on.&amp;nbsp; I never recommended you delete ALL the IOS.&amp;nbsp; My recommendation is to delete the FULL IOS by using the command&amp;nbsp; "delete /f /r flash:/ap3g2-k9w8-mx.152-2.JB". &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;This leaves, hopefully, the "rcv" directory in place so when you reboot the AP, the AP will contact the WLC and download again the full IOS.&amp;nbsp; &lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Thu, 22 Aug 2013 06:01:49 GMT</pubDate>
      <guid>https://community.cisco.com/t5/wireless/2600-series-boot-problem-upon-controller-upgrade/m-p/2348915#M78892</guid>
      <dc:creator>Leo Laohoo</dc:creator>
      <dc:date>2013-08-22T06:01:49Z</dc:date>
    </item>
    <item>
      <title>2600 series boot problem upon controller upgrade</title>
      <link>https://community.cisco.com/t5/wireless/2600-series-boot-problem-upon-controller-upgrade/m-p/2348916#M78893</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt; Ok, good to know. &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Wouldn't it be handy to let the AP always download the OS from the controller&lt;/P&gt;&lt;P&gt;upon boot (and reset). This would avoid such problems and kind of enforce an&lt;STRONG&gt; always-sync&lt;/STRONG&gt; state with&lt;/P&gt;&lt;P&gt;the controller. Also argumenting that for instance nowadays with the upcoming of for instance the 3780 which&lt;/P&gt;&lt;P&gt;can be both a switch and a controller (avoiding overloaded network-cap-wap-paths). This may become an even more&lt;/P&gt;&lt;P&gt;feasible or 'practical'&amp;nbsp; solution in the future ?&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;M.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Thu, 22 Aug 2013 07:28:28 GMT</pubDate>
      <guid>https://community.cisco.com/t5/wireless/2600-series-boot-problem-upon-controller-upgrade/m-p/2348916#M78893</guid>
      <dc:creator>Mark Elsen</dc:creator>
      <dc:date>2013-08-22T07:28:28Z</dc:date>
    </item>
  </channel>
</rss>

