<?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: Can't set 1700 CAP to Autonomous once WLC has Provisioned it in Wireless</title>
    <link>https://community.cisco.com/t5/wireless/can-t-set-1700-cap-to-autonomous-once-wlc-has-provisioned-it/m-p/3343498#M105253</link>
    <description>&lt;P&gt;Thanks Flavio.&amp;nbsp; However, I am curious as to whether or not my AP was just shipped to me without the proper unified firmware on it, or if the WLC auto provisioning it once it was connected to the network removed some kind of one-time flag that lets you toggle between CAP or SAP. For example, when I set a 1702 to boot into autonomous mode, I can't boot it back to lightweight mode. So I am wondering if you let a WLC provision your CAP in it's default mode, is that action what makes it so you can no longer boot into autonomous mode or is it coincidence?&lt;/P&gt;
&lt;P&gt;Basically I told them not to plug it into the network for this very reason and it looks like they did it anyway. So I am trying to figure out if&amp;nbsp;this is a self-inflicted injury or if I need to tell my vendor they gave me the wrong firmware.&amp;nbsp;&lt;/P&gt;</description>
    <pubDate>Tue, 06 Mar 2018 19:01:21 GMT</pubDate>
    <dc:creator>Dean Romanelli</dc:creator>
    <dc:date>2018-03-06T19:01:21Z</dc:date>
    <item>
      <title>Can't set 1700 CAP to Autonomous once WLC has Provisioned it</title>
      <link>https://community.cisco.com/t5/wireless/can-t-set-1700-cap-to-autonomous-once-wlc-has-provisioned-it/m-p/3343396#M105251</link>
      <description>&lt;P&gt;Hi All,&lt;/P&gt;
&lt;P&gt;I have an international site with a failed 1602 access point that I've instructed the local branch manager to replace with a Cisco 1702.&amp;nbsp; I have this site using AP's in autonomous mode - no WLC.&amp;nbsp; Whenever I field 1702's, the first thing I do is &lt;EM&gt;capwap ap autonomous &lt;/EM&gt;to force the unified image to load standalone IOS.&lt;/P&gt;
&lt;P&gt;However, when this new AP arrived, they took it to their head office about 5 minutes up the street, which is a different site that has a WLC and lightweight CAP's.&amp;nbsp; They plugged it into the network for POE, ran a console cable from it to a PC, started Teamviewer and told me it is ready for configuration and that once I was finished they would take it over to the other site to replace the failed unit.&lt;/P&gt;
&lt;P&gt;When I got onto the PC and consoled into the AP, I found that the WLC took the liberty of provisioning the AP as one of it's own, since it was on the network, and now I cannot convert the image to autonomous mode.&lt;/P&gt;
&lt;P&gt;&lt;EM&gt;AP3890.a5d0.9440#capwap ap auton&lt;/EM&gt;&lt;/P&gt;
&lt;P&gt;&lt;EM&gt;Convert to Autonomous image. Proceed? (yes/[no]): yes&lt;/EM&gt;&lt;/P&gt;
&lt;P&gt;&lt;EM&gt;No Autonomous image found! Conversion failed.&lt;/EM&gt;&lt;/P&gt;
&lt;P&gt;&lt;EM&gt;AP3890.a5d0.9440#show ver&lt;/EM&gt;&lt;BR /&gt;&lt;EM&gt;Cisco IOS Software, C1700 Software (AP3G2-K9W8-M), Version 15.3(3)JA4, RELEASE SOFTWARE (fc1)&lt;/EM&gt;&lt;BR /&gt;&lt;EM&gt;Technical Support: &lt;A href="http://www.cisco.com/techsupport" target="_blank"&gt;http://www.cisco.com/techsupport&lt;/A&gt;&lt;/EM&gt;&lt;BR /&gt;&lt;EM&gt;Copyright (c) 1986-2015 by Cisco Systems, Inc.&lt;/EM&gt;&lt;BR /&gt;&lt;EM&gt;Compiled Wed 01-Jul-15 18:19 by prod_rel_team&lt;/EM&gt;&lt;/P&gt;
&lt;P&gt;&lt;EM&gt;ROM: Bootstrap program is C1700 boot loader&lt;/EM&gt;&lt;BR /&gt;&lt;EM&gt;BOOTLDR: C1700 Boot Loader (AP3G2-BOOT-M) LoaderVersion 15.3() [ TRUE]&lt;/EM&gt;&lt;/P&gt;
&lt;P&gt;&lt;EM&gt;AP3890.a5d0.9440 uptime is 17 minutes&lt;/EM&gt;&lt;BR /&gt;&lt;EM&gt;System returned to ROM by power-on&lt;/EM&gt;&lt;BR /&gt;&lt;EM&gt;System image file is "flash:/ap3g2-k9w8-mx.153-3.JA4/ap3g2-k9w8-xx.153-3.JA4"&lt;/EM&gt;&lt;/P&gt;
&lt;P&gt;Is this because it's already been provisioned as a CAP and the "flag" that allows me to choose the mode is gone now? I know when I do capwap ap autonomous on a successful model that once it boots into autonomous mode I cannot set it back to lightweight mode, so I am wondering if the reverse is going on now or if it is a different problem?&lt;/P&gt;
&lt;P&gt;&lt;LI-WRAPPER&gt;&lt;/LI-WRAPPER&gt;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Mon, 05 Jul 2021 15:20:39 GMT</pubDate>
      <guid>https://community.cisco.com/t5/wireless/can-t-set-1700-cap-to-autonomous-once-wlc-has-provisioned-it/m-p/3343396#M105251</guid>
      <dc:creator>Dean Romanelli</dc:creator>
      <dc:date>2021-07-05T15:20:39Z</dc:date>
    </item>
    <item>
      <title>Re: Can't set 1700 CAP to Autonomous once WLC has Provisioned it</title>
      <link>https://community.cisco.com/t5/wireless/can-t-set-1700-cap-to-autonomous-once-wlc-has-provisioned-it/m-p/3343411#M105252</link>
      <description>&lt;P&gt;Hi&amp;nbsp;&lt;a href="https://community.cisco.com/t5/user/viewprofilepage/user-id/319845"&gt;@Dean Romanelli&lt;/a&gt;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;The process will may be not so simple but it is actually simple.&amp;nbsp; You need to have a TFTP server, which can be your own machine and a autonomous image:&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Console to the AP and issue:&lt;/P&gt;
&lt;P&gt;This command permit you to access conf t&lt;/P&gt;
&lt;P&gt;&lt;STRONG&gt;&lt;SPAN&gt;debug capwap console cli&lt;/SPAN&gt;&lt;SPAN&gt;&amp;nbsp;&lt;/SPAN&gt;&lt;/STRONG&gt;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;&lt;SPAN&gt;Add ip address and gateway to talk to a TFTP server:&lt;/SPAN&gt;&lt;/P&gt;
&lt;P&gt;&lt;SPAN&gt;AP5475.d0f5.2ee7#&lt;/SPAN&gt;&lt;SPAN&gt;&lt;STRONG&gt;conf t&lt;/STRONG&gt;&lt;/SPAN&gt;&lt;BR /&gt;&lt;SPAN&gt;AP5475.d0f5.2ee7(config)#&lt;/SPAN&gt;&lt;SPAN&gt;&lt;STRONG&gt;ip default-gateway&amp;nbsp;x.x.x.x&lt;/STRONG&gt;&lt;/SPAN&gt;&lt;BR /&gt;&lt;SPAN&gt;AP5475.d0f5.2ee7(config)#&lt;/SPAN&gt;&lt;SPAN&gt;&lt;STRONG&gt;int g0&lt;/STRONG&gt;&lt;/SPAN&gt;&lt;BR /&gt;&lt;SPAN&gt;AP5475.d0f5.2ee7(config-if)#&lt;/SPAN&gt;&lt;SPAN&gt;&lt;STRONG&gt;ip address&amp;nbsp;x.x.x.x 255.255.255.0&lt;/STRONG&gt;&lt;/SPAN&gt;&lt;BR /&gt;&lt;SPAN&gt;AP5475.d0f5.2ee7(config-if)#&lt;/SPAN&gt;&lt;SPAN&gt;&lt;STRONG&gt;no sh&lt;/STRONG&gt;&lt;/SPAN&gt;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;&lt;SPAN&gt;Point to a TFTP server to get the autonomous image:&lt;/SPAN&gt;&lt;/P&gt;
&lt;P&gt;&lt;SPAN&gt;&lt;STRONG&gt;archive download-sw /force-reload /overwrite tftp://y.y.y.y/AP-image.JA.tar&lt;/STRONG&gt;&lt;/SPAN&gt;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;&lt;SPAN&gt;&lt;STRONG&gt;-If I helped you somehow, please, rate it as useful.-&lt;/STRONG&gt;&lt;/SPAN&gt;&lt;/P&gt;</description>
      <pubDate>Tue, 06 Mar 2018 17:03:08 GMT</pubDate>
      <guid>https://community.cisco.com/t5/wireless/can-t-set-1700-cap-to-autonomous-once-wlc-has-provisioned-it/m-p/3343411#M105252</guid>
      <dc:creator>Flavio Miranda</dc:creator>
      <dc:date>2018-03-06T17:03:08Z</dc:date>
    </item>
    <item>
      <title>Re: Can't set 1700 CAP to Autonomous once WLC has Provisioned it</title>
      <link>https://community.cisco.com/t5/wireless/can-t-set-1700-cap-to-autonomous-once-wlc-has-provisioned-it/m-p/3343498#M105253</link>
      <description>&lt;P&gt;Thanks Flavio.&amp;nbsp; However, I am curious as to whether or not my AP was just shipped to me without the proper unified firmware on it, or if the WLC auto provisioning it once it was connected to the network removed some kind of one-time flag that lets you toggle between CAP or SAP. For example, when I set a 1702 to boot into autonomous mode, I can't boot it back to lightweight mode. So I am wondering if you let a WLC provision your CAP in it's default mode, is that action what makes it so you can no longer boot into autonomous mode or is it coincidence?&lt;/P&gt;
&lt;P&gt;Basically I told them not to plug it into the network for this very reason and it looks like they did it anyway. So I am trying to figure out if&amp;nbsp;this is a self-inflicted injury or if I need to tell my vendor they gave me the wrong firmware.&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Tue, 06 Mar 2018 19:01:21 GMT</pubDate>
      <guid>https://community.cisco.com/t5/wireless/can-t-set-1700-cap-to-autonomous-once-wlc-has-provisioned-it/m-p/3343498#M105253</guid>
      <dc:creator>Dean Romanelli</dc:creator>
      <dc:date>2018-03-06T19:01:21Z</dc:date>
    </item>
    <item>
      <title>Re: Can't set 1700 CAP to Autonomous once WLC has Provisioned it</title>
      <link>https://community.cisco.com/t5/wireless/can-t-set-1700-cap-to-autonomous-once-wlc-has-provisioned-it/m-p/3343512#M105254</link>
      <description>&lt;P&gt;I dont think this happen because they connect the AP to the WLC but it is a characteristic on the AP mode and version.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;There are some discussions around it here on the forum:&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;&lt;A href="https://supportforums.cisco.com/t5/getting-started-with-wireless/how-to-convert-an-ap-1700-2700-from-lightweight-mode-to/td-p/2571808" target="_self"&gt;https://supportforums.cisco.com/t5/getting-started-with-wireless/how-to-convert-an-ap-1700-2700-from-lightweight-mode-to/td-p/2571808&lt;/A&gt;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;-If I helped you somehow, please, rate it as useful.-&lt;/P&gt;</description>
      <pubDate>Tue, 06 Mar 2018 19:45:31 GMT</pubDate>
      <guid>https://community.cisco.com/t5/wireless/can-t-set-1700-cap-to-autonomous-once-wlc-has-provisioned-it/m-p/3343512#M105254</guid>
      <dc:creator>Flavio Miranda</dc:creator>
      <dc:date>2018-03-06T19:45:31Z</dc:date>
    </item>
  </channel>
</rss>

