You are currently viewing the content available in Vietnam. If you are looking for information for another region, please select the correct country from the top-left dropdown in the page and 'Navigate to Browse FAQs' in the Support menu.
Issue:
PowerChute fails to shut down ESXi host/s when the DNS server is offline.
Product Line:
PowerChute Business Edition Agent versions 9.0.3, 9.1.1, 9.2, 9.2.1, 9.5, 10.x
PowerChute Network Shutdown versions 2.2.3, 2.2.4, 3.0, 3.0.1
Environment:
VMware Virtual Management Assistant (vMA)
Cause:
PowerChute runs a script the pulls the host name/s from vifptarget library. If the DNS server is running as virtual machine (VM) and has been shut down or the DNS server is off line the ESXi host name/s cannot be resolved causing the shut down to fail.
NOTE: PowerChute Network Shutdown version 3.1 and 4.x do not utilize vifptarget library. If running older versions of PowerChute Network Shutdown we recommend updated to the latest version.
Comparability information for PowerChute Network Shutdown can be found here.
To download the latest version of PowerChute Network Shutdown click here.
Solution:
Add the ESXi host/s to /etc/hosts file
PowerChute fails to shut down ESXi host/s when the DNS server is offline.
Product Line:
PowerChute Business Edition Agent versions 9.0.3, 9.1.1, 9.2, 9.2.1, 9.5, 10.x
PowerChute Network Shutdown versions 2.2.3, 2.2.4, 3.0, 3.0.1
Environment:
VMware Virtual Management Assistant (vMA)
Cause:
PowerChute runs a script the pulls the host name/s from vifptarget library. If the DNS server is running as virtual machine (VM) and has been shut down or the DNS server is off line the ESXi host name/s cannot be resolved causing the shut down to fail.
NOTE: PowerChute Network Shutdown version 3.1 and 4.x do not utilize vifptarget library. If running older versions of PowerChute Network Shutdown we recommend updated to the latest version.
Comparability information for PowerChute Network Shutdown can be found here.
To download the latest version of PowerChute Network Shutdown click here.
Solution:
Add the ESXi host/s to /etc/hosts file