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 runs on each node in a Nutanix block and is responsible for running the Nutanix Cluster. 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 Nutanix 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
Selecting the Controller VM Startup checkbox re-starts any Controller VMs that were shut down when a UPS critical event has been resolved and the Nutanix Hosts are powered on. PowerChute first checks that the host is available.
If Controller VMs are in the process of being started when a critical event occurs, PowerChute waits for the Startup Duration time to elapse before shutting down Controller VMs. This is to ensure that the Controller VMs are shut down gracefully.
|
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 Startup Duration field. |