Emulex Fibre Channel Expansion Card for IBM eServer BladeCenter Linux Device Driver for 2.4 version kernels (C) Copyright International Business Machines Corporation 1999, 2005. All rights reserved. US Government Users Restricted Rights - Use, duplication, or disclosure restricted by GSA ADP Schedule Contract with IBM Corp. Note: Before using this information and the product it supports, read the general information in "Notices and trademarks" in this document. Driver Installation Notes ---------------------------------------------------------------------- 1. System Requirements 2. Driver Installation 3. Driver Uninstallation 4. Notes 5. Web Sites 6. Notices 7. Disclaimer ---------------------------------------------------------------------- 1. System Requirements The Emulex LPFC driver and LPFC DFC driver RPMs require gcc compiler tools and the kernel sources for the running kernel be installed on the system in order for the RPM installation to succeed. The following distributions of Linux are supported by the Emulex drivers: Red Hat Enterprise Linux 3 Update 6 and higher SuSE Linux Enterprise Server 8 with Service Pack 3 and 4 The lpfc-install script installs both the LPFC driver and the LPFC DFC driver RPMs. These RPMs install their driver sources to the /usr/src/lpfc directory, build their drivers for the currently running kernel, and then install the drivers to the proper directory for the currently running kernel. Once the RPMs are installed, the lpfc-install script creates a new ramdisk for the currently running kernel so that the 'lpfc' driver is loaded when the kernel is initialized during system startup. The 'elxlpfc' init script is also installed and configured to start and stop the 'lpfcdfc' driver during system startup and shutdown. 2. Driver Installation Refer to the LPFC Linux 7.3 documentation on the Emulex website at http://www.emulex.com for an installation manual that includes a complete set of options for the lpfc-install program Follow the quick link for Drivers, then Downloads, then Documentation. IBM strongly recommends uninstalling any old driver kits before installing the new driver kit. Please refer to the "Driver Uninstallation" section to uninstall previous versions of the Emulex LPFC 7.x or older driver. Create a download directory. Change to that directory and download the updated driver from the Emulex website. Untar the driver kit archive: # tar xvzf {download_directory_path}/{driver_kit_name}.tar.gz Log in as the user 'root' to a terminal, For SLES8 installed on HS or LS blades: A link must be created from /etc/UnitedLinux-release to /etc/SuSE-release: ln -s /etc/UnitedLinux-release /etc/SuSE-release Change directory to {download_directory_path}/{driver_kit_name} and execute the 'lpfc-install' script with no options to install the driver: ./lpfc-install Once the 'lpfc-install' script has completed successfully, the Emulex LPFC and LPFC DFC drivers will be loaded, and fibre channel disks that are properly connected to the system should be accessible. However, a reboot of the system is recommended to load the 'lpfc' driver through the ramdisk. For FAilover support: Go to http://www-307.ibm.com/pc/support/site.wss/document.do?lndocid=MIGR-63242 to download the latest RDAC driver for Linux 2.4 kernels Minimum driver version to support the Emulex 4Gb daughtercard is 9.00.a5.18 3. Driver Uninstallation To completely remove the Emulex LPFC and LPFC DFC drivers from a system, first exit out of all applications that use Fibre Channel-attached drives, then unmount the drives. Execute system command swapon -s to be sure that the OS is not using any swap space on Fibre Channel-attached drives Log in as the user 'root' to a terminal. To uninstall the failover driver, follow the instructions in the readme for the RDAC driver. Copy the 'lpfc-install' script to a temporary directory, such as '/tmp': cp /usr/src/lpfc/lpfc-install /tmp Next, execute the lpfc-install script in the temporary directory with the '--uninstall' option. /tmp/lpfc-install --uninstall 4. Notes - On SLES 8 SP3, the uninstall procedure does not fully remove all of the driver files that get built during installation. Run the 'lpfc-install --uninstall' command twice to remove all the driver files. - SLES 8 does not handle the Peripheral Qualifier Bit set to 1 correctly. If you need to use some lun scanning software to dynamically add new luns to a SLES 8 system, you must set the lpfc_inq_pqb_filter parameter. - On some large configurations, with many targets and other initiators, FC discovery may not complete before the SCSI subsystem probes for devices. If this occurs, some SCSI devices may not be detected at boot. The missing devices can be detected by requesting the SCSI subsystem to rescan via /proc/scsi/scsi and the "scsi add-single-device " mechanism. Emulex provides a script, called lun_scan.sh, which automates the scan requests for Emulex adapters. This script is contained in the driver applications kit. This script can be integrated into the system run-level transitions to ensure that all devices are fully detected. - The Emulex LPFC driver kit installs both the lpfc driver and the lpfcdfc driver. The lpfc driver cannot be removed if the lpfcdfc driver is loaded. To remove both drivers, first remove the lpfcdfc driver, then remove the lpfc driver as indicated by the following commands: modprobe -r lpfcdfc modprobe -r lpfc - If an old Emulex driver is archived during the installation process, the RPM uninstallation will generate a message stating that the /usr/src/lpfc directory is not empty and cannot be removed. This directory is removed later during uninstallation of the driver kit. - For Red Hat Enterprise Linux installations, the kernel-source package with the same version as the currently running kernel must be installed for the LPFC 7.3 driver build to succeed. - If an Emulex HBA was installed in a system before Linux was configured on that system, run 'lpfc-install --uninstall' before installing the Emulex LPFC driver kit to remove any configuration that the distribution may have performed. - If you are installing the Emulex Fibre Channel Driver on a PPC64 running SuSE SLES 8, the initial ramdisk (/boot/initrd) may not have been configured when the system was installed. The /boot/initrd file containing the Emulex Fibre Channel driver is required if you need access to the fibre channel drives early in the boot process. If this access is required follow these steps: 1. Install as usual using the lpfc-install script. 2. Edit /etc/lilo.conf and add the following line in the appropriate kernel entry; initrd = /boot/initrd 3. Execute the lilo command to finalize the changes. /sbin/lilo 4. When you reboot, the Emulex Fibre Channel driver will be loaded early in the boot process. - If you are using the 'lilo' boot loader on an x86-based machine, please execute the 'lilo' command after lpfc-install has successfully completed. This command will ensure that the ramdisk loads properly during subsequent reboots of the system. No additional steps are necessary if you are using the 'grub' boot loader. - If you are planning to upgrade the kernel, please consult the section "Upgrading the Kernel" in the Installation manual and follow the steps required for proper driver operation before you perform the upgrade. ________________________________________ 5.0 WEB Sites and Support Phone Number ________________________________________ You can download new and updated files for BladeCenter Fibre Channel products from http://www.ibm.com/support/. For a list of supported operating systems on legacy (non-shipping) controllers, see http://www.ibm.com/servers/eserver/serverproven/compat/us/. You can receive hardware service through IBM Services or through your IBM reseller, if your reseller is authorized by IBM to provide warranty service. See http://www.ibm.com/planetwide/ for support telephone numbers, or in the U.S. and Canada, call 1-800-IBM-SERV (1-800-426-7378). In the U.S. and Canada, hardware service and support is available 24 hours a day, 7 days a week. In the U.K., these services are available Monday through Friday, from 9 a.m. to 6 p.m. ____________________________ 6.0 Notices and Trademarks ____________________________ The following terms are trademarks of International Business Machines Corporation in the United States, other countries, or both: IBM BladeCenter eServer UNIX is a registered of The Open Group in the United States and other countries. Microsoft, Windows, and Windows NT are of Microsoft Corporation in the United States, other countries, or both. Linux is a trademark of Linus Torvalds in the United States, other countries, or both. Java and all Java-based trademarks and logos are trademarks of Sun Microsystems, Inc. in the United States, other countries, or both. Adaptec and HostRAID are trademarks of Adaptec, Inc. Other company, product, or service names may be trademarks or service marks of others. ________________ 7.0 Disclaimer ________________ THIS DOCUMENT IS PROVIDED "AS IS" WITHOUT WARRANTY OF ANY KIND. IBM DISCLAIMS ALL WARRANTIES, WHETHER EXPRESS OR IMPLIED, INCLUDING WITHOUT LIMITATION, THE IMPLIED WARRANTIES OF FITNESS FOR A PARTICULAR PURPOSE AND MERCHANTABILITY WITH RESPECT TO THE INFORMATION IN THIS DOCUMENT. BY FURNISHING THIS DOCUMENT, IBM GRANTS NO LICENSES TO ANY PATENTS OR COPYRIGHTS.NG WITHOUT LIMITATION, THE IMPLIED WARRANTIES OF FITNESS FOR A PARTICULAR PURPOSE AND MERCHANTABILITY WITH RESPECT TO THE INFORMATION IN THIS DOCUMENT. BY FURNISHING THIS DOCUMENT, IBM GRANTS NO LICENSES TO ANY PATENTS OR COPYRIGHTS.