Issue:
PowerChute Network Shutdown v4.x fails to shut down the vCenter Server VM or ESXi hosts when using a local account.
This issue manifests itself as follows when attempting to shut down ESXi hosts during a shutdown sequence, as seen in the PowerChute error log.
19-05-18 10:44:38,096 ERROR Thread-40 com.apcc.m11.components.WebServer.util.virtualization.VMWareConnection - Unable to log directly into host (NoPermission or InvalidLogin): 192.168.1.10 19-05-18 10:44:38,096 DEBUG Thread-40 com.apcc.m11.components.WebServer.util.virtualization.VMWareConnection - com.vmware.vim25.InvalidLogin
Product Line:
PowerChute Network Shutdown versions 4.x
Environment:
All support OS configured with VMware vCenter Server and ESXi host(s).
Cause:
PowerChute attempts to log in with a lower-case username
e.g.
User created in ESXi host and entered in PowerChute as PCNSUSER
When PowerChute contacts the host, it enters pcnsuser
The user is rejected because the ESXi host expects PCNSUSER (all uppercase letters).
Solution:
1 - Create a user in the host/s with lowercase letters.
2 - To avoid having to use a lowercase username, set the default SSO domain to localos.
Example: if using PCNSuser@localos set the default domain in vCenter to localos. This allows for connection to vCenter using the username "PCNSuser" without having to include "@localos" and use this in the PCNS UI. This would avoid PCNS converting the username to lowercase.
The same would be true for vsphere.local accounts - whatever the default domain is set to, you can use the username without having to include the domain name, "@vsphere.local".
