HP StorageWorks XP12000 HP StorageWorks XP Disk Array Configuration Guide: HP- - Page 42

SCSI TID map for Fibre Channel adapters

Get HP StorageWorks XP12000 - Disk Array PDF manuals and user guides View all HP StorageWorks XP12000 manuals
Add to My Manuals
Save this manual to your list of manuals

Page 42 highlights

Device type Physical extent Max physical extent size size (PE) (MPE) n = 36 8 62518 OPEN-L*n n = 2 to 3 default default OPEN-8/9/E-CVS OPEN-V default default OPEN-8/9/E*n-CVS OPEN-V*n (n = 2 to 70 to 119731(MB) × N1 8 36) default 119732 to (MB) × N1 8 N2 N1 = [ VCS volume capacity (in MB) from Remote Console PC ] × nN2 = N1 / PE ( means round up to next integer) Example: CVS volume capacity is 6000 MB for OPEN-9*22-CVS volume:N1 = 6000 × 22 = 132000N2 = 132000/8 = 16500 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 because 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 operating 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. The following table identifies the fixed mappings between the TID (drive) values assigned by the operating 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. The mapping cannot be done when these conditions exist: • Disk array devices and other types of devices are connected in the same loop • Information for unused devices remains in the server system • Multiple ports participate in the same arbitrated loop Table 12 SCSI TID map t value AL-PA AL-PA AL-PA AL-PA AL-PA AL-PA AL-PA AL-PA 0 EF CD B2 98 72 55 3A 25 1 E8 CC B1 97 71 54 39 23 42 Disk array supported emulations

  • 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
Max physical extent size
(MPE)
Physical extent
size (PE)
Device type
62518
8
n = 36
default
default
n = 2 to 3
OPEN-L*n
default
default
OPEN-8/9/E-CVS OPEN-V
default
8
70 to 119731(MB) × N1
OPEN-8/9/E*n-CVS
OPEN-V*n (n = 2 to
36)
N2
8
119732 to (MB) × N1
N1 = [ VCS volume capacity (in MB) from Remote Console PC ] × nN2 =
N1 / PE
(
means round up to
next integer) Example: CVS volume capacity is 6000 MB for OPEN-9*22-CVS volume:N1 = 6000 × 22 =
132000N2 =
132000/8
= 16500
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 because 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 operating 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.
The following table identifies the fixed mappings between the TID (drive) values assigned by the
operating 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.
The mapping cannot be done when these conditions exist:
•
Disk array devices and other types of devices are connected in the same loop
•
Information for unused devices remains in the server system
•
Multiple ports participate in the same arbitrated loop
Table 12 SCSI TID map
AL-PA
AL-PA
AL-PA
AL-PA
AL-PA
AL-PA
AL-PA
AL-PA
t value
25
3A
55
72
98
B2
CD
EF
0
23
39
54
71
97
B1
CC
E8
1
Disk array supported emulations
42