SIM-S not functioning since Commnad View Upgrade

[GianMarco Occhionero]

I had Command View 8 on my management server which I upgraded to 9.1 last week. Since then the my EVA8000 is no longer visible via Systems Insight Manager 5.3 with SP1. It was working fine prior to the upgrade. I have tried unistalling and reinstalling commandview and features with no luck. I can telnet to port 5989 on the management server and running WbemDisco.cmd give the following.

Connect to 10.200.1.1 in namespace interop with SSL=true

ObjectManager.Name=HP:CxwsCimom_10.200.1.1
ElementName=HP Cxws Server
CimomVersion=
Description=HP Cxws Server

Enumerating instances of CIM_RegisteredProfile...

Profile.RegisteredName=Server
RegisteredVersion=1.3.0
ProviderVersion=
SubProfile.RegisteredName=Profile Registration
Profile.RegisteredName=SMI-S
RegisteredVersion=1.3.0
ProviderVersion=

I suspect that the uninstall of SIM-S did not occur correctly. If I delete the C:\Program Files\Hewlett-Packard\SMI-S folder it is not recreated when i reinstall Commandeview. Any ideas ?

[Bernd Theobalt]

Hi GianMarco,

is the CV-EVA installaed on the HP-SIM server or a different one?

Please do a netstat -na and look if port 5989 is in listening state. Please check, if there is an old SMI-S installation from CV-EVA < 6.0.2 is still running on that server.

Bernd

[GianMarco Occhionero]

CV-EVA is installed on a different server than HP-SIM. Port 5989 was not in the listening state and the HP StorageWorks CIM Object Manager service was missing since the upgrade. I ran InstallCxwsCimomService.bat from C:\Program Files\Hewlett-Packard\SMI-S\CXWSCimom\bin which installed the service and the server now responds to 5989 with the output I posted in my original post.

[GianMarco Occhionero]

I got a little further. I formatted and reinstalled my CommandView server. In commandview I added my SIM server certificate.

This is the output from WbemDisco.cmd

Gui: Creating frame...
HOST = 10.200.1.1
PORT = 5989
NAMESP = interop
USER = *****
PASSWD = *****
Connect to 10.200.1.1 in namespace interop with SSL=true

ObjectManager.Name=HP:CxwsCimom_10.200.1.1
ElementName=HP Cxws Server
CimomVersion=
Description=HP Cxws Server

Enumerating instances of CIM_RegisteredProfile...

Profile.RegisteredName=Server
RegisteredVersion=1.3.0
ProviderVersion=
SubProfile.RegisteredName=Profile Registration
Profile.RegisteredName=SMI-S
RegisteredVersion=1.3.0
ProviderVersion=
Profile.RegisteredName=Array
RegisteredVersion=1.3.0
ProviderVersion=9.1.0
HPVersion=EVA9.1-Dev15
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=Location
SubProfile.RegisteredName=Physical Package
SubProfile.RegisteredName=Multiple Computer System
SubProfile.RegisteredName=Block Server Performance
HPEVA_StorageSystem.Name="50001FE1500BE480",CreationClassName="HPEVA_StorageSy
stem"
NameSpace = root/eva
Vendor=HP
Name=EVA
IdentifyingNumber=50001FE1500BE480

My command view server and EVA show up in SIM, though the EVA does not have any information visible in SIM, ports, storage information, etc.

[Rob Buxton]

That last bit may be populated from the data collection task. I think that runs on discovery and weekly. As it was already discovered it may not have run yet.

[GianMarco Occhionero]

I still have the issue. When SIM runs its initial data collection on the EVA it fails with the following error.

[SMI]
An unexpected error was encountered in the middle of communication with the CIMOM.
Root Cause: Unknown; but some possibilities are
o The CIMOM stopped running;
o The system on which the CIMOM is located was shut down;
o Network problems between the central management server (CMS) and the CIMOM;
o Unexpected error within the CIMOM itself.
Corrective Action: Make sure that the CIMOM is running and responding to requests from the CMS.

[SMI]

An error occurred connecting to this system with the WBEM protocol. Check the system configuration.
Root Cause: Identification determined that WBEM is supported on this system, but either accessing it via WBEM, or maintaining a WBEM connection to it, failed.
Corrective Action: Check network and configuration of target system. Check the following pages to ensure appropriate WBEM credentials and port number data are provided: Global Protocol Settings, System Protocol Settings. Rerun Identification and Data Collection.

The collection on the commandview server is successful.