<?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 APs not joining time is correct in Wireless</title>
    <link>https://community.cisco.com/t5/wireless/wlc-2504-aps-not-joining-time-is-correct/m-p/4698399#M246785</link>
    <description>&lt;P&gt;I apologize rrudling, I sure feel like an a**.&amp;nbsp;&lt;/P&gt;&lt;P&gt;I went through the field notice briefly just now and will go into detail when I'm on site again.. Thanks.&lt;/P&gt;</description>
    <pubDate>Tue, 04 Oct 2022 23:59:39 GMT</pubDate>
    <dc:creator>Elesh</dc:creator>
    <dc:date>2022-10-04T23:59:39Z</dc:date>
    <item>
      <title>wlc 2504 APs not joining time is correct</title>
      <link>https://community.cisco.com/t5/wireless/wlc-2504-aps-not-joining-time-is-correct/m-p/4696946#M246638</link>
      <description>&lt;P&gt;My APs are not joining the controller all of a sudden. The APs used to work fine but after a reboot ALL of them are not joining.&amp;nbsp;&lt;/P&gt;&lt;P&gt;I set the date and time manually and set a NTP server and rebooted, but still have the same issue. I can ping the APs.&lt;/P&gt;&lt;P&gt;Under Statistics -&amp;gt; ap join, I select the AP. Under discovery phase stats, it shows last successful attempt with a recent time, and last unsuccessful attemp is blank. There are no errors, all blank&lt;/P&gt;&lt;P&gt;One funny thing I notice when i run&amp;nbsp; Show Sysinfo is this line:&lt;/P&gt;&lt;P&gt;OUI File Last Update Time........................ Sun Sep 07 10:44:07 IST 2014&lt;/P&gt;&lt;P&gt;Does anyone have any ideas?&lt;/P&gt;</description>
      <pubDate>Fri, 30 Sep 2022 19:08:22 GMT</pubDate>
      <guid>https://community.cisco.com/t5/wireless/wlc-2504-aps-not-joining-time-is-correct/m-p/4696946#M246638</guid>
      <dc:creator>Elesh</dc:creator>
      <dc:date>2022-09-30T19:08:22Z</dc:date>
    </item>
    <item>
      <title>Re: wlc 2504 APs not joining time is correct</title>
      <link>https://community.cisco.com/t5/wireless/wlc-2504-aps-not-joining-time-is-correct/m-p/4697001#M246646</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;AP:&amp;nbsp; sh version&lt;/LI&gt;
&lt;/OL&gt;</description>
      <pubDate>Sat, 01 Oct 2022 00:45:54 GMT</pubDate>
      <guid>https://community.cisco.com/t5/wireless/wlc-2504-aps-not-joining-time-is-correct/m-p/4697001#M246646</guid>
      <dc:creator>Leo Laohoo</dc:creator>
      <dc:date>2022-10-01T00:45:54Z</dc:date>
    </item>
    <item>
      <title>Re: wlc 2504 APs not joining time is correct</title>
      <link>https://community.cisco.com/t5/wireless/wlc-2504-aps-not-joining-time-is-correct/m-p/4697123#M246656</link>
      <description>&lt;P&gt;Read this field notice very carefully, twice if necessary:&amp;nbsp;&lt;A href="https://www.cisco.com/c/en/us/support/docs/field-notices/639/fn63942.html" target="_blank"&gt;https://www.cisco.com/c/en/us/support/docs/field-notices/639/fn63942.html&lt;/A&gt;&lt;/P&gt;
&lt;P&gt;I've posted a summary of this numerous times before - if you search you'll find it - which is what you should be doing before posting the same thing many others have ...&lt;/P&gt;</description>
      <pubDate>Sat, 01 Oct 2022 19:13:47 GMT</pubDate>
      <guid>https://community.cisco.com/t5/wireless/wlc-2504-aps-not-joining-time-is-correct/m-p/4697123#M246656</guid>
      <dc:creator>Rich R</dc:creator>
      <dc:date>2022-10-01T19:13:47Z</dc:date>
    </item>
    <item>
      <title>Re: wlc 2504 APs not joining time is correct</title>
      <link>https://community.cisco.com/t5/wireless/wlc-2504-aps-not-joining-time-is-correct/m-p/4697291#M246669</link>
      <description>&lt;P&gt;I've tried to search but was unable to find your post.. Could you provide a link?&lt;/P&gt;</description>
      <pubDate>Sun, 02 Oct 2022 20:03:41 GMT</pubDate>
      <guid>https://community.cisco.com/t5/wireless/wlc-2504-aps-not-joining-time-is-correct/m-p/4697291#M246669</guid>
      <dc:creator>Elesh</dc:creator>
      <dc:date>2022-10-02T20:03:41Z</dc:date>
    </item>
    <item>
      <title>Re: wlc 2504 APs not joining time is correct</title>
      <link>https://community.cisco.com/t5/wireless/wlc-2504-aps-not-joining-time-is-correct/m-p/4697300#M246671</link>
      <description>&lt;P&gt;Another thing that I noticed is the the NTP is not syncng. Here is my output for sh time:&lt;/P&gt;&lt;P&gt;Time............................................. Sun Oct 2 13:56:58 2022&lt;/P&gt;&lt;P&gt;Timezone delta................................... 0:0&lt;BR /&gt;Timezone location................................ (GMT -8:00) Pacific Time (US and Canada)&lt;/P&gt;&lt;P&gt;NTP Servers&lt;BR /&gt;NTP Version.................................. 3&lt;BR /&gt;NTP Polling Interval......................... 3500&lt;/P&gt;&lt;P&gt;Index NTP Key Index NTP Server Status NTP Msg Auth Status&lt;BR /&gt;------- ---------------------------------------------------------------------&lt;BR /&gt;1 0 0.pool.ntp.org Not Synched AUTH DISABLED&lt;BR /&gt;2 0 1.pool.ntp.org Not Synched AUTH DISABLED&lt;BR /&gt;3 0 time.windows.com In Progress AUTH DISABLED&lt;/P&gt;</description>
      <pubDate>Sun, 02 Oct 2022 21:00:00 GMT</pubDate>
      <guid>https://community.cisco.com/t5/wireless/wlc-2504-aps-not-joining-time-is-correct/m-p/4697300#M246671</guid>
      <dc:creator>Elesh</dc:creator>
      <dc:date>2022-10-02T21:00:00Z</dc:date>
    </item>
    <item>
      <title>Re: wlc 2504 APs not joining time is correct</title>
      <link>https://community.cisco.com/t5/wireless/wlc-2504-aps-not-joining-time-is-correct/m-p/4697309#M246674</link>
      <description>&lt;P&gt;Try only set date and time without NTP.&lt;/P&gt;
&lt;P&gt;Do you have Mac ACL for the APS?&lt;/P&gt;</description>
      <pubDate>Sun, 02 Oct 2022 21:58:57 GMT</pubDate>
      <guid>https://community.cisco.com/t5/wireless/wlc-2504-aps-not-joining-time-is-correct/m-p/4697309#M246674</guid>
      <dc:creator>CarlosdeAssuncao</dc:creator>
      <dc:date>2022-10-02T21:58:57Z</dc:date>
    </item>
    <item>
      <title>Re: wlc 2504 APs not joining time is correct</title>
      <link>https://community.cisco.com/t5/wireless/wlc-2504-aps-not-joining-time-is-correct/m-p/4697407#M246687</link>
      <description>&lt;P&gt;Admittedly the search is not very good:&amp;nbsp;&lt;A href="https://community.cisco.com/t5/wireless/problem-getting-lap-s-to-re-regiser-with-wlc/m-p/4691443/highlight/true#M246270" target="_blank"&gt;https://community.cisco.com/t5/wireless/problem-getting-lap-s-to-re-regiser-with-wlc/m-p/4691443/highlight/true#M246270&lt;/A&gt;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Mon, 03 Oct 2022 07:38:36 GMT</pubDate>
      <guid>https://community.cisco.com/t5/wireless/wlc-2504-aps-not-joining-time-is-correct/m-p/4697407#M246687</guid>
      <dc:creator>Rich R</dc:creator>
      <dc:date>2022-10-03T07:38:36Z</dc:date>
    </item>
    <item>
      <title>Re: wlc 2504 APs not joining time is correct</title>
      <link>https://community.cisco.com/t5/wireless/wlc-2504-aps-not-joining-time-is-correct/m-p/4697408#M246688</link>
      <description>&lt;P&gt;Cisco devices (certainly IOS anyway) have a habit of looking up the DNS for those names at boot time only and never again.&amp;nbsp; So if the IP address changes they will never know - they still keep trying the same old IP forever.&amp;nbsp; I suspect you'll either need to add IP addresses and check them regularly or delete and re-add the names to force new IP lookup.&amp;nbsp; You need to disable NTP to fix your cert problem anyway.&lt;/P&gt;</description>
      <pubDate>Mon, 03 Oct 2022 07:42:42 GMT</pubDate>
      <guid>https://community.cisco.com/t5/wireless/wlc-2504-aps-not-joining-time-is-correct/m-p/4697408#M246688</guid>
      <dc:creator>Rich R</dc:creator>
      <dc:date>2022-10-03T07:42:42Z</dc:date>
    </item>
    <item>
      <title>Re: wlc 2504 APs not joining time is correct</title>
      <link>https://community.cisco.com/t5/wireless/wlc-2504-aps-not-joining-time-is-correct/m-p/4697409#M246689</link>
      <description>&lt;P&gt;ps: the OUI will be the one which came with the WLC code unless you update it manually but beware:&amp;nbsp;&lt;A href="https://bst.cisco.com/bugsearch/bug/CSCvg66702" target="_blank"&gt;https://bst.cisco.com/bugsearch/bug/CSCvg66702&lt;/A&gt;&amp;nbsp;&lt;SPAN class="subheader-large"&gt;OUI Update failure and WLC System reloads unexpectedly while updating the OUI file&lt;/SPAN&gt;&lt;BR /&gt;Also updating the OUI doesn't actually add new OUI's it just updates the ones it already has if they've changed so pretty pointless most of the time.&lt;BR /&gt;The only way to really get updates properly is with a new version of WLC code but Cisco's support for that is quite limited now.&lt;BR /&gt;What they really want you to do is use ISE for device identification - that gets regular updates.&lt;/P&gt;</description>
      <pubDate>Mon, 03 Oct 2022 07:50:00 GMT</pubDate>
      <guid>https://community.cisco.com/t5/wireless/wlc-2504-aps-not-joining-time-is-correct/m-p/4697409#M246689</guid>
      <dc:creator>Rich R</dc:creator>
      <dc:date>2022-10-03T07:50:00Z</dc:date>
    </item>
    <item>
      <title>Re: wlc 2504 APs not joining time is correct</title>
      <link>https://community.cisco.com/t5/wireless/wlc-2504-aps-not-joining-time-is-correct/m-p/4698358#M246776</link>
      <description>&lt;P&gt;Here is the output form the commands:&lt;/P&gt;&lt;P&gt;&lt;STRONG&gt;wlc: sh sysinfo&lt;/STRONG&gt;&lt;BR /&gt;(Cisco Controller) &amp;gt;show sysinfo&lt;/P&gt;&lt;P&gt;Manufacturer's Name.............................. Cisco Systems Inc.&lt;BR /&gt;Product Name..................................... Cisco Controller&lt;BR /&gt;Product Version.................................. 8.5.151.0&lt;BR /&gt;Bootloader Version............................... 1.0.16&lt;BR /&gt;Field Recovery Image Version..................... 1.0.0&lt;BR /&gt;Firmware Version................................. PIC 16.0&lt;/P&gt;&lt;P&gt;&lt;BR /&gt;OUI File Last Update Time........................ Sun Sep 07 10:44:07 IST 2014&lt;/P&gt;&lt;P&gt;&lt;BR /&gt;Build Type....................................... DATA + WPS&lt;/P&gt;&lt;P&gt;System Name...................................... Cisco_db:cc:e5&lt;BR /&gt;System Location..................................&lt;BR /&gt;System Contact...................................&lt;BR /&gt;System ObjectID.................................. 1.3.6.1.4.1.9.1.1279&lt;BR /&gt;IP Address....................................... 192.168.1.200&lt;BR /&gt;IPv6 Address..................................... ::&lt;BR /&gt;Last Reset....................................... Power on reset&lt;BR /&gt;System Up Time................................... 0 days 0 hrs 2 mins 21 secs&lt;BR /&gt;System Timezone Location......................... (GMT -8:00) Pacific Time (US a nd Canada)&lt;/P&gt;&lt;P&gt;--More-- or (q)uit&lt;BR /&gt;System Stats Realtime Interval................... 5&lt;BR /&gt;System Stats Normal Interval..................... 180&lt;/P&gt;&lt;P&gt;Configured Country............................... US - United States&lt;BR /&gt;Operating Environment............................ Commercial (0 to 40 C)&lt;BR /&gt;Internal Temp Alarm Limits....................... 0 to 65 C&lt;BR /&gt;Internal Temperature............................. +27 C&lt;BR /&gt;External Temperature............................. +30 C&lt;BR /&gt;Fan Status....................................... 4800 rpm&lt;/P&gt;&lt;P&gt;State of 802.11b Network......................... Disabled&lt;BR /&gt;State of 802.11a Network......................... Enabled&lt;BR /&gt;Number of WLANs.................................. 1&lt;BR /&gt;Number of Active Clients......................... 0&lt;/P&gt;&lt;P&gt;OUI Classification Failure Count................. 0&lt;/P&gt;&lt;P&gt;Memory Current Usage............................. 34&lt;BR /&gt;Memory Average Usage............................. 36&lt;BR /&gt;CPU Current Usage................................ 0&lt;BR /&gt;CPU Average Usage................................ 0&lt;/P&gt;&lt;P&gt;Flash Type....................................... Compact Flash Card&lt;/P&gt;&lt;P&gt;--More-- or (q)uit&lt;BR /&gt;Flash Size....................................... 1073741824&lt;/P&gt;&lt;P&gt;Burned-in MAC Address............................ 64:D8:14:DB:CC:E0&lt;BR /&gt;Maximum number of APs supported.................. 75&lt;BR /&gt;System Nas-Id....................................&lt;BR /&gt;WLC MIC Certificate Types........................ SHA1&lt;/P&gt;&lt;P&gt;&lt;BR /&gt;&lt;STRONG&gt;AP: sh version&lt;/STRONG&gt;&lt;/P&gt;&lt;P&gt;ROM: Bootstrap program is U-Boot boot loader&lt;BR /&gt;BOOTLDR: U-Boot boot loader Version 30&lt;/P&gt;&lt;P&gt;APC064.E444.0628 uptime is 0 days, 0 hours, 8 minutes&lt;BR /&gt;Last reload time : Sun Oct 2 14:57:11 UTC 2022&lt;BR /&gt;Last reload reason : Capwap Discovery Failed&lt;/P&gt;&lt;P&gt;memory. -AP1832I-B-K9 ARMv7 Processor rev 0 (v7l) with 997268/801636K bytes of --More--&lt;BR /&gt;Processor board ID KWC232506ZF&lt;BR /&gt;AP Running Image : 8.5.151.0&lt;BR /&gt;Primary Boot Image : 8.5.151.0&lt;BR /&gt;Backup Boot Image : 8.3.143.4&lt;BR /&gt;1 Gigabit Ethernet interfaces&lt;BR /&gt;2 802.11 Radios&lt;BR /&gt;Radio FW version : f6d58b5e05c762162e07fe70e0671647&lt;BR /&gt;NSS FW version : NSS.AK.C.CS-3-fix3&lt;/P&gt;&lt;P&gt;Base ethernet MAC Address : C0:64:E4:44:06:28&lt;BR /&gt;Part Number : 0-0000-00&lt;BR /&gt;PCA Assembly Number : 074-104694-02&lt;BR /&gt;PCA Revision Number : 01&lt;BR /&gt;PCB Serial Number : KWC232506ZF&lt;BR /&gt;Top Assembly Part Number : 074-104694-02&lt;BR /&gt;Top Assembly Serial Number : KWC232506ZF&lt;BR /&gt;Top Revision Number : A0&lt;BR /&gt;Product/Model Number : AIR-AP1832I-B-K9&lt;/P&gt;</description>
      <pubDate>Tue, 04 Oct 2022 21:06:07 GMT</pubDate>
      <guid>https://community.cisco.com/t5/wireless/wlc-2504-aps-not-joining-time-is-correct/m-p/4698358#M246776</guid>
      <dc:creator>Elesh</dc:creator>
      <dc:date>2022-10-04T21:06:07Z</dc:date>
    </item>
    <item>
      <title>Re: wlc 2504 APs not joining time is correct</title>
      <link>https://community.cisco.com/t5/wireless/wlc-2504-aps-not-joining-time-is-correct/m-p/4698377#M246779</link>
      <description>&lt;P&gt;I have removed the NTP servers, and it still is having issues. So I connect to a AP using the console port, here is what I see. It seems the certificate has expired? But why would it expire.. Is this an easy fix?&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;[*10/04/2022 22:00:14.0484] CAPWAP State: Discovery&lt;BR /&gt;[*10/04/2022 22:00:14.0484] IP DNS query for CISCO-CAPWAP-CONTROLLER.lan&lt;BR /&gt;[*10/04/2022 22:00:14.0584] Discovery Request sent to 172.16.32.8, discovery typ e STATIC_CONFIG(1)&lt;BR /&gt;[*10/04/2022 22:00:14.0584] Discovery Request sent to 255.255.255.255, discovery type UNKNOWN(0)&lt;BR /&gt;[*10/04/2022 22:00:14.0584] Discovery Response from 172.16.32.8&lt;BR /&gt;[*10/04/2022 22:00:14.0784] Discovery Response from 172.16.32.8&lt;BR /&gt;[*10/04/2022 22:00:23.0000]&lt;BR /&gt;[*10/04/2022 22:00:23.0000] CAPWAP State: DTLS Setup&lt;BR /&gt;[*10/04/2022 22:00:23.0000] dtls_connectionDB_add_connection: Number of DTLS con nections exceeded two&lt;BR /&gt;[*10/04/2022 22:00:23.2199] Certificate is expired&lt;BR /&gt;[*10/04/2022 22:00:23.2199] Certificate Start Date: Aug 15 12:24:27 2012 GMT&lt;BR /&gt;[*10/04/2022 22:00:23.2199] Certificate End Date: Aug 15 12:34:27 2022 GMT&lt;BR /&gt;[*10/04/2022 22:00:23.2199] display_verify_cert_status: Verify Cert: FAILED at 0 depth: certificate has expired&lt;BR /&gt;[*10/04/2022 22:00:23.2199] X509 OpenSSL Errors...&lt;BR /&gt;[*10/04/2022 22:00:23.2199]&lt;BR /&gt;[*10/04/2022 22:00:23.2199] NONE&lt;BR /&gt;[*10/04/2022 22:00:23.2199]&lt;BR /&gt;[*10/04/2022 22:00:23.2199]&lt;BR /&gt;[*10/04/2022 22:00:23.2199] dtls_verify_con_cert: Controller certificate verific ation error&lt;BR /&gt;[*10/04/2022 22:00:23.2199] dtls_process_packet: Controller certificate verifica tion failed&lt;BR /&gt;[*10/04/2022 22:00:23.2199] sendPacketToDtls: DTLS: Closing connection 0x18ea000 .&lt;BR /&gt;[*10/04/2022 22:00:23.2199]&lt;BR /&gt;[*10/04/2022 22:00:23.2199] Lost connection to the controller, going to restart CAPWAP (reason : dtls_rc_connection_closed)...&lt;BR /&gt;[*10/04/2022 22:00:23.2199]&lt;BR /&gt;[*10/04/2022 22:00:23.2199] Restarting CAPWAP State Machine.&lt;BR /&gt;[*10/04/2022 22:00:23.3299] Discarding msg CAPWAP_WTP_EVENT_REQUEST(type 9) in C APWAP state: DTLS Setup(3).&lt;BR /&gt;[*10/04/2022 22:00:23.3299] Failed to disconnect DTLS-CTRL session.&lt;BR /&gt;[*10/04/2022 22:00:23.3299]&lt;BR /&gt;[*10/04/2022 22:00:23.3299] CAPWAP State: DTLS Teardown&lt;BR /&gt;[*10/04/2022 22:00:23.3499] DTLS: Error while processing DTLS packet 0x1934000.&lt;BR /&gt;[*10/04/2022 22:00:27.9285] No more AP manager addresses remain..&lt;BR /&gt;[*10/04/2022 22:00:27.9285] No valid AP manager found for controller 'Cisco_db:c c:e5' (ip: 172.16.32.8)&lt;BR /&gt;[*10/04/2022 22:00:27.9285] Failed to join controller Cisco_db:cc:e5.&lt;BR /&gt;[*10/04/2022 22:00:27.9285] Failed to join controller.&lt;/P&gt;</description>
      <pubDate>Tue, 04 Oct 2022 22:04:45 GMT</pubDate>
      <guid>https://community.cisco.com/t5/wireless/wlc-2504-aps-not-joining-time-is-correct/m-p/4698377#M246779</guid>
      <dc:creator>Elesh</dc:creator>
      <dc:date>2022-10-04T22:04:45Z</dc:date>
    </item>
    <item>
      <title>Re: wlc 2504 APs not joining time is correct</title>
      <link>https://community.cisco.com/t5/wireless/wlc-2504-aps-not-joining-time-is-correct/m-p/4698395#M246784</link>
      <description>&lt;P&gt;Did you read the field notice or my summary like I suggested?&amp;nbsp; &lt;BR /&gt;Or you just disabled NTP and hoped that would somehow magically fix everything - it will not.&amp;nbsp; You need to follow ALL the steps in the correct order to resolve the issue.&lt;/P&gt;
&lt;P&gt;&lt;SPAN&gt;&amp;gt; But why would it expire..&lt;BR /&gt;Because Cisco issued 10 year Manufacturing Installed Certificates (MIC) which expire - yes you guessed it - 10 years after manufacture.&amp;nbsp; If you'd read the field notice you'd know this already.&lt;/SPAN&gt;&lt;/P&gt;</description>
      <pubDate>Tue, 04 Oct 2022 23:44:11 GMT</pubDate>
      <guid>https://community.cisco.com/t5/wireless/wlc-2504-aps-not-joining-time-is-correct/m-p/4698395#M246784</guid>
      <dc:creator>Rich R</dc:creator>
      <dc:date>2022-10-04T23:44:11Z</dc:date>
    </item>
    <item>
      <title>Re: wlc 2504 APs not joining time is correct</title>
      <link>https://community.cisco.com/t5/wireless/wlc-2504-aps-not-joining-time-is-correct/m-p/4698399#M246785</link>
      <description>&lt;P&gt;I apologize rrudling, I sure feel like an a**.&amp;nbsp;&lt;/P&gt;&lt;P&gt;I went through the field notice briefly just now and will go into detail when I'm on site again.. Thanks.&lt;/P&gt;</description>
      <pubDate>Tue, 04 Oct 2022 23:59:39 GMT</pubDate>
      <guid>https://community.cisco.com/t5/wireless/wlc-2504-aps-not-joining-time-is-correct/m-p/4698399#M246785</guid>
      <dc:creator>Elesh</dc:creator>
      <dc:date>2022-10-04T23:59:39Z</dc:date>
    </item>
    <item>
      <title>Re: wlc 2504 APs not joining time is correct</title>
      <link>https://community.cisco.com/t5/wireless/wlc-2504-aps-not-joining-time-is-correct/m-p/4698557#M246796</link>
      <description>&lt;P&gt;LOL fair enough &lt;span class="lia-unicode-emoji" title=":slightly_smiling_face:"&gt;🙂&lt;/span&gt; glad we got there in the end!&lt;/P&gt;</description>
      <pubDate>Wed, 05 Oct 2022 08:13:18 GMT</pubDate>
      <guid>https://community.cisco.com/t5/wireless/wlc-2504-aps-not-joining-time-is-correct/m-p/4698557#M246796</guid>
      <dc:creator>Rich R</dc:creator>
      <dc:date>2022-10-05T08:13:18Z</dc:date>
    </item>
    <item>
      <title>Re: wlc 2504 APs not joining time is correct</title>
      <link>https://community.cisco.com/t5/wireless/wlc-2504-aps-not-joining-time-is-correct/m-p/4700036#M246909</link>
      <description>&lt;P&gt;Just to be clear. Do I need to reset the time to the past and&amp;nbsp;&lt;SPAN&gt;&amp;nbsp;run&amp;nbsp;&lt;/SPAN&gt;config ap cert-expiry-ignore {mic|ssc} enable on the WLC, or on each AP?&lt;/P&gt;</description>
      <pubDate>Fri, 07 Oct 2022 17:21:43 GMT</pubDate>
      <guid>https://community.cisco.com/t5/wireless/wlc-2504-aps-not-joining-time-is-correct/m-p/4700036#M246909</guid>
      <dc:creator>Elesh</dc:creator>
      <dc:date>2022-10-07T17:21:43Z</dc:date>
    </item>
    <item>
      <title>Re: wlc 2504 APs not joining time is correct</title>
      <link>https://community.cisco.com/t5/wireless/wlc-2504-aps-not-joining-time-is-correct/m-p/4700174#M246919</link>
      <description>&lt;P&gt;Resetting time to the past (temporarily) is simply to allow the APs to join as if the certs had not expired yet - so they can download new software and config from the WLC.&lt;BR /&gt;The config is done as global config on the WLC only.&amp;nbsp; The WLC will update every AP which joins with that config - but only after they have been updated to the new software which supports that config.&lt;BR /&gt;&lt;BR /&gt;&lt;/P&gt;</description>
      <pubDate>Sat, 08 Oct 2022 10:05:14 GMT</pubDate>
      <guid>https://community.cisco.com/t5/wireless/wlc-2504-aps-not-joining-time-is-correct/m-p/4700174#M246919</guid>
      <dc:creator>Rich R</dc:creator>
      <dc:date>2022-10-08T10:05:14Z</dc:date>
    </item>
  </channel>
</rss>

