I am new to using the vcenter server appliance, and not comfortable in the linux world, so bear with me.
All of my previous hosts have been of the esx flavor, NOT esxi.
I have created a new cluster of hosts using esxi5. I want to use esxtop to monitor them. I understand that I must use resxtop. To do this, I need the vCenter Server Appliance(I think). I downloaded this version vMA-22.214.171.124-472630_OVF10. I have installed the template, setup the vMA to function(setup the database, started services, etc.), logged into the console as root (both from the VM console and also via ssh).
I have made sure that my servers are NOT in lockdown mode.
My problem is this; when I type resxtop --server (servername) I get an error that resxtop is not found.
I can't find anything stating that resxtop is not included with the vMA, is this correct? The latest instructions I can find for the vMA is the vsphere Management Assistant guide (vsphere 5). In THOSE instructions it says that when I first boot the vMA appliance, I should be asked to set up a password for a user called vi-admin. This never happens. Are these instructions wrong? Am I barking up the wrong tree? Do I need to be logged in as this vi-admin or is root sufficient (I would have thought root to be sufficient)?
I feel STUPID that I cannot find any documentation helping me out with this, or any google searches where others have this problem.
No need to fee "Stupid" - We all are here to learn and earn :smileysilly:
Okay so vMA does not ask you to change the password - makes me thing something might be wrong with the vMA.
I am not sure if a md5 has is provided so you can check it and verify your download is intact.
If I were you I would simply try to download a fresh copy and redeploy.
My money is on the vMA package is probably not intact.
Like ESX Servers, You can run "esxtop" on ESXi too. (Hope, It's from ESX 4 & 4.1)
So the same command "esxtop" works in vMA too.
Ok, so I went and re-downloaded the older version, 4.1, and it all worked as advertised. I will re-download the newest version, 5.0 , tomorrow and see if it is a corrupted, or incomplete, package.
Thanks, I will update when I get a chance.