mapping VM disks to LUNs

have win2008 server running as a VM on VMWare ESX 4 (this server is configured as part og MS CLuster). Is there any way to figure out how disks on 2008 server are mapper do LUNs o SAN?

When I look the disk porperties oin WIN Disk Mnaagement it lists the following convention: Bus Number 0, Target Id 0, LUN 0 (with Target value changing from disk to disk)
When you look at the VMware then the mappings to LUNs are represented in the following format: vmhba0:C0:T0:L1 (with L value changing)
How can I figure how the disk mapping actually works in 2008? and which LUNs on SAN are actually mapped?
elo-miloAsked:
Who is Participating?

[Product update] Infrastructure Analysis Tool is now available with Business Accounts.Learn More

x
I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

coolsport00Commented:
I had this same kind of issue to address in my organization recently. I will share how I was able to determine which LUN went with which disk/RDM at least for my situation and maybe it will help you. To be more specific for my setup, I have RDMs attached to a VM. To figure out which VM 'disk' (RDM) was with which LUN, I went into 2 areas - the VM -> Edit Settings area and into my SAN mgmt tool (for me, I use EMC CX4-120, so a Web-based Navisphere GUI is my mgmt tool). I clicked on a disk in my VM -> Edit Settings area and looked at the 'Physical LUN and Datastore Mapping File' area that is greyed out. The number displayed there will give you the LUN ID your LUNs have in your SAN Mgmt tool. So, go to the properties of your LUNs and look for that same LUN ID (typically a long string of numbers/letters...25 or so maybe?). For me, when I go into my LUN properties, the string is under 'Unique ID'.

Hope that helps. Let me know if I understood your question correctly.

Regards,
~coolsport00
0

Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
elo-miloAuthor Commented:
Thanks. I don;t think it can help me though. What I'm trying to figure out is how to look at the windows server box and figure out how it is mapped to SAN. The sond step is to compare windows mappings with vmware mappings and understand what's going on.

Thanks.
0
Vijay kumar MohanrajCloud ArchitechCommented:
New LUNs should be requested in 500Gb chunks of disk, presented from the EMC Symmetrix Storage Array in a minimum of a RAID5 configuration  and depending on which cluster the LUN is to be presented to, should be viewable by the ESX host HBA WWNs, if it is viewable from ESX host it can be access from VM level.
0
Big Business Goals? Which KPIs Will Help You

The most successful MSPs rely on metrics – known as key performance indicators (KPIs) – for making informed decisions that help their businesses thrive, rather than just survive. This eBook provides an overview of the most important KPIs used by top MSPs.

coolsport00Commented:
There is no native way to see what volume belongs to what LUN in Windows. Gosh...that would be fabulous if so! :)

~coolsport00
0
rvivek_2002Commented:
Are you using RDM, if so waht mode Physical compatibiity mode or virtual?. Inside windows all the LUNs are treated as normal SCSI disk , hence will have only SCSI devic IDs. Edit VM settings is the right place to check.
0
elo-miloAuthor Commented:
coolsport:
"There is no native way to see what volume belongs to what LUN in Windows. Gosh...that would be fabulous if so! :)"
------ is there any other way (if there is no native)?
My problem is that windows presents starage disks in format: Bus Number 0, Target Id 0, LUN 0 (with Target value changing from disk to disk). Wmware presents mapping in  vmhba0:C0:T0:L1 (with L value changing) .... and they point to different places. It droves me nuts, honestly :)

rvivek:
-----
1. How can I tell if we use RDM? (On some VMs it says "Mapped RAW Luns", on some it just points to DATASTORE\*.vmdk file
2. "What mode Physical compatibiity mode or virtual?. " - Where can I check it?
3. "All the LUNs are treated as normal SCSI disk , hence will have only SCSI device IDs"
----- OK. So the convetion that VMWare uses - vmhba0:C0:T0:L1 (channel, target. lun) it is actually the more correct representation of what's going on?

Thanks.
0
It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today
VMware

From novice to tech pro — start learning today.