vSphere Management Assistant (vMA)by Brian Drew<br />So VMware has announced the end of ESX and we all must move to ESXi. What’s the big deally whopper? <br />Well for starters as you probably know the service console is no more – it goes away. In response VMware provides the vMA as a ESXi management platform from which to launch commands, scripts, etc against ESXi hosts. <br />As promised, but late, in this deck I cover how get the vMA operational and begin using it for ESXi management.<br />
overview<br />The vMA is a virtual machine that you download from VMware. It comes as an OVF that you then deploy in vSphere.<br />The vMA is a Cent-OS (Linux) based VM. There is no management GUI for ESXi. Everything is command line. Time to bone up!<br />It is very easy to deploy, a little tougher to configure, and tougher still to use if you are not used to the command line. <br />I wasn’t a CLI guru but this forced my hand, all of our hands. <br />Once you get used to it I actually think you’ll like it. <br />Let’s move on. <br />
First things first<br />Download the vMA OVF here: http://www.vmware.com/support/developer/vima/<br />While there grab these docs:<br />http://www.vmware.com/support/developer/vima/vma41/doc/vma_41_guide.pdf<br />http://www.vmware.com/pdf/vsphere4/r41/vsp4_41_vcli_inst_script.pdf<br />And book mark this URL<br />http://www.vmware.com/support/developer/vcli/vcli41/doc/reference/index.html<br />
vMAInstall and config<br /><ul><li>During the OVF deployment I set the disk for thin provisioning and make sure to set the correct network settings. Then power it up.
Select the VM console in vCenter and you’ll land at the Network Configuration wizard.
The Welcome screen looks like this:</li></li></ul><li>The Network Wizard is as straight forward as that first step so just follow along to configure your IP settings and the vi-admin password. <br />Once done you should see this screen. <br />vMAinstall and configcontd<br />
First SSH (I use putty) or use the console to login using vi-admin and the password you entered during the Wizard. <br />Here is where things get interesting. <br />There is not much you can do yet. You first need to add your ESXi hosts and vCenter to the vMA so that they can be managed. <br />We’ll do that on the next page but first, did you notice that helpful hint at login?<br />When stuck try “vma-help”. <br />Now what<br />
You’ll get to know the vifp command real quick. Just typing “vifp” lists out the command options.<br />Use vifp to add, remove, reconfigure or list your servers – your ESXi and/or vCenter servers. <br />You also set the authentication policy with vifp. The options are Active Directory (adauth) or fastpass(fpauth). <br />The AD auth conflicted with my vCMA install so I’m using fastpass. <br />AD is cool if you don’t want to remember multiple credential sets. <br />To use AD auth you need to add your ESXi hosts to AD in vCenter. <br />Vifp<br />
Back to adding those ESXi and vCenter servers. <br />The command is as easy as this – “addserverexsihost.domain.domain--authpolicyfpauth”<br />The syntax for all is right there when you type “vifp”<br />Once done type use “vifplistservers –l” to see all your servers. The “-l” adds the authpolicy column so you can see it too. <br />Yours should look something like this:<br />Vifpcontd<br />
Your vMA is now operational and configured with your ESXi hosts and vCenter. <br />Now we have to tell vMA where to send the commands that we are going to issue. <br />We do this by setting the default target for the current session and here’s how we do it.<br />Use “vifptarget –s esxihost…” to do this. Here is how mine looked:<br />Set default target <br />Look how the command prompt changed to show that you are “on” the esxi host that you specified. <br />
You should now be able to issue commands without having to authenticate. <br />Let’s test that theory by issuing a command. Which command you ask? I don’t know, let’s see what vma-help offers us.<br />I picked an easy one – “esxcfg-nics –l”<br />Oddly enough the results look like this:<br />Lets test it out <br />
I hope that demystifies the vMA a bit. It’s not magic, just new. Once you have it operational my recommendation is to try to do things you normally use the service console for with the vMA.<br />I try to do everything via the vMA first. This is where you’ll launch your scripts from as well. <br />Check out the logger function. I didn’t want to confuse the matter here. <br />Best to all<br />The End<br />Wrap up <br />