HP EVA4400 in HP SIM

[SwisspostIT]

hello,

last week we added our HP EVA4400 Storage System successfully to HP SIM.

We installed the needed Components (Management Integration Framework & SMI-S Service) from HP P6000 Command View Software Suite to our HP SIM Server and configured everything like descibed in the HP Documentation (added EVA IP Adress and Login to the "discoverer.bat" configured Ports and added to wbemportlist.xml).

In HP SIM we made a discovery Task with the EVA Credentials on our HP SIM Server and so it discovered the EVA Storage and listed it's details.

But since about one day later we don't get anymore details of the EVA, all information and status are gone...

I checked on HP SIM Server with the Wbemdisco.cmd and this gives following output:

E:\HP System Insight Manager>WbemDisco.cmd

E:\HP System Insight Manager>echo Mon 02/20/2012  9:45:07.59
Mon 02/20/2012  9:45:07.59

E:\HP System Insight Manager>echo off
WbemDisco 01.01.00
------------------
Gui: Gui starting
Gui: Creating frame...
HOST   = 10.224.160.136
PORT   = 60000
NAMESP = interop
USER   = Admin
PASSWD = *****
Connect to 10.224.160.136 in namespace interop with SSL=true

ObjectManager.Name=HP:CxwsCimom_172.25.32.120
  ElementName=HP Cxws Server
  CimomVersion=<missing>
  Description=HP Cxws Server

Enumerating instances of CIM_RegisteredProfile...

Profile.RegisteredName=Server
  RegisteredVersion=1.4.0
  ProviderVersion=<missing>
    SubProfile.RegisteredName=Profile Registration
Profile.RegisteredName=SMI-S
  RegisteredVersion=1.3.0
  ProviderVersion=<missing>
Profile.RegisteredName=SMI-S
  RegisteredVersion=1.4.0
  ProviderVersion=<missing>
Profile.RegisteredName=Array
  RegisteredVersion=1.4.0
  ProviderVersion=10.0.0
  HPVersion=EVA10.0-Dev30
    SubProfile.RegisteredName=Software
    SubProfile.RegisteredName=Masking and Mapping
    SubProfile.RegisteredName=Copy Services
    SubProfile.RegisteredName=Block Services
    SubProfile.RegisteredName=Disk Drive Lite
    SubProfile.RegisteredName=FC Target Ports
    SubProfile.RegisteredName=FC Initiator Ports
    SubProfile.RegisteredName=Job control
    SubProfile.RegisteredName=Access Points
    SubProfile.RegisteredName=Physical Package
    SubProfile.RegisteredName=Multiple Computer System
    SubProfile.RegisteredName=Block Server Performance
    SubProfile.RegisteredName=SAS Initiator Ports
    SubProfile.RegisteredName=Thin Provisioning

Does anyone have any idea what I could check in configuration or what I could try to do to get this EVA successfully integrated in HP SIM?

Thanks in advance!

[SwisspostIT]

I have some more Information.

When I run a discovery task on our HP SIM Server (which hosts the SMI-S Provider and acts in this case as the Management Server of the EVA) the output regarding SMI-S is like this:

        * Checking for WBEM protocol support on system...
Normal:   This system has at least one SMI-S CIMOM installed to serve as the
          storage proxy to discover storage systems.
Minor:    The Central Management System (CMS) cannot communicate with the
          CIMOM locally installed on the managed system using the WBEM
          protocol, Identification will try to identify Windows systems using
          the WMI Mapper as proxy; for Linux and HP-UX systems, check
          credentials by going to Options->Security->Credentials->System
          Credentials. For Linux systems also check if the HP WBEM provider
          is installed.
Critical: There are no valid WBEM / WMI credentials for the system(s).
        * Running WBEM rules based identification...
Minor:    Identification cannot get computer system hardware data from the
          WBEM / WMI providers.

I have configured the System Credentials on the HP SIM Server for WBEM Port 60000 with the used Account for the SMI-S Provider (it's the same Account with same Password for our EVA Login)