We are currently having trouble with esx3.5 u3 where by the esx server can connect to the SAN via iSCSI, it will display all of the 4 lun's but will not mount one particular LUN.
When we reverted back to 3.03 all luns are seen and mounted correcty. It would be greatly appreaciated if someone could help me or point me in the right
We have other clusters running which can mount the LUN with no problem. The LUN is formated with vmfs and does contain data of which all hosts that mount the LUN can see.
The esx host that is having this problem is contained with in a cluster, the other host in this cluster was updated to 3.5 u3 and can mount the LUN successfully. The only errors that
Thanks for replying, really appreciate it.
Have you tried to mask the LUN from the host that is having the issue and then performing a rescan from the host to be sure that it has released the LUN. Then present it back to the host and perform another rescan. Can you check the LUN id on the host compared to the others. Does it have the same LUN ID as another LUN?
Moved to ESX 3.5 forum.
Edward L. Haletky VMware Communities User Moderator, VMware vExpert 2009, Virtualization Practice Analyst[/url]
Now Available: 'VMware vSphere(TM) and Virtual Infrastructure Security: Securing the Virtual Environment'[/url]
Also available 'VMWare ESX Server in the Enterprise'[/url]
[url=http://www.astroarch.com/wiki/index.php/Blog_Roll]SearchVMware Pro[/url]|Blue Gears[/url]|Top Virtualization Security Links[/url]|Virtualization Security Round Table Podcast[/url]