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.
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.
Udgivet til: Schneider Electric Danmark
Brug for hjælp?
Produktvælger
Find hurtigt og nemt de rette produkter og det rette tilbehør til dine anvendelser.
Få et tilbud
Start din salgsforespørgsel online, så vil du blive kontaktet af en ekspert.
Find forhandler
Find den nærmeste Schneider Electric-distributør.
Hjælpecenter
Find supportressourcer til alle dine behov på ét sted.