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.
Опубликовано для: Schneider Electric Казахстан


Нужна помощь?
Инструмент для подбора продукции
Быстро и легко находите подходящие продукты и принадлежности для ваших условий применения.
Получить коммерческое предложение
Заполните заявку онлайн, и с вами свяжется наш эксперт.
Где купить?
Легко находите ближайшего к вам дистрибьютора Schneider Electric.
Центр поддержки
Находите ресурсы поддержки для всех ваших потребностей в одном месте.