QLogic QLA4010/QLA4010C/QLA4050/QLA4050C/ QLA4052C/QMC4052/QLE4060C/QLE4062C iscsi Driver for Linux Kernel 2.6.x.

Transcription

1 QLogic QLA4010/QLA4010C/QLA4050/QLA4050C/ QLA4052C/QMC4052/QLE4060C/QLE4062C iscsi Driver for Linux Kernel 2.6.x This software license applies only to QLogic customers. QLogic Corporation. All rights reserved. 1. Package Contents 2. OS Support 3. Supported Features 4. Using the Driver 4.1 Creating the Driver Disk or Folder 4.2 Installing the Driver 4.3 Removing the Driver 5. Driver Parameters 5.1 System Parameters 5.2 Multiple LUN Support 5.3 Driver Command Line Parameters 6. Additional Notes 7. Contacting Support Table of Contents 1. Package Contents The contents provided in the qla4xxx package are as follows: qla4xxx-vx.yy.zz.tar.gz driver package 2. OS Support The qla4xxx driver is compatible with the following OS platforms: Red Hat Enterprise Linux AS 4 (Update 5 and Update 6) Red Hat Enterprise Linux AS 5 (Update 1) Novell SLES 9 (SP3 and SP4) Novell SLES 10 (SP1) 3. Supported Features The qla4xxx supports the following: Up to 128 targets 4. Using the Driver This section provides the following procedures for using the iscsi driver for Linux: 4.1 Creating the Driver Disk or Folder 4.2 Installing the Driver 4.3 Removing the Driver iscsi Driver for Linux Kernel 2.6.x Readme File 1 of 5

2 4.1 Creating the Driver Disk or Folder To create a driver disk or folder: 1. Download the qla4xxx driver qla4xxx-vx.yy.zz.tar.gz file from QLogic's website. 2. If prompted What would you like to do with this file? choose Save this file to disk. 3. Insert a blank disk and download the file directly to the disk. 4.2 Installing the Driver The kernel sources should be already installed on the system for the relevant kernel. If the sources are not installed, install them from the RedHat/SuSE source CD(s) before continuing with the driver installation. Most distributions include the kernel source on the first disc of the distribution CDs. This section makes extensive use of the build.sh script located in driver source (extras/build.sh). This script currently supports driver compilation (installation and updates) on SLES9 and RHEL4 distributions on main hardware platforms. Execute one of the following commands as appropriate: Type the following command to build the driver sources based on the standard SLES9/RHEL4 build environment: #./extras/build.sh Type the following command to clean driver source directory of all build files (i.e. *.ko, *.o, etc): #./extras/build.sh clean Type the following command to rebuild the driver sources from scratch: #./extras/build.sh new This command is a shortcut for: #./build.sh clean #./build.sh Type the following command to build and install the driver module files: This command does the following: 1. Builds the driver.ko files. 2. Copies the.ko files to the appropriate /lib/modules/... directory. 3. Adds the appropriate directive in the modprobe.conf[.local] file to remove the qla4xxx_conf module when the qla4xxx modules are unloaded. NOTE: Refer to the OS specific Driver Disk Kit documentation for the procedure to install iscsi bootable systems. For details, see the following topics: Building a Driver from the Source Code Load the Driver Manually using INSMOD or MODPROBE Making a RAMDISK Image to Load the Driver Installing using the RPM Package Building a Driver from the Source Code From the source code, you can build a qla4xxx.ko for your host system, and load the driver manually or automatically using a RAMDISK image during system boot time. 1. Using the disk you created in Section 4.1, copy the qla4xxx-vx.yy.zz.tar.gz file to /qla4xxx. Type the following commands from the "/" (root) directory: # mkdir qla4xxx # cd qla4xxx # mount /mnt/floppy # cp /mnt/floppy/*.gz]. (the period at the end is required) # tar -xvzf *.gz # cd x.yy.zz 2. Build the driver modules from the source code by executing the build.sh script. For example: #./extras/build.sh To load the driver manually, see section To make a RAMDISK image to load the driver during system boot time, see section iscsi Driver for Linux Kernel 2.6.x Readme File 2 of 5

3 4.2.2 Load the Driver Manually using INSMOD or MODPROBE Before loading the driver manually, first build the driver binary from the driver source files. To load the driver directly from the local build directory, type the following command: # insmod qla4xxx.ko To load the driver using modprobe, perform the following steps: a. Install the driver module *.ko file to the appropriate kernel module directory: b. Type the following command to load the driver for qla4xxx HBAs: # modprobe -v qla4xxx To unload/uninstall the driver, execute one of the following commands: # rmmod qla4xxx # modprobe -r qla4xxx Making a RAMDISK Image to Load the Driver To build a RAMDISK image, using the driver built in section 4.2.1: 1. Install the driver module file (qla4xxx.ko) to the appropriate kernel module directory. For example: 2. Update the module configuration file as follows: For RedHat: Edit the /etc/modprobe.conf file and add the following entry, if it is not already present: alias scsi_hostadapter1 qla4xxx For SuSE: Edit the /etc/sysconfig/kernel file and modify the INITRD_MODULES directive as follows:... INITRD_MODULES="... qla4xxx" 3. Change to the /boot directory. 4. Type the following command to backup the current RAMDISK image: # cp -f initrd-2.6.[kernel_version].img initrd.2.6.[k_v].img.bak 5. Type the following command to build the RAMDISK image: For RedHat: # mkinitrd -f initrd-2.6.[kernel_version].img [kernel_version] For SuSE: # /sbin/mk_initrd 6. Reboot the system to load the RAMDISK image and the QLogic driver Installing using the RPM Package The Source RPM distribution package consists of the following file: qla4xxx-vx.xxbxx-y.noarch.rpm - Source RPM where: vx.xxbxx represents the driver version, for example, "v5.00.2" Y represents the RPM release version, for example, - 1 This RPM package contains the QLogic driver sources and the following utilities: build_qla4xxx.sh - A shell script that is executed during the initial installation of RPM. This script does the following: Rebuilds the kernel headers Builds the driver using the kernel headers Installs the newly created driver Builds the RAMDISK along with the QLogic driver installed by Source RPM Executes the LILO loader if necessary The script is installed in the /usr/src/qla4xx path. iscsi Driver for Linux Kernel 2.6.x Readme File 3 of 5

4 NOTE: To view the content of the RPM package, type the following command: # rpm -qpl qla4xxx-vx.xxbxx-y.zzzz.rpm more The following paragraphs describe the prerequisites to install the driver using the RPM package. The kernel-source/kernel-headers RPM must be installed. To verify the installation, type the following: # rpm -a -q grep kernel If the above RPMs are not installed, install them as follows: For RedHat distribution, type the following commands to extract the kernel-headers and kernelsources RPM files from the installation CDs: # cd /mnt/cdrom/redhat/rpms # rpm -iv kernel-headers*.rpm # rpm -iv kernel-source*.rpm NOTE: The kernel-headers RPM may or may not be on the Installation CD. The RPM is sometimes bundled along with the kernel-source RPM. For SuSE distribution, type one of the following commands to install the kernel-sources: # yast -i kernel-source # yast2 -i kernel-source The following paragraphs describe how to install/uninstall the QLogic Source RPM. To install the Source RPM, type the following command: # rpm -i qla4xxx-vx.xxbxx-y.noarch.rpm To uninstall the Source RPM, type the following command: # rpm -e qla4xxx-vx.xxbxx-y To install only the Driver Source from the Source RPM, type the following command: # rpm -i --noscripts qla4xxx-vx.xxbxx-y.zzzz.rpm Note the following when using the RPM Package: The Driver Source and the build_qla4xxx.sh utility are installed in the /usr/src/qla4xxx path upon installation of the Source RPM. The driver binaries are installed in the /lib/modules/{kernelversion}/kernel/drivers/scsi/ path. The driver binaries are installed ONLY for the running kernel. You must reboot the system for the new RAMDISK to take effect. The reboot automatically loads the new QLogic driver installed by the Source RPM. Or, you can manually load the "qla4xxx" driver by typing the following command: # modprobe -v qla4xxx 4.3 Removing the Driver To remove the iscsi driver for Linux, type one of the following commands to unload/uninstall the driver: # rmmod qla4xxx # modprobe -r qla4xxx 5. Driver Parameters This section provides the following parameter information: 5.1 System Parameters 5.2 Multiple LUN Support 5.3 Driver Command Line Parameters 5.1 System Parameters Most driver and device parameters are exported via sysfs as a regular file, so you can change parameters using regular commands. Device parameters are located in the following path: /sys/class/scsi_device/<host>:<bus>:<target>:<lun>/device/ Timeout parameter. In the 2.6 kernel, a command timeout is 30 seconds. If a command takes longer than 30 seconds, which could happen in a network environment, it may be necessary to increase the timeout value in sysfs for the device. For example: echo 60 >/sys/class/scsi_device/4:0:0:0/device/timeout Rescan parameter. This parameter initiates a rescan on the device. The Linux driver does not recognize dynamically added devices automatically; therefore, a manual rescan must be performed. The following is an example of the rescan parameter: echo "- - -" > /sys/class/scsi_host/hostx/scan For example: echo "- - -" > /sys/class/scsi_host/host6/scan Where "hostx" is replaced by your "Host number". iscsi Driver for Linux Kernel 2.6.x Readme File 4 of 5

5 5.2 Multiple LUN Support If the SCSI Mid-Layer is compiled as a module, configure support for multiple LUNs as follows: 1. Locate the modprobe.conf (loadable module configuration file) in the /etc directory. 2. Open the modprobe.conf file. 3. Add the following line in the modprobe.conf to scan for multiple LUNs: options scsi_mod max_luns=255 NOTE: If you have multiple adapters, set max_luns to the largest number of LUNs supported by any one of these adapters. 5.3 Driver Command Line Parameters The driver gets its parameters from the command line itself or from the modprobe 'option' directive found in the modules.conf file. The parameters are in the <keyword>=value format. For example: ql4xdiscoverwait=60 In this format, <keyword> is one of the following option parameters: Usage: insmod qla4xxx <keyword>=value Driver Command Line Parameters Parameter Description Default ql4xmaxqdepth This parameter defines the maximum queue depth reported to the SCSI Mid-Level per device. The queue depth 2 specifies the number of outstanding requests per LUN. (obsolete with sysfs) ql4xdiscoverywait This parameter defines how long to wait for a port during boot-time. 60 ql4xcmdretrycount This parameter defines the maximum number of SCSI Mid-Level retries allowed per command. 20 extended_error_logging This parameter enables debug and defines the debug level to use. The debug information is written to the /var/ 0 (disable) log/messages file. For a complete list of the available parameters, enter the following command: # modinfo -p qla4xxx.ko Usage examples: # insmod qla4xxx.ko ql4xdiscoverwait=60 6. Additional Notes Please refer to the Release Notes (release.txt). 7. Contacting Support Please feel free to contact your QLogic approved reseller or QLogic Technical Support at any phase of integration for assistance. QLogic Technical Support can be reached by the following methods: Web: North America Contact Information support@qlogic.com Phone: (952) Support contact information for other regions of the world is available at the QLogic website: Go to Top Copyright All rights reserved worldwide. QLogic, the QLogic logo, and the Powered by QLogic logo are registered trademarks of QLogic Corporation. All other brand and product names are trademarks or registered trademarks of their respective owners. iscsi Driver for Linux Kernel 2.6.x Readme File 5 of 5