HP StorageWorks XP10000 - Disk Array Configuration Manual page 19

h20000.www2.hp.com/bizsupport/TechSupport/Document.jsp?objectID=PSD_CN0714W) for more
information. Support is limited to legacy environments with Solaris 8 and 9 only.
Configure 2 Gbit FCAs differently as explained below. For 1 Gbit FCAs, see the HP StorageWorks
XP12000 Disk Array configuration guide for Sun Solaris. AMCC/JNI legacy drivers are available
from AMCC/JNI at http://www.jni.com. The JNI EZFibre FCA configuration utility does not allow
dynamic LUN addition. Instead edit the configuration files manually as explained below, and use
EZFibre for view-only purposes. If you do not plan to use dynamic LUN addition, you may use EZFibre
to configure the FCA.
Persistent bindings are necessary in a fabric topology and are used to bind a SCSI target ID to a
particular WWPN (of an array port). This is required to guarantee that the SCSI target IDs will remain
the same when the system is rebooted. Persistent bindings can be set by editing the configuration file
as shown in the examples that follow. Make sure the target in the driver configuration file and in the
kernel file (/kernel/drv/sd.conf) match. Replace the WWNs shown in the examples with the
correct WWNs for your array ports. You can view port WWNs using XP Command View or XP Array
Manager.
AMCC/JNI 2 Gbit FCAs
Use JNIC146x driver (version 5.3.1.1).
Edit the FCA driver settings in the /kernel/drv/jnic146x.conf file.
For a SAN environment:
FcLoopEnabled
FcFabricEnabled = 1;
For a direct connect:
FcLoopEnabled
FcFabricEnabled = 0;
To enable failover for VxVM Dynamic Multi Pathing (DMP):
FailoverDelay = 30;
For SAN persistent binding:
automap = 0;
jnic146x0-target20_hba
jnic146x0-target20_wwpn
jnic146x1-target30_hba
jnic146x1-target30_wwpn
(Replace the WWPNs above with the WWPNs for your array ports.)
Make sure the jnic146x entry below is present at the bottom of the /kernel/drv/sd.conf file:
name="sd" parent="jnic146x" target=0;
Perform a reconfiguration reboot so the host can implement the changes you made in the config-
uration files.
After configuring LUNs as explained in
date_drv command to request that the jnic146x driver instances perform LUN rediscovery:
/opt/JNIC146x/jnic146x_update_drv -r -a
= 0;
= 1;
= "jnic146x0";
= "50060e8003285301";
= "jnic146x1";
= "50060e8003285311";
"Defining the
XP Disk Array Configuration Guide for Sun Solaris
paths" on page 21, use the jnic146x_up-
19