<?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: roaming issue in ZoneDirector</title>
    <link>https://community.ruckuswireless.com/t5/ZoneDirector/roaming-issue/m-p/9857#M1935</link>
    <description>I am assuming that the issue is that the controllers are not linked to each other:&lt;BR /&gt;&lt;BR /&gt;Exmaple:&lt;BR /&gt;&lt;BR /&gt;10 AP's on controller 1 for building 1 and then say 20 AP's on the other controller in buillding 2.&lt;BR /&gt;&lt;BR /&gt;If this is the case you have to configure Force DHCP on the SSID's&amp;nbsp; on all controllers.&lt;BR /&gt;&lt;BR /&gt;This is due to teh fact that the 802.11r function only works with AP's on the same network i.e. the same controller.&lt;BR /&gt;&lt;BR /&gt;Juts think AP01 is on ZD1 and APO2 is on ZD02. AP01 cannot advertise to AP02 that a client has joined as its not aware of AP02 and vice versa, so the only way to get the client to roam is by forcing the client to take a new IP address, as the client will not make a DHCP request until its lease runs out.&lt;BR /&gt;&lt;BR /&gt;Good Luck&lt;BR /&gt;&lt;BR /&gt;&lt;span class="lia-unicode-emoji" title=":slightly_smiling_face:"&gt;🙂&lt;/span&gt;</description>
    <pubDate>Fri, 16 Jun 2017 13:23:24 GMT</pubDate>
    <dc:creator>seanmuir</dc:creator>
    <dc:date>2017-06-16T13:23:24Z</dc:date>
    <item>
      <title>roaming issue</title>
      <link>https://community.ruckuswireless.com/t5/ZoneDirector/roaming-issue/m-p/9856#M1934</link>
      <description>HI All, &amp;nbsp;we have 3 ruckus ZD1106 WLC , There are 3 wireless controller, when user connected on one SSID and move from one building to another then automatically disconnected from same SSID After disconnecting from SSID , they have to delete wireless profile from system and after configuring on system it work.</description>
      <pubDate>Fri, 16 Jun 2017 12:32:51 GMT</pubDate>
      <guid>https://community.ruckuswireless.com/t5/ZoneDirector/roaming-issue/m-p/9856#M1934</guid>
      <dc:creator>raghu_m</dc:creator>
      <dc:date>2017-06-16T12:32:51Z</dc:date>
    </item>
    <item>
      <title>Re: roaming issue</title>
      <link>https://community.ruckuswireless.com/t5/ZoneDirector/roaming-issue/m-p/9857#M1935</link>
      <description>I am assuming that the issue is that the controllers are not linked to each other:&lt;BR /&gt;&lt;BR /&gt;Exmaple:&lt;BR /&gt;&lt;BR /&gt;10 AP's on controller 1 for building 1 and then say 20 AP's on the other controller in buillding 2.&lt;BR /&gt;&lt;BR /&gt;If this is the case you have to configure Force DHCP on the SSID's&amp;nbsp; on all controllers.&lt;BR /&gt;&lt;BR /&gt;This is due to teh fact that the 802.11r function only works with AP's on the same network i.e. the same controller.&lt;BR /&gt;&lt;BR /&gt;Juts think AP01 is on ZD1 and APO2 is on ZD02. AP01 cannot advertise to AP02 that a client has joined as its not aware of AP02 and vice versa, so the only way to get the client to roam is by forcing the client to take a new IP address, as the client will not make a DHCP request until its lease runs out.&lt;BR /&gt;&lt;BR /&gt;Good Luck&lt;BR /&gt;&lt;BR /&gt;&lt;span class="lia-unicode-emoji" title=":slightly_smiling_face:"&gt;🙂&lt;/span&gt;</description>
      <pubDate>Fri, 16 Jun 2017 13:23:24 GMT</pubDate>
      <guid>https://community.ruckuswireless.com/t5/ZoneDirector/roaming-issue/m-p/9857#M1935</guid>
      <dc:creator>seanmuir</dc:creator>
      <dc:date>2017-06-16T13:23:24Z</dc:date>
    </item>
  </channel>
</rss>

