Subscribing is a smart move!
You can subscribe to this forum after you log in or create your free account.
PCNS appliance cannot login to hosts
APC UPS Data Center & Enterprise Solutions Forum
Schneider Electric support forum for our Data Center and Business Power UPS, UPS Accessories, Software, Services, and associated commercial products designed to share knowledge, installation, and configuration.
Invite a Co-worker
Send a co-worker an invite to the Exchange portal.Just enter their email address and we?ll connect them to register. After joining, they will belong to the same company.
Send Invite Cancel
Solved
Go to Solution
This was originally posted on APC forums on 7/2/2018
Hello everyone,
We recently deployed a PCNS aplliance (4.2) to a vsphere 6.0 environment with 2 hosts and everything seems to be working OK (VM shutdown, host protection, etc.).
Still there seems to be an issue as PCNS tries to login not only to the vcenter (which works fine as seen in the bottom line in my screenshot) but also to the hosts using the same credentials which fails.
The user has the Administrator role on both hosts and can be used otherwise to login (e.g. vsphere-client).
To be honest I don't know why PCNS is even trying to login to the hosts directly.
Can anyone help?
Accepted Solutions
This was originally posted on APC forums on 7/26/2018
I think I figured out the problem. I assume you, like me, have your AD domain set as the default domain in vCenter. It appears that you can either set your default domain back to vsphere.local or possibly add the APC user to your AD domain. Maybe APC will answer to what happens if you add the user to your AD domain and AD is not available as the domain controller VM has already be shut down but perhaps since it is already logged in it doesn't matter. I have just changed my default domain to vsphere.local and will see if it produces any problems anywhere else. Hope this helps!
This was originally posted on APC forums on 7/24/2018
On 7/24/2018 1:24 PM, Bill said:Hi,
When connecting directly to ESXi hosts PowerChute just uses user as the account name since ESXi will not allow @vsphere.local for a username.
That may be the way it is supposed to work, but in my case, also on vmWare 6.5 it appears that PowerChute is sending the full name when attempting to log into the hosts as I see this issue since we have upgraded vmWare. As you can see from the error logged below it is attempting to log into ESXi as apc@vsphere.local.
This reply was originally posted by Bill on APC forums on 7/26/2018
Hi,
I have created a pcnstester account on the 6.5 VCSA in the vsphere.local domain
Added the user and given it administrator privileges via roles
I then created the same user in the ESXi 6.5 host using the same password and gave it administrator privileges on the host.
Then when configuring PowerChute I selected managed by vCenter and added the pcnstester credentials
The pcnstester account can communicate with both VCSA and the host/s
This was originally posted on APC forums on 7/26/2018
I followed the same procedure:
Then:
Added the user to the host and gave it permission:
When I attempt to reconfigure the PowerChute settings using "apcpcns" as you did I get the following error:
If I use apcpcns@vsphere.local it passes this screen but is still unable to log into the hosts as it is trying to log in as apcpcns@vsphere.local.
This was originally posted on APC forums on 7/26/2018
I think I figured out the problem. I assume you, like me, have your AD domain set as the default domain in vCenter. It appears that you can either set your default domain back to vsphere.local or possibly add the APC user to your AD domain. Maybe APC will answer to what happens if you add the user to your AD domain and AD is not available as the domain controller VM has already be shut down but perhaps since it is already logged in it doesn't matter. I have just changed my default domain to vsphere.local and will see if it produces any problems anywhere else. Hope this helps!
Create your free account or log in to subscribe to the forum - and gain access to more than 10,000+ support articles along with insights from experts and peers.