Hey Guys,
Does anyone know of any tasks that can be performed only with vMA and not with the client itself?
If so can you list them.
Thanks
RJ
Main ones specific to the vMA...
vi-fastpass
vi-logger
sessionfiles
and also resxtop (unless you install vSphereCLI on a Linux machine).
When you say the 'client', if you meant the vSphere client, there are still a few config items that aren't exposed, and you need to use vMA/vSphereCLI or PowerCLI.
iSCSI binding (using esxcli swiscsi)
Claimrules and masking (using esxcli corestorage claimrule)
1) Collection of Syslog ESXi entries by the vilogger utility.
2) Ability to power down guests in a UPS configured environment sustaining an outage.
3) As above but with hosts also.
Hey LogiBoy,
Thanks for writing.
2) Ability to power down guests in a UPS configured environment sustaining an outage.
3) As above but with hosts also.
Now a UPS configured environment - can't you power down from the client. Why do you specifically do it from vMA. I am guessing UPS is the typical uninterrupted power supply. Or is it something different?
Thanks
RJ
You cannot get the client to automatically power down guests and hosts in a power failure event. You have to do it manually.
Installing UPS aware software on the vMA allows you to automate this process.
Thanks.
I am curious to find out how this whole power failure event is dealt with.so a vMA loaded with the UPS vmware software can communicate with the UPS and indicate power failure?
Am I right on my understanding? Is there any term for this so I can google it?
Any other vMA only tasks that you can think of?
Thanks
RJ
http://blog.meetsworld.org/2010/02/vmware-esxi-and-powerchute-network-shutdown/
As requested. Can't think of any other uses off the top of my head, but you will see vMA being used a lot more in the future as the stuff people want to do on the console of ESX won't be available in vSphere 5.
Cheers,
Paul
Main ones specific to the vMA...
vi-fastpass
vi-logger
sessionfiles
and also resxtop (unless you install vSphereCLI on a Linux machine).
When you say the 'client', if you meant the vSphere client, there are still a few config items that aren't exposed, and you need to use vMA/vSphereCLI or PowerCLI.
iSCSI binding (using esxcli swiscsi)
Claimrules and masking (using esxcli corestorage claimrule)
Thanks for all the replies guys.
RJ