Solved

vSphere vMA

Posted on 2013-06-13
2
129 Views
Last Modified: 2015-08-07
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.
0
Comment
Question by:cgitst
2 Comments
 
LVL 30

Expert Comment

by:IanTh
ID: 39246986
have a look in the vpxd.log  it will give us more info
0
 
LVL 19

Accepted Solution

by:
compdigit44 earned 500 total points
ID: 39266359
What is the build number of your vMA? Version 5.0 has a know bug with REsxtop:

https://www.vmware.com/support/developer/vima/vma50/vma_50_relnotes.html

Resxtop commands fail with the vim.fault.NoPermission error.
Log in to vMA as vi-admin and add targets. Log in as vi-user and initialize the target using the vifptarget command. Now, when you run resxtop commands, the commands fail with the vim.fault.NoPermission error.
Workaround: Do one of the following:

    Log in to vMA as vi-admin to run the command.
    Log in to a different shell as vi-user and run the command without vi-fastpass.
0

Featured Post

NFR key for Veeam Backup for Microsoft Office 365

Veeam is happy to provide a free NFR license (for 1 year, up to 10 users). This license allows for the non‑production use of Veeam Backup for Microsoft Office 365 in your home lab without any feature limitations.

Question has a verified solution.

If you are experiencing a similar issue, please ask a related question

If we need to check who deleted a Virtual Machine from our vCenter. Looking this task in logs can be painful and spend lot of time, so the best way to check this is in the vCenter DB. Just connect to vCenter DB(default DB should be VCDB and using…
When rebooting a vCenters 6.0 and try to connect using vSphere Client we get this issue "Invalid URL: The hostname could not parsed." When we get this error we need to do some changes in the vCenter advanced settings to fix the issue.
Teach the user how to use configure the vCenter Server storage filters Open vSphere Web Client:  Navigate to vCenter Server Advanced Settings: Add the four vCenter Server storage filters: Review the advanced settings: Modify the values of the four v…
Teach the user how to use create log bundles for vCenter Server or ESXi hosts Open vSphere Web Client: Generate vCenter Server and ESXi host log bundle:  Open vCenter Server Appliance Web Management interface and generate log bundle: Open vCenter Se…

827 members asked questions and received personalized solutions in the past 7 days.

Join the community of 500,000 technology professionals and ask your questions.

Join & Ask a Question