Search FAQs
With VM Startup enabled, PowerChute Network Shutdown Fails to Restart a Fault Tolerant VM that it shut down.
Issue:
In addition to the Fault Tolerant VM failing to start, there are errors reported in vSphere client for PowerChute Network Shutdown (PowerChute) attempting to start a secondary VM.
Product Line:
PowerChute Network Shutdown v3.1, 4.x
Environment:
VMware
Cause:
This issue occurs if the vCenter Server goes offline during a shutdown sequence. PowerChute then fails to identify which VM is the primary and which is the secondary.
Resolution:
None. When vCenter Server becomes accessible, PowerChute will be able to identify the primary VM and issue a startup command to it. The secondary VM will be started by the system.
In addition to the Fault Tolerant VM failing to start, there are errors reported in vSphere client for PowerChute Network Shutdown (PowerChute) attempting to start a secondary VM.
Product Line:
PowerChute Network Shutdown v3.1, 4.x
Environment:
VMware
Cause:
This issue occurs if the vCenter Server goes offline during a shutdown sequence. PowerChute then fails to identify which VM is the primary and which is the secondary.
Resolution:
None. When vCenter Server becomes accessible, PowerChute will be able to identify the primary VM and issue a startup command to it. The secondary VM will be started by the system.
Released for:APC Bulgaria
Did this answer your question?
