WBEM and ESX virtual machines

[Kevin Everts_1]

I'm having a problem getting my ESX virtual machines identified. They show up as "Unknown" for the system type. I do have VMM installed and running. I've tried to set up WBEM to get the information but it isn't working. The credentials I'm testing with are of a domain administrator. I've tried using global settings as well as setting the credentials on the individual hosts. When I run the identification task, I get the following output:

Starting identification process...
Checking for known running web servers.
Checking for System Management Home Page and other HP web agents.
The System Management Homepage is not supported on this system.
Checking for WBEM support on system.
This system does not have any SMI-S CIMOM installed
This system doesn´t have a server CIMOM installed locally, or cannot connect to it using all credentials specified
Running WBEM rules based identification.
Cannot get ComputerSystem WBEM/WMI data from the system
Running VM Identification
The system is not a VMware ESX Host, or WBEM credentials may not be specified, skipping VM Identification
Running WS-Man identification.
The system did not respond to WS-Management, verify credentials.
Checking for SNMP support on system.
The system responded to a SNMP request, it supports SNMP.
Running SNMP base Cluster identification using common cluster MIB.
This was not a system with the common cluster MIBs supported.
Running HP ProLiant management agent identification
System does not have the SNMP ProLiant Server (foundation) agents installed.
Running HP NetServer identification.
System supports the NetServer SNMP agent, adding system type
Running HP-UX SNMP identification.
System does not have the HPUX SNMP agents installed.
Running SNMP System Type Manager identification.
No matching SNMP System Type Manager rule was found.
Checking for DMI protocol support.
The system does not have Windows DMI support.
Running DMI System Type Manager identification.
The system does not have Windows DMI support.
Running HP-UX DMI identification.
The system does not have HP-UX DMI support.
Running HP/Compaq Desktop identification.
The system does not have Windows DMI support.
Running HP DMI Desktop identification.
The system does not have HP DMI Desktop support.
Running Generic DMI identification.
The system does not have Generic DMI support.
Checking for SSH protocol support.
The SSH protocol is not supported on this system
Running Storage identification.
Storage identification completed.
Running HP Service Guard Identification.
The system is not part of HP Service Guard cluster
Checking if this system is supported by Insight Power Manager.
Insight Power Manager is not supported.
Running VM identification.
Building system relationships.
Running limited data collection for common attribute.
Done with limited data collection, checking retrieved data.
The system does not have SMH or SSO support.
Running node communication diagnosis
System identification done with this system.

Any help would be appreciated.

[Rob Buxton]

I think ESX Identification is still done via SNMP. So you'll need to ensure all of the snmp settings are correct.

[Kevin Everts_1]

Even the identification of the guests?

[JKytsi]

Checking for WBEM support on system.
This system does not have any SMI-S CIMOM installed
This system doesn´t have a server CIMOM installed locally, or cannot connect to it using all credentials specified

You have wrong WBEM credentials specified or You have disabled WBEM globally.

[Kevin Everts_1]

The credentials that I'm using are those of a domain administrator. How do I verify that the guest is granting or denying access?

[rob100]

Is this log coming from a Virtual Machine identification?
The information of the VM hosted comes from the ESX (with WBEM interrogation).

[Rob Buxton]

I enter WBEM credentials for the guests in order for them to be identified.
Works okay for Windows Guests. Typically I don't have SNMP installed on the guests.
SNMP is used for HPSIM to identify the ESX Host.

[Kevin Everts_1]

Ok, this is weird. At different points in time, different systems show up correctly. I.E. on Monday virtual server A will be identified correctly, on Tuesday virtual server B will show up correctly but A isn't anymore. On Wednesday they may both show up correctly or neither of them will.

All of them are using the same credentials that were set on each machine...

Any thoughts?

[Rob Buxton]

I've had issues where I had wbem credentials in the global section and was running the daily identification task.
not sure why but the timing seemed to implicate this process.
I disable this task and only use server specific wbem credentials.
I still have the occasional glitches but it's a bit more stable.