The subject says it all.  The vMA VM is fast and responsive but as soon and I run a vifp command or an esxcli command against a target it takes ~10 seconds for a result.  Any thoughts?

It looks like I might be the only one having this problem.

I've recently installed the vMA appliance and used this PDF as an installation guide:

https://pubs.vmware.com/vsphere-55/topic/com.vmware.ICbase/PDF/vma_55_guide.pdf

The Domain controller is a Windows 2008 R2.

The vMA server is vSphere 5.5.0.3 Build 2301366

(vMA was updated to this version immediately after the install via the web interface)

Following the instruction to join the local domain that vcenter is on I ran this command:

sudo domainjoin-cli --loglevel verbose --log . join <my_domain> Administrator

(I added the loglevel and log argument after experiencing the problem in order to provide better error details below)

This is the relevant error that it produces:

20150505005817:INFO:Checking status of daemon [/etc/init.d/lsassd]

20150505005817:INFO:Daemon [/etc/init.d/lsassd]: status [3]

20150505005817:INFO:Getting DC

20150505005817:ERROR:Lsass Error [CENTERROR_DOMAINJOIN_UNRESOLVED_DOMAIN_NAME]

0x9CAC - Failed to lookup the domain controller for given domain. Check that the domain name is correctly entered. Check that your DNS server is reachable, and that your system is configured to use DNS in nsswitch. Check that port 389 UDP is not blocked by your firewall.

I can ping my PDC and the PDC can ping the vMA server.

No firewall was installed or any other software for that matter and I am able to add other servers to the domain with no problem.

What should I be looking for here?

Thanks for any info.

I am trying to install PCNS for VMware on vMA so our UPS can shutdown our hosts.  I'm getting the following message (see attached screenshot): "This version of Powerchute Network Shutdown only supports VMware ESXi" but I have ESXi. 

When I look on the Compatibilty Chart for PCNS for VMware it says "VMware ESXi Server 4.0 Update 1" but I believe we have Update 2 (we have ESXi 4.0.0, 261974), perhaps someone can confirm this is Update 2 please.

In any case, APC is saying PCNS for VMware is not compatible with Update 2, has anyone ran into this?  Does this mean we're out of luck until APC releases a new version?

vMA 4.1.0 BUILD-268751

I removed my vMA prior to removing it targets.  Is there a preferred way to cleanup the residual "vi-admin00" and "vi-user00" account information on the esx hosts prior to deploying a new vMA?  Also, is there any residual information left over in regards to vCenter since I registered vCenter as a target.

The vMA documentation states:  IMPORTANT If you delete vMA without removing all servers, the vi‐admin and vi‐user users remain on the target ESX/ESXi hosts. The next time you add the host to a vMA instance, vMA creates a user name with a different numeric extension.

Thanks.

John

We are a care home company looking to virtualise our environment using ESXi 4.1. I need to connect the ESXi running on a DELL poweredge R610 to a UPS. I have downloaded the new VMware vSphere Management Assistant (vMA), installed it and verified that it can connect to the ESXi via the ESXi client interface. My next task is to install the vmtools on vMA, but the instructions on how to do this not very clear to me.

Tried the following steps from Dell_ UPS Management Software Installation and Configuration User's Guide

• Insert the VMware server installation CD. (is this the free iso download for ESXi install?)

• Go to \VMware\RPMS to locate the VMware Tools installation package. (Where do I do this, in the vMA console from the ESXi client interface?)

• Log in to the guest operating system from the virtual machine console (I guess this is the vMA)
• ·         Select the template name and then right-click and select Install/Upgrade VMware Tools from the menu. (I selected the first option, from two given)

• Mount the CD with the command: using mount /dev/cdrom /mnt (vi-admin is not allowed to use this command, has to be root?)

Needless to say I have NOT made much progress from these instructions so far, can someone please help me. I have attached doc that has the instructions.

To start, ultimately, I want these (among other metrics which I have already written the script to collect) to go into a CSV file.

I would like to grab the names of the datacenters, and then the number of hosts and VMs in each. There isn't any built in metric for any of those... spitting out the datacenter names is a matter of grabbing them, but how can I get the number of hosts and VMs in each datacenter? Is the best way with some sort of funky (I'd guess for) loop?

Also, is there an easy way to only grab certain metrics (performance counters)? Like if I wanted to ONLY grab the total CPU usage what is the best way to approach that without letting the user specify in the opts?

Sorry if some of these questions are horrible, I just started working with vMA and I may not completely understand the API yet... haven't finished all the documentation (there seems to be quite a lot of it!).

Hi,

fairly new to using the perl sdk...  I am trying to deply from a template using vmclone.pl.  It works fine when I don't customize the vm or guest, but when I do I get the following failure when running in verbose mode:

as I want to be able to create and customise a datacenter with 9 VMs in it for demonstrations, I am hoping to script the all of this as I will do it quite frequently, but i am currently stuck.  The verbose log seems to be saying something about encoding or something up with the schema... but it doesn;t mean much to me, has anyone else any expereince?

thanks

Bill

I upgraded my vma appliance from 5.1.0.0 build 782391 to 5.1.0.1 build 1062361 this morning and now when I try to issue the vifptarget command to specify one of the hosts in my list as the target I get

-bash: vifptarget: command not found

I can view the man page of the command and I see it listed in /opt/vmware/vma/bin/ along with vifp which does work to add or remove hosts.

I've tried logging out or restarting the appliance but that didn't help. I tried adding the command's location to my path and that only generated errors.

Does anybody know what's wrong with it?

thanks

Hi all,

this is my first post so please don't hurt me ;-). and thanks for your patience

Our System-Environment:

- we have a rielloUPS with netman (ethernet) running and a small ESXi System with two ESXi-Host.

- VMWare ESXi 5.1.0-799733

- vMA Version 5.1.0.1-1062361

- Riello PowerShield 5.3.0 for vMA  kernel 2.6-x86_64 + ups_shut.scr + ghettohostshutdown5.pl from Riello UPS GmbH - VMware ESXi 5
we have done every step in the supplied installation pdf-manual.

It seems that someone at Riello has already done some porting work at the Original Script from William Lam, but we cannot get it to run

first of all /etc/init.d/upsmon:

- the script uses ". /etc/rc.d/init.d/functions" we changed to ". /etc/rc.status

- the script uses "daemon $upsagent" for starting (we changed it to "start_daemon -u vi-admin -p $pidfile $upsagent"

with these changes we were able to start the daemon.

after installing the rpm, and some additional chmod +x changes to ups_shut.scr and ghettohostshutdown5.pl

the scripts will be executed by the daemon when the UPS goes on battery.

BUT SADLY:

the ghettohostshutdown5.pl is not able to login to our esxi hosts (esxi01 and esxi02) vma-host is "esxi01"

<SNIP>

06-11-2013 19:35:08 -- info: Host is "VmaTarget=HASH(0x1a99318)"
06-11-2013 19:35:08 -- info: Hostname is "esxi02"
06-11-2013 19:35:08 -- info: Found host: "esxi02"
06-11-2013 19:35:08 -- debug: Main: Login by vi-fastpass to: esxi02
06-11-2013 19:35:08 -- info: Error: Unable to login to host: "esxi02"! Ensure host is being managed by vMA!

</SNIP>

INTERESTING:

When i run the script MANUALLY as vi-admin with identical parameters from log:

<SNIP>

06-12-2013 01:07:18 -- info: Host is "VmaTarget=HASH(0x7be0f8)"

06-12-2013 01:07:18 -- info: Hostname is "esxi02"

06-12-2013 01:07:18 -- info: Found host: "esxi02"

06-12-2013 01:07:18 -- debug: Main: Login by vi-fastpass to: esxi02

06-12-2013 01:07:22 -- info: Begin auto operation on VMs ...

06-12-2013 01:07:23 -- info: Execute autoShutdownVMs()

06-12-2013 01:07:23 -- info: Issuing AutoStartPowerOff() ...

Can't use an undefined value as an ARRAY reference at /home/vi-admin/ghettoHostShutdown5.pl line 443.

</SNIP>

where is the difference when calling/execute the ghettohostshutdown5.pl:

- manually

and

- and by daemon, as "vi-admin" user

Thanks in advance

Hi,

Is there any way in which I could manage VM snapshots using vMA? I'm using the command "vmware-cmd" but I see no option to LIST the snapshots and revert to a specific one.

I can only get the command to show me in a boolean fashion if the VM has snapshots, remove them or revert to the last one.

Thanks in advance!

elgreco81

Hello

I need a Perl script that run on vMA 5.0

I need a script that accept VM guest name and returning me which ESX it attached to

Can someone help me?

Thanks

Hello,

I'd like to install the package hpsmh-6.2.1-14.x86_64.rpm from

http://h20000.www2.hp.com/bizsupport/TechSupport/SoftwareDescription.jsp?lang=it&cc=it&prodTypeId=15351&prodSeriesId=3454575&prodNameId=3562405&swEnvOID=4091&swLang=8&mode=2&taskId=135&swItem=MTX-d752ad6a8cb44bebafae8cf8de

that is the download page of the drivers for HP proliant servers.

In the installation instructions is written:

Installation:

Download the rpm package to a directory on your hard drive and change to that directory.

Type rpm -ivh hpsmh-< version >.x86_64.rpm to install.

The problem is that the RPM is not present on my ESXi installation. I tried to use ipkg but the error was:

/vmfs/volumes/4c895c80-e7b9fb9a-751b-00237dd0c11a/INST/PATCH # ipkg install hpsmh-6.2.1-14.x86_64.rpm

ipkg: invalid magic

Any suggestion?

Thank you in advance,

Davide

Im trying add targe ESXi 5.5:

vi-admin@localhost:~> vifp addserver esxi1 --authpolicy fpauth --username root --password Passw0rd

vi-admin@localhost:~> vifp listservers

esxi1  ESXi

vi-admin@localhost:~> vifptarget -s esxi1

vi-admin@localhost:~[esxi1]> esxcli network nic list

Runtime error: The session is not authenticated.

In vSphere client task inform me about create users:

but when im trying run some remote commands i receive:

Runtime error: The session is not authenticated.

Some suggestion ?

Hi.

I need add 3 hosts to vMA.I dont have domain controller.

1. I deploy fresh vMA from OVF and configure IP and password for vi-admin.

2. Add first ESX01 host with success. ( vifp addserver esx02 --authpolicy fpauth )

3. Added second and third ESXi finish with fail.(commands bellow)

vi-admin@vma02:~> vifp addserver esx02 --authpolicy fpauth

root@esx02's password:

vi-admin@vma02:~> vifp listservers

esx02.localdomain       ESXi

vi-admin@vma02:~> vifp addserver esx03 --authpolicy fpauth

root@esx03's password:

Error: Failed to add users

in vSphere client we can see something that:

During above tasks is creating vi-user and next vi-admin. After several seconds vi-admin is removed(i dont know why...)

/var/log/vmware/vma/vifpd.log on vMA

[2016-04-07 19:51:07.186 7F220CD47700 info 'App'] command-> 1

[2016-04-07 19:51:07.187 7F220AEC7700 info 'App'] ADDSERVER

[2016-04-07 19:51:07.197 7F220CD47700 info 'App'] MessageQueue::RecvMessage - Queue id is 0

[2016-04-07 19:51:07.595 7F220AEC7700 info 'App'] MessageQueue::SendMessage - Queue id is 0

[2016-04-07 19:51:12.144 7F220CD47700 info 'App'] command-> 1

[2016-04-07 19:51:12.145 7F220CD47700 info 'App'] MessageQueue::RecvMessage - Queue id is 0

[2016-04-07 19:51:12.145 7F220AE45700 info 'App'] ADDSERVER

[2016-04-07 19:51:12.504 7F220AE45700 info 'App'] Already connected.

[2016-04-07 19:51:12.509 7F220AE45700 info 'App'] Already connected.

[2016-04-07 19:51:30.308 7F220AE45700 info 'App'] permissions set for vi-admin00@esx03.localdomain

[2016-04-07 19:51:30.345 7F220AE45700 info 'App'] credstore: added user vi-admin00@esx03.localdomain to credstore of vi-admin

[2016-04-07 19:51:30.361 7F220AE45700 info 'App'] can take ownership of user vi-user01@esx03.localdomain.

[2016-04-07 19:51:30.361 7F220AE45700 warning 'App'] taking ownership of vi-user01@esx03.localdomain as it seems to be created by us.

[2016-04-07 19:51:52.534 7F220AE45700 error 'App'] addserver: Error occured while adding users for esx03.localdomain ..rolling back. Error in Vma

core.

[2016-04-07 19:51:52.582 7F220AE45700 info 'App'] user vi-admin00@esx03.localdomain is created by vifp. Removing it...

[2016-04-07 19:51:52.703 7F220AE45700 info 'App'] failed to remove permissions for vi-admin00@esx03.localdomain.

[2016-04-07 19:51:52.704 7F220AE45700 info 'App'] removed user vi-admin00@esx03.localdomain.

[2016-04-07 19:51:52.733 7F220AE45700 info 'App'] user vi-admin00@esx03.localdomain is removed from credstore of vi-admin.

[2016-04-07 19:51:52.768 7F220AE45700 error 'App'] Failed to add users

[2016-04-07 19:51:52.768 7F220AE45700 info 'App'] MessageQueue::SendMessage - Queue id is 0

[2016-04-07 19:51:52.772 7F220AE45700 info 'App'] MessageQueue::SendMessage - Queue id is 0

In which logs can i find something more ?

var/log/vmkernel.log on host is not clear for me... but if somebody will ask i will paste.

What should i do more ? i want only add 3 esxi servers to vMA and next login to those esxi without puting passwords.

Interesting is when i deployed next vMA02 and VM03 i can only add one esxi to vMA. During adding Second and third esxi generate that same errors... Now i have 1 vMA for each host .....

Please about suggestion and help.... because my adventure with vMA is not good... last time i was problem with this vMA 5.5 The session is not authenticated after connect to target ESXi and dont resolved this in my second lab...

Sebastian

For those of you that might be interested in installing and giving Virtual Disk Development Kit 1.1 a try on VMware vMA, you may run into an issue with the following:

 

The following libraries could not be found on your system:

libfuse.so.2

 

Here is the procedure on remediating the issue and getting VDDK 1.1 installed

1. Download VDDK 1.1 ( VMware-vix-disklib-1.1.0-163495.x86_64.tar.gz ) and upload to your vMA host

2. Extract the contents

tar -zxvf VMware-vix-disklib-1.1.0-163495.x86_64.tar.gz

3. Download libfuse.so.2 rpm package for RHEL 5 (http://rpm.pbone.net/index.php3/stat/4/idpl/9551023/com/libfuse-2.7.4-1.el5.pp.x86_64.rpm.html) and upload to your vMA host. You can actually do this in one step using curl found on vMA:

curl -O ftp://ftp.pbone.net/mirror/ftp.pramberger.at/systems/linux/contrib/rhel5/x86_64/libfuse-2.7.4-1.el5.pp.x86_64.rpm

4. Install the rpm dependancy

[vi-admin@inTheGhetto ~]$ sudo rpm -ivh libfuse-2.7.4-1.el5.pp.x86_64.rpm
warning: libfuse-2.7.4-1.el5.pp.x86_64.rpm: Header V3 DSA signature: NOKEY, key ID 6971f6ac
Preparing...                ########################################### [100%]   1:libfuse                ########################################### [100%]

5. cd into VDDK 1.1 extracted directory

cd vmware-vix-disklib-distrib/

6. Install VDDK 1.1 and accept the EULA and default installation in /usr

[vi-admin@inTheGhetto vmware-vix-disklib-distrib]$ sudo ./vmware-install.pl

Now both vmware-mount and vmware-vdiskmanager will work without complaining about the missing libfuse.so.2

I would hope in the future that all side toolkits/products will be compatible with vMA without any additional research/package dependency. I disklike the fact that users must go out to the net to find patches/packages to satisfy a VMware product installation. I know that vApp's produced by VMware are highly customized to fit a specific need and I prefer that all dependency's are covered without having end-users potentially download unsupported/unknown packages onto these vApps.

It would also be awesome to include with vMA: VMware VIX, VDDK, etc.

=========================================================================

William Lam

VMware vExpert 2009

VMware ESX/ESXi scripts and resources at: http://engineering.ucsb.edu/~duonglt/vmware/

vGhetto Script Repository

VMware Code Central - Scripts/Sample code for Developers and Administrators

http://twitter.com/lamw

If you find this information useful, please award points for "correct" or "helpful".

I have installed ESXi 4.0 server as a host on Dell OptiPlex 755 with 4 GB ram(Intel Core2 Duo E4600@2.4GHz

2.39 GHz).I am using 32-bit system.Now I also installed vMA and when I am put the power on,it is throwing the following error on the console  --

Your CPU doesnt support long mode.Use a 32-bit distribution.

I checked some forums and found out that  VT should be enabled in BIOS and when I check my BIOS setting and make the following changes-

Performance &gt; VT for Direct I/O Access(set toOn)

but getting the same error..

please help me to resolve it...

Thanks in Advance.

Hi all,

I have vMA fresh download from vmware web site. Then:

$ sudo /etc/init.d/wsman status

openwsmand is stopped

$ sudo /etc/init.d/wsman start

wsman is already running

$ sudo /etc/init.d/wsman status

openwsmand is stopped

$ sudo /etc/init.d/wsman stop

$ sudo /etc/init.d/wsman status

openwsmand is stopped

$ sudo /etc/init.d/wsman start

wsman is already running

$ sudo /etc/init.d/wsman status

openwsmand is stopped

There isn't service in process list (ps -aef). Any idea?

Thanks

Kris

Hi,

I just updated the vMA appliance using the following patch meta file;

http://www.vmware.com/go/vma4/update/vmw-VIMA-4.0.0-metadata.zip

I am a bit surprised this was last updated 26 February 2010, leaving the system with missing critical security patches. When launching the latest version of Nessus against a fully patched vMA, I ended up with 12 High (this includes kernel, openssh, and perl) and 25 Medium unpatched vulnerabilities, all related to missing patches.Did I miss something (wrong meta file, poorly applied patches...) or is it really the current, up to date, patch status ?

Hi, just wondering if anyone can help.  I originally configured my VMA to be a DHCP client, but now I need to configure it with a static IP.  Any help would be greatly appreciated.

Hi VMWare gurus, I have a tricky problem to feed your mind;

I am running a vMA appliance as a guest on an ESXi host. I want to run a perl script that will connect to an ESX/ESXi host (given as a parameter), will enumerate all virtual machines on the host and will shutdown those that are powered on.

I coded the script and it works pretty fine, except from one little thing ; if you target the ESX host you are running the vMA on, the script will power it off, resulting in a quite stupid virtual suicide.

So here is my question: is there any way for such a script to recognize the guest it is running from ?  ?:|

Thank you