<?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: Control and Data path down in Wireless</title>
    <link>https://community.cisco.com/t5/wireless/control-and-data-path-down/m-p/4506652#M235804</link>
    <description>&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;- Check&lt;STRONG&gt; logs&lt;/STRONG&gt; on both controllers for more info's if any. You could for instance d&lt;SPAN&gt;elete the mobility group from both WLC's and add it back on , can sometimes help &lt;EM&gt;in environments where also firewalls are in place.&lt;/EM&gt;&lt;/SPAN&gt;&lt;/P&gt;
&lt;P&gt;&lt;SPAN&gt;&amp;nbsp;M.&lt;/SPAN&gt;&lt;/P&gt;</description>
    <pubDate>Mon, 22 Nov 2021 15:56:42 GMT</pubDate>
    <dc:creator>Mark Elsen</dc:creator>
    <dc:date>2021-11-22T15:56:42Z</dc:date>
    <item>
      <title>Control and Data path down</title>
      <link>https://community.cisco.com/t5/wireless/control-and-data-path-down/m-p/4506593#M235802</link>
      <description>&lt;P&gt;Hi,&lt;/P&gt;&lt;P&gt;I have 5508 WLC in DMZ as ANCHOR and 8540 model as internal WLC, the Guest WLAN was working fine and the mobility anchor was up, suddenly I found the mobility status as (Control and Data Path Down) and Guest Wlan stop working.&lt;/P&gt;&lt;P&gt;please your guidance.&lt;/P&gt;&lt;P&gt;thanks,&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Mon, 22 Nov 2021 14:39:58 GMT</pubDate>
      <guid>https://community.cisco.com/t5/wireless/control-and-data-path-down/m-p/4506593#M235802</guid>
      <dc:creator>mahjouboi11</dc:creator>
      <dc:date>2021-11-22T14:39:58Z</dc:date>
    </item>
    <item>
      <title>Re: Control and Data path down</title>
      <link>https://community.cisco.com/t5/wireless/control-and-data-path-down/m-p/4506652#M235804</link>
      <description>&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;- Check&lt;STRONG&gt; logs&lt;/STRONG&gt; on both controllers for more info's if any. You could for instance d&lt;SPAN&gt;elete the mobility group from both WLC's and add it back on , can sometimes help &lt;EM&gt;in environments where also firewalls are in place.&lt;/EM&gt;&lt;/SPAN&gt;&lt;/P&gt;
&lt;P&gt;&lt;SPAN&gt;&amp;nbsp;M.&lt;/SPAN&gt;&lt;/P&gt;</description>
      <pubDate>Mon, 22 Nov 2021 15:56:42 GMT</pubDate>
      <guid>https://community.cisco.com/t5/wireless/control-and-data-path-down/m-p/4506652#M235804</guid>
      <dc:creator>Mark Elsen</dc:creator>
      <dc:date>2021-11-22T15:56:42Z</dc:date>
    </item>
    <item>
      <title>Re: Control and Data path down</title>
      <link>https://community.cisco.com/t5/wireless/control-and-data-path-down/m-p/4506776#M235809</link>
      <description>&lt;P&gt;Did this happen after any recent changes? You can do a mping and eping verify foreign to anchor WLC reachability.&lt;/P&gt;&lt;P&gt;More info on below blog by Rasika&lt;/P&gt;&lt;P&gt;&lt;A href="https://mrncciew.com/2013/03/24/mobility-ping-tests/" target="_blank" rel="noopener"&gt;https://mrncciew.com/2013/03/24/mobility-ping-tests/&lt;/A&gt;&lt;/P&gt;&lt;P&gt;If communication between anchor and foreign is firewalled, ports 16666 (16667 for secure mobility) and IP protocol 97 must be allowed bidirectionally between the WLC management interfaces of both.&lt;/P&gt;</description>
      <pubDate>Mon, 22 Nov 2021 20:01:55 GMT</pubDate>
      <guid>https://community.cisco.com/t5/wireless/control-and-data-path-down/m-p/4506776#M235809</guid>
      <dc:creator>Arshad Safrulla</dc:creator>
      <dc:date>2021-11-22T20:01:55Z</dc:date>
    </item>
    <item>
      <title>Re: Control and Data path down</title>
      <link>https://community.cisco.com/t5/wireless/control-and-data-path-down/m-p/4506817#M235812</link>
      <description>&lt;P&gt;Check connectivity between foreign and anchor WLCs, confirm firewalls rules/ ACLs haven't been added. Can always try readding the mobility config and see if that fixes it.&lt;/P&gt;</description>
      <pubDate>Mon, 22 Nov 2021 21:36:07 GMT</pubDate>
      <guid>https://community.cisco.com/t5/wireless/control-and-data-path-down/m-p/4506817#M235812</guid>
      <dc:creator>Haydn Andrews</dc:creator>
      <dc:date>2021-11-22T21:36:07Z</dc:date>
    </item>
  </channel>
</rss>

