Server Management - Systems Insight Manager
cancel
Showing results for 
Search instead for 
Did you mean: 

Identify System fails using WBEM

Mario Schäfer
Occasional Contributor

Identify System fails using WBEM

I'm testing WBEM as an alternate to SNMP, but can't intergrate systems in HP SIM. The identify of systems over WBEM fails.

I'm using HP SIM 5.3 and have configured sign-in credentials, installed HP WBEM Providers on client manually and on another client over "Configure and Repair Agents". I've dicovered both devices before. When I run "Identify System" for both servers I'll get error messages that WBEM Support is not detected, see the complete identification log below.
The user configured in the sign-in credentials is an administrator of both clients.
If I install the System Management Homepage on the clients, I'm able to see data inventory data delivered from WBEM. However the integration in HP SIM still fails.

I've already spend hours of reading manuals and the HP Board. Seems like there are a few other users with the same problem but without a solution. Can anybody help?
______________________
Complete Identify Log:

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 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 has the SNMP ProLiant server (foundation) agents installed, adding system type.
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.
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
No additional subtypes found from SNMP
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.
The system does not have SMH or SSO support.
Running node communication diagnosis
System identification done with this system.
4 REPLIES
odavila
Occasional Visitor

Re: Identify System fails using WBEM

Mario, let me know if you ever figure this one out. I've been dealing with this exact issue for two days now.
Mario Schäfer
Occasional Contributor

Re: Identify System fails using WBEM

Hi odavila, i will post in this thread if I find a solution.

Short Update: HP SIM is in a different subnet than the two testservers, but none ports are blocked. All traffic will be submitted.

Any ideas someone? Perhaps an expert from HP can give us some help in this thread?
PNair
Frequent Advisor

Re: Identify System fails using WBEM

Have you configured a WMI mapper proxy? It is under Options->Protocol Settings WMI mapper proxy
Mario Schäfer
Occasional Contributor

Re: Identify System fails using WBEM

I've thought that the WMI-Mapper Proxy have been installed with standard installation of HP SIM, but it dont't seems so.

So I've installed the WMI-Mapper Proxy subsequently. After that, the identify of systems over WBEM was successful.