Newbie - EVA3000/Secure Path/ Win2k issues

[Harb_S]

I'm a newbie to the Storage environment. I have an issue with HP EVA3000, using a Win2k Management appliance, using Securepath 4.0C to connect to the nodes.
The issue I upresented 3 vdisks (that were preseted to a two node rac cluster, running win2k3) from the "command view" before deleting the logical drives/partitions from the OS. After that the drives on the nodes. I've attached the screenshot, node1.doc
The disk drives are not visible in the Disk Manager. Is there a where of identifying these drives and deleting them.
I know more info will be required, plesae let me know.
Any help will be much appreciated. Thanks

[The Spartan]

To identify or map LUNs -

1. Reach command prompt, type
spmgr display
OR
2. Look up the disk manager and then properties of the disk. With the knowledge of wwn of the host, refer the EVA CV. It would tell you which Vdisk the host looks at.

[Bill Costigan]

I not sure exactly what you are asking.

If you unpresented the vdisks they are gone as far as the windows server is concerned.

They still exist unchanged on the EVA.

You can re-present them to the same server or a different server if you want to get back to the data on them OR delete them from the EVA if you really want them to go away. Once they are deleted, the data is lost.

If you forgot which vdisks you unpresented, you can list all vdisks presented to a particular host, or all hosts to which a particular vdisk is presented from CommandView

[Harb_S]

I've done a bit investigation and it looks like the the disk signature are getting swapped at the os level. Is there a way i.e. registry entry which can be amended/deleted.

[Harb_S]

Bill,
Answering your question. The vdisks have been unpresented/deleted from command view and they are not there on the EVA as I had expected. The issue is the OS is getting confused i.e. the disk signatures are playing up. The drive letters on the OS are getting swapped out and the drive letters assigned to the now unpresented disk are not being freed.

[Bill Costigan]

I understand now. The Windows server wants to find these disks and they aren't there anymore.

I know someone who ran into a similar problem using a microsoft cluster with exchange. The cluster wasn't stating because some of the resources were missing after the disks on the eva were recreated.

He found some instructions on the MS web about redoing the disk signatures based on what the cluster was looking for. He ended up reinstalling windows and the cluster. I don't know if that was because it was faster or because the MS proceedure didn't work as he need it to.