Replace a host (EVS-deployed)
This page applies to EVS-deployed environments (VCF 5.2.x). For Self-deployed environments that run VCF 9.x, see Manage hosts.
Replace a host when it fails, or before an EC2 system-maintenance or instance-retirement event occurs.
You create the new host with the Amazon Elastic VMware Service console or the AWS CLI, move it into the cluster in SDDC Manager, and then delete the old host.
For when to replace a host, see Host maintenance and retirement events.
Replace a host with local storage before the scheduled event occurs. If EC2 reboots the instance during the event, you lose the vSAN data that’s stored on its instance store volumes.
Don’t use the Amazon EC2 console to stop, start, or terminate Amazon EVS hosts. On hosts with local storage, these actions cause the loss of the vSAN data on the instance store volumes. To create, replace, or delete a host, use the Amazon EVS console, the AWS CLI, or the Amazon EVS API.
Amazon EVS hosts use the Amazon EVS custom vendor add-on to provide important host functionality. A new host has the latest available version of the add-on. If your environment uses hosts with an older add-on version, adding the new host to your vSphere cluster causes cluster image remediation to fail. For the fix, see Troubleshoot hosts.
If you updated your ESX version after deployment, SDDC Manager can fail during VMware Cloud Foundation (VCF) host validation in the commission hosts step. For the fix, see Troubleshoot hosts.
Before you begin
Before you begin, make sure that the following are true.
-
Your Host count per EVS environment quota allows one more host than the environment has. Host creation fails if the quota is lower than the number of hosts in the environment. You might need to request a quota increase for maintenance that requires host replacement. For more information, see Service quotas for Amazon EVS.
-
The A and PTR DNS records for the new host exist. For more information, see Deployment prerequisite checklist.
-
You know the ESX version that your vSphere cluster uses. For more information, see Add a host (VCF 5.x).
Step 1: Create the new host
To create the new host in the Amazon EVS console or with the AWS CLI, use the following steps.
Example
Step 2: Retrieve the ESX root password
-
Retrieve the ESX root password of the new host from AWS Secrets Manager. For more information, see Retrieve VCF credentials and access appliances and Get secrets from AWS Secrets Manager in the AWS Secrets Manager User Guide.
-
Sign in to the VMware Host Client of the new host as
rootwith this password, to confirm that the password works before you commission the host.
Step 3: Move the new host into the cluster
In SDDC Manager
-
Commission the new host, using the ESX root password that you retrieved in the previous step. For more information, see Commission Hosts
in the Broadcom documentation. -
Add the new host to the cluster that contains the host to be replaced. For more information, see How to Add an ESX Host to Your vSphere Cluster by Using the Quickstart Workflow
in the Broadcom documentation. -
Decommission the old host to remove it from SDDC Manager. For more information, see Decommission Hosts
in the Broadcom documentation.
Step 4: Delete the old host
To delete the old host in the Amazon EVS console or with the AWS CLI, use the following steps.
Example
You have replaced the host. To check the environment after the change, see Monitor environment status. If a step fails, see Troubleshoot hosts.