Home

McDATA 8832 User's Manual

Contents

1. 40 5 3 Broadcom Advanced Control Suite installation ccccccccsesecceceeeseeeeseeeeeeeeeseeseeeeeeeessaaaeeees 41 5 4 HVS TOP WIM AU ONS MN TER D ccs 41 6 Remote Update of the Firmware on an HS20 or HS40 cc eeceee eee eee eee eee eea eee eeeeeeeeeeeeeeeeeeeeeeeeaaes 42 6 1 BIOS and ISMP sea aoe Tm 42 6 2 BMC Update for the HS20 8843 and LS20 sese nennen 42 Version 3 0 3 10 2006 http w3 03 ibm com support techdocs atsmastr nsf W eblndex WP 100564 3 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 IBM BladeCenter Deployment Guide 7 Flash the QLogic HBA BIOS 44 8 Red Hat Boot Diskette Modification Process cccccccccccesceeceeeeeceeeeceeceeeceesaeeceseueeeeseeeeeesaaeees 45 8 1 Modify or Create the Post install Driver Diskette Image ccccccsseeeeeeeeeeeeeeeeeseeeeeeeeeeeaaaees 48 Appendix Firmware Versions ccccccsccssesssesscssesssesssesssecssesssessscssesssessusesesarecsressrecsvessesarecavecee 50 Appendix D Worksheets eerte 53 Table of Tables Table 1 Recommended settings for the QLogic QLA23xx adapter card for Windows 2000 or 2003 15 Table 2 Management Module BIOS INfo
2. seeeeseissssssseseseesseeeseennnn nnne nnne nnn nnne nnns 21 Figure 24 Verify Disk Media E 22 Figure 25 Blade POST with HBA configured cccccccccceccaeeeeeeceeeeeeceaeeeeeeeeeessueaseeeeeeeeessseaseseeeeeessaaagesss 22 Figure 26 Change Media Tray OWNneL ccccccccccseesseeccceeeceaeeeeeeeeeeseeaeeeceeeeeessueeeseeeeeeeesssaeseeeeeeessaeagegeees 24 Figure 27 Remote Media via the Remote Console sssssssessssssseeeee enne enne nnne nnns 24 Figure 28 Loading the Remote Diskette cccccccsssceccaeeeeeeeeeeeeeeeeecesseeeeseeeeeeessaeeeessaeeeesaeeessaeeeesseseees 25 Figure 29 Power On Restart Blade cccccccseeecceeseseeeeecsaeeseeeeeeeeeseeeessaeeeceeeeseeeeeeeeseegeeeeesseeeeeessaageeseeeeaas 25 4 http w3 03 ibm com support techdocs atsmastr nsf W eblndex W P 100564 2006 IBM Version 3 0 3 10 2006 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 IBM BladeCenter Deployment Guide Figure 30 linux TON Dac RR RTL 26 Figure 31 Unmount the Diskette Image sseessssessssssesseeeeeee nennen nnne nnnm nnns nnns 26 Figure 32 Boot Failure for RH 3 0 0 0 cccccsecccccseeeeeeeeseeecaeeeeeseeeeeeseaeees
3. On Demand Remote Control start Remote Control 9 Firmware Update a To disable the buttons located on the blade servers for KVM and media tray switching check the boxes below and click save Click Start Remote Control ta control a blade server remotely A new window will appear that provides access to the uH Remote Console and Remote Disk functionality On this window you will have full keyboard and mouse control af the blade iD ieee e server which currently owns the KM You will also be able to change KWM and media tray ownership ower Restart Management Note An Internet connection is required to download the Java Runtime Environment JRE ifthe Java 1 4 Plug in is not already Firmware Update installed MM Control General Settings Disable local KVM switching Login Profiles Configuration Serial Over LAN Disable local media tray switching errem n Alerts Fot Assignments 05 FISADIE KEY Tepeats Network Interfaces Network Protocals Save start Remote Control Figure 4 Disable key repeats 3 Start a Remote Control of the target blade by clicking on Remote Control under Blade Tasks Ensure that the media tray and KVM selections are for the target blade o Gae d Winzk3 Im m Glades ES Bladel iBlade4 ESX Blade E d TITTEN Tic WR p 47 pm eY Blades ium mh F LE EEL ha es uer Red Hat Enterprise Linux AS release 3 Taroon Update 3 Kernel
4. gzip 9 modules cpio ls 2 4 9 e 40BOOT modules cpio gz mv modules cpio gz modules cgz 12 Copy the required driver disk files from the initrd img image to the modules boot directory cp mnt initrd modules module info modules dep pcitable ls 2 4 9 e 40BOOT modules cgz module info modules dep pcitable 13 Remove driver entries from the initrd img pcitable file that are associated with the device drivers removed in step 9 Remove all lines that make reference to the removed device drivers 3c59x eepro100 pcnet32 usb ohci For example 0x10b7 0x4500 3c59x 3Com Corporation 3c450 Cyclone unknown 0x8086 0x1030 eepro100 Intel Corp 82559 InBusiness 10 100 0x1022 0x2001 pcnet32 Advanced Micro Devices cat pcitable grep v 3c59x grep v eeprol00 grep v pcnet32 gt pcitable new 46 http w3 03 ibm com support techdocs atsmastr nsf W ebIndex WP 100564 2006 IBM Version 3 0 3 10 2006 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 14 15 16 17 18 I9 20 21 IBM BladeCenter Deployment Guide mv pcitable new pcitable Remove driver entries from the module info file that are associated with the device drivers removed in step 9 Remove all stanzas that beg
5. 3 Next type send brk and hit enter You ll get a new line but no output 4 Then hit the sysrq command key you want such as h or m or p or w It should look like this root katherini root I i Hit Ctrl here elnet gt send brk yshq Show Regs hm After send brk then hit p id TGid H H comm Swapper LIP HHbH L amp cH1B93123 1 CPU 3 LIP is at default idle Lkernell Oxe9 4 4 41 4H ELsmp ESP HBHb cH1H31cZ EFLAGS HHHHHz4b Hot tainted HHHBBHBH EBA cH1H981HH ECX cBH43bcB8H EDA cB8He4HBH lip EDI c He48hHH EBP cHIB91804 DS BH68 ES BAGS FS HHAH GS HAHAH GHH5BHH3b CRZ b 5e 7BHHH CRS BHBzZ73ccH CR4 BABBHGTH all Trace XcH1B91cz2 1 cpu_idle kernel Hx42 Hxc8BHe5f b cH1294f3 gt printk kernel 4x1535 Hxc8BeSfcc Figure 36 alt sysrq from Linux client 4 8 3 2 alt sysrq from a Windows Client For a Windows client you need to use PuTTY or alternately the telnet client from the cygwin package was not able to get this working using regular telnet application in Windows Hyperterminal didn t work either 1 First telnet to the MM and login Then enter the command console T system blade x where x is the target blade number 2 here is the trick From the PuTTY pulldown menu click on Special Command gt Break 3 Then hit the sysrq command key you want Start with sysrq h Use sysrq 8 for maximum output level Version 3 0 3 10 2006 http w3 03 ibm com support techdocs atsmastr nsf W ebl
6. A device enclosed in parenthesis has been isabled in the Drresponding type enu Select Item Change Option General Help Save and Exit Exit wu2 51 CoCopyright 1965 2005 American Megatrends Inc Figure 15 HS40 Boot Sequence Press ESC to exit out of the BIOS and select the option to save changes Note For of HS40 blades make sure that EFI is at the end of the boot order if present If you have a lot of blades to update in a single blade chassis the boot order changes may be made through the Management Module and applied to any or of all of blades in the chassis as a group See Figure 16 Changing boot order from Management Module Since EFI appears as an unknown device for HS40s it is recommended that the HS40 boot sequence be modified in BIOS program Version 3 0 3 10 2006 http w3 03 ibm com support techdocs atsmastr nsf W eblndex WP 100564 17 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 3 3 18 IBM BladeCenter Deployment Guide i File Edit View Favorites Tools Help 3 o Bak C x B Ph Search sj Favorites Qi Media 4 2 Links 2 Matrix 2 Siebel i Google Srvr proven X Files 2 X Sales IBM Help H o t2 Bay 1 WMN315676989 Bay
7. When the Linux operating system starts a LILO boot prompt is displayed instead of the graphical user interface Pressing Tab while at this prompt will install all of the boot options that are listed To load the operating system in interactive mode type linux Interact and then press Enter To see the choices of kernels for boot from simply hit the tab key To re enable the graphical boot screen replace or uncomment the above line in the 1110o conf file and rerunning LILO 36 http w3 03 ibm com support techdocs atsmastr nsf W ebIndex WP 100564 2006 IBM Version 3 0 3 10 2006 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 IBM BladeCenter Deployment Guide 4 8 3 alt sysrq One of the reasons you may be configuring SOL is for utilizing the alt sysrq magic key sequence Enter the command gt sysctl w kernel sysrq 1 This will update that value in etc sysct1 conf and also set the value in proc sys kernel sysrqto 1 4 8 3 1 SOL using a Linux client 1 First telnet to the MM and login Then enter the command console T system blade x where x is the target blade number 2 here is the trick Once you have an SOL connection hit the escape sequence which is ctr1 This should bump you to a telnet prompt
8. gt tmp img ls bootnet img drvnet img mnt modules boot modules drv tmp img Mount the uncompressed initrd img file tmp img via the loopback device mount o loop tmp img mnt initrd ls mnt initrd bin dev etc linuxrc lost found modules proc sbin tmp var ls mnt initrd modules module info modules cgz modules dep pcitable Mount the drvnet img file via the loopback device mount o loop drvnet img mnt drv Extract the driver modules from the archive stored in the initrd img file to the first module directory created in step 2 modules boot cd modules boot gunzip c mnt rinitrd modules modules ogz cpio id 1412 blocks ls 2 4 9 e 40BOOT 1s 2 4 9 e 40BOOT SCOUR O bobo lock scsi qmod o usb olocri o vfat o eeprol00 o input o nis Sunroc o0 usb storage o Eat keybdev o pcnet32 0 usbcore o usb uhci o cd Extract the driver modules from the archive stored in the drvnet img file to the second module directory created in step 2 modules drv cd modules drv t gunzip c lt mnt drv modules cgz cpio id 3714 blocks Version 3 0 3 10 2006 http w3 03 ibm com support techdocs atsmastr nsf W eblndex WP 100564 45 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 IBM Blad
9. 01 c0 1a Serial Number 11S59P661 221 RJX336034 Reason for Status Normal Super user 2 True User Authentication Enabled False Vendor IBM Firmware Version 2 0 0 22 0 Thu Mar 11 19 41 18 2004 2 0 0 19 0 Tue Jan 27 17 12 39 2004 V2 0 0 22 0 Thu Mar 11 19 41 18 2004 Configured Zonesets Figure 11 SANSurfer Switch Faceplate 14 http w3 03 ibm com support techdocs atsmastr nsf W ebIndex WP 100564 2006 IBM Version 3 0 3 10 2006 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 IBM BladeCenter Deployment Guide 3 Right click on the desired port and choose port properties from the menu 4 Atthe top of port properties put a bullet next to offline or down 9 Repeat steps 1 4 and reverse step 5 to online the port amp Port Properties 5ANsurfer Switch Manager Symbolic Mame QLogic Selected Port Bay 4 Port States online offline diagnostics gt down ox eee wm Figure 12 Port Properties http knowledge storage ibm com servers storage support hbasearch interop hbaSearch do Recommended settings BIOS Disabled 2048 Loop reset delay Adapter hard loop ID Disabled Hard loop ID Execution throttle Fast
10. 3 SN418ICMC00172 Blade Boot Monitors System Status 2 devico Hardware VPD Firmware VPD 3 device Blade Tasks At device BH A Power Restart On Demand Remote Control Firmware Update Configuration Geral Over LAN Apply to all blade servers Figure 16 Changing boot order from Management Module for HS20 2 Configuring the Qlogic HBA 2 1 Acquiring HBA WWPNs World Wide Port Names Each HBA has a unique WWPN by which it is identified in a SAN network Accurate tracking of WWPNs ensures that each server has the proper storage presented to the appropriate location The recording of the WWPN information is only required once for ESM to perform zoning for the SAN If this has already been performed skip to Section 3 2 2 To acquire these WWPNs e Restart the target blade server being configured for remote boot and enter the QLogic BIOS utility using CTRL Q This must be done at a specific time during the POST Note you must click the sticky Ctrl icon on the Remote Control page when using the Management Module for this task and then you ll only need to press Q on the keyboard e Oneata time select each HBA listed and record the WWPNs http w3 03 ibm com support techdocs atsmastr nsf W ebIndex WP 100564 2006 IBM Version 3 0 3 10 2006 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 b
11. Web and telnet interfaces can be started by accessing the switch directly or starting a session from the management module s Web interface Note The external ports on the switch must be enabled and enabled for management as well to manage the switch directly without going through the management module Because the management interface is on VLAN 4095 and cannot be moved a separate interface from the management interface must be created with an IP address valid on the production network to manage the switch directly MAC MAC MAC la 28 38 1b 2b 3b Figure 2 BladeCenter internal network 8 http w3 03 ibm com support techdocs atsmastr nsf W eblndex WP 100564 2006 IBM Version 3 0 3 10 2006 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 IBM BladeCenter Deployment Guide Note For switch communication through the management module external Ethernet port the switch module internal network interface and the management module internal and external interfaces must be on the same subnet 2 2 BladeCenter Management Module To use the Management Module to perform tasks in the coming sections remotely first do the following Open a browser and input the IP address of the MM The default IP address of the external port o
12. installation package and extract files and place the directory structure onto a driver diskette Boot the blade and access the Windows installation media As the Windows installation media is accessed a message will appear prompting the user to press the F6 function key to load a device driver Depress the key and when prompted load the HBA device driver created in step 1 If Windows prompts you to use the driver included with Windows or the driver that you have specified be certain to use the driver from the diskette not the driver included with Windows Continue with the Windows OS load as normal Install the recommended service packs and reboot For path failover a multi path device driver must be installed as specified by the storage vendor Power down the HS20 blade server Once the OS has been installed you can re enable the port for the secondary HBA on the Qlogic switch If required zone the external switch for the WWPN of the second HBA Power on the server and enter the QLogic BIOS by pressing CTRL Q For port B 2600 From the Configurable Boot Settings set the BOOT Device to the alternate controller s World Wide Name that you gathered and the BOOT LUN to O From the Basic Settings panel verify that the BIOS on this adapter is Enabled Verify that your storage partitioning and host group configuration looks similar This configuration should account for both HBA WWPNs and the boot partition being configur
13. is 1 43 Programming QLA2312 flash at I O Address 2400 Verifying QLA2312 flash at I O Address 2400 Flash at I O Address 2400 Verified Successfully New version of the QLA2312 flash BIOS at I O Address 2600 is 1 43 Programming QLA2312 flash at I O Address 2400 Error erasing flash at I O Address 2600 Figure 39 QLogic HBA Flash NOTE During the installation of the BIOS the error message shown above will be displayed This message is normal and does not indicate an issue 7 Remove the disk and reboot the PC After POST you should see the following with your new BIOS version QLogic Corporation QLA2200 PCI Fibre Channel Rom BIOS Version 1 43 Copyright C QLogic Corporation 1993 2001 All rights reserved www qlogic com Press CTRL Q for Fast UTIL NOTE See the IBM eServer BladeCenter Fibre Channel Expansion Card Installation and User s Guide that can be found in the Docs folder of this Utility CD for additional information For more information on the IBMUTIL program either type ibmutil at the command prompt If you need to restore the defaults settings for the HBA perform the following steps a b 44 Press CTRL Q to enter Fast UTIL when the following BIOS banner displays Perform the following steps to restore the default settings and reboot the PC Use the UP ARROW and DOWN ARROW keys to make your selection i Select Configuration Settings then press ENTER ll Select Restore Default Settings then
14. not on the same path as the bootable HBA port you will receive an INACCESSIBLE BOOT DEVICE error message 4 f 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 W eblndex WP 100564 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 IBM BladeCenter Deployment Guide 6 Remote Update of the Firmware on an HS20 or HS40 The steps below detail how to update the blade firmware remotely This process is much quicker than updating the firmware locally using the media tray since the slow diskette reads are replaced by much quicker virtual floppy reads from the Management Module The downside is we are exposed to some of the network related management module quirks we have experienced 6 1 BIOS and ISMP 1 Go here to download the most recent versions of the BIOS and ISMP updates for the HS40 Currently there are three files that you ll need to download 2 for the BIOS update and 1 for the ISMP update www 306 ibm com pc support site wss document do lndocid MIGR 54597 2 The files are downloaded as self extracting disk
15. press ENTER iii You are prompted to press any key Press ENTER iv Press ESC v When prompted press ENTER to save the changes vi Select Exit Fast UTIL then press ENTER vii When prompted to reboot the system press ENTER http w3 03 ibm com support techdocs atsmastr nsf W ebIndex WP 100564 2006 IBM Version 3 0 3 10 2006 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 IBM BladeCenter Deployment Guide Red Hat Boot Diskette Modification Process Copy the Network Boot Diskette bootnet img and Supplemental Driver Diskette drvnet img files from the installation media CD or ISO to a temporary staging area cp mnt cdrom images bootnet img drvnet img ls bootnet img drvnet img Create the temporary mount point and two module directories t mkdir p mut iboot drv inrttfd ls mnt boot dry initrd mkdir modules boot modules drv ls bootnet img drvnet img mnt modules boot modules drv Mount the bootnet img file via the loopback device mount o loop bootnet img mnt boot ls mnt boot boot msg general msg ldlinux sys rescue msg vmlinu z expert msg initrd img param msg Bvelanux ctg Uncompress the initrd img file to the staging area gunzrp gG lt mnt boot dinitro img
16. provides physical planning information for the IBM BladeCenter products It describes the BladeCenter components explains deployment and installation considerations and provides worksheets that you can use to determine the configuration power weight and cabling requirements for your BladeCenter unit http www 1l ibm com support docview wss uid psglMIGR 53670 e IBM server BladeCenter Type 8677 Installation and User s Guide This document contains general information about your BladeCenter unit including information about features how to configure your BladeCenter unit and how to get help It is provided with the BladeCenter unit and is on the IBM BladeCenter Documentation CD e IBM server BladeCenter Management Module User Guide This guide contains information about configuring the management module and managing components installed in BladeCenter chassis http www 1l ibm com support docview wss rs 0 amp uid psglMIGR 45153 e IBM amp server xSeries and BladeCenter Server Management 8624 6495 This document covers the hardware side of the IBM systems management solution including the BladeCenter management module It is available for download from the IBM Web site at http www ibm com redbooks 1 2 BladeCenter Subsystems The various BladeCenter Subsystems include e Server Blades provide the processors memory hard disk s and firmware of an industry standard server In addition they will normally incorporate keyboard
17. since it won t attempt to partition the second path The partition table on device sdb was unreadable To create new partitions it must be initialized causing the loss of ALL DATA on this drive This operation will override any previous installation choices about which drives to ignore Would you like to initialize this drive erasing ALL DATA lt Tab gt lt Alt Tab gt between elements 1 lt opace gt selects 1 XFlZ5 next screen Figure 34 Invalid Partition Table Aside from the 2 differences noted above the process detailed in Section 4 is essentially unchanged just make sure you are using the correct diskette image 4 4 Red Hat Linux AS Broadcom driver installation After loading the operating system the network drivers should work immediately However we downloaded the latest Broadcom device drivers for Linux and performed the instructions in Example 6 1 to install them The latest Broadcom device drivers were obtained from the following URL http www ibm com pc support site wss document do lndocid MIGR 54186 Version 3 0 3 10 2006 http w3 03 ibm com support techdocs atsmastr nsf W eblndex WP 100564 29 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 IBM BladeCenter Deployment Guide root localhos
18. the secondary HBA on the Qlogic switch 12 Zone the McData switch for the WWPN of the second HBA 26 http w3 03 ibm com support techdocs atsmastr nsf W ebIndex WP 100564 2006 IBM Version 3 0 3 10 2006 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 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 Device to the alternate controller s World Wide Name that you gathered and the BOOT LUN to 0 15 From the Basic Settings panel verify that the BIOS on this adapter is Enabled 16 Verify that your storage partitioning and host group configuration looks similar This configuration should account for both HBA worldwide port names and the boot partition being configured to LUN 0 17 Reboot the server 4 2 Kickstart Information The SYSLINUX CFG should have the following line at the top of the file Of note the ks cfg file is built into initrd img text is specified to avoid problems displaying the graphical installation dialogs via the Management Module that result in blank screens nofb is another way to avoid a black screen during install default ksinstall prompt 1 timeout 600 label ksinsta
19. 2 Bceast29 42 166 255 Mask 255 255 255 0 UP BROADCAST RUNNING MULTICAST MTU 1500 Metric 1 Browse MAC Address Table Top Switch VID MAC Address Port Learned 9 00 11 25 4a 00 4c Bay 13 Dynamic ethl Link encap Ethernet HWaddr 00 11 25 4A 00 4D inet addtr 10 0 200 32 Beast 10 0 255 255 Mask 255 255 0 0 UP BROADCAST RUNNING MULTICAST MTU 1500 Metric 1 Browse MAC Address Table Bottom Switch VID MAC Address Port Learned 100 00 11 25 4a 00 4d Bay 13 Dynamic Version 3 0 3 10 2006 http w3 03 ibm com support techdocs atsmastr nsf W eblndex WP 100564 23 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 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 to detail the OS installation steps and may reference steps that have been described and completed in previous sections The steps below assume that the QLogic configuration steps in Section 3 2 have been completed These steps have been confirmed for Red Hat AS 2 1 Update 4 and Red Hat AS 3 0 Update 3 and above Please see Section 4 4 for known issues related to this and other releases of Red Hat 1 Recommended From the secondary QLogic Fibre Channel switch module DISAB
20. 2 is now going to switch 1 In older versions of Linux it was observed that ethO went to the Ethernet switch in switch bay 2 and eth1 goes to the Ethernet switch in switch bay 1 This was reversed from a normal Windows 2000 install as previously mentioned and also proves to be the source of some confusion However current testing with Linux Red Hat Version 3 Update 6 and SLES 9 has shown that ethO goes to the Ethernet switch in bay 1 and eth1 goes to the switch in bay 2 On an HS40 blade 0 amp 2 should be connected to top switch module and 1 amp 3 connect to the bottom switch module The designations can be verified by browsing the MAC address table on the Ethernet switch and match the values to the MAC addresses show in the ifconfig output on the blade The following example shows the MAC address of Eth 0 1 devices Log into the top switch module bay 1 and search for the MAC address on Internal port 13 Bay 13 corresponding to EthO device It shows the same MAC address of EthO For Eth1 do the same by logging into switch module bay2 bottom and searching for the MAC address on internal port 13 it also shows the same MAC address for Eth1 root hs20 8843 root cat proc version Linux version 2 4 21 27 ELsmp bhcompileGbugs build redhat com gcc version 3 2 3 20030502 Red Hat Linux 3 2 3 47 1 SMP Wed Dec 1 21 59 02 EST 2004 root hs20 8843 root ifconfig a etho Link encap Ethernet HWaddr 00 11 25 4A 00 4C inet addr 9 42 166 8
21. 3 No blade presen dace j pdate 4 No blade presen Lonnguratio sip LAN SEE Eee ee lO Module Tasks 6 No blade presen Power Restart f Wo blade presen Management g No blade presen Firmware Update q No blade presen MM C 0 m pene Settings ERN ee Login Profiles 11 No blade presen Alerts 12 No blade presen Port Assignments 13 No blade presen Network Interfaces 14 No blade presen Network Protocols E Security Power On Blade Configuration File Firmware Update xw s u Enable Local Power Control Figure 28 Power On Restart Blade 5 From this point on the Red Hat installation proceeds like a standard installation Note you must specify linux nofb when installing via BladeCenter Remote Control otherwise you will see the No Video Available screen instead of the Linux installation dialogs You should also be able to set the correct mode setting with the vga 0x301 option See RETAIN Tip 167679 http www l ibm com support docview wss uid psglMIGR 55660 for more information Version 3 0 3 10 2006 http w3 03 ibm com support techdocs atsmastr nsf W eblndex WP 100564 25 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 IBM BladeCenter Deployment Guide redhat To insta
22. IBM BladeCenter Deployment Guide tf 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 com support techdocs atsmastr nsf W eblndex WP 100564 1 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 IBM BladeCenter Deployment Guide 2 http w3 03 ibm com support techdocs atsmastr nsf W ebIndex WP 100564 2006 IBM Version 3 0 3 10 2006 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 IBM BladeCenter Deployment Guide Table of Contents MEE PUOTI e c 6 1 1 87 17 6 1 2 BladeCenter SUDSYStOMS ccccccccceccceesseeeceeeeeeeeessseceeeeeeeeaeaeesceeeesseeesseeeeeeeesseeaseeeeeeeessaagaasss 6 1 3 IOUS MR 7 1 3 1 OF MA OS NIETO TT ENDS 7 Installauon dnd GOMMGUPANON ace sinceroa dae mre onmes sni In Uer sued cut o qtu aaa airaa Ra S nnc pese idut SU Uude 8 2 PNA ivit acetate cineca ate e
23. ITITTIITI Vendor IBM Model 46P 7096a 5320 1 Fev 1 Type Processor ANSI SCS revision ti blk queue f 3hbetB8 70 Limit 42984957295Mb mask Hk amp TffffffTfTTITIIIII Loading jbd o module Journalled Block Device driver loaded Loading ext3 o module Mounting proc filesystem Creating block devices Creating root device mkrootdev label not found Mounting root filesystem mount error 2 mounting ext3 pivotroot pivot _root sysroot sysroot initrd failed umount initrd proc failed 2 Freeing unused kernel memory 22B8k freed Kernel panic No init found Try passing init option to kernel 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 The problem appears to be with the autopartitioning code and or the partitioning statements in the ks cfg If you are stuck and can t get the second path disabled on the switch then the following approach should work The actual partitioning of the drive must be done in the pre section of the kickstart configuration file shown in Figure 32 The partition information is specified using MB values indicated by the uM flag Each partition is defined on a separate line with each separated by the n character The actual partitions can be assigned as before but the sizes are not specified since the partitions have already been created in the pre script Do not include the clearpart statement
24. LE the port of the secondary HBA This HBA can be re enabled after the initial OS load This process is detailed in 2 4 Note we have been able to successfully load Red Hat Version 2 1 without this step but we see shadow drives during installation Please see Section 4 3 for more information relating to dual path installations with Version 3 0 2 The bootnet img diskette provided in the Red Hat AS2 1 Update 4 does not contain the network drivers for the network chips on either blades HS20 tg3 HS40 e1000 A custom bootnet image file is required for using this kickstart process A single image can be built that works for both HS20 and HS40 blades 3 One of the differences between installing 2 1 and 3 0 on the blades is that in Version 3 0 the network drivers do not fit on single floppy image with the installation kernel What we ve done to support Kickstart from a floppy is create separate boot diskettes for the HS20 and HS40 4 Using the Management Module boot the blade server from the kickstart floppy using the following steps a First itis recommended that the media tray is not owned by the target blade See Figure 25 BladeCenter Remote Control Microsoft Internet Explorer 7 Change KVM Media Tray Owner Change KVM owner Blade SNf418ICMCO0008 Change media tray owner Figure 25 Change Media Tray Owner b Load the kickstart floppy image to the RSA card This can be done either from a physical floppy disk b
25. LUN 21 Broadcom drivers VN EN n 18 Linux installation eeeeseee 29 QLogic Switch Windows installation 40 Disabling ports eesssseessssssss 13 DISK BETOLS cscnittsedesententaee rive isa fev eicecun es bireer onines 31 SANSHBIOE assensum fen eziiri vits er crrig penis tienes 14 Firmware Levels RDA 35 aei m 50 51 Red Hat go 30 51 CAC ONG Ais pen ancumicentwencdtateetsudeonsetinsaeersiunseeetsls 32 Management Module 50 AS 2 1 InstallatlOnizsssiaos irat trenes 24 CLOSE PB Aeria qusc dE 52 AS 3 0 InstallatiOnisise seccion toii iride ea ioni 24 HS20 AS 4 0 Installation 34 Boot sequence eeeeeseeeeeeeeenen nnn 17 Boot Diskettes eesssssse 45 Disable IDE Leeeuusssee 16 Disk errors eeeesseeeeeseseee eene 31 Firmware levels eeeese 50 51 Installation options 31 Updating firmware eseseeeeess 42 Partitioning eeeeeeeeeeeeeene 27 28 29 HS40 Related Documents ccccceeseeeeeeeeeaeeeeeeeees 6 BOO SCOMCIICS vaca astconetesscsescinescosssevaeeantepiee
26. Z 41 z21 zH ELsmp on an i586 fafrin login _ as amp Applet com ibm asm remotedisk RemoteDisk started teeta Figure 5 KVM and Media Ownership 10 http w3 03 ibm com support techdocs atsmastr nsf W ebIndex WP 100564 2006 IBM Version 3 0 3 10 2006 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 T IBM BladeCenter Deployment Guide The Remote Control window is a pop up window If you have a popup blocker installed Remote Control will be blocked so make sure popups are allowed for the management module IP Note Remote Control does work with Firefox so if you are having trouble with the popup blocker in Windows XP SP2 Firefox may be a viable alternative The Remote Control window includes a tool bar Figure 6 with sticky keys for passing ctrl alt and others keystrokes to the target system This is particularly important when trying to enter setup screens such as the QLogic setup which is accessed by hitting ct r1 Click on the sticky ctrl then hit Q when you see the message during POST If there is no keyboard response in Remote Control confirm that the Remote Control window has focus Click on the keyboard widget in the toolbar There is also a known issue fixed
27. agement Module firmware update interface While this flashing via the Management Module apparently can be done while the blade is running the final apply of the firmware WILL cause the blade to power off So the target blade should be power off AND all blades must be discovered before flashing remotely Or ue To install the BladeCenter BMC firmware from the BladeCenter Management Module web interface perform the following steps 1 In the navigation frame click Firmware Update under Blade Tasks select the Target blade slot number then click Browse 2 Switch to the drive and directory containing the unpackaged files The package files are found on Diskette 2 Navigate to the PKT file you want to update named as BWBIxxy PKT Where xx build ID and y revision 3 Click Open The file including the full path appears in the box beside Browse 4 To begin the update process click Update A progress indicator opens as the file is transferred to temporary storage A confirmation page opens when the file transfer is completed and the BladeCenter Integrated System Management Processor has been restarted In case of a failed RS485 remote flash 1 Only one blade can be in kernel mode in a chassis at one time 2 The Management Module has known issues if a flash fails The easiest way to recover is to a Pull the failed blade from the chassis b Reset the MM c Reinsert the failed blade d Retry the flash on the failed blade after the bla
28. and do not specify zerombr in the kickstart file either zerombr yes indicates that you would like the Red Hat installation program to initialize all invalid partition tables on disks visible at the time of installation zZzerombr yes clearpart all part boot fstype ext3 onpart sdal part fstype ext3 onpart sda2 part swap onpart sda3 spre printi 1 100 1 Xn 12000 05Wn 2048 S9SXn LbWn sfdisk dev sda uM Figure 32 Kickstart Modifications The above example creates the partition information shown in Figure 33 28 http w3 03 ibm com support techdocs atsmastr nsf W ebIndex WP 100564 2006 IBM Version 3 0 3 10 2006 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 IBM BladeCenter Deployment Guide root fafrin root fdisk 1 Disk dev sda 18 1 GB 18158714880 bytes 255 heads 63 sectors track 2207 cylinders Units cylinders of 16065 512 8225280 bytes Device Boot Start End Blocks Id dev sdal 1 13 104422 83 dev sda2 14 1543 12289725 83 dev sda3 1805 2104515 82 inux swap dev sda4 2207 3229065 83 inux Figure 33 fdisk Output Note If you see this message shown in Figure 34 answer no In this situation it may be possible to install successfully without the pre script
29. and floppy media Management Power Module 1 Module 1 Switch Module Bay Power Module 2 Management Module Bay 2 Figure 1 BladeCenter Chassis Rear View 1 3 Notes This is currently a living document and will continue to grow as we have more experience with IBM Blades in the boot to SAN environment This document 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 A At you are installing Linux please pay close attention to the issues listed in Section 4 5 1 3 1 Contributors We would like to acknowledge the contributions of the following people 1 Richard Gebhardt IBM Lab Services Appendix E Modify or Create the Post install Driver Diskette Image portions of Section 4 Installation Process for Red Hat Linux 2 Fred Rabert Nortel Networks Assistance with Section on Nortel switches plus BroadCom Driver installation instructions Version 3 0 3 10 2006 http w3 03 ibm com support techdocs atsmastr nsf W eblndex WP 100564 7 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 IBM BladeCenter Deployment Guide Installat
30. asis without warranty of any kind Please be aware that its contents have not been certified by IBM IBM BladeCenter Deployment Guide Configuration Settings i Host Adapter Settings Figure 17 Configuring the QLogic HBA QLAZ3xx CBE 1 38 095605 4 2 GEES 6636552 Enabled Figure 18 Host Adapter Settings 3 2 2 Configuring the path to the boot LUN The HBA that the server will be booting from will need to be defined in the bios At this point the HBA s WWID has been zoned on the backend storage as the owner of the boot LUN e lf you are not already in the QLogic BIOS utility restart the target blade server being configured for remote boot and enter the QLogic BIOS utility using CTRL Q as described in Section 3 2 1 e Select Configuration Settings then Selectable Boot Settings then set Selectable Boot to Enabled e Select primary boot path press Enter and the LUN ID should be visible as shown in Figure 20 Version 3 0 3 10 2006 http w3 03 ibm com support techdocs atsmastr nsf W eblndex WP 100564 19 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 IBM BladeCenter Deployment Guide Selectable Boot Settings Figure 19 Enable Selectable Boot Illustration Hn device present Figure 20 Bootab
31. ation 3 When media tray is assigned to a blade it will automatically hotplug itself and the cdrom and floppy drive will be available for use When user is done with the cdrom and or floppy media tray should be unassigned from the blade and or the usb storage module should be removed The command for this is rmmod usb storage This step should also be performed when the IBM Remote Disk is used The IBM Remote Disk is the feature where an image or even the local floppy or CDROM drive can be mounted on the blade from the local machine have not seen anything to indicate that a Red Hat kernel fix can be completed to prevent these error messages from being generated floppy o error messages Adding alias block major 2 off to etc modules conf will get rid of that noise There is a know bug in anaconda which causes the installation of Red Hat 2 1 Update 3 to fail in most cases on an HS40 http bugzilla redhat com bugzilla show bug cgi id 113346 This is the charming You re running me on a live system That s incredibly stupid message and has been addressed in errata rhn redhat com errata RHEA 2004 148 html which is included in RHAS 2 1 Update 4 An error message of pc key b controller malfunction OxA7 is seen many times when RHEL 3 is booting during a five second interval This problem exists because the IBM eServer BladeCenter HS20 type 8843 is the first legacy free x86 system and therefore does not have a standard keyboard co
32. ce Hard Disk 0 Third Startup Device Network Fourth Startup Device 16 http w3 03 ibm com support techdocs atsmastr nsf WebIndex WP 100564 2006 IBM Version 3 0 3 10 2006 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 IBM BladeCenter Deployment Guide Startup Sequence Options Primary Sbortap Seguenor First Startuj Second Startup Device hird Starti Fourth Starts Wake On LAN Figure 14 HS20 Boot Seq Device leu jor ip Device Peeviois Ua lie uence Diskette Driue 8 estore Setting L Defoe lt setting 3 Adjusting the boot sequence for HS40 blades is slightly different Use the arrow keys to scroll to each startup device then hit enter and select the appropriate value in the popup window as shown in Figure 15 HS40 Boot Sequence Startup Sequence options Startup Sequence options First Startup Device Second Startup Device Third Startup Device Fourth Startup Device Sth Boot Device CTEAC FD H5PIUBT CLG CD ROM CRN 6245 CHA B PortID 6548131 Options LG CD ROM CRN 6245B1 16 TOSHIBA DUD ROUM 5D R8H40121121 TEAC FD G5PUB HA OD PortID 654013 OPEN L IBA GE Slot BIHB v1215 IBA GE Slot amp 110 v1215 EFI 1 18 14 51 Specifies the boot sequence from the avallable devices
33. cing it on an accessible storage device local or remote and specify the location in the kickstart file see the Kickstart File Modification section below If we were adding the ServeRAID adapter to an existing driver diskette image then we would have to follow a process similar to that described in Section I but instead of adding the device driver and diskette image files to the boot image we would add them to an already existing driver diskette image file 2 Kickstart File Modification You must specify the location of the supplemental driver diskette image create in step II by placing the following keyword and parameters in the Red Hat kickstart file If we are installing via FTP driverdisk source ftp path to 26k4970 img If we are installing via HTTP driverdisk source http path to 26k4970 img If we are installing via NFS driverdisk source nfs host path to 26k4970 img When adding a network device driver such as bcm5700 and e1000 to the Red Hat installation initial ramdisk image you must perform the following steps 3 Create the following script update modules sh and place it in the rh3 directory of the NFS share Please note that by default it is assumed that the driver diskette image you created in section has the filename dd img and is located in the root directory of the NFS share bin sh constants IMAGE_FILE dd img DEPMOD sbin depmod Save current directory CWD pwd create te
34. command posting Enabled gt 4 GB addressing Disabled for 32 bit systems LUNs per target Enable LIP reset Enable LIP full login Enable target reset Yes Note Enable LIP reset Enable LIP full login and Enable target reset parameters control the behavior of the adapter when Windows tries to do a SCSI bus reset You must perform a target reset to make cluster failovers work Use the SCSI bus device reset option to clear SCSI reservations 20 minimum 20 minimum Enabled No Table 1 Recommended settings for the QLogic QLA23xx adapter card for Windows 2000 or 2003 Version 3 0 3 10 2006 http w3 03 ibm com support techdocs atsmastr nsf W eblndex WP 100564 15 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 IBM BladeCenter Deployment Guide Blade Configuration and Installation 3 Configuring the Blades for Remote Boot The next few steps require BIOS configuration To enter the BIOS follow these steps 1 Logon to the Management Module and select Power Restart under Blade Tasks 2 Select the blade to be restarted then at the bottom of the page click Restart Blade and Ok when prompted 3 Start a Remote Control of the target blade by clicking on Remote Control under Blade Tasks Ensure that the media
35. ctivity 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 IBM BladeCenter Deployment Guide Figure 23 Verify Disk Media Once the HBA configuration steps are completed during the POST sequence you will notice the following text which indicates that the blade is now booting from the LUN O0 associated to the Fibre Channel Daughter Card QLogic Corporation WLAZI12 PCI Fibre Channel ROM BIOS Version 1 36 Subsystem Vendor ID 1814 Copyright C QLogic Corporation 1993 2083 ALL rights reserved wi Gloqgic com Press CTRL 0 gt for Fast llTIL BIOS for Adapter H is disabled ISP23512 Ficmware Version 3 02 18 QLogic adapter using IRQ number HB Device Device Adapter Port Lun Vendor Product Product Number Type Humber ID Humber ID ID Revision Disk 1 HLOFOA A IBM 1742 HSER ROM BIOS Installed Figure 24 Blade POST with HBA configured 3 3 Ethernet Port Numbering In most cases for Windows 2000 2003 the connection named Local Area Connection goes to the Ethernet switch in switch bay 1 and the connection named Local Area Connection 2 goes to the Ethernet switch in switch bay 2 We use the phrase most cases because this is not always the case For Windows 2000 the order of the Local Area Connection names assigned is based on the order in which the drivers for each NIC are installed The driver
36. cts cigctcec nestor hg 8 2 1 NOWO Omi AO he esessicpcns ntt co code cee ccentc scp deme echo sunm ed MPO END MUNI EDU NM ON OD S UN UNI TRU Ut DUE 8 2 2 BladeCenter Management Module esssssssseesseseseeeeeenn nennen nnne nennen nnns nnn nnns 9 2 3 Remote Control Hints and Tips nennen nnne nennen nnn nnns nnn nnns 9 2 4 Embedded Fibre Channel SWitChes ccccccccssssseeecceeeeeeeeeseeeeeeeeesaeeeceeeeesseaeaeeeeeeseessaaagases 12 2 4 1 SAN GOMIGQUIVAU ON RR 12 2 4 2 Disabling ports on the QLOGIC switch ccccccccccceeeeeececeeeeeeesseseeeceeeeeeeseesesesaaaaeeeeeeees 13 Blade Configuration and Installation ccccccccccccccssseeeceeeeeeeeseeseeeeeeeeseeeseeeeeeeesseeeeeeeeeeeeeseaeasseeeeeeeessaeaseses 16 3 Configuring the Blades for Remote Boot cccccccccsseeseeeeeeeeeeeeeeeeceeeeeeaeeeeeeeeesesseaeeeeeeeeeesaaaaaeees 16 3 1 1 Disabling IDE devices NEN TL 16 3 1 2 ele E BOO ONG CW aorar iyi EA E E EN 16 32 Contig ring the Qlogic HBA s ssec Dene mm 18 3 2 1 Acquiring HBA WWPNs World Wide Port Names cccsssceecsseseeesseeeeeeseeseeeeaeeeeeas 18 3 2 2 Configuring the path to the boot LUN ccccccccsssseeeceeeeeeeeeeeeeeeeeeseeeaeseeeeeeessaeeaeees 19 3 2 3 Testing the path to the boot LUN sseeeeessseeeeennneenenen nnnm 21 3 9 Ethernet Port Numbering eeesssssssesssseeee nennen nennen nnne nnns n
37. deCenters which use Qlogic HBAs Host Bus Adapters Separate fabrics allow full redundancy in the storage path The IBM Blade Server boots to drives physically located on the Hitachi subsystem over the SAN Qlogic HBAs must be specifically configured to allow remote booting See diagram 1 for a visual representation of this architecture 12 http w3 03 ibm com support techdocs atsmastr nsf W ebIndex WP 100564 2006 IBM Version 3 0 3 10 2006 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 IBM BladeCenter Deployment Guide DS4000 Multipath Configuration Blade 1 Blade 2 To install blade 2 3 disable port on switch 2 X However with red paths enabled still see multiple LUNs J M Since we are already cross connected in the chassis we don t need to cross connect here DS4000 Figure 8 Storage Connection Diagram 2 4 2 Disabling ports on the QLogic switch Here are the steps necessary to disable ports on the QLogic switch This can be done either via a telnet session or a browser session 2 4 2 1 Using Telnet 1 Start a telnet session with the IP address of the QLogic Switch Module 2 After logging in enter the command show port to view the current
38. ded 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 IBM BladeCenter Deployment Guide You have logged off the web interface This window will attempt to close in 5 seconds If a confirmation dialog is displayed click Yes or OK To maintain security you must also manually close any other web browser windows that might be open Otherwise any previously entered user IDs and passwords will remain available in the temporary browser cache Microsoft Internet Explorer E The Web page you are viewing is trying to dose the window Do you want to dose this window Figure 7 Logoff and Close the Browser Messages 9 Unexpected DLL version number error when starting Remote Control Invalid Library Initializing RemoteDisk v2 0 Attempting to load remotedrive dll LI ted DLL ber e Mid bc Rd Remote Disk library successfully loaded DLL reported 12 Expected 13 Unexpected DLL version number If you encounter this error when the remote control window is opened exit Internet Explorer find the copy of remotedrive dll on your system most likely in c Program Files Internet Exploder and delete it 2 4 Embedded Fibre Channel Switches 2 4 1 SAN Configuration Shown in Figure 8 is an example of a dual path SAN configuration that we will be using as a reference in this document Two McData directors steer traffic through separate fabrics to the IBM Bla
39. des have all been discovered 42 http w3 03 ibm com support techdocs atsmastr nsf W ebIndex WP 100564 2006 IBM Version 3 0 3 10 2006 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 IBM BladeCenter Deployment Guide Notes 1 It is necessary to upgrade the BIOS on the HS40 to the 1 44 level and the ISMP to 1 24 if you are installing Linux on the blade See Table 5 There is a problem identified in the 1 32 version of the BIOS related to EFI which causes processors to be disabled The only fix for this error is to upgrade the BIOS and ISMP firmware Occasionally the boot of the first BIOS diskette will fail with old time DOS messages such as cannot find country sys If you end up at a DOS prompt when booting the BIOS diskette simply run AUTOEXEC BAT to kick off the update process If you don t get a DOS prompt restart the blade Take care when mounting the second BIOS diskette and try to avoid having to restart the Management Module once the update process has begun If you do encounter and unrecoverable error at this point you should be able to restart the BIOS process from the beginning The blade will most likely boot off of the backup BIOS In this case answer no when asked if you d like to backup the prima
40. device 4 vend prod 0x5ab 0x30 is not claimed by any active driver 09 44 30 spencerooni 1 Initializing USB Mass Storage driver 09 44 30 spencerooni 1 usb c registered new driver usb storage 09 44 30 spencerooni 1 scsil SCSI emulation for USB Mass Storage devices 09 44 30 spencerooni Le Vendor TEAC Model FD 05PUB Rev 2000 09 44 30 spencerooni Li Type Direct Access ANSI SCSI revision 02 09 44 30 spencerooni l Attached scsi removable disk sdc at scsil channel 0 id O spencerooni kernel sdc READ CAPACITY failed Spencerooni kernel sdc status 1 message 00 host 0 driver 08 spencerooni kernel Current sd00 00 sense key Not Ready spencerooni kernel Additional sense indicates Medium not present spencerooni kernel sdc block size assumed to be 512 bytes disk size 1GB spencerooni kernel sdc I O error dev 08 20 sector 0 spencerooni kernel I O error dev 08 20 sector 0 spencerooni kernel unable to read partition table Now that wouldn t be the end of the world necessarily However ANYTIME the KVM is switched on the Bladecenter to from that blade the USB stuff KVM and media tray get re hotplugged for lack of a better term and the sdc errors are generated They occur even after switch the media tray owner to a different blade The result is too many spurious errors which is making the internal support team cranky Modification 1 Do not boot blade with media tray assi
41. e 17 Remote Control Bitte 0 2B a ne eee nae eee m 16 Pints and TIDS T ien 9 m E ree ee eee 17 26 31 32 51 INN eara A 9 Firmware levels cccccccccssseeeceesseeeeeeeeeees 51 Mous SUPPO eese cup dsnp cda Eau viis cena 32 Updating firmware eeseeeesses 42 qoi 11 iomutil Nr r 44 Popup Blocker eseessssss 11 RICK STAT vcswensevseuieasxvceunedaweceulemsiciaentleasciedmedsenases 27 28 Sticky KEYS seciisaraiscopnetsawasetaisiiateecetieimeats 11 18 Management Module Repeating keystrokes 10 50 Boot ordei ee 18 Serial Over LAN SOL KVM Media Tray ownership 24 I WEA DN EEE E ETA TT 36 Power Restart cccccccsseeeeeeeeeeesaeseeeeeeeeeeees 25 LILO Remote control eee 10 16 boot MESSAQES ceccceeeeseeeseeeeeeeaeeeeees 36 Remote disk cccecceceeceececeeeeeeeeeeceeeeenes 24 26 kernel Selection 36 Management Module Failover 50 MO CORE um oases 36 Medid WAY T 31 Serial Over LAN SOL ssss 35 Mouse Tracking eeeeessseeees 32 SLES 9 Installation 34 aco nie 38 39 Startup Sequence See Boot sequence Network drivers cccccseeeeecseeeeesee
42. e Auto Logical Drive Transfer ADT AVT mode is not supported when using Linux in a cluster or when using RDAC Since ADT AVT is automatically enabled in the Linux storage partitioning host type It has to be disabled by selecting host type of LNXCL e AVT is required if you are using the Qlogic Failover drivers e The Linux SCSI layer does not support skipped sparse LUNs If the mapped LUNs are not contiguous the Linux kernel will not scan the rest of the LUNs Therefore the LUNs after the skipped LUN will not be available to the host server The LUNs should always be mapped using consecutive LUN numbers e Although the host server can have different FC HBAs from multiple vendors or different FC HBA models from the same vendors only one model of FC HBAs can be connected to the IBM DS4000 otorage Servers e fa host server has multiple HBA ports and each HBA port sees both controllers via an un zoned switch the Linux RDAC driver may return I O errors during controller failover e Linux SCSI device names have the possibility of changing when the host system reboots We recommend using a utility such as devlabel to create user defined device names that will map devices based on a unique identifier called a UUID The devlabel utility is available as part of the Red Hat Enterprise Linux 3 distribution or online at http www lerhaupt com devlabel devlabel html e Linux RDAC supports re scanning to recognize a newly mapped LUN without rebooting
43. e script created in step 1 copy driver diskette image from the root directory of the NFS share to the root directory on the target machine cp mnt source dd img mnt sysimage copy module update script from the root directory of the NFS share to the root directory on the target machine cp mnt source update modules sh mnt sysimage Execute the script in the chrooted environment chroot mnt sysimage update modules sh Version 3 0 3 10 2006 http w3 03 ibm com support techdocs atsmastr nsf W eblndex WP 100564 49 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 IBM BladeCenter Deployment Guide Appendix A Firmware Versions The following tables contain both the minimum versions required deploy on the BladeCenter and its various components and the current versions at the time this document was published Please visit the IBM support site for the most current firmware versions for all components www 306 ibm com pc support site wss document do lndocid MIGR 54597 There is also a URL for registering for proactive emails regarding firmware updates https www 1 ibm com support mysupport us en First time you visit select register After you have logged into the site select edit profile and add the servers t
44. eCenter Deployment Guide ls 2 4 9 e 40BOOT t ls 2 4 9 e 40BOOT tg3 0 e1000 0 tqg3 o el000 0 9 Remove device drivers that will not be utilized from the driver modules extracted to the first module directory in step 7 Since the BladeCenter HS20 and BladeCenter HS40 servers do not support 3Com 3c59x Intel 10 100 AMD PCnet32 or USB OHCI devices it is safe to remove the associated device drivers to free much needed space in the image cd modules boot cd 2 4 9 e 40BOOT 1s 2 4 9 e 40BOOT 2905903 10 bobo lockd scsi_mod o usb ohci o vfat o eeprol00 o input o nfs o Ssumnrpo o usb storage o Lato keybdev o pcnet32 0 usbcore o USb UhC1 20 i rm 3c59x 0 eeprol00 o pcnet52 0 usb ohcori o ls Iat o LpuLo lockd o Sosri modo usbCcore o usb ullBcbso hid o keybdev o nfs o Ssunrtpcso usb storage o vfat o 10 Copy the Broadcom NetXtreme Gigabit Ethernet Adapter and Intel Gigabit Ethernet Adapter drivers from the second module directory drvnet img modules module archive to the first module directory cp modules drv 2 4 9 e 40BOOT tg3 0 e1000 0 ls el1000 0 hid o keybdev o nfs o sunrpc o usbcore o usb uhcri o Ia3t o input o lockd o SCSI mod o tg3 o ush storage o vfat o cd 11 Recreate the modules archive from the first modules directory modules boot ls 2 4 9 e 40BOOT find type f grep v modules cpio cpio o H crc gt modules cpio 1481 blocks ls 2 4 9 e 40BOOT modules cpio
45. eaueeeeseaeeeessaeeeessageeessaeeeessesseessaeeees 28 Figure 33 Kickstart Modifications elles nennen nnne nennen nn nnns n nnns nana nnne 28 moUi EG Mie e ONDU easier m 29 mie Vir eereainilebuzuieni e 29 Figure 36 RPM Install of Broadcom Device Drivers eessseeeseseseeeeee nennen 30 FIgure 37 albsvsre TOM TALC CION socasorcoducs ame m px da bapU N qu NU C UCnU M DdG SON d JE 37 FIOM SSA Sy SC TOn HONE mr 38 Figure 39 Broadcom Se UI e sssini EEA EE EE EEEE 41 Fig re 40 OLodgie HBA Flashi aeu usura ee ene ne uua EEE eee eee eee 44 Version 3 0 3 10 2006 http w3 03 ibm com support techdocs atsmastr nsf Weblndex WP 100564 5 The BladeCenter Deployment Guide is intended as a personal productivity tool Itis 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 IBM BladeCenter Deployment Guide 1 Introduction 1 1 Overview The IBM BladeCenter Deployment Guide is intended to present the general steps necessary to successfully deploy IBM blades in the IBM server BladeCenter Its primary focus is to detail the steps required for setting up remote boot on IBM Blades The information provided in this document is based on technical observations Due to the breadth of content related to this topic this guide has now been split into 3 par
46. ed to LUN 0 Reboot the server setup is complete 5 2 Installing Broadcom NetXtreme Gigabit Ethernet device drivers Complete the following steps to install Broadcom NetXtreme Gigabit Ethernet device drivers 1 Insert the CD or diskette that contains the Broadcom NetXtreme Gigabit Ethernet device drivers into the appropriate drive The CD or diskette contains an InstallShield wizard that installs the device drivers for the device For information about downloading the Broadcom NetXtreme Gigabit Ethernet application see 2 0 Where to download device drivers and files NOTE Steps 2 through 5 can be skipped in this section if there will not be a need to extract files 40 However if the driver was downloaded from the IBM website the downloaded file must be extracted Select the application In the InstallShield wizard window select Next Enter the location of the folder where the files are to be saved Make note of this location for future reference Later you will need to point to this location when installing your device drivers Select Next The InstallShield wizard extracts the files needed to install all Broadcom Gigabit Ethernet device drivers on the blade server When InstallShield is finished select Next On the desktop right click My Computer and select Manage Select Device Manager The Broadcom NetXtreme Gigabit Ethernet device is detected automatically as an unknown device under Other Devices Right click one of the unkn
47. ed to a selectable value within the management module would recommend changing the telnet SOL timeout to no timeout Default is 120 seconds This can be changed via the web interface under MM Control gt Network Protocols Telnet Protocol or via the CLI system telnetcfg telnetcfg t lt secs gt Displays and configures the telnet settings for the MM t inactivity timeout in secs valid value from 0 to 4 294 967 295 seconds This command sets it to no timeout t 0 System telnetcfg t 0 T system mm 1 Although this says telnet config it works for both telnet and SOL 4 9 Netdump Netdump is a Red Hat specific crash dump facility Unlike traditional crash dump facilities this facility dumps memory images to a centralized server via the network More information on netdump can be found here http Awww redhat com support wpapers redhat netdump 38 http w3 03 ibm com support techdocs atsmastr nsf W ebIndex WP 100564 2006 IBM Version 3 0 3 10 2006 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 IBM BladeCenter Deployment Guide Here is the link to the instructions from Red Hat that can be used to set up netdump http Awww redhat com support wpapers redhat netdump setup html The netdump ser
48. eeeessaeaeeeeeeeesessaaasesss 12 Figure 9 Storage Connection Diagram cccccccccsssesssecceeeeceaeeeeeeeeeeseeeeeeeeeeeeeessuaaeeeeeeeessuaaseeeeeeseessaeageeeees 13 Fig re 10 POM Status ONNE T 13 Figure e gi eir I A OMNE sssr onnaa a aa EAER ea R a aeia 14 Figure 12 SANSurfer Switch Faceplate cccccccssssssecceeeeeeeeeeseeceeeeeeeeeeseseeeeeeeseaseeeeeeeesseaeaeeeeeeesssaaaaeses 14 Figure TS Porn Propers aniano teotan E eaei suetenimerdusinetsainencnaens 15 Figure 14 Disable the IDE Devices HS20 and HS40 cc ecccceccccccessceeeeeeeeeceeeceeseeeeeesseaeeesseeeeesaaeeeeeas 16 Fone To F A Heer UC CE T Em OTT OT 17 Figure 16 HS40 Boot Sequence ssssssssssssssssseseseneen nennen esnnnnai nnn rris EEEE AA ENERE ENS 17 Figure 17 Changing boot order from Management Module for HS20 cccceecceeeeeeeeeeeeeeeeeeeeeeeaeeeeeeeeas 18 Figure 18 Configuring the QLOGIC HBA ccccccccssssessseeceecceeeeeeceeeeesaeeesesseseceeeeeeeeeeesesaeaessseeeeeeeeeeeeeeeeenes 19 Figure 19 Host Adapter Settings cccccccccsseccccceeecseesseeceeeeeseeeesseeeeeeeseeesseeceeeeesseaeaseeeeeseessuaeaseeeeeesessaaasesss 19 Figure 20 Enable Selectable Boot Illustration 2lssseeeeeeeeeessseeeeeeeerrenenenennn nnne 20 Figure 2T Bootable EUN address uscito notice ott Ente E UM nt qi ae A AE EAE 20 POUE peer 3 e Uie zie I ERIT TT 21 Figure 23 Confirm the media is accessible
49. eo resolution d Toreload the mouse device driver module type insmod mousedev e Toreturn to GUI mode if necessary type init 5 2 Changing the pointer speed settings To enable the remote mouse to track properly in Red Hat Linux set the mouse acceleration and threshold values to 1 To change mouse acceleration and threshold values for the current session open a terminal window and type xset m 1 1 Complete the following steps to preserve these changes between sessions NOTE A remote mouse is not supported in the text console If you are using GNOME Press Ctrl Esc From the menu click Programs gt Settings gt Session gt Session properties gt Startup programs Click the Startup programs tab Click Add In the command line type xset m 1 1 and click OK Click Apply and OK to close the window Log out from the session and select Save current setup in the Log Out window The next time you log in the remote and local mouse are synchronized If you are using KDE 1 Using the keyboard press Alt F1 2 From the menu click Preferences gt Peripherals gt Mouse 3 Click the Advanced tab and change the Pointer Acceleration and Threshold values to 1 4 Click Apply and OK to close the window 5 Log out from the session and select Save current setup in the Log Out window The next time you log in the remote and local mouse are synchronized 3 Synchronizing the remote and local mouse for remote c
50. f the management module is 192 168 70 125 the default subnet mask is 255 255 255 0 and the default hostname is MMxxxxxxxxxxxx where xxxxxxxxxxxx is the burned in MAC address It is possible to connect directly into the management module by using a crossover cable between a laptop and the Ethernet port of the management module Change the ip address of the laptop to an address on the same subnet as the management module 192 168 70 124 is a good choice e The logon screen will display and you will be prompted to log onto the MM web server The default user ID and password are USERID and PASSWORD 0 is a zero These are case sensitive e Once you enter your user ID and password you will presented with a welcome window that displays where you are connected and for security purposes where you set the duration that your connection can be idle before being automatically disconnected e Click lt Continue gt The BladeCenter Management and Configuration window opens From the Management and Configuration program main menu select settings that you want to view or change 2 3 Remote Control Hints and Tips Note All of the subsequent tasks described in the document can be performed either from direct KVM connection at the BladeCenter or via the Management Module remote console In most cases instructions will be provided assuming access via the Management Module 1 Sun JVM Version 1 4 2 is the minimum required for remote control function The M
51. gned in order to avoid errors when someone takes the media tray away AND when the floppy drive is empty NOTE alias floppy off should be added to modules conf to avoid floppy drive errors when media tray not assigned on boot Version 3 0 3 10 2006 http w3 03 ibm com support techdocs atsmastr nsf W eblndex WP 100564 31 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 10 11 12 32 IBM BladeCenter Deployment Guide One final note on this item currently the media tray is required for installing Linux on the blades but should only be needed in rare circumstances after that Additionally since there appear to be several combinations of events that will cause the EFI shell boot option to be restored in the boot sequence on a blade see item 4 it is recommended that boot sequence be confirmed when an HS40 is rebooted until the firmware fix is released This can be done by simply confirming that the HS40 boots from the HBA during a restart So these items should be included as required steps for building a Linux blade Modification 2 Leave read only floppy diskette in the drive This prevents the Medium not present errors from occurring This is not a complete solution but is a good start See 3 for more Modific
52. hannel adapters can boot only from LUN numbers up to 15 so your boot LUN number must be in the range 0 to 15 Renumber the gatekeeper VCM LUN to 16 or higher and it won t interfere with the boot LUN To renumber the LUN either contact the vendor for assistance or consult your storage array management documentation 2 Changing the Boot Loader Configuration Another way to deal with the gatekeeper LUN is to specify in your boot configuration where to find the boot LUN This requires editing the etc lilo conf file Note If you have already completed the installation and you are unable to boot the server you should boot from a Linux rescue CD and mount the boot LUN so you can make the following changes 1 Backup the file etc lilo conf 2 Editthe file etc lilo conf 3 Find the line that says default esx 4 After the default line insert these two lines disk dev sdb bios 0x80 Use a tab to indent the second line Exit the editor saving your changes Run lilo 7 Reboot the server This time it should boot successfully from dev sdb Do 4 6 Other Linux Distributions and Blades We ve just begun our own testing with SLES 9 and Red Hat 4 on blades in a boot to SAN environment and we hope to add more material here in the future At this point the only new problem encountered was that our 8832 blade would not boot from the iso image of SLES9 mounted via the Management Module It would boot from the actual CDROM mounted remo
53. hat you would like receive notification on The tables in that appendix will also help translate between build ids and release versions You can see the current firmware levels from the management module All values current as of Feb 28 2006 9 Management Module P Minimum Reg Most Current 1 19H Release Date 2005 02 11 2005 12 22 Revision Main App BRET73H BRET82 Table 2 Management Module BIOS Information A minimum of BRET82A is highly recommended since it contains several important fixes 1 Repeating keystrokes fix 2 Gratuitous arp fix 3 Improved failover and firmware transfer handling HS20 BIOS Model 8832 O Dominum Reg Most Current 4 HS20ISMP 8832 Lo imum ies Most uen HS20 Diagnostics 8832 Minimum Req Most Current Release Date 2004 07 08 2004 1 1 09 Build Id BSYT15A BSYT16A Table 3 HS20 Model 8832 Firmware Information 50 http w3 03 ibm com support techdocs atsmastr nsf W ebIndex WP 100564 2006 IBM Version 3 0 3 10 2006 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 IBM BladeCenter Deployment Guide HS20 BIOS Model 8843 MinReq Most Current 4 HS20 BMC 8843 MiniumReg Most Current HS20 Diagnostics 8843 Mi
54. icrosoft JVM is not supported It may work some of the time but Remote Disk tends to act flaky with the MSJVM To check this in Internet Explorer go to Tools Options and then click on the Advanced tab Internet Options General Security Privacy Content Connections Programs Advanced Settings C Use Passive FTP for firewall and DSL modem compatibility Use smooth scrolling amp HTTP 1 1 settings Use HTTP 1 1 Use HTTP 1 1 through proxy connections amp Java Sun Use Java 2 v1 4 2 04 for lt applet gt requires restart E Microsoft VM Java console enabled requires restart Java logging enabled JIT compiler for virtual machine enabled requires restart 2H Multimedia C Dont display online media content in the media bar Enable Automatic Image Resizing Enable Image Toolbar requires restart Play animations in web pages Restore Defaults Figure 3 JVM Selection in IE Version 3 0 3 10 2006 http w3 03 ibm com support techdocs atsmastr nsf W eblndex WP 100564 9 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 IBM BladeCenter Deployment Guide 2 Repeating Keystrokes in order to remove the repeating keystroke problem you need to check the Disable key repeats box and click Save
55. images Perform the following steps for each Extract the diskette image to a real floppy disk then create a disk image file of the physical floppy disk using a program such as DSKIMAGE Save the images with easily identifiable names 3 Next upload the first BIOS diskette image to the Management Module See Figure 26 Remote Media via the Remote Console for an example of how to perform this Once the diskette image has been loaded restart the target blade The blade will boot to DOS You ll be asked several questions the default answers are acceptable After several minutes of reading erasing writing and verifying the update program will ask for the second BIOS diskette Unmount the media Figure 30 and then upload the second BIOS diskette to the management module After the upload completes return focus to the remote console window and hit enter 7 When the BIOS update completes it will ask you if you d like to reboot Before answering yes unmount the second BIOS diskette and upload the ISMP diskette Then ok the reboot 8 The ISMP diskette will boot to a DOS prompt At the DOS prompt enter LCREFLSH 9 When the ISMP update is finished you will be returned to a DOS prompt Unmount the remote disk and reboot 6 2 BMC Update for the HS20 8843 and LS20 BMC firmware update for the 8843 blade can be done either by using a bootable diskette image available from ibm com or remotely by using PKT files and applying them via the Man
56. in the 73G release of the Management Module firmware where the ct r1 or the alt keys become stuck on Clicking the icons on the toolbar twice should clear this state and may restore keyboard response 10 0 0 110 BladeCenter Remote Control Microsoft Internet Explorer H Change KVM Media Tray Owner Remote Disk Remote Console Blade4 ESX Blade2 dE s A a E ESA key ZG SCrver No Video Available Figure 6 Remote Control Window If during a Linux installation you see the message No Video Available shown in Figure 6 then most likely nofb was not specifying as a boot option See Section 4 3 for more information When switching from managing one chassis to another it is recommended that you close your browser after logging off from the first chassis especially if you were using Remote Control in the first session Otherwise you may encounter errors with the Remote Disk applet middle frame Figure 5 in the second session such as remotedrive dll is not accessible exception java lang NullPointerException Initialization error Library not installed Unsatisfied Link Error Applet com ibm asm remotedisk RemoteDisk not inited Version 3 0 3 10 2006 http w3 03 ibm com support techdocs atsmastr nsf W eblndex WP 100564 11 The BladeCenter Deployment Guide is intended as a personal productivity tool It is not intended to be comprehensive and is provi
57. in with the name of a removed device driver 3c59x eepro100 pcnet32 usb ohci For example 3c59x eth 3Com 3c590 3c595 3c90x 3cx980 eepro1l00 eth Intel EtherExpress Pro 100B pcnet32 eth AMD PCnet32 Remove driver entries from the modules dep file that are associated with the device drivers removed in step 9 Remove all lines that make reference to the removed device drivers 3c59x eepro100 pcnet32 usb ohci cat modules dep grep v 3c59x grep v eeprol100 grep v pcnet32 grep v usb ochi gt modules dep new mv modules dep new modules dep Add driver entries present in the drvnet img pcitable to the initrd img pcitable file that are associated with the device drivers added in step 10 All entries in the pcitable file must be sorted by PCI ID cat mnt drv pcitable grep tg3 gt gt pcitable cat mnt drv pcitable grep e1000 gt gt pcitable At this point use an editor or sort script to sort the pcitable information by PCI ID Add driver entries present in the drvnet img module info file to the module info file that are associated with the device drivers added in step 10 For blades we ll be adding the tg3 and e1000 entries which should look something like this e1000 eth Intel EtherExpress 1000 gigabit coe eth Broadcom Tigon3 ethernet driver Add driver entries present in the drvnet img modules dep file to the modules dep file that are associated with the device drivers added i
58. ion and Configuration 2 Preparatory Steps The BladeCenter Chassis components should be prepared by updating the firmware and assigning the appropriate IP addresses to the management and switch modules The IP addresses of the various modules as well as the userids and passwords for each will be needed during the installation A sample worksheet can be found in 1 Appendix A The operating systems that are supported in BladeCenter boot from SAN configurations are Linux RedHat Advanced Server 2 1 3 0 and 4 0 Microsoft Windows 2000 W2K Advanced Server Microsoft Windows 2000 Server Microsoft Windows 2003 WS03 Enterprise Edition Web Edition and Server Note Since the storage subsystem provides multiple paths to the server multiple views of the same logical disk will be presented Multipathing software controls these multiple views by interposing between the operating system and the hardware Since the multipathing software is not available for the initial boot only one path may be presented to the server for the initial boot This process is described in detail later in this document 2 1 Network Configuration The two switch modules provide redundant paths to each of the server blades for reaching other server blades within the same chassis or for communication to external devices via the network infrastructure Figure 2 BladeCenter internal network The Ethernet switch modules can be managed via telnet or a Web interface Both the
59. ite 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 Indocid MIGR 4381 5 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 Broadcom Management Pragrams Setup Select Featuiret Choore the lesbie Setup val nall Tele We Features vou want to intel end clear Wve Features vou do noc wait ko instal p Control Sulle excrplian The component wil install tha OENHP Brosdcom Advanced Sereer CIM Provider HEE Space Required an C 124 04 E Space Avalabla on C 450504 K 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
60. ix lt d sc rpmlib CompressedFileNames lt 3 0 4 1 Requires post bin sh Requires preun bin sh Requires postun bin sh Requires Loe29pnux S02 l305605 5050 bin sh libc so 6 GLIBC_2 0 l1506 89 6 GLlBOC 2 1 Jobe so 6 GHEBC 2 1 3 Wrote usr src redhat RPMS i386 basplnx 6 2 1 1 1386 rpm Executing Sclean bin sh e var tmp rpm tmp 3526 root localhost redhat rpm ivh RPMS i1386 basplnx 6 2 1 1 1386 rpm Preparing FHHHHHHE EE EH EEE EEE HEH HH HH HE EH TE EEE EEE EEE EEE 1003 1 basplnx FHT EHE FH HT HE FEE FH FHF HF EE EH SF tHE EEE 1005 root localhost redhat Figure 35 RPM Install of Broadcom Device Drivers 4 5 Issues related to Red Hat AS 2 1 3 0 and blades 1 The firmware for HS40 blades MUST be updated to the minimum levels shown in Table 5 HS40 BIOS and ISMP Information if the blade is going to be running Linux There is a problem identified in the 1 32 version of the BIOS related to EFI which causes processors to be disabled The only fix for this error is to upgrade the BIOS and ISMP firmware 2 Installing Red Hat by booting from remote CDs is not currently supported on the HS40 Installing the 30 http w3 03 ibm com support techdocs atsmastr nsf W eblndex W P 100564 2006 IBM Version 3 0 3 10 2006 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 an
61. le LUN address 20 2006 IBM Version 3 0 3 10 2006 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 IBM BladeCenter Deployment Guide Logic FasttUTIL Version 1 25 Adapter Type I Address Configuration settings modified Figure 21 Save your changes Critical Note At this point only one boot path is configured During the INITIAL Operating System build only one boot path should be active After the initial OS build a secondary path can be added if this is supported by the storage vendor 3 2 3 Testing the path to the boot LUN The path to the LUN that the server will be booting from can be tested at this point e Select verify disk media e Once the boot media is verified save changes and exit aqu Pee MU E em T ISI SE Adapter Type 1 1 Rddrsezsz Selected Device LUM Wendor Product Rev Port Home Port Ib i asy T 4 PRAE EEN PERIE na nag opto Low level Format Uerifu Dish Data Select Different Disk dise lt firrow keys to move cursor Enter to select option Esc to backup Figure 22 Confirm the media is accessible Version 3 0 3 10 2006 http w3 03 ibm com support techdocs atsmastr nsf W eblndex WP 100564 21 The BladeCenter Deployment Guide is intended as a personal produ
62. ll kernel vmlinuz append ks file ks cfg text initrd initrd img lang devfs nomount ramdisk size 7108 The kickstart config file will have some blade specific entries mouse generic3usb device input mice Sample partition statements clearpart all part boot fstype ext3 size 128 ondisk sda asprimary part fstype ext3 size 20000 grow ondisk sda part swap size 2048 maxsize 2048 ondisk sda 4 3 Multipath Red Hat Installation While it is possible to install RHAS2 1 with both paths enabled using the standard partitioning statements in the kickstart configuration file this approach does not work with Version 3 0 The installation will complete and Linux will begin to boot but you will eventually witness the following error Version 3 0 3 10 2006 http w3 03 ibm com support techdocs atsmastr nsf W eblndex WP 100564 27 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 IBM BladeCenter Deployment Guide p zm E H bringup ioch 53C1H3H Capabilities iInitiator t mptbase 1 MPT adapter found 1 installed Loading mptscsih o module Fusion MPT SCSI Host driver 2 06 16 scsi ioch LSISSC1030 FwRev 01000e00h Ports 1 Max 222 IRU 28 blk queue f 3be218 70 limit 4294967295Mb mask UkKTfffTfTTfIfTfT
63. ll or upgrade Red Hat Enterprise Linux in graphical mode press the lt EHTER gt key Io install or upgrade Red Hat Enterprise Linux in text node type linux text lt EHTER gt Use the function keys listed below for nore infornation LFi1 Hainl CF2 Options EF3 benerall LIFd Kernell LF5 Rescue tii linux nofh Figure 29 linux nofb 6 Important When the installation is complete unmount the diskette drive before the reboot Remote Disk On Card Figure 30 Unmount the Diskette Image 7 When loading Linux on an HS40 after unmounting the diskette it is possible that EFI may replace the IBM Remote Disk in the boot order and the blade may boot into EFI instead of Linux If this occurs follow the steps shown on page 17 to reorder the boot sequence 8 Depending on your kickstart file configuration the network interface adapters may not be configured during install However you should reference your OS installation guide to configure your respective network interface adapters 9 Apply the recommended errata and driver updates If this includes a kernel update you will need to compile new drivers to comply with the new kernel Note When building the new kernel and driver image please add a new option to the lilo conf file so that you can revert back to the installed kernel if there were problems with the new driver 10 Power down the blade server 11 Once the OS has been installed you can re enable the port for
64. mote Control or the serial console SOL The existing documentation refers to these options as being able to monitor the boot via SOL or being able to interact with the boot via SOL If you are using LILO complete the following steps 1 Complete the following steps to modify the etc lilo conf file a Add the following text to the end of the first default linux line Monitor b Comment out the message z boot message line by adding a at the beginning of this line This disables the graphical LILO boot screen since it will not display correctly in the SOL session The next time the blade is booted the text LILO prompt appears in place of the graphical boot screen c Increase the timeout value to give the operator a better chance to choose which way the blade boots d Add the following line before the first image line This will allow you to only Monitor the OS boot via SOL e Add the following text to the end of the first label linux line Monitor f Add the following line to the first image section This enables SOL append console ttyS1 19200n8 console ttyl g Add the following lines between the two image sections This will allow you to Interact with the OS boot via SOL image boot vmlinuz 2 4 21 37 ELsmp label linux Interact initrd boot initrd 2 4 21 37 ELsmp img read only root dev hda6 append console ttyl console ttyS1 19200n8 2 Run the lilo command to store and activate the LILO configuration sbin lilo v
65. mporary directories mkdir tmp mnt mkdir tmp modules 5 mount o loop S IMAGE FILE tmp mnt 9 5 cd tmp modules Tf ftmp mnt 2 5 modules ogz then echo malformed driver diskette image SIMAGE FILE exit 1 48 http w3 03 ibm com support techdocs atsmastr nsf W ebIndex W P 100564 2006 IBM Version 3 0 3 10 2006 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 IBM BladeCenter Deployment Guide I3 gunzlip e fltmp ummntelo mooules ogx cpio ad tor moduleDir in do for moduleFile in find SmoduleDir name 0o0 do if d lib modules moduleDir then targetModuleFiles find lib modules SmoduleDir name moduleFile if StargetModuleFiles J then cp SmoduleFile lib modules SmoduleDir kernel else for targetModuleFile in targetModuleFiles do cp moduleFile StargetModuleFile done Tn t update module dependencies SDEPMOD a SmoduleDir Rr done done cd SCWD umount tmp mnt clean up rm rf tmp modules 95 rm rf tmp mnt Run chmod x update modules sh to mark it executable Add the following text with appropriate changes to reflect the names of the files you created to the post section of the kickstart file in order to facilitate execution of th
66. n step 10 Copy the files copied and modified in steps 12 18 to the mounted initrd img image cp module info pcitable modules cgz modules dep mnt initrd modules Unmount the initrd img from the loopback device cd ss umount mnt initrd Compress the initrd img file gzip 9 tmp img mv tmp img gz initrd img Version 3 0 3 10 2006 http w3 03 ibm com support techdocs atsmastr nsf W eblndex WP 100564 47 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 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 deployments 8 1 Modify or Create the Post install Driver Diskette Image 1 Create the supplemental driver disk containing drivers that will be used in the post install environment Up to this point we have only been concerned with the drivers that will be used during installation the BOOT environment to access storage and network devices Since we are only updating the ServeRAID drivers in this example this step is easy we simply make the driver diskette image file 26k4970 img available to the Red Hat installer by pla
67. na nnn rss n narrans 22 4 Installation Process for Red Hat Linux lsseeeseesseseeseeeeeeeee nnne nnne 24 4 1 Red Hat Advanced Server 2 1 3 0 Installation cccccccccssssssececeeeeseeeeeeeeeeeeseeeeeeeeeeeeessaaaaeees 24 4 2 Kickstart IMOMAT P NT TTE E Ea EET 27 4 3 Multipath Red Hat Installation lseseeseeessesesseeseeeeeerneneeenn nnns 27 4 4 Red Hat Linux AS Broadcom driver installation cccccsscsecccesseeeeeecseeeeceeeeeeeseeeseeaaeseeessaaess 29 4 5 Issues related to Red Hat AS 2 1 3 0 and blades eeeeeeeeeeeeeeene 30 4 6 Other Linux Distributions and Blades sessi nennen nnne 34 4 7 RDAC Installation and Configuration ssseeeesesesseeeeeee nnne 35 4 8 Serial Over LAN SOL for Blades ssssessssssssssseeeennnene nennen nennen nnne n nnn nnns 35 4 8 1 Gu p E 35 4 8 2 Summary of Linux changes for SOL sseessssssssssseeee eene 36 4 8 3 c icio MNT TT T mU UU 37 4 9 pisei 38 5 Install Process for Windows 2000 and 2003 Remote Boot cccccccceccseeeeecneeeeeeseeeeeeeeeeeeenaeeees 40 5 1 Operating Syst m InstallauOF usui ha doc deste eec oeaiei iai etude e aloaia 40 5 2 Installing Broadcom NetXtreme Gigabit Ethernet device drivers
68. nce only on an as is basis without warranty of any kind Please be aware that its contents have not been certified by IBM IBM BladeCenter Deployment Guide There are several well written white papers available that describe the steps required to configure Serial Over LAN for the BladeCenter The firmware sections of these documents can be skipped as long as you have followed the firmware recommendations in this document For Linux you must make the changes to both etc inittab and your boot loader configuration file either lilo conf or grub conf in order to get the full functionality under Linux 4 8 2 Summary of Linux changes for SOL 1 Add the following line to the end of the Run gettys in standard runlevels section of the etc inittab file This enables hardware flow control and enables users to log in through the SOL console 7 2345 respawn sbin agetty h ttyS1 19200 vt102 2 Add the following line at the bottom of the etc securetty file to enable a user to log in as the root user through the SOL console ttysl 3 LILO configuration In order to enable SOL in Linux we need to add 2 parms to the kernel line in the bootloader configuration file console ttyS1 19200n8 console ttyl The order of these two parms affects where a portion of the Linux boot and shutdown messages are displayed and consequently how the Linux boot can be managed Basically your two options are having the messages go to the main console the one you see via Re
69. ndex WP 100564 37 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 IBM BladeCenter Deployment Guide E 10 0 0 110 PuTTY y Move Size Minimize Hu LEID Ru 1 uz Maximize X Close Alt F4 Special Command Are You There Event Log Synch New Session Erase Character Duplicate Session Erase Line Saved Sessions Go Ahead Change Settings No Operation Copy All to Clipboard Abort Process Clear Scrollback Abort Output Reset Terminal Interrupt Process Suspend Process Full Screen End Of Record Hein End Of File About PuTTY rakernermevesrmpm 5 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 circumstances the serial data of the 8843 Blade Server may stop flowing This results in a blank SOL session with only a blinking cursor When this occurs simply press the control and q keys Ctrl q at the same time This key sequence will allow the flow of serial data to resume Notes Telnet sessions with the BladeCenter management module have a default timeout value of 120 seconds This means the telnet session will remain active indefinitely This value may be customiz
70. ng the command 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 QLogic USERID gt admin start QLogic admin USERID gt set port 4 state offline QLogic admin USERID gt show port Admin Operational Login Config Running Port Status Ext1 Online Online LoggedIn Active 1Gb s Ext2 Online Offline NotLoggedIn Unknown Inactive Auto Bayl Online Online LoggedIn F Active 2Gb s Bay2 Online Offline NotLoggedIn Unknown Inactive 2Gb s Bay3 Online Offline NotLoggedIn Unknown Inactive 2Gb s Bay4 Offline Offline NotLoggedIn Unknown Inactive 2Gb s Bay5 Online Offline NotLoggedIn Unknown Inactive 2Gb s Bay6 Online Offline NotLoggedIn Unknown Inactive 2Gb s Figure 10 Port Status Offline 2 4 2 2 Using SANSurfer GUI 1 Start the SANSurfer GUI If the fabric has not already been discovered click Fabric Add Fabric and enter the IP address of the target QLogic switch in the window that will pop up That should open SAN Browser 2 Click the handle in the left pane to drop down the switch highlight it and the faceplate will appear in the right pane SANsurfer Switch Manager Faceplate File Fabric Switch Port Zoning Wizards View Help Fi e id amp m c B Add Open Save Refresh Events Zoning Help QLogic 9 glogic Normal QLogic ERR ORR BEEBE First Port Address 010000 iWorld Wide Name i1 0 00 00 c0 dd
71. nimum Req Most Current Table 4 HS20 Model 8843 Firmware Information HS40 BIOS P Minimum Req Most Current Note While version 1 44 is the minimum required version 1 56 fixes the EFI boot order problem referenced in Item 4 in Section 4 5 and is therefore highly recommended HS40ISMP P MinmumReg Most Current BRMK29A 2005 05 24 Table 5 HS40 BIOS and ISMP Information LS20 BIOS Minimum Reg Most Current i 05 a Build Date LS20 BMC Minimum Req Most Current Version 3 0 3 10 2006 http w3 03 ibm com support techdocs atsmastr nsf W eblndex WP 100564 51 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 IBM BladeCenter Deployment Guide Release Date 2005 12 22 2005 12 22 Build Id BKBT414C BKBT414C Table 6 LS20 BIOS and BMC Information 4 QLogic HBA Firmware See 7 Flash the QLogic HBA BIOS for instructions on how to update the HBA BIOS Version 4 Table 7 QLogic Firmware Information Note we are now recommending v1 43 for the QLogic BIOS Old minimum was v1 38 52 http w3 03 ibm com support techdocs atsmastr nsf W ebIndex WP 100564 2006 IBM Version 3 0 3 10 2006 The BladeCenter Deployment Guide is intended as a personal productivity tool It is
72. 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 IBM BladeCenter Deployment Guide Appendix B Worksheets BladeCenter Information BladeCenter Location User ID for BladeCenter Modules Password for BladeCenter Modules BladeCenter Components Firmware Level IP Address Management Module S Management Module S Ethernet Switch Modulet o0 Ethernet SwitchModule2 Jo ooo o0 Fibre Channel Switch Modulet 000 oo Fibre Channel Switch Module2 oo ooo Blade Configuration Information Hostname IP Address Operating System System Adapter WWID HDC HDC HDC HDC HDC Name Name WWID WWID WWID 1 Version 3 0 3 10 2006 http w3 03 ibm com support techdocs atsmastr nsf W eblndex W P 100564 53 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 IBM BladeCenter Deployment Guide Index z ec 37 Flash the BIOS eeeessssss 44 anacdondaettOESasesetoonietueticateaesum Su bed vertido 32 Reset Default Settings 44 Boot sequence seaeesmaskekesercebal unu tuve VE De E a EYE 16 Testing boot
73. ntroller This enhancement allows the operating system to use of the keyboard controller IRQ for other devices This error message has no negative impact to the system and can be ignored http www 1 ibm com support docview wss uid psg1MIGR 57605 Linux experiences kernel panics or hangs during boot of 8843 blades Hang typically happens when reaching net4 frame diverter after real time clock driver Fix is to add the usb handoff kernel directive within the bootloader configuration file This is intended to resolve a problem with rather than eliminate usb Here is a summary of the usb issue When the BIOS is configured with legacy USB support enabled it can generate a system management interrupt SMI during the boot sequence The BIOS routine which handles that action clobbers a CPU register That understandably is a bad thing as the Linux kernel does not expect its data to be randomly changed by asynchronous events like that SMI Whether or not the corruption is catastrophic depends on the exact timing of events down to the microsecond That s why sometimes the bootup is successful If you suffer major path problems LIPs or controller panics it can hang the server indefinitely as the system attempts to find a stable path 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 Mouse suppor
74. ontrol sessions If the remote and local mouse are not synchronized correctly that is if there is a constant offset between them on the remote client window move the mouse toward the bottom of the monitor screen in the remote client window Then move the local mouse back in the window This will correct the alignment between the mice 4 Correcting mouse cursor click related issues NOTE The blade server might not start in GUI mode if the mouse is not detected when the blade server is turned on This might happen if the blade server is not associated with the keyboard monitor and mouse If there is no mouse cursor or if single clicks from the remote mouse do not work complete the following steps to correct the problem 1 Open a terminal window 2 Type setup 3 Click Mouse Configuration 4 Scroll down and select the generic or two button USB mouse Click OK 5 Click Yes to update X Configuration NOOR WD Version 3 0 3 10 2006 http w3 03 ibm com support techdocs atsmastr nsf W eblndex WP 100564 33 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 IBM BladeCenter Deployment Guide 6 Exit the utility 7 Press Ctrl Alt Backspace The next time you log in to the X Window System the remote mouse will work c
75. orrectly 13 Boot from SAN fails with Gatekeeper LUN on EMC backed storage When installing in a boot from SAN configuration on an EMC Symmetrix storage array the following message appears The partition table on device sda was unreachable To create new partitions it must be initialized Or after rebooting you simply see a blinking cursor This happens because the Symmetrix uses LUN O0 as a gatekeeper LUN which is marked as a pseudo device The Linux installer maps LUN 0 to dev sda When the installer tries to configure the boot LUN it is unable to use dev sda so it uses dev sdb instead This leads to a problem with identifying the boot loader There are two possible solutions to this problem One solution is to mask or renumber the LUN of the gatekeeper the other is to change the boot loader configuration 1 Masking or Renumbering the Gatekeeper VCM LUN To boot from SAN ESX Server requires that the boot LUN be the lowest numbered LUN in the storage array To accomplish this you may follow one of two approaches in order of preference e To prevent the installer from attempting to write to this device EMC recommends masking the LUN 1 Initialize the Volume Logix database using the administrative host 2 Modify the active configuration file to enable the foa flag2 This restricts access to the Volume Logix database e The gatekeeper VCM LUN can be assigned a number higher than the boot LUN number Current Fibre C
76. own Ethernet devices Select Properties gt Reinstall Driver In the Welcome to Upgrade Device Driver Wizard window select Next Select Search for a suitable driver for my device and select Next From the Optional Search Location menu select Specify a location and select Next http w3 03 ibm com support techdocs atsmastr nsf W ebIndex WP 100564 2006 IBM Version 3 0 3 10 2006 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 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 Su
77. rmation ccccccssssecceeeeeseeeeeceeeseceeeeeseeeeeteeseceeeseeaeeeeeesaeaeeeees 50 Table 3 HS20 Model 8832 Firmware Information sees 50 Table 4 HS20 Model 8843 Firmware Information ccccesceceeseecesseeteeeeceneeeeeeeceneeeeeeetaeseeteneeetsneeenens 51 Table 5 HS40 BIOS and ISMP Information ccccccceeecccecceeseeceeeeesseeeeeeaeseceeeeeeeseceeeeeeegeceseeaueeeesesaasaneees 51 Table 6 LS20 BIOS and BMC Information lsseeeesssssesseeeeneneennennnnnnne nnnm nnne nnns 52 Table 7 QLogic Firmware Information sssseeeeessssssseeeeee enne nennen nnn nnns nnns 52 Table of Figures Figure 1 BladeCenter Chassis Rear View ssseessessssssssseeeee nennen nnne nnnnnn nnn nnne nnne n ann nnns 7 Figure 2 BladeCenter internal network ccccccccccsseeseecceeececaeeeeeeeeeeesaueeeeeeeeeeeseaeaseseeeeeessasaaaeeseeeessaeaaaaesss 8 Figure Sal VM Selecion im mE o E Eo STE 9 Figure 4 Disable Key TODOS aso gases a a ace deneedases a eaeedewest 10 Figure 5 KVM and Media Ownership cccccccccccseeseseceeeeeceeeeeeeceeeeeeeaeseeeeeeeeseeaesseeceeeeesseaaseeeeeeesssaaagesss 10 Figure 6 Remote Control Window ccccceccccceeeeeeesseeeeeeeeseeeeeeeceeeesseeeseeeeeeeeseeaeaeeeeeeeeesssaasseeeeeeessaeaaaeees 11 Figure 7 Logoff and Close the Browser M SSaQG G ccccccccseeeeceeeeecaeeeeeeeceeeeeeaueeueec
78. ry BIOS If these steps are performed after Linux has been installed it is advisable to confirm that the blade reboots back to Linux and not into EFI Version 3 0 3 10 2006 http w3 03 ibm com support techdocs atsmastr nsf W eblndex WP 100564 43 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 7 IBM BladeCenter Deployment Guide Flash the QLogic HBA BIOS Perform the following steps to flash the QLogic HBA BIOS 1 Create a blank bootable disk formatted with MS DOS PC DOS or DR DOS 2 Using a text editor verify that the config sys and autoexec bat files are blank and contain no entries 3 Insert the disk created in step 1 in an appropriate drive Double click the archive icon then type the following in the Unzip to folder field to extract the contents of the BIOS files archived to the disk ask 4 Insert the disk from step 3 into the drive mounted on the target blade and boot from the disk 5 Atthe a prompt type ibmutil i f then press ENTER This will update the BIOS for both channels of the expansion card in the system 6 Ifthe QLogic HBA is detected the following lines display Current version of the QLA2312 flash BIOS at I O Address 2400 is 1 38 New version of the QLA2312 flash BIOS at I O Address 2400
79. s necessary to support the NICs on a blade server are not part of a standard Windows 2000 2003 install and the NICs will be generically listed in Windows 2000 Device Manager as two or more Ethernet Controllers until the necessary drivers are loaded For these NICs to become active a third party driver supplied by IBM needs to be installed The normal procedure most users follow is to install the drivers on the first Ethernet Controller in the list and then install the drivers on the second Ethernet Controller in the list and so on The end result of this is the most cases scenario previously mentioned where the Windows 2000 2003 connection named Local Area Connection goes to switch 1 and the one named Local Area Connection 2 goes to switch 2 22 http w3 03 ibm com support techdocs atsmastr nsf W ebIndex WP 100564 2006 IBM Version 3 0 3 10 2006 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 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 names are reversed and the connection named Local Area Connection is now the one going to switch 2 and the connection named Local Area Connection
80. seeeesseeeeseaees 8 Unexpected DLL version error 12 IV OL OO P u 27 Windows Installation QLogic HBA Device Drivers eeeeeeeeeeeeee 40 Cle U 18 EAP ONS ceseesp ii nrR UD IXbI EF Est RON ERN RE 41 Firmware levels ess 52 Worksheets ccccccccseeeeceeeeceseeseeeeeseeeeesaeeees 53 54 http w3 03 ibm com support techdocs atsmastr nsf Weblndex WP 100564 2006 IBM Version 3 0 3 10 2006 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
81. status of the ports Operational Login Config Running Link Status Type Type State LoggedIn 1Gb s Online Offline NotLoggedIn Unknown Inactive Auto Online Online LoggedIn F Active 2Gb s Online Offline NotLoggedIn Online Offline NotLoggedIn Unknown Inactive 2Gb s Unknown Inactive 2Gb s Online Online LoggedIn F Active 2Gb s Online Offline NotLoggedIn Unknown Inactive 2Gb s Online Offline N Online Offline Online Offline Online Offline tLoggedIn Unknown Inactive 2Gb s lotLoggedIn Unknown Inactive 2Gb s lotLoggedIn Unknown Inactive 2Gb s lotLoggedIn Unknown Inactive 2Gb s Unknown Inactive 2Gb s Online Offline Online Offline Online Offline Online Offline lotLoggedIn Unknown Inactive 2Gb s Unknown Inactive 2Gb s tive 2Gb s Unknown Inactive 2Gb s lot LoggedIn lot LoggedIn Unknown Inac F F F F F F F F F F F F F F O O O O Online Offline lotLoggedIn O O O O lot LoggedIn Figure 9 Port Status Online Version 3 0 3 10 2006 http w3 03 ibm com support techdocs atsmastr nsf W eblndex WP 100564 13 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 IBM BladeCenter Deployment Guide 3 Enter admin mode by entering admin start 4 Disable the target port by enteri
82. t for the BladeCenter unit The ability of the remote console applet to accurately track the location of the mouse cursor in a Linux X Window System session depends on the configuration of the X Window System Complete the http w3 03 ibm com support techdocs atsmastr nsf W ebIndex WP 100564 2006 IBM Version 3 0 3 10 2006 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 IBM BladeCenter Deployment Guide procedures in the following sections to configure Red Hat Linux and the X Window System for accurate mouse tracking Type the commands through the remote console or at the keyboard that is attached to the BladeCenter unit 1 Providing resolution information to the mouse handler The mouse handler mousedev must have the correct resolution information to track the remote mouse cursor correctly If the host blade server resolution is not 1024 x 768 complete the following steps to provide the correct resolution data to the mouse handler a f you need to switch to text mode type init 3 b To unload the mouse device driver module type rmmod mousedev c To notify the mouse device driver of the video resolution add the following line to the etc modules conf file options mousedev xres x yres y where x and y are the vid
83. t root mount dev sda mnt floppy root localhost root ls al mnt floppy botal 299 rwxr xr x 1 root root 279997 Jan 20 06 basplnx 6 2 1 1 9r 0 12596 rpm root localhost root root localhost root cp mnt floppy basplnx 6 2 1 1 src i386 rpm tmp root localhost root root localhost root ed tmp root localhost tmp rpm ivh basplnx 6 2 1 1 src i386 rpm l basplnx FHFHETEEE Et ETE E HE THEE EE TEETH EEE 1005 root localhost tmp root localhost tmp cd usr src redhat root localhost redhat root localhost redhat rpmbuild bb SPECS basplnx spec Executing prep bin sh e var tmp rpm tmp 4397 Executing build bin sh e var tmp rpm tmp 4397 qoc DLINUX D KERNEL DMODUDLDLE I lib modules 2 4 9 e 24smp build inoclude Wall Wstriot prototypes 02 o blf o gcc DLINUX RERNEID DMODULE I lib modules 2 4 9 e 24smp build include Wall Wstrict prototypes O2 c pal c ld r o basp o blf o pal o blfcore o Executing install bin sh e var tmp rpm tmp 67022 Processing files basplnx 6 2 1 1 Executing doc bin sh e var tmp rpm tmp 6067022 Finding Provides using usr lib rpm tfind provides s Finding Requires using ust lib rpm find reguires PreReq bin sh bin sh bin sh rpmlib PayloadFilesHavePrefix lt 4 0 1 rpmlib CompressedFileNames lt 3 0 4 1 Requires interp bin sh bin sh bin sh Requires rpmlib rpmlib PayloadFilesHavePref
84. tely and the install 34 http w3 03 ibm com support techdocs atsmastr nsf W eblndex WP 100564 2006 IBM Version 3 0 3 10 2006 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 IBM BladeCenter Deployment Guide If you are installing SLES9 to a local drive on an HS20 watch out for this RETAIN tip http www 1 ibm com support docview wss uid psg1MIGH 57844 4 7 RDAC Installation and Configuration Notes on Linux There are two versions of the Linux RDAC The version 09 00 A5 09 for Linux 2 4 kernels only like Redhat EL 3 and SuSe SLES 8 and RDAC package version 09 01 B5 XX for Linux 2 6 kernel environment e Make sure you read the README TXT files for V9 15 Linux RDAC HBA and Storage Manager for Linux e When using the Linux RDAC as the failover failback driver the host type should be set to LNXCL instead of Linux If Linux RDAC is not used the host type of Linux must be used instead e There is not a requirement that the UTM Access LUN must be removed from the LNXCL Storage Partitioning partition e The Linux RDAC driver cannot co exist with a HBA level multi path failover failback driver such as the 6 06 63 fo driver You might have to modify the driver make file for it to be compiled in the non failover mode
85. the server The utility program is packed with the Linux RDAC driver It can be invoked by using either hot add or mppBusRescan command note that hot add is a symbolic link to mppBusRescan There are man pages for both commands However the Linux RDAC driver doesn t support LUN deletion One has to reboot the server after deleting the mapped logical drives 4 8 Serial Over LAN SOL for Blades 4 8 1 Overview The Management Module command line interface provides access to the text console command prompt on each blade server through a Serial over LAN SOL connection enabling the blade servers to be managed from a remote location To start an SOL connection with a blade server you must first start a telnet or ssh session with the management module When this session is running you can start a remote console SOL session with any blade server in the BladeCenter unit that is set up and enabled for SOL operation You can establish up to 20 separate Telnet sessions with a BladeCenter management module For a BladeCenter unit this enables you to have 14 simultaneous SOL sessions active one for each of up to 14 blade servers with 6 additional command line interface sessions available for BladeCenter unit management Version 3 0 3 10 2006 http w3 03 ibm com support techdocs atsmastr nsf W eblndex WP 100564 35 The BladeCenter Deployment Guide is intended as a personal productivity tool It is not intended to be comprehensive and is provided for guida
86. tray and KVM selections are for the target blade 4 Enter the Blade BIOS by pressing F1 or clicking the F1 button at the appropriate time during POST 3 1 1 Disabling IDE devices Since the BladeCenter servers will boot to drives located on the SAN the locally attached drives will not be used To boot to the Qlogic HBAs the local IDE controllers for the IBM BladeCenter should be disabled To disable the IDE devices in the Blade Server BIOS use the following steps from within the BIOS setup program 1 Select Devices and IO ports from the main menu 2 Select IDE configuration menu Select Disable to disable the Primary and Secondary IDE controllers Note in some instances you may see the following error 19990303 No Boot device found If you encounter this error then spin up delay should be enabled on the HBA See Section 3 2 Configuring the Qlogic HBA for details IM Setup c Copyright IBM Corporation 2002 Configuration Setup Utility OnBoard PCI IDE Controller Disabled Primary IDE Channe Master Device lat Drei Secondary IDE Channel D astcr DCUIC IDE Configuration Menu r Syster MAC Addresse Figure 13 Disable the IDE Devices HS20 and HS40 3 1 2 Check the Boot Order e From main BIOS screen access Start Options then Startup Sequence to access the boot order and insure the devices are listed in the following order Device Startup Order CD Rom First Startup Device Diskette Drive 0 Second Startup Devi
87. ts 1 Management Module information specific to the initial setup and ongoing usage of the Management Module 2 Embedded Switches information related to the configuration of the embedded Ethernet and Fibre channel switches 3 Blades blade configuration and installation information with a primary focus of installing Linux in a boot to SAN environment Remote boot root boot or boot from SAN is the name referred to the server configuration where the server operating system is installed on a logical drive LUN that does not reside inside the server chassis This document will describe in detail the process that one must go through to setup a remote boot for HS20 or HS40 blade servers The blade servers utilize the IBM BladeCenter Fibre Channel Expansion Card connected to the BladeCenter Fibre Channel Switch Modules via the BladeCenter backplane The switch modules in turn are connected to the core fibre channel switches that host the SAN Fabric This document is a supplement the IBM server BladeCenter publications provided with the BladeCenter products In addition to the publications being provided with the BladeCenter products they also are available in Portable Document Format PDF The latest versions of the publications are available from the IBM web site at http www ibm com pc support BladeCenter publications include the following e IBM server BladeCenter Type 8677 Planning and Installation Guide This manual
88. ver from the RHELSUS distribution is version 0 6 11 3 Basically here is what needs to be done at the server 1 rpm i netdump server 0 6 11 3 1386 rom 2 passwd netdump 3 chkconfig netdump server on 4 service netdump server start And at the client 1 netdump client package probably already installed 2 service netdump propagate 3 modify etc sysconfig netdump Add line NETDUMPADDR 10 0 0 26 4 chkconfig netdump on 5 service netdump start Note there have been instances reported where there have been dependency issues between netdump and openssh Here are the openssh packages that are installed on our test blade root katherini tmp rpm qa grep ssh openssh olients 3 6 1p2 5233 20 1 oOpenssne 3 5 1p2 225 20 441 openssh server 3 6 1p2 33 30 1 Version 3 0 3 10 2006 http w3 03 ibm com support techdocs atsmastr nsf W eblndex WP 100564 39 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 2 IBM BladeCenter Deployment Guide Install Process for Windows 2000 and 2003 Remote Boot 5 1 Operating System Installation 1 9 c e B I eS 11 12 13 14 15 16 Obtain the Fibre Daughter card device driver specified by your storage vendor to support the use of the Qlogic HBA with their storage Take the
89. video and mouse interfaces and an onboard service processor e Management Modules incorporate the chassis level management processor and Keyboard Video Mouse KVM access for the blades e Switch Modules provide multiple high speed Ethernet ports in Switch Module slots 1 and 2 for use by all of the Server Blades to interconnect internally as well as to external network devices Switch 6 http w3 03 ibm com support techdocs atsmastr nsf W ebIndex WP 100564 2006 IBM Version 3 0 3 10 2006 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 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 e Power Four modular power supplies provide primary and backup power to all BladeCenter subsystems Power supplies 1 and 2 are responsible for powering blade 1 through 6 plus all of the BladeCenter components such as the switches management modules media tray etc and power supplies 3 and 4 are responsible for power blades 7 through 14 e Cooling Dual modular blowers provide forced air cooling of BladeCenter components and subsystems e Media Tray Removable media subsystem that is shared by all blades Includes CD DVD
90. y kind Please be aware that its contents have not been certified by IBM IBM BladeCenter Deployment Guide HS40 from the local media tray will work but it is recommended that the lowres option be used for the installation of AS2 1 When booting from the remote floppy the Jowres for RHAS2 1 or the nofb for RHAS3 0 install mode should function correctly There have been intermittent instances of no keyboard response When loading Linux on an HS40 after unmounting the diskette it is possible that EFI may replace the IBM Remote Disk in the boot order and the blade may boot into EFI instead of Linux There is also a problem referenced in RETAIN tip H1822293 that results in the HS40 boot order being reordered http www 1 ibm com support docview wss uid psg1MIGR 56325 If this occurs follow the steps shown on page 17 to reorder the boot sequence When a blade boots and the media tray is assigned to during boot up the floppy drive in the media tray is assigned as in this example dev sdc However since there is no diskette in the drive we see the following errors beginning at READ CAPACITY FAILED Nov 5 09 44 30 spencerooni kernel c new USB device 00 0f 2 1 1 assigned address 3 Nov 5 09 44 30 spencerooni kernel c USB device 3 vend prod 0x644 0x0 is not claimed by any active driver Nov 5 09 44 30 spencerooni kernel c new USB device 00 0f 2 1 3 assigned address 4 Nov 5 09 44 30 spencerooni kernel c USB
91. y selecting Removable Drive A or by selecting Select File and specifying a diskette image file Select one from the left list box then click on the gt gt Figure 26 After clicking the gt gt you ll see the dialog shown in Figure 27 BladeCenter Remote Control Microsoft Internet Explorer Change KVM Media Tray Owner Change KVM owner P Remote Disk Ne418ICMCOQ0008 gt Change media tray owner None Write Protect rive F Remote Console Blade SNi418ICMCO0008 4S 007 usiogkey v Et DAR Tab LI Insert 0a Figure 26 Remote Media via the Remote Console 24 htto w3 03 ibm com support techdocs atsmastr nsf W eblndex WP 100564 2006 IBM Version 3 0 3 10 2006 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 IBM BladeCenter Deployment Guide Remote Disk On Card Figure 27 Loading the Remote Diskette c Power on or restart the target blade BladeCenter Management M Bay 1 WMN315735129 Blade Power Restart e Monitors system Status Event Log Click the checkboxes in the first col LEDs table to perform the desired action Hardware VPD Firmware VPD Name Blade Tasks Om Demand 5 SN418ICMCOOL Remote Control

Download Pdf Manuals

Related Search

Related Contents

第1章 大型給湯器  Paul BISSON - Cercle d`Archeologie  GYPS-U004A - 産業用鉛蓄電池｜株式会社 GSユアサ  EX623 English User`s Manual  Samsung Электрическая варочная  Manuel de référence  Opal-RT + ML60x User Guide.backup.book  Le Moniteur d`Issoire 1882-10-25 page 02  

Copyright © All rights reserved. Failed to retrieve file