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

Our Brands

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

PowerChute Network Shutdown 4.0 Fails to shutdown host containing VMware vMA and vCenter Server Appliance, when host is added in cluster with IP

Issue:  
ESXi host that contains both PowerChute Network Shutdown (PCNS) installed in VMware Virtual Management Assistant (vMA) and vCenter Server Appliance (VCSA) and is added to cluster with IP (while configuring the cluster) does not shutdown.
 
Product Line:
PowerChute Network Shutdown 4.0
 
Environment:
Issue specific to scenario where VMware vMA and vCenter are on same host
OS: Any VMware ESXi, vMA and vCenter

Cause:
ESXi host running PCNS and vCenter Server VMs has been added to the Inventory using IP address instead of Fully Qualified Domain Name (FQDN)
 
Solution:

Uninstall PowerChute Network Shutdown 4.0 and install PowerChute Network Shutdown version 4.2

Or while setting up cluster, add hosts in vCenter with FQDN rather than IP to avoid this issue.
 

Can't find what you are looking for?

Reach out to our Customer Care team to receive information on technical support, assistance for complaints and more.