Home
General
Virtualization
Runtime errors in vMA
Essendon
vMA is joined to the domain and can ping all hosts and vCenter like a star. When I run the following command I dont get an output, all it says is - Runtime error
esxcli --server vcenter.domain.local --vihost vesxi1.domain.local network nic list
I have tried adding both my vCenter and ESXi host using both adauth and fpauth authentication policies, but get the the same runtime error. If I target my ESXi host directly, the command esxicli network nic list runs without an issue.
Seems there's some kind of issue running the command against the vCenter machine. What could it be?
Another question - I ran the following command
resxtop --server vcenter.domain.local --vihost vesxi1.domain.local
The error I get is: Login failed, reason: Cannot find esxtop service on the host. Is the host powered on?
If I run the command - resxtop --vesxi1.domain.local
The command runs successfully. I ran esxtop by putty'ing to the host and it ran with no issues. Some weird stuff going on here for sure.
Find more posts tagged with
Comments
dave330i
Never ran vMA like that. I've always used vifptarget -s <host name>, then ran the commands directly against the host.
Essendon
Yeah I'd do that too, but the vMA guide from VMware runs commands against vCenter. Just wanted to know what I was missing.
I'll keep plugging away at this and will update if I fix it.
blargoe
I don't think you need the --vihost part unless your esxi servers are in lockdown mode. I've never used it myself... just vifptarget -s servername, then the command (except for resxtop, which is resxtop --server servername)
Quick Links
All Categories
Recent Posts
Activity
Unanswered
Groups
Best Of