<?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: VSZ migration to new IP in Access Points - Indoor and Outdoor</title>
    <link>https://community.ruckuswireless.com/t5/Access-Points-Indoor-and-Outdoor/VSZ-migration-to-new-IP/m-p/8203#M1780</link>
    <description>Hi I got the same issue, i got two vSZ-High Scale. we are about to decommission the old vSZ.&amp;nbsp;&lt;BR alt="" name="" rel="" target="" title="" type="" value="" /&gt;&lt;BR alt="" name="" rel="" target="" title="" type="" value="" /&gt;i tried to perform the option 2.&amp;nbsp;&lt;BR alt="" name="" rel="" target="" title="" type="" value="" /&gt;&lt;BR alt="" name="" rel="" target="" title="" type="" value="" /&gt;remote ap-cli &lt;MAC&gt; "set scg ip &lt;NEW ip=""&gt;"&lt;BR alt="" name="" rel="" target="" title="" type="" value="" /&gt;&lt;BR alt="" name="" rel="" target="" title="" type="" value="" /&gt;the ap is being registered on the new Instance however the AP still keeps coming back on the old instance. is there a way for us to migrate the AP permanently to the new Instance?&lt;/NEW&gt;&lt;/MAC&gt;</description>
    <pubDate>Tue, 13 Nov 2018 22:10:22 GMT</pubDate>
    <dc:creator>jeffrey_alvin_s</dc:creator>
    <dc:date>2018-11-13T22:10:22Z</dc:date>
    <item>
      <title>VSZ migration to new IP</title>
      <link>https://community.ruckuswireless.com/t5/Access-Points-Indoor-and-Outdoor/VSZ-migration-to-new-IP/m-p/8200#M1777</link>
      <description>So, I currently have a VSZ VM server on one Public IP Subnet, I need to migrate it to a different Public IP Subnet. I haven't been able to find a good way to move AP's to a different controller IP remotely, so my thought was to either forward all IP traffic from the original IP to the new IP, but I haven't been able to make that work, and I'm not sure that will work on a public. My second thought was to add both IP's to the new VSZ instance, so we can gradually go to all the AP sites and migrate them to the new IP.&amp;nbsp;&lt;BR /&gt;Has anyone else forwarded AP controller traffic before to a new IP? Or does anyone know if you can add a second VSZ controller IP to the same VSZ?</description>
      <pubDate>Thu, 31 May 2018 14:36:00 GMT</pubDate>
      <guid>https://community.ruckuswireless.com/t5/Access-Points-Indoor-and-Outdoor/VSZ-migration-to-new-IP/m-p/8200#M1777</guid>
      <dc:creator>south_central_c</dc:creator>
      <dc:date>2018-05-31T14:36:00Z</dc:date>
    </item>
    <item>
      <title>Re: VSZ migration to new IP</title>
      <link>https://community.ruckuswireless.com/t5/Access-Points-Indoor-and-Outdoor/VSZ-migration-to-new-IP/m-p/8201#M1778</link>
      <description>What if you were to commission a new server VM on the new IP and cluster it with the old one?&amp;nbsp; Then the access points would receive both IPs as controllers available to connect to.&amp;nbsp; They can now communicate with the new SZ, subsequently decommission the old server (after a little while).&lt;BR /&gt;&lt;BR /&gt;I have not tried this, but in theory it should get you where you need to go... best of luck!</description>
      <pubDate>Fri, 01 Jun 2018 12:51:55 GMT</pubDate>
      <guid>https://community.ruckuswireless.com/t5/Access-Points-Indoor-and-Outdoor/VSZ-migration-to-new-IP/m-p/8201#M1778</guid>
      <dc:creator>sunny_gupta</dc:creator>
      <dc:date>2018-06-01T12:51:55Z</dc:date>
    </item>
    <item>
      <title>Re: VSZ migration to new IP</title>
      <link>https://community.ruckuswireless.com/t5/Access-Points-Indoor-and-Outdoor/VSZ-migration-to-new-IP/m-p/8202#M1779</link>
      <description>Hi Aaron,&lt;BR /&gt;&lt;BR /&gt;Hope you are doing Good.&lt;BR /&gt;&lt;BR /&gt;Sandeep's suggetion would work.&amp;nbsp;&lt;BR /&gt;&lt;BR /&gt;1.Build a new vSZ with the new Public IP, restore it with old vSZ configuration backup.&lt;BR /&gt;2.Schedule a down time, now run AP-CLI script on old vSZ (set scg ip &lt;NEW public="" ip=""&gt;)&amp;nbsp;refer KB to build AP-cli script (&lt;A href="https://support.ruckuswireless.com/answers/000004057" rel="nofollow" target="_blank" title="https//supportruckuswirelesscom/answers/000004057"&gt;https://support.ruckuswireless.com/answers/000004057&lt;/A&gt;).&lt;BR /&gt;3.Shutdown the old vSZ, APs would terminate&amp;nbsp;to new vSZ.&lt;BR /&gt;&lt;BR /&gt;Please test with one AP and then plan accordingly.&lt;BR /&gt;&lt;BR /&gt;Should you have any issues please feel free to open a case with Support.&lt;BR /&gt;&lt;BR /&gt;Thank you.&lt;BR /&gt;&lt;BR /&gt;Abilash PR.&lt;/NEW&gt;</description>
      <pubDate>Fri, 01 Jun 2018 14:54:52 GMT</pubDate>
      <guid>https://community.ruckuswireless.com/t5/Access-Points-Indoor-and-Outdoor/VSZ-migration-to-new-IP/m-p/8202#M1779</guid>
      <dc:creator>abilash_p_r</dc:creator>
      <dc:date>2018-06-01T14:54:52Z</dc:date>
    </item>
    <item>
      <title>Re: VSZ migration to new IP</title>
      <link>https://community.ruckuswireless.com/t5/Access-Points-Indoor-and-Outdoor/VSZ-migration-to-new-IP/m-p/8203#M1780</link>
      <description>Hi I got the same issue, i got two vSZ-High Scale. we are about to decommission the old vSZ.&amp;nbsp;&lt;BR alt="" name="" rel="" target="" title="" type="" value="" /&gt;&lt;BR alt="" name="" rel="" target="" title="" type="" value="" /&gt;i tried to perform the option 2.&amp;nbsp;&lt;BR alt="" name="" rel="" target="" title="" type="" value="" /&gt;&lt;BR alt="" name="" rel="" target="" title="" type="" value="" /&gt;remote ap-cli &lt;MAC&gt; "set scg ip &lt;NEW ip=""&gt;"&lt;BR alt="" name="" rel="" target="" title="" type="" value="" /&gt;&lt;BR alt="" name="" rel="" target="" title="" type="" value="" /&gt;the ap is being registered on the new Instance however the AP still keeps coming back on the old instance. is there a way for us to migrate the AP permanently to the new Instance?&lt;/NEW&gt;&lt;/MAC&gt;</description>
      <pubDate>Tue, 13 Nov 2018 22:10:22 GMT</pubDate>
      <guid>https://community.ruckuswireless.com/t5/Access-Points-Indoor-and-Outdoor/VSZ-migration-to-new-IP/m-p/8203#M1780</guid>
      <dc:creator>jeffrey_alvin_s</dc:creator>
      <dc:date>2018-11-13T22:10:22Z</dc:date>
    </item>
    <item>
      <title>Re: VSZ migration to new IP</title>
      <link>https://community.ruckuswireless.com/t5/Access-Points-Indoor-and-Outdoor/VSZ-migration-to-new-IP/m-p/8204#M1781</link>
      <description>I was able to figured out the problem. make sure that your AP's and the new controller's zone has the same firmware.&lt;BR /&gt;&lt;BR /&gt;Cheers,&lt;BR /&gt;Jeffrey Alvin Subido</description>
      <pubDate>Wed, 14 Nov 2018 15:18:26 GMT</pubDate>
      <guid>https://community.ruckuswireless.com/t5/Access-Points-Indoor-and-Outdoor/VSZ-migration-to-new-IP/m-p/8204#M1781</guid>
      <dc:creator>jeffrey_alvin_s</dc:creator>
      <dc:date>2018-11-14T15:18:26Z</dc:date>
    </item>
  </channel>
</rss>

