<?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 Error on checking node resource plan. The cluster requires all resource plan to be the same. in RUCKUS Self-Help</title>
    <link>https://community.ruckuswireless.com/t5/RUCKUS-Self-Help/Error-on-checking-node-resource-plan-The-cluster-requires-all/m-p/80262#M361</link>
    <description>&lt;P&gt;&lt;STRONG&gt;Issue&lt;/STRONG&gt; - On joining a new RUCKUS Virtual SmartZone (vSZ) node to an existing vSZ Cluster, we are getting the error "Error on checking node resource plan. The cluster requires all resource plan to be the same."&lt;/P&gt;&lt;P&gt;&lt;span class="lia-inline-image-display-wrapper lia-image-align-inline" image-alt="Dilshad_Zafar_0-1716590711542.png" style="width: 999px;"&gt;&lt;img src="https://community.ruckuswireless.com/t5/image/serverpage/image-id/11627i38D44A8F6EB400B4/image-size/large/is-moderation-mode/true?v=v2&amp;amp;px=999" role="button" title="Dilshad_Zafar_0-1716590711542.png" alt="Dilshad_Zafar_0-1716590711542.png" /&gt;&lt;/span&gt;&lt;/P&gt;&lt;P class="lia-align-center"&gt;&lt;FONT size="1 2 3 4 5 6 7"&gt;Fig 1 - Node join validation error&lt;/FONT&gt;&lt;/P&gt;&lt;P&gt;&lt;STRONG&gt;Environment&lt;/STRONG&gt; - This example is from a vSZ-E (Essentials) with firmware 6.1.2 and running on VMWare ESXi Hypervisor. However, it is also applicable to vSZ-H (High-Scale) running any firmware version and deployed on any supported Hypervisor platform.&lt;/P&gt;&lt;P&gt;&lt;STRONG&gt;Resolution and Explanation&lt;/STRONG&gt; - Make sure that VM Resource level of all the nodes of a vSZ cluster are the same. The Resource level matrix can be found on the respective firmware version's Upgrade Guides. For instance, vSZ-E 6.1.2 version has 1, 1.5, 2&amp;nbsp; and 3 as the Resource Levels that is dependent on the RAM, Disk size and vCPU per node :-&lt;/P&gt;&lt;P class="lia-align-center"&gt;&lt;span class="lia-inline-image-display-wrapper lia-image-align-inline" image-alt="Dilshad_Zafar_1-1716588621828.png" style="width: 999px;"&gt;&lt;img src="https://community.ruckuswireless.com/t5/image/serverpage/image-id/11625iB82C5928463F821E/image-size/large/is-moderation-mode/true?v=v2&amp;amp;px=999" role="button" title="Dilshad_Zafar_1-1716588621828.png" alt="Dilshad_Zafar_1-1716588621828.png" /&gt;&lt;/span&gt;&lt;FONT size="1 2 3 4 5 6 7"&gt;Fig 2 - Resource Level Matrix of vSZ-E&lt;/FONT&gt;&lt;/P&gt;&lt;P&gt;In this case, it was found that the vSZ node trying to join the Cluster had 21 GB of RAM allocated which brought it to &lt;STRONG&gt;Resource Level 3&lt;/STRONG&gt;, while the existing Cluster Node had only14 GB of RAM allocated which means it was running on &lt;STRONG&gt;Resource Level 1.&amp;nbsp;&lt;/STRONG&gt;Therefore, a node with Resource Level 1 could not join a Cluster on Resource Level 4.&amp;nbsp;&lt;/P&gt;&lt;P class="lia-align-center"&gt;&lt;span class="lia-inline-image-display-wrapper lia-image-align-inline" image-alt="Dilshad_Zafar_2-1716589227296.png" style="width: 999px;"&gt;&lt;img src="https://community.ruckuswireless.com/t5/image/serverpage/image-id/11626iF1DE1264AC43D04A/image-size/large/is-moderation-mode/true?v=v2&amp;amp;px=999" role="button" title="Dilshad_Zafar_2-1716589227296.png" alt="Dilshad_Zafar_2-1716589227296.png" /&gt;&lt;/span&gt;&lt;FONT size="1 2 3 4 5 6 7"&gt;Fig 3 - RAM allocation to vSZ node&lt;/FONT&gt;&lt;/P&gt;&lt;P&gt;After shutting down the instance and lowering the Memory to match the resource level of Cluster, the new vSZ node joined without any issue.&lt;/P&gt;&lt;P&gt;Regards,&lt;/P&gt;</description>
    <pubDate>Fri, 24 May 2024 22:46:02 GMT</pubDate>
    <dc:creator>Dilshad_Zafar</dc:creator>
    <dc:date>2024-05-24T22:46:02Z</dc:date>
    <item>
      <title>Error on checking node resource plan. The cluster requires all resource plan to be the same.</title>
      <link>https://community.ruckuswireless.com/t5/RUCKUS-Self-Help/Error-on-checking-node-resource-plan-The-cluster-requires-all/m-p/80262#M361</link>
      <description>&lt;P&gt;&lt;STRONG&gt;Issue&lt;/STRONG&gt; - On joining a new RUCKUS Virtual SmartZone (vSZ) node to an existing vSZ Cluster, we are getting the error "Error on checking node resource plan. The cluster requires all resource plan to be the same."&lt;/P&gt;&lt;P&gt;&lt;span class="lia-inline-image-display-wrapper lia-image-align-inline" image-alt="Dilshad_Zafar_0-1716590711542.png" style="width: 999px;"&gt;&lt;img src="https://community.ruckuswireless.com/t5/image/serverpage/image-id/11627i38D44A8F6EB400B4/image-size/large/is-moderation-mode/true?v=v2&amp;amp;px=999" role="button" title="Dilshad_Zafar_0-1716590711542.png" alt="Dilshad_Zafar_0-1716590711542.png" /&gt;&lt;/span&gt;&lt;/P&gt;&lt;P class="lia-align-center"&gt;&lt;FONT size="1 2 3 4 5 6 7"&gt;Fig 1 - Node join validation error&lt;/FONT&gt;&lt;/P&gt;&lt;P&gt;&lt;STRONG&gt;Environment&lt;/STRONG&gt; - This example is from a vSZ-E (Essentials) with firmware 6.1.2 and running on VMWare ESXi Hypervisor. However, it is also applicable to vSZ-H (High-Scale) running any firmware version and deployed on any supported Hypervisor platform.&lt;/P&gt;&lt;P&gt;&lt;STRONG&gt;Resolution and Explanation&lt;/STRONG&gt; - Make sure that VM Resource level of all the nodes of a vSZ cluster are the same. The Resource level matrix can be found on the respective firmware version's Upgrade Guides. For instance, vSZ-E 6.1.2 version has 1, 1.5, 2&amp;nbsp; and 3 as the Resource Levels that is dependent on the RAM, Disk size and vCPU per node :-&lt;/P&gt;&lt;P class="lia-align-center"&gt;&lt;span class="lia-inline-image-display-wrapper lia-image-align-inline" image-alt="Dilshad_Zafar_1-1716588621828.png" style="width: 999px;"&gt;&lt;img src="https://community.ruckuswireless.com/t5/image/serverpage/image-id/11625iB82C5928463F821E/image-size/large/is-moderation-mode/true?v=v2&amp;amp;px=999" role="button" title="Dilshad_Zafar_1-1716588621828.png" alt="Dilshad_Zafar_1-1716588621828.png" /&gt;&lt;/span&gt;&lt;FONT size="1 2 3 4 5 6 7"&gt;Fig 2 - Resource Level Matrix of vSZ-E&lt;/FONT&gt;&lt;/P&gt;&lt;P&gt;In this case, it was found that the vSZ node trying to join the Cluster had 21 GB of RAM allocated which brought it to &lt;STRONG&gt;Resource Level 3&lt;/STRONG&gt;, while the existing Cluster Node had only14 GB of RAM allocated which means it was running on &lt;STRONG&gt;Resource Level 1.&amp;nbsp;&lt;/STRONG&gt;Therefore, a node with Resource Level 1 could not join a Cluster on Resource Level 4.&amp;nbsp;&lt;/P&gt;&lt;P class="lia-align-center"&gt;&lt;span class="lia-inline-image-display-wrapper lia-image-align-inline" image-alt="Dilshad_Zafar_2-1716589227296.png" style="width: 999px;"&gt;&lt;img src="https://community.ruckuswireless.com/t5/image/serverpage/image-id/11626iF1DE1264AC43D04A/image-size/large/is-moderation-mode/true?v=v2&amp;amp;px=999" role="button" title="Dilshad_Zafar_2-1716589227296.png" alt="Dilshad_Zafar_2-1716589227296.png" /&gt;&lt;/span&gt;&lt;FONT size="1 2 3 4 5 6 7"&gt;Fig 3 - RAM allocation to vSZ node&lt;/FONT&gt;&lt;/P&gt;&lt;P&gt;After shutting down the instance and lowering the Memory to match the resource level of Cluster, the new vSZ node joined without any issue.&lt;/P&gt;&lt;P&gt;Regards,&lt;/P&gt;</description>
      <pubDate>Fri, 24 May 2024 22:46:02 GMT</pubDate>
      <guid>https://community.ruckuswireless.com/t5/RUCKUS-Self-Help/Error-on-checking-node-resource-plan-The-cluster-requires-all/m-p/80262#M361</guid>
      <dc:creator>Dilshad_Zafar</dc:creator>
      <dc:date>2024-05-24T22:46:02Z</dc:date>
    </item>
  </channel>
</rss>

