<?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: vSCG vSZ redundancy in Access Points - Indoor and Outdoor</title>
    <link>https://community.ruckuswireless.com/t5/Access-Points-Indoor-and-Outdoor/vSCG-vSZ-redundancy/m-p/4375#M543</link>
    <description>Hi Othmane
&lt;BR /&gt;
You can build a vSZ as a cluster, as this is done it acts as one big vSZ with all the needs you mentioned. 
&lt;BR /&gt;
To build this you need the vsz build up from scratch with 3 nic's. One  of them is the cluster network.
&lt;BR /&gt;&lt;BR /&gt;
to geographicaly be independent, we'll that is a tricky one. The cluster network allows a delay off maximum 10-15 mS. 
&lt;BR /&gt;&lt;BR /&gt;
Niko</description>
    <pubDate>Tue, 25 Oct 2016 06:55:04 GMT</pubDate>
    <dc:creator>niko_mattheus</dc:creator>
    <dc:date>2016-10-25T06:55:04Z</dc:date>
    <item>
      <title>vSCG vSZ redundancy</title>
      <link>https://community.ruckuswireless.com/t5/Access-Points-Indoor-and-Outdoor/vSCG-vSZ-redundancy/m-p/4374#M542</link>
      <description>Hi guys,&lt;BR /&gt;&lt;BR /&gt;We have a Virtual Smartzone installed on a VM and we would like to implement redundancy. The goal is to have like two active/passive or active/active instances:&lt;BR /&gt;- in case of the failure of an instance, the APs should be able to join another one &lt;BR /&gt;- our AAA authentication traffic also goes via the vSZ, so we would like to ensure that already connected users are still connected and &lt;B&gt;&lt;U&gt;the new users should be able to authenticate&lt;BR /&gt;&lt;/U&gt;&lt;/B&gt;- Ideally, we would like to have geographical redundancy and put the instances in different locations&lt;B&gt;&lt;U&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;/U&gt;﻿&lt;/B&gt;﻿Is there any doc that shows how we can implement this or maybe another way to achieve it.&lt;BR /&gt;&lt;BR /&gt;Any help would be highly appreciated!&lt;BR /&gt;thanks</description>
      <pubDate>Mon, 24 Oct 2016 14:56:25 GMT</pubDate>
      <guid>https://community.ruckuswireless.com/t5/Access-Points-Indoor-and-Outdoor/vSCG-vSZ-redundancy/m-p/4374#M542</guid>
      <dc:creator>othmane_douiri_</dc:creator>
      <dc:date>2016-10-24T14:56:25Z</dc:date>
    </item>
    <item>
      <title>Re: vSCG vSZ redundancy</title>
      <link>https://community.ruckuswireless.com/t5/Access-Points-Indoor-and-Outdoor/vSCG-vSZ-redundancy/m-p/4375#M543</link>
      <description>Hi Othmane
&lt;BR /&gt;
You can build a vSZ as a cluster, as this is done it acts as one big vSZ with all the needs you mentioned. 
&lt;BR /&gt;
To build this you need the vsz build up from scratch with 3 nic's. One  of them is the cluster network.
&lt;BR /&gt;&lt;BR /&gt;
to geographicaly be independent, we'll that is a tricky one. The cluster network allows a delay off maximum 10-15 mS. 
&lt;BR /&gt;&lt;BR /&gt;
Niko</description>
      <pubDate>Tue, 25 Oct 2016 06:55:04 GMT</pubDate>
      <guid>https://community.ruckuswireless.com/t5/Access-Points-Indoor-and-Outdoor/vSCG-vSZ-redundancy/m-p/4375#M543</guid>
      <dc:creator>niko_mattheus</dc:creator>
      <dc:date>2016-10-25T06:55:04Z</dc:date>
    </item>
  </channel>
</rss>

