HP StorageWorks HSG80 ACS Solution Software V8.8 for Sun Solaris Installation and Configuration Guide (AA-RV1RA-TE, March 2005)

FC Configuration Procedures
163HSG80 ACS Solution Software V8.8 for Sun Solaris Installation and Configuration Guide
FFFF-SSSS-TTTT-LLL1 for Port 1
FFFF-SSSS-TTTT-LLL2 for Port 2
By utilizing the WWPN, the user has complete control over the mappings (and
subsequently the system binding) from a server to a port in the fabric. By enabling
the Port Names, there is the flexibility of mapping a server to a specific port of a
fabric array or to multiple ports of a fabric array.
Additionally, the user is able to map a server with multiple adapters to multiple
arrays in the fabric. And, if the idea extends across servers, then there are many
possibilities of configuring and sharing a storage in a fabric. Thus, in a shorthand
version, connections are as follows:
Server 1 => Switch => array1, Port 1 & array1, Port 2
Or
Server 1 => Switch => array1, Port 1 & array2, Port 1
In every case, storage subsystems can be accessed that are 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 following examples have been reformatted for clarity.