Using the Shutdown Duration field, you must allow sufficient time for all your Controller VMs to gracefully shut down before the hosts are commanded to shut down.
A Controller Virtual Machine is installed on each HyperFlex node in a cluster and is responsible for managing the HyperFlex cluster storage.
Controller VM Shutdown is enabled by default. In the PowerChute shutdown sequence, the Controller VM is shut down after all other VMs in the Cluster, and the HyperFlex Cluster itself are shut down.
The Duration field is the time allowed for all the Controller VMs to gracefully shut down. If the Controller VMs are shut down before the Duration time, PowerChute waits until this time has elapsed before proceeding to the next step in the sequence.
|
Using the Shutdown Duration field, you must allow sufficient time for all your Controller VMs to gracefully shut down before the hosts are commanded to shut down. |
Controller VM Shutdown/Startup
If the Skip Maintenance Mode checkbox is selected in PowerChute, the Controller VMs will get started automatically using the VMware VM Shutdown/Startup configuration for each host. PowerChute will not start the Controller VMs, but PowerChute will still wait the configured Controller VM Startup Duration before proceeding with User VM startup
If PowerChute is deployed as a VM and VMware HA is disabled for the cluster, the PowerChute VM should be configured to start after the Controller VMs using the VM Shutdown/Startup option in vSphere.
|
It is recommended to wait at least 5 minutes after Controller VM startup to ensure all services are running before re-starting the Cluster. You should account for this using the Controller VM Startup Duration field. |