SIM 5.3.0.0 SMI-S CIMOM not installed

[ManojR]

Hi All,

I have installed SIM 5.3 in windows 2003.
when i click on TOOLS --> IDENTIFY SYSTEM..
it is giving me following output...


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 SM
H.
Checking for WBEM support on system.
This system has WBEM protocol support
This system does not have any SMI-S CIMOM installed
This system has a server CIMOM installed
Running WBEM rules based identification.
Got 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 does not have the SNMP ProLiant Server (foundation) agents installed.
Running HP NetServer identification.
System supports the NetServer SNMP agent, adding system type
Running HP-UX SNMP identification.
System has the HPUX SNMP agents installed, adding system type.
Running SNMP System Type Manager identification.
Found matching SNMP System Type Manager rule, added as possible system type
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 system supports SSH protocol
Running SSH Identification.
This system cannot be logged in using ssh; check credentials or use a non-root u
ser
Running Storage identification.
Storage identification completed.
Running HP Service Guard Identification.
The system is not part of HP Service Guard cluster
Running SNMP Subtypes identification
No additional subtypes found from SNMP
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 Integration is not enabled, skipping VM Identification
Building system relationships.
Running limited data collection for common attribute.
The SSH is not configured on this system
SMH trust status is true.
Running node communication diagnosis
System identification done with this system.

[AF_2]

We have had exactly the same problem all week with an HP SIM Consultant on-site. We have not resolved the issue but the problem appears to lie in permissions in the CIM and HPQ namespaces.

Ensure the SIM user account is in the DCOM Administrators group on the server...Sometimes it works, sometimes it doesn't

HP, can you please get some QA on this?

WBEM on Unix doesn't have the complex permissions that WBEM/WMI has on Windows....

[David Claypool]

What is the problem? What did you expect to see that you're not seeing?

[AF_2]

Hi,

We have not been able to configure or subscribe to WBEM events. We can push-install the WBEM/WMI provider without issue and configure the CMS to subscribe to wbem events but test events don't work and we can't identify the systems successfully.

We've made the SIM global account a member of the DCOM admins, and also local admins on the servers

As soon as we swapped to SNMP everything lept into life.

The error:
This system does not have any SMI-S CIMOM installed

comes up on every system.

[David Claypool]

SMI-S (Storage Management Initiative Specification) is for SAN storage management and is an implementation of WBEM. It does not use DCOM as a transport like WMI. SMI-S is transported over HTTPS encoded in XML. For a StorageWorks EVA the SMI-S provider is CommandView EVA. It creates an 'hp-storage-admins' group that the user must authenticate to. For more information, http://www.hp.com/go/hpsim --> Providers --> SMI-S

[AF_2]

Thanks for the reply.

OK - what is required to get WBEM agents working on from a windows-based CMS to a Windows-based Endpoint and how do we test it is working ?

(probably easier to ask this question !)

Thanks

Alex