<?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: cluster out of service in To Be Moved</title>
    <link>https://community.ruckuswireless.com/t5/To-Be-Moved/cluster-out-of-service/m-p/6959#M313</link>
    <description>Hello,
&lt;BR /&gt;One of the solutions that ruckus provided us is to put a patch and establish the resource conditions that the controller needs. The other solution is to create the virtual controller again with the features you need.
&lt;BR /&gt;&lt;BR /&gt;Contact ruckus support to help you with a support session.&lt;BR /&gt;&lt;BR /&gt;Regards..</description>
    <pubDate>Fri, 09 Jun 2017 13:24:53 GMT</pubDate>
    <dc:creator>ivan_gonzalez_g</dc:creator>
    <dc:date>2017-06-09T13:24:53Z</dc:date>
    <item>
      <title>cluster out of service</title>
      <link>https://community.ruckuswireless.com/t5/To-Be-Moved/cluster-out-of-service/m-p/6957#M311</link>
      <description>Hi,&lt;BR /&gt;Hello,
I am working on the VSZ-High Scale platform, I have increased the memory resources, I got a bug: "Cluster Out of Service" ..... Someone can help me to activate the cluster again, because no I can do any work on the platform ....
&amp;nbsp;&lt;BR /&gt;&lt;BR /&gt;When entering the CLI and trying to activate the cluster service I get the following message:&lt;BR /&gt;&lt;BR /&gt;% Unable to change the cluster state back to service. Reason: Only Network Partition State can change to In Service State!.&lt;BR /&gt;&lt;BR /&gt;Thanks...</description>
      <pubDate>Sat, 20 May 2017 16:44:39 GMT</pubDate>
      <guid>https://community.ruckuswireless.com/t5/To-Be-Moved/cluster-out-of-service/m-p/6957#M311</guid>
      <dc:creator>ivan_gonzalez_g</dc:creator>
      <dc:date>2017-05-20T16:44:39Z</dc:date>
    </item>
    <item>
      <title>Re: cluster out of service</title>
      <link>https://community.ruckuswireless.com/t5/To-Be-Moved/cluster-out-of-service/m-p/6958#M312</link>
      <description>We assigned more memory to our VM and got the same error ("Cluster Out of Service") after the reboot.&lt;BR /&gt;Now we can't upgrade our controller. Please advise.</description>
      <pubDate>Fri, 09 Jun 2017 11:19:45 GMT</pubDate>
      <guid>https://community.ruckuswireless.com/t5/To-Be-Moved/cluster-out-of-service/m-p/6958#M312</guid>
      <dc:creator>daniel_svanberg</dc:creator>
      <dc:date>2017-06-09T11:19:45Z</dc:date>
    </item>
    <item>
      <title>Re: cluster out of service</title>
      <link>https://community.ruckuswireless.com/t5/To-Be-Moved/cluster-out-of-service/m-p/6959#M313</link>
      <description>Hello,
&lt;BR /&gt;One of the solutions that ruckus provided us is to put a patch and establish the resource conditions that the controller needs. The other solution is to create the virtual controller again with the features you need.
&lt;BR /&gt;&lt;BR /&gt;Contact ruckus support to help you with a support session.&lt;BR /&gt;&lt;BR /&gt;Regards..</description>
      <pubDate>Fri, 09 Jun 2017 13:24:53 GMT</pubDate>
      <guid>https://community.ruckuswireless.com/t5/To-Be-Moved/cluster-out-of-service/m-p/6959#M313</guid>
      <dc:creator>ivan_gonzalez_g</dc:creator>
      <dc:date>2017-06-09T13:24:53Z</dc:date>
    </item>
    <item>
      <title>Re: cluster out of service</title>
      <link>https://community.ruckuswireless.com/t5/To-Be-Moved/cluster-out-of-service/m-p/6960#M314</link>
      <description>There was need for a patch with SZ 3.2 and earlier releases, that Dimitri mentions.&lt;BR /&gt;Check with Tech Support might be advisable.</description>
      <pubDate>Mon, 12 Jun 2017 21:08:50 GMT</pubDate>
      <guid>https://community.ruckuswireless.com/t5/To-Be-Moved/cluster-out-of-service/m-p/6960#M314</guid>
      <dc:creator>michael_brado</dc:creator>
      <dc:date>2017-06-12T21:08:50Z</dc:date>
    </item>
  </channel>
</rss>

