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 a UPS associated with [Host]. This will trigger a shutdown sequence using the actions configured on the Virtualization Settings page.
DRS will attempt to migrate powered on VMs to another Host in the cluster.
When VM migration is enabled in PowerChute and DRS automation level is set to fully automated, PowerChute starts a maintenance mode task on the host and allows DRS to migrate VMs to available hosts in the cluster.
PowerChute will attempt to migrate powered on VMs to another Host in the cluster.
When VM migration is enabled in PowerChute and DRS is disabled, PowerChute migrates VMs to available hosts in the cluster. If using the Custom Target Host migration option PowerChute will attempt to migrate to those target Hosts.
Unable to find a suitable Host to migrate VMs from Host [Host].
PowerChute could not find any suitable host within the cluster to migrate the VMs from [Host ] to.
Insufficient time configured to migrate VMs from Host [Host].
PowerChute was unable to migrate VMs from [Host] as insufficient time was provided in the Duration field.
Unable to migrate any VMs from Host [Host].
PowerChute was unable to migrate any VMs from [Host].
Unable to migrate all VMs from Host [Host].
PowerChute successfully migrated some of the VMs from [Host]. However, not all VMs were migrated.
No VMs require migration from Host [Host].
All powered on VMs have already been migrated on [Host].
VMs have been successfully migrated from Host [Host].
A critical event has occurred on a UPS associated with [Host] and PowerChute has successfully migrated virtual machines from it.
PowerChute started a maintenance mode task on [Host].
PowerChute has successfully put [Host] into maintenance mode.
PowerChute was unable to put [Host] into maintenance mode.
A critical event has occurred on a UPS associated with this host and PowerChute was unable to put [Host] into maintenance mode as there are still powered on VMs.
A critical event has occurred on a UPS associated with this host and PowerChute has cancelled the maintenance mode task for [Host] as there are still powered on VMs prior to attempting to shut down the host.
PowerChute cancelled the maintenance mode task on [Host] as the vCenter Server Appliance VM is shutting down.
A critical event has occurred on a UPS associated with this host and PowerChute could complete the maintenance mode task for [Host] as the duration configured is insufficient.
PowerChute takes the Host out of maintenance mode when a critical event is resolved and the Host is powered back on.
Migrating VMs on Host [Host] to another Host in cluster [Cluster].
A critical event has occurred on a UPS associated with the [Host] and PowerChute is trying to migrate virtual machines to another host in the [Cluster].
Migration was not performed because Host [Host] is not part of any cluster.
PowerChute could not migrate the VMs on this host because the host is not part of any VMware cluster.
A critical event has occurred on a UPS associated with this host and PowerChute is shutting down its virtual machines.
PowerChute is now shutting down the host.
PowerChute was unable to shut down VMs from [Host] as insufficient time was provided in the Shutdown Duration field
PowerChute is shutting down the specified vApp.
PowerChute is shutting down the VMs that are in the specified vApp.
PowerChute was unable to shut down [vApp] as insufficient time was configured for the Shutdown Duration field.
PowerChute is starting to shut down any vApps.
PowerChute was unable to re-start [vApp] as insufficient time was provided in the Duration field.
A critical event has occurred on a UPS associated with [Host]. PowerChute has not found any vApp associated with [Host] to shut down.
A critical event has been resolved and a host has restarted. PowerChute is trying to start up the VMs on that host.
A critical event has been resolved and the host has restarted. PowerChute is starting up the specified vApp in the VMware datacenter.
PowerChute is advising you to link your VMware hosts to a UPS Setup. See VMware Host Protection.
The PowerChute machine is shutting down.
PowerChute cannot connect to vCenter Server over the network. VM Migration and vApp shutdown cannot be performed when this occurs.
PowerChute cannot connect to vCenter Server using its credentials. Check that the username and password entered under vCenter Server Settings are correct. VM Migration and vApp shutdown cannot be performed when this occurs.
PowerChute cannot connect to the host over the network.
PowerChute cannot connect to the VMware host using its credentials. Check that the username and password entered under vCenter Server Settings are correct.
A critical event has occurred on a UPS associated with [Host] and PowerChute was unable to shut down [Host].
PowerChute is shutting down the Host containing the vCenter Server VM.
PowerChute could not previously restart VMs on the specified host and is now trying again
PowerChute could not previously restart a specified vApp and is now trying again.
PowerChute will not shut down the specified vApp as PowerChute is installed on a VM in that vApp.
The VM running PowerChute must be removed from the vApp.
PowerChute cannot connect to vCenter Server in order to perform VM Migration during a shutdown sequence.
PowerChute cannot connect to vCenter Server in order to perform vApp Shut down during a shutdown sequence.
With an Advanced UPS configuration, when critical events occur on UPS Setups at different times, this event indicates that the shutdown is already in progress so it will not be started again.
For example: if a critical event occurs on a UPS Setup with VMware Hosts linked and later on a critical event occurs on a Physical UPS setup, the shutdown sequence will not be performed twice, as it is already in progress from the critical event on the first UPS setup.
A critical event has triggered a shutdown sequence, however as either a VM or a vApp startup is already in progress, PowerChute will wait for the specified duration to elapse before continuing with the shutdown sequence. See Virtual Machine Shutdown/Startup.
PowerChute can now connect to the vCenter Server.
PowerChute can now connect to the host.
The specified critical event has been occurred on a UPS. This will trigger a shutdown sequence if not other shutdown sequence is currently active.
The specified critical event has been resolved.
The specified event has been resolved.
The event has been resolved.
This is logged when PowerChute previously detected that HA was disabled.
The specified cluster is not a high availability cluster. Because of this, if the host containing PowerChute in this cluster is shut down, PowerChute cannot be restarted automatically. See also HA Admission Control.
This occurs if Force vApp shutdown is disabled.
A critical event caused a shutdown but the specified vApp is already powered off.
PowerChute will not shut down the specified vApp as the vCenter Server VM is installed on a VM in that vApp.
The VM running the vCenter Server VM must be removed from the vApp.
PowerChute in unable to gracefully shut down the VM.
Check that the VM Shutdown Duration is long enough to allow for VMs to be shut down gracefully.
PowerChute is shutting down the VM running vCenter Server.
PowerChute is attempting to start the VM running vCenter Server.
This event is logged when Hosts that PowerChute is configured to protect (via the Host Protection Page) are no longer present in the vCenter Server Inventory. When this occurs the old hosts will be removed and you need to update the PowerChute configuration using the Host Protection page.
This event is logged if PowerChute cannot determine which VMware host is running vCenter Server VM. This can indicate a vSphere Configuration issue and will prevent PowerChute from gracefully shutting down the Dell VxRail cluster. vCenter Server VM.
This event is logged if PowerChute has identified the vCenter Server VM in the inventory but the VM is powered off. This can indicate a vSphere Configuration issue and will prevent PowerChute from gracefully shutting down the vCenter Server VM that PowerChute is configured for. the VxRail Cluster from being shut down.
Detected vSAN Synchronization in progress on Host [Host], waiting duration.
Active data re-synchronization has been detected on the host with Delay Maintenance Mode enabled. PowerChute will wait and check for active data to complete with a retry limit before proceeding with host shutdown.
PowerChute will proceed with host shutdown, as the retry limit has been reached.
FTT exceeded triggered a shutdown of vSAN Cluster VMs on Host [Host].
Fault Tolerance Threshold (FTT) is enabled and has been exceeded. Shut down all Cluster VMs is also enabled and has triggered a shutdown of all VMs on non-critical hosts in the vSAN Cluster.
A critical event has occurred on a critical host that is currently getting its VMs/vApps shut down in a separate shutdown sequence (as a non-critical host) due to Shut down all Cluster VMs being enabled.
Starting Maintenance Mode Task on Host [Host] using data evacuation mode: [Mode].
A maintenance mode task has been started on a vSAN host using the data evacuation mode: No Action or Ensure Accessibility.
PowerChute is attempting to start Witness Host VM.
Disabling vSphere Cluster Services (vCLS) on cluster [cluster].
PowerChute is attempting to disable vSphere Cluster Services (vCLS) on the cluster.
Unable to disable vSphere Cluster Services, vCLS VMs will not be deleted.
PowerChute was unable to disable vSphere Cluster Services (vCLS) within the specified Disable vSphere Cluster Services (vCLS) Duration. Ensure that vCenter Server is available.
vSphere Cluster Services (vCLS) VMs have not gracefully been shut down in the allocated time.
PowerChute was unable to delete the vSphere Cluster Services (vCLS) VMs within the specified Disable vSphere Cluster Services (vCLS) Duration.
PowerChute is attempting to disable High Availability (HA) on the cluster.
Enabling vSphere Cluster Services (vCLS) on the cluster [cluster].
PowerChute is attempting to enable vSphere Cluster Services (vCLS) on the cluster.
Unable to enable vSphere Cluster Services, vCLS VMs will not be created.
PowerChute was unable to enable vSphere Cluster Services (vCLS) and create the vCLS VMs on the host within the specified Enable vSphere Cluster Services (vCLS) Duration. Ensure that vCenter Server is available.
Enabling High Availability (HA) on cluster [cluster].
PowerChute is attempting to enable High Availability (HA) on the cluster.