These types of issues tend to be SAN related, not ESX related. ESX will show what ever you give it, so if your not presenting the LUN to the hardware, ESX will not give you the results you want.
The thread you posted didn't have a solution in it because the original poster found his answer in the SAN, not in addressing ESX.
To help point you in the direction you need to go, what kind of SAN is it? FiberChannel or iSCSI? What make and model is the SAN?
Have you gone through the SAN manual on the VMWare site?
Correct, as the OP of that thread I found my issue was related to the SAN configuration. The HBA configuration mapping was incorrect in my case so I had to modify the host group settings on the SAN configuration so that the ESX servers were in the same host group.
When the SAN config is done, you rescan the Storage Adapters and the extra LUN (or LUNs) should be visible. You can setup the ESX partition on the LUN from the 1st ESX server (format it to VMFS), then when you rescan on the remaining ESX servers, the LUN should be visible in it's VMFS form.
--------------------------------------
"Insert funny comment in here!"
--------------------------------------
Thanks for the links Provogeek, that explains alot. I was confused about multiple hosts accessing the same LUN, as all my experience with FC SANs has indicated that when using Windows software you could not have more than one host assigned to a single LUN. The VMFS handles this as I learned from the link you provided.
David
This site uses cookies to help personalise content, tailor your experience and to keep you logged in if you register.
By continuing to use this site, you are consenting to our use of cookies.