<?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 2 new 1602i AP won't connect to vWLC in Wireless</title>
    <link>https://community.cisco.com/t5/wireless/2-new-1602i-ap-won-t-connect-to-vwlc/m-p/2871822#M56327</link>
    <description>&lt;P&gt;I have a virtual WLC running software version 7.6.130.0.&amp;nbsp; I have a variety of APs on it from 1141 all the way to 2702's.&amp;nbsp; I have 104 APs current connected with 7 licenses remaining.&lt;/P&gt;
&lt;P&gt;&lt;/P&gt;
&lt;P&gt;I just purchased 2 refurbished 1602i's and am trying to get them to connect to the WLC.&amp;nbsp;&lt;/P&gt;
&lt;P&gt;&lt;/P&gt;
&lt;P&gt;This is what they keep giving me over and over again:&lt;/P&gt;
&lt;P&gt;&lt;/P&gt;
&lt;P&gt;*Mar&amp;nbsp; 3 20:16:43.071: AP has SHA2 MIC certificate - Using SHA1 MIC certificate for DTLS.&lt;BR /&gt;&lt;BR /&gt;*Mar&amp;nbsp; 3 20:16:43.000: %CAPWAP-5-DTLSREQSEND: DTLS connection request sent peer_ip: 10.20.3.10 peer_port: 5246&lt;BR /&gt;*Mar&amp;nbsp; 3 20:17:12.999: DTLS_CLIENT_ERROR: ../capwap/base_capwap/dtls/base_capwap_dtls_connection_db.c:2214 Max retransmission count reached for Connection 0x7631114!&lt;BR /&gt;&lt;BR /&gt;*Mar&amp;nbsp; 3 20:17:42.999: %DTLS-5-SEND_ALERT: Send FATAL : Close notify Alert to 10.20.3.10:52&lt;/P&gt;
&lt;P&gt;&lt;/P&gt;
&lt;P&gt;I did a lot of searching on the forums and I find references to some of these errors but they are all for people that upgraded the WLC to version 8.0.&lt;/P&gt;
&lt;P&gt;&lt;/P&gt;
&lt;P&gt;Any help would be greatly appreciated.&lt;/P&gt;</description>
    <pubDate>Mon, 05 Jul 2021 11:43:10 GMT</pubDate>
    <dc:creator>Jacob Simons</dc:creator>
    <dc:date>2021-07-05T11:43:10Z</dc:date>
    <item>
      <title>2 new 1602i AP won't connect to vWLC</title>
      <link>https://community.cisco.com/t5/wireless/2-new-1602i-ap-won-t-connect-to-vwlc/m-p/2871822#M56327</link>
      <description>&lt;P&gt;I have a virtual WLC running software version 7.6.130.0.&amp;nbsp; I have a variety of APs on it from 1141 all the way to 2702's.&amp;nbsp; I have 104 APs current connected with 7 licenses remaining.&lt;/P&gt;
&lt;P&gt;&lt;/P&gt;
&lt;P&gt;I just purchased 2 refurbished 1602i's and am trying to get them to connect to the WLC.&amp;nbsp;&lt;/P&gt;
&lt;P&gt;&lt;/P&gt;
&lt;P&gt;This is what they keep giving me over and over again:&lt;/P&gt;
&lt;P&gt;&lt;/P&gt;
&lt;P&gt;*Mar&amp;nbsp; 3 20:16:43.071: AP has SHA2 MIC certificate - Using SHA1 MIC certificate for DTLS.&lt;BR /&gt;&lt;BR /&gt;*Mar&amp;nbsp; 3 20:16:43.000: %CAPWAP-5-DTLSREQSEND: DTLS connection request sent peer_ip: 10.20.3.10 peer_port: 5246&lt;BR /&gt;*Mar&amp;nbsp; 3 20:17:12.999: DTLS_CLIENT_ERROR: ../capwap/base_capwap/dtls/base_capwap_dtls_connection_db.c:2214 Max retransmission count reached for Connection 0x7631114!&lt;BR /&gt;&lt;BR /&gt;*Mar&amp;nbsp; 3 20:17:42.999: %DTLS-5-SEND_ALERT: Send FATAL : Close notify Alert to 10.20.3.10:52&lt;/P&gt;
&lt;P&gt;&lt;/P&gt;
&lt;P&gt;I did a lot of searching on the forums and I find references to some of these errors but they are all for people that upgraded the WLC to version 8.0.&lt;/P&gt;
&lt;P&gt;&lt;/P&gt;
&lt;P&gt;Any help would be greatly appreciated.&lt;/P&gt;</description>
      <pubDate>Mon, 05 Jul 2021 11:43:10 GMT</pubDate>
      <guid>https://community.cisco.com/t5/wireless/2-new-1602i-ap-won-t-connect-to-vwlc/m-p/2871822#M56327</guid>
      <dc:creator>Jacob Simons</dc:creator>
      <dc:date>2021-07-05T11:43:10Z</dc:date>
    </item>
    <item>
      <title>What happens if you try</title>
      <link>https://community.cisco.com/t5/wireless/2-new-1602i-ap-won-t-connect-to-vwlc/m-p/2871823#M56328</link>
      <description>&lt;P&gt;What happens if you try getting it to join manually from the CLI?&lt;/P&gt;</description>
      <pubDate>Thu, 03 Mar 2016 21:20:08 GMT</pubDate>
      <guid>https://community.cisco.com/t5/wireless/2-new-1602i-ap-won-t-connect-to-vwlc/m-p/2871823#M56328</guid>
      <dc:creator>Philip D'Ath</dc:creator>
      <dc:date>2016-03-03T21:20:08Z</dc:date>
    </item>
    <item>
      <title>I have never had to do that</title>
      <link>https://community.cisco.com/t5/wireless/2-new-1602i-ap-won-t-connect-to-vwlc/m-p/2871824#M56329</link>
      <description>&lt;P&gt;I have never had to do that before.&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Can you point me at some documentation or let me know what the commands would be to do it?&lt;/P&gt;</description>
      <pubDate>Thu, 03 Mar 2016 21:23:02 GMT</pubDate>
      <guid>https://community.cisco.com/t5/wireless/2-new-1602i-ap-won-t-connect-to-vwlc/m-p/2871824#M56329</guid>
      <dc:creator>Jacob Simons</dc:creator>
      <dc:date>2016-03-03T21:23:02Z</dc:date>
    </item>
    <item>
      <title>lwapp ap controller ip</title>
      <link>https://community.cisco.com/t5/wireless/2-new-1602i-ap-won-t-connect-to-vwlc/m-p/2871825#M56330</link>
      <description>&lt;P&gt;You need to use the command:&lt;/P&gt;
&lt;PRE class="prettyprint"&gt;lwapp ap controller ip address &amp;lt;IP-address&amp;gt;&lt;/PRE&gt;
&lt;P&gt;&lt;/P&gt;
&lt;P&gt;If that is not allowed, you may need to execute this command first:&lt;/P&gt;
&lt;PRE class="prettyprint"&gt;"debug lwapp console cli"&lt;BR /&gt;or&lt;BR /&gt;"debug capwap console cli"&lt;/PRE&gt;</description>
      <pubDate>Thu, 03 Mar 2016 21:34:52 GMT</pubDate>
      <guid>https://community.cisco.com/t5/wireless/2-new-1602i-ap-won-t-connect-to-vwlc/m-p/2871825#M56330</guid>
      <dc:creator>Philip D'Ath</dc:creator>
      <dc:date>2016-03-03T21:34:52Z</dc:date>
    </item>
    <item>
      <title>I was able to run the first</title>
      <link>https://community.cisco.com/t5/wireless/2-new-1602i-ap-won-t-connect-to-vwlc/m-p/2871826#M56331</link>
      <description>&lt;P&gt;I was able to run the first command.&amp;nbsp; It didn't return any errors but it didn't seem to make any changes either. The same errors I mentioned in my initial post continue to repeat.&lt;/P&gt;
&lt;P&gt;&lt;/P&gt;</description>
      <pubDate>Fri, 04 Mar 2016 14:01:36 GMT</pubDate>
      <guid>https://community.cisco.com/t5/wireless/2-new-1602i-ap-won-t-connect-to-vwlc/m-p/2871826#M56331</guid>
      <dc:creator>Jacob Simons</dc:creator>
      <dc:date>2016-03-04T14:01:36Z</dc:date>
    </item>
    <item>
      <title>The current version of</title>
      <link>https://community.cisco.com/t5/wireless/2-new-1602i-ap-won-t-connect-to-vwlc/m-p/2871827#M56332</link>
      <description>&lt;P&gt;The current version of software on the access-point might be to low and not including the needed certificates. Because of this I recommend you to download one of the latest &lt;SPAN id="03F6A29FAB6B0E5D63DB9D4FD7748B28D1E70CD6" class="overlay_img"&gt;ap1g2-k9w8&lt;/SPAN&gt; images from the Cisco website and install it manually. Please post the whole console output of the access-point and the recent logging of the WLC if the access-point still can't join the WLC after upgrading the software of the access-point.&lt;BR /&gt;&lt;BR /&gt;&lt;EM&gt;Please rate useful posts... &lt;span class="lia-unicode-emoji" title=":slightly_smiling_face:"&gt;🙂&lt;/span&gt;&lt;/EM&gt;&lt;/P&gt;</description>
      <pubDate>Sat, 05 Mar 2016 17:06:01 GMT</pubDate>
      <guid>https://community.cisco.com/t5/wireless/2-new-1602i-ap-won-t-connect-to-vwlc/m-p/2871827#M56332</guid>
      <dc:creator>Freerk Terpstra</dc:creator>
      <dc:date>2016-03-05T17:06:01Z</dc:date>
    </item>
    <item>
      <title>I think we should try what</title>
      <link>https://community.cisco.com/t5/wireless/2-new-1602i-ap-won-t-connect-to-vwlc/m-p/2871828#M56333</link>
      <description>&lt;P&gt;I think we should try what Freerk has suggested, and put a newer recovery image on the APs.&lt;/P&gt;</description>
      <pubDate>Sun, 06 Mar 2016 19:35:49 GMT</pubDate>
      <guid>https://community.cisco.com/t5/wireless/2-new-1602i-ap-won-t-connect-to-vwlc/m-p/2871828#M56333</guid>
      <dc:creator>Philip D'Ath</dc:creator>
      <dc:date>2016-03-06T19:35:49Z</dc:date>
    </item>
    <item>
      <title>I checked out the software</title>
      <link>https://community.cisco.com/t5/wireless/2-new-1602i-ap-won-t-connect-to-vwlc/m-p/2871829#M56334</link>
      <description>&lt;P&gt;I checked out the software version on the AP and it is pretty new. ap1g2-k9w8-mx.153-3.JBB6.&amp;nbsp; Here are all the boot up logs off of the AP and the relevent message logs of the WLC.&lt;/P&gt;
&lt;P&gt;&lt;/P&gt;
&lt;H1&gt;AP&lt;/H1&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;flashfs[0]: 74 files, 15 directories&lt;/P&gt;
&lt;P&gt;flashfs[0]: 0 orphaned files, 0 orphaned directories&lt;/P&gt;
&lt;P&gt;flashfs[0]: Total bytes: 31936000&lt;/P&gt;
&lt;P&gt;flashfs[0]: Bytes used: 30277120&lt;/P&gt;
&lt;P&gt;flashfs[0]: Bytes available: 1658880&lt;/P&gt;
&lt;P&gt;flashfs[0]: flashfs fsck took 19 seconds.&lt;/P&gt;
&lt;P&gt;flashfs[1]: 0 files, 1 directories&lt;/P&gt;
&lt;P&gt;flashfs[1]: 0 orphaned files, 0 orphaned directories&lt;/P&gt;
&lt;P&gt;flashfs[1]: Total bytes: 16386048&lt;/P&gt;
&lt;P&gt;flashfs[1]: Bytes used: 1024&lt;/P&gt;
&lt;P&gt;flashfs[1]: Bytes available: 16385024&lt;/P&gt;
&lt;P&gt;flashfs[1]: flashfs fsck took 0 seconds.&lt;/P&gt;
&lt;P&gt;Reading cookie from SEEPROM&lt;/P&gt;
&lt;P&gt;Base Ethernet MAC address: d0:72:dc:36:ea:56&lt;/P&gt;
&lt;P&gt;************* loopback_mode = 0&lt;/P&gt;
&lt;P&gt;Marvell Phy Revision = 0xdd1 - Production Phy, Rev. A0&lt;/P&gt;
&lt;P&gt;Marvell Phy Rev. A0 initialization...&lt;/P&gt;
&lt;P&gt;Turn off CLK125&lt;/P&gt;
&lt;P&gt;1000BaseT Status reg.&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; = 0x7800&lt;/P&gt;
&lt;P&gt;1000BaseT Copper Status 1 reg. = 0xbc08&lt;/P&gt;
&lt;P&gt;1000BaseT Copper Status 2 reg. = 0x1c40&lt;/P&gt;
&lt;P&gt;Receive Error Counter reg.&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; = 0x0&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Loading "flash:/ap1g2-k9w8-mx.153-3.JBB6/ap1g2-k9w8-mx.153-3.JBB6"...##############&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;File "flash:/ap1g2-k9w8-mx.153-3.JBB6/ap1g2-k9w8-mx.153-3.JBB6" uncompressed and installed, entry point: 0x2004000&lt;/P&gt;
&lt;P&gt;executing...&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Secondary Bootloader - Starting system.&lt;/P&gt;
&lt;P&gt;FLASH CHIP: Micronix MX25L256_35F&lt;/P&gt;
&lt;P&gt;Xmodem file system is available.&lt;/P&gt;
&lt;P&gt;flashfs[0]: 74 files, 15 directories&lt;/P&gt;
&lt;P&gt;flashfs[0]: 0 orphaned files, 0 orphaned directories&lt;/P&gt;
&lt;P&gt;flashfs[0]: Total bytes: 31936000&lt;/P&gt;
&lt;P&gt;flashfs[0]: Bytes used: 30277120&lt;/P&gt;
&lt;P&gt;flashfs[0]: Bytes available: 1658880&lt;/P&gt;
&lt;P&gt;flashfs[0]: flashfs fsck took 20 seconds.&lt;/P&gt;
&lt;P&gt;Reading cookie from SEEPROM&lt;/P&gt;
&lt;P&gt;Base Ethernet MAC address: d0:72:dc:36:ea:56&lt;/P&gt;
&lt;P&gt;Secondary bootloader Ethernet not enabled, skip ether_init&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Boot CMD: 'boot flash:/ap1g2-k9w8-mx.153-3.JBB6/ap1g2-k9w8-xx.153-3.JBB6;flash:/ap1g2-k9w8-mx.153-3.JBB6/ap1g2-k9w8-xx.153-3.JBB6'&lt;/P&gt;
&lt;P&gt;Loading "flash:/ap1g2-k9w8-mx.153-3.JBB6/ap1g2-k9w8-xx.153-3.JBB6"...##########################################&lt;/P&gt;
&lt;P&gt;File "flash:/ap1g2-k9w8-mx.153-3.JBB6/ap1g2-k9w8-xx.153-3.JBB6" uncompressed and installed, entry point: 0x100000&lt;/P&gt;
&lt;P&gt;executing...&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&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; Restricted Rights Legend&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Use, duplication, or disclosure by the Government is&lt;/P&gt;
&lt;P&gt;subject to restrictions as set forth in subparagraph&lt;/P&gt;
&lt;P&gt;(c) of the Commercial Computer Software - Restricted&lt;/P&gt;
&lt;P&gt;Rights clause at FAR sec. 52.227-19 and subparagraph&lt;/P&gt;
&lt;P&gt;(c) (1) (ii) of the Rights in Technical Data and Computer&lt;/P&gt;
&lt;P&gt;Software clause at DFARS sec. 252.227-7013.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&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; cisco Systems, Inc.&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; 170 West Tasman Drive&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; San Jose, California 95134-1706&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Cisco IOS Software, C1600 Software (AP1G2-K9W8-M), Version 15.3(3)JBB6, RELEASE SOFTWARE (fc2)&lt;/P&gt;
&lt;P&gt;Technical Support: http://www.cisco.com/techsupport&lt;/P&gt;
&lt;P&gt;Copyright (c) 1986-2015 by Cisco Systems, Inc.&lt;/P&gt;
&lt;P&gt;Compiled Sun 01-Nov-15 20:15 by prod_rel_team&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Initializing flashfs...&lt;/P&gt;
&lt;P&gt;FLASH CHIP: Micronix MX25L256_35F&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;flashfs[2]: WARNING - Unable to allocate backup blocks.&lt;/P&gt;
&lt;P&gt;Please free some space on the flash file system.&lt;/P&gt;
&lt;P&gt;flashfs[2]: 74 files, 15 directories&lt;/P&gt;
&lt;P&gt;flashfs[2]: 0 orphaned files, 0 orphaned directories&lt;/P&gt;
&lt;P&gt;flashfs[2]: Total bytes: 31936000&lt;/P&gt;
&lt;P&gt;flashfs[2]: Bytes used: 30277120&lt;/P&gt;
&lt;P&gt;flashfs[2]: Bytes available: 1658880&lt;/P&gt;
&lt;P&gt;flashfs[2]: flashfs fsck took 18 seconds.&lt;/P&gt;
&lt;P&gt;flashfs[2]: Initialization complete.&lt;/P&gt;
&lt;P&gt;flashfs[4]: 0 files, 1 directories&lt;/P&gt;
&lt;P&gt;flashfs[4]: 0 orphaned files, 0 orphaned directories&lt;/P&gt;
&lt;P&gt;flashfs[4]: Total bytes: 11999232&lt;/P&gt;
&lt;P&gt;flashfs[4]: Bytes used: 1024&lt;/P&gt;
&lt;P&gt;flashfs[4]: Bytes available: 11998208&lt;/P&gt;
&lt;P&gt;flashfs[4]: flashfs fsck took 0 seconds.&lt;/P&gt;
&lt;P&gt;flashfs[4]: Initialization complete....done Initializing flashfs.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Radio0 present 8764B 8000 0 A8000000 A8010000 0&lt;/P&gt;
&lt;P&gt;Rate table has 586 entries (20 legacy/160 11n/406 11ac)&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;POWER TABLE FILENAME = flash:/ap1g2-k9w8-mx.153-3.JBB6/K2.bin&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Radio1 present 8764B 8000 0 88000000 88010000 4&lt;/P&gt;
&lt;P&gt;POWER TABLE FILENAME = flash:/ap1g2-k9w8-mx.153-3.JBB6/K5.bin&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;This product contains cryptographic features and is subject to United&lt;/P&gt;
&lt;P&gt;States and local country laws governing import, export, transfer and&lt;/P&gt;
&lt;P&gt;use. Delivery of Cisco cryptographic products does not imply&lt;/P&gt;
&lt;P&gt;third-party authority to import, export, distribute or use encryption.&lt;/P&gt;
&lt;P&gt;Importers, exporters, distributors and users are responsible for&lt;/P&gt;
&lt;P&gt;compliance with U.S. and local country laws. By using this product you&lt;/P&gt;
&lt;P&gt;agree to comply with applicable laws and regulations. If you are unable&lt;/P&gt;
&lt;P&gt;to comply with U.S. and local laws, return this product immediately.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;A summary of U.S. laws governing Cisco cryptographic products may be found at:&lt;/P&gt;
&lt;P&gt;http://www.cisco.com/wwl/export/crypto/tool/stqrg.html&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;If you require further assistance please contact us by sending email to&lt;/P&gt;
&lt;P&gt;export@cisco.com.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;cisco AIR-CAP1602I-A-K9 (PowerPC) processor (revision B0) with 187382K/74672K bytes of memory.&lt;/P&gt;
&lt;P&gt;Processor board ID FGL1815W78N&lt;/P&gt;
&lt;P&gt;PowerPC CPU at 533Mhz, revision number 0x2151&lt;/P&gt;
&lt;P&gt;Last reset from power-on&lt;/P&gt;
&lt;P&gt;LWAPP image version 8.1.131.0&lt;/P&gt;
&lt;P&gt;1 Gigabit Ethernet interface&lt;/P&gt;
&lt;P&gt;2 802.11 Radios&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;32K bytes of flash-simulated non-volatile configuration memory.&lt;/P&gt;
&lt;P&gt;Base ethernet MAC Address: D0:72:DC:36:EA:56&lt;/P&gt;
&lt;P&gt;Part Number&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;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; : 73-14671-04&lt;/P&gt;
&lt;P&gt;PCA Assembly Number&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;&amp;nbsp; : 000-00000-00&lt;/P&gt;
&lt;P&gt;PCA Revision Number&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;&amp;nbsp; :&lt;/P&gt;
&lt;P&gt;PCB Serial Number&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;&amp;nbsp;&amp;nbsp;&amp;nbsp; : FOC181246WP&lt;/P&gt;
&lt;P&gt;Top Assembly Part Number&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; : 800-38552-01&lt;/P&gt;
&lt;P&gt;Top Assembly Serial Number&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; : FGL1815W78N&lt;/P&gt;
&lt;P&gt;Top Revision Number&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;&amp;nbsp; : A0&lt;/P&gt;
&lt;P&gt;Product/Model Number&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;&amp;nbsp; : AIR-CAP1602I-A-K9&lt;/P&gt;
&lt;P&gt;% Please define a domain-name first.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Press RETURN to get started!&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;*Mar 1 00:00:20.947: %SOAP_FIPS-2-SELF_TEST_IOS_SUCCESS: IOS crypto FIPS self test passed (15)&lt;/P&gt;
&lt;P&gt;*Mar 1 00:00:21.943: %SOAP_FIPS-2-SELF_TEST_HW_SUCCESS: HW crypto FIPS self test passed (1-8)&lt;/P&gt;
&lt;P&gt;*Mar 1 00:00:21.943: Registering HW DTLS&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;*Mar 1 00:00:21.951: APAVC: Initial WLAN Buffers Given to System is 500&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;*Mar 1 00:00:21.967: APAVC: WlanPAKs 9355 RadioPaks 8747&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;*Mar 1 00:00:23.991: %LINK-6-UPDOWN: Interface GigabitEthernet0, changed state to up&lt;/P&gt;
&lt;P&gt;*Mar 1 00:00:25.699: %LINEPROTO-5-UPDOWN: Line protocol on Interface GigabitEthernet0, changed state to up&lt;/P&gt;
&lt;P&gt;*Mar 1 00:00:28.855: %SOAP_FIPS-2-SELF_TEST_RAD_SUCCESS: RADIO crypto FIPS self test passed on interface Dot11Radio 0 (4)&lt;/P&gt;
&lt;P&gt;*Mar 1 00:00:28.999: Loading Power Tables from flash:/ap1g2-k9w8-mx.153-3.JBB6/K2.bin. Class = A&lt;/P&gt;
&lt;P&gt;*Mar 1 00:00:28.999: record size of 3ss: 1168 read_ptr: 34F2BFE&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;*Mar 1 00:00:35.323: %SOAP_FIPS-2-SELF_TEST_RAD_SUCCESS: RADIO crypto FIPS self test passed on interface Dot11Radio 1 (4)&lt;/P&gt;
&lt;P&gt;*Mar 1 00:00:35.399: Loading Power Tables from flash:/ap1g2-k9w8-mx.153-3.JBB6/K5.bin. Class = A&lt;/P&gt;
&lt;P&gt;*Mar 1 00:00:35.399: record size of 3ss: 1168 read_ptr: 34F2BFE&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;*Mar 1 00:00:35.575: Wait until the stile protocol list is initialized.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;*Mar 1 00:00:37.747: Start STILE Activation&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;*Mar 3 17:12:42.051: %SYS-5-RESTART: System restarted --&lt;/P&gt;
&lt;P&gt;Cisco IOS Software, C1600 Software (AP1G2-K9W8-M), Version 15.3(3)JBB6, RELEASE SOFTWARE (fc2)&lt;/P&gt;
&lt;P&gt;Technical Support: http://www.cisco.com/techsupport&lt;/P&gt;
&lt;P&gt;Copyright (c) 1986-2015 by Cisco Systems, Inc.&lt;/P&gt;
&lt;P&gt;Compiled Sun 01-Nov-15 20:15 by prod_rel_team&lt;/P&gt;
&lt;P&gt;*Mar 3 17:12:42.051: %SNMP-5-COLDSTART: SNMP agent on host APd072.dc36.ea56 is undergoing a cold start&lt;/P&gt;
&lt;P&gt;*Mar 3 17:12:43.391: %LINEPROTO-5-UPDOWN: Line protocol on Interface BVI1, changed state to up&lt;/P&gt;
&lt;P&gt;*Mar 3 17:12:44.639: %LINK-6-UPDOWN: Interface Dot11Radio0, changed state to up&lt;/P&gt;
&lt;P&gt;*Mar 3 17:12:44.871: %LINK-6-UPDOWN: Interface Dot11Radio1, changed state to up&lt;/P&gt;
&lt;P&gt;*Mar 3 17:12:49.331: %SSH-5-DISABLED: SSH 2.0 has been disabled&lt;/P&gt;
&lt;P&gt;*Mar 3 17:12:49.403: %SSH-5-ENABLED: SSH 2.0 has been enabledlwapp_crypto_init: MIC Present and Parsed Successfully&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;*Mar 3 17:12:59.603: Currently running a Release Image&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;*Mar 3 17:12:59.699: Using SHA-2 signed certificate for image signing validation.&lt;/P&gt;
&lt;P&gt;*Mar 3 17:13:31.483: APAVC: Succeeded to activate all the STILE protocols.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;*Mar 3 17:13:31.483: APAVC: Registering with CFT&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;*Mar 3 17:13:31.483: APAVC: CFT registration of delete callback succeeded&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;*Mar 3 17:13:31.483: APAVC: Reattaching Original Buffer pool for system use&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;*Mar 3 17:13:31.483: Pool-ReAtach: paks 9355 radio8747&lt;/P&gt;
&lt;P&gt;%Default route without gateway, if not a point-to-point interface, may impact performance&lt;/P&gt;
&lt;P&gt;*Mar 3 17:13:35.863: %DHCP-6-ADDRESS_ASSIGN: Interface BVI1 assigned DHCP address 10.20.20.3, mask 255.255.0.0, hostname APd072.dc36.ea56&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;*Mar 3 17:13:37.191: AP image integrity check PASSED&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;*Mar 3 17:13:37.375: %LINK-5-CHANGED: Interface Dot11Radio0, changed state to reset&lt;/P&gt;
&lt;P&gt;*Mar 3 17:13:37.375: %LINK-5-CHANGED: Interface Dot11Radio1, changed state to reset&lt;/P&gt;
&lt;P&gt;*Mar 3 17:13:37.795: Cert ISSUER (39): cn=Cisco Manufacturing CA SHA2,o=Cisco&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;*Mar 3 17:13:47.835: %SYS-6-LOGGINGHOST_STARTSTOP: Logging to host 255.255.255.255 port 0 CLI Request Triggered&lt;/P&gt;
&lt;P&gt;Translating "CISCO-CAPWAP-CONTROLLER.walworth1.mpc.com"...domain server (10.25.1.30) [OK]&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;*Mar 3 17:13:58.843: %CAPWAP-5-DHCP_OPTION_43: Controller address 10.20.3.10 obtained through DHCP&lt;/P&gt;
&lt;P&gt;*Mar 3 17:14:09.911: AP has SHA2 MIC certificate - Using SHA1 MIC certificate for DTLS.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;*Mar 7 15:50:52.000: %CAPWAP-5-DTLSREQSEND: DTLS connection request sent peer_ip: 10.20.3.10 peer_port: 5246Get AP Certificate: failed to get local certificate&lt;/P&gt;
&lt;P&gt;*Mar 7 15:50:52.055: DTLS_CLIENT_ERROR: ../capwap/base_capwap/dtls/base_capwap_dtls_handshake.c:1439 Error fetching certificate.&lt;/P&gt;
&lt;P&gt;*Mar 7 15:50:52.055: %DTLS-5-SEND_ALERT: Send FATAL : Internal error Alert to 10.20.3.10:5246&lt;/P&gt;
&lt;P&gt;*Mar 7 15:50:52.055: DTLS_CLIENT_ERROR: ../capwap/base_capwap/dtls/base_capwap_dtls_client.c:426 Error sending Certificate.&lt;/P&gt;
&lt;P&gt;*Mar 7 15:50:52.055: %DTLS-5-SEND_ALERT: Send FATAL : Close notify Alert to 10.20.3.10:5246&lt;/P&gt;
&lt;P&gt;*Mar 7 15:51:01.067: %CDP_PD-4-POWER_OK: Full power - INJECTOR_CONFIGURED_ON_SOURCE inline power source&lt;/P&gt;
&lt;P&gt;*Mar 7 15:51:02.335: %LINK-6-UPDOWN: Interface Dot11Radio0, changed state to up&lt;/P&gt;
&lt;P&gt;*Mar 7 15:51:03.335: %LINEPROTO-5-UPDOWN: Line protocol on Interface Dot11Radio0, changed state to up&lt;/P&gt;
&lt;P&gt;*Mar 7 15:51:03.607: %LINK-6-UPDOWN: Interface Dot11Radio1, changed state to up&lt;/P&gt;
&lt;P&gt;*Mar 7 15:51:04.607: %LINEPROTO-5-UPDOWN: Line protocol on Interface Dot11Radio1, changed state to up&lt;/P&gt;
&lt;P&gt;*Mar 7 15:51:57.071: AP has SHA2 MIC certificate - Using SHA1 MIC certificate for DTLS.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;User Access Verification&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Username:&lt;/P&gt;
&lt;P&gt;*Mar 7 15:51:57.000: %CAPWAP-5-DTLSREQSEND: DTLS connection request sent peer_ip: 10.20.3.10 peer_port: 5246&lt;/P&gt;
&lt;P&gt;% Username: timeout expired!&lt;/P&gt;
&lt;P&gt;APd072.dc36.ea56 con0 is now available&lt;/P&gt;
&lt;P&gt;Press RETURN to get started.&lt;/P&gt;
&lt;P&gt;*Mar 7 15:52:26.999: DTLS_CLIENT_ERROR: ../capwap/base_capwap/dtls/base_capwap_dtls_connection_db.c:2214 Max retransmission count reached for Connection 0x58A8C88!&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;H1&gt;WLC&lt;/H1&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;*apfMsConnTask_3: Mar 07 09:53:09.051: #APF-3-AID_UPDATE_FAILED: apf_80211.c:6571 Error updating Association ID for REAP AP Client10:bd:18:1a:54:b0 - AID 9&lt;/P&gt;
&lt;P&gt;*apfMsConnTask_3: Mar 07 09:53:09.051: #LWAPP-3-INVALID_AID2: spam_api.c:1465 Association identifier 9 for client 00:23:68:d7:b0:3f is already in use by 80:00:0b:b7:56:3d&lt;/P&gt;
&lt;P&gt;*SISF BT Process: Mar 07 09:52:58.639: #SISF-3-INTERNAL: sisf_shim_utils.c:442 Internal error, check handle invalid entry&lt;/P&gt;
&lt;P&gt;*apfMsConnTask_3: Mar 07 09:52:52.671: #APF-3-AID_UPDATE_FAILED: apf_80211.c:6571 Error updating Association ID for REAP AP Client10:bd:18:1a:54:b0 - AID 9&lt;/P&gt;
&lt;P&gt;*apfMsConnTask_3: Mar 07 09:52:52.671: #LWAPP-3-INVALID_AID2: spam_api.c:1465 Association identifier 9 for client 34:4d:f7:7d:1c:42 is already in use by 80:00:0b:b7:56:3d&lt;/P&gt;
&lt;P&gt;&lt;/P&gt;
&lt;P&gt;&lt;/P&gt;</description>
      <pubDate>Mon, 07 Mar 2016 16:04:00 GMT</pubDate>
      <guid>https://community.cisco.com/t5/wireless/2-new-1602i-ap-won-t-connect-to-vwlc/m-p/2871829#M56334</guid>
      <dc:creator>Jacob Simons</dc:creator>
      <dc:date>2016-03-07T16:04:00Z</dc:date>
    </item>
    <item>
      <title>This is the issue:</title>
      <link>https://community.cisco.com/t5/wireless/2-new-1602i-ap-won-t-connect-to-vwlc/m-p/2871830#M56335</link>
      <description>&lt;P&gt;This is the issue:&lt;/P&gt;
&lt;BLOCKQUOTE&gt;
&lt;P&gt;&lt;SPAN&gt;Get AP Certificate: failed to get local certificate&lt;/SPAN&gt;&lt;/P&gt;
&lt;/BLOCKQUOTE&gt;
&lt;P&gt;&lt;SPAN&gt;&lt;/SPAN&gt;&lt;/P&gt;
&lt;P&gt;&lt;SPAN&gt;The AP is missing its burned in certificate. &amp;nbsp;If it was me, I think I would return the access points. &amp;nbsp;I'm wondering if they are genuine Cisco AP's.&lt;/SPAN&gt;&lt;/P&gt;
&lt;P&gt;&lt;SPAN&gt;&lt;/SPAN&gt;&lt;/P&gt;
&lt;P&gt;&lt;SPAN&gt;Failing that, you may be able to put a locally significant&amp;nbsp;certificate&amp;nbsp;on it if you like a lot of pain.&lt;/SPAN&gt;&lt;/P&gt;
&lt;P&gt;&lt;SPAN&gt;&lt;A href="http://www.cisco.com/c/en/us/support/docs/wireless/4400-series-wireless-lan-controllers/110141-loc-sig-cert.html"&gt;http://www.cisco.com/c/en/us/support/docs/wireless/4400-series-wireless-lan-controllers/110141-loc-sig-cert.html&lt;/A&gt;&lt;/SPAN&gt;&lt;/P&gt;</description>
      <pubDate>Mon, 07 Mar 2016 18:55:38 GMT</pubDate>
      <guid>https://community.cisco.com/t5/wireless/2-new-1602i-ap-won-t-connect-to-vwlc/m-p/2871830#M56335</guid>
      <dc:creator>Philip D'Ath</dc:creator>
      <dc:date>2016-03-07T18:55:38Z</dc:date>
    </item>
    <item>
      <title>They are refurbished access</title>
      <link>https://community.cisco.com/t5/wireless/2-new-1602i-ap-won-t-connect-to-vwlc/m-p/2871831#M56336</link>
      <description>&lt;P&gt;They are refurbished access points.&amp;nbsp; They have a sticker on the back that says Cisco Wholesale Refurbished. It does have the rest of the standard stickers on the back with the model and serial numbers and such.&lt;/P&gt;</description>
      <pubDate>Mon, 07 Mar 2016 21:38:33 GMT</pubDate>
      <guid>https://community.cisco.com/t5/wireless/2-new-1602i-ap-won-t-connect-to-vwlc/m-p/2871831#M56336</guid>
      <dc:creator>Jacob Simons</dc:creator>
      <dc:date>2016-03-07T21:38:33Z</dc:date>
    </item>
    <item>
      <title>Refer the link : https:/</title>
      <link>https://community.cisco.com/t5/wireless/2-new-1602i-ap-won-t-connect-to-vwlc/m-p/2871832#M56337</link>
      <description>&lt;P&gt;Refer the link : &lt;A href="https://supportforums.cisco.com/discussion/12341441/unable-join-cisco-ap-2602i-ap-wlc-2504-version-801000"&gt;https://supportforums.cisco.com/discussion/12341441/unable-join-cisco-ap-2602i-ap-wlc-2504-version-801000&lt;/A&gt;&lt;/P&gt;
&lt;P&gt;&lt;A href="https://supportforums.cisco.com/discussion/12562396/ap-fetal-error"&gt;https://supportforums.cisco.com/discussion/12562396/ap-fetal-error&lt;/A&gt;&lt;/P&gt;</description>
      <pubDate>Tue, 08 Mar 2016 01:50:35 GMT</pubDate>
      <guid>https://community.cisco.com/t5/wireless/2-new-1602i-ap-won-t-connect-to-vwlc/m-p/2871832#M56337</guid>
      <dc:creator>mohanak</dc:creator>
      <dc:date>2016-03-08T01:50:35Z</dc:date>
    </item>
    <item>
      <title>Thank you for your response. </title>
      <link>https://community.cisco.com/t5/wireless/2-new-1602i-ap-won-t-connect-to-vwlc/m-p/2871833#M56338</link>
      <description>&lt;P&gt;Thank you for your response.&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Both links look to be problems caused by the software level on the controller being version 8.&amp;nbsp; As I said in my first post I am running version 7.6.&lt;/P&gt;</description>
      <pubDate>Tue, 08 Mar 2016 14:17:18 GMT</pubDate>
      <guid>https://community.cisco.com/t5/wireless/2-new-1602i-ap-won-t-connect-to-vwlc/m-p/2871833#M56338</guid>
      <dc:creator>Jacob Simons</dc:creator>
      <dc:date>2016-03-08T14:17:18Z</dc:date>
    </item>
    <item>
      <title>Have you already tried to</title>
      <link>https://community.cisco.com/t5/wireless/2-new-1602i-ap-won-t-connect-to-vwlc/m-p/2871834#M56339</link>
      <description>&lt;P&gt;Have you already tried to download one of the latest &lt;SPAN&gt;ap1g2-k9w8&lt;/SPAN&gt; images from the Cisco website and install it manually?&lt;/P&gt;</description>
      <pubDate>Tue, 08 Mar 2016 19:25:05 GMT</pubDate>
      <guid>https://community.cisco.com/t5/wireless/2-new-1602i-ap-won-t-connect-to-vwlc/m-p/2871834#M56339</guid>
      <dc:creator>Freerk Terpstra</dc:creator>
      <dc:date>2016-03-08T19:25:05Z</dc:date>
    </item>
    <item>
      <title>Yes,  I did try with 15.3</title>
      <link>https://community.cisco.com/t5/wireless/2-new-1602i-ap-won-t-connect-to-vwlc/m-p/2871835#M56340</link>
      <description>&lt;P&gt;Yes,&amp;nbsp; I did try with 15.3.jbb6.&amp;nbsp; That was the newest I could download. I got the same result as with the stock IOS. I also put on the same IOS that I had used in the previous 1600's that we have purchased.&amp;nbsp; That is version 15.3.JA.&amp;nbsp; That also did the same thing.&lt;/P&gt;
&lt;P&gt;&lt;/P&gt;
&lt;P&gt;I also contacted the company that I purchased the AP's from.&amp;nbsp; There tech department is going to look into the issue and possibly send me a couple new access points.&lt;/P&gt;</description>
      <pubDate>Tue, 08 Mar 2016 20:26:13 GMT</pubDate>
      <guid>https://community.cisco.com/t5/wireless/2-new-1602i-ap-won-t-connect-to-vwlc/m-p/2871835#M56340</guid>
      <dc:creator>Jacob Simons</dc:creator>
      <dc:date>2016-03-08T20:26:13Z</dc:date>
    </item>
    <item>
      <title>I found out why they are</title>
      <link>https://community.cisco.com/t5/wireless/2-new-1602i-ap-won-t-connect-to-vwlc/m-p/2871836#M56341</link>
      <description>&lt;P&gt;I found out why they are behaving like they are.&amp;nbsp; The company that I bought them from gets them and then hooks them up to a WLC to make sure they work and such.&amp;nbsp; Their WLC is running software version 8.&amp;nbsp; Once it connects up to that the certificate gets updated and it won't connect to a controller running anything older.&lt;/P&gt;
&lt;P&gt;&lt;/P&gt;
&lt;P&gt;I even when so far as to delete everything out of the flash directory and reload from the rommon prompt but the cert is still there.&lt;/P&gt;
&lt;P&gt;&lt;/P&gt;
&lt;P&gt;I have them looking into whether they have any access points that haven't been hooked up to their controller yet that I can just reset myself.&lt;/P&gt;</description>
      <pubDate>Wed, 09 Mar 2016 20:44:09 GMT</pubDate>
      <guid>https://community.cisco.com/t5/wireless/2-new-1602i-ap-won-t-connect-to-vwlc/m-p/2871836#M56341</guid>
      <dc:creator>Jacob Simons</dc:creator>
      <dc:date>2016-03-09T20:44:09Z</dc:date>
    </item>
  </channel>
</rss>

