<?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: Can I have 2 vSZ-H 5.2.x Cluster nodes on separate cloud platforms for 
redundancy and geographi in To Be Moved</title>
    <link>https://community.ruckuswireless.com/t5/To-Be-Moved/Can-I-have-2-vSZ-H-5-2-x-Cluster-nodes-on-separate-cloud/m-p/62953#M2461</link>
    <description>&lt;P&gt;Hello Tim, did you make sure both controllers can ping each other through their private IP addresses? This would be necessary for the cluster to form.&lt;/P&gt;</description>
    <pubDate>Thu, 13 Jul 2023 19:12:09 GMT</pubDate>
    <dc:creator>Orlando_Elias</dc:creator>
    <dc:date>2023-07-13T19:12:09Z</dc:date>
    <item>
      <title>Can I have 2 vSZ-H 5.2.x Cluster nodes on separate cloud platforms for 
redundancy and geographic failover?</title>
      <link>https://community.ruckuswireless.com/t5/To-Be-Moved/Can-I-have-2-vSZ-H-5-2-x-Cluster-nodes-on-separate-cloud/m-p/21308#M1300</link>
      <description>I MSP for a number of schools and clients in various states and I own 2 instances of vSZ-H that I want to cluster together but have one on AWS and the other on Google Cloud.&lt;BR alt="" name="" rel="" target="" title="" type="" value="" /&gt;&lt;BR alt="" name="" rel="" target="" title="" type="" value="" /&gt;I have the vSZ-H&amp;nbsp;5.2.0.0.699 node in Google Cloud running as my master with all APs and switches connected there and want to add a cluster node running in AWS for failover and platform redundancy.&lt;BR alt="" name="" rel="" target="" title="" type="" value="" /&gt;&lt;BR alt="" name="" rel="" target="" title="" type="" value="" /&gt;I can bring up the second vSZ-H on AWS but when I try to connect it as a follower node, I get an NTP error in the setup wizard.&lt;BR alt="" name="" rel="" target="" title="" type="" value="" /&gt;&lt;BR alt="" name="" rel="" target="" title="" type="" value="" /&gt;The error is "Cannot reach cluster IP [X.X.X.X] with NTP service!" With X.X.X.X being the internal (private) IP of the running leader which is entered in the&amp;nbsp;&lt;B alt="" name="" rel="" target="" title="" type="" value=""&gt;Join Exist vSZ Cluster IP&amp;nbsp;&lt;/B&gt;field which is what technical support said should be entered. The &lt;B alt="" name="" rel="" target="" title="" type="" value=""&gt;Control NAT IP&lt;/B&gt; is the public IP of the Leader node.&lt;BR alt="" name="" rel="" target="" title="" type="" value="" /&gt;&lt;BR alt="" name="" rel="" target="" title="" type="" value="" /&gt;If I factory reset it, I can bring it up standalone just fine with no errors. In fact, in a previous life this was a vSZ-E standalone that worked fine other than the -E limitations.&lt;BR alt="" name="" rel="" target="" title="" type="" value="" /&gt;&lt;BR alt="" name="" rel="" target="" title="" type="" value="" /&gt;Has anyone done this with separate datacenters or cloud providers? This does not seem too unusual a scenario, right?&lt;BR alt="" name="" rel="" target="" title="" type="" value="" /&gt;&lt;BR alt="" name="" rel="" target="" title="" type="" value="" /&gt;Currently, the firewall rules for both the &lt;B alt="" name="" rel="" target="" title="" type="" value=""&gt;GCC&lt;/B&gt; and &lt;B alt="" name="" rel="" target="" title="" type="" value=""&gt;AWS&lt;/B&gt; instances are pretty wide open, so it does not seem like that should be an issue?&lt;BR alt="" name="" rel="" target="" title="" type="" value="" /&gt;&lt;BR alt="" name="" rel="" target="" title="" type="" value="" /&gt;case #&amp;nbsp;01077014&amp;nbsp;&lt;BR alt="" name="" rel="" target="" title="" type="" value="" /&gt;&lt;BR alt="" name="" rel="" target="" title="" type="" value="" /&gt;Thanks!&lt;BR alt="" name="" rel="" target="" title="" type="" value="" /&gt;Tim&lt;BR alt="" name="" rel="" target="" title="" type="" value="" /&gt;&lt;BR alt="" name="" rel="" target="" title="" type="" value="" /&gt;&lt;BR alt="" name="" rel="" target="" title="" type="" value="" /&gt;</description>
      <pubDate>Thu, 09 Jul 2020 01:19:03 GMT</pubDate>
      <guid>https://community.ruckuswireless.com/t5/To-Be-Moved/Can-I-have-2-vSZ-H-5-2-x-Cluster-nodes-on-separate-cloud/m-p/21308#M1300</guid>
      <dc:creator>timothy_kamps</dc:creator>
      <dc:date>2020-07-09T01:19:03Z</dc:date>
    </item>
    <item>
      <title>Re: Can I have 2 vSZ-H 5.2.x Cluster nodes on separate cloud platforms for 
redundancy and geographi</title>
      <link>https://community.ruckuswireless.com/t5/To-Be-Moved/Can-I-have-2-vSZ-H-5-2-x-Cluster-nodes-on-separate-cloud/m-p/62953#M2461</link>
      <description>&lt;P&gt;Hello Tim, did you make sure both controllers can ping each other through their private IP addresses? This would be necessary for the cluster to form.&lt;/P&gt;</description>
      <pubDate>Thu, 13 Jul 2023 19:12:09 GMT</pubDate>
      <guid>https://community.ruckuswireless.com/t5/To-Be-Moved/Can-I-have-2-vSZ-H-5-2-x-Cluster-nodes-on-separate-cloud/m-p/62953#M2461</guid>
      <dc:creator>Orlando_Elias</dc:creator>
      <dc:date>2023-07-13T19:12:09Z</dc:date>
    </item>
  </channel>
</rss>

