topic Re: HP SIM 6.2 installed on Windows 2008R2 x64 and Problem with Discovery/Identification with VM in Server Management - Systems Insight Manager

HP SIM 6.2 installed on Windows 2008R2 x64 and Problem with Discovery/Identification with VM

SENAC — Tue, 29 Mar 2011 14:56:43 GMT

Hi,

I have installed an HP SIM version 6.2 on OS Windows 2008 R2 x64.
I have a problem with discovery only with all my Virtual Machine on VMware ESX 4.1.
I have Status Message : Some Critical Failure with this message :
"Major: The system cannot be identified properly for HP SIM to manage;
unable to get one or more of the following: model, serial number or
unique identifier (UUID). For management processors, verify the
system is running the latest firmware. For Linux based operating
systems, you must have dmidecode installed, enable the
PermitRootLogin and PasswordAuthentication in sshd, and use root
sign-in credential. For HP-UX, verify the sign-in credential. For
Windows, check if WMIMapper is configured correctly on the CMS and
verify the sign-in credential.
Critical: HP SIM cannot communicate with these systems using the WBEM
protocol."

PEGASUS WMI Mapper 2.7 is installed.
The System Credential is OK.
The firewall are disable on my Server.
SNMP Service in my VMs is correctly configured.

I don't understand why I have this problem.
The same configuration Work on Microsoft Windows 2003 x86 with the same settings.

I think the problem is a compatibility between HP SIM6.2 and Microsoft Windows 2008R2 x64.

What is the Solution ?

Thanks for your answers...

Re: HP SIM 6.2 installed on Windows 2008R2 x64 and Problem with Discovery/Identification with VM

David Claypool — Wed, 30 Mar 2011 03:19:22 GMT

Use 'Manage Communications' to diagnose.

Re: HP SIM 6.2 installed on Windows 2008R2 x64 and Problem with Discovery/Identification with VM

SENAC — Fri, 01 Apr 2011 13:07:48 GMT

I have found my Problem.
After my installation on Windows 2008 R2, the two services : Pegasus WMI Mapper and Pegasus WMIMapper Indications Service don't start.
The error Message is 1069: The service did not start due to a logon failure.

To correct the problem, I Add the right to user "SERVICE" to "Open a session as a service" in the console gpedit.msc.

Now, the discovery is OK.