We've got two ESX 3.0 Servers configured in a cluster and we'd like to make sure LUN's assigned to a VM through Raw Device Mapping are not seen by other VM's on any of the two ESX nodes.
Currently, VM's on one of the two ESX nodes are seeing LUN's assigned to VM's on the other node as available to be claimed.
You mean that you can add a Harddisk and select the LUN (RAW) that is already in use by another VM?
AFAIK there's no option for masking this since the ESX hosts just presents you a list of published LUN's toward itself. For example when you want to use Microsoft Cluster you would like to publish the same LUN twice as a harddisk to the VM.
Hello,
Your only solution is to limit WHO can modify the LUN information using Roles and Permissions for the VMs in question. Limit access to 'Add Existing Disk', 'Add New Disk' roles under Virtual Machine->Configuration.
This way only a select group of administrators can use this option if it is warranted.
You can also track anything like this when it happens by looking in the C:\Program Files\VMware VirtualCenter 2.0\tomcat\logs directory for the proper logfile.
Best regards,
Edward
Message was edited by:
Texiwill
It would be nice to have some kind of warning when you try to add an already used LUN to another VM.
It becomes hard and prone to error having to manually keep track of all of the assinged LUN's in an environmemnt that has tenths of VM's and LUNs.
Thanks for you inputs.
Hello,
I suggest you make a Feature Request to VMware. You are correct it would be useful.
Best regards,
Edward
Yep your right.. That's why I always tell people that using RDM's means good administration.