same port ID. In a hub environment, each Symmetrix port must have a
different Hard Loop ID (Target ID).
Example of sd.conf for Arbitrated Loop in a Hubless Environment
The following example is for a hubless loop configuration with a
Target ID (Symmetrix Hard loop ID) of 0.
name="sd" class="scsi"
target=0 lun=0;
name="sd" class="scsi"
target=0 lun=1;
.
.
.
name="sd" class="scsi"
target=0 lun_6;
name="sd" class="scsi"
target=0 lun_7;
Note: Add only those Target/Lun definitions that are needed. In a direct-connect
configuration, it is recommended that all Symmetrix ports be given the same
Target ID. If different Hard Loop IDs are used for each port, lines must be
added
to sd.conf for each LUN of each target. The fewer Target/Lun definitions in
sd.conf, the less time it takes to boot.
Example of sd.conf for Arbitrated Loop in a Hub Environment:
The following example is for a hub loop configuration with two Target IDs of 0
and
1. Each target has 128 luns. For every Symmetrix port assigned to a host, there
must be a target and series of LUNs configured in the sd.conf file. Targets are
determined from the Symmetrix Hard Loop ID. In this example, 256 separate
Target/LUN definitions are added to the sd.conf file.
name="sd" class="scsi"
target=0 lun=0;
name="sd" class="scsi"
target=0 lun=1;
.
.
.
name="sd" class="scsi"
target=0 lun_6;
name="sd" class="scsi"
target=0 lun_7;
name="sd" class="scsi"
target=1 lun=0;
name="sd" class="scsi"
target=1 lun=1;
.
.
.
name="sd" class="scsi"
target=1 lun_6;
name="sd" class="scsi"
target=1 lun_7;
Kommentare zu diesen Handbüchern