Page 1
Power Systems IBM Flex System p260 and p460 Compute Nodes Installation and Service Guide...
Page 3
Power Systems IBM Flex System p260 and p460 Compute Nodes 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 501, 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.
Contents Safety notices .... Removing the compute node from an IBM Flex System Enterprise Chassis Reseating the compute node in a chassis. Chapter 1. Introduction ..
Page 6
Performing the check-out procedure . Class A Notices. Verifying the partition configuration. Class B Notices . Running the diagnostics program Terms and conditions. Starting AIX concurrent diagnostics . Power Systems: IBM Flex System p260 and p460 Compute Nodes Installation and Service Guide...
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 p260 and p460 Compute Nodes 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)
Chapter 1. Introduction ® The IBM Flex System p260 Compute Node or IBM Flex System p460 Compute Node is based on IBM ® POWER technologies. These compute nodes run in IBM Flex System Enterprise Chassis units to provide a high-density, high-performance compute-node environment with advanced processing technology.
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.
| grep BR command Related documentation Documentation for the IBM Flex System p260 Compute Node or IBM Flex System p460 Compute Node includes PDF files on the IBM Flex System Enterprise Chassis Documentation CD and in the information center.
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.
Features and specifications Features and specifications of the IBM Flex System p260 Compute Node and IBM Flex System p460 Compute Node are summarized in these topics. Features and specifications of the IBM Flex System p260 Compute...
Page 18
The IBM Flex System p260 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 (ASM) are provided by the IBM Flex System Enterprise Chassis.
Features and specifications of the IBM Flex System p460 Compute Node are summarized in this overview. The IBM Flex System p460 Compute Node is the two-bay symmetric multiprocessing (SMP) unit and is used in an IBM Flex System Enterprise Chassis.
Page 20
GB SSDs with SAS-to-SATA multiple VIOS, and PowerVM board for communication with conversion Enterprise removable-media drives v Hardware mirroring supported v Optical media available by shared chassis feature Power Systems: IBM Flex System p260 and p460 Compute Nodes Installation and Service Guide...
The compute node uses the following features and technologies: v Service processor The service processor for the IBM Flex System p260 Compute Node or IBM Flex System p460 Compute Node provides support for the following functions: – Intelligent Platform Management Interface (IPMI) –...
Page 22
Large system memory capacity The memory bus in the IBM Flex System p260 Compute Node supports up to 512 GB of system memory, and the IBM Flex System p460 Compute Node supports up to 1024 GB of system memory.
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.
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.
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 p260 Compute Node. Figure 2. System-board connectors for the IBM Flex System p260 Compute Node The following table identifies and describes the connectors for the IBM Flex System p260 Compute Node.
Page 27
Figure 3. Base-unit connectors for the IBM Flex System p460 Compute Node The following table identifies and describes the connectors for the IBM Flex System p460 Compute Node. Table 3. Connectors for the IBM Flex System p460 Compute Node Callout...
Page 28
Figure 4. DIMM connectors for the IBM Flex System p260 Compute Node The following figure shows individual DIMM connectors for the IBM Flex System p460 Compute Node system board. Figure 5. DIMM connectors for the IBM Flex System p460 Compute Node...
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 p260 Compute Node. The following figures and table shows the system-board LEDs.
Page 30
Figure 7. LED locations on the system board of the IBM Flex System p460 Compute Node The following table identifies the light path diagnostic LEDs. Table 4. IBM Flex System p260 Compute Node and IBM Flex System p460 Compute Node LEDs Callout...
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 32
Power Systems: IBM Flex System p260 and p460 Compute Nodes Installation and Service Guide...
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. Before you begin Attention: Installing the wrong firmware update might cause the compute node to malfunction. Before you install a firmware update, read any readme and change history files that are provided with the downloaded update.
Page 35
About this task To install compute node firmware using an in-band method, complete the following steps: Procedure 1. Download the IBM Flex System p260 Compute Node one-bay firmware or the IBM Flex System p460 Compute Node two-bay firmware. a. Go to http://www.ibm.com/software/brandcatalog/puresystems/centre/update.
F3 again to exit the diagnostic program. Using the SMS utility Use the System Management Services (SMS) utility to configure the IBM Flex System p260 Compute Node or IBM Flex System p460 Compute Node.
1. Turn on or restart the compute node, and establish an SOL session with it. See the IBM Chassis Management Module Command-Line Interface Reference Guide for more information. 2. When the POST menu and indicators are displayed, and after the word Keyboard is displayed and before the word Speaker is displayed, press 1.
Learn how to increase or decrease the number of active processor cores in the compute node. You can order your IBM Flex System p260 Compute Node or IBM Flex System p460 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.
MAC addresses for integrated Ethernet controllers Two integrated Ethernet ports are used by the service processor on the IBM Flex System p260 Compute Node or IBM Flex System p460 Compute Node. Additional Ethernet ports are provided by the feature cards plugged into the two expansion cards slots. These expansion card Ethernet ports, when used with a Virtual I/O Server (VIOS), provide virtual logical Ethernet to client logical partitions (LPARs).
Disk drives and solid-state drives in the IBM Flex System p260 Compute Node or IBM Flex System p460 Compute Node can be used to implement and manage various types of RAID arrays in operating systems that are on the ServerProven list.
Locating the installation instructions You can order the IBM Flex System p260 Compute Node or IBM Flex System p460 Compute Node with Virtual I/O Server (VIOS), AIX operating-system, or IBM i operating-system 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 42
Installing IBM i You can install the IBM i operating system in a client partition of the VIOS. See the IBM i on a POWER Blade Read-me First document on the IBM website. Additional installation ™ information and IBM i restrictions are described in i5/OS client partition considerations.
The installation aids are provided in the IBM Installation Toolkit for the Linux operating system, a set of tools that aids the installation of the Linux operating system on IBM compute nodes that are based on IBM POWER7 Architecture technologies. You can also use the tools to update the IBM Flex System p260 Compute Node or IBM Flex System p460 Compute Node firmware.
Page 44
Power Systems: IBM Flex System p260 and p460 Compute Nodes Installation and Service Guide...
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 46
Power Systems: IBM Flex System p260 and p460 Compute Nodes Installation and Service Guide...
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.
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.
Figure 8. 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.
4. Wait at least 30 seconds for the hard disk drive to stop spinning. 5. Open the release handles, as shown in Figure 8 on page 37. The IBM Flex System p260 Compute Node has one release handle. The IBM Flex System p460 Compute Nodehas two release handles. The compute node can be moved out of the bay approximately 0.6 cm (0.25 inch).
Replacement of tier 1 customer-replaceable units (CRUs) is your responsibility. 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.
Page 52
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 37.
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 54
Before you close the cover, verify that all components are installed and seated correctly and that you have not left loose tools or parts inside the compute node. Power Systems: IBM Flex System p260 and p460 Compute Nodes Installation and Service Guide...
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 p260 Compute Node or IBM Flex System p460 Compute Node. If the bezel becomes damaged, you can remove the bezel by using the following procedure.
Page 56
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 37.
Installing the bezel assembly You can replace a damaged bezel on an IBM Flex System p260 Compute Node or IBM Flex System p460 Compute Node. About this task If the bezel becomes damaged, you can install a new bezel by using the following procedure.
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 93.
Page 59
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 37.
Figure 18. Installing a hard disk drive All drive connectors are from the same controller. Both the IBM Flex System p260 Compute Node and IBM Flex System p460 Compute Node can be used to implement RAID functions. See “Configuring a RAID array”...
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 93.
Page 62
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 37.
7. Remove any SSDs from the carrier case. See “Removing a SATA solid-state drive” on page 53. 8. If you are instructed to return the SSD carrier, follow all packaging instructions, and use any packaging materials for shipping that are supplied to you. Note: Even if you do not plan to install another SSD in the drive slot, replace the SSD carrier in the slot to act as a thermal baffle and to avoid machine damage.
Page 64
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 93.
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 37.
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 37.
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 68
Figure 24. DIMM connectors for the IBM Flex System p460 Compute Node Attention: To avoid breaking the DIMM retaining clips or damaging the DIMM connectors, open and close the clips gently. Power Systems: IBM Flex System p260 and p460 Compute Nodes Installation and Service Guide...
Page 69
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 93.
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.
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 p260 Compute Node is 512 GB and for an IBM Flex System p460 Compute Node is 1024 GB.
Page 72
X (X) X (X) X (X) X (X) X (X) X (X) X (X) X (X) X (X) X (X) X (X) X (X) X (X) Power Systems: IBM Flex System p260 and p460 Compute Nodes Installation and Service Guide...
Figure 28. DIMM connectors for the IBM Flex System p460 Compute Node Related reference: Chapter 7, “Parts listing for IBM Flex System p260 and p460 Compute Nodes,” on page 97 The parts listing identifies each replaceable part and its part number.
Page 74
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 37.
3. Open and remove the compute node cover. See “Removing the compute node cover” on page 39. 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.
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 93.
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 37.
Page 78
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.
Replacing the thermal sensor on an IBM Flex System p460 Compute Node 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 remove the thermal sensor on an IBM Flex System p460 Compute Node and replace it with a new thermal sensor.
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 81
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 37.
Page 82
6. Carefully open the retaining clips (A) on each end of the DIMM connector by pressing them in the direction of the arrows. Remove the DIMM (B). Figure 36. Removing a DIMM Power Systems: IBM Flex System p260 and p460 Compute Nodes Installation and Service Guide...
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 84
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. Power Systems: IBM Flex System p260 and p460 Compute Nodes Installation and Service Guide...
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 86
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 37.
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 88
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. 7. 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 93.
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 78. 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 90
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 p260 and p460 Compute Nodes Installation and Service Guide...
Page 91
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 92
This is to ensure that the activation code is stored in the vital product data on the management card. Power Systems: IBM Flex System p260 and p460 Compute Nodes Installation and Service Guide...
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.
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.
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 93.
Page 96
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 97
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 98
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 99
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 88 or 27 on page 88 of this procedure, depending upon whether the compute node is managed by a management console.
Page 100
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 p260 and p460 Compute Nodes Installation and Service Guide...
Page 101
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).
3. Turn on the compute node, as described in “Turning on the compute node” on page 12. 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.
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 42.
Page 104
Before you close the cover, verify that all components are installed and seated correctly and that you have not left loose tools or parts inside the compute node. Power Systems: IBM Flex System p260 and p460 Compute Nodes Installation and Service Guide...
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 106
5. Verify that the release handles on the compute node are in the open position (perpendicular to the compute node, as shown in Figure 44 on page 93). For the IBM Flex System p260 Compute Node, there is one release handle. For the IBM Flex System p460 Compute Node, there are two release handles.
Page 107
What to do next If you have changed the configuration of the compute node or if this is a different compute node than the one you removed, you must configure the compute node. You might also have to install the compute node operating system.
Page 108
Power Systems: IBM Flex System p260 and p460 Compute Nodes Installation and Service Guide...
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 110
“Failing v 3.6 GHz, 16-core system board (CCIN A898) v 00E1832 function v 4.1 GHz, 16-core system board (CCIN A897) v 00E1825 codes” on page 446 Power Systems: IBM Flex System p260 and p460 Compute Nodes Installation and Service Guide...
Page 111
33F8354 Memory, 2 GB DDR3, 1066 MHz low profile (LP) DIMM 78P1011 Note: 7895-22X only. Memory, 4 GB DDR3, 1066 MHz very low profile (VLP) 78P0501 DIMM Chapter 7. Parts listing for IBM Flex System p260 and p460 Compute Nodes...
Page 112
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 Power Systems: IBM Flex System p260 and p460 Compute Nodes Installation and Service Guide...
Page 113
IBM Flex System 2-port 8 Gb Fibre Channel adapter 69Y1941 2E16 IBM Flex System 4-port 10 Gb Ethernet adapter 81Y3125 2E37 IBM Flex System 4-port 1 Gb Ethernet adapter 49Y7902 2E3D Chapter 7. Parts listing for IBM Flex System p260 and p460 Compute Nodes...
Page 114
Memory, 32 GB DDR3, 1066 MHz low profile (LP) 78P1539 DIMM DIMM filler 60H2962 Cover (supports two disk drives) 00J0291 Cover (supports two solid-state drives) 00J0293 26BD Cover (no drives supported) 00E6260 Power Systems: IBM Flex System p260 and p460 Compute Nodes Installation and Service Guide...
Page 115
FRU and CRU label 00E6285 Light path label 00J0141 Miscellaneous parts kit (left cam handle, right cam 46M2828 handle, and latch bracket) Miscellaneous parts kit (network adapter retention) 94Y4866 Chapter 7. Parts listing for IBM Flex System p260 and p460 Compute Nodes...
Page 116
Power Systems: IBM Flex System p260 and p460 Compute Nodes Installation and Service Guide...
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 118
Diagnostic utilities for the AIX operating system An AIX operating-system diagnostic CD, also known as the stand-alone Diagnostics CD, is available from IBM. You can start the CD from a CD drive or from NIM. To download the CD image, go to http://www14.software.ibm.com/webapp/set2/sas/f/diags/home.html.
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 120
In some circumstances, an error might require a dump to show more data. The Integrated Virtualization Manager (IVM) or Hardware Management Console (HMC) sets up a dump area. Specific IVM or HMC information is included as part of the information that can optionally be sent to IBM support for analysis.
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 122
See “System-board connectors” on page 14 for component locations. Notes: 1. Location codes do not indicate the location of the compute node within the IBM Flex System Enterprise Chassis. The codes identify components of the compute node only. 2. For checkpoints with no associated location code, see “Light path diagnostics” on page 485 to identify the failing component when there is a hang condition.
Page 123
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 11. Mapping network adapter ports to IBM Flex System Enterprise Chassis I/O bays for the IBM Flex System p260 Compute Node IBM Flex IBM Flex...
Page 124
Table 11. Mapping network adapter ports to IBM Flex System Enterprise Chassis I/O bays for the IBM Flex System p260 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 125
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 13. Mapping network adapter ports to IBM Flex System Enterprise Chassis I/O bays for the IBM Flex System p460 Compute Node IBM Flex IBM Flex...
Page 126
Table 13. Mapping network adapter ports to IBM Flex System Enterprise Chassis I/O bays for the IBM Flex System p460 Compute Node (continued) IBM Flex IBM Flex IBM Flex System 2-port IBM Flex System 4-port IBM Flex System 2-port IBM Flex...
Table 13. Mapping network adapter ports to IBM Flex System Enterprise Chassis I/O bays for the IBM Flex System p460 Compute Node (continued) IBM Flex IBM Flex IBM Flex System 2-port IBM Flex System 4-port IBM Flex System 2-port IBM Flex...
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.
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 p260 Compute Node or IBM Flex System p460 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 130
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 p260 and p460 Compute Nodes Installation and Service Guide...
Page 131
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 132
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 p260 and p460 Compute Nodes Installation and Service Guide...
Page 133
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 134
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 p260 and p460 Compute Nodes Installation and Service Guide...
Page 135
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 136
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 p260 and p460 Compute Nodes Installation and Service Guide...
Page 137
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 138
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 139
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.
If an action solves the problem, then you can stop performing the remaining actions. See Chapter 7, “Parts listing for IBM Flex System p260 and p460 Compute Nodes,” on page 97 to determine which components are CRUs and which components are FRUs.
Page 141
632BCFC1 • 632BCFC5 632BCFC1 Explanation: A virtual optical device cannot access the file containing the list of volumes. Service action / serviceable event: Yes Called home automatically: No Problem determination: On this partition and on the Network File System server, verify that the proper file is specified and that the proper authority is granted.
Page 142
Explanation: Virtual optical device error. Self configuring SCSI device (SCSD) selection or reselection timeout occurred. Service action / serviceable event: No Called home automatically: No Problem determination: Refer to the hosting partition for problem analysis. Power Systems: IBM Flex System p260 and p460 Compute Nodes Installation and Service Guide...
Page 143
632CC010 • 632CC300 632CC010 Explanation: Virtual optical device error. Undefined sense key returned by device. Service action / serviceable event: No Called home automatically: No Problem determination: Refer to the hosting partition for problem analysis. 632CC020 Explanation: Virtual optical device error. Configuration error. Service action / serviceable event: No Called home automatically: No Problem determination: Refer to the hosting partition for problem analysis.
Page 144
Explanation: Virtual optical device error. Physical link error detected by device. Service action / serviceable event: No Called home automatically: No Problem determination: Refer to the hosting partition for problem analysis. Power Systems: IBM Flex System p260 and p460 Compute Nodes Installation and Service Guide...
Page 145
632CC402 • 632CCFFE 632CC402 Explanation: Virtual optical device driver error. An internal program error occurred. Service action / serviceable event: Yes Called home automatically: Yes Problem determination: Install any available operating system updates. 632CCFF2 Explanation: Informational system log entry only. Service action / serviceable event: No Called home automatically: No Response: No corrective action is required.
If an action solves the problem, you can stop performing the remaining actions. See Chapter 7, “Parts listing for IBM Flex System p260 and p460 Compute Nodes,” on page 97 to determine which components are CRUs and which components are FRUs.
Explanation: User-initiated RSCDUMP of RPA partition's PFW content. Response: No corrective action is required. A2D03002 Explanation: User-initiated RSCDUMP of IBM i partition's SLIC bootloader and PFW content. Response: No corrective action is required. A2XXYYYY Explanation: See the description for the B200yyyy error code with the same yyyy value.
Page 148
Otherwise this problem will not be called home. Problem determination: Do not power off the LPAR. Look for and repair problems in the I/O host. Power Systems: IBM Flex System p260 and p460 Compute Nodes Installation and Service Guide...
Page 149
B6000266 • B6xx0266 B6000266 Explanation: Contact was lost with the device indicated in the SRC. The operating system is halted waiting for the I/O function of a critical resource to return. When the I/O returns this SRC will disappear from the panel and the O/S will continue running.
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 p260 and p460 Compute Nodes Installation and Service Guide...
Page 151
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;...
If an action solves the problem, then you can stop performing the remaining actions. See Chapter 7, “Parts listing for IBM Flex System p260 and p460 Compute Nodes,” on page 97 to determine which components are CRUs and which components are FRUs.
Page 153
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 154
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 p260 and p460 Compute Nodes Installation and Service Guide...
To find a description of an SRC that is not listed in this IBM Flex System p260 Compute Node or IBM Flex System p460 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 156
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 p260 and p460 Compute Nodes Installation and Service Guide...
Page 157
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.
If an action solves the problem, then you can stop performing the remaining actions. See Chapter 7, “Parts listing for IBM Flex System p260 and p460 Compute Nodes,” on page 97 to determine which components are CRUs and which components are FRUs.
Page 159
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 160
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 p260 and p460 Compute Nodes Installation and Service Guide...
Page 161
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 162
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 p260 and p460 Compute Nodes Installation and Service Guide...
Page 163
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 164
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 p260 and p460 Compute Nodes Installation and Service Guide...
Page 165
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 166
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 p260 and p460 Compute Nodes Installation and Service Guide...
Page 167
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 168
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 p260 and p460 Compute Nodes Installation and Service Guide...
Page 169
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 170
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 p260 and p460 Compute Nodes Installation and Service Guide...
Page 171
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 172
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 p260 and p460 Compute Nodes Installation and Service Guide...
Page 173
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 174
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 p260 and p460 Compute Nodes Installation and Service Guide...
Page 175
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 176
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 p260 and p460 Compute Nodes Installation and Service Guide...
Page 177
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.
If an action solves the problem, then you can stop performing the remaining actions. See Chapter 7, “Parts listing for IBM Flex System p260 and p460 Compute Nodes,” on page 97 to determine which components are CRUs and which components are FRUs.
Page 179
A6xx0255 • B6000255 A6xx0255 Explanation: Contact was lost with the device indicated in the SRC. The operating system is halted waiting for the I/O function of a critical resource to return. When the I/O returns this SRC will disappear from the panel and the O/S will continue running.
Page 180
Otherwise this problem will not be called home. Problem determination: Do not power off the LPAR. Look for and repair problems in the I/O host. Power Systems: IBM Flex System p260 and p460 Compute Nodes Installation and Service Guide...
If an action solves the problem, then you can stop performing the remaining actions. See Chapter 7, “Parts listing for IBM Flex System p260 and p460 Compute Nodes,” on page 97 to determine which components are CRUs and which components are FRUs.
Page 182
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 183
B7000441 • B7000641 B7000441 Explanation: Service processor failure. The platform encountered an error early in the startup or termination process. Response: Replace the system-board and chassis assembly, as described in Replacing the system-board and chassis assembly. B7000443 Explanation: Service processor failure. Response: Replace the system-board and chassis assembly, as described in Replacing the system-board and chassis assembly.
Page 184
B7000A01 Explanation: Informational system log entry only. Response: No corrective action is required. B7000A10 Explanation: Informational system log entry only. Response: No corrective action is required. Power Systems: IBM Flex System p260 and p460 Compute Nodes Installation and Service Guide...
Page 185
B7001150 • B7001732 B7001150 Explanation: Informational system log entry only. Response: No corrective action is required. B7001151 Explanation: Informational system log entry only. Response: No corrective action is required. B7001152 Explanation: Informational system log entry only. Response: No corrective action is required. B7001160 Explanation: Service processor failure Response:...
Page 186
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 187
B7004402 • B70047CB B7004402 Explanation: A system firmware error occurred while attempting to allocate the memory necessary to create a platform dump. Response: Go to Isolating firmware problems. B7004705 Explanation: System firmware failure. A problem occurred when initializing, reading, or using the system VPD. The Capacity on Demand function is not available.
Page 188
1. Use the management console to verify or reconfigure the invalid virtual I/O configuration. 2. Check for server firmware updates; then, install the updates if available. Power Systems: IBM Flex System p260 and p460 Compute Nodes Installation and Service Guide...
Page 189
Explanation: An unsupported Preferred Operating System was detected. The Preferred Operating System specified is not supported. The IPL will not continue. Response: Work with IBM support to select a supported Preferred Operating System; then, re-IPL the system. B7005303 Explanation: An unsupported Preferred Operating System was detected.
Page 190
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 191
B7005603 • B7006909 B7005603 Explanation: Enclosure feature code and/or serial number not valid. Response: Verify that the machine type, model, and serial number are correct for this server. B7006900 Explanation: PCI host bridge failure Response: 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.
Page 192
Explanation: PHYP NVRAM is unavailable after a service processor reset and reload. Response: Go to Isolating firmware problems. B7006954 Explanation: Informational system log entry only. Response: No corrective action is required. Power Systems: IBM Flex System p260 and p460 Compute Nodes Installation and Service Guide...
Page 193
B7006955 • B7006973 B7006955 Explanation: Informational system log entry only. Response: No corrective action is required. B7006956 Explanation: An NVRAM failure was detected. Response: Go to Isolating firmware problems. B7006965 Explanation: Informational system log entry only. Response: No corrective action is required. B7006970 Explanation: PCI host bridge failure Response:...
Page 194
Explanation: Remote I/O (RIO), high-speed link (HSL), or 12X loop status message. Response: Replace the system-board and chassis assembly, as described in Replacing the system-board and chassis assembly. Power Systems: IBM Flex System p260 and p460 Compute Nodes Installation and Service Guide...
Page 195
B7006987 • B70069C2 B7006987 Explanation: Remote I/O (RIO), high-speed link (HSL), or 12X connection failure. Response: Replace the system-board and chassis assembly, as described in Replacing the system-board and chassis assembly. B7006990 Explanation: Service processor failure. Response: Replace the system-board and chassis assembly, as described in Replacing the system-board and chassis assembly.
Page 196
1. Collect error logs and informational logs. 2. Although the partition or application may have continued to run after the failure, it might need to be restarted to recover. Power Systems: IBM Flex System p260 and p460 Compute Nodes Installation and Service Guide...
Page 197
Explanation: PCI-E switch had a permanent unrecoverable (internal) chip failure. All downstream I/O is failed. Response: 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. Chapter 8. Troubleshooting...
Page 198
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. Power Systems: IBM Flex System p260 and p460 Compute Nodes Installation and Service Guide...
Page 199
3. 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. 4. After the FRU has been replaced, the partition or application associated with the failed downstream I/O may have to be restarted.
Page 200
Response: Replace the system-board and chassis assembly, as described in Replacing the system-board and chassis assembly. B700F107 Explanation: System firmware detected an error. Response: 1. Collect the event log information. 2. Go to Isolating firmware problems. Power Systems: IBM Flex System p260 and p460 Compute Nodes Installation and Service Guide...
B700F108 • B700F130 B700F108 Explanation: A firmware error caused the system to terminate. Response: 1. Collect the event log information. 2. Go to Isolating firmware problems. B700F10A Explanation: System firmware detected an error Response: Look for and correct B1xxxxxx errors. B700F10B Explanation: A processor resource has been disabled due to hardware problems Response: Replace the system-board and chassis assembly, as described in Replacing the system-board and chassis...
Page 202
If an action solves the problem, then you can stop performing the remaining actions. See Chapter 7, “Parts listing for IBM Flex System p260 and p460 Compute Nodes,” on page 97 to determine which components are CRUs and which components are FRUs.
Page 203
BA000032 • BA000050 BA000032 Explanation: The firmware failed to register the lpevent queues 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 BA000034 Explanation: The firmware failed to exchange capacity and allocate lpevents Response:...
Page 204
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 p260 and p460 Compute Nodes Installation and Service Guide...
Page 205
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 BA00E830 Explanation: Failure when initializing ibm,event-scan Response: 1. Reboot the server.
Page 206
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 p260 and p460 Compute Nodes Installation and Service Guide...
Page 207
BA010003 • BA010007 BA010003 Explanation: Cannot get server hardware address 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 208
AIX or Linux. Verify that all of the iSCSI configuration arguments on the operating system comply with the configuration for the iSCSI Host Bus Adapter (HBA), which is the iSCSI initiator. Power Systems: IBM Flex System p260 and p460 Compute Nodes Installation and Service Guide...
Page 209
BA01000E • BA010015 BA01000E Explanation: The LUN specified is not valid. Response: The embedded host Ethernet adapters (HEAs) help provide iSCSI, which is supported by iSCSI software device drivers on either AIX or Linux. Verify that all of the iSCSI configuration arguments on the operating system comply with the configuration for the iSCSI Host Bus Adapter (HBA), which is the iSCSI initiator.
Page 210
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 p260 and p460 Compute Nodes Installation and Service Guide...
Page 211
BA017020 • BA01B012 BA017020 Explanation: Failed to open the TFTP package Response: Verify that the Trivial File Transfer Protocol (TFTP) parameters are correct. BA017021 Explanation: Failed to load the TFTP file Response: Verify that the TFTP server and network connections are correct. BA01B010 Explanation: Opening the BOOTP node failed.
Page 212
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 p260 and p460 Compute Nodes Installation and Service Guide...
Page 213
BA01D030 • BA01D052 BA01D030 Explanation: DHCP failed to write to the network Response: 1. Verify that the network cable is connected, and that the network is active. 2. If the problem persists: Search RETAIN tips and the firmware change history for the reference code to determine the recommended actions.
Page 214
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 p260 and p460 Compute Nodes Installation and Service Guide...
Page 215
BA030011 • BA040030 BA030011 Explanation: RTAS attempt to allocate memory failed 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 BA04000F Explanation: Self test failed on device;...
Page 216
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 p260 and p460 Compute Nodes Installation and Service Guide...
Page 217
BA050004 • BA060020 BA050004 Explanation: Failed to locate service processor device tree node. 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 BA05000A Explanation: Failed to send a boot failed message Response:...
Page 218
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 p260 and p460 Compute Nodes Installation and Service Guide...
Page 219
BA060061 • BA060200 BA060061 Explanation: The operating system expects a non-IOSP partition, but it failed to make the transition to MGC mode. Response: 1. Verify that: v The alpha-mode operating system image is intended for this partition. v The configuration of the partition supports an alpha-mode operating system. 2.
Page 220
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 p260 and p460 Compute Nodes Installation and Service Guide...
Page 221
BA090002 • BA09000B BA090002 Explanation: SCSD DASD: test unit ready failed; sense data available 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 BA090003 Explanation: SCSD DASD: send diagnostic failed;...
Page 222
5. 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 p260 and p460 Compute Nodes Installation and Service Guide...
Page 223
BA090011 • BA120002 BA090011 Explanation: The retry limit has been exceeded. 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 224
5. 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 p260 and p460 Compute Nodes Installation and Service Guide...
Page 225
BA130011 • BA130014 BA130011 Explanation: USB CD-ROM in the media tray: execution of ATA/ATAPI command was not completed with the allowed time. Response: 1. Retry the operation. 2. Reboot the server. 3. Troubleshoot the media tray and CD-ROM drive. 4. Replace the USB CD or DVD drive. 5.
Page 226
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 p260 and p460 Compute Nodes Installation and Service Guide...
Page 227
BA140003 • BA151002 BA140003 Explanation: The SCSD read/write optical 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 228
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 p260 and p460 Compute Nodes Installation and Service Guide...
Page 229
BA154040 • BA15C001 BA154040 Explanation: The TFTP package open 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 230
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 p260 and p460 Compute Nodes Installation and Service Guide...
Page 231
BA170210 • BA170998 BA170210 Explanation: Setenv/$Setenv parameter error - name contains a null character 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 232
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 p260 and p460 Compute Nodes Installation and Service Guide...
Page 233
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 234
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 p260 and p460 Compute Nodes Installation and Service Guide...
Page 235
BA210001 • BA210010 BA210001 Explanation: Partition firmware reports a stack underflow was caught 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 236
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 p260 and p460 Compute Nodes Installation and Service Guide...
Page 237
BA210101 • BA220010 BA210101 Explanation: The partition firmware event log queue is full 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 BA210102 Explanation: There was a communication failure between partition firmware and the hypervisor.
Page 238
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 p260 and p460 Compute Nodes Installation and Service Guide...
Page 239
If a firmware update is needed, see Updating the firmware BA278009 Explanation: The operating system's server firmware update management tools are incompatible with this system. Response: Go to the IBM download site at www14.software.ibm.com/webapp/set2/sas/f/lopdiags/home.html to download the latest version of the service aids package for Linux. BA27800A Explanation: The firmware installation failed due to a hardware error that was reported.
Page 240
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 p260 and p460 Compute Nodes Installation and Service Guide...
Page 241
BA330000 • BA330004 BA330000 Explanation: Memory allocation 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 242
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 p260 and p460 Compute Nodes Installation and Service Guide...
Page 243
BA340005 • BA340008 BA340005 Explanation: An internal firmware error occurred; the location code mapping table was corrupted. 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 244
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 p260 and p460 Compute Nodes Installation and Service Guide...
BA340021 • BA400002 BA340021 Explanation: A logical partition event communication failure occurred when writing the BladeCenter open fabric manager system initiator capabilities data to the service processor. Response: 1. Reboot the server. 2. Check for server firmware updates; install the updates if available. 3.
If an action solves the problem, you can stop performing the remaining actions. See Chapter 7, “Parts listing for IBM Flex System p260 and p460 Compute Nodes,” on page 97 to determine which components are CRUs and which components are FRUs.
Page 247
C1001F0F • C1009X02 C1001F0F Explanation: Pre-standby: waiting for standby synchronization from initial transition file 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 248
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 p260 and p460 Compute Nodes Installation and Service Guide...
Page 249
C1009X18 • C1009X28 C1009X18 Explanation: Hardware object manager (HOM): GARD 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 250
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 p260 and p460 Compute Nodes Installation and Service Guide...
Page 251
C1009X3C • C1009X48 C1009X3C Explanation: Processor self-test 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. Replace the system-board, as described in Replacing the system-board and chassis assembly. C1009X40 Explanation: Processor self-test step in progress Response:...
Page 252
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 p260 and p460 Compute Nodes Installation and Service Guide...
Page 253
C1009X5E • C1009X68 C1009X5E Explanation: Processor cache test case 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 254
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 p260 and p460 Compute Nodes Installation and Service Guide...
Page 255
C1009X80 • C1009X8C C1009X80 Explanation: ASIC test being run 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. C1009X82 Explanation: ASIC RGC being reset Response:...
Page 256
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 p260 and p460 Compute Nodes Installation and Service Guide...
Page 257
C1009X9E • C1009XAC C1009X9E Explanation: ASIC HSS set up 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 258
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 p260 and p460 Compute Nodes Installation and Service Guide...
Page 259
C1009XBD • C1009XCC C1009XBD Explanation: AVP memory test case 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 260
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 p260 and p460 Compute Nodes Installation and Service Guide...
Page 261
C103A400 • C116C2XX C103A400 Explanation: Special purpose registers are being loaded, and instructions are being started, on the server processors 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.
If an action solves the problem, you can stop performing the remaining actions. See Chapter 7, “Parts listing for IBM Flex System p260 and p460 Compute Nodes,” on page 97 to determine which components are CRUs and which components are FRUs.
Page 263
C2001010 • C2001300 C2001010 Explanation: Startup source Response: 1. Go to Recovering the system firmware. 2. Replace the system-board, as described in Replacing the system-board and chassis assembly. C2001100 Explanation: Adding partition resources to the secondary configuration Response: 1. Go to Recovering the system firmware. 2.
Page 264
Explanation: Issuing a power on command 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 p260 and p460 Compute Nodes Installation and Service Guide...
Page 265
C200211F • C20023FF C200211F Explanation: Power on command successful Response: 1. Go to Recovering the system firmware. 2. Replace the system-board, as described in Replacing the system-board and chassis assembly. C20021FF Explanation: Power on phase complete Response: 1. Go to Recovering the system firmware. 2.
Page 266
Explanation: Validating ISL command parameters 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 p260 and p460 Compute Nodes Installation and Service Guide...
Page 267
C2003111 • C20032FF C2003111 Explanation: Waiting for bus object to become operational Response: 1. Go to Recovering the system firmware. 2. Replace the system-board, as described in Replacing the system-board and chassis assembly. C2003112 Explanation: Waiting for bus unit to become disabled Response: 1.
Page 268
Explanation: Preparing connection to load source device 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 p260 and p460 Compute Nodes Installation and Service Guide...
Page 269
C20043FF • C2006030 C20043FF Explanation: Load source device is connected Response: 1. Go to Recovering the system firmware. 2. Replace the system-board, as described in Replacing the system-board and chassis assembly. C2006000 Explanation: Locating first LID information on the load source Response: 1.
Page 270
Explanation: Loading raw kernel memory image completed 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 p260 and p460 Compute Nodes Installation and Service Guide...
Page 271
C2008040 • C2008100 C2008040 Explanation: Begin transfer slot locks to partition Response: 1. Go to Recovering the system firmware. 2. Replace the system-board, as described in Replacing the system-board and chassis assembly. C2008060 Explanation: End transfer slot locks to partition Response: 1.
Page 272
Explanation: End associate of system ports 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 p260 and p460 Compute Nodes Installation and Service Guide...
If an action solves the problem, you can stop performing the remaining actions. See Chapter 7, “Parts listing for IBM Flex System p260 and p460 Compute Nodes,” on page 97 to determine which components are CRUs and which components are FRUs.
If an action solves the problem, you can stop performing the remaining actions. See Chapter 7, “Parts listing for IBM Flex System p260 and p460 Compute Nodes,” on page 97 to determine which components are CRUs and which components are FRUs.
Page 275
CA000030 • CA000050 CA000030 Explanation: Attempting to establish a communication link by using lpevents Response: 1. Go to Checkout procedure. 2. Replace the system-board, as described in Replacing the system-board and chassis assembly. CA000032 Explanation: Attempting to register lpevent queues Response: 1.
Page 276
Explanation: Attempting to load the second pass of C code 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 p260 and p460 Compute Nodes Installation and Service Guide...
Page 277
CA0000A0 • CA00D008 CA0000A0 Explanation: Open firmware package corrupted (phase 2) Response: 1. Go to Checkout procedure. 2. Replace the system-board, as described in Replacing the system-board and chassis assembly. CA00D001 Explanation: PCI probe process completed, create PCI bridge interrupt routing properties Response: 1.
Page 278
Explanation: Runtime open firmware initialization complete; control returned to initialization 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 p260 and p460 Compute Nodes Installation and Service Guide...
Page 279
CA00D020 • CA00E10A CA00D020 Explanation: About to download the run the SLIC loader (IOP-less boot) Response: 1. Go to Checkout procedure. 2. Replace the system-board, as described in Replacing the system-board and chassis assembly. CA00D021 Explanation: About to download the run the IO Reporter (for VPD collection) Response: 1.
Page 280
Replace the system-board, as described in Replacing the system-board and chassis assembly. CA00E134 Explanation: Create memory 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 p260 and p460 Compute Nodes Installation and Service Guide...
Page 281
CA00E135 • CA00E139 CA00E135 Explanation: Create HCA node Response: 1. Go to Checkout procedure. 2. Replace the system-board, as described in Replacing the system-board and chassis assembly. CA00E136 Explanation: Create BSR node Response: 1. Go to Checkout procedure. 2. Replace the system-board, as described in Replacing the system-board and chassis assembly. CA00E137 Explanation: Create HEA node Response:...
Page 282
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 p260 and p460 Compute Nodes Installation and Service Guide...
Page 283
CA00E142 • CA00E150 CA00E142 Explanation: The management module bootlist is being set from the operating system bootlist 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. CA00E143 Explanation: The operating system bootlist is being set from the management module bootlist Response:...
Page 284
CA00E156 Explanation: Create plug-in PCI bridge 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 p260 and p460 Compute Nodes Installation and Service Guide...
Page 285
CA00E15B • CA00E174 CA00E15B Explanation: Transfer control to operating system (service mode boot) Response: Go to Boot problem resolution. CA00E15F Explanation: Adapter VPD evaluation Response: 1. Go to Checkout procedure. 2. Replace the system-board, as described in Replacing the system-board and chassis assembly. CA00E170 Explanation: Start of PCI bus probe Response:...
Page 286
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 p260 and p460 Compute Nodes Installation and Service Guide...
Page 287
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 288
Explanation: User requested boot using customized service mode boot list using keyboard entry 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 p260 and p460 Compute Nodes Installation and Service Guide...
Page 289
CA00E1A4 • CA00E1AB CA00E1A4 Explanation: User requested boot to SMS menus Response: 1. Go to Checkout procedure. 2. Replace the system-board, as described in Replacing the system-board and chassis assembly. CA00E1A5 Explanation: User requested boot to open firmware prompt Response: 1.
Page 290
CA00E1B2 Explanation: XOFF received, waiting for XON 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 p260 and p460 Compute Nodes Installation and Service Guide...
Page 291
CA00E1B3 • CA00E1D4 CA00E1B3 Explanation: XON received Response: 1. Go to Checkout procedure. 2. Replace the system-board, as described in Replacing the system-board and chassis assembly. CA00E1B4 Explanation: System-directed boot-string didn't load an operating system Response: 1. Go to Checkout procedure. 2.
Page 292
2. Replace the system-board, as described in Replacing the system-board and chassis assembly. CA00E1F2 Explanation: Power on password prompt 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 p260 and p460 Compute Nodes Installation and Service Guide...
Page 293
CA00E1F3 • CA00E1F8 CA00E1F3 Explanation: Privileged-access password prompt Response: 1. Go to Checkout procedure. 2. Replace the system-board, as described in Replacing the system-board and chassis assembly. CA00E1F4 Explanation: End self-test sequence on one or more boot devices; begin system management services Response: 1.
Page 294
Explanation: Building device list for fibre-channel (SAN) adapters. (The WWPN 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. Power Systems: IBM Flex System p260 and p460 Compute Nodes Installation and Service Guide...
Page 295
CA00E1FF • CA00E444 CA00E1FF Explanation: Build device list for fibre-channel (SAN) adapters. (The LUN 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. CA00E440 Explanation: Validate NVRAM, initialize partitions as needed Response:...
Page 296
2. Replace the system-board, as described in Replacing the system-board and chassis assembly. CA00E840 Explanation: Initializing hot plug 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 p260 and p460 Compute Nodes Installation and Service Guide...
Page 297
CA00E843 • CA00E875 CA00E843 Explanation: Initializing interface/AIX access Response: 1. Go to Checkout procedure. 2. Replace the system-board, as described in Replacing the system-board and chassis assembly. CA00E850 Explanation: Initializing dynamic reconfiguration Response: 1. Go to Checkout procedure. 2. Replace the system-board, as described in Replacing the system-board and chassis assembly. CA00E860 Explanation: Initializing sensors Response:...
Page 298
2. Replace the system-board, as described in Replacing the system-board and chassis assembly. CA00E887 Explanation: Initialize gdata for activate_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 p260 and p460 Compute Nodes Installation and Service Guide...
Page 299
CA00E890 • CA26TTSS CA00E890 Explanation: Starting to initialize open firmware Response: 1. Go to Checkout procedure. 2. Replace the system-board, as described in Replacing the system-board and chassis assembly. CA00E891 Explanation: Finished initializing open firmware Response: 1. Go to Checkout procedure. 2.
Page 300
2. Restart the server using the permanent boot image, as described in Starting the PERM image. 3. Use the Update and Manage System Flash menu to reject the temporary image. Power Systems: IBM Flex System p260 and p460 Compute Nodes Installation and Service Guide...
If an action solves the problem, you can stop performing the remaining actions. See Chapter 7, “Parts listing for IBM Flex System p260 and p460 Compute Nodes,” on page 97 to determine which components are CRUs and which components are FRUs.
Page 302
2. Replace the system-board, as described in Replacing the system-board and chassis assembly. D1061XXX Explanation: Dump all NVRAM 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 p260 and p460 Compute Nodes Installation and Service Guide...
Page 303
D1071XXX • D1131XXX D1071XXX Explanation: Dump component trace for failing component Response: 1. Go to Checkout procedure. 2. Replace the system-board, as described in Replacing the system-board and chassis assembly. D1081XXX Explanation: Dump component data from /opt/p0 Response: 1. Go to Checkout procedure. 2.
Page 304
Explanation: Dump BDMP component trace (after dump if enough space) 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 p260 and p460 Compute Nodes Installation and Service Guide...
Page 305
D11A1XXX • D1241XXX D11A1XXX Explanation: Dump any state information before dumping starts Response: 1. Go to Checkout procedure. 2. Replace the system-board, as described in Replacing the system-board and chassis assembly. D11B1XXX Explanation: Dump /proc filesystem Response: 1. Go to Checkout procedure. 2.
Page 306
Explanation: Jump to the position in dump directly after CRC1 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 p260 and p460 Compute Nodes Installation and Service Guide...
Page 307
D12B1XXX • D1301XXX D12B1XXX Explanation: Initialize the headers dump time and serial numbers Response: 1. Go to Checkout procedure. 2. Replace the system-board, as described in Replacing the system-board and chassis assembly. D12C1XXX Explanation: Display final SRC to panel Response: 1.
Page 308
2. Replace the system-board, as described in Replacing the system-board and chassis assembly. D13B1XXX Explanation: Get dump length sequence 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 p260 and p460 Compute Nodes Installation and Service Guide...
If an action solves the problem, you can stop performing the remaining actions. See Chapter 7, “Parts listing for IBM Flex System p260 and p460 Compute Nodes,” on page 97 to determine which components are CRUs and which components are FRUs.
Page 310
2. Replace the system-board, as described in Replacing the system-board and chassis assembly. D1XX3Y08 Explanation: Send command 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 p260 and p460 Compute Nodes Installation and Service Guide...
Page 311
D1XX3Y09 • D1XX3YF0 D1XX3Y09 Explanation: Get optimized cache Response: 1. Go to Checkout procedure. 2. Replace the system-board, as described in Replacing the system-board and chassis assembly. D1XX3Y0A Explanation: Get general purpose (GP) register Response: 1. Go to Checkout procedure. 2.
If an action solves the problem, you can stop performing the remaining actions. See Chapter 7, “Parts listing for IBM Flex System p260 and p460 Compute Nodes,” on page 97 to determine which components are CRUs and which components are FRUs.
D1XXC000 • D1XXC003 D1XXC000 Explanation: Indicates a message is ready to send to the hypervisor to power off Response: 1. Go to Checkout procedure. 2. Replace the system-board, as described in Replacing the system-board and chassis assembly. D1XXC001 Explanation: Waiting for the hypervisor to acknowledge the delayed power off notification Response: 1.
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_713 Power Systems: IBM Flex System p260 and p460 Compute Nodes Installation and Service Guide...
Page 315
101-714 • 101-717 101-714 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 316
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_721 Power Systems: IBM Flex System p260 and p460 Compute Nodes Installation and Service Guide...
Page 317
101-722 • 101-725 101-722 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 318
2. If the 8-digit error and location codes were NOT reported, run AIX diagnostics in problem determination procedure and record and report the 8-digit error and location codes for this SRN. Response: Power Systems: IBM Flex System p260 and p460 Compute Nodes Installation and Service Guide...
110-101 • 110-923 110-101 Explanation: The diagnostics did not detect an installed resource. If this SRN appeared when running concurrent diagnostics, then run concurrent diagnostics using the diag -a command. Response: 110-921 Explanation: The system halted while diagnostics were executing. Go to Performing the checkout procedure or problem resolution.
Response: Failing Item: v FFC_812 v FFC_XXX 110-935 Explanation: The system halted while diagnostics were executing. Use the problem determination procedure. Response: Failing Item: v FFC_812 Power Systems: IBM Flex System p260 and p460 Compute Nodes Installation and Service Guide...
111-107 • 650-XXX 111-107 Explanation: A machine check occurred. Go to Performing the checkout procedure. Response: 111-108 Explanation: An encoded SRN was displayed. Go to Performing the checkout procedure. Response: 111-121 Explanation: There is a display problem. Go to Performing the checkout procedure. Response: 111-78C Explanation: PCI adapter I/O bus problem.
Page 322
Explanation: A non-critical error has been detected: external cache parity or multi-bit ECC error. Schedule deferred maintenance. Go to Performing the checkout procedure. Response: Failing Item: v FFC_D01 Power Systems: IBM Flex System p260 and p460 Compute Nodes Installation and Service Guide...
Page 323
652-613 • 652-632 652-613 Explanation: A non-critical error has been detected: external cache ECC single-bit error. Schedule deferred maintenance. Go to Performing the checkout procedure. Response: Failing Item: v FFC_D01 652-623 Explanation: A non-critical error has been detected: correctable error threshold exceeded. Schedule deferred maintenance.
Page 324
652-666 Explanation: A non-critical error has been detected: correctable error threshold exceeded. Schedule deferred maintenance. Go to Performing the checkout procedure. Response: Failing Item: v FFC_304 Power Systems: IBM Flex System p260 and p460 Compute Nodes Installation and Service Guide...
Page 325
652-669 • 652-732 652-669 Explanation: A non-critical error has been detected: correctable error threshold exceeded. Schedule deferred G maintenance. Go to Performing the checkout procedure. Response: Failing Item: v FFC_2CD 652-66A Explanation: A non-critical error has been detected: correctable error threshold exceeded. Schedule deferred maintenance.
Page 326
Explanation: A non-critical error has been detected: intermediate or system bus time-out error. Schedule deferred maintenance. Go to Performing the checkout procedure. Response: Failing Item: v FFC_2D2 v FFC_292 Power Systems: IBM Flex System p260 and p460 Compute Nodes Installation and Service Guide...
Page 327
652-770 • 652-88X 652-770 Explanation: A non-critical error has been detected: intermediate system bus address parity error. Schedule deferred maintenance. Go to Performing the checkout procedure. Response: Failing Item: v FFC_2C8 v FFC_292 652-771 Explanation: A non-critical error has been detected: intermediate or system bus data parity error. Schedule deferred maintenance.
Page 328
Explanation: I/O Card NVRAM test failed. Go to Performing the checkout procedure. Response: Failing Item: v FFC_814 815-100 Explanation: The floating-point processor test failed. Go to Performing the checkout procedure. Response: Failing Item: v FFC_815 Power Systems: IBM Flex System p260 and p460 Compute Nodes Installation and Service Guide...
Page 329
815-101 • 817-123 815-101 Explanation: Floating point processor failed. Go to Performing the checkout procedure. Response: Failing Item: v FFC_815 815-102 Explanation: Floating point processor failed. Go to Performing the checkout procedure. Response: Failing Item: v FFC_815 815-200 Explanation: Power-on self-test indicates a processor failure. Go to Performing the checkout procedure. Response: Failing Item: v FFC_815...
Page 330
Response: Failing Item: v FFC_817 817-215 Explanation: Time of day clock not running test failed. Go to Performing the checkout procedure. Response: Failing Item: v FFC_817 Power Systems: IBM Flex System p260 and p460 Compute Nodes Installation and Service Guide...
Page 331
817-217 • 887-105 817-217 Explanation: Time of day clock not running. Go to Performing the checkout procedure. Response: Failing Item: v FFC_817 887-101 Explanation: POS register test failed. Go to Performing the checkout procedure. Response: Failing Item: v FFC_887 887-102 Explanation: 887I/O register test failed.
Page 332
Explanation: External loopback fairness test failed. Go to Performing the checkout procedure. Response: Failing Item: v FFC_887 887-111 Explanation: External loopback fairness and parity tests failed. Go to Performing the checkout procedure. Response: Failing Item: v FFC_887 Power Systems: IBM Flex System p260 and p460 Compute Nodes Installation and Service Guide...
Page 333
887-112 • 887-116 887-112 Explanation: External loopback (twisted pair) test failed. Go to Performing the checkout procedure. Response: Failing Item: v FFC_887 887-113 Explanation: External loopback (twisted pair) parity test failed. Go to Performing the checkout procedure. Response: Failing Item: v FFC_887 887-114 Explanation: Ethernet loopback (twisted pair) fairness test failed.
Page 334
Explanation: Ethernet 10 base-2 transceiver test failed. Go to Performing the checkout procedure. Response: Failing Item: v FFC_B09 887-123 Explanation: Internal loopback test failed. Go to Performing the checkout procedure. Response: Failing Item: v FFC_887 Power Systems: IBM Flex System p260 and p460 Compute Nodes Installation and Service Guide...
Page 335
887-124 • 887-304 887-124 Explanation: Software error log indicates a hardware problem. Go to Performing the checkout procedure. Response: Failing Item: v FFC_887 887-125 Explanation: Fuse test failed. Go to Performing the checkout procedure. Response: Failing Item: v FFC_887 887-202 Explanation: Vital Product Data test failed.
Page 336
Explanation: Fuse test failed. Go to Performing the checkout procedure. Response: Failing Item: v FFC_887 887-401 Explanation: Circuit breaker for Ethernet test failed. Go to Performing the checkout procedure. Response: Failing Item: v FFC_887 Power Systems: IBM Flex System p260 and p460 Compute Nodes Installation and Service Guide...
Page 337
887-402 • 101-XXXX 887-402 Explanation: Ethernet 10 Base-2 transceiver test failed. Go to Performing the checkout procedure. Response: Failing Item: v FFC_887 887-403 Explanation: Ethernet 10 Base-T transceiver test failed. Go to Performing the checkout procedure. Response: Failing Item: v FFC_887 887-405 Explanation: Ethernet- network Rerun diagnostics in advanced mode for accurate problem determination.
Page 338
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 p260 and p460 Compute Nodes Installation and Service Guide...
Page 339
252B-712 • 252B-715 252B-712 Explanation: 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_252B...
Page 340
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 v FFC_293 Power Systems: IBM Flex System p260 and p460 Compute Nodes Installation and Service Guide...
Page 341
252B-719 • 252B-722 252B-719 Explanation: Device bus termination power lost or not detected. 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 342
Explanation: Error log analysis indicates that the microcode could not be loaded on the adapter. Go to Performing the checkout procedure. Response: Failing Item: v FFC_254 Power Systems: IBM Flex System p260 and p460 Compute Nodes Installation and Service Guide...
Page 343
254E-604 • 254E-702 254E-604 Explanation: Error log analysis indicates a permanent adapter failure. Go to Performing the checkout procedure. Response: Failing Item: v FFC_254 254E-605 Explanation: Error log analysis indicates permanent adapter failure is reported on the other port of this adapter. Go to Performing the checkout procedure.
Page 344
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 p260 and p460 Compute Nodes Installation and Service Guide...
Page 345
256D-603 • 256D-606 256D-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 346
Explanation: Configuration error. Go to Performing the checkout procedure. Response: Failing Item: v FFC_25C4 25C4-601 Explanation: Download firmware error. Go to Performing the checkout procedure. Response: Failing Item: v FFC_25C4 Power Systems: IBM Flex System p260 and p460 Compute Nodes Installation and Service Guide...
Page 347
25C4-602 • 2604-104 25C4-602 Explanation: EEPROM read error. Go to Performing the checkout procedure. Response: Failing Item: v FFC_25C4 25C4-701 Explanation: Permanent adapter failure. Go to Performing the checkout procedure. Response: Failing Item: v FFC_25C4 25C4-XXX Explanation: Generic reference for Broadcom adapter. Go to Performing the checkout procedure. Response: Failing Item: v FFC_25C4...
Page 348
FFC_2604 2604-201 Explanation: Configuration Register Test Failure for the Fibre Channel adapter card. Go to Performing the checkout procedure. Response: Failing Item: v FFC_2604 v FFC_221 Power Systems: IBM Flex System p260 and p460 Compute Nodes Installation and Service Guide...
Page 349
2604-203 • 2604-703 2604-203 Explanation: PCI Wrap Test Failure for the Fibre Channel adapter card. Replace the 4Gb Fibre Channel Adapter card. Response: Failing Item: v FFC_2604 2604-204 Explanation: DMA Test Failure for the Fibre Channel adapter card. Go to Performing the checkout procedure. Response: Failing Item: v FFC_2604...
Page 350
FFC_2604 2607-102 Explanation: Reset Test failure for the Fibre Channel adapter card. Replace the 8Gb PCIe Fibre Channel Expansion Card. Response: Failing Item: v FFC_2607 Power Systems: IBM Flex System p260 and p460 Compute Nodes Installation and Service Guide...
Page 351
2607-103 • 2607-108 2607-103 Explanation: Register Test failure for the Fibre Channel adapter card. Replace the 8Gb PCIe Fibre Channel Expansion Card. Response: Failing Item: v FFC_2607 2607-104 Explanation: SRAM Test failure for the Fibre Channel adapter card. Replace the 8Gb PCIe Fibre Channel Expansion Card.
Page 352
FFC_221 2607-205 Explanation: Error on Read/Write Operation 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 p260 and p460 Compute Nodes Installation and Service Guide...
Page 353
2607-701 • 2607-706 2607-701 Explanation: Error Log Analysis indicates that the adapter self-test failed for the Fibre Channel adapter card. Go to Performing the checkout procedure. Response: Failing Item: v FFC_2607 2607-703 Explanation: Error Log Analysis indicates that an unknown adapter error has occurred for the Fibre Channel adapter card.
Page 354
2. Replace the cable. 3. Verify that the network is functional. 4. Verify that the network switch is functional. Response: Failing Item: v CABLE v NETWORK Power Systems: IBM Flex System p260 and p460 Compute Nodes Installation and Service Guide...
Page 355
2624-301 • 2624-703 2624-301 Explanation: Loop back test failure. Do the following steps one at a time, in order, and rerun the test after each step: 1. Reseat the cable. 2. Replace the cable. 3. Verify that the network is functional. 4.
Page 356
Explanation: Generic reference for 4X PCI-E DDR InfiniBand Host Channel Adapter. Go to Performing the checkout procedure. Response: Failing Item: v FFC_2624 2625-101 Explanation: Configuration failure. Replace the 2-port QDR 40 GB/S InfiniBand expansion card (CFFh). Response: Failing Item: v FFC_2625 Power Systems: IBM Flex System p260 and p460 Compute Nodes Installation and Service Guide...
Page 357
2625-102 • 2625-301 2625-102 Explanation: Queue pair create failure. Replace the 2-port QDR 40 GB/S InfiniBand expansion card (CFFh). Response: Failing Item: v FFC_2625 2625-103 Explanation: Loop back test failure. Replace the 2-port QDR 40 GB/S InfiniBand expansion card (CFFh). Response: Failing Item: v FFC_2625...
Page 358
Explanation: Error Log Analysis indicates that this adapter has failed due to a internal error. Replace the 2-port QDR 40 GB/S InfiniBand expansion card (CFFh). Response: Failing Item: v FFC_2625 Power Systems: IBM Flex System p260 and p460 Compute Nodes Installation and Service Guide...
Page 359
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 360
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 361
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 362
FFC_2640 2640-136 Explanation: Timeout waiting for controller or drive with no busy status. Go to Performing the checkout procedure. Response: Failing Item: v FFC_2640 v FFC_2631 Power Systems: IBM Flex System p260 and p460 Compute Nodes Installation and Service Guide...
Page 363
268B-102 • 268B-110 268B-102 Explanation: An unrecoverable media error occurred. Replace the 300 GB SFF SAS Hard Disk Drive. Response: Failing Item: v FFC_268B 268B-104 Explanation: The motor failed to restart. Replace the 300 GB SFF SAS Hard Disk Drive. Response: Failing Item: v FFC_268B...
Page 364
Explanation: A SCSI command time-out occurred. Replace the 300 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_268B v FFC_B88 Power Systems: IBM Flex System p260 and p460 Compute Nodes Installation and Service Guide...
Page 365
268B-120 • 268B-128 268B-120 Explanation: A SCSI busy or command error. Replace the 300 GB SFF SAS Hard Disk Drive. Response: Failing Item: v FFC_268B 268B-122 Explanation: A SCSI reservation conflict error. Replace the 300 GB SFF SAS Hard Disk Drive. Response: Failing Item: v FFC_268B...
Page 366
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_268B v FFC_B88 v SOFTWARE Power Systems: IBM Flex System p260 and p460 Compute Nodes Installation and Service Guide...
Page 367
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 368
Explanation: The electronics card test failed. Replace the 200 GB SATA Solid State Drive. Response: Failing Item: v FFC_26B4 26B4-108 Explanation: The bus test failed. Replace the 200 GB SATA Solid State Drive. Response: Failing Item: v FFC_26B4 Power Systems: IBM Flex System p260 and p460 Compute Nodes Installation and Service Guide...
26B4-110 • 26B4-117 26B4-110 Explanation: The media format is corrupted. Replace the 200 GB SATA Solid State Drive. Response: Failing Item: v FFC_26B4 26B4-112 Explanation: The diagnostic test failed. Replace the 200 GB SATA Solid State Drive. Response: Failing Item: v FFC_26B4 26B4-114 Explanation: An unrecoverable hardware error.
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 v FFC_26BD Power Systems: IBM Flex System p260 and p460 Compute Nodes Installation and Service Guide...
Page 371
26B4-126 • 26B4-130 26B4-126 Explanation: A software error was caused by a hardware failure. 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.
Page 372
SOFTWARE v FFC_26B4 v FFC_26BD v FFC_B88 26B4-136 Explanation: The certify operation failed. Replace the 200 GB SATA Solid State Drive. Response: Failing Item: v FFC_26B4 Power Systems: IBM Flex System p260 and p460 Compute Nodes Installation and Service Guide...
Page 373
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: 26B4-140 Explanation: Error log analysis indicates poor signal quality. Replace each part reported by the diagnostic program one at a time.
Page 374
Response: Failing Item: v FFC_26D2 26D2-110 Explanation: The media format is corrupted. Replace the 600 GB SFF SAS Hard Disk Drive. Response: Failing Item: v FFC_26D2 Power Systems: IBM Flex System p260 and p460 Compute Nodes Installation and Service Guide...
Page 375
26D2-112 • 26D2-118 26D2-112 Explanation: The diagnostic test failed. Replace the 600 GB SFF SAS Hard Disk Drive. Response: Failing Item: v FFC_26D2 26D2-114 Explanation: An unrecoverable hardware error. Replace the 600 GB SFF SAS Hard Disk Drive. Response: Failing Item: v FFC_26D2 26D2-116 Explanation: A protocol error.
Page 376
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_26D2 Power Systems: IBM Flex System p260 and p460 Compute Nodes Installation and Service Guide...
Page 377
26D2-129 • 26D2-135 26D2-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 378
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_26D2 Power Systems: IBM Flex System p260 and p460 Compute Nodes Installation and Service Guide...
Page 379
26D2-640 • 26D7-108 26D2-640 Explanation: Error log analysis indicates a path error. Replace the 600 GB SFF SAS Hard Disk Drive. Response: Failing Item: v FFC_26D2 26D7-102 Explanation: An unrecoverable media error occurred. Replace the 900 GB SFF SAS Hard Disk Drive. Response: Failing Item: v FFC_26D7...
Page 380
2. If you do not find a problem, call your operating-system support person. Response: Failing Item: v FFC_26D7 26D7-117 Explanation: A write-protect error occurred. Replace the 900 GB SFF SAS Hard Disk Drive. Response: Failing Item: v FFC_26D7 Power Systems: IBM Flex System p260 and p460 Compute Nodes Installation and Service Guide...
Page 381
26D7-118 • 26D7-126 26D7-118 Explanation: A SCSI command time-out occurred. 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 26D7-120 Explanation: A SCSI busy or command error.
Page 382
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_B88 v SOFTWARE Power Systems: IBM Flex System p260 and p460 Compute Nodes Installation and Service Guide...
Page 383
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: v FFC_26D7 Chapter 8.
Page 384
Explanation: Adapter configuration error Replace the PCIe2 16Gb 2-port FC Mezzanine Adapter If the problem persists, replace the system board. Response: Failing Item: v FFC_2750 v FFC_221 Power Systems: IBM Flex System p260 and p460 Compute Nodes Installation and Service Guide...
Page 385
2750-601 • 2755-201 2750-601 Explanation: Adapter taken off-line. Replace the PCIe2 16Gb 2-port FC Mezzanine Adapter Response: Failing Item: v FFC_2750 2750-602 Explanation: Adapter parity error Replace the PCIe2 16Gb 2-port FC Mezzanine Adapter Response: Failing Item: v FFC_2750 2750-603 Explanation: Permanent adapter failure.
Page 386
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 Power Systems: IBM Flex System p260 and p460 Compute Nodes Installation and Service Guide...
Page 387
5. Go to Performing the checkout procedure. Response: 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 Chapter 8. Troubleshooting...
Page 388
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 389
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 390
Explanation: Permanent controller error. Replace the PCIe x8 Internal 3Gb SAS Adapter. Response: Failing Item: v FFC_2D29 2D29-713 Explanation: Controller error. Replace the PCIe x8 Internal 3Gb SAS Adapter. Response: Failing Item: v FFC_2D29 Power Systems: IBM Flex System p260 and p460 Compute Nodes Installation and Service Guide...
Page 391
2D29-720 • 2E00-701 2D29-720 Explanation: Controller devce bus configuration error. Use MAP3150 to determine resolution. Response: 2E00-201 Explanation: Configuration error. 1. Check the BladeCenter management-module event log. If an error was recorded by the system, see POST progress codes (checkpoints). 2.
Page 392
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 Power Systems: IBM Flex System p260 and p460 Compute Nodes Installation and Service Guide...
Page 393
2E10-604 • 2E10-701 2E10-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 394
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 p260 and p460 Compute Nodes Installation and Service Guide...
Page 395
2E13-603 • 2E13-606 2E13-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 396
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 v FFC_221 Power Systems: IBM Flex System p260 and p460 Compute Nodes Installation and Service Guide...
Page 397
2E14-601 • 2E14-604 2E14-601 Explanation: Error Log Analysis indicates 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 398
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 v FFC_221 Power Systems: IBM Flex System p260 and p460 Compute Nodes Installation and Service Guide...
Page 399
2E15-201 • 2E15-603 2E15-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_2E15...
Page 400
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 v FFC_221 Power Systems: IBM Flex System p260 and p460 Compute Nodes Installation and Service Guide...
Page 401
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 402
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 403
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 404
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_2E21 Power Systems: IBM Flex System p260 and p460 Compute Nodes Installation and Service Guide...
Page 405
2E21-701 • 2E23-102 2E21-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 406
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 p260 and p460 Compute Nodes Installation and Service Guide...
Page 407
2E23-107 • 2E23-201 2E23-107 Explanation: External Wrap with TCP Checksum 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.
Page 408
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 p260 and p460 Compute Nodes Installation and Service Guide...
Page 409
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 410
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 411
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 412
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_2E34 Power Systems: IBM Flex System p260 and p460 Compute Nodes Installation and Service Guide...
Page 413
2E34-701 • 2E35-602 2E34-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_2E34...
Page 414
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_2E36 Power Systems: IBM Flex System p260 and p460 Compute Nodes Installation and Service Guide...
Page 415
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 416
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 417
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 v FFC_221 Chapter 8.
Page 418
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 419
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 420
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 422
Explanation: Addressed device failed to respond to selection. Go to Performing the checkout procedure. Response: Failing Item: v FFC_722 2506-3010 Explanation: Disk returned wrong response to adapter. Go to Performing the checkout procedure. Response: Failing Item: v FFC_722 Power Systems: IBM Flex System p260 and p460 Compute Nodes Installation and Service Guide...
Page 423
2506-3020 • 2506-4040 2506-3020 Explanation: Storage subsystem configuration error. Go to Performing the checkout procedure. Response: 2506-3100 Explanation: Controller detected device bus interface error. Go to Performing the checkout procedure. Response: 2506-3109 Explanation: Controller timed out a device command. Go to Performing the checkout procedure. Response: 2506-3110 Explanation: Device bus interface error.
Page 424
Explanation: Unsupported enclosure function detected. Go to Performing the checkout procedure. Response: 2506-4150 Explanation: PCI bus error detected by controller. Go to Performing the checkout procedure. Response: Failing Item: v FFC_2506 Power Systems: IBM Flex System p260 and p460 Compute Nodes Installation and Service Guide...
Page 425
2506-4160 • 2506-8157 2506-4160 Explanation: PCI bus error detected by controller. Go to Performing the checkout procedure. Response: Failing Item: v FFC_2506 2506-7001 Explanation: Temporary disk data error. Go to Performing the checkout procedure. Response: Failing Item: v FFC_722 2506-8008 Explanation: A permanent Cache Battery Pack failure occurred.
Page 426
Explanation: Cache data belongs to disks other than those attached. Go to Performing the checkout procedure. Response: 2506-9020 Explanation: Two or more disks are missing from a RAID-5 or RAID 6 Disk Array. Go to Performing the checkout procedure. Response: Power Systems: IBM Flex System p260 and p460 Compute Nodes Installation and Service Guide...
Page 427
2506-9021 • 2506-9027 2506-9021 Explanation: Two or more disks are missing from a RAID-5 or RAID 6 Disk Array. Go to Performing the checkout procedure. Response: 2506-9022 Explanation: Two or more disks are missing from a RAID-5 or RAID 6 Disk Array. Go to Performing the checkout procedure.
Page 428
Performing the checkout procedure. Response: 2506-9050 Explanation: Required cache data can not be located for one or more disks. Go to Performing the checkout procedure. Response: Power Systems: IBM Flex System p260 and p460 Compute Nodes Installation and Service Guide...
Page 429
2506-9051 • 2506-9073 2506-9051 Explanation: Cache data exists for one or more missing/failed disks. Go to Performing the checkout procedure. Response: 2506-9052 Explanation: Cache data exists for one or more modified disks. Go to Performing the checkout procedure. Response: 2506-9054 Explanation: RAID controller resources not available due to previous problems.
Page 430
Explanation: Incorrect disk configuration change has been detected. Go to Performing the checkout procedure. Response: 2506-9092 Explanation: Disk requires Format before use. Format the disk and retry the operation. Response: Power Systems: IBM Flex System p260 and p460 Compute Nodes Installation and Service Guide...
Page 431
2506-FF3D • 2506-FFFE 2506-FF3D Explanation: Temporary controller failure. Retry the operation. Response: Failing Item: v FFC_2506 2506-FFF3 Explanation: Disk media format bad. Reformat the disk and retry the operation. Response: 2506-FFF4 Explanation: Device problem. Perform diagnostics on the device and retry the operation. Response: Failing Item: v FFC_722...
Page 432
2D14-3109 Explanation: Controller timed out a device command. Use MAP3150 to determine resolution. Response: 2D14-3110 Explanation: Device bus interface error. Use MAP3150 to determine resolution. Response: Power Systems: IBM Flex System p260 and p460 Compute Nodes Installation and Service Guide...
Page 433
2D14-4010 • 2D14-4100 2D14-4010 Explanation: Configuration error, incorrect connection between cascaded enclosures. Use MAP3142 to determine resolution. Response: 2D14-4020 Explanation: Configuration error, connections exceed IOA design limits. Use MAP3143 to determine resolution. Response: 2D14-4030 Explanation: Configuration error, incorrect multipath connection. Use MAP3144 to determine resolution. Response: 2D14-4040 Explanation: Configuration error, incomplete multipath connection between controller and enclosure detected.
Page 434
Explanation: Temporary disk data error. Replace the system board (SAS controller). Response: Failing Item: v FFC_722 2D14-8150 Explanation: Controller failure. Replace the system board (SAS controller). Response: Failing Item: v FFC_2D14 Power Systems: IBM Flex System p260 and p460 Compute Nodes Installation and Service Guide...
Page 435
2D14-8157 • 2D14-9020 2D14-8157 Explanation: Temporary controller failure. Replace the system board (SAS controller). Response: Failing Item: v FFC_2D14 2D14-9000 Explanation: Controller detected device error during configuration discovery. Use MAP3190 to determine resolution. Response: 2D14-9001 Explanation: Controller detected device error during configuration discovery. Use MAP3190 to determine resolution. Response: 2D14-9002 Explanation: Controller detected device error during configuration discovery.
Page 436
Explanation: Previously degraded disk in Disk Array not found at required physical location. Use MAP3190 to determine resolution. Response: 2D14-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 p260 and p460 Compute Nodes Installation and Service Guide...
Page 437
2D14-9028 • 2D14-9050 2D14-9028 Explanation: Maximum number of functional Disk Arrays has been exceeded. Use MAP3190 to determine resolution. Response: 2D14-9029 Explanation: Maximum number of functional Disk Arrays disks has been exceeded. Use MAP3190 to determine resolution. Response: 2D14-9030 Explanation: Disk Array is degraded due to missing/failed disk. Use MAP3110 to determine resolution. Response: 2D14-9031 Explanation: Automatic reconstruction initiated for Disk Array.
Page 438
Explanation: Maximum number of functional Disk Arrays has been exceeded. Use MAP3190 to determine resolution. Response: 2D14-9073 Explanation: Multiple controllers connected in an invalid configuration. Use MAP3140 to determine resolution. Response: Power Systems: IBM Flex System p260 and p460 Compute Nodes Installation and Service Guide...
Page 439
2D14-9074 • 2D14-9092 2D14-9074 Explanation: Multiple controllers not capable of similar functions or controlling same set of devices. Use MAP3141 to determine resolution. Response: 2D14-9075 Explanation: Incomplete multipath connection between controller and remote controller. Use MAP3149 to determine resolution. Response: 2D14-9076 Explanation: Missing remote controller.
Page 440
Explanation: Temporary device bus error. Replace the FRU identified by diagnostics. Response: Failing Item: v FFC_722 2D14-FFFE Explanation: Temporary device bus error. Use MAP3150 to determine resolution. Response: Power Systems: IBM Flex System p260 and p460 Compute Nodes Installation and Service Guide...
Page 441
2D29-102E • 2D29-3110 2D29-102E Explanation: Reallocation failed due to disk out of alternate sectors. Replace the FRU identified by diagnostics. Response: Failing Item: v FFC_722 2D29-3002 Explanation: Addressed device failed to respond to selection. Replace the FRU identified by diagnostics. Response: Failing Item: v FFC_722...
Page 442
Response: 2D29-4060 Explanation: Multipath redundancy level got worse. Use MAP3153 to determine resolution. Response: 2D29-4100 Explanation: Device bus fabric error. Use MAP3152 to determine resolution. Response: Power Systems: IBM Flex System p260 and p460 Compute Nodes Installation and Service Guide...
Page 443
2D29-4101 • 2D29-8150 2D29-4101 Explanation: Temporary device bus fabric error. Use MAP3152 to determine resolution. Response: 2D29-4110 Explanation: Unsupported enclosure function detected. Use MAP3145 to determine resolution. Response: 2D29-4150 Explanation: PCI bus error detected by controller. Replace the PCIe x8 Internal 3Gb SAS Adapter. Response: Failing Item: v FFC_2D29...
Page 444
Explanation: Cache data belongs to disks other than those attached. Use MAP3190 to determine resolution. Response: 2D29-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 p260 and p460 Compute Nodes Installation and Service Guide...
Page 445
2D29-9021 • 2D29-9027 2D29-9021 Explanation: Two or more disks are missing from a RAID-5 or RAID 6 Disk Array. Use MAP3111 to determine resolution. Response: 2D29-9022 Explanation: Two or more disks are missing from a RAID-5 or RAID 6 Disk Array. Use MAP3111 to determine resolution.
Page 446
Explanation: Background Disk Array parity checking detected and corrected errors on specified disk. Use MAP3190 to determine resolution. Response: 2D29-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 p260 and p460 Compute Nodes Installation and Service Guide...
Page 447
2D29-9051 • 2D29-9073 2D29-9051 Explanation: Cache data exists for one or more missing/failed disks. Use MAP3132 to determine resolution. Response: 2D29-9052 Explanation: Cache data exists for one or more modified disks. Use MAP3190 to determine resolution. Response: 2D29-9054 Explanation: RAID controller resources not available due to previous problems. Use MAP3121 to determine resolution.
Page 448
Explanation: Incorrect disk configuration change has been detected. Use MAP3133 to determine resolution. Response: 2D29-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 p260 and p460 Compute Nodes Installation and Service Guide...
Page 449
2D29-FF3D • 2D29-FFFE 2D29-FF3D Explanation: Temporary controller failure. Retry the operation. Replace the PCIe x8 Internal 3Gb SAS Adapter. Response: Failing Item: v FFC_2D29 2D29-FFF3 Explanation: Disk media format bad. Reformat the disk and retry the operation. Use MAP3135 to determine resolution.
1. Some SRNs might have 4 digits rather than 3 digits after the dash (–). 2. The ssss before the dash (–) represents the 3 digit or 4 digit SCSD SRN. Power Systems: IBM Flex System p260 and p460 Compute Nodes Installation and Service Guide...
Page 451
SSSS-102 • SSSS-106 SSSS-102 Explanation: An unrecoverable media error occurred. 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 452
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 p260 and p460 Compute Nodes Installation and Service Guide...
Page 453
SSSS-116 • SSSS-120 SSSS-116 Explanation: A protocol error. 1. Make sure that the device, adapter and diagnostic firmware, and the application software levels are compatible. 2. If you do not find a problem, call your operating-system support person. Response: Failing Item: v FFC_SSSS SSSS-117 Explanation: A write-protect error occurred.
Page 454
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 FFC_SSSS v SOFTWARE Power Systems: IBM Flex System p260 and p460 Compute Nodes Installation and Service Guide...
Page 455
SSSS-129 • SSSS-134 SSSS-129 Explanation: Error log analysis indicates a SCSD bus 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.
Page 456
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 v FFC_252B Power Systems: IBM Flex System p260 and p460 Compute Nodes Installation and Service Guide...
Page 457
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: v FFC_SSSS SSSS-140 Explanation: Error log analysis indicates poor signal quality.
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 459
System-board and chassis assembly (power supply sensor failed) 25A0 System-board and chassis assembly 2627 IBM Flex System 2 port QDR InfiniBand adapter 2629 IBM Flex System 2 port QDR InfiniBand adapter (configuration problem) 2631 System-board and chassis assembly 268B 300 GB SAS small-form-factor disk drive 26B4...
Perform MAP 3121 in the Systems Hardware information center. MAP 3130: Perform MAP 3130 in the Systems Hardware information center. MAP 3131: Perform MAP 3131 in the Systems Hardware information center. MAP 3132: Power Systems: IBM Flex System p260 and p460 Compute Nodes Installation and Service Guide...
Page 461
Perform MAP 3132 in the Systems Hardware information center. MAP 3133: Perform MAP 3133 in the Systems Hardware information center. MAP 3134: Perform MAP 3134 in the Systems Hardware information center. MAP 3135: Perform MAP 3135 in the Systems Hardware information center. MAP 3140: Perform MAP 3140 in the Systems Hardware information center.
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.
For intermittent problems, check the management-module event log and “POST progress codes (checkpoints)” on page 233. 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 498.
Page 464
Select the resources to be tested and record any SRNs. Then go to “Service request numbers (SRNs)” on page 301. This ends the Linux procedure. For more information about installing and using all supported operating systems, search the IBM Support website. Power Systems: IBM Flex System p260 and p460 Compute Nodes Installation and Service Guide...
Verifying the partition configuration Perform this procedure if there is a configuration problem with the system or a logical partition. Procedure 1. Check the processor and memory allocations of the system or the partition. Processor or memory resources that fail during system startup could cause the startup problem in the partition. Make sure that the processor and memory have enough functioning resources in the system for all the partitions.
See the documentation that comes with your operating system for information about shutting down the operating system. Power Systems: IBM Flex System p260 and p460 Compute Nodes Installation and Service Guide...
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.
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.
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 p260 and p460 Compute Nodes,” on page 97 to determine which components are CRUs and which components are FRUs.
Page 470
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 p260 and p460 Compute Nodes,” on page 97 to determine which components are CRUs and which components are FRUs.
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 p260 and p460 Compute Nodes,” on page 97 to determine which components are CRUs and which components are FRUs.
Page 472
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 p260 and p460 Compute Nodes,” on page 97 to determine which components are CRUs and which components are FRUs.
Page 473
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 p260 and p460 Compute Nodes,” on page 97 to determine which components are CRUs and which components are FRUs.
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.
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 p260 and p460 Compute Nodes,” on page 97 to determine which components are CRUs and which components are FRUs.
Page 476
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 p260 and p460 Compute Nodes,” on page 97 to determine which components are CRUs and which components are FRUs.
Page 477
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 p260 and p460 Compute Nodes,” on page 97 to determine which components are CRUs and which components are FRUs.
Page 478
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 p260 and p460 Compute Nodes,” on page 97 to determine which components are CRUs and which components are FRUs.
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 p260 and p460 Compute Nodes,” on page 97 to determine which components are CRUs and which components are FRUs.
Page 480
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 p260 and p460 Compute Nodes,” on page 97 to determine which components are CRUs and which components are FRUs.
Page 481
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 p260 and p460 Compute Nodes,” on page 97 to determine which components are CRUs and which components are FRUs.
Page 482
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 p260 and p460 Compute Nodes,” on page 97 to determine which components are CRUs and which components are FRUs.
Page 483
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 p260 and p460 Compute Nodes,” on page 97 to determine which components are CRUs and which components are FRUs.
Page 484
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 p260 and p460 Compute Nodes,” on page 97 to determine which components are CRUs and which components are FRUs.
Page 485
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 p260 and p460 Compute Nodes,” on page 97 to determine which components are CRUs and which components are FRUs.
Page 486
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 p260 and p460 Compute Nodes,” on page 97 to determine which components are CRUs and which components are FRUs.
Page 487
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 p260 and p460 Compute Nodes,” on page 97 to determine which components are CRUs and which components are FRUs.
Page 488
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 p260 and p460 Compute Nodes,” on page 97 to determine which components are CRUs and which components are FRUs.
Page 489
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 p260 and p460 Compute Nodes,” on page 97 to determine which components are CRUs and which components are FRUs.
Page 490
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 p260 and p460 Compute Nodes,” on page 97 to determine which components are CRUs and which components are FRUs.
Page 491
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 p260 and p460 Compute Nodes,” on page 97 to determine which components are CRUs and which components are FRUs.
Page 492
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 p260 and p460 Compute Nodes,” on page 97 to determine which components are CRUs and which components are FRUs.
Page 493
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 p260 and p460 Compute Nodes,” on page 97 to determine which components are CRUs and which components are FRUs.
Page 494
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 p260 and p460 Compute Nodes,” on page 97 to determine which components are CRUs and which components are FRUs.
Page 495
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 p260 and p460 Compute Nodes,” on page 97 to determine which components are CRUs and which components are FRUs.
Page 496
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 p260 and p460 Compute Nodes,” on page 97 to determine which components are CRUs and which components are FRUs.
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 p260 and p460 Compute Nodes,” on page 97 to determine which components are CRUs and which components are FRUs.
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 499
Figure 47. LED locations on the system board of the IBM Flex System p260 Compute Node The following figure shows LEDs on the system board of the IBM Flex System p460 Compute Node. Figure 48. LED locations on the system board of the IBM Flex System p460 Compute Node The following table identifies the light path diagnostic LEDs.
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 p260 and p460 Compute Nodes,” on page 97 to determine which components are CRUs and which components are FRUs.
Page 501
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 p260 and p460 Compute Nodes,” on page 97 to determine which components are CRUs and which components are FRUs.
Page 502
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 p260 and p460 Compute Nodes,” on page 97 to determine which components are CRUs and which components are FRUs.
Page 503
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 p260 and p460 Compute Nodes,” on page 97 to determine which components are CRUs and which components are FRUs.
FC loc code:U78AF.001.startSN-P1-C35-L1-T1 Ports logged in 1 Flags a<LOGGED_IN,STRIP_MERGE> VFC client name fcs1 VFC client DRC:U9999.999.9999999-V4-C32-T1 In this example, the original serial number is represented as startSN. Power Systems: IBM Flex System p260 and p460 Compute Nodes Installation and Service Guide...
2. To save the location code information for each Fibre Channel adapter (fcs), enter the lsdev command as follows: lsdev -vpd | grep fcs | tee LSDEV_OUTPUT_before The output might look like the following example: fcs0 U78AF.001.startSN-P1-C35-L1-T1 Dual Port 8Gb FC Mezzanine Card (7710322577107501) fcs1 U78AF.001.startSN-P1-C35-L1-T2 Dual Port 8Gb FC Mezzanine Card (7710322577107501) In this example, the original serial number is represented as startSN.
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. Power Systems: IBM Flex System p260 and p460 Compute Nodes Installation and Service Guide...
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. Recovering the TEMP image from the PERM image To recover the TEMP image from the PERM image, you must perform the reject function. The reject function copies the PERM image into the TEMP image.
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.
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.
Compute Node, you must determine whether the problem is in the compute node or in the 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. For more information, see the following documentation: –...
Page 511
3. Turn off the compute node. 4. Remove the compute node from the IBM Flex System Enterprise Chassis, and remove the cover. 5. Remove or disconnect the following devices, one at a time, until you find the failure. Reinstall, turn on, and reconfigure the compute node each time.
Page 512
Power Systems: IBM Flex System p260 and p460 Compute Nodes Installation and Service Guide...
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.
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 516
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 p260 and p460 Compute Nodes Installation and Service Guide...
Page 517
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 518
IBM-Allee 1, 71139 Ehningen, Germany Tel: +49 7032 15 2941 email: lugi@de.ibm.com Generelle Informationen: Das Gerät erfüllt die Schutzanforderungen nach EN 55024 und EN 55022 Klasse A. Power Systems: IBM Flex System p260 and p460 Compute Nodes Installation and Service Guide...
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 520
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 521
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.
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.
Need help?
Do you have a question about the Flex System p260 and is the answer not in the manual?
Questions and answers