hi folks -- we sometimes have issues with vmotioning some VMs with in a cluster - with the error - "Virtual Disk 'X' is a mapped direct access LUN that is not accessible"
upon further digging - we found that this is possibly due to VML ID conflicts - my question to the experts here is - how is the VML ID calculated ? Is it based on the ID given by the SAN array + the time the LUN is presented the ESX host ? if it based on the presentation time - it will seriously break the elasticity of the farm - because as hosts are dynamically added and deleted the VML ID keep changing for the luns - there by causing the migration issues
please advise
thanks,
~Sai
PS: I have already checked the kb 1016210
