An administrator is adding a node with a higher AOS release to an existing cluster.
What is the most efficient action an administrator should take to ensure it is in a supported state?
An administrator is adding a node with a higher AOS release to an existing cluster.
What is the most efficient action an administrator should take to ensure it is in a supported state?
To ensure the node is in a supported state when added to an existing cluster, the most efficient action is to add the node to the cluster and leave the existing AOS version in place. The cluster management software will automatically reimage the new node to match the lower AOS version of the existing cluster, ensuring compatibility and integration without manual intervention.
should be C
So Option B ". Add the node to the cluster and leave the existing AOS version in place" is also good as it will automatically reimage. Seems Better than option C
There is no such thing as an automatic reimage. Think about that, software will update without ensuring compatibility with other software found on your cluster? Like AHV? Like HBA firmware.
C is Correct. Alternately, if the AOS version on the node is higher than the cluster, you must either upgrade the cluster to that version or reimage the node. To upgrade your cluster, see the Acropolis Upgrade Guide.
This is the correct answer. The question asked for the easiest...Upgrade the cluster then add the node.
But it is not easier than just adding the node with out doing anything else! It will be automatically reimaged to the current AOS version of the cluster!
That's not correct. It says"However, if the AOS version on the node is higher than the version on the cluster, you can choose to upgrade the cluster to that higher version. If you do not upgrade the cluster to match the node AOS version, the node will be automatically reimaged to match the lower AOS version of the cluster during the expansion process." That means, if you don't upgrade the cluster, just leave the node as it is, and it will be automatically reimaged to the lower version.
I agree with you! B is correct!
C is correct answer. https://portal.nutanix.com/page/documents/details?targetId=Web-Console-Guide-Prism-v5_10:wc-cluster-expand-wc-r.html
"if the AOS version on the node is higher than the version on the cluster, you can choose to upgrade the cluster to that higher version. If you do not upgrade the cluster to match the node AOS version, the node will be automatically reimaged to match the lower AOS version of the cluster during the expansion process."
Configuration Description Same AOS and hypervisor versions - The node is added to the cluster without reimaging it. Same hypervisor version but different AOS version - The node is automatically reimaged before it is added. However, if the AOS version on the node is higher than the version on the cluster, you can upgrade the cluster to the higher version. If you do not upgrade the base cluster to match the node AOS version, the node is reimaged automatically to match the lower AOS version of the cluster. For more information about how to upgrade your cluster, see the Acropolis Upgrade Guide. Same AOS version but different hypervisor version - The node is automatically reimaged before it is added.