<?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: Mobility Express Controller Failover in Wireless</title>
    <link>https://community.cisco.com/t5/wireless/mobility-express-controller-failover/m-p/3908265#M203127</link>
    <description>Looks like this fixes the issue. You need to change just the default username from cisco. This setting can be found in the web gui of the controller.&lt;BR /&gt;&lt;BR /&gt;Wireless Settings &amp;gt; Access Points &amp;gt; Global AP Configuration &amp;gt; Credentials(SSH) &amp;gt;Username&lt;BR /&gt;&lt;BR /&gt;</description>
    <pubDate>Wed, 14 Aug 2019 17:54:00 GMT</pubDate>
    <dc:creator>LucasC88</dc:creator>
    <dc:date>2019-08-14T17:54:00Z</dc:date>
    <item>
      <title>Mobility Express Controller Failover</title>
      <link>https://community.cisco.com/t5/wireless/mobility-express-controller-failover/m-p/3907701#M203119</link>
      <description>&lt;P&gt;I have a handful of 3800 series aironets. I have switched them to ME mode and all works as expected other than failover. The docs state that when an AP running the controller goes down another ME enabled AP should pick up the controller role and the management ip, config, etc should be passed along with it. This does not appear to be the case for me. One of the APs will end up launching the controller role but it will start in provisioning mode rather than with the previous config. I've read through all the docs and can't find any additional info as to why this may occur. Thanks in advanced&lt;/P&gt;</description>
      <pubDate>Mon, 05 Jul 2021 17:51:22 GMT</pubDate>
      <guid>https://community.cisco.com/t5/wireless/mobility-express-controller-failover/m-p/3907701#M203119</guid>
      <dc:creator>LucasC88</dc:creator>
      <dc:date>2021-07-05T17:51:22Z</dc:date>
    </item>
    <item>
      <title>Re: Mobility Express Controller Failover</title>
      <link>https://community.cisco.com/t5/wireless/mobility-express-controller-failover/m-p/3908108#M203120</link>
      <description>Which software version are you running?&lt;BR /&gt;Have you configured the secondary AP on the Master? You can (and I think must) define which should be the backup controller.</description>
      <pubDate>Wed, 14 Aug 2019 13:47:37 GMT</pubDate>
      <guid>https://community.cisco.com/t5/wireless/mobility-express-controller-failover/m-p/3908108#M203120</guid>
      <dc:creator>patoberli</dc:creator>
      <dc:date>2019-08-14T13:47:37Z</dc:date>
    </item>
    <item>
      <title>Re: Mobility Express Controller Failover</title>
      <link>https://community.cisco.com/t5/wireless/mobility-express-controller-failover/m-p/3908122#M203121</link>
      <description>&lt;P&gt;If you are referring to the next preferred master setting I have tried that as well. The doc states that this should not be required and that it is not recommended but regardless this did not help. The issue appears to be due to the actual configuration not syncing between devices. The other APs will pick up the controller role but it initializes as if it is a fresh controller without a config (provisioning mode)&lt;/P&gt;</description>
      <pubDate>Wed, 14 Aug 2019 14:04:47 GMT</pubDate>
      <guid>https://community.cisco.com/t5/wireless/mobility-express-controller-failover/m-p/3908122#M203121</guid>
      <dc:creator>LucasC88</dc:creator>
      <dc:date>2019-08-14T14:04:47Z</dc:date>
    </item>
    <item>
      <title>Re: Mobility Express Controller Failover</title>
      <link>https://community.cisco.com/t5/wireless/mobility-express-controller-failover/m-p/3908149#M203122</link>
      <description>&lt;P&gt;Sounds like you're hitting a bug. Which version are you running?&lt;/P&gt;</description>
      <pubDate>Wed, 14 Aug 2019 14:38:48 GMT</pubDate>
      <guid>https://community.cisco.com/t5/wireless/mobility-express-controller-failover/m-p/3908149#M203122</guid>
      <dc:creator>patoberli</dc:creator>
      <dc:date>2019-08-14T14:38:48Z</dc:date>
    </item>
    <item>
      <title>Re: Mobility Express Controller Failover</title>
      <link>https://community.cisco.com/t5/wireless/mobility-express-controller-failover/m-p/3908158#M203123</link>
      <description>&lt;P&gt;I'm on mobile right now but I believe it is 8.5.151&lt;/P&gt;</description>
      <pubDate>Wed, 14 Aug 2019 14:58:46 GMT</pubDate>
      <guid>https://community.cisco.com/t5/wireless/mobility-express-controller-failover/m-p/3908158#M203123</guid>
      <dc:creator>LucasC88</dc:creator>
      <dc:date>2019-08-14T14:58:46Z</dc:date>
    </item>
    <item>
      <title>Re: Mobility Express Controller Failover</title>
      <link>https://community.cisco.com/t5/wireless/mobility-express-controller-failover/m-p/3908163#M203124</link>
      <description>&lt;P&gt;That would be a good release.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Have you changed the default credentials? I found this bug:&lt;/P&gt;
&lt;P&gt;&lt;FONT style="background-color: #ffffff;"&gt;&lt;A href="https://bst.cloudapps.cisco.com/bugsearch/bug/CSCvo85185" target="_blank"&gt;https://bst.cloudapps.cisco.com/bugsearch/bug/CSCvo85185&lt;/A&gt;&lt;/FONT&gt;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Wed, 14 Aug 2019 15:08:42 GMT</pubDate>
      <guid>https://community.cisco.com/t5/wireless/mobility-express-controller-failover/m-p/3908163#M203124</guid>
      <dc:creator>patoberli</dc:creator>
      <dc:date>2019-08-14T15:08:42Z</dc:date>
    </item>
    <item>
      <title>Re: Mobility Express Controller Failover</title>
      <link>https://community.cisco.com/t5/wireless/mobility-express-controller-failover/m-p/3908165#M203125</link>
      <description>I'll give this a shot when I get back into the office and report back.</description>
      <pubDate>Wed, 14 Aug 2019 15:11:42 GMT</pubDate>
      <guid>https://community.cisco.com/t5/wireless/mobility-express-controller-failover/m-p/3908165#M203125</guid>
      <dc:creator>LucasC88</dc:creator>
      <dc:date>2019-08-14T15:11:42Z</dc:date>
    </item>
    <item>
      <title>Re: Mobility Express Controller Failover</title>
      <link>https://community.cisco.com/t5/wireless/mobility-express-controller-failover/m-p/3908242#M203126</link>
      <description>&lt;BLOCKQUOTE&gt;&lt;HR /&gt;&lt;a href="https://community.cisco.com/t5/user/viewprofilepage/user-id/891153"&gt;@LucasC88&lt;/a&gt;&amp;nbsp;wrote:&lt;BR /&gt;&lt;P&gt;The other APs will pick up the controller role but it initializes as if it is a fresh controller without a config (provisioning mode)&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Are the other APs on the same Vlan than your current Master AP ?&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;You can check if your Surbordinate APs are ME capable AND synced :&lt;/P&gt;&lt;P&gt;- Show version (Your AP should have a ME image and be ME capable)&lt;/P&gt;&lt;P&gt;- sh flash config-sync (make a change on the Master AP and you should see on the surbordinate APs their config synced with the master with a timestamp in the flash)&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;HR /&gt;&lt;/BLOCKQUOTE&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Wed, 14 Aug 2019 17:18:39 GMT</pubDate>
      <guid>https://community.cisco.com/t5/wireless/mobility-express-controller-failover/m-p/3908242#M203126</guid>
      <dc:creator>MTOMASSINI</dc:creator>
      <dc:date>2019-08-14T17:18:39Z</dc:date>
    </item>
    <item>
      <title>Re: Mobility Express Controller Failover</title>
      <link>https://community.cisco.com/t5/wireless/mobility-express-controller-failover/m-p/3908265#M203127</link>
      <description>Looks like this fixes the issue. You need to change just the default username from cisco. This setting can be found in the web gui of the controller.&lt;BR /&gt;&lt;BR /&gt;Wireless Settings &amp;gt; Access Points &amp;gt; Global AP Configuration &amp;gt; Credentials(SSH) &amp;gt;Username&lt;BR /&gt;&lt;BR /&gt;</description>
      <pubDate>Wed, 14 Aug 2019 17:54:00 GMT</pubDate>
      <guid>https://community.cisco.com/t5/wireless/mobility-express-controller-failover/m-p/3908265#M203127</guid>
      <dc:creator>LucasC88</dc:creator>
      <dc:date>2019-08-14T17:54:00Z</dc:date>
    </item>
  </channel>
</rss>

