Win2003 does not see VDISK's

[Goossens_1]

Could not find the answers on the forum:

2003 server, Openview 8, emulex LP9002 (using the correct driver version)
No zoning on the switch (disabled it)
EVA 5000


Can create VDISK's and manage them with OpenView.

Used SmartStart CD to setup EVA, ERROR:
VDS 9002, getdiskinterface failed

Thanks,

[Uwe Zessin]

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.

[Goossens_1]

ok big typo !
off course I mean: Commandview 8, sorry

Did not know that Smartstart was limited!

This is the error that I get from smartstart:
VDS 9002, getdiskinterface failed

But, how do I get the OS to recognize them without smartstart then ?

will get a screenshot later.

I am using MPIO from HP, should I start using the Microsoft one.

[Uwe Zessin]

Let's start with some basics:

- do you see the EVA controller devices or some unknown devices in the Windows device manager?

- can you open Command View EVA? Do you 'see' the EVA?

- has the EVA already been set-up ('initialized' = given a name)?

[Goossens_1]

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.

[Uwe Zessin]

Ah, that's good to hear...

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.

[Goossens_1]

presentation is also done, did not do a scan for new disks ...... must say I really missed that one on my list ! Will try now.

thanks

[Goossens_1]

just did a rescan: no new disks !

(even after a restart it did also not see the disks).

[Goossens_1]

ok, it looks like I did setup everything correctly and that the problem apperently is the Emulex HBA adpater not presenting the disk to the OS.

HBAnywere shows that I am connected to the eva, but I do not see the disk's !

[Víctor Cespón · Accepted solution]

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.