Hi ,
I have 6 esxi 5.0 in one cluster. I created one data store on one of the host and then did rescan for vmfs volumes on other hosts in cluster.
but some how that data store is not visible to other hosts in cluster.
because of this reasonr i cant do vmotion of vms running on this host.
Please share your thoughts.
I am under the assumption this isn't storage local to the server correct? Have you double checked that the lun presented to the hosts correctly on the backend storage array?
Do you see the device under the storage adapters -> devices?
Hi Marc,
I have checked with my storage admin. luns are properly masked to hosts and i do see under storage devices.
These hosts are in productions and due to running vms on it i cant delete datastore and provision it again.
varoon wrote:
Hi Marc,
I have checked with my storage admin. luns are properly masked to hosts and i do see under storage devices.
These hosts are in productions and due to running vms on it i cant delete datastore and provision it again.
so on the other hosts you see the path in your storage devices?
ask your stoarge admin to make sure that the lun is set to read write from mupltiple initiators.
sometimes admins forget.
I wouldnt worry about deleting the datastore this sounds like a host/storage issue.
Be sure that you have chosen the correct lun when you created the datastore and not inadvertantly used local storage.
What make of Storage Array are you using and what protocol (iscsi/fc etc).
If using fc then fc switch zoning may need checking as well as lun masking on the storage array.
Do you have any other datastores connected from this Storage Array to your ESXi hosts - if so ask the storage admins to cross check the settings between the working datastores (luns) and the new one that you are having issues with.
If not consider also 'scanning for new storage devices as well as new VMFS volumes.
Ask the storage admins to confirm that they are seeing the initiators (fc or iscsi) from your ESXi hosts successfully connecting to the Storage Array, once confirmed connectivity between the ESXi hosts and Storage Array is confirmed you can begin to narrow down the problem,
Gav