You must start up the system components of the system in a strict order to avoid data loss and faults in the components.

Prerequisites

  • Verify that you have direct console access to the switches and ESXi hosts in the system.
  • Verify that you have the host names and IP addresses of the ESXi hosts that are members of the management domain.

    You can obtain this information in the Domain Details pages in the SDDC Manager Dashboard.

  • Verify that you have the host names and IP addresses of the ESXi hosts that are members of each VI workload domain.

    You can obtain this information in the Domain Details pages in the SDDC Manager Dashboard.

  • See Knowledge Base article 2142676 Shutting down and powering on a vSAN 6.x Cluster when vCenter Server is running on top of vSAN for information about starting up hosts and exiting maintenance mode.

Procedure

  1. Power on each ESXi host in the management domain, and exit maintenance mode.
    1. Use SSH to connect and log in to the ESXi console.
    2. Use the following CLI command to exit maintenance mode. 
      # esxcli system maintenanceMode set -e false
    3. Perform the above steps on each ESXi host until none are in maintenance mode.
  2. Power on each ESXi host in the first VI workload domain, and exit maintenance mode.
    1. Use SSH to connect and log in to the ESXi console.
    2. Use the following CLI command to exit maintenance mode. 
      # esxcli system maintenanceMode set -e false
    3. Perform the above steps on each ESXi host until none are in maintenance mode.
    4. Repeat the above steps for each VI workload domain.
  3. Power on the infrastructure management VMs in the management domain.
    Important: You must power on the VMs using the ESXi host client on each management ESXi host.
    Important: You must wait until each VM is powered on and all it services started before powering on the next VM.
    Power on the VMs in the following order:
    • Platform Services Controller virtual appliances.
    • vCenter Server for the management domain.
    • VxRail Manager.
    • SDDC Manager VM.
    • NSX Manager virtual appliance for the management domain.
    • NSX Controller cluster virtual appliances for the management domain.
    • NSX Edge Service Gateway virtual appliances.
    • vCenter Server for each VI workload domain.
    • NSX Manager virtual appliance for each VI workload domain.
  4. Log in to the SDDC Manager Dashboard to verify that it displays correctly.
    1. On the SDDC Manager Dashboard, navigate to the management domain.
    2. In the domain details panel, click the launch for the vCenter Server instance.
      A new browser tab opens and displays the vSphere Web Client.
  5. Power on the vRealize Automation virtual appliance and IaaS components in the management domain.
    Important: You must wait until each VM or virtual appliance is powered on and all of its services started before running on the next VM.
    Power on the VMs in the following order:
    • The vRealize Automation IaaS SQL Server VM.
    • All vRealize Automation virtual appliances.
    • All vRealize Automation IaaS Web Server VMs.
      Note:

      Power on the primary IaaS Web Server VM first.

    • All vRealize Automation IaaS Manager Services.
      Note:

      Power on the primary IaaS Manager Server VM first.

    • All vRealize Automation IaaS proxy agents.
    • All vRealize Automation IaaS Distributed Execution Management (DEM) hosts.
  6. Power on the vRealize Operations Manager virtual appliances in the management domain.
    Important: You must wait until each VM or virtual appliance is powered on and all of its services running before powering on the next VM.
    Power on the VMs in the following order:
    • The vRealize Operations Manager primary node.
    • The vRealize Operations Manager primary replica node.
    • All vRealize Operations Manager data nodes.
    • All vRealize Operations Manager remote collector nodes.
  7. Power on the vRealize Log Insight virtual appliances in the management domain.
    Important: You must wait until each VM or virtual appliance is powered on and all of its services running before powering on the next VM.
    Power on the VMs in the following order:
    • The vRealize Log Insight primary node.
    • All vRealize Log Insight worker nodes.
  8. Power on the vRealize Suite Lifecycle Manager appliance in the management domain.
  9. Power on the VMs in the first VI workload domain.
    Important: Each workload domain includes a three-node NSX Controller cluster. Power on these VMs first.
    1. On the SDDC Manager Dashboard, navigate to the management domain.
    2. In the domain details panel, click the launch for the vCenter Server instance.
      A new browser tab opens and displays the vSphere Web Client.
    3. In the vSphere Web Client, power on the VMs in the following order:
      • VxRail Manager.
      • The three-node NSX Controller cluster.
      • The workload domain VMs.
    4. Repeat this procedure on each VI workload domain.
  10. Power on the VMs in the Horizon domains (if any).
    1. On the SDDC Manager Dashboard, navigate to the first Horizon domain.
    2. In the domain details panel, launch the vCenter Server instance.
      A new browser tab opens and displays the vSphere Web Client.
    3. In the vSphere Web Client, power on the Horizon domain VMs.
    4. Repeat this procedure on each Horizon domain.
  11. Using SSH, log in to the SDDC Manager VM as vcf.
  12. Run the following command: 
    sudo /opt/vmware/sddc-support/sos --health-check
  13. When prompted, enter the vcf user password.
    Verify that everything works correctly.