<?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 SmartZone 100 leader - failback in Access Points - Indoor and Outdoor</title>
    <link>https://community.ruckuswireless.com/t5/Access-Points-Indoor-and-Outdoor/SmartZone-100-leader-failback/m-p/30330#M8476</link>
    <description>Dear support,&lt;BR /&gt;&lt;BR /&gt;I have two SmartZone 100 controllers and they are working together in&amp;nbsp; a cluster (one as a leader the other one as a follower). When I restart the leader I thought that when it comes back online that it is going to be&amp;nbsp; leader again, not follower. So do you have any advice how to set up SmartZone 100 failback? The idea is if SmartZone 100 leader is restarted to be a leader again when it comes back online.&amp;nbsp;</description>
    <pubDate>Wed, 19 Feb 2020 15:45:31 GMT</pubDate>
    <dc:creator>marko_carapic</dc:creator>
    <dc:date>2020-02-19T15:45:31Z</dc:date>
    <item>
      <title>SmartZone 100 leader - failback</title>
      <link>https://community.ruckuswireless.com/t5/Access-Points-Indoor-and-Outdoor/SmartZone-100-leader-failback/m-p/30330#M8476</link>
      <description>Dear support,&lt;BR /&gt;&lt;BR /&gt;I have two SmartZone 100 controllers and they are working together in&amp;nbsp; a cluster (one as a leader the other one as a follower). When I restart the leader I thought that when it comes back online that it is going to be&amp;nbsp; leader again, not follower. So do you have any advice how to set up SmartZone 100 failback? The idea is if SmartZone 100 leader is restarted to be a leader again when it comes back online.&amp;nbsp;</description>
      <pubDate>Wed, 19 Feb 2020 15:45:31 GMT</pubDate>
      <guid>https://community.ruckuswireless.com/t5/Access-Points-Indoor-and-Outdoor/SmartZone-100-leader-failback/m-p/30330#M8476</guid>
      <dc:creator>marko_carapic</dc:creator>
      <dc:date>2020-02-19T15:45:31Z</dc:date>
    </item>
    <item>
      <title>Re: SmartZone 100 leader - failback</title>
      <link>https://community.ruckuswireless.com/t5/Access-Points-Indoor-and-Outdoor/SmartZone-100-leader-failback/m-p/30331#M8477</link>
      <description>You have to restart the flower so the primary back again as leader</description>
      <pubDate>Wed, 19 Feb 2020 15:48:30 GMT</pubDate>
      <guid>https://community.ruckuswireless.com/t5/Access-Points-Indoor-and-Outdoor/SmartZone-100-leader-failback/m-p/30331#M8477</guid>
      <dc:creator>tamer_morcos</dc:creator>
      <dc:date>2020-02-19T15:48:30Z</dc:date>
    </item>
    <item>
      <title>Re: SmartZone 100 leader - failback</title>
      <link>https://community.ruckuswireless.com/t5/Access-Points-Indoor-and-Outdoor/SmartZone-100-leader-failback/m-p/30332#M8478</link>
      <description>There is nothing special about the "leader" node beyond being a single point of time synchronization for the cluster and AP's and also an arbiter of data base conflicts.&amp;nbsp; In SZ Cluster all nodes are active and peers.&amp;nbsp; Any node can be leader at any time.&amp;nbsp; From an operational point of view there is no reason to make one node always the leader so no mechanism exists to failback.&amp;nbsp; If you insist on having one particular node be leader you can reboot the follower - but this is a drastic and potentially problematic solution that will affect end user operation as AP's move from one node to another.&amp;nbsp; Best is to not worry about which node is the leader. &lt;BR alt="" name="" rel="" target="" title="" type="" value="" /&gt;</description>
      <pubDate>Wed, 19 Feb 2020 15:54:20 GMT</pubDate>
      <guid>https://community.ruckuswireless.com/t5/Access-Points-Indoor-and-Outdoor/SmartZone-100-leader-failback/m-p/30332#M8478</guid>
      <dc:creator>albert_pierson</dc:creator>
      <dc:date>2020-02-19T15:54:20Z</dc:date>
    </item>
  </channel>
</rss>

