ID VM guest

[SIT]

Hi,

I have Linux-VMware ESX Server servers. They are identify by SIM. The VM agent is install and the VM Host is licensed (i see all my Virtual machines with Performance ...)> great

But i have the following problem : when i select one of those virtual machines, they are not identify - unmanaged. If i set manualy the subsystem "Virtual Machine Guest, VMware ESX Guest", in "Virtual Machine Configuration Details" > No matching VMM node found for XXXXX while they are recongnize by the ESX Server.
Just my VM where HP SIM is install is corrctly identify > vm control, VM backup, VM config ...

Is there a guideline ?
Thanks for your support

[Rob Buxton]

As a lot of the VMs don't have either SNMP or the HP Hardware Agents I revert to wbem.

I have wbem enabled globally, but with no credentials. I then use server specific credentials for wbem for all of the VMs.

In addition I maintain a script that uses the mxnodesecurity command to update the password if required. This runs against each virtual server. So as well as adding the credentials for the VM, I add another line to this script for the newly added server.

[SIT]

Hi,

OK, but why Vm's are identified by the VMWare Server :

Virtuals machines
select the VM. Then i see correctly :
VM Control
Vm detail ...

While, when i enter in the search case the Vm name, then select the Vm, it appear as (Unmanaged) ?

Thanks

[Rob Buxton]

I think its because using the VMM agent is not one of the discovery / identification protocols.
It would be nice VMM did pass on the identification info into HPSIM.

[SIT]

OK so for you, it 's a problem with HPSIM wich not support "natively" Vm's .... ?

[SIT]

Thanks for your support

Another point: You said that you use WBEM for VM's. On mine, when i try to configure the agent I have the following errors >
Configure WBEM / WMI user (START) ...
Configure WBEM / WMI user (DONE) ..................................... [FAILED]
HP WBEM provider or its WBEM / WMI user configuration utility is not available o
n this system.
Subscribing to WBEM / WMI indications ...
Subscribe to WBEM / WMI Indications (DONE).......................... [FAILED]
Check whether target system met the requirements and all of the software require
d to support indications is installed.
WBEM protocol settings are not valid/enabled for this system in HP SIM. Check yo
ur HP SIM settings.

[Rob Buxton]

I just have WBEM enabled Globally in HPSIM, but with no credentials at the global level. And then add credentials at the server specific wbem point. Just click on the server name and it's one of the options under the tools tab (sorry at home so can't be more precise).

I then just run an identification task - I don't configure anything clever on the VM guest. This works for Windows guests - not tried anything with Linux guests.

[SIT]

Thanks for your answer

I know how to configure the SNMP settings on the server but where can i configure the Wbem credential on the server ?

[SIT]

How to set credential on Vm since, HPSIM, don't install the agent through "Configure or repair agent". I receive the following error :

Configuration of agents started, waiting for it to be completed.
Configure Agents and Providers (START) ...
Subscribing to WBEM / WMI indications ...
Subscribe to WBEM / WMI Indications (DONE).......................... [FAILED]
Check whether target system met the requirements and all of the software require
d to support indications is installed.
WBEM protocol settings are not valid/enabled for this system in HP SIM. Check yo
ur HP SIM settings.

The OS of my Vm is W2k3 R2.

Is it possible to launch directly the Wbem Agent install ?

Thanks

[Rob Buxton]

Click on the Virtual Server Name in HPSIM.
Go to Tools & Links.
Go to System Protocol Settings
Select the Update WBEM Details, and then check the Use Values Specified below and enter the appropriate credentials.

At the bottom leave the Run Identification task checked.
The virtual server should now get identified.

[SIT]

Ok but in the System Tab - Product Description - Management Protocols, i don't have WBEM. I have to setup Wbem protocol on the Vm ?

The credential that i enter must be match the wbem settings on the Vm like SSh and the community string for example ?

Thanks for your patience ;)

[NJK-Work]

Hey Rob,

On a side note, I used to do what you do about not setting the WBEM password globally and for the same reason - the data collection would get messed up if both WBEM and normal agent collection ran.

But then it dawned on me that WBEM will only work if the account you use has admin rights to the target server. Since I was already doing this for the VMs and NOT doing this for the physical machines, I was able to set a global password and not have to wory about individually setting a WBEM password for each VM. Since my WBEM admin account is not a local administrator of any of the physical machines, WBEM does not touch them and my data collection jobs (or actually the data that they collect) remain good.

Just a thought - you might want to try it.

Nelson

[NJK-Work]

Oh - I should add. Our WBEM admin account is put into the local administrators group of our standard VMware templates. That way all new VMs build automatically plug right into SIM without any additional configuration.

Eric - sorry for hijacking your post ;)

Nelson

[SIT]

It's OK, no pb ;)

For WBEm, does i have to install something (i have not WBEM in Management Protocols)like snmp for example ?

[NJK-Work]

I believe you need the "Pegasus WMI Mapper" service installed and running. This may only be needed if you need to manage UNIX/Linux servers from SIM, so I am not 100% certain if this is needed for Windows.

Do you see this service running in your list of services on your SIM server?

Nelson

[SIT]

Hi,

Yes, on my SIM i have the Pegasus WMI Mapper.
The service is running and the run status is "Automatique"

[Rob Buxton]

Nelson,
Thanks that looks like a good workaround.
As our VMs have grown maintaining the list was getting interesting!
Yes we have the Pegausus WMI mapper. I also have to periodically restart it as it seems to have a memory leak.

[David Claypool]

Nelson, just be aware that during the identification process run daily, that password is going to be used to attempt to authenticate to every single one of your devices. As it fails on one of your physical Windows servers (since you say it isn't a valid password for anything other than your VMs), it's going to generate DCOM 10009 errors.

[SIT]

I finaly find my issue.

I'd just leave blank the WBEM setting in Global protocol ... please no comment ... ;)


Thanks a lot, now I see my VM identified in SIm

[SIT]

Just to know

Why you leave credantials to blank in the global protocol settings and configure VM by VM ... ?

[SIT]

Just check the WBEM case without credential in the global protocol setting

[mark q]

I have a question here too..

I have a local account - not a part of administrators will wbem be able to identify vm's if this user is not part of the operators group?

I have about 500 vm's that I need to identify and the user is there and the password is correct but I cannot correctly identify vm windows guests.