Scribd
Upload
63 views3 pages

Setup Solaris Emulex Kernel Config Files and Add Luns

The document provides instructions for setting up persistent bindings and adding LUNs to the Solaris kernel configuration files for Emulex host bus adapters. It describes using the lputil utility to set up persistent bindings for each adapter, then modifying the /kernel/drv/sd.conf file to add entries for any LUNs greater than 0 that will be connected via Fibre Channel. The entries should specify the target ID and LUN in a standardized format. A sample modified sd.conf file is shown adding LUNs for targets 5 and 16. The system may require a reboot for the LUN additions to take effect.

Uploaded by

umamamheswaran
Copyright
© Attribution Non-Commercial (BY-NC)
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as DOC, PDF, TXT or read online on Scribd
63 views3 pages

Setup Solaris Emulex Kernel Config Files and Add Luns

The document provides instructions for setting up persistent bindings and adding LUNs to the Solaris kernel configuration files for Emulex host bus adapters. It describes using the lputil utility to set up persistent bindings for each adapter, then modifying the /kernel/drv/sd.conf file to add entries for any LUNs greater than 0 that will be connected via Fibre Channel. The entries should specify the target ID and LUN in a standardized format. A sample modified sd.conf file is shown adding LUNs for targets 5 and 16. The system may require a reboot for the LUN additions to take effect.

Uploaded by

umamamheswaran
Copyright
© Attribution Non-Commercial (BY-NC)
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as DOC, PDF, TXT or read online on Scribd
You are on page 1/ 3

Setup Solaris Emulex kernel config files and add LUNs

KernelBindingEmlxLunsSolaris_sym001

The following procedures specific to Emulex HBAs describe how to add persistent bindings and LUNs to the Solaris kernel config files.
KernelBindingEmlxLunsSolarisa_sym001

Adding persistent bindings to Solaris Emulex kernel files


Done

Overview The Emulex driver comes with a utility called lputil to set up persistent bindings (among other functions). To set up persistent bindings, follow the steps below, repeating them for each adapter.

1.

Type the following command and press Enter:


/usr/sbin/lpfc/lputil

2. 3. 4. 5. 6. 7.

On the menu that appears select 5. Persistent Bindings. Select 5. Bind Automapped Targets. Select an adapter, 0-n, where n is the number of adapters installed in your system. When prompted, Bind all auto-mapped targets? (Y/N) = >, select Y (yes). Select 2. Bind by port name. Reboot the server by entering the following command:
reboot -- -r

Table of Contents

KernelBindingEmlxLunsSolarisb_sym001

Adding LUNs to the Solaris config file for Emulex HBA


Done

Overview This procedure adds LUNs to the Solaris Emulex config file (sd.conf). Before you add LUNs to sd.conf, verify that the HBA and HBA drivers have been installed in the Solaris computer. EMC storage array devices are addressed using Target IDs and LUNs. The Solaris configuration file /kernel/drv/sd.conf should contain all Targets and LUNs that a user may want to access. Devices accessed with Emulex Fibre Channel adapters and Emulex drivers can be up to 512 targets, with a maximum of 256 LUNs per target. LUN Numbers being 0 255. When editing the file, follow these precautions: Do not delete any original data from this file. 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 and avoid leading zeros (0) when

KernelBindingEmlxLunsSolaris_sym001

entering the LUN value. The instructions for dynamically adding new devices is described in the Manual Set Emulex Documentation Drivers and Software, which can be obtained from
http://www.emulex.com/ts/docfc/solframe.htm

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 /kernel/drv/sd.conf file 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 Emulex adapter and Emulex driver are addressed behind a single target ID with multiple LUNs (up to 256). Use the following format to construct entries in the sd.conf file for the target ID and LUN: name=sd class=scsi target=X lun=Y; This entry will not cancel the effect of any other class=scsi entries for target=X and lun=Y. If the user wants the sd driver to probe only for target=X and lun=Y on adapter lpfcZ, the class=scsi entries for target=X and lun=Y must be deleted. 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. The following sample sd.conf file illustrates how to add LUNs, connected to a Fibre Channel HBA, to sd.conf. The lines in bold are added to the file. This example adds devices to FA 1 (target 5) and FA 16 (target 6) of a storage system. You will add devices under the entries for the lpfc parent.
# Start lpfc auto-generated configuration -- do NOT alter or delete this line # WARNING: anything you put within this auto-generated section # will be DELETED if you execute pkgrm to remove the lpfc driver # package. # You may need to add additional lines to probe for additional # LUNs or targets. You SHOULD delete any lines that represent # lpfc targets or LUNs that are not used. # You should add any new entries between this line # and the End lpfc auto generated configuration line # name="sd" class="scsi" target=16 lun=0; # name="sd" class="scsi" target=17 lun=0; # A small number of LUNs for a RAID array # name="sd" class="scsi" target=17 lun=1; # name="sd" class="scsi" target=17 lun=2; # name="sd" class="scsi" target=17 lun=3; name="sd" class="scsi" target=5 lun=0; name="sd" class="scsi" target=5 lun=1; name="sd" class="scsi" target=5 lun=2; name="sd" class="scsi" target=5 lun=3; name="sd" class="scsi" target=5 lun=4; name="sd" class="scsi" target=5 lun=5; name="sd" class="scsi" target=6 lun=0;

KernelBindingEmlxLunsSolaris_sym001

name="sd" name="sd" name="sd" name="sd"

class="scsi" class="scsi" class="scsi" class="scsi"

target=6 target=6 target=6 target=6

lun=1; lun=2; lun=3; lun=4;

name="sd" class="scsi" target=6 lun=5;


# End lpfc auto-generated configuration -- do NOT alter or delete this line

3.

Reboot the host If you are using Emulex driver 5.x or older, you have to reboot the host for the changes in the sd.conf file to take effect. Driver 6.x or later supports adding new Target IDs and LUNs without rebooting, even if the unassigned Target IDs and LUNs were not in sd.conf at the last system reboot.

Table of Contents

KernelBindingEmlxLunsSolaris_sym001

You might also like