<?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: AP Not Joining request Failed in Controllers</title>
    <link>https://community.cisco.com/t5/controllers/ap-not-joining-request-failed/m-p/4725402#M808</link>
    <description>&lt;P&gt;Hi,&lt;/P&gt;&lt;P&gt;check this one out&amp;nbsp;&lt;STRONG&gt;&lt;A href="https://community.cisco.com/t5/wireless-mobility-knowledge-base/lightweight-ap-fail-to-create-capwap-lwapp-connection-due-to/ta-p/3155111" target="_blank" rel="noopener"&gt;https://community.cisco.com/t5/wireless-mobility-knowledge-base/lightweight-ap-fail-to-create-capwap-lwapp-connection-due-to/ta-p/3155111&lt;/A&gt;&lt;/STRONG&gt;&lt;/P&gt;&lt;P&gt;If AP is fairly new, you can try checking a few things:&lt;/P&gt;&lt;P&gt;&amp;nbsp;1. Version might be better to be at the same number.&lt;/P&gt;&lt;P&gt;2. Config WLC to accept those new certificates not yet installed in the WLC (which is tearing down the TLS):&lt;/P&gt;&lt;P&gt;&lt;EM&gt;For 7.0.252.0:&lt;/EM&gt;&lt;BR /&gt;(WLC)&amp;gt;&lt;STRONG&gt;&lt;EM&gt;config ap lifetime-check {mic|ssc} enable&lt;/EM&gt;&lt;/STRONG&gt;&lt;/P&gt;&lt;P&gt;&lt;EM&gt;For 7.4.140.0 and later:&lt;/EM&gt;&lt;BR /&gt;(WLC)&amp;gt;&lt;STRONG&gt;config ap cert-expiry-ignore {mic|ssc} enable&lt;/STRONG&gt;&lt;/P&gt;&lt;P&gt;3. NTP might be an issue, try checking the clock in the AP which should be close to the WLC one, if not, apply a NTP field in the DHCP for the AP so it can be up to date and connect to the WLC.&lt;/P&gt;&lt;P&gt;hope that helps,&lt;/P&gt;&lt;P&gt;AIV&lt;/P&gt;</description>
    <pubDate>Mon, 21 Nov 2022 19:29:40 GMT</pubDate>
    <dc:creator>KyoCode</dc:creator>
    <dc:date>2022-11-21T19:29:40Z</dc:date>
    <item>
      <title>AP Not Joining request Failed</title>
      <link>https://community.cisco.com/t5/controllers/ap-not-joining-request-failed/m-p/4725314#M806</link>
      <description>&lt;P&gt;Hi guys.&lt;/P&gt;&lt;P&gt;AP 1562E-not joining vWlc. I have attached the logs.&lt;/P&gt;&lt;P&gt;Kindly suggest.&lt;/P&gt;&lt;P&gt;&lt;STRONG&gt;dtls_verify_con_cert: vWLC Certificate verification error&lt;/STRONG&gt;&lt;BR /&gt;&lt;STRONG&gt;dtls_process_packet: Controller certificate verification failed&lt;/STRONG&gt;&lt;BR /&gt;&lt;STRONG&gt;sendPacketToDtls: DTLS: Closing connection 0x2147c00.&lt;/STRONG&gt;&lt;BR /&gt;&lt;STRONG&gt;Lost connection to the controller, going to restart CAPWAP (reason : dtls_rc_connection_closed)...&lt;/STRONG&gt;&lt;BR /&gt;&lt;STRONG&gt;DTLS: Error while processing DTLS packet 0x21b1000.&lt;/STRONG&gt;&lt;BR /&gt;&lt;STRONG&gt;Restarting CAPWAP State Machine.&lt;/STRONG&gt;&lt;BR /&gt;&lt;STRONG&gt;Discarding msg CAPWAP_WTP_EVENT_REQUEST(type 9) in CAPWAP state: DTLS Setup(3).&lt;/STRONG&gt;&lt;BR /&gt;&lt;STRONG&gt;Failed to disconnect DTLS-CTRL session.&lt;/STRONG&gt;&lt;/P&gt;&lt;P&gt;&lt;STRONG&gt;CAPWAP State: DTLS Teardown&lt;/STRONG&gt;&lt;BR /&gt;&lt;STRONG&gt;No more AP manager addresses remain..&lt;/STRONG&gt;&lt;BR /&gt;&lt;STRONG&gt;No valid AP manager found for controller 'cisco-vWLC' (ip: 172.168.81.218)&lt;/STRONG&gt;&lt;BR /&gt;&lt;STRONG&gt;Failed to join controller cisco-vWLC.&lt;/STRONG&gt;&lt;BR /&gt;&lt;STRONG&gt;Failed to join controller.&lt;/STRONG&gt;&lt;/P&gt;&lt;P&gt;&lt;STRONG&gt;CAPWAP State: Discovery&lt;/STRONG&gt;&lt;BR /&gt;&lt;STRONG&gt;Discovery Request sent to 172.168.81.xxx, discovery type STATIC_CONFIG(1)&lt;/STRONG&gt;&lt;BR /&gt;&lt;STRONG&gt;Discovery Request sent to 172.168.81.xxx, discovery type STATIC_CONFIG(1)&lt;/STRONG&gt;&lt;BR /&gt;&lt;STRONG&gt;Discovery Request sent to 255.255.255.255, discovery type UNKNOWN(0)&lt;/STRONG&gt;&lt;BR /&gt;&lt;STRONG&gt;Discovery Response from 172.168.81.xxx&lt;/STRONG&gt;&lt;BR /&gt;&lt;STRONG&gt;Unsupported vendor spec payload TLV_VENDOR_SPECIFIC_PAYLOAD(215) for msgtype 2&lt;/STRONG&gt;&lt;BR /&gt;&lt;STRONG&gt;Discovery Response from 172.168.81.xxx&lt;/STRONG&gt;&lt;BR /&gt;&lt;STRONG&gt;Unsupported vendor spec payload TLV_VENDOR_SPECIFIC_PAYLOAD(215) for msgtype 2&lt;/STRONG&gt;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Mon, 21 Nov 2022 15:26:46 GMT</pubDate>
      <guid>https://community.cisco.com/t5/controllers/ap-not-joining-request-failed/m-p/4725314#M806</guid>
      <dc:creator>Rohatash Singh</dc:creator>
      <dc:date>2022-11-21T15:26:46Z</dc:date>
    </item>
    <item>
      <title>Re: AP Not Joining request Failed</title>
      <link>https://community.cisco.com/t5/controllers/ap-not-joining-request-failed/m-p/4725401#M807</link>
      <description>&lt;P&gt;what is the version vWLC ? do you have any other AP joined or are none of them working?&lt;/P&gt;
&lt;P&gt;Do you have enough License?&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Mon, 21 Nov 2022 19:25:34 GMT</pubDate>
      <guid>https://community.cisco.com/t5/controllers/ap-not-joining-request-failed/m-p/4725401#M807</guid>
      <dc:creator>balaji.bandi</dc:creator>
      <dc:date>2022-11-21T19:25:34Z</dc:date>
    </item>
    <item>
      <title>Re: AP Not Joining request Failed</title>
      <link>https://community.cisco.com/t5/controllers/ap-not-joining-request-failed/m-p/4725402#M808</link>
      <description>&lt;P&gt;Hi,&lt;/P&gt;&lt;P&gt;check this one out&amp;nbsp;&lt;STRONG&gt;&lt;A href="https://community.cisco.com/t5/wireless-mobility-knowledge-base/lightweight-ap-fail-to-create-capwap-lwapp-connection-due-to/ta-p/3155111" target="_blank" rel="noopener"&gt;https://community.cisco.com/t5/wireless-mobility-knowledge-base/lightweight-ap-fail-to-create-capwap-lwapp-connection-due-to/ta-p/3155111&lt;/A&gt;&lt;/STRONG&gt;&lt;/P&gt;&lt;P&gt;If AP is fairly new, you can try checking a few things:&lt;/P&gt;&lt;P&gt;&amp;nbsp;1. Version might be better to be at the same number.&lt;/P&gt;&lt;P&gt;2. Config WLC to accept those new certificates not yet installed in the WLC (which is tearing down the TLS):&lt;/P&gt;&lt;P&gt;&lt;EM&gt;For 7.0.252.0:&lt;/EM&gt;&lt;BR /&gt;(WLC)&amp;gt;&lt;STRONG&gt;&lt;EM&gt;config ap lifetime-check {mic|ssc} enable&lt;/EM&gt;&lt;/STRONG&gt;&lt;/P&gt;&lt;P&gt;&lt;EM&gt;For 7.4.140.0 and later:&lt;/EM&gt;&lt;BR /&gt;(WLC)&amp;gt;&lt;STRONG&gt;config ap cert-expiry-ignore {mic|ssc} enable&lt;/STRONG&gt;&lt;/P&gt;&lt;P&gt;3. NTP might be an issue, try checking the clock in the AP which should be close to the WLC one, if not, apply a NTP field in the DHCP for the AP so it can be up to date and connect to the WLC.&lt;/P&gt;&lt;P&gt;hope that helps,&lt;/P&gt;&lt;P&gt;AIV&lt;/P&gt;</description>
      <pubDate>Mon, 21 Nov 2022 19:29:40 GMT</pubDate>
      <guid>https://community.cisco.com/t5/controllers/ap-not-joining-request-failed/m-p/4725402#M808</guid>
      <dc:creator>KyoCode</dc:creator>
      <dc:date>2022-11-21T19:29:40Z</dc:date>
    </item>
    <item>
      <title>Re: AP Not Joining request Failed</title>
      <link>https://community.cisco.com/t5/controllers/ap-not-joining-request-failed/m-p/4725472#M809</link>
      <description>&lt;P&gt;Post the complete output to the following commands:&amp;nbsp;&lt;/P&gt;
&lt;OL&gt;
&lt;LI&gt;WLC:&amp;nbsp; sh sysinfo&lt;/LI&gt;
&lt;LI&gt;WLC:&amp;nbsp; sh time&lt;/LI&gt;
&lt;LI&gt;AP:&amp;nbsp; sh capwap client rcb&lt;/LI&gt;
&lt;LI&gt;AP:&amp;nbsp; sh version&lt;/LI&gt;
&lt;/OL&gt;</description>
      <pubDate>Mon, 21 Nov 2022 22:07:01 GMT</pubDate>
      <guid>https://community.cisco.com/t5/controllers/ap-not-joining-request-failed/m-p/4725472#M809</guid>
      <dc:creator>Leo Laohoo</dc:creator>
      <dc:date>2022-11-21T22:07:01Z</dc:date>
    </item>
    <item>
      <title>Re: AP Not Joining request Failed</title>
      <link>https://community.cisco.com/t5/controllers/ap-not-joining-request-failed/m-p/4726554#M810</link>
      <description>&lt;P&gt;Hi,&lt;/P&gt;&lt;P&gt;Vwlc version is -8.10.181.&lt;/P&gt;&lt;P&gt;No other AP has joined&lt;/P&gt;&lt;P&gt;It's showing 200 AP supported&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Wed, 23 Nov 2022 11:28:58 GMT</pubDate>
      <guid>https://community.cisco.com/t5/controllers/ap-not-joining-request-failed/m-p/4726554#M810</guid>
      <dc:creator>Rohatash Singh</dc:creator>
      <dc:date>2022-11-23T11:28:58Z</dc:date>
    </item>
    <item>
      <title>Re: AP Not Joining request Failed</title>
      <link>https://community.cisco.com/t5/controllers/ap-not-joining-request-failed/m-p/4726599#M812</link>
      <description>&lt;BLOCKQUOTE&gt;&lt;HR /&gt;&amp;nbsp;wrote:&lt;a href="https://community.cisco.com/t5/user/viewprofilepage/user-id/1435635"&gt;@Rohatash Singh &lt;/a&gt;&lt;BR /&gt;&lt;SPAN&gt;AP Image type : MOBILITY EXPRESS IMAGE&lt;/SPAN&gt;&lt;HR /&gt;&lt;/BLOCKQUOTE&gt;
&lt;P&gt;The 1562 is loaded with Mobility Express firmware.&lt;/P&gt;</description>
      <pubDate>Wed, 23 Nov 2022 13:23:47 GMT</pubDate>
      <guid>https://community.cisco.com/t5/controllers/ap-not-joining-request-failed/m-p/4726599#M812</guid>
      <dc:creator>Leo Laohoo</dc:creator>
      <dc:date>2022-11-23T13:23:47Z</dc:date>
    </item>
  </channel>
</rss>

