McDATA 8832 warranty Broadcom Advanced Control Suite installation, List of limitations

Page 41

IBM BladeCenter Deployment Guide

8.Type the location of the Ethernet device drivers that you extracted in step 6. Select OK.

9.When the message "System found a driver for device" is displayed, select Next to install the device driver.

10.When you are prompted to restart the blade server, select Yes if you do not have more device drivers to install, or select No if you have another device driver to install.

5.3 Broadcom Advanced Control Suite installation

Network interface card (NIC) teaming is one method for providing high availability and fault tolerance in IBM Eserver servers. In this example, we use Broadcom Advanced Server Program (BASP) to implement teaming functionality along with load balancing, fault tolerance, and VLAN tagging.

To enable NIC teaming, the Broadcom Advanced Control Suite application must be used on the HS20s. The program is included with the drivers, which you can download at: http://www.ibm.com/pc/support/site.wss/document.do?lndocid=MIGR-43815.

To install the suite, perform the following steps:

1.Navigate to the location where the Broadcom Advanced Control Suite application files were extracted (default C:\Drivers\BcomXXX, where XXX is the code level). Execute Launch.exe.

2.Click MANAGEMENT PROGRAMS, and a window similar to the one in Figure 45 opens.

Figure 38 Broadcom Setup

3. Select Control Suite and BASP. Click Next to continue and click then Finish.

5.4 List of limitations

1.If there is a path failure and the host is generating I/O, the boot drive will move to the other path. However, while this transition is occurring, the system will appear to freeze for up to 30 seconds.

2.You cannot enable the BIOS for both adapters at the same time. If you do and there is a path failure on the primary adapter (and the adapter is still active), the system will trap with an INACCESSIBLE_BOOT_DEVICE error on reboot.

3.If the boot device, (LUN 0), is not on the same path as the bootable HBA port, you will receive an INACCESSIBLE_BOOT_DEVICE error message.

4.If you suffer major path problems (LIPs) or controller panics, it can hang the server indefinitely as RDAC tries to find a stable path.

5.The IDE disk devices should not be re-enabled.

Version 3.0, 3/10/2006

http://w3-03.ibm.com/support/techdocs/atsmastr.nsf/WebIndex/WP100564

41

The BladeCenter Deployment Guide is intended as a personal productivity tool. It is not intended to be comprehensive and is provided for

guidance only, on an 'as is basis' without warranty of any kind. Please be aware that its contents have not been certified by IBM.

Image 41
Contents IBM BladeCenter Deployment Guide Part 3 Blades IBM Version 3.0, 3/10/2006 Table of Contents Table of Figures Table of TablesLinux nofb BladeCenter Subsystems Introduction OverviewBladeCenter Chassis Rear View ContributorsPreparatory Steps Network ConfigurationBladeCenter Management Module Remote Control Hints and TipsDisable key repeats Remote Control Window SAN Configuration Embedded Fibre Channel SwitchesStorage Connection Diagram Disabling ports on the QLogic switchUsing SANSurfer GUI Port Properties Check the Boot Order Configuring the Blades for Remote BootDisabling IDE devices Device Startup OrderHS20 Boot Sequence Acquiring HBA WWPNs World Wide Port Names Configuring the Qlogic HBAConfiguring the QLogic HBA Configuring the path to the boot LUNEnable Selectable Boot Illustration Save your changes Testing the path to the boot LUNVerify Disk Media Ethernet Port NumberingBrowse MAC Address Table Bottom Switch Learned Browse MAC Address Table Top SwitchMAC Address Port Learned MAC Address PortChange Media Tray Owner Loading the Remote Diskette Linux nofb Kickstart Information Multipath Red Hat InstallationBoot Failure for RH Fdisk Output Red Hat Linux AS Broadcom driver installationRPM Install of Broadcom Device Drivers Issues related to Red Hat AS 2.1/3.0 and bladesRev IBM Version 3.0, 3/10/2006 IBM BladeCenter Deployment Guide Other Linux Distributions and Blades Changing the Boot Loader ConfigurationOverview Rdac Installation and ConfigurationSerial Over LAN SOL for Blades 72345respawn/sbin/agetty -h ttyS1 19200 vt102 Summary of Linux changes for SOLAlt-sysrq from Linux client Alt-sysrqAlt-sysrq from PuTTY NetdumpIBM BladeCenter Deployment Guide IBM Version 3.0, 3/10/2006 List of limitations Broadcom Advanced Control Suite installationBMC Update for the HS20 8843 and LS20 Remote Update of the Firmware on an HS20 or HS40Bios and Ismp IBM BladeCenter Deployment Guide QLogic HBA Flash Flash the QLogic HBA Bios# mount -o loop drvnet.img mnt/drv Red Hat Boot Diskette Modification ProcessIBM Version 3.0, 3/10/2006 # cd # umount mnt/initrd Driverdisk --source=nfshost/path/to/26k4970.img Modify or Create the Post-install Driver Diskette ImageIBM BladeCenter Deployment Guide HS20 Model 8832 Firmware Information Management Module Bios InformationAppendix A. Firmware Versions HS40 Bios and Ismp Information HS40 BiosQLogic Firmware Information LS20 Bios and BMC InformationBladeCenter Components BladeCenter InformationIndex