<?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: Multiple mobility networks in Wireless</title>
    <link>https://community.cisco.com/t5/wireless/multiple-mobility-networks/m-p/3911628#M170582</link>
    <description>&lt;P&gt;I am using it with real WLCs(3504/2504) but not with ME WLC but you can give a try.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Try&amp;nbsp; to autorize the AP specific to WLC, means only autorize AP(Building1) can join to ME WLC(Building 1) and same for other building.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;&lt;A href="http://www.manualsdir.com/manuals/62928/cisco-wireless-lan-controller-ol-17037-01.html?page=24" target="_blank"&gt;http://www.manualsdir.com/manuals/62928/cisco-wireless-lan-controller-ol-17037-01.html?page=24&lt;/A&gt;&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/4400-series-wireless-lan-controllers/98848-lap-auth-uwn-config.html" target="_blank"&gt;https://www.cisco.com/c/en/us/support/docs/wireless/4400-series-wireless-lan-controllers/98848-lap-auth-uwn-config.html&lt;/A&gt;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Regards&lt;/P&gt;
&lt;P&gt;Dont forget to arte helpful posts&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
    <pubDate>Wed, 21 Aug 2019 13:20:28 GMT</pubDate>
    <dc:creator>Sandeep Choudhary</dc:creator>
    <dc:date>2019-08-21T13:20:28Z</dc:date>
    <item>
      <title>Multiple mobility networks</title>
      <link>https://community.cisco.com/t5/wireless/multiple-mobility-networks/m-p/3911158#M170578</link>
      <description>&lt;P&gt;I was wondering if there is a method to keep capwap APs from joining any mobility express controller or locking them down to a subnet?&amp;nbsp; I'm standing up another mobility express network on a separate subnet for another building and I noticed other APs joining the new installation rather than staying connected to there "designated controller". I have removed the DNS entries and was hoping Dhcp option 43 would force the join or even election of a new controller in the subnet. That does not seem to work as I have previously configured APs joining the new network instead of staying put.&lt;/P&gt;&lt;P&gt;Any suggestion s would be great.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Thanks&lt;/P&gt;&lt;P&gt;Mark&lt;/P&gt;</description>
      <pubDate>Mon, 05 Jul 2021 17:53:03 GMT</pubDate>
      <guid>https://community.cisco.com/t5/wireless/multiple-mobility-networks/m-p/3911158#M170578</guid>
      <dc:creator>khatiblou</dc:creator>
      <dc:date>2021-07-05T17:53:03Z</dc:date>
    </item>
    <item>
      <title>Re: Multiple mobility networks</title>
      <link>https://community.cisco.com/t5/wireless/multiple-mobility-networks/m-p/3911272#M170579</link>
      <description>&lt;P&gt;No its not a good idea!&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Best case would be to implement single wireless solution in whole network not multiple.&amp;nbsp;&lt;/P&gt;
&lt;P&gt;&lt;SPAN&gt;Simply designate one as Master and maybe one or two as backup. The rest will then simply connect to the Master while booting.&lt;/SPAN&gt;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Regards&lt;/P&gt;
&lt;P&gt;Dont forget to rate helpful posts&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Wed, 21 Aug 2019 04:53:49 GMT</pubDate>
      <guid>https://community.cisco.com/t5/wireless/multiple-mobility-networks/m-p/3911272#M170579</guid>
      <dc:creator>Sandeep Choudhary</dc:creator>
      <dc:date>2019-08-21T04:53:49Z</dc:date>
    </item>
    <item>
      <title>Re: Multiple mobility networks</title>
      <link>https://community.cisco.com/t5/wireless/multiple-mobility-networks/m-p/3911325#M170580</link>
      <description>&lt;P&gt;On the existing AP's on the WLC you should go to their high availability tab and only enter the primary controller name and IP being your current controller.&lt;BR /&gt;&lt;BR /&gt;If your AP's of the existing installation are of a certain type and the mobility express AP's are from another type, then you could utilize option 43 in combination of vendor class identifiers to only give out option 43 to a certain type of AP's.&lt;BR /&gt;&lt;BR /&gt;There are examples on the internet but I haven't done anything like it.&lt;/P&gt;</description>
      <pubDate>Wed, 21 Aug 2019 06:10:47 GMT</pubDate>
      <guid>https://community.cisco.com/t5/wireless/multiple-mobility-networks/m-p/3911325#M170580</guid>
      <dc:creator>joey.debra</dc:creator>
      <dc:date>2019-08-21T06:10:47Z</dc:date>
    </item>
    <item>
      <title>Re: Multiple mobility networks</title>
      <link>https://community.cisco.com/t5/wireless/multiple-mobility-networks/m-p/3911601#M170581</link>
      <description>&lt;P&gt;Thanks for the reply Sandeep,&lt;/P&gt;&lt;P&gt;I have thought of that but our connections between buildings is a hodgepodge of Layer2, layer3, VPN that some locations would have issues with capwap APs keeping in contact with the masters. I'm just confused that a method to segregate controllers isn't readily accessible&amp;nbsp; and in our situation and it would be much better to have 1 or 2 WLans per location visible instead of 15 at all locations.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Thanks&lt;/P&gt;</description>
      <pubDate>Wed, 21 Aug 2019 12:51:48 GMT</pubDate>
      <guid>https://community.cisco.com/t5/wireless/multiple-mobility-networks/m-p/3911601#M170581</guid>
      <dc:creator>khatiblou</dc:creator>
      <dc:date>2019-08-21T12:51:48Z</dc:date>
    </item>
    <item>
      <title>Re: Multiple mobility networks</title>
      <link>https://community.cisco.com/t5/wireless/multiple-mobility-networks/m-p/3911628#M170582</link>
      <description>&lt;P&gt;I am using it with real WLCs(3504/2504) but not with ME WLC but you can give a try.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Try&amp;nbsp; to autorize the AP specific to WLC, means only autorize AP(Building1) can join to ME WLC(Building 1) and same for other building.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;&lt;A href="http://www.manualsdir.com/manuals/62928/cisco-wireless-lan-controller-ol-17037-01.html?page=24" target="_blank"&gt;http://www.manualsdir.com/manuals/62928/cisco-wireless-lan-controller-ol-17037-01.html?page=24&lt;/A&gt;&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/4400-series-wireless-lan-controllers/98848-lap-auth-uwn-config.html" target="_blank"&gt;https://www.cisco.com/c/en/us/support/docs/wireless/4400-series-wireless-lan-controllers/98848-lap-auth-uwn-config.html&lt;/A&gt;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Regards&lt;/P&gt;
&lt;P&gt;Dont forget to arte helpful posts&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Wed, 21 Aug 2019 13:20:28 GMT</pubDate>
      <guid>https://community.cisco.com/t5/wireless/multiple-mobility-networks/m-p/3911628#M170582</guid>
      <dc:creator>Sandeep Choudhary</dc:creator>
      <dc:date>2019-08-21T13:20:28Z</dc:date>
    </item>
    <item>
      <title>Re: Multiple mobility networks</title>
      <link>https://community.cisco.com/t5/wireless/multiple-mobility-networks/m-p/3911661#M170583</link>
      <description>&lt;P&gt;Thanks for the reply Joey,&lt;/P&gt;&lt;P&gt;I'm looking at the HA setup now but how does the roll over of Master APs finding random master APs and just joining? Is their more to the HA setup that effects the way capwap APs pick a master? I was setting up 4 2802i APs at my desk for a new location and a 1562i capwap AP in an existing production network just joined. Whats even better is that the switch/trunk configuration for that 1562i and the WLan created for the 2802i is incompatible. Good idea on the DHCP options, I'm going to dig into that to see what else can be done... or it's going to be writing ACLs to block APs from roaming off the lan.. ugh&lt;/P&gt;</description>
      <pubDate>Wed, 21 Aug 2019 13:44:35 GMT</pubDate>
      <guid>https://community.cisco.com/t5/wireless/multiple-mobility-networks/m-p/3911661#M170583</guid>
      <dc:creator>khatiblou</dc:creator>
      <dc:date>2019-08-21T13:44:35Z</dc:date>
    </item>
    <item>
      <title>Re: Multiple mobility networks</title>
      <link>https://community.cisco.com/t5/wireless/multiple-mobility-networks/m-p/3911748#M170584</link>
      <description>&lt;P&gt;What I also found is that when an AP joins an incorrect controller:&lt;BR /&gt;The moment you set the primary controller on that AP, it immediatly disconnects and tries to join the correct controller.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;You also need to be wary that when you have Mobility express capable AP's and they run an ME image they don't even look for a regular controller but look for an ME controller.&lt;BR /&gt;&lt;BR /&gt;The moment you issue the ap-type capwap in the CLI of the AP it strips off the ME code and reboots and starts to look for regular WLC's.&amp;nbsp; But in your case you actually want the new AP's to join the ME controller so that's not the case &lt;span class="lia-unicode-emoji" title=":slightly_smiling_face:"&gt;🙂&lt;/span&gt;&lt;/P&gt;</description>
      <pubDate>Wed, 21 Aug 2019 15:52:28 GMT</pubDate>
      <guid>https://community.cisco.com/t5/wireless/multiple-mobility-networks/m-p/3911748#M170584</guid>
      <dc:creator>joey.debra</dc:creator>
      <dc:date>2019-08-21T15:52:28Z</dc:date>
    </item>
    <item>
      <title>Re: Multiple mobility networks</title>
      <link>https://community.cisco.com/t5/wireless/multiple-mobility-networks/m-p/3911760#M170585</link>
      <description>&lt;P&gt;Sandeep,&lt;/P&gt;&lt;P&gt;Yeah I can't find any of this in the Mobility Express controller web page nor in either the capwap or controller cli. Would have been nice though &lt;span class="lia-unicode-emoji" title=":winking_face:"&gt;😉&lt;/span&gt;&lt;/P&gt;</description>
      <pubDate>Wed, 21 Aug 2019 16:06:43 GMT</pubDate>
      <guid>https://community.cisco.com/t5/wireless/multiple-mobility-networks/m-p/3911760#M170585</guid>
      <dc:creator>khatiblou</dc:creator>
      <dc:date>2019-08-21T16:06:43Z</dc:date>
    </item>
    <item>
      <title>Re: Multiple mobility networks</title>
      <link>https://community.cisco.com/t5/wireless/multiple-mobility-networks/m-p/3911799#M170586</link>
      <description>&lt;P&gt;So I have configured DHCP with options 43 and 60 for each scope and flushed all the DNS entries for all ME controllers along with setting HA for both groups of APs. So far no wandering APs.&lt;/P&gt;&lt;P&gt;Thanks Joey&lt;/P&gt;</description>
      <pubDate>Wed, 21 Aug 2019 17:08:37 GMT</pubDate>
      <guid>https://community.cisco.com/t5/wireless/multiple-mobility-networks/m-p/3911799#M170586</guid>
      <dc:creator>khatiblou</dc:creator>
      <dc:date>2019-08-21T17:08:37Z</dc:date>
    </item>
  </channel>
</rss>

