Emulex 4Gb Fibre Channel Expansion Card for IBM eServer BladeCenter SANBooot for RH Linux (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. EmulexSANBootRHReadme.txt Version 1.00 05/22/06 ________ CONTENTS ________ 1.0 Overview 2.0 Change History 3.0 Installation and Setup Instructions 4.0 Configuration Information 5.0 Unattended Mode 6.0 Web Sites and Support Phone Number 7.0 Trademarks and Notices 8.0 Disclaimer _______________ 1.0 Overview _______________ This README describes the current procedure for installing to a SAN disk on RedHat4 and SLES9 for x86, EM64T/AMD64, for x86, EMT64/AMD64 and PPC. ____________________ 2.0 Change History ____________________ Version 1.00 05/22/06 - Initial Release _________________________________________ 3.0 Installation and Setup Instructions _________________________________________ To ensure proper installation, the initial OS install must be installed in a single path configuration. After the OS is installed, refer to the failover driver instructions available from the Linux failover driver, or storage array failover failover. All local drives attached to the blades should be disabled during the remote boot installation. _________________________________________ 3.1 RH4 for x86, EM64T and AMD64 Installation _________________________________________ 1.) Configure the 4Gb Expansion Card for remote boot by using the Alt+E Boot BIOS menus. For more information on the Boot BIOS menus, refer to the Emulex 4Gb Expansion Card Installation Guide. 2.) Boot to RedHat Installation CD 3.) Continue the installation procedure 4.) When you reach the Disk Partitioning Setup portion of the install, you can choose to install via automatic or manual partitioning. When choosing automatic partioning, you should choose to install to the "sda" disk which is the external Fibre channel disk discovered during the installation. 5.) Once you select the external disk, you can complete the rest of the installation. _________________________________________ 3.2 SLES9 for x86 and EM64T/AMD64 Installation _________________________________________ 1.) Configure the 4Gb Expansion Card for remote boot by using the Alt+E Boot BIOS menus. For more information on the Boot BIOS menus, refer to the Emulex 4Gb Expansion Card Installation Guide. 2.) Boot to SLES installation CD 3.) Continue the installation procedure 4.) When you reach the Disk Partitioning Setup portion of the install, you can choose to install via automatic or manual partitioning. When choosing automatic partioning, you should choose to install to the "sda" disk which is the external Fibre channel disk discovered during the installation. 5.) Once you select the external disk, you can complete the rest of the installation. ________________________________________ 3.3 RHEL4 for PPC Installation for JS21 _________________________________________ 1.) Prerequisites: a) Preconfigure SAN to insure that installation LUN will be accesible by Emulex HBA - Record IEEE address information for each from labels on Emulex HBA prior to HBA installation - WWPN for port [n] will be 0x1000{port[n]_ieee_address} - WWNN for port [n] will be 0x2000{port[n]_ieee_address} - Configure switch zoning such that each HBA host port is in same zone as desired storage target - Configure storage target such that target installation LUN is acessible by HBA host port b) If installing from CD Media, use documented procedure for your blade center to assign CD media to blade containg Emulex HBA. Install RHEL4 CD1 in CD ROM drive. c) Use documented procedure to access system console using Serial Over Lan (SOL). 2.) Use documented procedure for your blade center/blade to select desired boot source. 3.) Boot selected installation media, follow installation procedure documented in Linux Distribution. If a vnc viewer is available, consider enabling vnc installation by adding vnc to boot: argument list. i.e. boot: linux vnc. This option will provide a GUI installation interface superior to the text only interface available via SOL and will also allow custom partition configuration using disk druid which is not avialable when the installation is performed in non-GUI mode. 4.) Continue the installation procedure up to Disk Partition Dialog. At this point, you will need to know what kernel device name i.e. /dev/sd{xx} corresponds to the installation target device. If a warning dialog box appears, advising the partition table on device sd{xx} is unreadable, you must select yes if you want to use this drive as the installation target. Use caution here to avoid overwriting data disks. NOTE: On JS21, the internal disks are SCSI devices and will be assigned kernel device names /dev/sda for first disk and /dev/sdb for second disk if present. Therefore, the first SAN disk may be /dev/sda, /dev/sdb or /dev/sdc, if there are none, one, or two internal disks installed, respectively. 5.) Select 'Autopartition'. Select one of three choices for how partitions should be treated. From the list of available drives, use space bar in text mode or mouse click in GUI mode to deselect all disks except a single disk for the installation target disk. Note: in GUI mode, the disk size and model information will be displayed, in text mode only the size information will be displayed. Use the information available to select the desired disk for installation. Select 'OK' or 'Next' to continue. Confirm you selection, if correct, select 'Yes' to continue. 6.) Review the suggested partitioning. If acceptable, Select 'OK' or 'Next' to continue. If not correct, select 'Back' as needed to make corrections. Confirm parititioning scheme, if correct, select 'Yes' to continue. 7.) When finished with the Disk Parititioning step, follow prompts to complete the the installation. 8.) At completion of installation, select 'Reboot' to boot the new installation. ________________________________________ 3.4 SLES9 for PPC Installation for JS21 _________________________________________ 1.) Prerequisites: a) Preconfigure SAN to insure that installation LUN will be accesible by Emulex HBA - Record IEEE address information for each from labels on Emulex HBA prior to HBA installation - WWPN for port [n] will be 0x1000{port[n]_ieee_address} - WWNN for port [n] will be 0x2000{port[n]_ieee_address} - Configure switch zoning such that each HBA host port is in same zone as desired storage target - Configure storage target such that target installation LUN is acessible by HBA host port b) If installing from CD Media, use documented procedure for your blade center to assign CD media to blade containg Emulex HBA. Install SLES CD1 in CD ROM drive. c) Use documented procedure to access system console using Serial Over Lan (SOL). 2.) Use documented procedure for your blade center/blade to select desired boot source. 3.) Boot selected installation media, follow installation procedure documented in Linux Distribution. If vnc viewer is available, consider enabling vnc installation by adding vnc=1 to boot: arguments. i.e. boot: install vnc=1. This option will provide a GUI installation interface superior to the text only interface available via SOL. 4.) Continue the installation procedure up to Installation Settings Dialog. At this point, you will need to know what kernel device name i.e. /dev/sdxx corresponds to the installation target device. If unsure, at next step select "Create custom partition setup" to have YaST display a list of discovered devices. 5.) Select 'Change', select Partitioning. Review the suggested partitioning. If acceptable Select 'Next' to continue. If unsure, or to verify the proposed target device, select "Create custom partition setup", select 'Next'. A list of available disks will be displayed. 6.) Select the kernel device name for the desired installation disk, Select 'Next'. NOTE: On JS21, the internal disks are SCSI devices and will be assigned kernel device names /dev/sda for first disk and /dev/sdb for second disk if present. Therefore, the first SAN disk may be /dev/sda, /dev/sdb or /dev/sdc, if there are none, one, or two internal disks installed, respectively. From the Preparing Hard Disk -- Step 2 dialog, confirm that the selected disk is of the size and type of the installation target, if so select 'Use entire hard disk' for default partitioning, the select 'Next' to continue. 7.) When finished with the Disk Parititioning step, follow prompts to complete the file copy phase of installation. Upon completion of the file copy phase, the system will reboot by default to the installed SAN disk to complete the system configuration phase of the installation. 8.) Once system reboots, complete the rest of the installation. _______________________________ _______________________________ 4.0 Configuration Information _______________________________ Information for configuration of the Emulex 4Gb Expansion Cards can be found in the Manual for the version of Emulex device driver installed on your system. Need website URL here???? 5.0 Unattended Mode _____________________ This package does not support unattended mode. ________________________________________ 6.0 WEB Sites and Support Phone Number ________________________________________ IBM Support Web Site: http://www.ibm.com/pc/support IBM Marketing Netfinity Web Site: http://www.pc.ibm.com/netfinity If you have any questions about this update, or problems applying the update go to the following Help Center World Telephone Numbers URL: 1-800-772-2227 http://www.pc.ibm.com/qtechinfo/YAST-3P2QYL.html. ____________________________ 7.0 Trademarks and Notices ____________________________ The following terms are trademarks of the IBM Corporation in the United States or other countries or both: IBM BladeCenter eServer Microsoft, Windows, and Windows NT are trademarks of Microsoft Corporation in the United States, other countries, or both. Linux is a registered trademark of Linus Torvalds. Intel trademarks or registered trademarks are trademarks of Intel Corporation. Other company, product, and service names may be trademarks or service marks of others. ________________ 8.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. Note to Government Users Note to U.S. Government Users -- Documentation related to restricted rights -- Use, duplication or disclosure is subject to restrictions set forth in GSA ADP Schedule Contract with IBM Corporation. O ANY PATENTS OR COPYRIGHTS. Note to Government Users Note to U.S. Government Users -- Documentation related to restricted rights -- Use, duplication or disclosure is subject to restrictions set forth in GSA ADP Schedule Contract with IBM Corporation.