VMWare host doesn't see LUN of LeftHand SAN

billdarron
billdarron used Ask the Experts™
on
I inherited a Lefthand SAN installation and have been working to figure out how it works and configure it correctly.  I hope that someone here can assist me with the configuration for our VMWare configuration.  We are running VMWare 3.5 and we need to sort out this storage solution before we upgrade to the latest version.

We need a single volume or two that can be seen by the two existing hosts we have in a VMWare cluster.  We need to add another machine to the cluster eventually, but right now we have the problem where there is not enough disk space to do anything until we expand one existing volume that is connected to the two hosts.  Also, there is a second volume that should span two hosts but doesn’t.  I can’t quite understand why because it looks like it should be configured correctly.

I have attached screen shots from the Lefthand and VMWare configurations with the hope that someone can quickly tell why this isn’t set up right and tell me the errors that prevent the two hosts don’t both see the two volumes.

Additionally, I need to know if I can simply expand one or both of the volumes (I do have space on the SAN) and also how to connect a future VMWare host to the two existing volumes.
I would be grateful if you could point me towards the best sections of documentation to read, or any other good sources of instruction.

Thanks in advance for your help.
   LefthandSAN-Configuration.pdf
Comment
Watch Question

Do more with

Expert Office
EXPERT OFFICE® is a registered trademark of EXPERTS EXCHANGE®
1.Try to rescan iSCSI Software adapter,vmhba32 on Jupiter. This should enable it to see the other LUNs if it has been provided access to them.

2.A VMFS Extent can be shared simultaneously by 32 ESX/ESXi hosts, so that shouldn't be a problem.

3.I would suggest that you take a look at iSCSI SAN Configuration guide available at the VMware website, the link for which I have updated below.
   http://www.vmware.com/pdf/vi3_35/esx_3/r35u2/vi3_35_25_u2_iscsi_san_cfg.pdf

4.A single VMFS Extent cannot be more than 2 TB in size (when block size is 8 MB). You can add as many as 32 x 2 TB extents to make a 64 TB Volume, but I suggest you not to do this since you may have SCSI reservations issue in future with this setup.

5.From Page 2 of the pdf, I can see that both Jupiter and Saturn are able to reach the SAN.

6.Please answer this query, you want 2 different VMFS datastores to be visible to both Jupiter and Saturn which are part of the same cluster.

7.In ESX 3.5, there was dependency on a service console port group when iSCSI software initiator is used. Please check whether iSCSI Port group has got access to Service Console port group on Jupiter.


Author

Commented:
Thanks arunraju.  I'll reply point by point:

1. I rescanned.  It didn't see anything different.

2. Good to know.  Thanks.  I need to look at the Lefthand documentation too in order to make sure I can see how to add additional hosts correctly.

3. Thanks for the link.

4.  I don't even have that much storage, so there is no issue there.  I do need to know if I can simply increase the size of the attached storage.

5. That certainly seems to be the case, but for some reason both LUNS are not available.

6. Correct.  One cluster, two hosts, two LUNS available to both.

7. Looks OK to me.  See attached.



jupiter-VMWare-networking.JPG

Author

Commented:
OOps, my capture missed the most important part!
jupiter-VMWare-networking2.JPG

Do more with

Expert Office
Submit tech questions to Ask the Experts™ at any time to receive solutions, advice, and new ideas from leading industry professionals.

Start 7-Day Free Trial