<?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: AP3602 cannot join vWLC with error message in Wireless</title>
    <link>https://community.cisco.com/t5/wireless/ap3602-cannot-join-vwlc-with-error-message/m-p/4283874#M225843</link>
    <description>&lt;P&gt;Thank you!&lt;/P&gt;</description>
    <pubDate>Mon, 01 Feb 2021 20:01:06 GMT</pubDate>
    <dc:creator>eigrpy</dc:creator>
    <dc:date>2021-02-01T20:01:06Z</dc:date>
    <item>
      <title>AP3602 cannot join vWLC with error message</title>
      <link>https://community.cisco.com/t5/wireless/ap3602-cannot-join-vwlc-with-error-message/m-p/4281893#M225672</link>
      <description>&lt;P&gt;Hello, AP3602E can ping vWLC(8.0.152.0), but cannot join it. I got the below error message from the AP. Do you think it is certificate expired or something else? Thank you&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;*Jan 13 02:32:41.003: %DTLS-5-SEND_ALERT: Send FATAL : Bad certificate Alert to 10.0.100.111:5246&lt;BR /&gt;*Jan 13 02:32:41.007: %DTLS-5-SEND_ALERT: Send FATAL : Close notify Alert to 10.0.100.111:5246&lt;BR /&gt;*Jan 13 02:33:59.000: %CAPWAP-5-DTLSREQSEND: DTLS connection request sent peer_ip: 10.0.100.111 peer_port: 5246&lt;BR /&gt;*Jan 13 02:34:04.999: DTLS_CLIENT_ERROR: ../capwap/base_capwap/dtls/base_capwap_dtls_handshake.c:929 Unexpected message received while expecting HelloVerifyRequest&lt;BR /&gt;*Jan 13 02:34:04.999: %DTLS-5-SEND_ALERT: Send FATAL : Unexpected message Alert to 10.0.100.111:5246&lt;BR /&gt;*Jan 13 02:34:04.999: %DTLS-5-SEND_ALERT: Send FATAL : Close notify Alert to 10.0.100.111:5246&lt;BR /&gt;*Jan 13 02:35:07.000: %CAPWAP-5-DTLSREQSEND: DTLS connection request sent peer_ip: 10.0.100.111 peer_port: 5246&lt;BR /&gt;*Jan 13 02:35:20.999: DTLS_CLIENT_ERROR: ../capwap/base_capwap/dtls/base_capwap_dtls_handshake.c:929 Unexpected message received while expecting HelloVerifyRequest&lt;BR /&gt;*Jan 13 02:35:20.999: %DTLS-5-SEND_ALERT: Send FATAL : Unexpected message Alert to 10.0.100.111:5246&lt;BR /&gt;*Jan 13 02:35:20.999: %DTLS-5-SEND_ALERT: Send FATAL : Close notify Alert to 10.0.100.111:5246&lt;/P&gt;</description>
      <pubDate>Mon, 05 Jul 2021 20:07:40 GMT</pubDate>
      <guid>https://community.cisco.com/t5/wireless/ap3602-cannot-join-vwlc-with-error-message/m-p/4281893#M225672</guid>
      <dc:creator>eigrpy</dc:creator>
      <dc:date>2021-07-05T20:07:40Z</dc:date>
    </item>
    <item>
      <title>Re: AP3602 cannot join vWLC with error message</title>
      <link>https://community.cisco.com/t5/wireless/ap3602-cannot-join-vwlc-with-error-message/m-p/4281894#M225673</link>
      <description>&lt;P&gt;Are you seeing any errors on the vWLC side? I also noticed that the time/date is off. Could have a negative effect on the certificates but not sure if the time synchronizes to NTP before or after connection with the vWLC.&lt;/P&gt;</description>
      <pubDate>Fri, 29 Jan 2021 02:50:09 GMT</pubDate>
      <guid>https://community.cisco.com/t5/wireless/ap3602-cannot-join-vwlc-with-error-message/m-p/4281894#M225673</guid>
      <dc:creator>TJ-20933766</dc:creator>
      <dc:date>2021-01-29T02:50:09Z</dc:date>
    </item>
    <item>
      <title>Re: AP3602 cannot join vWLC with error message</title>
      <link>https://community.cisco.com/t5/wireless/ap3602-cannot-join-vwlc-with-error-message/m-p/4281907#M225676</link>
      <description>&lt;P&gt;Thank you. its time issue&lt;/P&gt;</description>
      <pubDate>Fri, 29 Jan 2021 04:34:37 GMT</pubDate>
      <guid>https://community.cisco.com/t5/wireless/ap3602-cannot-join-vwlc-with-error-message/m-p/4281907#M225676</guid>
      <dc:creator>eigrpy</dc:creator>
      <dc:date>2021-01-29T04:34:37Z</dc:date>
    </item>
    <item>
      <title>Re: AP3602 cannot join vWLC with error message</title>
      <link>https://community.cisco.com/t5/wireless/ap3602-cannot-join-vwlc-with-error-message/m-p/4283821#M225838</link>
      <description>&lt;P&gt;Hi Tyson&lt;/P&gt;&lt;P&gt;You are right, the date and time is not correct in these log above, but why you say "&lt;SPAN&gt;I also noticed that the time/date is &lt;STRONG&gt;off&lt;/STRONG&gt;" ? Thanks&lt;/SPAN&gt;&lt;/P&gt;</description>
      <pubDate>Mon, 01 Feb 2021 19:56:32 GMT</pubDate>
      <guid>https://community.cisco.com/t5/wireless/ap3602-cannot-join-vwlc-with-error-message/m-p/4283821#M225838</guid>
      <dc:creator>eigrpy</dc:creator>
      <dc:date>2021-02-01T19:56:32Z</dc:date>
    </item>
    <item>
      <title>Re: AP3602 cannot join vWLC with error message</title>
      <link>https://community.cisco.com/t5/wireless/ap3602-cannot-join-vwlc-with-error-message/m-p/4283843#M225841</link>
      <description>&lt;P&gt;The post was listed on Jan 28th and the logs showed a date of Jan 13th. I made an assumption that the logs were not 15 days old plus the asterisk (*) at the beginning of a log entry usually means that the time/date stamp cannot be trusted because the clock is not synchronized with an NTP server.&lt;/P&gt;</description>
      <pubDate>Mon, 01 Feb 2021 19:20:53 GMT</pubDate>
      <guid>https://community.cisco.com/t5/wireless/ap3602-cannot-join-vwlc-with-error-message/m-p/4283843#M225841</guid>
      <dc:creator>TJ-20933766</dc:creator>
      <dc:date>2021-02-01T19:20:53Z</dc:date>
    </item>
    <item>
      <title>Re: AP3602 cannot join vWLC with error message</title>
      <link>https://community.cisco.com/t5/wireless/ap3602-cannot-join-vwlc-with-error-message/m-p/4283874#M225843</link>
      <description>&lt;P&gt;Thank you!&lt;/P&gt;</description>
      <pubDate>Mon, 01 Feb 2021 20:01:06 GMT</pubDate>
      <guid>https://community.cisco.com/t5/wireless/ap3602-cannot-join-vwlc-with-error-message/m-p/4283874#M225843</guid>
      <dc:creator>eigrpy</dc:creator>
      <dc:date>2021-02-01T20:01:06Z</dc:date>
    </item>
  </channel>
</rss>

