Knowledge Base

Search the Knowledge Base:
Products:
Search In:
 

A Mapped SAN LUN Added to a Virtual Machine Is Not Visible from the List

Details

When I add a mapped SAN LUN to a virtual machine, why isn't the LUN visible in the list of LUNs from which to select?

Solution

When adding a mapped SAN LUN to a virtual machine, the desired LUN might not be visible in the list of LUNs from which to select. In some cases, the option to add a mapped SAN LUN may be unavailable even though the ESX Server system is properly connected to SAN LUNs.

When a mapped SAN LUN is added to a virtual machine, it becomes unavailable for use by other virtual machines within the same ESX Server system. When the list of available LUNs appears, only LUNs not in use by any other virtual machine are displayed. When all available LUNs are in use by other virtual machines on the ESX Server system, the option to add a mapped SAN LUN is unavailable.

Remove the desired mapped SAN LUN from all other virtual machines on the ESX Server system before adding it to another virtual machine. For sharing LUNs between virtual machines on a single ESX Server machine for the purpose of running a Microsoft MSCS cluster, refer to Setup for Microsoft Cluster Service (http://www.vmware.com/pdf/vi3_vm_and_mscs.pdf).
 
Note: This issue is resolved in ESX Server 3.0.1.

Keywords

2216; urlz; esx301; vi3relnotes

Feedback

Rating: 1 - Lowest 2 3 4 5 - Highest (0 Ratings)   

Did this article help you?
This article resolved my issue.
This article did not resolve my issue.
This article helped but additional information was required to resolve my issue.
What can we do to improve this information? (2000 or fewer characters)
Submit
Rating: 1 - Lowest 2 3 4 5 - Highest (0 Ratings)   
Actions
  • KB Article: 2216
  • Updated: Jan 16, 2008
  • Products:
    VMware ESX
  • Product Versions:
    VMware ESX 3.0.x