TITLE: HP NC-Series open-iscsi Boot Package for Linux VERSION: 1.0.0 LANGUAGE: English CATEGORY: Drivers DIVISIONS: Comm-Network PRODUCTS AFFECTED: HP NC370x Gigabit server adapter (All models) HP NC371x Gigabit server adapter (All models) HP NC373x Gigabit server adapter (All models) HP NC374x Gigabit server adapter (All models) HP NC380x Gigabit server adapter (All models) OPERATING SYSTEM: SLES 10 for x86 SLES 10 for x86_64 PREREQUISITES: Any ProLiant server that includes an iLO (integrated Lights Out) management device and supports one of the above operating systems 256MB RAM minimum Latest HP System ROM NOTE: Visit the following URL to upgrade the ROM http://h18000.www1.hp.com/support/files (Select ProLiant from the server column) EFFECTIVE DATE: 04/12/2007 SUPERSEDES: None (Initial version) DESCRIPTION: SLES10 iSCSI boot is supported by a single RPM. The hp-iscsi-boot RPM contains the files necessary to install SLES10 directly onto an iSCSI target and prepare the disk for iSCSI boot. These files consist of scripts and utilities that run during installation and during post-install. ENHANCEMENTS/FIXES: None. (Initial release) Table of Contents ================= Introduction iSCSI boot Overview Packaging iSCSI Direct Install Upgrading bnx2 After Installation Module Parameters Limitations Uninstalling the RPM Package Documentation Introduction ============ This release contains a single RPM used during SLES10 installation to install the OS directly on an iSCSI target and create a ramdisk to be used during boot that brings up the iSCSI initiator and connects to the target to locate the root file system. This release does not contain an iSCSI initiator. The standard iSCSI initiator that ships with the SLES10 OS is being used for iSCSI boot. iSCSI boot Overview ==================== This iSCSI boot implementation allows you to boot a server from an iSCSI target without the need for a local disk in the server. Unlike other implementations, it does not require a separate DHCP server or a PXE server to support iSCSI boot. The NC37xx family of Multifunction Gigabit Ethernet Adapters are used to provide iSCSI boot functionality. The Ethernet Adapter must be updated with a special iSCSI boot option ROM prior to installing this RPM on the server to support iSCSI boot. The method of installing this option ROM is not discussed in this document. Please refer to iSCSI boot User Guide for instructions. The iSCSI boot User Guide is in the /docs directory. Within this document, the term iSCSI Target Disks refers to the disk drives composing the iSCSI target array that will be used by the servers to perform an iSCSI boot. These iSCSI target disks should be installed with one of the supported OS mentioned in Supported OS section. These disks can be installed directly using CDs or PXE. We provide an RPM that contains all the files you will need for directly installing an OS on the iSCSI target disks using any of these 3 methods. Please refer to the "iSCSI Direct Install" section below for more information on installing directly to iSCSI targets. Packaging ========= HP provides the `hp-iscsi-boot' binary RPM. This rpm contains scripts, utilities, and configuration files that are necessary for direct installation on iSCSI targets. Binary RPM - hp-iscsi-boot-.i386.rpm iSCSI Direct Install ==================== iSCSI Direct install is a method of installing the OS on the remote iSCSI target disk through a server which may be diskless. Prior to installing the OS on your iSCSI target, you must install the provided binary RPM(hp-iscsi-iboot-.i386.rpm on a Linux system (This can be any Linux system). These release notes refer to this sytem as the Install Server. Install the binary RPM hp-iscsi-iboot on the Install Server - # rpm -ihv /hp-iscsi-boot-.i386.rpm If you have the HP rpm linux-iscsi-install (the iSCSI boot soution for RH3, RH4, and SLES9) installed on your system, you will need to use the --force option to the rpm command. # rpm --force -ihv /hp-iscsi-boot-.i386.rpm This binary rpm will install iSCSI boot/configuration related code and utilities in /opt/hp/hp-iscsi-boot/scripts/configure /opt/hp/hp-iscsi-boot/scripts/install_bnx2 /opt/hp/hp-iscsi-boot/scripts/connect_iscsi_target /opt/hp/hp-iscsi-boot/scripts/prep_iscsi_boot /opt/hp/hp-iscsi-boot/scripts/get_interface /opt/hp/hp-iscsi-boot/scripts/get_iscsi_conf /opt/hp/hp-iscsi-boot/scripts/autoinst.xml /opt/hp/hp-iscsi-boot/utils/optrom/ibootcfg /opt/hp/hp-iscsi-boot/utils/bin/rebuild_initrd The ibootcfg utility can be used to update option ROM configuration information for the iSCSI target and initiator for the server that is being installed. Please refer to the man page for ibootcfg(1) for proper usage of this command. Customizing the Autoyast control file ===================================== To complete the setup of a disk for iSCSI boot, special scripts and utilities must be installed during post-install of the Operating System. In order to accomplish this, the Autoyast control file is used during OS installation to customize the post install of the iSCSI target. A sample control file (autoinst.xml) is supplied with the hp-iscsi-boot binary RPM. This file must be modified by the user and placed on the NFS share or the diskette image being used during the install. On the Install Server, execute the following: # vi /opt/hp/hp-iscsi-boot/scripts/autoinst.xml By default the boot loader is set to 'grub'. The boot loader 'lilo' is not supported in this release. You may use the default one provided if you are using grub as the boot loader. If you are using NFS to install, you need to modify the following variables in autoinst.xml script with the NFS server IP and the share point: COPYMETHOD=nfs NFSSERVER= NFSSHARE= The Autoyast Control file contains the steps to be executed during pre-install and post-install stages. During pre-install, it brings up the network interface connected to the iSCSI target. It also loads and starts the iSCSI initiator and connects to the target. During post-install, it copies the required scripts to the target disk and prepares the disk for iscsi boot. These files can be provided through floppy OR NFS share. The copymethod can be specified through the Autoyast control file. By default the COPYMETHOD is set to floppy. The root password is set to "root123" in autoinst.xml file. You may modify autoinst.xml file to change the root password. To modify the root password, search for the following line in the autoinst.xml file and modify it accordingly: root123 Creating an Installation floppy ================================= Skip this section if you are doing any type of Network installation - (e.g PXE/NFS). Prior to beginning the install of the OS, copy the iSCSI boot configuration scripts to a floppy. This floppy will be inserted during the pre-install stage of the OS installation. Place an empty floppy in the floppy drive and perform the following steps: # umount /dev/fd0 (If the floppy is automatically mounted) # mkfs -t vfat /dev/fd0 # mount /dev/fd0 /mnt # cp -r /opt/hp/hp-iscsi-boot/scripts /mnt # sync # umount /mnt iLO Virtual Floppy Setup ======================== If you are using iLO virtual floppy then you need to convert the above floppy into a disk image. Creating a disk image from a floppy: - Insert the floppy created in the above section into the floppy drive and issue following command: # dd if=/dev/fd0 of=hp-iscsi-boot-disk.img Copy this disk image to the system where you are planning to use the iLO console. On the iLO Web page go to 'Virtual Devices->Virtual Media-> Virtual Media Applet'. In the 'Virtual Floppy/USb Key' box, select 'Local Image File' radio button. Click on 'Browse' button and select the disk image 'hp-iscsi-boot-disk.img'. Click on 'Connect' push button to activate Virtual floppy. Now you are ready to Start the installation. Direct Install on iSCSI target disk using CDs and floppies ========================================================== Skip this section if you are doing any type of Network installation (e.g PXE/NFS). This direct install method requires the floppy that should have been created on the Install Server as described in the previous sections. Pre-Installation Update the iSCSI boot Option ROM on the diskless server with target IP Address, target name etc. Please refer to the iSCSI boot User Guide for instructions. The iSCSI boot User Guide is located in the /docs directory. This information can be provided by using a DOS utility. In addition, the hp-iscsi-boot RPM contains a Linux executable utility that allows you to initialize the option ROM target information. This utility is called ibootcfg. For information on how to use this utility, please refer to the man page for ibootcfg(1) after installing the hp-iscsi-boot RPM. Installation (SLES10) CDs and floppies ========================================= a. Switch on the server with SLES10's first installation CD in the CD-ROM drive. b. Make sure that Option ROM initialized successfully and is able to login successfully onto the target disk. This can be confirmed by looking at the iSCSI option ROM messages during POST. c. If you are using local CDROM for install then select "Installation" at the first screen and pass the following boot Options: autoyast=floppy:///scripts/autoinst.xml Note: If you are using a USB OR virtual* floppy drive then pass the following boot Options: autoyast=device://sda/scripts/autoinst.xml d. Immediately insert the installation floppy while the system is booting from CD. e. On some servers, the installation will return the message "Error - no hard disks and no hard disk controllers were found for this installation. Check your hardware." Ignore this message and press "OK". f. The scripts from the installation floppy will be copied onto the root file system. The scripts will read the Option ROM data and connect to the target disk. g. Upon successful connection the target disk will be mounted as /dev/sda (OR /dev/sdb if you are using a USB OR virtual* floppy drive). i.e it will appear as if it is local disk. j. If installation is unable to find 'autoinst.xml' file then you will be prompted to provide the location of autoinst.xml file. Enter the correct location of autoinst.xml and press "OK". This may happen if the USB floppy is mounted on a device other than /dev/sda. You will not be prompted if the 'autoinst.xml' file is found at the location specified in Step (d). It is out of scope of this Manual to provide steps to determine the device on which the USB floppy is mounted. k. Follow the traditional installation procedure. (Refer to SLES10 installation). *iLO-2 (Integrated Lights-Out 2) Virtual Media allows you to use local image files from your client PC. A floppy that is connected through this mechanism is known as a Virtual Floppy drive. (Refer to iLO-2 documentation for steps to connect a floppy drive as a virtual media.) Post-Installation ================= a. The installation will automatically set up the disk for iSCSI boot during post installation. b. Once the disk is configured for iSCSI boot you will be taken back to the standard OS installation screen and the system will reboot. Direct Install on target iSCSI disk using NFS ============================================= Prior to beginning the NFS install, NFS server needs to be setup with iSCSI boot/Configuration related code and utilities. NFS install setup ================= Install the binary RPM hp-iscsi-boot on the NFS Server - # rpm -ihv //hp-iscsi-boot-.i386.rpm This binary rpm will install iSCSI boot/configuration related code and utilities in /opt/hp/hp-iscsi-boot/scripts/configure /opt/hp/hp-iscsi-boot/scripts/install_bnx2 /opt/hp/hp-iscsi-boot/scripts/connect_iscsi_target /opt/hp/hp-iscsi-boot/scripts/prep_iscsi_boot /opt/hp/hp-iscsi-boot/scripts/get_interface /opt/hp/hp-iscsi-boot/scripts/get_iscsi_conf /opt/hp/hp-iscsi-boot/scripts/autoinst.xml Export the folder /opt/hp/hp-iscsi-boot for NFS sharing (Refer to NFS documentation for nfs sharing on Linux). Note: You may copy the contents under /opt/hp/hp-iscsi-boot to some other folder and NFS share that folder. The directory structure under the NFS share folder must be same as that of the /opt/hp/hp-iscsi-boot directory. For SLES10 Modify the autoinst.xml file as described in "Customizing the Autoyast control file" section. Make sure to select nfs as COPYMETHOD and set NFSSHARE to "/opt/hp/hp-iscsi-boot" directory. Make sure that OS distribution files to be installed are present on the NFS server and exported via NFS. Please refer to SLES10 installation Manuals for setting up the NFS installation source. Installation (SLES10) using NFS ================================== a. Switch on the server with the first installation CD in the CD-ROM drive. if PXE, see the section "Installation using a PXE server". b. Make sure that Option ROM initialized successfully and is able to login successfully onto the target disk. This can be confirmed by looking at the iSCSI option ROM messages during POST. c. Select "Installation" at the first screen and pass the following boot Options: "autoyast=nfs://://opt/hp/hp-iscsi-boot/scripts /autoinst.xml install=nfs://://" d. On some servers, the installation will return the message "Error - no hard disks and no hard disk controllers were found for this installation. Check your hardware." Ignore this message and press "OK". e. The modules from the Install floppy image will be pulled through nfs and copied into the memory. The scripts will read the Option ROM data and connect to the target disk. f. Upon successful connection the target disk will be mounted as /dev/sda. i.e it will appear as if it is local disk. Note: If you have any SCSI local disk(s) attached then those will be listed first (as /dev/sda, /dev/sdb...) and the iSCSI target disk will be listed last - e.g /dev/sdc Make sure that you choose the iSCSI target disk (/dev/sdc) for partitioning and not the local disk. g. Once the modules are successfully loaded the installation will continue by pulling sources from NFS server. h. For customizing Autoyast installation refer to SuSE Manuals for Auto-Installation using AutoYast. Installation using a PXE server =============================== If the system to be installed contains a network adaptor card with Pre-Execution Environment (PXE) support then direct install over PXE is possible. PXE install Setup ================= The following steps must be performed to prepare for a PXE installation: 1. Configure the NFS server to export the installation source. 2. Configure the TFTP server necessary for PXE booting. 3. Start/enable the tftp service. 4. Configure the DHCP. Note: It is not in the scope of this document to explain the above steps in detail. Please refer to respective manuals for more information. Additionally, configure the NFS server to export the Install floppy iSCSI boot/Configuration related code and utilities. Refer to section "NFS install setup". On the PXE server execute the following: # vi /tftpboot/linux-install/pxelinux.cfg/default In this file add the following lines: For SLES10: label kernel /boot//loader/linux append initrd=/boot//loader/\ initrd load_ramdisk=1 autoyast=nfs::/opt/hp/\ hp-iscsi-boot/scripts/autoinst.xml devfs=nomount \ install=nfs:: Optionally, modify /tftpboot/linux-install/msgs/boot.msg to use custom boot messages. Performing Installation using PXE ================================= a. Switch on the server. b. Make sure that Option ROM initialized successfully and is able to login successfully onto the target disk. This can be confirmed by looking at the iSCSI option ROM messages during POST. c. Press for PXE installation when prompted. d. Enter the label number (specified in the above section) at the PXE boot prompt and hit . e. The installation will start pulling the installation sources from NFS server. f. On some servers, the installation will return the message "Error - no hard disks and no hard disk controllers were found for this installation. Check your hardware." Ignore this message and press "OK". Upgrading bnx2 After Installation ================================= You may wish to upgrade the bnx2 driver after installation. To do this, follow the steps outlined below. You can obtain the bnx2 source RPM from NCDEx.xx or the iSCSI boot softpaq. Prior to upgrading the bnx2 driver, you must install the hp-iscsi-boot rpm as outlined below. # rpm -ihv /hp-iscsi-boot-.i386.rpm # rpm -e bnx2- # rpm -ivh /bnx2-.src.rpm # rpmbuild -bb /usr/src/packages/SPECS/bnx2.spec # rpm -ivh --force /usr/src/packages/RPMS//bnx2-.rpm # cd /opt/hp/hp-iscsi-boot/utils/bin # ./rebuild_initrd # reboot Note: Please do not issue the command 'rmmod bnx2'. This command will result in system hang. The command "rebuild_initrd" does not take any argument. It updates the /boot/initrd- image with the currently installed version of the bnx2 driver. Please refer to the man page for rebuild_initrd(8) for more info. A system reboot must occur to get the changes affected. Module Parameters ================= none Limitations =========== Once the server is booted over iSCSI, bringing down the network interface that iSCSI is using will result in a system hang. If the system crashes, the diskdump utility that would normally take a system dump will not work on an iSCSI booted system. After booting a system over iSCSI, if the SmartStart Linux PSP is installed it changes the default boot kernel in the boot loader conf file - /boot/grub/menu.lst. The PSP default kernel does not support iSCSI boot. Please update the /boot/grub/grub.conf to make the default boot kernel point to entry 0. The current release does not support 'lilo' boot loader. iSCSI Boot is not supported on HP StorageWorks 1510i Modular Array. VLANs are not supported in this release. If PXE is being used to install the OS on a iSCSI device on a c-Class blade, disable the internal disk controller with RBSU (F9 during POST). After the install is complete, the internal controller can be reenabled. If the HP StorageWorks SB40c Storage Blade is being used with a c-Class blade, it must be removed prior to installing the OS. It may be placed back in the system after the install completes. If you attempt to boot from an iSCSI disk with no OS installed on it, the system may hang rather than report an error. Mutual CHAP is not supported in this release. On some blade systems, once the system is booted and the GUI is started, the system console on a KVM switch may report that it is in an unsupported mode. The iLO2 integrated remote console works fine. This is a problem with the SLES 10 installation procedure and not with the iSCSI boot installation procedure. If CHAP is used with SLES10 for the root disk, the same CHAP user name and password must be used for all additional data disks being connected to the system. This is a limitation on the SLES10 open-iscsi initiator. If the RBSU utility is used to reset system defaults, the iSCSI boot parameters will be lost. You will need to rerun the DOS EV utility or the Linux ibootcfg utility to reset the parameters. Many errors from the use of the ibootcfg utility are not reported correctly. As a precaution you should always use ibootcfg -P to verify the proper setting of the iSCSI boot parameters after using ibootcfg -i to set them. If the utility is not setting the iSCSI boot parameters, turn off power to the server and run the ibootcfg utility again. No problems have been seen when using ibootcfg to set parameters on a machine that is powered off. Troubleshooting =============== Problem: Installation fails to read the iSCSI install scripts from the iLO virtual floppy. Resolution: On the iLO Web page go to 'Virtual Devices->Virtual Media-> Virtual Media Applet'. In the 'Virtual Floppy/USb Key' box, disconnect and reconnect the Virtual floppy drive by clicking the 'disconnect' and then the 'connect' push buttons. Problem: After installation, the server will not boot linux. Resolution: Check the RBSU settings for the adaptor that is connected to the target. On some servers and with some versions of the BIOS, you may have to enable iSCSI boot or modify the boot controller order. Problem: On some BL685c servers with more than 4 Gb of memory, the system fails to finish the boot sequence after a SLES10 install. Resolution: Add the parameter "numa=off" to the list of parameters given for "Boot options:" or in the PXE configuration file, depending on the type of install. Uninstalling the RPM Packages ============================= On the Install server, run # rpm -e hp-iscsi-boot Documentation ============= Please look at /usr/share/doc/packages/open-iscsi/README for iSCSI initiator design and installation notes. (c) Copyright 2002, 2003-2007 Hewlett-Packard Development Company, L.P. Product names mentioned herein may be trademarks and/or registered trademarks of their respective companies