Jump to content
Main menu
Main menu
move to sidebar
hide
Navigation
Main page
Recent changes
Random page
Help about MediaWiki
Special pages
Niidae Wiki
Search
Search
Appearance
Create account
Log in
Personal tools
Create account
Log in
Pages for logged out editors
learn more
Contributions
Talk
Editing
SCSI
(section)
Page
Discussion
English
Read
Edit
View history
Tools
Tools
move to sidebar
hide
Actions
Read
Edit
View history
General
What links here
Related changes
Page information
Appearance
move to sidebar
hide
Warning:
You are not logged in. Your IP address will be publicly visible if you make any edits. If you
log in
or
create an account
, your edits will be attributed to your username, along with other benefits.
Anti-spam check. Do
not
fill this in!
==Device identification== ===Parallel interface=== {{Technical|section|date=June 2008}} On a parallel SCSI bus, a device (e.g. host adapter, disk drive) is identified by a "SCSI ID", which is a number in the range 0β7 on a narrow bus and in the range 0β15 on a wide bus. On earlier models a physical jumper or switch controls the [[SCSI ID]] of the initiator ([[host adapter]]). On modern host adapters (since about 1997), doing I/O to the adapter sets the SCSI ID; for example, the adapter often contains an [[Option ROM]] (SCSI BIOS) program that runs when the computer boots up and that program has menus that let the operator choose the SCSI ID of the host adapter. Alternatively, the host adapter may come with software that must be installed on the host computer to configure the SCSI ID. The traditional SCSI ID for a host adapter is 7, as that ID has the highest priority during bus arbitration (even on a 16-bit bus). The SCSI ID of a device in a drive enclosure that has a back plane is set either by jumpers or by the slot in the enclosure the device is installed into, depending on the model of the enclosure. In the latter case, each slot on the enclosure's back plane delivers control signals to the drive to select a unique SCSI ID. A SCSI enclosure without a back plane often has a switch for each drive to choose the drive's SCSI ID. The enclosure is packaged with connectors that must be plugged into the drive where the jumpers are typically located; the switch emulates the necessary jumpers. While there is no standard that makes this work, drive designers typically set up their jumper headers in a consistent format that matches the way that these switches implement. Setting the bootable (or first) hard disk to SCSI ID 0 is an accepted IT community recommendation. SCSI ID 2 is usually set aside for the floppy disk drive while SCSI ID 3 is typically for a CD-ROM drive.<ref>{{cite book|last=Groth|first=David|author2=Dan Newland |title=A+ Complete Study Guide |url=http://www.bookfinder4u.com/IsbnSearch.aspx?isbn=0782128025&mode=direct|edition=2nd|date=January 2001|publisher=l Sybex|location=Alameda, CA, USA|isbn=978-0-7821-4244-0|page=183}}</ref> ===General=== Note that a SCSI target device (which can be called a "physical unit") is sometimes divided into smaller "logical units". For example, a high-end disk subsystem may be a single SCSI device but contain dozens of individual disk drives, each of which is a logical unit. Further, a RAID array may be a single SCSI device, but may contain many logical units, each of which is a "virtual" diskβa stripe set or mirror set constructed from portions of real disk drives. The SCSI ID, WWN, etc. in this case identifies the whole subsystem, and a second number, the [[logical unit number]] (LUN) identifies a disk device (real or virtual) within the subsystem. It is quite common, though incorrect, to refer to the logical unit itself as a "LUN".<ref> {{cite web | title = na_lun(1) β Manual page for "lun" on NetApp DataONTAP | publisher = [[NetApp]] | date = July 7, 2009 | quote = The lun command is used to create and manage luns[...] | url = https://library.netapp.com/ecmdocs/ECMP1511537/html/man1/na_lun.1.html }} </ref> Sometimes, redundantly, the actual LUN may be called a "LUN number" or "LUN id".<ref> {{cite web | title = na_lun(1) β Manual page for "lun" on NetApp DataONTAP | publisher = [[NetApp]] | date = July 7, 2009 | quote = If a LUN ID is not specified, the smallest number [...] is automatically picked. | url = https://library.netapp.com/ecmdocs/ECMP1511537/html/man1/na_lun.1.html }} </ref> In modern SCSI transport protocols, there is an automated process for the "discovery" of the IDs. The SSA initiator (normally the host computer through the 'host adaptor') "walk the loop" to determine what devices are connected and then assigns each one a 7-bit "hop-count" value. [[Fibre Channel]] β Arbitrated Loop (FC-AL) initiators use the LIP (Loop Initialization Protocol) to interrogate each device port for its WWN ([[World Wide Name]]). For iSCSI, because of the unlimited scope of the (IP) network, the process is quite complicated. These discovery processes occur at power-on/initialization time and also if the bus topology changes later, for example if an extra device is added. SCSI has the CTL (Channel, Target or Physical Unit Number, Logical Unit Number) identification mechanism per [[host bus adapter]], or the HCTL (HBA, Channel, PUN, LUN) identification mechanism, one host adapter may have more than one channels.<ref>{{Cite web|title=SCSI Addressing|url=https://tldp.org/HOWTO/SCSI-2.4-HOWTO/scsiaddr.html|access-date=2021-03-04|website=tldp.org}}</ref>
Summary:
Please note that all contributions to Niidae Wiki may be edited, altered, or removed by other contributors. If you do not want your writing to be edited mercilessly, then do not submit it here.
You are also promising us that you wrote this yourself, or copied it from a public domain or similar free resource (see
Encyclopedia:Copyrights
for details).
Do not submit copyrighted work without permission!
Cancel
Editing help
(opens in new window)
Search
Search
Editing
SCSI
(section)
Add topic