You shut down the components of the management domain in VMware Cloud Foundation in a specific order to keep components operational by maintaining the necessary infrastructure, networking, and management services as long as possible before shutdown.
After you shut down the components in all VI workload domains, you begin shutting down the management domain.
You can shut down the management domain in two ways - by using the user interface in a manner specific to each product, which is the default way, or by running a PowerShell script.
Shutdown Order for the Management Domain
If your VMware Cloud Foundation instance is deployed with the consolidated architecture, shut down any customer workloads or additional virtual machines in the management domain before you proceed with the shutdown order of the management components.
You shut down Site Recovery Manager and vSphere Replication after you shut down the management components that can be failed over between the VMware Cloud Foundation instances. You also shut Site Recovery Manager and vSphere Replication down as late as possible to have the management virtual machines protected as long as possible if a disaster event occurs. The virtual machines in the paired VMware Cloud Foundation instance become unprotected after you shut down Site Recovery Manager and vSphere Replication in the current VMware Cloud Foundation instance.
You shut down vRealize Log Insight as late as possible to collect as much as log data for potential troubleshooting. You shut down the Workspace ONE Access instances after the management components they provide identity and access management services for.
Shutdown Order |
SDDC Component |
---|---|
1 |
|
2 |
vRealize Operations Manager analytics cluster and remote collectors |
3 |
Clustered Workspace ONE® Access™ * |
4 |
VMware vRealize® Suite Lifecycle Manager ™* |
5 |
Site Recovery Manager for the management domain |
6 |
vSphere Replication for the management domain |
7 |
|
8 |
|
9 |
NSX Edge nodes for the management domain * |
10 |
NSX Manager nodes for the management domain * |
11 |
SDDC Manager * |
12 |
vSphere Cluster Services virtual machines in the management domain * |
13 |
vCenter Server for the management domain * |
14 |
Management ESXi hosts and vSAN * |
15 |
|
* For information on the shutdown steps, see this article.
Save the Credentials for the ESXi Hosts and vCenter Server for the Management Domain
Before you shut down the management domain, get the credentials for the management domain hosts and vCenter Server from SDDC Manager and save them. You need these credentials to shut down the ESXi hosts and then to start them and vCenter Server back up. Because SDDC Manager is down during each of these operations, you must save the credentials in advance.
To get the credentials, log in to the SDDC Manager appliance by using a Secure Shell (SSH) client as vcf and run the lookup_passwords command.
Shut Down the Clustered Workspace ONE Access Virtual Machines
Use the vRealize Suite Lifecycle Manager user interface to shut down the Workspace ONE Access three-node cluster that provides identity and access management services to management components that are available across VMware Cloud Foundation instances .
Procedure
- Log in to vRealize Suite Lifecycle Manager at https://<vrealize_suite_lifecycle_manager_fqdn> as vcfadmin@local.
- On the My services page, click Lifecycle operations.
- In the navigation pane, click Environments.
- On the Environments page, on the globalenvironment card, click View details.
- In the VMware Identity Manager section, click the horizontal ellipsis icon and select Power off.
- In the Power off VMware Identity Manager dialog box, click Submit.
- On the Requests page, ensure that the request completes successfully.
Shut Down the vRealize Suite Lifecycle Manager Virtual Machine
Shut down the vRealize Suite Lifecycle Manager virtual machine in the management domain of VMware Cloud Foundation from the vSphere Client.
Procedure
- Log in to the management domain vCenter Server at https://<vcenter_server_fqdn>/ui as [email protected].
- In the VMs and templates inventory, expand the management domain vCenter Server tree and expand the management domain data center.
- Right-click the vRealize Suite Lifecycle Manager virtual machine and select .
- In the confirmation dialog box, click Yes.
Shut Down the NSX Edge Nodes
You begin shutting down the VMware NSX-T™ Data Center infrastructure in the management domain or in a VI workload domain in VMware Cloud Foundation by shutting down the NSX Edge nodes that provide north-south traffic connectivity between the physical data center networks and the NSX SDN networks
Procedure
Shut Down the NSX Manager Nodes
You continue shutting down the NSX-T Data Center infrastructure in the management domain and a VI workload domain by shutting down the three-node NSX Manager cluster by using the vSphere Client.
Procedure
Shut Down the SDDC Manager Virtual Machine
Shut down the SDDC Manager virtual machine in the management domain by using the vSphere Client.
Procedure
Shut Down the vSphere Cluster Services Virtual Machines
To shut down the vSphere Cluster Services (vCLS) virtual machines in a cluster in the management domain or in a VI workload domain in VMware Cloud Foundation, you put the cluster in retreat mode. The retreat mode triggers clean-up of the vCLS virtual machines.
Procedure
Results
The vCLS monitoring service initiates the clean-up of vCLS VMs. If vSphere DRS is enabled for the cluster, it stops working and you see an additional warning in the cluster summary. vSphere DRS remains disabled until vCLS is re-enabled on this cluster.
Shut Down the vCenter Server Instance in the Management Domain
You check the vSAN cluster health and shut down the vCenter Server virtual machine from the first management ESXi host by using the VMware Host Client.
Procedure
Shut Down vSAN and the ESXi Hosts in the Management Domain or for vSphere with Tanzu
You shut down vSAN and the ESXi hosts in the management domain or in a VI workload domain with vSphere with Tanzu by preparing the vSAN cluster for shutdown, placing each ESXi host in maintenance mode to prevent any virtual machines being deployed to or starting up on the host, and shutting down the host.