Setup Solaris QLogic kernel config files and add LUNs

KernelBindingQlgxLunsSolaris_sym001

Adding persistent bindings to Solaris QLogic kernel files

KernelBindingQlgxLunsSolarisa_sym001 Done

1. Overview 1. This procedure explains how to configure one persistent binding per SP port on each HBA in the QLogic qla2x00.conf file. Using two procedures, this section for Solaris with QLogic HBAs describes how to add persistent bindings and make LUNs available to the host. 1.
Find the WWN In the /var/adm/messages file, locate the keyword WWPN next to the driver instance. For example, this messages file contains the following entries:
qla2300-hbax-SCSI-target-id-0-fibre-channel-port name=" 50060482c464abec"; qla2300-hbax-SCSI-target-id-0-fibre-channel-port-name=" 50060482c464abec";

where x represents the HBA driver instance. Note: It is possible that you might find multiple instances of the driver. If there are multiple instances, determine which driver you are using before continuing. CAUTION: Verify that you are using the WWPN of the FA and not the HBA. The correct WWPN will begin with 5006048nnnnnnnnn. To collect the FA WWN, execute the following SYMCLI command:
symcfg sid SymmID list fa all

Subsitiute SymmID with the last four digits of the Symmetrix Serial Number.

2.

Create entries for each HBA Open the qla2x00.conf file for your driver and create an entry for each HBA and target combination using the format:
hbax-SCSI-target-id-y-fibre-channel-port-name="PPPP";

where x is the driver instance number of the HBA, y is the device address, and PPPP is the target WWPN of the EMC storage array. The driver instance can be obtained by looking at the message file, located at /var/adm/messages, search for qlc and you will see a driver instance Number next to it. Save the changes you made to the .conf file.

3.

Reboot the server Reboot the server by entering the following command:
reboot -- -r

Table of Contents

KernelBindingLunsQlgxSolaris_sym001

Adding LUNs to Solaris config file for QLogic HBA

KernelBindingQlgxLunsSolarisb_sym001 Done

1. Overview This procedure adds LUNs to the Solaris QLogic Solaris config file. If you installed driver 4.15.03 or later, there is no need to edit the sd.conf file and therefore, skip these steps. When editing the file, follow these precautions: Do not delete any original data from this file; the Solaris operating system might not boot properly. Do not insert hidden format characters. The file is very sensitive to hidden format characters, and a misplaced tab or other formatting character can make all subsequent entries unreadable. Enter all target and LUN values in decimal format.

1.

Make a copy of the kernel Before editing the current /kernel/drv/sd.conf file, use the following command to make a copy of it in case the file is lost or errors are made:
cp /kernel/drv/sd.conf /kernel/drv/sd.conf.bak

2.

Modify the config file Modify the config file (/kernel/drv/sd.conf): The default sd.conf file contains entries for LUN 0 only. Therefore, you must edit the file to add entries for any LUNs with numbers greater than 0 that you will bind in the storage systems connected to the server. Devices accessed through Fibre Channel, using the QLogic driver, are addressed behind a single target ID with up to 256 LUNs. Note: 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. 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 ID1, and so on. The following is an example of the sd.conf file:
name="sd" name="sd" . . . name="sd" name="sd" name="sd" . . . name="sd" class="scsi" target=0 lun=0; class="scsi" target=0 lun=1;

class="scsi" target=0 lun=255; class="scsi" target=1 lun=0; class="scsi" target=2 lun=0;

class="scsi" target=125 lun=0;

KernelBindingLunsQlgxSolaris_sym001

3.

After you add all of the LUNs that you think you will need, save the file and reboot the operating system:
reboot -- -r

Note: With a reboot, the host recognizes the new driver and sets the driver variables. In an FC-SW topology, the host also adds the new driver instances to its internal list of drivers.

4.

Verify that Solaris recognizes the devices by using the format command If Solaris does not recognize any devices, verify the connection to the Storage array.

Table of Contents

KernelBindingLunsQlgxSolaris_sym001