{"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
{"searchBar":{"inputPlaceholder":"Search by keyword or ask a question","searchBtn":"Search","error":"Please enter a keyword to search"}}How to deploy PowerChute Network Shutdown v4.3, v4.4.x Appliance in vSAN cluster.
Issue:
After deploying the PowerChute Network Shutdown Appliance to a vSAN Datastore, a configuration change is required to allow for graceful shutdown of the vSAN Cluster.
Product Line:
PowerChute Network Shutdown version v4.3, v4.4.x
Environment:
PowerChute Network Shutdown Appliance version v4.3, v4.4.x deployed on vSAN Datastore on one of the Hosts that is part of the vSAN Cluster.
Cause:
Software issue
Solution:
For PowerChute Network Shutdown version v4.3
After deploying the PowerChute Network Shutdown Appliance to a vSAN Datastore, a configuration change is required to allow for graceful shutdown of the vSAN Cluster.
Product Line:
PowerChute Network Shutdown version v4.3, v4.4.x
Environment:
PowerChute Network Shutdown Appliance version v4.3, v4.4.x deployed on vSAN Datastore on one of the Hosts that is part of the vSAN Cluster.
Cause:
Software issue
Solution:
For PowerChute Network Shutdown version v4.3
- Log into the PowerChute Appliance as root
- Enter the command systemctl stop PowerChute to stop the PowerChute service
- Edit pcnsconfig.ini The command to enter is vi /opt/APC/PowerChute/group1/pcnsconfig.ini If not familiar with using vi editor another option is to copy the file to a Windows system. Edit with text editor then copy the file back.
- Add Skip_Maintenance_Mode = true to the [HostDetails] section of the pcnsconfig.ini file (see example below) and save the file.
- Enter the command systemctl start PowerChute to start the PowerChute service
[HostDetails]
ConfigurationMode = Managed
Server = 192.168.1.190
Server_Protocol = https
Server_PORT = 443
nutanix_support = false
is_VCSA = true
Skip_Maintenance_Mode = true
ConfigurationMode = Managed
Server = 192.168.1.190
Server_Protocol = https
Server_PORT = 443
nutanix_support = false
is_VCSA = true
Skip_Maintenance_Mode = true
For PowerChute Network Shutdown version v4.4.x
- Log into the PowerChute 4.4 web interface
- Go to Vitalization Settings
- Select Skip Host Maintenance Mode
When a UPS critical event trigger PowerChute shutdown - all User VMs and Hosts are shut down gracefully.
The PowerChute VM gets powered off last when it's Host is shut down.
NOTE: We will only support Single/Redundant UPS Configurations. For vSAN Stretched Cluster, PCNS should be deployed on the Management Host (runs the Witness Appliance outside the vSAN Cluster).
The PowerChute VM gets powered off last when it's Host is shut down.
NOTE: We will only support Single/Redundant UPS Configurations. For vSAN Stretched Cluster, PCNS should be deployed on the Management Host (runs the Witness Appliance outside the vSAN Cluster).
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.