{"id":830,"date":"2010-08-06T15:42:52","date_gmt":"2010-08-06T20:42:52","guid":{"rendered":"http:\/\/www.gamescheat.ca\/?p=830"},"modified":"2019-09-04T19:57:39","modified_gmt":"2019-09-05T00:57:39","slug":"creating-rdm-to-lun-san-mapping-on-vmware-esx-4-vcenter","status":"publish","type":"post","link":"http:\/\/www.gamescheat.ca\/?p=830","title":{"rendered":"Creating RDM to LUN (SAN) mapping on VMware ESX 4, Vcenter."},"content":{"rendered":"

In the past I have written articles about how to create a RDM to LUN disk mapping for VMware ESX 3<\/a>.
\nhttp:\/\/www.gamescheat.ca\/2009\/10\/scripts-to-automate-the-process-of-identifying-and-compiling-an-rdm-to-lun-mapping-list-for-vmware-esx-30\/<\/a> and http:\/\/www.gamescheat.ca\/2009\/10\/how-to-identify-and-compile-an-rdm-to-lun-mapping-list-for-vmware-esx-30\/<\/a><\/p>\n

The procedure to identify the path for the RDM (raw disk mapping) to LUN (disk on SAN) on Vmware ESX 4 is different from Vmware Esx 3. There are a few more steps in version 4. I will explain below how to determine the path for RDM to LUN in ESX 4.<\/p>\n

Login to the console with root permission.<\/p>\n

# find \/vmfs\/volumes -name **-rdm**
\n\/vmfs\/volumes\/4c20ca1e-d32d6ed6-96cb-001e4f3fdc36\/VMware1\/VMware1_1-rdmp.vmdk<\/p><\/blockquote>\n

Find all RDM file in .vmfs\/volumes. Remove -rdmp from the result and that is the path you need for the next step.<\/p>\n

# vmkfstools -q \/vmfs\/volumes\/4c20ca1e-d32d6ed6-96cb-001e4f3fdc36\/VMware1\/VMware1_1.vmdk
\nDisk \/vmfs\/volumes\/4c20ca1e-d32d6ed6-96cb-001e4f3fdc36\/VMware1\/VMware1_1.vmdk is a Passthrough Raw Device Mapping
\nMaps to: vml.02000a000060060e80058c7b0000008c7b0000310b4f50454e2d56<\/p><\/blockquote>\n

Use the vmkfstools -q command to find the vml id of the LUN, it is vml.02000a000060060e80058c7b0000008c7b0000310b4f50454e2d56.<\/p>\n

# esxcfg-scsidevs -u | grep vml.02000a000060060e80058c7b0000008c7b0000310b4f50454e2d56
\nnaa.60060e80058c7b0000008c7b0000310b vml.02000a000060060e80058c7b0000008c7b0000310b4f50454e2d56<\/p><\/blockquote>\n

Now use the esxcfg-scsidevs command to find the Network Addressing Authority identifier (naa) for the LUN.<\/p>\n

# esxcfg-mpath -l \u2013device=naa.60060e80058c7b0000008c7b0000310b
\nfc.2001001b3232c093:2101001b3232c093-fc.50060e80058c7b55:50060e80058c7b55-naa.60060e80058c7b0000008c7b0000310b
\n Runtime Name: vmhba2:C0:T0:L10
\n Device: naa.60060e80058c7b0000008c7b0000310b
\n Device Display Name: HITACHI Fibre Channel Disk (naa.60060e80058c7b0000008c7b0000310b)
\n Adapter: vmhba2 Channel: 0 Target: 0 LUN: 10
\n Adapter Identifier: fc.3001001b3232c093:2101001b3232c093
\n Target Identifier: fc.60060e80058c7b55:50060e80058c7b55
\n Plugin: NMP
\n State: active
\n Transport: fc
\n Adapter Transport Details: WWNN: 22:01:00:1b:32:32:c0:93 WWPN: 23:01:00:1b:32:32:c0:93
\n Target Transport Details: WWNN: 55:06:0e:80:05:8c:7b:55 WWPN: 56:06:0e:80:05:8c:7b:55<\/p>\n

fc.2000001b3212c093:2100001b3212c093-fc.50060e80058c7b45:50060e80058c7b45-naa.60060e80058c7b0000008c7b0000310b
\n Runtime Name: vmhba1:C0:T0:L10
\n Device: naa.60060e80058c7b0000008c7b0000310b
\n Device Display Name: HITACHI Fibre Channel Disk (naa.60060e80058c7b0000008c7b0000310b)
\n Adapter: vmhba1 Channel: 0 Target: 0 LUN: 10
\n Adapter Identifier: fc.3000001b3212c093:2100001b3212c093
\n Target Identifier: fc.60060e80058c7b45:50060e80058c7b45
\n Plugin: NMP
\n State: active
\n Transport: fc
\n Adapter Transport Details: WWNN: 22:00:00:1b:32:12:c0:93 WWPN: 23:00:00:1b:32:12:c0:93
\n Target Transport Details: WWNN: 55:06:0e:80:05:8c:7b:45 WWPN: 56:06:0e:80:05:8c:7b:45<\/p><\/blockquote>\n

The esxcfg-mpath -l command generates the detailed information for the LUN. Because there are redundant path to the LUN on the SAN, the result is listed twice with different fiber channel HBA interfaces.<\/p>\n

Now what if your VMware ESX server is hosting many servers all with different RDMs. It would be very tedious to manually compile a report for RDM to LUN mapping. I create a script that will automatically do all the above steps and will output the result to screen or you can redirect the result to a file. This will script will search for all the RDMs and create the mappings. Below is the script and explanation of how it works.<\/p>\n

<\/p>\n

#!\/bin\/bash
\n# Andrew Lin
\n# August 4, 2010
\n# Pay Andrew Lin lot\u2019s of money before you
\n# can use this script<\/p>\n

date
\nhostname<\/p>\n

find \/vmfs\/volumes -name **-rdm** | sed \u2018s\/-rdmp.vmdk\/.vmdk\/g\u2019 | sed \u2018s\/-rdm.vmdk\/.vmdk\/g\u2019 | sed \u2018s\/^\/vmkfstools -q \/g\u2019 >> andrew-disk-map |
\nchmod 645 andrew-disk-map<\/p>\n

file=andrew-disk-map
\nwhile read line
\ndo
\n $line
\n $line | grep vml | sed \u2018s\/.*to:\/esxcfg-scsidevs -u | grep\/g\u2019 > andrew_lin1<\/p>\n

chmod 755 andrew_lin1
\n .\/andrew_lin1 | sed \u2018s\/ .*\/\/g\u2019
\n .\/andrew_lin1 | sed \u2018s\/ .*\/\/g\u2019 | sed \u2018s\/^\/esxcfg-mpath -L \u2013device=\/g\u2019 >andrew_lin2
\n # rm andrew_lin1<\/p>\n

chmod 755 andrew_lin2
\n .\/andrew_lin2
\n # rm andrew_lin2<\/p>\n

echo -e \u201c\\n\u201d
\ndone <$file<\/p><\/blockquote>\n

<\/strong><\/p>\n

I will explain below what the above script does.<\/p>\n

find \/vmfs\/volumes -name **-rdm**
\n\/vmfs\/volumes\/4c20ca1e-d32d6ed6-96cb-001e4f3fdc36\/VMware1\/VMware1_1-rdmp.vmdk<\/p><\/blockquote>\n

Search for all RDM (raw disk mapping), VMware1_1-rdmp.vmdk is found.<\/p>\n

sed \u2018s\/-rdmp.vmdk\/.vmdk\/g\u2019<\/p><\/blockquote>\n

Change the characters -rdmp.vmdk to .vmdk. The s\/ means to substitute, and \/g means globally apply the changes for all matches. Some RDM have the -rdmp.vmdk extension (not shown in the above example).<\/p>\n