Hp SIM and EVA6000 Data collection

[wendling]

Hello,
Can anyone help me for this problem ?
new eva6000, xcs6 connected to an admin server windows 2003 and command view eva 6.0.2.37 and HP sim 5.1.
I configured a user with cimuser utility and the storage device appeared in insight.
But when i tried to collect eva data i get the following error:


Exit code: 0
Stdout:

[SMI]
The CIMOM for this device did not respond.
Root Cause: There are many possible c
auses for this error:
o The CIMOM has been stopped;
o The system on which the
CIMOM is running is down;
o There are problems with the network between the cen
tral management server (CMS) and the system with the CIMOM;
o The CIMOM has bee
n moved to a different system or port;
o The CIMOM, or underlying element manag
er, is no longer managing this device.;
Corrective Action: Ensure that the CIMOM
is running on the expected system and port, managing this device, and that it is
reachable via the network from the CMS.
[SMI]

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

Thank's in advance.
gerard

[Jimmy Rueedi · Accepted solution]

Hi Gerard

Did the same today...

Did you upgrade the CommandView EVA?
Did you configure a WMI Proxy for this purpose while th older version was running?

My suggestions (maybe is not all needed, but I get it working today)
1.) Follow the suggestions in this thread: http://forums1.itrc.hp.com/service/forums/questionanswer.do?threadId=1069512

If no success with the WBEMDisco.cmd proceed wiht the following steps:

2.) Assign a Domain User or Group to the local User Group "HP Storage Users" and / or "HP Storage Admin" (could also be the local admin of your managment station where CVE runs)
3.) Restart the "HP StorageWorks SMI-S CIMServer" on the management station

Post the output of WBEMDisco, if it doesn't run successfully.

Regards
Jimmy

[wendling]

Thank' Jimmy,

I upgrated CV EVA from 6.0.0.193 to 6.0.2.37.
Here is the result of wbemdisco:

C:\Program Files\HP\Systems Insight Manager>echo 11/06/2007 10:37:42,66
11/06/2007 10:37:42,66

C:\Program Files\HP\Systems Insight Manager>echo off
WbemDisco 01.00.01
------------------
Gui: Gui starting
Gui: Creating frame...
HOST = 10.131.5.80
PORT = 5989
NAMESP = root
USER = administrateur
PASSWD = *****
Connect to 10.131.5.80 in namespace root with SSL=true
*** Error connecting with SSL=true - CIM_ERR_INVALID_CLASS: The specified class does not exist (CIM_ERR_INVALID_CLASS) ***

Any idea for this error?
Gérard

[Jimmy Rueedi]

Try root/pg_interop

[Jimmy Rueedi]

No, unfortunately.
sorry.

As I know "root/pg_interop" should be the correct namespace for the EVA 6000.

Did i mention, that you don't need to create a user with the cimuser tool?

CVE 6.0.2 uses Windows authentication.

So you can choose, to use a local server admin (or user) and also a domain user.

-->
You have to insert this user into the local user group "HP Storage Admins" and "HP Storage Users" (I inserted in bth groups the same users, also the local admin)

Regards

[Rob Buxton]

Just to confirm a few things;
10.131.5.80 is the IP address of the server that has CommandView EVA installed?
administrateur is the name of the smi-s account - the default would be administrator. You would need to have set up this account in SMI-S using the CIMAUTH command.
You don't have any other SMI-S components installed on this server?

[wendling]

Thank's for the answers.
10.131.5.80 is the Command View EVA server,
administrateur is the SMI-S account, thisa ccount has also been configured in the WBEM section of "global protocol settings" in insight and as a cim user.
As i said the storage appears in insight but the collections don't work.

Gérard.

[Rob Buxton]

Rather than have the account in the global settings, try using the system specific settings and override the global wbem and use the account you've set up.
You'll still need wbem enabled globally.

[wendling]

Hello,

I have the same problem on another site with CVEVA 7.0, SIM 5.1 sp1.
Is this supported on the same server?

Here is the output of wbemdisco:

C:\Program Files\HP\Systems Insight Manager>echo 17/10/2007 11:40:03,05
17/10/2007 11:40:03,05

C:\Program Files\HP\Systems Insight Manager>echo off
WbemDisco 01.00.01
------------------
Gui: Gui starting
Gui: Creating frame...
HOST = 130.1.1.1
PORT = 5989
NAMESP = root/pg_interop
USER = glc\administrateur
PASSWD = *****
Connect to 130.1.1.1 in namespace root/pg_interop with SSL=true
*** Error connecting with SSL=true - CIM_ERR_INVALID_NAMESPACE: The target namespace does not exist: "IDispatch error #3598" (CIM_ERR_INVALID_NAMESPACE) ***


and the output of a data collection:

SMI]
The CIMOM for this device did not respond.
Root Cause: There are many possible causes for this error:
o The CIMOM has been stopped;
o The system on which the CIMOM is running is down;
o There are problems with the network between the central management server (CMS) and the system with the CIMOM;
o The CIMOM has been moved to a different system or port;
o The CIMOM, or underlying element manager, is no longer managing this device.;
Corrective Action: Ensure that the CIMOM is running on the expected system and port, managing this device, and that it is reachable via the network 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.




Data collection was skipped for this system because the previous collection occurred within the DataCollectionMinIntervalMinutes setting.
Root Cause: The target system has already been data collected recently.
Corrective Action: Check the following setting (and adjust values as needed) using mxglobalsettings: DataCollectionMinIntervalMinutes (default is 15 minutes), or just re-collect after the interval has expired.


Please help!
What am i missing ?
What am i doing wrong?

Thank's in advance.
Gerard

[wendling]

Hello,

I have the same problem on another site with CVEVA 7.0, SIM 5.1 sp1.
Is this supported on the same server?

Here is the output of wbemdisco:

C:\Program Files\HP\Systems Insight Manager>echo 17/10/2007 11:40:03,05
17/10/2007 11:40:03,05

C:\Program Files\HP\Systems Insight Manager>echo off
WbemDisco 01.00.01
------------------
Gui: Gui starting
Gui: Creating frame...
HOST = 130.1.1.1
PORT = 5989
NAMESP = root/pg_interop
USER = glc\administrateur
PASSWD = *****
Connect to 130.1.1.1 in namespace root/pg_interop with SSL=true
*** Error connecting with SSL=true - CIM_ERR_INVALID_NAMESPACE: The target namespace does not exist: "IDispatch error #3598" (CIM_ERR_INVALID_NAMESPACE) ***


and the output of a data collection:

SMI]
The CIMOM for this device did not respond.
Root Cause: There are many possible causes for this error:
o The CIMOM has been stopped;
o The system on which the CIMOM is running is down;
o There are problems with the network between the central management server (CMS) and the system with the CIMOM;
o The CIMOM has been moved to a different system or port;
o The CIMOM, or underlying element manager, is no longer managing this device.;
Corrective Action: Ensure that the CIMOM is running on the expected system and port, managing this device, and that it is reachable via the network 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.






Please help!
What am i missing ?
What am i doing wrong?

Thank's in advance.
Gerard

[Rob Buxton]

I've not tried CV 7 as yet, but I've only attempted to install CV and HPSIM on the same server once. The experiment didn't last long. I can't remember if I found anything that says it is or isn't supported, but it didn't work for me.

[wendling]

Tank's for answering Rob,

Wbemdisco and system identification is OK now.
I just have this error when i start a data collection:
-------------------------------------------
The CIMOM for this device did not respond.
Root Cause: There are many possible causes for this error:
o The CIMOM has been stopped;
o The system on which the CIMOM is running is down;
o There are problems with the network between the central management server (CMS) and the system with the CIMOM;
o The CIMOM has been moved to a different system or port;
o The CIMOM, or underlying element manager, is no longer managing this device.;
Corrective Action: Ensure that the CIMOM is running on the expected system and port, managing this device, and that it is reachable via the network 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.
---------------------------------------------
Has somebody an idea?