How do we monitor ESXi 3.5 Installable with HP SIM 5.3 SP1

[Robert Babayan]

Hi Guys,

We have HP SIM 5.3 SP1 and a few HP Proliant DL 580 G5 servers with ESXi 3.5 Update 4 (HP version > hpvm-install-hd-153875.iso )with HP CIM providers. I added these servers into HP SIM 5.3 console I can not re-discover them using the WBEM and ESX's " root " login/ password it failes to communicate with the ESX servers and the link to " Healh Status " for each server is not working.

There are no HP Management Agents available for ESX3.5i but there is for ESX3.5 full version ? when you download the below agents and you read the read me files it only refers to ESX3.5.

see this link:

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

according to this HP document ( HP VMware ESXi management environment) on page: 2 it onlt talks about Vmware ESXi on the internal USB key. ...." HP Insight Management WBEM Providers (Insight Providers) are pre-installed along with integrated VMware ESXi on the internal USB key to provide active hardware management using HP SIM ".

Does this mean HP only support the Vmware ESXi 3.5 on the Internal USB key ??

- Is there any other agents available for ESXi 3.5 Update 4 (HP version > hpvm-install-hd-153875.iso ) ??

- How do we configure these ESX servers to get monitored in HP SIM 5.3 SP1 console ? I need a step by step instructions please ....

I need some assistance with this one, please !

Cheers,
Robert

[Rob Buxton]

It uses wbem to get those details.
I had a number of issues getting wbem to work. I added the credentials as server specific and used the root account & password.
At first I could ID the server with WBEM but the properties and health link failed as you have.
I finally deleted and re-added the ESXi server, rediscovered it, re-identified it and then restarted the ESXi Host server. After that it came right.
The starting point is to ensure you can ID the server and under the Edit Credentials section on the server you should see wbem as the used credential.

[Robert Babayan]

Thanks Rob...

I tried all you suggested it didnot work..." Health Status " link still not accessiable and we can not discover this HP DL 580 G5 server ??

1- I deleted the ESX3.5i host from HP SIM 5.3 SP1 console and I created a manually Discovery job to re-discover the ESX 3.5i with the credential ( login: root / password for it ) for WEBEM to use it did not discover the server. It can ping it successfully. I even tried to create a subscribe to WEBEM still did not work .. here is the result of the job below, if you want send me your email address and please let me know what other details do you need from HP SIM console so, we could hopefully reslove this issue ?

here is the results of the Discovery Job:
-----------------------------------------

ID: 59697

Status: Complete
Start time: 19/02/10 14:50
Task name: ESX Host Server Discovery Job End time: 19/02/10 14:53
Tool: System Automatic Discovery Duration: 3 min, 12 sec
Owner: OCAUS01\admin_rb Target: svmdevvire001
Run by: OCAUS01\admin_rb
Command: N/A

--------------------------------------------------------------------------------
System Name: svmdevvire001
Status: Complete

Exit code: 0
Stdout:

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 VM 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 did not respond to SNMP, verify security settings and community strin
gs.
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
The system does not support SNMP.
Running HP NetServer identification.
The system does not support SNMP.
Running HP-UX SNMP identification.
The system does not support SNMP.
Running SNMP System Type Manager identification.
The system does not support SNMP.
Checking for DMI protocol support.
DMI is globally disabled, skipping DMI identification.
Running DMI System Type Manager identification.
DMI is globally disabled, skipping DMI identification.
Running HP-UX DMI identification.
DMI is globally disabled, skipping DMI identification.
Running HP/Compaq Desktop identification.
DMI is globally disabled, skipping DMI identification.
Running HP DMI Desktop identification.
DMI is globally disabled, skipping DMI identification.
Running Generic DMI identification.
DMI is globally disabled, skipping DMI identification.
Running SSH Protocol identification.
The SSH protocol is not supported on this system
Running SSH Identification.
SSH Protocol is not detected; skipped SSH Identification
Running Storage identification.
Did not detect WBEM support on this system. Will not attempt storage identificat
ion. If this is a storage host, check WBEM credentials and make sure the provide
rs and CIMOM are operational on the host.
Storage identification completed.
Running HP Service Guard Identification.
The system is not part of HP Service Guard cluster
Running SNMP Subtypes identification
Create bare-metal device nodes if OA is discovered with "Automatic Device discov
ery" option enabled.
Create bare-metal server node if ILO is discovered with "Automatic Server discov
ery" option enabled.
Running VM identification.
VMM is installed, but the system is not a VM Host or may not be configured in VM
M
System Passes the discovery filter, system will be added.
Building system relationships.
Running limited data collection for common attribute.
The system does not have SMH or SSO support.
Running node communication diagnosis
System identification done with this system.

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

Any assistance would be appreciated to try to reslove this issue ?

Cheers,
Robert