<?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-3-DATA_KEEPALIVE_ERR: Failed to receive data keep-alive in Wireless</title>
    <link>https://community.cisco.com/t5/wireless/capwap-3-data-keepalive-err-failed-to-receive-data-keep-alive/m-p/5157061#M274232</link>
    <description>&lt;P&gt;That bug is caused by having a device on the local subnet with an (invalid) IP address the same as the WLC.&amp;nbsp; Obviously if you have that you should remove it!&lt;BR /&gt;In any event that bug was fixed long before 8.10 so it cannot be that particular bug.&lt;BR /&gt;Don't waste your time with TAC until you have updated to 8.10.196.0 - that's probably the first thing TAC will tell you to do anyway!&lt;BR /&gt;If you still see the problem then get a packet capture on the AP switch port so that you can see exactly what is going on.&lt;BR /&gt;Share the complete console log file from the AP from power-on showing all logs up to and including when it starts failing.&amp;nbsp; Save the logs to a text file (.txt) and attach here.&lt;BR /&gt;Also check the WLC logs for any relevant messages.&lt;BR /&gt;Check the AP join stats on the WLC showing the disjoin reason.&lt;/P&gt;
&lt;P&gt;Since all your AP models are supported on 9800-CL virtualised WLC why are you still using AireOS vWLC which is now effectively end of life?&amp;nbsp; &lt;A href="https://www.cisco.com/c/en/us/products/collateral/wireless/8500-series-wireless-controllers/wireless-software-8-10-pb.html" target="_blank"&gt;https://www.cisco.com/c/en/us/products/collateral/wireless/8500-series-wireless-controllers/wireless-software-8-10-pb.html&lt;/A&gt; I highly recommend upgrading to IOS-XE based 9800-CL which is still fully supported.&amp;nbsp; 9800 release 17.12.x is the last release to support the 1702 and 2702 APs because they are now &lt;STRONG&gt;End of Support&lt;/STRONG&gt;. (which also means that TAC could refuse to troubleshoot any issues with those APs)&lt;BR /&gt;&lt;A href="https://www.cisco.com/c/en/us/td/docs/wireless/controller/9800/17-12/release-notes/rn-17-12-9800.html#supported-aps" target="_blank"&gt;https://www.cisco.com/c/en/us/td/docs/wireless/controller/9800/17-12/release-notes/rn-17-12-9800.html#supported-aps&lt;/A&gt;&lt;/P&gt;</description>
    <pubDate>Wed, 07 Aug 2024 11:20:56 GMT</pubDate>
    <dc:creator>Rich R</dc:creator>
    <dc:date>2024-08-07T11:20:56Z</dc:date>
    <item>
      <title>CAPWAP-3-DATA_KEEPALIVE_ERR: Failed to receive data keep-alive</title>
      <link>https://community.cisco.com/t5/wireless/capwap-3-data-keepalive-err-failed-to-receive-data-keep-alive/m-p/4138343#M197434</link>
      <description>&lt;P&gt;I checked for another post regarding the use of "_" as AP Group name but that is not our case. I am getting multiple error messages likes this after migration this site from a traditional MPLS connection with guaranteed BW to SD-WAN where the remote gateway is now a FW running an IPSEC tunnel to the HQ with the capwap tunnel travelling inside. We are having&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;I got this article where it mentions something about MTU and larger packets being dropped so I was wondering if my issue has something to do with this. I am still doing my research, collecting debugs, etc.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&lt;A href="https://www.cisco.com/c/en/us/support/docs/wireless/wireless-lan-controller-software/211405-Configure-CAPWAP-Path-MTU-Discovery.html" target="_blank" rel="noopener"&gt;https://www.cisco.com/c/en/us/support/docs/wireless/wireless-lan-controller-software/211405-Configure-CAPWAP-Path-MTU-Discovery.html&lt;/A&gt;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Mon, 05 Jul 2021 19:25:28 GMT</pubDate>
      <guid>https://community.cisco.com/t5/wireless/capwap-3-data-keepalive-err-failed-to-receive-data-keep-alive/m-p/4138343#M197434</guid>
      <dc:creator>ajc</dc:creator>
      <dc:date>2021-07-05T19:25:28Z</dc:date>
    </item>
    <item>
      <title>Re: CAPWAP-3-DATA_KEEPALIVE_ERR: Failed to receive data keep-alive</title>
      <link>https://community.cisco.com/t5/wireless/capwap-3-data-keepalive-err-failed-to-receive-data-keep-alive/m-p/5156989#M274227</link>
      <description>&lt;P&gt;Hello,&lt;/P&gt;&lt;P&gt;Have you found a solution ?&lt;/P&gt;</description>
      <pubDate>Wed, 07 Aug 2024 09:24:45 GMT</pubDate>
      <guid>https://community.cisco.com/t5/wireless/capwap-3-data-keepalive-err-failed-to-receive-data-keep-alive/m-p/5156989#M274227</guid>
      <dc:creator>romain-salmon</dc:creator>
      <dc:date>2024-08-07T09:24:45Z</dc:date>
    </item>
    <item>
      <title>Re: CAPWAP-3-DATA_KEEPALIVE_ERR: Failed to receive data keep-alive</title>
      <link>https://community.cisco.com/t5/wireless/capwap-3-data-keepalive-err-failed-to-receive-data-keep-alive/m-p/5157023#M274228</link>
      <description>&lt;P&gt;&lt;a href="https://community.cisco.com/t5/user/viewprofilepage/user-id/1764647"&gt;@romain-salmon&lt;/a&gt;&amp;nbsp;probably better to open a new thread.&amp;nbsp; But either way:&lt;BR /&gt;- What model of WLC and APs are you using?&lt;BR /&gt;- What version of software are you using?&lt;BR /&gt;- What exactly is the problem you are experiencing?&lt;/P&gt;
&lt;P&gt;Generically speaking:&lt;BR /&gt;- make sure your software is up to date as per TAC recommended link below.&amp;nbsp; WLC 2504, 5508 or 8510 should be running 8.5.182.12.&amp;nbsp; WLC 3504, 5520, 8540 should be running 8.10.196.0&lt;BR /&gt;- Check your WLC config using Config Analyzer (link below)&lt;BR /&gt;- Refer to&amp;nbsp;&lt;A href="https://bst.cisco.com/bugsearch/bug/CSCvm76689" target="_blank"&gt;https://bst.cisco.com/bugsearch/bug/CSCvm76689&lt;/A&gt;&amp;nbsp;and&amp;nbsp;&lt;A href="https://bst.cisco.com/bugsearch/bug/CSCvt16235" target="_blank"&gt;https://bst.cisco.com/bugsearch/bug/CSCvt16235&lt;/A&gt;&amp;nbsp;regarding AP path MTU settings.&lt;/P&gt;</description>
      <pubDate>Wed, 07 Aug 2024 10:04:55 GMT</pubDate>
      <guid>https://community.cisco.com/t5/wireless/capwap-3-data-keepalive-err-failed-to-receive-data-keep-alive/m-p/5157023#M274228</guid>
      <dc:creator>Rich R</dc:creator>
      <dc:date>2024-08-07T10:04:55Z</dc:date>
    </item>
    <item>
      <title>Re: CAPWAP-3-DATA_KEEPALIVE_ERR: Failed to receive data keep-alive</title>
      <link>https://community.cisco.com/t5/wireless/capwap-3-data-keepalive-err-failed-to-receive-data-keep-alive/m-p/5157024#M274229</link>
      <description>&lt;P&gt;Hello thanks for your fast reply.&lt;/P&gt;&lt;P&gt;&lt;SPAN&gt;- What model of WLC and APs are you using?vWLC: 8.10.185.0. AP :&amp;nbsp; AIR-CAP1702I-E-K9,AIR-CAP2702E-E-K9,AIR-AP1832I-E-K9,&amp;nbsp;AIR-AP2802E-E-K9. But i dunno if i have the problem for all the AP.&lt;/SPAN&gt;&lt;BR /&gt;&lt;SPAN&gt;- What exactly is the problem you are experiencing?&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN&gt;I have exactly this problem : some joined the WLC then disconnect after 1min. I ll open a TAC case soon&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN&gt;&amp;nbsp;&lt;A href="https://bst.cloudapps.cisco.com/bugsearch/bug/CSCvc42741" target="_blank"&gt;https://bst.cloudapps.cisco.com/bugsearch/bug/CSCvc42741&lt;/A&gt;&lt;/SPAN&gt;&lt;/P&gt;</description>
      <pubDate>Wed, 07 Aug 2024 10:10:32 GMT</pubDate>
      <guid>https://community.cisco.com/t5/wireless/capwap-3-data-keepalive-err-failed-to-receive-data-keep-alive/m-p/5157024#M274229</guid>
      <dc:creator>romain-salmon</dc:creator>
      <dc:date>2024-08-07T10:10:32Z</dc:date>
    </item>
    <item>
      <title>Re: CAPWAP-3-DATA_KEEPALIVE_ERR: Failed to receive data keep-alive</title>
      <link>https://community.cisco.com/t5/wireless/capwap-3-data-keepalive-err-failed-to-receive-data-keep-alive/m-p/5157061#M274232</link>
      <description>&lt;P&gt;That bug is caused by having a device on the local subnet with an (invalid) IP address the same as the WLC.&amp;nbsp; Obviously if you have that you should remove it!&lt;BR /&gt;In any event that bug was fixed long before 8.10 so it cannot be that particular bug.&lt;BR /&gt;Don't waste your time with TAC until you have updated to 8.10.196.0 - that's probably the first thing TAC will tell you to do anyway!&lt;BR /&gt;If you still see the problem then get a packet capture on the AP switch port so that you can see exactly what is going on.&lt;BR /&gt;Share the complete console log file from the AP from power-on showing all logs up to and including when it starts failing.&amp;nbsp; Save the logs to a text file (.txt) and attach here.&lt;BR /&gt;Also check the WLC logs for any relevant messages.&lt;BR /&gt;Check the AP join stats on the WLC showing the disjoin reason.&lt;/P&gt;
&lt;P&gt;Since all your AP models are supported on 9800-CL virtualised WLC why are you still using AireOS vWLC which is now effectively end of life?&amp;nbsp; &lt;A href="https://www.cisco.com/c/en/us/products/collateral/wireless/8500-series-wireless-controllers/wireless-software-8-10-pb.html" target="_blank"&gt;https://www.cisco.com/c/en/us/products/collateral/wireless/8500-series-wireless-controllers/wireless-software-8-10-pb.html&lt;/A&gt; I highly recommend upgrading to IOS-XE based 9800-CL which is still fully supported.&amp;nbsp; 9800 release 17.12.x is the last release to support the 1702 and 2702 APs because they are now &lt;STRONG&gt;End of Support&lt;/STRONG&gt;. (which also means that TAC could refuse to troubleshoot any issues with those APs)&lt;BR /&gt;&lt;A href="https://www.cisco.com/c/en/us/td/docs/wireless/controller/9800/17-12/release-notes/rn-17-12-9800.html#supported-aps" target="_blank"&gt;https://www.cisco.com/c/en/us/td/docs/wireless/controller/9800/17-12/release-notes/rn-17-12-9800.html#supported-aps&lt;/A&gt;&lt;/P&gt;</description>
      <pubDate>Wed, 07 Aug 2024 11:20:56 GMT</pubDate>
      <guid>https://community.cisco.com/t5/wireless/capwap-3-data-keepalive-err-failed-to-receive-data-keep-alive/m-p/5157061#M274232</guid>
      <dc:creator>Rich R</dc:creator>
      <dc:date>2024-08-07T11:20:56Z</dc:date>
    </item>
  </channel>
</rss>

