{"searchBar":{"inputPlaceholder":"Rechercher par mot-clé ou poser une question","searchBtn":"Rechercher","error":"Veuillez saisir un mot-clé pour effectuer une recherche"}}
{}

Nos marques

{"support":{"yesButton":"Oui","noButton":"Non","feedback":{"title":"Quelles améliorations pouvons-nous apporter ?"},"submitButton":"Soumettre","successMessage":"Merci de nous avoir fait part de vos commentaires.","title":"Cela vous a-t-il été utile ?","feedbackPercentLabel":"personnes ont trouvé cela utile","captcha":{"error":"Veuillez cocher la case appropriée."}}}
Consulter notre FAQ

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.
 

Vous ne trouvez pas ce que vous recherchez ?

Contactez notre service client local si vous avez des questions ou si vous avez besoin de plus de détails ou d'une assistance technique.