Hyper-V: UPS without Outlet Groups

The time taken to suspend the Cluster node is not configurable and may vary depending on your environment. This delay can be incorporated into the VM Migration or VM Shutdown duration.

Example 1: Hyper-V Failover Cluster, Turn off the UPS enabled, stop cluster enabled, no shutdown command file configured.

PowerChute is installed on one of the nodes in a Hyper-V Failover Cluster. The option to Turn off the UPS is enabled on the Shutdown settings page. The option to stop the Cluster is enabled in the Virtualization Settings page. No shutdown command file is configured.  VM migration and VM shutdown are enabled with a 120 second delay configured for each.

When a critical UPS event, such as On Battery occurs, the following sequence is triggered.

1. PowerChute reports that the UPS is on battery.
2. After the shutdown delay configured for the On Battery event has elapsed, PowerChute sends a command to turn off the UPS. UPS turn off starts.
3. PowerChute suspends the Cluster node and starts to migrate VMs and then shut down any VMs that cannot be migrated.
4. After 4 minutes (VM migration delay = 120, VM shutdown delay = 120), PowerChute stops the cluster.
5. After 2 minutes (stop cluster duration = 120), PowerChute starts the operating system shutdown sequence.
6. After a 70-second delay the operating system starts to shut down.
7. The UPS will wait the amount of time indicated by one of the following, whichever is greater:
   
   Low Battery Duration or Maximum Required Delay.
   These are shown on the UPS Shutdown page in the NMC user interface.
8. After this delay, a further non-configurable two minute delay is counted down.
9. The UPS will then turn off after the user-configurable Shutdown Delay time has elapsed.
   This is configurable on the UPS Shutdown page in the NMC user interface.

It is recommended that the Low Battery Duration is configured to allow enough time for the operating system shutdown to complete. Ideally, the operating system should have shut down before the non-configurable two minute delay (step 8) starts to count down.

Example 2: Hyper-V Failover Cluster, Turn off the UPS enabled, shutdown command file configured.

PowerChute is installed on one of the nodes in a Hyper-V Failover Cluster. The option to Turn off the UPS is enabled on the Shutdown settings page. A shutdown command file is configured. VM migration and VM shutdown are enabled with a 120 second delay configured for each.

When a critical UPS event, such as On Battery occurs, the following sequence is triggered.

1. PowerChute reports that the UPS is on battery. 
2. After the shutdown delay configured for the On Battery event has elapsed, PowerChute sends a command to turn off the UPS. UPS turn off starts.
3. PowerChute suspends the Cluster node and starts to migrate VMs and then shut down any VMs that cannot be migrated.
4. After 4 minutes (VM migration delay = 120, VM shutdown delay = 120), PowerChute executes the shutdown command file.
5. After the duration configured for the shutdown command file has elapsed, PowerChute resumes the cluster node and starts the operating system shutdown sequence.
6. An additional 70 second delay is counted down before the operating system starts to shut down.
7. The UPS will wait the amount of time indicated by one of the following, whichever is greater:
   

   Low Battery Duration or Maximum Required Delay.
   These are shown on the UPS Shutdown page in the NMC user interface.

8. After this delay, a further non-configurable two minute delay is counted down.
9. The UPS will then turn off after the user-configurable Shutdown Delay time has elapsed (this is configurable on the UPS Shutdown page in the NMC user interface).

It is recommended that the Low Battery Duration is configured to allow enough time for the shutdown command file and operating system shutdown to complete. Ideally, the operating system should have shut down before the two minute delay (step 8) starts to count down.