1. Manuals
  2. Brands
  3. IBM Manuals
  4. Server
  5. BladeCenter JS20
  6. Maintenance and troubleshooting manual

IBM JS20 - BladeCenter - 8842 Maintenance And Troubleshooting Manual

Hardware maintenance manual
Hide thumbs Also See for JS20 - BladeCenter - 8842:
Table of Contents

Advertisement

Quick Links

Download this manual See also: Installer and User Manual
BladeCenter JS20
Type 8842
Hardware Maintenance Manual and

Troubleshooting Guide

Advertisement

Table of Contents
loading

Related Manuals for IBM JS20 - BladeCenter - 8842

Summary of Contents for IBM JS20 - BladeCenter - 8842

  • Page 1: Troubleshooting Guide

    BladeCenter JS20 Type 8842 Hardware Maintenance Manual and Troubleshooting Guide...
  • Page 3 BladeCenter JS20 Type 8842 Hardware Maintenance Manual and Troubleshooting Guide...
  • Page 4 Before using this information and the product it supports, read Appendix B, “Safety information,” on page 163 and “Notices” on page 197 v The most recent version of this document is available at http://www.ibm.com/pc/support/. 16th Edition (June 2006) © Copyright International Business Machines Corporation 2003. All rights reserved.

  • Page 5: About This Manual

    About this manual This manual contains diagnostic information, a symptom-to-FRU index, service ® information, error codes, error messages, and configuration information for the IBM ® BladeCenter JS20 Type 8842 blade server. Important safety information Be sure to read all caution and danger statements in this book before performing any of the instructions;...
  • Page 6 BladeCenter JS20 Type 8842: Hardware Maintenance Manual and Troubleshooting Guide...

  • Page 7: Table Of Contents

    Related documentation ..... . 3 The IBM BladeCenter Documentation CD ....4 Hardware and software requirements .
  • Page 8 Service aids and the Linux system error log ... . . 40 FRU/CRU isolation ..... . . 46 Error symptom charts .
  • Page 9 Removing the blade server bezel assembly ....75 Installing IDE hard disk drives ....75 Installing memory modules .
  • Page 10 Before you call ......161 Using the documentation ..... 161 Getting help and information from the World Wide Web .

  • Page 11: Chapter 1. Introduction

    Chapter 1. Introduction The IBM BladeCenter JS20 Type 8842, also known as the blade server, is based ™ on the IBM Power Architecture technologies. The BladeCenter JS20 Type 8842 is compatible with IBM BladeCenter units. This high-performance blade server is well-suited for networking environments that require outstanding microprocessor performance, efficient memory management, flexibility, and reliable data storage.
  • Page 12 BladeCenter unit supports varies by the wattage of the power modules that are installed in the BladeCenter unit. For more information about determining the power requirements for the blade server, see the IBM Eserver BladeCenter Power Module Upgrade Guidelines Technical Update on the World Wide Web at http://www.ibm.com/support/.

  • Page 13: Related Documentation

    This Hardware Maintenance Manual and Troubleshooting Guide is provided in Portable Document Format (PDF) on the IBM BladeCenter JS20 Documentation CD that comes with the IBM BladeCenter JS20 Type 8842. It contains information to help you solve problems yourself or to provide helpful information to a service technician.

  • Page 14: The Ibm Bladecenter Documentation Cd

    Nortel Networks Layer 2-7 GbE Switch Module for IBM Eserver BladeCenter and a description of the switch-module features. v IBM BladeCenter 2-Port Fibre Channel Switch Module Installation Guide: This document contains instructions for setting up, installing, and configuring the IBM Eserver BladeCenter 2-Port Fibre Channel Switch Module, and a description of the switch module features.

  • Page 15: Notices And Statements Used In This Document

    Notices and statements used in this document The caution and danger statements that appear in this document are also in the multilingual Safety Information document, which is on the IBM BladeCenter unit or blade server Documentation CD. Each statement is numbered for reference to the corresponding statement in the Safety Information document.

  • Page 16: Features And Specifications

    Note: Power, cooling, removable-media drives, external ports, and advanced system management are provided by the IBM Eserver BladeCenter unit. For more information, see the Installation and User’s Guide for your BladeCenter unit.

  • Page 17: Bladecenter Js20 Specifications For Nebs/Etsi Environments

    Microprocessor: Size: Environment (NEBS): v Air temperature: ® v Two IBM Power PC v Height: 24.5 cm (9.7 inches) – Blade server on: 5° to 40°C (41° microprocessors with 512 KB ECC v Depth: 44.6 cm (17.6 inches) to 104°F). Altitude: -60 to 1800 m L2 cache v Width: 2.9 cm (1.14 inches)
  • Page 18 2. BladeCenter JS20 models that are designed for the NEBS environment contain a power-management capability that provides the maximum possible operating time for your system. Power management is invoked only when the blade server is installed in a BladeCenter T unit and only under the short term extended thermal conditions that are described in the preceding table as "short term"...

  • Page 19: Preinstallation Checklist

    I/O bay 1 of the BladeCenter unit. __ d. Configure the BladeCenter unit for SOL operation as described in the IBM Eserver BladeCenter and BladeCenter T Serial Over LAN Setup Guide. Verify that the firmware code for the BladeCenter unit, management module, and Ethernet switch modules supports the SOL feature.

  • Page 20: Checking The Status Of The Media Tray

    __ a. The hardware and firmware in the BladeCenter unit are at the supported levels for the blade server. Go to the IBM Support Web site, http://www.ibm.com/support/, for additional information. __ b. The BladeCenter unit has the correct customer interface card (CIC) (see “Checking the status of the media tray”).
  • Page 21 To have the CIC replaced, call the IBM Support Center and report the CIC as a failed part and request replacement with the latest CIC field replaceable unit (FRU). Chapter 1. Introduction...
  • Page 22 BladeCenter JS20 Type 8842: Hardware Maintenance Manual and Troubleshooting Guide...

  • Page 23: Chapter 2. Blade Server Power, Controls, And Indicators

    To disable the Wake on LAN feature for one or more blade servers, use the BladeCenter management-module Web interface. For more information about the BladeCenter management-module Web interface, see the BladeCenter and BladeCenter T Management Module User’s Guide on the IBM BladeCenter Documentation CD. v Throughout this document, the management-module Web-based user interface is also known as the BladeCenter management-module Web interface.

  • Page 24: Turning Off The Blade Server

    Turning off the blade server When you turn off the blade server, it is still connected to power through the BladeCenter unit. The blade server can respond to requests from the service processor, such as a remote request to turn on the blade server. To remove all power from the blade server, you must remove it from the BladeCenter unit.
  • Page 25 Power control button Notes: 1. The blade-error LED, information LED, and location LED can be turned off through the BladeCenter management-module Web interface. 2. For additional information about errors, see “Light path diagnostics” on page 46. 3. This blade server does not have a keyboard/mouse/video select button. CD/diskette/USB select button Blade-error...
  • Page 26 Activity LED: When this green LED is lit, it indicates that there is hard disk drive or network activity. Power-on LED: This green LED indicates the power status of the blade server in the following manner: v Flashing rapidly – The service processor on the blade server is communicating with the BladeCenter management module.

  • Page 27: Chapter 3. Configuration

    IBM Eserver BladeCenter and BladeCenter T Management Module Command-Line Interface Reference Guide Other documents on the IBM BladeCenter Documentation CD that you might find useful in the configuration process are: v IBM 4-Port Gb Ethernet Switch Module for BladeCenter Installation and User’s...

  • Page 28: Using The Command-Line Interface

    BladeCenter unit. The command-line interface also provides access to the text-console command prompt for the blade server through an SOL connection. See the IBM Eserver BladeCenter and BladeCenter T Management Module Command Line Interface Reference Guide on the IBM BladeCenter Documentation CD for information and instructions.

  • Page 29: Blade Server Ethernet Controller Enumeration

    traffic switches back to the primary Ethernet controller port. (See the operating-system device driver documentation for information about configuring for failover.) Important: To support failover on the blade server Ethernet controller, the Ethernet switch modules in the BladeCenter unit must have identical configurations to each other.
  • Page 30 BladeCenter JS20 Type 8842: Hardware Maintenance Manual and Troubleshooting Guide...

  • Page 31: Chapter 4. Problem Determination Procedures For Aix And Linux

    1. Turn off the server, making sure to first turn off all external devices, if attached. 2. Check all cables and power cords. 3. Turn on all external devices; then, turn on the blade server. © Copyright IBM Corp. 2003...

  • Page 32: Obtaining An Srn/Src Or Error Code

    4. Start the Serial Over Lan (SOL) console for the blade server to be tested and check for the following responses: a. Progress codes are displayed on the console. b. AIX or Linux login prompt appears. Step 003 Record any error messages or codes that are displayed on the screen.
  • Page 33 Step 005 Perform the following procedure for problem determination. Note: When possible, run AIX Online Diagnostics in Concurrent Mode. AIX Online diagnostics perform additional functions, compared to standalone diagnostics CD. 1. Perform the AIX online concurrent mode diagnostics for Problem Determination, see “Performing AIX online concurrent mode diagnostics for problem determination”...
  • Page 34 Step 008 Load the Standalone Diagnostics in Service Mode. Refer to “Running the standalone diagnostics from CD-ROM” on page 25 or “Running standalone diagnostics from a management (NIM) server” on page 68. Can you load the standalone diagnostics? Go to “Undetermined problems” on page 156. If you still have a problem then Call to get additional support.

  • Page 35: Chapter 5. Aix Online, Standalone And Verification Procedures

    Before attempting to load standalone CD diagnostic, make sure you are at the latest firmware level (xx.xx) before continuing. Step 003 Log in to the management module. Step 004 Enable SOL for the JS20 Blade to be tested. © Copyright IBM Corp. 2003...
  • Page 36 Step 005 Select CD-ROM as the first device to be booted from the configuration menu boot sequence. Step 006 On the operator panel on the blade to be tested, press the CD button to assign the CD-ROM to the blade to be tested; then, insert the diagnostic CD into the CD drive.
  • Page 37 not function. In this case, use the F# function keys or press Esc and the number in the screen menus. For example, for PF3 you can press F3 or you can press the Esc key and the #3 key. Step 010 v Select Diagnostic Routine and, if attempting to run diagnostics in Problem Determination, go to Step 011 .

  • Page 38: Performing Aix Online Concurrent Mode Diagnostics For Previous Diagnostic Results: Service Aids

    3. When the task is completed, press F3 or the Esc and #3 keys to return to the Task Select screen. 4. If you want to run another task, select the task to be performed. From the Task Selection list, select the service aid task you want to perform;...

  • Page 39: Performing Aix Online Concurrent Mode Diagnostics For System Verification

    IDENTIFIER: DATE Date/Time: Fri Jul 16 04:06:09 Sequence Number: 287 Event type: SRN Callout Resource Name: sysplanar0 Resource Description: System Planar Location: 00-00 Diag Session: 12736 Test Mode: No Console,Non-Advanced,Normal IPL,ELA,Option Checkout Error Log Sequence Number: Error Log Identifier: BFE4C025 SRN: 2B276422 Description:...

  • Page 40: Verifying The Replacement Part Using Aix Diagnostics

    7. If any SRNs or firmware error codes are displayed, record all information provided from the diagnostic results, go to the “SRN tables” on page 110 or “Firmware error codes” on page 102. If ″No trouble found″ is displayed, continue to the next step. 8.
  • Page 41 (such as USB CD-ROM or diskette drive) are assigned to the JS20 blade against which you are running diag -. Follow the prompts to resolve the resource conflict. See“Missing resources” on page 60 for more information. If an 8-digit error code is displayed, go to “Firmware error codes”...
  • Page 42 resource associated with that repair action. If the resource associated with your action does not appear on the resource list, select ″sysplanar0″ and press Enter. b. After you have made your selections, choose F7 Commit. Did another Resource Repair Action display appear? If RA Complete appears, press Enter for the NTF screen.

  • Page 43: Chapter 6. Running A Serial Over Lan Session

    SOL console redirect session with a blade server. The most recent versions of all BladeCenter documentation are available from the IBM Web site. Complete the following steps to check for updated BladeCenter documentation and technical updates: 1. Go to http://www.ibm.com/support/.

  • Page 44: Selecting The Command Target

    JS20 Installation and User’s Guide on the IBM BladeCenter Documentation CD. Also, see the documentation for the operating system for information about commands that you can enter through an SOL connection. See the IBM Eserver BladeCenter and BladeCenter T Management Module Command Line Interface...

  • Page 45: Establishing A Telnet Connection

    Starting an SOL session Notes: 1. The SOL feature must be enabled for both the BladeCenter unit and the blade server before you can start an SOL session with the blade server. See the IBM Chapter 6. Running a Serial Over LAN session...

  • Page 46: Ending An Sol Session

    Additional information about setting up and enabling SOL, and configuring a blade server for SOL, is available in the BladeCenter JS20 Installation and User’s Guide on the IBM BladeCenter Documentation CD. 2. The BladeCenter management module automatically stores the previous 8 KB of serial data that was transmitted by each blade server, even when SOL sessions are not active.

  • Page 47: Chapter 7. Diagnostics

    Web site: http://techsupport.services.ibm.com/server/lopdiags/. Diagnostic utilities for the Linux operating system are available from IBM. For more information, go to http://www.ibm.com/servers/eservers/support/bladecenter/; in the Hardware field select BladeCenter JS20, in the Software field select Linux on POWER environment, then click Go.

  • Page 48: Checkout Procedure

    Note: If your system will not start, you can use the “Running the standalone diagnostics from CD-ROM” on page 25 procedure to isolate a hard disk drive failure that may be preventing the system from starting. v If your operating system is Linux, then you have the eSever Standalone Diagnostics CD available to check out your hardware.

  • Page 49: Diagnostic Tools Overview

    1. If a firmware checkpoint (progress) (3 or 4-digit) code or firmware error (8-digit) code is displayed on the console, see “Firmware checkpoint (progress) codes” on page 94 or “Firmware error codes” on page 102. 2. Check the BladeCenter management module event log and if the operating system is Linux, check the Linux Syslog (platform log).

  • Page 50: Post

    Note: The service processor runs on its own power boundary and continually monitors hardware attributes and the environmental conditions within the system. The service processor is controlled by firmware and does not require the operating system to be operational to perform its tasks. POST After power is turned on and before the operating system is loaded, the system does a power-on self-test (POST).
  • Page 51 With the toolkit installed, problem determination and correction is greatly enhanced and the likelihood of an extended system outage is reduced. The Linux service aids for hardware diagnostics are separate from the operating system installation and are available for download from the following Web site: http://techsupport.services.ibm.com/server/lopdiags/.
  • Page 52 Aug 13 09:38:45 larry diagela: 08/13/2003 09:38:44 Aug 13 09:38:45 larry diagela: Automatic Error Log Analysis has detected a problem. Aug 13 09:38:45 larry diagela: Aug 13 09:38:45 larry diagela: The Service Request Number(s)/Probable Cause(s) Aug 13 09:38:45 larry diagela: (causes are listed in descending order of probability): Aug 13 09:38:45 larry diagela: Aug 13 09:38:45 larry diagela: 651-880: The CEC or SPCN reported an error.
  • Page 53 Aug 27 12:16:33 larry kernel: RTAS: 15 -------- RTAS event begin -------- Aug 27 12:16:33 larry kernel: RTAS 0: 04440040 000003f8 96008508 19155800 Aug 27 12:16:33 larry kernel: RTAS 1: 20030827 00000001 20000000 00000000 Aug 27 12:16:33 larry kernel: RTAS 2: 00000000 00000000 00000000 00000000 Aug 27 12:16:33 larry kernel: RTAS 3: 49424d00 55302e31 2d463400 00503034 Aug 27 12:16:33 larry kernel: RTAS 4: 10117661 04a0005d 10110000 00000000 Aug 27 12:16:33 larry kernel: RTAS 5: 00007701 000000e0 00000003 000000e3...
  • Page 54 The number after the colon is a sequence number that correlates this data with any diagela data with the same sequence number. The end of the extended data is marked by the line Aug 27 12:16:33 larry kernel: RTAS: 15 ----- RTAS event end ------- with the same sequence number.
  • Page 55 RTAS daemon started RTAS: -------- event-scan begin -------- RTAS: Location Code: U0.1-P1-C2 RTAS: Log Debug: 04 4b2726fb04a00011702c0014000000000000000000000000f1800001001801d3ffffffff0100000 00000000042343138 20202020383030343236464238454134303030303 030303030303030 RTAS: Log Debug: D2 5046413405020d0a000001000271400100000033434d502044415441000001000000000000010000 f180000153595320444154410000000000000000200216271501050920021627150105092002063 7150105095352432044415441702c001400000000000000020018820201d3820000000000000000 0000000000000000000000000000000000000000000000000000000000000000000000000000000 00000000000000000000000000280048ea400000000000000000000000000000000000000004350 542044415441702cff08000000001c000000702cf0080000000080000000702cf100702cf200702 c000400000800702c01040bf2002e702c02040c1fffbf702c0300702c1000702c11040bf2002e70 2c12040c1fffbf702c1300702ca000702ca108000000000000a03c702ca208000000000000effc7 02cb000702cb108000000000000a03c702cb208000000000000effc702cc000702cc10800000000 0000a03c702cc208000000000000effc702c3000702c31080000000000000003702c32080000000 00000007b702c8000702c81080000000020e27a39702c820800000000fffeffff702cd000702cd1 080000000010004010702cd208000000007777f3fffffffffffffffffffffffffffffffffffffff fffffffffffffffffffffffffff RTAS: WARNING: (FULLY RECOVERED) type: INTERN_DEV_FAIL RTAS: initiator: UNKNOWN target: UNKNOWN RTAS: Status: unrecoverable new RTAS: Date/Time: 20020905 15372200...

  • Page 56: Fru/Cru Isolation

    If you cannot find the problem in the error symptom charts, go to “Checkout procedure” on page 38 and “Undetermined problems” on page 156. If you encounter problems with an Ethernet or Fibre Channel switch module, IBM Eserver BladeCenter Optical Pass-Thru Module, I/O expansion card, or other...

  • Page 57: Memory Errors

    DIMM 3 error DIMM 2 error LED (CR46) LED (CR45) DIMM 1 error DIMM 4 error LED (CR40) LED (CR53) Microprocessor 1 error LED (CR58) Service processor error LED (CR27) NMI error Microprocessor 0 LED (CR17) error LED (CR19) System board error LED (CR20) Temperature Reserved (CR29)

  • Page 58: Recovering The System Firmware Code

    This service aid toolkit provides the key tools required to take advantage of the inherent pSeries hardware RAS functions as outlined in the Linux on pSeries RAS White paper available from http://techsupport.services.ibm.com/server/ Linux_on_pSeries/images/Linux_RAS.pdf. These functions include first failure data capture and error log analysis. With the toolkit installed, problem determination and correction is greatly enhanced and the likelihood of an extended system outage is reduced.

  • Page 59: Recovering The Temp Image From The Perm Image

    2. If you have not installed the ppc64 Linux utilities, perform the installation now. For instructions, go to the Linux on POWER Web site at http:// techsupport.services.ibm.com/server/lopdiags/. 3. Reject the TEMP image. If you are using the Red Hat Linux or SUSE LINUX operating system, type...

  • Page 60: Updating The Blade Server Firmware

    Information on how to validate, update and commit the system firmware is included. The blade server contains firmware code for the system and service processor. IBM will periodically make firmware updates available for the server system and the service processor. You can maintain the latest levels of firmware code for the blade...

  • Page 61: Determination Of Current Server Firmware Levels

    If these two types of information differ, download the latest firmware code from the IBM Support Web site. Follow the update instructions on the IBM Support Web site.

  • Page 62: Verifying The System Firmware Levels Using Linux

    Do not power off the system while performing this task! Complete the following steps: 1. Obtain the flash image you want to update from the IBM Support Web site at http://www.ibm.com/support/ (look for the flash image for Type 8842, under ″AIX Diagnostics Version Number″, this is the version used by the AIX diagnostics...

  • Page 63: Committing The Temporary Firmware Image Using Aix

    3. From the ″Function Selection″ menu, choose ″Task Selection″. 4. From the ″Tasks Selection List″ choose ″Update and Manage System Flash″. 5. From the ″Update and Manage System Flash″ list: v If, in Step 1 above, you have put the image in the /etc/microcode file system, then choose the ″File System″...

  • Page 64: Recovering The System Firmware Code

    (see“Determination of current server firmware levels” on page 51). Cross reference information is given in the firmware information (“Blade Server Firmware - IBM BladeCenter JS20”) on the IBM Support Web site at http://www.ibm.com/support/, as well as in the README file for the firmware image.

  • Page 65: Recovery Of System Firmware Code Using Service Aids

    This service aid toolkit provides the key tools required to take advantage of the inherent pSeries hardware RAS functions as outlined in the Linux on pSeries RAS Whitepaper available from http://techsupport.services.ibm.com/server/ Linux_on_pSeries/images/Linux_RAS.pdfsuch as first failure data capture and error log analysis. With the toolkit installed, problem determination and correction is greatly enhanced and the likelihood of an extended system outage is reduced.

  • Page 66: Recovering The Primary Image

    AIX, begin with Step 002 . Step 001 Complete the following steps: 1. If you have not installed the ppc64 Linux utilities, perform the installation now. See http://techsupport.services.ibm.com/server/ lopdiags/. 2. Reject the primary image. From the command line, type update_flash -r then, go to Step 003 .
  • Page 67 BladeCenter unit. Step 006 Restart the blade server. Note: You might need to update the firmware code to the latest version. See http://www.ibm.com/pc/support for more information about how to update the firmware code. Statement 21 CAUTION: Hazardous energy is present when the blade server is connected to the power source.
  • Page 68 BladeCenter JS20 Type 8842: Hardware Maintenance Manual and Troubleshooting Guide...

  • Page 69: Chapter 8. General Aix And Xseries Standalone Diagnostic Information

    CE login must have a role of Run Diagnostics and a primary group of System. This enables the user to: v Run the diagnostics including the service aids, certify, format, and so forth. © Copyright IBM Corp. 2003...

  • Page 70: Missing Resources

    v Run all the operating system commands run by system group users. v Configure and unconfigure devices that are not busy. In addition, CE login can have Shutdown Group enabled to allow: v Use of the Update System Microcode service aid. v Use of shutdown and reboot operations.

  • Page 71: Diagnostic Programs

    Diagnostic programs This section provides an overview of the various diagnostic programs. The diagnostic controller runs as an application program on the AIX operating system and carries out the following functions: v Displays diagnostic menus v Checks availability of needed resources v Checks error log entries under certain conditions v Loads diagnostic application programs v Loads task and service aid programs...

  • Page 72: Introducing Tasks And Service Aids

    Introducing tasks and service aids The AIX diagnostic package contains programs that are called Tasks. Tasks can be thought of as performing a specific function on a resource; for example, running diagnostics or performing a service aid on a resource. This chapter describes the tasks available in AIX Diagnostics version 5.2 and later.

  • Page 73: Error Log Analysis

    If the error should be analyzed, a diagnostic application is invoked and the error is analyzed. No testing is done if the diagnostics determine that the error requires a service action. Instead, it sends a message to your console, or to all system groups.

  • Page 74: Download Microcode

    v Backup and Restore Media v Certify Media v Change Hardware Vital Product Data v Configure Reboot Policy v Configure Surveillance Policy v Delete Resource from Resource List v Disk Maintenance v Display Configuration and Resource List v Display Firmware Device Node Information v Display Hardware Error Report v Display Hardware Vital Product Data v Display Machine Check Error Log...

  • Page 75: Update And Manage System Flash

    For many adapters and devices, microcode installation occurs and becomes effective while the adapters and devices are in use. It is recommended that a current backup be available and the installation be scheduled during a non-peak production period. Notes: 1. If the source is /etc/microcode, the image must be stored in the /etc/microcode directory on the system.
  • Page 76 that you want to download be put into the /etc/microcode directory on the system. If there is not enough space in the /var file system for the new flash update image file, an error is reported. If this error occurs, exit the service aid, increase the size of the /var file system, and retry the service aid.

  • Page 77: Using The Standalone Cd-Rom And Online Current Diagnostics

    Flag Description Commits the temporary flash image when booted from the temporary image. This overwrites the permanent image with the temporary image. Rejects the temporary image when booted from the permanent image. This overwrites the temporary image with the permanent image. Using the standalone CD-ROM and online current diagnostics The diagnostics consist of standalone diagnostics and online diagnostics.

  • Page 78: Running The Online Diagnostics In Concurrent Mode

    v Under some conditions the system may stop, with instructions displayed on attached displays and terminals. Follow the instructions to select a console display. Running the online diagnostics in concurrent mode Use concurrent mode to run online diagnostics on some of the system resources while the system is running normal system activity.

  • Page 79: Nim Server Configuration

    All operations to configure the NIM server require root authority. 4. If you replace the network adapter in the client, the network adapter hardware address for the client must be updated on the NIM server. 5. The Control state (Cstate) for standalone clients on the NIM server should be kept in the Diagnostic Boot has been Enabled state.
  • Page 80 4. If the system is running in a full-machine partition, turn on the system unit power. Restart the AIX operating system in the system you wish to run online diagnostics. 5. Enter any requested passwords. 6. Select Utilities. 7. Depending on the console type, select [was ″RIPL or Remote Initial Program Load Setup″].

  • Page 81: Chapter 9. Installing Options

    Read the information in “Preinstallation checklist” on page 9. v Back up all important data before you make changes to disk drives. v For a list of supported options for the blade server, go to http://www.ibm.com/pc/ us/compat/. v Before you remove a hot-swap blade server from the BladeCenter unit, you must shut down the operating system by typing shutdown -h now.
  • Page 82 v Limit your movement. Movement can cause static electricity to build up around you. v Handle the device carefully, holding it by its edges or its frame. v Do not touch solder joints, pins, or exposed printed circuitry. v Do not leave the device where others can handle and damage it. v While the device is still in its static-protective package, touch it to any unpainted metal surface of the BladeCenter chassis or any unpainted metal surface on any other grounded rack component in the rack in which you are installing the device...

  • Page 83: Removing The Blade Server From The Bladecenter Unit

    Removing the blade server from the BladeCenter unit The following illustration shows an example of how to remove the blade server from a typical BladeCenter unit; the orientation of the blade server depends on the type of BladeCenter unit you have. Note: The illustrations in this document might differ slightly from your hardware.

  • Page 84: Opening The Blade Server Cover

    Opening the blade server cover The following illustration shows how to open the cover on the blade server. Cover pins Blade-cover release (blue) Blade-cover release (blue) Complete the following steps to open the blade server cover: 1. Read “Important safety information” on page iii and “Installation guidelines” on page 71 2.

  • Page 85: Removing The Blade Server Bezel Assembly

    Removing the blade server bezel assembly Before you can replace a defective system-board assembly or blade-server bezel assembly, you must first remove the blade-server bezel assembly. The following illustration shows how to remove the bezel assembly from a blade server. Bezel-assembly release Bezel-assembly...
  • Page 86 IDE drive Tray Riser card IDE connector 2 (J2) Short screws IDE connector 1 (J1) Attention: v Drives must be installed in the following order: IDE connector 1 (J1) first, then IDE connector 2 (J2). v Do not install a hard disk drive in IDE connector 2 if you intend to also install an optional I/O expansion card.

  • Page 87: Installing Memory Modules

    (SDRAM) with error correcting code (ECC) DIMMs. For a current list of supported DIMMs for the blade server, go to http://www.ibm.com/pc/us/compat/. v Install DIMMs in a matched pair. Each pair must be the same size, speed, type, and technology.
  • Page 88 Before you begin, read the documentation that comes with the option. BladeCenter JS20 Type 8842: Hardware Maintenance Manual and Troubleshooting Guide...

  • Page 89: Installing An I/O Expansion Card

    Complete the following steps to install a DIMM: 1. Read the safety information beginning on page iii and “Installation guidelines” on page 71 2. If the blade server is operating, shut down the operating system by typing the shutdown -h now command. Refer to your operating system documentation. If the blade server was not turned off, press the power-control button (behind the blade-server control-panel door) to turn off the blade server.
  • Page 90 You cannot install a hard disk drive in IDE connector 2 while an I/O expansion card is installed in the blade server. v The Myrinet Cluster Expansion Card for IBM Eserver BladeCenter comes with a cable for connection to the system board of a compatible device. However, the cable is not used in the BladeCenter JS20 Type 8842.
  • Page 91 The following illustration shows how to install an I/O expansion card on the blade server. The card is installed near IDE connector 2. IBM I/O expansion card I/O expansion tray I/O expansion card connector Raised hook Short screws I/O expansion card...

  • Page 92: Ethernet Controller, Switch Module, And Cabling Requirements

    For more information about installing, configuring, and using the Ethernet switch modules, see the documentation that comes with the Ethernet switch module that you are using, such as the IBM 4-Port Gb Ethernet Switch Module for BladeCenter Installation and User’s Guide or Nortel Networks Layer 2-7 GbE Switch Module for IBM BladeCenter Installation Guide.

  • Page 93: Replacing The Battery

    Replacing the battery IBM has designed this product with your safety in mind. The lithium battery must be handled correctly to avoid possible danger. If you replace the battery, you must adhere to the following instructions. Note: In the U. S., call 1-800-IBM-4333 for information about battery disposal.
  • Page 94 Complete the following steps to replace the battery: 1. Read the safety information beginning on page iii and “Installation guidelines” on page 71 2. Follow any special handling and installation instructions that come with the battery. 3. If the blade server is operating, shut down the operating system by typing the shutdown -h now command.
  • Page 95 8. Remove the battery: a. Use your finger to press down on one side of the battery; then, slide the battery out from its socket. The spring mechanism will push the battery out toward you as you slide it from the socket. Note: You might need to lift the battery clip slightly with your fingernail to make it easier to slide the battery.

  • Page 96: System Board

    To obtain a new system board, you must order a new blade server. The replacement system board comes attached to the new blade server. To order a blade server, contact your IBM authorized reseller or IBM marketing representative. Important: After you replace the system board, you must either update the new blade server with the latest firmware or restore the pre-existing firmware from a diskette or CD image.

  • Page 97: System-Board Led Locations

    System-board LED locations The following illustration shows the location of the LEDs on the system board. DIMM 3 error DIMM 2 error LED (CR46) LED (CR45) DIMM 1 error DIMM 4 error LED (CR40) LED (CR53) Microprocessor 1 error LED (CR58) Service processor error LED (CR27) NMI error...
  • Page 98 The serial number of the blade server (with the original system-board assembly) must match the serial number that you reported when you called IBM for service. v Because the new system-board assembly is not associated with a blade-server serial number, you must transfer the serial number from the original system-board assembly to the new system-board assembly.
  • Page 99 15. Configure an SOL connection and attach it to this blade server. For additional information, see the IBM Eserver BladeCenter and BladeCenter T Serial Over LAN Setup Guide. 16. The blade server will boot to the open firmware command to enter the serial number of the blade server (with the original system-board assembly).

  • Page 100: Completing The Installation

    Note: These checkpoint codes are described in Chapter 7, “Diagnostics,” on page 37. 17. Reset the system date and time through the operating system that you installed. For additional information, see your operating-system documentation. The system-board assembly replacement procedure is now complete. Continue with “Input/output connectors and devices”...
  • Page 101 Bezel-assembly release Bezel-assembly release Control-panel cable Control panel connector Complete the following steps to install the blade-server bezel assembly: 1. Read the safety information beginning on page iii and “Installation guidelines” on page 71 2. Connect the control-panel cable to the control-panel connector on the system-board assembly.

  • Page 102: Closing The Blade Server Cover

    Therefore, to enable communication between the blade server and these devices, you must perform the configuration tasks that are described in Chapter 3, “Configuration,” on page 17 and the IBM Eserver BladeCenter and BladeCenter T Serial Over LAN Setup Guide.

  • Page 103: Chapter 10. Symptom-To-Fru Index

    1. Check the configuration before you replace a FRU. Configuration problems can cause false errors and symptoms. 2. For IBM devices not supported by this index, refer to the manual for that device. 3. Always start with “General checkout” on page 37.

  • Page 104: Firmware Checkpoint (Progress) Codes

    5. Try reseating a suspected component or reconnecting a cable before replacing the component. 6. If the actions listed for a specific symptom do not resolve the problem, see “General checkout” on page 37 and “Undetermined problems” on page 156. POST error codes and messages are displayed on the screen.
  • Page 105 Checkpoint FRU/action D101 (a machine serial number has v Re-enter valid serial number. been entered) D102 (machine type and model field 1. Enter valid machine type and model. were found to be blank) 2. If prompt continues, system board and chassis. D103 (machine type and model have v Re-enter valid machine type and model.
  • Page 106 Checkpoint FRU/action E143 (operating system bootlist set 1. Go to “Checkout procedure” on page 38. from management module bootlist) 2. System board and chassis. E149 (Create boot manager node) 1. Go to “Checkout procedure” on page 38. 2. System board and chassis. E14A (build vital product 1.
  • Page 107 Checkpoint FRU/action E176 (TFTP file transfer) 1. Verify that server is correctly configured, then retry operation. 2. Verify that network connections are correct, then retry operation. 3. If no problems are found with bootp server or network, replace system board and chassis. 4.
  • Page 108 Checkpoint FRU/action E1AB (System booting using default 1. Go to “Checkout procedure” on page 38. service mode boot list) 2. System board and chassis. E1AC (System booting using 1. Go to “Checkout procedure” on page 38. customized service mode boot list) 2.
  • Page 109 Checkpoint FRU/action E1F6 (Determine boot device 1. Go to “Checkout procedure” on page 38. sequence) 2. System board and chassis. E1F7 (No boot image located) v Go to “Boot problem resolution” on page 153. E1F8 (Building boot device list for 1.
  • Page 110 Checkpoint FRU/action E20B (Reading boot mode) 1. Go to “Checkout procedure” on page 38. Note: If you have already been through the checkout procedure, continue with step 2. 2. System board and chassis. E20C (Finished hardware probing; 1. Go to “Checkout procedure” on page 38. passing control to partition firmware) 2.
  • Page 111 Checkpoint FRU/action E21D (Executing PCI initialization) 1. Go to “Checkout procedure” on page 38. 2. System board and chassis. E21E (execute I/O APIC test) 1. Go to “Checkout procedure” on page 38. 2. System board and chassis. E21F (Building the PFDS structure) 1.

  • Page 112: Firmware Error Codes

    Type the setup-fc-disk command at the open firmware prompt and press in the boot list; however, the Enter; then, restart the blade server. ibm,fw-fcpdisk alias name has not been defined in the /alias node.) 20A80102 (The ibm,fw-fcpdisk alias Run the setup-fc-disk utility.
  • Page 113 Error code FRU/action 20D0000F (self-test failed on device; 1. If a location code is specified, replace the device at that location. error and/or location code 2. Go to “Checkout procedure” on page 38. information may not be available) 20D00010 (self-test failed on device, 1.
  • Page 114 Error code FRU/action 20EE0011 (unable to execute the 1. Go to “Checkout procedure” on page 38. vpd method) 2. System board and chassis. 20EE0012 (unable to execute the 1. Go to “Checkout procedure” on page 38. mem-dimm-vpd method) 2. System board and chassis. 20EE0015 (failed to read VPD ″boot 1.
  • Page 115 Error code FRU/action 21020010 (USB CD drive remained 1. Retry operation. busy longer than the amount of 2. Update system firmware. allocated time) 3. USB CD drive. 4. System board and chassis. 21020011 (USB CD drive: 1. Retry operation. processing of ATA or ATAPI 2.
  • Page 116 Error code FRU/action 22010001 (PCI token ring adapter v Adapter failure) 22011001 (PCI token ring adapter v Adapter failure) 25A00001 (L2 cache controller v System board and chassis. failure) 25A10001 (cache L2 SRAM failure) v System board and chassis. 25A80xxx (NVRAM problems) 1.
  • Page 117 Error code FRU/action 25C00000 (no DIMMs detected) 1. Reseat DIMMs and restart server. 2. Go to “Checkout procedure” on page 38. 3. System board and chassis. 25C0xxyy (DIMM failure where: 1. Verify that all DIMMs are supported (see “Installing memory modules” on v xx of–...

  • Page 118: Service Request Numbers

    Error code FRU/action 25C10003 (companion (in the pair) 1. Make sure all DIMMs are supported; replace all unsupported DIMMs and of the memory DIMM specified by restart server. the location code is failing, 2. Make sure all DIMMs are installed in pairs; install DIMMs properly and unsupported, missing, or unmatched) restart server.

  • Page 119: Linux Service Aid "Diagela

    The Linux service aids for hardware diagnostics are separate from the operating system installation and are available for download from the following Web site: http://techsupport.services.ibm.com/server/lopdiags This service aid tool kit provides the key tools required to take advantage of the inherent JS20 hardware reliability, availability, and serviceability (RAS) functions.

  • Page 120: Description And Action

    Description and action This column lists a brief description of the failure that this SRN represents. It also contains instructions as to what to do to continue the problem analysis. Using the SRN list The Service Request Number list is in numerical sequence by SRN. Use the list as follows: 1.
  • Page 121 Service Failing request Function number source Code Description and action 101-xxxx xxxx The system hung while configuring a resource. The last three or four digits after the dash (-) identify the failing function code for the resource being configured. Go to undetermined problem procedure. 103-151 The time-of-day battery failed.
  • Page 122 Service Failing request Function number source Code Description and action 651-151 152 2E2 Sensor indicates a voltage is outside the normal range. Use Chapter 4, “Problem determination procedures for AIX and Linux,” on page 21. 651-152 Sensor indicates an abnormally high internal temperature. Action: Verify that: 1.
  • Page 123 Service Failing request Function number source Code Description and action 651-612 External cache ECC single-bit error. 651-613 External cache ECC single-bit error. 651-614 System bus time-out error. 651-615 Time-out error waiting for I/O. 651-619 Error log analysis indicates an error detected by the CPU. Action: Use failing function codes and the physical location codes from the diagnostic problem report screen to determine the FRUs.
  • Page 124 Service Failing request Function number source Code Description and action 651-66B Correctable error threshold exceeded. Action: Use Chapter 4, “Problem determination procedures for AIX and Linux,” on page 21. 651-674 Failed memory module. Action: Use Chapter 4, “Problem determination procedures for AIX and Linux,” on page 21. 651-675 Failed memory module.
  • Page 125 Service Failing request Function number source Code Description and action 651-734 Intermediate or system bus data parity error. 651-735 Intermediate or system bus time-out error. 651-736 Intermediate or system bus time-out error. 651-740 Note: Ensure that the system IPLROS and service processor are at the latest firmware level before removing any parts from the system.
  • Page 126 Service Failing request Function number source Code Description and action 651-811 Under voltage condition was detected Action: Shut the system down and do the following before replacing any FRUs. 1. Visually inspect the power cables and reseat the connectors. 2. Run the following command diag -Avd sysplanar0. When the Resource Repair Action menu displays, select sysplanar0.
  • Page 127 Service Failing request Function number source Code Description and action 652-600 A non-critical error has been detected: uncorrectable memory or unsupported memory. Action: Schedule deferred maintenance. Examine the memory modules and determine if they are supported types. If the modules are supported, then replace the appropriate memory modules.
  • Page 128 Service Failing request Function number source Code Description and action 652-66B A non-critical error has been detected: correctable error threshold exceeded. Action: Schedule deferred maintenance. Use Chapter 4, “Problem determination procedures for AIX and Linux,” on page 21. 652-731 A non-critical error has been detected: intermediate or system bus address parity error.
  • Page 129 Service Failing request Function number source Code Description and action 815-101 Floating point processor failed. 815-102 Floating point processor failed. 815-200 815 7C0 Power-on self-test indicates a processor failure. 815-201 Processor has a status of failed. Processors with a failed status are deconfigured and therefore cannot be tested or used by the system.
  • Page 130 Service Failing request Function number source Code Description and action 887-304 Coprocessor internal test failed. 887-305 Internal loopback test failed. 887-306 Internal loopback test failed. 887-307 External loopback test failed. 887-319 Software device driver indicates a hardware failure. 887-400 Fuse test failed. 887-401 Circuit breaker for Ethernet test failed.

  • Page 131: Srns A00-(X)Xxx Through A1D-(X)Xxx

    Service Failing request Function number source Code Description and action 2D02 2631 Generic reference for USB controller/adapter - system planar see “FFC table” on page 142, FFC 2631 SRNs A00-(x)xxx through A1D-(x)xxx Note: Some SRNs in this chapter may have 4 rather than 3 digits after the dash (–).
  • Page 132 Service request number source Description FRU/action A01-02x CPU internal cache or cache controller 1. Check the BladeCenter management module error. event log; if an error was recorded by the system or if a checkpoint code is displayed on the console, see Chapter 10, “Symptom-to-FRU index,”...
  • Page 133 Service request number source Description FRU/action A02-04x Memory Control subsystem internal error. 1. Check the BladeCenter management module event log; if an error was recorded by the system or if a checkpoint code is displayed on the console, see Chapter 10, “Symptom-to-FRU index,”...
  • Page 134 Service request number source Description FRU/action A03-00x Error log analysis indicates an error 1. Check the BladeCenter management module detected by the I/O device, but the failure event log; if an error was recorded by the could not be isolated. system or if a checkpoint code is displayed on the console, see Chapter 10, “Symptom-to-FRU index,”...
  • Page 135 Service request number source Description FRU/action A03-13x I/O Expansion bus parity error. 1. Check the BladeCenter management module event log; if an error was recorded by the system or if a checkpoint code is displayed on the console, see Chapter 10, “Symptom-to-FRU index,”...
  • Page 136 Service request number source Description FRU/action A05-04x System shutdown due to voltage outside 1. Check the BladeCenter management module normal range. event log; if an error was recorded by the system or if a checkpoint code is displayed on the console, see Chapter 10, “Symptom-to-FRU index,”...
  • Page 137 Service request number source Description FRU/action A05-10x System shutdown due to FRU that has 1. Check the BladeCenter management module failed. event log; if an error was recorded by the system or if a checkpoint code is displayed on the console, see Chapter 10, “Symptom-to-FRU index,”...
  • Page 138 Service request number source Description FRU/action A0D-06x Service Processor reports unknown 1. Check the BladeCenter management module communication error. event log; if an error was recorded by the system or if a checkpoint code is displayed on the console, see Chapter 10, “Symptom-to-FRU index,”...
  • Page 139 Service request number source Description FRU/action A0D-24x Service Processor detected a 1. Check the BladeCenter management module surveillance time-out. event log; if an error was recorded by the system or if a checkpoint code is displayed on the console, see Chapter 10, “Symptom-to-FRU index,”...
  • Page 140 Service request number source Description FRU/action A10-200 The resource was marked failed by the 1. Check the BladeCenter management module platform. The system is operating in event log; if an error was recorded by the degraded mode. system or if a checkpoint code is displayed on the console, see Chapter 10, “Symptom-to-FRU index,”...
  • Page 141 Service request number source Description FRU/action A11-50x Recoverable errors on resource indicate 1. If repair is not immediately available, reboot a trend toward an unrecoverable error. and the resource will be deconfigured; However, the resource could not be operations can continue in a degraded mode. deconfigured and is still in use.
  • Page 142 Service request number source Description FRU/action A12-04x A non-critical error has been detected, a 1. Check the BladeCenter management module memory control subsystem internal error. event log; if an error was recorded by the system or if a checkpoint code is displayed on the console, see Chapter 10, “Symptom-to-FRU index,”...
  • Page 143 Service request number source Description FRU/action A12-12x A non-critical error has been detected, an 1. Check the BladeCenter management module I/O host bridge time-out error. event log; if an error was recorded by the system or if a checkpoint code is displayed on the console, see Chapter 10, “Symptom-to-FRU index,”...
  • Page 144 Service request number source Description FRU/action A13-03x A non-critical error has been detected, an 1. Check the BladeCenter management module I/O bus time-out, access or other error. event log; if an error was recorded by the system or if a checkpoint code is displayed on the console, see Chapter 10, “Symptom-to-FRU index,”...
  • Page 145 Service request number source Description FRU/action A13-12x A non-critical error has been detected, an 1. Check the BladeCenter management module error on system bus. event log; if an error was recorded by the system or if a checkpoint code is displayed on the console, see Chapter 10, “Symptom-to-FRU index,”...
  • Page 146 Service request number source Description FRU/action A15-01x Sensor indicates a fan is turning too 1. Check the BladeCenter management module slowly. event log; if an error was recorded by the system or if a checkpoint code is displayed on the console, see Chapter 10, “Symptom-to-FRU index,”...
  • Page 147 Service request number source Description FRU/action A15-14x Power fault due to unspecified cause. 1. Check the BladeCenter management module event log; if an error was recorded by the system or if a checkpoint code is displayed on the console, see Chapter 10, “Symptom-to-FRU index,”...
  • Page 148 Service request number source Description FRU/action A15-24x Power Fault specifically due to internal 1. Check the BladeCenter management module battery failure. event log; if an error was recorded by the system or if a checkpoint code is displayed on the console, see Chapter 10, “Symptom-to-FRU index,”...
  • Page 149 Service request number source Description FRU/action A1D-07x A non-critical error has been detected,: 1. Check the BladeCenter management module Internal service processor firmware error event log; if an error was recorded by the or incorrect version. system or if a checkpoint code is displayed on the console, see Chapter 10, “Symptom-to-FRU index,”...
  • Page 150 Service request number source Description FRU/action A1D-21x A non-critical error has been detected, a 1. Check the BladeCenter management module service processor detected error with event log; if an error was recorded by the time-of-day clock backup battery. system or if a checkpoint code is displayed on the console, see Chapter 10, “Symptom-to-FRU index,”...

  • Page 151: Failing Function Codes (Ffcs)

    Service request number source Description FRU/action A1D-37x A non-critical error has been detected: 1. Check the BladeCenter management module Clock or PLL Error. event log; if an error was recorded by the system or if a checkpoint code is displayed on the console, see Chapter 10, “Symptom-to-FRU index,”...

  • Page 152: Ffc Table

    v If the operating system is AIX, perform “Verifying the replacement part using AIX diagnostics” on page 30 v If the operating system is Linux, perform “Running the standalone diagnostics from CD-ROM” on page 25 The failing function codes are listed in numerical sequence. A function may not be physically packaged on the same FRU in different system units.
  • Page 153 Failing Function FRU Part Code Machine Type/Model Number Description and notes 8842 model JS20 74P2278 System planar 8842 model JS20 74P2278 System planar 8842 model JS20 Common Memory Logic problem for memory card and refer to HMM for FRU part numbers. Note: If more than a pair of memory modules from the same memory card are reported missing, first replace the FRU that the memory modules connect to;...
  • Page 154 Failing Function FRU Part Code Machine Type/Model Number Description and notes 8842 model JS20 74P2278 System planar - thermal sensor problem 8842 model JS20 74P2278 System planar - voltage sensor problem 8842 model JS20 74P2278 System planar - serial port controller problem 8842 model JS20 74P2278 System planar - JTAG/COP controller problem...

  • Page 155: Light Path Diagnostics Leds

    Light path diagnostics LEDs Lit blade-error LED CRU/action None v Check the event log or Linux Syslog (platform log) in the BladeCenter management module. DIMM x error v DIMM x v DIMM 1 – CR40 Note: Multiple DIMM LEDs do not necessarily indicate multiple DIMM failures. v DIMM 2 –...

  • Page 156: Cd Drive Problems

    CD drive problems Symptom FRU/action CD drive cannot be configured The customer interface card (FRU number 59P6629) in the BladeCenter Type 8677 with JS20 blade server but unit is not compatible with the JS20 blade server and must be replaced with the works with HSxx blade server latest level FRU.

  • Page 157: Diskette Drive Problems

    Diskette drive problems Symptom FRU/action Diskette drive activity LED stays 1. If there is a diskette in the drive, verify that: on, or the system bypasses the v The diskette is inserted correctly in the drive. diskette drive. v The diskette is good and not damaged – the drive light comes on (one-second flash) when the diskette is inserted (try another diskette if you have one).

  • Page 158: Memory Problems

    FRU/action Testing the monitor. v See the information that comes with the monitor for adjusting and testing instructions. (Some IBM monitors have their own self-tests.) The screen is blank. 1. Verify that: v The system power cord is connected to the BladeCenter power module and a working electrical outlet.

  • Page 159: Mouse Problems

    Verify that the monitor cable is connected to the video port on the BladeCenter you direct it to a working blade management module. Some IBM monitors have their own self-tests. If you server, or goes blank when you suspect a problem with the monitor, see the information that comes with the start some application programs monitor for adjusting and testing instructions.

  • Page 160: Network Connection Problems

    2. If the option comes with its own test instructions, use those instructions to test the option. 3. Replace the option you just installed. An IBM option that used to work 1. Verify that all of the option hardware and cable connections are secure. does not work now.

  • Page 161: Power Problems

    Local power control for the blade server is enabled (use the BladeCenter management-module Web interface to verify), or the blade server was instructed through the management module (Web interface or IBM Director) to turn on. 2. If you just installed an option in the blade server, remove it, and restart the blade server.

  • Page 162: Software Problems

    Software problems Symptom FRU/action Suspected software problem. 1. To determine if problems are caused by the software, verify that: v The server has the minimum memory needed to use the software. For memory requirements, see the information that comes with the software. Note: If you have just installed an adapter or memory, you might have a memory address conflict.

  • Page 163: Boot Problem Resolution

    Boot problem resolution Depending on the boot device, a checkpoint may be displayed on the console for an extended period of time while the boot image is retrieved from the device. This is particularly true for CD-ROM and network boot attempts. When booting from the CD-ROM, watch for activity on the drive’s LED indicator.

  • Page 164: Physical Location Codes

    (the unique identifiers that identify the individual blade server asset against which an IBM warranty is provided). The physical location code gives no indication of the location of the blade server within the BladeCenter unit. Physical location codes are within the domain of the enclosure, which in this case is the individual, fully-assembled blade.
  • Page 165 Component Location code DIMM3 Un-P1-C3 DIMM4 Un-P1-C4 PPC970,1 Un-P1 PPC970,2 Un-P1 Memory-controller Un-P1 PCI-X bus 1 Un-P1 PCI-X bus 2 Un-P1 PCI bus Un-P1 IDE controller 1 Un-P1-T8 IDE controller 2 Un-P1-T9 IDE disk 1 Un-P1-D1 IDE disk 2 Un-P1-D2 USB hub 1 Un-P1 USB hub 2...

  • Page 166: Undetermined Problems

    If all of the blade servers exhibit the same symptom, it is probably a BladeCenter unit problem; for more information, see the IBM BladeCenter Hardware Maintenance Manual and Troubleshooting Guide. Check the LEDs on all power supplies of the BladeCenter unit where the blade server is installed.
  • Page 167 a. Turn off the blade server, remove it from the BladeCenter unit, and open the cover. b. If there are two IDE drives: 1) Remove the second drive attached to IDE connector 2. 2) Close the cover, reinstall the JS20 server, turn it on, and look for an error in the BladeCenter management-module event log and the Linux Syslog (platform log): a) If no error occurs and you are able to log in, then the drive...

  • Page 168: Problem Determination Tips

    Problem determination tips Because of the variety of hardware and software combinations that can be encountered, use the following information to assist you in problem determination. If possible, have this information available when requesting assistance from Service Support and Engineering functions. v Machine type and model v Hard disk upgrades v Failure symptom...

  • Page 169: Chapter 11. Parts Listing, Type 8842

    Chapter 11. Parts listing, Type 8842 This parts listing supports the JS20 Type 8842 blade server. © Copyright IBM Corp. 2003...
  • Page 170 Note: Field replaceable units (FRUs) should be serviced only by qualified field service technicians. Customer replaceable units can be replaced by the customer. Index System, Type 8842 FRU No. CRU/FRU Blade cover (all models) 25R8494 Memory, 256MB PC2700 ECC (models 21x, 41x) 73P2270 Memory, 512MB PC2700 ECC (optional) 73P2277...

  • Page 171: Appendix A. Getting Help And Technical Assistance

    If you need help, service, or technical assistance or just want more information about IBM products, you will find a wide variety of sources available from IBM to assist you. This appendix contains information about where to go for additional information about IBM and IBM products, what to do if you experience a problem ®...

  • Page 172: Getting Help And Information From The World Wide Web

    Getting help and information from the World Wide Web On the World Wide Web, the IBM Web site has up-to-date information about IBM Eserver and IntelliStation products, services, and support. The address for IBM xSeries and BladeCenter information is http://www.ibm.com/eserver/xseries/. The address for pSeries information is http://www.ibm.com/eserver/pseries/.

  • Page 173: Appendix B. Safety Information

    The following section contains the safety information that you need to be familiar with before servicing an IBM computer. General safety Follow these rules to ensure general safety: v Observe good housekeeping in the area of the machines during and after maintenance.

  • Page 174: Electrical Safety

    Electrical safety CAUTION: Electrical current from power, telephone, and communication cables can be hazardous. To avoid personal injury or equipment damage, disconnect the attached power cords, telecommunication systems, networks, and modems before you open the server covers, unless instructed otherwise in the installation and configuration procedures.

  • Page 175: Safety Inspection Guide

    This guide addresses only those items. However, good judgment should be used to identify potential safety hazards due to attachment of non-IBM features or options not covered by this inspection guide.

  • Page 176: Grounding Requirements

    Insulation must not be frayed or worn. 4. Remove the cover. 5. Check for any obvious non-IBM alterations. Use good judgment as to the safety of any non-IBM alterations. 6. Check inside the unit for any obvious unsafe conditions, such as metal filings, contamination, water or other liquids, or signs of fire or smoke damage.
  • Page 177 Statement 2 CAUTION: When replacing the lithium battery, use only IBM Part Number 33F8354 or an equivalent type battery recommended by the manufacturer. If your system has a module containing a lithium battery, replace it only with the same module type made by the same manufacturer.
  • Page 178 Statement 3 CAUTION: When laser products (such as CD-ROMs, DVD-ROM drives, fiber optic devices, or transmitters) are installed, note the following: v Do not remove the covers. Removing the covers of the laser product could result in exposure to hazardous laser radiation. There are no serviceable parts inside the device.
  • Page 179 Statement 5 CAUTION: The power control button on the device and the power switch on the power supply do not turn off the electrical current supplied to the device. The device also might have more than one power cord. To remove all electrical current from the device, ensure that all power cords are disconnected from the power source.
  • Page 180 Importante: Todas as instruções de cuidado e perigo da IBM documentation começam com um número. Este número é utilizado para fazer referência cruzada de uma instrução de cuidado ou perigo no idioma inglês com as versões traduzidas das instruções de cuidado ou perigo encontradas nesta seção.
  • Page 181 Aqueça a mais de 100°C (212°F) v Conserte nem desmonte Para descartar a bateria, entre em contato com a área de atendimento a clientes IBM, pelo telefone (011) 889-8986, para obter informações sobre como enviar a bateria pelo correio para a IBM.
  • Page 182 Instrução 4 ≥18 kg (39.7 lb) ≥32 kg (70.5 lb) ≥55 kg (121.2 lb) CUIDADO: Ao levantar a máquina, faça-o com segurança. Instrução 5 CUIDADO: Os botões Liga/Desliga localizados no dispositivo e na fonte de alimentação não desligam a corrente elétrica fornecida ao dispositivo. O dispositivo também pode ter mais de um cabo de alimentação.
  • Page 183 Appendix B. Safety information...
  • Page 184 BladeCenter JS20 Type 8842: Hardware Maintenance Manual and Troubleshooting Guide...
  • Page 185 Appendix B. Safety information...
  • Page 186 BladeCenter JS20 Type 8842: Hardware Maintenance Manual and Troubleshooting Guide...
  • Page 187 Appendix B. Safety information...
  • Page 188 BladeCenter JS20 Type 8842: Hardware Maintenance Manual and Troubleshooting Guide...
  • Page 189 Appendix B. Safety information...
  • Page 190 BladeCenter JS20 Type 8842: Hardware Maintenance Manual and Troubleshooting Guide...
  • Page 191 Important: Toutes les consignes Attention et Danger indiquées dans la bibliothèque IBM documentation sont précédées d’un numéro. Ce dernier permet de mettre en correspondance la consigne en anglais avec ses versions traduites dans la présente section. Par exemple, si une consigne de type Attention est précédée du chiffre 1, ses traductions sont également précédées du chiffre 1 dans la présente section.
  • Page 192 Remplacez la pile au lithium usagée par une pile de référence identique exclusivement - voir la référence IBM - ou par une pile équivalente recommandée par le fabricant. Si votre système est doté d’un module contenant une pile au lithium, vous devez le remplacer uniquement par un module identique, produit par le même...
  • Page 193 Notice n° 4 ≥18 kg (39.7 lb) ≥32 kg (70.5 lb) ≥55 kg (121.2 lb) ATTENTION: Faites-vous aider pour soulever ce produit. Notice n° 5 ATTENTION: Le bouton de mise sous tension/hors tension de l’unité et l’interrupteur d’alimentation du bloc d’alimentation ne coupent pas l’arrivée de courant électrique à l’intérieur de la machine.
  • Page 194 Wichtig: Alle Sicherheitshinweise in dieser IBM documentation beginnen mit einer Nummer. Diese Nummer verweist auf einen englischen Sicherheitshinweis mit den übersetzten Versionen dieses Hinweises in diesem Abschnitt. Wenn z. B. ein Sicherheitshinweis mit der Nummer 1 beginnt, so erscheint die übersetzung für diesen Sicherheitshinweis in diesem Abschnitt unter dem Hinweis...
  • Page 195 Hinweis 2 ACHTUNG: Eine verbrauchte Batterie nur durch eine Batterie mit der IBM Teilenummer 33F8354 oder durch eine vom Hersteller empfohlene Batterie ersetzen. Wenn Ihr System ein Modul mit einer Lithium-Batterie enthält, ersetzen Sie es immer mit dem selben Modultyp vom selben Hersteller.
  • Page 196 Hinweis 4 ≥18 kg ≥32 kg ≥55 kg ACHTUNG: Beim Anheben der Maschine die vorgeschriebenen Sicherheitsbestimmungen beachten. Hinweis 5 ACHTUNG: Mit dem Betriebsspannungsschalter an der Vorderseite des Servers und dem Betriebsspannungsschalter am Netzteil wird die Stromversorgung für den Server nicht unterbrochen.
  • Page 197 Importante: Tutti gli avvisi di attenzione e di pericolo riportati nella pubblicazione IBM documentation iniziano con un numero. Questo numero viene utilizzato per confrontare avvisi di attenzione o di pericolo in inglese con le versioni tradotte riportate in questa sezione.
  • Page 198 Avviso 2 ATTENZIONE: Quando si sostituisce la batteria al litio, utilizzare solo una batteria IBM con numero parte 33F8354 o batterie dello stesso tipo o di tipo equivalente consigliate dal produttore. Se il sistema di cui si dispone è provvisto di un modulo contenente una batteria al litio, sostituire tale batteria solo con un tipo di modulo uguale a quello fornito dal produttore.
  • Page 199 Avviso 4 ≥18 kg ≥32 kg ≥55 kg ATTENZIONE: Durante il sollevamento della macchina seguire delle norme di sicurezza. Avviso 5 ATTENZIONE: Il pulsante del controllo dell’alimentazione situato sull’unità e l’interruttore di alimentazione posto sull’alimentatore non disattiva la corrente elettrica fornita all’unità. L’unità potrebbe disporre di più...
  • Page 200 BladeCenter JS20 Type 8842: Hardware Maintenance Manual and Troubleshooting Guide...
  • Page 201 Appendix B. Safety information...
  • Page 202 BladeCenter JS20 Type 8842: Hardware Maintenance Manual and Troubleshooting Guide...
  • Page 203 Appendix B. Safety information...
  • Page 204 Importante: Todas las declaraciones de precauciín de esta IBM documentation empiezan con un número. Dicho número se emplea para establecer una referencia cruzada de una declaraciín de precauciín o peligro en inglés con las versiones traducidas que de dichas declaraciones pueden encontrarse en esta secciín.
  • Page 205 Cuando desee sustituir la batería de litio, utilice únicamente el número de pieza 33F8354 de IBM o cualquier tipo de batería equivalente que recomiende el fabricante. Si el sistema tiene un mídulo que contiene una batería de litio, sustitúyalo únicamente por el mismo tipo de mídulo, que ha de estar creado por el mismo fabricante.
  • Page 206 Declaración 4 ≥18 kg ≥32 kg ≥55 kg PRECAUCIÓN: Tome medidas de seguridad al levantar el producto. Declaración 5 PRECAUCIÓN: El botín de control de alimentaciín del dispositivo y el interruptor de alimentaciín de la fuente de alimentaciín no apagan la corriente eléctrica suministrada al dispositivo. Es posible también que el dispositivo tenga más de un cable de alimentaciín.

  • Page 207: Notices

    Web sites. The materials at those Web sites are not part of the materials for this IBM product, and use of those Web sites is at your own risk. IBM may use or distribute any of the information you supply in any way it believes appropriate without incurring any obligation to you.

  • Page 208: Trademarks

    ServerProven BladeCenter TechConnect C2T Interconnect ThinkPad Chipkill Tivoli EtherJet Tivoli Enterprise FlashCopy Update Connector Wake on LAN IBM (logo) XA-32 IntelliStation XA-64 NetBAY X-Architecture Netfinity XceL4 NetView XpandOnDemand OS/2 WARP xSeries Intel, MMX, and Pentium are trademarks of Intel Corporation in the United States, other countries, or both.

  • Page 209: Product Recycling And Disposal

    IBM makes no representations or warranties with respect to non-IBM products. Support (if any) for the non-IBM products is provided by the third party, not IBM. Some software may differ from its retail version (if available), and may not include user manuals or all program functionality.

  • Page 210: Electronic Emission Notices

    Properly shielded and grounded cables and connectors must be used in order to meet FCC emission limits. IBM is not responsible for any radio or television interference caused by using other than recommended cables and connectors or by unauthorized changes or modifications to this equipment.

  • Page 211: European Union Emc Directive Conformance Statement

    IBM cannot accept responsibility for any failure to satisfy the protection requirements resulting from a nonrecommended modification of the product, including the fitting of non-IBM option cards. This product has been tested and found to comply with the limits for Class A Information Technology Equipment according to CISPR 22/European Standard EN 55022.
  • Page 212 BladeCenter JS20 Type 8842: Hardware Maintenance Manual and Troubleshooting Guide...

  • Page 213: Index

    15 removing 88 error symptoms 145 components, system board 86 errors configuration light path 145 automatic 17 memory 47 connectors symptoms 145 battery 86 Ethernet I/O expansion card 86 cabling requirements 82 IDE 86 © Copyright IBM Corp. 2003...
  • Page 214 Ethernet controller installing (continued) configuring 18 bezel assembly 91 enumeration 19 components on system board 88 failover 18 I/O expansion card 79 redundant network connection 18 IDE hard disk drives 75 Ethernet switch module memory module 77 compatibility requirements 82 options 71 operating-system requirements 9 system board 87...
  • Page 215 problems (continued) option 150 network connection pointing device 149 I/O expansion card 79 power 151 network connection problems 150 service processor 151 network requirements software 152 Ethernet switch module 9 startup 152, 153 notes 5 undetermined 156 notes, important 198 progress codes 40 notices protecting yourself from electrostatic discharge...
  • Page 216 starting blade server 13 command-line interface 34 TEMP image 48 starting a session using SSH 35 starting a session using Telnet 35 startup problems 152, 153 statements and notices 5 static electricity 71 static-sensitive devices, handling 71 stopping the blade server 14 strap, electrostatic discharge (ESD) 71 system board components...
  • Page 218 Part Number: 90P3485 Printed in USA (1P) P/N: 90P3485...

This manual is also suitable for:

Bladecenter js20 type 8842

Table of Contents