EMC Fibre Channel with QLogic Host Bus Adapters for the Linux v2.6.x Kernel Environment and the v8.x-Series Driver P/N 300-002-803 REV A05 EMC Corporation Corporate Headquarters: Hopkinton, MA 01748-9103 1-508-435-1000 www.EMC.
Copyright © 2001–2007 EMC Corporation. All rights reserved. Published: April, 2007 EMC believes the information in this publication is accurate as of its publication date. The information is subject to change without notice. THE INFORMATION IN THIS PUBLICATION IS PROVIDED “AS IS.” EMC CORPORATION MAKES NO REPRESENTATIONS OR WARRANTIES OF ANY KIND WITH RESPECT TO THE INFORMATION IN THIS PUBLICATION, AND SPECIFICALLY DISCLAIMS IMPLIED WARRANTIES OF MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE.
Contents Preface ............................................................................................................................. 7 Chapter 1 Introduction Purpose of this document................................................................ 12 QLogic SANsurfer and SANsurferCLI....................................12 Host connectivity .............................................................................. 13 EMC storage array-specific settings...........................................
Installation methods for the QLogic v8.xx.xx driver................... 29 Installing the QLogic v8.xx.xx Driver via the QLogic DKMS RPM: Method 1 .............................................................. 30 Installing the QLogic v8.xx.xx driver via the QLogic installation script: Method 2 ..................................................... 32 File modifications on SLES 9 hosts .......................................... 42 Uninstallation methods for the QLogic v8.xx.xx driver .............
Installing onto the EMC storage array with the QLogic v8.x-series driver ...........................................................71 Upgrading the kernel .................................................................72 Appendix A Setting Up External Boot for IBM Blade Server HS40 (8839) Configure HS40 BladeCenter server to boot from external array ..................................................................................... 74 Index ...........................................................
Preface As part of an effort to improve and enhance the performance and capabilities of its product line, EMC from time to time releases revisions of its hardware and software. Therefore, some functions described in this document may not be supported by all revisions of the software or hardware currently in use. For the most up-to-date information on product features, refer to your product release notes.
Preface For information on Navisphere, refer to the Navisphere Management software documentation in the Documentation Library on EMC PowerLink. http://Powerlink.EMC.com Conventions used in this document EMC uses the following conventions for special notices. Note: A note presents information that is important, but not hazard-related. ! CAUTION A caution contains information essential to avoid data loss or damage to the system or equipment.
Preface Where to get help Courier: Used for: • System output, such as an error message or script • URLs, complete paths, filenames, prompts, and syntax when shown outside of running text Courier bold: Used for: • Specific user input (such as commands) Courier italic: Used in procedures for: • Variables on command line • User input variables <> Angle brackets enclose parameter or variable values supplied by the user [] Square brackets enclose optional values | Vertical bar indicates alternate se
Preface 10
1 Invisible Body Tag Introduction This document describes the procedures for installing an EMC-approved QLogic host bus adapter (HBA) into a Linux host environment and configuring the host for connection to an EMC storage array over Fibre Channel. ◆ ◆ ◆ Purpose of this document ................................................................. 12 Host connectivity ............................................................................... 13 EMC storage array-specific settings .......................
Introduction Purpose of this document This document is meant to assist in the installation and setup of QLogic Host Bus Adapters (HBAs) and the v8.x-series driver on Linux v2.6.x hosts. The focus of this document is to set up Linux hosts using the QLogic v8.x-series driver downloadable from the EMC-approved section of the QLogic website. QLogic SANsurfer and SANsurferCLI QLogic's SANsurfer program is a GUI-based utility and the SANsurferCLI is a text-based utility.
Introduction Host connectivity Review the EMC Support Matrix or contact your EMC® representative for the latest information on qualified HBAs, drivers, and Linux distributions. Note: EMC does not support mixing different types of Fibre Channel HBA (including different types from the same vendor) in a server. The Fibre Channel HBA driver functions as a device driver layer below the standard Linux SCSI adapter driver.
Introduction EMC storage array-specific settings Please refer to Host Connectivity Guide for Linux, available at http://Powerlink.EMC.com,for EMC storage array-specific settings.
2 Invisible Body Tag Installing and Configuring the QLogic HBA and v8.x-Series Driver This chapter describes the procedures for installing an EMC-approved QLogic host bus adapter (HBA) into a Linux host and configuring the host for connection to an EMC storage array over Fibre Channel. ◆ ◆ ◆ ◆ ◆ ◆ ◆ ◆ ◆ ◆ ◆ ◆ Installing the HBA ............................................................................. Configuring the BIOS settings .........................................................
Installing and Configuring the QLogic HBA and v8.x-Series Driver Installing the HBA Before the QLogic HBA is installed, the host must be configured with Linux. Install the Linux kernel (including sources) from the distribution installation CD by following the procedure provided in the distribution installation guide. Partition the boot drive, and select the packages and services necessary for the host. To install the QLogic HBA, follow the instructions included with your adapter.
Installing and Configuring the QLogic HBA and v8.x-Series Driver Configuring the BIOS settings After the HBA is installed, follow these steps during system boot to verify and configure HBA firmware settings. To use SANsurfer or SANsurferCLI for this function refer to the SANsurfer or SANsurferCLI documentation you have downloaded. Refer to the EMC Support Matrix for required BIOS versions for qualified HBAs.
Installing and Configuring the QLogic HBA and v8.x-Series Driver – If the banner displays the required version, continue to “EMC recommended HBA BIOS settings” on page 20. – If the banner does not display the required version, upgrade the firmware as described under the “Upgrading the HBA BIOS” on page 19; then proceed to “EMC recommended HBA BIOS settings” on page 20.
Installing and Configuring the QLogic HBA and v8.x-Series Driver Upgrading the HBA BIOS The BIOS may be upgraded using the QLogic SANsurfer GUI or SANsurferCLI text interface, or by using a DOS bootable floppy. Upgrading the HBA BIOS using QLogic SANsurfer The SANsurfer GUI may be downloaded from the EMC-approved section of the QLogic website. To update the BIOS using the SANsurferCLI, please refer to the QLogic provided documentation on their website for detailed instructions.
Installing and Configuring the QLogic HBA and v8.x-Series Driver c. Click the EMC link below OEM Models. d. Find the NVRAM file for the HBA(s) in your system, and click the associated Download link to save the file. 2. The file is a self-extracting .zip file that must be extracted to a bootable floppy diskette, as follows: a. Insert a diskette into a Microsoft Windows 9x machine. b. Open any DOS window. c. At the DOS prompt, format the diskette by entering: format /s a: d.
Installing and Configuring the QLogic HBA and v8.x-Series Driver EMC recommended NVRAM settings for Linux Table 1 lists the NVRAM parameters and their values. The QLogic default values are those that ship with a standard HBA that wasn't included in an EMC package. The EMC-recommended settings depend upon whether or not failover functionality is used. The settings listed under the No Failover Functionality heading are those that have been pre-configured in the EMC-approved NVRAM file.
Installing and Configuring the QLogic HBA and v8.x-Series Driver QLogic Bios settings (continued) Table 1 EMC recommended settings Data Rate QLogic default No Multipath functionality With Multipath functionality 2 1 2 4 1 2 4 Note: Match port data rate on real environment. Note: Match port data rate on real environment.
Installing and Configuring the QLogic HBA and v8.x-Series Driver The values for the Connection Options parameter are as follows: ◆ 0 for Loop Only ◆ 1 for Point to Point ◆ 2 for Loop preferred, otherwise Point to Point Note: For Linux attach, EMC recommends setting the Connection Options parameter to 1 when attached to a fabric and to 0 when attached to an EMC Storage Array directly. * The WWNN of the server's boot LUN must be listed in this field.
Installing and Configuring the QLogic HBA and v8.x-Series Driver Manually setting the topology for QLogic HBAs The EMC default setting for the topology is set to 2 (Loop preferred; otherwise, point to point). For Linux environments, it is recommended that the Connection Options parameter be set to 1 when attached to a fabric and to 0 when attached to an EMC Storage Array directly. Follow these steps to set the NVRAM variables for the topology: 1. Boot the host.
Installing and Configuring the QLogic HBA and v8.x-Series Driver Manually setting the data rate for QLogic HBAs The EMC default setting for the data rate on the QLA23xx/QLE23xx HBAs is Auto Select mode. If necessary, the mode may be set manually to 1 GB, 2 GB, or Auto Select mode. The EMC default setting for the data rate on the QLA24xx/QLE24xx 4 GB capable HBAs is Auto Select mode. If necessary, the mode may be set manually to 1 GB, 2 GB, or Auto Select mode.
Installing and Configuring the QLogic HBA and v8.x-Series Driver Configuring the Linux v2.6.x host with the QLogic v8.x-series driver Using the QLogic adapter with the Linux operating system requires HBA driver software. The driver functions at a layer below the Linux SCSI driver to present Fibre Channel devices to the operating system as if they were standard SCSI devices. Refer to the latest EMC Support Matrix for specific qualified kernel versions and distributions.
Installing and Configuring the QLogic HBA and v8.x-Series Driver Installation instructions for the QLogic v8.x-series driver Note: Only the QLogic v8.01.xx driver provides support for the 4 GB capable QLA24xx/QLE24xx-series HBAs , not the v8.00.xx driver. Installing the QLogic v8.xx.xx drivers The QLogic v8.xx.xx driver is supported on QLA23xx/QLE23xx-series HBAs for RHEL 4.0, RHEL 4.0 U1, and SLES 9 SP1 hosts. The QLogic v8.01.06 driver introduces support for the 4 GB capable QLA24xx/QLE24xx-series HBAs.
Installing and Configuring the QLogic HBA and v8.x-Series Driver 4. Find the desired and supported driver for the kernel version and distribution, and click the associated Download link to save the file. What next? Select a method to install the driver onto the Linux host: For the QLogic v8.xx.xx driver: 28 ◆ To create a modular v8.xx.xx driver using the DKMS RPM, refer to “Installing the QLogic v8.xx.xx Driver via the QLogic DKMS RPM: Method 1” on page 30. ◆ To create a modular v8.xx.
Installing and Configuring the QLogic HBA and v8.x-Series Driver Installation methods for the QLogic v8.xx.xx driver The QLogic v8.xx.xx driver may be installed onto a Linux host using one of the two following methods: ◆ Method One - Use the QLogic DKMS RPM to compile and install the modular driver for Dell servers running RHEL 4.0 systems and attached to EMC Storage Arrays. This method requires no manual edits for Dell servers attached to EMC Storage Arrays.
Installing and Configuring the QLogic HBA and v8.x-Series Driver To stop the PowerPath service, issue one of the two following commands: /etc/init.d/PowerPath stop or service PowerPath stop 5. If the QLogic SANsurfer daemon qlremote is installed and enabled on the host, then the qlremote service must be stopped in order for the driver to be removed from the currently running kernel. To stop the qlremote service, issue one of the two following commands: /etc/init.
Installing and Configuring the QLogic HBA and v8.x-Series Driver 3. Uncompress and extract the source files from the tar archive: [root@l82bi205 extra]# tar zxvf qla2xxx-v8.xx.xx-2dkms.tar.gz The initial decompression will provide you with the following: qla2xxx-v8.xx.xx-2/ qla2xxx-v8.xx.xx-2/qla2xxx-v8.xx.xx-2dkms.noarch.rpm qla2xxx-v8.xx.xx-2/dkms-2.0.5-1.noarch.rpm qla2xxx-v8.xx.xx-2/README.dkms 4. Install the DKMS RPM: cd qla2xxx-v8.xx.xx-2 rpm -ivh dkms-2.0.5-1.noarch.rpm Preparing...
Installing and Configuring the QLogic HBA and v8.x-Series Driver Installing the QLogic v8.xx.xx driver via the QLogic installation script: Method 2 This section guides you through the process of installing and utilizing the QLogic installation script for RHEL 4.0 and SLES 9 SP1 distributions. The script will build and install the driver and will modify the /etc/modprobe.conf file on RHEL 4.0 hosts and the /etc/modprobe.conf.local and /etc/sysconfig/kernel files on SLES 8 hosts.
Installing and Configuring the QLogic HBA and v8.x-Series Driver Note: EMC does not support the persistent binding implementation contained within the QLogic driver. As a result, it is recommended that the driver be compiled and installed without persistent binding enabled. This can be accomplished by using the 'dp' switch with the installation script. Proceed with the installation. cd qlafc-linux-8.xx.xx-1-install/.
Installing and Configuring the QLogic HBA and v8.x-Series Driver The SANsurferCLI (SCLI) is a command line interface that provides more flexibility for performing HBA configuration, device discovery, Option ROM and NVRAM updates, etc. RHEL 4.0 examples An example of the console output reported by the QLogic installation script on RHEL 4.0 hosts is as follows: ./qlinstall -i -dp #*********************************************************# # QLogic HBA Linux Driver Installation # # Version: 1.00.
Installing and Configuring the QLogic HBA and v8.x-Series Driver Building default persistent binding using SCLI Configuration saved on HBA port 0. Changes have persistent storage. Please reload the QLA driver module/rebuild the the saved configuration to take effect. Configuration saved on HBA port 1. Changes have persistent storage. Please reload the QLA driver module/rebuild the the saved configuration to take effect. been saved to RAM disk for been saved to RAM disk for Saved copy of /etc/modprobe.
Installing and Configuring the QLogic HBA and v8.
Installing and Configuring the QLogic HBA and v8.x-Series Driver Files modifications on RHEL 4.0 hosts An example of the installation script's modifications to the file /etc/modprobe.
Installing and Configuring the QLogic HBA and v8.x-Series Driver Loaded module qla2300 Installing scli.... Preparing... ################################################## scli ################################################## Installation completed successfully. Building default persistent binding using SCLI Configuration saved. Changes have been saved to persistent storage. Please reload the QLA driver module/rebuild the RAM disk for the saved configuration to take effect. Configuration saved.
Installing and Configuring the QLogic HBA and v8.
Installing and Configuring the QLogic HBA and v8.
Installing and Configuring the QLogic HBA and v8.
Installing and Configuring the QLogic HBA and v8.x-Series Driver File modifications on SLES 9 hosts An example of the installation script's modifications to the file /etc/sysconfig/kernel is as follows: INITRD_MODULES="cciss reiserfs qla2xxx_conf qla2xxx qla2300" An example of the installation script's modifications to the file /etc/modprobe.conf.
Installing and Configuring the QLogic HBA and v8.x-Series Driver Uninstallation methods for the QLogic v8.xx.xx driver This section describes how to successfully uninstall the QLogic v8.xx.xx driver from a Linux host. The method used to uninstall the driver is dependent upon the installation package: ◆ Method One - Using the QLogic DKMS RPM ◆ Method Two - Using the QLogic installation script Uninstalling the QLogic v8.xx.
Installing and Configuring the QLogic HBA and v8.x-Series Driver Uninstalling the QLogic v8.xx.xx driver via the QLogic installation script: Method 2 This section provides guidance for uninstalling the QLogic v8.xx.xx driver via the QLogic installation script. The driver may be removed from the system with the 'u' switch for the qlinstall script. The following are example steps to uninstall the QLogic driver. Please also refer to the README file in the driver package 1.
Installing and Configuring the QLogic HBA and v8.x-Series Driver Table 2 Supported driver versions OS Driver version Asianux 2.0 Miracle Linux SE 4.0 RedFlag DC Server 5.0 Haansoft Linux 2006 Server 8.00.03b1 Note: Does not support the 4 Gb HBAs RHEL4 U3 Asianux 2.0 SP1 Miracle Linux SE 4.0 SP1 RedFlag DC Server 5.0 SP1 Haansoft Linux 2006 Server SP1 8.01.02-d4 RHEL4 U4 8.01.04-d7 RHEL5 8.01.07-k1 SLES9 SP3 8.01.02-sles SLES10 8.01.
Installing and Configuring the QLogic HBA and v8.x-Series Driver QLogic v8.x-series driver parameters The QLogic driver contains a number of parameters that may be modified to perform failover functionality or to enhance performance. The QLogic and EMC recommended values are inTable 3 and descriptions of the parameters follow the table. The values to which these parameters are set are dependent upon the environment and the type of applications and subsequent I/O being used on the system.
Installing and Configuring the QLogic HBA and v8.x-Series Driver Table 3 QLogic v8.
Installing and Configuring the QLogic HBA and v8.x-Series Driver Table 3 QLogic v8.x-series driver parameters Parameters QLogic default values ql2xexcludemodel EMC default recommendations 0 0 recoveryTime 10 seconds 10 seconds failbackTime 5 seconds 5 seconds Description of QLogic v8.x-series driver parameters When attaching to CLARiiON and Symmetrix Storage Arrays, EMC recommends that the ConfigRequired and ql2xfailover parameters be set to zero.
Installing and Configuring the QLogic HBA and v8.x-Series Driver ◆ ql2xintrdelaytimer: defines the amount of time for the firmware to wait before generating an interrupt to the host as notification of the request completion. ◆ ql2xenablezio: defines whether to enable ZIO functionality. ◆ ql2xplogiabsentdevice: defines whether to enable a PLOGI to devices that are not present after a fabric scan. This is needed for several broken switches.
Installing and Configuring the QLogic HBA and v8.x-Series Driver ◆ ql2xlbType: defines the load balancing method for the driver. If set to 0, then all LUNs will be exposed on the first active path. If set to 1, then the load will be balanced across all active optimized controller ports. ◆ ql2xexcludemodel: defines HBA models to be excluded from being marked as available for failover functionality.
Installing and Configuring the QLogic HBA and v8.x-Series Driver 2. Add the options line for the appropriate driver settings. options qla2xxx ConfigRequired=0 ql2xfailover=0 For example, the /etc/modprobe.conf file on RHEL 4.0 might look as follows: alias eth0 tg3 alias eth1 tg3 alias scsi_hostadapter megaraid_mbox alias scsi_hostadapter2 qla2xxx alias scsi_hostadapter3 qla2xxx_conf alias scsi_hostadapter4 qla2300 options qla2xxx ConfigRequired=0 ql2xfailover=0 And the /etc/modprobe.conf.
Installing and Configuring the QLogic HBA and v8.x-Series Driver Displaying the QLogic v8.x-series driver parameter information via modinfo The QLogic v8.x-series driver parameters and their definitions may be viewed by using the modinfo command. This command may be used on any Linux kernel module. Note: EMC does not support the failover functionality of the QLogic driver. The modinfo command may be run on the qla2300, qla2xxx_conf, and qla2xxx modules.
Installing and Configuring the QLogic HBA and v8.x-Series Driver parm: ql2xprocessnotready:Option to disable handling of NOT-READY in the driver. Default is 1 - Handled by the driver. Set to 0 - Disable the handling inside the driver parm: ql2xloginretrycount:Specify an alternate value for the NVRAM login retry count. parm: ql2xdoinitscan:Signal mid-layer to perform scan after driver load: 0 -- no signal sent to mid-layer.
Installing and Configuring the QLogic HBA and v8.x-Series Driver Additional notes Device reconfiguration: procedures The Linux v2.6.x kernel lacks a command built into the kernel that allows for a dynamic SCSI bus reconfiguration such as drvconfig or ioscan. The SCSI bus may be rescanned with a system reboot, or with a removal and reinsertion of the modular driver. In either case, all I/O must be stopped and all other mounted filesystems must be unmounted before rebooting or removing the modular driver.
Installing and Configuring the QLogic HBA and v8.x-Series Driver /etc/init.d/PowerPath stop or service PowerPath stop ◆ If the QLogic SANsurfer daemon qlremote is installed and enabled on the host, then the qlremote service must be stopped in order for the driver to be removed from the currently running kernel. To stop the qlremote service, issue one of the two following commands: /etc/init.d/qlremote stop or service qlremote stop The modprobe command is a wrapper or an extension to insmod and rmmod.
Installing and Configuring the QLogic HBA and v8.x-Series Driver The v8.x series driver consists of multiple modules. For example, if the command lsmod is invoked on a server with a QLA2340-E-SP HBAs installed, the following three modules will be reported: ◆ qla2xxx_conf - The QLogic Linux driver configuration module containing information regarding persistent binding. ◆ qla2xxx - The low level QLogic Linux HBA driver module.
Installing and Configuring the QLogic HBA and v8.x-Series Driver of the regularly attached devices and the mount table altered accordingly. HPQ server-specific note When using HPQ systems, it is highly recommended that the HPQ SmartStart CD be run to configure the HPQ server prior to installing the Linux operating system. The SmartStart CD is shipped by HPQ with their systems and is a bootable CD that is used to configure HPQ servers.
Installing and Configuring the QLogic HBA and v8.x-Series Driver (CLARiiON Only) disconnected ghost LUNs When a Linux host is attached to both SPs in a CLARiiON storage array, the driver will report a disconnected LUN 0 on SPB and a failure to read the capacity of the device. The Navisphere Host Agent requires that disconnected LUN 0 be reported properly. A device file name is allocated to the disconnected LUN 0 in the /dev filesystem, but the device cannot be mounted, partitioned, or otherwise accessed.
3 Invisible Body Tag Configuring a Boot Device on an EMC Storage Array EMC supports booting Linux from an EMC storage array through an EMC-qualified QLogic Fibre Channel HBA. (Refer to the EMC Support Matrix for specific HBAs, BIOS revisions, and drivers.) ◆ ◆ ◆ ◆ Cautions and restrictions for booting from EMC storage array.. Common limitations .......................................................................... Configuring a Symmetrix boot device............................................
Configuring a Boot Device on an EMC Storage Array Cautions and restrictions for booting from EMC storage array ! CAUTION If Linux loses connectivity long enough, the disks disappear from the system. To prevent further data from being lost in a situation like this, EMC recommends that the error behavior be changed from continue to remount read-only. To make this change, consult the manpage for tune2fs. A hard reboot is required to bring the system back to a usable state.
Configuring a Boot Device on an EMC Storage Array Symmetrix-specific cautions and restrictions ◆ Lost connection to Symmetrix Storage Array (pulled or damaged cable connection). ◆ Symmetrix service and upgrade procedures, such as on-line Symmetrix microcode upgrades and/or configuration changes. ◆ Symmetrix director failures, including failed lasers. ◆ Symmetrix Storage Array power failure. ◆ Storage area network service and upgrade procedures, such as firmware upgrades or hardware replacements.
Configuring a Boot Device on an EMC Storage Array Common limitations Boot configurations must not deviate from the following limitations established by EMC: ◆ The EMC Storage device must have enough disk space to hold the Linux operating system. ◆ A maximum of 32 volumes may be configured on the EMC Storage Array port that will be used to boot Linux. ◆ EMC recommends that you install, rather than upgrade, the kernel-source and kernel UP, SMP, and Hugemem RPMs.
Configuring a Boot Device on an EMC Storage Array Note: The EMC-recommended method is to use LUN masking. • CLARiiON ghost LUN — If the LUN 0 presented to a SCSI path is not owned by the SP attached to that path, a disconnected LUN 0 (ghost LUN) will be presented. The ghost LUN is not write-enabled so that the MBR cannot be written to it. Always ensure that the boot LUN is owned by the correct SP and does not trespass at any time; trespass of the boot LUN would result in a system crash.
Configuring a Boot Device on an EMC Storage Array ◆ Booting from the SAN requires the use of a Navisphere Management station with the Navisphere Manager or NaviCLI installed. The stations must be separate from the boot server, but networked to the CLARiiON Storage Array. Symmetrix-specific limitations: 64 ◆ When attached to a Symmetrix, the physical-to-logical split must be 1:8 or less (1:7, 1:6, etc.). EMC supports the use of any LUN from 00 through FF as a boot disk.
Configuring a Boot Device on an EMC Storage Array Configuring a Symmetrix boot device This section describes how to install an EMC-qualified version of Linux onto an EMC Symmetrix Storage Array connected to an Intel-based x86 and x86_64 class systems and AMD Opteron-based x86_64 class systems. Preparing the Symmetrix storage array ◆ It is recommended that Volume Logix be enabled on the Symmetrix Storage Array for LUN masking purposes.
Configuring a Boot Device on an EMC Storage Array ◆ Disable the BIOS on any other HBAs in the system other than the QLogic HBA designated for booting. Configuring the QLogic BIOS for SAN boot After the BIOS is installed and enabled, it must be configured for use for booting from the SAN. The following procedure describes how to configure the BIOS. 1. Connect the Symmetrix fibre channel port to the adapter in the lowest-numbered PCI slot in the server.
Configuring a Boot Device on an EMC Storage Array 5. From the Configuration Settings menu, select Adapter Settings and press Enter. 6. From the Host Adapter Settings menu, select Host Adapter BIOS and press Enter to enable it if it is not already enabled. Note: Refer to the Table 1 on page 21 for recommended settings. 7. Press ESC to exit the Configuration Settings menu. 8. From the Configuration Settings menu, select Selectable Boot Settings and press Enter. 9.
Configuring a Boot Device on an EMC Storage Array Configuring a CLARiiON boot device This section describes how to install an EMC-qualified version of Linux onto an EMC CLARiiON Storage Array connected to an Intel-based x86 and x86_64 class systems and AMD Opteron-based x86_64 class systems. Preparing the CLARiiON storage array ◆ It is recommended that Access Logix be enabled on the CLARiiON Storage Array for LUN masking purposes.
Configuring a Boot Device on an EMC Storage Array ◆ SCSI hard disks are allowed in SAN boot configurations. However, the BIOS for the disk's SCSI adapters must be disabled. Any SCSI disks attached to the host should be disconnected during the operating system installation. ◆ For servers with SCSI CD-ROM drives, ensure that the BIOS is enabled on the SCSI channel that includes the CD-ROM. Disable the BIOS on any other integrated SCSI channels.
Configuring a Boot Device on an EMC Storage Array • If there are multiple QLogic HBAs, a list of addresses occupied by those HBAs appears. Since the EMC storage array is attached to the lowest-numbered PCI slot, select the first adapter from the list; then press Enter. The Fast!UTIL Options menu appears. 4. From the Fast!UTIL Options menu, select Configuration Settings and press Enter.. 5. From the Configuration Settings menu, select Adapter Settings and press Enter.. 6.
Configuring a Boot Device on an EMC Storage Array 13. When the QLogic banner is displayed (as shown in step 2), press Ctrl-Q. 14. Once the Fast!UTIL loads, select the Configuration Settings menu and press Enter.. 15. From the Configuration Settings menu, select the Selectable Boot Settings menu and press Enter.. 16. From the Selectable Boot Settings menu, select Selectable Boot Device and press ENTER to enable this option if it is not already enabled. 17. Select Current Boot Node Name and press Enter..
Configuring a Boot Device on an EMC Storage Array Using the installation CDs, boot the server to be installed. The installation may be performed as it would when using an internal HBA/controller driver. Once the installation is complete, use QLogic driver installation script to upgrade the driver to the EMC-qualified driver version as follows: ./qlinstall -up Note: Please refer to the EMC Support Matrix for the most recent information on qualified kernel and driver releases as well as architectures.
A Invisible Body Tag Setting Up External Boot for IBM Blade Server HS40 (8839) This appendix contains information on setting up external boot for IBM Blade Server HS40. ◆ Configure HS40 BladeCenter server to boot from external array..
Setting Up External Boot for IBM Blade Server HS40 (8839) Configure HS40 BladeCenter server to boot from external array IBM HS40 (8839) Blade Servers encounter a dual-port HBA conflict when attempting to configure boot BIOS to boot from an external array. To configure an HS40 BladeCenter server to boot successfully follow the steps below. 1. Create a single zone containing the HBA port from which you want to boot. This prevents any conflicts with the other fibre port. 2.
Index B M BIOS Settings 17 Version 17 boot configuration 62 boot device cautions and restrictions 60 boot disk 60 booting from an EMC storage array 60 modprobe 55 C CLARiiON 58 disconnected ghost LUNs 58 configuration boot 62 E EMC Support Matrix 17, 26 EMC Support Matrixall 26 Q QLogic Linux driver, unloading and reloading the modular 54 R reboot 57 rebooting the host 54 rmmod 55 S SANsurfer 17 SANsurferCLI 17 system booting 60 crash events 60 F Fast!Util 17 H HBA installation 16 I insmod 55 in
Index 76
