Powerchute Network Shutdown 4.2.0 Build 6755 & vCenter 6.5

[Anonymous user]

Hello everybody,

i have a issue with this environment:

• Appliance Network Shutdown 4.2.0 Build 6755
• vCenter 6.5.0.14000 Build Number 7515524
• 4 nodes VMware ESXi, 6.5.0, 7388607

We tested the envinroment bypassing the power plug, and this are the events:

02/16/2018	16:51:41	Running Shutdown Command File.
02/16/2018	16:51:10	vCenter Server is accessible. PowerChute will be able to issue commands to Virtual Machines or Hosts.
02/16/2018	16:51:10	UPS critical event: On Battery resolved on Hosts esxi03.dominio.nomination.com, esxi01.dominio.nomination.com, esxi02.dominio.nomination.com, 10.64.1.201, esxi04.dominio.nomination.com.
02/16/2018	16:51:00	Cannot connect to vCenter Server. PowerChute may not be able to issue commands to Virtual Machines or Hosts.
02/16/2018	16:43:50	SNMPV1: New connection by user public from 10.64.1.222
02/16/2018	16:24:03	UPS is no longer running on battery power or output power has been turned on.
02/16/2018	16:19:51	Shutting down VMs on Host esxi02.dominio.nomination.com.
02/16/2018	16:19:51	Starting Maintenance Mode Task on Host esxi02.dominio.nomination.com.
02/16/2018	16:19:51	Shutting down VMs on Host esxi01.dominio.nomination.com.
02/16/2018	16:19:51	Starting Maintenance Mode Task on Host esxi01.dominio.nomination.com.
02/16/2018	16:19:51	Shutting down VMs on Host esxi03.dominio.nomination.com.
02/16/2018	16:19:51	Starting Maintenance Mode Task on Host esxi03.dominio.nomination.com.
02/16/2018	16:19:50	Shutdown sequence started on Hosts esxi03.dominio.nomination.com, esxi01.dominio.nomination.com, esxi02.dominio.nomination.com, 10.64.1.201, esxi04.dominio.nomination.com in response to UPS critical event: On Battery.
02/16/2018	16:19:50	UPS critical event: On Battery.
02/16/2018	16:18:50	UPS has switched to battery power.

the result was that the nodes went in maintenance but only few vms shutted down.

im going to attach the some logs catched from /opt/APC/PowerChute/group1.

I don't have any dns related issues. Please help me!

[Anonymous user]

no one can help me?

[BillP]

Hi,

All of the errors below were logged in error.log The errors" findByIP" and "NoPermission or InvalidLogin" are all listed in the troubleshooting section of PCNS VMware User's Guide. 

16-02-18 16:51:17,465 ERROR Thread-34 com.apcc.m11.components.Shutdowner.Hosts.ESXManagedHost - checkForVCSAVMAndHostInCriticalHosts - cannot obtain HostSystem using findByIP and findByDnsName for critical host esxi03.dominio.nomination.com

16-02-18 16:51:22,481 ERROR Thread-34 com.apcc.m11.components.Shutdowner.Hosts.ESXManagedHost - checkForVCSAVMAndHostInCriticalHosts - cannot obtain HostSystem using findByIP and findByDnsName for critical host esxi01.dominio.nomination.com

16-02-18 16:51:28,451 ERROR Thread-34 com.apcc.m11.components.Shutdowner.Hosts.ESXManagedHost - checkForVCSAVMAndHostInCriticalHosts - cannot obtain HostSystem using findByIP and findByDnsName for critical host esxi02.dominio.nomination.com

16-02-18 16:51:34,022 ERROR Thread-34 com.apcc.m11.components.Shutdowner.Hosts.ESXManagedHost - checkForVCSAVMAndHostInCriticalHosts - cannot obtain HostSystem using findByIP and findByDnsName for critical host 10.64.1.201

16-02-18 16:51:41,061 ERROR Thread-34 com.apcc.m11.components.Shutdowner.Hosts.ESXManagedHost - checkForVCSAVMAndHostInCriticalHosts - cannot obtain HostSystem using findByIP and findByDnsName for critical host esxi04.dominio.nomination.com

16-02-18 17:36:52,918 ERROR Thread-34 com.apcc.m11.components.WebServer.util.virtualization.VMWareConnection - Unable to log directly into host (NoPermission or InvalidLogin): esxi03.dominio.nomination.com

16-02-18 17:36:52,918 ERROR Thread-34 com.apcc.m11.components.Shutdowner.Hosts.ESXManagedHost - Unable to establish a connection to shut down the host.

16-02-18 17:37:00,184 ERROR Thread-34 com.apcc.m11.components.WebServer.util.virtualization.VMWareConnection - Unable to log directly into host (NoPermission or InvalidLogin): esxi01.dominio.nomination.com

16-02-18 17:37:00,184 ERROR Thread-34 com.apcc.m11.components.Shutdowner.Hosts.ESXManagedHost - Unable to establish a connection to shut down the host.

16-02-18 17:37:06,537 ERROR Thread-34 com.apcc.m11.components.WebServer.util.virtualization.VMWareConnection - Unable to log directly into host (NoPermission or InvalidLogin): esxi02.dominio.nomination.com

16-02-18 17:37:06,538 ERROR Thread-34 com.apcc.m11.components.Shutdowner.Hosts.ESXManagedHost - Unable to establish a connection to shut down the host.

16-02-18 17:37:10,858 ERROR Thread-34 com.apcc.m11.components.WebServer.util.virtualization.VMWareConnection - Unable to log directly into host (NoPermission or InvalidLogin): 10.64.1.201

16-02-18 17:37:10,858 ERROR Thread-34 com.apcc.m11.components.Shutdowner.Hosts.ESXManagedHost - Unable to establish a connection to shut down the host.

16-02-18 17:37:16,948 ERROR Thread-34 com.apcc.m11.components.WebServer.util.virtualization.VMWareConnection - Unable to log directly into host (NoPermission or InvalidLogin): esxi04.dominio.nomination.com

16-02-18 17:37:16,948 ERROR Thread-34 com.apcc.m11.components.Shutdowner.Hosts.ESXManagedHost - Unable to establish a connection to shut down the host.

To correct the error "NoPermission or InvalidLogin" you need to create a local account on vCenter Server and each host for PowerChute to use to communicate the shutdown command. See page 19 of Application Note 180.

I also recommend adding the hosts IP addresses and domain names to the /etc/hosts on the appliance to resolve the findByIP errors. 

[Anonymous user]

thank you for reply, one more question.

The user i have to add to hosts must be pcnsadmin with pcnsadmin as password? is it customizable? if not, i think is a security concern

please let me know

[BillP]

Hi,

The user name used to log into PowerChute must match the assigned user name PowerChute will use to communicate with the network management card. The password used to log into PowerChute is unique to PowerChute. 

The user name and password Powerchute uses to communicate with vCenter Server should be the same user name and password PowerChute would use to log into the individual hosts. The reason is, if PowerChute cannot communicate with vCenter Server it requires the ability to log into the individual hosts to power them down.

[Anonymous user]

ok, so if im connecting to vcenter using the user upsadmin (just for example) i need to create the same user (with the same password) on all my hosts esxi. is that correct?

[BillP · Accepted solution]

Hi,

Yes, that is the recommended configuration.