SIM 5.0 and EVA SMI-S integration?

[Ole Thomsen_1]

This is driving me nuts!

I've tried to monitor our EVA in HPSIM since CVE 4.0, now using Command View 4.1.1 and SMI-S 4.1.1 - no luck.

Command View and SMH is working fine running on a blade server, but no matter what WBEM username/password I use there is no connection from HPSIM to EVA3000.

How do I troubleshoot this?

Ole

[ICT System]

Hi Ole,

Same problem here. SIM 5, CVE 4.1.1.3, SMI-S for CVE version 4.1.1.

Protocol settings for snmp & wbem is ok.

Any hints and tips are most welcome.

Thanks,

Raymond

[Richard_244 · Accepted solution]

Hi,

Have you tried setting up the smi-s cimom username and password.

C:\Program Files\Hewlett-Packard\SMI-S\cimom
To list the available groups and users, execute this command:
$ UserAccountsManager -LG

To change the user password, execute this command:
$ UserAccountsManager -CP -U -O -N
where:
â ¢ U is the username.
â ¢ O is the old password of the user.
â ¢ N is the new password for the user.



Test the Provider Installations

After you have installed HP SIM 5.0, you can test each provider installation as follows:

1.Open a DOS window on the Central Management Station (CMS â where HP SIM 5.0 was installed).

2.Set the current directory to â ¦/Program Files/HP/Systems Insight Manager/.

3.For each provider installed, type wbemdisco

where

is the IP address or DNS name of the SMA or PC on which the SMI-S provider has been installed;

is the port on which it is running (the default is 5989);

is the â interoperabilityâ namespace of the provider (the default for HP devices is â rootâ );

is the user name giving access to the data available from the provider (the default for HP devices is â administratorâ );

is the corresponding password giving access to the data available from the provider (the default for HP devices is â administratorâ ). See details below on how to change the password.



4.You should see output that looks like this:



HOST = coresma2

PORT = 5989

NAMESP = root

USER = administrator

PASSWD = *****

Connect to coresma2 in namespace root with SSL=true



Enumerating instances of CIM_RegisteredProfile...



Profile.RegisteredName=Array

Profile.RegisteredVersion=1.0.2

ProviderVersion=4.0

Profile.HPVersion=EVA4.0.0-Dev25

SubProfile.RegisteredName=SNIA:Software

SubProfile.RegisteredName=SNIA:Pool Manipulation Capabilities and Settings

SubProfile.RegisteredName=SNIA:Backend Ports

SubProfile.RegisteredName=SNIA:LUN Mapping and Masking

SubProfile.RegisteredName=SNIA:LUN Creation

SubProfile.RegisteredName=SNIA:Copy Services

SubProfile.RegisteredName=SNIA:Access Point

SubProfile.RegisteredName=SNIA:Location

SubProfile.RegisteredName=SNIA:Cluster

HPEVA_StorageSystem.CreationClassName="HPEVA_StorageSystem",Name="50001FE150014420"

NameSpace = root/eva

Vendor=HP

Name=HSV100

IdentifyingNumber=50001FE150014420



This example shows one EVA array being reported on by the provider.


Lastly you may need to go to the SIM options and register for WBEM events from the server that runs the smi-s provider.


Regards

Richard Harris

[Ole Thomsen_1]

Thanks a lot Ríchard, this is very useful information.

My password/username is OK.

Wbemdisco:
With SSL=true I receive an error, after that the script connects with SSL=false and receive all info.

Running Windows 2003 SP1 on both HPSIM and EVA manager server.

Ole

[ICT System]

Richard,

Thanks for the help. Here is the output:

HOST = sa-iib00-08
PORT = 5989
NAMESP = root
USER = administrator
PASSWD = *****
Connect to sa-iib00-08 in namespace root with SSL=true

Enumerating instances of CIM_RegisteredProfile...

Profile.RegisteredName=Array
Profile.RegisteredVersion=1.0.3
ProviderVersion=4.1.1
Profile.HPVersion=EVA4.1.1-Dev6
SubProfile.RegisteredName=SNIA:Software
SubProfile.RegisteredName=SNIA:Pool Manipulation Capabilities and Settings
SubProfile.RegisteredName=SNIA:Backend Ports
SubProfile.RegisteredName=SNIA:LUN Mapping and Masking
SubProfile.RegisteredName=SNIA:LUN Creation
SubProfile.RegisteredName=SNIA:Copy Services
SubProfile.RegisteredName=SNIA:Access Point
SubProfile.RegisteredName=SNIA:Location
SubProfile.RegisteredName=SNIA:Cluster
HPEVA_StorageSystem.CreationClassName="HPEVA_StorageSystem",Name="50001FE150021B70"
NameSpace = root/eva
Vendor=HP
Name=HSV100
IdentifyingNumber=50001FE150021B70
Profile.RegisteredName=Server
Profile.RegisteredVersion=1.0.2
ProviderVersion=
Profile.HPVersion=

So this seems to work.

I deleted the host running the smi-s components and rediscovered it. The system showed up but not the EVA3000 array.

Any suggestions?

Regards,

Raymond

[ICT System]

Thanks for the help. SIM just reported the storage array.

Regards,

Raymond

[Richard_244]

Raymond,

Don't forget to register for wbem events.
Options->events>subscribe to wbem events->select host that runs the provider.

Sample information that is available with a registered EVA is included.



Regards
Richard Harris
HP Qld, Australia

[Richard_244]

The issue I'm trying to resolve is when I do discover the EVA in SIM, sometimes it has ? state for a number of weeks before eventually it comes back with a green tick status, this is despite the fact that from SIM I can see all of its ports and storage and that I'm receiving wbem events when they occur on the array.

Can anyone suggest how to speed up the change from a ? to a tick?


Regards

Richard Harris

[Ole Thomsen_1]

I just reinstalled SIM, but this did not solve my problem with SMI-S....

wbemdisco still gives me the attached result.

It seems that the ssl connection fails, but fallback to non-ssl gives the correct output.

Furthermore i get the following error when subscribing to WBEm events:

Host URL to connect to is = https://172.17.2.30:5989/cimom

FAILED to create indication subscription.

Any help is appreciated.

Ole

[Joel Rubenstein]

Ole,

You are not trying to run the EVA SNI-S provider on the same server that is running SIM? This causes a port conflict since the WMI Mapper also listens on port 5989

[Ole Thomsen_1]

Thanks Joel,

no the provider is installed on our EVA SAN Management server, which does not run SIM.

It seems to me that the SMS does not accept the ssl connections on port 5989, but haven't got a clue why.

Ole

[Joel Rubenstein]

Have you used a utility like tcpView from
http://www.sysinternals.com/Utilities/TcpView.html

to verify that it is the EVA SMI-S provider actually listening on port 5989?

[Ole Thomsen_1]

Yes, i used netstat to verify that the service is listening on port 5989, and just to make sure that wbemdisco is communicating to this port i also ran netstat while running wbemdisco.

This part is ok :-)

Ole

[Ole Thomsen_1]

I reinstalled hpSMISEVA_4_1_1 (again) and now wbemdisco succeeds and our EVA shows up in HPSIM :-)

However, WBEM event subscription still fails, but I will open a new thread about this specific problem.

Thanks to everybody!

Ole