Can't see any SAN in Insight?

[ClausAndersen]

We'll i found something disturbing but i still can't get it to work.

If i install SMI-S 5.0 and run the "WBEMAUTHCHECK host post namespace user password v 5" and "WBEMDISCO host post namespace user password" i actually get the following showing the correct return.

C:\Program Files\HP\Systems Insight Manager>WbemAuthCheck.cmd mgmt01 5989 root/p
g_interop administrator administrator v 5

C:\Program Files\HP\Systems Insight Manager>j2re\bin\java.exe -Dorg.snia.wbem.ci
mom.properties=./WbemTools.properties -classpath .;./lib/dc.jar;./lib/mx.jar;./l
ib/cimclient.jar;./lib/xerces.jar;./lib/wbemutil.jar -mx400m -ms400m WbemAutho
rizationCheck mgmt01 5989 root/pg_interop administrator administrator v 5

TESTING CREDENTINALS VIA MxWBEMConnect::checkAuthorization() ....


Testing with
host: mgmt01
port: 5989
protocol: https
namespce: root/pg_interop
verbosity: 5
user: administrator
password: *******

Checking authorization in device namespaces for mgmt01 under ns=root/pg_inter
op for user=administrator
Trying to connect to CIMOM at: mgmt01 under ns=root/pg_interop for user=administ
rator
SUCCESS


Found the following device namespaces:
root/PG_Internal
root/cimv2
root/eva



Checking Authorization in namespace: CIMNameSpace=root/PG_Internal [host mgmt01]

CIMException retrieving instance of CIM_ComputerSystem.

Checking Authorization in namespace: CIMNameSpace=root/cimv2 [host mgmt01]
SUCCESS

Checking Authorization in namespace: CIMNameSpace=root/eva [host mgmt01]
CIMException retrieving instance of CIM_ComputerSystem.
Authorization Check Succeeded for: mgmt01 under ns=root/pg_interop for user=adm
inistrator

AUTHORIZATION CHECK PASSED


C:\Program Files\HP\Systems Insight Manager>pause
Press any key to continue . . .

C:\Program Files\HP\Systems Insight Manager>popd

C:\Program Files\HP\Systems Insight Manager>endlocal

C:\Program Files\HP\Systems Insight Manager>WbemDisco.cmd mgmt01 5989 root/pg_in
terop administrator administrator
HOST = mgmt01
PORT = 5989
NAMESP = root/pg_interop
USER = administrator
PASSWD = *****
Connect to mgmt01 in namespace root/pg_interop with SSL=true

Enumerating instances of CIM_RegisteredProfile...

Profile.RegisteredName=Array
Profile.RegisteredVersion=1.1.0
ProviderVersion=5.0
Profile.HPVersion=EVA5.0-Dev28
SubProfile.RegisteredName=SNIA:Software
SubProfile.RegisteredName=SNIA:Pool Manipulation Capabilities and Settings
SubProfile.RegisteredName=SNIA:Job control
SubProfile.RegisteredName=SNIA:Physical Package Package
SubProfile.RegisteredName=SNIA:Backend Ports
SubProfile.RegisteredName=SNIA:Masking and Mapping
SubProfile.RegisteredName=SNIA:Disk Drive Lite
SubProfile.RegisteredName=SNIA:FC Target Port
SubProfile.RegisteredName=SNIA:Fibre Channel Initiator Port
SubProfile.RegisteredName=SNIA:LUN Creation
SubProfile.RegisteredName=SNIA:Copy Services
SubProfile.RegisteredName=SNIA:Access Point
SubProfile.RegisteredName=SNIA:Location
SubProfile.RegisteredName=SNIA:Multiple Computer System
SubProfile.RegisteredName=SNIA:Block Server Performance
HPEVA_StorageSystem.CreationClassName="HPEVA_StorageSystem",Name="50001FE15008
E190"
NameSpace = root/EVA
Vendor=HP
Name=EVA
IdentifyingNumber=50001FE15008E190
HPEVA_StorageSystem.CreationClassName="HPEVA_StorageSystem",Name="50001FE15008
E180"
NameSpace = root/EVA
Vendor=HP
Name=EVA
IdentifyingNumber=50001FE15008E180
Profile.RegisteredName=Server
Profile.RegisteredVersion=1.1.0
ProviderVersion=
Profile.HPVersion=
Press any key to continue . . .


But it doesn't come in to HP SIM anyway. Then when i try to update to SMI-S 5.01 it stops working with the error in WBEMDISCO again.
If you do this you might note the update from 5.0 to 5.01 has to be run like 4-5 times to completely update the SMI-s and PEgasus components.
Allso when i use 5.0 it doesn't allways start the Pegasus service after a server restart.
I really think theres software bugs here i can't explaine it in any other way, but i hope one of you guys might get further with this newfound info.

I'm gonna try not using SSL even though it's not supported by HP.

[ClausAndersen]

Nope running with no SSL gives the exact same outcome. So thats not the problem.

[Daniel Leblanc]

Still no one got anything!!!

[ClausAndersen]

No :(

I'm running a case with HP, but they haven't come up with anything usefull yet.
I just installed a brand new server and tried the it - same problem (completely new customer).
I have ask the HP guy to elevate the problem to the Pegasus programming guys.

Info: Command View EVA 6.0 and XCS6.0 will be coming soon (10. september). It might solve the problem. But i don't know if the SMI-S component gets upgraded or not.

[Daniel Leblanc]

TY!!

[Rob Buxton]

You're getting further than me with the WBEMDisco, it fails with the following in the first section.

SubProfile.RegisteredName=SNIA:Block Services
*** Error following [RegisteredProfile] --ElementConformsToProfile-> [ComputerSy
stem] - Connection reset (CIM_ERR_FAILED) ***

I've confirmed the account / password using webAuthCheck.

Not sure if it's relevent, the version as recorded by my connect is;
Profile.HPVersion=EVA5.0.1-RC5

If you're getting that level of connectivity HPSIM should be able to see and pick up the data. You'd need the WBEM credentials that you've used in the wbemauthcheck entered as teh Server Specific WBEM settings for the CV EVA Server. A Discovery should then be enough.

[ClausAndersen]

just to follow up. I just found this from the Command View EVA 6.0 product bulletin.

HP StorageWorks Command View EVA v6.0 Media Kit includes four CDs with on-line documentation and software executables; and installation Instructions. 1 CD for Command View EVA software (includes SMI-S EVA 6.0 provider) and HP SSSU, 1 CD for documentation, 1 CD for Command View EVAPerf software V6.0 and 1 CD for the HP System Tool CD ISEE and WEBES.
NOTE: Please refer to HP.com for the latest HP Command View EVAPerf software updates.

So it seems there will be a new provider component soon. I guess i'll stop for now until this arrives, which should be VERY soon.

[Kevin Everts_1]

Rob,

I'm trying to set this up on my EVA 3000 with CommandView 5.0 installed.

I have a question about your post on Aug 22, 2006 23:35:52 GMT.

Where do you specify root/pg_interop in CV EVA 5?

[ClausAndersen]

Last week HP told me to try an older version of the HP SIM. So i tried the HP SIM5.0 with the integrated SP3. I did it with the SMI-S5.0, and this actually seems to work. I got my 2 EVA systems back into HP SIM and i could do a succesfull data collection.

I just have one problem remaining, the status keeps saying "unknown" even though i can see and gather data from them. I haven't tried finding a solution since the customer kindof fucked up the machine and removed my test environment.
I'll try to see if CV EVA and SMI-S 6.0 works with HP SIM 5.0 SP3 when it gets out.

So it does seems like there's problems with both the SMI-S 5.01 and HP SIM5.0 SP5 code.

[Rob Buxton]

Keith,
Sorry missed the question, the pg_interop is set up as part of CV EVA, you just use this in the wbemdisco call described above. This changed with SMI-S 5 I believe, I think it was just root with SMI-S,

Claus,
Interesting, but I did have SMI-S working with HPSIM 5.0, and I believe it was using SMI-S 5.0.1 although it may have been just 5.0.
The issue we have at the moment is that the SMI-S connection crashes the Pegasus CIMOM service on the CV EVA server. The service is set to restart but you can see events and the restart in the PegasusStandard log file.

Soon I'll be building a brand new CV EVA server, so that will be interesting to see what happens.