Download Print this page
IBM Flex System p24L Installation And Service Manual
IBM Flex System p24L Installation And Service Manual

IBM Flex System p24L Installation And Service Manual

Compute node
Hide thumbs Also See for Flex System p24L:

Advertisement

Quick Links

Power Systems
IBM Flex System p24L Compute Node
Installation and Service Guide
IBM

Advertisement

loading
Need help?

Need help?

Do you have a question about the Flex System p24L and is the answer not in the manual?

Questions and answers

Summary of Contents for IBM Flex System p24L

  • Page 1 Power Systems IBM Flex System p24L Compute Node Installation and Service Guide...
  • Page 3 Power Systems IBM Flex System p24L Compute Node Installation and Service Guide...
  • Page 4 Before using this information and the product it supports, read the information in “Safety notices” on page v, “Notices,” on page 459, the IBM Systems Safety Notices manual, G229-9054, and the IBM Environmental Notices and User Guide, Z125–5823. This edition applies to IBM Power Systems servers that contain the POWER7 processor and to all associated models.
  • Page 5 Completing the installation . Verifying the system firmware levels . Installing and closing the compute node cover.. Using the SMS utility . Installing the compute node in an IBM Flex Starting the SMS utility . System Enterprise Chassis SMS utility menu choices .
  • Page 6 Electronic emission notices . Using the diagnostics program Class A Notices. Boot problem resolution . Class B Notices . Troubleshooting by symptom . Terms and conditions. Intermittent problems Power Systems: IBM Flex System p24L Compute Node Installation and Service Guide...
  • Page 7 You should also refer to the safety information documentation any time you do not clearly understand any safety information in the U.S. English publications. Replacement or additional copies of safety information documentation can be obtained by calling the IBM Hotline at 1-800-300-8751.
  • Page 8 Electrical voltage and current from power, telephone, and communication cables are hazardous. To avoid a shock hazard: v Connect power to this unit only with the IBM provided power cord. Do not use the IBM provided power cord for any other product.
  • Page 9 Observe the following precautions when working on or around your IT rack system: v Heavy equipment–personal injury or equipment damage might result if mishandled. v Always lower the leveling pads on the rack cabinet. v Always install stabilizer brackets on the rack cabinet. v To avoid hazardous conditions due to uneven mechanical loading, always install the heaviest devices in the bottom of the rack cabinet.
  • Page 10 Pack the rack cabinet in the original packaging material, or equivalent. Also lower the leveling pads to raise the casters off of the pallet and bolt the rack cabinet to the pallet. (R002) (L001) (L002) viii Power Systems: IBM Flex System p24L Compute Node Installation and Service Guide...
  • Page 11 (L003) All lasers are certified in the U.S. to conform to the requirements of DHHS 21 CFR Subchapter J for class 1 laser products. Outside the U.S., they are certified to be in compliance with IEC 60825 as a class 1 laser product.
  • Page 12 Exchange only with the IBM-approved part. Recycle or discard the battery as instructed by local regulations. In the United States, IBM has a process for the collection of this battery. For information, call 1-800-426-4333. Have the IBM part number for the battery unit available when you call. (C003)
  • Page 13 IBM Flex System Enterprise Chassis units to provide a high-density, high-performance compute-node environment with advanced processing technology. The Installation and User's Guide includes the compute node information on the IBM Flex System Enterprise Chassis Documentation CD. All of the following information is in the document and also in the information...
  • Page 14 IBM Flex System Enterprise Chassis. A set of blank labels comes with the compute node. When you install the compute node in the IBM Flex System Enterprise Chassis, write identifying information on a label and place the label on the bezel. See the documentation for your IBM Flex System Enterprise Chassis for the location of the label placement.
  • Page 15 | grep BR command Related documentation Documentation for the IBM Flex System p24L Compute Node includes PDF files on the IBM Flex System Enterprise Chassis Documentation CD and in the information center. The most recent version of all IBM Flex System Enterprise Chassis documentation is in the IBM Flex System Information Center.
  • Page 16 Review the IBM Flex System Information Center or the Planning Guide and the Installation Guide for your IBM Flex System Enterprise Chassis. The information can help you prepare for system installation and configuration.
  • Page 17 Features and specifications Features and specifications of the IBM Flex System p24L Compute Node are summarized in this overview. The IBM Flex System p24L Compute Node is a one-bay compute node and is used in an IBM Flex System Enterprise Chassis. Notes: v Power, cooling, removable-media drives, external ports, and advanced system management are provided by the IBM Flex System Enterprise Chassis.
  • Page 18 Width: 215 mm (8.5 in.) security mode in which the compute node operates. See the ServerProven website for information about supported operating-system versions and all compute node optional devices. Power Systems: IBM Flex System p24L Compute Node Installation and Service Guide...
  • Page 19 Large system memory capacity The memory bus in the IBM Flex System p24L Compute Node supports up to 512 GB of system memory. For the official list of supported DIMMs, see http://www.ibm.com/systems/info/x86servers/ serverproven/compat/us/ (http://www-03.ibm.com/servers/eserver/serverproven/compat/us/).
  • Page 20 Power Systems: IBM Flex System p24L Compute Node Installation and Service Guide...
  • Page 21 3. Check log LED: When this amber LED is lit, it indicates that an error for the compute node has been detected that must be addressed by the user. See the error log repository to further investigate this serviceable event. The LED can be turned off through the management console. © Copyright IBM Corp. 2012, 2015...
  • Page 22 Start the compute node automatically when power is restored after a power failure. If a power failure occurs, the IBM Flex System Enterprise Chassis and then the compute node can start automatically when power is restored. You must configure the compute node to restart through the management module.
  • Page 23 Turning off the compute node When you turn off the compute node, it is still connected to power through the IBM Flex System Enterprise Chassis. The compute node can respond to requests from the service processor, such as a remote request to turn on the compute node. To remove all power from the compute node, you must remove it from the IBM Flex System Enterprise Chassis.
  • Page 24 System-board connectors Compute node components attach to the connectors on the system board. The following figure shows the connectors on the base-unit system board in the IBM Flex System p24L Compute Node. Figure 2. System-board connectors for the IBM Flex System p24L Compute Node The following table identifies and describes the connectors for the IBM Flex System p24L Compute Node.
  • Page 25 Press and hold the front power-control button to see any light path diagnostic LEDs that were turned on during error processing. Use the following figure to identify the failing component. The following figure shows LEDs on the IBM Flex System p24L Compute Node. The following figures and table shows the system-board LEDs.
  • Page 26 ETE connector LED Input/output connectors and devices The input/output connectors that are available to the compute node are supplied by the IBM Flex System Enterprise Chassis. See the documentation that comes with the IBM Flex System Enterprise Chassis for information about the input/output connectors.
  • Page 27 Related tasks: “Using the SMS utility” on page 18 Use the System Management Services (SMS) utility to configure the IBM Flex System p24L Compute Node. Updating the firmware IBM periodically makes firmware updates available for you to install on the compute node, on the management module, or on expansion cards in the compute node.
  • Page 28 1. Download the IBM Flex System p24L Compute Node firmware. a. Go to http://www.ibm.com/software/brandcatalog/puresystems/centre/update. b. Select the update group that matches the IBM Flex System version to which you want to update. For example, select the Flex System 1.2.1 tab.
  • Page 29 These images are referred to as TEMP and PERM, respectively. The compute node normally starts from the TEMP image. Start the TEMP image before you update the firmware. About this task To start the TEMP image, see http://publib.boulder.ibm.com/infocenter/flexsys/information/topic/ com.ibm.acc.psm.hosts.doc/dpsm_managing_hosts_power_firmware.html. Verifying the system firmware levels The diagnostics program displays the current system firmware levels for the temporary (TEMP) and permanent (PERM) images.
  • Page 30 4. When you have verified the firmware levels, press F3 until the Diagnostic Operating Instructions window is displayed, and then press F3 again to exit the diagnostic program. Using the SMS utility Use the System Management Services (SMS) utility to configure the IBM Flex System p24L Compute Node. Starting the SMS utility Start the SMS utility to configure the compute node.
  • Page 31 Learn how to increase or decrease the number of active processor cores in the compute node. You can order your IBM Flex System p24L Compute Node with a feature that instructs the factory to reduce the number of active processor cores in the compute node to reduce software licensing costs. The factory uses the field core override option to reduce the number of processor cores when feature code 2319: Factory deconfiguration of one core is ordered with a new system.
  • Page 32 1. The Integrated Virtualization Manager (IVM), see Updating the Integrated Virtualization Manager. For more information about planning, deploying, and managing the use of integrated Ethernet controllers, see the Configuring section of the PowerVM Information Roadmap. Power Systems: IBM Flex System p24L Compute Node Installation and Service Guide...
  • Page 33 Locating the installation instructions You can order the IBM Flex System p24L Compute Node with Virtual I/O Server (VIOS) or Linux already installed. If you did not order your compute node with these operating systems installed, you can install them as a local operating system.
  • Page 34 The online Linux installation instructions are available in the Linux on BladeCenter JS22 topic in the IBM Systems Information Center. If you ordered the IBM Flex System p24L Compute Node, do not use the information in the IBM Systems Information Center. Instead, go to http://publib.boulder.ibm.com/infocenter/lnxinfo/v3r0m0/ topic/liabd/install_ivm.htm in the Linux Information Center.
  • Page 35 Manager (RPM) files for Red Hat Enterprise Linux (RHEL) and SUSE Linux Enterprise Server (SLES). The IBM Installation Toolkit for Linux is available as an ISO compact disc (CD) image, which you can use to create your own CD. The Service and productivity tools for Linux systems site describes how to create a The hardware diagnostic aids and productivity tools are required for such hardware reliability, availability, and serviceability (RAS) functions as first-failure data-capture and error-log analysis.
  • Page 36 Power Systems: IBM Flex System p24L Compute Node Installation and Service Guide...
  • Page 37 To access the ASMI by using the IBM Flex System Manager, see Launching Advanced System Management (http://publib.boulder.ibm.com/infocenter/flexsys/information/topic/ com.ibm.acc.psm.hosts.doc/dpsm_managing_hosts_launch_asm.html).
  • Page 38 Power Systems: IBM Flex System p24L Compute Node Installation and Service Guide...
  • Page 39 Back up all important data before you make changes to disk drives. v Before you remove a hot-swap compute node from the IBM Flex System Enterprise Chassis, you must shut down the operating system and turn off the compute node. You do not have to shut down the IBM Flex System Enterprise Chassis itself.
  • Page 40 Do not leave the device where others can handle and damage it. v While the device is still in its static-protective package, touch it to an unpainted metal part of the IBM Flex System Enterprise Chassis or any unpainted metal surface on any other grounded rack component in the rack that you are installing the device in for at least 2 seconds.
  • Page 41 Figure 5. Removing the compute node from the IBM Flex System Enterprise Chassis Attention: v To maintain proper system cooling, do not operate the IBM Flex System Enterprise Chassis without a compute node, expansion unit, or compute node filler installed in each bay.
  • Page 42 To perform a virtual reseat by using the IBM Chassis Management Module (CMM), go to http://pic.dhe.ibm.com/infocenter/flexsys/information/topic/com.ibm.acc.8731.doc/ unmanaging_chassis.html. To perform a virtual reseat by using the IBM Flex System Manager (FSM), go to http:// pic.dhe.ibm.com/infocenter/flexsys/information/topic/com.ibm.acc.8731.doc/ unmanaging_chassis.html. 2. Is the problem resolved? Yes: This ends the procedure.
  • Page 43 About this task 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. Removing the compute node cover Remove the compute node from the chassis unit and press the compute node cover releases to open and remove the compute node cover.
  • Page 44 Installing and closing the compute node cover Install and close the cover of the compute node before you insert the compute node into the IBM Flex System Enterprise Chassis. Do not attempt to override this important protection.
  • Page 45 Figure 7. Installing the cover for an IBM Flex System p24L Compute Node Statement 21 CAUTION: Hazardous energy is present when the compute node is connected to the power source. Always replace the compute node cover before installing the compute node.
  • Page 46 If a bezel is damaged, you can remove it from a compute node. About this task Removal of the bezel assembly is not required for servicing internal components of your IBM Flex System p24L Compute Node. If the bezel becomes damaged, you can remove the bezel by using the following procedure.
  • Page 47 3. Install the compute node into the IBM Flex System Enterprise Chassis. See “Installing the compute node in an IBM Flex System Enterprise Chassis” on page 76.
  • Page 48 3. Shut down the operating system on all partitions of the compute node, turn off the compute node, and remove the compute node from the IBM Flex System Enterprise Chassis. See “Removing the compute node from an IBM Flex System Enterprise Chassis” on page 29.
  • Page 49 2. Shut down the operating system on all partitions of the compute node, turn off the compute node, and remove the compute node from the IBM Flex System Enterprise Chassis. See “Removing the compute node from an IBM Flex System Enterprise Chassis” on page 29.
  • Page 50 Hazardous energy is present when the compute node is connected to the power source. Always replace the compute node cover before installing the compute node. 8. Install the compute node into the IBM Flex System Enterprise Chassis. See “Installing the compute node in an IBM Flex System Enterprise Chassis” on page 76.
  • Page 51 3. Shut down the operating system on all partitions of the compute node, turn off the compute node, and remove the compute node from the IBM Flex System Enterprise Chassis. See “Removing the compute node from an IBM Flex System Enterprise Chassis” on page 29.
  • Page 52 About this task Figure 13 shows how to install the disk drive. Figure 13. Installing an SSD carrier To install an SSD carrier, complete the following steps: Procedure Power Systems: IBM Flex System p24L Compute Node Installation and Service Guide...
  • Page 53 Hazardous energy is present when the compute node is connected to the power source. Always replace the compute node cover before installing the compute node. 11. Install the compute node into the IBM Flex System Enterprise Chassis. See “Installing the compute node in an IBM Flex System Enterprise Chassis” on page 76.
  • Page 54 3. Shut down the operating system on all partitions of the compute node, turn off the compute node, and remove the compute node from the IBM Flex System Enterprise Chassis. See “Removing the compute node from an IBM Flex System Enterprise Chassis” on page 29.
  • Page 55 2. Shut down the operating system on all partitions of the compute node, turn off the compute node, and remove the compute node from the IBM Flex System Enterprise Chassis. See “Removing the compute node from an IBM Flex System Enterprise Chassis” on page 29.
  • Page 56 If IBM removes a tier 1 CRU at your request, you will be charged for the removal. The low profile (LP) DIMM is a tier 2 CRU. You can remove it yourself or request IBM to remove it, at no additional charge, under the type of warranty service that is designated for the compute node.
  • Page 57 Figure 16. DIMM connectors for the IBM Flex System p24L Compute Node Attention: To avoid breaking the DIMM retaining clips or damaging the DIMM connectors, open and close the clips gently. 6. Carefully open the retaining clips (A) on each end of the DIMM connector by pressing them in the direction of the arrows.
  • Page 58 If IBM installs a tier 1 CRU at your request, you will be charged for the installation. The low profile (LP) DIMM is a tier 2 CRU. You can install it yourself or request IBM to install it, at no additional charge, under the type of warranty service that is designated for the compute node.
  • Page 59 Hazardous energy is present when the compute node is connected to the power source. Always replace the compute node cover before installing the compute node. 12. Install the compute node into the IBM Flex System Enterprise Chassis. See “Installing the compute node in an IBM Flex System Enterprise Chassis” on page 76.
  • Page 60 Supported DIMMs Your compute node contains connectors for registered dual inline memory modules (RDIMMs). Each system board in the IBM Flex System p24L Compute Node contains connectors for 16 low profile (LP) or very low profile (VLP) memory DIMMs. The maximum size for a single DIMM is 8 GB for a VLP DIMM and 32 GB for an LP DIMM. The maximum memory capacity for an IBM Flex System p24L Compute Node is 1024 GB.
  • Page 61 Chapter 7, “Parts listing for IBM Flex System p24L Compute Node,” on page 79 The parts listing identifies each replaceable part and its part number. Related information: http://www.ibm.com/systems/info/x86servers/serverproven/compat/us/ Removing a network adapter If your network adapter needs to be replaced, you can remove it from its connector in a compute node.
  • Page 62 Hazardous energy is present when the compute node is connected to the power source. Always replace the compute node cover before installing the compute node. 9. Install the compute node into the IBM Flex System Enterprise Chassis. See “Installing the compute node in an IBM Flex System Enterprise Chassis” on page 76.
  • Page 63 3. Open and remove the compute node cover. See “Removing the compute node cover” on page 31. 4. Touch the static-protective package that contains the part to any unpainted metal surface on the IBM Flex System Enterprise Chassis or any unpainted metal surface on any other grounded rack component, and then remove the new part from its shipment package.
  • Page 64 2. Shut down the operating system on all partitions of the compute node, turn off the compute node, and remove the compute node from the IBM Flex System Enterprise Chassis. See “Removing the compute node from an IBM Flex System Enterprise Chassis” on page 29.
  • Page 65 CAUTION: When replacing the lithium battery, use only IBM Part Number 33F8354 or an equivalent type battery recommended by the manufacturer. If your system has a module containing a lithium battery, replace it only with the same module type made by the same manufacturer. The battery contains lithium and can explode if not properly used, handled, or disposed of.
  • Page 66 Use this information for removing and replacing tier 2 CRUs. About this task You can install a tier 2 CRU, or you can request IBM to install it, at no additional charge, under the type of warranty service that is designated for the compute node.
  • Page 67 Hazardous energy is present when the compute node is connected to the power source. Always replace the compute node cover before installing the compute node. 10. Install the compute node into the IBM Flex System Enterprise Chassis. See “Installing the compute node in an IBM Flex System Enterprise Chassis” on page 76.
  • Page 68 If IBM installs a tier 1 CRU at your request, you will be charged for the installation. The low profile (LP) DIMM is a tier 2 CRU. You can install it yourself or request IBM to install it, at no additional charge, under the type of warranty service that is designated for the compute node.
  • Page 69 Removing the management card You can remove this tier 2 CRU, or you can request IBM to remove it, at no additional charge, under the type of warranty service that is designated for the compute node. Remove the management card to replace the card or to reuse the card in a new system-board and chassis assembly.
  • Page 70 Manually record the values of Enclosure location, Feature Code/Sequence Number, Enclosure serial number, and Reserved. 6. Turn off the compute node and remove the compute node from the IBM Flex System Enterprise Chassis. See “Removing the compute node from an IBM Flex System Enterprise Chassis” on page 29.
  • Page 71 Installing the management card You can install this tier 2 CRU, or you can request IBM to install it, at no additional charge, under the type of warranty service that is designated for the compute node. Use this procedure to install the management card into the currently installed system board.
  • Page 72 3. Touch the static-protective package that contains the management card to any unpainted metal surface on the IBM Flex System Enterprise Chassis or any unpainted metal surface on any other grounded rack component, and then remove the management card from its package.
  • Page 73 By using Advanced System Management Interface (ASMI): a. Access the ASMI. If you are already connected to the ASMI, go to step 2c on page 62. 1) To access the ASMI through the IBM Flex System Manager (FSM), see http:// publib.boulder.ibm.com/infocenter/flexsys/information/topic/com.ibm.acc.psm.hosts.doc/ dpsm_managing_hosts_launch_asm.html.
  • Page 74 The following is an example of the PowerVM output: Note: When you request the activation code, you must supply the information that is emphasized in the following example. Power Systems: IBM Flex System p24L Compute Node Installation and Service Guide...
  • Page 75 3. Send a request for the VET activation code for your replacement management card to the System p Capacity on Demand mailbox at pcod@us.ibm.com. If the ASMI was used to get the VET information, include the following fields and their values:...
  • Page 76 This is to ensure that the activation code is stored in the vital product data on the management card. Power Systems: IBM Flex System p24L Compute Node Installation and Service Guide...
  • Page 77 Removing the light path diagnostics panel You can remove this tier 2 CRU, or you can request IBM to remove it, at no additional charge, under the type of warranty service that is designated for the compute node. Remove the light path diagnostics panel to replace the panel or to reuse the panel in a new system-board and chassis assembly.
  • Page 78 Installing the light path diagnostics panel You can install this tier 2 CRU, or you can request IBM to install it, at no additional charge, under the type of warranty service that is designated for the compute node. Use this procedure to install the light path diagnostics panel into the currently installed system board.
  • Page 79 Hazardous energy is present when the compute node is connected to the power source. Always replace the compute node cover before installing the compute node. 11. Install the compute node into the IBM Flex System Enterprise Chassis. See “Installing the compute node in an IBM Flex System Enterprise Chassis” on page 76.
  • Page 80 If this system is managed by an IBM Flex System Manager (FSM) management console, back up partition profile data. Using the Systems management command-line interface (SMCLI), enter the bkprofdata command.
  • Page 81 6. Have the customer record the compute node IPv4 address and any static IPv6 addresses. Complete the following steps: a. Access the Chassis Management Module (CMM) web interface. For instructions, see Ethernet connection (http://pic.dhe.ibm.com/infocenter/flexsys/information/topic/ com.ibm.acc.cmm.doc/remote_console_ethernet_connect_cmm.html). b. From the menu bar, click Chassis Management. Then, from the drop-down menu, click Component IP Configuration.
  • Page 82 15. Touch the static-protective package that contains the system-board and chassis assembly to any unpainted metal surface on the IBM Flex System Enterprise Chassis or any unpainted metal surface on any other grounded rack component, and then remove the assembly from its package.
  • Page 83 20. Place the repair identification tag on the bottom of the compute node chassis. 21. Install the compute node into the IBM Flex System Enterprise Chassis. Do not turn on the compute node until step 26 on page 72 or 27 on page 72 of this procedure, depending upon whether the compute node is managed by a management console.
  • Page 84 FSM. Recover the partition profile data. For instructions, see Correcting a Recovery state for a server (http://pic.dhe.ibm.com/infocenter/flexsys/information/topic/ com.ibm.acc.psm.troubleshooting.doc/ dpsm_troubleshooting_managedsystemstate_recovery.html). Power Systems: IBM Flex System p24L Compute Node Installation and Service Guide...
  • Page 85 Click Save Settings and continue system server firmware boot. 30. Have the customer activate a VIOS partition by using one of the following methods: v If this system is managed by an FSM, see Activating a virtual server (http://pic.dhe.ibm.com/ infocenter/flexsys/information/topic/com.ibm.acc.psm.resources.doc/vs/sdmc_vs- activating_vs.html).
  • Page 86 3. Turn on the compute node, as described in “Turning on the compute node” on page 10. Note: If you have just connected the power cords of the IBM Flex System Enterprise Chassis to electrical outlets, you must wait until the power-on LED on the compute node flashes slowly before you press the power-control button.
  • Page 87 Installing and closing the compute node cover Install and close the cover of the compute node before you insert the compute node into the IBM Flex System Enterprise Chassis. Do not attempt to override this important protection. About this task Figure 31.
  • Page 88 3. Slide the cover forward to the closed position until the releases click into place in the cover. 4. Install the compute node into the IBM Flex System Enterprise Chassis. See “Installing the compute node in an IBM Flex System Enterprise Chassis.”...
  • Page 89 Important: Do not place the label on the compute node or in any way block the ventilation holes on the compute node. See the online information or the documentation that comes with your IBM Flex System Enterprise Chassis for information about label placement.
  • Page 90 You might also have to install the compute node operating system. See Chapter 4, “Installing the operating system,” on page 21 for detailed information about these tasks. Power Systems: IBM Flex System p24L Compute Node Installation and Service Guide...
  • Page 91 1 CRU at your request, you will be charged for the installation. v Tier 2 customer replaceable unit: You can 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 compute node.
  • Page 92 IBM Flex System 4-port 1 Gb Ethernet adapter 49Y7902 2E3D IBM Flex System 8-port 10 Gb converged adapter 00E1677 2E28, 2E52 IBM Flex System 2-port 10 Gb RoCE adapter 90Y3481 2770 Power Systems: IBM Flex System p24L Compute Node Installation and Service Guide...
  • Page 93 Disk drive filler 40K5928 Service label 00J0134 FRU and CRU label 00E6284 Light path label 00J0140 Miscellaneous parts kit (left cam handle) 81Y5203 Miscellaneous parts kit (network adapter retention) 94Y4866 Chapter 7. Parts listing for IBM Flex System p24L Compute Node...
  • Page 94 Power Systems: IBM Flex System p24L Compute Node Installation and Service Guide...
  • Page 95 1 CRU at your request, you are charged for the installation. v Tier 2 customer replaceable unit: You can 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 compute node.
  • Page 96 Use light path diagnostics LEDs on the system board to identify system errors. If the system-error LED on the system LED panel on the front or rear of the IBM Flex System Enterprise Chassis is lit, one or more error LEDs on the IBM Flex System Enterprise Chassis components also might be lit. These LEDs help identify the cause of the problem.
  • Page 97 Use the light path diagnostic LEDs to identify failing hardware. If the enclosure fault LED on the front or rear of the IBM Flex System Enterprise Chassis is lit, one or more fault LEDs on the compute node will also be lit. Use the light path diagnostic LEDs on the compute node to help identify the failing item.
  • Page 98 Note: If you power off the compute node 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 by operating system.
  • Page 99 For a Linux operating system, collect the dump from the /var/log/dump directory. v For an IBM Flex System p24L Compute Node that is managed by the Integrated Virtualization Manager (IVM), collect the dump using the Manage Dumps task in the IVM console.
  • Page 100 Um codes are for firmware. The format is the same as for a Un location code. Um = Utttt.mmm.sssssss Firmware version Um-Y1 Table 8. Mapping network adapter ports to IBM Flex System Enterprise Chassis I/O bays for the IBM Flex System p24L Compute Node IBM Flex IBM Flex...
  • Page 101 Table 8. Mapping network adapter ports to IBM Flex System Enterprise Chassis I/O bays for the IBM Flex System p24L Compute Node (continued) IBM Flex IBM Flex IBM Flex System 2-port IBM Flex System 4-port IBM Flex System 2-port IBM Flex...
  • Page 102 The IBM Flex System p24L Compute Node does not display checkpoints or error codes on the remote console. If the POST detects a problem, a 9-word, 8-digit error code is logged in the IBM Flex System Enterprise Chassis management-module event log. A location code that identifies a component might also be included.
  • Page 103 Dxxxyyyy - Dump checkpoint (must hang to indicate an error) To find a description of an SRC that is not listed in this IBM Flex System p24L Compute Node documentation, refer to the POWER7 Reference Code Lookup page at http://publib.boulder.ibm.com/ infocenter/systems/scope/hw/index.jsp?topic=/ipha8/codefinder.htm.
  • Page 104 If a firmware update is needed, see Updating the firmware 2. Replace the system board. If there is more than one system board, use the location code in the SRC to identify which system board to replace. Power Systems: IBM Flex System p24L Compute Node Installation and Service Guide...
  • Page 105 11002620 • 1100262C 11002620 Explanation: 12V dc pGood input fault. Response: 1. Search RETAIN tips and the firmware change history for the reference code to determine the recommended actions. If a firmware update is needed, see Updating the firmware 2. Replace the system board. If there is more than one system board, use the location code in the SRC to identify which system board to replace.
  • Page 106 If a firmware update is needed, see Updating the firmware 2. Replace the system board. If there is more than one system board, use the location code in the SRC to identify which system board to replace. Power Systems: IBM Flex System p24L Compute Node Installation and Service Guide...
  • Page 107 11002640 • 11002649 11002640 Explanation: VRM CP1 core pGood fault Response: 1. Search RETAIN tips and the firmware change history for the reference code to determine the recommended actions. If a firmware update is needed, see Updating the firmware 2. Replace the system board. If there is more than one system board, use the location code in the SRC to identify which system board to replace.
  • Page 108 5. Monitor the server operation to verify that the problem is solved. 6. If the chassis unit is functioning normally, but the problem persists, replace the system board specified by the location code that was reported with the SRC. Power Systems: IBM Flex System p24L Compute Node Installation and Service Guide...
  • Page 109 11002674 • 11002679 11002674 Explanation: Expansion server pGood fault at standby. Response: 1. Search RETAIN tips and the firmware change history for the reference code to determine the recommended actions. If a firmware update is needed, see Updating the firmware 2.
  • Page 110 If a firmware update is needed, see Updating the firmware 2. Replace the system board. If there is more than one system board, use the location code in the SRC to identify which system board to replace. Power Systems: IBM Flex System p24L Compute Node Installation and Service Guide...
  • Page 111 1100267F • 11002900 1100267F Explanation: ETE daughter card pGood fault. Response: 1. Search RETAIN tips and the firmware change history for the reference code to determine the recommended actions. If a firmware update is needed, see Updating the firmware 2. Replace the ETE daughter card. 1100269C Explanation: 1.2V A pGood fault.
  • Page 112 If a firmware update is needed, see Updating the firmware 2. If this is an IBM Flex System p260 or p24L compute node, replace the light path diagnostics panel. If this is an IBM Flex System p460 compute node, check word 3 of the SRC. If word 3 is 00003100, the thermal sensor in the first bay is failing;...
  • Page 113 11003134 • 11008413 11003134 Explanation: Fault on the hardware monitoring chip. Response: Perform the DTRCARD symbolic CRU isolation procedure by completing the following steps: 1. Reseat the PCIe expansion card. 2. If the problem persists, replace the expansion card. 3. If the problem persists: Search RETAIN tips and the firmware change history for the reference code to determine the recommended actions.
  • Page 114 3. Search RETAIN tips and the firmware change history for the reference code to determine the recommended actions. If a firmware update is needed, see Updating the firmware 4. Replace the base system-board, as described in Replacing the system-board and chassis assembly. Power Systems: IBM Flex System p24L Compute Node Installation and Service Guide...
  • Page 115 If an action solves the problem, you can stop performing the remaining actions. See Chapter 7, “Parts listing for IBM Flex System p24L Compute Node,” on page 79 to determine which components are CRUs and which components are FRUs.
  • Page 116 Response: Replace the management card, as described in Removing the management card and Installing the management card. A7004721 Explanation: The World Wide Port Name (WWPN) Prefix is not valid. Response: Refer to https://www-912.ibm.com/supporthome.nsf/document/51455410 Power Systems: IBM Flex System p24L Compute Node Installation and Service Guide...
  • Page 117 Response: The management interfaces have been used to set AMM to "ON" for the system. However, at IPL time, the system does not have a valid license for AMM. The customer needs to contact IBM or a Partner Sales representative to purchase and enter an Activation Code for this feature. If this is not possible, then turn off the system;...
  • Page 118 If an action solves the problem, then you can stop performing the remaining actions. See Chapter 7, “Parts listing for IBM Flex System p24L Compute Node,” on page 79 to determine which components are CRUs and which components are FRUs.
  • Page 119 AA060007 • AA06000E AA060007 Explanation: A keyboard was not found. Response: Verify that a keyboard is attached to the USB port that is assigned to the partition. AA06000B Explanation: The system or partition was not able to find an operating system on any of the devices in the boot list. Response: 1.
  • Page 120 1. Use the operating system to set the system clock. 2. If the problem persists, check for server firmware updates. 3. Install any available updates and retry the operation. Power Systems: IBM Flex System p24L Compute Node Installation and Service Guide...
  • Page 121 A B1xxyyyy system reference code (SRC) is an error code that is related to an event or exception that occurred in the service processor firmware. To find a description of an SRC that is not listed in this IBM Flex System p24L Compute Node documentation, refer to the POWER7 Reference Code Lookup page at http://publib.boulder.ibm.com/ infocenter/systems/scope/hw/index.jsp?topic=/ipha8/codefinder.htm.
  • Page 122 B1817202 Explanation: The permanent and temporary firmware sides are both marked invalid Response: Go to Checkout procedure. B1817203 Explanation: Error setting boot parameters Response: Go to Checkout procedure. Power Systems: IBM Flex System p24L Compute Node Installation and Service Guide...
  • Page 123 B1817204 • B1818BC1 B1817204 Explanation: Error reading boot parameters Response: Go to Checkout procedure. B1817205 Explanation: Boot code error Response: Go to Checkout procedure. B1817206 Explanation: Unit check timer was reset Response: Go to Checkout procedure. B1817207 Explanation: Error reading from NVRAM Response: Go to Checkout procedure.
  • Page 124 If an action solves the problem, then you can stop performing the remaining actions. See Chapter 7, “Parts listing for IBM Flex System p24L Compute Node,” on page 79 to determine which components are CRUs and which components are FRUs.
  • Page 125 B2001132 • B2001143 B2001132 Explanation: A problem occurred during the startup of a partition. A platform firmware error occurred while it was trying to allocate memory. The startup will not continue. Response: Collect a platform dump and then go to Isolating firmware problems. B2001133 Explanation: A problem occurred during the migration of a partition.
  • Page 126 Explanation: During the startup of a partition, a partitioning configuration problem occurred; the partition is lacking the necessary resources to start up. Response: Go to Verifying the partition configuration. Power Systems: IBM Flex System p24L Compute Node Installation and Service Guide...
  • Page 127 B2001260 • B2001320 B2001260 Explanation: A problem occurred during the startup of a partition. The partition could not start at the Timed Power On setting because the partition was not set to Normal. Response: Set the partition to Normal. B2001265 Explanation: The partition could not start up.
  • Page 128 Explanation: During the startup of a partition, an attempt to toggle the power state of a slot has failed. Response: Check for server firmware updates; then, install the updates if available. Power Systems: IBM Flex System p24L Compute Node Installation and Service Guide...
  • Page 129 B2002260 • B2002485 B2002260 Explanation: During the startup of a partition, the partition firmware attempted an operation that failed. Response: Go to Isolating firmware problems. B2002300 Explanation: During the startup of a partition, an attempt to toggle the power state of a slot has failed. Response: Check for server firmware updates;...
  • Page 130 Explanation: A problem occurred during the startup of a partition. Response: Go to Isolating firmware problems. B2003113 Explanation: A problem occurred during the startup of a partition. Response: Look for B7xx xxxx errors and resolve them. Power Systems: IBM Flex System p24L Compute Node Installation and Service Guide...
  • Page 131 B2003114 • B2003140 B2003114 Explanation: A problem occurred during the startup of a partition. Response: Look for other errors and resolve them. B2003120 Explanation: Informational system log entry only. Response: No corrective action is required. B2003123 Explanation: Informational system log entry only. Response: No corrective action is required.
  • Page 132 Response: No corrective action is required. B2004400 Explanation: A problem occurred during the startup of a partition. Response: Check for server firmware updates; then, install the updates if available. Power Systems: IBM Flex System p24L Compute Node Installation and Service Guide...
  • Page 133 B2005106 • B2005122 B2005106 Explanation: A problem occurred during the startup of a partition. There is not enough space to contain the partition main storage dump. The startup will not continue. Response: Verify that there is sufficient memory available to start the partition as it is configured. If there is already enough memory, then go to Isolating firmware problems.
  • Page 134 Explanation: A problem occurred during the startup of a partition while doing a Firmware Assisted Dump that would have caused another Firmware Assisted Dump. Response: Check for server firmware updates; then, install the updates if available. Power Systems: IBM Flex System p24L Compute Node Installation and Service Guide...
  • Page 135 B200514A • B2006003 B200514A Explanation: A Firmware Assisted Dump did not complete due to a copy error. Response: Check for server firmware updates; then, install the updates if available. B200542A Explanation: A Firmware Assisted Dump did not complete due to a read error. Response: Check for server firmware updates;...
  • Page 136 Response: Go to Isolating firmware problems. B2006015 Explanation: A problem occurred during the startup of a partition. The load source media is corrupted or not valid. Response: Replace the load source media. Power Systems: IBM Flex System p24L Compute Node Installation and Service Guide...
  • Page 137 B2006025 • B2008081 B2006025 Explanation: A problem occurred during the startup of a partition. This is a problem with the load source media being corrupt or not valid. Response: Replace the load source media. B2006027 Explanation: During the startup of a partition, a failure occurred when allocating memory for an internal object used for firmware module load operations.
  • Page 138 Explanation: During the startup of a partition, there was a failure verifying the VPD for the partition resources during startup. Response: Check for server firmware updates; then, install the updates if available. Power Systems: IBM Flex System p24L Compute Node Installation and Service Guide...
  • Page 139 B2008115 • B200813A B2008115 Explanation: During the startup of a partition, there was a low level partition-to-partition communication failure. Response: Check for server firmware updates; then, install the updates if available. B2008117 Explanation: During the startup of a partition, the partition did not start up due to a system firmware error. Response: Check for server firmware updates;...
  • Page 140 Explanation: System firmware detected an error. Response: Use the management console to increase the Logical Memory Block (LMB) size, and to reduce the number of virtual devices for the partition. Power Systems: IBM Flex System p24L Compute Node Installation and Service Guide...
  • Page 141 Response: Verify that processor resources are assigned to the partition. B2008160 Explanation: A problem occurred during the migration of a partition. Response: Contact IBM support. B2008161 Explanation: A problem occurred during the migration of a partition. Response: Contact IBM support.
  • Page 142 Response: Collect the partition dump information; then, go to Isolating firmware problems. B200F004 Explanation: Informational system log entry only. Response: No corrective action is required. B200F005 Explanation: Informational system log entry only. Response: No corrective action is required. Power Systems: IBM Flex System p24L Compute Node Installation and Service Guide...
  • Page 143 B200F006 • B200F00D B200F006 Explanation: During the startup of a partition, the code load operation for the partition startup timed out. Response: 1. Check the error logs and take the actions for the error codes that are found. 2. Go to Isolating firmware problems. B200F007 Explanation: During a shutdown of the partition, a time-out occurred while trying to stop a partition.
  • Page 144 If an action solves the problem, then you can stop performing the remaining actions. See Chapter 7, “Parts listing for IBM Flex System p24L Compute Node,” on page 79 to determine which components are CRUs and which components are FRUs.
  • Page 145 Explanation: System firmware has experienced a low storage condition Response: No immediate action is necessary. 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.
  • Page 146 Note: This code and associated data can be used to determine why the time of day for a partition was lost. B7000602 Explanation: System firmware detected an error condition. Response: 1. Collect the event log information. 2. Go to Isolating firmware problems. Power Systems: IBM Flex System p24L Compute Node Installation and Service Guide...
  • Page 147 B7000611 • B7000804 B7000611 Explanation: There is a problem with the system hardware clock; the clock time is invalid. Response: Use the operating system to set the system clock. B7000621 Explanation: Informational system log entry only. Response: No corrective action is required. B7000641 Explanation: System firmware detected an error.
  • Page 148 1. Go to Isolating firmware problems. 2. Replace the system-board, as described in Replacing the system-board and chassis assembly. B7001161 Explanation: Informational system log entry only. Response: No corrective action is required. Power Systems: IBM Flex System p24L Compute Node Installation and Service Guide...
  • Page 149 Response: Look for and correct B1xxxxxx errors. If there are no serviceable 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 150 Response: Restart the system. B7004710 Explanation: Informational system log entry only. Response: No corrective action is required. B7004714 Explanation: Informational system log entry only. Response: No corrective action is required. Power Systems: IBM Flex System p24L Compute Node Installation and Service Guide...
  • Page 151 B7004715 • B7005122 B7004715 Explanation: A problem occurred when initializing, reading, or using system VPD. Response: Replace the management card, as described in Removing the management card and Installing the management card. B7004750 Explanation: Informational system log entry only. Response: No corrective action is required. B7004788 Explanation: Informational system log entry only.
  • Page 152 Response: Check the Management Module event log for error codes; then, take the actions associated with those error codes. B7005301 Explanation: User intervention required. The system detected a problem with the partition configuration. Response: Use the management console to reallocate the system resources. Power Systems: IBM Flex System p24L Compute Node Installation and Service Guide...
  • Page 153 Response: Refer to https://www-912.ibm.com/supporthome.nsf/document/51455410 B7005306 Explanation: There is insufficient licensed memory for firmware to support the manufacturing default configuration. Response: Contact IBM support or marketing representative to obtain an activation code to license more memory in the system. B7005400 Explanation: System firmware detected a problem with a processor.
  • Page 154 If the problem persists, use the PCI expansion card (PIOCARD) problem isolation procedure to determine the failing component. B7006906 Explanation: System bus error Response: Replace the system-board and chassis assembly, as described in Replacing the system-board and chassis assembly. Power Systems: IBM Flex System p24L Compute Node Installation and Service Guide...
  • Page 155 B7006907 • B7006950 B7006907 Explanation: System bus error Response: 1. Replace the system-board, as described in Replacing the system-board and chassis assembly. 2. Go to Isolating firmware problems. B7006908 Explanation: System bus error Response: Replace the system-board and chassis assembly, as described in Replacing the system-board and chassis assembly.
  • Page 156 1. Replace the system-board, as described in Replacing the system-board and chassis assembly. If the problem persists, use the PCI expansion card (PIOCARD) problem isolation procedure to determine the failing component. Power Systems: IBM Flex System p24L Compute Node Installation and Service Guide...
  • Page 157 B7006971 • B700697C B7006971 Explanation: PCI bus failure Response: 1. Use the PCI expansion card (PIOCARD) problem isolation procedure to determine the failing component. 2. If the problem persists, replace the system-board and chassis assembly, as described in Replacing the system-board and chassis assembly.
  • Page 158 Explanation: Service processor failure. Response: Replace the system-board and chassis assembly, as described in Replacing the system-board and chassis assembly. B7006991 Explanation: System firmware failure Response: Go to Isolating firmware problems. Power Systems: IBM Flex System p24L Compute Node Installation and Service Guide...
  • Page 159 B7006993 • B70069DB B7006993 Explanation: Service processor failure Response: 1. Replace the system-board, as described in Replacing the system-board and chassis assembly. 2. Go to Isolating firmware problems. B7006994 Explanation: Service processor failure. Response: Replace the system-board and chassis assembly, as described in Replacing the system-board and chassis assembly.
  • Page 160 3. Replace the system-board and chassis assembly, as described in Replacing the system-board and chassis assembly. 4. Although the partition or application may have continued to run after the I/O adapter failures, it might need to be restarted to recover. Power Systems: IBM Flex System p24L Compute Node Installation and Service Guide...
  • Page 161 1. Collect error logs and info logs. 2. Replace the system-board and chassis assembly, as described in Replacing the system-board and chassis assembly. Send the failed FRU and the data to IBM for fault analysis. B7006A22 Explanation: PCI-E switch had a recoverable failure, however, all downstream I/O had to be failed during recovery.
  • Page 162 3. Update the firmware to the current level, as described in Updating the firmware. 4. If the problem persists, replace the system-board and chassis assembly, as described in Replacing the system-board and chassis assembly. Send the failed FRU and the data to IBM for fault analysis. B7006A28 Explanation: PCI-E switch had a correctable error.
  • Page 163 B700BA01 • B700F105 B700BA01 Explanation: During analysis of a previous serviceable error, a request to activate a FRU fault indicator was not successful. Response: Replace the system-board and chassis assembly, as described in Replacing the system-board and chassis assembly. B700BAD1 Explanation: The platform firmware detected an error.
  • Page 164 Response: Replace the system-board and chassis assembly, as described in Replacing the system-board and chassis assembly. B700F10C Explanation: The platform LIC detected an internal problem performing Partition Mobility. Response: 1. Collect the event log information. 2. Go to Isolating firmware problems. Power Systems: IBM Flex System p24L Compute Node Installation and Service Guide...
  • Page 165 If an action solves the problem, then you can stop performing the remaining actions. See Chapter 7, “Parts listing for IBM Flex System p24L Compute Node,” on page 79 to determine which components are CRUs and which components are FRUs.
  • Page 166 2. If the problem persists: Search RETAIN tips and the firmware change history for the reference code to determine the recommended actions. If a firmware update is needed, see Updating the firmware Power Systems: IBM Flex System p24L Compute Node Installation and Service Guide...
  • Page 167 BA000040 • BA000080 BA000040 Explanation: The firmware was unable to obtain the RTAS code lid details Response: 1. Reboot the server. 2. If the problem persists: Search RETAIN tips and the firmware change history for the reference code to determine the recommended actions.
  • Page 168 2. If the problem persists: Search RETAIN tips and the firmware change history for the reference code to determine the recommended actions. If a firmware update is needed, see Updating the firmware Power Systems: IBM Flex System p24L Compute Node Installation and Service Guide...
  • Page 169 BA00E840 • BA010000 BA00E840 Explanation: Failure when initializing PCI hot-plug Response: 1. Reboot the server. 2. If the problem persists: Search RETAIN tips and the firmware change history for the reference code to determine the recommended actions. If a firmware update is needed, see Updating the firmware BA00E843 Explanation: Failure when initializing the interface to AIX or Linux Response:...
  • Page 170 2. If the problem persists: Search RETAIN tips and the firmware change history for the reference code to determine the recommended actions. If a firmware update is needed, see Updating the firmware Power Systems: IBM Flex System p24L Compute Node Installation and Service Guide...
  • Page 171 BA010006 • BA01000B BA010006 Explanation: The boot image is too large Response: Start up from another device with a bootable image. BA010007 Explanation: The device does not have the required device_type property. Response: 1. Reboot the server. 2. If the problem persists: Search RETAIN tips and the firmware change history for the reference code to determine the recommended actions.
  • Page 172 2. If the problem persists: Search RETAIN tips and the firmware change history for the reference code to determine the recommended actions. If a firmware update is needed, see Updating the firmware Power Systems: IBM Flex System p24L Compute Node Installation and Service Guide...
  • Page 173 BA010013 • BA012011 BA010013 Explanation: The information in the error log entry for this SRC provides network trace data. Response: Informational message. No action is required. BA010014 Explanation: The information in the error log entry for this SRC provides network trace data. Response: Informational message.
  • Page 174 2. If the problem persists, Search RETAIN tips and the firmware change history for the reference code to determine the recommended actions. If a firmware update is needed, see Updating the firmware Power Systems: IBM Flex System p24L Compute Node Installation and Service Guide...
  • Page 175 BA01B012 • BA01D001 BA01B012 Explanation: BOOTP failed to write to the network Response: Perform the following actions that checkpoint CA00E174 describes: 1. Verify that: v The bootp server is correctly configured; then, retry the operation. v The network connections are correct; then, retry the operation. 2.
  • Page 176 DHCP acknowledgement (DHCP ack) to the client DHCP request. Another client might have used the address that was served. Verify that the DHCP server has addresses available. Power Systems: IBM Flex System p24L Compute Node Installation and Service Guide...
  • Page 177 BA01D052 • BA01D056 BA01D052 Explanation: DHCP::discover: 10 incapable servers were found Response: Ten DHCP servers have sent DHCP offers, none of which met the requirements of the client. Check the compatibility of the configuration that the client is requesting and the server DHCP configuration files. BA01D053 Explanation: DHCP::discover received a reply, but without a message type Response: Verify that the DHCP server is properly configured.
  • Page 178 2. Search RETAIN tips and the firmware change history for the reference code to determine the recommended actions. If a firmware update is needed, see Updating the firmware Power Systems: IBM Flex System p24L Compute Node Installation and Service Guide...
  • Page 179 BA040030 • BA040060 BA040030 Explanation: The firmware was not able to build the UID properly for this system. As a result, problems may occur with the licensing of the AIX operating system. Response: 1. Reboot the server. 2. Search RETAIN tips and the firmware change history for the reference code to determine the recommended actions.
  • Page 180 2. Search RETAIN tips and the firmware change history for the reference code to determine the recommended actions. If a firmware update is needed, see Updating the firmware Power Systems: IBM Flex System p24L Compute Node Installation and Service Guide...
  • Page 181 BA060020 • BA060060 BA060020 Explanation: The environment variable boot-device exceeded the allowed character limit. Response: 1. Reboot the server. 2. Search RETAIN tips and the firmware change history for the reference code to determine the recommended actions. If a firmware update is needed, see Updating the firmware BA060021 Explanation: The environment variable boot-device contained more than five entries.
  • Page 182 4. If the problem persists: Search RETAIN tips and the firmware change history for the reference code to determine the recommended actions. If a firmware update is needed, see Updating the firmware Power Systems: IBM Flex System p24L Compute Node Installation and Service Guide...
  • Page 183 BA060201 • BA090001 BA060201 Explanation: Failed to read the VPD "boot path" field value Response: 1. Reboot the server. 2. Search RETAIN tips and the firmware change history for the reference code to determine the recommended actions. If a firmware update is needed, see Updating the firmware BA060202 Explanation: Failed to update the VPD with the new "boot path"...
  • Page 184 4. Search RETAIN tips and the firmware change history for the reference code to determine the recommended actions. If a firmware update is needed, see Updating the firmware Power Systems: IBM Flex System p24L Compute Node Installation and Service Guide...
  • Page 185 BA09000C • BA090010 BA09000C Explanation: The media is write-protected Response: 1. Change the setting of the media to allow writing, then retry the operation. 2. Insert new media of the correct type. 3. Reboot the server. 4. Search RETAIN tips and the firmware change history for the reference code to determine the recommended actions.
  • Page 186 4. Search RETAIN tips and the firmware change history for the reference code to determine the recommended actions. If a firmware update is needed, see Updating the firmware Power Systems: IBM Flex System p24L Compute Node Installation and Service Guide...
  • Page 187 BA120003 • BA130010 BA120003 Explanation: On an undetermined SCSD device, send diagnostic failed; sense data available Response: 1. Troubleshoot the SCSD devices. 2. Verify that the SCSD cables and devices are properly plugged. Correct any problems that are found. 3. Replace the SCSD cables and devices. 4.
  • Page 188 6. Search RETAIN tips and the firmware change history for the reference code to determine the recommended actions. If a firmware update is needed, see Updating the firmware Power Systems: IBM Flex System p24L Compute Node Installation and Service Guide...
  • Page 189 BA130015 • BA140002 BA130015 Explanation: USB CD-ROM in the media tray: ATA/ATAPI packet command execution failed. Response: 1. Remove the CD or DVD in the drive and replace it with a known-good disk. 2. Retry the operation. 3. Reboot the server. 4.
  • Page 190 4. If the problem persists: Search RETAIN tips and the firmware change history for the reference code to determine the recommended actions. If a firmware update is needed, see Updating the firmware Power Systems: IBM Flex System p24L Compute Node Installation and Service Guide...
  • Page 191 BA153002 • BA154030 BA153002 Explanation: Gigabit Ethernet adapter failure Response: Verify that the MAC address programmed in the FLASH/EEPROM is correct. BA153003 Explanation: Gigabit Ethernet adapter failure Response: 1. Reboot the server. 2. Check for server firmware updates; install the updates if available. 3.
  • Page 192 Explanation: The command to retrieve the MAC address from the adapter failed. Response: 1. Check for and apply any adapter microcode or firmware driver updates. 2. Replace adapter specified by the location code that was reported with the SRC. Power Systems: IBM Flex System p24L Compute Node Installation and Service Guide...
  • Page 193 BA170000 • BA170203 BA170000 Explanation: NVRAMRC initialization failed; device test failed Response: 1. Reboot the server. 2. Check for server firmware updates; install the updates if available. 3. If the problem persists: Search RETAIN tips and the firmware change history for the reference code to determine the recommended actions.
  • Page 194 2. Search RETAIN tips and the firmware change history for the reference code to determine the recommended actions. If a firmware update is needed, see Updating the firmware Power Systems: IBM Flex System p24L Compute Node Installation and Service Guide...
  • Page 195 BA180008 • BA180012 BA180008 Explanation: PCI device Fcode evaluation error Response: 1. Reboot the server. 2. Search RETAIN tips and the firmware change history for the reference code to determine the recommended actions. If a firmware update is needed, see Updating the firmware BA180009 Explanation: The Fcode on a PCI adapter left a data stack imbalance Response:...
  • Page 196 If a firmware update is needed, see Updating the firmware BA180100 Explanation: The FDDI adapter Fcode driver is not supported on this server. Response: IBM may produce a compatible driver in the future, but does not guarantee one. BA180101 Explanation: Stack underflow from fibre-channel adapter Response: 1.
  • Page 197 BA190001 • BA210000 BA190001 Explanation: Firmware function to get/set time-of-day reported an error Response: 1. Reboot the server. 2. Check for server firmware updates; install the updates if available. 3. Search RETAIN tips and the firmware change history for the reference code to determine the recommended actions.
  • Page 198 2. Search RETAIN tips and the firmware change history for the reference code to determine the recommended actions. If a firmware update is needed, see Updating the firmware Power Systems: IBM Flex System p24L Compute Node Installation and Service Guide...
  • Page 199 BA210011 • BA210100 BA210011 Explanation: The transfer of control to the IO reporter failed Response: 1. Reboot the server. 2. Search RETAIN tips and the firmware change history for the reference code to determine the recommended actions. If a firmware update is needed, see Updating the firmware BA210012 Explanation: There was an NVRAMRC forced-boot problem;...
  • Page 200 3. If the problem persists: Search RETAIN tips and the firmware change history for the reference code to determine the recommended actions. If a firmware update is needed, see Updating the firmware Power Systems: IBM Flex System p24L Compute Node Installation and Service Guide...
  • Page 201 BA220020 • BA278006 BA220020 Explanation: CRQ registration error; partner vslot may not be valid Response: Verify that this client virtual slot device has a valid server virtual slot device in a hosting partition. BA278001 Explanation: Failed to flash firmware: invalid image file Response: Download a new firmware update image and retry the update.
  • Page 202 3. Search RETAIN tips and the firmware change history for the reference code to determine the recommended actions. If a firmware update is needed, see Updating the firmware Power Systems: IBM Flex System p24L Compute Node Installation and Service Guide...
  • Page 203 BA290001 • BA310030 BA290001 Explanation: RTAS low memory corruption was detected Response: 1. Reboot the server. 2. Check for server firmware updates; install the updates if available. 3. Search RETAIN tips and the firmware change history for the reference code to determine the recommended actions.
  • Page 204 3. Search RETAIN tips and the firmware change history for the reference code to determine the recommended actions. If a firmware update is needed, see Updating the firmware Power Systems: IBM Flex System p24L Compute Node Installation and Service Guide...
  • Page 205 BA340001 • BA340004 BA340001 Explanation: There was a logical partition event communication failure reading the BladeCenter open fabric manager parameter data structure from the service processor. Response: 1. Reboot the server. 2. Check for server firmware updates; install the updates if available. 3.
  • Page 206 3. Search RETAIN tips and the firmware change history for the reference code to determine the recommended actions. If a firmware update is needed, see Updating the firmware Power Systems: IBM Flex System p24L Compute Node Installation and Service Guide...
  • Page 207 BA340009 • BA340020 BA340009 Explanation: An internal firmware error occurred; the open fabric manager system initiator capability processing encountered an unexpected error. Response: 1. Reboot the server. 2. Check for server firmware updates; install the updates if available. 3. Search RETAIN tips and the firmware change history for the reference code to determine the recommended actions.
  • Page 208 2. For checkpoints with location codes, see “Location codes” on page 87 to identify the failing component when there is a hang condition. 3. For eight-digit codes not listed here, see Progress codes overview in the Systems Hardware information center. Power Systems: IBM Flex System p24L Compute Node Installation and Service Guide...
  • Page 209 C10010XX • C1001F0D Use ASMI to display the error and event logs. See Displaying error and event logs in the IBM Power Systems Hardware Information Center. C1xxyyyy service processor checkpoints: The C1xxyyyy progress codes, or checkpoints, offer information about the initialization of both the service processor and the compute node.
  • Page 210 1. Search RETAIN tips and the firmware change history for the reference code to determine the recommended actions. If a firmware update is needed, see Updating the firmware. 2. Replace the system-board, as described in Replacing the system-board and chassis assembly. Power Systems: IBM Flex System p24L Compute Node Installation and Service Guide...
  • Page 211 C1009X04 • C1009X14 C1009X04 Explanation: Hardware object manager (HOM): build cards IPL step in progress Response: 1. Search RETAIN tips and the firmware change history for the reference code to determine the recommended actions. If a firmware update is needed, see Updating the firmware. 2.
  • Page 212 1. Search RETAIN tips and the firmware change history for the reference code to determine the recommended actions. If a firmware update is needed, see Updating the firmware. 2. Replace the system-board, as described in Replacing the system-board and chassis assembly. Power Systems: IBM Flex System p24L Compute Node Installation and Service Guide...
  • Page 213 C1009X2C • C1009X3A C1009X2C Explanation: Processor initialization in progress Response: 1. Search RETAIN tips and the firmware change history for the reference code to determine the recommended actions. If a firmware update is needed, see Updating the firmware. 2. Replace the system-board, as described in Replacing the system-board and chassis assembly. C1009X30 Explanation: Processor self-synchronization in progress Response:...
  • Page 214 1. Search RETAIN tips and the firmware change history for the reference code to determine the recommended actions. If a firmware update is needed, see Updating the firmware. 2. Replace the system-board, as described in Replacing the system-board and chassis assembly. Power Systems: IBM Flex System p24L Compute Node Installation and Service Guide...
  • Page 215 C1009X4C • C1009X5C C1009X4C Explanation: Processor wire test IPL step in progress Response: 1. Search RETAIN tips and the firmware change history for the reference code to determine the recommended actions. If a firmware update is needed, see Updating the firmware. 2.
  • Page 216 1. Search RETAIN tips and the firmware change history for the reference code to determine the recommended actions. If a firmware update is needed, see Updating the firmware. 2. Replace the system-board, as described in Replacing the system-board and chassis assembly. Power Systems: IBM Flex System p24L Compute Node Installation and Service Guide...
  • Page 217 C1009X6C • C1009X7C C1009X6C Explanation: Processor link initialization step in progress Response: 1. Search RETAIN tips and the firmware change history for the reference code to determine the recommended actions. If a firmware update is needed, see Updating the firmware. 2.
  • Page 218 1. Search RETAIN tips and the firmware change history for the reference code to determine the recommended actions. If a firmware update is needed, see Updating the firmware. 2. Replace the system-board, as described in Replacing the system-board and chassis assembly. Power Systems: IBM Flex System p24L Compute Node Installation and Service Guide...
  • Page 219 C1009X90 • C1009X9C C1009X90 Explanation: Wire test in progress Response: 1. Search RETAIN tips and the firmware change history for the reference code to determine the recommended actions. If a firmware update is needed, see Updating the firmware. 2. Replace the system-board, as described in Replacing the system-board and chassis assembly. C1009X92 Explanation: ASIC restore erepair in progress Response:...
  • Page 220 1. Search RETAIN tips and the firmware change history for the reference code to determine the recommended actions. If a firmware update is needed, see Updating the firmware. 2. Replace the system-board, as described in Replacing the system-board and chassis assembly. Power Systems: IBM Flex System p24L Compute Node Installation and Service Guide...
  • Page 221 C1009XB0 • C1009XBB C1009XB0 Explanation: ASIC I/O initialization step in progress Response: 1. Search RETAIN tips and the firmware change history for the reference code to determine the recommended actions. If a firmware update is needed, see Updating the firmware. 2.
  • Page 222 1. Search RETAIN tips and the firmware change history for the reference code to determine the recommended actions. If a firmware update is needed, see Updating the firmware. 2. Replace the system-board, as described in Replacing the system-board and chassis assembly. Power Systems: IBM Flex System p24L Compute Node Installation and Service Guide...
  • Page 223 C1009XD0 • C103A3XX C1009XD0 Explanation: Message passing waiting period has begun Response: 1. Search RETAIN tips and the firmware change history for the reference code to determine the recommended actions. If a firmware update is needed, see Updating the firmware. 2.
  • Page 224 1. Search RETAIN tips and the firmware change history for the reference code to determine the recommended actions. If a firmware update is needed, see Updating the firmware. 2. Replace the system-board, as described in Replacing the system-board and chassis assembly. Power Systems: IBM Flex System p24L Compute Node Installation and Service Guide...
  • Page 225 If an action solves the problem, you can stop performing the remaining actions. See Chapter 7, “Parts listing for IBM Flex System p24L Compute Node,” on page 79 to determine which components are CRUs and which components are FRUs.
  • Page 226 2. Replace the system-board, as described in Replacing the system-board and chassis assembly. C2001300 Explanation: Initializing ISL roadmap Response: 1. Go to Recovering the system firmware. 2. Replace the system-board, as described in Replacing the system-board and chassis assembly. Power Systems: IBM Flex System p24L Compute Node Installation and Service Guide...
  • Page 227 C20013FF • C2002110 C20013FF Explanation: ISL roadmap initialized successfully Response: 1. Go to Recovering the system firmware. 2. Replace the system-board, as described in Replacing the system-board and chassis assembly. C2001400 Explanation: Initializing SP Communication Area #1 Response: 1. Go to Recovering the system firmware. 2.
  • Page 228 C20023FF Explanation: End acquiring VIO slot locks Response: 1. Go to Recovering the system firmware. 2. Replace the system-board, as described in Replacing the system-board and chassis assembly. Power Systems: IBM Flex System p24L Compute Node Installation and Service Guide...
  • Page 229 C2002400 • C2003100 C2002400 Explanation: Begin powering on slots Response: 1. Go to Recovering the system firmware. 2. Replace the system-board, as described in Replacing the system-board and chassis assembly. C2002450 Explanation: Waiting for power on of slots to complete Response: 1.
  • Page 230 2. Replace the system-board, as described in Replacing the system-board and chassis assembly. C20032FF Explanation: ISL command complete successfully Response: 1. Go to Recovering the system firmware. 2. Replace the system-board, as described in Replacing the system-board and chassis assembly. Power Systems: IBM Flex System p24L Compute Node Installation and Service Guide...
  • Page 231 C2003300 • C2004300 C2003300 Explanation: Start SoftPOR of a failed ISL slot Response: 1. Go to Recovering the system firmware. 2. Replace the system-board, as described in Replacing the system-board and chassis assembly. C2003350 Explanation: Waiting for SoftPOR of a failed ISL slot Response: 1.
  • Page 232 2. Replace the system-board, as described in Replacing the system-board and chassis assembly. C2006030 Explanation: Priming LP configuration LID Response: 1. Go to Recovering the system firmware. 2. Replace the system-board, as described in Replacing the system-board and chassis assembly. Power Systems: IBM Flex System p24L Compute Node Installation and Service Guide...
  • Page 233 C2006040 • C20062FF C2006040 Explanation: Preparing to initiate LID load from load source Response: 1. Go to Recovering the system firmware. 2. Replace the system-board, as described in Replacing the system-board and chassis assembly. C2006050 Explanation: LP configuration LID primed successfully Response: 1.
  • Page 234 Explanation: Initializing service processor communication area #2 Response: 1. Go to Recovering the system firmware. 2. Replace the system-board, as described in Replacing the system-board and chassis assembly. Power Systems: IBM Flex System p24L Compute Node Installation and Service Guide...
  • Page 235 C2008104 • C200813F C2008104 Explanation: Loading data structures into main store Response: 1. Go to Recovering the system firmware. 2. Replace the system-board, as described in Replacing the system-board and chassis assembly. C2008110 Explanation: Initializing event paths Response: 1. Go to Recovering the system firmware. 2.
  • Page 236 If an action solves the problem, you can stop performing the remaining actions. See Chapter 7, “Parts listing for IBM Flex System p24L Compute Node,” on page 79 to determine which components are CRUs and which components are FRUs.
  • Page 237 If an action solves the problem, you can stop performing the remaining actions. See Chapter 7, “Parts listing for IBM Flex System p24L Compute Node,” on page 79 to determine which components are CRUs and which components are FRUs.
  • Page 238 2. Replace the system-board, as described in Replacing the system-board and chassis assembly. CA000050 Explanation: Attempting to load RTAS firmware Response: 1. Go to Checkout procedure. 2. Replace the system-board, as described in Replacing the system-board and chassis assembly. Power Systems: IBM Flex System p24L Compute Node Installation and Service Guide...
  • Page 239 CA000060 • CA000091 CA000060 Explanation: Attempting to obtain open firmware details Response: 1. Go to Checkout procedure. 2. Replace the system-board, as described in Replacing the system-board and chassis assembly. CA000070 Explanation: Attempting to load open firmware Response: 1. Go to Checkout procedure. 2.
  • Page 240 2. Replace the system-board, as described in Replacing the system-board and chassis assembly. CA00D008 Explanation: Initialize console and flush queues Response: 1. Go to Checkout procedure. 2. Replace the system-board, as described in Replacing the system-board and chassis assembly. Power Systems: IBM Flex System p24L Compute Node Installation and Service Guide...
  • Page 241 CA00D00C • CA00D013 CA00D00C Explanation: The partition firmware is about to search for an NVRAM script Response: 1. Go to Checkout procedure. 2. Replace the system-board, as described in Replacing the system-board and chassis assembly. CA00D00D Explanation: Evaluating NVRAM script Response: 1.
  • Page 242 Response: Go to Boot problem resolution. CA00E10A Explanation: Load RTAS device tree Response: 1. Go to Checkout procedure. 2. Replace the system-board, as described in Replacing the system-board and chassis assembly. Power Systems: IBM Flex System p24L Compute Node Installation and Service Guide...
  • Page 243 CA00E10B • CA00E134 CA00E10B Explanation: Set RTAS device properties Response: 1. Go to Checkout procedure. 2. Replace the system-board, as described in Replacing the system-board and chassis assembly. CA00E110 Explanation: Create KDUMP properties Response: 1. Reboot the server. 2. If the problem persists: a.
  • Page 244 2. Replace the system-board, as described in Replacing the system-board and chassis assembly. CA00E139 Explanation: Create aliases node and system aliases Response: 1. Go to Checkout procedure. 2. Replace the system-board, as described in Replacing the system-board and chassis assembly. Power Systems: IBM Flex System p24L Compute Node Installation and Service Guide...
  • Page 245 CA00E13A • CA00E141 CA00E13A Explanation: Create packages node Response: 1. Go to Checkout procedure. 2. Replace the system-board, as described in Replacing the system-board and chassis assembly. CA00E13B Explanation: Create HEA node Response: 1. Reboot the server. 2. If the problem persists: a.
  • Page 246 Response: Go to Boot problem resolution. CA00E150 Explanation: Create host (primary) node Response: 1. Go to Checkout procedure. 2. Replace the system-board, as described in Replacing the system-board and chassis assembly. Power Systems: IBM Flex System p24L Compute Node Installation and Service Guide...
  • Page 247 CA00E151 • CA00E156 CA00E151 Explanation: Probing PCI bus Response: 1. Go to Checkout procedure. 2. Replace the system-board, as described in Replacing the system-board and chassis assembly. CA00E152 Explanation: Probing for adapter FCODE; evaluate if present Response: 1. Go to Checkout procedure. 2.
  • Page 248 The network connections are correct; then, retry the operation. 2. If the problem persists: a. Go to Checkout procedure. b. Replace the system-board, as described in Replacing the system-board and chassis assembly. Power Systems: IBM Flex System p24L Compute Node Installation and Service Guide...
  • Page 249 CA00E175 • CA00E178 CA00E175 Explanation: Bootp request Response: 1. Verify that: v The bootp server is correctly configured; then, retry the operation. v The network connections are correct; then, retry the operation. 2. If the problem persists: a. Go to Checkout procedure. b.
  • Page 250 1. Go to Checkout procedure. 2. Replace the system-board, as described in Replacing the system-board and chassis assembly. CA00E198 Explanation: The system is rebooting to enact changes that were specified in ibm,client-architecture-support Response: Go to Boot problem resolution. CA00E199 Explanation: The system is rebooting to enact changes that were specified in the boot image ELF header Response: 1.
  • Page 251 CA00E19B • CA00E1A3 CA00E19B Explanation: NVRAM menu? variable not found - assume FALSE Response: 1. Go to Checkout procedure. 2. Replace the system-board, as described in Replacing the system-board and chassis assembly. CA00E19D Explanation: Create NVRAM node Response: 1. Go to Checkout procedure. 2.
  • Page 252 Explanation: System booting using default service mode boot list Response: 1. Go to Checkout procedure. 2. Replace the system-board, as described in Replacing the system-board and chassis assembly. Power Systems: IBM Flex System p24L Compute Node Installation and Service Guide...
  • Page 253 CA00E1AC • CA00E1B2 CA00E1AC Explanation: System booting using customized service mode boot list Response: 1. Go to Checkout procedure. 2. Replace the system-board, as described in Replacing the system-board and chassis assembly. CA00E1AD Explanation: System booting to the operating system Response: 1.
  • Page 254 2. Replace the system-board, as described in Replacing the system-board and chassis assembly. CA00E1D4 Explanation: Create SCSD byte device node (ST) Response: 1. Go to Checkout procedure. 2. Replace the system-board, as described in Replacing the system-board and chassis assembly. Power Systems: IBM Flex System p24L Compute Node Installation and Service Guide...
  • Page 255 CA00E1DC • CA00E1F2 CA00E1DC Explanation: Dynamic console selection Response: 1. Verify the video session and the SOL session. The console might be redirected to the video controller. 2. Start a remote control session or access the local KVM to see the status. 3.
  • Page 256 Explanation: Build boot device list for SCSD adapters. (The location code of the SCSD adapter being scanned is also displayed.) Response: 1. Go to Checkout procedure. 2. Replace the system-board, as described in Replacing the system-board and chassis assembly. Power Systems: IBM Flex System p24L Compute Node Installation and Service Guide...
  • Page 257 CA00E1F9 • CA00E1FE CA00E1F9 Explanation: Build boot device list for fibre-channel adapters. (The location code of the SAN adapter being scanned is also displayed.) Response: 1. Go to Checkout procedure. 2. Replace the system-board, as described in Replacing the system-board and chassis assembly. CA00E1FA Explanation: Building device list for SCSD adapters.
  • Page 258 Response: 1. Reboot the server. 2. If the problem persists: a. Go to Checkout procedure. b. Replace the system-board, as described in Replacing the system-board and chassis assembly. Power Systems: IBM Flex System p24L Compute Node Installation and Service Guide...
  • Page 259 CA00E701 • CA00E840 CA00E701 Explanation: Create memory VPD Response: 1. Go to Checkout procedure. 2. Replace the system-board, as described in Replacing the system-board and chassis assembly. CA00E800 Explanation: Initialize RTAS Response: 1. Go to Checkout procedure. 2. Replace the system-board, as described in Replacing the system-board and chassis assembly. CA00E810 Explanation: Initializing ioconfig pfds Response:...
  • Page 260 2. Replace the system-board, as described in Replacing the system-board and chassis assembly. CA00E875 Explanation: Initializing rtas_last_error Response: 1. Go to Checkout procedure. 2. Replace the system-board, as described in Replacing the system-board and chassis assembly. Power Systems: IBM Flex System p24L Compute Node Installation and Service Guide...
  • Page 261 CA00E876 • CA00E887 CA00E876 Explanation: Initializing rtas_error_inject Response: 1. Go to Checkout procedure. 2. Replace the system-board, as described in Replacing the system-board and chassis assembly. CA00E877 Explanation: Initializing dump interface Response: 1. Go to Checkout procedure. 2. Replace the system-board, as described in Replacing the system-board and chassis assembly. CA00E879 Explanation: Initializing the platform-assisted kdump interface Response:...
  • Page 262 Response: 1. Reboot the server. 2. If the problem persists: a. Go to Checkout procedure. b. Replace the system-board, as described in Replacing the system-board and chassis assembly. Power Systems: IBM Flex System p24L Compute Node Installation and Service Guide...
  • Page 263 CA279001 • CA2799FF CA279001 Explanation: The firmware update image contains an update module that is not already on the system. Response: 1. Look at the event log for a BA27xxxx error code to determine if a firmware installation error occurred. 2.
  • Page 264 If an action solves the problem, you can stop performing the remaining actions. See Chapter 7, “Parts listing for IBM Flex System p24L Compute Node,” on page 79 to determine which components are CRUs and which components are FRUs.
  • Page 265 D101C00F • D1061XXX D101C00F Explanation: No power off to allow debugging for CPU controls Response: 1. Go to Checkout procedure. 2. Replace the system-board, as described in Replacing the system-board and chassis assembly. D1021XXX Explanation: Dump dump header directory Response: 1.
  • Page 266 2. Replace the system-board, as described in Replacing the system-board and chassis assembly. D1131XXX Explanation: Dump all traces Response: 1. Go to Checkout procedure. 2. Replace the system-board, as described in Replacing the system-board and chassis assembly. Power Systems: IBM Flex System p24L Compute Node Installation and Service Guide...
  • Page 267 D1141XXX • D1191XXX D1141XXX Explanation: Dump code version Response: 1. Go to Checkout procedure. 2. Replace the system-board, as described in Replacing the system-board and chassis assembly. D1151XXX Explanation: Dump all /opt/p3 except rtbl Response: 1. Go to Checkout procedure. 2.
  • Page 268 2. Replace the system-board, as described in Replacing the system-board and chassis assembly. D1241XXX Explanation: Dump CRC1 calculation off Response: 1. Go to Checkout procedure. 2. Replace the system-board, as described in Replacing the system-board and chassis assembly. Power Systems: IBM Flex System p24L Compute Node Installation and Service Guide...
  • Page 269 D1251XXX • D12A1XXX D1251XXX Explanation: Dump CRC1 calculation on Response: 1. Go to Checkout procedure. 2. Replace the system-board, as described in Replacing the system-board and chassis assembly. D1261XXX Explanation: Dump CRC2 calculation off Response: 1. Go to Checkout procedure. 2.
  • Page 270 D1301XXX Explanation: Turn off error log capture into dump Response: 1. Go to Checkout procedure. 2. Replace the system-board, as described in Replacing the system-board and chassis assembly. Power Systems: IBM Flex System p24L Compute Node Installation and Service Guide...
  • Page 271 D1311XXX • D13B1XXX D1311XXX Explanation: Turn on error log capture into dump Response: 1. Go to Checkout procedure. 2. Replace the system-board, as described in Replacing the system-board and chassis assembly. D1321XXX Explanation: Store information about existing core files Response: 1.
  • Page 272 If an action solves the problem, you can stop performing the remaining actions. See Chapter 7, “Parts listing for IBM Flex System p24L Compute Node,” on page 79 to determine which components are CRUs and which components are FRUs.
  • Page 273 D1XX3Y03 • D1XX3Y08 D1XX3Y03 Explanation: Get array values Response: 1. Go to Checkout procedure. 2. Replace the system-board, as described in Replacing the system-board and chassis assembly. D1XX3Y04 Explanation: Stop the clocks Response: 1. Go to Checkout procedure. 2. Replace the system-board, as described in Replacing the system-board and chassis assembly. D1XX3Y05 Explanation: Flush the cache Response:...
  • Page 274 2. Replace the system-board, as described in Replacing the system-board and chassis assembly. D1XX3YF0 Explanation: Memory collection set-up Response: 1. Go to Checkout procedure. 2. Replace the system-board, as described in Replacing the system-board and chassis assembly. Power Systems: IBM Flex System p24L Compute Node Installation and Service Guide...
  • Page 275 If an action solves the problem, you can stop performing the remaining actions. See Chapter 7, “Parts listing for IBM Flex System p24L Compute Node,” on page 79 to determine which components are CRUs and which components are FRUs.
  • Page 276 The third column describes the problem and an action to take to try to fix the problem. The description also includes how to find the FFC number for an SRN if one exists. Power Systems: IBM Flex System p24L Compute Node Installation and Service Guide...
  • Page 277 101-711 • 101-713 2. See “Failing function codes” on page 409 for a description of each FFC value. 3. If the SRN does not appear in the table, see “Solving undetermined problems” on page 457. 101-711 through FFC-725 SRNs: ® The AIX operating system might generate service request numbers (SRNs) from 101-711 to FFC-725.
  • Page 278 2. If the problem remains, refer to Failing function codes to find the FFC that matches the last three digits of the SRN. 3. Suspect the device adapter or device itself. Response: Failing Item: v FFC_717 Power Systems: IBM Flex System p24L Compute Node Installation and Service Guide...
  • Page 279 101-718 • 101-721 101-718 Explanation: The system hung while trying to configure an unknown resource. 1. Run the stand-alone diagnostics problem determination procedure. 2. If the problem remains, refer to Failing function codes to find the FFC that matches the last three digits of the SRN.
  • Page 280 2. If the problem remains, refer to Failing function codes to find the FFC that matches the last three digits of the SRN. 3. Suspect the device adapter or device itself. Response: Failing Item: v FFC_725 Power Systems: IBM Flex System p24L Compute Node Installation and Service Guide...
  • Page 281 101-726 • 109-200 101-726 Explanation: The system hung while trying to configure an unknown resource. 1. Run the stand-alone diagnostics problem determination procedure. 2. If the problem remains, refer to Failing function codes to find the FFC that matches the last three digits of the SRN.
  • Page 282 Explanation: The system halted while diagnostics were executing. Go to Performing the checkout procedure or problem resolution. Note: xxx corresponds to the last three digits of the SRN. Response: Failing Item: v FFC_812 v FFC_XXX Power Systems: IBM Flex System p24L Compute Node Installation and Service Guide...
  • Page 283 110-924 • 110-935 110-924 Explanation: The system halted while diagnostics were executing. Go to Performing the checkout procedure or problem resolution. Note: xxx corresponds to the last three digits of the SRN. Response: Failing Item: v FFC_812 v FFC_XXX 110-925 Explanation: The system halted while diagnostics were executing.
  • Page 284 Explanation: System does not perform a soft reset. Go to Performing the checkout procedure. Response: Failing Item: v FFC_210 650-XXX Explanation: Disk drive configuration failed. Replace the FRU identified by diagnostics. Response: Failing Item: v FFC_650 Power Systems: IBM Flex System p24L Compute Node Installation and Service Guide...
  • Page 285 651-199 • 652-612 651-199 Explanation: This is a test of the flow of a serviceable event from this system to management console. This is not a real problem. Response: Problem determination: Use the management console to list serviceable events and verify the serviceable event was sent to the HMC.
  • Page 286 FFC_307 652-632 Explanation: A non-critical error has been detected: I/O expansion bus connection failure. Schedule deferred maintenance. Go to Performing the checkout procedure. Response: Failing Item: v FFC_307 Power Systems: IBM Flex System p24L Compute Node Installation and Service Guide...
  • Page 287 652-633 • 652-666 652-633 Explanation: A non-critical error has been detected: I/O expansion unit not in an operating state. Schedule deferred maintenance. Go to Performing the checkout procedure. Response: Failing Item: v FFC_307 652-634 Explanation: A non-critical error has been detected: internal device error. Schedule deferred maintenance. Go to Performing the checkout procedure.
  • Page 288 Explanation: A non-critical error has been detected: intermediate or system bus data parity error. Schedule deferred maintenance. Go to Performing the checkout procedure. Response: Failing Item: v FFC_2C8 Power Systems: IBM Flex System p24L Compute Node Installation and Service Guide...
  • Page 289 652-733 • 652-736 652-733 Explanation: A non-critical error has been detected: intermediate or system bus address parity error. Schedule deferred maintenance. Go to Performing the checkout procedure. Response: Failing Item: v FFC_2C8 v FFC_292 652-734 Explanation: A non-critical error has been detected: intermediate or system bus data parity error. Schedule deferred maintenance.
  • Page 290 3. If the 8-digit error and location codes were NOT reported, then run diagnostics in problem determination mode and record and report the 8-digit error and location codes for this SRN. Response: Power Systems: IBM Flex System p24L Compute Node Installation and Service Guide...
  • Page 291 652-89X • 815-100 652-89X Explanation: The CEC or SPCN reported a non-critical error. 1. Schedule deferred maintenance. 2. Refer to the entry MAP in this system unit system service guide, with the 8-digit error and location codes, for the necessary repair action. 3.
  • Page 292 Go to Performing the checkout procedure. Response: Failing Item: v FFC_815 817-123 Explanation: The I/O planar time-of-day clock test failed. Go to Performing the checkout procedure. Response: Failing Item: v FFC_817 Power Systems: IBM Flex System p24L Compute Node Installation and Service Guide...
  • Page 293 817-124 • 817-215 817-124 Explanation: Time of day RAM test failed. Go to Performing the checkout procedure. Response: Failing Item: v FFC_817 817-210 Explanation: The time-of-day clock is at POR. Go to Performing the checkout procedure. Response: Failing Item: v FFC_817 817-211 Explanation: Time of day POR test failed.
  • Page 294 Explanation: Vital Product Data (VPD) failed. Go to Performing the checkout procedure. Response: Failing Item: v FFC_887 887-105 Explanation: LAN coprocessor internal tests failed. Go to Performing the checkout procedure. Response: Failing Item: v FFC_887 Power Systems: IBM Flex System p24L Compute Node Installation and Service Guide...
  • Page 295 887-106 • 887-111 887-106 Explanation: Internal loopback test failed. Go to Performing the checkout procedure. Response: Failing Item: v FFC_887 887-107 Explanation: External loopback test failed. Go to Performing the checkout procedure. Response: Failing Item: v FFC_887 887-108 Explanation: External loopback test failed. Go to Performing the checkout procedure. Response: Failing Item: v FFC_887...
  • Page 296 Explanation: External loopback (twisted pair) fairness and parity tests failed. Go to Performing the checkout procedure. Response: Failing Item: v FFC_887 887-116 Explanation: Twisted pair wrap data failed. Go to Performing the checkout procedure. Response: Failing Item: v FFC_887 Power Systems: IBM Flex System p24L Compute Node Installation and Service Guide...
  • Page 297 887-117 • 887-123 887-117 Explanation: Software device configuration fails. Go to Performing the checkout procedure. Response: Failing Item: v FFC_887 887-118 Explanation: Device driver indicates a hardware problem. Go to Performing the checkout procedure. Response: Failing Item: v FFC_887 887-120 Explanation: Device driver indicates a hardware problem.
  • Page 298 Explanation: RJ-45 converter test failed. Go to Performing the checkout procedure. Response: Failing Item: v FFC_887 887-304 Explanation: Coprocessor internal test failed. Go to Performing the checkout procedure. Response: Failing Item: v FFC_887 Power Systems: IBM Flex System p24L Compute Node Installation and Service Guide...
  • Page 299 887-305 • 887-401 887-305 Explanation: Internal loopback test failed. Go to Performing the checkout procedure. Response: Failing Item: v FFC_887 887-306 Explanation: Internal loopback test failed. Go to Performing the checkout procedure. Response: Failing Item: v FFC_887 887-307 Explanation: External loopback test failed. Go to Performing the checkout procedure. Response: Failing Item: v FFC_887...
  • Page 300 Explanation: The system hung while configuring a resource. The last three or four digits after the dash (-) identify the failing function code for the resource being configured. Go to undetermined problem procedure. Response: Failing Item: v FFC_XXXX Power Systems: IBM Flex System p24L Compute Node Installation and Service Guide...
  • Page 301 110-XXXX • 252B-711 110-XXXX Explanation: The system halted while diagnostics were executing. Note: xxxx corresponds to the last three or four digits of the SRN following the dash (-). 1. If your 110 SRN is not listed, substitute the last three or four digits of the SRN for xxxx and go to Failing function codes to identify the failing feature.
  • Page 302 1. Check the BladeCenter management-module event log. If an error was recorded by the system, see POST progress codes (checkpoints). 2. Replace any parts reported by the diagnostic program. 3. Replace the system-board Response: Failing Item: v FFC_252B Power Systems: IBM Flex System p24L Compute Node Installation and Service Guide...
  • Page 303 252B-716 • 252B-718 252B-716 Explanation: PCI bus error detected by EEH. 1. Check the BladeCenter management-module event log. If an error was recorded by the system, see POST progress codes (checkpoints). 2. Replace any parts reported by the diagnostic program. 3.
  • Page 304 1. Check the BladeCenter management-module event log. If an error was recorded by the system, see POST progress codes (checkpoints). 2. Replace any parts reported by the diagnostic program. 3. Replace the system-board Response: Failing Item: v FFC_252B Power Systems: IBM Flex System p24L Compute Node Installation and Service Guide...
  • Page 305 252B-723 • 254E-603 252B-723 Explanation: Device bus interface problem. 1. Check the BladeCenter management-module event log. If an error was recorded by the system, see POST progress codes (checkpoints). 2. Replace any parts reported by the diagnostic program. 3. Replace the system-board Response: Failing Item: v FFC_252B...
  • Page 306 Explanation: Error log analysis indicates permanent adapter failure is reported on the other port of this adapter. Go to Performing the checkout procedure. Response: Failing Item: v FFC_254E v FFC_221 Power Systems: IBM Flex System p24L Compute Node Installation and Service Guide...
  • Page 307 2567-XXX • 256D-602 2567-XXX Explanation: USB integrated system-board and chassis assembly. Go to Performing the checkout procedure. Response: Failing Item: v FFC_2567 256D-201 Explanation: Adapter configuration error. 1. Check the BladeCenter management-module event log. If an error was recorded by the system, see POST progress codes (checkpoints).
  • Page 308 1. Check the BladeCenter management-module event log. If an error was recorded by the system, see POST progress codes (checkpoints). 2. Replace any parts reported by the diagnostic program. 3. Replace the system-board Response: Failing Item: v FFC_256D Power Systems: IBM Flex System p24L Compute Node Installation and Service Guide...
  • Page 309 256D-701 • 25C4-601 256D-701 Explanation: Error Log Analysis indicates permanent adapter failure. 1. Check the BladeCenter management-module event log. If an error was recorded by the system, see POST progress codes (checkpoints). 2. Replace any parts reported by the diagnostic program. 3.
  • Page 310 Response: Failing Item: v FFC_2604 2604-104 Explanation: SRAM Test failure for the Fibre Channel adapter card. Replace the 4Gb Fibre Channel Adapter card. Response: Failing Item: v FFC_2604 Power Systems: IBM Flex System p24L Compute Node Installation and Service Guide...
  • Page 311 2604-105 • 2604-201 2604-105 Explanation: Internal Wrap Test failure for the Fibre Channel adapter card. Replace the 4Gb Fibre Channel Adapter card. Response: Failing Item: v FFC_2604 2604-106 Explanation: Gigabit Link Module (GLM) Wrap Test failure for the Fibre Channel adapter card. Replace the 4Gb Fibre Channel Adapter card.
  • Page 312 Explanation: Error Log Analysis indicates that an unknown adapter error has occurred for the Fibre Channel adapter card. Go to Performing the checkout procedure. Response: Failing Item: v FFC_2604 Power Systems: IBM Flex System p24L Compute Node Installation and Service Guide...
  • Page 313 2604-704 • 2607-102 2604-704 Explanation: Error Log Analysis indicates that an adapter error has occurred for the Fibre Channel adapter card. Go to Performing the checkout procedure. Response: Failing Item: v FFC_2604 2604-705 Explanation: Error Log Analysis indicates that a parity error has been detected for the Fibre Channel adapter card. The adapter must be replaced immediately.
  • Page 314 2607-108 Explanation: Enhanced Error Handling Failure on the bus for the Fibre Channel adapter card. Go to Performing the checkout procedure. Response: Failing Item: v FFC_2607 v FFC_221 Power Systems: IBM Flex System p24L Compute Node Installation and Service Guide...
  • Page 315 2607-110 • 2607-205 2607-110 Explanation: Enhanced Error Handling Failure on the Fibre Channel adapter card. Replace the 8Gb PCIe Fibre Channel Expansion Card. Response: Failing Item: v FFC_2607 2607-201 Explanation: Configuration Register Test Failure for the Fibre Channel adapter card. Go to Performing the checkout procedure.
  • Page 316 Failure to adhere to this action could result in data being read or written incorrectly or in the loss of data. Response: Failing Item: v FFC_2607 Power Systems: IBM Flex System p24L Compute Node Installation and Service Guide...
  • Page 317 2607-XXX • 2624-201 2607-XXX Explanation: Generic reference for 8Gb PCIe Fibre Channel Expansion Card. Go to Performing the checkout procedure. Response: Failing Item: v FFC_2607 2624-101 Explanation: Configuration failure. Replace the 4X PCI-E DDR InfiniBand Host Channel Adapter. Response: Failing Item: v FFC_2624 2624-102 Explanation: Queue pair create failure.
  • Page 318 Explanation: Error Log Analysis indicates that this adapter has failed due to a memory error. Replace the 4X PCI-E DDR InfiniBand Host Channel Adapter. Response: Failing Item: v FFC_2624 Power Systems: IBM Flex System p24L Compute Node Installation and Service Guide...
  • Page 319 2624-704 • 2625-101 2624-704 Explanation: Error Log Analysis indicates that this adapter has failed due to a unrecoverable internal parity error Replace the 4X PCI-E DDR InfiniBand Host Channel Adapter. Response: Failing Item: v FFC_2624 2624-705 Explanation: Error Log Analysis indicates that this adapter has failed due to a internal error. Replace the 4X PCI-E DDR InfiniBand Host Channel Adapter.
  • Page 320 3. Verify that the network is functional. 4. Verify that the network switch is functional. 5. Go to Performing the checkout procedure. Response: Failing Item: v CABLE v NETWORK v FFC_2625 Power Systems: IBM Flex System p24L Compute Node Installation and Service Guide...
  • Page 321 2625-701 • 2625-705 2625-701 Explanation: Error Log Analysis indicates that this adapter has failed due to an internal error. Replace the 2-port QDR 40 GB/S InfiniBand expansion card (CFFh). Response: Failing Item: v FFC_2625 2625-702 Explanation: Error Log Analysis indicates that this adapter has failed due to a failure with the uplink interface used to connect this device to the host processor.
  • Page 322 Explanation: Configuration failure. Replace the IBM Flex System IB6132 QDR InfiniBand Adapter. Response: Failing Item: v FFC_2627 2627-102 Explanation: Queue pair create failure. Replace the IBM Flex System IB6132 QDR InfiniBand Adapter. Response: Failing Item: v FFC_2627 2627-103 Explanation: Loop back test failure. Replace the IBM Flex System IB6132 QDR InfiniBand Adapter.
  • Page 323 Response: Failing Item: v CABLE v NETWORK v FFC_2627 2627-701 Explanation: Error Log Analysis indicates that this adapter has failed due to an internal error. Replace the IBM Flex System IB6132 QDR InfiniBand Adapter. Response: Failing Item: v FFC_2627 2627-702 Explanation: Error Log Analysis indicates that this adapter has failed due to a failure with the uplink interface used to connect this device to the host processor.
  • Page 324 2627-703 • 2640-121 2627-703 Explanation: Error Log Analysis indicates that this adapter has failed due to a memory error. Replace the IBM Flex System IB6132 QDR InfiniBand Adapter. Response: Failing Item: v FFC_2627 2627-704 Explanation: Error Log Analysis indicates that this adapter has failed due to a unrecoverable internal parity error Replace the IBM Flex System IB6132 QDR InfiniBand Adapter.
  • Page 325 2640-131 • 2640-136 2640-131 Explanation: Smart status threshold exceeded. Go to Performing the checkout procedure. Response: Failing Item: v FFC_2640 2640-132 Explanation: Command timeouts threshold exceeded. Go to Performing the checkout procedure. Response: Failing Item: v FFC_2640 2640-133 Explanation: Command timeout with error condition. Go to Performing the checkout procedure. Response: Failing Item: v FFC_2640...
  • Page 326 Explanation: The bus test failed. Replace the 300 GB SFF SAS Hard Disk Drive. Response: Failing Item: v FFC_268B 268B-110 Explanation: The media format is corrupted. Replace the 300 GB SFF SAS Hard Disk Drive. Response: Failing Item: v FFC_268B Power Systems: IBM Flex System p24L Compute Node Installation and Service Guide...
  • Page 327 268B-112 • 268B-118 268B-112 Explanation: The diagnostic test failed. Replace the 300 GB SFF SAS Hard Disk Drive. Response: Failing Item: v FFC_268B 268B-114 Explanation: An unrecoverable hardware error. Replace the 300 GB SFF SAS Hard Disk Drive. Response: Failing Item: v FFC_268B 268B-116 Explanation: A protocol error.
  • Page 328 Run the diagnostic program in problem determination mode on each part reported in the original SRN. If the problem persists, replace the next part in the list. Response: Failing Item: v FFC_B88 v FFC_268B Power Systems: IBM Flex System p24L Compute Node Installation and Service Guide...
  • Page 329 268B-129 • 268B-135 268B-129 Explanation: Error log analysis indicates a SCSI bus problem. Replace each part reported by the diagnostic program one at a time. Run the diagnostic program in problem determination mode on each part reported in the original SRN. If the problem persists, replace the next part in the list.
  • Page 330 Run the diagnostic program in problem determination mode on each part reported in the original SRN. If the problem persists, replace the next part in the list. Response: Failing Item: v FFC_B88 v FFC_268B Power Systems: IBM Flex System p24L Compute Node Installation and Service Guide...
  • Page 331 268B-640 • 26B4-108 268B-640 Explanation: Error log analysis indicates a path error. Replace the 300 GB SFF SAS Hard Disk Drive. Response: Failing Item: v FFC_268B 26B4-102 Explanation: An unrecoverable media error occurred. Replace the 200 GB SATA Solid State Drive. Response: Failing Item: v FFC_26B4...
  • Page 332 2. If you do not find a problem, call your operating-system support person. Response: Failing Item: v FFC_26B4 v FFC_26BD 26B4-117 Explanation: A write-protect error occurred. Replace the 200 GB SATA Solid State Drive. Response: Failing Item: v FFC_26B4 Power Systems: IBM Flex System p24L Compute Node Installation and Service Guide...
  • Page 333 26B4-118 • 26B4-124 26B4-118 Explanation: A SCSI command time-out occurred. Replace each part reported by the diagnostic program one at a time. Retry the diagnostic test after each part is replaced. If the problem persists, replace the next part in the list. Response: Failing Item: v FFC_26B4...
  • Page 334 26B4-130 Explanation: Error log analysis indicates a problem reported by the disk drive's self-monitoring function. Replace the 200 GB SATA Solid State Drive. Response: Failing Item: v FFC_26B4 Power Systems: IBM Flex System p24L Compute Node Installation and Service Guide...
  • Page 335 26B4-132 • 26B4-136 26B4-132 Explanation: A disk drive hardware error occurred. Replace each part reported by the diagnostic program one at a time. Retry the diagnostic test after each part is replaced. If the problem persists, replace the next part in the list. Response: Failing Item: v FFC_26B4...
  • Page 336 Explanation: Error log analysis indicates a path error. Replace the SAS to SATA Interposer Card. If the problem persists, replace the 200 GB SATA Solid State Drive. Response: Failing Item: v FFC_26B4 v FFC_26BD Power Systems: IBM Flex System p24L Compute Node Installation and Service Guide...
  • Page 337 26D2-102 • 26D2-110 26D2-102 Explanation: An unrecoverable media error occurred. Replace the 600 GB SFF SAS Hard Disk Drive. Response: Failing Item: v FFC_26D2 26D2-104 Explanation: The motor failed to restart. Replace the 600 GB SFF SAS Hard Disk Drive. Response: Failing Item: v FFC_26D2...
  • Page 338 Explanation: A SCSI command time-out occurred. Replace the 600 GB SFF SAS Hard Disk Drive. Run diagnostics again on the drive. If the error repeats, replace the 2nd FRU identified by diagnostics. Response: Failing Item: v FFC_26D2 v FFC_B88 Power Systems: IBM Flex System p24L Compute Node Installation and Service Guide...
  • Page 339 26D2-120 • 26D2-128 26D2-120 Explanation: A SCSI busy or command error. Replace the 600 GB SFF SAS Hard Disk Drive. Response: Failing Item: v FFC_26D2 26D2-122 Explanation: A SCSI reservation conflict error. Replace the 600 GB SFF SAS Hard Disk Drive. Response: Failing Item: v FFC_26D2...
  • Page 340 Retry the diagnostic test after each part is replaced. If the problem persists, replace the next part in the list. Response: Failing Item: v FFC_26D2 v FFC_B88 v SOFTWARE Power Systems: IBM Flex System p24L Compute Node Installation and Service Guide...
  • Page 341 1. Make sure that: v 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. Response: Failing Item:...
  • Page 342 Explanation: The electronics card test failed. Replace the 900 GB SFF SAS Hard Disk Drive. Response: Failing Item: v FFC_26D7 26D7-108 Explanation: The bus test failed. Replace the 900 GB SFF SAS Hard Disk Drive. Response: Failing Item: v FFC_26D7 Power Systems: IBM Flex System p24L Compute Node Installation and Service Guide...
  • Page 343 26D7-110 • 26D7-117 26D7-110 Explanation: The media format is corrupted. Replace the 900 GB SFF SAS Hard Disk Drive. Response: Failing Item: v FFC_26D7 26D7-112 Explanation: The diagnostic test failed. Replace the 900 GB SFF SAS Hard Disk Drive. Response: Failing Item: v FFC_26D7 26D7-114...
  • Page 344 Explanation: A software error was caused by a hardware failure. Replace the 900 GB SFF SAS Hard Disk Drive. Run diagnostics again on the drive. If the error repeats, replace the 2nd FRU identified by diagnostics. Response: Failing Item: v FFC_26D7 v FFC_B88 Power Systems: IBM Flex System p24L Compute Node Installation and Service Guide...
  • Page 345 26D7-128 • 26D7-134 26D7-128 Explanation: The error log analysis indicates a hardware failure. Replace each part reported by the diagnostic program one at a time. Run the diagnostic program in problem determination mode on each part reported in the original SRN. If the problem persists, replace the next part in the list. Response: Failing Item: v FFC_B88...
  • Page 346 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. Response: Failing Item: v FFC_26D7 Power Systems: IBM Flex System p24L Compute Node Installation and Service Guide...
  • Page 347 26D7-140 • 2750-201 26D7-140 Explanation: Error log analysis indicates poor signal quality. Replace each part reported by the diagnostic program one at a time. Run the diagnostic program in problem determination mode on each part reported in the original SRN. If the problem persists, replace the next part in the list.
  • Page 348 2755-201 Explanation: Adapter configuration error Replace the PCIe2 16Gb 4-port FC Mezzanine Adapter If the problem persists, replace the system board. Response: Failing Item: v FFC_2755 v FFC_221 Power Systems: IBM Flex System p24L Compute Node Installation and Service Guide...
  • Page 349 Explanation: Configuration failure. Replace the IBM Flex System EN4132 2-port 10Gb RoCE Adapter Response: Failing Item: v FFC_2770 2770-102 Explanation: Queue pair create failure. Replace the IBM Flex System EN4132 2-port 10Gb RoCE Adapter Response: Failing Item: v FFC_2770 Chapter 8. Troubleshooting...
  • Page 350 Failing Item: v CABLE v NETWORK v FFC_2770 2770-601 Explanation: Error Log Analysis indicates adapter hardware error Replace the IBM Flex System EN4132 2-port 10Gb RoCE Adapter Response: Failing Item: v FFC_2770 Power Systems: IBM Flex System p24L Compute Node Installation and Service Guide...
  • Page 351 10Gb RoCE Adapter Response: Failing Item: v FFC_2770 2770-701 Explanation: Error Log Analysis indicates that this adapter has failed due to an internal error. Replace the IBM Flex System EN4132 2-port 10Gb RoCE Adapter Response: Failing Item: v FFC_2770 2770-702 Explanation: Error Log Analysis indicates that this adapter has failed due to a failure with the uplink interface used to connect this device to the host processor.
  • Page 352 Replace the IBM Flex System EN4132 2-port 10Gb RoCE Adapter Response: Failing Item: v FFC_2770 2770-705 Explanation: Error Log Analysis indicates that this adapter has failed due to a internal error. Replace the IBM Flex System EN4132 2-port 10Gb RoCE Adapter Response: Failing Item: v FFC_2770 2770-706 Explanation: Error Log Analysis indicates that this adapter has failed due to a memory error.
  • Page 353 2D14-710 • 2D29-713 2D14-710 Explanation: Permanent controller error. Replace the system board (SAS controller). Response: Failing Item: v FFC_2D14 2D14-713 Explanation: Controller error. Replace the system board (SAS controller). Response: Failing Item: v FFC_2D14 2D14-720 Explanation: Controller devce bus configuration error. Use MAP3150 to determine resolution. Response: 2D29-101 Explanation: Adapter configuration error.
  • Page 354 1. Check the BladeCenter management-module event log. If an error was recorded by the system, see POST progress codes (checkpoints). 2. Replace any parts reported by the diagnostic program. 3. Replace the system-board Response: Failing Item: v FFC_2E00 v FFC_221 Power Systems: IBM Flex System p24L Compute Node Installation and Service Guide...
  • Page 355 2E10-201 • 2E10-603 2E10-201 Explanation: Adapter configuration error. 1. Check the BladeCenter management-module event log. If an error was recorded by the system, see POST progress codes (checkpoints). 2. Replace any parts reported by the diagnostic program. 3. Replace the system-board Response: Failing Item: v FFC_2E10...
  • Page 356 1. Check the BladeCenter management-module event log. If an error was recorded by the system, see POST progress codes (checkpoints). 2. Replace any parts reported by the diagnostic program. 3. Replace the system-board Response: Failing Item: v FFC_2E10 v FFC_221 Power Systems: IBM Flex System p24L Compute Node Installation and Service Guide...
  • Page 357 2E10-702 • 2E13-602 2E10-702 Explanation: Error Log Analysis indicates permanent adapter failure. 1. Check the BladeCenter management-module event log. If an error was recorded by the system, see POST progress codes (checkpoints). 2. Replace any parts reported by the diagnostic program. 3.
  • Page 358 1. Check the BladeCenter management-module event log. If an error was recorded by the system, see POST progress codes (checkpoints). 2. Replace any parts reported by the diagnostic program. 3. Replace the system-board Response: Failing Item: v FFC_2E13 Power Systems: IBM Flex System p24L Compute Node Installation and Service Guide...
  • Page 359 2E13-701 • 2E14-201 2E13-701 Explanation: Error Log Analysis indicates permanent adapter failure. 1. Check the BladeCenter management-module event log. If an error was recorded by the system, see POST progress codes (checkpoints). 2. Replace any parts reported by the diagnostic program. 3.
  • Page 360 1. Check the BladeCenter management-module event log. If an error was recorded by the system, see POST progress codes (checkpoints). 2. Replace any parts reported by the diagnostic program. 3. Replace the system-board Response: Failing Item: v FFC_2E14 Power Systems: IBM Flex System p24L Compute Node Installation and Service Guide...
  • Page 361 2E14-605 • 2E14-702 2E14-605 Explanation: 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). 2.
  • Page 362 1. Check the BladeCenter management-module event log. If an error was recorded by the system, see POST progress codes (checkpoints). 2. Replace any parts reported by the diagnostic program. 3. Replace the system-board Response: Failing Item: v FFC_2E15 Power Systems: IBM Flex System p24L Compute Node Installation and Service Guide...
  • Page 363 2E15-604 • 2E15-701 2E15-604 Explanation: Error Log Analysis indicates a permanent adapter failure. 1. Check the BladeCenter management-module event log. If an error was recorded by the system, see POST progress codes (checkpoints). 2. Replace any parts reported by the diagnostic program. 3.
  • Page 364 3. Replace the system-board Response: Failing Item: v FFC_2E15 v FFC_221 2E16-201 Explanation: Adapter configuration error. Replace the IBM Flex System FC3172 2-port 8Gb FC Adapter. If the problem persists, replace the system board. Response: Failing Item: v FFC_2E16 v FFC_221 2E16-601 Explanation: Error log analysis indicates adapter failure.
  • Page 365 2E16-603 • 2E16-701 2E16-603 Explanation: Error log analysis indicates that the microcode could not be loaded on the adapter. Replace the IBM Flex System FC3172 2-port 8Gb FC Adapter. Response: Failing Item: v FFC_2E16 2E16-604 Explanation: Error log analysis indicates a permanent adapter failure. Replace the IBM Flex System FC3172 2-port 8Gb FC Adapter.
  • Page 366 2E16-702 • 2E21-602 2E16-702 Explanation: Error log analysis indicates permanent adapter failure is reported on the other port of this adapter. Replace the IBM Flex System FC3172 2-port 8Gb FC Adapter. If the problem persists, replace the system board. Response: Failing Item:...
  • Page 367 2E21-603 • 2E21-606 2E21-603 Explanation: Error Log Analysis indicates that the microcode could not be loaded on the adapter. 1. Check the BladeCenter management-module event log. If an error was recorded by the system, see POST progress codes (checkpoints). 2. Replace any parts reported by the diagnostic program. 3.
  • Page 368 1. Check the BladeCenter management-module event log. If an error was recorded by the system, see POST progress codes (checkpoints). 2. Replace any parts reported by the diagnostic program. 3. Replace the system-board Response: Failing Item: v FFC_2E23 Power Systems: IBM Flex System p24L Compute Node Installation and Service Guide...
  • Page 369 2E23-103 • 2E23-106 2E23-103 Explanation: Flash Test Failure 1. Check the BladeCenter management-module event log. If an error was recorded by the system, see POST progress codes (checkpoints). 2. Replace any parts reported by the diagnostic program. 3. Replace the system-board Response: Failing Item: v FFC_2E23...
  • Page 370 1. Check the BladeCenter management-module event log. If an error was recorded by the system, see POST progress codes (checkpoints). 2. Replace any parts reported by the diagnostic program. 3. Replace the system-board Response: Failing Item: v FFC_2E23 v FFC_221 Power Systems: IBM Flex System p24L Compute Node Installation and Service Guide...
  • Page 371 2E23-202 • 2E23-603 2E23-202 Explanation: Network link test failure. 1. Check the BladeCenter management-module event log. If an error was recorded by the system, see POST progress codes (checkpoints). 2. Replace any parts reported by the diagnostic program. 3. Replace the system-board Response: Failing Item: v FFC_241...
  • Page 372 2. Replace any parts reported by the diagnostic program. 3. Replace the system-board Response: Failing Item: v FFC_2E23 2E28-201 Explanation: Adapter configuration error Replace the IBM Flex System CN4058 8-port 10Gb Converged Adapter If the problem persists, replace the system board. Response: Failing Item: v FFC_2E28 v FFC_221 2E28-601 Explanation: Adapter taken off-line.
  • Page 373 Explanation: Adapter down error Replace the IBM Flex System CN4058 8-port 10Gb Converged Adapter Response: Failing Item: v FFC_2E28 2E29-201 Explanation: Adapter configuration error Replace the IBM Flex System CN4058 8-port 10Gb Converged Adapter If the problem persists, replace the system board. Response: Failing Item: v FFC_2E29...
  • Page 374 2E29-604 • 2E33-602 2E29-604 Explanation: Adapter down error Replace the IBM Flex System CN4058 8-port 10Gb Converged Adapter Response: Failing Item: v FFC_2E29 2E33-201 Explanation: Adapter configuration error. 1. Check the BladeCenter management-module event log. If an error was recorded by the system, see POST progress codes (checkpoints).
  • Page 375 2E33-701 • 2E34-602 2E33-701 Explanation: Permanent adapter failure. 1. Check the BladeCenter management-module event log. If an error was recorded by the system, see POST progress codes (checkpoints). 2. Replace any parts reported by the diagnostic program. 3. Replace the system-board Response: Failing Item: v FFC_2E33...
  • Page 376 1. Check the BladeCenter management-module event log. If an error was recorded by the system, see POST progress codes (checkpoints). 2. Replace any parts reported by the diagnostic program. 3. Replace the system-board Response: Failing Item: v FFC_2E35 Power Systems: IBM Flex System p24L Compute Node Installation and Service Guide...
  • Page 377 2E35-701 • 2E36-602 2E35-701 Explanation: Permanent adapter failure. 1. Check the BladeCenter management-module event log. If an error was recorded by the system, see POST progress codes (checkpoints). 2. Replace any parts reported by the diagnostic program. 3. Replace the system-board Response: Failing Item: v FFC_2E35...
  • Page 378 3. Replace the system-board Response: Failing Item: v FFC_2E36 v FFC_221 2E37-111 Explanation: Enhanced Error Handling failure on bus. Replace the IBM Flex System EN4054 4-port 10Gb Ethernet Adapter. Response: Failing Item: v FFC_2E37 2E37-112 Explanation: Enhanced Error Handling failure while testing adapter. Replace the IBM Flex System EN4054 4-port 10Gb Ethernet Adapter.
  • Page 379 Explanation: Internal loopback test failed. Replace the IBM Flex System EN4054 4-port 10Gb Ethernet Adapter. Response: Failing Item: v FFC_2E37 2E37-152 Explanation: Internal loopback IP checksum offload test failed. Replace the IBM Flex System EN4054 4-port 10Gb Ethernet Adapter. Response: Failing Item: v FFC_2E37 2E37-153 Explanation: Internal loopback TCP checksum offload test failed.
  • Page 380 Explanation: Adapter hardware error. Replace the IBM Flex System EN4054 4-port 10Gb Ethernet Adapter. Response: Failing Item: v FFC_2E37 2E37-702 Explanation: EEH service error. Replace the IBM Flex System EN4054 4-port 10Gb Ethernet Adapter. If the problem persists, replace the system board. Response: Failing Item: v FFC_2E37...
  • Page 381 2E37-703 • 2E3D-104 2E37-703 Explanation: Failure to initialize due to a problem while reading the EEPROM on the adapter. Replace the IBM Flex System EN4054 4-port 10Gb Ethernet Adapter. Response: Failing Item: v FFC_2E37 2E3D-101 Explanation: PCI Configuration Registers Test Failure. Replace the IBM Flex System EN2024 4-port 1Gb Ethernet Adapter If the problem persists, replace the system board.
  • Page 382 Explanation: Internal Loopback Test Failure. Replace the IBM Flex System EN2024 4-port 1Gb Ethernet Adapter Response: Failing Item: v FFC_2E3D 2E3D-201 Explanation: Adapter configuration error. Replace the IBM Flex System EN2024 4-port 1Gb Ethernet Adapter If the problem persists, replace the system board. Response: Failing Item: v FFC_2E3D...
  • Page 383 2E52-201 • 2E53-201 2E52-201 Explanation: Adapter configuration error Replace the IBM Flex System CN4058 8-port 10Gb Converged Adapter If the problem persists, replace the system board. Response: Failing Item: v FFC_2E52 v FFC_221 2E52-605 Explanation: Ethernet hardware error Replace the IBM Flex System CN4058 8-port 10Gb Converged Adapter...
  • Page 384 2. Replace any parts reported by the diagnostic program. 3. Reseat the 3Gb SAS Adapter card. 4. Replace the 3Gb SAS Adapter card. 5. Replace the system-board Response: Failing Item: v FFC_2506 v FFC_221 Power Systems: IBM Flex System p24L Compute Node Installation and Service Guide...
  • Page 385 950-2D14 • 2506-3010 950-2D14 Explanation: A resource was not detected that was previously installed. Check the Management Module event log for an system event. If there is not a system error, replace the system board (SAS controller). Response: Failing Item: v FFC_2D14 950-2D29 Explanation: A resource was not detected that was previously installed.
  • Page 386 Explanation: Configuration error, incorrect multipath connection. Go to Performing the checkout procedure. Response: 2506-4040 Explanation: Configuration error, incomplete multipath connection between controller and enclosure detected. Go to Performing the checkout procedure. Response: Power Systems: IBM Flex System p24L Compute Node Installation and Service Guide...
  • Page 387 2506-4041 • 2506-4150 2506-4041 Explanation: Configuration error, incomplete multipath connection between enclosure and device detected. Go to Performing the checkout procedure. Response: 2506-4050 Explanation: Attached enclosure does not support required multipath function. Go to Performing the checkout procedure. Response: 2506-4060 Explanation: Multipath redundancy level got worse.
  • Page 388 Explanation: Controller failure. Go to Performing the checkout procedure. Response: Failing Item: v FFC_2506 2506-8157 Explanation: Temporary controller failure. Go to Performing the checkout procedure. Response: Failing Item: v FFC_2506 Power Systems: IBM Flex System p24L Compute Node Installation and Service Guide...
  • Page 389 2506-9000 • 2506-9020 2506-9000 Explanation: Controller detected device error during configuration discovery. Go to Performing the checkout procedure. Response: 2506-9001 Explanation: Controller detected device error during configuration discovery. Go to Performing the checkout procedure. Response: 2506-9002 Explanation: Controller detected device error during configuration discovery. Go to Performing the checkout procedure.
  • Page 390 Explanation: Previously degraded disk in Disk Array not found at required physical location. Go to Performing the checkout procedure. Response: 2506-9027 Explanation: Disk Array is or would become degraded and parity data is out of synchronization. Go to Performing the checkout procedure. Response: Power Systems: IBM Flex System p24L Compute Node Installation and Service Guide...
  • Page 391 2506-9028 • 2506-9050 2506-9028 Explanation: Maximum number of functional Disk Arrays has been exceeded. Go to Performing the checkout procedure. Response: 2506-9029 Explanation: Maximum number of functional Disk Arrays disks has been exceeded. Go to Performing the checkout procedure. Response: 2506-9030 Explanation: Disk Array is degraded due to missing/failed disk.
  • Page 392 Explanation: Maximum number of functional Disk Arrays has been exceeded. Go to Performing the checkout procedure. Response: 2506-9073 Explanation: Multiple controllers connected in an invalid configuration. Go to Performing the checkout procedure. Response: Power Systems: IBM Flex System p24L Compute Node Installation and Service Guide...
  • Page 393 2506-9074 • 2506-9092 2506-9074 Explanation: Multiple controllers not capable of similar functions or controlling same set of devices. Go to Performing the checkout procedure. Response: 2506-9075 Explanation: Incomplete multipath connection between controller and remote controller. Go to Performing the checkout procedure. Response: 2506-9076 Explanation: Missing remote controller.
  • Page 394 Failing Item: v FFC_722 2506-FFFA Explanation: Temporary device bus error. Retry the operation. Response: Failing Item: v FFC_722 2506-FFFE Explanation: Temporary device bus error. Retry the operation. Response: Power Systems: IBM Flex System p24L Compute Node Installation and Service Guide...
  • Page 395 2D14-102E • 2D14-3110 2D14-102E Explanation: Reallocation failed due to disk out of alternate sectors. Replace the FRU identified by diagnostics. Response: Failing Item: v FFC_722 2D14-3002 Explanation: Addressed device failed to respond to selection. Replace the FRU identified by diagnostics. Response: Failing Item: v FFC_722...
  • Page 396 Explanation: Attached enclosure does not support required multipath function. Use MAP3148 to determine resolution. Response: 2D14-4060 Explanation: Multipath redundancy level got worse. Use MAP3153 to determine resolution. Response: 2D14-4100 Explanation: Device bus fabric error. Use MAP3152 to determine resolution. Response: Power Systems: IBM Flex System p24L Compute Node Installation and Service Guide...
  • Page 397 2D14-4101 • 2D14-8150 2D14-4101 Explanation: Temporary device bus fabric error. Use MAP3152 to determine resolution. Response: 2D14-4110 Explanation: Unsupported enclosure function detected. Use MAP3145 to determine resolution. Response: 2D14-4150 Explanation: PCI bus error detected by controller. Replace the system board (SAS controller). Response: Failing Item: v FFC_2D14...
  • Page 398 Explanation: Cache data belongs to disks other than those attached. Use MAP3190 to determine resolution. Response: 2D14-9020 Explanation: Two or more disks are missing from a RAID-5 or RAID 6 Disk Array. Use MAP3111 to determine resolution. Response: Power Systems: IBM Flex System p24L Compute Node Installation and Service Guide...
  • Page 399 2D14-9021 • 2D14-9027 2D14-9021 Explanation: Two or more disks are missing from a RAID-5 or RAID 6 Disk Array. Use MAP3111 to determine resolution. Response: 2D14-9022 Explanation: Two or more disks are missing from a RAID-5 or RAID 6 Disk Array. Use MAP3111 to determine resolution.
  • Page 400 Explanation: Background Disk Array parity checking detected and corrected errors on specified disk. Use MAP3190 to determine resolution. Response: 2D14-9050 Explanation: Required cache data can not be located for one or more disks. Use MAP3131 to determine resolution. Response: Power Systems: IBM Flex System p24L Compute Node Installation and Service Guide...
  • Page 401 2D14-9051 • 2D14-9073 2D14-9051 Explanation: Cache data exists for one or more missing/failed disks. Use MAP3132 to determine resolution. Response: 2D14-9052 Explanation: Cache data exists for one or more modified disks. Use MAP3190 to determine resolution. Response: 2D14-9054 Explanation: RAID controller resources not available due to previous problems. Use MAP3121 to determine resolution.
  • Page 402 Explanation: Incorrect disk configuration change has been detected. Use MAP3133 to determine resolution. Response: 2D14-9092 Explanation: Disk requires Format before use. Format the disk and retry the operation. Use MAP3134 to determine resolution. Response: Power Systems: IBM Flex System p24L Compute Node Installation and Service Guide...
  • Page 403 2D14-FF3D • 2D14-FFFE 2D14-FF3D Explanation: Temporary controller failure. Retry the operation. Replace the system board (SAS controller). Response: Failing Item: v FFC_2D14 2D14-FFF3 Explanation: Disk media format bad. Reformat the disk and retry the operation. Use MAP3135 to determine resolution. Response: 2D14-FFF4 Explanation: Device problem.
  • Page 404 Explanation: Controller detected device bus interface error. Use MAP3150 to determine resolution. Response: 2D29-3109 Explanation: Controller timed out a device command. Use MAP3150 to determine resolution. Response: 2D29-3110 Explanation: Device bus interface error. Use MAP3150 to determine resolution. Response: Power Systems: IBM Flex System p24L Compute Node Installation and Service Guide...
  • Page 405 2D29-4010 • 2D29-4100 2D29-4010 Explanation: Configuration error, incorrect connection between cascaded enclosures. Use MAP3142 to determine resolution. Response: 2D29-4020 Explanation: Configuration error, connections exceed IOA design limits. Use MAP3143 to determine resolution. Response: 2D29-4030 Explanation: Configuration error, incorrect multipath connection. Use MAP3144 to determine resolution. Response: 2D29-4040 Explanation: Configuration error, incomplete multipath connection between controller and enclosure detected.
  • Page 406 Explanation: Temporary disk data error. Replace the PCIe x8 Internal 3Gb SAS Adapter. Response: Failing Item: v FFC_722 2D29-8150 Explanation: Controller failure. Replace the PCIe x8 Internal 3Gb SAS Adapter. Response: Failing Item: v FFC_2D29 Power Systems: IBM Flex System p24L Compute Node Installation and Service Guide...
  • Page 407 2D29-8157 • 2D29-9020 2D29-8157 Explanation: Temporary controller failure. Replace the PCIe x8 Internal 3Gb SAS Adapter. Response: Failing Item: v FFC_2D29 2D29-9000 Explanation: Controller detected device error during configuration discovery. Use MAP3190 to determine resolution. Response: 2D29-9001 Explanation: Controller detected device error during configuration discovery. Use MAP3190 to determine resolution. Response: 2D29-9002 Explanation: Controller detected device error during configuration discovery.
  • Page 408 Explanation: Previously degraded disk in Disk Array not found at required physical location. Use MAP3190 to determine resolution. Response: 2D29-9027 Explanation: Disk Array is or would become degraded and parity data is out of synchronization. Use MAP3113 to determine resolution. Response: Power Systems: IBM Flex System p24L Compute Node Installation and Service Guide...
  • Page 409 2D29-9028 • 2D29-9050 2D29-9028 Explanation: Maximum number of functional Disk Arrays has been exceeded. Use MAP3190 to determine resolution. Response: 2D29-9029 Explanation: Maximum number of functional Disk Arrays disks has been exceeded. Use MAP3190 to determine resolution. Response: 2D29-9030 Explanation: Disk Array is degraded due to missing/failed disk. Use MAP3110 to determine resolution. Response: 2D29-9031 Explanation: Automatic reconstruction initiated for Disk Array.
  • Page 410 Explanation: Maximum number of functional Disk Arrays has been exceeded. Use MAP3190 to determine resolution. Response: 2D29-9073 Explanation: Multiple controllers connected in an invalid configuration. Use MAP3140 to determine resolution. Response: Power Systems: IBM Flex System p24L Compute Node Installation and Service Guide...
  • Page 411 2D29-9074 • 2D29-9092 2D29-9074 Explanation: Multiple controllers not capable of similar functions or controlling same set of devices. Use MAP3141 to determine resolution. Response: 2D29-9075 Explanation: Incomplete multipath connection between controller and remote controller. Use MAP3149 to determine resolution. Response: 2D29-9076 Explanation: Missing remote controller.
  • Page 412 Explanation: Temporary device bus error. Replace the FRU identified by diagnostics. Response: Failing Item: v FFC_722 2D29-FFFE Explanation: Temporary device bus error. Use MAP3150 to determine resolution. Response: Power Systems: IBM Flex System p24L Compute Node Installation and Service Guide...
  • Page 413 A24-000 • A24-XXX A00-FF0 through A24-xxx SRNs: The AIX operating system might generate service request numbers (SRNs) from A00-FF0 to A24-xxx. Note: Some SRNs in this sequence might have 4 rather than 3 digits after the dash (–). Table 10 shows the meaning of an x in any of the following SRNs, such as A01-00x. Table 10.
  • Page 414 2. Replace any parts reported by the diagnostic program. 3. Replace the system board and chassis assembly, as described in Replacing the system-board and chassis assembly. Response: Failing Item: v FFC_SSSS Power Systems: IBM Flex System p24L Compute Node Installation and Service Guide...
  • Page 415 SSSS-108 • SSSS-114 SSSS-108 Explanation: 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). 2. Replace any parts reported by the diagnostic program. 3. Replace the system board and chassis assembly, as described in Replacing the system-board and chassis assembly. Response: Failing Item: v FFC_SSSS...
  • Page 416 2. Replace any parts reported by the diagnostic program. 3. Replace the system board and chassis assembly, as described in Replacing the system-board and chassis assembly. Response: Failing Item: v FFC_SSSS Power Systems: IBM Flex System p24L Compute Node Installation and Service Guide...
  • Page 417 SSSS-122 • SSSS-128 SSSS-122 Explanation: A SCSD reservation conflict error. 1. Check the BladeCenter management-module event log. If an error was recorded by the system, see POST progress codes (checkpoints). 2. Replace any parts reported by the diagnostic program. 3. Replace the system board and chassis assembly, as described in Replacing the system-board and chassis assembly. Response: Failing Item: v FFC_SSSS...
  • Page 418 2. Replace any parts reported by the diagnostic program. 3. Replace the system board and chassis assembly, as described in Replacing the system-board and chassis assembly. Response: Failing Item: v FFC_252B v SOFTWARE Power Systems: IBM Flex System p24L Compute Node Installation and Service Guide...
  • Page 419 SSSS-135 • SSSS-137 SSSS-135 Explanation: The device failed to configure. 1. Check the BladeCenter management-module event log. If an error was recorded by the system, see POST progress codes (checkpoints). 2. Replace any parts reported by the diagnostic program. 3. Replace the system board and chassis assembly, as described in Replacing the system-board and chassis assembly. Response: Failing Item: v FFC_SSSS...
  • Page 420 2. Replace any parts reported by the diagnostic program. 3. Replace the system board and chassis assembly, as described in Replacing the system-board and chassis assembly. Response: Failing Item: v FFC_SSSS Power Systems: IBM Flex System p24L Compute Node Installation and Service Guide...
  • Page 421 2. System-board and chassis assembly System-board and chassis assembly Check the event log for an IBM Flex System Enterprise Chassis blower or fan fault. See the documentation that comes with the IBM Flex System Enterprise Chassis. System-board and chassis assembly...
  • Page 422 IBM Flex System 8-port 10 Gb converged adapter 2E37 IBM Flex System 4-port 10 Gb Ethernet adapter 2E3D IBM Flex System 4-port 1 Gb Ethernet adapter 2E52 IBM Flex System 8-port 10 Gb converged adapter Power Systems: IBM Flex System p24L Compute Node Installation and Service Guide...
  • Page 423 Controller maintenance analysis procedures: These procedures are intended to resolve adapter, cache, or disk array problems associated with a controller. See “Service request numbers (SRNs)” on page 264 to identify which MAP to use. MAP 3110: Perform MAP 3110 in the Systems Hardware information center. MAP 3111: Perform MAP 3111 in the Systems Hardware information center.
  • Page 424 Perform MAP 3143 in the Systems Hardware information center. MAP 3144: Perform MAP 3144 in the Systems Hardware information center. MAP 3145: Perform MAP 3145 in the Systems Hardware information center. MAP 3146: Power Systems: IBM Flex System p24L Compute Node Installation and Service Guide...
  • Page 425 The following table shows the syntax of a nine-word B700xxxx system reference code (SRC) as it might be displayed in the event log of the IBM Chassis Management Module (CMM). Additional information for the event can be viewed by clicking more... in the message field.
  • Page 426 For intermittent problems, check the management-module event log and “POST progress codes (checkpoints)” on page 196. v If the compute node front panel shows no LEDs, verify the compute node status and errors in the IBM Flex System Enterprise Chassis Web interface. Also, see “Solving undetermined problems” on page 457.
  • Page 427 Select the resources to be tested and record any SRNs. Then go to “Service request numbers (SRNs)” on page 264. This ends the Linux procedure. For more information about installing and using all supported operating systems, search the IBM Support website. Verifying the partition configuration Perform this procedure if there is a configuration problem with the system or a logical partition.
  • Page 428 See the documentation that comes with your operating system for information about shutting down the operating system. Power Systems: IBM Flex System p24L Compute Node Installation and Service Guide...
  • Page 429 2. If the system is running in a full-machine partition, turn on the compute node and establish a Serial over LAN (SOL) session. For information about starting an SOL session, see the IBM Chassis Management Module Command-Line Interface Reference Guide.
  • Page 430 Procedure 1. Make sure that your boot list is correct. a. Use the management console to display the boot sequences for the compute nodes in your IBM Flex System Enterprise Chassis. b. Find your compute node on the list that is displayed and make sure that the device from which you are attempting to boot is the first device in the boot sequence.
  • Page 431 Follow the suggested actions in the order in which they are listed in the Action column until the problem is solved. v See Chapter 7, “Parts listing for IBM Flex System p24L Compute Node,” on page 79 to determine which components are CRUs and which components are FRUs.
  • Page 432 Follow the suggested actions in the order in which they are listed in the Action column until the problem is solved. v See Chapter 7, “Parts listing for IBM Flex System p24L Compute Node,” on page 79 to determine which components are CRUs and which components are FRUs.
  • Page 433 Follow the suggested actions in the order in which they are listed in the Action column until the problem is solved. v See Chapter 7, “Parts listing for IBM Flex System p24L Compute Node,” on page 79 to determine which components are CRUs and which components are FRUs.
  • Page 434 Follow the suggested actions in the order in which they are listed in the Action column until the problem is solved. v See Chapter 7, “Parts listing for IBM Flex System p24L Compute Node,” on page 79 to determine which components are CRUs and which components are FRUs.
  • Page 435 Follow the suggested actions in the order in which they are listed in the Action column until the problem is solved. v See Chapter 7, “Parts listing for IBM Flex System p24L Compute Node,” on page 79 to determine which components are CRUs and which components are FRUs.
  • Page 436 Follow the suggested actions in the order in which they are listed in the Action column until the problem is solved. v See Chapter 7, “Parts listing for IBM Flex System p24L Compute Node,” on page 79 to determine which components are CRUs and which components are FRUs.
  • Page 437 Follow the suggested actions in the order in which they are listed in the Action column until the problem is solved. v See Chapter 7, “Parts listing for IBM Flex System p24L Compute Node,” on page 79 to determine which components are CRUs and which components are FRUs.
  • Page 438 Follow the suggested actions in the order in which they are listed in the Action column until the problem is solved. v See Chapter 7, “Parts listing for IBM Flex System p24L Compute Node,” on page 79 to determine which components are CRUs and which components are FRUs.
  • Page 439 Follow the suggested actions in the order in which they are listed in the Action column until the problem is solved. v See Chapter 7, “Parts listing for IBM Flex System p24L Compute Node,” on page 79 to determine which components are CRUs and which components are FRUs.
  • Page 440 Follow the suggested actions in the order in which they are listed in the Action column until the problem is solved. v See Chapter 7, “Parts listing for IBM Flex System p24L Compute Node,” on page 79 to determine which components are CRUs and which components are FRUs.
  • Page 441 Follow the suggested actions in the order in which they are listed in the Action column until the problem is solved. v See Chapter 7, “Parts listing for IBM Flex System p24L Compute Node,” on page 79 to determine which components are CRUs and which components are FRUs.
  • Page 442 Follow the suggested actions in the order in which they are listed in the Action column until the problem is solved. v See Chapter 7, “Parts listing for IBM Flex System p24L Compute Node,” on page 79 to determine which components are CRUs and which components are FRUs.
  • Page 443 Follow the suggested actions in the order in which they are listed in the Action column until the problem is solved. v See Chapter 7, “Parts listing for IBM Flex System p24L Compute Node,” on page 79 to determine which components are CRUs and which components are FRUs.
  • Page 444 Follow the suggested actions in the order in which they are listed in the Action column until the problem is solved. v See Chapter 7, “Parts listing for IBM Flex System p24L Compute Node,” on page 79 to determine which components are CRUs and which components are FRUs.
  • Page 445 Follow the suggested actions in the order in which they are listed in the Action column until the problem is solved. v See Chapter 7, “Parts listing for IBM Flex System p24L Compute Node,” on page 79 to determine which components are CRUs and which components are FRUs.
  • Page 446 Follow the suggested actions in the order in which they are listed in the Action column until the problem is solved. v See Chapter 7, “Parts listing for IBM Flex System p24L Compute Node,” on page 79 to determine which components are CRUs and which components are FRUs.
  • Page 447 Follow the suggested actions in the order in which they are listed in the Action column until the problem is solved. v See Chapter 7, “Parts listing for IBM Flex System p24L Compute Node,” on page 79 to determine which components are CRUs and which components are FRUs.
  • Page 448 Follow the suggested actions in the order in which they are listed in the Action column until the problem is solved. v See Chapter 7, “Parts listing for IBM Flex System p24L Compute Node,” on page 79 to determine which components are CRUs and which components are FRUs.
  • Page 449 Follow the suggested actions in the order in which they are listed in the Action column until the problem is solved. v See Chapter 7, “Parts listing for IBM Flex System p24L Compute Node,” on page 79 to determine which components are CRUs and which components are FRUs.
  • Page 450 Follow the suggested actions in the order in which they are listed in the Action column until the problem is solved. v See Chapter 7, “Parts listing for IBM Flex System p24L Compute Node,” on page 79 to determine which components are CRUs and which components are FRUs.
  • Page 451 Follow the suggested actions in the order in which they are listed in the Action column until the problem is solved. v See Chapter 7, “Parts listing for IBM Flex System p24L Compute Node,” on page 79 to determine which components are CRUs and which components are FRUs.
  • Page 452 Follow the suggested actions in the order in which they are listed in the Action column until the problem is solved. v See Chapter 7, “Parts listing for IBM Flex System p24L Compute Node,” on page 79 to determine which components are CRUs and which components are FRUs.
  • Page 453 Follow the suggested actions in the order in which they are listed in the Action column until the problem is solved. v See Chapter 7, “Parts listing for IBM Flex System p24L Compute Node,” on page 79 to determine which components are CRUs and which components are FRUs.
  • Page 454 Follow the suggested actions in the order in which they are listed in the Action column until the problem is solved. v See Chapter 7, “Parts listing for IBM Flex System p24L Compute Node,” on page 79 to determine which components are CRUs and which components are FRUs.
  • Page 455 Follow the suggested actions in the order in which they are listed in the Action column until the problem is solved. v See Chapter 7, “Parts listing for IBM Flex System p24L Compute Node,” on page 79 to determine which components are CRUs and which components are FRUs.
  • Page 456 Follow the suggested actions in the order in which they are listed in the Action column until the problem is solved. v See Chapter 7, “Parts listing for IBM Flex System p24L Compute Node,” on page 79 to determine which components are CRUs and which components are FRUs.
  • Page 457 Follow the suggested actions in the order in which they are listed in the Action column until the problem is solved. v See Chapter 7, “Parts listing for IBM Flex System p24L Compute Node,” on page 79 to determine which components are CRUs and which components are FRUs.
  • Page 458 Follow the suggested actions in the order in which they are listed in the Action column until the problem is solved. v See Chapter 7, “Parts listing for IBM Flex System p24L Compute Node,” on page 79 to determine which components are CRUs and which components are FRUs.
  • Page 459 About this task View the system LEDs remotely through the Chassis Manager in the web interface of the IBM Flex System Manager management software. To view the system LEDs remotely by using the Hardware Management Console (HMC), see LED Status.
  • Page 460 Figure 34. LED locations on the system board of the IBM Flex System p24L Compute Node The following table identifies the light path diagnostic LEDs. Table 16. IBM Flex System p24L Compute Node LEDs Callout Unit LEDs 3 V lithium battery LED...
  • Page 461 Follow the suggested actions in the order in which they are listed in the Action column until the problem is solved. v See Chapter 7, “Parts listing for IBM Flex System p24L Compute Node,” on page 79 to determine which components are CRUs and which components are FRUs.
  • Page 462 Follow the suggested actions in the order in which they are listed in the Action column until the problem is solved. v See Chapter 7, “Parts listing for IBM Flex System p24L Compute Node,” on page 79 to determine which components are CRUs and which components are FRUs.
  • Page 463 5. If the problem is not resolved, contact your next level of support. Save vfchost map data Before you replace physical components on your compute node, it might be necessary to first save the original virtual Fibre Channel vfchost data of your compute node. Procedure To save the original vfchost data and the original physical Fibre Channel adapter port (fcs) location codes, complete the following steps by using the padmin user account:...
  • Page 464 FC name fcs0 FC loc code:U78AF.001.newSN99-P1-C35-L1-T1 Ports logged in 0 Flags 4<NOT_LOGGED> VFC client name VFC client DRC In this example, the new serial number is represented as newSN99. Power Systems: IBM Flex System p24L Compute Node Installation and Service Guide...
  • Page 465 Starting the PERM image You can force the compute node to start the permanent (PERM) image. About this task To force the compute node to start the PERM image, see http://publib.boulder.ibm.com/infocenter/ flexsys/information/topic/com.ibm.acc.psm.hosts.doc/dpsm_managing_hosts_power_firmware.html. Starting the TEMP image The system firmware is contained in separate temporary and permanent images in the flash memory of the compute node.
  • Page 466 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 window is displayed. Then, press F3 again to exit the diagnostic program. Power Systems: IBM Flex System p24L Compute Node Installation and Service Guide...
  • Page 467 To check the general function of shared resources, complete the following steps: Procedure 1. Verify that the required power modules are installed in the IBM Flex System Enterprise Chassis and that the chassis is connected to a working power source.
  • Page 468 3. Verify that the installation of the I/O-module type is supported by the IBM Flex System Enterprise Chassis and compute node hardware. 4. Verify that the I/O modules for the network interface are installed in the correct bays of the IBM Flex System Enterprise Chassis.
  • Page 469 IBM Flex System Enterprise Chassis. About this task v If all of the compute nodes have the same symptom, it is probably a problem in the IBM Flex System Enterprise Chassis.
  • Page 470 If you suspect a networking problem and the compute node passes all the system tests, suspect a network cabling problem that is external to the system. Power Systems: IBM Flex System p24L Compute Node Installation and Service Guide...
  • Page 471 All statements regarding the manufacturer's future direction or intent are subject to change or withdrawal without notice, and represent goals and objectives only. The manufacturer's prices shown are the manufacturer's suggested retail prices, are current and are subject to change without notice. Dealer prices may vary. © Copyright IBM Corp. 2012, 2015...
  • Page 472 IBM, the IBM logo, and ibm.com are trademarks or registered trademarks of International Business Machines Corp., registered in many jurisdictions worldwide. Other product and service names might be trademarks of IBM or other companies. A current list of IBM trademarks is available on the Web at Copyright and trademark information at www.ibm.com/legal/copytrade.shtml.
  • Page 473 Class A Notices The following Class A statements apply to the IBM servers that contain the POWER7 processor and its features unless designated as electromagnetic compatibility (EMC) Class B in the feature information.
  • Page 474 Declaration: This is a Class A product. In a domestic environment this product may cause radio interference in which case the user may need to perform practical action. Power Systems: IBM Flex System p24L Compute Node Installation and Service Guide...
  • Page 475 Warning: This is a Class A product. In a domestic environment this product may cause radio interference in which case the user will be required to take adequate measures. IBM Taiwan Contact Information: Electromagnetic Interference (EMI) Statement - Korea Appendix. Notices...
  • Page 476 Um dieses sicherzustellen, sind die Geräte wie in den Handbüchern beschrieben zu installieren und zu betreiben. Des Weiteren dürfen auch nur von der IBM empfohlene Kabel angeschlossen werden. IBM übernimmt keine Verantwortung für die Einhaltung der Schutzanforderungen, wenn das Produkt ohne Zustimmung von IBM verändert bzw.
  • Page 477 Properly shielded and grounded cables and connectors must be used in order to meet FCC emission limits. Proper cables and connectors are available from IBM-authorized dealers. IBM is not responsible for any radio or television interference caused by unauthorized changes or modifications to this equipment.
  • Page 478 This product is in conformity with the protection requirements of EU Council Directive 2004/108/EC on the approximation of the laws of the Member States relating to electromagnetic compatibility. IBM cannot accept responsibility for any failure to satisfy the protection requirements resulting from a non-recommended modification of the product, including the fitting of non-IBM option cards.
  • Page 479 Um dieses sicherzustellen, sind die Geräte wie in den Handbüchern beschrieben zu installieren und zu betreiben. Des Weiteren dürfen auch nur von der IBM empfohlene Kabel angeschlossen werden. IBM übernimmt keine Verantwortung für die Einhaltung der Schutzanforderungen, wenn das Produkt ohne Zustimmung von IBM verändert bzw.
  • Page 480 Permissions for the use of these publications are granted subject to the following terms and conditions. Applicability: These terms and conditions are in addition to any terms of use for the IBM website. Personal Use: You may reproduce these publications for your personal, noncommercial use provided that all proprietary notices are preserved.
  • Page 481 Appendix. Notices...
  • Page 482 IBM® Printed in USA...