Page 1 BladeCenter JS21 Types 7988 and 8844 Problem Determination and Service Guide...
Page 3 BladeCenter JS21 Types 7988 and 8844 Problem Determination and Service Guide...
Page 4 Note: Before using this information and the product it supports, read the general information in Appendix B, “Notices,” on page 173, and the Warranty and Support Information document on the IBM BladeCenter Documentation CD. Sixth Edition (November 2010) © Copyright IBM Corporation 2007.
Page 6 Solving undetermined problems ....135 Calling IBM for service ..... 136 Chapter 3.
Page 7 Configuring a SAS RAID array....169 Updating IBM Director ..... . 169 Checking the status of the media tray .
Page 8 BladeCenter JS21 Types 7988 and 8844: Problem Determination and Service Guide...
Page 9: Safety
Les sikkerhetsinformasjonen (Safety Information) før du installerer dette produktet. Antes de instalar este produto, leia as Informações sobre Segurança. Antes de instalar este producto, lea la información de seguridad. Läs säkerhetsinformationen innan du installerar den här produkten. © Copyright IBM Corp. 2007...
Page 10: Guidelines For Trained Service Technicians
Use the information in this section to help you identify potential unsafe conditions in an IBM product that you are working on. Each IBM product, as it was designed and manufactured, has required safety items to protect users and service technicians from injury.
Page 11: Safety Statements
v Do not touch the reflective surface of a dental mirror to a live electrical circuit. The surface is conductive and can cause personal injury or equipment damage if it touches a live electrical circuit. v Some rubber floor mats contain small conductive fibers to decrease electrostatic discharge.
Page 12 Statement 1: DANGER Electrical current from power, telephone, and communication cables is hazardous. To avoid a shock hazard: v Do not connect or disconnect any cables or perform installation, maintenance, or reconfiguration of this product during an electrical storm. v Connect all power cords to a properly wired and grounded electrical outlet.
Page 13 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 14 Statement 4: ≥ 18 kg (39.7 lb) ≥ 32 kg (70.5 lb) ≥ 55 kg (121.2 lb) CAUTION: Use safe practices when lifting. 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.
Page 15 Statement 8: CAUTION: Never remove the cover on a power supply or any part that has the following label attached. Hazardous voltage, current, and energy levels are present inside any component that has this label attached. There are no serviceable parts inside these components.
Page 16 BladeCenter JS21 Types 7988 and 8844: Problem Determination and Service Guide...
Page 17: Chapter 1. Introduction
Replaceable components are of three types: v Tier 1 customer replaceable unit (CRU): Replacement of Tier 1 CRUs is your responsibility. If IBM installs a Tier 1 CRU at your request, you will be charged for the installation. v Tier 2 customer replaceable unit: You may install a Tier 2 CRU yourself or request IBM to install it, at no additional charge, under the type of warranty service that is designated for your blade server.
Page 18: Notices And Statements In This Document
Notices and statements 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 Documentation CD. Each statement is numbered for reference to the corresponding statement in the Safety Information document.
Page 19: Features And Specifications
Electrical input: 12 V dc v Two 1 Gigabit Ethernet controllers Support for: Environment: v Expansion card interface v Air temperature: v Two single-core, 64-bit, IBM v Intelligent Platform Management – Blade server on: 10° to 35°C (50° ® PowerPC 970MP microprocessors Interface (IPMI) to 95°F).
Page 20: Blade Server Control Panel Buttons And Leds
For information about supported Linux operating systems, see http://www.ibm.com/servers/eserver/serverproven/compat/us/. The LED on this button flashes while the request is being processed, then is lit when the ownership of the keyboard and video has been transferred to the blade server.
Page 21 Location LED: When this blue LED is lit, it has been turned on by the system administrator to aid in visually locating the blade server. The location LED can be turned off through the management-module Web interface or through IBM Director Console.
Page 22: Turning On The Blade Server
Turning on the blade server After you connect the blade server to power through the BladeCenter unit, the blade server can start in any of the following ways: v You can press the power-control button on the front of the blade server (behind the control panel door, see “Blade server control panel buttons and LEDs”...
Page 23: 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 24: System-Board Jumpers
System-board jumpers The following illustration shows the jumpers on the system board. BIOS code page jumper (J14) System-board LEDs The following illustration shows the LEDs on the system board. You have to remove the blade server from the BladeCenter unit, open the cover, and press the light path diagnostics switch to light any error LEDs that were turned on during processing.
Page 25: Chapter 2. Diagnostics
(see “Location codes” on page 66). Note: Some POST codes may not display on the operator panel, these codes can be viewed using the Progress Indicator History option in the SMS utility (see “Using the SMS utility” on page 166). © Copyright IBM Corp. 2007...
Page 26: Progress Codes
Progress codes enable users and service personnel to know what the system is doing as it initializes. These codes are not intended to be error indicators, but in some cases a system could hang at one of the progress codes without displaying an eight-digit error code.
Page 27 v If the system hangs on a progress code, follow the suggested actions in the order in which they are listed in the Action column until the problem is resolved. v See Chapter 3, “Parts listing, Types 7988 and 8844,” on page 137 to determine which components are CRUs and which components are FRUs.
Page 28 v If the system hangs on a progress code, follow the suggested actions in the order in which they are listed in the Action column until the problem is resolved. v See Chapter 3, “Parts listing, Types 7988 and 8844,” on page 137 to determine which components are CRUs and which components are FRUs.
Page 29 v If the system hangs on a progress code, follow the suggested actions in the order in which they are listed in the Action column until the problem is resolved. v See Chapter 3, “Parts listing, Types 7988 and 8844,” on page 137 to determine which components are CRUs and which components are FRUs.
Page 30 v If the system hangs on a progress code, follow the suggested actions in the order in which they are listed in the Action column until the problem is resolved. v See Chapter 3, “Parts listing, Types 7988 and 8844,” on page 137 to determine which components are CRUs and which components are FRUs.
Page 31 v If the system hangs on a progress code, follow the suggested actions in the order in which they are listed in the Action column until the problem is resolved. v See Chapter 3, “Parts listing, Types 7988 and 8844,” on page 137 to determine which components are CRUs and which components are FRUs.
Page 32 v If the system hangs on a progress code, follow the suggested actions in the order in which they are listed in the Action column until the problem is resolved. v See Chapter 3, “Parts listing, Types 7988 and 8844,” on page 137 to determine which components are CRUs and which components are FRUs.
Page 33 v If the system hangs on a progress code, follow the suggested actions in the order in which they are listed in the Action column until the problem is resolved. v See Chapter 3, “Parts listing, Types 7988 and 8844,” on page 137 to determine which components are CRUs and which components are FRUs.
Page 34 v If the system hangs on a progress code, follow the suggested actions in the order in which they are listed in the Action column until the problem is resolved. v See Chapter 3, “Parts listing, Types 7988 and 8844,” on page 137 to determine which components are CRUs and which components are FRUs.
Page 35 v If the system hangs on a progress code, follow the suggested actions in the order in which they are listed in the Action column until the problem is resolved. v See Chapter 3, “Parts listing, Types 7988 and 8844,” on page 137 to determine which components are CRUs and which components are FRUs.
Page 36 v If the system hangs on a progress code, follow the suggested actions in the order in which they are listed in the Action column until the problem is resolved. v See Chapter 3, “Parts listing, Types 7988 and 8844,” on page 137 to determine which components are CRUs and which components are FRUs.
Page 37 v If the system hangs on a progress code, follow the suggested actions in the order in which they are listed in the Action column until the problem is resolved. v See Chapter 3, “Parts listing, Types 7988 and 8844,” on page 137 to determine which components are CRUs and which components are FRUs.
Page 38 v If the system hangs on a progress code, follow the suggested actions in the order in which they are listed in the Action column until the problem is resolved. v See Chapter 3, “Parts listing, Types 7988 and 8844,” on page 137 to determine which components are CRUs and which components are FRUs.
Page 39 v If the system hangs on a progress code, follow the suggested actions in the order in which they are listed in the Action column until the problem is resolved. v See Chapter 3, “Parts listing, Types 7988 and 8844,” on page 137 to determine which components are CRUs and which components are FRUs.
Page 40 v If the system hangs on a progress code, follow the suggested actions in the order in which they are listed in the Action column until the problem is resolved. v See Chapter 3, “Parts listing, Types 7988 and 8844,” on page 137 to determine which components are CRUs and which components are FRUs.
Page 41 v If the system hangs on a progress code, follow the suggested actions in the order in which they are listed in the Action column until the problem is resolved. v See Chapter 3, “Parts listing, Types 7988 and 8844,” on page 137 to determine which components are CRUs and which components are FRUs.
Page 42 The system is rebooting to enact 1. Make sure that: changes specified in v The bootp server is correctly configured, ibm,client-architecture-support then retry the operation. v The network connections are correct, then retry the operation. 2. Go to “Checkout procedure” on page 106.
Page 43 v If the system hangs on a progress code, follow the suggested actions in the order in which they are listed in the Action column until the problem is resolved. v See Chapter 3, “Parts listing, Types 7988 and 8844,” on page 137 to determine which components are CRUs and which components are FRUs.
Page 44 v If the system hangs on a progress code, follow the suggested actions in the order in which they are listed in the Action column until the problem is resolved. v See Chapter 3, “Parts listing, Types 7988 and 8844,” on page 137 to determine which components are CRUs and which components are FRUs.
Page 45 v If the system hangs on a progress code, follow the suggested actions in the order in which they are listed in the Action column until the problem is resolved. v See Chapter 3, “Parts listing, Types 7988 and 8844,” on page 137 to determine which components are CRUs and which components are FRUs.
Page 46 v If the system hangs on a progress code, follow the suggested actions in the order in which they are listed in the Action column until the problem is resolved. v See Chapter 3, “Parts listing, Types 7988 and 8844,” on page 137 to determine which components are CRUs and which components are FRUs.
Page 47 v If the system hangs on a progress code, follow the suggested actions in the order in which they are listed in the Action column until the problem is resolved. v See Chapter 3, “Parts listing, Types 7988 and 8844,” on page 137 to determine which components are CRUs and which components are FRUs.
Page 48 v If the system hangs on a progress code, follow the suggested actions in the order in which they are listed in the Action column until the problem is resolved. v See Chapter 3, “Parts listing, Types 7988 and 8844,” on page 137 to determine which components are CRUs and which components are FRUs.
Page 49 v If the system hangs on a progress code, follow the suggested actions in the order in which they are listed in the Action column until the problem is resolved. v See Chapter 3, “Parts listing, Types 7988 and 8844,” on page 137 to determine which components are CRUs and which components are FRUs.
Page 50: Attention Codes
Attention codes The following table describes the partitioning firmware attention codes that may be displayed if POST detects a problem and suggested actions to correct the problem. v Follow the suggested actions in the order in which they are listed in the Action column until the problem is solved.
Page 51 v Follow the suggested actions in the order in which they are listed in the Action column until the problem is solved. v See Chapter 3, “Parts listing, Types 7988 and 8844,” on page 137 to determine which components are CRUs and which components are FRUs.
Page 52 3. Go to “Checkout procedure” on page 106. 4. Replace the system board and chassis assembly. BA00E830 ibm,event-scan init failure 1. Reboot the blade server. 2. Look for server firmware updates; apply if available. 3. Go to “Checkout procedure” on page 106.
Page 53: Error Codes
Error codes The following table describes the error codes that may be displayed if POST detects a problem and suggested actions to correct the problem. Note: For problems persisting after completing the suggested actions, see “Checkout procedure” on page 106 and “Solving undetermined problems” on page 135.
Page 54 v Follow the suggested actions in the order in which they are listed in the Action column until the problem is solved. v See Chapter 3, “Parts listing, Types 7988 and 8844,” on page 137 to determine which components are CRUs and which components are FRUs.
Page 55 v Follow the suggested actions in the order in which they are listed in the Action column until the problem is solved. v See Chapter 3, “Parts listing, Types 7988 and 8844,” on page 137 to determine which components are CRUs and which components are FRUs.
Page 56 v Follow the suggested actions in the order in which they are listed in the Action column until the problem is solved. v See Chapter 3, “Parts listing, Types 7988 and 8844,” on page 137 to determine which components are CRUs and which components are FRUs.
Page 57 v Follow the suggested actions in the order in which they are listed in the Action column until the problem is solved. v See Chapter 3, “Parts listing, Types 7988 and 8844,” on page 137 to determine which components are CRUs and which components are FRUs.
Page 58 v Follow the suggested actions in the order in which they are listed in the Action column until the problem is solved. v See Chapter 3, “Parts listing, Types 7988 and 8844,” on page 137 to determine which components are CRUs and which components are FRUs.
Page 59 v Follow the suggested actions in the order in which they are listed in the Action column until the problem is solved. v See Chapter 3, “Parts listing, Types 7988 and 8844,” on page 137 to determine which components are CRUs and which components are FRUs.
Page 60 v Follow the suggested actions in the order in which they are listed in the Action column until the problem is solved. v See Chapter 3, “Parts listing, Types 7988 and 8844,” on page 137 to determine which components are CRUs and which components are FRUs.
Page 61 v Follow the suggested actions in the order in which they are listed in the Action column until the problem is solved. v See Chapter 3, “Parts listing, Types 7988 and 8844,” on page 137 to determine which components are CRUs and which components are FRUs.
Page 62 v Follow the suggested actions in the order in which they are listed in the Action column until the problem is solved. v See Chapter 3, “Parts listing, Types 7988 and 8844,” on page 137 to determine which components are CRUs and which components are FRUs.
Page 63 v Follow the suggested actions in the order in which they are listed in the Action column until the problem is solved. v See Chapter 3, “Parts listing, Types 7988 and 8844,” on page 137 to determine which components are CRUs and which components are FRUs.
Page 64 v Follow the suggested actions in the order in which they are listed in the Action column until the problem is solved. v See Chapter 3, “Parts listing, Types 7988 and 8844,” on page 137 to determine which components are CRUs and which components are FRUs.
Page 65 v Follow the suggested actions in the order in which they are listed in the Action column until the problem is solved. v See Chapter 3, “Parts listing, Types 7988 and 8844,” on page 137 to determine which components are CRUs and which components are FRUs.
Page 66 v Follow the suggested actions in the order in which they are listed in the Action column until the problem is solved. v See Chapter 3, “Parts listing, Types 7988 and 8844,” on page 137 to determine which components are CRUs and which components are FRUs.
Page 67 v Follow the suggested actions in the order in which they are listed in the Action column until the problem is solved. v See Chapter 3, “Parts listing, Types 7988 and 8844,” on page 137 to determine which components are CRUs and which components are FRUs.
Page 68 v Follow the suggested actions in the order in which they are listed in the Action column until the problem is solved. v See Chapter 3, “Parts listing, Types 7988 and 8844,” on page 137 to determine which components are CRUs and which components are FRUs.
Page 69 v Follow the suggested actions in the order in which they are listed in the Action column until the problem is solved. v See Chapter 3, “Parts listing, Types 7988 and 8844,” on page 137 to determine which components are CRUs and which components are FRUs.
Page 70 v Follow the suggested actions in the order in which they are listed in the Action column until the problem is solved. v See Chapter 3, “Parts listing, Types 7988 and 8844,” on page 137 to determine which components are CRUs and which components are FRUs.
Page 71 v Follow the suggested actions in the order in which they are listed in the Action column until the problem is solved. v See Chapter 3, “Parts listing, Types 7988 and 8844,” on page 137 to determine which components are CRUs and which components are FRUs.
Page 72 v Follow the suggested actions in the order in which they are listed in the Action column until the problem is solved. v See Chapter 3, “Parts listing, Types 7988 and 8844,” on page 137 to determine which components are CRUs and which components are FRUs.
Page 73 v Follow the suggested actions in the order in which they are listed in the Action column until the problem is solved. v See Chapter 3, “Parts listing, Types 7988 and 8844,” on page 137 to determine which components are CRUs and which components are FRUs.
Page 74 v Follow the suggested actions in the order in which they are listed in the Action column until the problem is solved. v See Chapter 3, “Parts listing, Types 7988 and 8844,” on page 137 to determine which components are CRUs and which components are FRUs.
Page 75 v Follow the suggested actions in the order in which they are listed in the Action column until the problem is solved. v See Chapter 3, “Parts listing, Types 7988 and 8844,” on page 137 to determine which components are CRUs and which components are FRUs.
Page 76 4. Replace the system board and chassis assembly. BA180100 The FDDI adapter Fcode driver is not supported on this server. IBM may produce a compatible driver in the future, but does not guarantee one. BA188000 There is an unsupported adapter in the Remove the adapter.
Page 77 v Follow the suggested actions in the order in which they are listed in the Action column until the problem is solved. v See Chapter 3, “Parts listing, Types 7988 and 8844,” on page 137 to determine which components are CRUs and which components are FRUs.
Page 78 v Follow the suggested actions in the order in which they are listed in the Action column until the problem is solved. v See Chapter 3, “Parts listing, Types 7988 and 8844,” on page 137 to determine which components are CRUs and which components are FRUs.
Page 79 Restart the blade server. firmware flash update BA278009 The operating system tools to update the Go to the IBM microcode download web site blade server firmware are incompatible (http://techsupport.services.ibm.com/server/ with this system. lopdiags) and download the latest version of the service aids package for Linux.
Page 80 v Follow the suggested actions in the order in which they are listed in the Action column until the problem is solved. v See Chapter 3, “Parts listing, Types 7988 and 8844,” on page 137 to determine which components are CRUs and which components are FRUs.
Page 81 v Follow the suggested actions in the order in which they are listed in the Action column until the problem is solved. v See Chapter 3, “Parts listing, Types 7988 and 8844,” on page 137 to determine which components are CRUs and which components are FRUs.
Page 82: Location Codes
Location codes Location codes are displayed with some error codes to identify the component that caused the error. Note: Location codes do not indicate the location of the blade server within the BladeCenter unit, they only identify components of the blade server. Location code Component Um-E1...
Page 83: Service Request Numbers
Note: The “diagela” service aid is part of the Linux service aids for hardware diagnostics. The service aids are separate from the operating system and are available for download from the following Web site: http:// techsupport.services.ibm.com/server/lopdiags. Using the SRN tables The SRN list is in numerical sequence. The failing function codes (FFCs) are provided to aid in locating a failing component (see “Failing function codes”...
Page 84 Description and action 110-101 The diagnostics did not detect an installed resource. Action: If this SRN appeared when running concurrent diagnostics, then run concurrent diagnostics using the diag -a command. 110-921 to The system halted while diagnostics were executing. 110-926 Note: xxx corresponds to the last three digits of the SRN.
Page 85 Description and action 252B-713 252B Adapter failure. 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 “POST checkpoint codes” on page 9. 2.
Page 86 Description and action 252B-721 252B Temporary adapter detected device bus failure. 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 “POST checkpoint codes” on page 9. 2.
Page 87 Description and action 256D-605 256D Error Log Analysis indicates permanent adapter failure is reported on the other port of this adapter. 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 “POST checkpoint codes”...
Page 88 Description and action 651-161 Sensor indicates a voltage is outside the normal range. Action: Go to “Performing the checkout procedure” on page 106. 651-162 Sensor indicates an abnormally high internal temperature. Action: Make sure that: 1. The room ambient temperature is within the system operating environment. 2.
Page 89 Description and action 651-632 Internal device error. 651-639 Error log analysis indicates an error detected by the I/O. Action: Use the problem determination procedure and failing function codes, use the physical location codes from the diagnostic problem report screen to determine the FRUs. 651-640 I/O general bus error.
Page 90 Description and action 651-711 System bus parity error. 651-712 System bus parity error. 651-713 System bus protocol/transfer error. 651-714 System bus protocol/transfer error. 651-715 System bus protocol/transfer error. 651-720 Uncorrectable memory error. Action: Go to “Performing the checkout procedure” on page 106.
Page 91 Description and action 651-780 Uncorrectable memory error. Action: Go to “Performing the checkout procedure” on page 106. 651-781 Uncorrectable memory error. Action: Go to “Performing the checkout procedure” on page 106. 651-784 Uncorrectable memory error. Action: Go to “Performing the checkout procedure” on page 106.
Page 92 Description and action 651-832 G2E1 Sensor detected an abnormally high internal temperature. Action: Make sure that: 1. The room ambient temperature is within the system operating environment. 2. There is unrestricted air flow around the system. 3. There are no fan failures. 651-841 Sensor detected a voltage outside of the normal range.
Page 93 Description and action 652-666 A non-critical error has been detected: correctable error threshold exceeded. Action: Schedule deferred maintenance. Go to “Performing the checkout procedure” on page 106. 652-669 A non-critical error has been detected: correctable error threshold exceeded. Action: Schedule deferred G maintenance. Go to “Performing the checkout procedure” on page 106.
Page 94 Description and action 814-112 The NVRAM test failed. 814-113 The VPD test failed. 814-114 I/O Card NVRAM test failed. 815-100 The floating-point processor test failed. 815-101 Floating point processor failed. 815-102 Floating point processor failed. 815-200 Power-on self-test indicates a processor failure. 815-201 Processor has a status of failed.
Page 95 Description and action 887-125 Fuse test failed. 887-202 Vital Product Data test failed. 887-203 Vital Product Data test failed. 887-209 RJ-45 converter test failed. 887-304 Coprocessor internal test failed. 887-305 Internal loopback test failed. 887-306 Internal loopback test failed. 887-307 External loopback test failed.
Page 96 Description and action 25C4-201 25C4 Configuration error. Go to “Performing the checkout procedure” on page 106. 25C4-701 25C4 Permanent adapter failure. Go to “Performing the checkout procedure” on page 106. 25C4-601 25C4 Download firmware error. Go to “Performing the checkout procedure” on page 106. 25C4-602 25C4 EEPROM read error.
Page 97 Description FRU/action A01-01x GCPU 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 “POST checkpoint codes” on page 9. 2. If no entry is found, replace the system-board and chassis assembly.
Page 98 Description FRU/action A02-03x Correctable error threshold exceeded. 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 “POST checkpoint codes” on page 9. 2.
Page 99 Description FRU/action A02-13x I/O Host Bridge address/data 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 “POST checkpoint codes” on page 9. 2.
Page 100 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 “POST checkpoint codes” on page 9. 2.
Page 101 Description FRU/action A05-04x System shutdown due to voltage outside 1. Check the BladeCenter management module event normal range. log; if an error was recorded by the system or if a checkpoint code is displayed on the console, see “POST checkpoint codes” on page 9. 2.
Page 102 Description FRU/action A05-14x System shutdown due to power fault with an 1. Check the BladeCenter management module event unspecified cause. log; if an error was recorded by the system or if a checkpoint code is displayed on the console, see “POST checkpoint codes”...
Page 103 Description FRU/action A0D-07x Internal service processor firmware error or 1. Check the BladeCenter management module event incorrect version. log; if an error was recorded by the system or if a checkpoint code is displayed on the console, see “POST checkpoint codes” on page 9. 2.
Page 104 Description FRU/action A0D-31x Error detected while handling an 1. Check the BladeCenter management module event attention/interrupt from the system hardware. log; if an error was recorded by the system or if a checkpoint code is displayed on the console, see “POST checkpoint codes”...
Page 105 Description FRU/action A10-210 The processor has been deconfigured. The 1. Check the BladeCenter management module event system is operating in degraded mode. log; if an error was recorded by the system or if a checkpoint code is displayed on the console, see “POST checkpoint codes”...
Page 106 Description FRU/action A11-510 Resource has been deconfigured and is no 1. Schedule maintenance; the system is operating in a longer in use due to a trend toward an degraded mode. unrecoverable error. 2. Check the BladeCenter management module event log for an entry around this time. If no entry is found, replace the system-board and chassis assembly.
Page 107 Description FRU/action A12-05x A non-critical error has been detected, a 1. Check the BladeCenter management module event memory address error (invalid address or log; if an error was recorded by the system or if a access attempt). checkpoint code is displayed on the console, see “POST checkpoint codes”...
Page 108 Description FRU/action A12-13x A non-critical error has been detected, a I/O 1. Check the BladeCenter management module event host bridge address/data parity error. log; if an error was recorded by the system or if a checkpoint code is displayed on the console, see “POST checkpoint codes”...
Page 109 Description FRU/action A13-04x A non-critical error has been detected, an I/O 1. Check the BladeCenter management module event bridge/device internal error. log; if an error was recorded by the system or if a checkpoint code is displayed on the console, see “POST checkpoint codes”...
Page 110 Description FRU/action A13-14x A non-critical error has been detected, an I/O 1. Check the BladeCenter management module event expansion bus time-out error. log; if an error was recorded by the system or if a checkpoint code is displayed on the console, see “POST checkpoint codes”...
Page 111 Description FRU/action A15-07x Sensor indicates a power supply has failed. 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 “POST checkpoint codes” on page 9. 2.
Page 112 Description FRU/action A15-21x Over temperature condition. 1. Make sure that: a. The room ambient temperature is within the system operating environment. b. There is unrestricted air flow around the system. c. All system covers are closed. d. There are no fan failures 2.
Page 113 Description FRU/action A1D-04x A non-critical error has been detected, an 1. Check the BladeCenter management module event internal service processor memory error. log; if an error was recorded by the system or if a checkpoint code is displayed on the console, see “POST checkpoint codes”...
Page 114 Description FRU/action A1D-18x A non-critical error has been detected, a 1. Check the BladeCenter management module event service processor detected NVRAM error. log; if an error was recorded by the system or if a checkpoint code is displayed on the console, see “POST checkpoint codes”...
Page 115 Description FRU/action A1D-31x A non-critical error has been detected: Error 1. Check the BladeCenter management module event detected while handling an attention/interrupt log; if an error was recorded by the system or if a from the system hardware. checkpoint code is displayed on the console, see “POST checkpoint codes”...
Page 116 Description FRU/action A24-000 Spurious interrupts on shared interrupt level 1. Check the BladeCenter management module event have exceeded threshold log. If an error was recorded by the system or if a checkpoint code is displayed on the console, see “POST checkpoint codes” on page 9. 2.
Page 117 Description and action ssss-108 ssss The bus test failed. 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 “POST checkpoint codes” on page 9. 2.
Page 118 Description and action ssss-122 ssss A SCSI reservation conflict 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 “POST checkpoint codes” on page 9. 2.
Page 119 The ventilation holes in the blade server bezel are not blocked. v The management module event log is not reporting any system environmental warnings. 2. If the problem remains, call IBM support. ssss-140 Error log analysis indicates poor signal quality.
Page 120: Failing Function Codes
Failing function codes Failing function codes (FFCs) represent functions within the system unit. Note: When replacing a component, perform system verification for the component (see “Using the diagnostics program” on page 111). Description and notes 1. Battery Note: After replacing the battery, make sure that: a.
Page 121 Description and notes System-board and chassis assembly System-board and chassis assembly (System/SP interface logic problem) System-board and chassis assembly (I2C primary) System-board and chassis assembly (I2C secondary) System-board and chassis assembly (VPD module) System-board and chassis assembly (Power controller) System-board and chassis assembly (Fan sensor problem) System-board and chassis assembly (Thermal sensor problem) System-board and chassis assembly (Voltage sensor problem) System-board and chassis assembly (Serial port controller problem)
Page 122: Checkout Procedure
Checkout procedure The checkout procedure is the sequence of tasks that you should follow to diagnose a problem in the blade server. About the checkout procedure Before performing the checkout procedure for diagnosing hardware problems, review the following information: v Read the safety information that begins on page vii. v The firmware diagnostic program provides the primary methods of testing the major components of the blade server.
Page 123 4. Check the BladeCenter management module event log. If an error was recorded by the system, see “Attention codes” on page 34 or “Error codes” on page 37. 5. If no error was recorded, or if the login prompt appears and you still suspect a problem, continue to Step 003 .
Page 124: Verifying The Partition Configuration
Step 007 Perform the following steps: 1. Use the management-module Web interface to make sure that the device from which you load the standalone diagnostics is set as the first device in the blade server boot sequence. 2. Turn off the blade server and wait 45 seconds before proceeding.
Page 125: Starting Standalone Diagnostics From A Cd
AIX operating system cannot start the concurrent diagnostics program. The latest version of the standalone diagnostics can be downloaded from the World Wide Web at http://www14.software.ibm.com/webapp/set2/sas/f/diags/home.html. 1. Verify with the system administrator and systems users that the blade server may be shut down.
Page 126: Starting Standalone Diagnostics From A Nim Server
Starting standalone diagnostics from a NIM server Perform the following steps to start the standalone diagnostics from a network installation management (NIM) server. Note: Refer to the Network Installation Management Guide and Reference for information about configuring the blade server as a NIM server client. 1.
Page 127: Using The Diagnostics Program
Using the diagnostics program This section provides the basic procedures for running the diagnostics program. 1. Start the diagnostics from the AIX operating system, from a CD, or from a management server (see “Starting AIX concurrent diagnostics” on page 108, “Starting standalone diagnostics from a CD”...
Page 128: 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 and network boot attempts. When booting from a CD, watch for a blinking activity LED on the CD or DVD drive.
Page 129: Troubleshooting Tables
3. If the boot fails, try a known-good bootable CD. 4. If possible, try to boot another blade server in the BladeCenter unit to verify that the CD or DVD drive is functional. v If the CD boots on the second server, replace the system-board and chassis assembly in the JS21 blade server you were originally trying to boot.
Page 130: Cd Or Dvd Drive Problems
CD or DVD drive problems v Follow the suggested actions in the order in which they are listed in the Action column until the problem is solved. v See Chapter 3, “Parts listing, Types 7988 and 8844,” on page 137 to determine which components are CRUs and which components are FRUs.
Page 131: Diskette Drive Problems
Diskette drive problems v Follow the suggested actions in the order in which they are listed in the Action column until the problem is solved. v See Chapter 3, “Parts listing, Types 7988 and 8844,” on page 137 to determine which components are CRUs and which components are FRUs.
Page 132: Hard Disk Drive Problems
Hard disk drive problems v Follow the suggested actions in the order in which they are listed in the Action column until the problem is solved. v See Chapter 3, “Parts listing, Types 7988 and 8844,” on page 137 to determine which components are CRUs and which components are FRUs.
Page 133: Keyboard Problems
Keyboard problems v Follow the suggested actions in the order in which they are listed in the Action column until the problem is solved. v See Chapter 3, “Parts listing, Types 7988 and 8844,” on page 137 to determine which components are CRUs and which components are FRUs.
Page 134: Memory Problems
Memory problems v Follow the suggested actions in the order in which they are listed in the Action column until the problem is solved. v See Chapter 3, “Parts listing, Types 7988 and 8844,” on page 137 to determine which components are CRUs and which components are FRUs.
Page 135: Monitor Or Video Problems
Monitor or video problems Some IBM monitors have their own self-tests. If you suspect a problem with your monitor, see the documentation that comes with the monitor for instructions for testing and adjusting the monitor. If you cannot diagnose the problem, call for service.
Page 136: Network Connection Problems
v Follow the suggested actions in the order in which they are listed in the Action column until the problem is solved. v See Chapter 3, “Parts listing, Types 7988 and 8844,” on page 137 to determine which components are CRUs and which components are FRUs.
Page 137: Optional Device Problems
If an action step is preceded by “(Trained service technician only),” that step must be performed only by a trained service technician. Symptom Action An IBM optional device that was 1. Make sure that: just installed does not work. ®...
Page 138: Power Problems
Power problems v Follow the suggested actions in the order in which they are listed in the Action column until the problem is solved. v See Chapter 3, “Parts listing, Types 7988 and 8844,” on page 137 to determine which components are CRUs and which components are FRUs.
Page 139: Service Processor Problems
Service processor problems v Follow the suggested actions in the order in which they are listed in the Action column until the problem is solved. v See Chapter 3, “Parts listing, Types 7988 and 8844,” on page 137 to determine which components are CRUs and which components are FRUs.
Page 140: Light Path Diagnostics
Light path diagnostics Light path diagnostics is a system of LEDs on the control panel and on the system board of the blade server. When an error occurs, LEDs are lit throughout the blade server. By viewing the LEDs in a particular order, you can often identify the source of the error.
Page 141: Light Path Diagnostics Leds
The following illustration shows the locations of the system board error LEDs. DIMM 1 error LED (CR40) System-management processor error LED (CR27) DIMM 2 error LED (CR45) NMI error LED (CR17) Temperature error LED (CR16) DIMM 3 error LED (CR46) System board error LED (CR20) DIMM 4 error LED (CR53) Microprocessor 1 error LED (CR19)
Page 142 v Follow the suggested actions in the order in which they are listed in the Action column until the problem is solved. v See Chapter 3, “Parts listing, Types 7988 and 8844,” on page 137 to determine which components are CRUs and which components are FRUs.
Page 143: Firmware Problem Isolation
Firmware problem isolation To isolate a firmware problem, complete the following steps in the order in which they are listed until the problem is solved. Step 001 Perform the following steps: 1. If the blade server is operating, shut down the operating system and turn off the blade server.
Page 144: Recovering The Temp Image From The Perm Image
Statement 21: CAUTION: Hazardous energy is present when the blade server is connected to the power source. Always replace the blade cover before installing the blade server. 6. Replace the cover (see “Installing the blade server cover” on page 146), reinstall the blade server in the BladeCenter unit (see “Installing the blade server in a BladeCenter unit”...
Page 145: Verifying The System Firmware Levels
Statement 21: CAUTION: Hazardous energy is present when the blade server is connected to the power source. Always replace the blade cover before installing the blade server. f. Replace the cover (see “Installing the blade server cover” on page 146), reinstall the blade server in the BladeCenter unit (see “Installing the blade server in a BladeCenter unit”...
Page 146: Solving Shared Bladecenter Resource Problems
Solving shared BladeCenter resource problems Problems with BladeCenter shared resources might appear to be in the blade server. The following sections provide procedures to help you isolate blade server problems from shared BladeCenter resource problems. If the problem is thought to be with a shared resource, see the Problem Determination and Service Guide or the Hardware Maintenance Manual and Troubleshooting Guide for your BladeCenter unit and other BladeCenter component documentation for additional...
Page 147: Media Tray Problems
Media tray problems To check for problems with the media tray (removable media drives and USB ports), complete the following steps until the problem is solved: 1. Make sure that: v The media-tray select button LED on the front of the blade server is lit, indicating that the blade server is connected to the shared media tray.
Page 148 6. For problems affecting one or more of the removable media drives: a. Reseat the following components: 1) Removable-media drive cable (if applicable) 2) Removable-media drive 3) Media tray cable (if applicable) 4) Media tray b. Replace the following components one at a time, in the order shown, restarting the blade server each time: 1) Removable-media drive cable (if applicable) 2) Media tray cable (if applicable)
Page 149: Network Connection Problems
Network connection problems To check for network connection problems, complete the following steps until the problem is solved: 1. Make sure that: v The network cables are securely connected to the I/O module. v Power configuration of the BladeCenter unit supports the I/O module configuration.
Page 150: Video Problems
The monitor works with another blade server. v Some IBM monitors have their own self-tests. If you suspect a problem with the monitor, see the information that comes with the monitor for instructions for adjusting and testing the monitor. If the monitor self-tests show that the monitor is working correctly, consider the location of the monitor.
Page 151: Solving Undetermined Problems
Solving undetermined problems Note: When you are diagnosing a problem in the JS21 Type 7988 or 8844 blade server, you must determine whether the problem is in the blade server or in the BladeCenter unit. v If all of the blade servers have the same symptom, it is probably a BladeCenter unit problem;...
Page 152: Calling Ibm For Service
Calling IBM for service See Appendix A, “Getting help and technical assistance,” on page 171 for information about calling IBM for service. When you call for service, have as much of the following information available as possible: v Machine type and model...
Page 153: Chapter 3. Parts Listing, Types 7988 And 8844
Replaceable components are of three types: v Tier 1 customer replaceable unit (CRU): Replacement of Tier 1 CRUs is your responsibility. If IBM installs a Tier 1 CRU at your request, you will be charged for the installation. v Tier 2 customer replaceable unit: You may install a Tier 2 CRU yourself or request IBM to install it, at no additional charge, under the type of warranty service that is designated for your blade server.
Page 154 CRU No. CRU No. Index Description FRU No. (Tier 1) (Tier 2) Cover (all models) 42D8680 Bracket, expansion (all models) 32R2451 Memory, 512 MB DDR2, PC2-3200, 400 MHz (model 31x) 39M5820 Memory, 512 MB DDR2, PC2-3200, 400 MHz (option) 39M5820 Memory, 512 MB DDR2, PC2-4200, 533 MHz (option) 41Y2706 Memory, 1 GB DDR2, PC2-3200, 400 MHz (models 41x, 51x)
Page 155 CRU No. CRU No. Index Description FRU No. (Tier 1) (Tier 2) Gummo Gigabit Ethernet assembly (option) 46M5963 Infiniband expansion card (option) 26K6459 Infiniband expansion card, four-port (option) 32R1763 Kit, miscellaneous 32R2451 Label, FRU list (all models) 32R2434 Label, OEM (Type 7988) 44T5707 Label, system service (all models) 32R2433...
Page 156 BladeCenter JS21 Types 7988 and 8844: Problem Determination and Service Guide...
Page 157: Chapter 4. Removing And Replacing Blade Server Components
Replaceable components are of three types: v Tier 1 customer replaceable unit (CRU): Replacement of Tier 1 CRUs is your responsibility. If IBM installs a Tier 1 CRU at your request, you will be charged for the installation. v Tier 2 customer replaceable unit: You may install a Tier 2 CRU yourself or request IBM to install it, at no additional charge, under the type of warranty service that is designated for your blade server.
Page 158: System Reliability Guidelines
System reliability guidelines To help ensure proper cooling and system reliability, observe the following guidelines: v Make sure that microprocessor socket 2 always contains either a microprocessor heat sink filler or a microprocessor and heat sink. If the blade server has only one microprocessor, it must be installed in the microprocessor socket 1.
Page 159: Removing The Blade Server From A Bladecenter Unit
Removing the blade server from a BladeCenter unit Attention: v To maintain proper system cooling, do not operate the BladeCenter unit without a blade server, expansion unit, or blade filler installed in each blade bay. v Note the bay number. Reinstalling a blade server into a different bay than the one from which it was removed could have unintended consequences.
Page 160: Installing The Blade Server In A Bladecenter Unit
Installing the blade server in a BladeCenter unit To install a blade server in a BladeCenter unit, complete the following steps. Release handles (open) Statement 21: CAUTION: Hazardous energy is present when the blade server is connected to the power source.
Page 161: Removing And Replacing Tier 1 Crus
Removing and replacing Tier 1 CRUs Replacement of Tier 1 CRUs is your responsibility. If IBM installs a Tier 1 CRU at your request, you will be charged for the installation. The illustrations in this document might differ slightly from your hardware.
Page 162: Installing The Blade Server Cover
Installing the blade server cover To install the blade server cover, complete the following steps. Cover pins Blade-cover release Blade-cover release Statement 21: CAUTION: Hazardous energy is present when the blade server is connected to the power source. Always replace the blade cover before installing the blade server. Important: The blade server cannot be inserted into the BladeCenter unit until the cover is installed and closed.
Page 163: Removing The Bezel Assembly
Removing the bezel assembly To remove the bezel assembly, complete the following steps. Bezel-assembly release Bezel-assembly release Bezel Control-panel assembly connector Control-panel cable 1. Read the safety information that begins on page vii and “Installation guidelines” on page 141. 2. If the blade server is installed in a BladeCenter unit, remove it (see “Removing the blade server from a BladeCenter unit”...
Page 164: Installing The Bezel Assembly
Installing the bezel assembly To install the bezel assembly, complete the following steps. Bezel-assembly release Bezel-assembly release Bezel Control-panel assembly connector Control-panel cable 1. Connect the control-panel cable to the control-panel connector on the system board. 2. Carefully slide the bezel assembly onto the blade server until it clicks into place. 3.
Page 165: Removing A Sas Hard Disk Drive
Removing a SAS hard disk drive To remove a SAS hard disk drive, complete the following steps. SAS hard disk drives Release levers 1. Read the safety information that begins on page vii and “Installation guidelines” on page 141. 2. If the blade server is installed in a BladeCenter unit, remove it (see “Removing the blade server from a BladeCenter unit”...
Page 166: Installing A Sas Hard Disk Drive
Installing a SAS hard disk drive To install a SAS hard disk drive, complete the following steps. SAS hard disk drives Release levers 1. Identify the location in which the hard disk drive will be installed. Attention: Do not press on the top of the drive. Pressing the top could damage the drive.
Page 167: Removing A Memory Module
Removing a memory module To remove a dual-inline memory module (DIMM), complete the following steps. DIMM Retaining clip 1. Read the safety information that begins on page vii and “Installation guidelines” on page 141. 2. If the blade server is installed in a BladeCenter unit, remove it (see “Removing the blade server from a BladeCenter unit”...
Page 168: Installing A Memory Module
Installing a memory module Note: If you are replacing a faulty DIMM, make sure that the replacement DIMM is the correct type of memory. If you are adding DIMMs, install the DIMMs in the sequence shown in the following table. See the Installation and User’s Guide for additional information about the type of memory that is compatible with the blade server.
Page 169: Removing And Installing An I/O Expansion Card
Removing and installing an I/O expansion card The following sections describe how to remove and install small-form-factor and standard-form-factor I/O expansion cards in the blade server. Removing a small-form-factor expansion card To remove a small-form-factor expansion card, complete the following steps. Expansion card 1.
Page 170 Installing a small-form-factor expansion card To install a small-form-factor expansion card, complete the following steps. Expansion card 1. Touch the static-protective package that contains the expansion card to any unpainted metal surface on the BladeCenter unit or any unpainted metal surface on any other grounded rack component;...
Page 171 Removing a standard-form-factor expansion card To remove a standard-form-factor expansion card, complete the following steps. Expansion card 1. Read the safety information that begins on page vii and “Installation guidelines” on page 141. 2. If the blade server is installed in a BladeCenter unit, remove it (see “Removing the blade server from a BladeCenter unit”...
Page 172 Installing a standard-form-factor expansion card To install a standard-form-factor expansion card, complete the following steps. Expansion card 1. Touch the static-protective package that contains the expansion card to any unpainted metal surface on the BladeCenter unit or any unpainted metal surface on any other grounded rack component;...
Page 173: Removing The Battery
To order replacement batteries, call 1-800-426-7378 within the United States, and 1-800-465-7999 or 1-800-465-6666 within Canada. Outside the U.S. and Canada, call your IBM marketing representative or authorized reseller. v After you replace the battery, you must reconfigure the blade server and reset the system date and time.
Page 174 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 175: Removing A Hard Disk Drive Tray
Removing a hard disk drive tray To remove a hard disk drive tray, complete the following steps. Hard disk drive tray 1. Read the safety information that begins on page vii and “Installation guidelines” on page 141. 2. If the blade server is installed in a BladeCenter unit, remove it (see “Removing the blade server from a BladeCenter unit”...
Page 176: Installing A Hard Disk Drive Tray
Installing a hard disk drive tray To install a hard disk drive tray, complete the following steps. Hard disk drive tray 1. Place the drive tray into position on the system board and install the four screws to secure it. 2.
Page 177: Removing The Expansion Bracket
Removing the expansion bracket To remove the expansion bracket, complete the following steps. Expansion bracket 1. Read the safety information that begins on page vii and “Installation guidelines” on page 141. 2. If the blade server is installed in a BladeCenter unit, remove it (see “Removing the blade server from a BladeCenter unit”...
Page 178: Installing The Expansion Bracket
Installing the expansion bracket To install the expansion bracket, complete the following steps. Expansion bracket 1. Place the expansion bracket in position on the system board and install the two scews that secure it to the system board. 2. Install the standard-form-factor expansion card, if one was removed (see “Installing a standard-form-factor expansion card”...
Page 179: Removing And Replacing Tier 2 Crus
Removing and replacing Tier 2 CRUs You may install a Tier 2 CRU yourself or request IBM to install it, at no additional charge, under the type of warranty service that is designated for the blade server. Replacing the system-board and chassis assembly This section describes how to replace the system-board and chassis assembly.
Page 180 10. Write the machine type, model number, and serial number of the blade server on the repair identification (RID) tag that comes with the replacement system-board and chassis assembly. This information is on the identification label that is behind the control-panel door on the front of the blade server. Important: v Completing the information on the RID tag ensures future entitlement for service.
Page 181: Chapter 5. Configuration Information And Instructions
BIOS, service processor, and diagnostic firmware levels are consistent for all blade servers within the BladeCenter unit. You can download the latest firmware from the IBM Support Web site at http://www.ibm.com/systems/support/. Install the updated firmware using the...
Page 182: Using The Sms Utility
Using the SMS utility This section provides the instructions to start the SMS utility and descriptions of the menu choices. Starting the SMS utility Complete the following steps to start the SMS utility: 1. Turn on or restart the blade server, and establish an SOL session with it (see the BladeCenter Management Module Command-Line Interface Reference Guide or BladeCenter Serial-Over-LAN Setup Guide for more information.
Page 183: Configuring The Gigabit Ethernet Controllers
Ethernet controllers, see the Broadcom NetXtreme Gigabit Ethernet Software CD that comes with the blade server. For updated information about configuring the controllers, see http://www.ibm.com/systems/ support/. The Ethernet controllers in your blade server support failover, which provides automatic redundancy for the Ethernet controllers.
Page 184: Creating A Ce Login
Creating a CE login If the blade server is running an AIX operating system, it is recommended that a customer engineer (CE) login be created that enables a user to perform operating system commands that are required to service the system without being logged in as a root user.
Page 185: Configuring A Sas Raid Array
Updating IBM Director If you plan to use IBM Director to manage the blade server, you must check for the latest applicable IBM Director updates and interim fixes. To install the IBM Director updates and any other applicable updates and interim fixes, complete the following steps.
Page 186: Checking The Status Of The Media Tray
CIC replaced before you install a JS21 Type 7988 or 8844 blade server in the BladeCenter unit. To have the CIC replaced, call the IBM Support Center, report the CIC as a failed part, and request replacement with the latest CIC FRU. The IBM Support Center team will evaluate the problem, determine which replacement part is required, and send the applicable part.
Page 187: 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...
Page 188: Software Service And Support
Software service and support Through IBM Support Line, you can get telephone assistance, for a fee, with usage, configuration, and software problems with BladeCenter products. For information about which products are supported by Support Line in your country or region, see http://www.ibm.com/services/sl/products/.
Page 189: Appendix B. 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 190: Trademarks
Trademarks The following terms are trademarks of International Business Machines Corporation in the United States, other countries, or both: Active Memory TechConnect Active PCI IBM (logo) Tivoli Active PCI-X IntelliStation Tivoli Enterprise NetBAY Update Connector Alert on LAN Netfinity Wake on LAN...
Page 191: 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 192: Battery Return Program
United States, go to http://www.ibm.com/ibm/environment/ products/batteryrecycle.shtml or contact your local waste disposal facility. In the United States, IBM has established a return process for reuse, recycling, or proper disposal of used IBM sealed lead acid, nickel cadmium, nickel metal hydride, and battery packs from IBM equipment.
Page 193 For proper collection and treatment, contact your local IBM representative. For California: Perchlorate material – special handling may apply. See http://www.dtsc.ca.gov/ hazardouswaste/perchlorate/.
Page 194: 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 195: Taiwanese Class A Warning Statement
This is a Class A product. In a domestic environment this product may cause radio interference in which case the user may be required to take adequate measures. European Community contact: IBM Technical Regulations Pascalstr. 100, Stuttgart, Germany 70569 Telephone: 0049 (0)711 785 1176 Fax: 0049 (0)711 785 1283 E-mail: tjahn@de.ibm.com...
Page 196 BladeCenter JS21 Types 7988 and 8844: Problem Determination and Service Guide...
Page 197: Index
10 error symptoms Chipkill memory 3 CD drive, DVD drive 114 Class A electronic emission notice 178 general 115 committing TEMP image 129 hard disk drive 116 components intermittent 116 system board 7 © Copyright IBM Corp. 2007...
Page 198 149 memory module installing 152 removing 151 I/O expansion card specifications 3 daughter card 153 supported 3 IBM Director memory problems 118 updating 169 memory specifications 3 Web sites 169 microprocessor image problems 118 PERM 128...
Page 199 notes, important 174 removing (continued) notices expansion bracket 161 electronic emission 178 hard disk drive tray 159 FCC, Class A 178 I/O expansion card 153 product recycling 175 memory module 151 notices and statements 2 SAS hard disk drive 149 small-form-factor expansion card 153 standard-form-factor expansion card 155 repair identification (RID) tag 164...
Page 200 United States electronic emission Class A notice 178 United States FCC Class A notice 178 Universal Serial Bus (USB) problems 123 updating firmware 165 IBM Director 169 utility default boot list 165 open firmware prompt 165 stored boot list 165...
Page 202 Part Number: 49Y0169 Printed in USA (1P) P/N: 49Y0169...

IBM BladeCenter JS21 Types 8844 Service Manual

Safety

Chapter 1. Introduction

Chapter 2. Diagnostics

Chapter 3. Parts Listing, Types 7988 and 8844

Chapter 4. Removing and Replacing Blade Server Components

Chapter 5. Configuration Information and Instructions

Appendix A. Getting Help and Technical Assistance

Appendix B. Notices

Quick Links

Related Manuals for IBM BladeCenter JS21 Types 8844

Summary of Contents for IBM BladeCenter JS21 Types 8844

Table of Contents