commands using vMA

[ayanes21]

I have installed and configured the vMA 5.x.  I have added and registered my vcenter server and two hosts (ESXi01, ESXi02).  When i connect to the vMA using vi-admin and target the ESXi02 host i can run all my commands with out issues.  However when I connect to the ESXi01 host and i try a command like resxtop i am prompted for user credentials, any credentials I try fails with "Login failed, reason: vim.fault.NoPermission" or "Login failed, reason: vim.fault.InvalidLogin".  Even though when I first connect using the vi-admin account I have tried supplying the vi-admin account, I've also tried using my windows credentials and that fails, also I've tried using the root account of the host and that fails as well.  Both hosts look exactly the same so I don't know what is prompting credentials for one host and not the other.  This is really bugging me so any help is greatly appreciated.clear

[MKguy]

Try to reconfigure the host that doesn't work with:

vifp reconfigure [hostname]

Can the vMA resolve hostname of the other host too? Also use the FQDNs rather than short names to register them with the vMA.

Try if this works without having any vifptarget set:

resxtop --server [IP of host] --user root

[ayanes21]

This command did not work using IP for the effected host I get the following error "Login failed, reason: vim.fault.NoPermission"

resxtop --server [IP of host] --user root

This did not either and gave me an error "Error: Insufficient permissions for root@psb-esxi01"

vifp reconfigure [hostname]

Also I blocked out the FQDN but I did register the servers using FQDN.

[MKguy]

If that works via IP then there is no reason why everything else wouldn't.

I suspect it's a general communication error because those commands using fpauth always dumbly fail in the same way as if you entered wrong credentials, even if the problem is at communication layers 2-4.

So can you ping the host using it's (FQDN) hostname from the vMA or nslookup it?

What does this curl yield:

# curl -Ivk https://[FQDN]

What if you register the host using it's IP with vifp addserver?

[ayanes21]

Sorry i thought it worked but stupidly i connected to the host IP of the one that was always working.  However I just realized I had lock down mode enabled on this host once I disabled it to test I was able to connect.  It still prompts me for a user name and password but the commands did run using root this time.  I read in a post If you enable or disable lockdown mode using the direct console user interface, permissions for users and groups on the host are discarded. To preserve these permissions, you must enable and disable lockdown mode using the vSphere Client connected to vCenter Server.  Could this be the issue.

[MKguy]

Check the permissions in the vSphere Client connecting directly to the host, if the vMA users are gone just run another vifp reconfigure.

[ayanes21]

The vifp reconfigure finally worked thank you.