Compaq StorageWorks HSG60 ACS Solution Software V8.6 for Sun Solaris Installation and Configuration Guide

Fibre Channel: Considerations for Both Loop and Fabric Environments 6–7
Additionally, the user is able to map a server with multiple adapters to multiple arrays in
the fabric. And, if we extend the idea across servers, then we have many possibilities of
configuring and sharing a storage in a fabric. Thus, in a shorthand version we can connect
as follows:
Server 1 => Switch => array1, Port 1 & array1, Port 2
Or Server 1 => Switch => array1, Port 1 & array2, Port 1
In every case we can access storage subsystems not directly connected to a single switch
by resolving the access path through the fabric to a specific WWPN.
Obviously, this ability brings with it complexity and the need to both design and consider
the growth possibilities for the fabric and the storage capability. So, this is a second
caution: take the time to plan a configuration, test the portions of it and record the
various connections and paths. This activity will provide a valuable tool for support of
Fibre Channel fabric installations.
Loop Connections at the Solaris Level
SCSI Target bindings are defined in the /kernel/drv/sd.conf file for both loop and fabric
definitions. These entries look similar to the following:
name="sd" parent="/iommu@f,e0000000/sbus@f,e0001000/fcaw@0,0"
Target=65 lun=1
sd.conf entries reflect the choices that the user has made regarding the Targets, and the
number of LUNs they wish to map to.
The examples below have been reformatted for clarity and discussion.
Loop Mappings
Three entries from a sd.conf file are shown below.
name="sd" parent="/sbus@a,0/fcaw@2,0" Target=64 lun=0;
name="sd" parent="/sbus@a,0/fcaw@2,0" Target=64 lun=1;
...
name="sd" parent="/sbus@a,0/fcaw@2,0" Target=64 lun=15;