SIM 5.2.2 SMI-S / CIMOM issues

[Miika T]

I have SIM 5.2.2 and Command View 8.02 installed in W2K3 x64 bl460c. I've modified the cimserver_planned.conf and wbemportlist.xml to fix the overlapping wbem ports (see attachment).

The problem seems to be that whenever I try to run identify on a server that has SMI-S providers installed, SIM doesn't seem to find it. On the local server where CV is installed or on remote server where I have MSA SMI-S provider, I get this are the identify result:

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 VMware ESX 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.
Checking for SSH protocol support.
The system supports SSH protocol
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.
The system is not part of HP Service Guard cluster
Checking if this system is supported by Insight Power Manager.
Insight Power Manager is supported.
Running VM identification.
VMM Integration is not enabled, skipping VM Identification
Building system relationships.
Running limited data collection for common attribute.
Done with limited data collection, checking retrieved data.
The SSH is not configured on this system
SMH trust status is true.
Running node communication diagnosis
System identification done with this system.

Any advice what I am missing or doing wrong here?

-MiikaT

[Miika T]

I noticed that the SIM config lacked one "/" in the xml config:



This resolved the issue of not seeing the local EVA, but the remote MSA SMI-S/CIMOM
is still not recognized by SIM identify.

-MiikaT

[JKytsi]

When we installed cv 8.02 I noticed that the SMI-S/wbem usename that SIM previosly used had changed to username/password we use to log in to CV eva.

[Jeff La]

MiikaT, I have the same issue, where is the name of the xml file you added the slash to?
My new server with withthe latest greatest software is working pretty good but it won't always identify new servers even though WBEM is correct and I have snmp enabled.
Did you find anything else

Jeff

[Miika T]

Jeff,

I fixed the wbemportlist.xml, see attached (working?) versions. SIM seems to find the local CV, but the remote MSA is still not identified, even though wbemdisco returns valid data:

C:\Program Files (x86)\HP\Systems Insight Manager>WbemDisco.cmd remote-server

C:\Program Files (x86)\HP\Systems Insight Manager>echo Tue 02/10/2009 16:12:02.3
9
Tue 02/10/2009 16:12:02.39

C:\Program Files (x86)\HP\Systems Insight Manager>echo off
WbemDisco 01.01.00
------------------
HOST = remote-server
PORT = 5989
NAMESP = root
USER = administrator
PASSWD = *****
Connect to remote-server in namespace root with SSL=true

ObjectManager.Name=service:wbem:https://192.168.2.72:5989
ElementName=HPCIMObjectManager:192.168.72:5989
CimomVersion=1.0.3.10
Description=CIM Object Manager for WBEM-based HP providers

Enumerating instances of CIM_RegisteredProfile...

Profile.RegisteredName=Array
RegisteredVersion=1.0.3
ProviderVersion=1.0.3.0
SubProfile.RegisteredName=ExtraCapacitySet
SubProfile.RegisteredName=Cluster
SubProfile.RegisteredName=Software
SubProfile.RegisteredName=PoolMCS
SubProfile.RegisteredName=DiskDrive
SubProfile.RegisteredName=LUNMappingMasking
SubProfile.RegisteredName=LUNCreation
SubProfile.RegisteredName=ExtentMapping
HPMSA_ArraySystem.CreationClassName="HPMSA_ArraySystem",Name="500508B300944440
"
NameSpace = root/hpmsa
Vendor=HP
Name=MSA1500 CS
IdentifyingNumber=500508B300944440
Profile.RegisteredName=Server
RegisteredVersion=1.0.3
ProviderVersion=

C:\Program Files (x86)\HP\Systems Insight Manager>

-Miika T