You must shut down the system components 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.

  • Coordinate the shutdown in advance with business stakeholders to minimize any impact.

  • Verify that no VMs are running on snapshots.

  • Verify that you have saved the account passwords to a location external from the Cloud Foundation system you are shutting down. See Look Up Account Credentials.

  • Verify that valid backups of all management VMs, tenant VMs, and switch configurations are available and saved to a location external from the Cloud Foundation system you are shutting down. See Backing up and Restoring a Cloud Foundation System.

  • If a data protection solution is running on any of the domains, verify that it is properly shut down per vendor instructions.

  • 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 verifying the state of the vSAN cluster before a shutdown.

Procedure

  1. Before starting the shutdown procedure, note down the following information:
    • The hostname and IP address of the ESXI hosts that are members of the management domain. To see the hosts in the management domain, navigate to the Domain Details page in the SDDC Manager Dashboard.

    • The hostname and IP address of the ESXI hosts that are members of each workload domain. To see the hosts in the VI workload domains, for each domain navigate to the Domain Details page in the SDDC Manager Dashboard.

  2. Shut down the workload VMs in each VI workload domain.
    1. On the SDDC Manager Dashboard, navigate to the workload domain.
    2. Click the launch link (Launch link icon that indicates a link in the EVO SDDC Manager UI launches another web UI) for the vCenter Server instance that is displayed in the domain details window for that workload domain.

      A new browser tab opens and displays the vSphere Web Client.

    3. Locate the VMs for that workload domain.
    4. Shut down these VMs.
      Note:

      Each workload domain includes a three-node NSX Controller cluster. Shut down these VMs last.

    5. Perform the above steps for each VI workload domain.
  3. Place the hosts for each workload domain in maintenance mode.

    You must use the ESXCLI command, which supports setting the vSAN mode when entering maintenance mode.

    1. For each ESXi host, connect and log in to the ESXi console using SSH.
    2. Place each host into maintenance mode using the following command, with the noAction option included.
      esxcli system maintenanceMode set -e true -m noAction
    3. After a few minutes, confirm each host is in maintenance mode by repeating the command.
      esxcli system maintenanceMode set -e true -m noAction

      It should return the following:

      Maintenance mode is already enabled.
    4. Shut down all the ESXi hosts in the VI workload domain.
      # poweroff
    5. Repeat the above steps for each VI workload domain.
  4. Shut down the vRealize Log Insight virtual appliances in the management domain in the following order:
    Important:

    Verify that the console of each virtual appliance and its services are fully shut down before proceeding to the next step.

    • All vRealize Log Insight Worker nodes.

    • The vRealize Log Insight Master node.

  5. Shut down the vRealize Operations Manager virtual appliances in the management domain in the following order:
    Important:

    Verify that the console of each virtual appliance and its services are fully shut down before proceeding to the next step.

    • All vRealize Operations Manager Remote Collector nodes.

    • All vRealize Operations Manager Data nodes.

    • The vRealize Operations Manager Replica node.

    • The vRealize Operations Manager Master node.

  6. Shut down the vRealize Automation virtual appliance and IaaS components in the management domain in the following order:
    Important:

    Verify that the console of each virtual appliance or VM and its services are fully shut down before proceeding to the next step.

    • All vRealize Automation IaaS Distributed Execution Management (DEM) VMs.

    • All vRealize Automation IaaS Proxy Agent VMs.

    • All vRealize Automation IaaS Manager Server VMs.

      Note:

      Shut down the secondary IaaS Manager Server VM first; shut down the primary IaaS Manager Server VM second.

    • All vRealize Automation IaaS Web Server VMs.

      Note:

      Shut down the secondary IaaS Web Server VM first; shut down the primary IaaS Web Server VM second.

    • All vRealize Automation virtual appliances.

    • The vRealize Automation IaaS SQL Server VM.

  7. Shut down the infrastructure management virtual appliances in the management domain in the following sequence.
    1. Shut down the following virtual appliances using the SSH console, verifying that the console of each virtual appliance and its services are fully shut down before proceeding to the next step.
      • All NSX Edge Service Gateway virtual appliances.

      • The NSX Manager virtual appliances for the VI workload domains.

      • The NSX Manager virtual appliance for the management domain.

      • All NSX Controller cluster virtual appliances for the management domain.

    2. Shut down the remaining virtual appliances or VMs from their hosts in the ESXi Host Client on each management ESXi host.
      • The vCenter Server virtual appliance for the VI workload domains.

      • The vCenter Server virtual appliance for the management domain.

      • The Platform Services Controller virtual appliances.

      • SDDC Manager Utility VM.

      • SDDC Manager Controller VM.

  8. Place the management domain ESXi hosts in maintenance mode.
    Important:

    By shutting down the SDDC Manager Controller VM and SDDC Manager Utility VM, you cease operations for the embedded DNS in the Cloud Foundation system. As a result, you must use the IP address of each ESXi host.

    You must use the ESXCLI command that supports setting the vSAN mode when entering maintenance mode.

    1. For each ESXi host, connect and log in to the ESXi console using SSH.
    2. Put each host into maintenance mode using the following command, with the noAction option included.
      # esxcli system maintenanceMode set -e true -m noAction
    3. After a few minutes, confirm each host is in maintenance mode by repeating the command.
      esxcli system maintenanceMode set -e true -m noAction

      It should return the following:

      Maintenance mode is already enabled.
    4. Shut down all the ESXi hosts in the management domain.
      # poweroff
  9. Shut down the unassigned ESXi hosts in the Cloud Foundation system, if any.
    # poweroff
    1. For each unassigned ESXi host, connect and log in to the ESXi console using SSH.
    2. Shut down each unassigned ESXi host.
      # poweroff
  10. Shut down the switches in the following order.
    Important:

    For a management switch, log in first and then shut it down.

    1. ToR switches in each rack.

    2. Inter-rack switches in rack 2.

      Note:

      In some deployments, inter-racks switches may be used for egress (instead of the ToR switches). By shutting down the switch, you may break that connection. It is recommended that you have physical access to the switch to remedy such a break.

    3. Management switches in each rack.