SIM 6.0 problems with identifying systems.

[Rob Prince]

I have a new install of SIM 6.0 and when I run discovery on a number of my proliant dl servers I get the following message upon identify system. Any suggestions. Thanks

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.

[Rob Buxton]

HP SIM needs to get access to the servers to identify them.
It can do that in a number of ways.
SNMP - In which case community names need to be set up and the the HPSIM server added as an allowed host.
WBEM - Credentials need to be added.
These are part of the global protocol settings.

You may want to provide a bit more detail on what you've done. Have you used HPSIM before. Have you downloaded, started reading the Installation guides etc.

[Rob Prince]

The situation for us has been I was running SIM 5.3 and then our server crashed and I decided to start all over with SIM 6.0, rebuild server with Server2008, SQL2005 and installed a fresh copy of SIM6.0, upon initial discovery a number of my proliant servers we're discovered just fine, it has only been a few problem child servers that I have experienced this problem on, I do have SNMP and the community read string set. I am not sure about the WBEM becasue I read that you are either suppose to use SNMP or WBEM. I have read the installation guide and multiple other documents on this so far, just hoping to maybe find someone else who is experiencing the same thing that I am and had a solution. Thanks

[MBSNL]

I've got more or less the same thing here.
Old HPSIM 5.x, no issues other than it needs replacement.

We've got a new Server (W2008), new SQL instance. About 1800 objects have been added (mainly: ILO, BladeSystems, ProLiant) without any major issues.

About 90 objects now have this issue as reported by the original writer. None of the other objects have this issue.

Things that look OK are:
IP config, DNS forward+reverse, SNMP config, SMH Config+Trust to CMS, WMI working fine.

Any idea's?

[MBSNL]

Update:

Referring to these suggestions "http://forums11.itrc.hp.com/service/forums/questionanswer.do?threadId=1429178"

The command: wmic /node:"HOST" bios get serialnumber
is working for all systems (except 1, investigating that now) so still 89 issues not explained.

[MBSNL]

OK. Somehow I decided to enable the "WMI Mapper Proxy". That fixed another 87 system, so only 2 left out of 1800+ objects.

Can someone explain what the "WMI Mapper Proxy" will fix, that is different on these 90 original "direct" communications?

[MBSNL]

Only Windows OS 2003SP2 and above involved here.