ADIC FCR 200, Operator'S Manual

Page: 123 / 140

SCC Addressing Option D-5
SCC Addressing Option
When the FCR200 is configured to use SCC addressing, the
unit is capable of responding as a controller device to the FCP
Initiator, or routing the FCP request to a specified
BUS:TARGET:LUN triplet. When a request using the
Peripheral Device Addressing Method is received (An FCP
command with the LUN field with bits 7 and 6 of byte 0 are set
to 0), the unit routes the request to the FCR200, which acts on
the command directly. When a request using the Logical Unit
Addressing Method is received (bits 7 and 6 set to 10b), the
request is routed to the BUS:TARGET:LUN as specified in the
defined field.
Host systems using SCC addressing will typically do initial
device discovery using the Peripheral Device Addressing
method. On issuing an INQUIRY command, the host will
receive the FCR200 inquiry data (Appendix C), indicating the
device type as a controller device. The host will then know on
this basis that subsequent commands to attached devices will
use the Logical Unit Addressing method. The host can
perform discovery by either walking through the
BUS:TARGET:LUN values as would a standard SCSI driver,
or by issuing a REPORT LUNS command (Appendix B). This
command is sent to the controller (using the Peripheral Device
Addressing Method), and returns a table indicating attached
devices. The host can then perform actions on these devices
directly without having to perform discovery through all
possible combinations.
13:0x25 34:0x47 55:0x6A 76:0x97 97:0xB6 118:0xDA
14:0x26 35:0x49 56:0x6B 77:0x98 98:0xB9 119:0xDC
15:0x27 36:0x4A 57:0x6C 78:0x9B 99:0xBA 120:0xE0
16:0x29 37:0x4B 58:0x6D 79:0x9D 100:0xBC 121:0xE1
17:0x2A 38:0x4C 59:0x6E 80:0x9E 101:0xC3 122:0xE2
18:0x2B 39:0x4D 60:0x71 81:0x9F 102:0xC5 123:0xE4
19:0x2C 40:0x4E 61:0x72 82:0xA3 103:0xC6 124:0xE8
20:0x2D 41:0x51 62:0x73 83:0xA5 104:0xC7 125:0xEF
Table D-5 Arbitrated Loop Node Number to ALPA Lookup Table
0:0x01 21:0x2E 42:0x52 63:0x74 84:0xA6 105:0xC9