Page 1 Power Systems IBM Flex System p270 Compute Node Installation and Service Guide...
Page 3 Power Systems IBM Flex System p270 Compute Node Installation and Service Guide...
Page 4 Before using this information and the product it supports, read the information in “Safety notices” on page v, “Notices,” on page 487, the IBM Systems Safety Notices manual, G229-9054, and the IBM Environmental Notices and User Guide, Z125–5823. This edition applies to IBM Power Systems servers that contain the POWER7 processor and to all associated models.
Page 5: Table Of Contents
Installing a SATA solid-state drive . . 43 Notices and statements . Removing a DIMM . . 44 Features and specifications of the IBM Flex System Installing a DIMM . . 47 p270 Compute Node. Supported DIMMs . . 48 What your compute node offers .
Page 6 . 444 Class B Notices . . 493 Starting stand-alone diagnostics from a NIM Terms and conditions. . 496 server . . 445 Using the diagnostics program . 446 Power Systems: IBM Flex System p270 Compute Node Installation and Service Guide...
Page 7: Safety Notices
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 p270 Compute Node Installation and Service Guide...
Page 11 (L003) All lasers are certified in the U.S. to conform to the requirements of DHHS 21 CFR Subchapter J for class 1 laser products. Outside the U.S., they are certified to be in compliance with IEC 60825 as a class 1 laser product.
Page 12 Exchange only with the IBM-approved part. Recycle or discard the battery as instructed by local regulations. In the United States, IBM has a process for the collection of this battery. For information, call 1-800-426-4333. Have the IBM part number for the battery unit available when you call. (C003)
Page 13: Chapter 1. Introduction
IBM Flex System Enterprise Chassis units to provide a high-density, high-performance compute-node environment with advanced processing technology. The Installation and User's Guide includes the compute node information on the IBM Flex System Enterprise Chassis Documentation CD. All of the following information is in the document and also in the information...
Page 14 IBM Flex System Enterprise Chassis. A set of blank labels comes with the compute node. When you install the compute node in the IBM Flex System Enterprise Chassis, write identifying information on a label and place the label on the bezel. See the documentation for your IBM Flex System Enterprise Chassis for the location of the label placement.
Page 15: Related Documentation
Related documentation Documentation for the IBM Flex System p270 Compute Node includes PDF files on the IBM Flex System Enterprise Chassis Documentation CD and in the information center. The most recent version of all IBM Flex System Enterprise Chassis documentation is in the IBM Flex System Information Center.
Page 16: Ibm Documentation Cd
Review the IBM Flex System Information Center or the Planning Guide and the Installation Guide for your IBM Flex System Enterprise Chassis. The information can help you prepare for system installation and configuration.
Page 17: Notices And Statements
A DANGER statement is placed just before the description of a potentially lethal or extremely hazardous procedural step or situation. Features and specifications of the IBM Flex System p270 Compute Node Features and specifications of the IBM Flex System p270 Compute Node are summarized in this overview. Chapter 1. Introduction...
Page 18 The IBM Flex System p270 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.
Page 19: What Your Compute Node Offers
The compute node uses the following features and technologies: v Service processor The service processor for the IBM Flex System p270 Compute Node provides support for the following functions: – Intelligent Platform Management Interface (IPMI) – The operating system –...
Page 20 Large system memory capacity The memory bus in the IBM Flex System p270 Compute Node supports up to 512 GB of system memory. For the official list of supported dual-inline memory modules (DIMMs), see http://www.ibm.com/systems/info/x86servers/serverproven/compat/us/ (http://www.ibm.com/...
Page 21: Chapter 2. Power, Controls, Indicators, And Connectors
3. Check log LED: When this amber LED is lit, it indicates that an error for the compute node has been detected that must be addressed by the user. See the error log repository to further investigate this serviceable event. The LED can be turned off through the management console. © Copyright IBM Corp. 2013, 2015...
Page 22: Turning On The Compute Node
Start the compute node automatically when power is restored after a power failure. If a power failure occurs, the IBM Flex System Enterprise Chassis and then the compute node can start automatically when power is restored. You must configure the compute node to restart through the management module.
Page 23: Turning Off The Compute Node
Turning off the compute node When you turn off the compute node, it is still connected to power through the IBM Flex System Enterprise Chassis. The compute node can respond to requests from the service processor, such as a remote request to turn on the compute node. To remove all power from the compute node, you must remove it from the IBM Flex System Enterprise Chassis.
Page 24: System-Board Connectors
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 p270 Compute Node. Figure 2. System-board connectors for the IBM Flex System p270 Compute Node The following table identifies and describes the connectors for the IBM Flex System p270 Compute Node.
Page 25: System-Board Leds
Use the following figure to identify the failing component. The following figure shows LEDs on the IBM Flex System p270 Compute Node. Figure 4. LED locations on the system board of the IBM Flex System p270 Compute Node The following table identifies the light path diagnostic LEDs.
Page 26: Input/Output Connectors And Devices
Microprocessor LEDs Input/output connectors and devices The input/output connectors that are available to the compute node are supplied by the IBM Flex System Enterprise Chassis. See the documentation that comes with the IBM Flex System Enterprise Chassis for information about the input/output connectors.
Page 27: Chapter 3. Configuring The Compute Node
Use the management module to change the boot list to determine which firmware image to boot, and to perform other configuration tasks. Related tasks: “Using the SMS utility” on page 18 Use the System Management Services (SMS) utility to configure the IBM Flex System p270 Compute Node. © Copyright IBM Corp. 2013, 2015...
Page 28: Updating The Firmware
Updating the firmware IBM periodically makes firmware updates available for you to install on the compute node, on the management module, or on the 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 29 1. Download the IBM Flex System p270 Compute Node one-bay firmware. a. Go to http://www.ibm.com/software/brandcatalog/puresystems/centre/update. b. Select the update group that matches the IBM Flex System version to which you want to update. For example, select the Flex System 1.2.1 tab.
Page 30: Starting The Temp Image
F3 again to exit the diagnostic program. Using the SMS utility Use the System Management Services (SMS) utility to configure the IBM Flex System p270 Compute Node. Power Systems: IBM Flex System p270 Compute Node Installation and Service Guide...
Page 31: Starting The Sms Utility
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.
Page 32: Configuring Processor Cores
Learn how to increase or decrease the number of active processor cores in the compute node. You can order your IBM Flex System p270 Compute Node with a feature that instructs the factory to reduce the number of active processor cores in the compute node to reduce software licensing costs. The factory uses the field core override option to reduce the number of processor cores when feature code 2319: Factory deconfiguration of one core is ordered with a new system.
Page 33: Mac Addresses For Integrated Ethernet Controllers
MAC addresses for integrated Ethernet controllers Two integrated Ethernet ports are used by the service processor on the IBM Flex System p270 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).
Page 34 Disk drives and solid-state drives in the IBM Flex System p270 Compute Node can be used to implement and manage various types of RAID arrays in operating systems that are on the ServerProven list. For the compute node, you must configure the RAID array through the smit sasdam utility, which is the SAS RAID Disk Array Manager for the AIX operating system.
Page 35: Chapter 4. Installing The Operating System
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. After installing VIOS, you can install the AIX, Linux, or IBM i operating system as a client operating system in a logical partition (LPAR).
Page 36 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.
Page 37: Installing Service And Productivity Tools For Linux
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 p270 Compute Node firmware.
Page 38 Power Systems: IBM Flex System p270 Compute Node Installation and Service Guide...
Page 39: Chapter 5. Accessing The Service Processor
To access 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 40 Power Systems: IBM Flex System p270 Compute Node Installation and Service Guide...
Page 41: Chapter 6. Installing And Removing Components
Back up all important data before you make changes to disk drives. v Before you remove a hot-swap compute node from the IBM Flex System Enterprise Chassis, you must shut down the operating system and turn off the compute node. You do not have to shut down the IBM Flex System Enterprise Chassis itself.
Page 42: System Reliability Guidelines
Do not leave the device where others can handle and damage it. v While the device is still in its static-protective package, touch it to an unpainted metal part of the IBM Flex System Enterprise Chassis or any unpainted metal surface on any other grounded rack component in the rack that you are installing the device in for at least 2 seconds.
Page 43: Removing The Compute Node From An Ibm Flex System Enterprise Chassis
Figure 5. Removing the compute node from the IBM Flex System Enterprise Chassis Attention: v To maintain proper system cooling, do not operate the IBM Flex System Enterprise Chassis without a compute node, expansion unit, or compute node filler installed in each bay.
Page 44: Reseating The Compute Node In A Chassis
To perform a virtual reseat by using the IBM Chassis Management Module (CMM), go to http://pic.dhe.ibm.com/infocenter/flexsys/information/topic/com.ibm.acc.8731.doc/ unmanaging_chassis.html. To perform a virtual reseat by using the IBM Flex System Manager (FSM), go to http:// pic.dhe.ibm.com/infocenter/flexsys/information/topic/com.ibm.acc.8731.doc/ unmanaging_chassis.html. 2. Is the problem resolved? Yes: This ends the procedure.
Page 45: Removing The Compute Node Cover
About this task If IBM installs a tier 1 CRU at your request, you will be charged for the installation. The illustrations in this documentation might differ slightly from your hardware. Removing the compute node cover Remove the compute node from the chassis unit and press the compute node cover releases to open and remove the compute node cover.
Page 46: Installing And Closing The Compute Node Cover
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 47 Figure 7. Installing the cover for an IBM Flex System p270 Compute Node Statement 21 CAUTION: Hazardous energy is present when the compute node is connected to the power source. Always replace the compute node cover before you install the compute node.
Page 48: Removing A Sas Hard Disk Drive
4. 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 92. Removing a SAS hard disk drive If the serial-attached SCSI (SAS) hard disk drive is damaged or in need of replacing, you can remove it from the compute node.
Page 49: Installing A Sas Hard Disk Drive
Figure 9. Installing a hard disk drive All drive connectors are from the same controller. The IBM Flex System p270 Compute Node can be used to implement RAID functions. See “Configuring a RAID array” on page 21 for information about RAID configuration.
Page 50: Removing A Solid-State Drive Carrier
Hazardous energy is present when the compute node is connected to the power source. Always replace the compute node cover before you install 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 92.
Page 51 3. Shut down the operating system on all partitions of the compute node, turn off the compute node, and remove the compute node from the IBM Flex System Enterprise Chassis. See “Removing the compute node from an IBM Flex System Enterprise Chassis” on page 31.
Page 52: Installing A Solid-State Drive Carrier
About this task Figure 11 shows how to install the disk drive. Figure 11. Installing an SSD carrier To install an SSD carrier, complete the following steps: Procedure Power Systems: IBM Flex System p270 Compute Node Installation and Service Guide...
Page 53 Hazardous energy is present when the compute node is connected to the power source. Always replace the compute node cover before you install 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 92.
Page 54: Removing A Sata Solid-State Drive
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 31.
Page 55: Installing A Sata Solid-State Drive
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 31.
Page 56: Removing A Dimm
Removing a DIMM Very low profile (VLP) and low profile (LP) dual-inline memory modules (DIMMs) are tier 1 CRUs. You can remove them yourself. If IBM removes a tier 1 CRU at your request, you will be charged for the removal.
Page 57 Figure 14. DIMM connectors for the IBM Flex System p270 Compute Node Attention: To avoid breaking the DIMM retaining clips or damaging the DIMM connectors, open and close the clips gently. 6. Are you removing DIMM 16 on an IBM Flex System p270 Compute Node? Yes: Continue with the next step.
Page 58 Hazardous energy is present when the compute node is connected to the power source. Always replace the compute node cover before installing the compute node. 12. Install the compute node into the IBM Flex System Enterprise Chassis. See “Installing the compute node in an IBM Flex System Enterprise Chassis” on page 92.
Page 59: Installing A Dimm
Installing a DIMM Very low profile (VLP) and low profile (LP) dual-inline memory modules (DIMMs) are tier 1 CRUs. You can install them yourself. If IBM installs a tier 1 CRU at your request, you will be charged for the installation.
Page 60: Supported Dimms
Supported DIMMs Your compute node contains connectors for registered dual inline memory modules (RDIMMs). The system board in the IBM Flex System p270 Compute Node contains connectors for 16 low profile (LP) or very low profile (VLP) memory DIMMs. The maximum size for a single DIMM is 8 GB for a VLP DIMM and 32 GB for an LP DIMM. The maximum memory capacity for an IBM Flex System p270 Compute Node is 512 GB.
Page 61: Removing An I/O Expansion Adapter
Table 5. Memory module combinations for the IBM Flex System p270 Compute Node (continued) DIMM slots for the IBM Flex System p270 Compute Node DIMM count Figure 18. DIMM connectors for the IBM Flex System p270 Compute Node Related reference: Chapter 7, “Parts listing for IBM Flex System p270 Compute Node,”...
Page 62 3. Carefully lay the compute node on a flat, static-protective surface, with the cover side up. 4. Open and remove the compute node cover. See “Removing the compute node cover” on page 33. 5. Are you removing an I/O expansion ETE adapter (location Un-P1-C20) on an IBM Flex System p270 Compute Node? v Yes: Continue with the next step.
Page 63 Figure 20. Removing an I/O expansion ETE adapter from its connector 8. Pull the slot’s two blue release tabs open, as indicated in Figure 21. Then, lift the I/O expansion adapter up and away from its connector and out of the compute node. Figure 21.
Page 64: Installing An I/O Expansion Adapter
3. Open and remove the compute node cover. See “Removing the compute node cover” on page 33. 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.
Page 65 7. To install an I/O expansion ETE adapter, you must first remove the I/O expansion adapter 2 if it is present. The I/O expansion adapter 2 is at location Un-P1-C19 on an IBM Flex System p270 Compute Node. Pull the slot’s two blue release tabs open, as indicated in Figure 22. Then, lift the adapter up and away from its connector and out of the compute node.
Page 66 Press down gently until the adapter is firmly seated. d. Lock the adapter in place by moving the slot’s two blue release tabs into the closed position. Power Systems: IBM Flex System p270 Compute Node Installation and Service Guide...
Page 67 Hazardous energy is present when the compute node is connected to the power source. Always replace the compute node cover before you install 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 92.
Page 68: Removing The Battery
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 31.
Page 69 Statement 2: CAUTION: When replacing the lithium battery, use only IBM Part Number 33F8354 or an equivalent type battery recommended by the manufacturer. If your system has a module containing a lithium battery, replace it only with the same module type made by the same manufacturer. The battery contains lithium and can explode if not properly used, handled, or disposed of.
Page 70: Removing And Replacing Tier 2 Crus
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 71 IBM Flex System Enterprise Chassis at this time. 4. Access the Advanced System Management Interface (ASMI). If you are already connected to the ASMI, go to the step 5. v 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 72: Installing The Management Card
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 73 3. Touch the static-protective package that contains the management card to any unpainted metal surface on the IBM Flex System Enterprise Chassis or any unpainted metal surface on any other grounded rack component, and then remove the management card from its package.
Page 74 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 92. Power on the compute node. If a Virtual I/O Server (VIOS) partition is installed, power on only the VIOS partition.
Page 75: Obtaining A Powervm Virtualization Engine System Technologies Activation Code
By using Advanced System Management Interface (ASMI): a. Access the ASMI. If you are already connected to the ASMI, go to step 2c. 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 76 The following is an example of the lsvet command output: Note: When you request the activation code, you must supply the information that is emphasized in the following example. sys_type=7895,sys_serial_num=12-34567,anchor_card_ccin=52EF, anchor_card_serial_num=01-231S000, anchor_card_unique_id=30250812077C3228, resource_id=CA1F,activated_resources=0000,sequence_num=0040, entry_check=EC Power Systems: IBM Flex System p270 Compute Node Installation and Service Guide...
Page 77 VET activation code. 5. Enter the VET activation code to activate PowerVM virtualization through one of the following methods: v For ASMI, HMC, or IVM graphical user interface (GUI), see http://www.ibm.com/support/entry/ portal/docdisplay?lndocid=MIGR-5091991. v For FSM, see http://www.ibm.com/support/entry/portal/docdisplay?lndocid=MIGR-5091991. v For IVM command-line interface (CLI), complete the following steps: a.
Page 78: Removing The Light Path Diagnostics Panel
Removing the light path diagnostics panel You can remove this tier 2 CRU, or you can request IBM to remove it, at no additional charge, under the type of warranty service that is designated for the compute node. Remove the light path diagnostics panel to replace the panel or to reuse the panel in a new system-board and chassis assembly.
Page 79: Installing The Light Path Diagnostics Panel
Installing the light path diagnostics panel You can install this tier 2 CRU, or you can request IBM to install it, at no additional charge, under the type of warranty service that is designated for the compute node. Use this procedure to install the light path diagnostics panel into the currently installed system board.
Page 80 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 31.
Page 81: Removing And Replacing Frus (Trained Service Technician Only)
Hazardous energy is present when the compute node is connected to the power source. Always replace the compute node cover before you install 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 92.
Page 82 Note: If you plan to remove dust or debris from the heat sink, this operation must be performed in another room that is greater than 7.62 m (25 ft) away from the work area. Power Systems: IBM Flex System p270 Compute Node Installation and Service Guide...
Page 83 Figure 32. Loosening the heat-sink actuation screw Figure 33. Removing the heat sink Chapter 6. Installing and removing components...
Page 84 Figure 35 on page 73. b. Lower the tool over the microprocessor by ensuring that the two guide pins (B) are inserted into the alignment holes on each side of the tool. Power Systems: IBM Flex System p270 Compute Node Installation and Service Guide...
Page 85 Figure 35. Preparing the microprocessor for removal c. With the removal tool (A) sitting on top of the microprocessor, push down on the tool to lock the microprocessor into the tool, as shown in Figure 36 on page 74. Note: The tool drops slightly when you push down so that the jaws can grab the bottom of the microprocessor.
Page 86 Figure 37. Placing the tool at an angle on the top cover of the packaging Power Systems: IBM Flex System p270 Compute Node Installation and Service Guide...
Page 87: Installing A Microprocessor And Heat Sink
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 31.
Page 88 Figure 39. Then push down on the tool to lock the microprocessor into the tool, as shown in Figure 40 on page 77. Figure 39. Preparing for microprocessor installation Power Systems: IBM Flex System p270 Compute Node Installation and Service Guide...
Page 89 Figure 40. Locking the microprocessor into the tool 6. Prepare for microprocessor installation: a. Grasping the sides of the tool and microprocessor, carefully lift it slightly out of the microprocessor tray. Then turn it over so that the microprocessor side is up. b.
Page 90 After the tool and microprocessor holes and guide pins are properly aligned, squeeze and hold the two tool tabs (A) together until a firm stop is reached. Then lift the tool off the microprocessor, as shown in Figure 42 on page 79. Power Systems: IBM Flex System p270 Compute Node Installation and Service Guide...
Page 91 TIM is optional and is only performed if the TIM is damaged. Do not reuse the removed heat sink if the TIM is damaged. Either discard the heat sink and the damaged TIM locally or return them to IBM based on the part-order-form part status. Figure 43. Inspecting the thermal interface material...
Page 92 Ensure that the heat-sink load arm is engaged. Note: If the load arm is not engaged, you must manually engage the load arm onto the heat sink while the load screw is being tightened. Power Systems: IBM Flex System p270 Compute Node Installation and Service Guide...
Page 93 Figure 45. Installing the heat sink 12. Secure the heat sink: a. Upon placing the heat sink on the microprocessor, ensure that the heat-sink load arm on the side of the heat sink becomes engaged, as shown in Figure 46 on page 82. b.
Page 94 Align the beveled corner of the module (A) to the corner of the packaging with triangle (B) and place it in the packaging, as shown in Figure 47. Close the packaging cover. Figure 47. Placing the microprocessor into the packaging Power Systems: IBM Flex System p270 Compute Node Installation and Service Guide...
Page 95: Replacing The System-Board And Chassis Assembly
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 96 Record any static addresses that are displayed in the IPv6 property tab. For more information about displaying the IP configuration of a compute node, see Chassis management options (http://pic.dhe.ibm.com/infocenter/flexsys/information/topic/com.ibm.acc.cmm.doc/ cmm_ui_chassis_management.html). Power Systems: IBM Flex System p270 Compute Node Installation and Service Guide...
Page 97 9. Have the customer shut down the operating system on all partitions of the compute node, and turn off the compute node. 10. 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 31.
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 89 or 27 on page 89 of this procedure, depending upon whether the compute node is managed by a management console.
Page 100 If the NTP mode is not set and the time is not correct in UTC, enter the correct time and save. This operation can be completed only when the compute node is turned off. Power Systems: IBM Flex System p270 Compute Node Installation and Service Guide...
Page 101 If the compute node is still not displayed, reseat the compute node. See Removing the compute node from an IBM Flex System Enterprise Chassis (http://pic.dhe.ibm.com/infocenter/ flexsys/information/topic/com.ibm.acc.7895.doc/removing_the_blade_server.html). Once the FSM discovers the compute node, collect inventory on the chassis, and then request access again.
Page 102: Completing The Installation
Click Save Settings and continue system server firmware boot. 30. Have the customer activate a VIOS partition by using one of the following methods: a. If this system is managed by an FSM, see Activating a virtual server (http://pic.dhe.ibm.com/ infocenter/flexsys/information/topic/com.ibm.acc.psm.resources.doc/vs/sdmc_vs- activating_vs.html).
Page 103: Installing And Closing The Compute Node Cover
SMS utility” on page 18. 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 104: Installing The Compute Node In An Ibm Flex System Enterprise Chassis
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 105 Important: Do not place the label on the compute node or in any way block the ventilation holes on the compute node. See the online information or the documentation that comes with your IBM Flex System Enterprise Chassis for information about label placement.
Page 106 You might also have to install the compute node operating system. See Chapter 4, “Installing the operating system,” on page 23 for detailed information about these tasks. Power Systems: IBM Flex System p270 Compute Node Installation and Service Guide...
Page 107: Chapter 7. Parts Listing For Ibm Flex System P270 Compute Node
1 CRU at your request, you will be charged for the installation. v Tier 2 customer replaceable unit: You may install a tier 2 CRU yourself or request IBM to install it, at no additional charge, under the type of warranty service that is designated for your compute node.
Page 108 IBM Flex System 2-port QDR InfiniBand adapter 90Y3461 2627 IBM Flex System 2-port 8 Gb Fibre Channel adapter 69Y1941 2E16 IBM Flex System 4-port 10 Gb Ethernet adapter 81Y3125 2E37 Power Systems: IBM Flex System p270 Compute Node Installation and Service Guide...
Page 109 Miscellaneous parts kit (network adapter retention) 94Y4866 *The microprocessor removal tool is included with the system-board and chassis assembly FRU and microprocessor parts kit FRUs. The microprocessor removal tool cannot be ordered independently. Chapter 7. Parts listing for IBM Flex System p270 Compute Node...
Page 110 Power Systems: IBM Flex System p270 Compute Node Installation and Service Guide...
Page 111: Chapter 8. Troubleshooting
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 112 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.
Page 113: Diagnostics
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 114 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.
Page 115: Collecting Dump Data
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 116 See “System-board connectors” on page 12 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 473 to identify the failing component when there is a hang condition.
Page 117 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 9. Mapping network adapter ports to IBM Flex System Enterprise Chassis I/O bays for the IBM Flex System p270 Compute Node IBM Flex IBM Flex...
Page 118: Reference Codes
Table 9. Mapping network adapter ports to IBM Flex System Enterprise Chassis I/O bays for the IBM Flex System p270 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 119: System Reference Codes (Srcs)
The IBM Flex System p270 Compute Node does not display checkpoints or error codes on the remote console. If the POST detects a problem, a 9-word, 8-digit error code is logged in the IBM Flex System Enterprise Chassis management-module event log. A location code that identifies a component might also be included.
Page 120: 1Xxxyyyy Srcs
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 p270 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 121 110000AC • 11002610 110000AC Explanation: The 110000AC SRC indicates your compute node lost ac power. This procedure will help you determine the source of the power loss condition that brought you here. If the system or expansion unit that exhibited the power loss starts normally, or stays powered on after an ac power failure, replacement of parts might not be needed.
Page 122 If a firmware update is needed, see Updating the firmware 2. Replace the system board. If there is more than one system board, use the location code in the SRC to identify which system board to replace. Power Systems: IBM Flex System p270 Compute Node Installation and Service Guide...
Page 123 1100262D • 11002632 1100262D Explanation: 3.3V reg_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 124 If a firmware update is needed, see Updating the firmware 2. Replace the system board. If there is more than one system board, use the location code in the SRC to identify which system board to replace. Power Systems: IBM Flex System p270 Compute Node Installation and Service Guide...
Page 125 1100265A • 11002673 1100265A Explanation: 1.2VA 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 126 If a firmware update is needed, see Updating the firmware 2. Replace the system board. If there is more than one system board, use the location code in the SRC to identify which system board to replace. Power Systems: IBM Flex System p270 Compute Node Installation and Service Guide...
Page 127 1100267A • 1100267D 1100267A Explanation: CFFh expansion card A0_pGood fault. Response: Perform the DTRCARD symbolic CRU isolation procedure by completing the following steps: 1. Reseat the PCIe expansion card. 2. If the problem persists, replace the expansion card. 3. If the problem persists: Search RETAIN tips and the firmware change history for the reference code to determine the recommended actions.
Page 128 2. On a double-wide server, replace the following, one at a time, until the failure is no longer detected: a. The SSD interposer card on the expansion planar b. The first SSD drive on the expansion planar c. The second SSD drive on the expansion planar Power Systems: IBM Flex System p270 Compute Node Installation and Service Guide...
Page 129 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 130 If a firmware update is needed, see Updating the firmware 2. Replace the system board. If there is more than one system board, use the location code in the SRC to identify which system board to replace. Power Systems: IBM Flex System p270 Compute Node Installation and Service Guide...
Page 131: 6Xxxyyyy Srcs
If an action solves the problem, then you can stop performing the remaining actions. See Chapter 7, “Parts listing for IBM Flex System p270 Compute Node,” on page 95 to determine which components are CRUs and which components are FRUs.
Page 132 Explanation: A non-recoverable error was detected while reading a virtual optical volume. Service action / serviceable event: Yes Called home automatically: No Problem determination: Resolve any errors on the Network File System server. Power Systems: IBM Flex System p270 Compute Node Installation and Service Guide...
Page 133 632BCFC6 • 632CC002 632BCFC6 Explanation: Virtual optical device error. The file specified does not contain data that can be processed as a virtual optical volume. Service action / serviceable event: Yes Called home automatically: No Problem determination: On the Network File System server, verify that all the files specified in the list of optical volumes are correct.
Page 134 Explanation: Virtual optical device error. Media or device error 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 p270 Compute Node Installation and Service Guide...
Page 135 632CC301 • 632CC400 632CC301 Explanation: Virtual optical device error. Media or device error occurred. Service action / serviceable event: No Called home automatically: No Problem determination: Refer to the hosting partition for problem analysis. 632CC302 Explanation: Virtual optical device error. Media or device error occurred. Service action / serviceable event: No Called home automatically: No Problem determination: Refer to the hosting partition for problem analysis.
Page 136 Response: No corrective action is required. 632CCFFE Explanation: Informational system log entry only. Service action / serviceable event: No Called home automatically: No Response: No corrective action is required. Power Systems: IBM Flex System p270 Compute Node Installation and Service Guide...
Page 137: A1Xxyyyy Service Processor Srcs
If an action solves the problem, you can stop performing the remaining actions. See Chapter 7, “Parts listing for IBM Flex System p270 Compute Node,” on page 95 to determine which components are CRUs and which components are FRUs.
Page 138: A6Xxyyyy Licensed Internal Code Or Hardware Event Srcs
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 p270 Compute Node Installation and Service Guide...
Page 139 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 140 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 p270 Compute Node Installation and Service Guide...
Page 141: A7Xxyyyy Licensed Internal Code Srcs
Explanation: A problem occurred when initializing, reading, or using system VPD. Response: Replace the management card, as described in Removing the management card and Installing the management card. A7004721 Explanation: The World Wide Port Name (WWPN) Prefix is not valid. Response: Refer to https://www-912.ibm.com/supporthome.nsf/document/51455410 Chapter 8. Troubleshooting...
Page 142 Response: The management interfaces have been used to set AMM to "ON" for the system. However, at IPL time, the system does not have a valid license for AMM. The customer needs to contact IBM or a Partner Sales representative to purchase and enter an Activation Code for this feature. If this is not possible, then turn off the system;...
Page 143: Aaxxyyyy Partition Firmware Attention Codes
If an action solves the problem, then you can stop performing the remaining actions. See Chapter 7, “Parts listing for IBM Flex System p270 Compute Node,” on page 95 to determine which components are CRUs and which components are FRUs.
Page 144 For a Linux operating system, boot the server using the stand-alone diagnostics CD or a NIM server; then, run diagnostics against the failing adapter. Power Systems: IBM Flex System p270 Compute Node Installation and Service Guide...
Page 145 AA060011 • AA190001 AA060011 Explanation: The firmware did not find an operating system image and at least one hard disk in the boot list was not detected by the firmware. The firmware is retrying the entries in the boot list. Response: This might occur if a disk enclosure that contains the boot disk is not fully initialized or if the boot disk belongs to another partition.
Page 146: B1Xxyyyy Service Processor Srcs
A B1xxyyyy system reference code (SRC) is an error code that is related to an event or exception that occurred in the service processor firmware. To find a description of an SRC that is not listed in this IBM Flex System p270 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 147 B15611B1 • B1817203 B15611B1 Explanation: The service processor could not communicate with the Chassis Management Module. Response: Go to Reseating the compute node in a chassis. B15611B9 Explanation: The service processor could not communicate with the Chassis Management Module. Response: Go to Reseating the compute node in a chassis. B15611BA Explanation: The service processor could not communicate with the Chassis Management Module.
Page 148 3. Perform a firmware update. See Updating the firmware. If these actions do not resolve the problem, contact your next level of support. Reseating the compute node in a chassis Power Systems: IBM Flex System p270 Compute Node Installation and Service Guide...
Page 149: B2Xxyyyy Logical Partition Srcs
If an action solves the problem, then you can stop performing the remaining actions. See Chapter 7, “Parts listing for IBM Flex System p270 Compute Node,” on page 95 to determine which components are CRUs and which components are FRUs.
Page 150 Explanation: A problem occurred during the migration of a partition. The migration of a partition did not complete. Response: Check for server firmware updates; then, install the updates if available. Power Systems: IBM Flex System p270 Compute Node Installation and Service Guide...
Page 151 B2001144 • B2001230 B2001144 Explanation: A problem occurred during the migration of a partition. The migration of a partition did not complete. Response: Check for server firmware updates; then, install the updates if available. B2001148 Explanation: A problem occurred during the migration of a partition. The migration of a partition did not complete.
Page 152 No default load source was selected. The startup will attempt to continue, but there may not be enough information to find the correct load source. Response: Configure a load source for the partition. Then restart the partition. Power Systems: IBM Flex System p270 Compute Node Installation and Service Guide...
Page 153 B2001321 • B2002250 B2001321 Explanation: A problem occurred during the startup of a partition. Response: Verify that the correct slot is specified for the load source. Then restart the partition. B2001322 Explanation: In the partition startup, code failed during a check of the load source path. Response: Verify that the path for the load source is specified correctly.
Page 154 Response: Check for server firmware updates; then, install the updates if available. B2002485 Explanation: During the startup of a partition, the partition firmware attempted an operation that failed. Response: Go to Isolating firmware problems. Power Systems: IBM Flex System p270 Compute Node Installation and Service Guide...
Page 155 B2003000 • B2003113 B2003000 Explanation: Informational system log entry only. Response: No corrective action is required. B2003081 Explanation: During the startup of a partition, the startup did not complete due to a copy error. Response: Check for server firmware updates; then, install the updates if available. B2003084 Explanation: A problem occurred during the startup of a partition.
Page 156 Explanation: A problem occurred during the startup of a partition. This is a configuration problem in the partition. Response: Reconfigure the partition to include the intended load source path. Power Systems: IBM Flex System p270 Compute Node Installation and Service Guide...
Page 157 B2003141 • B2004400 B2003141 Explanation: Informational system log entry only. Response: No corrective action is required. B2003142 Explanation: Informational system log entry only. Response: No corrective action is required. B2003143 Explanation: Informational system log entry only. Response: No corrective action is required. B2003144 Explanation: Informational system log entry only.
Page 158 34 to retry the current Main Store Dump startup while the partition is still in the failed state. B2005122 Explanation: Informational system log entry only. Response: No corrective action is required. Power Systems: IBM Flex System p270 Compute Node Installation and Service Guide...
Page 159 B2005123 • B2005149 B2005123 Explanation: Informational system log entry only. Response: No corrective action is required. B2005127 Explanation: Timeout occurred during a main store dump IPL. Response: There was not enough memory available for the dump to complete before the timeout occurred. Retry the main store dump IPL, or else power on the partition normally.
Page 160 The firmware resource and all associated virtual and/or physical devices will not be available until the issue is resolved. Response: Collect a platform dump and then go to Isolating firmware problems. Power Systems: IBM Flex System p270 Compute Node Installation and Service Guide...
Page 161 Explanation: During the IPL of the partition, an error was detected while trying to setup the partition for firmware use. The IPL of the partition will not continue. Response: Contact IBM support. B2006009 Explanation: An active memory sharing partition is attempting to use a paging space device for which it does not have ownership.
Page 162 Explanation: During the startup of a partition, an internal firmware time-out occurred; the partition might continue to start up but it can experience problems while running. Response: Check for server firmware updates; then, install the updates if available. Power Systems: IBM Flex System p270 Compute Node Installation and Service Guide...
Page 163 B2008105 • B2008114 B2008105 Explanation: During the startup of a partition, there was a failure loading the VPD areas of the partition; the load source media has been corrupted or is unsupported on this server. Response: Check for server firmware updates; then, install the updates if available. B2008106 Explanation: A problem occurred during the startup of a partition.
Page 164 Explanation: During the startup of a partition, the partition did not start up due to a system firmware error. Response: Go to Isolating firmware problems. B200813A Explanation: There was a problem establishing a console. Response: Go to Isolating firmware problems. Power Systems: IBM Flex System p270 Compute Node Installation and Service Guide...
Page 165 B2008140 • B2008151 B2008140 Explanation: Informational system log entry only. Response: No corrective action is required. B2008141 Explanation: Informational system log entry only. Response: No corrective action is required. B2008142 Explanation: Informational system log entry only. Response: No corrective action is required. B2008143 Explanation: Informational system log entry only.
Page 166 Response: Evaluate the entire LPAR configuration. Adjust partition profiles with the new number of processors available in the system. B200B07B Explanation: Informational system log entry only. Response: No corrective action is required. Power Systems: IBM Flex System p270 Compute Node Installation and Service Guide...
Page 167 B200B215 • B200F005 B200B215 Explanation: A problem occurred after a partition ended abnormally. There was a communications problem between this partition's service processor and the platform's service processor. Response: Restart the platform. B200C1F0 Explanation: An internal system firmware error occurred during a partition shutdown or a restart. Response: Go to Isolating firmware problems.
Page 168 Response: No corrective action is required. B200F00C Explanation: Informational system log entry only. Response: No corrective action is required. B200F00D Explanation: Informational system log entry only. Response: No corrective action is required. Power Systems: IBM Flex System p270 Compute Node Installation and Service Guide...
Page 169: B6Xxyyyy Licensed Internal Code Or Hardware Event Srcs
If an action solves the problem, then you can stop performing the remaining actions. See Chapter 7, “Parts listing for IBM Flex System p270 Compute Node,” on page 95 to determine which components are CRUs and which components are FRUs.
Page 170 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 p270 Compute Node Installation and Service Guide...
Page 171 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.
Page 172: B7Xxyyyy Licensed Internal Code Srcs
If an action solves the problem, then you can stop performing the remaining actions. See Chapter 7, “Parts listing for IBM Flex System p270 Compute Node,” on page 95 to determine which components are CRUs and which components are FRUs.
Page 173 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 174 Explanation: Informational system log entry only. Response: No corrective action is required. B7000641 Explanation: System firmware detected an error. Response: 1. Collect the platform dump information. 2. Go to Isolating firmware problems. Power Systems: IBM Flex System p270 Compute Node Installation and Service Guide...
Page 175 B7000650 • B7000A10 B7000650 Explanation: System firmware detected an error. Resource management was unable to allocate main storage. A platform dump was initiated. Response: 1. Collect the event log. 2. Collect the platform dump data. 3. Collect the partition configuration information. 4.
Page 176 Explanation: The VPD on a processor card is not correct and the processor card cannot be used, resulting in reduced processing power. Response: Replace the system-board and chassis assembly, as described in Replacing the system-board and chassis assembly. Power Systems: IBM Flex System p270 Compute Node Installation and Service Guide...
Page 177 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 178 Response: No corrective action is required. B7004788 Explanation: Informational system log entry only. Response: No corrective action is required. B70047CB Explanation: Informational system log entry only. Response: No corrective action is required. Power Systems: IBM Flex System p270 Compute Node Installation and Service Guide...
Page 179 B7005120 • B7005191 B7005120 Explanation: System firmware detected an error Response: If the system is not exhibiting problematic behavior, you can ignore this error. Otherwise, go to Isolating firmware problems. B7005121 Explanation: System firmware detected a programming problem for which a platform dump may have been initiated.
Page 180 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 181 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 182 Response: Replace the system-board and chassis assembly, as described in Replacing the system-board and chassis assembly. B7006909 Explanation: System bus error Response: 1. Replace the system-board, as described in Replacing the system-board and chassis assembly. 2. Go to Isolating firmware problems. Power Systems: IBM Flex System p270 Compute Node Installation and Service Guide...
Page 183 B7006911 • B7006954 B7006911 Explanation: Platform LIC unable to find or retrieve VPD LID file. Response: Check for server firmware updates; then, install the updates if available. B7006912 Explanation: Platform LIC unable to find or retrieve VPD LID file. Response: Check for server firmware updates; then, install the updates if available. B7006944 Explanation: Informational system log entry only.
Page 184 1. Use the PCI expansion card (PIOCARD) problem isolation procedure to determine the failing component. 2. If the problem persists, replace the system-board and chassis assembly, as described in Replacing the system-board and chassis assembly. Power Systems: IBM Flex System p270 Compute Node Installation and Service Guide...
Page 185 B7006974 • B7006985 B7006974 Explanation: Informational system log entry only. Response: No corrective action is required. B7006978 Explanation: Informational system log entry only. Response: No corrective action is required. B7006979 Explanation: Informational system log entry only. Response: No corrective action is required. B700697C Explanation: Connection from service processor to system processor failed.
Page 186 Response: Replace the system-board and chassis assembly, as described in Replacing the system-board and chassis assembly. B7006995 Explanation: Informational system log entry only. Response: No corrective action is required. B70069C2 Explanation: Informational system log entry only. Response: No corrective action is required. Power Systems: IBM Flex System p270 Compute Node Installation and Service Guide...
Page 187 B70069C3 • B70069F2 B70069C3 Explanation: Informational system log entry only. Response: No corrective action is required. B70069D9 Explanation: Host Ethernet Adapter (HEA) failure. Response: Replace the system-board and chassis assembly, as described in Replacing the system-board and chassis assembly. B70069DA Explanation: Informational system log entry only.
Page 188 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. Power Systems: IBM Flex System p270 Compute Node Installation and Service Guide...
Page 189 3. Update the firmware to the current level, as described in Updating the firmware. 4. If the problem persists, replace the system-board and chassis assembly, as described in Replacing the system-board and chassis assembly. Send the failed FRU and the data to IBM for fault analysis. Chapter 8. Troubleshooting...
Page 190 Response: Replace the system-board and chassis assembly, as described in Replacing the system-board and chassis assembly. B700BAD1 Explanation: The platform firmware detected an error. Response: Go to Isolating firmware problems. Power Systems: IBM Flex System p270 Compute Node Installation and Service Guide...
Page 191 B700BAD2 • B700F107 B700BAD2 Explanation: System firmware detected an error. Response: 1. Collect the event log information. 2. Go to Isolating firmware problems. B700F103 Explanation: System firmware failure Response: 1. Collect the event log information. 2. Collect the platform dump information. 3.
Page 192: Baxxyyyy Partition Firmware Srcs
Response: Check for server firmware updates; then, install the updates if available. BAxxyyyy partition firmware SRCs: The power-on self-test (POST) might display an error code that the partition firmware detects. Try to correct the problem with the suggested action. Power Systems: IBM Flex System p270 Compute Node Installation and Service Guide...
Page 193 If an action solves the problem, then you can stop performing the remaining actions. See Chapter 7, “Parts listing for IBM Flex System p270 Compute Node,” on page 95 to determine which components are CRUs and which components are FRUs.
Page 194 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 p270 Compute Node Installation and Service Guide...
Page 195 BA000060 • BA000082 BA000060 Explanation: The firmware was unable to obtain the open firmware code lid details Response: 1. Reboot the server. 2. If the problem persists: Search RETAIN tips and the firmware change history for the reference code to determine the recommended actions.
Page 196 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 p270 Compute Node Installation and Service Guide...
Page 197 BA00E850 • BA010002 BA00E850 Explanation: Failure when initializing dynamic reconfiguration 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 BA00E860 Explanation: Failure when initializing sensors Response:...
Page 198 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 p270 Compute Node Installation and Service Guide...
Page 199 BA010008 • BA01000D BA010008 Explanation: The device_type property for this device is not supported by the iSCSI initiator configuration specification. Response: 1. Reboot the server. 2. If the problem persists: Search RETAIN tips and the firmware change history for the reference code to determine the recommended actions.
Page 200 Response: Informational message. No action is required. BA010015 Explanation: The information in the error log entry for this SRC provides network trace data. Response: Informational message. No action is required. Power Systems: IBM Flex System p270 Compute Node Installation and Service Guide...
Page 201 BA010020 • BA012013 BA010020 Explanation: A trace entry addition failed because of a bad trace type. Response: 1. Reboot the server. 2. If the problem persists: Search RETAIN tips and the firmware change history for the reference code to determine the recommended actions.
Page 202 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 p270 Compute Node Installation and Service Guide...
Page 203 BA01B013 • BA01D020 BA01B013 Explanation: The discover mode is invalid 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 BA01B014 Explanation: Closing the BOOTP node failed Response:...
Page 204 Response: Ten DHCP servers have sent DHCP offers, none of which met the requirements of the client. Check the compatibility of the configuration that the client is requesting and the server DHCP configuration files. Power Systems: IBM Flex System p270 Compute Node Installation and Service Guide...
Page 205 BA01D053 • BA01D0FF BA01D053 Explanation: DHCP::discover received a reply, but without a message type Response: Verify that the DHCP server is properly configured. BA01D054 Explanation: DHCP::discover: DHCP nak received Response: DHCP discovery did receive a DHCP offer from a server that meets the client requirements, but the server sent a DHCP not acknowledged (DHCP nak) to the client DHCP request.
Page 206 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 p270 Compute Node Installation and Service Guide...
Page 207 BA040035 • BA050001 BA040035 Explanation: The firmware was unable to find the plant of manufacture in the VPD. This may cause problems with the licensing of the AIX operating system. Response: Verify that the machine type, model, and serial number are correct for this server. If this is a new server, check for server firmware updates;...
Page 208 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 p270 Compute Node Installation and Service Guide...
Page 209 BA060021 • BA060060 BA060021 Explanation: The environment variable boot-device contained more than five entries. 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 BA060022 Explanation: The environment variable boot-device contained an entry that exceeded 255 characters in length Response:...
Page 210 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 p270 Compute Node Installation and Service Guide...
Page 211 BA060201 • BA090001 BA060201 Explanation: Failed to read the VPD "boot path" field value Response: 1. Reboot the server. 2. Search RETAIN tips and the firmware change history for the reference code to determine the recommended actions. If a firmware update is needed, see Updating the firmware BA060202 Explanation: Failed to update the VPD with the new "boot path"...
Page 212 4. Search RETAIN tips and the firmware change history for the reference code to determine the recommended actions. If a firmware update is needed, see Updating the firmware Power Systems: IBM Flex System p270 Compute Node Installation and Service Guide...
Page 213 BA09000C • BA090010 BA09000C Explanation: The media is write-protected Response: 1. Change the setting of the media to allow writing, then retry the operation. 2. Insert new media of the correct type. 3. Reboot the server. 4. Search RETAIN tips and the firmware change history for the reference code to determine the recommended actions.
Page 214 4. Search RETAIN tips and the firmware change history for the reference code to determine the recommended actions. If a firmware update is needed, see Updating the firmware Power Systems: IBM Flex System p270 Compute Node Installation and Service Guide...
Page 215 BA120003 • BA130010 BA120003 Explanation: On an undetermined SCSD device, send diagnostic failed; sense data available Response: 1. Troubleshoot the SCSD devices. 2. Verify that the SCSD cables and devices are properly plugged. Correct any problems that are found. 3. Replace the SCSD cables and devices. 4.
Page 216 6. Search RETAIN tips and the firmware change history for the reference code to determine the recommended actions. If a firmware update is needed, see Updating the firmware Power Systems: IBM Flex System p270 Compute Node Installation and Service Guide...
Page 217 BA130015 • BA140002 BA130015 Explanation: USB CD-ROM in the media tray: ATA/ATAPI packet command execution failed. Response: 1. Remove the CD or DVD in the drive and replace it with a known-good disk. 2. Retry the operation. 3. Reboot the server. 4.
Page 218 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 p270 Compute Node Installation and Service Guide...
Page 219 BA153002 • BA154030 BA153002 Explanation: Gigabit Ethernet adapter failure Response: Verify that the MAC address programmed in the FLASH/EEPROM is correct. BA153003 Explanation: Gigabit Ethernet adapter failure Response: 1. Reboot the server. 2. Check for server firmware updates; install the updates if available. 3.
Page 220 Explanation: The command to retrieve the MAC address from the adapter failed. Response: 1. Check for and apply any adapter microcode or firmware driver updates. 2. Replace adapter specified by the location code that was reported with the SRC. Power Systems: IBM Flex System p270 Compute Node Installation and Service Guide...
Page 221 BA170000 • BA170203 BA170000 Explanation: NVRAMRC initialization failed; device test failed Response: 1. Reboot the server. 2. Check for server firmware updates; install the updates if available. 3. If the problem persists: Search RETAIN tips and the firmware change history for the reference code to determine the recommended actions.
Page 222 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 p270 Compute Node Installation and Service Guide...
Page 223 BA180008 • BA180012 BA180008 Explanation: PCI device Fcode evaluation error Response: 1. Reboot the server. 2. Search RETAIN tips and the firmware change history for the reference code to determine the recommended actions. If a firmware update is needed, see Updating the firmware BA180009 Explanation: The Fcode on a PCI adapter left a data stack imbalance Response:...
Page 224 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 225 BA190001 • BA210000 BA190001 Explanation: Firmware function to get/set time-of-day reported an error Response: 1. Reboot the server. 2. Check for server firmware updates; install the updates if available. 3. Search RETAIN tips and the firmware change history for the reference code to determine the recommended actions.
Page 226 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 p270 Compute Node Installation and Service Guide...
Page 227 BA210011 • BA210100 BA210011 Explanation: The transfer of control to the IO reporter failed Response: 1. Reboot the server. 2. Search RETAIN tips and the firmware change history for the reference code to determine the recommended actions. If a firmware update is needed, see Updating the firmware BA210012 Explanation: There was an NVRAMRC forced-boot problem;...
Page 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 p270 Compute Node Installation and Service Guide...
Page 229 BA220020 • BA278006 BA220020 Explanation: CRQ registration error; partner vslot may not be valid Response: Verify that this client virtual slot device has a valid server virtual slot device in a hosting partition. BA278001 Explanation: Failed to flash firmware: invalid image file Response: Download a new firmware update image and retry the update.
Page 230 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 p270 Compute Node Installation and Service Guide...
Page 231 BA290001 • BA310030 BA290001 Explanation: RTAS low memory corruption was detected Response: 1. Reboot the server. 2. Check for server firmware updates; install the updates if available. 3. Search RETAIN tips and the firmware change history for the reference code to determine the recommended actions.
Page 232 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 p270 Compute Node Installation and Service Guide...
Page 233 BA340001 • BA340004 BA340001 Explanation: There was a logical partition event communication failure reading the BladeCenter open fabric manager parameter data structure from the service processor. Response: 1. Reboot the server. 2. Check for server firmware updates; install the updates if available. 3.
Page 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 p270 Compute Node Installation and Service Guide...
Page 235 BA340009 • BA340020 BA340009 Explanation: An internal firmware error occurred; the open fabric manager system initiator capability processing encountered an unexpected error. Response: 1. Reboot the server. 2. Check for server firmware updates; install the updates if available. 3. Search RETAIN tips and the firmware change history for the reference code to determine the recommended actions.
Page 236: Post Progress Codes (Checkpoints)
2. For checkpoints with location codes, see “Location codes” on page 103 to identify the failing component when there is a hang condition. 3. For eight-digit codes not listed here, see Progress codes overview in the Systems Hardware information center. Power Systems: IBM Flex System p270 Compute Node Installation and Service Guide...
Page 237: C1Xxyyyy Service Processor Checkpoints
C10010XX • C1001F0D Use ASMI to display the error and event logs. See Displaying error and event logs in the IBM Power Systems Hardware Information Center. C1xxyyyy service processor checkpoints: The C1xxyyyy progress codes, or checkpoints, offer information about the initialization of both the service processor and the compute node.
Page 238 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 p270 Compute Node Installation and Service Guide...
Page 239 C1009X04 • C1009X14 C1009X04 Explanation: Hardware object manager (HOM): build cards IPL step in progress Response: 1. Search RETAIN tips and the firmware change history for the reference code to determine the recommended actions. If a firmware update is needed, see Updating the firmware. 2.
Page 240 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 p270 Compute Node Installation and Service Guide...
Page 241 C1009X2C • C1009X3A C1009X2C Explanation: Processor initialization in progress Response: 1. Search RETAIN tips and the firmware change history for the reference code to determine the recommended actions. If a firmware update is needed, see Updating the firmware. 2. Replace the system-board, as described in Replacing the system-board and chassis assembly. C1009X30 Explanation: Processor self-synchronization in progress Response:...
Page 242 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 p270 Compute Node Installation and Service Guide...
Page 243 C1009X4C • C1009X5C C1009X4C Explanation: Processor wire test IPL step in progress Response: 1. Search RETAIN tips and the firmware change history for the reference code to determine the recommended actions. If a firmware update is needed, see Updating the firmware. 2.
Page 244 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 p270 Compute Node Installation and Service Guide...
Page 245 C1009X6C • C1009X7C C1009X6C Explanation: Processor link initialization step in progress Response: 1. Search RETAIN tips and the firmware change history for the reference code to determine the recommended actions. If a firmware update is needed, see Updating the firmware. 2.
Page 246 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 p270 Compute Node Installation and Service Guide...
Page 247 C1009X90 • C1009X9C C1009X90 Explanation: Wire test in progress Response: 1. Search RETAIN tips and the firmware change history for the reference code to determine the recommended actions. If a firmware update is needed, see Updating the firmware. 2. Replace the system-board, as described in Replacing the system-board and chassis assembly. C1009X92 Explanation: ASIC restore erepair in progress Response:...
Page 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 p270 Compute Node Installation and Service Guide...
Page 249 C1009XB0 • C1009XBB C1009XB0 Explanation: ASIC I/O initialization step in progress Response: 1. Search RETAIN tips and the firmware change history for the reference code to determine the recommended actions. If a firmware update is needed, see Updating the firmware. 2.
Page 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 p270 Compute Node Installation and Service Guide...
Page 251 C1009XD0 • C103A3XX C1009XD0 Explanation: Message passing waiting period has begun Response: 1. Search RETAIN tips and the firmware change history for the reference code to determine the recommended actions. If a firmware update is needed, see Updating the firmware. 2.
Page 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 p270 Compute Node Installation and Service Guide...
Page 253: C2Xxyyyy Virtual Service Processor Checkpoints
If an action solves the problem, you can stop performing the remaining actions. See Chapter 7, “Parts listing for IBM Flex System p270 Compute Node,” on page 95 to determine which components are CRUs and which components are FRUs.
Page 254 2. Replace the system-board, as described in Replacing the system-board and chassis assembly. C2001300 Explanation: Initializing ISL roadmap Response: 1. Go to Recovering the system firmware. 2. Replace the system-board, as described in Replacing the system-board and chassis assembly. Power Systems: IBM Flex System p270 Compute Node Installation and Service Guide...
Page 255 C20013FF • C2002110 C20013FF Explanation: ISL roadmap initialized successfully Response: 1. Go to Recovering the system firmware. 2. Replace the system-board, as described in Replacing the system-board and chassis assembly. C2001400 Explanation: Initializing SP Communication Area #1 Response: 1. Go to Recovering the system firmware. 2.
Page 256 C20023FF Explanation: End acquiring VIO slot locks Response: 1. Go to Recovering the system firmware. 2. Replace the system-board, as described in Replacing the system-board and chassis assembly. Power Systems: IBM Flex System p270 Compute Node Installation and Service Guide...
Page 257 C2002400 • C2003100 C2002400 Explanation: Begin powering on slots Response: 1. Go to Recovering the system firmware. 2. Replace the system-board, as described in Replacing the system-board and chassis assembly. C2002450 Explanation: Waiting for power on of slots to complete Response: 1.
Page 258 2. Replace the system-board, as described in Replacing the system-board and chassis assembly. C20032FF Explanation: ISL command complete successfully Response: 1. Go to Recovering the system firmware. 2. Replace the system-board, as described in Replacing the system-board and chassis assembly. Power Systems: IBM Flex System p270 Compute Node Installation and Service Guide...
Page 259 C2003300 • C2004300 C2003300 Explanation: Start SoftPOR of a failed ISL slot Response: 1. Go to Recovering the system firmware. 2. Replace the system-board, as described in Replacing the system-board and chassis assembly. C2003350 Explanation: Waiting for SoftPOR of a failed ISL slot Response: 1.
Page 260 2. Replace the system-board, as described in Replacing the system-board and chassis assembly. C2006030 Explanation: Priming LP configuration LID Response: 1. Go to Recovering the system firmware. 2. Replace the system-board, as described in Replacing the system-board and chassis assembly. Power Systems: IBM Flex System p270 Compute Node Installation and Service Guide...
Page 261 C2006040 • C20062FF C2006040 Explanation: Preparing to initiate LID load from load source Response: 1. Go to Recovering the system firmware. 2. Replace the system-board, as described in Replacing the system-board and chassis assembly. C2006050 Explanation: LP configuration LID primed successfully Response: 1.
Page 262 Explanation: Initializing service processor communication area #2 Response: 1. Go to Recovering the system firmware. 2. Replace the system-board, as described in Replacing the system-board and chassis assembly. Power Systems: IBM Flex System p270 Compute Node Installation and Service Guide...
Page 263 C2008104 • C200813F C2008104 Explanation: Loading data structures into main store Response: 1. Go to Recovering the system firmware. 2. Replace the system-board, as described in Replacing the system-board and chassis assembly. C2008110 Explanation: Initializing event paths Response: 1. Go to Recovering the system firmware. 2.
Page 264: Ipl Status Progress Codes
If an action solves the problem, you can stop performing the remaining actions. See Chapter 7, “Parts listing for IBM Flex System p270 Compute Node,” on page 95 to determine which components are CRUs and which components are FRUs.
Page 265: Caxxyyyy Partition Firmware Checkpoints
If an action solves the problem, you can stop performing the remaining actions. See Chapter 7, “Parts listing for IBM Flex System p270 Compute Node,” on page 95 to determine which components are CRUs and which components are FRUs.
Page 266 2. Replace the system-board, as described in Replacing the system-board and chassis assembly. CA000050 Explanation: Attempting to load RTAS firmware Response: 1. Go to Checkout procedure. 2. Replace the system-board, as described in Replacing the system-board and chassis assembly. Power Systems: IBM Flex System p270 Compute Node Installation and Service Guide...
Page 267 CA000060 • CA000091 CA000060 Explanation: Attempting to obtain open firmware details Response: 1. Go to Checkout procedure. 2. Replace the system-board, as described in Replacing the system-board and chassis assembly. CA000070 Explanation: Attempting to load open firmware Response: 1. Go to Checkout procedure. 2.
Page 268 2. Replace the system-board, as described in Replacing the system-board and chassis assembly. CA00D008 Explanation: Initialize console and flush queues Response: 1. Go to Checkout procedure. 2. Replace the system-board, as described in Replacing the system-board and chassis assembly. Power Systems: IBM Flex System p270 Compute Node Installation and Service Guide...
Page 269 CA00D00C • CA00D013 CA00D00C Explanation: The partition firmware is about to search for an NVRAM script Response: 1. Go to Checkout procedure. 2. Replace the system-board, as described in Replacing the system-board and chassis assembly. CA00D00D Explanation: Evaluating NVRAM script Response: 1.
Page 270 Response: Go to Boot problem resolution. CA00E10A Explanation: Load RTAS device tree Response: 1. Go to Checkout procedure. 2. Replace the system-board, as described in Replacing the system-board and chassis assembly. Power Systems: IBM Flex System p270 Compute Node Installation and Service Guide...
Page 271 CA00E10B • CA00E134 CA00E10B Explanation: Set RTAS device properties Response: 1. Go to Checkout procedure. 2. Replace the system-board, as described in Replacing the system-board and chassis assembly. CA00E110 Explanation: Create KDUMP properties Response: 1. Reboot the server. 2. If the problem persists: a.
Page 272 2. Replace the system-board, as described in Replacing the system-board and chassis assembly. CA00E139 Explanation: Create aliases node and system aliases Response: 1. Go to Checkout procedure. 2. Replace the system-board, as described in Replacing the system-board and chassis assembly. Power Systems: IBM Flex System p270 Compute Node Installation and Service Guide...
Page 273 CA00E13A • CA00E141 CA00E13A Explanation: Create packages node Response: 1. Go to Checkout procedure. 2. Replace the system-board, as described in Replacing the system-board and chassis assembly. CA00E13B Explanation: Create HEA node Response: 1. Reboot the server. 2. If the problem persists: a.
Page 274 Response: Go to Boot problem resolution. CA00E150 Explanation: Create host (primary) node Response: 1. Go to Checkout procedure. 2. Replace the system-board, as described in Replacing the system-board and chassis assembly. Power Systems: IBM Flex System p270 Compute Node Installation and Service Guide...
Page 275 CA00E151 • CA00E156 CA00E151 Explanation: Probing PCI bus Response: 1. Go to Checkout procedure. 2. Replace the system-board, as described in Replacing the system-board and chassis assembly. CA00E152 Explanation: Probing for adapter FCODE; evaluate if present Response: 1. Go to Checkout procedure. 2.
Page 276 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 p270 Compute Node Installation and Service Guide...
Page 277 CA00E175 • CA00E178 CA00E175 Explanation: Bootp request Response: 1. Verify that: v The bootp server is correctly configured; then, retry the operation. v The network connections are correct; then, retry the operation. 2. If the problem persists: a. Go to Checkout procedure. b.
Page 278 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 279 CA00E19B • CA00E1A3 CA00E19B Explanation: NVRAM menu? variable not found - assume FALSE Response: 1. Go to Checkout procedure. 2. Replace the system-board, as described in Replacing the system-board and chassis assembly. CA00E19D Explanation: Create NVRAM node Response: 1. Go to Checkout procedure. 2.
Page 280 Explanation: System booting using default service mode boot list Response: 1. Go to Checkout procedure. 2. Replace the system-board, as described in Replacing the system-board and chassis assembly. Power Systems: IBM Flex System p270 Compute Node Installation and Service Guide...
Page 281 CA00E1AC • CA00E1B2 CA00E1AC Explanation: System booting using customized service mode boot list Response: 1. Go to Checkout procedure. 2. Replace the system-board, as described in Replacing the system-board and chassis assembly. CA00E1AD Explanation: System booting to the operating system Response: 1.
Page 282 2. Replace the system-board, as described in Replacing the system-board and chassis assembly. CA00E1D4 Explanation: Create SCSD byte device node (ST) Response: 1. Go to Checkout procedure. 2. Replace the system-board, as described in Replacing the system-board and chassis assembly. Power Systems: IBM Flex System p270 Compute Node Installation and Service Guide...
Page 283 CA00E1DC • CA00E1F2 CA00E1DC Explanation: Dynamic console selection Response: 1. Verify the video session and the SOL session. The console might be redirected to the video controller. 2. Start a remote control session or access the local KVM to see the status. 3.
Page 284 Explanation: Build boot device list for SCSD adapters. (The location code of the SCSD adapter being scanned is also displayed.) Response: 1. Go to Checkout procedure. 2. Replace the system-board, as described in Replacing the system-board and chassis assembly. Power Systems: IBM Flex System p270 Compute Node Installation and Service Guide...
Page 285 CA00E1F9 • CA00E1FE CA00E1F9 Explanation: Build boot device list for fibre-channel adapters. (The location code of the SAN adapter being scanned is also displayed.) Response: 1. Go to Checkout procedure. 2. Replace the system-board, as described in Replacing the system-board and chassis assembly. CA00E1FA Explanation: Building device list for SCSD adapters.
Page 286 Response: 1. Reboot the server. 2. If the problem persists: a. Go to Checkout procedure. b. Replace the system-board, as described in Replacing the system-board and chassis assembly. Power Systems: IBM Flex System p270 Compute Node Installation and Service Guide...
Page 287 CA00E701 • CA00E840 CA00E701 Explanation: Create memory VPD Response: 1. Go to Checkout procedure. 2. Replace the system-board, as described in Replacing the system-board and chassis assembly. CA00E800 Explanation: Initialize RTAS Response: 1. Go to Checkout procedure. 2. Replace the system-board, as described in Replacing the system-board and chassis assembly. CA00E810 Explanation: Initializing ioconfig pfds Response:...
Page 288 2. Replace the system-board, as described in Replacing the system-board and chassis assembly. CA00E875 Explanation: Initializing rtas_last_error Response: 1. Go to Checkout procedure. 2. Replace the system-board, as described in Replacing the system-board and chassis assembly. Power Systems: IBM Flex System p270 Compute Node Installation and Service Guide...
Page 289 CA00E876 • CA00E887 CA00E876 Explanation: Initializing rtas_error_inject Response: 1. Go to Checkout procedure. 2. Replace the system-board, as described in Replacing the system-board and chassis assembly. CA00E877 Explanation: Initializing dump interface Response: 1. Go to Checkout procedure. 2. Replace the system-board, as described in Replacing the system-board and chassis assembly. CA00E879 Explanation: Initializing the platform-assisted kdump interface Response:...
Page 290 Response: 1. Reboot the server. 2. If the problem persists: a. Go to Checkout procedure. b. Replace the system-board, as described in Replacing the system-board and chassis assembly. Power Systems: IBM Flex System p270 Compute Node Installation and Service Guide...
Page 291 CA279001 • CA2799FF CA279001 Explanation: The firmware update image contains an update module that is not already on the system. Response: 1. Look at the event log for a BA27xxxx error code to determine if a firmware installation error occurred. 2.
Page 292: D1Xx1Yyy Service Processor Dump Status Codes
If an action solves the problem, you can stop performing the remaining actions. See Chapter 7, “Parts listing for IBM Flex System p270 Compute Node,” on page 95 to determine which components are CRUs and which components are FRUs.
Page 293 D101C00F • D1061XXX D101C00F Explanation: No power off to allow debugging for CPU controls Response: 1. Go to Checkout procedure. 2. Replace the system-board, as described in Replacing the system-board and chassis assembly. D1021XXX Explanation: Dump dump header directory Response: 1.
Page 294 2. Replace the system-board, as described in Replacing the system-board and chassis assembly. D1131XXX Explanation: Dump all traces Response: 1. Go to Checkout procedure. 2. Replace the system-board, as described in Replacing the system-board and chassis assembly. Power Systems: IBM Flex System p270 Compute Node Installation and Service Guide...
Page 295 D1141XXX • D1191XXX D1141XXX Explanation: Dump code version Response: 1. Go to Checkout procedure. 2. Replace the system-board, as described in Replacing the system-board and chassis assembly. D1151XXX Explanation: Dump all /opt/p3 except rtbl Response: 1. Go to Checkout procedure. 2.
Page 296 2. Replace the system-board, as described in Replacing the system-board and chassis assembly. D1241XXX Explanation: Dump CRC1 calculation off Response: 1. Go to Checkout procedure. 2. Replace the system-board, as described in Replacing the system-board and chassis assembly. Power Systems: IBM Flex System p270 Compute Node Installation and Service Guide...
Page 297 D1251XXX • D12A1XXX D1251XXX Explanation: Dump CRC1 calculation on Response: 1. Go to Checkout procedure. 2. Replace the system-board, as described in Replacing the system-board and chassis assembly. D1261XXX Explanation: Dump CRC2 calculation off Response: 1. Go to Checkout procedure. 2.
Page 298 D1301XXX Explanation: Turn off error log capture into dump Response: 1. Go to Checkout procedure. 2. Replace the system-board, as described in Replacing the system-board and chassis assembly. Power Systems: IBM Flex System p270 Compute Node Installation and Service Guide...
Page 299 D1311XXX • D13B1XXX D1311XXX Explanation: Turn on error log capture into dump Response: 1. Go to Checkout procedure. 2. Replace the system-board, as described in Replacing the system-board and chassis assembly. D1321XXX Explanation: Store information about existing core files Response: 1.
Page 300: D1Xx3Yzz Service Processor Dump Codes
If an action solves the problem, you can stop performing the remaining actions. See Chapter 7, “Parts listing for IBM Flex System p270 Compute Node,” on page 95 to determine which components are CRUs and which components are FRUs.
Page 301 D1XX3Y03 • D1XX3Y08 D1XX3Y03 Explanation: Get array values Response: 1. Go to Checkout procedure. 2. Replace the system-board, as described in Replacing the system-board and chassis assembly. D1XX3Y04 Explanation: Stop the clocks Response: 1. Go to Checkout procedure. 2. Replace the system-board, as described in Replacing the system-board and chassis assembly. D1XX3Y05 Explanation: Flush the cache Response:...
Page 302 2. Replace the system-board, as described in Replacing the system-board and chassis assembly. D1XX3YF0 Explanation: Memory collection set-up Response: 1. Go to Checkout procedure. 2. Replace the system-board, as described in Replacing the system-board and chassis assembly. Power Systems: IBM Flex System p270 Compute Node Installation and Service Guide...
Page 303: D1Xx9Yyy To D1Xxcyyy Service Processor Power-Off Checkpoints
If an action solves the problem, you can stop performing the remaining actions. See Chapter 7, “Parts listing for IBM Flex System p270 Compute Node,” on page 95 to determine which components are CRUs and which components are FRUs.
Page 304: Service Request Numbers (Srns)
The third column describes the problem and an action to take to try to fix the problem. The description also includes how to find the FFC number for an SRN if one exists. Power Systems: IBM Flex System p270 Compute Node Installation and Service Guide...
Page 305: 101-711 Through Ffc-725 Srns
101-711 • 101-713 2. See “Failing function codes” on page 437 for a description of each FFC value. 3. If the SRN does not appear in the table, see “Solving undetermined problems” on page 484. 4. After replacing a component, verify the replacement part and perform a log-repair action using the AIX diagnostics.
Page 306 2. If the problem remains, refer to Failing function codes to find the FFC that matches the last three digits of the SRN. 3. Suspect the device adapter or device itself. Response: Failing Item: v FFC_717 Power Systems: IBM Flex System p270 Compute Node Installation and Service Guide...
Page 307 101-718 • 101-721 101-718 Explanation: The system hung while trying to configure an unknown resource. 1. Run the stand-alone diagnostics problem determination procedure. 2. If the problem remains, refer to Failing function codes to find the FFC that matches the last three digits of the SRN.
Page 308 2. If the problem remains, refer to Failing function codes to find the FFC that matches the last three digits of the SRN. 3. Suspect the device adapter or device itself. Response: Failing Item: v FFC_725 Power Systems: IBM Flex System p270 Compute Node Installation and Service Guide...
Page 309 101-726 • 109-200 101-726 Explanation: The system hung while trying to configure an unknown resource. 1. Run the stand-alone diagnostics problem determination procedure. 2. If the problem remains, refer to Failing function codes to find the FFC that matches the last three digits of the SRN.
Page 310 Explanation: The system halted while diagnostics were executing. Go to Performing the checkout procedure or problem resolution. Note: xxx corresponds to the last three digits of the SRN. Response: Failing Item: v FFC_812 v FFC_XXX Power Systems: IBM Flex System p270 Compute Node Installation and Service Guide...
Page 311 110-924 • 110-935 110-924 Explanation: The system halted while diagnostics were executing. Go to Performing the checkout procedure or problem resolution. Note: xxx corresponds to the last three digits of the SRN. Response: Failing Item: v FFC_812 v FFC_XXX 110-925 Explanation: The system halted while diagnostics were executing.
Page 312 Explanation: System does not perform a soft reset. Go to Performing the checkout procedure. Response: Failing Item: v FFC_210 650-XXX Explanation: Disk drive configuration failed. Replace the FRU identified by diagnostics. Response: Failing Item: v FFC_650 Power Systems: IBM Flex System p270 Compute Node Installation and Service Guide...
Page 313 651-199 • 652-612 651-199 Explanation: This is a test of the flow of a serviceable event from this system to management console. This is not a real problem. Response: Problem determination: Use the management console to list serviceable events and verify the serviceable event was sent to the HMC.
Page 314 FFC_307 652-632 Explanation: A non-critical error has been detected: I/O expansion bus connection failure. Schedule deferred maintenance. Go to Performing the checkout procedure. Response: Failing Item: v FFC_307 Power Systems: IBM Flex System p270 Compute Node Installation and Service Guide...
Page 315 652-633 • 652-666 652-633 Explanation: A non-critical error has been detected: I/O expansion unit not in an operating state. Schedule deferred maintenance. Go to Performing the checkout procedure. Response: Failing Item: v FFC_307 652-634 Explanation: A non-critical error has been detected: internal device error. Schedule deferred maintenance. Go to Performing the checkout procedure.
Page 316 Explanation: A non-critical error has been detected: intermediate or system bus data parity error. Schedule deferred maintenance. Go to Performing the checkout procedure. Response: Failing Item: v FFC_2C8 Power Systems: IBM Flex System p270 Compute Node Installation and Service Guide...
Page 317 652-733 • 652-736 652-733 Explanation: A non-critical error has been detected: intermediate or system bus address parity error. Schedule deferred maintenance. Go to Performing the checkout procedure. Response: Failing Item: v FFC_2C8 v FFC_292 652-734 Explanation: A non-critical error has been detected: intermediate or system bus data parity error. Schedule deferred maintenance.
Page 318 3. If the 8-digit error and location codes were NOT reported, then run diagnostics in problem determination mode and record and report the 8-digit error and location codes for this SRN. Response: Power Systems: IBM Flex System p270 Compute Node Installation and Service Guide...
Page 319 652-89X • 815-100 652-89X Explanation: The CEC or SPCN reported a non-critical error. 1. Schedule deferred maintenance. 2. Refer to the entry MAP in this system unit system service guide, with the 8-digit error and location codes, for the necessary repair action. 3.
Page 320 Go to Performing the checkout procedure. Response: Failing Item: v FFC_815 817-123 Explanation: The I/O planar time-of-day clock test failed. Go to Performing the checkout procedure. Response: Failing Item: v FFC_817 Power Systems: IBM Flex System p270 Compute Node Installation and Service Guide...
Page 321 817-124 • 817-215 817-124 Explanation: Time of day RAM test failed. Go to Performing the checkout procedure. Response: Failing Item: v FFC_817 817-210 Explanation: The time-of-day clock is at POR. Go to Performing the checkout procedure. Response: Failing Item: v FFC_817 817-211 Explanation: Time of day POR test failed.
Page 322 Explanation: Vital Product Data (VPD) failed. Go to Performing the checkout procedure. Response: Failing Item: v FFC_887 887-105 Explanation: LAN coprocessor internal tests failed. Go to Performing the checkout procedure. Response: Failing Item: v FFC_887 Power Systems: IBM Flex System p270 Compute Node Installation and Service Guide...
Page 323 887-106 • 887-111 887-106 Explanation: Internal loopback test failed. Go to Performing the checkout procedure. Response: Failing Item: v FFC_887 887-107 Explanation: External loopback test failed. Go to Performing the checkout procedure. Response: Failing Item: v FFC_887 887-108 Explanation: External loopback test failed. Go to Performing the checkout procedure. Response: Failing Item: v FFC_887...
Page 324 Explanation: External loopback (twisted pair) fairness and parity tests failed. Go to Performing the checkout procedure. Response: Failing Item: v FFC_887 887-116 Explanation: Twisted pair wrap data failed. Go to Performing the checkout procedure. Response: Failing Item: v FFC_887 Power Systems: IBM Flex System p270 Compute Node Installation and Service Guide...
Page 325 887-117 • 887-123 887-117 Explanation: Software device configuration fails. Go to Performing the checkout procedure. Response: Failing Item: v FFC_887 887-118 Explanation: Device driver indicates a hardware problem. Go to Performing the checkout procedure. Response: Failing Item: v FFC_887 887-120 Explanation: Device driver indicates a hardware problem.
Page 326 Explanation: RJ-45 converter test failed. Go to Performing the checkout procedure. Response: Failing Item: v FFC_887 887-304 Explanation: Coprocessor internal test failed. Go to Performing the checkout procedure. Response: Failing Item: v FFC_887 Power Systems: IBM Flex System p270 Compute Node Installation and Service Guide...
Page 327 887-305 • 887-401 887-305 Explanation: Internal loopback test failed. Go to Performing the checkout procedure. Response: Failing Item: v FFC_887 887-306 Explanation: Internal loopback test failed. Go to Performing the checkout procedure. Response: Failing Item: v FFC_887 887-307 Explanation: External loopback test failed. Go to Performing the checkout procedure. Response: Failing Item: v FFC_887...
Page 328 Explanation: The system hung while configuring a resource. The last three or four digits after the dash (-) identify the failing function code for the resource being configured. Go to undetermined problem procedure. Response: Failing Item: v FFC_XXXX Power Systems: IBM Flex System p270 Compute Node Installation and Service Guide...
Page 329 110-XXXX • 252B-711 110-XXXX Explanation: The system halted while diagnostics were executing. Note: xxxx corresponds to the last three or four digits of the SRN following the dash (-). 1. If your 110 SRN is not listed, substitute the last three or four digits of the SRN for xxxx and go to Failing function codes to identify the failing feature.
Page 330 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 p270 Compute Node Installation and Service Guide...
Page 331 252B-716 • 252B-718 252B-716 Explanation: PCI bus error detected by EEH. 1. Check the BladeCenter management-module event log. If an error was recorded by the system, see POST progress codes (checkpoints). 2. Replace any parts reported by the diagnostic program. 3.
Page 332 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 p270 Compute Node Installation and Service Guide...
Page 333 252B-723 • 254E-603 252B-723 Explanation: Device bus interface problem. 1. Check the BladeCenter management-module event log. If an error was recorded by the system, see POST progress codes (checkpoints). 2. Replace any parts reported by the diagnostic program. 3. Replace the system-board Response: Failing Item: v FFC_252B...
Page 334 Explanation: Error log analysis indicates permanent adapter failure is reported on the other port of this adapter. Go to Performing the checkout procedure. Response: Failing Item: v FFC_254E v FFC_221 Power Systems: IBM Flex System p270 Compute Node Installation and Service Guide...
Page 335 2567-XXX • 256D-602 2567-XXX Explanation: USB integrated system-board and chassis assembly. Go to Performing the checkout procedure. Response: Failing Item: v FFC_2567 256D-201 Explanation: Adapter configuration error. 1. Check the BladeCenter management-module event log. If an error was recorded by the system, see POST progress codes (checkpoints).
Page 336 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 p270 Compute Node Installation and Service Guide...
Page 337 256D-701 • 25C4-601 256D-701 Explanation: Error Log Analysis indicates permanent adapter failure. 1. Check the BladeCenter management-module event log. If an error was recorded by the system, see POST progress codes (checkpoints). 2. Replace any parts reported by the diagnostic program. 3.
Page 338 Response: Failing Item: v FFC_2604 2604-104 Explanation: SRAM Test failure for the Fibre Channel adapter card. Replace the 4Gb Fibre Channel Adapter card. Response: Failing Item: v FFC_2604 Power Systems: IBM Flex System p270 Compute Node Installation and Service Guide...
Page 339 2604-105 • 2604-201 2604-105 Explanation: Internal Wrap Test failure for the Fibre Channel adapter card. Replace the 4Gb Fibre Channel Adapter card. Response: Failing Item: v FFC_2604 2604-106 Explanation: Gigabit Link Module (GLM) Wrap Test failure for the Fibre Channel adapter card. Replace the 4Gb Fibre Channel Adapter card.
Page 340 Explanation: Error Log Analysis indicates that an unknown adapter error has occurred for the Fibre Channel adapter card. Go to Performing the checkout procedure. Response: Failing Item: v FFC_2604 Power Systems: IBM Flex System p270 Compute Node Installation and Service Guide...
Page 341 2604-704 • 2607-102 2604-704 Explanation: Error Log Analysis indicates that an adapter error has occurred for the Fibre Channel adapter card. Go to Performing the checkout procedure. Response: Failing Item: v FFC_2604 2604-705 Explanation: Error Log Analysis indicates that a parity error has been detected for the Fibre Channel adapter card. The adapter must be replaced immediately.
Page 342 2607-108 Explanation: Enhanced Error Handling Failure on the bus for the Fibre Channel adapter card. Go to Performing the checkout procedure. Response: Failing Item: v FFC_2607 v FFC_221 Power Systems: IBM Flex System p270 Compute Node Installation and Service Guide...
Page 343 2607-110 • 2607-205 2607-110 Explanation: Enhanced Error Handling Failure on the Fibre Channel adapter card. Replace the 8Gb PCIe Fibre Channel Expansion Card. Response: Failing Item: v FFC_2607 2607-201 Explanation: Configuration Register Test Failure for the Fibre Channel adapter card. Go to Performing the checkout procedure.
Page 344 Failure to adhere to this action could result in data being read or written incorrectly or in the loss of data. Response: Failing Item: v FFC_2607 Power Systems: IBM Flex System p270 Compute Node Installation and Service Guide...
Page 345 2607-XXX • 2624-201 2607-XXX Explanation: Generic reference for 8Gb PCIe Fibre Channel Expansion Card. Go to Performing the checkout procedure. Response: Failing Item: v FFC_2607 2624-101 Explanation: Configuration failure. Replace the 4X PCI-E DDR InfiniBand Host Channel Adapter. Response: Failing Item: v FFC_2624 2624-102 Explanation: Queue pair create failure.
Page 346 Explanation: Error Log Analysis indicates that this adapter has failed due to a memory error. Replace the 4X PCI-E DDR InfiniBand Host Channel Adapter. Response: Failing Item: v FFC_2624 Power Systems: IBM Flex System p270 Compute Node Installation and Service Guide...
Page 347 2624-704 • 2625-101 2624-704 Explanation: Error Log Analysis indicates that this adapter has failed due to a unrecoverable internal parity error Replace the 4X PCI-E DDR InfiniBand Host Channel Adapter. Response: Failing Item: v FFC_2624 2624-705 Explanation: Error Log Analysis indicates that this adapter has failed due to a internal error. Replace the 4X PCI-E DDR InfiniBand Host Channel Adapter.
Page 348 3. Verify that the network is functional. 4. Verify that the network switch is functional. 5. Go to Performing the checkout procedure. Response: Failing Item: v CABLE v NETWORK v FFC_2625 Power Systems: IBM Flex System p270 Compute Node Installation and Service Guide...
Page 349 2625-701 • 2625-705 2625-701 Explanation: Error Log Analysis indicates that this adapter has failed due to an internal error. Replace the 2-port QDR 40 GB/S InfiniBand expansion card (CFFh). Response: Failing Item: v FFC_2625 2625-702 Explanation: Error Log Analysis indicates that this adapter has failed due to a failure with the uplink interface used to connect this device to the host processor.
Page 350 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 351 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 352 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 353 2640-131 • 2640-136 2640-131 Explanation: Smart status threshold exceeded. Go to Performing the checkout procedure. Response: Failing Item: v FFC_2640 2640-132 Explanation: Command timeouts threshold exceeded. Go to Performing the checkout procedure. Response: Failing Item: v FFC_2640 2640-133 Explanation: Command timeout with error condition. Go to Performing the checkout procedure. Response: Failing Item: v FFC_2640...
Page 354 Explanation: The bus test failed. Replace the 300 GB SFF SAS Hard Disk Drive. Response: Failing Item: v FFC_268B 268B-110 Explanation: The media format is corrupted. Replace the 300 GB SFF SAS Hard Disk Drive. Response: Failing Item: v FFC_268B Power Systems: IBM Flex System p270 Compute Node Installation and Service Guide...
Page 355 268B-112 • 268B-118 268B-112 Explanation: The diagnostic test failed. Replace the 300 GB SFF SAS Hard Disk Drive. Response: Failing Item: v FFC_268B 268B-114 Explanation: An unrecoverable hardware error. Replace the 300 GB SFF SAS Hard Disk Drive. Response: Failing Item: v FFC_268B 268B-116 Explanation: A protocol error.
Page 356 Run the diagnostic program in problem determination mode on each part reported in the original SRN. If the problem persists, replace the next part in the list. Response: Failing Item: v FFC_B88 v FFC_268B Power Systems: IBM Flex System p270 Compute Node Installation and Service Guide...
Page 357 268B-129 • 268B-135 268B-129 Explanation: Error log analysis indicates a SCSI bus problem. Replace each part reported by the diagnostic program one at a time. Run the diagnostic program in problem determination mode on each part reported in the original SRN. If the problem persists, replace the next part in the list.
Page 358 Run the diagnostic program in problem determination mode on each part reported in the original SRN. If the problem persists, replace the next part in the list. Response: Failing Item: v FFC_B88 v FFC_268B Power Systems: IBM Flex System p270 Compute Node Installation and Service Guide...
Page 359 268B-640 • 26B4-108 268B-640 Explanation: Error log analysis indicates a path error. Replace the 300 GB SFF SAS Hard Disk Drive. Response: Failing Item: v FFC_268B 26B4-102 Explanation: An unrecoverable media error occurred. Replace the 200 GB SATA Solid State Drive. Response: Failing Item: v FFC_26B4...
Page 360 2. If you do not find a problem, call your operating-system support person. Response: Failing Item: v FFC_26B4 v FFC_26BD 26B4-117 Explanation: A write-protect error occurred. Replace the 200 GB SATA Solid State Drive. Response: Failing Item: v FFC_26B4 Power Systems: IBM Flex System p270 Compute Node Installation and Service Guide...
Page 361 26B4-118 • 26B4-124 26B4-118 Explanation: A SCSI command time-out occurred. Replace each part reported by the diagnostic program one at a time. Retry the diagnostic test after each part is replaced. If the problem persists, replace the next part in the list. Response: Failing Item: v FFC_26B4...
Page 362 26B4-130 Explanation: Error log analysis indicates a problem reported by the disk drive's self-monitoring function. Replace the 200 GB SATA Solid State Drive. Response: Failing Item: v FFC_26B4 Power Systems: IBM Flex System p270 Compute Node Installation and Service Guide...
Page 363 26B4-132 • 26B4-136 26B4-132 Explanation: A disk drive hardware error occurred. Replace each part reported by the diagnostic program one at a time. Retry the diagnostic test after each part is replaced. If the problem persists, replace the next part in the list. Response: Failing Item: v FFC_26B4...
Page 364 Explanation: Error log analysis indicates a path error. Replace the SAS to SATA Interposer Card. If the problem persists, replace the 200 GB SATA Solid State Drive. Response: Failing Item: v FFC_26B4 v FFC_26BD Power Systems: IBM Flex System p270 Compute Node Installation and Service Guide...
Page 365 26D2-102 • 26D2-110 26D2-102 Explanation: An unrecoverable media error occurred. Replace the 600 GB SFF SAS Hard Disk Drive. Response: Failing Item: v FFC_26D2 26D2-104 Explanation: The motor failed to restart. Replace the 600 GB SFF SAS Hard Disk Drive. Response: Failing Item: v FFC_26D2...
Page 366 Explanation: A SCSI command time-out occurred. Replace the 600 GB SFF SAS Hard Disk Drive. Run diagnostics again on the drive. If the error repeats, replace the 2nd FRU identified by diagnostics. Response: Failing Item: v FFC_26D2 v FFC_B88 Power Systems: IBM Flex System p270 Compute Node Installation and Service Guide...
Page 367 26D2-120 • 26D2-128 26D2-120 Explanation: A SCSI busy or command error. Replace the 600 GB SFF SAS Hard Disk Drive. Response: Failing Item: v FFC_26D2 26D2-122 Explanation: A SCSI reservation conflict error. Replace the 600 GB SFF SAS Hard Disk Drive. Response: Failing Item: v FFC_26D2...
Page 368 Retry the diagnostic test after each part is replaced. If the problem persists, replace the next part in the list. Response: Failing Item: v FFC_26D2 v FFC_B88 v SOFTWARE Power Systems: IBM Flex System p270 Compute Node Installation and Service Guide...
Page 369 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 370 Explanation: The electronics card test failed. Replace the 900 GB SFF SAS Hard Disk Drive. Response: Failing Item: v FFC_26D7 26D7-108 Explanation: The bus test failed. Replace the 900 GB SFF SAS Hard Disk Drive. Response: Failing Item: v FFC_26D7 Power Systems: IBM Flex System p270 Compute Node Installation and Service Guide...
Page 371 26D7-110 • 26D7-117 26D7-110 Explanation: The media format is corrupted. Replace the 900 GB SFF SAS Hard Disk Drive. Response: Failing Item: v FFC_26D7 26D7-112 Explanation: The diagnostic test failed. Replace the 900 GB SFF SAS Hard Disk Drive. Response: Failing Item: v FFC_26D7 26D7-114...
Page 372 Explanation: A software error was caused by a hardware failure. Replace the 900 GB SFF SAS Hard Disk Drive. Run diagnostics again on the drive. If the error repeats, replace the 2nd FRU identified by diagnostics. Response: Failing Item: v FFC_26D7 v FFC_B88 Power Systems: IBM Flex System p270 Compute Node Installation and Service Guide...
Page 373 26D7-128 • 26D7-134 26D7-128 Explanation: The error log analysis indicates a hardware failure. Replace each part reported by the diagnostic program one at a time. Run the diagnostic program in problem determination mode on each part reported in the original SRN. If the problem persists, replace the next part in the list. Response: Failing Item: v FFC_B88...
Page 374 The ventilation holes in the blade server bezel are not blocked. v The Management Module event log is not reporting any system environmental warnings. 2. If the problem remains, call IBM support. Response: Failing Item: v FFC_26D7 Power Systems: IBM Flex System p270 Compute Node Installation and Service Guide...
Page 375 26D7-140 • 2750-201 26D7-140 Explanation: Error log analysis indicates poor signal quality. Replace each part reported by the diagnostic program one at a time. Run the diagnostic program in problem determination mode on each part reported in the original SRN. If the problem persists, replace the next part in the list.
Page 376 2755-201 Explanation: Adapter configuration error Replace the PCIe2 16Gb 4-port FC Mezzanine Adapter If the problem persists, replace the system board. Response: Failing Item: v FFC_2755 v FFC_221 Power Systems: IBM Flex System p270 Compute Node Installation and Service Guide...
Page 377 Explanation: Configuration failure. Replace the IBM Flex System EN4132 2-port 10Gb RoCE Adapter Response: Failing Item: v FFC_2770 2770-102 Explanation: Queue pair create failure. Replace the IBM Flex System EN4132 2-port 10Gb RoCE Adapter Response: Failing Item: v FFC_2770 Chapter 8. Troubleshooting...
Page 378 Failing Item: v CABLE v NETWORK v FFC_2770 2770-601 Explanation: Error Log Analysis indicates adapter hardware error Replace the IBM Flex System EN4132 2-port 10Gb RoCE Adapter Response: Failing Item: v FFC_2770 Power Systems: IBM Flex System p270 Compute Node Installation and Service Guide...
Page 379 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 380 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 381 2D14-710 • 2D29-713 2D14-710 Explanation: Permanent controller error. Replace the system board (SAS controller). Response: Failing Item: v FFC_2D14 2D14-713 Explanation: Controller error. Replace the system board (SAS controller). Response: Failing Item: v FFC_2D14 2D14-720 Explanation: Controller devce bus configuration error. Use MAP3150 to determine resolution. Response: 2D29-101 Explanation: Adapter configuration error.
Page 382 1. Check the BladeCenter management-module event log. If an error was recorded by the system, see POST progress codes (checkpoints). 2. Replace any parts reported by the diagnostic program. 3. Replace the system-board Response: Failing Item: v FFC_2E00 v FFC_221 Power Systems: IBM Flex System p270 Compute Node Installation and Service Guide...
Page 383 2E10-201 • 2E10-603 2E10-201 Explanation: Adapter configuration error. 1. Check the BladeCenter management-module event log. If an error was recorded by the system, see POST progress codes (checkpoints). 2. Replace any parts reported by the diagnostic program. 3. Replace the system-board Response: Failing Item: v FFC_2E10...
Page 384 1. Check the BladeCenter management-module event log. If an error was recorded by the system, see POST progress codes (checkpoints). 2. Replace any parts reported by the diagnostic program. 3. Replace the system-board Response: Failing Item: v FFC_2E10 v FFC_221 Power Systems: IBM Flex System p270 Compute Node Installation and Service Guide...
Page 385 2E10-702 • 2E13-602 2E10-702 Explanation: Error Log Analysis indicates permanent adapter failure. 1. Check the BladeCenter management-module event log. If an error was recorded by the system, see POST progress codes (checkpoints). 2. Replace any parts reported by the diagnostic program. 3.
Page 386 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 p270 Compute Node Installation and Service Guide...
Page 387 2E13-701 • 2E14-201 2E13-701 Explanation: Error Log Analysis indicates permanent adapter failure. 1. Check the BladeCenter management-module event log. If an error was recorded by the system, see POST progress codes (checkpoints). 2. Replace any parts reported by the diagnostic program. 3.
Page 388 1. Check the BladeCenter management-module event log. If an error was recorded by the system, see POST progress codes (checkpoints). 2. Replace any parts reported by the diagnostic program. 3. Replace the system-board Response: Failing Item: v FFC_2E14 Power Systems: IBM Flex System p270 Compute Node Installation and Service Guide...
Page 389 2E14-605 • 2E14-702 2E14-605 Explanation: Error Log Analysis indicates permanent adapter failure is reported on the other port of this adapter. 1. Check the BladeCenter management-module event log. If an error was recorded by the system, see POST progress codes (checkpoints). 2.
Page 390 1. Check the BladeCenter management-module event log. If an error was recorded by the system, see POST progress codes (checkpoints). 2. Replace any parts reported by the diagnostic program. 3. Replace the system-board Response: Failing Item: v FFC_2E15 Power Systems: IBM Flex System p270 Compute Node Installation and Service Guide...
Page 391 2E15-604 • 2E15-701 2E15-604 Explanation: Error Log Analysis indicates a permanent adapter failure. 1. Check the BladeCenter management-module event log. If an error was recorded by the system, see POST progress codes (checkpoints). 2. Replace any parts reported by the diagnostic program. 3.
Page 392 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 393 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 394 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 395 2E21-603 • 2E21-606 2E21-603 Explanation: Error Log Analysis indicates that the microcode could not be loaded on the adapter. 1. Check the BladeCenter management-module event log. If an error was recorded by the system, see POST progress codes (checkpoints). 2. Replace any parts reported by the diagnostic program. 3.
Page 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_2E23 Power Systems: IBM Flex System p270 Compute Node Installation and Service Guide...
Page 397 2E23-103 • 2E23-106 2E23-103 Explanation: Flash Test Failure 1. Check the BladeCenter management-module event log. If an error was recorded by the system, see POST progress codes (checkpoints). 2. Replace any parts reported by the diagnostic program. 3. Replace the system-board Response: Failing Item: v FFC_2E23...
Page 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_2E23 v FFC_221 Power Systems: IBM Flex System p270 Compute Node Installation and Service Guide...
Page 399 2E23-202 • 2E23-603 2E23-202 Explanation: Network link test failure. 1. Check the BladeCenter management-module event log. If an error was recorded by the system, see POST progress codes (checkpoints). 2. Replace any parts reported by the diagnostic program. 3. Replace the system-board Response: Failing Item: v FFC_241...
Page 400 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 401 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 402 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 403 2E33-701 • 2E34-602 2E33-701 Explanation: Permanent adapter failure. 1. Check the BladeCenter management-module event log. If an error was recorded by the system, see POST progress codes (checkpoints). 2. Replace any parts reported by the diagnostic program. 3. Replace the system-board Response: Failing Item: v FFC_2E33...
Page 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_2E35 Power Systems: IBM Flex System p270 Compute Node Installation and Service Guide...
Page 405 2E35-701 • 2E36-602 2E35-701 Explanation: Permanent adapter failure. 1. Check the BladeCenter management-module event log. If an error was recorded by the system, see POST progress codes (checkpoints). 2. Replace any parts reported by the diagnostic program. 3. Replace the system-board Response: Failing Item: v FFC_2E35...
Page 406 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 407 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 408 Explanation: Adapter hardware error. Replace the IBM Flex System EN4054 4-port 10Gb Ethernet Adapter. Response: Failing Item: v FFC_2E37 2E37-702 Explanation: EEH service error. Replace the IBM Flex System EN4054 4-port 10Gb Ethernet Adapter. If the problem persists, replace the system board. Response: Failing Item: v FFC_2E37...
Page 409 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 410 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 411 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 412 2. Replace any parts reported by the diagnostic program. 3. Reseat the 3Gb SAS Adapter card. 4. Replace the 3Gb SAS Adapter card. 5. Replace the system-board Response: Failing Item: v FFC_2506 v FFC_221 Power Systems: IBM Flex System p270 Compute Node Installation and Service Guide...
Page 413 950-2D14 • 2506-3010 950-2D14 Explanation: A resource was not detected that was previously installed. Check the Management Module event log for an system event. If there is not a system error, replace the system board (SAS controller). Response: Failing Item: v FFC_2D14 950-2D29 Explanation: A resource was not detected that was previously installed.
Page 414 Explanation: Configuration error, incorrect multipath connection. Go to Performing the checkout procedure. Response: 2506-4040 Explanation: Configuration error, incomplete multipath connection between controller and enclosure detected. Go to Performing the checkout procedure. Response: Power Systems: IBM Flex System p270 Compute Node Installation and Service Guide...
Page 415 2506-4041 • 2506-4150 2506-4041 Explanation: Configuration error, incomplete multipath connection between enclosure and device detected. Go to Performing the checkout procedure. Response: 2506-4050 Explanation: Attached enclosure does not support required multipath function. Go to Performing the checkout procedure. Response: 2506-4060 Explanation: Multipath redundancy level got worse.
Page 416 Explanation: Controller failure. Go to Performing the checkout procedure. Response: Failing Item: v FFC_2506 2506-8157 Explanation: Temporary controller failure. Go to Performing the checkout procedure. Response: Failing Item: v FFC_2506 Power Systems: IBM Flex System p270 Compute Node Installation and Service Guide...
Page 417 2506-9000 • 2506-9020 2506-9000 Explanation: Controller detected device error during configuration discovery. Go to Performing the checkout procedure. Response: 2506-9001 Explanation: Controller detected device error during configuration discovery. Go to Performing the checkout procedure. Response: 2506-9002 Explanation: Controller detected device error during configuration discovery. Go to Performing the checkout procedure.
Page 418 Explanation: Previously degraded disk in Disk Array not found at required physical location. Go to Performing the checkout procedure. Response: 2506-9027 Explanation: Disk Array is or would become degraded and parity data is out of synchronization. Go to Performing the checkout procedure. Response: Power Systems: IBM Flex System p270 Compute Node Installation and Service Guide...
Page 419 2506-9028 • 2506-9050 2506-9028 Explanation: Maximum number of functional Disk Arrays has been exceeded. Go to Performing the checkout procedure. Response: 2506-9029 Explanation: Maximum number of functional Disk Arrays disks has been exceeded. Go to Performing the checkout procedure. Response: 2506-9030 Explanation: Disk Array is degraded due to missing/failed disk.
Page 420 Explanation: Maximum number of functional Disk Arrays has been exceeded. Go to Performing the checkout procedure. Response: 2506-9073 Explanation: Multiple controllers connected in an invalid configuration. Go to Performing the checkout procedure. Response: Power Systems: IBM Flex System p270 Compute Node Installation and Service Guide...
Page 421 2506-9074 • 2506-9092 2506-9074 Explanation: Multiple controllers not capable of similar functions or controlling same set of devices. Go to Performing the checkout procedure. Response: 2506-9075 Explanation: Incomplete multipath connection between controller and remote controller. Go to Performing the checkout procedure. Response: 2506-9076 Explanation: Missing remote controller.
Page 422 Failing Item: v FFC_722 2506-FFFA Explanation: Temporary device bus error. Retry the operation. Response: Failing Item: v FFC_722 2506-FFFE Explanation: Temporary device bus error. Retry the operation. Response: Power Systems: IBM Flex System p270 Compute Node Installation and Service Guide...
Page 423 2D14-102E • 2D14-3110 2D14-102E Explanation: Reallocation failed due to disk out of alternate sectors. Replace the FRU identified by diagnostics. Response: Failing Item: v FFC_722 2D14-3002 Explanation: Addressed device failed to respond to selection. Replace the FRU identified by diagnostics. Response: Failing Item: v FFC_722...
Page 424 Explanation: Attached enclosure does not support required multipath function. Use MAP3148 to determine resolution. Response: 2D14-4060 Explanation: Multipath redundancy level got worse. Use MAP3153 to determine resolution. Response: 2D14-4100 Explanation: Device bus fabric error. Use MAP3152 to determine resolution. Response: Power Systems: IBM Flex System p270 Compute Node Installation and Service Guide...
Page 425 2D14-4101 • 2D14-8150 2D14-4101 Explanation: Temporary device bus fabric error. Use MAP3152 to determine resolution. Response: 2D14-4110 Explanation: Unsupported enclosure function detected. Use MAP3145 to determine resolution. Response: 2D14-4150 Explanation: PCI bus error detected by controller. Replace the system board (SAS controller). Response: Failing Item: v FFC_2D14...
Page 426 Explanation: Cache data belongs to disks other than those attached. Use MAP3190 to determine resolution. Response: 2D14-9020 Explanation: Two or more disks are missing from a RAID-5 or RAID 6 Disk Array. Use MAP3111 to determine resolution. Response: Power Systems: IBM Flex System p270 Compute Node Installation and Service Guide...
Page 427 2D14-9021 • 2D14-9027 2D14-9021 Explanation: Two or more disks are missing from a RAID-5 or RAID 6 Disk Array. Use MAP3111 to determine resolution. Response: 2D14-9022 Explanation: Two or more disks are missing from a RAID-5 or RAID 6 Disk Array. Use MAP3111 to determine resolution.
Page 428 Explanation: Background Disk Array parity checking detected and corrected errors on specified disk. Use MAP3190 to determine resolution. Response: 2D14-9050 Explanation: Required cache data can not be located for one or more disks. Use MAP3131 to determine resolution. Response: Power Systems: IBM Flex System p270 Compute Node Installation and Service Guide...
Page 429 2D14-9051 • 2D14-9073 2D14-9051 Explanation: Cache data exists for one or more missing/failed disks. Use MAP3132 to determine resolution. Response: 2D14-9052 Explanation: Cache data exists for one or more modified disks. Use MAP3190 to determine resolution. Response: 2D14-9054 Explanation: RAID controller resources not available due to previous problems. Use MAP3121 to determine resolution.
Page 430 Explanation: Incorrect disk configuration change has been detected. Use MAP3133 to determine resolution. Response: 2D14-9092 Explanation: Disk requires Format before use. Format the disk and retry the operation. Use MAP3134 to determine resolution. Response: Power Systems: IBM Flex System p270 Compute Node Installation and Service Guide...
Page 431 2D14-FF3D • 2D14-FFFE 2D14-FF3D Explanation: Temporary controller failure. Retry the operation. Replace the system board (SAS controller). Response: Failing Item: v FFC_2D14 2D14-FFF3 Explanation: Disk media format bad. Reformat the disk and retry the operation. Use MAP3135 to determine resolution. Response: 2D14-FFF4 Explanation: Device problem.
Page 432 Explanation: Controller detected device bus interface error. Use MAP3150 to determine resolution. Response: 2D29-3109 Explanation: Controller timed out a device command. Use MAP3150 to determine resolution. Response: 2D29-3110 Explanation: Device bus interface error. Use MAP3150 to determine resolution. Response: Power Systems: IBM Flex System p270 Compute Node Installation and Service Guide...
Page 433 2D29-4010 • 2D29-4100 2D29-4010 Explanation: Configuration error, incorrect connection between cascaded enclosures. Use MAP3142 to determine resolution. Response: 2D29-4020 Explanation: Configuration error, connections exceed IOA design limits. Use MAP3143 to determine resolution. Response: 2D29-4030 Explanation: Configuration error, incorrect multipath connection. Use MAP3144 to determine resolution. Response: 2D29-4040 Explanation: Configuration error, incomplete multipath connection between controller and enclosure detected.
Page 434 Explanation: Temporary disk data error. Replace the PCIe x8 Internal 3Gb SAS Adapter. Response: Failing Item: v FFC_722 2D29-8150 Explanation: Controller failure. Replace the PCIe x8 Internal 3Gb SAS Adapter. Response: Failing Item: v FFC_2D29 Power Systems: IBM Flex System p270 Compute Node Installation and Service Guide...
Page 435 2D29-8157 • 2D29-9020 2D29-8157 Explanation: Temporary controller failure. Replace the PCIe x8 Internal 3Gb SAS Adapter. Response: Failing Item: v FFC_2D29 2D29-9000 Explanation: Controller detected device error during configuration discovery. Use MAP3190 to determine resolution. Response: 2D29-9001 Explanation: Controller detected device error during configuration discovery. Use MAP3190 to determine resolution. Response: 2D29-9002 Explanation: Controller detected device error during configuration discovery.
Page 436 Explanation: Previously degraded disk in Disk Array not found at required physical location. Use MAP3190 to determine resolution. Response: 2D29-9027 Explanation: Disk Array is or would become degraded and parity data is out of synchronization. Use MAP3113 to determine resolution. Response: Power Systems: IBM Flex System p270 Compute Node Installation and Service Guide...
Page 437 2D29-9028 • 2D29-9050 2D29-9028 Explanation: Maximum number of functional Disk Arrays has been exceeded. Use MAP3190 to determine resolution. Response: 2D29-9029 Explanation: Maximum number of functional Disk Arrays disks has been exceeded. Use MAP3190 to determine resolution. Response: 2D29-9030 Explanation: Disk Array is degraded due to missing/failed disk. Use MAP3110 to determine resolution. Response: 2D29-9031 Explanation: Automatic reconstruction initiated for Disk Array.
Page 438 Explanation: Maximum number of functional Disk Arrays has been exceeded. Use MAP3190 to determine resolution. Response: 2D29-9073 Explanation: Multiple controllers connected in an invalid configuration. Use MAP3140 to determine resolution. Response: Power Systems: IBM Flex System p270 Compute Node Installation and Service Guide...
Page 439 2D29-9074 • 2D29-9092 2D29-9074 Explanation: Multiple controllers not capable of similar functions or controlling same set of devices. Use MAP3141 to determine resolution. Response: 2D29-9075 Explanation: Incomplete multipath connection between controller and remote controller. Use MAP3149 to determine resolution. Response: 2D29-9076 Explanation: Missing remote controller.
Page 440 Explanation: Temporary device bus error. Replace the FRU identified by diagnostics. Response: Failing Item: v FFC_722 2D29-FFFE Explanation: Temporary device bus error. Use MAP3150 to determine resolution. Response: Power Systems: IBM Flex System p270 Compute Node Installation and Service Guide...
Page 441: A00-Ff0 Through A24-Xxx Srns
A24-000 • A24-XXX A00-FF0 through A24-xxx SRNs: The AIX operating system might generate service request numbers (SRNs) from A00-FF0 to A24-xxx. Note: Some SRNs in this sequence might have 4 rather than 3 digits after the dash (–). Table 11 shows the meaning of an x in any of the following SRNs, such as A01-00x. Table 11.
Page 442 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 p270 Compute Node Installation and Service Guide...
Page 443 SSSS-108 • SSSS-114 SSSS-108 Explanation: The bus test failed. 1. Check the BladeCenter management-module event log. If an error was recorded by the system, see POST progress codes (checkpoints). 2. Replace any parts reported by the diagnostic program. 3. Replace the system board and chassis assembly, as described in Replacing the system-board and chassis assembly. Response: Failing Item: v FFC_SSSS...
Page 444 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 p270 Compute Node Installation and Service Guide...
Page 445 SSSS-122 • SSSS-128 SSSS-122 Explanation: A SCSD reservation conflict error. 1. Check the BladeCenter management-module event log. If an error was recorded by the system, see POST progress codes (checkpoints). 2. Replace any parts reported by the diagnostic program. 3. Replace the system board and chassis assembly, as described in Replacing the system-board and chassis assembly. Response: Failing Item: v FFC_SSSS...
Page 446 2. Replace any parts reported by the diagnostic program. 3. Replace the system board and chassis assembly, as described in Replacing the system-board and chassis assembly. Response: Failing Item: v FFC_252B v SOFTWARE Power Systems: IBM Flex System p270 Compute Node Installation and Service Guide...
Page 447 SSSS-135 • SSSS-137 SSSS-135 Explanation: The device failed to configure. 1. Check the BladeCenter management-module event log. If an error was recorded by the system, see POST progress codes (checkpoints). 2. Replace any parts reported by the diagnostic program. 3. Replace the system board and chassis assembly, as described in Replacing the system-board and chassis assembly. Response: Failing Item: v FFC_SSSS...
Page 448 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 p270 Compute Node Installation and Service Guide...
Page 449: Failing Function Codes
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 450 IBM Flex System 8-port 10 Gb converged adapter 2E37 IBM Flex System 4-port 10 Gb Ethernet adapter 2E3D IBM Flex System 4-port 1 Gb Ethernet adapter 2E52 IBM Flex System 8-port 10 Gb converged adapter Power Systems: IBM Flex System p270 Compute Node Installation and Service Guide...
Page 451: Controller Maintenance Analysis Procedures
Controller maintenance analysis procedures: These procedures are intended to resolve adapter, cache, or disk array problems associated with a controller. See “Service request numbers (SRNs)” on page 292 to identify which MAP to use. MAP 3110: Perform MAP 3110 in the Systems Hardware information center. MAP 3111: Perform MAP 3111 in the Systems Hardware information center.
Page 452 Perform MAP 3143 in the Systems Hardware information center. MAP 3144: Perform MAP 3144 in the Systems Hardware information center. MAP 3145: Perform MAP 3145 in the Systems Hardware information center. MAP 3146: Power Systems: IBM Flex System p270 Compute Node Installation and Service Guide...
Page 453: Error Logs
The following table shows the syntax of a nine-word B700xxxx system reference code (SRC) as it might be displayed in the event log of the IBM Chassis Management Module (CMM). Additional information for the event can be viewed by clicking more... in the message field.
Page 454: Checkout Procedure
For intermittent problems, check the management-module event log and “POST progress codes (checkpoints)” on page 224. 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 484.
Page 455 Select the resources to be tested and record any SRNs. Then go to “Service request numbers (SRNs)” on page 292. This ends the Linux procedure. For more information about installing and using all supported operating systems, search the IBM Support website. Chapter 8. Troubleshooting...
Page 456: Verifying The Partition Configuration
Stop all programs, and then shut down the operating system and shut down the compute node. See the documentation that comes with your operating system documentation for information about shutting down the operating system. Power Systems: IBM Flex System p270 Compute Node Installation and Service Guide...
Page 457: Starting Stand-Alone Diagnostics From A Nim Server
4. Turn on the compute node and establish a Serial over LAN (SOL). For information about starting an SOL session, see the IBM Chassis Management Module Command-Line Interface Reference Guide. Note: It can take several minutes to load the stand-alone diagnostics from the CD or flash drive.
Page 458: Using The Diagnostics Program
2. If the system is running in a full-machine partition, turn on the compute node and establish a Serial over LAN (SOL) session. For information about starting an SOL session, see the IBM Chassis Management Module Command-Line Interface Reference Guide.
Page 459: Boot Problem Resolution
Procedure 1. Make sure that your boot list is correct. a. Use the management console to display the boot sequences for the compute nodes in your IBM Flex System Enterprise Chassis. b. Find your compute node on the list that is displayed and make sure that the device from which you are attempting to boot is the first device in the boot sequence.
Page 460: Troubleshooting By Symptom
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 p270 Compute Node,” on page 95 to determine which components are CRUs and which components are FRUs.
Page 461 Follow the suggested actions in the order in which they are listed in the Action column until the problem is solved. v See Chapter 7, “Parts listing for IBM Flex System p270 Compute Node,” on page 95 to determine which components are CRUs and which components are FRUs.
Page 462: Connectivity Problems
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 p270 Compute Node,” on page 95 to determine which components are CRUs and which components are FRUs.
Page 463 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 p270 Compute Node,” on page 95 to determine which components are CRUs and which components are FRUs.
Page 464 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 p270 Compute Node,” on page 95 to determine which components are CRUs and which components are FRUs.
Page 465: Pci Expansion Card (Piocard) Problem Isolation Procedure
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 p270 Compute Node,” on page 95 to determine which components are CRUs and which components are FRUs.
Page 466: Hypervisor Problems
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 p270 Compute Node,” on page 95 to determine which components are CRUs and which components are FRUs.
Page 467 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 p270 Compute Node,” on page 95 to determine which components are CRUs and which components are FRUs.
Page 468 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 p270 Compute Node,” on page 95 to determine which components are CRUs and which components are FRUs.
Page 469: Service Processor Problems
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 p270 Compute Node,” on page 95 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 p270 Compute Node,” on page 95 to determine which components are CRUs and which components are FRUs.
Page 471 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 p270 Compute Node,” on page 95 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 p270 Compute Node,” on page 95 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 p270 Compute Node,” on page 95 to determine which components are CRUs and which components are FRUs.
Page 474 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 p270 Compute Node,” on page 95 to determine which components are CRUs and which components are FRUs.
Page 475 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 p270 Compute Node,” on page 95 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 p270 Compute Node,” on page 95 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 p270 Compute Node,” on page 95 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 p270 Compute Node,” on page 95 to determine which components are CRUs and which components are FRUs.
Page 479 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 p270 Compute Node,” on page 95 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 p270 Compute Node,” on page 95 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 p270 Compute Node,” on page 95 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 p270 Compute Node,” on page 95 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 p270 Compute Node,” on page 95 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 p270 Compute Node,” on page 95 to determine which components are CRUs and which components are FRUs.
Page 485: Software Problems
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 p270 Compute Node,” on page 95 to determine which components are CRUs and which components are FRUs.
Page 486: Viewing The Light Path Diagnostic Leds
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 487 Figure 53. LED locations on the system board of the IBM Flex System p270 Compute Node The following table identifies the light path diagnostic LEDs. Table 17. IBM Flex System p270 Compute Node LEDs Callout Unit LEDs 3 V lithium battery LED...
Page 488: Light Path Diagnostics 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 p270 Compute Node,” on page 95 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 p270 Compute Node,” on page 95 to determine which components are CRUs and which components are FRUs.
Page 490: Isolating Firmware Problems
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 p270 Compute Node Installation and Service Guide...
Page 491: Restore Vfchost Map Data
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.
Page 492: Recovering The System Firmware
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 p270 Compute Node Installation and Service Guide...
Page 493: Recovering The Temp Image From The Perm Image
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.
Page 494: Committing The Temp System Firmware 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.
Page 495: Solving Shared Network Connection Problems
3. Verify that the installation of the I/O-module type is supported by the IBM Flex System Enterprise Chassis and compute node hardware. 4. Verify that the I/O modules for the network interface are installed in the correct bays of the IBM Flex System Enterprise Chassis.
Page 496: Solving Shared Power Problems
IBM Flex System Enterprise Chassis. About this task v If all of the compute nodes have the same symptom, it is probably a problem in the IBM Flex System Enterprise Chassis.
Page 497 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 498 Power Systems: IBM Flex System p270 Compute Node Installation and Service Guide...
Page 499: Appendix. Notices
All statements regarding the manufacturer's future direction or intent are subject to change or withdrawal without notice, and represent goals and objectives only. The manufacturer's prices shown are the manufacturer's suggested retail prices, are current and are subject to change without notice. Dealer prices may vary. © Copyright IBM Corp. 2013, 2015...
Page 500: Trademarks
IBM, the IBM logo, and ibm.com are trademarks or registered trademarks of International Business Machines Corp., registered in many jurisdictions worldwide. Other product and service names might be trademarks of IBM or other companies. A current list of IBM trademarks is available on the Web at Copyright and trademark information at www.ibm.com/legal/copytrade.shtml.
Page 501: Electronic Emission Notices
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 502 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 p270 Compute Node Installation and Service Guide...
Page 503 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 504 Um dieses sicherzustellen, sind die Geräte wie in den Handbüchern beschrieben zu installieren und zu betreiben. Des Weiteren dürfen auch nur von der IBM empfohlene Kabel angeschlossen werden. IBM übernimmt keine Verantwortung für die Einhaltung der Schutzanforderungen, wenn das Produkt ohne Zustimmung von IBM verändert bzw.
Page 505: Class B Notices
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 506 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 507 Um dieses sicherzustellen, sind die Geräte wie in den Handbüchern beschrieben zu installieren und zu betreiben. Des Weiteren dürfen auch nur von der IBM empfohlene Kabel angeschlossen werden. IBM übernimmt keine Verantwortung für die Einhaltung der Schutzanforderungen, wenn das Produkt ohne Zustimmung von IBM verändert bzw.
Page 508: Terms And Conditions
Permissions for the use of these publications are granted subject to the following terms and conditions. Applicability: These terms and conditions are in addition to any terms of use for the IBM website. Personal Use: You may reproduce these publications for your personal, noncommercial use provided that all proprietary notices are preserved.
Page 509 Appendix. Notices...
Page 510 IBM® Printed in USA...

IBM Flex System p270 Compute Node Installation And Service Manual

Chapter 1. Introduction

Chapter 2. Power, Controls, Indicators, and Connectors

Chapter 3. Configuring the Compute Node

Chapter 4. Installing the Operating System

Chapter 5. Accessing the Service Processor

Chapter 6. Installing and Removing Components

Chapter 7. Parts Listing for IBM Flex System P270 Compute Node

Chapter 8. Troubleshooting

Appendix. Notices

Quick Links

Troubleshooting

Related Manuals for IBM Flex System p270 Compute Node

Summary of Contents for IBM Flex System p270 Compute Node

Table of Contents