<?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: CAPWAP DTLS session closed for AP, cause: DTLS server session shut in Wireless</title>
    <link>https://community.cisco.com/t5/wireless/capwap-dtls-session-closed-for-ap-cause-dtls-server-session/m-p/5356077#M287978</link>
    <description>&lt;P&gt;We investigated and found the cause of this problem. Initially, when we brought up the controller on the virtual machine, no NTP server was added, so the PKI certificate was created without an NTP server.&lt;/P&gt;&lt;P&gt;First of all, the NTP settings must be configured correctly. After that, the PKI certificate needs to be regenerated in order to resolve the problem.&lt;/P&gt;&lt;P&gt;Thank you for your attention.&lt;/P&gt;</description>
    <pubDate>Thu, 18 Dec 2025 07:21:28 GMT</pubDate>
    <dc:creator>subhan-zeynaloff98</dc:creator>
    <dc:date>2025-12-18T07:21:28Z</dc:date>
    <item>
      <title>CAPWAP DTLS session closed for AP, cause: DTLS server session shutdown</title>
      <link>https://community.cisco.com/t5/wireless/capwap-dtls-session-closed-for-ap-cause-dtls-server-session/m-p/4650342#M244163</link>
      <description>&lt;P&gt;&lt;span class="lia-inline-image-display-wrapper lia-image-align-inline" image-alt="이미지 006.png" style="width: 999px;"&gt;&lt;img src="https://community.cisco.com/t5/image/serverpage/image-id/156981iAEABE0C3FDF06D6A/image-size/large?v=v2&amp;amp;px=999" role="button" title="이미지 006.png" alt="이미지 006.png" /&gt;&lt;/span&gt;&lt;span class="lia-inline-image-display-wrapper lia-image-align-inline" image-alt="이미지 008.png" style="width: 999px;"&gt;&lt;img src="https://community.cisco.com/t5/image/serverpage/image-id/156982iC22CCDF779B41F65/image-size/large?v=v2&amp;amp;px=999" role="button" title="이미지 008.png" alt="이미지 008.png" /&gt;&lt;/span&gt;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Several APs are being disconnected.&lt;/P&gt;
&lt;P&gt;CAPWAP DTLS session closed for AP, cause: DTLS server session shutdown&lt;/P&gt;
&lt;P&gt;Does anyone know the cause?&lt;/P&gt;</description>
      <pubDate>Thu, 14 Jul 2022 14:30:55 GMT</pubDate>
      <guid>https://community.cisco.com/t5/wireless/capwap-dtls-session-closed-for-ap-cause-dtls-server-session/m-p/4650342#M244163</guid>
      <dc:creator>JustTakeTheFirstStep</dc:creator>
      <dc:date>2022-07-14T14:30:55Z</dc:date>
    </item>
    <item>
      <title>Re: CAPWAP DTLS session closed for AP, cause: DTLS server session shut</title>
      <link>https://community.cisco.com/t5/wireless/capwap-dtls-session-closed-for-ap-cause-dtls-server-session/m-p/4650436#M244170</link>
      <description>&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; - FYI :&amp;nbsp;&lt;A href="https://bst.cloudapps.cisco.com/bugsearch/bug/CSCwa35350" target="_blank"&gt;https://bst.cloudapps.cisco.com/bugsearch/bug/CSCwa35350&lt;/A&gt;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;M.&lt;/P&gt;</description>
      <pubDate>Thu, 14 Jul 2022 16:04:14 GMT</pubDate>
      <guid>https://community.cisco.com/t5/wireless/capwap-dtls-session-closed-for-ap-cause-dtls-server-session/m-p/4650436#M244170</guid>
      <dc:creator>Mark Elsen</dc:creator>
      <dc:date>2022-07-14T16:04:14Z</dc:date>
    </item>
    <item>
      <title>Re: CAPWAP DTLS session closed for AP, cause: DTLS server session shut</title>
      <link>https://community.cisco.com/t5/wireless/capwap-dtls-session-closed-for-ap-cause-dtls-server-session/m-p/4651219#M244198</link>
      <description>&lt;P&gt;Many possible reasons including the bug&amp;nbsp;&lt;a href="https://community.cisco.com/t5/user/viewprofilepage/user-id/291804"&gt;@Mark Elsen&lt;/a&gt;&amp;nbsp;suggested.&lt;BR /&gt;&lt;SPAN&gt;You're running 17.5.1 which was a limited support release.&lt;BR /&gt;&lt;/SPAN&gt;&lt;SPAN&gt;&lt;A href="https://www.cisco.com/c/en/us/products/collateral/ios-nx-os-software/ios-xe-17/ios-xe-17-5-x-eol.html" target="_blank"&gt;https://www.cisco.com/c/en/us/products/collateral/ios-nx-os-software/ios-xe-17/ios-xe-17-5-x-eol.html&lt;/A&gt;&lt;/SPAN&gt;&lt;SPAN&gt;&lt;BR /&gt;&lt;/SPAN&gt;&lt;/P&gt;
&lt;P&gt;&lt;SPAN&gt;You should move to an extended support release which has the fix for that bug (and many others).&amp;nbsp; Suggest you upgrade to 17.6.3.&lt;/SPAN&gt;&lt;/P&gt;
&lt;P&gt;&lt;SPAN&gt;Refer to&amp;nbsp;&lt;A href="https://www.cisco.com/c/en/us/support/docs/wireless/catalyst-9800-series-wireless-controllers/214749-tac-recommended-ios-xe-builds-for-wirele.html#anc7" target="_blank"&gt;https://www.cisco.com/c/en/us/support/docs/wireless/catalyst-9800-series-wireless-controllers/214749-tac-recommended-ios-xe-builds-for-wirele.html#anc7&lt;/A&gt;&lt;BR /&gt;Note "&lt;FONT size="2"&gt;&lt;STRONG&gt;&lt;FONT color="#339966"&gt;Cisco recommends&amp;nbsp;&lt;/FONT&gt;&lt;/STRONG&gt;&lt;/FONT&gt;&lt;STRONG&gt;&lt;FONT color="#339966"&gt;17.6.3 CCO image&amp;nbsp;for all deployments without IOS APs.&lt;/FONT&gt;&lt;/STRONG&gt;"&lt;/SPAN&gt;&lt;/P&gt;</description>
      <pubDate>Fri, 15 Jul 2022 14:22:52 GMT</pubDate>
      <guid>https://community.cisco.com/t5/wireless/capwap-dtls-session-closed-for-ap-cause-dtls-server-session/m-p/4651219#M244198</guid>
      <dc:creator>Rich R</dc:creator>
      <dc:date>2022-07-15T14:22:52Z</dc:date>
    </item>
    <item>
      <title>Re: CAPWAP DTLS session closed for AP, cause: DTLS server session shut</title>
      <link>https://community.cisco.com/t5/wireless/capwap-dtls-session-closed-for-ap-cause-dtls-server-session/m-p/4673431#M245298</link>
      <description>&lt;P&gt;Glad to see it's not just my deployment.&amp;nbsp; I have a similar issue as that shown by Snika:&lt;/P&gt;&lt;P&gt;Random AP's dropping sporadically with AP DISJOIN / JOIN messages.&lt;/P&gt;&lt;P&gt;usually accompanied with log string: "CAPWAP DTLS session closed for AP, cause: DTLS server session shutdown"&lt;/P&gt;&lt;P&gt;Happens between 20 and 50 times daily, across my 300 AP's.&lt;/P&gt;&lt;P&gt;Installation:&amp;nbsp; &amp;nbsp;9800-L-F in High-Availability pair, running 17.3.5b, due to need to support Wave-1 AP's&amp;nbsp; (2700/3700).&lt;/P&gt;&lt;P&gt;Interesting item:&amp;nbsp; All DISJOIN messages in the 9800 logs are associated with "Chassis 2", and all JOIN messages are associated with "Chassis 1".&amp;nbsp; This is curious because the Active controller in the SSO Redundancy setup is Chassis 1.&amp;nbsp; Chassis 2 is a hot-standby mirror of Chassis 1.&amp;nbsp; Examples:&lt;/P&gt;&lt;P&gt;Aug 22 13:27:57 UTC: %CAPWAPAC_SMGR_TRACE_MESSAGE-5-AP_JOIN_DISJOIN: Chassis 1 R0/0: wncd: AP Event: AP Name: fll2ap205, MAC: bc26.c7a2.bdee Joined&lt;BR /&gt;Aug 22 13:30:33 UTC: %CAPWAPAC_SMGR_TRACE_MESSAGE-5-AP_JOIN_DISJOIN: Chassis 1 R0/0: wncd: AP Event: Session-IP: 10.6.132.71[5256] Mac: 780c.f04e.b180 CAPWAP DTLS session closed for AP, cause: DTLS server session shutdown&lt;BR /&gt;Aug 22 13:30:33 UTC: %CAPWAPAC_SMGR_TRACE_MESSAGE-5-AP_JOIN_DISJOIN: Chassis 2 R0/0: wncd: AP Event: AP Name: fll2ap106, MAC: 700f.6a26.337a Disjoined&lt;BR /&gt;Aug 22 13:31:02 UTC: %CAPWAPAC_SMGR_TRACE_MESSAGE-5-AP_JOIN_DISJOIN: Chassis 1 R0/0: wncd: AP Event: AP Name: fll2ap106, MAC: 700f.6a26.337a Joined&lt;BR /&gt;Aug 22 13:31:41 UTC: %CAPWAPAC_SMGR_TRACE_MESSAGE-5-AP_JOIN_DISJOIN: Chassis 2 R0/0: wncd: AP Event: AP Name: fll2ap107, MAC: 7872.5d2c.eaee Disjoined&lt;BR /&gt;Aug 22 13:31:41 UTC: %CAPWAPAC_SMGR_TRACE_MESSAGE-5-AP_JOIN_DISJOIN: Chassis 1 R0/0: wncd: AP Event: Session-IP: 10.6.132.73[5256] Mac: 7872.5d9f.0080 CAPWAP DTLS session closed for AP, cause: DTLS server session shutdown&lt;BR /&gt;Aug 22 13:31:53 UTC: %CAPWAPAC_SMGR_TRACE_MESSAGE-5-AP_JOIN_DISJOIN: Chassis 2 R0/0: wncd: AP Event: AP Name: fll2ap213, MAC: f4db.e61a.7df2 Disjoined&lt;BR /&gt;Aug 22 13:31:53 UTC: %CAPWAPAC_SMGR_TRACE_MESSAGE-5-AP_JOIN_DISJOIN: Chassis 1 R0/0: wncd: AP Event: Session-IP: 10.6.132.183[5272] Mac: f4db.e61d.f020 CAPWAP DTLS session closed for AP, cause: DTLS server session shutdown&lt;BR /&gt;Aug 22 13:32:11 UTC: %CAPWAPAC_SMGR_TRACE_MESSAGE-5-AP_JOIN_DISJOIN: Chassis 1 R0/0: wncd: AP Event: AP Name: fll2ap107, MAC: 7872.5d2c.eaee Joined&lt;BR /&gt;Aug 22 13:32:24 UTC: %CAPWAPAC_SMGR_TRACE_MESSAGE-5-AP_JOIN_DISJOIN: Chassis 1 R0/0: wncd: AP Event: AP Name: fll2ap213, MAC: f4db.e61a.7df2 Joined&lt;BR /&gt;Aug 22 13:35:17 UTC: %CAPWAPAC_SMGR_TRACE_MESSAGE-5-AP_JOIN_DISJOIN: Chassis 2 R0/0: wncd: AP Event: AP Name: fll2ap208, MAC: 502f.a8ec.aa86 Disjoined&lt;BR /&gt;Aug 22 13:35:17 UTC: %CAPWAPAC_SMGR_TRACE_MESSAGE-5-AP_JOIN_DISJOIN: Chassis 1 R0/0: wncd: AP Event: Session-IP: 10.6.132.188[5248] Mac: 00ea.bd69.bc40 CAPWAP DTLS session closed for AP, cause: DTLS server session shutdown&lt;BR /&gt;Aug 22 13:35:48 UTC: %CAPWAPAC_SMGR_TRACE_MESSAGE-5-AP_JOIN_DISJOIN: Chassis 1 R0/0: wncd: AP Event: AP Name: fll2ap208, MAC: 502f.a8ec.aa86 Joined&lt;BR /&gt;Aug 22 14:11:11 UTC: %CAPWAPAC_SMGR_TRACE_MESSAGE-5-AP_JOIN_DISJOIN: Chassis 1 R0/0: wncd: AP Event: Session-IP: 10.15.178.78[5248] Mac: bc26.c7ba.5ce0 CAPWAP DTLS session closed for AP, cause: DTLS server session shutdown&lt;BR /&gt;Aug 22 14:11:11 UTC: %CAPWAPAC_SMGR_TRACE_MESSAGE-5-AP_JOIN_DISJOIN: Chassis 2 R0/0: wncd: AP Event: AP Name: fll3ap612, MAC: 502f.a8ec.6f90 Disjoined&lt;BR /&gt;Aug 22 14:11:42 UTC: %CAPWAPAC_SMGR_TRACE_MESSAGE-5-AP_JOIN_DISJOIN: Chassis 1 R0/0: wncd: AP Event: AP Name: fll3ap612, MAC: 502f.a8ec.6f90 Joined&lt;BR /&gt;Aug 22 14:13:05 UTC: %CAPWAPAC_SMGR_TRACE_MESSAGE-5-AP_JOIN_DISJOIN: Chassis 2 R0/0: wncd: AP Event: AP Name: fll3ap812, MAC: 7872.5d2c.eaf0 Disjoined&lt;BR /&gt;Aug 22 14:13:05 UTC: %CAPWAPAC_SMGR_TRACE_MESSAGE-5-AP_JOIN_DISJOIN: Chassis 1 R0/0: wncd: AP Event: Session-IP: 10.15.178.99[5248] Mac: 7872.5d9f.00a0 CAPWAP DTLS session closed for AP, cause: DTLS server session shutdown&lt;BR /&gt;Aug 22 14:13:11 UTC: %CAPWAPAC_SMGR_TRACE_MESSAGE-5-AP_JOIN_DISJOIN: Chassis 2 R0/0: wncd: AP Event: AP Name: fll3ap204, MAC: f4db.e61a.7d98 Disjoined&lt;BR /&gt;Aug 22 14:13:11 UTC: %CAPWAPAC_SMGR_TRACE_MESSAGE-5-AP_JOIN_DISJOIN: Chassis 1 R0/0: wncd: AP Event: Session-IP: 10.15.178.49[5264] Mac: f4db.e61d.ea80 CAPWAP DTLS session closed for AP, cause: DTLS server session shutdown&lt;BR /&gt;Aug 22 14:13:17 UTC: %CAPWAPAC_SMGR_TRACE_MESSAGE-5-AP_JOIN_DISJOIN: Chassis 2 R0/0: wncd: AP Event: AP Name: fll3ap601, MAC: 700f.6a26.3114 Disjoined&lt;BR /&gt;Aug 22 14:13:17 UTC: %CAPWAPAC_SMGR_TRACE_MESSAGE-5-AP_JOIN_DISJOIN: Chassis 1 R0/0: wncd: AP Event: Session-IP: 10.15.178.175[5256] Mac: 780c.f04e.8b20 CAPWAP DTLS session closed for AP, cause: DTLS server session shutdown&lt;BR /&gt;Aug 22 14:13:35 UTC: %CAPWAPAC_SMGR_TRACE_MESSAGE-5-AP_JOIN_DISJOIN: Chassis 1 R0/0: wncd: AP Event: AP Name: fll3ap812, MAC: 7872.5d2c.eaf0 Joined&lt;BR /&gt;Aug 22 14:13:47 UTC: %CAPWAPAC_SMGR_TRACE_MESSAGE-5-AP_JOIN_DISJOIN: Chassis 1 R0/0: wncd: AP Event: AP Name: fll3ap601, MAC: 700f.6a26.3114 Joined&lt;BR /&gt;Aug 22 14:14:46 UTC: %CAPWAPAC_SMGR_TRACE_MESSAGE-5-AP_JOIN_DISJOIN: Chassis 2 R0/0: wncd: AP Event: AP Name: fll3ap104, MAC: 7872.5d2c.eaca Disjoined&lt;BR /&gt;Aug 22 14:14:46 UTC: %CAPWAPAC_SMGR_TRACE_MESSAGE-5-AP_JOIN_DISJOIN: Chassis 1 R0/0: wncd: AP Event: Session-IP: 10.15.178.155[5248] Mac: 7872.5d9e.fe40 CAPWAP DTLS session closed for AP, cause: DTLS server session shutdown&lt;BR /&gt;Aug 22 14:14:57 UTC: %CAPWAPAC_SMGR_TRACE_MESSAGE-5-AP_JOIN_DISJOIN: Chassis 2 R0/0: wncd: AP Event: AP Name: fll3ap702, MAC: a093.514b.07f8 Disjoined&lt;BR /&gt;Aug 22 14:14:57 UTC: %CAPWAPAC_SMGR_TRACE_MESSAGE-5-AP_JOIN_DISJOIN: Chassis 1 R0/0: wncd: AP Event: Session-IP: 10.15.178.83[5264] Mac: 502f.a84d.4d00 CAPWAP DTLS session closed for AP, cause: DTLS server session shutdown&lt;BR /&gt;Aug 22 14:15:16 UTC: %CAPWAPAC_SMGR_TRACE_MESSAGE-5-AP_JOIN_DISJOIN: Chassis 1 R0/0: wncd: AP Event: AP Name: fll3ap104, MAC: 7872.5d2c.eaca Joined&lt;BR /&gt;Aug 22 14:15:27 UTC: %CAPWAPAC_SMGR_TRACE_MESSAGE-5-AP_JOIN_DISJOIN: Chassis 1 R0/0: wncd: AP Event: AP Name: fll3ap702, MAC: a093.514b.07f8 Joined&lt;BR /&gt;Aug 22 14:15:52 UTC: %CAPWAPAC_SMGR_TRACE_MESSAGE-5-AP_JOIN_DISJOIN: Chassis 2 R0/0: wncd: AP Event: AP Name: fll3ap711, MAC: a093.514b.0860 Disjoined&lt;BR /&gt;Aug 22 14:15:52 UTC: %CAPWAPAC_SMGR_TRACE_MESSAGE-5-AP_JOIN_DISJOIN: Chassis 1 R0/0: wncd: AP Event: Session-IP: 10.15.178.87[5248] Mac: 502f.a84d.5380 CAPWAP DTLS session closed for AP, cause: DTLS server session shutdown&lt;BR /&gt;Aug 22 14:16:13 UTC: %CAPWAPAC_SMGR_TRACE_MESSAGE-5-AP_JOIN_DISJOIN: Chassis 1 R0/0: wncd: AP Event: Session-IP: 10.15.178.85[5248] Mac: 7872.5d48.e980 CAPWAP DTLS session closed for AP, cause: DTLS server session shutdown&lt;BR /&gt;Aug 22 14:16:13 UTC: %CAPWAPAC_SMGR_TRACE_MESSAGE-5-AP_JOIN_DISJOIN: Chassis 2 R0/0: wncd: AP Event: AP Name: fll3ap717, MAC: 7872.5d46.6c0e Disjoined&lt;BR /&gt;Aug 22 14:16:22 UTC: %CAPWAPAC_SMGR_TRACE_MESSAGE-5-AP_JOIN_DISJOIN: Chassis 1 R0/0: wncd: AP Event: AP Name: fll3ap711, MAC: a093.514b.0860 Joined&lt;BR /&gt;Aug 22 14:16:43 UTC: %CAPWAPAC_SMGR_TRACE_MESSAGE-5-AP_JOIN_DISJOIN: Chassis 1 R0/0: wncd: AP Event: AP Name: fll3ap717, MAC: 7872.5d46.6c0e Joined&lt;BR /&gt;Aug 22 14:17:06 UTC: %CAPWAPAC_SMGR_TRACE_MESSAGE-5-AP_JOIN_DISJOIN: Chassis 2 R0/0: wncd: AP Event: AP Name: fll3ap202, MAC: f4db.e61a.76b2 Disjoined&lt;/P&gt;</description>
      <pubDate>Mon, 22 Aug 2022 15:31:50 GMT</pubDate>
      <guid>https://community.cisco.com/t5/wireless/capwap-dtls-session-closed-for-ap-cause-dtls-server-session/m-p/4673431#M245298</guid>
      <dc:creator>russell.splain</dc:creator>
      <dc:date>2022-08-22T15:31:50Z</dc:date>
    </item>
    <item>
      <title>Re: CAPWAP DTLS session closed for AP, cause: DTLS server session shut</title>
      <link>https://community.cisco.com/t5/wireless/capwap-dtls-session-closed-for-ap-cause-dtls-server-session/m-p/4746090#M249868</link>
      <description>&lt;P&gt;Hello, have you found a solution to this issue? We have the same issue when using 17.6.4 and the C9800-CL. A few AP are&amp;nbsp; disconnecting from the controller and&amp;nbsp;switching from capwap to ewc-ap.&lt;/P&gt;</description>
      <pubDate>Wed, 28 Dec 2022 13:21:11 GMT</pubDate>
      <guid>https://community.cisco.com/t5/wireless/capwap-dtls-session-closed-for-ap-cause-dtls-server-session/m-p/4746090#M249868</guid>
      <dc:creator>Filip Spisak</dc:creator>
      <dc:date>2022-12-28T13:21:11Z</dc:date>
    </item>
    <item>
      <title>Re: CAPWAP DTLS session closed for AP, cause: DTLS server session shut</title>
      <link>https://community.cisco.com/t5/wireless/capwap-dtls-session-closed-for-ap-cause-dtls-server-session/m-p/4746203#M249879</link>
      <description>&lt;P&gt;&lt;a href="https://community.cisco.com/t5/user/viewprofilepage/user-id/1447720"&gt;@Filip Spisak&lt;/a&gt;&amp;nbsp;you should open a new thread since you have a different model controller and design. Then describe your whole setup. The only thing I can tell you is to delete the EWC image so that AP’s don’t convert. &amp;nbsp;Then you still have to troubleshoot why the AP’s loose connection to the 9800-CL, that I think would be your main issue.&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Wed, 28 Dec 2022 17:02:18 GMT</pubDate>
      <guid>https://community.cisco.com/t5/wireless/capwap-dtls-session-closed-for-ap-cause-dtls-server-session/m-p/4746203#M249879</guid>
      <dc:creator>Scott Fella</dc:creator>
      <dc:date>2022-12-28T17:02:18Z</dc:date>
    </item>
    <item>
      <title>Re: CAPWAP DTLS session closed for AP, cause: DTLS server session shut</title>
      <link>https://community.cisco.com/t5/wireless/capwap-dtls-session-closed-for-ap-cause-dtls-server-session/m-p/4778907#M251941</link>
      <description>&lt;P&gt;Hello, what was the solution to your problem?&lt;/P&gt;
&lt;P&gt;Right now I'm going to update to version 17.6.4 I hope this solves this problem&lt;/P&gt;</description>
      <pubDate>Tue, 21 Feb 2023 03:36:13 GMT</pubDate>
      <guid>https://community.cisco.com/t5/wireless/capwap-dtls-session-closed-for-ap-cause-dtls-server-session/m-p/4778907#M251941</guid>
      <dc:creator>stobar1101</dc:creator>
      <dc:date>2023-02-21T03:36:13Z</dc:date>
    </item>
    <item>
      <title>Re: CAPWAP DTLS session closed for AP, cause: DTLS server session shut</title>
      <link>https://community.cisco.com/t5/wireless/capwap-dtls-session-closed-for-ap-cause-dtls-server-session/m-p/4779851#M251983</link>
      <description>In our case, it turned out that NAC policies applied to AP switch ports&lt;BR /&gt;interfered with AP CAPWAP messages. Changing NAC switch port policy solved&lt;BR /&gt;the problem. 17.6.4 has been running fine ever since.&lt;BR /&gt;</description>
      <pubDate>Tue, 21 Feb 2023 19:30:29 GMT</pubDate>
      <guid>https://community.cisco.com/t5/wireless/capwap-dtls-session-closed-for-ap-cause-dtls-server-session/m-p/4779851#M251983</guid>
      <dc:creator>russell.splain</dc:creator>
      <dc:date>2023-02-21T19:30:29Z</dc:date>
    </item>
    <item>
      <title>Re: CAPWAP DTLS session closed for AP, cause: DTLS server session shut</title>
      <link>https://community.cisco.com/t5/wireless/capwap-dtls-session-closed-for-ap-cause-dtls-server-session/m-p/5055497#M269694</link>
      <description>&lt;P&gt;Hello &lt;a href="https://community.cisco.com/t5/user/viewprofilepage/user-id/97989"&gt;@russell.splain&lt;/a&gt;&lt;/P&gt;
&lt;P&gt;I am facing the same issue, could you please provide more details about the solution? Sorry I didn't understand well what you meant !&lt;/P&gt;
&lt;P&gt;Many thanks,&lt;/P&gt;
&lt;P&gt;Hamid&lt;/P&gt;</description>
      <pubDate>Wed, 03 Apr 2024 09:40:55 GMT</pubDate>
      <guid>https://community.cisco.com/t5/wireless/capwap-dtls-session-closed-for-ap-cause-dtls-server-session/m-p/5055497#M269694</guid>
      <dc:creator>hara12386</dc:creator>
      <dc:date>2024-04-03T09:40:55Z</dc:date>
    </item>
    <item>
      <title>Re: CAPWAP DTLS session closed for AP, cause: DTLS server session shut</title>
      <link>https://community.cisco.com/t5/wireless/capwap-dtls-session-closed-for-ap-cause-dtls-server-session/m-p/5356077#M287978</link>
      <description>&lt;P&gt;We investigated and found the cause of this problem. Initially, when we brought up the controller on the virtual machine, no NTP server was added, so the PKI certificate was created without an NTP server.&lt;/P&gt;&lt;P&gt;First of all, the NTP settings must be configured correctly. After that, the PKI certificate needs to be regenerated in order to resolve the problem.&lt;/P&gt;&lt;P&gt;Thank you for your attention.&lt;/P&gt;</description>
      <pubDate>Thu, 18 Dec 2025 07:21:28 GMT</pubDate>
      <guid>https://community.cisco.com/t5/wireless/capwap-dtls-session-closed-for-ap-cause-dtls-server-session/m-p/5356077#M287978</guid>
      <dc:creator>subhan-zeynaloff98</dc:creator>
      <dc:date>2025-12-18T07:21:28Z</dc:date>
    </item>
  </channel>
</rss>

