VMWare host doesn't see LUN of LeftHand SAN

[William Darron]

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.

[Steven Clementi]

Can you check the properties of the VMHBA32 adaptor. Check to see if you can see the proper log in's on the adaptor.

I don;t have a 3.5 environment anymore to be able to tell you exactly where to look... but the properties sheet should have multiple tabs... general, dynamic, and static...maybe others.


For Expanding... it might be easier to just create an additional disk. You can certainly expand an existing disk... you would then have to go to the OS and extend it on the properties page.

In the future, when adding additional hosts, copy the existing configuration from one of the servers (manually) and assign a new Ip address to the new server's vmkernel for iSCSI port. Check the properties of the vmhba32 of the new server to get it's "IQN" id... then add it to the storage via the CMC.

You can than assihn disks to it.


Steven

[William Darron]

Upon investigation I found this:

Our SAN cluster is named GEMINI. The two nodes are CASTOR and POLLUX. I believe that it was configured incorrectly.

Right now the configuration has the IPS of:

GEMINI 192.168.3.50
CASTOR 192.168.3.50
POLLUX 192.168.3.11

This canâ t be correct. I believe that the CASTOR node should be configured as 192.168.3.12 or something like it.

I need to know what the impact of changing this IP is and how best to go about doing it.

[Steven Clementi]

You would change the iSCSI address in the properties for the vmKernel for iSCSI.

You can find this by clicking on the server in vCenter, or in the VI Client. Find the Configuration tab in the right window pane and click on the Networking menu item.


Steven