{}
{"support":{"yesButton":"yes","noButton":"no","feedback":{"title":"What can we do to improve?"},"submitButton":"Submit","successMessage":"Thank you for your feedback","title":"Did this answer your question?","feedbackPercentLabel":"of people found this helpful","captcha":{"error":"Please tick the box"}}}

Search FAQs

{"searchBar":{"inputPlaceholder":"Search by keyword or ask a question","searchBtn":"Search","error":"Please enter a keyword to search"}}

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.
Users group

Discuss this topic with experts

Visit our Community for first-hand insights from experts and peers on this topic and more.