<?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: WLC 2504 Controlller / AIR-CAP2602I-E-K9 / Self Signed Certificate in Wireless</title>
    <link>https://community.cisco.com/t5/wireless/re-wlc-2504-controlller-air-cap2602i-e-k9-self-signed/m-p/5278534#M282187</link>
    <description>&lt;P&gt;Wind back the date of the WLC to 1 year back.&lt;/P&gt;
&lt;P&gt;Once the APs join the WLC, put the correct time and date back on.&lt;/P&gt;</description>
    <pubDate>Fri, 04 Apr 2025 23:31:50 GMT</pubDate>
    <dc:creator>Leo Laohoo</dc:creator>
    <dc:date>2025-04-04T23:31:50Z</dc:date>
    <item>
      <title>Re: WLC 2504 Controlller / AIR-CAP2602I-E-K9 / Self Signed Certificate</title>
      <link>https://community.cisco.com/t5/wireless/re-wlc-2504-controlller-air-cap2602i-e-k9-self-signed/m-p/5278459#M282184</link>
      <description>&lt;P&gt;It would appear that there is a new snag to the expiring certificates that I ran into on a WLC 2504 with 8.5.160 and AP's of 3602i and 3702i. Specifically, the WLC certificate expired on Feb 17th 2025 and I guess the APs stay connected until something kicks them off, which happened recently to me.&lt;/P&gt;&lt;P&gt;The usual SSC/MIC ignore expiry problem doesn't apply since it's the WLC that isn't trusted now:&lt;/P&gt;&lt;P&gt;Apr 4 17:26:40.011: %PKI-3-CERTIFICATE_INVALID_EXPIRED: Certificate chain validation has failed. The certificate (SN: 4FD99CF4000000103486) has expired. Validity period ended on 00:18:54 UTC Feb 17 2025Peer certificate verification failed 001A&lt;/P&gt;&lt;P&gt;The consensus online appears to be to jump the clocks back and disable NTP etc. Any other tips? While it sounds like the 8.5.182.7 might fix this, I am not 100% sure it wouldn't have other issues that reference Wave 1 AP problems or not, but it sounds like I am pretty much stuck at this point, at least without going to a vWLC or similar.&lt;/P&gt;&lt;P&gt;Any advice or tips? It would be nice to NOT have to force an emergency forklift upgrade on the WiFi just yet! &lt;span class="lia-unicode-emoji" title=":slightly_smiling_face:"&gt;🙂&lt;/span&gt;&lt;/P&gt;</description>
      <pubDate>Fri, 04 Apr 2025 17:32:44 GMT</pubDate>
      <guid>https://community.cisco.com/t5/wireless/re-wlc-2504-controlller-air-cap2602i-e-k9-self-signed/m-p/5278459#M282184</guid>
      <dc:creator>dmcgrath.ca</dc:creator>
      <dc:date>2025-04-04T17:32:44Z</dc:date>
    </item>
    <item>
      <title>Re: WLC 2504 Controlller / AIR-CAP2602I-E-K9 / Self Signed Certificate</title>
      <link>https://community.cisco.com/t5/wireless/re-wlc-2504-controlller-air-cap2602i-e-k9-self-signed/m-p/5278534#M282187</link>
      <description>&lt;P&gt;Wind back the date of the WLC to 1 year back.&lt;/P&gt;
&lt;P&gt;Once the APs join the WLC, put the correct time and date back on.&lt;/P&gt;</description>
      <pubDate>Fri, 04 Apr 2025 23:31:50 GMT</pubDate>
      <guid>https://community.cisco.com/t5/wireless/re-wlc-2504-controlller-air-cap2602i-e-k9-self-signed/m-p/5278534#M282187</guid>
      <dc:creator>Leo Laohoo</dc:creator>
      <dc:date>2025-04-04T23:31:50Z</dc:date>
    </item>
    <item>
      <title>Re: WLC 2504 Controlller / AIR-CAP2602I-E-K9 / Self Signed Certificate</title>
      <link>https://community.cisco.com/t5/wireless/re-wlc-2504-controlller-air-cap2602i-e-k9-self-signed/m-p/5278579#M282192</link>
      <description>&lt;P&gt;That is&amp;nbsp;&lt;STRONG&gt;not&lt;/STRONG&gt; new - it was covered in Field Notice&amp;nbsp;FN63942 years ago (link below)!&lt;BR /&gt;&lt;A href="https://bst.cloudapps.cisco.com/bugsearch/bug/CSCuq19142" target="_blank"&gt;https://bst.cloudapps.cisco.com/bugsearch/bug/CSCuq19142&lt;/A&gt;&amp;nbsp;description specifically says "&lt;SPAN&gt;LAP/&lt;FONT color="#FF0000"&gt;&lt;STRONG&gt;WLC&lt;/STRONG&gt; &lt;/FONT&gt;MIC or SSC lifetime expiration causes DTLS failure" and WLC cert expiry is covered by Symptom 2 in the notes.&amp;nbsp; There are a number of other linked bugs for specific corner cases.&lt;/SPAN&gt;&lt;BR /&gt;The solution hasn't changed - you need to follow &lt;STRONG&gt;ALL&lt;/STRONG&gt; the steps in the field notice which means upgrading to latest software release &lt;STRONG&gt;+&lt;/STRONG&gt; the cert ignore config.&amp;nbsp; And it has to be done in the correct order (with setting date back to a date which matches WLC &lt;STRONG&gt;and&lt;/STRONG&gt; AP certs before you can do anything else) to get the software and the config applied to every AP.&lt;/P&gt;
&lt;P&gt;The software version you should be running is &lt;STRONG&gt;8.5.182.12&lt;/STRONG&gt; - link below (that's the final release for 2504).&lt;/P&gt;
&lt;P&gt;So you don't need a forklift emergency upgrade right now, but that technology is well past sell-by date so you do need to urgently look at upgrading.&lt;/P&gt;</description>
      <pubDate>Sat, 05 Apr 2025 10:03:14 GMT</pubDate>
      <guid>https://community.cisco.com/t5/wireless/re-wlc-2504-controlller-air-cap2602i-e-k9-self-signed/m-p/5278579#M282192</guid>
      <dc:creator>Rich R</dc:creator>
      <dc:date>2025-04-05T10:03:14Z</dc:date>
    </item>
  </channel>
</rss>

