Product guide
Table Of Contents
- Installing and Configuring the HBA and Driver
- Configuring a Boot Device on the EMC Storage Array

26
EMC Fibre Channel with QLogic Host Bus Adapters in the Solaris Environment
Installing and Configuring the HBA and Driver
Note: Changes to sd.conf will not take effect until the host is rebooted.
Devices accessed via Fibre Channel using the QLogic driver are
addressed behind a single target ID with up to 256 LUNs. (This
differs from existing SCSI device addressing, which might have
multiple targets and LUNs.) In the standard EMC storage array
device definition file, target 0 should have 256 LUNs, and all other
targets (1 through 125) have a LUN 0 only.
Edit
sd.conf to list all targets and all LUNs that might be addressed.
The Target ID needed to address a device is determined by the Fibre
Channel Arbitrated Loop Physical Address (AL_PA). A Loop_ID of
00 (AL_PA of EF) will have LUNs behind Target ID 0, Loop_ID 01 has
LUNs on target ID 1, and so on.
Since each Fibre Channel port can have only one loop ID (or AL_PA),
all devices accessed through a port will have the same target ID. If
you need to access existing devices that previously had multiple
target IDs, be aware of changes required for raw device addressing.
Note: Your actual target/LUN assignment will vary depending on unique
system configuration requirements. Be sure that existing and new
configurations are well documented before upgrading to Fibre Channel
directors.
Make sure that only the target=x lun=0 line is specified for any
target ID that does not need LUN support. This decreases the time
needed to reboot the system.
Sample sd.conf file Here is an example of
sd.conf:
name=”sd” class=”scsi”
_ _target=0 lun=0;
name=”sd” class=”scsi”
_ _target=0 lun=1;
.
.
name=”sd” class=”scsi”
_ _target=0 lun=255;
name=”sd” class=”scsi”
_ _target=1 lun=0;
name=”sd” class=”scsi”
_ _target=2 lun=0;
.
.
name=”sd” class=”scsi”
_ _target=125 lun=0;