Cannot identify hp sim agents/clients

[Ian Campbell2009]

I am unable to indentify about 1/2 of my windows 2003 hp dl380 servers. When I attempt to run the configure/repair agents it just sits there forever and if I run an indentification I get errors as shown below.

Any help would be really appreciated. I've tried manually installing the psp on the server locally and also installing the hp wbem agents but the hp sim server still can't communicate them them. I don't know what else to try.


Windows configuration command (START)...
Configuring SSH authentication (START)...
SSH is not installed on the target server. In order to install SSH, use a web b
rowser to browse to HP Systems Insight Manager, select Deploy from the menu, sel
ect Install OpenSSH, and follow instructions."


Set Trust relationship to "Trust by Certificate" (START) ...
Set Trust relationship to "Trust by Certificate" (DONE)............. [SUCCESS]
Added this instance of HP SIM to the trusted certificate list for System Managem
ent Homepage 2.0 or later.


Setting SNMP read community string (DONE)............................[SUCCESS]
Setting SNMP READ-WRITE community string (DONE)......................[SUCCESS]
Setting SNMP trap destination (DONE).................................[SUCCESS]
Update SNMP setting to accept SNMP requests from the HP SIM instance.[SUCCESS]
Successfully restarted necessary web based management applications to ensure tha
t all successful changes will be effective.
Running the Windows based repair tool (DONE).......................... [ERROR]
Additional details above.

Configuring SSH authentication (START)...
Configure SSH for host based authentication (DONE).................. [FAILED]
Configuration failed to complete due to the following exception:
Connection
to the target system failed due to Connection refused: connect.Target system mig
ht be down or does not have a SSH server. The network connection problem could a
lso cause this issue.

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.


Starting identification process...
Checking for known running web servers.
Checking for System Management Home Page and other HP web agents.
Received a response from the system management homepage, this system supports SMH.
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 strings.
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 identification. If this is a storage host, check WBEM credentials and make sure the providers and CIMOM are operational on the host.
Storage identification completed.
Running HP Service Guard Identification.
Running SNMP Subtypes identification
Create bare-metal device nodes if OA is discovered with "Automatic Device discovery" option enabled.
Create bare-metal server node if ILO is discovered with "Automatic Server discovery" option enabled.
Running VM identification.
VMM Integration is not enabled, skipping VM Identification
Building system relationships.
Running limited data collection for common attribute.
SMH trust status is false.
Running node communication diagnosis
System identification done with this system.

[Rob Buxton]

I'd check SNMP on one of the servers. Verify the HOSIM Server has been added as an allowed host and that the RO Community name matches that being used for identification.

HPSIM can ID a server with just SNMP.

If they seem correct you may want to verify there are no firewalls etc. blocking SNMP access from teh HPSIM Server.

One of the ways I test this is to go to Options->Manage System Types and try adding a new server using the IP address of one of the problem servers.
If you cannot get a response then it indicates SNMPisn't getting through.