Nutanix AHV: UPS without Outlet Groups

Example 1: Turn off the UPS enabled, AFS shutdown enabled, abort active replications enabled, no shutdown command file or SSH action configured.

PowerChute is installed on a physical machine outside the Cluster, configured for a Single/Redundant UPS configuration with several Nutanix Hosts in a Cluster. The option to Turn off the UPS is enabled on the Shutdown Settings page. No shutdown command file or SSH action configured. The durations in this example are as follows:

• VM Shutdown = 120 seconds
• Abort Active Replications Duration = 80 seconds
• AFS Shutdown Duration = 60 seconds
• Cluster Shutdown Duration = 60 seconds
• Controller VM Shutdown Duration = 120 seconds

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 issues a command to turn off the UPS. UPS turnoff starts.
3. PowerChute issues a command on the Nutanix Controller VMs to shut down User VMs.
4. After 120 seconds (VM Shutdown Duration), PowerChute shuts down Acropolis File Services and the AFS VMs.
5. After 60 seconds (AFS Shutdown Duration), PowerChute aborts any ongoing VM replications.
6. After 80 seconds (Abort Active Replications Duration), PowerChute shuts down the Nutanix Cluster.
7. After 60 seconds (Cluster Shutdown Duration), PowerChute issues a command to shut down the Controller VMs.
8. After 120 seconds (Controller VM Shutdown Duration), PowerChute issues commands to shut down the Nutanix Hosts.
9. After a 70 second delay, the operating system on the physical machine running PowerChute starts to shut down.
10. 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 Configuration - Shutdown page in the NMC interface.

11. After this delay, a further non-configurable two minute delay is counted down.
12. The UPS will then turn off after the user-configurable Shutdown Delay time has elapsed.
    This is configurable on the Configuration - 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 10) starts to count down.

Example 2: Turn off the UPS enabled, shutdown command file configured.

PowerChute is installed on a physical machine outside the Cluster, configured for a Single/Redundant UPS configuration with several Nutanix Hosts in a Cluster. The option to Turn off the UPS is enabled on the Shutdown Settings page. A shutdown command file is configured. The durations in this example are as follows:

• VM Shutdown Duration = 120 seconds
• Abort Active Replications Duration = 80 seconds
• AFS Shutdown Duration = 60 seconds
• Cluster Shutdown Duration = 60 seconds
• Controller VM Shutdown Duration = 120 seconds

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 issues a command to turn off the UPS. UPS turnoff starts.
3. PowerChute issues a command on the Nutanix Controller VMs to shut down User VMs.
4. After 120 seconds (VM Shutdown Duration), PowerChute shuts down Acropolis File Services and the AFS VMs.
5. After 60 seconds (AFS Shutdown Durations), PowerChute aborts any ongoing VM replications.
6. After 80 seconds (Abort Active Replications Duration), PowerChute shuts down the Nutanix Cluster.
7. After 60 seconds (Cluster Shutdown Duration), PowerChute issues a command to shut down the Controller VMs.
8. After 120 seconds (Controller VM Shutdown Duration), PowerChute starts to execute the shutdown command file.
9. After the delay configured for the command file has elapsed, PowerChute issues commands to shut down the Nutanix Hosts.
10. After a 70 second delay, the operating system on the physical machine running PowerChute starts to shut down.
11. 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 Configuration - Shutdown page in the NMC interface.

12. After this delay, a further non-configurable two minute delay is counted down.
13. The UPS will then turn off after the user-configurable Shutdown Delay time has elapsed.
    This is configurable on the Configuration - 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 11) starts to count down.

Example 3: Turn off the UPS enabled, shutdown command file configured, Execute Command File after Host Shutdown enabled.

PowerChute is installed on a physical machine outside the Cluster, configured for a Single/Redundant UPS configuration with several Nutanix Hosts in a Cluster. The option to Turn off the UPS is enabled on the Shutdown Settings page. A shutdown command file is configured. Execute Command File after Host Shutdown is enabled, with a delay of 30 seconds applied. The durations in this example are as follows:

• VM Shutdown Duration = 120 seconds
•  Abort Active Replications Duration = 80 seconds
• AFS Shutdown Duration = 60 seconds
• Cluster Shutdown Duration = 60 seconds
• Controller VM Shutdown Duration = 120 seconds

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 issues a command to turn off the UPS. UPS turnoff starts.
3. PowerChute issues a command on the Nutanix Controller VMs to shut down User VMs.
4. After 120 seconds (VM Shutdown Delay), PowerChute shuts down Acropolis File Services and the AFS VMs.
5. After 60 seconds (AFS Shutdown Delay), PowerChute aborts any ongoing VM replications.
6. After 80 seconds (Abort Active Replications Duration), PowerChute shuts down the Nutanix Cluster.
7. After 60 seconds (Cluster Shutdown Delay), PowerChute issues a command to shut down the Controller VMs.
8. After 120 seconds (Controller VM Shutdown Delay), PowerChute issues a command to shut down the Nutanix Hosts,
9. Following the 30 second delay configured for the Execute Command File after Host Shutdown option, PowerChute starts to execute the shutdown command file.
10. After the duration configured for the shutdown command file has elapsed, the OS Shutdown Command is issued and an additional 70 second delay is counted down before the operating system on the physical machine running PowerChute starts to shut down.
11. 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 Configuration - Shutdown page in the NMC interface.

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