Discovering EVA 5000

[Rob Mills]

I know this has been done before. I have searched and searched. I'm making headway but it's slow going.

I have an EVA 5000 connected via brocade switches. There is a Win2K3 server running CommandViewEVA version 6.0.2.37.

I have setup both a local and domain admin account and password, which I have included in my global credentials in SIM 5.3

When i run WBEMDISCO from the CMS, I get the following:

HOST = SERVER1
PORT = 5989
NAMESP = root
USER = cscsim
PASSWD = *****
Connect to SERVER1 in namespace root with SSL=true

ObjectManager.Name=service:wbem:https://x.x.250.200:5989
ElementName=HPCIMObjectManager:x.x.250.200:5989
CimomVersion=1.0.4.1
Description=CIM Object Manager for WBEM-based HP providers

Enumerating instances of CIM_RegisteredProfile...

*** Error enumerating RegisteredProfile - CIM_ERR_NOT_FOUND(Searching for hpeva_
registeredsubprofile in file C:\Program Files\Hewlett-Packard\SMI-S\cimom\persis
tence\classes\root\hpeva_registeredsubprofile) (CIM_ERR_NOT_FOUND) ***
CIM_ERR_NOT_FOUND(CIM_ERR_NOT_FOUND(Searching for hpeva_registeredsubprofile in
file C:\Program Files\Hewlett-Packard\SMI-S\cimom\persistence\classes\root\hpeva
_registeredsubprofile))
at org.snia.wbemcmd.xml.XMLOperationGeneric.processReturnStream(XMLOpera
tionGeneric.java:362)
at org.snia.wbemcmd.xml.XMLOperationGeneric.intrinsicMethod(XMLOperation
Generic.java:191)
at org.snia.wbemcmd.xml.XMLOperationGeneric.intrinsicMethod(XMLOperation
Generic.java:198)
at org.snia.wbemcmd.xml.XMLEnumerateInstanceNames.enumerateInstanceNames
(XMLEnumerateInstanceNames.java:142)
at org.snia.wbemcmd.cimom.CIMOMHandleXML.enumerateInstanceNames(CIMOMHan
dleXML.java:498)
at org.snia.wbem.client.CIMClient.enumerateInstanceNames(CIMClient.java:
1173)
at WbemDisco.getRegisteredProfiles(WbemDisco.java:305)
at WbemDisco.findDevices(WbemDisco.java:188)
at WbemDisco.main(WbemDisco.java:715)


It appears to me that I am missing some files. I have de-installed the SMI and re-installed it again. There is also a Brocade SMI and HP WBEM providers 2.30B installed.

thanks

[Rob Mills]

to continue, when discovering the Win2K3 server attached to the EVA 5000, I see the FC adapters, but not the EVA. WBEM indications from the server itself are still functioning.

thanks

[Rob Buxton]

You would need to check on some of the dependencies there. HPSIM and this version of CV are not supported on the same server. But from above that's not the case. I think there may be issues with mixing different CIMOMs on the same server. Not sure if you can have the Brocade and CV SMI-S stuff on the same host.

CV 6 is getting quite old now, you may want to look at getting the updated licenses and moving to either CV 8 or CV 9. There's been a bit more work done to allow running on the same host for some of the stuff.

[Rob Mills]

thanks Rob,

we are currently stuck on CV6.02 because of licensing. No, the CV and SIM are not running on the same server.

I was able to get wbemdisco to see the EVA just fine after I got rid of the Brocade SMI that was also running. However I am not getting any information from the EVA. HP is saying upgrade to 9, but i don't think that's going to happen.

[Rob Buxton]

With the Brocade off, are you still getting the error you originally described?
You say wbemdisco is working, if it is then HPSIM should be able to get the info.
On the HPSIM side, click on the CV Server and under Tools & Links go to System Credentials. Under wbem you should have the credentials used in wbemdisco. I use a local account on the CV server, that account must be part of one of the local HP Storage groups - I use HP Storage Admins.

[Rob Mills]

no, the error is now gone, and I have it setup the way you said. There is no information coming from the EVA.

WbemDisco 01.01.00
------------------
Gui: Gui starting
Gui: Creating frame...
HOST = s0002000
PORT = 5989
NAMESP = root/pg_interop
USER = cimadmin
PASSWD = *****
Connect to s0002000 in namespace root/pg_interop with SSL=true

ObjectManager.Name=PG:BD7E8BB9-DD99-4535-A9C0-43692F865C2D
ElementName=Pegasus
CimomVersion=
Description=Pegasus CIM Server Version 2.5.1.19 Development

Enumerating instances of CIM_RegisteredProfile...

Profile.RegisteredName=Array
RegisteredVersion=1.1.0
ProviderVersion=6.0
HPVersion=EVA6.0-RC6
SubProfile.RegisteredName=Array:Software
SubProfile.RegisteredName=Array:Pool Manipulation Capabilities and Settings
SubProfile.RegisteredName=Array:Job control
SubProfile.RegisteredName=Array:Physical Package Package
SubProfile.RegisteredName=Array:Backend Ports
SubProfile.RegisteredName=Array:Masking and Mapping
SubProfile.RegisteredName=Array:Block Services
SubProfile.RegisteredName=Array:Disk Drive Lite
SubProfile.RegisteredName=Array:FC Target Port
SubProfile.RegisteredName=Array:Fibre Channel Initiator Port
SubProfile.RegisteredName=Array:LUN Creation
SubProfile.RegisteredName=Array:Copy Services
SubProfile.RegisteredName=Array:Access Point
SubProfile.RegisteredName=Array:Location
SubProfile.RegisteredName=Array:Multiple Computer System
SubProfile.RegisteredName=Array:Block Server Performance
Profile.RegisteredName=Server
RegisteredVersion=1.1.0
ProviderVersion=



I had HP looking at it for an hour this morning. All they can suggest is:

a: upgrade (not happening) at 15k per eva
b: completely de-install/re-install CV 6.02

I will need to setup a lab machine first to do that.

[Rob Mills]

after considerable playing with permissions I managed to get time to completely de-install all SMI and CV EVA. Then I re-installed CV EVA 6.0, then re-installed CV EVA 6.02. I did not re-install the Brocade SMI. I then used cimuser and cimauth to enable a local account (that is a member of the HP Storage Admins group) on the root/pg_interop namespace.

I then deleted the server from SIM and re-discovered it with the proper credentials. it worked.

Thanks for the help.

[Rob Buxton]

Rob,
Glad to hear it's going.
I've not used the Brocade SMI stuff, it just seemed to be too complex to install and set up. How did you find it? Did it give you any useful data?

[Rob Mills]

actually have not used it. it was previously installed on these machines and not being used anywhere, so I disabled it for a time. When I got no complaints, I de-installed it.