Unsolved
This post is more than 5 years old
1 Rookie
•
124 Posts
0
2245
June 13th, 2011 08:00
LUN-id's for raw device mapping in VMware
We recently moved from EMC DMX to VNX for our SAN storage. When on the DMX the lun-id represented in hex, converted to decimal in VMware. this does not appear to hold true for the VNX.
Vmware creates the lun-id based on the next available. thus far not a problem because each host sees all luns.
We are creating RDM's... 1 host will see these devices. what is the best practice for the lun-id configuration
No Events found!
Julien_LECORRE
92 Posts
0
June 16th, 2011 03:00
Hi,
On VNX Storage you have the ALU [Array Lun ID] which is the LUN Number inside the VNX and the HLU [Host Lun ID] which is the LUN "Masking" Number seeing from the host.
VMware see the device as CxTyDz fashion. Controller is the HBA Target is the SP port NUmber on D is the device.
For ease of use when you have only one storage assign to your VMware Cluster the HLU is equivalent to the Device Number seeing in Vmware.
If you want that your RDM device only seen from one Host change the HLU number on the VNX.
Example:
STORAGEGROUP_ESXCLUSTER
ALU HLU
100 0
101 1
102 2
103 3
104 4
STORAGEGROUP_RDMESX1
ALU HLU
105 100
On ESX1 you will see LUN 0,1,2,3,4 and 100.
You should also use the VSI PlugIn in order to see more information about your storage under VMware
Hope this help