Lost my LUN's in VMware

[symm]

I had a problem like this

I had the used a duplicate lun numbers on the Vmware side


check the link
http://communities.vmware.com/message/701181#701181

[1parkplace]

Why would you have the volumes in seperate iSCSI Targets?

The way I have it setup and the most typical way to do it would be:

On the DSS - Target0 -> Contains LUNs for all 4 volumes. LUN IDs should be 1,2,3,4 (NONE set to 0)

VMWare doesn't like when you mess with Targets, but LUNs are a little easier to mess with. Basically, if you wanted to increase the size of the volume for let's say... LUN 4, you would remove LUN 4 from that target, resize the Volume, then re-attach to the target as LUN 4 again and rescan on the ESX server.

Feel free to email me at: (drewmeyer at 1parkplace dot com) and I can exchange screenshots of my setup so you can see it firsthand.

[DickieF]

Hi Thanks for the replies.

Symm - I checked again and certainly not duplicate LUN numbers. So I don't think that was the issue but thanks anyway.

1parkplace - thanks for the info - I didn't believe what I was doing WAS playing with the targets - but evidently it must have. Certainly OPen-E support didn't see anything wrong with the config otherwise I ma sure they would have told me. But I guess there are lots of ways of doing this. I'll send you that email to get a look at the config. Cheers