Restarting an ESXi 7.x, ESXi 8.x, and ESX 9.x via the vCenter web client
- Right-click the ESX Server in the Inventory and click Enter Maintenance Mode.
- If hosts are part of vSAN or NSX
- This migrates all powered-on virtual machines to another host in the cluster.
- When complete, right-click on the ESX Server host in the Inventory and select Reboot.
- Enter a reason in the reboot server window.
- Click OK.
- Wait for the ESX Server host to restart.
Note: If performing the task within vCenter, the host enters a Not Responding state until it has completely rebooted and its agents have started. This is expected behavior.
- Right-click the ESXi Server host in the Inventory and click Exit Maintenance Mode. This brings the host back into production.
Restarting an ESXi 7.x, 8.x, and ESX 9.x hosts from the DCUI.
Ensure that all virtual machines are powered off or migrated to another host.
- If hosts are part of vSAN or NSX
Access the host console directly, or connect via the System Management Interface.
Press F12.
Enter the root user name and password when prompted.
- Press F11 to restart the system.
Restarting an ESXi 7.x, 8.x, and ESX 9.x hosts from the SSH.
- Connect to the server using an SSH client with the command
ssh root@<host_ip_fqdn>. - Ensure the host is ready for a restart and prevent new VMs from starting by enabling maintenance mode with the command
vim-cmd hostsvc/maintenance_mode_enter.- If hosts are part of vSAN or NSX
- Trigger the system reboot using the graceful shutdown command
esxcli system shutdown reboot -d 10 -r "Maintenance", or just run reboot for a standard restart. - Once the server is back online, log in again and disable maintenance mode to resume normal operations using the command
vim-cmd hostsvc/maintenance_mode_exit.
Restarting an ESXi 7.x, 8.x, and ESX 9.x hosts from PowerCLI.
- Install the VCF PowerCLI module
- Set the execution policy to allow scripts to run if necessary, with
set-executionpolicy remotesigned. - Initiate a connection to the ESXi host or the vCenter server using
connect-viserver -server <vCenter_FQDN_IP_Address>. - Provide administrative credentials when prompted by the login window.
- Place the ESXi host into maintenance mode to safely evacuate or power off running virtual machines using
set-vmhost -vmhost <ESXI_Fqdn> -state maintenance.- If hosts are part of vSAN or NSX
- Execute the reboot command by running
restart-vmhost -vmhost <ESXI_Fqdn> -confirm:$false. - Monitor host status using get-vmhost until it shows status as powered on and is reachable again.
- Exit maintenance mode once the server is back online to resume normal operations with
set-vmhost -vmhost <ESXI_Fqdn> -state connected.
Restarting ESXi 7.x or 8.x or ESX 9.x hosts from the host webclient.
- Log in to the ESXi Host Client web interface
- Right-click Host in the left navigation pane and select Enter maintenance mode.
- If hosts are part of vSAN or NSX
- Once in maintenance mode, right-click Host in the navigation pane again.
- Select Reboot from the dropdown menu.
- Click Reboot in the confirmation pop-up window to execute the restart.
- The browser session will disconnect immediately; wait for the hardware to cycle and the services to come back online.
For hosts running ESXi 7.x, ESXi 8.x, or ESX 9.x, reboots are possible from an SSH session to the host by typing the command reboot from the command line.
- VSAN: Enter Maintenance Mode
The most common procedure is to initiate maintenance mode through the vSphere Client. This triggers the evacuation of virtual machines and handles vSAN data based on your selection.
- In the vSphere Client, navigate to Inventory > Hosts and Clusters.
- Right-click the target ESXi host and select Maintenance Mode > Enter Maintenance Mode.
- Crucial Step: Select vSAN Data Migration Mode. You will be prompted to choose one of the following:
- Ensure Accessibility (Default): vSAN ensures that all virtual machines on this host remain accessible, but it does not move all data. If another host fails while this host is in maintenance, data loss could occur.
- Full Data Evacuation: All data is moved from the host to other hosts in the cluster. This is the safest option but takes the longest. Use this if you expect the host to be offline for an extended period or if you are decommissioning it.
- No Data Evacuation: No data is moved. VMs that have objects only on this host will become unavailable.
For hosts functioning as NSX Transport Nodes, it is often a best practice (or mandatory for certain upgrades/tasks) to also place the node in NSX Maintenance Mode via the NSX Manager.
- Log in to the NSX Manager UI.
- Navigate to System > Fabric > Nodes > Host Transport Nodes.
- Select the ESXi host, click Actions, and select Enter NSX Maintenance Mode.