Click an event below for more information.
The events below are non-configurable and relate to virtualization tasks such as VM shutdown.
|
|
Click an event below for more information. |
A critical event has occurred on the UPS powering the Nutanix Cluster and PowerChute is shutting down the User Virtual Machines (UVMs) in the Cluster. This is the first step in the shutdown sequence.
PowerChute was unable to gracefully shut down the Nutanix User Virtual Machines (UVMs). PowerChute will attempt to power off the UVMs.
A critical event has resolved on the UPS powering the Nutanix Cluster and PowerChute is powering on the User Virtual Machines (UVMs) in the Cluster.
PowerChute was unable to gracefully shut down your VMs, power off your VMs, and force them off, on Cluster [Cluster] as insufficient time was configured. Ensure sufficient time is provided in the Duration field in the Virtual Machine Shutdown/Startup screen for all your VMs to gracefully shut down.
A critical event has occurred on the UPS powering the Nutanix Cluster and PowerChute stops the Acropolis File Service which shuts down the AFS VMs in the Cluster. This step occurs after the User VMs are shut down.
PowerChute was unable to stop the Acropolis File Service and shut down the AFS VMs in the Cluster.
A critical event has been resolved and PowerChute is trying to start the Acropolis File Service which will start up the AFS VMs in the Cluster.
PowerChute was unable to start the Acropolis File Service and start up the AFS VMs in the Cluster.
PowerChute did not detect any active replications for a Protection Domain. This step of the shutdown sequence is skipped, and PowerChute continues to the next step, shutting down the Nutanix Cluster.
PowerChute detected active replications for a Protection Domain. PowerChute will wait the delay specified in the Duration field on the Protection Domain Settings screen before aborting replications.
PowerChute is aborting any active replications of your protection domain(s).
PowerChute was unable to abort your active protection domain replications.
PowerChute is attempting to shut down the Nutanix Cluster.
PowerChute was unable to shut down the Nutanix Cluster.
PowerChute is attempting to start up the Nutanix Cluster.
PowerChute successfully started up the Nutanix Cluster.
PowerChute was unable to start up the Nutanix Cluster.
PowerChute was unable to establish a connection to the Nutanix Cluster.
Verify that your Cluster is running and verify the credentials specified in the CVM/Cluster Details screen.
A critical event has occurred on the UPS powering the Nutanix Cluster and PowerChute is shutting down all Controller Virtual Machines in the Cluster. Controller VMs are shut down after all other VMs in the Cluster, and the Nutanix Cluster itself are shut down.
A critical event has been resolved and PowerChute is attempting to start up the Controller Virtual Machine [CVM]. This event is triggered after the Nutanix host is online.
A critical event has been resolved and PowerChute is waiting for the Controller Virtual Machines in the Nutanix Cluster to startup. The Nutanix Cluster will start up when Controller VM startup is complete.
The Controller Virtual Machines on [Host] are starting up. PowerChute will wait the specified duration in the Startup Duration field in the Controller VM Shutdown/Startup screen before proceeding with the shutdown sequence.
The cluster stop operation was executed but the cluster is still running after the configured duration elapsed.
PowerChute could not connect to the cluster.
Authentication failures occurred when connecting to the cluster controller VMs for the cluster stop operation.
The cluster service did not start within the configured duration.
PowerChute could not connect to any cluster controller VM during the cluster stop operation.