Cluster Expansion Guidelines
-
If you have replication configured, put replication in pause mode before performing upgrade, expansion or cluster maintenance. After the upgrade, expansion or cluster maintenance is completed, then resume replication. Perform the pause and resume on any cluster that has replication configured to or from this local cluster.
-
If you are using RESTful APIs to perform cluster expansion, sometimes the task may take longer than expected.
-
ESXi installation is supported on SD cards for M4 converged nodes and M.2 SATA SSD for M5 converged nodes. For compute-only nodes, ESXi installation is supported for SD Cards, SAN boot, or front SSD/HDD. Installing ESXi on USB Flash is not supported for compute-only nodes
Note
HW RAID M.2 (UCS-M2-HWRAID and HX-M2-HWRAID) is not supported on Compute-only nodes.
-
You must click on the discovered cluster to proceed with expanding a standard ESX cluster in a 3.5.x or earlier release. Not doing so results in errors.
-
Use only Admin credentials for the Controller VM during expansion work flow. Using any other credentials other than Admin may cause the expansion to fail.
ESXi Installation Guidelines
-
Modify boot policy for compute node.
To modify the template and boot policy for HyperFlex Stretched Cluster compute only node on M5 server:
-
Clone the template.
-
Uncheck the Flex flash from local boot policy, if the compute M5 node does not have flash cards.
-
Add the SAN boot with proper WWPN to the boot order.
-
-
Start the DPI expansion workflow.
-
When prompted, install ESXi using an ISO image.
-
Return to the DPI expansion workflow and complete the ESXi installation workflow.
Note |
If the Hypervisor configuration fails with the SOL logging failure message, access the installer CLI through SSH with root and default password and configure the ESXi hypervisor. Then, run the advanced installer and check the HX Storage Software and Expand Cluster check boxes to proceed with the ESXi installation process. |