• Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 4186
  • Last Modified:

Understanding Drive's Bus Number/TargetID/LUN

right click on any drive->properties->Hardware Table->Click on Name of Drive and then see below drive properties

On a physical machine with SAN, I see

Port(2,2,2,2,3,3,3,3) Location: Bus Number 0, TargetID 6, LUN 0
Port(2,2,2,2,3,3,3,3) Location: Bus Number 0, TargetID 6, LUN 1
Port(2,2,2,2,3,3,3,3) Location: Bus Number 0, TargetID 6, LUN 2
Port(2,2,2,2,3,3,3,3) Location: Bus Number 0, TargetID 6, LUN 3
Port(2,2,2,2,3,3,3,3) Location: Bus Number 0, TargetID 6, LUN 4
Port(2,2,2,2,3,3,3,3) Location: Bus Number 0, TargetID 6, LUN 5
Port(2,2,2,2,3,3,3,3) Location: Bus Number 0, TargetID 6, LUN 6
Port(2,2,2,2,3,3,3,3) Location: Bus Number 0, TargetID 6, LUN 7
Port(2,2,2,2,3,3,3,3) Location: Bus Number 0, TargetID 6, LUN 8
Port(2,2,2,2,3,3,3,3) Location: Bus Number 0, TargetID 6, LUN 9
Port(2,2,2,2,3,3,3,3) Location: Bus Number 0, TargetID 6, LUN 10
Port(2,2,2,2,3,3,3,3) Location: Bus Number 0, TargetID 6, LUN 11
Location: Bus Number 1, TargetID 0, LUN 0

vs

On a VM I see

Location: Bus Number 0, TargetID 0, LUN 0
Location: Bus Number 0, TargetID 1, LUN 0
Location: Bus Number 0, TargetID 2, LUN 0

Does that mean in the physical machines, there are 12+1 LUNs? There 2 Bus numbers what is the significanse of it?
on the VM, does that mean there are all in the dedault LUN of the datastore?
0
25112
Asked:
25112
  • 5
  • 4
1 Solution
 
Andrew Hancock (VMware vExpert / EE MVE^2)VMware and Virtualization ConsultantCommented:
For the moment lets ignore physical and virtual machines, and look at some terms

Bus Number
This is the Storage Bus Number

TargetID
This is the method by which individual devices are identified on the Storage Bus. Often called a SCSI ID, each disk or chassis location has an ID.

LUN
A LUN is a Logical Unit Number. It can be used to refer to an entire physical disk, or a subset of a larger physical disk or disk volume. The physical disk or disk volume could be an entire single disk drive, a partition (subset) of a single disk drive, or disk volume from a RAID controller comprising multiple disk drives aggregated together for larger capacity and redundancy. LUNs represent a logical abstraction or, if you prefer, virtualization layer between the physical disk device/volume and the applications.

On your phsyical machine, you would have 13 disks presented to the OS, on Bus 0, SCSI 6, LUN - 0 - 11, and Bus 1, SCSI ID 0, LUN 0
On your virtual machinbe, you would have 3 disks presented to the OS, on SCSI ID 0, 1, 2

it's has nothing to do with datastores. Only the Physcial Server HOSTING the VM, has datastores.
0
 
25112Author Commented:
>>It can be used to refer to an entire physical disk, or a subset of a larger physical disk or disk volume. The physical disk or disk volume could be an entire single disk drive, a partition (subset) of a single disk drive, or disk volume from a RAID controller comprising multiple disk drives aggregated together for larger capacity and redundancy.

so many options there.. so just by looking at disk management it is not possible to tell what exactly or how small/big the LUN is, right?you need more tool as you said..
--------------------------
>On your phsyical machine, you would have 13 disks presented to the OS, on Bus 0, SCSI 6, LUN - 0 - 11, and Bus 1, SCSI ID 0, LUN 0

2 bus- 2 devices- lot of LUNs is that typical of SAN
1 bus-3devices-1LUN - means like 3 exit doors on a bus? (one box availing itself 3 times)-more room for bottleneck?

-----------------------------
datastore- i understood from the other post that it is the basically the array or arrays of disk, and the supply for disk. I understand it for a VM machine, that its host holds the datastore.. what about in a purely physical server.. how do you define its datastore.

0
 
Andrew Hancock (VMware vExpert / EE MVE^2)VMware and Virtualization ConsultantCommented:
The LUN is equal to the disk partition or disk, so LUN 12 = a Disk Partition or Disk.

It is typical of a SAN, but could also be local attached Scsi Disk.

Yes, But The BUS is designed to commincate with multiple devices.

A physical server just has disks. There is not datastore on a phsyical disk.

Datastores are sepecifc to VMware hosts, where a bunch of disks or single disk is formatted with VMFS (VMware Filing System), this is a datastore, where Virtual Machines are stored.

0
Industry Leaders: We Want Your Opinion!

We value your feedback.

Take our survey and automatically be enter to win anyone of the following:
Yeti Cooler, Amazon eGift Card, and Movie eGift Card!

 
25112Author Commented:
OK-
with the VM,
"
Location: Bus Number 0, TargetID 0, LUN 0
Location: Bus Number 0, TargetID 1, LUN 0
Location: Bus Number 0, TargetID 2, LUN 0
"
does it confirm that all 3 drives are part of the same LUN?

 (perhaps other VM have drives part of this LUN, too, but which we do not know from the above) there may be more LUNs in the datastore or the LUN is the only one for datastore for the Hosting machine.. right?
0
 
Andrew Hancock (VMware vExpert / EE MVE^2)VMware and Virtualization ConsultantCommented:
No, Because each has a Seperate TagertID, SCSI Id.

Each is Unique.

do not consure host storage resources with virtual machines guests.

Until you have access to the host, you will never know, how Host Storage is configured.
0
 
Andrew Hancock (VMware vExpert / EE MVE^2)VMware and Virtualization ConsultantCommented:
It's possible that VMs, may or may not share the same datastore on the hosts, the hosts may have multiple datastores, connected to SANs or Local Storage.

There is NO WAY to tell, unless you have access to the HOST server, hosting rhe VMs.
0
 
25112Author Commented:
>>No, Because each has a Seperate TagertID, SCSI Id.

OK; I take that for the VM environment. thanks..

 What about physical? does the same reasoning apply:  Each is not Unique?


Port(2,2,2,2,3,3,3,3) Location: Bus Number 0, TargetID 6, LUN 0
Port(2,2,2,2,3,3,3,3) Location: Bus Number 0, TargetID 6, LUN 1
Port(2,2,2,2,3,3,3,3) Location: Bus Number 0, TargetID 6, LUN 2
Port(2,2,2,2,3,3,3,3) Location: Bus Number 0, TargetID 6, LUN 3
Port(2,2,2,2,3,3,3,3) Location: Bus Number 0, TargetID 6, LUN 4
Port(2,2,2,2,3,3,3,3) Location: Bus Number 0, TargetID 6, LUN 5
Port(2,2,2,2,3,3,3,3) Location: Bus Number 0, TargetID 6, LUN 6
Port(2,2,2,2,3,3,3,3) Location: Bus Number 0, TargetID 6, LUN 7
Port(2,2,2,2,3,3,3,3) Location: Bus Number 0, TargetID 6, LUN 8
Port(2,2,2,2,3,3,3,3) Location: Bus Number 0, TargetID 6, LUN 9
Port(2,2,2,2,3,3,3,3) Location: Bus Number 0, TargetID 6, LUN 10
Port(2,2,2,2,3,3,3,3) Location: Bus Number 0, TargetID 6, LUN 11
Location: Bus Number 1, TargetID 0, LUN 0
0
 
Andrew Hancock (VMware vExpert / EE MVE^2)VMware and Virtualization ConsultantCommented:
No, because here the SCSI ID is the Same, it's 6, LUN is variable, so SCSI Address can contacted

0:6:0, 0:6:1 these could be disks, or Disk Units on a SAN/DAS, or storage which is presented to the server. (direct attached storage chassis)
0
 
25112Author Commented:
thanks as always..
0

Featured Post

Veeam and MySQL: How to Perform Backup & Recovery

MySQL and the MariaDB variant are among the most used databases in Linux environments, and many critical applications support their data on them. Watch this recorded webinar to find out how Veeam Backup & Replication allows you to get consistent backups of MySQL databases.

  • 5
  • 4
Tackle projects and never again get stuck behind a technical roadblock.
Join Now