TITLE: HP NC-Series iSCSI Boot Driver for Linux VERSION: 4.1.18 LANGUAGE: English CATEGORY: Drivers DIVISIONS: Comm-Network PRODUCTS AFFECTED: HP NC370x Gigabit server adpater (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: Red Hat Enterprise Linux 3 ES/AS for x86_64 (Update 5 and later) Red Hat Enterprise Linux 3 ES/AS for x86 (Update 5 and later) Red Hat Enterprise Linux 4 ES/AS for x86_64 (Update 2 and later) Red Hat Enterprise Linux 4 ES/AS for x86 (Update 2 and later) SLES 9 SP3 for x86 SLES 9 SP3 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: 08/17/2006 SUPERSEDES: None (Initial release) DESCRIPTION: Full iSCSI boot is supported by 2 RPMs. The linux-iscsi-boot RPM contains the Sources for iSCSI driver (with iSCSI boot support) for HP's ProLiant NC37xx and NC38xx class of Gigabit Ethernet NICs running under Linux. The linux-iscsi-install binary RPM contains driver diskette images for direct installation of the operating system to an iSCSI target, as well as other scripts necessary for setting up the target for iSCSI boot during post install of the OS. If you are using another method of installing a base OS on iSCSI targets and do not intend to use HPs direct install methods that are described in this document, please refer to the file Release.notes.noinstall for instructions on configuring already installed iSCSI targets for iSCSI boot. ENHANCEMENTS/FIXES: Initial release Table of Contents ================= Introduction iSCSI boot Overview Packaging iSCSI Direct Install Module Parameters Limitations Uninstalling the RPM Package Upgrading the bnx2 driver Documentation Introduction ============ This file describes the iSCSI initiator driver on Linux for the HP Gigabit Server Adapters mentioned in the PRODUCTS AFFECTED section of this document. This modified iSCSI initiator driver is based on the iscsi initiator driver released with whichever version of the OS you are using, namely either RH4, RH3, or SLES9. iSCSI boot support has been added to the driver. Using this driver with the NC37xx NIC (with iSCSI boot Option ROM support) will allow booting a server over iSCSI. User guides and additional HP Network Adapter information can be found at: http://h18000.www1.hp.com/support/networking/nics/index.html 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 on the NCDEx.xx CD. 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. Plese refer to the "iSCSI Direct Install" section below for more information on installing directly to iSCSI targets. Packaging ========= HP provides the `linux-iscsi-boot' source RPM. This rpm contains source for iSCSI boot related utilities/modules/documentation. Source RPM - linux-iscsi-boot--src.rpm The source RPM requires that the kernel source code be installed during the installation of the OS distribution. If you have not installed the kernel source code you must do so prior to installing the source RPM. This rpm is generally installed automatically during post-install of the operating system on the iSCSI target if the direct install method HP provides is used to install the target. HP provides the `linux-iscsi-install' binary RPM. This rpm contains driver diskette images, scripts, and configuration files that are necessary for direct installation on iSCSI targets. Binary RPM - linux-iscsi-install-.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. This method requires a special iSCSI driver to be used at install time. Prior to installing the OS on your iSCSI target, you must install the provided binary RPM(linux-iscsi-install-.i386.rpm on a Linux system (This can be any Linux system). This document will refer to this sytem as the Install Server. This binary RPM contains the driver diskette images you will need for installing the iSCSI targets, as well as copies of the scripts needed to install the linux-iscsi-boot rpm on the target during post install and complete the system setup for iSCSI boot. Install the binary RPM linux-iscsi-install on the Install Server - # rpm -ihv /linux-iscsi-install-.i386.rpm This binary rpm will install iSCSI boot/configuration related code and utilities in /opt/hp/iboot_install/scripts/configure.sh /opt/hp/iboot_install/scripts/install_bnx2.sh /opt/hp/iboot_install/scripts/install_iscsi.sh /opt/hp/iboot_install/scripts/prep_iscsi_boot.sh /opt/hp/iboot_install/scripts/setup_kernel_tree.sh /opt/hp/iboot_install/scripts/ks.cfg /opt/hp/iboot_install/scripts/autoinst.xml /opt/hp/iboot_install/utils/optrom/ibootcfg Additionally, the binary rpm will install driver diskette images for all supported releases in the /opt/hp/iboot_install/ddimages directory. 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 Kickstart file (For RedHat install) =================================================== To complete the setup of a disk for iSCSI boot, the linux-iscsi-boot and the bnx2 source rpm must be installed during post-install of the Operating System. Also, there are standard scripts that must be modified to support iSCSI boot from the target disk. In order to accomplish this, the Kickstart file is used during OS installation to customize the post install of the iSCSI target. A sample kickstart file (ks.cfg) is supplied with the linux-iscsi-install binary RPM. This file must be modified by the user and placed on the driver diskette image that is also supplied with the binary RPM. On the Install Server, execute the following: # vi /opt/hp/iboot_install/scripts/ks.cfg In this file, you need to modify the following variable to specify hostname: SYSNAME= Note: 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 do not wish to set the hostname and you are using grub as the boot loader. If you are using NFS to install, you need to modify the following variables in ks.cfg script with the NFS server IP and the share point: COPYMETHOD=nfs NFSSERVER= NFSSHARE= The kickstart file contains the steps to executed during post-install stage. During post-install it copies the required scripts and RPMS to the target disk and prepares the disk for iscsi boot. These files can be provided through a floppy OR NFS share. The copy method can be specified through the kickstart file. By default the COPYMETHOD is set to floppy. Customizing the Autoyast control file (For SLELS9 install) ========================================================== To complete the setup of a disk for iSCSI boot, the linux-iscsi-boot and the bnx2 source rpm must be installed during post-install of the Operating System. Also, there are standard scripts that must be modified to support iSCSI boot from the target disk. 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 linux-iscsi-install binary RPM. This file must be modified by the user and placed on the driver diskette image that is also supplied with the binary RPM. On the Install Server, execute the following: # vi /opt/hp/iboot_install/scripts/autoinst.xml In this file, you need to modify the following variable to specify hostname: SYSNAME= Note: 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 do not wish to set the hostname and 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 post-install stage. During post-install, it copies the required scripts and RPMS 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 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 in the autoinst.xml file and modify it accordingly: root123 Creating a Driver Diskette floppy ================================= Skip this section if you are doing any type of Network installation - (e.g PXE/NFS). After the binary RPM linux-iscsi-install has been installed on the Install server, the directory /opt/hp/iboot/iboot_install/ddimages will contain driver diskette images for all RH3, RH4, and SLES9 SP3 releases, both 32 and 64 bit. After placing the ks file (RedHat) or the autoinst.xml file (SLES9) on the diskette image, copy the image to a floppy for use during installation. RedHat: Copy the kickstart file onto the proper driver diskette for your OS and configuration (32 or 64bit, RH4, RH3). # cd /opt/hp/iboot_install/ddimages # mount -o loop iboot_install__driver.dd /mnt # cp /opt/hp/iboot_install/scripts/ks.cfg /mnt/ks.cfg # umount /mnt SLES9: Copy the Autoyast control file onto the proper driver diskette for your OS and configuration (32 or 64bit, SLES9). # cd /opt/hp/iboot_install/ddimages # mount -o loop iboot_install__driver.dd /mnt # cp /opt/hp/iboot_install/scripts/autoinst.xml /mnt/autoinst.xml # umount /mnt Place the floppy disk that will contain the dd image into the floppy drive. # umount /dev/fd0 (If the floppy is automatically mounted) # dd if=iboot_install__driver.dd of=/dev/fd0 Remove the floppy from the drive. Creating the linux-iscsi-boot rpm floppy (2nd floppy - for post-install) ======================================================================= 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, the bnx2 SRC RPM, and the linux-iscsi-boot SRC RPM to a floppy. This floppy will be inserted during the post-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 ext2 /dev/fd0 # mount /dev/fd0 /mnt # cp -r /opt/hp/iboot_install/scripts /mnt # mkdir /mnt/SRPMS # cp /linux-iscsi-boot.src.rpm /mnt/SRPMS # cp /bnx2-.src.rpm /mnt/SRPMS # sync # umount /mnt Note: Obtain the bnx2 driver (version >= 1.4.43c) source RPM from NCDEx.xx CD. 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 driver diskette and the linux-iscsi-boot rpm 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 on the NCDEx.xx CD. This information can be provided by using a DOS utility. In addition, the linux-iscsi-install 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 linux-iscsi-install RPM. Installation (RHEL3 & RHEL4) (CDs and floppies) =============================================== a. Switch on the server with the 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 type "linux dd noprobe ks=floppy" at "boot:" prompt. Note: If you are using a usb floppy drive then type "linux dd ks=hd:sda:/ks.cfg" at "boot:" prompt. For RHEL4 32-bit type: "linux dd ks=hd:sda:/ks.cfg noirqdebug" d. Insert the Driver Diskette (created in the above section) when prompted and press "OK". Note: If you are using a usb floppy drive then insert the Driver Diskette into usb floppy drive. Select "sda" from the list of devices and press "OK". e. When prompted, select "manually choose" f. Select the iBOOT install driver - "iboot_install" from the list and press "OK". It will be near the end of the listed drivers. The iboot_install driver 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 using usb floppy drive). i.e it will appear as if it is a local disk. h. A dialog box will appear asking "Do you want to load another driver?" Click "No". i. If there are no hard drives on your server, the message "No hard drives have been found" is displayed along with the question "Would you like to select drivers now?". Respond with the No button, which is not the default. If you have a hard disk on the system, this message will not be displayed. j. Follow the traditional installation procedure. Create partitions on /dev/sda (OR /dev/sdb if using usb floppy drive) and proceed with the installation. Installation (SLES9 SP3) CDs and floppies ========================================= a. Switch on the server with the Service Pack'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. Insert the Driver Diskette floppy when the first installation boot screen comes up. d. If you are using local CDROM for install then select "Manual installation" at the first screen and pass the following boot Options: autoyast=floppy:///autoinst.xml Note: If you are using a usb floppy drive then pass the following boot Options: autoyast=device://sdb/autoinst.xml e. The modules from the Driver Diskette will be copied into the memory. The iboot install driver 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. g. The installation will throw the following warning message - "Could not find SuSE Linux Enterprise Server 9 Installation Source". Press "OK" and continue. h. The installation will prompt you to select your language and keyboard layout. Select your installation language (such as 'English') and confirm by pressing . Next select the layout of your keyboard (for example, 'English (US)'). i. After selecting the language and keyboard, continue with Main menu. j. Select "Start Installation or System" from the Main Menu and press "OK". k. Select "Start Installation or Update" from the submenu and press "OK". l. You will be prompted for the installation source. Select the appropriate method and proceed with SLES9 installation. m. Insert "SLES9 Initial Release CD 1" in CD drive when installation prompts "Make sure that CD number 1 is in your drive". n. During Installation Settings choose "/dev/sda" for partitioning. (Refer to SLES9 installation). Post-Installation ================= a. During post-installation the user will be prompted to insert the linux-iscsi-boot floppy unless the user has modfied the autoinst.xml file to use NFS share. b. Insert the linux-iscsi-boot rpm floppy and press . c. Once the disk is configured for iSCSI boot you will be taken back to the standard OS installation screen to continue. Direct Install on target iSCSI disk using NFS ============================================= Prior to begining the NFS install, NFS server needs to be setup with Driver Diskette images and iSCSI boot/Configuration related code and utilities. NFS install setup ================= Install the binary RPM linux-iscsi-install on the NFS Server - # rpm -ihv //linux-iscsi-install-.i386.rpm This binary rpm will install iSCSI boot/configuration related code and utilities in /opt/hp/iboot_install/scripts/configure.sh /opt/hp/iboot_install/scripts/install_bnx2.sh /opt/hp/iboot_install/scripts/install_iscsi.sh /opt/hp/iboot_install/scripts/prep_iscsi_boot.sh /opt/hp/iboot_install/scripts/setup_kernel_tree.sh /opt/hp/iboot_install/scripts/ks.cfg /opt/hp/iboot_install/scripts/autoinst.xml Additionally, the binary rpm will install driver diskette images for all supported releases in the /opt/hp/iboot_install/ddimages directory. You must also place the linux-iscsi-boot source RPM and bnx2 driver source RPM in /opt/hp/iboot_install/SRPMS directory. Obtain the bnx2 driver (version >= 1.4.43c) source RPM from NCDEx.xx CD. # mkdir /opt/hp/iboot_install/SRPMS # cp /linux-iscsi-boot.src.rpm /opt/hp/iboot_install/SRPMS # cp /bnx2-.src.rpm /opt/hp/iboot_install/SRPMS Export the folder /opt/hp/iboot_install for NFS sharing (Refer to NFS documentation for nfs sharing on Linux). Note: You may copy the contents under /opt/hp/iboot_install 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/iboot_install directory. For RedHat Modify the ks.cfg file as described in the section "Customizing the Kickstart file". Make sure to select nfs as COPYMETHOD and set NFSSHARE to "/opt/hp/iboot_install" directory. Add the following lines before "%post" section in ks.cfg file: install nfs --server= --dir= For SLES9 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/iboot_install" directory. Create the Driver Diskette layout in the root directory of the OS installation source: # cd /opt/hp/iboot_install/ddimages # mount -o loop iboot_install__driver.dd /mnt # cp -r /mnt/01 / # find 01 -name "bnx2.*o" -exec rm {} \; # umount /mnt Make sure that OS distribution files to be installed are present on the NFS server and exported via NFS. Please refer to RedHat and SLES9 installation Manuals for setting up the NFS installation source. Installation (RHEL3 & RHEL4) 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. At the boot prompt type "linux dd=nfs::/opt/hp/iboot_install/ddimages/ ks=nfs::/opt/hp/iboot_install/scripts/ks.cfg" For RHEL4 32-bit type: "linux dd=nfs::/opt/hp/iboot_install/ddimages/ ks=nfs::/opt/hp/iboot_install/scripts/ks.cfg noirqdebug" d. The driver diskette will be pulled from nfs and the iboot_install module will be inserted automatically. The iboot_install driver will read the Option ROM data and connect to the target disk. e. Upon successful connection the target disk will be mounted as /dev/sda. i.e it will appear as if it is a local disk. f. Follow the traditional installation procedure. Create partitions on /dev/sda and proceed with the installation. 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. The installation will copy the packages to be installed from the NFS server and will not prompt for any CDs. For fully automating the install refer to RedHat Manuals for Kickstart installation details. Installation (SLES9 SP3) using NFS ================================== a. Switch on the server with the Service Pack's 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/iboot_install/scripts /autoinst.xml install=nfs://:// noirqdebug" d. The modules from the Driver Diskette image will be pulled through nfs and copied into the memory. The iboot_install driver will read the Option ROM data and connect to the target disk. e. 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. f. Once the modules are successfully loaded the installation will continue by pulling sources from NFS server. g. 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 interface card (NIC) 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 Driver Diskette images and the 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 Redhat: label kernel /images/pxeboot/vmlinuz append initrd=/images/pxeboot/\ initrd.img ramdisk_size=10000 dd=nfs::/opt/hp/\ iboot_install/ddimages/iboot_install_.dd \ ks=nfs::/opt/hp/iboot_install/scripts/ks.cfg For SLES9: label kernel /boot/loader/linux append initrd=/boot/loader/\ initrd.img load_ramdisk=1 autoyast=nfs::/opt/hp/\ iboot_install/scripts/autoinst.xml \ install=nfs:: noirqdebug 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. 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/grub.conf. The PSP default kernel does not support iSCSI boot. Please update the /boot/grub/grub.conf to make the default boot kernel point to the entry that says iSCSI in the title - E.g title iSCSI Red Hat Enterprise Linux AS (2.4.21-27.ELsmp) On some servers, RH3 32-bit and SLES 9 32-bit Direct Install will hang while loading the USB driver. The workaround for this is to disable USB in the BIOS before doing the install. The USB can be re-enabled after the iSCSI Direct install is done. The USB devices will then operate normally. On some servers, RH4 32-bit Direct Install using NFS/PXE fails because of Disabling IRQ issue. The IRQ assigned to NC37xx NIC (with iSCSI boot Option ROM support) gets disabled during direct install phase. The following error message gets displayed on the console: Disabling IRQ 5 This only occurs if "noprobe" option is not used. The workaround for this is to use 'noirqdebug' boot option. In RH4 only, the released iSCSI initiator driver no longer supports limiting the LUNs associated with a target that are available to the initiator (e.g if you specify LUN= in /etc/iscsi.conf on RH4, it is ignored). This means that all LUNs configured for a target name will be visible to the initiator when it connects to the target. This causes problems for iSCSI boot and Direct Install, since the drive /dev/sda is always used as the boot device. If multiple LUNs are visible to the initiator, they will be enumerated as /dev/sda, /dev/sdb etc. and the boot device will be unknown. Therefore, the iSCSI target configuration has limits on the way it can be configured. Some iSCSI targets support limiting the LUNs that are visible to the target. In that case, you must configure the target such that only the LUN for the boot disk is visible to the initiator. If the iSCSI target does not support that option, you must configure your target with only 1 LUN per target name. This is only applicable to RH4. The current release does not support 'lilo' boot loader. For SLES9 SP3, the disk device used to install is hard-coded to the pathname /dev/sda in the autoyinst.xml file. If you have any internal drives that are named /dev/sd{a-z}, you must physically remove them from the system prior to beginning the installation. Alternatively, you could disable the disk controllers through the BIOS prior to beginning the installation. A third option is to modify the autoinst.xml file with the correct device name of the iSCSI target. One example of a disk controller using the names /dev/sd{a-z} is the Ultra320 SCSI which is an embedded controller on some systems. If a drive other than the iSCSI target comes up as /dev/sda, the drive will be overwritten during install, destroying all data. Upgrading the bnx2 Driver ========================= Follow the steps below to upgrade bnx2 driver on an iSCSI booted server: RedHat: # rpm -e bnx2- # rpm -ivh bnx2-.src.rpm # rpmbuild -bb /usr/src/redhat/SPECS/bnx2.spec # rpm -ivh --force /usr/src/redhat/RPMS//bnx2-.rpm # cd /opt/hp/iboot/bin # ./iboot_config --config /opt/hp/iboot/etc/iboot.conf -r # reboot SLES9: # rpm -e bnx2- # rpm -ivh bnx2-.src.rpm # rpmbuild -bb /usr/src/package/SPECS/bnx2.spec # rpm -ivh --force /usr/src/package/RPMS//bnx2-.rpm # cd /opt/hp/iboot/bin # ./iboot_config --config /opt/hp/iboot/etc/iboot.conf -r # reboot Note: Please do not issue the command 'rmmod bnx2'. This command will result in system hang. A system reboot must occur to get the changes affected. Uninstalling the RPM Packages ============================= Uninstalling the linux-iscsi-boot package on an iSCSI booted server is not supported. On non-iscsi booted servers, run # rpm -e linux-iscsi-boot # rpm -e linux-iscsi-install Prior to removing the linux-iscsi-boot RPM, stop all the iSCSI sessions, stop the iscsid daemon and unload the iscsi module(s) ( iscsi_sfnet, scsi_transport_iscsi, iscsi). Documentation ============= Please look at /usr/share/doc/linux-iscsi*/README for iSCSI initiator design and installation notes. Copyright 2002, 2006 Hewlett-Packard Development Company, L.P. Product names mentioned herein may be trademarks and/or registered trademarks of their respective companies