Instruction/ maintenance manual of the product 8832 McDATA
Go to page of 54
IBM BladeCenter Deployment Guide IBM ® BladeCenter ™ Deployment Guide Part 3 - Blades Chris Gillen, IBM Sam Litenatsky, IBM Kevin Conover, IBM Version 3.0, 3/10/2006 http://w3-03.ibm.c om/support/techd ocs/atsmastr.ns f/WebIndex/WP100 564 The BladeCenter Deployment Guide is intended as a personal pro ductivity tool.
IBM BladeCenter Deployment Guide 2 http://w3-03.ibm.c om/support/techdo cs/atsmastr.nsf/WebIndex/WP100564 The BladeCenter Deployment Guide is intended as a personal pro ductivity tool. It is not inte nded to be compr ehensive and is pr o vided for guidance only , on an 'as is b asis' without warran ty of any kind.
IBM BladeCenter Deployment Guide Table of Contents 1 Introduct ion................................................................................................................... ..................... 6 1.1 Overview ................................
IBM BladeCenter Deployment Guide 7 Flash the QLogi c HBA BIOS ...................................................................................................... ..... 44 8 Red Hat Boot Diskette Modification Process ................................
IBM BladeCenter Deployment Guide Figure 30 linux nofb................................................................................................................. .................... 26 Figure 31 Unmount the Diskette Image .......................
IBM BladeCenter Deployment Guide 1 Introduction 1.1 Overview The IBM BladeCenter Deployment Guide is inten ded to p resent the general step s necessary to successfully deploy IBM blades in the I BM® BladeCenter™. Its primary focus is to detail the steps required for setting up rem ote boot on IBM Blade s.
IBM BladeCenter Deployment Guide Module slots 3 and 4 are used for Fibre Channel or other switch types and connect to the Server Blades as well as external devices. • Power - Four modular power supplies provide primary and backup power to all Blade Center subsystems.
IBM BladeCenter Deployment Guide Installation and Configuration 2 Preparatory Steps The BladeCenter Chassis compone nts should be pr epared by updating the firmwa re and assignin g the appropriate IP addresses to the man agement and switch modules.
IBM BladeCenter Deployment Guide Note: For switch communication throug h the managem ent module external Ethernet port, the switch module internal network int erface and the management module internal and external interfaces must be on the same subnet.
IBM BladeCenter Deployment Guide 2. Repeating Keystrokes - in ord er to remove the repeating keystroke problem, you need to check the "Disable key repeats" box and click Save. Figure 4 Disable key repeats 3. Start a Remote Control of the target blade by clicking on Rem ote Control under Blade Tasks .
IBM BladeCenter Deployment Guide 4. The Remote Control window is a pop up windo w. If you have a popup blo cker installed, Remote Control will be blocked, so make sure popups are allowed for the mana gement module IP.
IBM BladeCenter Deployment Guide 12 http://w3-03.ibm.com/support /techdo cs/atsmastr.nsf/W ebIndex/WP100564 © 2006 IBM Version 3.0, 3/ 10/2006 Figure 7 Logoff and Close the Bro wser Messages 9. Unexpected DLL version number error when starting Remote Cont rol.
IBM BladeCenter Deployment Guide Figure 8 Storage Connection Diagram 2.4.2 Disabling ports on the QLogic s witch Here are the steps necessary to disabl e ports on the QLogic switch. This can be don e either via a telnet session or a bro wser session. 2.
IBM BladeCenter Deployment Guide 3. Enter admin mode by entering “admin start” 4. Disable the target port by entering the comman d “ set port x state offline ” where x is the number of the port. For this example, we used “ 4 ” 5. Confirm the status by entering “ show port ”again.
IBM BladeCenter Deployment Guide 3. Right click on the desired port and c hoose "port properties" from the menu. 4. At the top of port properties put a bullet next to "offline" or "down". 5. Repeat steps 1-4 and reverse step 5 to online the port.
IBM BladeCenter Deployment Guide Blade Configuration and Installation 3 Configuring the Blades for Remote Boot The next few steps require BIOS configuration. To ent er the BIOS, follow the se steps: 1. Logon to the Management Module and select Power/Restart under Blade Tasks.
IBM BladeCenter Deployment Guide Figure 14 HS20 Boot Sequence 3. Adjusting the boot sequence for HS40 bl ades is slight ly different. Use the arrow keys to scroll to each startup device, then hit e nter and select the appr opriate value in the popu p window as shown in Figure 15 HS40 Boot Sequence .
IBM BladeCenter Deployment Guide Figure 16 Changing boot order from Management Module for HS20 3.2 Configuring the Qlogic HBA 3.2.1 Acquiring HBA WWPNs (World Wide Port Names) Each HBA has a uni que WWPN by which it is identified in a S AN network.
IBM BladeCenter Deployment Guide Figure 17 Configuring the QLogic HBA Figure 18 Host Adapter Settings 3.2.2 Configuring the pa th to the boot LUN The HBA that the server will be booting from will n eed to be d efined in the bios. At this point the HBA’s WWID has been zoned on the backend st ora ge as the owner of the boot LUN.
IBM BladeCenter Deployment Guide Figure 19 Enable Selectable Boot Illustration Figure 20 Bootable LUN address 20 http://w3-03.ibm.com/support /techdo cs/atsmastr.nsf/W ebIndex/WP100564 The BladeCenter Deployment Guide is intended as a personal pro ductivity tool.
IBM BladeCenter Deployment Guide Figure 21 Save your changes Critical Note: At this point, only one boot path is configured. During the INITIAL Operating System build, only one bo ot path shou ld be active. After the initial OS build a secondary path can be added if this is su pported by the storage vendor.
IBM BladeCenter Deployment Guide Figure 23 Verify Disk Media Once the HBA configuration steps ar e completed, during the POST sequ ence you will notice t he following text which indicates that the blade is now b ooti ng from the LUN 0 associated to the Fibre Channel Daughter Card.
IBM BladeCenter Deployment Guide If, however, the drivers are installed on the second Ethernet Controller in the list first, and then the first Ethernet Controller in the list, the connection nam es a.
IBM BladeCenter Deployment Guide 4 Installation Process for Red Hat Linux 4.1 Red Hat Advanced Server 2.1/3.0 Installation This section is intended t o detail the OS installation steps and may reference steps that have be en described and compl eted in previous sections.
IBM BladeCenter Deployment Guide Figure 27 Loading the Remote Diskette c. Power on or restart the target blade. Figure 28 Power On/Restart Blade 5. From this point on, the Red Hat installation proceeds like a standard installation. Version 3.0, 3/10/2006 http://w3-03.
IBM BladeCenter Deployment Guide Figure 29 linux nofb 6. Important: When the installation is co mplete, unmount the diskette drive before the reboot. Figure 30 Unmount the Diskette Image 7.
IBM BladeCenter Deployment Guide 13. Power on the server and enter the QLogic BIOS by pressing CTRL+Q . 14. From the Configurable Boot Settings , set the BOOT De vice to the alternate controller's Wo rld Wide Name (that you gathered) and the BOO T LUN to 0 .
IBM BladeCenter Deployment Guide Figure 31 Boot Failure for RH 3.0 Attempting a linux rescue does not appear to work; there are no partitions found on /dev/sda. Th e problem appears to be with the autopartitioning code and/ or the partitioning sta tements in the ks.
IBM BladeCenter Deployment Guide Version 3.0, 3/10/2006 http://w3-03.ibm.c om/support/techd ocs/atsmastr.ns f/WebIndex/WP100 564 29 Figure 33 fdisk Output Note: If you see this message shown i n Figure 34 , answer no.
IBM BladeCenter Deployment Guide 30 http://w3-03.ibm.com/support /techdo cs/atsmastr.nsf/W ebIndex/WP100564 © 2006 IBM Version 3.0, 3/ 10/2006 Figure 35 RPM Install of Broadcom Device Driv ers 4.
IBM BladeCenter Deployment Guide HS40 from the local media tray will wo rk, but it is recommended that the lowres option be used for the installation of AS2.1. 3. When b ooting from the remote floppy, the lowres (for RHAS2.1) or the nofb (for RHAS3.0) install mode should function correctly.
IBM BladeCenter Deployment Guide 32 http://w3-03.ibm.com/support /techdo cs/atsmastr.nsf/W ebIndex/WP100564 © 2006 IBM Version 3.0, 3/ 10/2006 irmware fix is released. This can be done by simply confirming that the ation 2: Leave read-only floppy diskette in the drive.
IBM BladeCenter Deployment Guide Version 3.0, 3/10/2006 http://w3-03.ibm.c om/support/techd ocs/atsmastr.ns f/WebIndex/WP100 564 33 Hat Linux and the X Window Sy stem for acc atta 1. P n to track the remote 768, complete the text mode, type: init 3 , type: rmmod mousedev following line to the olution) 2.
IBM BladeCenter Deployment Guide 34 http://w3-03.ibm.com/support /techdo cs/atsmastr.nsf/W ebIndex/WP100564 © 2006 IBM Version 3.0, 3/ 10/2006 13. b instead. This leads to a probl em 1. To boot ere d LUN in the storage arra • To p umber the gatekeeper (V CM) LUN to 16 or higher, 2.
IBM BladeCenter Deployment Guide Version 3.0, 3/10/2006 http://w3-03.ibm.c om/support/techd ocs/atsmastr.ns f/WebIndex/WP100 564 35 atch out for this RETAIN tip: http://www- If you are installing SLES9 to a loca l drive on an HS20, w 1.ibm.com/support/docview.
IBM BladeCenter Deployment Guide 36 http://w3-03.ibm.com/support /techdo cs/atsmastr.nsf/W ebIndex/WP100564 © 2006 IBM Version 3.0, 3/ 10/2006 nter. The firmware sections of these documents can be skipped as long a s you have followed the firmware recommendations in this do cum ent.
IBM BladeCenter Deployment Guide 4.8.3 alt-sysrq Version 3.0, 3/10/2006 http://w3-03.ibm.c om/support/techd ocs/atsmastr.ns f/WebIndex/WP100 564 37 u may be configuring SOL is for utilizing the alt-sysrq “magic key sequence”. ter the command: This will update that value in /etc/sysctl.
IBM BladeCenter Deployment Guide Figure 37 alt-sysrq from PuTTY Note, PuTTY has a nice feature that will log all of your session output to a file. Specify that before opening the telnet session. In certain rare circumsta nces, the serial data of the 8843 Blade Server may stop flowing.
IBM BladeCenter Deployment Guide Here is the link to the instructions from Red Hat that can be used to set up netdump: http://www.redhat.com/support/wpape rs/redhat/netdump/setup.html The netdump server from the RHEL3U3 distribution is version 0.6.1 1-3.
IBM BladeCenter Deployment Guide 5 Install Process for Windows 2000 and 2003 Remote Boot 5.1 Operating System Installation 1. Obtain the Fibre Daughter card device driver specified by your st orage vendor to support the use of the Qlogic HBA with their storage.
IBM BladeCenter Deployment Guide 8. Type the location of the Ethernet device driver s 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.
IBM BladeCenter Deployment Guide 6 Rem o te Update of the Firmw a re on an HS20 or H S40 The steps below detail ho w to update the blade firmware remotel y.
IBM BladeCenter Deployment Guide Notes: 1. It is necessary to upgrade the BIOS on the HS40 to the 1.44 level and the ISM P to 1.24 if you are installing Linux on the blade. (See Table 5 ) There is a probl em identified in the 1.32 versi on of the BIOS, related to EFI, which causes processors to be disabled.
IBM BladeCenter Deployment Guide 7 Flash the Q Logic HBA BIOS Perform the following steps to flash the QLogi c HBA BIOS: 1. Create a blank, bootable disk forma tted with MS-DOS, PC-DOS, or DR-DOS. 2. Using a text editor, verify that the config.sys an d autoexec.
IBM BladeCenter Deployment Guide 8 Red Hat Boot Diskette Modification Process 1. Copy the Network Boot Di skette (bootnet.img) and Supplemental Drive r Diskette (drvnet.img) files from the installation media (CD or ISO) to a temporary staging area. # cp /mnt/cdrom/images/{bootnet.
IBM BladeCenter Deployment Guide # ls 2.4.9-e.40BOOT # ls 2.4.9-e.40BOOT/{tg3.o,e1000.o} tg3.o e1000.o 9. Remove d evice drivers that will not be utilized from the driver modules extra cted to the first module directory in step #7.
IBM BladeCenter Deployment Guide # mv pcitable.new pcitable 14. Remove driver entries fro m the module-info file that are associated with the device drivers removed in step #9. Remove all stanzas that begin with the nam e of a remove d device driver (3c59x, eepro100, pcnet32, usb-ohci).
IBM BladeCenter Deployment Guide 22. Copy the initrd.img file to the bootnet.img image. # mv initrd.img mnt/boot 23. Unmount the bootnet.img. # umount mnt/boot At this point the bootnet.img file should be ready for use in remote deployment s. 8.1 Modify or Create the Post-i nstall Driver Diskette Image 1.
IBM BladeCenter Deployment Guide fi gunzip -c < /tmp/mnt-$$/modules.cgz | cpio -id for moduleDir in *; do for moduleFile in `find $moduleDir -name "*.o"`; do if [ -d /lib/modules/$moduleDir ]; then targetModuleFiles=`find /lib/modules/$moduleDir -name "$moduleFile"` if [ .
IBM BladeCenter Deployment Guide Appendix A. Firmware Versions The following tables contain both the minimum version s required deploy on the BladeCenter and its various components, and the current versions at the ti me this document wa s published. Please visit the IBM support site for the most current fi rmware versions for all components.
IBM BladeCenter Deployment Guide HS20 BIOS – Model 8843 Min Req Most Current Version 1.03 1.07 Release Date 2005/04/01 2006/01/2 0 Build Id BWE115AUS BWE122AUS Build Date 2005/03/25 2005/12/08 HS20 BMC – (8843) Minimum Req Most Current Version 1.
IBM BladeCenter Deployment Guide Release Date 2005/12/22 2005/12/2 2 Build Id BKBT414C BKBT 414C Table 6 LS20 BIOS and BMC Information QLogic HBA Firmware See 7 Flash the QLogic HBA BIOS for instructions on how to update the HBA BIOS. Minimum Req Most Current Version 1.
IBM BladeCenter Deployment Guide Appendix B. Worksheets BladeCenter Information BladeCenter Location User ID for BladeCenter Modules Password for BladeCenter Modules BladeCenter Component s Firmware L.
IBM BladeCenter Deployment Guide Index alt-sysrq ............................................................37 anaconda e rrors ............................................... 32 Boot sequence ................................................. 16 Broadcom drivers Linux insta llation .
An important point after buying a device McDATA 8832 (or even before the purchase) is to read its user manual. We should do this for several simple reasons:
If you have not bought McDATA 8832 yet, this is a good time to familiarize yourself with the basic data on the product. First of all view first pages of the manual, you can find above. You should find there the most important technical data McDATA 8832 - thus you can check whether the hardware meets your expectations. When delving into next pages of the user manual, McDATA 8832 you will learn all the available features of the product, as well as information on its operation. The information that you get McDATA 8832 will certainly help you make a decision on the purchase.
If you already are a holder of McDATA 8832, but have not read the manual yet, you should do it for the reasons described above. You will learn then if you properly used the available features, and whether you have not made any mistakes, which can shorten the lifetime McDATA 8832.
However, one of the most important roles played by the user manual is to help in solving problems with McDATA 8832. Almost always you will find there Troubleshooting, which are the most frequently occurring failures and malfunctions of the device McDATA 8832 along with tips on how to solve them. Even if you fail to solve the problem, the manual will show you a further procedure – contact to the customer service center or the nearest service center
