elo-milo
asked on
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?
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?
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
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.
There is no native way to see what volume belongs to what LUN in Windows. Gosh...that would be fabulous if so! :)
~coolsport00
~coolsport00
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.
ASKER
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.
"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.
ASKER
Thanks.