HP Surestore Disk Array 12h SGI IRIX Configuration Guide - Page 47

SCSI TID Map for Fibre Channel Adapters, dev/dsk/c*t*d, dev/dsk, dks*d*l*s

Page 47 highlights

SCSI TID Map for Fibre Channel Adapters When an arbitrated loop (AL) is established or reestablished, the port addresses are assigned automatically to prevent duplicate TIDs. With the SCSI over Fibre Channel protocol (FCP), there is no longer a need for target IDs in the traditional sense. SCSI is a bus-oriented protocol requiring each device to have a unique address since all commands go to all devices. For Fibre Channel, the AL-PA is used instead of the TID to direct packets to the desired destination. Unlike traditional SCSI, when control of the loop is acquired, a point-to-point connection is established from initiator to target. To enable transparent use of FCP, the SGI IRIX system maps a TID to each AL-PA. The host maps SCSI protocol to Fibre Channel protocol and detects and accesses Fibre Channel-connected devices using device files (/dev/dsk/c*t*d* and /dev/rdsk/c*t*d*) in the same way as for SCSI-connected devices. The device files for Fibre Channel-connected devices are configured in a different way from SCSI-connected devices, because Fibre Channel supports 126 addresses per path while SCSI supports 16 TIDs per path. Table 6 (page 48) identifies the fixed mappings between the TID (drive) values assigned by the IRIX system and the Fibre Channel native addresses (AL_PA/SEL_ID) for Fibre Channel adapters. The controller number (the dks value in /dev/dsk/ dks*d*l*s*) depends on the server configuration, and a different value is assigned per each column of Table 6. The mapping defined in table 10 cannot be guaranteed under the following conditions: • when disk array devices and other types of devices are connected in the same loop • when information for unused devices remains in the server system • when multiple ports participate in the same arbitrated loop Disk Parameters 47

  • 1
  • 2
  • 3
  • 4
  • 5
  • 6
  • 7
  • 8
  • 9
  • 10
  • 11
  • 12
  • 13
  • 14
  • 15
  • 16
  • 17
  • 18
  • 19
  • 20
  • 21
  • 22
  • 23
  • 24
  • 25
  • 26
  • 27
  • 28
  • 29
  • 30
  • 31
  • 32
  • 33
  • 34
  • 35
  • 36
  • 37
  • 38
  • 39
  • 40
  • 41
  • 42
  • 43
  • 44
  • 45
  • 46
  • 47
  • 48
  • 49
  • 50
  • 51
  • 52
  • 53
  • 54
  • 55
  • 56
  • 57
  • 58
  • 59
  • 60
  • 61
  • 62
  • 63
  • 64
  • 65
  • 66
  • 67
  • 68
  • 69
  • 70
  • 71
  • 72
  • 73
  • 74
  • 75
  • 76
  • 77
  • 78
  • 79
  • 80

Disk Parameters
47
SCSI TID Map for Fibre Channel Adapters
When an arbitrated loop (AL) is established or reestablished, the port addresses are
assigned automatically to prevent duplicate TIDs. With the SCSI over Fibre Channel
protocol (FCP), there is no longer a need for target IDs in the traditional sense.
SCSI is a bus-oriented protocol requiring each device to have a unique address since all
commands go to all devices. For Fibre Channel, the AL-PA is used instead of the TID
to direct packets to the desired destination.
Unlike traditional SCSI, when control of the loop is acquired, a point-to-point
connection is established from initiator to target. To enable transparent use of FCP, the
SGI IRIX system maps a TID to each AL-PA.
The host maps SCSI protocol to Fibre Channel protocol and detects and accesses Fibre
Channel-connected devices using device files (
/dev/dsk/c*t*d*
and
/dev/rdsk/c*t*d*
)
in the same way as for SCSI-connected devices. The device files for Fibre
Channel-connected devices are configured in a different way from SCSI-connected
devices, because Fibre Channel supports 126 addresses per path while SCSI supports
16 TIDs per path.
Table 6 (page 48) identifies the fixed mappings between the TID (drive) values
assigned by the IRIX system and the Fibre Channel native addresses (AL_PA/SEL_ID)
for Fibre Channel adapters. The controller number (the
dks
value in
/dev/dsk/
dks*d*l*s*
) depends on the server configuration, and a different value is assigned per
each column of Table 6.
The mapping defined in table 10 cannot be guaranteed under the following conditions:
when disk array devices and other types of devices are connected in the same loop
when information for unused devices remains in the server system
when multiple ports participate in the same arbitrated loop