HP XP P9000 Configuration Guide (AV400-96525, November 2012)

• For Solaris 8/9, perform a reconfiguration reboot of the host to implement changes to the
configuration file. For Solaris 10, use the stmsboot command which will perform the
modifications and then initiate a reboot.
• For Solaris 8/9, after you have rebooted and the LDEV has been defined as a LUN to the
host, use the cfgadm command to configure the controller instances for SAN connectivity.
The controller instance (c#) may differ between systems. Replace the WWPN in the following
example with the WWPNs for your array ports.
Example
# cfgadm -al
Ap_Id Type Receptacle Occupant Condition
c3 fc-fabric connected configured unknown
c3::50060e8003285301 disk connected configured unknown
c4 fc-fabric connected configured unknown
c4::50060e8003285311 disk connected configured unknown
# cfgadm -c configure c3::50060e8003285301
# cfgadm -c configure c4::50060e8003285311
Configuring Emulex FCAs with the lpfc driver
NOTE: The lpfc driver cannot be used with Oracle StorEdge Traffic Manager/Oracle Storage
VM Multipathing. Emulex does not support using both the lpfc driver and the emlxs driver (provided
with the Oracle SAN driver stack) concurrently. To use the emlxs driver, see “Configuring FCAs
with the Oracle SAN driver stack” (page 61).
To determine which Emulex FCAs and driver version HP supports with the lpfc driver, contact your
HP representative. The lpfc driver is not supported on x86 architecture. Configure Emulex FCAs
with the lpfc driver as follows:
• Ensure you have the latest supported version of the lpfc driver (available from http://
www.emulex.com).
• Edit the /kernel/drv/lpfc.conf driver configuration file to set up the FCA for a SAN
infrastructure:
topology = 2;
• If multiple FCAs and VxVM are used, adjust the following parameters to assure correct VxVM
behavior:
no-device-delay=0;
nodev-tmo=30;
linkdown-tmo=30; # verify, should be default value
• 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 or by using the lputil utility. The following example illustrates the
binding of target 20 (lpfc instance 2) to WWPN 50060e8003285301 and the binding of
target 30 (lpfc instance 0) to WWPN 50060e8003285311:
fcp-bind-WWPN="50060e8003285301:lpfc2t20",
"50060e8003285311:lpfc0t30";
(Replace the WWPNs in the previous example with the WWPNs for your array ports.)
• For each LUN that needs to be accessed, add an entry to the /kernel/drv/sd.conf file.
For example, assume you want to access LUNs 1 and 2 through both paths. You would add
the following entries (preferably at the end of the file):
name="sd" parent="lpfc" target=20 lun=1;
name="sd" parent="lpfc" target=20 lun=2;
62 Solaris