<?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 path on mobility member is down in Wireless</title>
    <link>https://community.cisco.com/t5/wireless/control-path-on-mobility-member-is-down/m-p/1037829#M3580</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;I also had this issue. After a few days of debugging I found the cause, it was a configuration failure on my site.&lt;/P&gt;&lt;P&gt;I need to mention that I have two WiSM blades. &lt;/P&gt;&lt;P&gt;The issue was that the wism service-vlan was the same vlan as the native-vlan. Because of that I received the errors. After I created a new vlan just for the service-port and put them into that vlan and assigned new ip addresses, everything was fine.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Tue, 09 Sep 2008 06:32:17 GMT</pubDate>
    <dc:creator>patoberli</dc:creator>
    <dc:date>2008-09-09T06:32:17Z</dc:date>
    <item>
      <title>Control path on mobility member is down</title>
      <link>https://community.cisco.com/t5/wireless/control-path-on-mobility-member-is-down/m-p/1037826#M3577</link>
      <description>&lt;P&gt;Greetings,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I have a tac case open on this issue but wanted to see if any of you may have encountered this problem.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Our guest controller loses is connection path every 5 days for 10 or fifteen minutes and then works fine for another five days until it does it again.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Any insight would be greatly appreciated&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Thanks much-&lt;/P&gt;</description>
      <pubDate>Sat, 03 Jul 2021 23:26:19 GMT</pubDate>
      <guid>https://community.cisco.com/t5/wireless/control-path-on-mobility-member-is-down/m-p/1037826#M3577</guid>
      <dc:creator>john.preves</dc:creator>
      <dc:date>2021-07-03T23:26:19Z</dc:date>
    </item>
    <item>
      <title>Re: Control path on mobility member is down</title>
      <link>https://community.cisco.com/t5/wireless/control-path-on-mobility-member-is-down/m-p/1037827#M3578</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Did you happen to of changed the ip address of the management, ap-manager or VIP?&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Tue, 09 Sep 2008 00:30:10 GMT</pubDate>
      <guid>https://community.cisco.com/t5/wireless/control-path-on-mobility-member-is-down/m-p/1037827#M3578</guid>
      <dc:creator>Scott Fella</dc:creator>
      <dc:date>2008-09-09T00:30:10Z</dc:date>
    </item>
    <item>
      <title>Re: Control path on mobility member is down</title>
      <link>https://community.cisco.com/t5/wireless/control-path-on-mobility-member-is-down/m-p/1037828#M3579</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Same here...&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Upgraded from 4.0.217 to 4.2.130 for 11N support.  Thought a MD release would be safe, nothing but problems for the last week.  We are experiencing CSCsr40109 and CSCsr89694.  217 ran solid for around a year, now our guest anchors are broken, data and control paths flapping continuously, and issues with the mobility group causing roaming problems with Vocera.  We are also seeing a third issue with DHCP not passing through the guest anchor and only a reboot will correct.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Ask your TAC engineer to execute the appropriate hidden "devshell" command from the console, which will show the Runtime Mobility Member List.  If you have a version other than 0 or 2, then you are hitting the mobility bug.  As for the anchor issue, the DE is looking over some debugs and captures, but no workarounds yet.  This seems to be a random issue that only effects some controllers.  Only 1 controller out of 10 are having this issue at our site.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Tue, 09 Sep 2008 01:46:47 GMT</pubDate>
      <guid>https://community.cisco.com/t5/wireless/control-path-on-mobility-member-is-down/m-p/1037828#M3579</guid>
      <dc:creator>Darren Ramsey</dc:creator>
      <dc:date>2008-09-09T01:46:47Z</dc:date>
    </item>
    <item>
      <title>Re: Control path on mobility member is down</title>
      <link>https://community.cisco.com/t5/wireless/control-path-on-mobility-member-is-down/m-p/1037829#M3580</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;I also had this issue. After a few days of debugging I found the cause, it was a configuration failure on my site.&lt;/P&gt;&lt;P&gt;I need to mention that I have two WiSM blades. &lt;/P&gt;&lt;P&gt;The issue was that the wism service-vlan was the same vlan as the native-vlan. Because of that I received the errors. After I created a new vlan just for the service-port and put them into that vlan and assigned new ip addresses, everything was fine.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Tue, 09 Sep 2008 06:32:17 GMT</pubDate>
      <guid>https://community.cisco.com/t5/wireless/control-path-on-mobility-member-is-down/m-p/1037829#M3580</guid>
      <dc:creator>patoberli</dc:creator>
      <dc:date>2008-09-09T06:32:17Z</dc:date>
    </item>
    <item>
      <title>Re: Control path on mobility member is down</title>
      <link>https://community.cisco.com/t5/wireless/control-path-on-mobility-member-is-down/m-p/1037830#M3581</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Thanks folks I'm looking into this now...&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Fri, 12 Sep 2008 19:38:10 GMT</pubDate>
      <guid>https://community.cisco.com/t5/wireless/control-path-on-mobility-member-is-down/m-p/1037830#M3581</guid>
      <dc:creator>john.preves</dc:creator>
      <dc:date>2008-09-12T19:38:10Z</dc:date>
    </item>
    <item>
      <title>Re: Control path on mobility member is down</title>
      <link>https://community.cisco.com/t5/wireless/control-path-on-mobility-member-is-down/m-p/1037831#M3582</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;John,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I have narrowed down the issue to having more than 5 entries in the guest anchor peer list.  When I add a 6th entry, the lowest IP in the peer list starts flapping.  Does it sound like you are seeing the same issue?&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Fri, 12 Sep 2008 19:43:33 GMT</pubDate>
      <guid>https://community.cisco.com/t5/wireless/control-path-on-mobility-member-is-down/m-p/1037831#M3582</guid>
      <dc:creator>Darren Ramsey</dc:creator>
      <dc:date>2008-09-12T19:43:33Z</dc:date>
    </item>
    <item>
      <title>Re: Control path on mobility member is down</title>
      <link>https://community.cisco.com/t5/wireless/control-path-on-mobility-member-is-down/m-p/1037832#M3583</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;I currently only have one entry but thanks, I know what to be looking for when we add the others!&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Fri, 12 Sep 2008 20:03:16 GMT</pubDate>
      <guid>https://community.cisco.com/t5/wireless/control-path-on-mobility-member-is-down/m-p/1037832#M3583</guid>
      <dc:creator>john.preves</dc:creator>
      <dc:date>2008-09-12T20:03:16Z</dc:date>
    </item>
  </channel>
</rss>

