{}
{"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

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

PowerChute Network Shutdown – some VMs are not started for HyperFlex cluster

Issue:
PowerChute Network Shutdown – some VMs are not started for HyperFlex cluster

Products:
PowerChute Network Shutdown v4.4, v4.4.1

Environment:
PowerChute Network Shutdown configured with HyperFlex support with VMware as hypervisor

Cause:
After the HyperFlex cluster service has started, some VMs may still be in an inaccessible state when PowerChute attempts to power them on. When this happens, the power on attempt will be unsuccessful and these VMs are not re-attempted.

Solution:
Increase the Cluster Startup Duration in PowerChute to allow enough time for all VMs to become accessible in the inventory before VM start up occurs.