Page 1 BladeCenter JS12 Type 7998 Problem Determination and Service Guide...
Page 3 BladeCenter JS12 Type 7998 Problem Determination and Service Guide...
Page 4 Appendix B, “Notices,” on page 289 and the Warranty and Support Information document for your blade server type on the Documentation CD. Second Edition (November 2009) © Copyright International Business Machines Corporation 2008, 2009. US Government Users Restricted Rights – Use, duplication or disclosure restricted by GSA ADP Schedule Contract with IBM Corp.
Page 5: Table Of Contents
. 141 Calling IBM for service . . 232 Using the SRN tables . . 142 101-711 through FFC-725 SRNs . 142 Chapter 3. Parts listing, Type 7998 A00-FF0 through A24-xxx SRNs . . 159 © Copyright IBM Corp. 2008, 2009...
Page 6 Installing a memory module . . 251 Hardware service and support . 287 Removing the management card . . 253 IBM Taiwan product service . . 287 Installing the management card . . 254 Entering vital product data . . 256 Appendix B.
Page 7: Safety
Vor der Installation dieses Produkts die Sicherheitshinweise lesen. Prima di installare questo prodotto, leggere le Informazioni sulla Sicurezza. Les sikkerhetsinformasjonen (Safety Information) før du installerer dette produktet. Antes de instalar este produto, leia as Informações sobre Segurança. © Copyright IBM Corp. 2008, 2009...
Page 8: Guidelines For Trained Service Technicians
Make sure that the insulation is not 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 computer for any obvious unsafe conditions, such as metal filings, contamination, water or other liquid, or signs of fire or smoke damage.
Page 9: Guidelines For Servicing Electrical Equipment
Guidelines for servicing electrical equipment Observe the guidelines for servicing electrical equipment. v Check the area for electrical hazards such as moist floors, nongrounded power extension cords, and missing safety grounds. v Use only approved tools and test equipment. Some hand tools have handles that are covered with a soft material that does not provide insulation from live electrical current.
Page 10: Safety Statements
Safety statements Important: Each caution and danger statement in this documentation is labeled with a number. This number is used to cross reference an English-language caution or danger statement with translated versions of the caution or danger statement in the Safety Information document. For example, if a caution statement is labeled, ″Statement 1,″...
Page 11 Statement 2 CAUTION: When replacing the lithium battery, use only IBM Part Number 16G8095 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 12 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 13 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 14 JS12 Type 7998: Problem Determination and Service Guide...
Page 15: 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 16: Notices And Statements In This Documentation
Features and specifications Features and specifications of the IBM BladeCenter JS12 Type 7998 blade server are summarized in this overview. JS12 Type 7998: Problem Determination and Service Guide...
Page 17 The JS12 blade server is used in one of the following IBM BladeCenter units: BladeCenter E (8677), BladeCenter H (8852), BladeCenter HT (8740 and 8750), BladeCenter S (8886), and BladeCenter T (8720 and 8730) units. Notes: v Power, cooling, removable-media drives, external ports, and advanced system management are provided by the BladeCenter unit.
Page 18: Supported Dimms
Supported DIMMs The BladeCenter JS12 Type 7998 blade server contains eight memory connectors for industry-standard registered, dual-inline-memory modules (RDIMMs). The DIMMS are very low profile, which means that each DIMM has a height of 18.3 millimeters (mm). Total memory can range from a minimum of 2 gigabytes (GB) to a maximum of 64 GB.
Page 19: Blade Server Control Panel Buttons And Leds
Blade server control panel buttons and LEDs Blade server control panel buttons and LEDs provide operational controls and status indicators. Note: Figure 1 shows the control-panel door in the closed (normal) position. To access the power-control button, you must open the control-panel door. Media-tray select button Keyboard/video select button Information LED...
Page 20 The information LED can be turned off through the Web interface of the management module or through IBM Director Console. Blade-error LED: When this amber LED is lit, it indicates that a system error has occurred in the blade server.
Page 21: Turning On The Blade Server
Lit continuously: The blade server has power and is turned on. Note: The enhanced service processor (BMC) can take as long as three minutes to initialize after you install the BladeCenter JS12 blade server, at which point the LED begins to flash slowly.
Page 22: Turning Off The Blade Server
v Start the blade server automatically when power is restored after a power failure. If a power failure occurs, the BladeCenter unit and then the blade server can start automatically when power is restored. You must configure the blade server to restart through the management module.
Page 23: System-Board Layouts
System-board layouts Illustrations show the connectors and LEDs on the system board. The illustrations might differ slightly from your hardware. System-board connectors Blade server components attach to the connectors on the system board. Figure 2 shows the connectors on the system board in the blade server. DIMM 1 (P1-C1) DIMM 2 (P1-C2) Control panel...
Page 24 Remove the blade server from the BladeCenter unit, open the cover to see any error LEDs that were turned on during error processing, and use Figure 3 to identify the failing component. Front SAS drive System board Power LED error LED (P1-D1) error LED (P1) (always on when plugged in) DIMM 1 error LED...
Page 25: Chapter 2. Diagnostics
Error checking hardware ranges from parity error detection coupled with processor instruction retry and bus retry, to ECC correction on caches and system buses. IBM hardware error checkers have these distinct attributes: v Continuous monitoring of system operations to detect potential calculation errors...
Page 26: Diagnostic Tools
The AIX-based stand-alone Diagnostics CD is in the ship package and is also available from the IBM Web site. Boot the CD from a CD drive or from an AIX network installation manager (NIM) server if the blade server cannot boot to an operating system, no matter which operating system is installed.
Page 27: Collecting Dump Data
Note: If you power off the blade through the management module while the service processor is performing a dump, platform dump data is lost. You might be asked to retrieve a dump to send it to IBM Support for analysis. The location of the dump data varies per operating system platform.
Page 28: Location Codes
v Collect an AIX dump from the /var/adm/platform directory. v Collect a Linux dump from the /var/log/dump directory. v Collect an Integrated Virtualization Manager (IVM) dump from the IVM-managed JS12 blade server through the Manage Dumps task in the IVM console.
Page 29: Reference Codes
To use reference codes effectively, use them in conjunction with other service and support procedures. The BladeCenter JS12 Type 7998 blade server produces several types of codes. Progress codes: The power-on self-test (POST) generates eight-digit status codes that are known as checkpoints or progress codes, which are recorded in the management-module event log.
Page 30: System Reference Codes (Srcs)
System reference codes (SRCs) System reference codes indicate a server hardware or software problem that can originate in hardware, in firmware, or in the operating system. A blade server component generates an error code when it detects a problem. An SRC identifies the component that generated the error code and describes the error.
Page 31: 1Xxxyyyy Srcs
Dxxxxxxx - Dump checkpoint (must hang to indicate an error) To find a description of a SRC that is not listed in this JS12 blade server documentation, refer to the POWER6 Reference Code Lookup page at https://www-01.ibm.com/servers/resourcelink/lib03030.nsf/pages/eClipzML/ $file/refCode.html. 1xxxyyyy SRCs The 1xxxyyyy system reference codes are system power control network (SPCN) reference codes.
Page 32 Table 5. 1xxxyyyy SRCs (continued) v Follow the suggested actions in the order in which they are listed in the Action column until the problem is solved. If an action solves the problem, then you can stop performing the remaining actions. v See Chapter 3, “Parts listing, Type 7998,”...
Page 33 Table 5. 1xxxyyyy SRCs (continued) v Follow the suggested actions in the order in which they are listed in the Action column until the problem is solved. If an action solves the problem, then you can stop performing the remaining actions. v See Chapter 3, “Parts listing, Type 7998,”...
Page 34 Table 5. 1xxxyyyy SRCs (continued) v Follow the suggested actions in the order in which they are listed in the Action column until the problem is solved. If an action solves the problem, then you can stop performing the remaining actions. v See Chapter 3, “Parts listing, Type 7998,”...
Page 35 Table 5. 1xxxyyyy SRCs (continued) v Follow the suggested actions in the order in which they are listed in the Action column until the problem is solved. If an action solves the problem, then you can stop performing the remaining actions. v See Chapter 3, “Parts listing, Type 7998,”...
Page 36: 6Xxxyyyy Srcs
Table 5. 1xxxyyyy SRCs (continued) v Follow the suggested actions in the order in which they are listed in the Action column until the problem is solved. If an action solves the problem, then you can stop performing the remaining actions. v See Chapter 3, “Parts listing, Type 7998,”...
Page 37 Table 6. 6xxxyyyy SRCs (continued) v Follow the suggested actions in the order in which they are listed in the Action column until the problem is solved. If an action solves the problem, then you can stop performing the remaining actions. v See Chapter 3, “Parts listing, Type 7998,”...
Page 38: A1Xxyyyy Service Processor Srcs
Table 6. 6xxxyyyy SRCs (continued) v Follow the suggested actions in the order in which they are listed in the Action column until the problem is solved. If an action solves the problem, then you can stop performing the remaining actions. v See Chapter 3, “Parts listing, Type 7998,”...
Page 39: Aa00E1A8 To Aa260005 Partition Firmware Attention Codes
A700yyyy Licensed internal code SRCs An A7xx SRC is a licensed internal code SRC that is deprecated in favor of a corresponding B7xx SRC. B7xx SRCs are described in “B700xxxx Licensed internal code SRCs” on page 39. Table 9. A700yyyy Licensed internal code SRCs Attention code Description Action...
Page 40 Table 10. AA00E1A8 to AA260005 Partition firmware attention codes (continued) v Follow the suggested actions in the order in which they are listed in the Action column until the problem is solved. If an action solves the problem, then you can stop performing the remaining actions. v See Chapter 3, “Parts listing, Type 7998,”...
Page 41 Table 10. AA00E1A8 to AA260005 Partition firmware attention codes (continued) v Follow the suggested actions in the order in which they are listed in the Action column until the problem is solved. If an action solves the problem, then you can stop performing the remaining actions. v See Chapter 3, “Parts listing, Type 7998,”...
Page 42: Bxxxxxxx Service Processor Early Termination Srcs
To find a description of a SRC that is not listed in this JS12 blade server documentation, refer to the POWER6 Reference Code Lookup page at https://www-01.ibm.com/servers/resourcelink/lib03030.nsf/pages/eClipzML/ $file/refCode.html. Table 11 describes error codes that might occur if POST detects a problem. The description also includes suggested actions to correct the problem.
Page 43: B200Xxxx Logical Partition Srcs
B200xxxx Logical partition SRCs A B200xxxx system reference code (SRC) is an error code that is related to logical partitioning. Table 12 describes error codes that might be displayed if POST detects a problem. The description also includes suggested actions to correct the problem. Note: For problems persisting after completing the suggested actions, see “Checkout procedure”...
Page 44 Table 12. B200xxxx Logical partition SRCs (continued) v Follow the suggested actions in the order in which they are listed in the Action column until the problem is solved. If an action solves the problem, then you can stop performing the remaining actions. v See Chapter 3, “Parts listing, Type 7998,”...
Page 45 Table 12. B200xxxx Logical partition SRCs (continued) v Follow the suggested actions in the order in which they are listed in the Action column until the problem is solved. If an action solves the problem, then you can stop performing the remaining actions. v See Chapter 3, “Parts listing, Type 7998,”...
Page 46 Table 12. B200xxxx Logical partition SRCs (continued) v Follow the suggested actions in the order in which they are listed in the Action column until the problem is solved. If an action solves the problem, then you can stop performing the remaining actions. v See Chapter 3, “Parts listing, Type 7998,”...
Page 47 Table 12. B200xxxx Logical partition SRCs (continued) v Follow the suggested actions in the order in which they are listed in the Action column until the problem is solved. If an action solves the problem, then you can stop performing the remaining actions. v See Chapter 3, “Parts listing, Type 7998,”...
Page 48 Table 12. B200xxxx Logical partition SRCs (continued) v Follow the suggested actions in the order in which they are listed in the Action column until the problem is solved. If an action solves the problem, then you can stop performing the remaining actions. v See Chapter 3, “Parts listing, Type 7998,”...
Page 49 600A A problem occurred during the Contact IBM support, as described in Appendix A, startup of a partition. The partition “Getting help and technical assistance,” on page 285. could not reserve the memory required for IPL.
Page 50 Table 12. B200xxxx Logical partition SRCs (continued) v Follow the suggested actions in the order in which they are listed in the Action column until the problem is solved. If an action solves the problem, then you can stop performing the remaining actions. v See Chapter 3, “Parts listing, Type 7998,”...
Page 51 Table 12. B200xxxx Logical partition SRCs (continued) v Follow the suggested actions in the order in which they are listed in the Action column until the problem is solved. If an action solves the problem, then you can stop performing the remaining actions. v See Chapter 3, “Parts listing, Type 7998,”...
Page 52 Verify that processor resources are assigned to the partition. 8160 A problem occurred during the Contact IBM support, as described in Appendix A, migration of a partition. “Getting help and technical assistance,” on page 285. 8161 A problem occurred during the Contact IBM support, as described in Appendix A, migration of a partition.
Page 53: B700Xxxx Licensed Internal Code Srcs
Table 12. B200xxxx Logical partition SRCs (continued) v Follow the suggested actions in the order in which they are listed in the Action column until the problem is solved. If an action solves the problem, then you can stop performing the remaining actions. v See Chapter 3, “Parts listing, Type 7998,”...
Page 54 No immediate action is necessary. storage condition Continue running the system normally. At the earliest convenient time or service window, work with IBM Support to collect a platform dump and restart the system; then, go to “Isolating firmware problems” on page 222. 0201 System firmware detected an error.
Page 55 Table 13. B700xxxx Licensed internal code SRCs (continued) v Follow the suggested actions in the order in which they are listed in the Action column until the problem is solved. If an action solves the problem, then you can stop performing the remaining actions. v See Chapter 3, “Parts listing, Type 7998,”...
Page 56 B1xxxxxx errors, or if correcting the errors does not correct the problem, contact IBM support to reset the server firmware settings. Attention: Resetting the server firmware settings results in the loss of all of the partition data that is stored on the service processor.
Page 57 Table 13. B700xxxx Licensed internal code SRCs (continued) v Follow the suggested actions in the order in which they are listed in the Action column until the problem is solved. If an action solves the problem, then you can stop performing the remaining actions. v See Chapter 3, “Parts listing, Type 7998,”...
Page 58 B700 xxxx Error Codes Description Action 5302 An unsupported Preferred Operating Work with IBM support to select a supported System was detected. Preferred Operating System; then, re-IPL the system. The Preferred Operating System specified is not supported. The IPL will not continue.
Page 59 Table 13. B700xxxx Licensed internal code SRCs (continued) v Follow the suggested actions in the order in which they are listed in the Action column until the problem is solved. If an action solves the problem, then you can stop performing the remaining actions. v See Chapter 3, “Parts listing, Type 7998,”...
Page 60 Table 13. B700xxxx Licensed internal code SRCs (continued) v Follow the suggested actions in the order in which they are listed in the Action column until the problem is solved. If an action solves the problem, then you can stop performing the remaining actions. v See Chapter 3, “Parts listing, Type 7998,”...
Page 61 Table 13. B700xxxx Licensed internal code SRCs (continued) v Follow the suggested actions in the order in which they are listed in the Action column until the problem is solved. If an action solves the problem, then you can stop performing the remaining actions. v See Chapter 3, “Parts listing, Type 7998,”...
Page 62: Ba000010 To Ba400002 Partition Firmware Srcs
BA000010 to BA400002 Partition firmware SRCs The power-on self-test (POST) might display an error code that the partition firmware detects. Try to correct the problem with the suggested action. Table 14 describes error codes that might be displayed if POST detects a problem. The description also includes suggested actions to correct the problem.
Page 63 Table 14. BA000010 to BA400002 Partition firmware SRCs (continued) v Follow the suggested actions in the order in which they are listed in the Action column until the problem is solved. If an action solves the problem, then you can stop performing the remaining actions. v See Chapter 3, “Parts listing, Type 7998,”...
Page 64 Table 14. BA000010 to BA400002 Partition firmware SRCs (continued) v Follow the suggested actions in the order in which they are listed in the Action column until the problem is solved. If an action solves the problem, then you can stop performing the remaining actions. v See Chapter 3, “Parts listing, Type 7998,”...
Page 65 “Replacing the Tier 2 system-board and chassis assembly” on page 274. BA00E830 Failure when initializing ibm,event-scan 1. Go to “Checkout procedure” on page 186. 2. Replace the system-board and chassis assembly, as described in “Replacing the Tier 2 system-board and chassis assembly”...
Page 66 Table 14. BA000010 to BA400002 Partition firmware SRCs (continued) v Follow the suggested actions in the order in which they are listed in the Action column until the problem is solved. If an action solves the problem, then you can stop performing the remaining actions. v See Chapter 3, “Parts listing, Type 7998,”...
Page 67 Table 14. BA000010 to BA400002 Partition firmware SRCs (continued) v Follow the suggested actions in the order in which they are listed in the Action column until the problem is solved. If an action solves the problem, then you can stop performing the remaining actions. v See Chapter 3, “Parts listing, Type 7998,”...
Page 68 Table 14. BA000010 to BA400002 Partition firmware SRCs (continued) v Follow the suggested actions in the order in which they are listed in the Action column until the problem is solved. If an action solves the problem, then you can stop performing the remaining actions. v See Chapter 3, “Parts listing, Type 7998,”...
Page 69 Table 14. BA000010 to BA400002 Partition firmware SRCs (continued) v Follow the suggested actions in the order in which they are listed in the Action column until the problem is solved. If an action solves the problem, then you can stop performing the remaining actions. v See Chapter 3, “Parts listing, Type 7998,”...
Page 70 Table 14. BA000010 to BA400002 Partition firmware SRCs (continued) v Follow the suggested actions in the order in which they are listed in the Action column until the problem is solved. If an action solves the problem, then you can stop performing the remaining actions. v See Chapter 3, “Parts listing, Type 7998,”...
Page 71 Table 14. BA000010 to BA400002 Partition firmware SRCs (continued) v Follow the suggested actions in the order in which they are listed in the Action column until the problem is solved. If an action solves the problem, then you can stop performing the remaining actions. v See Chapter 3, “Parts listing, Type 7998,”...
Page 72 Table 14. BA000010 to BA400002 Partition firmware SRCs (continued) v Follow the suggested actions in the order in which they are listed in the Action column until the problem is solved. If an action solves the problem, then you can stop performing the remaining actions. v See Chapter 3, “Parts listing, Type 7998,”...
Page 73 Table 14. BA000010 to BA400002 Partition firmware SRCs (continued) v Follow the suggested actions in the order in which they are listed in the Action column until the problem is solved. If an action solves the problem, then you can stop performing the remaining actions. v See Chapter 3, “Parts listing, Type 7998,”...
Page 74 Table 14. BA000010 to BA400002 Partition firmware SRCs (continued) v Follow the suggested actions in the order in which they are listed in the Action column until the problem is solved. If an action solves the problem, then you can stop performing the remaining actions. v See Chapter 3, “Parts listing, Type 7998,”...
Page 75 Table 14. BA000010 to BA400002 Partition firmware SRCs (continued) v Follow the suggested actions in the order in which they are listed in the Action column until the problem is solved. If an action solves the problem, then you can stop performing the remaining actions. v See Chapter 3, “Parts listing, Type 7998,”...
Page 76 Table 14. BA000010 to BA400002 Partition firmware SRCs (continued) v Follow the suggested actions in the order in which they are listed in the Action column until the problem is solved. If an action solves the problem, then you can stop performing the remaining actions. v See Chapter 3, “Parts listing, Type 7998,”...
Page 77 Table 14. BA000010 to BA400002 Partition firmware SRCs (continued) v Follow the suggested actions in the order in which they are listed in the Action column until the problem is solved. If an action solves the problem, then you can stop performing the remaining actions. v See Chapter 3, “Parts listing, Type 7998,”...
Page 78 Table 14. BA000010 to BA400002 Partition firmware SRCs (continued) v Follow the suggested actions in the order in which they are listed in the Action column until the problem is solved. If an action solves the problem, then you can stop performing the remaining actions. v See Chapter 3, “Parts listing, Type 7998,”...
Page 79 Table 14. BA000010 to BA400002 Partition firmware SRCs (continued) v Follow the suggested actions in the order in which they are listed in the Action column until the problem is solved. If an action solves the problem, then you can stop performing the remaining actions. v See Chapter 3, “Parts listing, Type 7998,”...
Page 80 Table 14. BA000010 to BA400002 Partition firmware SRCs (continued) v Follow the suggested actions in the order in which they are listed in the Action column until the problem is solved. If an action solves the problem, then you can stop performing the remaining actions. v See Chapter 3, “Parts listing, Type 7998,”...
Page 81 Table 14. BA000010 to BA400002 Partition firmware SRCs (continued) v Follow the suggested actions in the order in which they are listed in the Action column until the problem is solved. If an action solves the problem, then you can stop performing the remaining actions. v See Chapter 3, “Parts listing, Type 7998,”...
Page 82 Table 14. BA000010 to BA400002 Partition firmware SRCs (continued) v Follow the suggested actions in the order in which they are listed in the Action column until the problem is solved. If an action solves the problem, then you can stop performing the remaining actions. v See Chapter 3, “Parts listing, Type 7998,”...
Page 83 Table 14. BA000010 to BA400002 Partition firmware SRCs (continued) v Follow the suggested actions in the order in which they are listed in the Action column until the problem is solved. If an action solves the problem, then you can stop performing the remaining actions. v See Chapter 3, “Parts listing, Type 7998,”...
Page 84 Table 14. BA000010 to BA400002 Partition firmware SRCs (continued) v Follow the suggested actions in the order in which they are listed in the Action column until the problem is solved. If an action solves the problem, then you can stop performing the remaining actions. v See Chapter 3, “Parts listing, Type 7998,”...
Page 85 Table 14. BA000010 to BA400002 Partition firmware SRCs (continued) v Follow the suggested actions in the order in which they are listed in the Action column until the problem is solved. If an action solves the problem, then you can stop performing the remaining actions. v See Chapter 3, “Parts listing, Type 7998,”...
Page 86 Table 14. BA000010 to BA400002 Partition firmware SRCs (continued) v Follow the suggested actions in the order in which they are listed in the Action column until the problem is solved. If an action solves the problem, then you can stop performing the remaining actions. v See Chapter 3, “Parts listing, Type 7998,”...
Page 87 Table 14. BA000010 to BA400002 Partition firmware SRCs (continued) v Follow the suggested actions in the order in which they are listed in the Action column until the problem is solved. If an action solves the problem, then you can stop performing the remaining actions. v See Chapter 3, “Parts listing, Type 7998,”...
Page 88 Table 14. BA000010 to BA400002 Partition firmware SRCs (continued) v Follow the suggested actions in the order in which they are listed in the Action column until the problem is solved. If an action solves the problem, then you can stop performing the remaining actions. v See Chapter 3, “Parts listing, Type 7998,”...
Page 89 Table 14. BA000010 to BA400002 Partition firmware SRCs (continued) v Follow the suggested actions in the order in which they are listed in the Action column until the problem is solved. If an action solves the problem, then you can stop performing the remaining actions. v See Chapter 3, “Parts listing, Type 7998,”...
Page 90 Table 14. BA000010 to BA400002 Partition firmware SRCs (continued) v Follow the suggested actions in the order in which they are listed in the Action column until the problem is solved. If an action solves the problem, then you can stop performing the remaining actions. v See Chapter 3, “Parts listing, Type 7998,”...
Page 91 Table 14. BA000010 to BA400002 Partition firmware SRCs (continued) v Follow the suggested actions in the order in which they are listed in the Action column until the problem is solved. If an action solves the problem, then you can stop performing the remaining actions. v See Chapter 3, “Parts listing, Type 7998,”...
Page 92 Error code Description Action BA180100 The FDDI adapter Fcode driver is not IBM may produce a compatible driver in the supported on this server. future, but does not guarantee one. BA180101 Stack underflow from fibre-channel 1. Go to “Checkout procedure” on page 186.
Page 93 Table 14. BA000010 to BA400002 Partition firmware SRCs (continued) v Follow the suggested actions in the order in which they are listed in the Action column until the problem is solved. If an action solves the problem, then you can stop performing the remaining actions. v See Chapter 3, “Parts listing, Type 7998,”...
Page 94 Table 14. BA000010 to BA400002 Partition firmware SRCs (continued) v Follow the suggested actions in the order in which they are listed in the Action column until the problem is solved. If an action solves the problem, then you can stop performing the remaining actions. v See Chapter 3, “Parts listing, Type 7998,”...
Page 95 Table 14. BA000010 to BA400002 Partition firmware SRCs (continued) v Follow the suggested actions in the order in which they are listed in the Action column until the problem is solved. If an action solves the problem, then you can stop performing the remaining actions. v See Chapter 3, “Parts listing, Type 7998,”...
Page 96 Failed to reboot the system after a Restart the blade server. firmware flash update BA278009 The operating system’s server firmware Go to the IBM download site at update management tools are www14.software.ibm.com/webapp/set2/sas/ incompatible with this system. f/lopdiags/home.html to download the latest version of the service aids package for Linux.
Page 97 Table 14. BA000010 to BA400002 Partition firmware SRCs (continued) v Follow the suggested actions in the order in which they are listed in the Action column until the problem is solved. If an action solves the problem, then you can stop performing the remaining actions. v See Chapter 3, “Parts listing, Type 7998,”...
Page 98 Table 14. BA000010 to BA400002 Partition firmware SRCs (continued) v Follow the suggested actions in the order in which they are listed in the Action column until the problem is solved. If an action solves the problem, then you can stop performing the remaining actions. v See Chapter 3, “Parts listing, Type 7998,”...
Page 99 Table 14. BA000010 to BA400002 Partition firmware SRCs (continued) v Follow the suggested actions in the order in which they are listed in the Action column until the problem is solved. If an action solves the problem, then you can stop performing the remaining actions. v See Chapter 3, “Parts listing, Type 7998,”...
Page 100 Table 14. BA000010 to BA400002 Partition firmware SRCs (continued) v Follow the suggested actions in the order in which they are listed in the Action column until the problem is solved. If an action solves the problem, then you can stop performing the remaining actions. v See Chapter 3, “Parts listing, Type 7998,”...
Page 101 Table 14. BA000010 to BA400002 Partition firmware SRCs (continued) v Follow the suggested actions in the order in which they are listed in the Action column until the problem is solved. If an action solves the problem, then you can stop performing the remaining actions. v See Chapter 3, “Parts listing, Type 7998,”...
Page 102: Post Progress Codes (Checkpoints)
Table 14. BA000010 to BA400002 Partition firmware SRCs (continued) v Follow the suggested actions in the order in which they are listed in the Action column until the problem is solved. If an action solves the problem, then you can stop performing the remaining actions. v See Chapter 3, “Parts listing, Type 7998,”...
Page 103: C1001F00 To C1645300 Service Processor Checkpoints
The management module can display the most recent 32 SRCs and time stamps. Manually refresh the list to update it. Select Blade Service Data → blade_name in the management module to see a list of the 32 most recent SRCs. Table 15.
Page 104 Table 16. C1001F00 to C1645300 checkpoints (continued) 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 solved. If an action solves the problem, you can stop performing the remaining actions.
Page 105 Table 16. C1001F00 to C1645300 checkpoints (continued) 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 solved. If an action solves the problem, you can stop performing the remaining actions.
Page 106 Table 16. C1001F00 to C1645300 checkpoints (continued) 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 solved. If an action solves the problem, you can stop performing the remaining actions.
Page 107 Table 16. C1001F00 to C1645300 checkpoints (continued) 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 solved. If an action solves the problem, you can stop performing the remaining actions.
Page 108 Table 16. C1001F00 to C1645300 checkpoints (continued) 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 solved. If an action solves the problem, you can stop performing the remaining actions.
Page 109 Table 16. C1001F00 to C1645300 checkpoints (continued) 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 solved. If an action solves the problem, you can stop performing the remaining actions.
Page 110 Table 16. C1001F00 to C1645300 checkpoints (continued) 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 solved. If an action solves the problem, you can stop performing the remaining actions.
Page 111 Table 16. C1001F00 to C1645300 checkpoints (continued) 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 solved. If an action solves the problem, you can stop performing the remaining actions.
Page 112 Table 16. C1001F00 to C1645300 checkpoints (continued) 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 solved. If an action solves the problem, you can stop performing the remaining actions.
Page 113: C2001000 To C20082Ff Virtual Service Processor Checkpoints
Table 16. C1001F00 to C1645300 checkpoints (continued) 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 solved. If an action solves the problem, you can stop performing the remaining actions.
Page 114 The virtual service processor can start a variety of operating systems. Some codes are specific to an operating system and therefore, do not apply to all operating systems. Table 17 lists the progress codes that might be displayed during the power-on self-test (POST), along with suggested actions to take if the system hangs on the progress code.
Page 115 Table 17. C2001000 to C20082FF checkpoints (continued) 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 solved. If an action solves the problem, you can stop performing the remaining actions.
Page 116 Table 17. C2001000 to C20082FF checkpoints (continued) 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 solved. If an action solves the problem, you can stop performing the remaining actions.
Page 117 Table 17. C2001000 to C20082FF checkpoints (continued) 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 solved. If an action solves the problem, you can stop performing the remaining actions.
Page 118 Table 17. C2001000 to C20082FF checkpoints (continued) 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 solved. If an action solves the problem, you can stop performing the remaining actions.
Page 119 Table 17. C2001000 to C20082FF checkpoints (continued) 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 solved. If an action solves the problem, you can stop performing the remaining actions.
Page 120 Table 17. C2001000 to C20082FF checkpoints (continued) 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 solved. If an action solves the problem, you can stop performing the remaining actions.
Page 121 Table 17. C2001000 to C20082FF checkpoints (continued) 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 solved. If an action solves the problem, you can stop performing the remaining actions.
Page 122 Table 17. C2001000 to C20082FF checkpoints (continued) 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 solved. If an action solves the problem, you can stop performing the remaining actions.
Page 123: Ipl Status Progress Codes
The IPL status progress codes topic describes IPL status progress codes C3yx, C5yx, C500, C6xx, and C600 for an initialization of the IBM i operating system. C700xxxx Server firmware IPL status checkpoints: A server that stalls during an initial program load (IPL) of the server firmware indicates a problem with the server firmware code.
Page 124: Ca000000 To Ca2799Ff Partition Firmware Checkpoints
Table 18 shows the form of the C700xxxx progress codes, where xxxx can be any number or letter. 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 solved. If an action solves the problem, you can stop performing the remaining actions.
Page 125 Table 19. CA000000 to CA2799FF checkpoints (continued) 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 solved. If an action solves the problem, you can stop performing the remaining actions.
Page 126 Table 19. CA000000 to CA2799FF checkpoints (continued) 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 solved. If an action solves the problem, you can stop performing the remaining actions.
Page 127 Table 19. CA000000 to CA2799FF checkpoints (continued) 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 solved. If an action solves the problem, you can stop performing the remaining actions.
Page 128 Table 19. CA000000 to CA2799FF checkpoints (continued) 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 solved. If an action solves the problem, you can stop performing the remaining actions.
Page 129 Table 19. CA000000 to CA2799FF checkpoints (continued) 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 solved. If an action solves the problem, you can stop performing the remaining actions.
Page 130 Table 19. CA000000 to CA2799FF checkpoints (continued) 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 solved. If an action solves the problem, you can stop performing the remaining actions.
Page 131 Table 19. CA000000 to CA2799FF checkpoints (continued) 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 solved. If an action solves the problem, you can stop performing the remaining actions.
Page 132 Table 19. CA000000 to CA2799FF checkpoints (continued) 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 solved. If an action solves the problem, you can stop performing the remaining actions.
Page 133 Table 19. CA000000 to CA2799FF checkpoints (continued) 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 solved. If an action solves the problem, you can stop performing the remaining actions.
Page 134 “Replacing the Tier 2 system-board and chassis assembly” on page 274. CA00E198 The system is rebooting to enact changes Go to “Boot problem resolution” on page 193. that were specified in ibm,client-architecture-support JS12 Type 7998: Problem Determination and Service Guide...
Page 135 Table 19. CA000000 to CA2799FF checkpoints (continued) 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 solved. If an action solves the problem, you can stop performing the remaining actions.
Page 136 Table 19. CA000000 to CA2799FF checkpoints (continued) 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 solved. If an action solves the problem, you can stop performing the remaining actions.
Page 137 Table 19. CA000000 to CA2799FF checkpoints (continued) 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 solved. If an action solves the problem, you can stop performing the remaining actions.
Page 138 Table 19. CA000000 to CA2799FF checkpoints (continued) 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 solved. If an action solves the problem, you can stop performing the remaining actions.
Page 139 Table 19. CA000000 to CA2799FF checkpoints (continued) 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 solved. If an action solves the problem, you can stop performing the remaining actions.
Page 140 Table 19. CA000000 to CA2799FF checkpoints (continued) 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 solved. If an action solves the problem, you can stop performing the remaining actions.
Page 141 Table 19. CA000000 to CA2799FF checkpoints (continued) 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 solved. If an action solves the problem, you can stop performing the remaining actions.
Page 142 Table 19. CA000000 to CA2799FF checkpoints (continued) 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 solved. If an action solves the problem, you can stop performing the remaining actions.
Page 143 Table 19. CA000000 to CA2799FF checkpoints (continued) 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 solved. If an action solves the problem, you can stop performing the remaining actions.
Page 144 Table 19. CA000000 to CA2799FF checkpoints (continued) 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 solved. If an action solves the problem, you can stop performing the remaining actions.
Page 145: D1001Xxx To D1Xx3Fff Service Processor Dump Codes
Table 19. CA000000 to CA2799FF checkpoints (continued) 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 solved. If an action solves the problem, you can stop performing the remaining actions.
Page 146 Table 20. D1001xxx to D1xx3FFF dump codes 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 solved. If an action solves the problem, you can stop performing the remaining actions.
Page 147 Table 20. D1001xxx to D1xx3FFF dump codes (continued) 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 solved. If an action solves the problem, you can stop performing the remaining actions.
Page 148 Table 20. D1001xxx to D1xx3FFF dump codes (continued) 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 solved. If an action solves the problem, you can stop performing the remaining actions.
Page 149 Table 20. D1001xxx to D1xx3FFF dump codes (continued) 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 solved. If an action solves the problem, you can stop performing the remaining actions.
Page 150 Table 20. D1001xxx to D1xx3FFF dump codes (continued) 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 solved. If an action solves the problem, you can stop performing the remaining actions.
Page 151 Table 20. D1001xxx to D1xx3FFF dump codes (continued) 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 solved. If an action solves the problem, you can stop performing the remaining actions.
Page 152: D1Xx3Y01 To D1Xx3Yf2 Service Processor Dump Codes
D1xx3y01 to D1xx3yF2 Service processor dump codes: These D1xx3yxx service processor dump codes use the format: D1xx3yzz, where xx indicates the cage or node ID that the dump component is processing, y increments from 0 to F to indicate that the system is not hung, and zz indicates the command being processed.
Page 153 Table 21. D1xx3y01 to D1xx3yF2 checkpoints (continued) 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 solved. If an action solves the problem, you can stop performing the remaining actions.
Page 154: D1Xx900C To D1Xxc003 Service Processor Power-Off Checkpoints
Table 21. D1xx3y01 to D1xx3yF2 checkpoints (continued) 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 solved. If an action solves the problem, you can stop performing the remaining actions.
Page 155: Service Request Numbers (Srns)
Table 22. D1xx900C to D1xxC003 checkpoints (continued) 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 solved. If an action solves the problem, you can stop performing the remaining actions.
Page 156: Using The Srn Tables
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 Service and productivity tools for Linux on POWER systems site. Using the SRN tables The service request number (SRN) list is in numerical sequence.
Page 157 Table 23. 101-711 through FFC-725 SRNs (continued) Description and Action 103-151 The time-of-day battery failed. 1. Go to “Removing the battery” on page 267 to start the battery replacement procedure. 2. Go to “Installing the battery” on page 268 to complete the procedure. 109-200 The system crashed while you running it.
Page 158 Table 23. 101-711 through FFC-725 SRNs (continued) Description and Action 651-140 Display Character test failed. Note: Diagnostic will provide this SRN but there is no action to be taken. Do not perform operator panel test from diagnostics. 651-151 152 2E2 Sensor indicates a voltage is outside the normal range.
Page 159 Table 23. 101-711 through FFC-725 SRNs (continued) Description and Action 651-613 External cache ECC single-bit error. Go to “Performing the checkout procedure” on page 187. 651-614 System bus time-out error. Go to “Performing the checkout procedure” on page 187. 651-615 Time-out error waiting for I/O.
Page 160 Table 23. 101-711 through FFC-725 SRNs (continued) Description and Action 651-66A Correctable error threshold exceeded. Go to “Performing the checkout procedure” on page 187. 651-66B Correctable error threshold exceeded. Go to “Performing the checkout procedure” on page 187. 651-674 Failed memory module. Go to “Performing the checkout procedure” on page 187. 651-675 Failed memory module.
Page 161 Table 23. 101-711 through FFC-725 SRNs (continued) Description and Action 651-734 Intermediate or system bus data parity error. Go to “Performing the checkout procedure” on page 187. 651-735 Intermediate or system bus time-out error. Go to “Performing the checkout procedure” on page 187. 651-736 Intermediate or system bus time-out error.
Page 162 Table 23. 101-711 through FFC-725 SRNs (continued) Description and Action 651-786 304 214 Uncorrectable memory error. Go to “Performing the checkout procedure” on page 187. 651-789 2CD 214 Uncorrectable memory error. Go to “Performing the checkout procedure” on page 187. 651-78A 2CE 214 Uncorrectable memory error.
Page 163 Table 23. 101-711 through FFC-725 SRNs (continued) Description and Action 651-841 152 2E2 Sensor detected a voltage outside of the normal range. Go to “Performing the checkout procedure” on page 187. 651-842 Sensor detected an abnormally high internal temperature. Make sure that: 1.
Page 164 Table 23. 101-711 through FFC-725 SRNs (continued) Description and Action 652-731 A non-critical error has been detected: intermediate or system bus address parity error. Schedule deferred maintenance. Go to “Performing the checkout procedure” on page 187. 652-732 A non-critical error has been detected: intermediate or system bus data parity error. Schedule deferred maintenance.
Page 165 Table 23. 101-711 through FFC-725 SRNs (continued) Description and Action 815-100 The floating-point processor test failed. Go to “Performing the checkout procedure” on page 187. 815-101 Floating point processor failed. Go to “Performing the checkout procedure” on page 187. 815-102 Floating point processor failed.
Page 166 Table 23. 101-711 through FFC-725 SRNs (continued) Description and Action 887-113 External loopback (twisted pair) parity test failed. Go to “Performing the checkout procedure” on page 187. 887-114 Ethernet loopback (twisted pair) fairness test failed. Go to “Performing the checkout procedure”...
Page 167 Table 23. 101-711 through FFC-725 SRNs (continued) Description and Action 252B-101 252B Adapter configuration error. 1. Check the BladeCenter management-module event log. If an error was recorded by the system, see “POST progress codes (checkpoints)” on page 88. 2. Replace any parts reported by the diagnostic program. 3.
Page 168 Table 23. 101-711 through FFC-725 SRNs (continued) Description and Action 252B-718 252B 293 Temporary PCI bus error detected by adapter. 1. Check the BladeCenter management-module event log. If an error was recorded by the system, see “POST progress codes (checkpoints)” on page 88. 2.
Page 169 Table 23. 101-711 through FFC-725 SRNs (continued) Description and Action 254E-702 254E 221 Error log analysis indicates permanent adapter failure is reported on the other port of this adapter. Go to “Performing the checkout procedure” on page 187. 2567–xxx USB integrated system-board and chassis assembly. Go to “Performing the checkout procedure”...
Page 170 Table 23. 101-711 through FFC-725 SRNs (continued) Description and Action 256D-702 256D 221 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, see “POST progress codes (checkpoints)”...
Page 171 Table 23. 101-711 through FFC-725 SRNs (continued) Description and Action 2604-705 2604 Error Log Analysis indicates that a parity error has been detected for the Fibre Channel adapter card. The adapter must be replaced immediately. Failure to do so could result in data being read or written incorrectly.
Page 172 Table 23. 101-711 through FFC-725 SRNs (continued) Description and Action 2607-706 2607 Error Log Analysis indicates that a fatal hardware error has occurred for the Fibre Channel adapter card. This adapter was successfully taken off-line. It will remain off-line until reconfigured or the system is rebooted.
Page 173: A00-Ff0 Through A24-Xxx Srns
Table 23. 101-711 through FFC-725 SRNs (continued) Description and Action 2640-114 2640 IDE disk diagnostic failure. Go to “Performing the checkout procedure” on page 187. 2640-115 2640 2631 IDE disk error on open or configuring device system-board and chassis assembly - IDE controller.
Page 174 Note: Some SRNs in this sequence might have 4 rather than 3 digits after the dash (–). Table 24 shows the meaning of an x in any of the following SRNs, such as A01-00x. Table 24. Meaning of the last character (x) after the hyphen Number Meaning Replace all FRUs listed...
Page 175 Table 25. A00-FF0 through A24-xxx SRNs (continued) Description FRU/action A01-06x Time-out error waiting for I/O. 1. Check the BladeCenter management-module event log; if an error was recorded by the system, see “POST progress codes (checkpoints)” on page 88. 2. If no entry is found, replace the system-board and chassis assembly.
Page 176 Table 25. A00-FF0 through A24-xxx SRNs (continued) Description FRU/action A02-06x Memory Data error (Bad data going to 1. Check the BladeCenter management-module memory). event log; if an error was recorded by the system, see “POST progress codes (checkpoints)” on page 88. 2.
Page 177 Table 25. A00-FF0 through A24-xxx SRNs (continued) Description FRU/action A03-05x I/O Error on non-PCI bus. 1. Check the BladeCenter management-module event log; if an error was recorded by the system, see “POST progress codes (checkpoints)” on page 88. 2. If no entry is found, replace the system-board and chassis assembly.
Page 178 Table 25. A00-FF0 through A24-xxx SRNs (continued) Description FRU/action A03-16x I/O Expansion unit not in an operating 1. Check the BladeCenter management-module state. event log; if an error was recorded by the system, see “POST progress codes (checkpoints)” on page 88. 2.
Page 179 Table 25. A00-FF0 through A24-xxx SRNs (continued) Description FRU/action A05-06x System shutdown due to abnormally 1. Make sure that: high internal temperature. a. The room ambient temperature is within the system operating environment. b. There is unrestricted air flow around the system.
Page 180 Table 25. A00-FF0 through A24-xxx SRNs (continued) Description FRU/action A05-21x System shutdown due to Over 1. Make sure that: temperature condition. a. The room ambient temperature is within the system operating environment. b. There is unrestricted air flow around the system.
Page 181 Table 25. A00-FF0 through A24-xxx SRNs (continued) Description FRU/action A0D-09x Service Processor error accessing Vital 1. Check the BladeCenter management-module Product Data EEPROM. event log; if an error was recorded by the system, see “POST progress codes (checkpoints)” on page 88. 2.
Page 182 Table 25. A00-FF0 through A24-xxx SRNs (continued) Description FRU/action A0D-36x Other IPL Diagnostic Error. 1. Check the BladeCenter management-module event log; if an error was recorded by the system, see “POST progress codes (checkpoints)” on page 88. 2. If no entry is found, replace the system-board and chassis assembly.
Page 183 Table 25. A00-FF0 through A24-xxx SRNs (continued) Description FRU/action A11-01x A non-critical error has been detected, a 1. Check the BladeCenter management-module CPU internal error. event log; if an error was recorded by the system, see “POST progress codes (checkpoints)” on page 88. 2.
Page 184 Table 25. A00-FF0 through A24-xxx SRNs (continued) Description FRU/action A11-550 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.
Page 185 Table 25. A00-FF0 through A24-xxx SRNs (continued) Description FRU/action A12-07x A non-critical error has been detected, a 1. Check the BladeCenter management-module memory bus/switch internal error. event log; if an error was recorded by the system, see “POST progress codes (checkpoints)”...
Page 186 Table 25. A00-FF0 through A24-xxx SRNs (continued) Description FRU/action A12-16x A non-critical error has been detected, a 1. Check the BladeCenter management-module system bus internal hardware/switch event log; if an error was recorded by the error. system, see “POST progress codes (checkpoints)”...
Page 187 Table 25. A00-FF0 through A24-xxx SRNs (continued) Description FRU/action A13-06x A non-critical error has been detected, a 1. Check the BladeCenter management-module mezzanine bus address parity error. event log; if an error was recorded by the system, see “POST progress codes (checkpoints)”...
Page 188 Table 25. A00-FF0 through A24-xxx SRNs (continued) Description FRU/action A13-16x A non-critical error has been detected, 1. Check the BladeCenter management-module an I/O expansion unit not in an event log; if an error was recorded by the operating state. system, see “POST progress codes (checkpoints)”...
Page 189 Table 25. A00-FF0 through A24-xxx SRNs (continued) Description FRU/action A15-12x Sensor detected redundant power 1. Check the BladeCenter management-module supply failure. event log; if an error was recorded by the system, see “POST progress codes (checkpoints)” on page 88. 2. If no entry is found, replace the system-board and chassis assembly.
Page 190 Table 25. A00-FF0 through A24-xxx SRNs (continued) Description FRU/action A15-22x Fan failure and Over temperature 1. Check the BladeCenter management-module condition. event log; if an error was recorded by the system, see “POST progress codes (checkpoints)” on page 88. 2. If no entry is found, replace the system-board and chassis assembly.
Page 191 Table 25. A00-FF0 through A24-xxx SRNs (continued) Description FRU/action A1D-05x A non-critical error has been detected, a 1. Check the BladeCenter management-module service processor error accessing special event log; if an error was recorded by the registers. system, see “POST progress codes (checkpoints)”...
Page 192 Table 25. A00-FF0 through A24-xxx SRNs (continued) Description FRU/action A1D-19x A non-critical error has been detected, a 1. Check the BladeCenter management-module service processor error accessing real event log; if an error was recorded by the time clock/time-of-day clock. system, see “POST progress codes (checkpoints)”...
Page 193 Table 25. A00-FF0 through A24-xxx SRNs (continued) Description FRU/action A1D-34x A non-critical error has been detected: 1. Check the BladeCenter management-module Wire Test Error. event log; if an error was recorded by the system, see “POST progress codes (checkpoints)” on page 88. 2.
Page 194: Ssss-102 Through Ssss-640 Srns For Scsi Devices
Table 25. A00-FF0 through A24-xxx SRNs (continued) Description FRU/action A24-xxx Spurious interrupts have exceeded 1. Check the BladeCenter management-module threshold. event log; if an error was recorded by the system, see “POST progress codes (checkpoints)” on page 88. 2. Replace part numbers reported by the diagnostic program.
Page 195 Table 26. ssss-102 through ssss-640 SRNs (continued) 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, see “POST progress codes (checkpoints)” on page 88. 2. Replace any parts reported by the diagnostic program. 3.
Page 196 Table 26. ssss-102 through ssss-640 SRNs (continued) 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, see “POST progress codes (checkpoints)” on page 88. 2.
Page 197 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 199 252B Error log analysis indicates poor signal quality.
Page 198: Failing Function Codes 151 Through 2D02
Failing function codes 151 through 2D02 Failing function codes (FFCs) identify a function within the system unit that is failing. Table 27 describes the component that each function code identifies. Note: When replacing a component, perform system verification for the component.
Page 199 Table 27. Failing function codes 151 through 2D02 (continued) Description and notes 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)
Page 200: Checkout Procedure
Error logs ™ The power-on self-test (POST), the POWER Hypervisor (PHYP), and the service processor write errors to the BladeCenter management module event log. Select the Monitors → Event Log option in the management module Web interface to view entries that are currently stored in the management-module event log. This log includes entries for events that are detected by the blade servers.
Page 201: Performing The Checkout Procedure
v If the blade server hangs on a POST checkpoint, see “POST progress codes (checkpoints)” on page 88. If the blade server is halted and no error message is displayed, see “Troubleshooting tables” on page 194 and “Solving undetermined problems” on page 231. v For intermittent problems, check the management-module event log and “POST progress codes (checkpoints)”...
Page 202 Step 005 Perform the following steps: Note: When possible, run AIX online diagnostics in concurrent mode. AIX online diagnostics perform more functions than the stand-alone Diagnostics. 1. Perform the AIX online diagnostics, see “Starting AIX concurrent diagnostics” on page 189. Record any diagnostic results and see the “Service request numbers (SRNs)”...
Page 203: Verifying The Partition Configuration
“Service request numbers (SRNs)” on page 141. This ends the Linux procedure. For more information about installing and using all supported operating systems, search the IBM Support Site. Verifying the partition configuration Perform this procedure if there is a configuration problem with the system or a logical partition.
Page 204: Starting Stand-Alone Diagnostics From A Cd
Starting stand-alone diagnostics from a CD Perform these procedures to start the stand-alone diagnostics from a CD. These procedures can be used if the blade server is running a Linux operating system or if an AIX operating system cannot start the concurrent diagnostics program. You can download the latest version of the stand-alone diagnostics from the Standalone Diagnostics CD page.
Page 205: Starting Stand-Alone Diagnostics From A Nim Server
Starting stand-alone diagnostics from a NIM server Perform this procedure to start the stand-alone diagnostics from a network installation management (NIM) server. Note: See Network Installation Management in the AIX Information Center for information about configuring the blade server as a NIM server client. Also see the Configuring the NIM Master and Creating Basic Installation Resources Web page.
Page 206: Using The Diagnostics Program
7. When testing is complete, press F3 until the Diagnostic Operating Instructions screen is displayed; then press F3 again to exit the diagnostic program. Using the diagnostics program Follow 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.
Page 207: Boot Problem Resolution
3. When testing is complete, press F3 until the Diagnostic Operating Instructions screen is displayed; then press F3 again to exit the diagnostic program. Boot problem resolution Depending on the boot device, a checkpoint might be displayed in the list of checkpoints in the management module for an extended period of time while the boot image is retrieved from the device.
Page 208: Troubleshooting Tables
3. If you are attempting to boot from the CD or DVD drive: a. From the BladeCenter management-module Web interface, make sure that the media tray is assigned to your blade server: Blade Tasks → Remote Control. b. Turn the blade server power off; then, turn it on and retry the boot operation.
Page 209: General Problems
If these symptoms relate to shared BladeCenter unit resources, see “Solving shared BladeCenter resource problems” on page 225. If you cannot find the problem in these tables, see “Running the diagnostics program” on page 189 for information about testing the blade server. If you have just added new software or a new optional device and the blade server is not working, complete the following steps before using the troubleshooting tables:...
Page 210: Intermittent Problems
Intermittent problems Identify intermittent problem symptoms and corrective actions. 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, Type 7998,” on page 235 to determine which components are CRUs and which components are FRUs.
Page 211: Management Module Service Processor Problems
Management module service processor problems Determine if a problem is a management module service processor problem and, if so, the corrective action to take. v Follow the suggested actions in the order in which they are listed in the Action column until the problem is solved.
Page 212: Microprocessor Problems
Monitor or video problems View monitor or video problem symptoms to find corrective actions. 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.
Page 213 Make sure that the monitor cable is connected to the video port on the you direct it to a working blade BladeCenter management module. Some IBM monitors have their own self-tests. If server, or goes blank when you 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 214: Network Connection Problems
Network connection problems Identify network connection problem symptoms and what corrective actions to take. 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, Type 7998,” on page 235 to determine which components are CRUs and which components are FRUs.
Page 215: 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 1. Make sure that: was just installed does not v The option is designed for the blade server. See the ServerProven list at work.
Page 216: Power Problems
Power problems Identify power problem symptoms and what corrective actions to take. 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, Type 7998,” on page 235 to determine which components are CRUs and which components are FRUs.
Page 217: Power Hypervisor (Phyp) Problems
3. Check the bus and I/O adapter allocations for the partition. Verify that the partition has load source and console I/O resources. 4. Check the IPL mode of the system or failing partition. 5. For further assistance, contact IBM Support. Chapter 2. Diagnostics...
Page 218 3. Install new memory DIMMs, as described in “Installing a memory module” on page 251. See “Supported DIMMs” on page 4 for more information. NEXTLVL Contact IBM Support. Symbolic CRU PIOCARD The hardware that 1. Collect the error log information.
Page 219: Service Processor Problems
Service processor problems The baseboard management controller (BMC) is a flexible service processor that provides error diagnostics with associated error codes, and fault isolation procedures for troubleshooting. Note: Resetting the service processor causes a POWER6 reset/reload, which generates a dump. The dump is recorded in the management module event log. The reset/reload dump occurs whenever the service processor resets, such as when resetting the service processor through the management module Web interface or through the management module command line interface.
Page 220 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, Type 7998,” on page 235 to determine which components are CRUs and which components are FRUs.
Page 221 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, Type 7998,” on page 235 to determine which components are CRUs and which components are FRUs.
Page 222 2. If the problem persists, replace the system board and chassis assembly, as described in “Replacing the Tier 2 system-board and chassis assembly” on page 274. FSPSP06 The service processor Contact IBM Support. reported a suspected intermittent problem. FSPSP07 The time of day has 1.
Page 223 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, Type 7998,” on page 235 to determine which components are CRUs and which components are FRUs.
Page 224 Collect the dump for support and power off and power on the blade server. 5. If an A1xx SRC has not remained more than 40 minutes, call IBM Support. FSPSP16 Save any error log Contact IBM Support.
Page 225 ID. Record the resource ID and be found in the Vital the model of the system. Product Data (VPD) 2. Call IBM Support to find out what CRU the resource ID represents. table. 3. Replace the CRU that the resource ID represents. The system has...
Page 226 1. Set the enclosure feature code using SMS, which automatically resets the service processor. 2. If the problem persists, call IBM Support. If you do not see your reason code listed, call IBM Support. JS12 Type 7998: Problem Determination and Service Guide...
Page 227 Action Procedure Code FSPSP34 The memory cards Install a pair of DIMMs on the BladeCenter JS12 Type 7998 blade server. are plugged in an Install the first pair in DIMM connectors 1 and 3. invalid configuration Look for the following error codes in order. Follow the procedure for the and cannot be used first code you find.
Page 228 PSI link. FSPSP48 A diagnostics If the CRUs called out before this procedure do not fix the problem, function detects an contact IBM Support. external processor interface problem. FSPSP49 A diagnostic function If the CRUs called out before this procedure do not fix the problem, detects an internal contact IBM Support.
Page 229 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, Type 7998,” on page 235 to determine which components are CRUs and which components are FRUs.
Page 230 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, Type 7998,” on page 235 to determine which components are CRUs and which components are FRUs.
Page 231: Software Problems
Software problems Use this information to recognize software problem symptoms and to take corrective actions. 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, Type 7998,” on page 235 to determine which components are CRUs and which components are FRUs.
Page 232: 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. If the control panel indicates an error, use the descriptions of the LEDs to diagnose the problem and take corrective action.
Page 233: Light Path Diagnostics Leds
Front SAS drive System board Power LED (always on when plugged in) error LED (P1-D1) error LED (P1) DIMM 1 error LED (P1-C1) DIMM 2 error LED (P1-C2) DIMM 3 error LED (P1-C3) DIMM 4 error LED (P1-C4) PCI-X expansion card error LED (P1-C10) DIMM 5 error LED (P1-C5)
Page 234 Table 32. Light path diagnostic LED descriptions (continued) 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, Type 7998,” on page 235 to determine which components are CRUs and which components are FRUs.
Page 235 Table 32. Light path diagnostic LED descriptions (continued) 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, Type 7998,” on page 235 to determine which components are CRUs and which components are FRUs.
Page 236: Isolating Firmware Problems
Isolating firmware problems You can use this procedure to isolate firmware problems. To isolate a firmware problem, follow the procedure until the problem is solved. 1. If the blade server is operating, shut down the operating system and turn off the blade server.
Page 237: Starting The Temp Image
To force the blade server to start the PERM (permanent) image, complete the following procedure. 1. Access the advanced management module menus. 2. Click Blade Tasks → Configuration → Boot Mode. 3. Click the appropriate JS12 blade server in the list of blade servers in the BladeCenter unit.
Page 238: Verifying The System Firmware Levels
1. Start the diagnostics program. See “Running the diagnostics program” on page 189. The online BladeCenter information center is available in the IBM Systems Information Center. 2. From the Function Selection menu, select Task Selection and press Enter.
Page 239: Solving Shared Bladecenter Resource Problems
4. From the Update and Manage System Flash menu, select Commit the Temporary Image and press Enter. 5. When the commit function is complete, press F3 until the Diagnostic Operating Instructions screen is displayed; then press F3 again to exit the diagnostic program.
Page 240: Solving Shared Keyboard Problems
12. Check for video problems, as described in “Solving shared video problems” on page 230. Solving shared keyboard problems Problems with BladeCenter shared resources might appear to be in the blade server, but might actually be a problem in a BladeCenter unit keyboard component.
Page 241 To check the general function of shared BladeCenter media tray resources, perform the following procedure. 1. Verify that the media-tray select button LED on the front of the blade server is lit. A lit media-tray select button LED shows that the blade server is connected to the shared media tray.
Page 242: Solving Shared Network Connection Problems
7. Troubleshoot one or more of the removable media drives if they are the only failing components. a. Reseat the following components: v Removable-media drive cable (if applicable) v Removable-media drive v Media tray cable (if applicable) v Media tray 8.
Page 243: Solving Shared Power Problems
4. Verify that the installation of the I/O-module type is supported by the BladeCenter unit and blade server hardware. 5. Verify that the I/O modules for the network interface are installed in the correct BladeCenter bays. 6. Verify that the I/O modules for the network interface are configured correctly. 7.
Page 244: Solving Shared Video Problems
Problems with BladeCenter shared resources might appear to be in the blade server, but might actually be a problem in a BladeCenter unit video component. 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.
Page 245: Solving Undetermined Problems
7. Replace the monitor cable, if applicable. 8. Replace the monitor. 9. Replace the management module. See the online information center or the Problem Determination and Service Guide or the Hardware Maintenance Manual and Troubleshooting Guide for your BladeCenter unit. If these steps do not resolve the problem, it is likely a problem with the blade server.
Page 246: Calling Ibm For Service
Calling IBM for service Call IBM for service after you collect as much as possible of the following information. Before calling for service, collect as much as possible of the following available...
Page 247 See Appendix A, “Getting help and technical assistance,” on page 285 for information about how to call IBM for service. Chapter 2. Diagnostics...
Page 248 JS12 Type 7998: Problem Determination and Service Guide...
Page 249: Chapter 3. Parts Listing, Type 7998
The parts listing identifies each replaceable part, part number, and replaceable component type. Figure 5 shows replaceable components that are available for the JS12 Type 7998 blade server. Figure 5. Parts illustration, BladeCenter JS12 Type 7998 © Copyright IBM Corp. 2008, 2009...
Page 250 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 251 CRU No. CRU No. Index Description FRU No. (Tier 1) (Tier 2) Label, Planar, heatsink, and system service 44T5733 Label, Universal warning 90P4799 Battery, 3.0 volt 16G8095 Chapter 3. Parts listing, Type 7998...
Page 252 JS12 Type 7998: Problem Determination and Service Guide...
Page 253: 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 254: System Reliability Guidelines
points on hot-swap components.) See the instructions for removing or installing a specific hot-swap component for any additional procedures that you might have to perform before you remove or install the component. v When you are finished working on the blade server, reinstall all safety shields, guards, labels, and ground wires.
Page 255: Returning A Device Or Component
Returning a device or component If you are instructed to return a device or component, follow all packaging instructions, and use any packaging materials for shipping that are supplied to you. Removing the blade server from a BladeCenter unit Remove the blade server from the BladeCenter unit to access options, connectors, and system-board indicators.
Page 256: Installing The Blade Server In A Bladecenter Unit
Always replace the blade server cover before installing the blade server. Perform the following procedure to install a blade server in a BladeCenter unit. 1. Go to http://www.ibm.com/systems/support/ to download the latest firmware for the blade server. Download the firmware so that you can use it later to update the blade server after you start it.
Page 257 2. Read “Safety” on page v and the “Installation guidelines” on page 239. 3. If you have not done so already, install any optional devices that you want, such as a SAS drive or memory modules. 4. Select the bay for the blade server. v See the online information or the Installation and User’s Guide that comes with your BladeCenter unit to verify that the bay you choose is powered.
Page 258: Removing And Replacing Tier 1 Crus
Removing and replacing Tier 1 CRUs Replacement of Tier 1 customer-replaceable units (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 documentation might differ slightly from your hardware.
Page 259: Installing And Closing The Blade Server Cover
3. Carefully lay the blade server on a flat, static-protective surface, with the cover side up. 4. Press the blade-cover release on each side of the blade server and lift the cover open. 5. Lay the cover flat, or lift it from the blade server and store it for future use. Statement 21 CAUTION: Hazardous energy is present when the blade server is connected to the power...
Page 260: Removing The Bezel Assembly
1. Read “Safety” on page v and the “Installation guidelines” on page 239. 2. Lower the cover so that the slots at the rear slide down onto the pins at the rear of the blade server. Before you close the cover, verify that all components are installed and seated correctly and that you have not left loose tools or parts inside the blade server.
Page 261: Installing The Bezel Assembly
Installing the bezel assembly Install the bezel assembly. Bezel-assembly release Control-panel connector Control-panel cable Bezel-assembly release Bezel assembly Figure 11. Installing the bezel assembly 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.
Page 262: Removing A Sas Hard Disk Drive
Removing a SAS hard disk drive Remove the front or rear SAS hard disk drive to install a new drive. You also have to remove the rear drive to install certain expansion cards. Figure 12. Removing the rear SAS hard disk drive Perform the following procedure to remove either the front or the rear SAS hard disk drive.
Page 263: Installing A Sas Hard Disk Drive
Installing a SAS hard disk drive The blade server has two connectors on the system board for installing optional SAS hard disk drives within the blade. All SAS connectors are on the same bus. One SAS hard disk drive might already be installed.
Page 264 6. Install the appropriate drive. v Install the front SAS hard disk drive: a. Unlatch the bezel to increase the ease of installing the drive. (You do not have to remove the bezel.) b. Place the drive into the hard disk drive tray and push it toward the rear of the blade, into the connector until the drive moves past the lever at the front of the tray.
Page 265: Removing A Memory Module
Removing a memory module Remove a dual-inline memory module (DIMM). DIMM Retaining clip Figure 14. Removing a memory module 1. Read “Safety” on page v and the “Installation guidelines” on page 239. 2. Shut down the operating system, turn off the blade server, and remove the blade server from the BladeCenter unit.
Page 266 Table 33 shows the sequence for installing DIMMs. Table 33. Installing a memory module Pair DIMM connectors First DIMM 1 and DIMM 3 Second DIMM 6 and DIMM 8 Third DIMM 2 and DIMM 4 Fourth DIMM 5 and DIMM 7 See “Supported DIMMs”...
Page 267: Removing The Management Card
8. Verify that both of the connector retaining clips are in the fully open position. 9. Turn the DIMM so that the DIMM keys align correctly with the connector on the system board. Attention: To avoid breaking the DIMM retaining clips or damaging the DIMM connectors, handle the clips gently.
Page 268: Installing The Management Card
1. Read “Safety” on page v and the “Installation guidelines” on page 239. 2. Shut down the operating system, turn off the blade server, and remove the blade server from the BladeCenter unit. See “Removing the blade server from a BladeCenter unit”...
Page 269 1. Read the documentation that comes with the management card, if you ordered a replacement card. 2. Locate the connector on the currently installed system board into which the management card will be installed. See “System-board connectors” on page 9 for the location.
Page 270: Entering Vital Product Data
The management card contains the vital product data (VPD) for the service processor. IBM sets the correct VPD values for a new JS12 blade server. If you order a replacement management card, the replacement part is not configured. If you...
Page 271: Obtaining A Powervm Virtualization Engine System Technologies Activation Code
Table 34. JS12 vital product data (continued) Vital product data field Vital product data How to find this data lsvpd | grep WN WorldWide port number _________________________________ (12 characters) command lsvpd | grep BR Brand B0 (B followed by zero) command Perform the following procedure to enter VPD data into the management card.
Page 272 3. Send a note requesting the VET activation code for your replacement management (anchor) card to the System p Capacity on Demand mailbox at pcod@us.ibm.com. Include the following fields and their values from the information you received after running the lsvet command:...
Page 273 Figure 18. System p Capacity on Demand Activation code Web page Otherwise, look for a VET entry with a date that aligns with your request date; then make a record of the corresponding VET activation code. 5. In an IVM session, use the chvet -o e -k activation_code command to enter the 34-character VET activation code for activating PowerVM Editions virtualization.
Page 274: Removing And Installing An I/O Expansion Card
6. In an IVM session, validate that the code entry is successful using the lsvet -t hist command. The command returns information that is similar to the following example: time_stamp=03/06/2008 16:25:08,"entry=[VIOSI05000400-0331] CoD advanced functions activation code entered, resource ID: CA1F, capabilities: 2820." time_stamp=03/06/2008 16:25:08,entry=[VIOSI05000403-0332] Virtual I/O server capability enabled.
Page 275: Installing A Small-Form-Factor Expansion Card
Expansion card Figure 19. Removing a small form factor (SFF) expansion card 1. Read “Safety” on page v and the “Installation guidelines” on page 239. 2. Shut down the operating system, turn off the blade server, and remove the blade server from the BladeCenter unit. See “Removing the blade server from a BladeCenter unit”...
Page 276 Expansion card Figure 20. Installing a small-form-factor expansion card To install a small-form-factor expansion card, complete the following steps: 1. Read “Safety” on page v and the “Installation guidelines” on page 239. 2. Shut down the operating system, turn off the blade server, and remove the blade server from the BladeCenter unit.
Page 277: Removing A Standard-Form-Factor Expansion Card
9. Use the documentation that comes with the expansion card to install device drivers and to perform any configuration that the expansion card requires. Removing a standard-form-factor expansion card Complete this procedure to remove a standard-form-factor expansion card. Expansion card Expansion bracket Hard disk drive tray...
Page 278: Installing A Standard-Form-Factor Expansion Card
Installing a standard-form-factor expansion card Install a standard-form-factor expansion card to expand the I/O capabilities of your blade server. Expansion card Expansion bracket Hard disk drive tray Figure 21. Installing a standard-form-factor expansion card To install a standard-form-factor expansion card, complete the following steps: 1.
Page 279: Removing A Combination-Form-Factor Expansion Card
6. Install the expansion bracket. See “Installing the expansion bracket” on page 273. 7. Touch the static-protective package that contains the part to any unpainted metal surface on the BladeCenter unit or any unpainted metal surface on any other grounded rack component; then, remove the part from its package. 8.
Page 280: Installing A Combination-Form-Factor Expansion Card
1. Read “Safety” on page v and the “Installation guidelines” on page 239. 2. Shut down the operating system, turn off the blade server, and remove the blade server from the BladeCenter unit. See “Removing the blade server from a BladeCenter unit”...
Page 281: Removing The Battery
1. Read “Safety” on page v and the “Installation guidelines” on page 239. 2. Shut down the operating system, turn off the blade server, and remove the blade server from the BladeCenter unit. See “Removing the blade server from a BladeCenter unit” on page 241. 3.
Page 282: Installing 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: 1. Set the time and date.
Page 283 CAUTION: When replacing the lithium battery, use only IBM Part Number 16G8095 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. The battery contains lithium and can explode if not properly used, handled, or disposed of.
Page 284: Removing The Hard Disk Drive Tray
Removing the hard disk drive tray Each hard disk drive has a tray that you can remove when removing the hard disk drive. Hard disk drive tray Figure 26. Removing a hard disk drive tray Perform the following procedure to remove a hard disk drive tray. 1.
Page 285: Installing The Hard Disk Drive Tray
Installing the hard disk drive tray You can install the hard disk drive tray. Hard disk drive tray Figure 27. Installing the hard disk drive tray To install the hard disk drive tray, complete the following steps: 1. Place the drive tray into position on the system board and install the four screws to secure it.
Page 286: Removing The Expansion Bracket
4. Install the blade server into the BladeCenter unit. See “Installing the blade server in a BladeCenter unit” on page 242. Removing the expansion bracket You can remove the expansion bracket. Expansion bracket Figure 28. Removing the expansion bracket Perform the following procedure to remove the expansion bracket. 1.
Page 287: Installing The Expansion Bracket
Installing the expansion bracket You can install the expansion bracket. Expansion bracket Figure 29. Installing the expansion bracket To install the expansion bracket, complete the following steps: 1. Place the expansion bracket in position on the system board. 2. Secure the bracket to the system board with two screws from the option kit or from the removed drive tray.
Page 288: Replacing The Tier 2 System-Board And Chassis Assembly
Replacing the Tier 2 system-board and chassis assembly ® You can install this 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. Replace the system board and chassis assembly. When replacing the system board, you will replace the system board, blade base (chassis), the microprocessor, and heat sinks as one assembly.
Page 289 9. Install the bezel assembly. See “Installing the bezel assembly” on page 247 for instructions. 10. Install and close the blade server cover. See “Installing and closing the blade server cover” on page 245. Statement 21 CAUTION: Hazardous energy is present when the blade server is connected to the power source.
Page 290 JS12 Type 7998: Problem Determination and Service Guide...
Page 291: Chapter 5. Configuring
(SMS) to configure the JS12 blade server. Updating the firmware IBM periodically makes firmware updates available for you to install on the blade server, the management module, or expansion cards in the blade server. Important: To avoid problems and to maintain proper system performance, always verify that the blade server BIOS, service processor, and diagnostic firmware levels are consistent for all blade servers within the BladeCenter unit.
Page 292: Configuring The Blade Server
3. Log on to the AIX or Linux system as root, or log on to the Virtual I/O Server/IVM alpha partition as padmin. 4. Type ls /tmp/fwupdate to identify the name of the firmware. The result of the command lists any firmware updates that you downloaded to the directory, such as the following update, for example: 01EA3xx_yyy_zzz 5.
Page 293: Using The Sms Utility
v System management services (SMS) Use the system management services (SMS) utility to view information about your system or partition and to perform tasks such as setting up remote IPL, changing SCSI settings, and selecting boot options. The SMS utility can be used for AIX or Linux partitions.
Page 294: Sms Utility Menu Choices
SMS utility menu choices Select SMS tasks from the SMS utility main menu. Choices on the SMS utility main menu depend on the version of the firmware in the blade server. Some menu choices might differ slightly from these descriptions. v Select Language Select this choice to change the language that is used to display the SMS menus.
Page 295: 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. Failover capabilities vary per BladeCenter unit.
Page 296: Blade Server Ethernet Controller Enumeration
Blade server Ethernet controller enumeration The enumeration of the Ethernet controllers in a blade server is operating-system dependent. You can verify the Ethernet controller designations that a blade server uses through the operating-system settings. The routing of an Ethernet controller to a particular I/O-module bay depends on the type of blade server.
Page 297: Updating Ibm Director
Roadmap. 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 298 JS12 Type 7998: Problem Determination and Service Guide...
Page 299: Appendix A. Getting Help And Technical Assistance
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 information describes where to go for additional information about IBM and IBM products, what to do if you experience a problem with your BladeCenter product or optional device, and whom to call for service, if it is necessary.
Page 300: Before You Call
The troubleshooting information or the diagnostic programs might tell you that you need additional or updated device drivers or other software. IBM maintains pages on the Web where you can get the latest technical information and download device drivers and updates. To access these pages, go to www.ibm.com/jct01004c/systems/support/supportsite.wss/...
Page 301: Getting Help And Information From The Web
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 302 JS12 Type 7998: Problem Determination and Service Guide...
Page 303: 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.
Page 304: Trademarks
IBM may use or distribute any of the information you supply in any way it believes appropriate without incurring any obligation to you. Trademarks The following terms are trademarks of International Business Machines Corporation in the United States, other countries, or both.
Page 305: Important Notes
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 might differ from its retail version (if available) and might not include user manuals or all program functionality.
Page 306 (TI) que reciclen responsablemente sus equipos cuando éstos ya no les sean útiles. IBM dispone de una serie de programas y servicios de devolución de productos en varios países, a fin de ayudar a los propietarios de equipos a reciclar sus productos de TI.
Page 307: Battery Return Program
States, go to http://www.ibm.com/ibm/environment/products/index.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. For information on proper disposal of these batteries, contact IBM at 1-800-426-4333.
Page 308 For proper collection and treatment, contact your local IBM representative. JS12 Type 7998: Problem Determination and Service Guide...
Page 309: 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 310: Avis De Conformité À La Réglementation D'industrie Canada
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 311: Taiwanese Class A Warning Statement
Taiwanese Class A warning statement This is the Taiwanese Class A warning statement. Chinese Class A warning statement View the Chinese Class A warning statement. Japanese Voluntary Control Council for Interference (VCCI) statement View the Japanese VCCI statement. Appendix B. Notices...
Page 312 JS12 Type 7998: Problem Determination and Service Guide...
Page 313: Index
BladeCenter unit combination-form-factor expansion card documentation failover support through Ethernet installing 266 online 1 switch modules 281 removing 265 PDFs 1 power requirements 242 committing TEMP image 224 related 1 safety 245 documentation, using 286 © Copyright IBM Corp. 2008, 2009...
Page 314 3 light path diagnostics panel 9 Web sites 283 EU EMC directive 296 light path LED locations 218 IBM ServerProven Web site 239 expansion bracket Linux operating system IBM Taiwan product service 287 installing 273 using the reject function 223...
Page 315 partition firmware SRCs redundant array of independent disks BA000010 through BA400002 48 (RAID) MAC addressing scheme 282 parts listing 235 Serial Attached SCSI (SAS) management card PCI expansion card problem isolation array 248, 249 installing 254 (PIOCARD) 200 reference codes 15 removing 253 PERM image 101-711 through FFC-725 142...
Page 316 7 default boot list 278 C700xxxx 109 startup problems 193 open firmware prompt 278 ServerProven Web site, IBM 239 statements and notices 2 stored boot list 278 service and support, hardware 287 static electricity 240 system management services...
Page 318 Part Number: 60Y1568 Printed in USA (1P) P/N: 60Y1568...

IBM BladeCenter JS12 Problem Determination And Service Manual

Safety

Chapter 1. Introduction

Chapter 2. Diagnostics

Chapter 3. Parts Listing, Type 7998

Chapter 4. Removing and Replacing Blade Server Components

Chapter 5. Configuring

Appendix A. Getting Help and Technical Assistance

Appendix B. Notices

Index

Quick Links

Need help?

Questions and answers

Related Manuals for IBM BladeCenter JS12

Summary of Contents for IBM BladeCenter JS12

Table of Contents