1. DL manuals
  2. IBM
  3. Server
  4. Redbooks x3850 X5
  5. Problem Determination And Service Manual

IBM Redbooks x3850 X5 Problem Determination And Service Manual

Other manuals for Redbooks x3850 X5: Installation And User Manual, Product Manual
Manual is about: Types 7145, 7146, 7143, and 7191

Summary of Redbooks x3850 X5

  • Page 1

    Ibm system x3850 x5 and x3950 x5 types 7145, 7146, 7143, and 7191 problem determination and service guide.

  • Page 3

    Ibm system x3850 x5 and x3950 x5 types 7145, 7146, 7143, and 7191 problem determination and service guide.

  • Page 4

    Note before using this information and the product it supports, read the general information in “notices” on page 1031, the safety information and environmental notices and user guide documents on the ibm documentation cd, and the warranty information document that comes with the product. Nineteenth...

  • Page 5

    Contents safety . . . . . . . . . . . . . . . V guidelines for trained service technicians . . . . Vii inspecting for unsafe conditions . . . . . . Vii guidelines for servicing electrical equipment viii safety statements . . . . . . . . . . . . Ix chapter 1. Start here . . . . . . . . . 1 diagnosing...

  • Page 6

    Removing and replacing the memory expansion module components . . . . . . . . . . . 176 removing and replacing memory expansion module tier 1 crus . . . . . . . . . . 176 removing and replacing memory expansion module tier 2 crus . . . . . . . . . . 197 chapter 6. Configuration information and instr...

  • Page 7

    Safety before installing this product, read the safety information. Antes de instalar este produto, leia as informações de segurança. Læs sikkerhedsforskrifterne, før du installerer dette produkt. Lees voordat u dit product installeert eerst de veiligheidsvoorschriften. Ennen kuin asennat tämän tuot...

  • Page 8

    Les sikkerhetsinformasjonen (safety information) før du installerer dette produktet. Antes de instalar este produto, leia as informações sobre segurança. Antes de instalar este producto, lea la información de seguridad. Läs säkerhetsinformationen innan du installerar den här produkten. Bu ürünü kurm...

  • Page 9

    Guidelines for trained service technicians this section contains information for trained service technicians. Inspecting for unsafe conditions use this information to help you identify potential unsafe conditions in an ibm ® product that you are working on. Each ibm product, as it was designed and m...

  • Page 10

    Guidelines for servicing electrical equipment observe these guidelines when you service electrical equipment. V check the area for electrical hazards such as moist floors, nongrounded power extension cords, and missing safety grounds. V use only approved tools and test equipment. Some hand tools hav...

  • Page 11

    Safety statements these statements provide the caution and danger information that is used in this documentation. Important: each caution and danger statement in this documentation is labeled with a number. This number is used to cross reference an english-language caution or danger statement with t...

  • Page 12

    Statement 2 caution: when replacing the lithium battery, use only ibm part number 15f8409 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 cont...

  • Page 13

    Danger some laser products contain an embedded class 3a or class 3b laser diode. Note the following. Laser radiation when open. Do not stare into the beam, do not view directly with optical instruments, and avoid direct exposure to the beam. Class 1 laser product laser klasse 1 laser klass 1 luokan ...

  • Page 14

    Statement 8 caution: never remove the cover on a power supply or any part that has the following label attached. Hazardous voltage, current, and energy levels are present inside any component that has this label attached. There are no serviceable parts inside these components. If you suspect a probl...

  • Page 15

    Danger overloading a branch circuit is potentially a fire hazard and a shock hazard under certain conditions. To avoid these hazards, ensure that your system electrical requirements do not exceed branch circuit protection requirements. Refer to the information that is provided with your device for e...

  • Page 16

    Caution: hazardous moving parts are nearby. Statement 37 danger when you populate a rack cabinet, adhere to the following guidelines: v always lower the leveling pads on the rack cabinet. V always install the stabilizer brackets on the rack cabinet. V always install the heaviest devices in the botto...

  • Page 17

    Chapter 1. Start here you can solve many problems without outside assistance by following the troubleshooting procedures in this documentation and on the world wide web. This document describes the diagnostic tests that you can perform, troubleshooting procedures, and explanations of error messages ...

  • Page 18

    A. Install updatexpress system updates. You can install code updates that are packaged as an updatexpress system pack or updatexpress cd image. An updatexpress system pack contains an integration-tested bundle of online firmware and device-driver updates for your server. In addition, you can use ibm...

  • Page 19

    A single problem might cause multiple symptoms. Follow the troubleshooting procedure for the most obvious symptom. If that procedure does not diagnose the problem, use the procedure for another symptom, if possible. If the problem remains, contact ibm or an approved warranty service provider for ass...

  • Page 20

    4 ibm system x3850 x5 and x3950 x5 types 7145, 7146, 7143, and 7191: problem determination and service guide.

  • Page 21

    Chapter 2. Introduction this topic provides a brief introduction to the ibm system x3850 x5 and x3950 x5 types 7145, 7146, 7143, and 7191. This information supports your ibm system x3850 x5 and x3950 x5 types 7145 and 7146 server and the optional ibm max5 for system x (max5) memory expansion module....

  • Page 22

    Related documentation in addition to this document, the following documentation also comes with the server: v installation and user's guide this document is in portable document format (pdf) on the ibm documentation cd. It provides general information about setting up and cabling the server, includi...

  • Page 23

    Notices and statements in this document the caution and danger statements in this document are also in the multilingual safety information document, which is on the ibm documentation cd. Each statement is numbered for reference to the corresponding statement in your language in the safety informatio...

  • Page 24

    Table 1. Features and specifications microprocessor: v intel xeon ex versions of the 6000 and 7000 series or e7 series multi-core microprocessor with up to 24 mb or 30 mb last level cache. V 1066 mhz front-side bus (fsb) v support for up to four microprocessors – four quick path interconnect (qpi) l...

  • Page 25

    Table 2. Features and specifications (continued) scalability and memory expansion: v eight-socket scalability option uses 4 qpi external cables v multi-node configurations require 4 microprocessors in each node v max5 memory expansion module option uses four qpi ports note: when you add an optional ...

  • Page 26

    Noise levels (the declared a-weighed sound power level of the server) see acoustical noise emissions. Test voltage and frequency: 230v / 50 hz or 60 hz total harmonic distortion of the electricity supply system: the maximum harmonic content of the input voltage waveform will be equal or less than 2%...

  • Page 27

    Table 3. X3850 x5 memory ras features (continued) nodes hemisphere mode (dimm configuration match between both cpu memory controllers) (note 1) memory mirroring (note 2) dimm sparing (2 dimms spare per memory card) (note 3) dddc sparing (1 x4 dram spare per dimm pair) (note 4) rbs sparing (1 x4 dram...

  • Page 28

    2. Memory mirroring (cpu and max5 mirroring is conditionally supported as described below.) a. Cpu "instrasocket" mirroring is supported: the memory controlled by one cpu memory controller is mirrored to the memory controlled by the second memory controller of the same cpu. B. Each of the two mirror...

  • Page 29

    C. Automatically enabled if above requirements are met. D. Not affected by the "memory sparing" setting in uefi setup e. Rbs is an exa chipset function and is only supported in max5. 6. Rank sparing (not supported) 7. Hot-swap memory (not supported) 8. Refer to the ibm ex5 portfolio overview: "ibm s...

  • Page 30

    Hard disk drive activity led: when this led is flashing, it indicates that the drive is in use. Hard disk drive status led: on some server models, each hot-swap hard disk drive has a status led. When this led is lit, it indicates that the drive has failed. If an optional ibm serveraid controller is ...

  • Page 31

    Platform module (tpm). Press this button to turn on or turn off this led locally. You can use ibm systems director to light this led remotely. In a two-node configuration, this led is lit on the primary server and flashes on the secondary server during post. You can press this button or use an ipmi ...

  • Page 32

    Checkpoint code display v remind button: this button places the system-error led on the front panel into remind mode. In remind mode, the system-error led flashes once every 2 seconds until the problem is corrected, the server is restarted, or a new problem occurs. By placing the system-error led in...

  • Page 33

    System-management ethernet connector: use this connector to connect the server integrated management module (imm) to a network. The imm is used for systems-management and information control. This connector is used only by the imm. Qpi ports 1 - 4: in a single-node configuration, use these connector...

  • Page 34

    Ac dc ! Ac dc ! Ac power led (green) dc power led (green) error led (amber) ac dc ! Ac dc ! Qpi link 1 led qpi link 2 led qpi link 3 led qpi link 4 led power on led system error led locator led a thumbscrew is in this position only when a 2-node lock bracket is installed (2-node scalability kit opti...

  • Page 35

    Table 4. Qpi link leds (continued) link leds number of nodes qpi wrap card or cable status blinking 1 to 4 server(s) operating at reduced capacity locator led: use this led to visually locate the server among other servers. You can use ibm systems director to light this led remotely. In a two-node c...

  • Page 36

    Table 5. Power-supply leds (continued) power-supply leds description action notes ac dc error on off off power supply not fully seated, faulty system board, or faulty power supply 1. Reseat the power supply. 2. If the system-board error led is off, replace the power supply. 3. (trained service techn...

  • Page 37

    Note: some memory is reserved for various system resources and is unavailable to the operating system. The amount of memory that is reserved for system resources depends on the operating system, the configuration of the server, and the configured pci options. Turning off the server this topic provid...

  • Page 38

    Internal leds, connectors, and jumpers this topic provides general information about internal leds, connectors, and jumpers. The following illustrations show the connectors, leds, and jumpers on the internal boards. The illustrations might differ slightly from your hardware. Memory-card dimm connect...

  • Page 39

    Memory-card leds and button this topic provides an illustration that shows the leds on a memory card. The following illustration shows the leds on a memory card. Note: if the memory card is removed from the server, you must press the light path diagnostics button to light the led. Dimm 1 error led d...

  • Page 40

    Microprocessor-board connectors this topic provides an illustration of the connectors on the microprocessor board. The following illustration shows the connectors on the microprocessor board. Scalability link scalability link i/o board power i/o board pcie2 x8 connector for sas raid card fan 3 sas b...

  • Page 41

    Microprocessor 1 error led microprocessor 2 error led microprocessor 3 error led microprocessor 4 error led system management heartbeat led microprocessor board error led memory card connector 7 “microprocessor-board leds” on page 24 describes the function of each status led. Table 7. Microprocessor...

  • Page 42

    I/o-board connectors this topic provides an illusration that shows the connectors on the i/o board. The following illustration shows the connectors on the i/o board. Pcie2 x8 slot 7 slot 6 pcie2 x8 slot 5 pcie2 x8 slot 4 pcie2 x8 slot 1 pcie2 x16 slot 3 pcie2 x8 slot 2 pcie2 x8 (x4 electrically) eth...

  • Page 43

    Slot 7 error led i/o board error led slot 6 error led slot 5 error led slot 4 error led slot 3 error led slot 2 error led slot 1 error led power fault led “i/o-board leds” on page 26 describes the function of each non-light path diagnostics status led. Table 8. I/o-board non-light-path-diagnostics s...

  • Page 44

    Wake on lan bypass (j31) 1 2 3 password override (j29) 1 2 3 1 2 3 boot recovery (j22) “i/o-board jumpers” on page 27 describes the function of each jumper block. Table 9. I/o-board jumper blocks jumper name description wake on lan bypass (j31) the default position is pins 1 and 2. Move the jumper t...

  • Page 45

    Sas-backplane connectors this topic provides an illustration that shows the connectors on the sas backplane. The following illustration shows the connectors on the sas backplane. Sas signal connector sas signal connector sas power connector sas power connector cofiguration connector cofiguration con...

  • Page 46

    Table 10. Memory expansion module features and operating specifications v intel 7500 or 7510 scalable memory buffer (depending on your model) with eight memory ports (four dimms on each port) v xcellerated memory technology v exa5 chip set v quickpath interconnect (qpi) architecture technology: – fo...

  • Page 47

    Table 10. Memory expansion module features and operating specifications (continued) acoustical noise emissions: for maximum system configurations (32 dimms installed) v sound power (idling): 6.2 bels v sound power (operating): 6.8 bels size: v height: 4.4 cm (1.73 in.) v depth: 72.4 cm (28.5 in.) v ...

  • Page 48

    Memory expansion module indicators, leds, and power this topic discusses memory expansion module indicators, leds, and power. This section describes the indicators and light-emitting diodes (leds) on the front and rear of the ibm max5 for system x memory expansion module. Front view this topic provi...

  • Page 49

    Rear view this topic discusses the indicators on the rear of the ibm max5 for system x memory expansion module, the following illustration shows the indicators on the rear of the ibm max5 for system x memory expansion module: power-on led locate led system error led ac led (green) dc led (green) pow...

  • Page 50

    Turning the memory expansion module on and off this topic explains how to turn the memory expansion module on and off. Because the memory expansion module is controlled by the server, turning on the memory expansion module refers to connecting the memory expansion module power cord into the power so...

  • Page 51

    Power supply 2 connector power supply 1 connector supercap (capacitor) turn-on leds button information panel connector 5-drop fan cable connector dimm connectors 17 - 24 dimm connectors 1 - 4 dimm connectors 13 - 16 dimm connectors 5 - 12 dimm connectors 25 - 32 chapter 2. Introduction 35.

  • Page 52

    36 ibm system x3850 x5 and x3950 x5 types 7145, 7146, 7143, and 7191: problem determination and service guide.

  • Page 53

    Chapter 3. Diagnostics this topic provides general information about diagnostic tools to help resolve issues with the server. This chapter describes the diagnostic tools that are available to help you solve problems that might occur in the server. If you cannot diagnose and correct a problem by usin...

  • Page 54

    Ibm service. Also, it can collect and transmit system configuration information on a scheduled basis so that the information is available to you and your support representative. It uses minimal system resources, is available free of charge, and can be downloaded from the web. For more information an...

  • Page 55

    Viewing event logs through the setup utility this topic provides instructions on how to view event logs using the setup utility. About this task to view the post event log or system-event log, complete the following steps: procedure 1. Turn on the server. 2. When the prompt setup is displayed, press...

  • Page 56

    The following table describes the methods that you can use to view the event logs, depending on the condition of the server. The first two conditions generally do not require that you restart the server. Table 11. Methods for viewing event logs condition action the server is not hung and is connecte...

  • Page 57

    Microprocessor socket. See “microprocessor problems” on page 49 for information about diagnosing microprocessor problems. V before you run the diagnostic programs, you must determine whether the failing server is part of a shared hard disk drive cluster (two or more servers sharing external storage ...

  • Page 58

    F. Turn on all external devices. G. Turn on the server. If the server does not start, see “troubleshooting tables.” h. Check the system-error led on the operator information panel. If it is flashing, check the light path diagnostics leds (see “light path diagnostics” on page 57). I. Check for the fo...

  • Page 59

    Cd or dvd drive problems this topic provides a list of suggested actions to take when you have problems with the cd or dvd drive. About this task v follow the suggested actions in the order in which they are listed in the action column until the problem is solved. V see chapter 4, “parts listing, ty...

  • Page 60

    Embedded hypervisor problems this topic provides suggested actions for correcting problems with the embedded hypervisor. About this task v follow the suggested actions in the order in which they are listed in the action column until the problem is solved. V see chapter 4, “parts listing, types 7145,...

  • Page 61

    Hard disk drive problems this topic provides a list of suggested actions for problems with the hard disk drive. About this task v follow the suggested actions in the order in which they are listed in the action column until the problem is solved. V see chapter 4, “parts listing, types 7145, 7146, 71...

  • Page 62

    Usb keyboard, mouse, or pointing-device problems this topic provides suggested actions to resolve problems with the usb keyboard, mouse, or pointing device attached to the server. About this task v follow the suggested actions in the order in which they are listed in the action column until the prob...

  • Page 63

    Memory problems this topic provides a list of suggestion actions to help resolve problems with memory that is displayed on the server. Chapter 3. Diagnostics 47.

  • Page 64

    About this task v follow the suggested actions in the order in which they are listed in the action column until the problem is solved. V see chapter 4, “parts listing, types 7145, 7146, 7143, and 7191,” on page 81 to determine which components are customer replaceable units (cru) and which component...

  • Page 65

    Microprocessor problems this topic explores a list of possible solutions for problems with the primary microprocessor on the server. About this task v follow the suggested actions in the order in which they are listed in the action column until the problem is solved. V see chapter 4, “parts listing,...

  • Page 66

    Monitor or video problems this topic provides possible symptoms and solutions for problems with the monitor. About this task if you suspect a problem with your monitor, see the documentation that comes with the monitor for instructions for testing and adjusting the monitor. If you cannot diagnose th...

  • Page 67

    V follow the suggested actions in the order in which they are listed in the action column until the problem is solved. V see chapter 4, “parts listing, types 7145, 7146, 7143, and 7191,” on page 81 to determine which components are customer replaceable units (cru) and which components are field repl...

  • Page 68

    Optional-device problems this topic provides a list of symptoms and suggestions for resolving problems with optional devices. About this task v follow the suggested actions in the order in which they are listed in the action column until the problem is solved. V see chapter 4, “parts listing, types ...

  • Page 69

    Power problems this topic provides possible solutions to problems with the power or power button on the server. About this task v follow the suggested actions in the order in which they are listed in the action column until the problem is solved. V see chapter 4, “parts listing, types 7145, 7146, 71...

  • Page 70

    V follow the suggested actions in the order in which they are listed in the action column until the problem is solved. V see chapter 4, “parts listing, types 7145, 7146, 7143, and 7191,” on page 81 to determine which components are customer replaceable units (cru) and which components are field repl...

  • Page 71

    Serial-device problems this topic provides suggested actions to take to solve problems with serial devices. About this task v follow the suggested actions in the order in which they are listed in the action column until the problem is solved. V see chapter 4, “parts listing, types 7145, 7146, 7143, ...

  • Page 72

    V follow the suggested actions in the order in which they are listed in the action column until the problem is solved. V see chapter 4, “parts listing, types 7145, 7146, 7143, and 7191,” on page 81 to determine which components are customer replaceable units (cru) and which components are field repl...

  • Page 73

    Universal serial bus (usb) port problems this topic provides possible solutions to problems with usb devices. About this task v follow the suggested actions in the order in which they are listed in the action column until the problem is solved. V see chapter 4, “parts listing, types 7145, 7146, 7143...

  • Page 74

    Before you work inside the server to view light path diagnostics leds, read the safety information that begins with “safety” on page v and “handling static-sensitive devices” on page 100. 58 ibm system x3850 x5 and x3950 x5 types 7145, 7146, 7143, and 7191: problem determination and service guide.

  • Page 75

    If an error occurs, view the light path diagnostics leds in the following order: 1. Check the operator information panel on the front of the server. V if the information led is lit, it indicates that there is a suboptimal condition in the server. V if the system-error led is lit, it indicates that a...

  • Page 76

    The following illustration shows the leds on the microprocessor board. Microprocessor 1 error led microprocessor 2 error led microprocessor 3 error led microprocessor 4 error led system management heartbeat led microprocessor board error led memory card connector 7 note: a. You must remove the memor...

  • Page 77

    The following illustration shows the leds on a memory card. Note: you can view the led on top of the memory card while the card is in the server. When you remove the memory card from the server, you must press the light path diagnostics button on the card to relight the leds to identify the error. D...

  • Page 78

    The following illustration shows the leds on the i/o board. Slot 7 error led i/o board error led slot 6 error led slot 5 error led slot 4 error led slot 3 error led slot 2 error led slot 1 error led power fault led remind button this topic provides a description of the remind button. You can use the...

  • Page 79

    In multi-node configurations, you can also press this button during startup to start the server as a stand-alone server. Light path diagnostics leds this topic provides a table that describes the leds on the light path diagnostics panel. The following table describes the leds on the light path diagn...

  • Page 80

    V follow the suggested actions in the order in which they are listed in the action column until the problem is solved. V see chapter 4, “parts listing, types 7145, 7146, 7143, and 7191,” on page 81 to determine which components are customer replaceable units (cru) and which components are field repl...

  • Page 81

    V follow the suggested actions in the order in which they are listed in the action column until the problem is solved. V see chapter 4, “parts listing, types 7145, 7146, 7143, and 7191,” on page 81 to determine which components are customer replaceable units (cru) and which components are field repl...

  • Page 82

    V follow the suggested actions in the order in which they are listed in the action column until the problem is solved. V see chapter 4, “parts listing, types 7145, 7146, 7143, and 7191,” on page 81 to determine which components are customer replaceable units (cru) and which components are field repl...

  • Page 83

    V follow the suggested actions in the order in which they are listed in the action column until the problem is solved. V see chapter 4, “parts listing, types 7145, 7146, 7143, and 7191,” on page 81 to determine which components are customer replaceable units (cru) and which components are field repl...

  • Page 84

    V follow the suggested actions in the order in which they are listed in the action column until the problem is solved. V see chapter 4, “parts listing, types 7145, 7146, 7143, and 7191,” on page 81 to determine which components are customer replaceable units (cru) and which components are field repl...

  • Page 85

    Power-supply leds this topic provides information about power-supply leds. The following minimum configuration is required for the dc leds on the power supply to be lit: v ac power source v power cord connected v power supply with ac power present led on v i/o board with power supply connections v m...

  • Page 86

    The following illustration shows the locations of the power-supply leds. Ac dc ! Ac power led (green) dc power led (green) error led (amber) the following table describes the problems that are indicated by various combinations of the power-supply leds and the power-on led on the operator information...

  • Page 87

    V follow the suggested actions in the order in which they are listed in the action column until the problem is solved. V see chapter 4, “parts listing, types 7145, 7146, 7143, and 7191,” on page 81 to determine which components are customer replaceable units (cru) and which components are field repl...

  • Page 88

    1. In a multi-node environment, each server has a unique dsa interface. You can view server-specific information, such as error logs, from these unique dsa interfaces. 2. Before using dsa in a multi-node configuration, you must disable extended apic (x2apic). (to disable apic, go to the uefi setup, ...

  • Page 89

    If you are unable to restart the server or if you need comprehensive diagnostics, use dsa preboot. Running dsa preboot this topic provides steps for how to run dsa preboot. To run dsa preboot, complete the following steps: 1. If the server is running, turn off the server and all attached devices. 2....

  • Page 90

    In-band automatic recovery method this topic provides information about the in-band automatic recovery method, as well as instructions for how to recover the uefi firmware and restore the server operation to the primary bank. If the integrated management module (imm) detects a problem with the uefi ...

  • Page 91

    Out-of-band method for information about using the imm web interface to recover the uefi firmware, see the imm documentation. Nx boot failure this topic provides information about nx boot failure. Configuration changes, such as added devices or adapter firmware updates, and firmware or application c...

  • Page 92

    6. Connect the power cord to the server and check if the imm is recovered. System-event log this topic provides information about the types of messages contained in the system-event log. The system-event log contains messages of three types: information information messages do not require action; th...

  • Page 93

    V check the lan activity led on the rear of the server. The lan activity led is lit when data is active on the ethernet network. If the lan activity led is off, make sure that the hub and network are operating and that the correct device drivers are installed. V check for operating-system-specific c...

  • Page 94

    V power cord v microprocessor board v one microprocessor v two 1 gb dimms on one memory card (if a memory expansion module is connected to the server, two 2 gb dimms on the memory expansion module.) 4. Turn on the server. If the problem remains, suspect the following components in the following orde...

  • Page 95

    V software versions and levels v diagnostic program type and version level v configuration option settings v operating-system control-file setup see appendix d, “getting help and technical assistance,” on page 1027 for information about calling ibm for service. Chapter 3. Diagnostics 79.

  • Page 96

    80 ibm system x3850 x5 and x3950 x5 types 7145, 7146, 7143, and 7191: problem determination and service guide.

  • Page 97

    Chapter 4. Parts listing, types 7145, 7146, 7143, and 7191 this topic provides information about parts for types 7145, 7146, 7143, and 7191. The following replaceable components are available for the system x3850 x5 and x3950 x5 types 7145, 7146, 7143, and 7191 except as specified otherwise in “repl...

  • Page 98

    12 21 18 20 1 3 4 5 6 7 8 11 13 14 16 17 19 23 24 25 27 26 28 29 33 10 30 31 2 9 15 32 34 7a 36 35 22 82 ibm system x3850 x5 and x3950 x5 types 7145, 7146, 7143, and 7191: problem determination and service guide.

  • Page 99

    Replaceable server components this topic provides a parts listing for all removable server components. Replaceable components are of four types: v consumable part: purchase and replacement of consumable parts (components, such as batteries and printer cartridges, that have depletable life) is your r...

  • Page 100

    Table 12. Parts listing, types 7143, 7145, 7146, and 7191 (continued) index description cru part number (tier 1) cru part number (tier 2) fru part number 15 hard disk drive, sata multiburner (models h1x h2x) 44w3256 15 hard disk drive, 600 gb 10k, 2.5-inch sas (models h1x, h2x, h3x) 49y2004 15 hard ...

  • Page 101

    Table 12. Parts listing, types 7143, 7145, 7146, and 7191 (continued) index description cru part number (tier 1) cru part number (tier 2) fru part number 29 dimm, 16 gb (optional) 49y1382 29 dimm, 4 gb (1.35v) pc3l-10600r-999 cl9 ddr3 ecc (types 7143 and 7191) 49y1425 29 dimm, 8 gb (1.35v) pc3l-8500...

  • Page 102

    Table 12. Parts listing, types 7143, 7145, 7146, and 7191 (continued) index description cru part number (tier 1) cru part number (tier 2) fru part number 31 microprocessor (intel xeon e7-8867l 2.13 ghz, 30m, 10-core, 105w - 8 socket) types 7143 and 7191 (optional) 69y1885 31 microprocessor (intel xe...

  • Page 103

    Table 12. Parts listing, types 7143, 7145, 7146, and 7191 (continued) index description cru part number (tier 1) cru part number (tier 2) fru part number 3800 nvidia quadro fx 3pci-ex 16 adapter (optional) 43v5894 1.28 tb iops mlc duo adapter for ibm system x 81y4529 640 gb high iops mlc adapter for...

  • Page 104

    Table 12. Parts listing, types 7143, 7145, 7146, and 7191 (continued) index description cru part number (tier 1) cru part number (tier 2) fru part number sas signal cable (all models except arx, 5dx) 46c4124 latches, eia 5u (models 2sx, 4dx, 4fx, 4sx, 5gx, 5sx) (for servers connected to a memory exp...

  • Page 105

    Table 13. Consumable parts description part number serveraid sas controller battery 43w4342 to order a consumable part, complete the following steps: 1. Go to http://www.Ibm.Com. 2. From products menu, click upgrades, accessories & parts . 3. Click obtain maintenance parts ; then, follow the instruc...

  • Page 106

    Replaceable memory expansion module components this topic provides a table that lists the replaceable components for the ibm max5 for system x memory expansion module. The following replaceable components are available for the ibm max5 for system x memory expansion module. The following illustration...

  • Page 107

    Table 14. Parts listing, memory expansion module (continued) index description cru part number (tier 1) cru part number (tier 2) fru part number 2 memory, 4 gb pc3-10600r-999 ddr3 ecc (models 2sx, 4sx, 4dx, 5sx) 44t1598 2 memory, 4 gb (1.35v) pc3l-10600r-999 cl9 ddr3 ecc (for memory expansion module...

  • Page 108

    Table 14. Parts listing, memory expansion module (continued) index description cru part number (tier 1) cru part number (tier 2) fru part number cable, exa scalability (optional) 40k6752 cma (models f1x, f2x, b8x, b9x) 49y4817 eia latches (models 2sx 4sx 5sx 4dx 4fx 5gx f1x f2x b8x b9x) 40k6765 fill...

  • Page 109

    Ibm power cord part number used in these countries and regions 39m5206 china 39m5102 australia, fiji, kiribati, nauru, new zealand, papua new guinea 39m5123 afghanistan, albania, algeria, andorra, angola, armenia, austria, azerbaijan, belarus, belgium, benin, bosnia and herzegovina, bulgaria, burkin...

  • Page 110

    Ibm power cord part number used in these countries and regions 39m5199 japan 39m5068 argentina, paraguay, uruguay 39m5226 india 39m5240 brazil product recovery cds this topic provides a list of product recovery cds. Table 15 describes the product recovery cd crus. Table 15. Product recovery cds desc...

  • Page 111

    Table 15. Product recovery cds (continued) description cru part number microsoft windows server 2008 r2 foundation, turkish 81y2009 microsoft windows server 2008 r2 foundation, japanese 81y2010 microsoft windows server 2008 r2 foundation, simplified chinese 81y2011 microsoft windows server 2008 r2 f...

  • Page 112

    96 ibm system x3850 x5 and x3950 x5 types 7145, 7146, 7143, and 7191: problem determination and service guide.

  • Page 113

    Chapter 5. Removing and replacing components replaceable components are of four types: v consumable part: purchase and replacement of consumable parts (components, such as batteries and printer cartridges, that have depletable life) is your responsibility. If ibm acquires or installs a consumable pa...

  • Page 114

    V observe good housekeeping in the area where you are working. Place removed covers and other parts in a safe place. V if you must start the server while the cover is removed, make sure that no one is near the server and that no tools or other objects have been left inside the server. V do not attem...

  • Page 115

    A single-power-supply server operating at 208 v ac this topic discusses a single-power-supply server operating at 208 v ac. One power supply operating at 208 v ac supports a fully populated server, but it does not support power or cooling redundancy. System reliability guidelines this topic provides...

  • Page 116

    V avoid dropping any metallic objects, such as paper clips, hairpins, and screws, into the server. Handling static-sensitive devices this topic provides instructions for how to handle static-sensitive devices. Attention: static electricity can damage the server and other electronic devices. To avoid...

  • Page 117

    Internal cable routing and connectors this topic provides illustraions of the internal cable routing and connectors. About this task the following illustration shows the routing of the dvd power, fans 1 and 2, scalability led, and operator information cables. Dvd power cable connector fan 1 cable co...

  • Page 118

    The following illustration shows the routing of the usb and dvd signal cables. Dvd signal cable usb cable 102 ibm system x3850 x5 and x3950 x5 types 7145, 7146, 7143, and 7191: problem determination and service guide.

  • Page 119

    The following illustration shows the cable routing of the sas signal cables from the solid state drive backplane to the serveraid adapter. Sas signal cables (2) chapter 5. Removing and replacing components 103.

  • Page 120

    Returning a device or component this topic provides information for returning a device.. If you are instructed to return a device or component, follow all packaging instructions, and use any packaging materials for shipping that are supplied to you. Connecting the cables this topic provides illustra...

  • Page 121

    Front view operator information panel usb connectors dvd-eject button hard disk drive activity led electrostatic-discharge connector dvd drive activity led hard disk drive status led scalability led removing and replacing server components this topic provides information about the four types of repl...

  • Page 122

    Removing the top cover this topic provides instructions for how to remove the top cover. About this task attention: operating the server for more than 2 minutes with the top cover removed might damage server components. For proper cooling and airflow, replace the top cover before you turn on the ser...

  • Page 123

    Replacing the top cover this topic provides instructions for how to install the top cover. About this task to install the top cover, complete the following steps: procedure 1. Make sure that all internal cables are correctly routed. 2. Set the cover on top of the server so that approximately 13 mm (...

  • Page 124

    Results latch latch replacing the top-cover bracket this topic provides instructions for how to replace the top-cover bracket. About this task to replace the top-cover bracket, complete the following steps: procedure 1. Make sure that all internal cables are correctly routed. 2. Align the top-cover ...

  • Page 125

    About this task note: you do not have to remove the top cover before you remove the bezel. To remove the bezel, complete the following steps: procedure 1. Read the safety information that begins with “safety” on page v and “installation guidelines” on page 97. 2. Press on the bezel retention tabs at...

  • Page 126

    Removing an adapter this topic provides instructions for how to remove a pci express adapter. About this task to remove a pci express adapter, complete the following steps. Adapter adapter retention latch pin pin hole expansion slot cover procedure 1. Read the safety information that begins with “sa...

  • Page 127

    3. Remove the top cover (see “removing and replacing consumable parts and tier 1 crus” on page 105). 4. Disconnect any cables from the adapter. 5. Lift the blue adapter retention latch up away from the server and open the tab. 6. Carefully grasp the adapter by its top edge or upper corners, and pull...

  • Page 128

    Removing the battery this topic provides instructions for how to remove the battery. About this task to remove the battery, complete the following steps: procedure 1. Read the safety information that begins with “safety” on page v and “installation guidelines” on page 97. 2. Turn off the server and ...

  • Page 129

    6. Remove the battery: a. Use one finger to push the battery horizontally out of its housing. B. Lift the battery from the socket. 7. Dispose of the battery as required by local ordinances or regulations. Replacing the battery this topic provides instructions for how to install the replacement batte...

  • Page 130

    3. Insert the new battery: a. Position the battery so that the positive (+) symbol is facing you. B. Place the battery into its socket, and press the battery toward the housing until it snaps into place. 4. Install the top cover (see “removing and replacing consumable parts and tier 1 crus” on page ...

  • Page 131

    Removing the dvd drive this topic provides instructions for how to remove the dvd drive. About this task to remove the dvd drive, complete the following steps: procedure 1. Read the safety information that begins with “safety” on page v and “installation guidelines” on page 97. 2. Turn off the serve...

  • Page 132

    Replacing the dvd drive this topic provides instructions for how to install the replacement dvd drive. About this task to install the replacement dvd drive, complete the following steps: procedure 1. Install the dvd bracket on the side of the new dvd drive. 2. Slide the dvd drive into the server unt...

  • Page 133

    Replacing a 1.8-inch solid state drive this topic provides instructions on how to install the replacement solid state drive. About this task to install the replacement solid state drive, complete the following steps: procedure 1. Remove the drive cage filler panel. 2. Slide the drive release latch t...

  • Page 134

    Procedure 1. Read the safety information that begins with “safety” on page v and “installation guidelines” on page 97. 2. Be sure to save the data on your drive, especially if it is part of a raid array, before you remove it from the server. 3. Push the latch on the handle to the left, then open the...

  • Page 135

    About this task to remove the operator information panel assembly, complete the following steps. Release latch procedure 1. Read the safety information that begins with “safety” on page v and “installation guidelines” on page 97. 2. Turn off the server and peripheral devices, and disconnect the powe...

  • Page 136

    Replacing the operator information panel assembly this topic provides instructions for how to install the replacement operator information panel assembly. About this task to install the replacement operator information panel assembly, complete the following steps: procedure 1. Connect the operator i...

  • Page 137

    3. Open the fan-release handle by pushing the orange release latch down. 4. Pull out on the free end of the handle to slide the fan out of the server. 5. If you are instructed to return the fan, follow all packaging instructions, and use any packaging materials for shipping that are supplied to you....

  • Page 138

    Replacing the front hot-swap fans this topic provides instructions for installing a replacement hot-swap fan. About this task to install a replacement hot-swap fan, complete the following steps: procedure 1. Open the fan-release handle to 90° on the replacement fan. 2. Slide the fan into the server,...

  • Page 139

    4. If you are instructed to return the fan, follow all packaging instructions, and use any packaging materials for shipping that are supplied to you. Replacing the middle hot-swap fan this topic provides instructions for how to install the replacement middle hot-swap fan. About this task to install ...

  • Page 140

    Removing a hot-swap power supply in a single-node server: about this task to remove a hot-swap power supply in a single-node server, complete the following steps. Power supply power supply handle release latch power supply handle procedure 1. Read the safety information that begins with “safety” on ...

  • Page 141

    Removing a hot-swap power supply in a 2-node server: this topic provides instructions for how to remove a hot-swap power supply in a 2-node server. About this task to remove a hot-swap power supply in a 2-node server, complete the following steps. Power supply handle release latch power supply handl...

  • Page 142

    Power supply handle release latch power supply handle power supply right power supply procedure 1. Read the safety information that begins with “safety” on page v and “installation guidelines” on page 97 note: if your server has only one power supply, you must turn off the server before you remove t...

  • Page 143

    Replacing the hot-swap power supply this topic provides instructions for how to install the replacement hot-swap power supply. About this task to install the replacement hot-swap power supply, complete the following steps: procedure 1. Touch the static-protective package that contains the power supp...

  • Page 144

    Procedure 1. Read the safety information that begins with “safety” on page v and “installation guidelines” on page 97. 2. Turn off the server and peripheral devices, and disconnect the power cords and all external cables as necessary. 3. Rotate the blue release latch on the handle and pull the handl...

  • Page 145

    4. If you are removing the battery from a serveraid sas controller in one of the rear i/o connectors, see “removing an adapter” on page 110 for controller removal instructions. 5. If you are removing the battery from the serveraid sas controller behind the hard disk drives, see “removing the raid ad...

  • Page 146

    That your server supports the memory card that you are installing, look at the label on the top of the memory card. If the label does not state that the memory card can be used only in machine types 7143 and 7191, the memory card can be used only in machine types 7145 and 7146. V the server supports...

  • Page 147

    Memory card 1 memory card 2 memory card 3 memory card 4 memory card 5 memory card 6 memory card 7 memory card 8 microprocessor 1 connector microprocessor 2 connector microprocessor 3 connector microprocessor 4 connector front of server v the following illustration shows the dimm connectors on a memo...

  • Page 148

    Table 17. Low-cost and low-power dimm installation sequence dimm pair installation order memory-card connector number dimm-connector numbers installed microprocessors first 1 1 and 8 1 and 4 second 7 1 and 8 third 1 3 and 6 fourth 7 3 and 6 fifth 1 2 and 7 sixth 7 2 and 7 seventh 1 4 and 5 eighth 7 ...

  • Page 149

    Table 19. High-performance memory-card installation sequence (continued) dimm pair installation order memory-card connector number dimm connector numbers fifteenth 4 3 and 6 sixteenth 6 3 and 6 seventeenth 1 2 and 7 eighteenth 7 2 and 7 nineteenth 3 2 and 7 twentieth 5 2 and 7 twenty-first 2 2 and 7...

  • Page 150

    Table 20. Memory-card installation sequence for memory-mirroring configuration (continued) dimm quad installation order memory-card connector number dimm connector numbers eighth 5 3 and 6 6 3 and 6 ninth 1 2 and 7 2 2 and 7 tenth 7 2 and 7 8 2 and 7 eleventh 3 2 and 7 4 2 and 7 twelfth 5 2 and 7 6 ...

  • Page 151

    The following illustration shows the leds that are on a memory card. Dimm 1 error led dimm 2 error led dimm 3 error led dimm 4 error led dimm 5 error led dimm 6 error led dimm 7 error led dimm 8 error led memory card only error led light path diagnostics button light path diagnostics button power le...

  • Page 152

    Removing a memory card: this topic provides instructions for how to remove a memory card. About this task at least one memory card with one pair of dimms must be installed for the server to operate correctly. To remove a memory card, complete the following steps. Release lever error led procedure 1....

  • Page 153

    6. If you are instructed to return the memory card, follow all packaging instructions, and use any packaging materials for shipping that are supplied to you. Replacing a memory card: this topic provides instructions to install a replacement memory card. About this task the intel 7500 scalable memory...

  • Page 154

    Dimm retaining clip procedure 1. Read the safety information that begins with “safety” on page v and “installation guidelines” on page 97. 2. Turn off the server and peripheral devices, and disconnect the power cords and all external cables as necessary. 3. Remove the top cover (see “removing and re...

  • Page 155

    4. Insert the dimm into the connector by aligning the edges of the dimm with the slots at the ends of the dimm connector. Firmly press both ends of the dimm straight down into the connector. The retaining clips snap into the locked position when the dimm is seated in the connector. Note: if there is...

  • Page 156

    Removing the internal flash memory this topic provides instructions for how to remove the internal flash memory (or hypervisor key). About this task to remove the internal flash memory (or hypervisor key), complete the following steps: procedure 1. Read the safety information that begins with “safet...

  • Page 157

    5. If you are instructed to return the internal flash memory, follow all packaging instructions, and use any packaging materials for shipping that are supplied to you. Replacing the internal flash memory this topic provides instructions for how to install the replacement internal flash memory (or hy...

  • Page 158

    4. Remove the top cover bracket (see “removing the top-cover bracket” on page 107). 5. Remove the middle fan (see “removing the middle hot-swap fan” on page 122). 6. Remove the memory cards and memory card fillers (see “removing a memory card” on page 136). 7. Disconnect the sas cables from the raid...

  • Page 159

    Removing the i/o-board shuttle this topic provides instructions for how to remove the rear i/o-board shuttle. About this task to remove the rear i/o-board shuttle, complete the following steps. Release pin handle i/o shuttle dvd signal cable usb cable procedure 1. Read the safety information that be...

  • Page 160

    Replacing the i/o-board shuttle this topic provides instructions for how to install the replacement rear i/o-board shuttle. About this task to install the replacement rear i/o-board shuttle, complete the following steps: procedure 1. Align the i/o-board shuttle over the server so that the pins on th...

  • Page 161

    12. Restore the raid configuration information that you backed up before you removed the i/o-board shuttle. Removing the dvd cable about this task to remove the dvd cable, complete the following steps: procedure 1. Read the safety information that begins with “safety” on page v and “installation gui...

  • Page 162

    Replacing the dvd cable this topic provides instructions for how to install the replacement dvd cable. About this task to install the replacement dvd cable, complete the following steps: procedure 1. Route the dvd cable in the server and connect it to the i/o board; then, connect the other end of th...

  • Page 163

    To remove the raid adapter carrier and raid adapter assembly, complete the following steps. Raid card carrier tab slot procedure 1. Read the safety information that begins with “safety” on page v, “installation guidelines” on page 97, and “handling static-sensitive devices” on page 100. 2. Save the ...

  • Page 164

    Release latch tabs post 9. If a battery is installed on the raid adapter, remove the battery carrier card and the battery from the raid adapter. You must remove the three screws to separate them. 10. If you are instructed to return the raid adapter assembly, follow all packaging instructions, and us...

  • Page 165

    Replacing the raid adapter carrier and the raid adapter assembly this topic provides steps to replace the raid adapter carrier and raid adapter assembly. About this task to replace the raid adapter carrier and raid adapter assembly, complete the following steps: procedure 1. If you removed a battery...

  • Page 166

    4. Slide the raid adapter carrier and raid adapter assembly into the slot on the side of the server. Make sure that the carrier is flat against the side wall of the server so that the adapter is installed in the connector correctly. Raid card carrier tab slot 5. Install the top cover bracket (see “r...

  • Page 167

    Removing the hard disk drive backplane and cable assembly this topic provides instructions for how to remove the hard disk drive backplane cable assembly. About this task important: before you remove the hard disk drive backplane cable assembly from the server, take the following precautions to save...

  • Page 168

    To remove the hard disk drive backplane cable assembly, complete the following steps. Backplane power cables configuration cables procedure 1. Read the safety information that begins with “safety” on page v and “installation guidelines” on page 97. 2. Turn off the server and peripheral devices, and ...

  • Page 169

    Replacing the hard disk drive backplane and cable assembly this topic provides instructions for how to replace the hard disk drive backplane cable assembly. About this task to replace the hard disk drive backplane cable assembly, complete the following steps. Procedure 1. Connect the power and confi...

  • Page 170

    To remove the sas hard disk drive backplane assembly, complete the following steps. Sas power and configuration cables release tab backplane carrier alignment pins procedure 1. Read the safety information that begins with “safety” on page v and “installation guidelines” on page 97. 2. Turn off the s...

  • Page 171

    8. If you are instructed to return the sas hard disk drive backplane assembly, follow all packaging instructions, and use any packaging materials for shipping that are supplied to you. Replacing the sas hard disk drive backplane assembly this topic provides instructions for how to install the replac...

  • Page 172

    Removing the exflash 1.8-inch drive cage and backplane assembly this topic provides instructions to remove the exflash drive backplane assembly. About this task important: before you remove the exflash 1.8-inch backplane assembly from the server, take the following precautions to save data, firmware...

  • Page 173

    5. Pull the drives out of the cage assembly and install them in the same positions in the new cage assembly. Filler panel 6. If you have 2.5-inch hard disk drives installed below the 1.8-inch cage, pull the drives and fillers out of the server. 2.5 inch hard disk drive assembly 2.5 inch hard disk dr...

  • Page 174

    7. Slide the backplane retention release tab forward and slightly lift the hard disk drive backplane carrier to disconnect the cables from the rear of the 1.8-inch backplane and cage assembly. Retention release tab hard disk drive backplane carrier backplane cables 8. Disconnect the signal cable and...

  • Page 175

    Replacing the exflash 1.8-inch drive cage and backplane assembly this topic provides instructions for how to replace the exflash 1.8-inch drive cage and backplane assembly. About this task to install the replacement exflash drive cage and backplane, complete the following steps: procedure 1. Slide t...

  • Page 176

    Removing and replacing frus this topic provides information about frus. About this task frus must be installed only by trained service technicians. Microprocessor this topic provides notes that describe the types of microprocessor that the server supports and other information that you must consider...

  • Page 177

    The following illustration of the microprocessor board shows the locations of the microprocessor sockets. Microprocessor 1 microprocessor 2 microprocessor 3 microprocessor 4 removing a microprocessor and heat sink: this topic provides instructions for how to remove a microprocessor and heat sink. Ch...

  • Page 178

    About this task microprocessors are to be removed only by trained service technicians. Attention: v do not allow the thermal grease on the microprocessor and heat sink to come in contact with anything. Contact with any surface can compromise the thermal grease and the microprocessor socket. V droppi...

  • Page 179

    6. Lift the heat sink 2 out of the server. If the heat sink sticks to the microprocessor, slightly twist the heat sink back and forth to break the seal. After removal, place the heat sink on its side on a clean, flat surface. 7. Open the microprocessor release latch 1 by pressing down on the end, mo...

  • Page 180

    Handle installation tool microprocessor alignment holes note: if you are removing e7 series microprocessors, you must use the microprocessor installation tool with the text “x7500 + e7” on the bottom of the tool (see the following illustration). Tools that do not have this text on the bottom will no...

  • Page 181

    Installing a microprocessor and heat sink: this topic provides instructions and guidelines for installing a microprocessor and heat sink. About this task for important information about the type of microprocessors that the server supports, microprocessor population order and how it affects server pe...

  • Page 182

    Important: v a startup (boot) microprocessor must always be installed in microprocessor socket 1 on the microprocessor board. V to ensure correct server operation, be sure to use microprocessors that are compatible and install a memory card and an additional dimm for microprocessor 2. Compatible mic...

  • Page 183

    Microprocessor protective cover 4. Place the microprocessor, with the contacts facing down, on the foam pad in the shipping carton. 5. Open the microprocessor release latch 1 by pressing down on the end, moving it to the side, and releasing it to the open (up) position. Swing open the microprocessor...

  • Page 184

    X7500 + e7 c. Using the triangle on the microprocessor to align it with the installation tool, place the microprocessor on the underside of the tool. D. Twist the handle of the installation tool clockwise to secure the microprocessor in the tool. Note: you can pick up or release the microprocessor b...

  • Page 185

    Note: the microprocessor fits only one way in the socket. Installation tool microprocessor alignment holes screws 8. Close the load plate and then rotate the microprocessor-release latch to secure the microprocessor. 9. Remove the heat sink from its package. 10. Install the heat sink. Attention: do ...

  • Page 186

    12. Install the top cover (see “replacing the top cover” on page 107). 13. Slide the server into the rack. 14. Reconnect the external cables; then, reconnect the power cords and turn on the peripheral devices and the server. Thermal grease: this topic provides instructions for how to replace damaged...

  • Page 187

    Removing the microprocessor-board assembly this topic provides instructions for how to remove the microprocessor-board assembly. About this task important: this procedure is to be performed only by trained service technicians. Before you remove the microprocessor-board assembly from the server, take...

  • Page 188

    3. Remove the top cover (see “removing and replacing consumable parts and tier 1 crus” on page 105). 4. Remove the top-cover bracket (see “removing the top-cover bracket” on page 107). 5. Remove the power supplies (see “removing a hot-swap power supply” on page 123). 6. Remove the i/o-board shuttle ...

  • Page 189

    Tabs i x7500 + e7 18. Install microprocessor socket covers on the empty microprocessor sockets on the old microprocessor board before you pack the board for shipping. 19. If you are instructed to return the microprocessor-board assembly, follow all packaging instructions, and use any packaging mater...

  • Page 190

    4. If you have a single-node server without a memory expansion module attached, install the qpi wrap cards or fillers. If you have a two-node server or if your server is connected to a memory expansion module, reconnect the qpi cables. 5. Connect the following cables: front fan, scalability led, ope...

  • Page 191

    Removing the memory-card cage this topic provides instructions for how to remove the memory-card cage. About this task to remove the memory-card cage, complete the following steps. Rear thumbscrew latch front thumbscrew latches procedure 1. Read the safety information that begins with “safety” on pa...

  • Page 192

    Replacing the memory-card cage about this task to replace the memory-card cage, complete the following steps: procedure 1. Move any cables out of the way and then set the replacement memory card cage into the server. 2. Tighten the two thumbscrews. 3. Slide the locking latches to the locked position...

  • Page 193

    Removing the memory expansion module bezel this topic provides instructions for how to remove the memory expansion module bezel. About this task to remove the memory expansion module bezel, complete the following steps: procedure 1. Read the safety information that begins with “safety” on page v and...

  • Page 194

    2. Press in on the release tabs on both ends of the bezel and pull it off of the chassis. Bezel alignment tab alignment tab release tab release tab replacing the memory expansion module bezel about this task to replace the memory expansion module bezel, complete the following steps: procedure 1. Rea...

  • Page 195

    Removing the memory expansion module air baffle this topic provides instructions for how to remove the air baffle in the memory expansion module. About this task to remove the air baffle in the memory expansion module, complete the following steps: procedure 1. Read the safety information that begin...

  • Page 196

    Replacing the memory expansion module air baffle this topic provides instructions for how to replace the memory expansion module air baffle. About this task to replace the memory expansion module air baffle, complete the following steps: procedure 1. Read the safety information that begins with “saf...

  • Page 197

    Stop-tab release latch release latch stop-tab handle handle 5. Grasp the handles and pull the system-board tray out until it stops. 6. Disconnect the information panel assembly cable from the connector on the system board tray. 7. Press the information panel release tab to the left and hold it while...

  • Page 198

    Replacing the memory expansion module information panel assembly this topic provides instructions for how to replace the memory expansion module information panel assembly. About this task to replace the memory expansion module information panel assembly, complete the following steps: procedure 1. R...

  • Page 199

    Stop-tab release latch release latch stop-tab handle handle 7. Reinstall the bezel (see “replacing the memory expansion module bezel” on page 178). 8. Reconnect the power cords to the memory expansion module; then, connect all external cables to the memory expansion module. 9. Turn on the peripheral...

  • Page 200

    4. If you are instructed to return the fan, follow all packaging instructions, and use any packaging materials for shipping that are supplied to you. Replacing a memory expansion module hot-swap fan this topic provides instructions for how to replace a hot-swap fan in the memory expansion module. Ab...

  • Page 201

    Removing a memory expansion module dimm this topic provides instructions for how to remove a dimm from the memory expansion module. About this task to remove a dimm from the memory expansion module, complete the following steps: procedure 1. Read the safety information that begins with “safety” on p...

  • Page 202

    7. If you are instructed to return the dimm, follow all packaging instructions, and use any packaging materials for shipping that are supplied to you. Replacing a memory expansion module dimm this topic provides information about the types of dimms, as well as instructions for how to replace a memor...

  • Page 203

    V double-device data correction support is only available when 16 gb x4 dram technology dimms are installed in the memory expansion module and the memory expansion module is connected to a host server. V the memory expansion module supports memory sparing through the host server. Memory sparing rese...

  • Page 204

    V a minimum of two dimms must be installed in the memory expansion module for each microprocessor in the host server. V the maximum operating speed of the memory expansion module is determined by the slowest dimm installed in the memory expansion module. V the memory expansion module does not come w...

  • Page 205

    Module has 64 gb of memory installed, only 32 gb of addressable memory is available when you use memory mirroring. Chapter 5. Removing and replacing components 189.

  • Page 206

    - the following table lists the dimm installation sequence for memory-mirroring mode. Table 24. Memory-mirroring mode dimm population sequence for the memory expansion module sets of 4 dimms dimm connector population sequence set 1 9, 16, 28, 29 set 2 1, 8, 20, 21 set 3 11, 14, 26, 31 set 4 3, 6, 18...

  • Page 207

    To install a memory module in the memory expansion module, complete the following steps. Note: the memory expansion module might come with dimm fillers on dimm connectors that are not populated. Remove them before you install dimms in those connectors. Procedure 1. Touch the static-protective packag...

  • Page 208

    Removing a memory expansion module hot-swap power supply this topic provides precautions, as well as instructions for how to remove or install a hot-swap power supply. About this task when you remove or install a hot-swap power supply, observe the following precautions. Statement 5 caution: the powe...

  • Page 209

    2. If only one power supply is installed, turn off the host server and peripheral devices and disconnect the memory expansion module power cords. 3. If the memory expansion module is in a rack, at the back of the memory expansion module, pull back the cable management arm to gain access to the rear ...

  • Page 210

    2. Touch the static-protective package that contains the hot-swap power supply to any unpainted metal surface on the memory expansion module; then, remove the power supply from the package and place it on a static-protective surface. 3. If you are installing a hot-swap power supply into an empty bay...

  • Page 211

    4. Remove the system-board tray (see “removing the memory expansion module system-board tray assembly” on page 197). 5. Remove the fans (see “removing a memory expansion module hot-swap fan” on page 183). 6. From the inside of the system-board tray, remove the fan cable connectors from the system-bo...

  • Page 212

    Replacing the memory expansion module five-drop fan cable assembly this topic provides instructions for how to install the five-drop fan cable assembly. About this task to install the five-drop fan cable assembly, complete the following steps: procedure 1. Read the safety information that begins wit...

  • Page 213

    Removing and replacing memory expansion module tier 2 crus this topic provides general information about removing and replacing memory expansion module tier 2 crus. About this task you may install a tier 2 cru yourself or request ibm to install it, at no additional charge, under the type of warranty...

  • Page 214

    Stop-tab release latch release latch stop-tab handle handle 6. Grasp the handles and pull the system-board tray out until it stops; then, press inward on the stop-tabs on both sides of the system-board tray and pull the tray out of the chassis. 7. Remove the air baffle (see “replacing the memory exp...

  • Page 215

    4. Before you attach a memory expansion module to the server and try to use it, you must update the uefi firmware with the latest level of firmware code. If you attach and try to use the memory expansion module without updating the uefi firmware, you might get unexpected system behavior, or the serv...

  • Page 216

    200 ibm system x3850 x5 and x3950 x5 types 7145, 7146, 7143, and 7191: problem determination and service guide.

  • Page 217

    Chapter 6. Configuration information and instructions this topic provides general information about the configuration. This chapter provides information about updating the firmware and using the configuration utilities. Updating the firmware this topic provides instructions for updating the firmware...

  • Page 218

    Configuring the server this topic provides instructions on how to configure the server. The following configuration programs come with the server: v setup utility the setup utility (formerly called the configuration/setup utility program) is part of the ibm uefi firmware. Use it to perform configura...

  • Page 219

    For more information, see “using the remote presence capability and blue-screen capture” on page 215 v ethernet controller configuration for information about configuring the ethernet controller, see “configuring the broadcom gigabit ethernet controller” on page 216. V ibm advanced settings utility ...

  • Page 220

    – devices and i/o ports select this choice to view or change assignments for devices and input/output (i/o) ports. You can configure the serial ports; configure remote console redirection; enable or disable integrated ethernet controllers, the sas/sata controller, sata optical drive channels, and pc...

  • Page 221

    - commands on usb interface preference enable or disable the ethernet over usb interface on imm. - network configuration select this choice to view and select the system management network interface port, the imm mac address, the current imm ip address, and host name; define the static imm ip addres...

  • Page 222

    Select this choice to access the system event manager, where you can view the post event log and the system-event log. The post event log contains the three most recent error codes and messages that were generated during post. The system-event log contains post and system management interrupt (smi) ...

  • Page 223

    Passwords this topic provides general information about passwords. From the user security menu choice, you can set, change, and delete a power-on password and an administrator password. The user security choice is on the full setup utility menu only. If you set only a power-on password, you must typ...

  • Page 224

    The power-on password override jumper does not affect the administrator password. Attention: before you move any jumpers, turn off the server; then, disconnect all power cords and external cables. See the safety information that begins with “safety” on page v. Do not change settings or move jumpers ...

  • Page 225

    Starting the backup uefi firmware this topic provides general information about starting the backup uefi firmware. About this task the system board contains a backup copy area for the uefi firmware. This is a secondary copy of the uefi firmware that you update only during the process of updating the...

  • Page 226

    Serverguide features features and functions can vary slightly with different versions of the serverguide program. To learn more about the version that you have, start the serverguide setup and installation cd and view the online overview. Not all features are supported on all server models. The serv...

  • Page 227

    Typical operating-system installation this topic provides instructions for a typical operating-system installation. The serverguide program can reduce the time it takes to install an operating system. It provides the device drivers that are required for your hardware and for the operating system tha...

  • Page 228

    V boot sequence manipulation. V command-line interface. V configuration save and restore. V dimm error assistance. The unified extensible firmware interface (uefi) disables a failing dimm that is detected during post, and the imm lights the associated system-error led and the failing dimm error led....

  • Page 229

    Obtaining the ip address for the web interface access this topic provides instruction for obtaining the ip address for the web interface access. The imm mac address tag is tied to the rear of the server. The hostname of the imm is "imm-" plus the last twelve characters of the mac address. Because th...

  • Page 230

    Using the embedded hypervisor this topic provides instructions for using the embedded hypervisor. About this task the vmware esxi embedded hypervisor software is available on the ibm usb flash device with embedded hypervisor. The usb flash device can be installed in either of the i/o board internal ...

  • Page 231

    Procedure 1. Turn on the server. Note: approximately 1 to 3 minutes after the server is connected to ac power, the power-control button becomes active. 2. When the prompt setup is displayed, press f1. 3. From the setup utility main menu, select boot manager . 4. Select add boot option ; then, select...

  • Page 232

    Enabling the broadcom gigabit ethernet utility program this topic provides general information about enabling the broadcom gigabit ethernet utility program. You can configure the broadcom gigabit ports as a startable device, and can be customized in the startup sequence. Enable, disable, and customi...

  • Page 233

    Results for more information about raid arrays, see the ibm redbooks ® publications about raid arrays at http://www.Redbooks.Ibm.Com/abstracts/tips0054.Html. Ibm advanced settings utility program this topic provides information about the ibm advanced settings utility program. The ibm advanced settin...

  • Page 234

    B. If a newer version of ibm systems director than what comes with the server is shown in the drop-down list, follow the instructions on the web page to download the latest version. 2. Install the ibm systems director program. Results if your management server is connected to the internet, to locate...

  • Page 235

    Rear view server memory expansion module server memory expansion module exa cables qpi cables qpi cables the scalable partition web interface is an extension of the imm web interface and is used to create, delete, control, and view scalable partitions. The scalable partition web interface firmware i...

  • Page 236

    Creating an exa multi-node system this topic provides information about creating an exa multi-node system. About this task the following information provides instructions for creating an exa multi-node system from multiple servers and configuring it as a single logical 8-socket server. Note: to chec...

  • Page 237

    4. In the navigation pane, click scalable partitioning , and then click manage partition(s) . Use the scalable complex management page to create, delete, control, and view scalable partitions. Select the primary node; then, automatically or manually create a scalable partition: v to automatically cr...

  • Page 238

    3. Select the chassis that you are connected to through the imm. The interface control for the other chassis should be disabled. 4. Determine which method you plan to use to partition the multi-node server: v to delete the partition, click partition configuration , and then click delete . V to force...

  • Page 239

    Using the imm telnet interface this topic provides information about the imm telnet interface. About this task you can create, modify, and control partitions through the imm telnet interface. To use the imm telnet interface, log in to the imm telnet interface on either node and use the scale command...

  • Page 240

    Node. For example, if the exa system includes nodes 3c0d and 8bb9, to create a 2-node partition with node 3c0d as the primary node, type scale -create 3c0d, 8bb9 . After you use either method to create the partition, the scale information is updated with the node partition id assigned to the partiti...

  • Page 241

    Toggling partitions by using the imm telnet interface: this topic provides information about toggling partitions by using the imm telnet interface. About this task note: before you toggle a partition to standalone mode, make sure that all the nodes in the partition are powered off. A partition can b...

  • Page 242

    Configuring a qpi multi-node system this topic provides information about configuring a qpi multi-node system. About this task a multi-node configuration interconnects multiple servers or multiple partitions. This configuration requires 8 microprocessors and 16 memory cards (4 microprocessors and 8 ...

  • Page 243

    Appendix a. Dsa diagnostic test results after running the dsa diagnostic tests, use this information to resolve any issues that were found. Dsa broadcom network test results the following messages are generated when you run the broadcom network test. 405-000-000 brcm:testcontrolregisters test passed...

  • Page 244

    405-002-000 brcm:testeeprom test passed explanation: the test passed. Severity: event serviceable: no recoverable: no automatically notify support: no related links: v ibm support website v latest level of dsa v latest level of bmc/imm 405-003-000 brcm:testinternalmemory test passed explanation: the...

  • Page 245

    405-005-000 brcm:testloopbackmac test passed explanation: the test passed. Severity: event serviceable: no recoverable: no automatically notify support: no related links: v ibm support website v latest level of dsa v latest level of bmc/imm 405-006-000 brcm:testloopbackphysical test passed explanati...

  • Page 246

    405-800-000 brcm:testcontrolregisters test aborted explanation: the control registers test was canceled. Severity: warning serviceable: no recoverable: no automatically notify support: no related links: v ibm support website v latest level of dsa v latest level of bmc/imm 405-801-000 brcm:testmiireg...

  • Page 247

    405-803-000 brcm:testinternalmemory test aborted explanation: the internal memory test was canceled. Severity: warning serviceable: no recoverable: no automatically notify support: no related links: v ibm support website v latest level of dsa v latest level of bmc/imm 405-804-000 brcm:testinterrupt ...

  • Page 248

    405-806-000 brcm:testloopbackphysical test aborted explanation: loopback testing at the physical layer was canceled. Severity: warning serviceable: no recoverable: no automatically notify support: no related links: v ibm support website v latest level of dsa v latest level of bmc/imm 405-807-000 brc...

  • Page 249

    405-901-000 brcm:testmiiregisters test failed explanation: a failure was detected while testing internal phy registers. Severity: error serviceable: yes recoverable: no automatically notify support: no user response: complete the following steps: 1. Check component firmware level and upgrade if nece...

  • Page 250

    405-903-000 brcm:testinternalmemory test failed explanation: a failure was detected while testing internal memory. Severity: error serviceable: yes recoverable: no automatically notify support: no user response: complete the following steps: 1. Check component firmware level and upgrade if necessary...

  • Page 251

    405-905-000 brcm:testloopbackmac test failed explanation: brcm:testloopbackmac test failed. Severity: error serviceable: yes recoverable: no automatically notify support: no user response: complete the following steps: 1. Check component firmware level and upgrade if necessary. The installed firmwar...

  • Page 252

    405-907-000 brcm:testleds test failed explanation: a failure was detected while verifying operation of the status leds. Severity: error serviceable: yes recoverable: no automatically notify support: no user response: complete the following steps: 1. Check component firmware level and upgrade if nece...

  • Page 253

    218-001-000 brocade:externalloopbacktest passed explanation: the test passed. Severity: event serviceable: no recoverable: no automatically notify support: no related links: v ibm support website v latest level of dsa v latest level of bmc/imm 218-002-000 brocade:serdesloopbacktest passed explanatio...

  • Page 254

    218-004-000 brocade:externalethloopbacktest passed explanation: the test passed. Severity: event serviceable: no recoverable: no automatically notify support: no related links: v ibm support website v latest level of dsa v latest level of bmc/imm 218-005-000 brocade:serdesethloopbacktest passed expl...

  • Page 255

    218-800-000 brocade:memorytest aborted explanation: the test was canceled. Severity: warning serviceable: no recoverable: no automatically notify support: no related links: v ibm support website v latest level of dsa v latest level of bmc/imm 218-801-000 brocade:externalloopbacktest aborted explanat...

  • Page 256

    218-803-000 brocade:pciloopbacktest aborted explanation: the test was canceled. Severity: warning serviceable: no recoverable: no automatically notify support: no related links: v ibm support website v latest level of dsa v latest level of bmc/imm 218-804-000 brocade:externalethloopbacktest aborted ...

  • Page 257

    218-806-000 brocade:internalloopbacktest aborted explanation: the test was canceled. Severity: warning serviceable: no recoverable: no automatically notify support: no related links: v ibm support website v latest level of dsa v latest level of bmc/imm 218-900-000 brocade:memorytest failed explanati...

  • Page 258

    218-902-000 brocade:serdesloopbacktest failed explanation: a failure was detected during the loopback test. Severity: error serviceable: yes recoverable: no automatically notify support: no user response: complete the following steps: 1. Rerun the test. 2. Verify whether the firmware is at proper le...

  • Page 259

    218-904-000 brocade:externalethloopbacktest failed explanation: a failure was detected during the loopback test. Severity: error serviceable: yes recoverable: no automatically notify support: no user response: complete the following steps: 1. Check or replace sfp/cable. 2. Rerun the test. 3. Verify ...

  • Page 260

    218-906-000 brocade:internalloopbacktest failed explanation: a failure was detected during the loopback test. Severity: error serviceable: yes recoverable: no automatically notify support: no user response: complete the following steps: 1. Rerun the test. 2. Verify whether the firmware is at proper ...

  • Page 261

    Related links: v ibm support website v latest level of dsa v latest level of bmc/imm 180-901-000 check-point panel test failed explanation: check-point panel test failed. Operator reported incorrect display. Severity: error serviceable: yes recoverable: no automatically notify support: no user respo...

  • Page 262

    089-801-000 cpu stress test aborted explanation: cpu stress test aborted. Internal program error. Severity: warning serviceable: yes recoverable: no automatically notify support: no user response: complete the following steps: 1. Turn off and restart the system. 2. Make sure that the dsa diagnostic ...

  • Page 263

    089-803-000 cpu stress test aborted explanation: cpu stress test aborted. Memory size is insufficient to run the test. At least 1gb is required. Severity: warning serviceable: yes recoverable: no automatically notify support: no related links: v ibm support website v latest level of dsa v latest lev...

  • Page 264

    Dsa emulex adapter test results the following messages are generated when you run the emulex adapter test. 516-000-000 elxucna: nic mac loopbacktest passed explanation: the test passed. Severity: event serviceable: no recoverable: no automatically notify support: no related links: v ibm support webs...

  • Page 265

    516-800-000 elxucna: nic mac loopbacktest aborted explanation: loopback testing at the mac layer was canceled. Severity: warning serviceable: no recoverable: no automatically notify support: no related links: v ibm support website v latest level of dsa v latest level of bmc/imm 516-801-000 elxucna: ...

  • Page 266

    516-900-000 elxucna: nic mac loopbacktest failed explanation: a failure was detected during the loopback test at the mac layer. Severity: error serviceable: yes recoverable: no automatically notify support: no user response: complete the following steps: 1. Check component firmware level and upgrade...

  • Page 267

    516-902-000 elxucna: elxucna: nic led(beacon)test failed explanation: a failure was detected while verifying operation of the status leds. Severity: error serviceable: yes recoverable: no automatically notify support: no user response: complete the following steps: 1. Check component firmware level ...

  • Page 268

    401-801-000 exa port ping test aborted explanation: exa port ping test aborted. Unable to get device base address. Severity: warning serviceable: yes recoverable: no automatically notify support: no user response: complete the following steps: 1. Remove power cables, wait for 45 seconds, reconnect a...

  • Page 269

    401-901-001 exa port ping test failed explanation: exa port ping test failed. Severity: error serviceable: yes recoverable: no automatically notify support: no user response: complete the following steps: 1. Remove power cables, wait for 45 seconds, reconnect and rerun the test. 2. Make sure that th...

  • Page 270

    217-800-000 hdd test aborted explanation: hdd test aborted. The test was canceled. Severity: warning serviceable: yes recoverable: no automatically notify support: no user response: complete the following steps: 1. Check cable connections. 2. Rerun the test. 3. Verify that hard drive supports self t...

  • Page 271

    Dsa intel network test results the following messages are generated when you run the intel network test. 406-000-000 ianet:registers test passed explanation: the test passed. Severity: event serviceable: no recoverable: no automatically notify support: no related links: v ibm support website v lates...

  • Page 272

    406-003-000 ianet:interrupts test passed explanation: the test passed. Severity: event serviceable: no recoverable: no automatically notify support: no related links: v ibm support website v latest level of dsa v latest level of bmc/imm 406-004-000 ianet:loopback test passed explanation: the test pa...

  • Page 273

    406-801-000 ianet:eeprom test aborted explanation: eeprom test was canceled. Severity: warning serviceable: no recoverable: no automatically notify support: no related links: v ibm support website v latest level of dsa v latest level of bmc/imm 406-802-000 ianet:fifo test aborted explanation: fifo t...

  • Page 274

    406-804-000 ianet:loopback test aborted explanation: loopback test was canceled. Severity: warning serviceable: no recoverable: no automatically notify support: no related links: v ibm support website v latest level of dsa v latest level of bmc/imm 406-900-000 ianet:registers test failed explanation...

  • Page 275

    406-902-000 ianet:fifo test failed explanation: a failure was detected during the fifo test. Severity: error serviceable: yes recoverable: no automatically notify support: no user response: complete the following steps: 1. Check component firmware level and upgrade if necessary. The installed firmwa...

  • Page 276

    406-904-000 ianet:loopback test failed explanation: a failure was detected during the loopback test. Severity: error serviceable: yes recoverable: no automatically notify support: no user response: complete the following steps: 1. Check the ethernet cable for damage and ensure correct cable type and...

  • Page 277

    407-800-000 lsiesg:diskdefaultdiagnostic test aborted explanation: the test was canceled. Severity: warning serviceable: no recoverable: no automatically notify support: no related links: v ibm support website v latest level of dsa v latest level of bmc/imm 407-900-000 lsiesg:diskdefaultdiagnostic t...

  • Page 278

    408-000-000 mlnx:mlnx_diagnostictestethernetport test passed explanation: port test passed. Severity: event serviceable: no recoverable: no automatically notify support: no related links: v ibm support website v latest level of dsa v latest level of bmc/imm 408-001-000 mlnx:mlnx_diagnostictestibport...

  • Page 279

    408-801-000 mlnx:mlnx_diagnostictestibport test aborted explanation: port test was canceled. Severity: warning serviceable: no recoverable: no automatically notify support: no related links: v ibm support website v latest level of dsa v latest level of bmc/imm 408-900-000 mlnx:mlnx_diagnostictesteth...

  • Page 280

    Dsa memory isolation test results the following messages are generated when you run the memory isolation test. 201-000-000 standalone memory test passed explanation: quick/full memory test all cpus passed. Severity: event serviceable: no recoverable: no automatically notify support: no related links...

  • Page 281

    201-000-003 standalone memory test passed explanation: quick/full memory test cpu 3 passed. Severity: event serviceable: no recoverable: no automatically notify support: no related links: v ibm support website v latest level of dsa v latest level of bmc/imm 201-000-004 standalone memory test passed ...

  • Page 282

    201-811-001 standalone memory test aborted explanation: unable to locate smbios key "_sm_". Severity: warning serviceable: no recoverable: no automatically notify support: no user response: complete the following steps: 1. Perform the actions mentioned one at a time and try the test after each actio...

  • Page 283

    201-811-003 standalone memory test aborted explanation: unable to locate smbios key "_sm_". Severity: warning serviceable: no recoverable: no automatically notify support: no user response: complete the following steps: 1. Perform the actions mentioned one at a time and try the test after each actio...

  • Page 284

    201-812-001 standalone memory test aborted explanation: memory test is not supported for this system. Severity: warning serviceable: no recoverable: no automatically notify support: no user response: complete the following steps: 1. Perform the actions mentioned one at a time and try the test after ...

  • Page 285

    201-812-003 standalone memory test aborted explanation: memory test is not supported for this system. Severity: warning serviceable: no recoverable: no automatically notify support: no user response: complete the following steps: 1. Perform the actions mentioned one at a time and try the test after ...

  • Page 286

    201-813-001 standalone memory test aborted explanation: chipset error: can not turn off ecc error reporting in cpu. Severity: warning serviceable: no recoverable: no automatically notify support: no user response: complete the following steps: 1. Perform the actions mentioned one at a time and try t...

  • Page 287

    201-813-003 standalone memory test aborted explanation: chipset error: can not turn off ecc error reporting in cpu. Severity: warning serviceable: no recoverable: no automatically notify support: no user response: complete the following steps: 1. Perform the actions mentioned one at a time and try t...

  • Page 288

    201-814-001 standalone memory test aborted explanation: chipset error: can not disable scubbing feature for cpu. Severity: warning serviceable: no recoverable: no automatically notify support: no user response: complete the following steps: 1. Perform the actions mentioned one at a time and try the ...

  • Page 289

    201-814-003 standalone memory test aborted explanation: chipset error: can not disable scubbing feature for cpu. Severity: warning serviceable: no recoverable: no automatically notify support: no user response: complete the following steps: 1. Perform the actions mentioned one at a time and try the ...

  • Page 290

    201-815-001 standalone memory test aborted explanation: program error with quick memory menu option selection. Severity: warning serviceable: no recoverable: no automatically notify support: no user response: complete the following steps: 1. Perform the actions mentioned one at a time and try the te...

  • Page 291

    201-815-003 standalone memory test aborted explanation: program error with quick memory menu option selection. Severity: warning serviceable: no recoverable: no automatically notify support: no user response: complete the following steps: 1. Perform the actions mentioned one at a time and try the te...

  • Page 292

    201-816-001 standalone memory test aborted explanation: program error with full memory menu option selection. Severity: warning serviceable: no recoverable: no automatically notify support: no user response: complete the following steps: 1. Perform the actions mentioned one at a time and try the tes...

  • Page 293

    201-816-003 standalone memory test aborted explanation: program error with full memory menu option selection. Severity: warning serviceable: no recoverable: no automatically notify support: no user response: complete the following steps: 1. Perform the actions mentioned one at a time and try the tes...

  • Page 294

    201-818-001 standalone memory test aborted explanation: unable to locate smbios key "_sm_". Severity: warning serviceable: no recoverable: no automatically notify support: no user response: complete the following steps: 1. Perform the actions mentioned one at a time and try the test after each actio...

  • Page 295

    201-818-003 standalone memory test aborted explanation: unable to locate smbios key "_sm_". Severity: warning serviceable: no recoverable: no automatically notify support: no user response: complete the following steps: 1. Perform the actions mentioned one at a time and try the test after each actio...

  • Page 296

    201-819-001 standalone memory test aborted explanation: the start-end address ranges in the restricted area of the memory. Severity: warning serviceable: no recoverable: no automatically notify support: no user response: complete the following steps: 1. Perform the actions mentioned one at a time an...

  • Page 297

    201-819-003 standalone memory test aborted explanation: the start-end address ranges in the restricted area of the memory. Severity: warning serviceable: no recoverable: no automatically notify support: no user response: complete the following steps: 1. Perform the actions mentioned one at a time an...

  • Page 298

    201-820-001 standalone memory test aborted explanation: memory upper limit is less than 16 mbytes. Severity: warning serviceable: no recoverable: no automatically notify support: no user response: complete the following steps: 1. Perform the actions mentioned one at a time and try the test after eac...

  • Page 299

    201-820-003 standalone memory test aborted explanation: memory upper limit is less than 16 mbytes. Severity: warning serviceable: no recoverable: no automatically notify support: no user response: complete the following steps: 1. Perform the actions mentioned one at a time and try the test after eac...

  • Page 300

    201-821-001 standalone memory test aborted explanation: variable range mtrr registers are larger than fixed range mtrr registers. Severity: warning serviceable: no recoverable: no automatically notify support: no user response: complete the following steps: 1. Perform the actions mentioned one at a ...

  • Page 301

    201-821-003 standalone memory test aborted explanation: variable range mtrr registers are larger than fixed range mtrr registers. Severity: warning serviceable: no recoverable: no automatically notify support: no user response: complete the following steps: 1. Perform the actions mentioned one at a ...

  • Page 302

    201-822-001 standalone memory test aborted explanation: invalid mtrr service request. Severity: warning serviceable: no recoverable: no automatically notify support: no user response: complete the following steps: 1. Perform the actions mentioned one at a time and try the test after each action. 2. ...

  • Page 303

    201-822-003 standalone memory test aborted explanation: invalid mtrr service request. Severity: warning serviceable: no recoverable: no automatically notify support: no user response: complete the following steps: 1. Perform the actions mentioned one at a time and try the test after each action. 2. ...

  • Page 304

    201-824-001 standalone memory test aborted explanation: node interleave feature must be off. Go to setup and disable node interleave option and then re-run the test. Severity: warning serviceable: no recoverable: no automatically notify support: no user response: complete the following steps: 1. Per...

  • Page 305

    201-824-003 standalone memory test aborted explanation: node interleave feature must be off. Go to setup and disable node interleave option and then re-run the test. Severity: warning serviceable: no recoverable: no automatically notify support: no user response: complete the following steps: 1. Per...

  • Page 306

    201-826-001 standalone memory test aborted explanation: bios: memory controller has been disabled. Go to setup and enable memory controller. Severity: warning serviceable: no recoverable: no automatically notify support: no user response: complete the following steps: 1. Perform the actions mentione...

  • Page 307

    201-826-003 standalone memory test aborted explanation: bios: memory controller has been disabled. Go to setup and enable memory controller. Severity: warning serviceable: no recoverable: no automatically notify support: no user response: complete the following steps: 1. Perform the actions mentione...

  • Page 308

    201-827-001 standalone memory test aborted explanation: bios: ecc function has been disabled by bios. Go to setup and enable ecc generation. Severity: warning serviceable: no recoverable: no automatically notify support: no user response: complete the following steps: 1. Perform the actions mentione...

  • Page 309

    201-827-003 standalone memory test aborted explanation: bios: ecc function has been disabled by bios. Go to setup and enable ecc generation. Severity: warning serviceable: no recoverable: no automatically notify support: no user response: complete the following steps: 1. Perform the actions mentione...

  • Page 310

    201-844-001 standalone memory test aborted explanation: chipset error: problem in masking msr machine check control mask registers. Severity: warning serviceable: no recoverable: no automatically notify support: no user response: complete the following steps: 1. Perform the actions mentioned one at ...

  • Page 311

    201-844-003 standalone memory test aborted explanation: chipset error: problem in masking msr machine check control mask registers. Severity: warning serviceable: no recoverable: no automatically notify support: no user response: complete the following steps: 1. Perform the actions mentioned one at ...

  • Page 312

    201-845-001 standalone memory test aborted explanation: chipset error: problem clearing msr machine check control registers. Severity: warning serviceable: no recoverable: no automatically notify support: no user response: complete the following steps: 1. Perform the actions mentioned one at a time ...

  • Page 313

    201-845-003 standalone memory test aborted explanation: chipset error: problem clearing msr machine check control registers. Severity: warning serviceable: no recoverable: no automatically notify support: no user response: complete the following steps: 1. Perform the actions mentioned one at a time ...

  • Page 314

    201-859-001 standalone memory test aborted explanation: invalid xsecsrat type. Severity: warning serviceable: no recoverable: no automatically notify support: no user response: complete the following steps: 1. Perform the actions mentioned one at a time and try the test after each action. 2. If the ...

  • Page 315

    201-859-003 standalone memory test aborted explanation: invalid xsecsrat type. Severity: warning serviceable: no recoverable: no automatically notify support: no user response: complete the following steps: 1. Perform the actions mentioned one at a time and try the test after each action. 2. If the ...

  • Page 316

    201-860-001 standalone memory test aborted explanation: no oem0 type 1 found. Severity: warning serviceable: no recoverable: no automatically notify support: no user response: complete the following steps: 1. Perform the actions mentioned one at a time and try the test after each action. 2. If the p...

  • Page 317

    201-860-003 standalone memory test aborted explanation: no oem0 type 1 found. Severity: warning serviceable: no recoverable: no automatically notify support: no user response: complete the following steps: 1. Perform the actions mentioned one at a time and try the test after each action. 2. If the p...

  • Page 318

    201-861-001 standalone memory test aborted explanation: no srat type 1 found. Severity: warning serviceable: no recoverable: no automatically notify support: no user response: complete the following steps: 1. Perform the actions mentioned one at a time and try the test after each action. 2. If the p...

  • Page 319

    201-861-003 standalone memory test aborted explanation: no srat type 1 found. Severity: warning serviceable: no recoverable: no automatically notify support: no user response: complete the following steps: 1. Perform the actions mentioned one at a time and try the test after each action. 2. If the p...

  • Page 320

    201-862-001 standalone memory test aborted explanation: no oem1 structure found. Severity: warning serviceable: no recoverable: no automatically notify support: no user response: complete the following steps: 1. Perform the actions mentioned one at a time and try the test after each action. 2. If th...

  • Page 321

    201-862-003 standalone memory test aborted explanation: no oem1 structure found. Severity: warning serviceable: no recoverable: no automatically notify support: no user response: complete the following steps: 1. Perform the actions mentioned one at a time and try the test after each action. 2. If th...

  • Page 322

    201-863-001 standalone memory test aborted explanation: no ibmerror key in oem1 structure. Severity: warning serviceable: no recoverable: no automatically notify support: no user response: complete the following steps: 1. Perform the actions mentioned one at a time and try the test after each action...

  • Page 323

    201-863-003 standalone memory test aborted explanation: no ibmerror key in oem1 structure. Severity: warning serviceable: no recoverable: no automatically notify support: no user response: complete the following steps: 1. Perform the actions mentioned one at a time and try the test after each action...

  • Page 324

    201-864-001 standalone memory test aborted explanation: no gas located in oem1. Severity: warning serviceable: no recoverable: no automatically notify support: no user response: complete the following steps: 1. Perform the actions mentioned one at a time and try the test after each action. 2. If the...

  • Page 325

    201-864-003 standalone memory test aborted explanation: no gas located in oem1. Severity: warning serviceable: no recoverable: no automatically notify support: no user response: complete the following steps: 1. Perform the actions mentioned one at a time and try the test after each action. 2. If the...

  • Page 326

    201-865-001 standalone memory test aborted explanation: no xsecsrat key in oem0 structure. Severity: warning serviceable: no recoverable: no automatically notify support: no user response: complete the following steps: 1. Perform the actions mentioned one at a time and try the test after each action...

  • Page 327

    201-865-003 standalone memory test aborted explanation: no xsecsrat key in oem0 structure. Severity: warning serviceable: no recoverable: no automatically notify support: no user response: complete the following steps: 1. Perform the actions mentioned one at a time and try the test after each action...

  • Page 328

    201-866-001 standalone memory test aborted explanation: efi-sal invalid parameter from getmemorymap function. Severity: warning serviceable: no recoverable: no automatically notify support: no user response: complete the following steps: 1. Perform the actions mentioned one at a time and try the tes...

  • Page 329

    201-866-003 standalone memory test aborted explanation: efi-sal invalid parameter from getmemorymap function. Severity: warning serviceable: no recoverable: no automatically notify support: no user response: complete the following steps: 1. Perform the actions mentioned one at a time and try the tes...

  • Page 330

    201-867-001 standalone memory test aborted explanation: efi/sal: buffer not allocated. Severity: warning serviceable: no recoverable: no automatically notify support: no user response: complete the following steps: 1. Perform the actions mentioned one at a time and try the test after each action. 2....

  • Page 331

    201-867-003 standalone memory test aborted explanation: efi/sal: buffer not allocated. Severity: warning serviceable: no recoverable: no automatically notify support: no user response: complete the following steps: 1. Perform the actions mentioned one at a time and try the test after each action. 2....

  • Page 332

    201-868-001 standalone memory test aborted explanation: efi/sal: buffer allocated in getmemorymap too small. Severity: warning serviceable: no recoverable: no automatically notify support: no user response: complete the following steps: 1. Perform the actions mentioned one at a time and try the test...

  • Page 333

    201-868-003 standalone memory test aborted explanation: efi/sal: buffer allocated in getmemorymap too small. Severity: warning serviceable: no recoverable: no automatically notify support: no user response: complete the following steps: 1. Perform the actions mentioned one at a time and try the test...

  • Page 334

    201-869-001 standalone memory test aborted explanation: efi/sal invalid parameter from getmemorymap function. Severity: warning serviceable: no recoverable: no automatically notify support: no user response: complete the following steps: 1. Perform the actions mentioned one at a time and try the tes...

  • Page 335

    201-869-003 standalone memory test aborted explanation: efi/sal invalid parameter from getmemorymap function. Severity: warning serviceable: no recoverable: no automatically notify support: no user response: complete the following steps: 1. Perform the actions mentioned one at a time and try the tes...

  • Page 336

    201-870-001 standalone memory test aborted explanation: cpu doamin in acpi not valid. Severity: warning serviceable: no recoverable: no automatically notify support: no user response: complete the following steps: 1. Perform the actions mentioned one at a time and try the test after each action. 2. ...

  • Page 337

    201-870-003 standalone memory test aborted explanation: cpu doamin in acpi not valid. Severity: warning serviceable: no recoverable: no automatically notify support: no user response: complete the following steps: 1. Perform the actions mentioned one at a time and try the test after each action. 2. ...

  • Page 338

    201-871-001 standalone memory test aborted explanation: data mis-compare encountered. Severity: warning serviceable: no recoverable: no automatically notify support: no user response: complete the following steps: 1. Perform the actions mentioned one at a time and try the test after each action. 2. ...

  • Page 339

    201-871-003 standalone memory test aborted explanation: data mis-compare encountered. Severity: warning serviceable: no recoverable: no automatically notify support: no user response: complete the following steps: 1. Perform the actions mentioned one at a time and try the test after each action. 2. ...

  • Page 340

    201-877-001 standalone memory test aborted explanation: bios: sparing in extended pci reg. Must be off. Go to setup and disable sparing. Severity: warning serviceable: no recoverable: no automatically notify support: no user response: complete the following steps: 1. Perform the actions mentioned on...

  • Page 341

    201-877-003 standalone memory test aborted explanation: bios: sparing in extended pci reg. Must be off. Go to setup and disable sparing. Severity: warning serviceable: no recoverable: no automatically notify support: no user response: complete the following steps: 1. Perform the actions mentioned on...

  • Page 342

    201-878-001 standalone memory test aborted explanation: sparing feature must be turned off. Go to setup and turn the sparing feature off. Severity: warning serviceable: no recoverable: no automatically notify support: no user response: complete the following steps: 1. Perform the actions mentioned o...

  • Page 343

    201-878-003 standalone memory test aborted explanation: sparing feature must be turned off. Go to setup and turn the sparing feature off. Severity: warning serviceable: no recoverable: no automatically notify support: no user response: complete the following steps: 1. Perform the actions mentioned o...

  • Page 344

    201-885-001 standalone memory test aborted explanation: processor does not support mtrr register manipulation. Can not write to memory without cache. Severity: warning serviceable: no recoverable: no automatically notify support: no user response: complete the following steps: 1. Perform the actions...

  • Page 345

    201-885-003 standalone memory test aborted explanation: processor does not support mtrr register manipulation. Can not write to memory without cache. Severity: warning serviceable: no recoverable: no automatically notify support: no user response: complete the following steps: 1. Perform the actions...

  • Page 346

    201-886-001 standalone memory test aborted explanation: memory upper limit is less than 16 mbytes. Severity: warning serviceable: no recoverable: no automatically notify support: no user response: complete the following steps: 1. Perform the actions mentioned one at a time and try the test after eac...

  • Page 347

    201-886-003 standalone memory test aborted explanation: memory upper limit is less than 16 mbytes. Severity: warning serviceable: no recoverable: no automatically notify support: no user response: complete the following steps: 1. Perform the actions mentioned one at a time and try the test after eac...

  • Page 348

    201-899-002 standalone memory test aborted explanation: memory diagnostics test aborted by user. Severity: warning serviceable: no recoverable: no automatically notify support: no related links: v ibm support website v latest level of dsa v latest level of bmc/imm 201-899-003 standalone memory test ...

  • Page 349

    201-901-001 standalone memory test failed explanation: memory diagnostics test failed. Severity: error serviceable: yes recoverable: no automatically notify support: no user response: complete the following steps: 1. Perform the actions mentioned one at a time and try the test after each action. 2. ...

  • Page 350

    201-901-003 standalone memory test failed explanation: memory diagnostics test failed. Severity: error serviceable: yes recoverable: no automatically notify support: no user response: complete the following steps: 1. Perform the actions mentioned one at a time and try the test after each action. 2. ...

  • Page 351

    202-801-000 memstr test aborted explanation: internal program error. Severity: warning serviceable: yes recoverable: no automatically notify support: no user response: complete the following steps: 1. Turn off and restart the system. 2. Make sure that the dsa diagnostic code is at the latest level. ...

  • Page 352

    202-803-000 memstr test aborted explanation: user pressed ctrl-c. Severity: warning serviceable: yes recoverable: no automatically notify support: no related links: v ibm support website v latest level of dsa v latest level of bmc/imm 202-901-000 memstr test failed explanation: test failed. Severity...

  • Page 353

    202-902-000 memstr test failed explanation: memory size is insufficient to run the test. Severity: error serviceable: yes recoverable: no automatically notify support: no user response: complete the following steps: 1. Ensure that all memory is enabled by checking the "available system memory" in th...

  • Page 354

    409-003-000 nvidia::diagnosticserviceprovider::bandwidth test passed explanation: nvidia gpu bandwidth test passed. Severity: event serviceable: no recoverable: no automatically notify support: no related links: v ibm support website v latest level of dsa v latest level of bmc/imm 409-004-000 nvidia...

  • Page 355

    409-006-000 nvidia::diagnosticserviceprovider::binomial test passed explanation: nvidia gpu binomial test passed. Severity: event serviceable: no recoverable: no automatically notify support: no related links: v ibm support website v latest level of dsa v latest level of bmc/imm 409-800-000 nvidia u...

  • Page 356

    409-804-000 nvidia::diagnosticserviceprovider::query test aborted explanation: nvidia gpu query test was canceled. Severity: warning serviceable: no recoverable: no automatically notify support: no related links: v ibm support website v latest level of dsa v latest level of bmc/imm 409-805-000 nvidi...

  • Page 357

    409-900-000 nvidia user diagnostic test failed explanation: nvidia user diagnostic test failed. Severity: event serviceable: yes recoverable: no automatically notify support: no user response: complete the following steps: 1. Verify that the gpu is seated in the pcie slot correctly by reseating the ...

  • Page 358

    409-904-000 nvidia::diagnosticserviceprovider::query test failed explanation: nvidia gpu query test failed. Severity: error serviceable: yes recoverable: no automatically notify support: no user response: complete the following steps: 1. Verify that the gpu is seated in the pcie slot correctly by re...

  • Page 359

    409-906-000 nvidia::diagnosticserviceprovider::binomial test failed explanation: nvidia gpu binomial test failed. Severity: error serviceable: yes recoverable: no automatically notify support: no user response: complete the following steps: 1. Verify that the gpu is seated in the pcie slot correctly...

  • Page 360

    215-801-000 optical drive test aborted explanation: optical drive test aborted. Unable to communicate with driver. Severity: warning serviceable: yes recoverable: no automatically notify support: no user response: complete the following steps: 1. Make sure that the dsa diagnostic code is at the late...

  • Page 361

    215-803-000 optical drive test failed explanation: optical drive test failed. Disk may be in use by the operating system. Severity: error serviceable: yes recoverable: no automatically notify support: no user response: complete the following steps: 1. Wait for the system activity to cease 2. Run the...

  • Page 362

    215-901-000 optical drive test aborted explanation: optical drive test aborted. Drive media is not detected. Severity: warning serviceable: yes recoverable: no automatically notify support: no user response: complete the following steps: 1. Insert a new cd or dvd into the drive and wait for 15 secon...

  • Page 363

    215-903-000 optical drive test aborted explanation: optical drive test aborted. Could not access the device. Severity: warning serviceable: yes recoverable: no automatically notify support: no user response: complete the following steps: 1. Insert a new cd or dvd into the drive and wait for 15 secon...

  • Page 364

    166-801-001 imm i2c test aborted explanation: imm returned incorrect response length. Severity: warning serviceable: yes recoverable: no automatically notify support: no user response: perform the actions mentioned one at a time and try the test after each action: 1. Turn off the system and disconne...

  • Page 365

    166-804-001 imm i2c test aborted explanation: invalid command. Severity: warning serviceable: yes recoverable: no automatically notify support: no user response: perform the actions mentioned one at a time and try the test after each action: 1. Turn off the system and disconnect it from power. Wait ...

  • Page 366

    166-807-001 imm i2c test aborted explanation: out of space. Severity: warning serviceable: yes recoverable: no automatically notify support: no user response: perform the actions mentioned one at a time and try the test after each action: 1. Turn off the system and disconnect it from power. Wait for...

  • Page 367

    166-810-001 imm i2c test aborted explanation: request data length invalid. Severity: warning serviceable: yes recoverable: no automatically notify support: no user response: perform the actions mentioned one at a time and try the test after each action: 1. Turn off the system and disconnect it from ...

  • Page 368

    166-813-001 imm i2c test aborted explanation: cannot return number of requested data bytes. Severity: warning serviceable: yes recoverable: no automatically notify support: no user response: perform the actions mentioned one at a time and try the test after each action: 1. Turn off the system and di...

  • Page 369

    166-816-001 imm i2c test aborted explanation: command illegal for specified sensor or record type. Severity: warning serviceable: yes recoverable: no automatically notify support: no user response: perform the actions mentioned one at a time and try the test after each action: 1. Turn off the system...

  • Page 370

    166-819-001 imm i2c test aborted explanation: command response could not be provided. Sdr repository in?Update mode. Severity: warning serviceable: yes recoverable: no automatically notify support: no user response: perform the actions mentioned one at a time and try the test after each action: 1. T...

  • Page 371

    166-822-001 imm i2c test aborted explanation: destination unavailable. Severity: warning serviceable: yes recoverable: no automatically notify support: no user response: perform the actions mentioned one at a time and try the test after each action: 1. Turn off the system and disconnect it from powe...

  • Page 372

    166-901-001 imm i2c test failed explanation: imm indicates failure in host bus (bus 0). Severity: error serviceable: yes recoverable: no automatically notify support: no user response: perform the actions mentioned one at a time and try the test after each action: 1. Turn off the system and disconne...

  • Page 373

    166-903-001 imm i2c test failed explanation: imm indicates failure in memory bus (bus 2). Severity: error serviceable: yes recoverable: no automatically notify support: no user response: perform the actions mentioned one at a time and try the test after each action: 1. Turn off the system and discon...

  • Page 374

    166-905-001 imm i2c test failed explanation: imm indicates failure in sas bus (bus 4). Severity: error serviceable: yes recoverable: no automatically notify support: no user response: perform the actions mentioned one at a time and try the test after each action: 1. Turn off the system and disconnec...

  • Page 375

    166-909-001 imm i2c test failed explanation: imm indicates failure in the vpd bus (memory drawer bus 0). Severity: error serviceable: yes recoverable: no automatically notify support: no user response: perform the actions mentioned one at a time and try the test after each action: 1. Turn off the sy...

  • Page 376

    166-911-001 imm i2c test failed explanation: imm indicates failure in the voltage regulator bus (memory drawer bus 2). Severity: error serviceable: yes recoverable: no automatically notify support: no user response: perform the actions mentioned one at a time and try the test after each action: 1. T...

  • Page 377

    166-913-001 imm i2c test failed explanation: imm indicates failure in the power supply bus (memory drawer bus 4). Severity: error serviceable: yes recoverable: no automatically notify support: no user response: perform the actions mentioned one at a time and try the test after each action: 1. Turn o...

  • Page 378

    264-901-000 tape test failed explanation: an error was found in the tape alert log. Severity: error serviceable: yes recoverable: no automatically notify support: no user response: complete the following steps: 1. Clean the tape drive using the appropriate cleaning media and install new media. 2. Ru...

  • Page 379

    264-903-000 tape test failed explanation: tape test failed. Media is not detected. Severity: error serviceable: yes recoverable: no automatically notify support: no user response: complete the following steps: 1. Clean the tape drive using the appropriate cleaning media and install new media. 2. Run...

  • Page 380

    264-905-000 tape test failed explanation: tape test failed. Software error: invalid request. Severity: error serviceable: yes recoverable: no automatically notify support: no user response: complete the following steps: 1. If the system has stopped responding, turn off and restart the system. 2. Che...

  • Page 381

    264-907-000 tape test failed explanation: an error was found in the block address somewhere. Severity: error serviceable: yes recoverable: no automatically notify support: no user response: complete the following steps: 1. Clean the tape drive using the appropriate cleaning media and install new med...

  • Page 382

    366 ibm system x3850 x5 and x3950 x5 types 7145, 7146, 7143, and 7191: problem determination and service guide.

  • Page 383

    Appendix b. Integrated management module error messages this topic provides descriptions of integrated management module error messages. The imm messages are displayed in the integrated management module (imm) event log. You can view the imm event log through the imm web interface and through ibm dy...

  • Page 384

    Table 25. Events that automatically notify support (continued) event id message string automatically notify support 806f0021-2201ffff fault in slot [physicalconnectorsystemelementname] on system [computersystemelementname]. Yes 806f0021-2582ffff fault in slot [physicalconnectorsystemelementname] on ...

  • Page 385

    Table 25. Events that automatically notify support (continued) event id message string automatically notify support 806f0207-0301ffff [processorelementname] has failed with frb1/bist condition. Yes 806f0207-0302ffff [processorelementname] has failed with frb1/bist condition. Yes 806f0207-0303ffff [p...

  • Page 386

    Table 25. Events that automatically notify support (continued) event id message string automatically notify support 806f020d-040dffff failure predicted on drive [storagevolumeelementname] for array [computersystemelementname]. Yes 806f020d-040effff failure predicted on drive [storagevolumeelementnam...

  • Page 387

    Table 25. Events that automatically notify support (continued) event id message string automatically notify support 806f0813-2582ffff a uncorrectable bus error has occurred on system [computersystemelementname]. Yes 40000001-00000000 management controller [arg1] network initialization complete. Expl...

  • Page 388

    40000004-00000000 ethernet duplex setting modified from [arg1] to [arg2] by user [arg3]. Explanation: the specified user has changed the ethernet duplex setting of the integrated management module external network interface to the specified value. May also be shown as 4000000400000000 or 0x400000040...

  • Page 389

    40000007-00000000 ethernet interface [arg1] by user [arg2]. Explanation: the specified user has enabled or disabled the ethernet interface. May also be shown as 4000000700000000 or 0x4000000700000000 severity: info alert category: none serviceable: no cim information: prefix: imm and id: 0007 snmp t...

  • Page 390

    4000000a-00000000 ip subnet mask of network interface modified from [arg1] to [arg2] by user [arg3]. Explanation: the specified user has changed the subnet mask of the integrated management module external network interface to the specified value. May also be shown as 4000000a00000000 or 0x4000000a0...

  • Page 391

    4000000d-00000000 dhcp[[arg1]] failure, no ip address assigned. Explanation: a dhcp server has failed to assign an ip address to the imm. May also be shown as 4000000d00000000 or 0x4000000d00000000 severity: warning alert category: none serviceable: no cim information: prefix: imm and id: 0013 snmp ...

  • Page 392

    40000010-00000000 security: userid: [arg1] had [arg2] login failures from web client at ip address [arg3]. Explanation: a user has exceeded the maximum allowed number of unsuccessful login attempts from a web browser and has been prevented from logging in for the lockout period. May also be shown as...

  • Page 393

    40000013-00000000 remote access attempt failed. Invalid userid or password received. Userid is [arg1] from telnet client at ip address [arg2]. Explanation: a user has attempted to log in from a telnet session by using an invalid login id or password. May also be shown as 4000001300000000 or 0x400000...

  • Page 394

    40000016-00000000 enet[[arg1]] dhcp-hstn=[arg2], dn=[arg3], ip@=[arg4], sn=[arg5], gw@=[arg6], dns1@=[arg7] . Explanation: the dhcp server has assigned an imm ip address and configuration. May also be shown as 4000001600000000 or 0x4000001600000000 severity: info alert category: none serviceable: no...

  • Page 395

    40000019-00000000 lan: ethernet[[arg1]] interface is now active. Explanation: the imm ethernet interface has been enabled. May also be shown as 4000001900000000 or 0x4000001900000000 severity: info alert category: none serviceable: no cim information: prefix: imm and id: 0025 snmp trap id: automatic...

  • Page 396

    4000001c-00000000 watchdog [arg1] screen capture occurred . Explanation: an operating-system error has occurred, and the screen capture was successful. May also be shown as 4000001c00000000 or 0x4000001c00000000 severity: info alert category: system serviceable: no cim information: prefix: imm and i...

  • Page 397

    4000001e-00000000 running the backup management controller [arg1] main application. Explanation: the imm was unable to run the primary imm image and has resorted to running the backup image. May also be shown as 4000001e00000000 or 0x4000001e00000000 severity: warning alert category: critical servic...

  • Page 398

    40000021-00000000 management controller [arg1] clock has been set from ntp server [arg2]. Explanation: the imm clock has been set to the date and time that are provided by the network time protocol server. May also be shown as 4000002100000000 or 0x4000002100000000 severity: info alert category: non...

  • Page 399

    40000024-00000000 flash of [arg1] from [arg2] failed for user [arg3]. Explanation: the specified firmware has not been updated. May also be shown as 4000002400000000 or 0x4000002400000000 severity: info alert category: critical serviceable: no cim information: prefix: imm and id: 0036 snmp trap id: ...

  • Page 400

    40000027-00000000 platform watchdog timer expired for [arg1]. Explanation: a “platform watchdog timer expired” event has occurred. May also be shown as 4000002700000000 or 0x4000002700000000 severity: error alert category: critical serviceable: no cim information: prefix: imm and id: 0039 snmp trap ...

  • Page 401

    4000002a-00000000 [arg1] firmware mismatch internal to system [arg2]. Please attempt to flash the [arg3] firmware. Explanation: a specific type of firmware mismatch has been detected. May also be shown as 4000002a00000000 or 0x4000002a00000000 severity: error alert category: critical serviceable: no...

  • Page 402

    4000002d-00000000 ddns setting changed to [arg1] by user [arg2]. Explanation: ddns setting changed by user may also be shown as 4000002d00000000 or 0x4000002d00000000 severity: info alert category: none serviceable: no cim information: prefix: imm and id: 0045 snmp trap id: automatically notify supp...

  • Page 403

    40000030-00000000 ipv6 disabled by user [arg1] . Explanation: the specified user has disabled ipv6 support on the integrated management module. May also be shown as 4000003000000000 or 0x4000003000000000 severity: info alert category: none serviceable: no cim information: prefix: imm and id: 0048 sn...

  • Page 404

    40000033-00000000 ipv6 stateless auto-configuration enabled by user [arg1]. Explanation: ipv6 stateless address auto-configuration has been enabled on the integrated management module by the specified user. May also be shown as 4000003300000000 or 0x4000003300000000 severity: info alert category: no...

  • Page 405

    40000036-00000000 ipv6 stateless auto-configuration disabled by user [arg1]. Explanation: ipv6 stateless address auto-configuration has been disabled on the integrated management module by the specified user. May also be shown as 4000003600000000 or 0x4000003600000000 severity: info alert category: ...

  • Page 406

    40000039-00000000 enet[[arg1]] dhcpv6-hstn=[arg2], dn=[arg3], ip@=[arg4], pref=[arg5]. Explanation: the ipv6 dhcp-assigned address is active. May also be shown as 4000003900000000 or 0x4000003900000000 severity: info alert category: none serviceable: no cim information: prefix: imm and id: 0057 snmp...

  • Page 407

    4000003c-00000000 platform watchdog timer expired for [arg1]. Explanation: imm has detected an os did not start in the expected amount of time. May also be shown as 4000003c00000000 or 0x4000003c00000000 severity: error alert category: cricital serviceable: no cim information: prefix: imm and id: 00...

  • Page 408

    80010002-2801ffff numeric sensor [numericsensorelementname] going low (lower non-critical) has asserted. Explanation: the cmos battery voltage has dropped below its specified threshold. May also be shown as 800100022801ffff or 0x800100022801ffff severity: warning alert category: warning serviceable:...

  • Page 409

    80010204-1d01ffff numeric sensor [numericsensorelementname] going low (lower critical) has asserted. Explanation: imm has detected the speed of fan 1 (fan 1a tach or fan 1b tach) has gone low. May also be shown as 800102041d01ffff or 0x800102041d01ffff severity: error alert category: critical servic...

  • Page 410

    80010204-1d04ffff numeric sensor [numericsensorelementname] going low (lower critical) has asserted. Explanation: imm has detected the speed of fan 4 (fan 4a tach or fan 4b tach) has gone low. May also be shown as 800102041d04ffff or 0x800102041d04ffff severity: error alert category: critical servic...

  • Page 411

    80010204-1d07ffff numeric sensor [numericsensorelementname] going low (lower critical) has asserted. Explanation: imm has detected the speed of meu fan 2 has gone low. May also be shown as 800102041d07ffff or 0x800102041d07ffff severity: error alert category: critical serviceable: no cim information...

  • Page 412

    80010204-1d0affff numeric sensor [numericsensorelementname] going low (lower critical) has asserted. Explanation: imm has detected the speed of a fan (meu fan 5 tach) has gone low. May also be shown as 800102041d0affff or 0x800102041d0affff severity: error alert category: critical serviceable: no ci...

  • Page 413

    80010703-1500ffff numeric sensor [numericsensorelementname] going high (upper non-critical) has asserted. Explanation: an upper non-critical current sensor going high has asserted. May also be shown as 800107031500ffff or 0x800107031500ffff severity: warning alert category: warning serviceable: no c...

  • Page 414

    80010902-0701ffff numeric sensor [numericsensorelementname] going high (upper critical) has asserted. Explanation: a voltage has risen above its specified threshold (sensor planar 12v, planar 3.3v, or planar 5v). May also be shown as 800109020701ffff or 0x800109020701ffff severity: error alert categ...

  • Page 415

    80010b01-1801ffff numeric sensor [numericsensorelementname] going high (upper non-recoverable) has asserted. Explanation: an upper non-recoverable sensor going high has asserted. May also be shown as 80010b011801ffff or 0x80010b011801ffff severity: error alert category: critical serviceable: no cim ...

  • Page 416

    8003010c-1881ffff sensor [sensorelementname] has asserted. Explanation: lane failover on smi lane channel on the memory expansion module has occurred. May also be shown as 8003010c1881ffff or 0x8003010c1881ffff severity: info alert category: system serviceable: no cim information: prefix: plat and i...

  • Page 417

    8003010c-2583ffff sensor [sensorelementname] has asserted. Explanation: lane failover on smi lane channel 3 has occurred. May also be shown as 8003010c2583ffff or 0x8003010c2583ffff severity: info alert category: system serviceable: no cim information: prefix: plat and id: 0508 snmp trap id: automat...

  • Page 418

    8003010c-2586ffff sensor [sensorelementname] has asserted. Explanation: lane failover on smi lane channel 6 has occurred. May also be shown as 8003010c2586ffff or 0x8003010c2586ffff severity: info alert category: system serviceable: no cim information: prefix: plat and id: 0508 snmp trap id: automat...

  • Page 419

    8003010e-0701ffff sensor [sensorelementname] has asserted. Explanation: a memory resize has occurred. May also be shown as 8003010e0701ffff or 0x8003010e0701ffff severity: info alert category: system serviceable: no cim information: prefix: plat and id: 0508 snmp trap id: automatically notify suppor...

  • Page 420

    80070201-0303ffff sensor [sensorelementname] has transitioned to critical from a less severe state. Explanation: imm has detected a cpu 3 temperature sensor has transitioned to critical. May also be shown as 800702010303ffff or 0x800702010303ffff severity: error alert category: critical serviceable:...

  • Page 421

    80070201-0a01ffff sensor [sensorelementname] has transitioned to critical from a less severe state. Explanation: imm has detected a ps 1 temperature sensor has transitioned to critical. May also be shown as 800702010a01ffff or 0x800702010a01ffff severity: error alert category: critical serviceable: ...

  • Page 422

    80070201-1881ffff sensor [sensorelementname] has transitioned to critical from a less severe state. Explanation: imm has detected a meu ps temperature sensor has transitioned to critical. May also be shown as 800702011881ffff or 0x800702011881ffff severity: error alert category: critical serviceable...

  • Page 423

    A. Check the serverproven website to make sure that recently installed components are compatible with the compute node. B. Inspect the previously installed components for physical damage. V if the node does not successfully power on or if this is not the first occurrence of this problem, (trained se...

  • Page 424

    80070208-1881ffff sensor [sensorelementname] has transitioned to critical from a less severe state. Explanation: memory expansion module power failure. May also be shown as 800702081881ffff or 0x800702081881ffff severity: error alert category: critical serviceable: no cim information: prefix: plat a...

  • Page 425

    80070301-0302ffff sensor [sensorelementname] has transitioned to non-recoverable from a less severe state. Explanation: imm has detected that the temperature for cpu 2 has transitioned to a non recoverable state. May also be shown as 800703010302ffff or 0x800703010302ffff severity: error alert categ...

  • Page 426

    80070301-0304ffff sensor [sensorelementname] has transitioned to non-recoverable from a less severe state. Explanation: imm has detected that the temperature for cpu 4 has transitioned to a non recoverable state. May also be shown as 800703010304ffff or 0x800703010304ffff severity: error alert categ...

  • Page 427

    80070603-0701ffff sensor [sensorelementname] has transitioned to non-recoverable. Explanation: a sensor (pwr rail a/b/c/d/e/f/g/h fault) has transitioned to non-recoverable state. May also be shown as 800706030701ffff or 0x800706030701ffff severity: error alert category: critical serviceable: yes ci...

  • Page 428

    80070608-0a02ffff sensor [sensorelementname] has transitioned to non-recoverable. Explanation: imm has detected power supply related fault. (ps 12v oc fault, ps 12v ov fault, ps 12v uv fault, or ps aux uv fault) may also be shown as 800706080a02ffff or 0x800706080a02ffff severity: error alert catego...

  • Page 429

    16. 5. Remove memory card identified and check for connector pin damage on memory card and cpu memory card slot. 17. A) replace affected commodity if damage is found. 18. 6. Swap the memory card in the slot identified, with a memory card from another slot with the same configuration of dimms (size, ...

  • Page 430

    8. 4. Swap the memory card in the slot identified, with a memory card from another slot with the same configuration of dimms (size, type, number) 9. 5. Restart the server and see if problem still identifies the same memory card slot. 10. A) if problem remains with original slot, replace the i/o boar...

  • Page 431

    80070608-1403ffff sensor [sensorelementname] has transitioned to non-recoverable. Explanation: a system power fault has occurred. May also be shown as 800706081403ffff or 0x800706081403ffff severity: error alert category: critical serviceable: no cim information: prefix: plat and id: 0530 snmp trap ...

  • Page 432

    30. 5. Remove memory card identified and check for connector pin damage on memory card and cpu memory card slot. 31. A) replace affected commodity if damage is found. 32. 6. Swap the memory card in the slot identified, with a memory card from another slot with the same configuration of dimms (size, ...

  • Page 433

    23. 2. If local, pull out the operator information panel, observe and make note of what is being displayed on the checkpoint display for support reference. 24. 3. Using the imm web interface, capture a 'service data' file (note:) for support reference. 25. 4. (trained service technician only) replac...

  • Page 434

    16. 5. Remove memory card identified and check for connector pin damage on memory card and cpu memory card slot. 17. A) replace affected commodity if damage is found. 18. 6. Swap the memory card in the slot identified, with a memory card from another slot with the same configuration of dimms (size, ...

  • Page 435

    8. 4. Swap the memory card in the slot identified, with a memory card from another slot with the same configuration of dimms (size, type, number) 9. 5. Restart the server and see if problem still identifies the same memory card slot. 10. A) if problem remains with original slot, replace the i/o boar...

  • Page 436

    80070608-1407ffff sensor [sensorelementname] has transitioned to non-recoverable. Explanation: a system power fault has occurred. May also be shown as 800706081407ffff or 0x800706081407ffff severity: error alert category: critical serviceable: no cim information: prefix: plat and id: 0530 snmp trap ...

  • Page 437

    30. 5. Remove memory card identified and check for connector pin damage on memory card and cpu memory card slot. 31. A) replace affected commodity if damage is found. 32. 6. Swap the memory card in the slot identified, with a memory card from another slot with the same configuration of dimms (size, ...

  • Page 438

    23. 2. If local, pull out the operator information panel, observe and make note of what is being displayed on the checkpoint display for support reference. 24. 3. Using the imm web interface, capture a 'service data' file (note:) for support reference. 25. 4. (trained service technician only) replac...

  • Page 439

    6. 4. If the checkpoint display repeatedly blinks f:a then 6:9 7. - (trained service technician only) replace the cpu board and i/o board assembly 80070608-140bffff sensor [sensorelementname] has transitioned to non-recoverable. Explanation: a cpu vrd failure has occurre. May also be shown as 800706...

  • Page 440

    80070608-140dffff sensor [sensorelementname] has transitioned to non-recoverable. Explanation: a cpu vrd failure has occurre. May also be shown as 80070608140dffff or 0x80070608140dffff severity: error alert category: critical serviceable: no cim information: prefix: plat and id: 0530 snmp trap id: ...

  • Page 441

    80070608-140fffff sensor [sensorelementname] has transitioned to non-recoverable. Explanation: a cpu 3 4 vio fault has occurred. May also be shown as 80070608140fffff or 0x80070608140fffff severity: error alert category: critical serviceable: no cim information: prefix: plat and id: 0530 snmp trap i...

  • Page 442

    80070608-1412ffff sensor [sensorelementname] has transitioned to non-recoverable. Explanation: a system power fault has occurred. May also be shown as 800706081412ffff or 0x800706081412ffff severity: error alert category: critical serviceable: no cim information: prefix: plat and id: 0530 snmp trap ...

  • Page 443

    80070608-1415ffff sensor [sensorelementname] has transitioned to non-recoverable. Explanation: a system power fault has occurred. May also be shown as 800706081415ffff or 0x800706081415ffff severity: error alert category: critical serviceable: no cim information: prefix: plat and id: 0530 snmp trap ...

  • Page 444

    80080004-1d01ffff device [logicaldeviceelementname] has been removed from unit [physicalpackageelementname]. Explanation: device fan 1 has been removed. May also be shown as 800800041d01ffff or 0x800800041d01ffff severity: info alert category: system serviceable: no cim information: prefix: plat and...

  • Page 445

    80080004-1d04ffff device [logicaldeviceelementname] has been removed from unit [physicalpackageelementname]. Explanation: device fan 4 has been removed. May also be shown as 800800041d04ffff or 0x800800041d04ffff severity: info alert category: system serviceable: no cim information: prefix: plat and...

  • Page 446

    80080004-1d07ffff device [logicaldeviceelementname] has been removed from unit [physicalpackageelementname]. Explanation: device meu fan 2 has been removed. May also be shown as 800800041d07ffff or 0x800800041d07ffff severity: info alert category: system serviceable: no cim information: prefix: plat...

  • Page 447

    80080004-1d0affff device [logicaldeviceelementname] has been removed from unit [physicalpackageelementname]. Explanation: device meu fan 5 has been removed. May also be shown as 800800041d0affff or 0x800800041d0affff severity: info alert category: system serviceable: no cim information: prefix: plat...

  • Page 448

    800b0108-1381ffff redundancy lost for [redundancysetelementname] has asserted. Explanation: power supply redundancy has been lost. May also be shown as 800b01081381ffff or 0x800b01081381ffff severity: error alert category: critical serviceable: yes cim information: prefix: plat and id: 0802 snmp tra...

  • Page 449

    800b010a-1e82ffff redundancy lost for [redundancysetelementname] has asserted. Explanation: fan redundancy has been lost. May also be shown as 800b010a1e82ffff or 0x800b010a1e82ffff severity: error alert category: critical serviceable: yes cim information: prefix: plat and id: 0802 snmp trap id: 11 ...

  • Page 450

    800b010c-2581ffff redundancy lost for [redundancysetelementname] has asserted. Explanation: backup memory redundancy has been lost. May also be shown as 800b010c2581ffff or 0x800b010c2581ffff severity: error alert category: critical serviceable: yes cim information: prefix: plat and id: 0802 snmp tr...

  • Page 451

    800b030c-2581ffff non-redundant:sufficient resources from redundancy degraded or fully redundant for [redundancysetelementname] has asserted. Explanation: backup memory has transitioned from redundancy degraded or fully redundant to non-redundant:sufficient. May also be shown as 800b030c2581ffff or ...

  • Page 452

    800b050a-1e83ffff non-redundant:insufficient resources for [redundancysetelementname] has asserted. Explanation: insufficient cooling provided by fan 3. May also be shown as 800b050a1e83ffff or 0x800b050a1e83ffff severity: error alert category: critical serviceable: yes cim information: prefix: plat...

  • Page 453

    806f0007-0301ffff [processorelementname] has failed with ierr. Explanation: imm has detected processor 1 failed - ierr condition. May also be shown as 806f00070301ffff or 0x806f00070301ffff severity: error alert category: critical serviceable: yes cim information: prefix: plat and id: 0042 snmp trap...

  • Page 454

    806f0007-0303ffff [processorelementname] has failed with ierr. Explanation: imm has detected processor 3 failed - ierr condition. May also be shown as 806f00070303ffff or 0x806f00070303ffff severity: error alert category: critical serviceable: yes cim information: prefix: plat and id: 0042 snmp trap...

  • Page 455

    806f0008-0a01ffff [powersupplyelementname] has been added to container [physicalpackageelementname]. Explanation: imm has detected a power supply has been added. May also be shown as 806f00080a01ffff or 0x806f00080a01ffff severity: info alert category: system serviceable: no cim information: prefix:...

  • Page 456

    806f0009-1381ffff [powersupplyelementname] has been turned off. Explanation: imm has detected that the system power has been turned off. May also be shown as 806f00091381ffff or 0x806f00091381ffff severity: info alert category: system serviceable: no cim information: prefix: plat and id: 0106 snmp t...

  • Page 457

    806f000d-0402ffff the drive [storagevolumeelementname] has been added. Explanation: hard drive 2 has been installed. May also be shown as 806f000d0402ffff or 0x806f000d0402ffff severity: info alert category: critical serviceable: no cim information: prefix: plat and id: 0162 snmp trap id: 5 automati...

  • Page 458

    806f000d-0405ffff the drive [storagevolumeelementname] has been added. Explanation: hard drive 5 has been installed. May also be shown as 806f000d0405ffff or 0x806f000d0405ffff severity: info alert category: critical serviceable: no cim information: prefix: plat and id: 0162 snmp trap id: 5 automati...

  • Page 459

    806f000d-0408ffff the drive [storagevolumeelementname] has been added. Explanation: hard drive 8 has been installed. May also be shown as 806f000d0408ffff or 0x806f000d0408ffff severity: info alert category: critical serviceable: no cim information: prefix: plat and id: 0162 snmp trap id: 5 automati...

  • Page 460

    806f000d-040bffff the drive [storagevolumeelementname] has been added. Explanation: hard drive 11 has been installed. May also be shown as 806f000d040bffff or 0x806f000d040bffff severity: info alert category: critical serviceable: no cim information: prefix: plat and id: 0162 snmp trap id: 5 automat...

  • Page 461

    806f000d-040effff the drive [storagevolumeelementname] has been added. Explanation: hard drive 14 has been installed. May also be shown as 806f000d040effff or 0x806f000d040effff severity: info alert category: critical serviceable: no cim information: prefix: plat and id: 0162 snmp trap id: 5 automat...

  • Page 462

    806f000f-220102ff subsystem [memoryelementname] has insufficient memory for operation. Explanation: imm has detected that the usable memory is insufficient for operation. (abr status, firmware error) may also be shown as 806f000f220102ff or 0x806f000f220102ff severity: error alert category: critical...

  • Page 463

    806f000f-220107ff the system [computersystemelementname] encountered firmware error - unrecoverable keyboard failure. Explanation: imm has detected that system firmware error unrecoverable keyboard failure has occurred. May also be shown as 806f000f220107ff or 0x806f000f220107ff severity: error aler...

  • Page 464

    806f000f-22010cff cpu voltage mismatch detected on [processorelementname]. Explanation: imm has detected a cpu voltage mismatch with the cpu socket voltage. May also be shown as 806f000f22010cff or 0x806f000f22010cff severity: error alert category: critical serviceable: yes cim information: prefix: ...

  • Page 465

    806f001b-1f08ffff the network port [managedelementname] has been connected. Explanation: exa cable 2 is connected may also be shown as 806f001b1f08ffff or 0x806f001b1f08ffff severity: info alert category: warning serviceable: no cim information: prefix: plat and id: 0262 snmp trap id: 60 automatical...

  • Page 466

    806f0021-0b04ffff fault in slot [physicalconnectorsystemelementname] on system [computersystemelementname]. Explanation: imm has detected a fault in pcie slot 1. May also be shown as 806f00210b04ffff or 0x806f00210b04ffff severity: error alert category: critical serviceable: yes cim information: pre...

  • Page 467

    806f0021-0b06ffff fault in slot [physicalconnectorsystemelementname] on system [computersystemelementname]. Explanation: imm has detected a fault in pcie slot 3. May also be shown as 806f00210b06ffff or 0x806f00210b06ffff severity: error alert category: critical serviceable: yes cim information: pre...

  • Page 468

    806f0021-0b08ffff fault in slot [physicalconnectorsystemelementname] on system [computersystemelementname]. Explanation: imm has detected a fault in pcie slot 5. May also be shown as 806f00210b08ffff or 0x806f00210b08ffff severity: error alert category: critical serviceable: yes cim information: pre...

  • Page 469

    806f0021-0b0affff fault in slot [physicalconnectorsystemelementname] on system [computersystemelementname]. Explanation: imm has detected a fault in pcie slot 7. May also be shown as 806f00210b0affff or 0x806f00210b0affff severity: error alert category: critical serviceable: no cim information: pref...

  • Page 470

    For the appropriate user response. 806f0023-2101ffff watchdog timer expired for [watchdogelementname]. Explanation: the ipmi watchdog timer has expired. May also be shown as 806f00232101ffff or 0x806f00232101ffff severity: info alert category: system serviceable: no cim information: prefix: plat and...

  • Page 471

    806f0107-0301ffff an over-temperature condition has been detected on [processorelementname]. Explanation: the microprocessor 1 temperature has risen above the critical level, causing a hard shutdown of the node. May also be shown as 806f01070301ffff or 0x806f01070301ffff severity: error alert catego...

  • Page 472

    806f0107-0303ffff an over-temperature condition has been detected on [processorelementname]. Explanation: the microprocessor 3 temperature has risen above the critical level, causing a hard shutdown of the node. May also be shown as 806f01070303ffff or 0x806f01070303ffff severity: error alert catego...

  • Page 473

    806f0108-0a01ffff [powersupplyelementname] has failed. Explanation: imm has detected a fault on power supply 1. May also be shown as 806f01080a01ffff or 0x806f01080a01ffff severity: error alert category: critical serviceable: yes cim information: prefix: plat and id: 0086 snmp trap id: 4 automatical...

  • Page 474

    806f0109-1381ffff [powersupplyelementname] has been power cycled. Explanation: system has been power cycled. May also be shown as 806f01091381ffff or 0x806f01091381ffff severity: info alert category: system serviceable: no cim information: prefix: plat and id: 0108 snmp trap id: automatically notify...

  • Page 475

    806f010c-08810002 uncorrectable error detected for [physicalmemoryelementname] on subsystem [memoryelementname]. Explanation: a memory uncorrectable error has occured in dimm 2 of mem card 1. May also be shown as 806f010c08810002 or 0x806f010c08810002 severity: error alert category: critical service...

  • Page 476

    806f010c-08810004 uncorrectable error detected for [physicalmemoryelementname] on subsystem [memoryelementname]. Explanation: a memory uncorrectable error has occured in dimm 4 of mem card 1. May also be shown as 806f010c08810004 or 0x806f010c08810004 severity: error alert category: critical service...

  • Page 477

    806f010c-08810006 uncorrectable error detected for [physicalmemoryelementname] on subsystem [memoryelementname]. Explanation: a memory uncorrectable error has occured in dimm 6 of mem card 1. May also be shown as 806f010c08810006 or 0x806f010c08810006 severity: error alert category: critical service...

  • Page 478

    806f010c-08810008 uncorrectable error detected for [physicalmemoryelementname] on subsystem [memoryelementname]. Explanation: a memory uncorrectable error has occured in dimm 8 of mem card 1. May also be shown as 806f010c08810008 or 0x806f010c08810008 severity: error alert category: critical service...

  • Page 479

    806f010c-08820002 uncorrectable error detected for [physicalmemoryelementname] on subsystem [memoryelementname]. Explanation: a memory uncorrectable error has occured in dimm 2 of mem card 2. May also be shown as 806f010c08820002 or 0x806f010c08820002 severity: error alert category: critical service...

  • Page 480

    806f010c-08820004 uncorrectable error detected for [physicalmemoryelementname] on subsystem [memoryelementname]. Explanation: a memory uncorrectable error has occured in dimm 4 of mem card 2. May also be shown as 806f010c08820004 or 0x806f010c08820004 severity: error alert category: critical service...

  • Page 481

    806f010c-08820006 uncorrectable error detected for [physicalmemoryelementname] on subsystem [memoryelementname]. Explanation: a memory uncorrectable error has occured in dimm 6 of mem card 2. May also be shown as 806f010c08820006 or 0x806f010c08820006 severity: error alert category: critical service...

  • Page 482

    806f010c-08820008 uncorrectable error detected for [physicalmemoryelementname] on subsystem [memoryelementname]. Explanation: a memory uncorrectable error has occured in dimm 8 of mem card 2. May also be shown as 806f010c08820008 or 0x806f010c08820008 severity: error alert category: critical service...

  • Page 483

    806f010c-08830002 uncorrectable error detected for [physicalmemoryelementname] on subsystem [memoryelementname]. Explanation: a memory uncorrectable error has occured in dimm 2 of mem card 3. May also be shown as 806f010c08830002 or 0x806f010c08830002 severity: error alert category: critical service...

  • Page 484

    806f010c-08830004 uncorrectable error detected for [physicalmemoryelementname] on subsystem [memoryelementname]. Explanation: a memory uncorrectable error has occured in dimm 4 of mem card 3. May also be shown as 806f010c08830004 or 0x806f010c08830004 severity: error alert category: critical service...

  • Page 485

    806f010c-08830006 uncorrectable error detected for [physicalmemoryelementname] on subsystem [memoryelementname]. Explanation: a memory uncorrectable error has occured in dimm 6 of mem card 3. May also be shown as 806f010c08830006 or 0x806f010c08830006 severity: error alert category: critical service...

  • Page 486

    806f010c-08830008 uncorrectable error detected for [physicalmemoryelementname] on subsystem [memoryelementname]. Explanation: a memory uncorrectable error has occured in dimm 8 of mem card 3. May also be shown as 806f010c08830008 or 0x806f010c08830008 severity: error alert category: critical service...

  • Page 487

    806f010c-08840002 uncorrectable error detected for [physicalmemoryelementname] on subsystem [memoryelementname]. Explanation: a memory uncorrectable error has occured in dimm 2 of mem card 4. May also be shown as 806f010c08840002 or 0x806f010c08840002 severity: error alert category: critical service...

  • Page 488

    806f010c-08840004 uncorrectable error detected for [physicalmemoryelementname] on subsystem [memoryelementname]. Explanation: a memory uncorrectable error has occured in dimm 4 of mem card 4. May also be shown as 806f010c08840004 or 0x806f010c08840004 severity: error alert category: critical service...

  • Page 489

    806f010c-08840006 uncorrectable error detected for [physicalmemoryelementname] on subsystem [memoryelementname]. Explanation: a memory uncorrectable error has occured in dimm 6 of mem card 4. May also be shown as 806f010c08840006 or 0x806f010c08840006 severity: error alert category: critical service...

  • Page 490

    806f010c-08840008 uncorrectable error detected for [physicalmemoryelementname] on subsystem [memoryelementname]. Explanation: a memory uncorrectable error has occured in dimm 8 of mem card 4. May also be shown as 806f010c08840008 or 0x806f010c08840008 severity: error alert category: critical service...

  • Page 491

    806f010c-08850002 uncorrectable error detected for [physicalmemoryelementname] on subsystem [memoryelementname]. Explanation: a memory uncorrectable error has occured in dimm 2 of mem card 5. May also be shown as 806f010c08850002 or 0x806f010c08850002 severity: error alert category: critical service...

  • Page 492

    806f010c-08850004 uncorrectable error detected for [physicalmemoryelementname] on subsystem [memoryelementname]. Explanation: a memory uncorrectable error has occured in dimm 4 of mem card 5. May also be shown as 806f010c08850004 or 0x806f010c08850004 severity: error alert category: critical service...

  • Page 493

    806f010c-08850006 uncorrectable error detected for [physicalmemoryelementname] on subsystem [memoryelementname]. Explanation: a memory uncorrectable error has occured in dimm 6 of mem card 5. May also be shown as 806f010c08850006 or 0x806f010c08850006 severity: error alert category: critical service...

  • Page 494

    806f010c-08850008 uncorrectable error detected for [physicalmemoryelementname] on subsystem [memoryelementname]. Explanation: a memory uncorrectable error has occured in dimm 8 of mem card 5. May also be shown as 806f010c08850008 or 0x806f010c08850008 severity: error alert category: critical service...

  • Page 495

    806f010c-08860002 uncorrectable error detected for [physicalmemoryelementname] on subsystem [memoryelementname]. Explanation: a memory uncorrectable error has occured in dimm 2 of mem card 6. May also be shown as 806f010c08860002 or 0x806f010c08860002 severity: error alert category: critical service...

  • Page 496

    806f010c-08860004 uncorrectable error detected for [physicalmemoryelementname] on subsystem [memoryelementname]. Explanation: a memory uncorrectable error has occured in dimm 4 of mem card 6. May also be shown as 806f010c08860004 or 0x806f010c08860004 severity: error alert category: critical service...

  • Page 497

    806f010c-08860006 uncorrectable error detected for [physicalmemoryelementname] on subsystem [memoryelementname]. Explanation: a memory uncorrectable error has occured in dimm 6 of mem card 6. May also be shown as 806f010c08860006 or 0x806f010c08860006 severity: error alert category: critical service...

  • Page 498

    806f010c-08860008 uncorrectable error detected for [physicalmemoryelementname] on subsystem [memoryelementname]. Explanation: a memory uncorrectable error has occured in dimm 8 of mem card 6. May also be shown as 806f010c08860008 or 0x806f010c08860008 severity: error alert category: critical service...

  • Page 499

    806f010c-08870002 uncorrectable error detected for [physicalmemoryelementname] on subsystem [memoryelementname]. Explanation: a memory uncorrectable error has occured in dimm 2 of mem card 7. May also be shown as 806f010c08870002 or 0x806f010c08870002 severity: error alert category: critical service...

  • Page 500

    806f010c-08870004 uncorrectable error detected for [physicalmemoryelementname] on subsystem [memoryelementname]. Explanation: a memory uncorrectable error has occured in dimm 4 of mem card 7. May also be shown as 806f010c08870004 or 0x806f010c08870004 severity: error alert category: critical service...

  • Page 501

    806f010c-08870006 uncorrectable error detected for [physicalmemoryelementname] on subsystem [memoryelementname]. Explanation: a memory uncorrectable error has occured in dimm 6 of mem card 7. May also be shown as 806f010c08870006 or 0x806f010c08870006 severity: error alert category: critical service...

  • Page 502

    806f010c-08870008 uncorrectable error detected for [physicalmemoryelementname] on subsystem [memoryelementname]. Explanation: a memory uncorrectable error has occured in dimm 8 of mem card 7. May also be shown as 806f010c08870008 or 0x806f010c08870008 severity: error alert category: critical service...

  • Page 503

    806f010c-08880002 uncorrectable error detected for [physicalmemoryelementname] on subsystem [memoryelementname]. Explanation: a memory uncorrectable error has occured in dimm 2 of mem card 8. May also be shown as 806f010c08880002 or 0x806f010c08880002 severity: error alert category: critical service...

  • Page 504

    806f010c-08880004 uncorrectable error detected for [physicalmemoryelementname] on subsystem [memoryelementname]. Explanation: a memory uncorrectable error has occured in dimm 4 of mem card 8. May also be shown as 806f010c08880004 or 0x806f010c08880004 severity: error alert category: critical service...

  • Page 505

    806f010c-08880006 uncorrectable error detected for [physicalmemoryelementname] on subsystem [memoryelementname]. Explanation: a memory uncorrectable error has occured in dimm 6 of mem card 8. May also be shown as 806f010c08880006 or 0x806f010c08880006 severity: error alert category: critical service...

  • Page 506

    806f010c-08880008 uncorrectable error detected for [physicalmemoryelementname] on subsystem [memoryelementname]. Explanation: a memory uncorrectable error has occured in dimm 8 of mem card 8. May also be shown as 806f010c08880008 or 0x806f010c08880008 severity: error alert category: critical service...

  • Page 507

    806f010c-18810002 uncorrectable error detected for [physicalmemoryelementname] on subsystem [memoryelementname]. Explanation: a memory uncorrectable error has occured in dimm 2 of memory expansion unit(meu). May also be shown as 806f010c18810002 or 0x806f010c18810002 severity: error alert category: ...

  • Page 508

    806f010c-18810004 uncorrectable error detected for [physicalmemoryelementname] on subsystem [memoryelementname]. Explanation: a memory uncorrectable error has occured in dimm 4 of memory expansion unit(meu). May also be shown as 806f010c18810004 or 0x806f010c18810004 severity: error alert category: ...

  • Page 509

    806f010c-18810006 uncorrectable error detected for [physicalmemoryelementname] on subsystem [memoryelementname]. Explanation: a memory uncorrectable error has occured in dimm 6 of memory expansion unit(meu). May also be shown as 806f010c18810006 or 0x806f010c18810006 severity: error alert category: ...

  • Page 510

    806f010c-18810008 uncorrectable error detected for [physicalmemoryelementname] on subsystem [memoryelementname]. Explanation: a memory uncorrectable error has occured in dimm 8 of memory expansion unit(meu). May also be shown as 806f010c18810008 or 0x806f010c18810008 severity: error alert category: ...

  • Page 511

    806f010c-1881000a uncorrectable error detected for [physicalmemoryelementname] on subsystem [memoryelementname]. Explanation: a memory uncorrectable error has occured in dimm 10 of memory expansion unit(meu). May also be shown as 806f010c1881000a or 0x806f010c1881000a severity: error alert category:...

  • Page 512

    806f010c-1881000c uncorrectable error detected for [physicalmemoryelementname] on subsystem [memoryelementname]. Explanation: a memory uncorrectable error has occured in dimm 12 of memory expansion unit(meu). May also be shown as 806f010c1881000c or 0x806f010c1881000c severity: error alert category:...

  • Page 513

    806f010c-1881000e uncorrectable error detected for [physicalmemoryelementname] on subsystem [memoryelementname]. Explanation: a memory uncorrectable error has occured in dimm 14 of memory expansion unit(meu). May also be shown as 806f010c1881000e or 0x806f010c1881000e severity: error alert category:...

  • Page 514

    806f010c-18810010 uncorrectable error detected for [physicalmemoryelementname] on subsystem [memoryelementname]. Explanation: a memory uncorrectable error has occured in dimm 16 of memory expansion unit(meu). May also be shown as 806f010c18810010 or 0x806f010c18810010 severity: error alert category:...

  • Page 515

    806f010c-18810012 uncorrectable error detected for [physicalmemoryelementname] on subsystem [memoryelementname]. Explanation: a memory uncorrectable error has occured in dimm 18 of memory expansion unit(meu). May also be shown as 806f010c18810012 or 0x806f010c18810012 severity: error alert category:...

  • Page 516

    806f010c-18810014 uncorrectable error detected for [physicalmemoryelementname] on subsystem [memoryelementname]. Explanation: a memory uncorrectable error has occured in dimm 20 of memory expansion unit(meu). May also be shown as 806f010c18810014 or 0x806f010c18810014 severity: error alert category:...

  • Page 517

    806f010c-18810016 uncorrectable error detected for [physicalmemoryelementname] on subsystem [memoryelementname]. Explanation: a memory uncorrectable error has occured in dimm 22 of memory expansion unit(meu). May also be shown as 806f010c18810016 or 0x806f010c18810016 severity: error alert category:...

  • Page 518

    806f010c-18810018 uncorrectable error detected for [physicalmemoryelementname] on subsystem [memoryelementname]. Explanation: a memory uncorrectable error has occured in dimm 24 of memory expansion unit(meu). May also be shown as 806f010c18810018 or 0x806f010c18810018 severity: error alert category:...

  • Page 519

    806f010c-1881001a uncorrectable error detected for [physicalmemoryelementname] on subsystem [memoryelementname]. Explanation: a memory uncorrectable error has occured in dimm 26 of memory expansion unit(meu). May also be shown as 806f010c1881001a or 0x806f010c1881001a severity: error alert category:...

  • Page 520

    806f010c-1881001c uncorrectable error detected for [physicalmemoryelementname] on subsystem [memoryelementname]. Explanation: a memory uncorrectable error has occured in dimm 28 of memory expansion unit(meu). May also be shown as 806f010c1881001c or 0x806f010c1881001c severity: error alert category:...

  • Page 521

    806f010c-1881001e uncorrectable error detected for [physicalmemoryelementname] on subsystem [memoryelementname]. Explanation: a memory uncorrectable error has occured in dimm 30 of memory expansion unit(meu). May also be shown as 806f010c1881001e or 0x806f010c1881001e severity: error alert category:...

  • Page 522

    806f010c-18810020 uncorrectable error detected for [physicalmemoryelementname] on subsystem [memoryelementname]. Explanation: a memory uncorrectable error has occured in dimm 32 of memory expansion unit(meu). May also be shown as 806f010c18810020 or 0x806f010c18810020 severity: error alert category:...

  • Page 523

    806f010d-0400ffff the drive [storagevolumeelementname] has been disabled due to a detected fault. Explanation: the drive 0 has been disabled (defunct) due to a fault detected by the controller. May also be shown as 806f010d0400ffff or 0x806f010d0400ffff severity: error alert category: critical servi...

  • Page 524

    806f010d-0402ffff the drive [storagevolumeelementname] has been disabled due to a detected fault. Explanation: the drive 2 has been disabled (defunct) due to a fault detected by the controller. May also be shown as 806f010d0402ffff or 0x806f010d0402ffff severity: error alert category: critical servi...

  • Page 525

    806f010d-0404ffff the drive [storagevolumeelementname] has been disabled due to a detected fault. Explanation: the drive 4 has been disabled (defunct) due to a fault detected by the controller. May also be shown as 806f010d0404ffff or 0x806f010d0404ffff severity: error alert category: critical servi...

  • Page 526

    806f010d-0406ffff the drive [storagevolumeelementname] has been disabled due to a detected fault. Explanation: the drive 6 has been disabled (defunct) due to a fault detected by the controller. May also be shown as 806f010d0406ffff or 0x806f010d0406ffff severity: error alert category: critical servi...

  • Page 527

    806f010d-0408ffff the drive [storagevolumeelementname] has been disabled due to a detected fault. Explanation: the drive 8 has been disabled (defunct) due to a fault detected by the controller. May also be shown as 806f010d0408ffff or 0x806f010d0408ffff severity: error alert category: critical servi...

  • Page 528

    806f010d-040affff the drive [storagevolumeelementname] has been disabled due to a detected fault. Explanation: the drive 10 has been disabled (defunct) due to a fault detected by the controller. May also be shown as 806f010d040affff or 0x806f010d040affff severity: error alert category: critical serv...

  • Page 529

    806f010d-040cffff the drive [storagevolumeelementname] has been disabled due to a detected fault. Explanation: the drive 12 has been disabled (defunct) due to a fault detected by the controller. May also be shown as 806f010d040cffff or 0x806f010d040cffff severity: error alert category: critical serv...

  • Page 530

    806f010d-040effff the drive [storagevolumeelementname] has been disabled due to a detected fault. Explanation: the drive 14 has been disabled (defunct) due to a fault detected by the controller. May also be shown as 806f010d040effff or 0x806f010d040effff severity: error alert category: critical serv...

  • Page 531

    806f010f-2201ffff the system [computersystemelementname] encountered a firmware hang. Explanation: imm has detected a system firmware hang. May also be shown as 806f010f2201ffff or 0x806f010f2201ffff severity: error alert category: critical serviceable: yes cim information: prefix: plat and id: 0186...

  • Page 532

    4. If the sensor name is "qpi wrap card x", 5. A) the qpi wrap card, if installed. 6. B) reseat any installed qpi cables. Attention: do not disconnect or connect any of the cables when the server or memory expansion module has power connected. 7. C) replace the cpu board. 8. If the sensor name is "u...

  • Page 533

    806f011b-1f06ffff the connector [physicalconnectorelementname] has encountered a configuration error. Explanation: a cable configuration error has occurred. May also be shown as 806f011b1f06ffff or 0x806f011b1f06ffff severity: error alert category: critical serviceable: no cim information: prefix: p...

  • Page 534

    806f011b-1f09ffff the connector [physicalconnectorelementname] has encountered a configuration error. Explanation: a cable configuration error has occurred. May also be shown as 806f011b1f09ffff or 0x806f011b1f09ffff severity: error alert category: critical serviceable: no cim information: prefix: p...

  • Page 535

    806f0125-1801ffff [managedelementname] detected as absent. Explanation: imm has detected the memory drawer is absent. May also be shown as 806f01251801ffff or 0x806f01251801ffff severity: info alert category: system serviceable: no cim information: prefix: plat and id: 0392 snmp trap id: automatical...

  • Page 536

    806f0207-0302ffff [processorelementname] has failed with frb1/bist condition. Explanation: imm has detected a miroprocessor 2 failed - frb1/bist condition. May also be shown as 806f02070302ffff or 0x806f02070302ffff severity: error alert category: critical serviceable: yes cim information: prefix: p...

  • Page 537

    806f0207-0304ffff [processorelementname] has failed with frb1/bist condition. Explanation: imm has detected a miroprocessor 4 failed - frb1/bist condition. May also be shown as 806f02070304ffff or 0x806f02070304ffff severity: error alert category: critical serviceable: yes cim information: prefix: p...

  • Page 538

    806f020d-0401ffff failure predicted on drive [storagevolumeelementname] for array [computersystemelementname]. Explanation: failure predicted (pfa) on the hard drive 1. May also be shown as 806f020d0401ffff or 0x806f020d0401ffff severity: warning alert category: warning serviceable: yes cim informat...

  • Page 539

    806f020d-0404ffff failure predicted on drive [storagevolumeelementname] for array [computersystemelementname]. Explanation: failure predicted (pfa) on the hard drive 4. May also be shown as 806f020d0404ffff or 0x806f020d0404ffff severity: warning alert category: warning serviceable: yes cim informat...

  • Page 540

    806f020d-0407ffff failure predicted on drive [storagevolumeelementname] for array [computersystemelementname]. Explanation: failure predicted (pfa) on the hard drive 7. May also be shown as 806f020d0407ffff or 0x806f020d0407ffff severity: warning alert category: warning serviceable: yes cim informat...

  • Page 541

    806f020d-040affff failure predicted on drive [storagevolumeelementname] for array [computersystemelementname]. Explanation: failure predicted (pfa) on the hard drive 10. May also be shown as 806f020d040affff or 0x806f020d040affff severity: warning alert category: warning serviceable: yes cim informa...

  • Page 542

    806f020d-040dffff failure predicted on drive [storagevolumeelementname] for array [computersystemelementname]. Explanation: failure predicted (pfa) on the hard drive 13. May also be shown as 806f020d040dffff or 0x806f020d040dffff severity: warning alert category: warning serviceable: yes cim informa...

  • Page 543

    806f0223-2101ffff powering off system [computersystemelementname] initiated by [watchdogelementname]. Explanation: the ipmi watchdog timer has expired. The system was powered off. May also be shown as 806f02232101ffff or 0x806f02232101ffff severity: info alert category: system serviceable: no cim in...

  • Page 544

    806f0308-1881ffff [powersupplyelementname] has lost input. Explanation: meu power supple has lost. May also be shown as 806f03081881ffff or 0x806f03081881ffff severity: info alert category: system serviceable: no cim information: prefix: plat and id: 0100 snmp trap id: automatically notify support: ...

  • Page 545

    806f030c-08810002 scrub failure for [physicalmemoryelementname] on subsystem [memoryelementname]. Explanation: memory test failed in dimm 2 of mem card 1. May also be shown as 806f030c08810002 or 0x806f030c08810002 severity: error alert category: critical serviceable: no cim information: prefix: pla...

  • Page 546

    806f030c-08810004 scrub failure for [physicalmemoryelementname] on subsystem [memoryelementname]. Explanation: memory test failed in dimm 4 of mem card 1. May also be shown as 806f030c08810004 or 0x806f030c08810004 severity: error alert category: critical serviceable: no cim information: prefix: pla...

  • Page 547

    806f030c-08810006 scrub failure for [physicalmemoryelementname] on subsystem [memoryelementname]. Explanation: memory test failed in dimm 6 of mem card 1. May also be shown as 806f030c08810006 or 0x806f030c08810006 severity: error alert category: critical serviceable: no cim information: prefix: pla...

  • Page 548

    806f030c-08820001 scrub failure for [physicalmemoryelementname] on subsystem [memoryelementname]. Explanation: memory test failed in dimm 1 of mem card 2. May also be shown as 806f030c08820001 or 0x806f030c08820001 severity: error alert category: critical serviceable: no cim information: prefix: pla...

  • Page 549

    806f030c-08820003 scrub failure for [physicalmemoryelementname] on subsystem [memoryelementname]. Explanation: memory test failed in dimm 3 of mem card 2. May also be shown as 806f030c08820003 or 0x806f030c08820003 severity: error alert category: critical serviceable: no cim information: prefix: pla...

  • Page 550

    806f030c-08820005 scrub failure for [physicalmemoryelementname] on subsystem [memoryelementname]. Explanation: memory test failed in dimm 5 of mem card 2. May also be shown as 806f030c08820005 or 0x806f030c08820005 severity: error alert category: critical serviceable: no cim information: prefix: pla...

  • Page 551

    806f030c-08820007 scrub failure for [physicalmemoryelementname] on subsystem [memoryelementname]. Explanation: memory test failed in dimm 7 of mem card 2. May also be shown as 806f030c08820007 or 0x806f030c08820007 severity: error alert category: critical serviceable: no cim information: prefix: pla...

  • Page 552

    806f030c-08830001 scrub failure for [physicalmemoryelementname] on subsystem [memoryelementname]. Explanation: memory test failed in dimm 1 of mem card 3. May also be shown as 806f030c08830001 or 0x806f030c08830001 severity: error alert category: critical serviceable: no cim information: prefix: pla...

  • Page 553

    806f030c-08830003 scrub failure for [physicalmemoryelementname] on subsystem [memoryelementname]. Explanation: memory test failed in dimm 3 of mem card 3. May also be shown as 806f030c08830003 or 0x806f030c08830003 severity: error alert category: critical serviceable: no cim information: prefix: pla...

  • Page 554

    806f030c-08830005 scrub failure for [physicalmemoryelementname] on subsystem [memoryelementname]. Explanation: memory test failed in dimm 5 of mem card 3. May also be shown as 806f030c08830005 or 0x806f030c08830005 severity: error alert category: critical serviceable: no cim information: prefix: pla...

  • Page 555

    806f030c-08830007 scrub failure for [physicalmemoryelementname] on subsystem [memoryelementname]. Explanation: memory test failed in dimm 7 of mem card 3. May also be shown as 806f030c08830007 or 0x806f030c08830007 severity: error alert category: critical serviceable: no cim information: prefix: pla...

  • Page 556

    806f030c-08840001 scrub failure for [physicalmemoryelementname] on subsystem [memoryelementname]. Explanation: memory test failed in dimm 1 of mem card 4. May also be shown as 806f030c08840001 or 0x806f030c08840001 severity: error alert category: critical serviceable: no cim information: prefix: pla...

  • Page 557

    806f030c-08840003 scrub failure for [physicalmemoryelementname] on subsystem [memoryelementname]. Explanation: memory test failed in dimm 3 of mem card 4. May also be shown as 806f030c08840003 or 0x806f030c08840003 severity: error alert category: critical serviceable: no cim information: prefix: pla...

  • Page 558

    806f030c-08840005 scrub failure for [physicalmemoryelementname] on subsystem [memoryelementname]. Explanation: memory test failed in dimm 5 of mem card 4. May also be shown as 806f030c08840005 or 0x806f030c08840005 severity: error alert category: critical serviceable: no cim information: prefix: pla...

  • Page 559

    806f030c-08840007 scrub failure for [physicalmemoryelementname] on subsystem [memoryelementname]. Explanation: memory test failed in dimm 7 of mem card 4. May also be shown as 806f030c08840007 or 0x806f030c08840007 severity: error alert category: critical serviceable: no cim information: prefix: pla...

  • Page 560

    806f030c-08850001 scrub failure for [physicalmemoryelementname] on subsystem [memoryelementname]. Explanation: memory test failed in dimm 1 of mem card 5. May also be shown as 806f030c08850001 or 0x806f030c08850001 severity: error alert category: critical serviceable: no cim information: prefix: pla...

  • Page 561

    806f030c-08850003 scrub failure for [physicalmemoryelementname] on subsystem [memoryelementname]. Explanation: memory test failed in dimm 3 of mem card 5. May also be shown as 806f030c08850003 or 0x806f030c08850003 severity: error alert category: critical serviceable: no cim information: prefix: pla...

  • Page 562

    806f030c-08850005 scrub failure for [physicalmemoryelementname] on subsystem [memoryelementname]. Explanation: memory test failed in dimm 5 of mem card 5. May also be shown as 806f030c08850005 or 0x806f030c08850005 severity: error alert category: critical serviceable: no cim information: prefix: pla...

  • Page 563

    806f030c-08850007 scrub failure for [physicalmemoryelementname] on subsystem [memoryelementname]. Explanation: memory test failed in dimm 7 of mem card 5. May also be shown as 806f030c08850007 or 0x806f030c08850007 severity: error alert category: critical serviceable: no cim information: prefix: pla...

  • Page 564

    806f030c-08860001 scrub failure for [physicalmemoryelementname] on subsystem [memoryelementname]. Explanation: memory test failed in dimm 1 of mem card 6. May also be shown as 806f030c08860001 or 0x806f030c08860001 severity: error alert category: critical serviceable: no cim information: prefix: pla...

  • Page 565

    806f030c-08860003 scrub failure for [physicalmemoryelementname] on subsystem [memoryelementname]. Explanation: memory test failed in dimm 3 of mem card 6. May also be shown as 806f030c08860003 or 0x806f030c08860003 severity: error alert category: critical serviceable: no cim information: prefix: pla...

  • Page 566

    806f030c-08860005 scrub failure for [physicalmemoryelementname] on subsystem [memoryelementname]. Explanation: memory test failed in dimm 5 of mem card 6. May also be shown as 806f030c08860005 or 0x806f030c08860005 severity: error alert category: critical serviceable: no cim information: prefix: pla...

  • Page 567

    806f030c-08860007 scrub failure for [physicalmemoryelementname] on subsystem [memoryelementname]. Explanation: memory test failed in dimm 7 of mem card 6. May also be shown as 806f030c08860007 or 0x806f030c08860007 severity: error alert category: critical serviceable: no cim information: prefix: pla...

  • Page 568

    806f030c-08870001 scrub failure for [physicalmemoryelementname] on subsystem [memoryelementname]. Explanation: memory test failed in dimm 1 of mem card 7. May also be shown as 806f030c08870001 or 0x806f030c08870001 severity: error alert category: critical serviceable: no cim information: prefix: pla...

  • Page 569

    806f030c-08870003 scrub failure for [physicalmemoryelementname] on subsystem [memoryelementname]. Explanation: memory test failed in dimm 3 of mem card 7. May also be shown as 806f030c08870003 or 0x806f030c08870003 severity: error alert category: critical serviceable: no cim information: prefix: pla...

  • Page 570

    806f030c-08870005 scrub failure for [physicalmemoryelementname] on subsystem [memoryelementname]. Explanation: memory test failed in dimm 5 of mem card 7. May also be shown as 806f030c08870005 or 0x806f030c08870005 severity: error alert category: critical serviceable: no cim information: prefix: pla...

  • Page 571

    806f030c-08870007 scrub failure for [physicalmemoryelementname] on subsystem [memoryelementname]. Explanation: memory test failed in dimm 7 of mem card 7. May also be shown as 806f030c08870007 or 0x806f030c08870007 severity: error alert category: critical serviceable: no cim information: prefix: pla...

  • Page 572

    806f030c-08880001 scrub failure for [physicalmemoryelementname] on subsystem [memoryelementname]. Explanation: memory test failed in dimm 1 of mem card 8. May also be shown as 806f030c08880001 or 0x806f030c08880001 severity: error alert category: critical serviceable: no cim information: prefix: pla...

  • Page 573

    806f030c-08880003 scrub failure for [physicalmemoryelementname] on subsystem [memoryelementname]. Explanation: memory test failed in dimm 3 of mem card 8. May also be shown as 806f030c08880003 or 0x806f030c08880003 severity: error alert category: critical serviceable: no cim information: prefix: pla...

  • Page 574

    806f030c-08880005 scrub failure for [physicalmemoryelementname] on subsystem [memoryelementname]. Explanation: memory test failed in dimm 5 of mem card 8. May also be shown as 806f030c08880005 or 0x806f030c08880005 severity: error alert category: critical serviceable: no cim information: prefix: pla...

  • Page 575

    806f030c-08880007 scrub failure for [physicalmemoryelementname] on subsystem [memoryelementname]. Explanation: memory test failed in dimm 7 of mem card 8. May also be shown as 806f030c08880007 or 0x806f030c08880007 severity: error alert category: critical serviceable: no cim information: prefix: pla...

  • Page 576

    806f030c-088810008 scrub failure for [physicalmemoryelementname] on subsystem [memoryelementname]. Explanation: memory test failed in dimm 8 of mem card 1. May also be shown as 806f030c088810008 or 0x806f030c088810008 severity: error alert category: critical serviceable: no cim information: prefix: ...

  • Page 577

    806f030c-18810002 scrub failure for [physicalmemoryelementname] on subsystem [memoryelementname]. Explanation: memory test failed in dimm 2 of memory expansion module(meu). May also be shown as 806f030c18810002 or 0x806f030c18810002 severity: error alert category: critical serviceable: no cim inform...

  • Page 578

    806f030c-18810004 scrub failure for [physicalmemoryelementname] on subsystem [memoryelementname]. Explanation: memory test failed in dimm 4 of memory expansion module(meu). May also be shown as 806f030c18810004 or 0x806f030c18810004 severity: error alert category: critical serviceable: no cim inform...

  • Page 579

    806f030c-18810006 scrub failure for [physicalmemoryelementname] on subsystem [memoryelementname]. Explanation: memory test failed in dimm 6 of memory expansion module(meu). May also be shown as 806f030c18810006 or 0x806f030c18810006 severity: error alert category: critical serviceable: no cim inform...

  • Page 580

    806f030c-18810008 scrub failure for [physicalmemoryelementname] on subsystem [memoryelementname]. Explanation: memory test failed in dimm 8 of memory expansion module(meu). May also be shown as 806f030c18810008 or 0x806f030c18810008 severity: error alert category: critical serviceable: no cim inform...

  • Page 581

    806f030c-1881000a scrub failure for [physicalmemoryelementname] on subsystem [memoryelementname]. Explanation: memory test failed in dimm 10 of memory expansion module(meu). May also be shown as 806f030c1881000a or 0x806f030c1881000a severity: error alert category: critical serviceable: no cim infor...

  • Page 582

    806f030c-1881000c scrub failure for [physicalmemoryelementname] on subsystem [memoryelementname]. Explanation: memory test failed in dimm 12 of memory expansion module(meu). May also be shown as 806f030c1881000c or 0x806f030c1881000c severity: error alert category: critical serviceable: no cim infor...

  • Page 583

    806f030c-1881000e scrub failure for [physicalmemoryelementname] on subsystem [memoryelementname]. Explanation: memory test failed in dimm 14 of memory expansion module(meu). May also be shown as 806f030c1881000e or 0x806f030c1881000e severity: error alert category: critical serviceable: no cim infor...

  • Page 584

    806f030c-18810010 scrub failure for [physicalmemoryelementname] on subsystem [memoryelementname]. Explanation: memory test failed in dimm 16 of memory expansion module(meu). May also be shown as 806f030c18810010 or 0x806f030c18810010 severity: error alert category: critical serviceable: no cim infor...

  • Page 585

    806f030c-18810012 scrub failure for [physicalmemoryelementname] on subsystem [memoryelementname]. Explanation: memory test failed in dimm 18 of memory expansion module(meu). May also be shown as 806f030c18810012 or 0x806f030c18810012 severity: error alert category: critical serviceable: no cim infor...

  • Page 586

    806f030c-18810014 scrub failure for [physicalmemoryelementname] on subsystem [memoryelementname]. Explanation: memory test failed in dimm 20 of memory expansion module(meu). May also be shown as 806f030c18810014 or 0x806f030c18810014 severity: error alert category: critical serviceable: no cim infor...

  • Page 587

    806f030c-18810016 scrub failure for [physicalmemoryelementname] on subsystem [memoryelementname]. Explanation: memory test failed in dimm 22 of memory expansion module(meu). May also be shown as 806f030c18810016 or 0x806f030c18810016 severity: error alert category: critical serviceable: no cim infor...

  • Page 588

    806f030c-18810018 scrub failure for [physicalmemoryelementname] on subsystem [memoryelementname]. Explanation: memory test failed in dimm 24 of memory expansion module(meu). May also be shown as 806f030c18810018 or 0x806f030c18810018 severity: error alert category: critical serviceable: no cim infor...

  • Page 589

    806f030c-1881001a scrub failure for [physicalmemoryelementname] on subsystem [memoryelementname]. Explanation: memory test failed in dimm 26 of memory expansion module(meu). May also be shown as 806f030c1881001a or 0x806f030c1881001a severity: error alert category: critical serviceable: no cim infor...

  • Page 590

    806f030c-1881001c scrub failure for [physicalmemoryelementname] on subsystem [memoryelementname]. Explanation: memory test failed in dimm 28 of memory expansion module(meu). May also be shown as 806f030c1881001c or 0x806f030c1881001c severity: error alert category: critical serviceable: no cim infor...

  • Page 591

    806f030c-1881001e scrub failure for [physicalmemoryelementname] on subsystem [memoryelementname]. Explanation: memory test failed in dimm 30 of memory expansion module(meu). May also be shown as 806f030c1881001e or 0x806f030c1881001e severity: error alert category: critical serviceable: no cim infor...

  • Page 592

    806f030c-18810020 scrub failure for [physicalmemoryelementname] on subsystem [memoryelementname]. Explanation: memory test failed in dimm 32 of memory expansion module(meu). May also be shown as 806f030c18810020 or 0x806f030c18810020 severity: error alert category: critical serviceable: no cim infor...

  • Page 593

    806f0313-1701ffff a software nmi has occurred on system [computersystemelementname]. Explanation: a software nmi has occurred. Your system may have been rebooted, depending on the configuration setting. May also be shown as 806f03131701ffff or 0x806f03131701ffff severity: error alert category: criti...

  • Page 594

    806f0409-1381ffff [powersupplyelementname] has lost power. Explanation: imm detected that a power unit had lost power may also be shown as 806f04091381ffff or 0x806f04091381ffff severity: info alert category: system serviceable: no cim information: prefix: plat and id: 0112 snmp trap id: automatical...

  • Page 595

    806f040c-08810003 [physicalmemoryelementname] disabled on subsystem [memoryelementname]. Explanation: dimm 3 in mem card 1 has been disabled. May also be shown as 806f040c08810003 or 0x806f040c08810003 severity: info alert category: system serviceable: no cim information: prefix: plat and id: 0131 s...

  • Page 596

    806f040c-08810005 [physicalmemoryelementname] disabled on subsystem [memoryelementname]. Explanation: dimm 5 in mem card 1 has been disabled. May also be shown as 806f040c08810005 or 0x806f040c08810005 severity: info alert category: system serviceable: no cim information: prefix: plat and id: 0131 s...

  • Page 597

    806f040c-08810007 [physicalmemoryelementname] disabled on subsystem [memoryelementname]. Explanation: dimm 7 in mem card 1 has been disabled. May also be shown as 806f040c08810007 or 0x806f040c08810007 severity: info alert category: system serviceable: no cim information: prefix: plat and id: 0131 s...

  • Page 598

    806f040c-08820001 [physicalmemoryelementname] disabled on subsystem [memoryelementname]. Explanation: dimm 1 in mem card 2 has been disabled. May also be shown as 806f040c08820001 or 0x806f040c08820001 severity: info alert category: system serviceable: no cim information: prefix: plat and id: 0131 s...

  • Page 599

    806f040c-08820003 [physicalmemoryelementname] disabled on subsystem [memoryelementname]. Explanation: dimm 3 in mem card 2 has been disabled. May also be shown as 806f040c08820003 or 0x806f040c08820003 severity: info alert category: system serviceable: no cim information: prefix: plat and id: 0131 s...

  • Page 600

    806f040c-08820005 [physicalmemoryelementname] disabled on subsystem [memoryelementname]. Explanation: dimm 5 in mem card 2 has been disabled. May also be shown as 806f040c08820005 or 0x806f040c08820005 severity: info alert category: system serviceable: no cim information: prefix: plat and id: 0131 s...

  • Page 601

    806f040c-08820007 [physicalmemoryelementname] disabled on subsystem [memoryelementname]. Explanation: dimm 7 in mem card 2 has been disabled. May also be shown as 806f040c08820007 or 0x806f040c08820007 severity: info alert category: system serviceable: no cim information: prefix: plat and id: 0131 s...

  • Page 602

    806f040c-08830001 [physicalmemoryelementname] disabled on subsystem [memoryelementname]. Explanation: dimm 1 in mem card 3 has been disabled. May also be shown as 806f040c08830001 or 0x806f040c08830001 severity: info alert category: system serviceable: no cim information: prefix: plat and id: 0131 s...

  • Page 603

    806f040c-08830003 [physicalmemoryelementname] disabled on subsystem [memoryelementname]. Explanation: dimm 3 in mem card 3 has been disabled. May also be shown as 806f040c08830003 or 0x806f040c08830003 severity: info alert category: system serviceable: no cim information: prefix: plat and id: 0131 s...

  • Page 604

    806f040c-08830005 [physicalmemoryelementname] disabled on subsystem [memoryelementname]. Explanation: dimm 5 in mem card 3 has been disabled. May also be shown as 806f040c08830005 or 0x806f040c08830005 severity: info alert category: system serviceable: no cim information: prefix: plat and id: 0131 s...

  • Page 605

    806f040c-08830007 [physicalmemoryelementname] disabled on subsystem [memoryelementname]. Explanation: dimm 7 in mem card 3 has been disabled. May also be shown as 806f040c08830007 or 0x806f040c08830007 severity: info alert category: system serviceable: no cim information: prefix: plat and id: 0131 s...

  • Page 606

    806f040c-08840001 [physicalmemoryelementname] disabled on subsystem [memoryelementname]. Explanation: dimm 1 in mem card 4 has been disabled. May also be shown as 806f040c08840001 or 0x806f040c08840001 severity: info alert category: system serviceable: no cim information: prefix: plat and id: 0131 s...

  • Page 607

    806f040c-08840003 [physicalmemoryelementname] disabled on subsystem [memoryelementname]. Explanation: dimm 3 in mem card 4 has been disabled. May also be shown as 806f040c08840003 or 0x806f040c08840003 severity: info alert category: system serviceable: no cim information: prefix: plat and id: 0131 s...

  • Page 608

    806f040c-08840005 [physicalmemoryelementname] disabled on subsystem [memoryelementname]. Explanation: dimm 5 in mem card 4 has been disabled. May also be shown as 806f040c08840005 or 0x806f040c08840005 severity: info alert category: system serviceable: no cim information: prefix: plat and id: 0131 s...

  • Page 609

    806f040c-08840007 [physicalmemoryelementname] disabled on subsystem [memoryelementname]. Explanation: dimm 7 in mem card 4 has been disabled. May also be shown as 806f040c08840007 or 0x806f040c08840007 severity: info alert category: system serviceable: no cim information: prefix: plat and id: 0131 s...

  • Page 610

    806f040c-08850001 [physicalmemoryelementname] disabled on subsystem [memoryelementname]. Explanation: dimm 1 in mem card 5 has been disabled. May also be shown as 806f040c08850001 or 0x806f040c08850001 severity: info alert category: system serviceable: no cim information: prefix: plat and id: 0131 s...

  • Page 611

    806f040c-08850003 [physicalmemoryelementname] disabled on subsystem [memoryelementname]. Explanation: dimm 3 in mem card 5 has been disabled. May also be shown as 806f040c08850003 or 0x806f040c08850003 severity: info alert category: system serviceable: no cim information: prefix: plat and id: 0131 s...

  • Page 612

    806f040c-08850005 [physicalmemoryelementname] disabled on subsystem [memoryelementname]. Explanation: dimm 5 in mem card 5 has been disabled. May also be shown as 806f040c08850005 or 0x806f040c08850005 severity: info alert category: system serviceable: no cim information: prefix: plat and id: 0131 s...

  • Page 613

    806f040c-08850007 [physicalmemoryelementname] disabled on subsystem [memoryelementname]. Explanation: dimm 7 in mem card 5 has been disabled. May also be shown as 806f040c08850007 or 0x806f040c08850007 severity: info alert category: system serviceable: no cim information: prefix: plat and id: 0131 s...

  • Page 614

    806f040c-08860001 [physicalmemoryelementname] disabled on subsystem [memoryelementname]. Explanation: dimm 1 in mem card 6 has been disabled. May also be shown as 806f040c08860001 or 0x806f040c08860001 severity: info alert category: system serviceable: no cim information: prefix: plat and id: 0131 s...

  • Page 615

    806f040c-08860003 [physicalmemoryelementname] disabled on subsystem [memoryelementname]. Explanation: dimm 3 in mem card 6 has been disabled. May also be shown as 806f040c08860003 or 0x806f040c08860003 severity: info alert category: system serviceable: no cim information: prefix: plat and id: 0131 s...

  • Page 616

    806f040c-08860005 [physicalmemoryelementname] disabled on subsystem [memoryelementname]. Explanation: dimm 5 in mem card 6 has been disabled. May also be shown as 806f040c08860005 or 0x806f040c08860005 severity: info alert category: system serviceable: no cim information: prefix: plat and id: 0131 s...

  • Page 617

    806f040c-08860007 [physicalmemoryelementname] disabled on subsystem [memoryelementname]. Explanation: dimm 7 in mem card 6 has been disabled. May also be shown as 806f040c08860007 or 0x806f040c08860007 severity: info alert category: system serviceable: no cim information: prefix: plat and id: 0131 s...

  • Page 618

    806f040c-08870001 [physicalmemoryelementname] disabled on subsystem [memoryelementname]. Explanation: dimm 1 in mem card 7 has been disabled. May also be shown as 806f040c08870001 or 0x806f040c08870001 severity: info alert category: system serviceable: no cim information: prefix: plat and id: 0131 s...

  • Page 619

    806f040c-08870003 [physicalmemoryelementname] disabled on subsystem [memoryelementname]. Explanation: dimm 3 in mem card 7 has been disabled. May also be shown as 806f040c08870003 or 0x806f040c08870003 severity: info alert category: system serviceable: no cim information: prefix: plat and id: 0131 s...

  • Page 620

    806f040c-08870005 [physicalmemoryelementname] disabled on subsystem [memoryelementname]. Explanation: dimm 5 in mem card 7 has been disabled. May also be shown as 806f040c08870005 or 0x806f040c08870005 severity: info alert category: system serviceable: no cim information: prefix: plat and id: 0131 s...

  • Page 621

    806f040c-08870007 [physicalmemoryelementname] disabled on subsystem [memoryelementname]. Explanation: dimm 7 in mem card 7 has been disabled. May also be shown as 806f040c08870007 or 0x806f040c08870007 severity: info alert category: system serviceable: no cim information: prefix: plat and id: 0131 s...

  • Page 622

    806f040c-08880001 [physicalmemoryelementname] disabled on subsystem [memoryelementname]. Explanation: dimm 1 in mem card 8 has been disabled. May also be shown as 806f040c08880001 or 0x806f040c08880001 severity: info alert category: system serviceable: no cim information: prefix: plat and id: 0131 s...

  • Page 623

    806f040c-08880003 [physicalmemoryelementname] disabled on subsystem [memoryelementname]. Explanation: dimm 3 in mem card 8 has been disabled. May also be shown as 806f040c08880003 or 0x806f040c08880003 severity: info alert category: system serviceable: no cim information: prefix: plat and id: 0131 s...

  • Page 624

    806f040c-08880005 [physicalmemoryelementname] disabled on subsystem [memoryelementname]. Explanation: dimm 5 in mem card 8 has been disabled. May also be shown as 806f040c08880005 or 0x806f040c08880005 severity: info alert category: system serviceable: no cim information: prefix: plat and id: 0131 s...

  • Page 625

    806f040c-08880007 [physicalmemoryelementname] disabled on subsystem [memoryelementname]. Explanation: dimm 7 in mem card 8 has been disabled. May also be shown as 806f040c08880007 or 0x806f040c08880007 severity: info alert category: system serviceable: no cim information: prefix: plat and id: 0131 s...

  • Page 626

    806f040c-18810001 [physicalmemoryelementname] disabled on subsystem [memoryelementname]. Explanation: dimm 1 in memory expansion module(meu) has been disabled. May also be shown as 806f040c18810001 or 0x806f040c18810001 severity: info alert category: system serviceable: no cim information: prefix: p...

  • Page 627

    806f040c-18810003 [physicalmemoryelementname] disabled on subsystem [memoryelementname]. Explanation: dimm 3 in memory expansion module(meu) has been disabled. May also be shown as 806f040c18810003 or 0x806f040c18810003 severity: info alert category: system serviceable: no cim information: prefix: p...

  • Page 628

    806f040c-18810005 [physicalmemoryelementname] disabled on subsystem [memoryelementname]. Explanation: dimm 5 in memory expansion module(meu) has been disabled. May also be shown as 806f040c18810005 or 0x806f040c18810005 severity: info alert category: system serviceable: no cim information: prefix: p...

  • Page 629

    806f040c-18810007 [physicalmemoryelementname] disabled on subsystem [memoryelementname]. Explanation: dimm 7 in memory expansion module(meu) has been disabled. May also be shown as 806f040c18810007 or 0x806f040c18810007 severity: info alert category: system serviceable: no cim information: prefix: p...

  • Page 630

    806f040c-18810009 [physicalmemoryelementname] disabled on subsystem [memoryelementname]. Explanation: dimm 9 in memory expansion module(meu) has been disabled. May also be shown as 806f040c18810009 or 0x806f040c18810009 severity: info alert category: system serviceable: no cim information: prefix: p...

  • Page 631

    806f040c-1881000b [physicalmemoryelementname] disabled on subsystem [memoryelementname]. Explanation: dimm 11 in memory expansion module(meu) has been disabled. May also be shown as 806f040c1881000b or 0x806f040c1881000b severity: info alert category: system serviceable: no cim information: prefix: ...

  • Page 632

    806f040c-1881000d [physicalmemoryelementname] disabled on subsystem [memoryelementname]. Explanation: dimm 13 in memory expansion module(meu) has been disabled. May also be shown as 806f040c1881000d or 0x806f040c1881000d severity: info alert category: system serviceable: no cim information: prefix: ...

  • Page 633

    806f040c-1881000f [physicalmemoryelementname] disabled on subsystem [memoryelementname]. Explanation: dimm 15 in memory expansion module(meu) has been disabled. May also be shown as 806f040c1881000f or 0x806f040c1881000f severity: info alert category: system serviceable: no cim information: prefix: ...

  • Page 634

    806f040c-18810011 [physicalmemoryelementname] disabled on subsystem [memoryelementname]. Explanation: dimm 17 in memory expansion module(meu) has been disabled. May also be shown as 806f040c18810011 or 0x806f040c18810011 severity: info alert category: system serviceable: no cim information: prefix: ...

  • Page 635

    806f040c-18810013 [physicalmemoryelementname] disabled on subsystem [memoryelementname]. Explanation: dimm 19 in memory expansion module(meu) has been disabled. May also be shown as 806f040c18810013 or 0x806f040c18810013 severity: info alert category: system serviceable: no cim information: prefix: ...

  • Page 636

    806f040c-18810015 [physicalmemoryelementname] disabled on subsystem [memoryelementname]. Explanation: dimm 21 in memory expansion module(meu) has been disabled. May also be shown as 806f040c18810015 or 0x806f040c18810015 severity: info alert category: system serviceable: no cim information: prefix: ...

  • Page 637

    806f040c-18810017 [physicalmemoryelementname] disabled on subsystem [memoryelementname]. Explanation: dimm 23 in memory expansion module(meu) has been disabled. May also be shown as 806f040c18810017 or 0x806f040c18810017 severity: info alert category: system serviceable: no cim information: prefix: ...

  • Page 638

    806f040c-18810019 [physicalmemoryelementname] disabled on subsystem [memoryelementname]. Explanation: dimm 25 in memory expansion module(meu) has been disabled. May also be shown as 806f040c18810019 or 0x806f040c18810019 severity: info alert category: system serviceable: no cim information: prefix: ...

  • Page 639

    806f040c-1881001b [physicalmemoryelementname] disabled on subsystem [memoryelementname]. Explanation: dimm 27 in memory expansion module(meu) has been disabled. May also be shown as 806f040c1881001b or 0x806f040c1881001b severity: info alert category: system serviceable: no cim information: prefix: ...

  • Page 640

    806f040c-1881001d [physicalmemoryelementname] disabled on subsystem [memoryelementname]. Explanation: dimm 29 in memory expansion module(meu) has been disabled. May also be shown as 806f040c1881001d or 0x806f040c1881001d severity: info alert category: system serviceable: no cim information: prefix: ...

  • Page 641

    806f040c-1881001f [physicalmemoryelementname] disabled on subsystem [memoryelementname]. Explanation: dimm 31 in memory expansion module(meu) has been disabled. May also be shown as 806f040c1881001f or 0x806f040c1881001f severity: info alert category: system serviceable: no cim information: prefix: ...

  • Page 642

    806f040c-2581ffff [physicalmemoryelementname] disabled on subsystem [memoryelementname]. Explanation: imm has detected that memory has been disabled. May also be shown as 806f040c2581ffff or 0x806f040c2581ffff severity: info alert category: system serviceable: no cim information: prefix: plat and id...

  • Page 643

    806f0507-0303ffff [processorelementname] has a configuration mismatch. Explanation: imm has detected a processor configuration mismatch on cpu 3. May also be shown as 806f05070303ffff or 0x806f05070303ffff severity: error alert category: critical serviceable: yes cim information: prefix: plat and id...

  • Page 644

    806f050c-08810001 memory logging limit reached for [physicalmemoryelementname] on subsystem [memoryelementname]. Explanation: dimm 1 of mem card 1 memory logging limit has been reached. May also be shown as 806f050c08810001 or 0x806f050c08810001 severity: warning alert category: warning serviceable:...

  • Page 645

    806f050c-08810003 memory logging limit reached for [physicalmemoryelementname] on subsystem [memoryelementname]. Explanation: dimm 3 of mem card 1 memory logging limit has been reached. May also be shown as 806f050c08810003 or 0x806f050c08810003 severity: warning alert category: warning serviceable:...

  • Page 646

    806f050c-08810005 memory logging limit reached for [physicalmemoryelementname] on subsystem [memoryelementname]. Explanation: dimm 5 of mem card 1 memory logging limit has been reached. May also be shown as 806f050c08810005 or 0x806f050c08810005 severity: warning alert category: warning serviceable:...

  • Page 647

    806f050c-08810007 memory logging limit reached for [physicalmemoryelementname] on subsystem [memoryelementname]. Explanation: dimm 7 of mem card 1 memory logging limit has been reached. May also be shown as 806f050c08810007 or 0x806f050c08810007 severity: warning alert category: warning serviceable:...

  • Page 648

    806f050c-08820001 memory logging limit reached for [physicalmemoryelementname] on subsystem [memoryelementname]. Explanation: dimm 1 of mem card 2 memory logging limit has been reached. May also be shown as 806f050c08820001 or 0x806f050c08820001 severity: warning alert category: warning serviceable:...

  • Page 649

    806f050c-08820003 memory logging limit reached for [physicalmemoryelementname] on subsystem [memoryelementname]. Explanation: dimm 3 of mem card 2 memory logging limit has been reached. May also be shown as 806f050c08820003 or 0x806f050c08820003 severity: warning alert category: warning serviceable:...

  • Page 650

    806f050c-08820005 memory logging limit reached for [physicalmemoryelementname] on subsystem [memoryelementname]. Explanation: dimm 5 of mem card 2 memory logging limit has been reached. May also be shown as 806f050c08820005 or 0x806f050c08820005 severity: warning alert category: warning serviceable:...

  • Page 651

    806f050c-08820007 memory logging limit reached for [physicalmemoryelementname] on subsystem [memoryelementname]. Explanation: dimm 7 of mem card 2 memory logging limit has been reached. May also be shown as 806f050c08820007 or 0x806f050c08820007 severity: warning alert category: warning serviceable:...

  • Page 652

    806f050c-08830001 memory logging limit reached for [physicalmemoryelementname] on subsystem [memoryelementname]. Explanation: dimm 1 of mem card 3 memory logging limit has been reached. May also be shown as 806f050c08830001 or 0x806f050c08830001 severity: warning alert category: warning serviceable:...

  • Page 653

    806f050c-08830003 memory logging limit reached for [physicalmemoryelementname] on subsystem [memoryelementname]. Explanation: dimm 3 of mem card 3 memory logging limit has been reached. May also be shown as 806f050c08830003 or 0x806f050c08830003 severity: warning alert category: warning serviceable:...

  • Page 654

    806f050c-08830005 memory logging limit reached for [physicalmemoryelementname] on subsystem [memoryelementname]. Explanation: dimm 5 of mem card 3 memory logging limit has been reached. May also be shown as 806f050c08830005 or 0x806f050c08830005 severity: warning alert category: warning serviceable:...

  • Page 655

    806f050c-08830007 memory logging limit reached for [physicalmemoryelementname] on subsystem [memoryelementname]. Explanation: dimm 7 of mem card 3 memory logging limit has been reached. May also be shown as 806f050c08830007 or 0x806f050c08830007 severity: warning alert category: warning serviceable:...

  • Page 656

    806f050c-08840001 memory logging limit reached for [physicalmemoryelementname] on subsystem [memoryelementname]. Explanation: dimm 1 of mem card 4 memory logging limit has been reached. May also be shown as 806f050c08840001 or 0x806f050c08840001 severity: warning alert category: warning serviceable:...

  • Page 657

    806f050c-08840003 memory logging limit reached for [physicalmemoryelementname] on subsystem [memoryelementname]. Explanation: dimm 3 of mem card 4 memory logging limit has been reached. May also be shown as 806f050c08840003 or 0x806f050c08840003 severity: warning alert category: warning serviceable:...

  • Page 658

    806f050c-08840005 memory logging limit reached for [physicalmemoryelementname] on subsystem [memoryelementname]. Explanation: dimm 5 of mem card 4 memory logging limit has been reached. May also be shown as 806f050c08840005 or 0x806f050c08840005 severity: warning alert category: warning serviceable:...

  • Page 659

    806f050c-08840007 memory logging limit reached for [physicalmemoryelementname] on subsystem [memoryelementname]. Explanation: dimm 7 of mem card 4 memory logging limit has been reached. May also be shown as 806f050c08840007 or 0x806f050c08840007 severity: warning alert category: warning serviceable:...

  • Page 660

    806f050c-08850001 memory logging limit reached for [physicalmemoryelementname] on subsystem [memoryelementname]. Explanation: dimm 1 of mem card 5 memory logging limit has been reached. May also be shown as 806f050c08850001 or 0x806f050c08850001 severity: warning alert category: warning serviceable:...

  • Page 661

    806f050c-08850003 memory logging limit reached for [physicalmemoryelementname] on subsystem [memoryelementname]. Explanation: dimm 3 of mem card 5 memory logging limit has been reached. May also be shown as 806f050c08850003 or 0x806f050c08850003 severity: warning alert category: warning serviceable:...

  • Page 662

    806f050c-08850005 memory logging limit reached for [physicalmemoryelementname] on subsystem [memoryelementname]. Explanation: dimm 5 of mem card 5 memory logging limit has been reached. May also be shown as 806f050c08850005 or 0x806f050c08850005 severity: warning alert category: warning serviceable:...

  • Page 663

    806f050c-08850007 memory logging limit reached for [physicalmemoryelementname] on subsystem [memoryelementname]. Explanation: dimm 7 of mem card 5 memory logging limit has been reached. May also be shown as 806f050c08850007 or 0x806f050c08850007 severity: warning alert category: warning serviceable:...

  • Page 664

    806f050c-08860001 memory logging limit reached for [physicalmemoryelementname] on subsystem [memoryelementname]. Explanation: dimm 1 of mem card 6 memory logging limit has been reached. May also be shown as 806f050c08860001 or 0x806f050c08860001 severity: warning alert category: warning serviceable:...

  • Page 665

    806f050c-08860003 memory logging limit reached for [physicalmemoryelementname] on subsystem [memoryelementname]. Explanation: dimm 3 of mem card 6 memory logging limit has been reached. May also be shown as 806f050c08860003 or 0x806f050c08860003 severity: warning alert category: warning serviceable:...

  • Page 666

    806f050c-08860005 memory logging limit reached for [physicalmemoryelementname] on subsystem [memoryelementname]. Explanation: dimm 5 of mem card 6 memory logging limit has been reached. May also be shown as 806f050c08860005 or 0x806f050c08860005 severity: warning alert category: warning serviceable:...

  • Page 667

    806f050c-08860007 memory logging limit reached for [physicalmemoryelementname] on subsystem [memoryelementname]. Explanation: dimm 7 of mem card 6 memory logging limit has been reached. May also be shown as 806f050c08860007 or 0x806f050c08860007 severity: warning alert category: warning serviceable:...

  • Page 668

    806f050c-08870001 memory logging limit reached for [physicalmemoryelementname] on subsystem [memoryelementname]. Explanation: dimm 1 of mem card 7 memory logging limit has been reached. May also be shown as 806f050c08870001 or 0x806f050c08870001 severity: warning alert category: warning serviceable:...

  • Page 669

    806f050c-08870003 memory logging limit reached for [physicalmemoryelementname] on subsystem [memoryelementname]. Explanation: dimm 3 of mem card 7 memory logging limit has been reached. May also be shown as 806f050c08870003 or 0x806f050c08870003 severity: warning alert category: warning serviceable:...

  • Page 670

    806f050c-08870005 memory logging limit reached for [physicalmemoryelementname] on subsystem [memoryelementname]. Explanation: dimm 5 of mem card 7 memory logging limit has been reached. May also be shown as 806f050c08870005 or 0x806f050c08870005 severity: warning alert category: warning serviceable:...

  • Page 671

    806f050c-08870007 memory logging limit reached for [physicalmemoryelementname] on subsystem [memoryelementname]. Explanation: dimm 7 of mem card 7 memory logging limit has been reached. May also be shown as 806f050c08870007 or 0x806f050c08870007 severity: warning alert category: warning serviceable:...

  • Page 672

    806f050c-08880001 memory logging limit reached for [physicalmemoryelementname] on subsystem [memoryelementname]. Explanation: dimm 1 of mem card 8 memory logging limit has been reached. May also be shown as 806f050c08880001 or 0x806f050c08880001 severity: warning alert category: warning serviceable:...

  • Page 673

    806f050c-08880003 memory logging limit reached for [physicalmemoryelementname] on subsystem [memoryelementname]. Explanation: dimm 3 of mem card 8 memory logging limit has been reached. May also be shown as 806f050c08880003 or 0x806f050c08880003 severity: warning alert category: warning serviceable:...

  • Page 674

    806f050c-08880005 memory logging limit reached for [physicalmemoryelementname] on subsystem [memoryelementname]. Explanation: dimm 5 of mem card 8 memory logging limit has been reached. May also be shown as 806f050c08880005 or 0x806f050c08880005 severity: warning alert category: warning serviceable:...

  • Page 675

    806f050c-08880007 memory logging limit reached for [physicalmemoryelementname] on subsystem [memoryelementname]. Explanation: dimm 7 of mem card 8 memory logging limit has been reached. May also be shown as 806f050c08880007 or 0x806f050c08880007 severity: warning alert category: warning serviceable:...

  • Page 676

    806f050c-18810001 memory logging limit reached for [physicalmemoryelementname] on subsystem [memoryelementname]. Explanation: dimm 1 of meu memory logging limit has been reached. May also be shown as 806f050c18810001 or 0x806f050c18810001 severity: warning alert category: warning serviceable: no cim...

  • Page 677

    806f050c-18810003 memory logging limit reached for [physicalmemoryelementname] on subsystem [memoryelementname]. Explanation: dimm 3 of meu memory logging limit has been reached. May also be shown as 806f050c18810003 or 0x806f050c18810003 severity: warning alert category: warning serviceable: no cim...

  • Page 678

    806f050c-18810005 memory logging limit reached for [physicalmemoryelementname] on subsystem [memoryelementname]. Explanation: dimm 5 of meu memory logging limit has been reached. May also be shown as 806f050c18810005 or 0x806f050c18810005 severity: warning alert category: warning serviceable: no cim...

  • Page 679

    806f050c-18810007 memory logging limit reached for [physicalmemoryelementname] on subsystem [memoryelementname]. Explanation: dimm 7 of meu memory logging limit has been reached. May also be shown as 806f050c18810007 or 0x806f050c18810007 severity: warning alert category: warning serviceable: no cim...

  • Page 680

    806f050c-18810009 memory logging limit reached for [physicalmemoryelementname] on subsystem [memoryelementname]. Explanation: dimm 9 of meu memory logging limit has been reached. May also be shown as 806f050c18810009 or 0x806f050c18810009 severity: warning alert category: warning serviceable: no cim...

  • Page 681

    806f050c-1881000b memory logging limit reached for [physicalmemoryelementname] on subsystem [memoryelementname]. Explanation: dimm 11 of meu memory logging limit has been reached. May also be shown as 806f050c1881000b or 0x806f050c1881000b severity: warning alert category: warning serviceable: no ci...

  • Page 682

    806f050c-1881000d memory logging limit reached for [physicalmemoryelementname] on subsystem [memoryelementname]. Explanation: dimm 13 of meu memory logging limit has been reached. May also be shown as 806f050c1881000d or 0x806f050c1881000d severity: warning alert category: warning serviceable: no ci...

  • Page 683

    806f050c-1881000f memory logging limit reached for [physicalmemoryelementname] on subsystem [memoryelementname]. Explanation: dimm 15 of meu memory logging limit has been reached. May also be shown as 806f050c1881000f or 0x806f050c1881000f severity: warning alert category: warning serviceable: no ci...

  • Page 684

    806f050c-18810011 memory logging limit reached for [physicalmemoryelementname] on subsystem [memoryelementname]. Explanation: dimm 17 of meu memory logging limit has been reached. May also be shown as 806f050c18810011 or 0x806f050c18810011 severity: warning alert category: warning serviceable: no ci...

  • Page 685

    806f050c-18810013 memory logging limit reached for [physicalmemoryelementname] on subsystem [memoryelementname]. Explanation: dimm 19 of meu memory logging limit has been reached. May also be shown as 806f050c18810013 or 0x806f050c18810013 severity: warning alert category: warning serviceable: no ci...

  • Page 686

    806f050c-18810015 memory logging limit reached for [physicalmemoryelementname] on subsystem [memoryelementname]. Explanation: dimm 21 of meu memory logging limit has been reached. May also be shown as 806f050c18810015 or 0x806f050c18810015 severity: warning alert category: warning serviceable: no ci...

  • Page 687

    806f050c-18810017 memory logging limit reached for [physicalmemoryelementname] on subsystem [memoryelementname]. Explanation: dimm 23 of meu memory logging limit has been reached. May also be shown as 806f050c18810017 or 0x806f050c18810017 severity: warning alert category: warning serviceable: no ci...

  • Page 688

    806f050c-18810019 memory logging limit reached for [physicalmemoryelementname] on subsystem [memoryelementname]. Explanation: dimm 25 of meu memory logging limit has been reached. May also be shown as 806f050c18810019 or 0x806f050c18810019 severity: warning alert category: warning serviceable: no ci...

  • Page 689

    806f050c-1881001b memory logging limit reached for [physicalmemoryelementname] on subsystem [memoryelementname]. Explanation: dimm 27 of meu memory logging limit has been reached. May also be shown as 806f050c1881001b or 0x806f050c1881001b severity: warning alert category: warning serviceable: no ci...

  • Page 690

    806f050c-1881001d memory logging limit reached for [physicalmemoryelementname] on subsystem [memoryelementname]. Explanation: dimm 29 of meu memory logging limit has been reached. May also be shown as 806f050c1881001d or 0x806f050c1881001d severity: warning alert category: warning serviceable: no ci...

  • Page 691

    806f050c-1881001f memory logging limit reached for [physicalmemoryelementname] on subsystem [memoryelementname]. Explanation: dimm 31 of meu memory logging limit has been reached. May also be shown as 806f050c1881001f or 0x806f050c1881001f severity: warning alert category: warning serviceable: no ci...

  • Page 692

    806f050c-2581ffff memory logging limit reached for [physicalmemoryelementname] on subsystem [memoryelementname]. Explanation: memory logging limit has been reached. May also be shown as 806f050c2581ffff or 0x806f050c2581ffff severity: warning alert category: warning serviceable: yes cim information:...

  • Page 693

    806f050d-0401ffff array in system [computersystemelementname] is in critical condition. Explanation: the drive is part of an raid array that is in critical condition. Immediate action is required to avoid a system outage. To identify drives in the critical array all member drives will report this me...

  • Page 694

    806f050d-0404ffff array in system [computersystemelementname] is in critical condition. Explanation: the drive is part of an raid array that is in critical condition. Immediate action is required to avoid a system outage. To identify drives in the critical array all member drives will report this me...

  • Page 695

    806f050d-0407ffff array in system [computersystemelementname] is in critical condition. Explanation: the drive is part of an raid array that is in critical condition. Immediate action is required to avoid a system outage. To identify drives in the critical array all member drives will report this me...

  • Page 696

    806f050d-040affff array in system [computersystemelementname] is in critical condition. Explanation: the drive is part of an raid array that is in critical condition. Immediate action is required to avoid a system outage. To identify drives in the critical array all member drives will report this me...

  • Page 697

    806f050d-040dffff array in system [computersystemelementname] is in critical condition. Explanation: the drive is part of an raid array that is in critical condition. Immediate action is required to avoid a system outage. To identify drives in the critical array all member drives will report this me...

  • Page 698

    806f052b-2101ffff invalid or unsupported firmware or software was detected on system [computersystemelementname]. Explanation: the imm primary firmware image has been corrupted. The imm is running on the backup image. May also be shown as 806f052b2101ffff or 0x806f052b2101ffff severity: error alert ...

  • Page 699

    806f0607-0303ffff an sm bios uncorrectable cpu complex error for [processorelementname] has asserted. Explanation: the uefi has detected a configuration type issue with processor 3. May also be shown as 806f06070303ffff or 0x806f06070303ffff severity: error alert category: critical serviceable: yes ...

  • Page 700

    806f060d-0400ffff array in system [computersystemelementname] has failed. Explanation: the drive is part of an raid array that is in the failed condition. To identify drives in the failed array all member drives will report this message. May also be shown as 806f060d0400ffff or 0x806f060d0400ffff se...

  • Page 701

    806f060d-0402ffff array in system [computersystemelementname] has failed. Explanation: the drive is part of an raid array that is in the failed condition. To identify drives in the failed array all member drives will report this message. May also be shown as 806f060d0402ffff or 0x806f060d0402ffff se...

  • Page 702

    806f060d-0404ffff array in system [computersystemelementname] has failed. Explanation: the drive is part of an raid array that is in the failed condition. To identify drives in the failed array all member drives will report this message. May also be shown as 806f060d0404ffff or 0x806f060d0404ffff se...

  • Page 703

    806f060d-0406ffff array in system [computersystemelementname] has failed. Explanation: the drive is part of an raid array that is in the failed condition. To identify drives in the failed array all member drives will report this message. May also be shown as 806f060d0406ffff or 0x806f060d0406ffff se...

  • Page 704

    806f060d-0408ffff array in system [computersystemelementname] has failed. Explanation: the drive is part of an raid array that is in the failed condition. To identify drives in the failed array all member drives will report this message. May also be shown as 806f060d0408ffff or 0x806f060d0408ffff se...

  • Page 705

    806f060d-040affff array in system [computersystemelementname] has failed. Explanation: the drive is part of an raid array that is in the failed condition. To identify drives in the failed array all member drives will report this message. May also be shown as 806f060d040affff or 0x806f060d040affff se...

  • Page 706

    806f060d-040cffff array in system [computersystemelementname] has failed. Explanation: the drive is part of an raid array that is in the failed condition. To identify drives in the failed array all member drives will report this message. May also be shown as 806f060d040cffff or 0x806f060d040cffff se...

  • Page 707

    806f060d-040effff array in system [computersystemelementname] has failed. Explanation: the drive is part of an raid array that is in the failed condition. To identify drives in the failed array all member drives will report this message. May also be shown as 806f060d040effff or 0x806f060d040effff se...

  • Page 708

    806f070c-08810001 configuration error for [physicalmemoryelementname] on subsystem [memoryelementname]. Explanation: a memory configuration error has occurred on dimm 1 of mem card 1. May also be shown as 806f070c08810001 or 0x806f070c08810001 severity: error alert category: critical serviceable: no...

  • Page 709

    806f070c-08810004 configuration error for [physicalmemoryelementname] on subsystem [memoryelementname]. Explanation: a memory configuration error has occurred on dimm 4 of mem card 1. May also be shown as 806f070c08810004 or 0x806f070c08810004 severity: error alert category: critical serviceable: no...

  • Page 710

    806f070c-08810007 configuration error for [physicalmemoryelementname] on subsystem [memoryelementname]. Explanation: a memory configuration error has occurred on dimm 7 of mem card 1. May also be shown as 806f070c08810007 or 0x806f070c08810007 severity: error alert category: critical serviceable: no...

  • Page 711

    806f070c-08820002 configuration error for [physicalmemoryelementname] on subsystem [memoryelementname]. Explanation: a memory configuration error has occurred on dimm 2 of mem card 2. May also be shown as 806f070c08820002 or 0x806f070c08820002 severity: error alert category: critical serviceable: no...

  • Page 712

    806f070c-08820005 configuration error for [physicalmemoryelementname] on subsystem [memoryelementname]. Explanation: a memory configuration error has occurred on dimm 5 of mem card 2. May also be shown as 806f070c08820005 or 0x806f070c08820005 severity: error alert category: critical serviceable: no...

  • Page 713

    806f070c-08820008 configuration error for [physicalmemoryelementname] on subsystem [memoryelementname]. Explanation: a memory configuration error has occurred on dimm 8 of mem card 2. May also be shown as 806f070c08820008 or 0x806f070c08820008 severity: error alert category: critical serviceable: no...

  • Page 714

    806f070c-08830003 configuration error for [physicalmemoryelementname] on subsystem [memoryelementname]. Explanation: a memory configuration error has occurred on dimm 3 of mem card 3. May also be shown as 806f070c08830003 or 0x806f070c08830003 severity: error alert category: critical serviceable: no...

  • Page 715

    806f070c-08830006 configuration error for [physicalmemoryelementname] on subsystem [memoryelementname]. Explanation: a memory configuration error has occurred on dimm 6 of mem card 3. May also be shown as 806f070c08830006 or 0x806f070c08830006 severity: error alert category: critical serviceable: no...

  • Page 716

    806f070c-08840001 configuration error for [physicalmemoryelementname] on subsystem [memoryelementname]. Explanation: a memory configuration error has occurred on dimm 1 of mem card 4. May also be shown as 806f070c08840001 or 0x806f070c08840001 severity: error alert category: critical serviceable: no...

  • Page 717

    806f070c-08840004 configuration error for [physicalmemoryelementname] on subsystem [memoryelementname]. Explanation: a memory configuration error has occurred on dimm 4 of mem card 4. May also be shown as 806f070c08840004 or 0x806f070c08840004 severity: error alert category: critical serviceable: no...

  • Page 718

    806f070c-08840007 configuration error for [physicalmemoryelementname] on subsystem [memoryelementname]. Explanation: a memory configuration error has occurred on dimm 7 of mem card 4. May also be shown as 806f070c08840007 or 0x806f070c08840007 severity: error alert category: critical serviceable: no...

  • Page 719

    806f070c-08850002 configuration error for [physicalmemoryelementname] on subsystem [memoryelementname]. Explanation: a memory configuration error has occurred on dimm 2 of mem card 5. May also be shown as 806f070c08850002 or 0x806f070c08850002 severity: error alert category: critical serviceable: no...

  • Page 720

    806f070c-08850005 configuration error for [physicalmemoryelementname] on subsystem [memoryelementname]. Explanation: a memory configuration error has occurred on dimm 5 of mem card 5. May also be shown as 806f070c08850005 or 0x806f070c08850005 severity: error alert category: critical serviceable: no...

  • Page 721

    806f070c-08850008 configuration error for [physicalmemoryelementname] on subsystem [memoryelementname]. Explanation: a memory configuration error has occurred on dimm 8 of mem card 5. May also be shown as 806f070c08850008 or 0x806f070c08850008 severity: error alert category: critical serviceable: no...

  • Page 722

    806f070c-08860003 configuration error for [physicalmemoryelementname] on subsystem [memoryelementname]. Explanation: a memory configuration error has occurred on dimm 3 of mem card 6. May also be shown as 806f070c08860003 or 0x806f070c08860003 severity: error alert category: critical serviceable: no...

  • Page 723

    806f070c-08860006 configuration error for [physicalmemoryelementname] on subsystem [memoryelementname]. Explanation: a memory configuration error has occurred on dimm 6 of mem card 6. May also be shown as 806f070c08860006 or 0x806f070c08860006 severity: error alert category: critical serviceable: no...

  • Page 724

    806f070c-08870001 configuration error for [physicalmemoryelementname] on subsystem [memoryelementname]. Explanation: a memory configuration error has occurred on dimm 1 of mem card 7. May also be shown as 806f070c08870001 or 0x806f070c08870001 severity: error alert category: critical serviceable: no...

  • Page 725

    806f070c-08870004 configuration error for [physicalmemoryelementname] on subsystem [memoryelementname]. Explanation: a memory configuration error has occurred on dimm 4 of mem card 7. May also be shown as 806f070c08870004 or 0x806f070c08870004 severity: error alert category: critical serviceable: no...

  • Page 726

    806f070c-08870007 configuration error for [physicalmemoryelementname] on subsystem [memoryelementname]. Explanation: a memory configuration error has occurred on dimm 7 of mem card 7. May also be shown as 806f070c08870007 or 0x806f070c08870007 severity: error alert category: critical serviceable: no...

  • Page 727

    806f070c-08880002 configuration error for [physicalmemoryelementname] on subsystem [memoryelementname]. Explanation: a memory configuration error has occurred on dimm 2 of mem card 8. May also be shown as 806f070c08880002 or 0x806f070c08880002 severity: error alert category: critical serviceable: no...

  • Page 728

    806f070c-08880005 configuration error for [physicalmemoryelementname] on subsystem [memoryelementname]. Explanation: a memory configuration error has occurred on dimm 5 of mem card 8. May also be shown as 806f070c08880005 or 0x806f070c08880005 severity: error alert category: critical serviceable: no...

  • Page 729

    806f070c-08880008 configuration error for [physicalmemoryelementname] on subsystem [memoryelementname]. Explanation: a memory configuration error has occurred on dimm 8 of mem card 8. May also be shown as 806f070c08880008 or 0x806f070c08880008 severity: error alert category: critical serviceable: no...

  • Page 730

    806f070c-18810003 configuration error for [physicalmemoryelementname] on subsystem [memoryelementname]. Explanation: a memory configuration error has occurred on dimm 3 of memory expansion unit(meu). May also be shown as 806f070c18810003 or 0x806f070c18810003 severity: error alert category: critical...

  • Page 731

    806f070c-18810006 configuration error for [physicalmemoryelementname] on subsystem [memoryelementname]. Explanation: a memory configuration error has occurred on dimm 6 of memory expansion unit(meu). May also be shown as 806f070c18810006 or 0x806f070c18810006 severity: error alert category: critical...

  • Page 732

    806f070c-18810009 configuration error for [physicalmemoryelementname] on subsystem [memoryelementname]. Explanation: a memory configuration error has occurred on dimm 9 of memory expansion unit(meu). May also be shown as 806f070c18810009 or 0x806f070c18810009 severity: error alert category: critical...

  • Page 733

    806f070c-1881000c configuration error for [physicalmemoryelementname] on subsystem [memoryelementname]. Explanation: a memory configuration error has occurred on dimm 12 of memory expansion unit(meu). May also be shown as 806f070c1881000c or 0x806f070c1881000c severity: error alert category: critica...

  • Page 734

    806f070c-1881000f configuration error for [physicalmemoryelementname] on subsystem [memoryelementname]. Explanation: a memory configuration error has occurred on dimm 15 of memory expansion unit(meu). May also be shown as 806f070c1881000f or 0x806f070c1881000f severity: error alert category: critica...

  • Page 735

    806f070c-18810012 configuration error for [physicalmemoryelementname] on subsystem [memoryelementname]. Explanation: a memory configuration error has occurred on dimm 18 of memory expansion unit(meu). May also be shown as 806f070c18810012 or 0x806f070c18810012 severity: error alert category: critica...

  • Page 736

    806f070c-18810015 configuration error for [physicalmemoryelementname] on subsystem [memoryelementname]. Explanation: a memory configuration error has occurred on dimm 21 of memory expansion unit(meu). May also be shown as 806f070c18810015 or 0x806f070c18810015 severity: error alert category: critica...

  • Page 737

    806f070c-18810018 configuration error for [physicalmemoryelementname] on subsystem [memoryelementname]. Explanation: a memory configuration error has occurred on dimm 24 of memory expansion unit(meu). May also be shown as 806f070c18810018 or 0x806f070c18810018 severity: error alert category: critica...

  • Page 738

    806f070c-1881001b configuration error for [physicalmemoryelementname] on subsystem [memoryelementname]. Explanation: a memory configuration error has occurred on dimm 27 of memory expansion unit(meu). May also be shown as 806f070c1881001b or 0x806f070c1881001b severity: error alert category: critica...

  • Page 739

    806f070c-1881001e configuration error for [physicalmemoryelementname] on subsystem [memoryelementname]. Explanation: a memory configuration error has occurred on dimm 30 of memory expansion unit(meu). May also be shown as 806f070c1881001e or 0x806f070c1881001e severity: error alert category: critica...

  • Page 740

    806f070c-2581ffff configuration error for [physicalmemoryelementname] on subsystem [memoryelementname]. Explanation: a memory card configuration error has occurred. May also be shown as 806f070c2581ffff or 0x806f070c2581ffff severity: error alert category: critical serviceable: yes cim information: ...

  • Page 741

    806f070c-2586ffff configuration error for [physicalmemoryelementname] on subsystem [memoryelementname]. Explanation: a memory configuration (memory card 1 bank) error has occurred. May also be shown as 806f070c2586ffff or 0x806f070c2586ffff severity: error alert category: critical serviceable: no ci...

  • Page 742

    806f070c-2589ffff configuration error for [physicalmemoryelementname] on subsystem [memoryelementname]. Explanation: a memory configuration (memory card 4 bank) error has occurred. May also be shown as 806f070c2589ffff or 0x806f070c2589ffff severity: error alert category: critical serviceable: no ci...

  • Page 743

    806f070c-258cffff configuration error for [physicalmemoryelementname] on subsystem [memoryelementname]. Explanation: a memory configuration (memory card 7 bank) error has occurred. May also be shown as 806f070c258cffff or 0x806f070c258cffff severity: error alert category: critical serviceable: no ci...

  • Page 744

    806f070d-0401ffff rebuild in progress for array in system [computersystemelementname]. Explanation: imm has detected that an array rebuild is in progress. May also be shown as 806f070d0401ffff or 0x806f070d0401ffff severity: info alert category: system serviceable: no cim information: prefix: plat a...

  • Page 745

    806f070d-0404ffff rebuild in progress for array in system [computersystemelementname]. Explanation: imm has detected that an array rebuild is in progress. May also be shown as 806f070d0404ffff or 0x806f070d0404ffff severity: info alert category: system serviceable: no cim information: prefix: plat a...

  • Page 746

    806f070d-0407ffff rebuild in progress for array in system [computersystemelementname]. Explanation: imm has detected that an array rebuild is in progress. May also be shown as 806f070d0407ffff or 0x806f070d0407ffff severity: info alert category: system serviceable: no cim information: prefix: plat a...

  • Page 747

    806f070d-040affff rebuild in progress for array in system [computersystemelementname]. Explanation: imm has detected that an array rebuild is in progress. May also be shown as 806f070d040affff or 0x806f070d040affff severity: info alert category: system serviceable: no cim information: prefix: plat a...

  • Page 748

    806f070d-040dffff rebuild in progress for array in system [computersystemelementname]. Explanation: imm has detected that an array rebuild is in progress. May also be shown as 806f070d040dffff or 0x806f070d040dffff severity: info alert category: system serviceable: no cim information: prefix: plat a...

  • Page 749

    806f0807-0301ffff [processorelementname] has been disabled. Explanation: imm has detected that processor 1 has been disabled. May also be shown as 806f08070301ffff or 0x806f08070301ffff severity: info alert category: system serviceable: no cim information: prefix: plat and id: 0061 snmp trap id: aut...

  • Page 750

    806f0807-0304ffff [processorelementname] has been disabled. Explanation: imm has detected that processor 4 has been disabled. May also be shown as 806f08070304ffff or 0x806f08070304ffff severity: info alert category: system serviceable: no cim information: prefix: plat and id: 0061 snmp trap id: aut...

  • Page 751

    806f0813-2581ffff a uncorrectable bus error has occurred on system [computersystemelementname]. Explanation: imm has detected a bus uncorrectable error. May also be shown as 806f08132581ffff or 0x806f08132581ffff severity: error alert category: critical serviceable: yes cim information: prefix: plat...

  • Page 752

    806f090c-2586ffff [physicalmemoryelementname] on subsystem [memoryelementname] throttled. Explanation: a dimm in mem card 1 has throttled. May also be shown as 806f090c2586ffff or 0x806f090c2586ffff severity: info alert category: system serviceable: no cim information: prefix: plat and id: 0142 snmp...

  • Page 753

    806f090c-2589ffff [physicalmemoryelementname] on subsystem [memoryelementname] throttled. Explanation: a dimm in mem card 4 has throttled. May also be shown as 806f090c2589ffff or 0x806f090c2589ffff severity: info alert category: system serviceable: no cim information: prefix: plat and id: 0142 snmp...

  • Page 754

    806f090c-258cffff [physicalmemoryelementname] on subsystem [memoryelementname] throttled. Explanation: a dimm in mem card 7 has throttled. May also be shown as 806f090c258cffff or 0x806f090c258cffff severity: info alert category: system serviceable: no cim information: prefix: plat and id: 0142 snmp...

  • Page 755

    806f090c-258fffff [physicalmemoryelementname] on subsystem [memoryelementname] throttled. Explanation: a memory in meu bank 2 has throttled. May also be shown as 806f090c258fffff or 0x806f090c258fffff severity: info alert category: system serviceable: no cim information: prefix: plat and id: 0142 sn...

  • Page 756

    806f0a07-0301ffff [processorelementname] is operating in a degraded state. Explanation: the processor 1 is being throttled due to thermal or power conditions. May also be shown as 806f0a070301ffff or 0x806f0a070301ffff severity: warning alert category: warning serviceable: yes cim information: prefi...

  • Page 757

    806f0a07-0303ffff [processorelementname] is operating in a degraded state. Explanation: the processor 3 is being throttled due to thermal or power conditions. May also be shown as 806f0a070303ffff or 0x806f0a070303ffff severity: warning alert category: warning serviceable: yes cim information: prefi...

  • Page 758

    806f0a0c-2586ffff an over-temperature condition has been detected on the [physicalmemoryelementname] on subsystem [memoryelementname]. Explanation: imm has detected an over temperature condition on the memory card 1. May also be shown as 806f0a0c2586ffff or 0x806f0a0c2586ffff severity: error alert c...

  • Page 759

    806f0a0c-2588ffff an over-temperature condition has been detected on the [physicalmemoryelementname] on subsystem [memoryelementname]. Explanation: imm has detected an over temperature condition on the memory card 3. May also be shown as 806f0a0c2588ffff or 0x806f0a0c2588ffff severity: error alert c...

  • Page 760

    806f0a0c-258affff an over-temperature condition has been detected on the [physicalmemoryelementname] on subsystem [memoryelementname]. Explanation: imm has detected an over temperature condition on the memory card 5. May also be shown as 806f0a0c258affff or 0x806f0a0c258affff severity: error alert c...

  • Page 761

    806f0a0c-258cffff an over-temperature condition has been detected on the [physicalmemoryelementname] on subsystem [memoryelementname]. Explanation: imm has detected an over temperature condition on the memory card 7. May also be shown as 806f0a0c258cffff or 0x806f0a0c258cffff severity: error alert c...

  • Page 762

    806f0a0c-258effff an over-temperature condition has been detected on the [physicalmemoryelementname] on subsystem [memoryelementname]. Explanation: imm has detected an over temperature condition on the meu bank 1. May also be shown as 806f0a0c258effff or 0x806f0a0c258effff severity: error alert cate...

  • Page 763

    806f0a0c-2590ffff an over-temperature condition has been detected on the [physicalmemoryelementname] on subsystem [memoryelementname]. Explanation: imm has detected an over temperature condition on the meu bank 3. May also be shown as 806f0a0c2590ffff or 0x806f0a0c2590ffff severity: error alert cate...

  • Page 764

    806f0a13-2401ffff a fatal bus error has occurred on system [computersystemelementname]. Explanation: imm has detected a bus fatal error. May also be shown as 806f0a132401ffff or 0x806f0a132401ffff severity: error alert category: critical serviceable: yes cim information: prefix: plat and id: 0244 sn...

  • Page 765

    81010202-0701ffff numeric sensor [numericsensorelementname] going low (lower critical) has deasserted. Explanation: a previously low voltage has returned to above its specified threshold (sensor planar 12v, planar 3.3v, or planar 5v). May also be shown as 810102020701ffff or 0x810102020701ffff sever...

  • Page 766

    81010204-1d02ffff numeric sensor [numericsensorelementname] going low (lower critical) has deasserted. Explanation: imm has detected a fan (fan 2a tach, fan 2b tach) going low has deasserted. May also be shown as 810102041d02ffff or 0x810102041d02ffff severity: info alert category: critical servicea...

  • Page 767

    81010204-1d05ffff numeric sensor [numericsensorelementname] going low (lower critical) has deasserted. Explanation: imm has detected a fan (fan 5a tach, fan 5b tach) going low has deasserted. May also be shown as 810102041d05ffff or 0x810102041d05ffff severity: info alert category: critical servicea...

  • Page 768

    81010204-1d08ffff numeric sensor [numericsensorelementname] going low (lower critical) has deasserted. Explanation: imm has detected a fan (meu fan 3 tach) going low has deasserted. May also be shown as 810102041d08ffff or 0x810102041d08ffff severity: info alert category: critical serviceable: no ci...

  • Page 769

    81010701-0c01ffff numeric sensor [numericsensorelementname] going high (upper non-critical) has deasserted. Explanation: an upper non-critical sensor going high has deasserted. May also be shown as 810107010c01ffff or 0x810107010c01ffff severity: info alert category: warning serviceable: no cim info...

  • Page 770

    81010901-0c01ffff numeric sensor [numericsensorelementname] going high (upper critical) has deasserted. Explanation: an upper critical sensor going high has deasserted. May also be shown as 810109010c01ffff or 0x810109010c01ffff severity: info alert category: critical serviceable: no cim information...

  • Page 771

    81010903-1500ffff numeric sensor [numericsensorelementname] going high (upper critical) has deasserted. Explanation: an upper critical current sensor going high has deasserted may also be shown as 810109031500ffff or 0x810109031500ffff severity: info alert category: critical serviceable: no cim info...

  • Page 772

    81010b03-1500ffff numeric sensor [numericsensorelementname] going high (upper non-recoverable) has deasserted. Explanation: an upper non-recoverable current sensor going high has deasserted. May also be shown as 81010b031500ffff or 0x81010b031500ffff severity: info alert category: critical serviceab...

  • Page 773

    8103010c-2582ffff sensor [sensorelementname] has deasserted. Explanation: lane failover on smi lane channel 2 has deasserted. May also be shown as 8103010c2582ffff or 0x8103010c2582ffff severity: info alert category: system serviceable: no cim information: prefix: plat and id: 0509 snmp trap id: aut...

  • Page 774

    8103010c-2585ffff sensor [sensorelementname] has deasserted. Explanation: lane failover on smi lane channel 5 has deasserted. May also be shown as 8103010c2585ffff or 0x8103010c2585ffff severity: info alert category: system serviceable: no cim information: prefix: plat and id: 0509 snmp trap id: aut...

  • Page 775

    8103010c-2588ffff sensor [sensorelementname] has deasserted. Explanation: lane failover on smi lane channel 8 has deasserted. May also be shown as 8103010c2588ffff or 0x8103010c2588ffff severity: info alert category: system serviceable: no cim information: prefix: plat and id: 0509 snmp trap id: aut...

  • Page 776

    81070201-0302ffff sensor [sensorelementname] has transitioned to a less severe state from critical. Explanation: imm has detected a cpu 2 overtemp sensor transition to less severe from critical. May also be shown as 810702010302ffff or 0x810702010302ffff severity: info alert category: critical servi...

  • Page 777

    81070201-0a01ffff sensor [sensorelementname] has transitioned to a less severe state from critical. Explanation: power supply 1 thermal fault transition to less severe from critical may also be shown as 810702010a01ffff or 0x810702010a01ffff severity: info alert category: critical serviceable: no ci...

  • Page 778

    81070201-1e83ffff sensor [sensorelementname] has transitioned to a less severe state from critical. Explanation: ioh thermal status transition to less severe from critical may also be shown as 810702011e83ffff or 0x810702011e83ffff severity: info alert category: critical serviceable: no cim informat...

  • Page 779

    81070204-1881ffff sensor [sensorelementname] has transitioned to a less severe state from critical. Explanation: meu power supply fan transition to less severe from critical may also be shown as 810702041881ffff or 0x810702041881ffff severity: info alert category: critical serviceable: no cim inform...

  • Page 780

    81070301-0302ffff sensor [sensorelementname] has deasserted the transition to non-recoverable from a less severe state. Explanation: the microprocessor 2 temperature has returned to below its specified threshold. May also be shown as 810703010302ffff or 0x810703010302ffff severity: info alert catego...

  • Page 781

    81070301-1e83ffff sensor [sensorelementname] has deasserted the transition to non-recoverable from a less severe state. Explanation: ioh temp status transition to non-recoverable from less severe has deasserted may also be shown as 810703011e83ffff or 0x810703011e83ffff severity: info alert category...

  • Page 782

    81070608-0a02ffff sensor [sensorelementname] has deasserted the transition to non-recoverable. Explanation: memory expansion module power supply 2 error (transition to non-recoverable) has deasserted may also be shown as 810706080a02ffff or 0x810706080a02ffff severity: info alert category: critical ...

  • Page 783

    81070608-1403ffff sensor [sensorelementname] has deasserted the transition to non-recoverable. Explanation: a voltage regulator in memory expansion module transition to non-recoverable has deasserted. May also be shown as 810706081403ffff or 0x810706081403ffff severity: info alert category: critical...

  • Page 784

    81070608-1406ffff sensor [sensorelementname] has deasserted the transition to non-recoverable. Explanation: a voltage regulator in memory expansion module transition to non-recoverable has deasserted. May also be shown as 810706081406ffff or 0x810706081406ffff severity: info alert category: critical...

  • Page 785

    81070608-1409ffff sensor [sensorelementname] has deasserted the transition to non-recoverable. Explanation: a voltage regulator transition to non-recoverable has deasserted. May also be shown as 810706081409ffff or 0x810706081409ffff severity: info alert category: critical serviceable: no cim inform...

  • Page 786

    81070608-140cffff sensor [sensorelementname] has deasserted the transition to non-recoverable. Explanation: cpu 3 voltage regulator transition to non-recoverable has deasserted. May also be shown as 81070608140cffff or 0x81070608140cffff severity: info alert category: critical serviceable: no cim in...

  • Page 787

    81070608-140fffff sensor [sensorelementname] has deasserted the transition to non-recoverable. Explanation: a voltage regulator in cpu 3 or 4 transition to non-recoverable has deasserted. May also be shown as 81070608140fffff or 0x81070608140fffff severity: info alert category: critical serviceable:...

  • Page 788

    81070608-1412ffff sensor [sensorelementname] has deasserted the transition to non-recoverable. Explanation: a voltage regulator transition to non-recoverable has deasserted. May also be shown as 810706081412ffff or 0x810706081412ffff severity: info alert category: critical serviceable: no cim inform...

  • Page 789

    81070608-1415ffff sensor [sensorelementname] has deasserted the transition to non-recoverable. Explanation: a voltage regulator transition to non-recoverable has deasserted. May also be shown as 810706081415ffff or 0x810706081415ffff severity: info alert category: critical serviceable: no cim inform...

  • Page 790

    81080004-1d01ffff device [logicaldeviceelementname] has been added. Explanation: device fan 1 has been inserted. May also be shown as 810800041d01ffff or 0x810800041d01ffff severity: info alert category: system serviceable: no cim information: prefix: plat and id: 0536 snmp trap id: automatically no...

  • Page 791

    81080004-1d04ffff device [logicaldeviceelementname] has been added. Explanation: device fan 4 has been inserted. May also be shown as 810800041d04ffff or 0x810800041d04ffff severity: info alert category: system serviceable: no cim information: prefix: plat and id: 0536 snmp trap id: automatically no...

  • Page 792

    81080004-1d07ffff device [logicaldeviceelementname] has been added. Explanation: fan 2 in memory expansion module has been inserted. May also be shown as 810800041d07ffff or 0x810800041d07ffff severity: info alert category: system serviceable: no cim information: prefix: plat and id: 0536 snmp trap ...

  • Page 793

    81080004-1d0affff device [logicaldeviceelementname] has been added. Explanation: fan 5 in memory expansion module has been inserted. May also be shown as 810800041d0affff or 0x810800041d0affff severity: info alert category: system serviceable: no cim information: prefix: plat and id: 0536 snmp trap ...

  • Page 794

    810b010a-1e83ffff redundancy lost for [redundancysetelementname] has deasserted. Explanation: fan 3 redundancy has been regained. May also be shown as 810b010a1e83ffff or 0x810b010a1e83ffff severity: info alert category: critical serviceable: no cim information: prefix: plat and id: 0803 snmp trap i...

  • Page 795

    810b030c-2581ffff non-redundant:sufficient resources from redundancy degraded or fully redundant for [redundancysetelementname] has deasserted. Explanation: memory component group has regained its redundancy. May also be shown as 810b030c2581ffff or 0x810b030c2581ffff severity: info alert category: ...

  • Page 796

    810b050a-1e83ffff non-redundant:insufficient resources for [redundancysetelementname] has deasserted. Explanation: fan 3 has regained its redundancy. May also be shown as 810b050a1e83ffff or 0x810b050a1e83ffff severity: info alert category: warning serviceable: no cim information: prefix: plat and i...

  • Page 797

    816f0007-0301ffff [processorelementname] has recovered from ierr. Explanation: imm has detected that processor 1 recovered from an ierr condition. May also be shown as 816f00070301ffff or 0x816f00070301ffff severity: info alert category: critical serviceable: no cim information: prefix: plat and id:...

  • Page 798

    816f0007-0304ffff [processorelementname] has recovered from ierr. Explanation: imm has detected that processor 4 recovered from an ierr condition. May also be shown as 816f00070304ffff or 0x816f00070304ffff severity: info alert category: critical serviceable: no cim information: prefix: plat and id:...

  • Page 799

    816f0008-1881ffff [powersupplyelementname] has been removed from container [physicalpackageelementname]. Explanation: meu power supple has been removed. May also be shown as 816f00081881ffff or 0x816f00081881ffff severity: info alert category: system serviceable: no cim information: prefix: plat and...

  • Page 800

    816f000d-0401ffff the drive [storagevolumeelementname] has been removed from unit [physicalpackageelementname]. Explanation: presence of drive 1 is no longer detected. If hard drive is absent from drive bay a filler is required. May also be shown as 816f000d0401ffff or 0x816f000d0401ffff severity: i...

  • Page 801

    816f000d-0403ffff the drive [storagevolumeelementname] has been removed from unit [physicalpackageelementname]. Explanation: presence of drive 3 is no longer detected. If hard drive is absent from drive bay a filler is required. May also be shown as 816f000d0403ffff or 0x816f000d0403ffff severity: i...

  • Page 802

    816f000d-0405ffff the drive [storagevolumeelementname] has been removed from unit [physicalpackageelementname]. Explanation: presence of drive 5 is no longer detected. If hard drive is absent from drive bay a filler is required. May also be shown as 816f000d0405ffff or 0x816f000d0405ffff severity: i...

  • Page 803

    816f000d-0407ffff the drive [storagevolumeelementname] has been removed from unit [physicalpackageelementname]. Explanation: presence of drive 7 is no longer detected. If hard drive is absent from drive bay a filler is required. May also be shown as 816f000d0407ffff or 0x816f000d0407ffff severity: i...

  • Page 804

    816f000d-0409ffff the drive [storagevolumeelementname] has been removed from unit [physicalpackageelementname]. Explanation: presence of drive 9 is no longer detected. If hard drive is absent from drive bay a filler is required. May also be shown as 816f000d0409ffff or 0x816f000d0409ffff severity: i...

  • Page 805

    816f000d-040bffff the drive [storagevolumeelementname] has been removed from unit [physicalpackageelementname]. Explanation: presence of drive 11 is no longer detected. If hard drive is absent from drive bay a filler is required. May also be shown as 816f000d040bffff or 0x816f000d040bffff severity: ...

  • Page 806

    816f000d-040dffff the drive [storagevolumeelementname] has been removed from unit [physicalpackageelementname]. Explanation: presence of drive 13 is no longer detected. If hard drive is absent from drive bay a filler is required. May also be shown as 816f000d040dffff or 0x816f000d040dffff severity: ...

  • Page 807

    816f000d-040fffff the drive [storagevolumeelementname] has been removed from unit [physicalpackageelementname]. Explanation: presence of drive 15 is no longer detected. If hard drive is absent from drive bay a filler is required. May also be shown as 816f000d040fffff or 0x816f000d040fffff severity: ...

  • Page 808

    816f001b-1f06ffff the network port [managedelementname] has been disconnected. Explanation: memory expansion module led cable was disconnected. May also be shown as 816f001b1f06ffff or 0x816f001b1f06ffff severity: warning alert category: warning serviceable: no cim information: prefix: plat and id: ...

  • Page 809

    816f001b-1f09ffff the network port [managedelementname] has been disconnected. Explanation: the exa cable 3 is disconnected. May also be shown as 816f001b1f09ffff or 0x816f001b1f09ffff severity: warning alert category: warning serviceable: no cim information: prefix: plat and id: 0263 snmp trap id: ...

  • Page 810

    816f0021-0b06ffff fault condition removed on slot [physicalconnectorelementname] on system [computersystemelementname]. Explanation: imm has detected a fault condition in pcie slot 6 has been removed. May also be shown as 816f00210b06ffff or 0x816f00210b06ffff severity: info alert category: critical...

  • Page 811

    816f0021-0b09ffff fault condition removed on slot [physicalconnectorelementname] on system [computersystemelementname]. Explanation: fault condition in pcie slot 6 has been removed may also be shown as 816f00210b09ffff or 0x816f00210b09ffff severity: info alert category: critical serviceable: no cim...

  • Page 812

    816f0021-2582ffff fault condition removed on slot [physicalconnectorelementname] on system [computersystemelementname]. Explanation: imm has detected that a fault condition in a pcie slot has been removed. May also be shown as 816f00212582ffff or 0x816f00212582ffff severity: info alert category: cri...

  • Page 813

    816f0107-0302ffff an over-temperature condition has been removed on [processorelementname]. Explanation: the microprocessor 2 temperature has returned to below the critical level. May also be shown as 816f01070302ffff or 0x816f01070302ffff severity: info alert category: critical serviceable: no cim ...

  • Page 814

    816f0108-0a01ffff [powersupplyelementname] has returned to ok status. Explanation: imm has detected that power supply 1 has returned to a normal operational status. May also be shown as 816f01080a01ffff or 0x816f01080a01ffff severity: info alert category: critical serviceable: no cim information: pr...

  • Page 815

    816f010c-08810001 uncorrectable error recovery detected for [physicalmemoryelementname] on subsystem [memoryelementname]. Explanation: a memory uncorrectable error recovery has occured in dimm 1 of mem card 1. May also be shown as 816f010c08810001 or 0x816f010c08810001 severity: info alert category:...

  • Page 816

    816f010c-08810004 uncorrectable error recovery detected for [physicalmemoryelementname] on subsystem [memoryelementname]. Explanation: a memory uncorrectable error recovery has occured in dimm 4 of mem card 1. May also be shown as 816f010c08810004 or 0x816f010c08810004 severity: info alert category:...

  • Page 817

    816f010c-08810007 uncorrectable error recovery detected for [physicalmemoryelementname] on subsystem [memoryelementname]. Explanation: a memory uncorrectable error recovery has occured in dimm 7 of mem card 1. May also be shown as 816f010c08810007 or 0x816f010c08810007 severity: info alert category:...

  • Page 818

    816f010c-08820002 uncorrectable error recovery detected for [physicalmemoryelementname] on subsystem [memoryelementname]. Explanation: a memory uncorrectable error recovery has occured in dimm 2 of mem card 2. May also be shown as 816f010c08820002 or 0x816f010c08820002 severity: info alert category:...

  • Page 819

    816f010c-08820005 uncorrectable error recovery detected for [physicalmemoryelementname] on subsystem [memoryelementname]. Explanation: a memory uncorrectable error recovery has occured in dimm 5 of mem card 2. May also be shown as 816f010c08820005 or 0x816f010c08820005 severity: info alert category:...

  • Page 820

    816f010c-08820008 uncorrectable error recovery detected for [physicalmemoryelementname] on subsystem [memoryelementname]. Explanation: a memory uncorrectable error recovery has occured in dimm 8 of mem card 2. May also be shown as 816f010c08820008 or 0x816f010c08820008 severity: info alert category:...

  • Page 821

    816f010c-08830003 uncorrectable error recovery detected for [physicalmemoryelementname] on subsystem [memoryelementname]. Explanation: a memory uncorrectable error recovery has occured in dimm 3 of mem card 3. May also be shown as 816f010c08830003 or 0x816f010c08830003 severity: info alert category:...

  • Page 822

    816f010c-08830006 uncorrectable error recovery detected for [physicalmemoryelementname] on subsystem [memoryelementname]. Explanation: a memory uncorrectable error recovery has occured in dimm 6 of mem card 3. May also be shown as 816f010c08830006 or 0x816f010c08830006 severity: info alert category:...

  • Page 823

    816f010c-08840001 uncorrectable error recovery detected for [physicalmemoryelementname] on subsystem [memoryelementname]. Explanation: a memory uncorrectable error recovery has occured in dimm 1 of mem card 4. May also be shown as 816f010c08840001 or 0x816f010c08840001 severity: info alert category:...

  • Page 824

    816f010c-08840004 uncorrectable error recovery detected for [physicalmemoryelementname] on subsystem [memoryelementname]. Explanation: a memory uncorrectable error recovery has occured in dimm 4 of mem card 4. May also be shown as 816f010c08840004 or 0x816f010c08840004 severity: info alert category:...

  • Page 825

    816f010c-08840007 uncorrectable error recovery detected for [physicalmemoryelementname] on subsystem [memoryelementname]. Explanation: a memory uncorrectable error recovery has occured in dimm 7 of mem card 4. May also be shown as 816f010c08840007 or 0x816f010c08840007 severity: info alert category:...

  • Page 826

    816f010c-08850002 uncorrectable error recovery detected for [physicalmemoryelementname] on subsystem [memoryelementname]. Explanation: a memory uncorrectable error recovery has occured in dimm 2 of mem card 5. May also be shown as 816f010c08850002 or 0x816f010c08850002 severity: info alert category:...

  • Page 827

    816f010c-08850005 uncorrectable error recovery detected for [physicalmemoryelementname] on subsystem [memoryelementname]. Explanation: a memory uncorrectable error recovery has occured in dimm 5 of mem card 5. May also be shown as 816f010c08850005 or 0x816f010c08850005 severity: info alert category:...

  • Page 828

    816f010c-08850008 uncorrectable error recovery detected for [physicalmemoryelementname] on subsystem [memoryelementname]. Explanation: a memory uncorrectable error recovery has occured in dimm 8 of mem card 5. May also be shown as 816f010c08850008 or 0x816f010c08850008 severity: info alert category:...

  • Page 829

    816f010c-08860003 uncorrectable error recovery detected for [physicalmemoryelementname] on subsystem [memoryelementname]. Explanation: a memory uncorrectable error recovery has occured in dimm 3 of mem card 6. May also be shown as 816f010c08860003 or 0x816f010c08860003 severity: info alert category:...

  • Page 830

    816f010c-08860006 uncorrectable error recovery detected for [physicalmemoryelementname] on subsystem [memoryelementname]. Explanation: a memory uncorrectable error recovery has occured in dimm 6 of mem card 6. May also be shown as 816f010c08860006 or 0x816f010c08860006 severity: info alert category:...

  • Page 831

    816f010c-08870001 uncorrectable error recovery detected for [physicalmemoryelementname] on subsystem [memoryelementname]. Explanation: a memory uncorrectable error recovery has occured in dimm 1 of mem card 7. May also be shown as 816f010c08870001 or 0x816f010c08870001 severity: info alert category:...

  • Page 832

    816f010c-08870004 uncorrectable error recovery detected for [physicalmemoryelementname] on subsystem [memoryelementname]. Explanation: a memory uncorrectable error recovery has occured in dimm 4 of mem card 7. May also be shown as 816f010c08870004 or 0x816f010c08870004 severity: info alert category:...

  • Page 833

    816f010c-08870007 uncorrectable error recovery detected for [physicalmemoryelementname] on subsystem [memoryelementname]. Explanation: a memory uncorrectable error recovery has occured in dimm 7 of mem card 7. May also be shown as 816f010c08870007 or 0x816f010c08870007 severity: info alert category:...

  • Page 834

    816f010c-08880002 uncorrectable error recovery detected for [physicalmemoryelementname] on subsystem [memoryelementname]. Explanation: a memory uncorrectable error recovery has occured in dimm 2 of mem card 8. May also be shown as 816f010c08880002 or 0x816f010c08880002 severity: info alert category:...

  • Page 835

    816f010c-08880005 uncorrectable error recovery detected for [physicalmemoryelementname] on subsystem [memoryelementname]. Explanation: a memory uncorrectable error recovery has occured in dimm 5 of mem card 8. May also be shown as 816f010c08880005 or 0x816f010c08880005 severity: info alert category:...

  • Page 836

    816f010c-08880008 uncorrectable error recovery detected for [physicalmemoryelementname] on subsystem [memoryelementname]. Explanation: a memory uncorrectable error recovery has occured in dimm 8 of mem card 8. May also be shown as 816f010c08880008 or 0x816f010c08880008 severity: info alert category:...

  • Page 837

    816f010c-18810003 uncorrectable error recovery detected for [physicalmemoryelementname] on subsystem [memoryelementname]. Explanation: a memory uncorrectable error recovery has occured in dimm 3 of memory expansion unit(meu). May also be shown as 816f010c18810003 or 0x816f010c18810003 severity: info...

  • Page 838

    816f010c-18810006 uncorrectable error recovery detected for [physicalmemoryelementname] on subsystem [memoryelementname]. Explanation: a memory uncorrectable error recovery has occured in dimm 6 of memory expansion unit(meu). May also be shown as 816f010c18810006 or 0x816f010c18810006 severity: info...

  • Page 839

    816f010c-18810009 uncorrectable error recovery detected for [physicalmemoryelementname] on subsystem [memoryelementname]. Explanation: a memory uncorrectable error recovery has occured in dimm 9 of memory expansion unit(meu). May also be shown as 816f010c18810009 or 0x816f010c18810009 severity: info...

  • Page 840

    816f010c-1881000c uncorrectable error recovery detected for [physicalmemoryelementname] on subsystem [memoryelementname]. Explanation: a memory uncorrectable error recovery has occured in dimm 12 of memory expansion unit(meu). May also be shown as 816f010c1881000c or 0x816f010c1881000c severity: inf...

  • Page 841

    816f010c-1881000f uncorrectable error recovery detected for [physicalmemoryelementname] on subsystem [memoryelementname]. Explanation: a memory uncorrectable error recovery has occured in dimm 15 of memory expansion unit(meu). May also be shown as 816f010c1881000f or 0x816f010c1881000f severity: inf...

  • Page 842

    816f010c-18810012 uncorrectable error recovery detected for [physicalmemoryelementname] on subsystem [memoryelementname]. Explanation: a memory uncorrectable error recovery has occured in dimm 18 of memory expansion unit(meu). May also be shown as 816f010c18810012 or 0x816f010c18810012 severity: inf...

  • Page 843

    816f010c-18810015 uncorrectable error recovery detected for [physicalmemoryelementname] on subsystem [memoryelementname]. Explanation: a memory uncorrectable error recovery has occured in dimm 21 of memory expansion unit(meu). May also be shown as 816f010c18810015 or 0x816f010c18810015 severity: inf...

  • Page 844

    816f010c-18810018 uncorrectable error recovery detected for [physicalmemoryelementname] on subsystem [memoryelementname]. Explanation: a memory uncorrectable error recovery has occured in dimm 24 of memory expansion unit(meu). May also be shown as 816f010c18810018 or 0x816f010c18810018 severity: inf...

  • Page 845

    816f010c-1881001b uncorrectable error recovery detected for [physicalmemoryelementname] on subsystem [memoryelementname]. Explanation: a memory uncorrectable error recovery has occured in dimm 27 of memory expansion unit(meu). May also be shown as 816f010c1881001b or 0x816f010c1881001b severity: inf...

  • Page 846

    816f010c-1881001e uncorrectable error recovery detected for [physicalmemoryelementname] on subsystem [memoryelementname]. Explanation: a memory uncorrectable error recovery has occured in dimm 30 of memory expansion unit(meu). May also be shown as 816f010c1881001e or 0x816f010c1881001e severity: inf...

  • Page 847

    816f010c-2581ffff uncorrectable error recovery detected for [physicalmemoryelementname] on subsystem [memoryelementname]. Explanation: a memory uncorrectable error recovery has been detected. May also be shown as 816f010c2581ffff or 0x816f010c2581ffff severity: info alert category: critical servicea...

  • Page 848

    816f010d-0402ffff the drive [storagevolumeelementname] has been enabled. Explanation: the previously disabled drive 2 has been enabled. May also be shown as 816f010d0402ffff or 0x816f010d0402ffff severity: info alert category: critical serviceable: no cim information: prefix: plat and id: 0167 snmp ...

  • Page 849

    816f010d-0405ffff the drive [storagevolumeelementname] has been enabled. Explanation: the previously disabled drive 5 has been enabled. May also be shown as 816f010d0405ffff or 0x816f010d0405ffff severity: info alert category: critical serviceable: no cim information: prefix: plat and id: 0167 snmp ...

  • Page 850

    816f010d-0408ffff the drive [storagevolumeelementname] has been enabled. Explanation: the previously disabled drive 8 has been enabled. May also be shown as 816f010d0408ffff or 0x816f010d0408ffff severity: info alert category: critical serviceable: no cim information: prefix: plat and id: 0167 snmp ...

  • Page 851

    816f010d-040bffff the drive [storagevolumeelementname] has been enabled. Explanation: the previously disabled drive 11 has been enabled. May also be shown as 816f010d040bffff or 0x816f010d040bffff severity: info alert category: critical serviceable: no cim information: prefix: plat and id: 0167 snmp...

  • Page 852

    816f010d-040effff the drive [storagevolumeelementname] has been enabled. Explanation: the previously disabled drive 14 has been enabled. May also be shown as 816f010d040effff or 0x816f010d040effff severity: info alert category: critical serviceable: no cim information: prefix: plat and id: 0167 snmp...

  • Page 853

    816f0113-1701ffff system [computersystemelementname] has recovered from a bus timeout. Explanation: system has recovered from a bus timeout may also be shown as 816f01131701ffff or 0x816f01131701ffff severity: info alert category: critical serviceable: no cim information: prefix: plat and id: 0225 s...

  • Page 854

    816f011b-1f05ffff the connector [physicalconnectorelementname] configuration error has been repaired. Explanation: an fan cable configuration error was repaired may also be shown as 816f011b1f05ffff or 0x816f011b1f05ffff severity: info alert category: critical serviceable: no cim information: prefix...

  • Page 855

    816f011b-1f08ffff the connector [physicalconnectorelementname] configuration error has been repaired. Explanation: exa cable 2 configuration error was repaired may also be shown as 816f011b1f08ffff or 0x816f011b1f08ffff severity: info alert category: critical serviceable: no cim information: prefix:...

  • Page 856

    816f0207-0301ffff [processorelementname] has recovered from frb1/bist condition. Explanation: imm has detected that processor 1 has recovered from a frb1/bist condition. May also be shown as 816f02070301ffff or 0x816f02070301ffff severity: info alert category: critical serviceable: no cim informatio...

  • Page 857

    816f0207-0304ffff [processorelementname] has recovered from frb1/bist condition. Explanation: imm has detected that processor 4 has recovered from a frb1/bist condition. May also be shown as 816f02070304ffff or 0x816f02070304ffff severity: info alert category: critical serviceable: no cim informatio...

  • Page 858

    816f020d-0401ffff failure no longer predicted on drive [storagevolumeelementname] for array [computersystemelementname]. Explanation: the predicted failure for drive 1 no longer exists. May also be shown as 816f020d0401ffff or 0x816f020d0401ffff severity: info alert category: warning serviceable: no...

  • Page 859

    816f020d-0404ffff failure no longer predicted on drive [storagevolumeelementname] for array [computersystemelementname]. Explanation: the predicted failure for drive 4 no longer exists. May also be shown as 816f020d0404ffff or 0x816f020d0404ffff severity: info alert category: warning serviceable: no...

  • Page 860

    816f020d-0407ffff failure no longer predicted on drive [storagevolumeelementname] for array [computersystemelementname]. Explanation: the predicted failure for drive 7 no longer exists. May also be shown as 816f020d0407ffff or 0x816f020d0407ffff severity: info alert category: warning serviceable: no...

  • Page 861

    816f020d-040affff failure no longer predicted on drive [storagevolumeelementname] for array [computersystemelementname]. Explanation: the predicted failure for drive 10 no longer exists. May also be shown as 816f020d040affff or 0x816f020d040affff severity: info alert category: warning serviceable: n...

  • Page 862

    816f020d-040dffff failure no longer predicted on drive [storagevolumeelementname] for array [computersystemelementname]. Explanation: the predicted failure for drive 13 no longer exists. May also be shown as 816f020d040dffff or 0x816f020d040dffff severity: info alert category: warning serviceable: n...

  • Page 863

    816f0308-0a01ffff [powersupplyelementname] has returned to a normal input state. Explanation: imm has detected that the input power for power supply 1 has returned to normal. May also be shown as 816f03080a01ffff or 0x816f03080a01ffff severity: info alert category: system serviceable: no cim informa...

  • Page 864

    816f030c-08810001 scrub failure for [physicalmemoryelementname] on subsystem [memoryelementname] has recovered. Explanation: memory test failure has been recovered in dimm 1 of mem card 1. May also be shown as 816f030c08810001 or 0x816f030c08810001 severity: info alert category: critical serviceable...

  • Page 865

    816f030c-08810004 scrub failure for [physicalmemoryelementname] on subsystem [memoryelementname] has recovered. Explanation: memory test failure has been recovered in dimm 4 of mem card 1. May also be shown as 816f030c08810004 or 0x816f030c08810004 severity: info alert category: critical serviceable...

  • Page 866

    816f030c-08810007 scrub failure for [physicalmemoryelementname] on subsystem [memoryelementname] has recovered. Explanation: memory test failure has been recovered in dimm 7 of mem card 1. May also be shown as 816f030c08810007 or 0x816f030c08810007 severity: info alert category: critical serviceable...

  • Page 867

    816f030c-08820003 scrub failure for [physicalmemoryelementname] on subsystem [memoryelementname] has recovered. Explanation: memory test failure has been recovered in dimm 3 of mem card 2. May also be shown as 816f030c08820003 or 0x816f030c08820003 severity: info alert category: critical serviceable...

  • Page 868

    816f030c-08820006 scrub failure for [physicalmemoryelementname] on subsystem [memoryelementname] has recovered. Explanation: memory test failure has been recovered in dimm 6 of mem card 2. May also be shown as 816f030c08820006 or 0x816f030c08820006 severity: info alert category: critical serviceable...

  • Page 869

    816f030c-08830001 scrub failure for [physicalmemoryelementname] on subsystem [memoryelementname] has recovered. Explanation: memory test failure has been recovered in dimm 1 of mem card 3. May also be shown as 816f030c08830001 or 0x816f030c08830001 severity: info alert category: critical serviceable...

  • Page 870

    816f030c-08830004 scrub failure for [physicalmemoryelementname] on subsystem [memoryelementname] has recovered. Explanation: memory test failure has been recovered in dimm 4 of mem card 3. May also be shown as 816f030c08830004 or 0x816f030c08830004 severity: info alert category: critical serviceable...

  • Page 871

    816f030c-08830007 scrub failure for [physicalmemoryelementname] on subsystem [memoryelementname] has recovered. Explanation: memory test failure has been recovered in dimm 7 of mem card 3. May also be shown as 816f030c08830007 or 0x816f030c08830007 severity: info alert category: critical serviceable...

  • Page 872

    816f030c-08840002 scrub failure for [physicalmemoryelementname] on subsystem [memoryelementname] has recovered. Explanation: memory test failure has been recovered in dimm 2 of mem card 4. May also be shown as 816f030c08840002 or 0x816f030c08840002 severity: info alert category: critical serviceable...

  • Page 873

    816f030c-08840005 scrub failure for [physicalmemoryelementname] on subsystem [memoryelementname] has recovered. Explanation: memory test failure has been recovered in dimm 5 of mem card 4. May also be shown as 816f030c08840005 or 0x816f030c08840005 severity: info alert category: critical serviceable...

  • Page 874

    816f030c-08840008 scrub failure for [physicalmemoryelementname] on subsystem [memoryelementname] has recovered. Explanation: memory test failure has been recovered in dimm 8 of mem card 4. May also be shown as 816f030c08840008 or 0x816f030c08840008 severity: info alert category: critical serviceable...

  • Page 875

    816f030c-08850003 scrub failure for [physicalmemoryelementname] on subsystem [memoryelementname] has recovered. Explanation: memory test failure has been recovered in dimm 3 of mem card 5. May also be shown as 816f030c08850003 or 0x816f030c08850003 severity: info alert category: critical serviceable...

  • Page 876

    816f030c-08850006 scrub failure for [physicalmemoryelementname] on subsystem [memoryelementname] has recovered. Explanation: memory test failure has been recovered in dimm 6 of mem card 5. May also be shown as 816f030c08850006 or 0x816f030c08850006 severity: info alert category: critical serviceable...

  • Page 877

    816f030c-08860001 scrub failure for [physicalmemoryelementname] on subsystem [memoryelementname] has recovered. Explanation: memory test failure has been recovered in dimm 1 of mem card 6. May also be shown as 816f030c08860001 or 0x816f030c08860001 severity: info alert category: critical serviceable...

  • Page 878

    816f030c-08860004 scrub failure for [physicalmemoryelementname] on subsystem [memoryelementname] has recovered. Explanation: memory test failure has been recovered in dimm 4 of mem card 6. May also be shown as 816f030c08860004 or 0x816f030c08860004 severity: info alert category: critical serviceable...

  • Page 879

    816f030c-08860007 scrub failure for [physicalmemoryelementname] on subsystem [memoryelementname] has recovered. Explanation: memory test failure has been recovered in dimm 7 of mem card 6. May also be shown as 816f030c08860007 or 0x816f030c08860007 severity: info alert category: critical serviceable...

  • Page 880

    816f030c-08870002 scrub failure for [physicalmemoryelementname] on subsystem [memoryelementname] has recovered. Explanation: memory test failure has been recovered in dimm 2 of mem card 7. May also be shown as 816f030c08870002 or 0x816f030c08870002 severity: info alert category: critical serviceable...

  • Page 881

    816f030c-08870005 scrub failure for [physicalmemoryelementname] on subsystem [memoryelementname] has recovered. Explanation: memory test failure has been recovered in dimm 5 of mem card 7. May also be shown as 816f030c08870005 or 0x816f030c08870005 severity: info alert category: critical serviceable...

  • Page 882

    816f030c-08870008 scrub failure for [physicalmemoryelementname] on subsystem [memoryelementname] has recovered. Explanation: memory test failure has been recovered in dimm 8 of mem card 7. May also be shown as 816f030c08870008 or 0x816f030c08870008 severity: info alert category: critical serviceable...

  • Page 883

    816f030c-08880003 scrub failure for [physicalmemoryelementname] on subsystem [memoryelementname] has recovered. Explanation: memory test failure has been recovered in dimm 3 of mem card 8. May also be shown as 816f030c08880003 or 0x816f030c08880003 severity: info alert category: critical serviceable...

  • Page 884

    816f030c-08880006 scrub failure for [physicalmemoryelementname] on subsystem [memoryelementname] has recovered. Explanation: memory test failure has been recovered in dimm 6 of mem card 8. May also be shown as 816f030c08880006 or 0x816f030c08880006 severity: info alert category: critical serviceable...

  • Page 885

    816f030c-088810008 scrub failure for [physicalmemoryelementname] on subsystem [memoryelementname] has recovered. Explanation: memory test failure has been recovered in dimm 8 of mem card 1. May also be shown as 816f030c088810008 or 0x816f030c088810008 severity: info alert category: critical servicea...

  • Page 886

    816f030c-18810003 scrub failure for [physicalmemoryelementname] on subsystem [memoryelementname] has recovered. Explanation: memory test failure has been recovered in dimm 3 of memory expansion module(meu). May also be shown as 816f030c18810003 or 0x816f030c18810003 severity: info alert category: cr...

  • Page 887

    816f030c-18810006 scrub failure for [physicalmemoryelementname] on subsystem [memoryelementname] has recovered. Explanation: memory test failure has been recovered in dimm 6 of memory expansion module(meu). May also be shown as 816f030c18810006 or 0x816f030c18810006 severity: info alert category: cr...

  • Page 888

    816f030c-18810009 scrub failure for [physicalmemoryelementname] on subsystem [memoryelementname] has recovered. Explanation: memory test failure has been recovered in dimm 9 of memory expansion module(meu). May also be shown as 816f030c18810009 or 0x816f030c18810009 severity: info alert category: cr...

  • Page 889

    816f030c-1881000c scrub failure for [physicalmemoryelementname] on subsystem [memoryelementname] has recovered. Explanation: memory test failure has been recovered in dimm 12 of memory expansion module(meu). May also be shown as 816f030c1881000c or 0x816f030c1881000c severity: info alert category: c...

  • Page 890

    816f030c-1881000f scrub failure for [physicalmemoryelementname] on subsystem [memoryelementname] has recovered. Explanation: memory test failure has been recovered in dimm 15 of memory expansion module(meu). May also be shown as 816f030c1881000f or 0x816f030c1881000f severity: info alert category: c...

  • Page 891

    816f030c-18810012 scrub failure for [physicalmemoryelementname] on subsystem [memoryelementname] has recovered. Explanation: memory test failure has been recovered in dimm 18 of memory expansion module(meu). May also be shown as 816f030c18810012 or 0x816f030c18810012 severity: info alert category: c...

  • Page 892

    816f030c-18810015 scrub failure for [physicalmemoryelementname] on subsystem [memoryelementname] has recovered. Explanation: memory test failure has been recovered in dimm 21 of memory expansion module(meu). May also be shown as 816f030c18810015 or 0x816f030c18810015 severity: info alert category: c...

  • Page 893

    816f030c-18810018 scrub failure for [physicalmemoryelementname] on subsystem [memoryelementname] has recovered. Explanation: memory test failure has been recovered in dimm 24 of memory expansion module(meu). May also be shown as 816f030c18810018 or 0x816f030c18810018 severity: info alert category: c...

  • Page 894

    816f030c-1881001b scrub failure for [physicalmemoryelementname] on subsystem [memoryelementname] has recovered. Explanation: memory test failure has been recovered in dimm 27 of memory expansion module(meu). May also be shown as 816f030c1881001b or 0x816f030c1881001b severity: info alert category: c...

  • Page 895

    816f030c-1881001e scrub failure for [physicalmemoryelementname] on subsystem [memoryelementname] has recovered. Explanation: memory test failure has been recovered in dimm 30 of memory expansion module(meu). May also be shown as 816f030c1881001e or 0x816f030c1881001e severity: info alert category: c...

  • Page 896

    816f030c-2581ffff scrub failure for [physicalmemoryelementname] on subsystem [memoryelementname]has recovered. Explanation: a dimm has recovered from a memory test failure. May also be shown as 816f030c2581ffff or 0x816f030c2581ffff severity: info alert category: critical serviceable: no cim informa...

  • Page 897

    816f040c-08810001 [physicalmemoryelementname] disabled on subsystem [memoryelementname]. Explanation: dimm 1 in mem card 1 has been enabled. May also be shown as 816f040c08810001 or 0x816f040c08810001 severity: info alert category: system serviceable: no cim information: prefix: plat and id: 0130 sn...

  • Page 898

    816f040c-08810004 [physicalmemoryelementname] disabled on subsystem [memoryelementname]. Explanation: dimm 4 in mem card 1 has been enabled. May also be shown as 816f040c08810004 or 0x816f040c08810004 severity: info alert category: system serviceable: no cim information: prefix: plat and id: 0130 sn...

  • Page 899

    816f040c-08810007 [physicalmemoryelementname] disabled on subsystem [memoryelementname]. Explanation: dimm 7 in mem card 1 has been enabled. May also be shown as 816f040c08810007 or 0x816f040c08810007 severity: info alert category: system serviceable: no cim information: prefix: plat and id: 0130 sn...

  • Page 900

    816f040c-08820002 [physicalmemoryelementname] disabled on subsystem [memoryelementname]. Explanation: dimm 2 in mem card 2 has been enabled. May also be shown as 816f040c08820002 or 0x816f040c08820002 severity: info alert category: system serviceable: no cim information: prefix: plat and id: 0130 sn...

  • Page 901

    816f040c-08820005 [physicalmemoryelementname] disabled on subsystem [memoryelementname]. Explanation: dimm 5 in mem card 2 has been enabled. May also be shown as 816f040c08820005 or 0x816f040c08820005 severity: info alert category: system serviceable: no cim information: prefix: plat and id: 0130 sn...

  • Page 902

    816f040c-08820008 [physicalmemoryelementname] disabled on subsystem [memoryelementname]. Explanation: dimm 8 in mem card 2 has been enabled. May also be shown as 816f040c08820008 or 0x816f040c08820008 severity: info alert category: system serviceable: no cim information: prefix: plat and id: 0130 sn...

  • Page 903

    816f040c-08830003 [physicalmemoryelementname] disabled on subsystem [memoryelementname]. Explanation: dimm 3 in mem card 3 has been enabled. May also be shown as 816f040c08830003 or 0x816f040c08830003 severity: info alert category: system serviceable: no cim information: prefix: plat and id: 0130 sn...

  • Page 904

    816f040c-08830006 [physicalmemoryelementname] disabled on subsystem [memoryelementname]. Explanation: dimm 6 in mem card 3 has been enabled. May also be shown as 816f040c08830006 or 0x816f040c08830006 severity: info alert category: system serviceable: no cim information: prefix: plat and id: 0130 sn...

  • Page 905

    816f040c-08840001 [physicalmemoryelementname] disabled on subsystem [memoryelementname]. Explanation: dimm 1 in mem card 4 has been enabled. May also be shown as 816f040c08840001 or 0x816f040c08840001 severity: info alert category: system serviceable: no cim information: prefix: plat and id: 0130 sn...

  • Page 906

    816f040c-08840004 [physicalmemoryelementname] disabled on subsystem [memoryelementname]. Explanation: dimm 4 in mem card 4 has been enabled. May also be shown as 816f040c08840004 or 0x816f040c08840004 severity: info alert category: system serviceable: no cim information: prefix: plat and id: 0130 sn...

  • Page 907

    816f040c-08840007 [physicalmemoryelementname] disabled on subsystem [memoryelementname]. Explanation: dimm 7 in mem card 4 has been enabled. May also be shown as 816f040c08840007 or 0x816f040c08840007 severity: info alert category: system serviceable: no cim information: prefix: plat and id: 0130 sn...

  • Page 908

    816f040c-08850002 [physicalmemoryelementname] disabled on subsystem [memoryelementname]. Explanation: dimm 2 in mem card 5 has been enabled. May also be shown as 816f040c08850002 or 0x816f040c08850002 severity: info alert category: system serviceable: no cim information: prefix: plat and id: 0130 sn...

  • Page 909

    816f040c-08850005 [physicalmemoryelementname] disabled on subsystem [memoryelementname]. Explanation: dimm 5 in mem card 5 has been enabled. May also be shown as 816f040c08850005 or 0x816f040c08850005 severity: info alert category: system serviceable: no cim information: prefix: plat and id: 0130 sn...

  • Page 910

    816f040c-08850008 [physicalmemoryelementname] disabled on subsystem [memoryelementname]. Explanation: dimm 8 in mem card 5 has been enabled. May also be shown as 816f040c08850008 or 0x816f040c08850008 severity: info alert category: system serviceable: no cim information: prefix: plat and id: 0130 sn...

  • Page 911

    816f040c-08860003 [physicalmemoryelementname] disabled on subsystem [memoryelementname]. Explanation: dimm 3 in mem card 6 has been enabled. May also be shown as 816f040c08860003 or 0x816f040c08860003 severity: info alert category: system serviceable: no cim information: prefix: plat and id: 0130 sn...

  • Page 912

    816f040c-08860006 [physicalmemoryelementname] disabled on subsystem [memoryelementname]. Explanation: dimm 6 in mem card 6 has been enabled. May also be shown as 816f040c08860006 or 0x816f040c08860006 severity: info alert category: system serviceable: no cim information: prefix: plat and id: 0130 sn...

  • Page 913

    816f040c-08870001 [physicalmemoryelementname] disabled on subsystem [memoryelementname]. Explanation: dimm 1 in mem card 7 has been enabled. May also be shown as 816f040c08870001 or 0x816f040c08870001 severity: info alert category: system serviceable: no cim information: prefix: plat and id: 0130 sn...

  • Page 914

    816f040c-08870004 [physicalmemoryelementname] disabled on subsystem [memoryelementname]. Explanation: dimm 4 in mem card 7 has been enabled. May also be shown as 816f040c08870004 or 0x816f040c08870004 severity: info alert category: system serviceable: no cim information: prefix: plat and id: 0130 sn...

  • Page 915

    816f040c-08870007 [physicalmemoryelementname] disabled on subsystem [memoryelementname]. Explanation: dimm 7 in mem card 7 has been enabled. May also be shown as 816f040c08870007 or 0x816f040c08870007 severity: info alert category: system serviceable: no cim information: prefix: plat and id: 0130 sn...

  • Page 916

    816f040c-08880002 [physicalmemoryelementname] disabled on subsystem [memoryelementname]. Explanation: dimm 2 in mem card 8 has been enabled. May also be shown as 816f040c08880002 or 0x816f040c08880002 severity: info alert category: system serviceable: no cim information: prefix: plat and id: 0130 sn...

  • Page 917

    816f040c-08880005 [physicalmemoryelementname] disabled on subsystem [memoryelementname]. Explanation: dimm 5 in mem card 8 has been enabled. May also be shown as 816f040c08880005 or 0x816f040c08880005 severity: info alert category: system serviceable: no cim information: prefix: plat and id: 0130 sn...

  • Page 918

    816f040c-08880008 [physicalmemoryelementname] disabled on subsystem [memoryelementname]. Explanation: dimm 8 in mem card 8 has been enabled. May also be shown as 816f040c08880008 or 0x816f040c08880008 severity: info alert category: system serviceable: no cim information: prefix: plat and id: 0130 sn...

  • Page 919

    816f040c-18810003 [physicalmemoryelementname] disabled on subsystem [memoryelementname]. Explanation: dimm 3 in memory expansion module(meu) has been enabled. May also be shown as 816f040c18810003 or 0x816f040c18810003 severity: info alert category: system serviceable: no cim information: prefix: pl...

  • Page 920

    816f040c-18810006 [physicalmemoryelementname] disabled on subsystem [memoryelementname]. Explanation: dimm 6 in memory expansion module(meu) has been enabled. May also be shown as 816f040c18810006 or 0x816f040c18810006 severity: info alert category: system serviceable: no cim information: prefix: pl...

  • Page 921

    816f040c-18810009 [physicalmemoryelementname] disabled on subsystem [memoryelementname]. Explanation: dimm 9 in memory expansion module(meu) has been enabled. May also be shown as 816f040c18810009 or 0x816f040c18810009 severity: info alert category: system serviceable: no cim information: prefix: pl...

  • Page 922

    816f040c-1881000c [physicalmemoryelementname] disabled on subsystem [memoryelementname]. Explanation: dimm 12 in memory expansion module(meu) has been enabled. May also be shown as 816f040c1881000c or 0x816f040c1881000c severity: info alert category: system serviceable: no cim information: prefix: p...

  • Page 923

    816f040c-1881000f [physicalmemoryelementname] disabled on subsystem [memoryelementname]. Explanation: dimm 15 in memory expansion module(meu) has been enabled. May also be shown as 816f040c1881000f or 0x816f040c1881000f severity: info alert category: system serviceable: no cim information: prefix: p...

  • Page 924

    816f040c-18810012 [physicalmemoryelementname] disabled on subsystem [memoryelementname]. Explanation: dimm 18 in memory expansion module(meu) has been enabled. May also be shown as 816f040c18810012 or 0x816f040c18810012 severity: info alert category: system serviceable: no cim information: prefix: p...

  • Page 925

    816f040c-18810015 [physicalmemoryelementname] disabled on subsystem [memoryelementname]. Explanation: dimm 21 in memory expansion module(meu) has been enabled. May also be shown as 816f040c18810015 or 0x816f040c18810015 severity: info alert category: system serviceable: no cim information: prefix: p...

  • Page 926

    816f040c-18810018 [physicalmemoryelementname] disabled on subsystem [memoryelementname]. Explanation: dimm 24 in memory expansion module(meu) has been enabled. May also be shown as 816f040c18810018 or 0x816f040c18810018 severity: info alert category: system serviceable: no cim information: prefix: p...

  • Page 927

    816f040c-1881001b [physicalmemoryelementname] disabled on subsystem [memoryelementname]. Explanation: dimm 27 in memory expansion module(meu) has been enabled. May also be shown as 816f040c1881001b or 0x816f040c1881001b severity: info alert category: system serviceable: no cim information: prefix: p...

  • Page 928

    816f040c-1881001e [physicalmemoryelementname] disabled on subsystem [memoryelementname]. Explanation: dimm 30 in memory expansion module(meu) has been enabled. May also be shown as 816f040c1881001e or 0x816f040c1881001e severity: info alert category: system serviceable: no cim information: prefix: p...

  • Page 929

    816f040c-2581ffff [physicalmemoryelementname] enabled on subsystem [memoryelementname]. Explanation: a dimm has been enabled. May also be shown as 816f040c2581ffff or 0x816f040c2581ffff severity: info alert category: system serviceable: no cim information: prefix: plat and id: 0130 snmp trap id: aut...

  • Page 930

    816f0507-0303ffff [processorelementname] has recovered from a configuration mismatch. Explanation: processor 3 has recovered from a processor configuration mismatch. May also be shown as 816f05070303ffff or 0x816f05070303ffff severity: info alert category: critical serviceable: no cim information: p...

  • Page 931

    816f050c-08810001 memory logging limit removed for [physicalmemoryelementname] on subsystem [memoryelementname]. Explanation: dimm 1 of mem card 1 memory logging limit has been removed. May also be shown as 816f050c08810001 or 0x816f050c08810001 severity: info alert category: warning serviceable: no...

  • Page 932

    816f050c-08810004 memory logging limit removed for [physicalmemoryelementname] on subsystem [memoryelementname]. Explanation: dimm 4 of mem card 1 memory logging limit has been removed. May also be shown as 816f050c08810004 or 0x816f050c08810004 severity: info alert category: warning serviceable: no...

  • Page 933

    816f050c-08810007 memory logging limit removed for [physicalmemoryelementname] on subsystem [memoryelementname]. Explanation: dimm 7 of mem card 1 memory logging limit has been removed. May also be shown as 816f050c08810007 or 0x816f050c08810007 severity: info alert category: warning serviceable: no...

  • Page 934

    816f050c-08820002 memory logging limit removed for [physicalmemoryelementname] on subsystem [memoryelementname]. Explanation: dimm 2 of mem card 2 memory logging limit has been removed. May also be shown as 816f050c08820002 or 0x816f050c08820002 severity: info alert category: warning serviceable: no...

  • Page 935

    816f050c-08820005 memory logging limit removed for [physicalmemoryelementname] on subsystem [memoryelementname]. Explanation: dimm 5 of mem card 2 memory logging limit has been removed. May also be shown as 816f050c08820005 or 0x816f050c08820005 severity: info alert category: warning serviceable: no...

  • Page 936

    816f050c-08820008 memory logging limit removed for [physicalmemoryelementname] on subsystem [memoryelementname]. Explanation: dimm 8 of mem card 2 memory logging limit has been removed. May also be shown as 816f050c08820008 or 0x816f050c08820008 severity: info alert category: warning serviceable: no...

  • Page 937

    816f050c-08830003 memory logging limit removed for [physicalmemoryelementname] on subsystem [memoryelementname]. Explanation: dimm 3 of mem card 3 memory logging limit has been removed. May also be shown as 816f050c08830003 or 0x816f050c08830003 severity: info alert category: warning serviceable: no...

  • Page 938

    816f050c-08830006 memory logging limit removed for [physicalmemoryelementname] on subsystem [memoryelementname]. Explanation: dimm 6 of mem card 3 memory logging limit has been removed. May also be shown as 816f050c08830006 or 0x816f050c08830006 severity: info alert category: warning serviceable: no...

  • Page 939

    816f050c-08840001 memory logging limit removed for [physicalmemoryelementname] on subsystem [memoryelementname]. Explanation: dimm 1 of mem card 4 memory logging limit has been removed. May also be shown as 816f050c08840001 or 0x816f050c08840001 severity: info alert category: warning serviceable: no...

  • Page 940

    816f050c-08840004 memory logging limit removed for [physicalmemoryelementname] on subsystem [memoryelementname]. Explanation: dimm 4 of mem card 4 memory logging limit has been removed. May also be shown as 816f050c08840004 or 0x816f050c08840004 severity: info alert category: warning serviceable: no...

  • Page 941

    816f050c-08840007 memory logging limit removed for [physicalmemoryelementname] on subsystem [memoryelementname]. Explanation: dimm 7 of mem card 4 memory logging limit has been removed. May also be shown as 816f050c08840007 or 0x816f050c08840007 severity: info alert category: warning serviceable: no...

  • Page 942

    816f050c-08850002 memory logging limit removed for [physicalmemoryelementname] on subsystem [memoryelementname]. Explanation: dimm 2 of mem card 5 memory logging limit has been removed. May also be shown as 816f050c08850002 or 0x816f050c08850002 severity: info alert category: warning serviceable: no...

  • Page 943

    816f050c-08850005 memory logging limit removed for [physicalmemoryelementname] on subsystem [memoryelementname]. Explanation: dimm 5 of mem card 5 memory logging limit has been removed. May also be shown as 816f050c08850005 or 0x816f050c08850005 severity: info alert category: warning serviceable: no...

  • Page 944

    816f050c-08850008 memory logging limit removed for [physicalmemoryelementname] on subsystem [memoryelementname]. Explanation: dimm 8 of mem card 5 memory logging limit has been removed. May also be shown as 816f050c08850008 or 0x816f050c08850008 severity: info alert category: warning serviceable: no...

  • Page 945

    816f050c-08860003 memory logging limit removed for [physicalmemoryelementname] on subsystem [memoryelementname]. Explanation: dimm 3 of mem card 6 memory logging limit has been removed. May also be shown as 816f050c08860003 or 0x816f050c08860003 severity: info alert category: warning serviceable: no...

  • Page 946

    816f050c-08860006 memory logging limit removed for [physicalmemoryelementname] on subsystem [memoryelementname]. Explanation: dimm 6 of mem card 6 memory logging limit has been removed. May also be shown as 816f050c08860006 or 0x816f050c08860006 severity: info alert category: warning serviceable: no...

  • Page 947

    816f050c-08870001 memory logging limit removed for [physicalmemoryelementname] on subsystem [memoryelementname]. Explanation: dimm 1 of mem card 7 memory logging limit has been removed. May also be shown as 816f050c08870001 or 0x816f050c08870001 severity: info alert category: warning serviceable: no...

  • Page 948

    816f050c-08870004 memory logging limit removed for [physicalmemoryelementname] on subsystem [memoryelementname]. Explanation: dimm 4 of mem card 7 memory logging limit has been removed. May also be shown as 816f050c08870004 or 0x816f050c08870004 severity: info alert category: warning serviceable: no...

  • Page 949

    816f050c-08870007 memory logging limit removed for [physicalmemoryelementname] on subsystem [memoryelementname]. Explanation: dimm 7 of mem card 7 memory logging limit has been removed. May also be shown as 816f050c08870007 or 0x816f050c08870007 severity: info alert category: warning serviceable: no...

  • Page 950

    816f050c-08880002 memory logging limit removed for [physicalmemoryelementname] on subsystem [memoryelementname]. Explanation: dimm 2 of mem card 8 memory logging limit has been removed. May also be shown as 816f050c08880002 or 0x816f050c08880002 severity: info alert category: warning serviceable: no...

  • Page 951

    816f050c-08880005 memory logging limit removed for [physicalmemoryelementname] on subsystem [memoryelementname]. Explanation: dimm 5 of mem card 8 memory logging limit has been removed. May also be shown as 816f050c08880005 or 0x816f050c08880005 severity: info alert category: warning serviceable: no...

  • Page 952

    816f050c-08880008 memory logging limit removed for [physicalmemoryelementname] on subsystem [memoryelementname]. Explanation: dimm 8 of mem card 8 memory logging limit has been removed. May also be shown as 816f050c08880008 or 0x816f050c08880008 severity: info alert category: warning serviceable: no...

  • Page 953

    816f050c-18810003 memory logging limit removed for [physicalmemoryelementname] on subsystem [memoryelementname]. Explanation: dimm 3 of meu memory logging limit has been removed. May also be shown as 816f050c18810003 or 0x816f050c18810003 severity: info alert category: warning serviceable: no cim in...

  • Page 954

    816f050c-18810006 memory logging limit removed for [physicalmemoryelementname] on subsystem [memoryelementname]. Explanation: dimm 6 of meu memory logging limit has been removed. May also be shown as 816f050c18810006 or 0x816f050c18810006 severity: info alert category: warning serviceable: no cim in...

  • Page 955

    816f050c-18810009 memory logging limit removed for [physicalmemoryelementname] on subsystem [memoryelementname]. Explanation: dimm 9 of meu memory logging limit has been removed. May also be shown as 816f050c18810009 or 0x816f050c18810009 severity: info alert category: warning serviceable: no cim in...

  • Page 956

    816f050c-1881000c memory logging limit removed for [physicalmemoryelementname] on subsystem [memoryelementname]. Explanation: dimm 12 of meu memory logging limit has been removed. May also be shown as 816f050c1881000c or 0x816f050c1881000c severity: info alert category: warning serviceable: no cim i...

  • Page 957

    816f050c-1881000f memory logging limit removed for [physicalmemoryelementname] on subsystem [memoryelementname]. Explanation: dimm 15 of meu memory logging limit has been removed. May also be shown as 816f050c1881000f or 0x816f050c1881000f severity: info alert category: warning serviceable: no cim i...

  • Page 958

    816f050c-18810012 memory logging limit removed for [physicalmemoryelementname] on subsystem [memoryelementname]. Explanation: dimm 18 of meu memory logging limit has been removed. May also be shown as 816f050c18810012 or 0x816f050c18810012 severity: info alert category: warning serviceable: no cim i...

  • Page 959

    816f050c-18810015 memory logging limit removed for [physicalmemoryelementname] on subsystem [memoryelementname]. Explanation: dimm 21 of meu memory logging limit has been removed. May also be shown as 816f050c18810015 or 0x816f050c18810015 severity: info alert category: warning serviceable: no cim i...

  • Page 960

    816f050c-18810018 memory logging limit removed for [physicalmemoryelementname] on subsystem [memoryelementname]. Explanation: dimm 24 of meu memory logging limit has been removed. May also be shown as 816f050c18810018 or 0x816f050c18810018 severity: info alert category: warning serviceable: no cim i...

  • Page 961

    816f050c-1881001b memory logging limit removed for [physicalmemoryelementname] on subsystem [memoryelementname]. Explanation: dimm 27 of meu memory logging limit has been removed. May also be shown as 816f050c1881001b or 0x816f050c1881001b severity: info alert category: warning serviceable: no cim i...

  • Page 962

    816f050c-1881001e memory logging limit removed for [physicalmemoryelementname] on subsystem [memoryelementname]. Explanation: dimm 30 of meu memory logging limit has been removed. May also be shown as 816f050c1881001e or 0x816f050c1881001e severity: info alert category: warning serviceable: no cim i...

  • Page 963

    816f050c-2581ffff memory logging limit removed for [physicalmemoryelementname] on subsystem [memoryelementname]. Explanation: memory logging limit has been removed. May also be shown as 816f050c2581ffff or 0x816f050c2581ffff severity: info alert category: warning serviceable: no cim information: pre...

  • Page 964

    816f050d-0402ffff critical array [computersystemelementname] has deasserted. Explanation: the raid array is no longer in a critical condition. May also be shown as 816f050d0402ffff or 0x816f050d0402ffff severity: info alert category: critical serviceable: no cim information: prefix: plat and id: 017...

  • Page 965

    816f050d-0405ffff critical array [computersystemelementname] has deasserted. Explanation: the raid array is no longer in a critical condition. May also be shown as 816f050d0405ffff or 0x816f050d0405ffff severity: info alert category: critical serviceable: no cim information: prefix: plat and id: 017...

  • Page 966

    816f050d-0408ffff critical array [computersystemelementname] has deasserted. Explanation: the raid array is no longer in a critical condition. May also be shown as 816f050d0408ffff or 0x816f050d0408ffff severity: info alert category: critical serviceable: no cim information: prefix: plat and id: 017...

  • Page 967

    816f050d-040bffff critical array [computersystemelementname] has deasserted. Explanation: the raid array is no longer in a critical condition. May also be shown as 816f050d040bffff or 0x816f050d040bffff severity: info alert category: critical serviceable: no cim information: prefix: plat and id: 017...

  • Page 968

    816f050d-040effff critical array [computersystemelementname] has deasserted. Explanation: the raid array is no longer in a critical condition. May also be shown as 816f050d040effff or 0x816f050d040effff severity: info alert category: critical serviceable: no cim information: prefix: plat and id: 017...

  • Page 969

    816f0607-0302ffff an sm bios uncorrectable cpu complex error for [processorelementname] has deasserted. Explanation: an sm bios uncorrectable cpu complex error has been deasserted for microprocessor 2. May also be shown as 816f06070302ffff or 0x816f06070302ffff severity: info alert category: critica...

  • Page 970

    816f060d-0400ffff array in system [computersystemelementname] has been restored. Explanation: imm has detected that a failed array has been restored. May also be shown as 816f060d0400ffff or 0x816f060d0400ffff severity: info alert category: critical serviceable: no cim information: prefix: plat and ...

  • Page 971

    816f060d-0403ffff array in system [computersystemelementname] has been restored. Explanation: imm has detected that a failed array has been restored. May also be shown as 816f060d0403ffff or 0x816f060d0403ffff severity: info alert category: critical serviceable: no cim information: prefix: plat and ...

  • Page 972

    816f060d-0406ffff array in system [computersystemelementname] has been restored. Explanation: imm has detected that a failed array has been restored. May also be shown as 816f060d0406ffff or 0x816f060d0406ffff severity: info alert category: critical serviceable: no cim information: prefix: plat and ...

  • Page 973

    816f060d-0409ffff array in system [computersystemelementname] has been restored. Explanation: imm has detected that a failed array has been restored. May also be shown as 816f060d0409ffff or 0x816f060d0409ffff severity: info alert category: critical serviceable: no cim information: prefix: plat and ...

  • Page 974

    816f060d-040cffff array in system [computersystemelementname] has been restored. Explanation: imm has detected that a failed array has been restored. May also be shown as 816f060d040cffff or 0x816f060d040cffff severity: info alert category: critical serviceable: no cim information: prefix: plat and ...

  • Page 975

    816f060d-040fffff array in system [computersystemelementname] has been restored. Explanation: imm has detected that a failed array has been restored. May also be shown as 816f060d040fffff or 0x816f060d040fffff severity: info alert category: critical serviceable: no cim information: prefix: plat and ...

  • Page 976

    816f070c-08810003 configuration error for [physicalmemoryelementname] on subsystem [memoryelementname] has been deasserted. Explanation: a memory configuration error has been deasserted on dimm 3 of mem card 1. May also be shown as 816f070c08810003 or 0x816f070c08810003 severity: info alert category...

  • Page 977

    816f070c-08810006 configuration error for [physicalmemoryelementname] on subsystem [memoryelementname] has been deasserted. Explanation: a memory configuration error has been deasserted on dimm 6 of mem card 1. May also be shown as 816f070c08810006 or 0x816f070c08810006 severity: info alert category...

  • Page 978

    816f070c-08820001 configuration error for [physicalmemoryelementname] on subsystem [memoryelementname] has been deasserted. Explanation: a memory configuration error has been deasserted on dimm 1 of mem card 2. May also be shown as 816f070c08820001 or 0x816f070c08820001 severity: info alert category...

  • Page 979

    816f070c-08820004 configuration error for [physicalmemoryelementname] on subsystem [memoryelementname] has been deasserted. Explanation: a memory configuration error has been deasserted on dimm 4 of mem card 2. May also be shown as 816f070c08820004 or 0x816f070c08820004 severity: info alert category...

  • Page 980

    816f070c-08820007 configuration error for [physicalmemoryelementname] on subsystem [memoryelementname] has been deasserted. Explanation: a memory configuration error has been deasserted on dimm 7 of mem card 2. May also be shown as 816f070c08820007 or 0x816f070c08820007 severity: info alert category...

  • Page 981

    816f070c-08830002 configuration error for [physicalmemoryelementname] on subsystem [memoryelementname] has been deasserted. Explanation: a memory configuration error has been deasserted on dimm 2 of mem card 3. May also be shown as 816f070c08830002 or 0x816f070c08830002 severity: info alert category...

  • Page 982

    816f070c-08830005 configuration error for [physicalmemoryelementname] on subsystem [memoryelementname] has been deasserted. Explanation: a memory configuration error has been deasserted on dimm 5 of mem card 3. May also be shown as 816f070c08830005 or 0x816f070c08830005 severity: info alert category...

  • Page 983

    816f070c-08830008 configuration error for [physicalmemoryelementname] on subsystem [memoryelementname] has been deasserted. Explanation: a memory configuration error has been deasserted on dimm 8 of mem card 3. May also be shown as 816f070c08830008 or 0x816f070c08830008 severity: info alert category...

  • Page 984

    816f070c-08840003 configuration error for [physicalmemoryelementname] on subsystem [memoryelementname] has been deasserted. Explanation: a memory configuration error has been deasserted on dimm 3 of mem card 4. May also be shown as 816f070c08840003 or 0x816f070c08840003 severity: info alert category...

  • Page 985

    816f070c-08840006 configuration error for [physicalmemoryelementname] on subsystem [memoryelementname] has been deasserted. Explanation: a memory configuration error has been deasserted on dimm 6 of mem card 4. May also be shown as 816f070c08840006 or 0x816f070c08840006 severity: info alert category...

  • Page 986

    816f070c-08850001 configuration error for [physicalmemoryelementname] on subsystem [memoryelementname] has been deasserted. Explanation: a memory configuration error has been deasserted on dimm 1 of mem card 5. May also be shown as 816f070c08850001 or 0x816f070c08850001 severity: info alert category...

  • Page 987

    816f070c-08850004 configuration error for [physicalmemoryelementname] on subsystem [memoryelementname] has been deasserted. Explanation: a memory configuration error has been deasserted on dimm 4 of mem card 5. May also be shown as 816f070c08850004 or 0x816f070c08850004 severity: info alert category...

  • Page 988

    816f070c-08850007 configuration error for [physicalmemoryelementname] on subsystem [memoryelementname] has been deasserted. Explanation: a memory configuration error has been deasserted on dimm 7 of mem card 5. May also be shown as 816f070c08850007 or 0x816f070c08850007 severity: info alert category...

  • Page 989

    816f070c-08860002 configuration error for [physicalmemoryelementname] on subsystem [memoryelementname] has been deasserted. Explanation: a memory configuration error has been deasserted on dimm 2 of mem card 6. May also be shown as 816f070c08860002 or 0x816f070c08860002 severity: info alert category...

  • Page 990

    816f070c-08860005 configuration error for [physicalmemoryelementname] on subsystem [memoryelementname] has been deasserted. Explanation: a memory configuration error has been deasserted on dimm 5 of mem card 6. May also be shown as 816f070c08860005 or 0x816f070c08860005 severity: info alert category...

  • Page 991

    816f070c-08860008 configuration error for [physicalmemoryelementname] on subsystem [memoryelementname] has been deasserted. Explanation: a memory configuration error has been deasserted on dimm 8 of mem card 6. May also be shown as 816f070c08860008 or 0x816f070c08860008 severity: info alert category...

  • Page 992

    816f070c-08870003 configuration error for [physicalmemoryelementname] on subsystem [memoryelementname] has been deasserted. Explanation: a memory configuration error has been deasserted on dimm 3 of mem card 7. May also be shown as 816f070c08870003 or 0x816f070c08870003 severity: info alert category...

  • Page 993

    816f070c-08870006 configuration error for [physicalmemoryelementname] on subsystem [memoryelementname] has been deasserted. Explanation: a memory configuration error has been deasserted on dimm 6 of mem card 7. May also be shown as 816f070c08870006 or 0x816f070c08870006 severity: info alert category...

  • Page 994

    816f070c-08880001 configuration error for [physicalmemoryelementname] on subsystem [memoryelementname] has been deasserted. Explanation: a memory configuration error has been deasserted on dimm 1 of mem card 8. May also be shown as 816f070c08880001 or 0x816f070c08880001 severity: info alert category...

  • Page 995

    816f070c-08880004 configuration error for [physicalmemoryelementname] on subsystem [memoryelementname] has been deasserted. Explanation: a memory configuration error has been deasserted on dimm 4 of mem card 8. May also be shown as 816f070c08880004 or 0x816f070c08880004 severity: info alert category...

  • Page 996

    816f070c-08880007 configuration error for [physicalmemoryelementname] on subsystem [memoryelementname] has been deasserted. Explanation: a memory configuration error has been deasserted on dimm 7 of mem card 8. May also be shown as 816f070c08880007 or 0x816f070c08880007 severity: info alert category...

  • Page 997

    816f070c-18810002 configuration error for [physicalmemoryelementname] on subsystem [memoryelementname] has been deasserted. Explanation: a memory configuration error has been deasserted on dimm 2 of memory expansion unit(meu). May also be shown as 816f070c18810002 or 0x816f070c18810002 severity: inf...

  • Page 998

    816f070c-18810005 configuration error for [physicalmemoryelementname] on subsystem [memoryelementname] has been deasserted. Explanation: a memory configuration error has been deasserted on dimm 5 of memory expansion unit(meu). May also be shown as 816f070c18810005 or 0x816f070c18810005 severity: inf...

  • Page 999

    816f070c-18810008 configuration error for [physicalmemoryelementname] on subsystem [memoryelementname] has been deasserted. Explanation: a memory configuration error has been deasserted on dimm 8 of memory expansion unit(meu). May also be shown as 816f070c18810008 or 0x816f070c18810008 severity: inf...

  • Page 1000

    816f070c-1881000b configuration error for [physicalmemoryelementname] on subsystem [memoryelementname] has been deasserted. Explanation: a memory configuration error has been deasserted on dimm 11 of memory expansion unit(meu). May also be shown as 816f070c1881000b or 0x816f070c1881000b severity: in...

  • Page 1001

    816f070c-1881000e configuration error for [physicalmemoryelementname] on subsystem [memoryelementname] has been deasserted. Explanation: a memory configuration error has been deasserted on dimm 14 of memory expansion unit(meu). May also be shown as 816f070c1881000e or 0x816f070c1881000e severity: in...

  • Page 1002

    816f070c-18810011 configuration error for [physicalmemoryelementname] on subsystem [memoryelementname] has been deasserted. Explanation: a memory configuration error has been deasserted on dimm 17 of memory expansion unit(meu). May also be shown as 816f070c18810011 or 0x816f070c18810011 severity: in...

  • Page 1003

    816f070c-18810014 configuration error for [physicalmemoryelementname] on subsystem [memoryelementname] has been deasserted. Explanation: a memory configuration error has been deasserted on dimm 20 of memory expansion unit(meu). May also be shown as 816f070c18810014 or 0x816f070c18810014 severity: in...

  • Page 1004

    816f070c-18810017 configuration error for [physicalmemoryelementname] on subsystem [memoryelementname] has been deasserted. Explanation: a memory configuration error has been deasserted on dimm 23 of memory expansion unit(meu). May also be shown as 816f070c18810017 or 0x816f070c18810017 severity: in...

  • Page 1005

    816f070c-1881001a configuration error for [physicalmemoryelementname] on subsystem [memoryelementname] has been deasserted. Explanation: a memory configuration error has been deasserted on dimm 26 of memory expansion unit(meu). May also be shown as 816f070c1881001a or 0x816f070c1881001a severity: in...

  • Page 1006

    816f070c-1881001d configuration error for [physicalmemoryelementname] on subsystem [memoryelementname] has been deasserted. Explanation: a memory configuration error has been deasserted on dimm 29 of memory expansion unit(meu). May also be shown as 816f070c1881001d or 0x816f070c1881001d severity: in...

  • Page 1007

    816f070c-18810020 configuration error for [physicalmemoryelementname] on subsystem [memoryelementname] has been deasserted. Explanation: a memory configuration error has been deasserted on dimm 32 of memory expansion unit(meu). May also be shown as 816f070c18810020 or 0x816f070c18810020 severity: in...

  • Page 1008

    816f070c-2585ffff configuration error for [physicalmemoryelementname] on subsystem [memoryelementname]has deasserted. Explanation: a configuration error of missing boot memory has been deasserted. May also be shown as 816f070c2585ffff or 0x816f070c2585ffff severity: info alert category: critical ser...

  • Page 1009

    816f070c-2588ffff configuration error for [physicalmemoryelementname] on subsystem [memoryelementname]has deasserted. Explanation: a memory dimm configuration error in mem card 3 bank has deasserted. May also be shown as 816f070c2588ffff or 0x816f070c2588ffff severity: info alert category: critical ...

  • Page 1010

    816f070c-258bffff configuration error for [physicalmemoryelementname] on subsystem [memoryelementname]has deasserted. Explanation: a memory dimm configuration error in mem card 6 bank has deasserted. May also be shown as 816f070c258bffff or 0x816f070c258bffff severity: info alert category: critical ...

  • Page 1011

    816f070d-0400ffff rebuild completed for array in system [computersystemelementname]. Explanation: imm has detected that an array rebuild has completed. May also be shown as 816f070d0400ffff or 0x816f070d0400ffff severity: info alert category: system serviceable: no cim information: prefix: plat and ...

  • Page 1012

    816f070d-0403ffff rebuild completed for array in system [computersystemelementname]. Explanation: imm has detected that an array rebuild has completed. May also be shown as 816f070d0403ffff or 0x816f070d0403ffff severity: info alert category: system serviceable: no cim information: prefix: plat and ...

  • Page 1013

    816f070d-0406ffff rebuild completed for array in system [computersystemelementname]. Explanation: imm has detected that an array rebuild has completed. May also be shown as 816f070d0406ffff or 0x816f070d0406ffff severity: info alert category: system serviceable: no cim information: prefix: plat and ...

  • Page 1014

    816f070d-0409ffff rebuild completed for array in system [computersystemelementname]. Explanation: imm has detected that an array rebuild has completed. May also be shown as 816f070d0409ffff or 0x816f070d0409ffff severity: info alert category: system serviceable: no cim information: prefix: plat and ...

  • Page 1015

    816f070d-040cffff rebuild completed for array in system [computersystemelementname]. Explanation: imm has detected that an array rebuild has completed. May also be shown as 816f070d040cffff or 0x816f070d040cffff severity: info alert category: system serviceable: no cim information: prefix: plat and ...

  • Page 1016

    816f070d-040fffff rebuild completed for array in system [computersystemelementname]. Explanation: imm has detected that an array rebuild has completed. May also be shown as 816f070d040fffff or 0x816f070d040fffff severity: info alert category: system serviceable: no cim information: prefix: plat and ...

  • Page 1017

    816f0807-0303ffff [processorelementname] has been enabled. Explanation: imm has detected processor 3 has been enabled. May also be shown as 816f08070303ffff or 0x816f08070303ffff severity: info alert category: system serviceable: no cim information: prefix: plat and id: 0060 snmp trap id: automatica...

  • Page 1018

    816f0813-2581ffff system [computersystemelementname]has recovered from an uncorrectable bus error. Explanation: imm has detected that the system has recovered from a bus uncorrectable error. May also be shown as 816f08132581ffff or 0x816f08132581ffff severity: info alert category: critical serviceab...

  • Page 1019

    816f090c-2586ffff [physicalmemoryelementname] on subsystem [memoryelementname] is no longer throttled. Explanation: memory throttle in mem card 1 bank has deasserted. May also be shown as 816f090c2586ffff or 0x816f090c2586ffff severity: info alert category: system serviceable: no cim information: pr...

  • Page 1020

    816f090c-2589ffff [physicalmemoryelementname] on subsystem [memoryelementname] is no longer throttled. Explanation: memory throttle in mem card 4 bank has deasserted. May also be shown as 816f090c2589ffff or 0x816f090c2589ffff severity: info alert category: system serviceable: no cim information: pr...

  • Page 1021

    816f090c-258cffff [physicalmemoryelementname] on subsystem [memoryelementname] is no longer throttled. Explanation: memory throttle in mem card 7 bank has deasserted. May also be shown as 816f090c258cffff or 0x816f090c258cffff severity: info alert category: system serviceable: no cim information: pr...

  • Page 1022

    816f090c-258fffff [physicalmemoryelementname] on subsystem [memoryelementname] is no longer throttled. Explanation: memory throttle in meu mem bank 2 has deasserted. May also be shown as 816f090c258fffff or 0x816f090c258fffff severity: info alert category: system serviceable: no cim information: pre...

  • Page 1023

    816f0a07-0301ffff [processorelementname] is no longer operating in a degraded state. Explanation: imm has detected processor 1 is no longer running in the degraded state. May also be shown as 816f0a070301ffff or 0x816f0a070301ffff severity: info alert category: warning serviceable: no cim informatio...

  • Page 1024

    816f0a07-0304ffff [processorelementname] is no longer operating in a degraded state. Explanation: imm has detected processor 4 is no longer running in the degraded state. May also be shown as 816f0a070304ffff or 0x816f0a070304ffff severity: info alert category: warning serviceable: no cim informatio...

  • Page 1025

    816f0a0c-2588ffff an over-temperature condition has been removed on the [physicalmemoryelementname] on subsystem [memoryelementname]. Explanation: over-temp in mem card 3 bank has deasserted. May also be shown as 816f0a0c2588ffff or 0x816f0a0c2588ffff severity: info alert category: critical servicea...

  • Page 1026

    816f0a0c-258bffff an over-temperature condition has been removed on the [physicalmemoryelementname] on subsystem [memoryelementname]. Explanation: over-temp in mem card 6 bank has deasserted. May also be shown as 816f0a0c258bffff or 0x816f0a0c258bffff severity: info alert category: critical servicea...

  • Page 1027

    816f0a0c-258effff an over-temperature condition has been removed on the [physicalmemoryelementname] on subsystem [memoryelementname]. Explanation: over-temp in meu bank 1 has deasserted. May also be shown as 816f0a0c258effff or 0x816f0a0c258effff severity: info alert category: critical serviceable: ...

  • Page 1028

    816f0a0c-2591ffff an over-temperature condition has been removed on the [physicalmemoryelementname] on subsystem [memoryelementname]. Explanation: over-temp in meu bank 4 has deasserted. May also be shown as 816f0a0c2591ffff or 0x816f0a0c2591ffff severity: info alert category: critical serviceable: ...

  • Page 1029

    Appendix c. Uefi/post error codes this topic provides details about error codes that display after the server performs a series of tests called the power-on self test, or post, to check the operation of the server components and some optional devices. About this task when you turn on the server, it ...

  • Page 1030

    I.2018002 [i.2018002] the device found at bus % device % function % could not be configured due to resource constraints. The vendor id for the device is % and the device id is %. Explanation: out_of_resources (pci option rom) severity: info user response: complete the following steps: 1. If this pci...

  • Page 1031

    I.3108002 explanation: gpt corruption recoverd severity: info user response: complete the following steps: 1. No action needed. I.3808004 [i.3808004] the imm system event log (sel) is full. Explanation: ipmi system event log is full severity: info user response: complete the following steps: 1. Use ...

  • Page 1032

    I.580a4 [i.580a4] memory population change detected. Explanation: dimm population change detected severity: info user response: complete the following steps: 1. Check system event log for uncorrected dimm failures and replace those dimms. I.580a5 [i.580a5] mirror fail-over complete. Dimm number % ha...

  • Page 1033

    S.2018001 [s.2018001] an uncorrected pcie error has occurred at bus % device % function %. The vendor id for the device is % and the device id is %. Explanation: pcie uncorrected error detected severity: error user response: complete the following steps: 1. If this node and/or any attached cables we...

  • Page 1034

    S.3818007 [s.3818007] the firmware image capsules for both flash banks could not be verified. Explanation: crtm image capsule could not be verified severity: error user response: complete the following steps: 1. If system failed to boot successfully, dc cycle system. 2. If system boots to f1 steup, ...

  • Page 1035

    S.51006 [s.51006] a memory mismatch has been detected. Please verify that the memory configuration is valid. Explanation: one or more mismatched dimms detected severity: error user response: complete the following steps: 1. Could follow an uncorrectable memory error or failed memory test. Check log ...

  • Page 1036

    W.11004 [w.11004] a processor within the system has failed the bist. Explanation: processor self test failure detected severity: error user response: complete the following steps: 1. If the processor or firmware was just updated, check ibm support site for an applicable retain tip or firmware update...

  • Page 1037

    W.3108002 explanation: gpt corruption happened severity: warning user response: complete the following steps: 1. Check hard disk data integrity,check pcie storage cards option rom firmware version and function if hard disks connected to the pcie storage cards. W.3808000 [w.3808000] an imm communicat...

  • Page 1038

    W.3818005 [w.3818005] the crtm flash driver could not successfully flash the staging area. The update was aborted explanation: crtm update aborted severity: warning user response: complete the following steps: 1. Continue booting system. If system does not reset, manually reset the system. 2. If the...

  • Page 1039

    W.58007 [w.58007] invalid memory configuration (unsupported dimm population) detected. Please verify memory configuration is valid. Explanation: unsupported dimm population severity: error user response: complete the following steps: 1. Could follow an uncorrectable memory error or failed memory tes...

  • Page 1040

    W.580a7 explanation: dimm service action detected, slot re-enabled severity: warning user response: complete the following steps: 1. No action; information only. W.580b0 explanation: memory smi link failure severity: warning user response: complete the following steps: 1. Check the ibm support site ...

  • Page 1041

    W.680b3 [w.680b3] currently, there is no additional information for this event. Explanation: external qpi link width reduction detected severity: error user response: complete the following steps: 1. Make sure that your qpi wrap cards or qpi scalability cables are installed and in the proper sequenc...

  • Page 1042

    W.680b7 [w.680b7] external qpi link quarter width reduction detected explanation: external qpi link quarter width reduction detected severity: error user response: complete the following steps: 1. Make sure that your qpi wrap cards or qpi scalability cables are installed and in the proper sequence 2...

  • Page 1043

    Appendix d. Getting help and technical assistance if you need help, service, or technical assistance or just want more information about ibm products, you will find a wide variety of sources available from ibm to assist you. Use this information to obtain additional information about ibm and ibm pro...

  • Page 1044

    Documentation that is provided with your ibm product. The documentation that comes with ibm systems also describes the diagnostic tests that you can perform. Most systems, operating systems, and programs come with documentation that contains troubleshooting procedures and explanations of error messa...

  • Page 1045

    Ibm taiwan product service use this information to contact ibm taiwan product service. Ibm taiwan product service contact information: ibm taiwan corporation 3f, no 7, song ren rd. Taipei, taiwan telephone: 0800-016-888 appendix d. Getting help and technical assistance 1029.

  • Page 1046

    1030 ibm system x3850 x5 and x3950 x5 types 7145, 7146, 7143, and 7191: problem determination and service guide.

  • Page 1047

    Notices this information was developed for products and services offered in the u.S.A. Ibm may not offer the products, services, or features discussed in this document in other countries. Consult your local ibm representative for information on the products and services currently available in your a...

  • Page 1048

    Trademarks ibm, the ibm logo, and ibm.Com are 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 . Adobe and postsc...

  • Page 1049

    Commands or might be incapable of being written to. Ibm is not responsible for replacement of a device that has exceeded its maximum guaranteed number of program/erase cycles, as documented in the official published specifications for the device. Ibm makes no representation or warranties regarding n...

  • Page 1050

    Table 26. Limits for particulates and gases (continued) contaminant limits 1 ashrae 52.2-2008 - method of testing general ventilation air-cleaning devices for removal efficiency by particle size . Atlanta: american society of heating, refrigerating and air-conditioning engineers, inc. 2 the deliques...

  • Page 1051

    Electronic emission notices when you attach a monitor to the equipment, you must use the designated monitor cable and any interference suppression devices that are supplied with the monitor. Federal communications commission (fcc) statement note: this equipment has been tested and found to comply wi...

  • Page 1052

    European union emc directive conformance statement 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 s...

  • Page 1053

    Zulassungsbescheinigung laut dem deutschen gesetz über die elektromagnetische verträglichkeit von geräten (emvg) (bzw. Der emc eg richtlinie 2004/108/eg) für geräte der klasse a dieses gerät ist berechtigt, in Übereinstimmung mit dem deutschen emvg das eg-konformitätszeichen - ce - zu führen. Verant...

  • Page 1054

    Japan electronics and information technology industries association (jeita) statement japan electronics and information technology industries association (jeita) confirmed harmonics guidelines (products less than or equal to 20 a per phase) japan electronics and information technology industries ass...

  • Page 1055

    People's republic of china class a electronic emission statement taiwan class a compliance statement notices 1039.

  • Page 1056

    1040 ibm system x3850 x5 and x3950 x5 types 7145, 7146, 7143, and 7191: problem determination and service guide.

  • Page 1057

    Index a ac good led 70 power led 17 power leds 70 ac power supply specifications 30 accessible documentation 1034 adapter removing 110 replacing 111 administrator password 206, 208 advanced settings utility (asu) program, overview 217 air baffle, memory expansion module removing 179 replacing 180 as...

  • Page 1058

    Dsa (continued) editions 72 portable 72 preboot 72 dsa preboot 73 dvd cable 146 dvd cable, replacing 146 dvd drive activity led 13 eject button 13 install 116 internal cabling 102 problems 43 replacing 115 dynamic system analysis (dsa) 71 e electrical equipment, servicing viii electrical input 9 ele...

  • Page 1059

    Hot-swap (continued) power supply, memory expansion module removing 192 replacing 193 humidity 8 humidity specifications 31 hypervisor key installing 141 removing 140 hypervisor, embedded problems 44 i i/o board connector illustrations 26 jumpers 27 leds 26, 27 i/o shuttle removing 143 replacing 144...

  • Page 1060

    Mem, light path diagnostic led 66 memory 129 installation 136 problems 48 specifications 8 supported 129 memory card connector illustrations 22 dimm connectors 131 leds 23, 61 removing 136 memory card, replacing 137 memory expansion module 29, 34 bezel replacing 178 components removing and replacing...

  • Page 1061

    Problems (continued) general 44 hard disk drive 45 intermittent 45 keyboard 46 memory 48 microprocessor 49 monitor 50 optional devices 52 post 1013 serial port 55 serverguide 55 usb port 57 video 50, 57 product service, ibm taiwan 1029 publications 6 q qpi link leds 18 qpi multi-node 226 qpi ports 1...

  • Page 1062

    Size of memory enclosure 31 slots 8 software problems 56 software service and support telephone numbers 1028 solid state drive 116 solid state drive backplane, removing 156 sparing 129 specifications 7 specifications, memory expansion module 29 ssd backplane assembly, replacing 156 start here 40 sta...

  • Page 1064

    Part number: 00fh790 printed in usa (1p) p/n: 00fh790