VMware Cloud Community
morciod
Contributor
Contributor

Lun id's for Raw device mapping

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

Debbie
Tags (3)
0 Kudos
3 Replies
vmroyale
Immortal
Immortal

Hello.

Note: This discussion was moved from the VMware ESX 4 community to the VMware vSphere Storage community.

Good Luck!

Brian Atkinson | vExpert | VMTN Moderator | Author of "VCP5-DCV VMware Certified Professional-Data Center Virtualization on vSphere 5.5 Study Guide: VCP-550" | @vmroyale | http://vmroyale.com
0 Kudos
a_p_
Leadership
Leadership

Vmware creates the lun-id based on the next available.

Are you absolutely sure you did not miss anything in the VNX's configuration. It's hard to believe the LUN ID's are not the ones used for presenting the LUN on the storage system!? I will be setting up VMX within the next few weeks and sure take a close look at this.

André

0 Kudos
morciod
Contributor
Contributor

no they do not match up....  this is how they configure (thus we manage in a spreadsheet)

VNX Lun-nameVNX Lun-#VMware Lun#DataStore name
VMware_NFC_100VNX_NFC_01
VMware_NFC_211VNX_NFC_02
Vmware_152VNX_FC_01
Vmware_263VNX_FC_02
Vmware_374VNX_FC_03
Vmware_485VNX_FC_04
Vmware_596VNX_FC_05
Vmware_6107VNX_FC_06
Vmware_7118VNX_FC_07
Vmware_8129VNX_FC_08
Vmware_91310VNX_FC_09
Vmware_101411VNX_FC_10
Vmware_NFC_31814VNX_NFC_03
Vmware_NFC_41613VNX_NFC_04
Vmware_NFC_52412VNX_NFC_05

Debbie
0 Kudos