Very confusing collection of names... OpenView is an 'umbrella name', not a real product. I assume by "Openview" / "Openview 8" you mean "Command View EVA version 8".
> Can create VDISK's and manage them with OpenView.
Please be a bit more verbose - supply a screenshot (attach a .JPG) or give us the correct error message from the system.
> Used SmartStart CD to setup EVA,
Did you use "SmartStart EVA"? It is my understanding that it works in very limited environments and not neccessarily with that old hardware.
yes, EVA is innitialized, has a name and I can completely manage the EVA from Commandview (create Vdisk, folders, manage disk etc, upgrade firmware of controller and disks, etc .....).
Nothing strange in device manager (it does see the EVA as a device).
Installed to correct version of the driver for the Emulex HBA that supports EVA.
So everything is working, just can't get the OS to assign a drive letter on the management server (have not yet tried others servers that are connected to the fabric).
So all neccesary stpe (according to HP) have been done and do work.
now, a virtual disk is just an internal storage reservation and must be presented to a 'Host' first. That is done from the [presentation] tab which you can see on the virtual disk's properties page.
After that is done, your can scan for new disks from the Windows disk management.
What's the firmware version on the controllers? XCS 3.x and 4.x use different multipath software.
Do you have MPIO installed? Which version? Check in Windows Device Manager (not Disk Manager) if you see any HSV110 SCSI disk device or something like that.
Two similar cases I've seen were solved by either:
Reinstalling MPIO (was not generating the HSV110 Multipath disk devices) Configuring the preferred controller on the disk properties.
Active/active firmware implies a nice MMC plugin for multipath management and (mail) failure notification - best I have seen from the basic MPIO is some cryptic entries in the Windows event log.
What about Windows Device Manager? Do you see any "HP HSV110 SCSI Disk Device" under "Disk Drives"? That is the raw vdisk seen through 4 paths. When you install MPIO, it hides them and creates one "HP HSV110 Multi-Path Disk Device" which is what you see then in Windows Disk Manager.
That looks like basic connectivity is there and the vdisk presentation is not correct - can you supply a screen shot from the device manager (attach a .JPG - don't embedd in .DOC, please) ?
I added some vdisks the other day and I highlighted more than one to present at the same time. Although CommandView EVA saw the vdisks as presented, the host could not see them. I unpresented and then presented one at a time and the host could see them straight away....
wwn from dropdown shitchshow: all ok no zoning one switch (2 loops from controller)
Funny thing is that if I run microsoft diskraid it shows the HP HWP (version 4.xxx)and tells me the array is online and running fine !
This means the OS can communicate with the disk because Diskraid needs the HWP (VDS) for communicating with the array.
Only thing I can think of is that the HWP version 4.xxx (automatically installed by the smartstart CD) is not the correct one. Smartstart tells me it does install version 3.xxx but looks like I got 4.xxxx.
Earlier someone mentioned that I need 3.xxx because the firmeware of yhe controller is 3xxx (active/passive). Bit confused how this version 4 got on the system .....
LUN numbers are 1,2 and 3 (created 3 VDISK's), but not important for windows I believe.
will look into it tomorrow.
Thanks sofar for the good help. My first EVA (testing this by the way for mass-recording of IP-camera streams, VERY I/O intensive).
