1. DL manuals
  2. IBM
  3. Server
  4. System x3950 X6
  5. Installation And Service Manual

IBM System x3950 X6 Installation And Service Manual

Summary of System x3950 X6

  • Page 1

    System x3850 x6 and x3950 x6 types 3837 and 3839 installation and service guide.

  • Page 3

    System x3850 x6 and x3950 x6 types 3837 and 3839 installation and service guide.

  • Page 4

    Note: before using this information and the product it supports, read the general information in “notices” on page 1693 and the ibm safety information, and ibm environmental notices and user's guide on the ibm documentation cd, and the ibm warranty information document that comes with the server. Fi...

  • Page 5: Contents

    Contents safety . . . . . . . . . . . . . . . Vii guidelines for trained service technicians . . . . Xv inspecting for unsafe conditions . . . . . . . Xv guidelines for servicing electrical equipment . . . Xvi chapter 1. The ibm system x3850 x6 and x3950 x6 types 3837 and 3839 server . . . . . . . ....

  • Page 6

    Installing your operating system without using serverguide. . . . . . . . . . 126 using the setup utility . . . . . . . . . 126 starting the setup utility . . . . . . . 126 setup utility menu choices . . . . . . . 127 passwords . . . . . . . . . . . . 131 using the boot manager. . . . . . . . . 133 ...

  • Page 7

    Removing the standard i/o book . . . . 221 replacing the standard i/o book. . . . . 222 removing the standard i/o book air baffle 223 replacing the standard i/o book air baffle 225 removing the half-length i/o book . . . . 226 replacing the half-length i/o book . . . . 227 removing the full-length i...

  • Page 8

    Important notes . . . . . . . . . . . . 1694 particulate contamination . . . . . . . . . 1695 documentation format . . . . . . . . . . 1696 telecommunication regulatory statement . . . . 1696 electronic emission notices . . . . . . . . 1697 federal communications commission (fcc) statement . . . . ....

  • Page 9: Safety

    Safety this topic provides safety information that you should read before using the server. 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...

  • Page 10

    Les sikkerhetsinformasjonen (safety information) før du installerer dette produktet. Antes de instalar este produto, leia as informações sobre segurança. Bu ürünü kurmadan önce güvenlik bilgilerini okuyun. Antes de instalar este producto, lea la información de seguridad. Läs säkerhetsinformationen i...

  • Page 11

    Statement 1 danger electrical current from power, telephone, and communication cables is hazardous. To avoid a shock hazard: v do not connect or disconnect any cables or perform installation, maintenance, or reconfiguration of this product during an electrical storm. V connect all power cords to a p...

  • Page 12

    Caution: when replacing the lithium battery, use only ibm part number 33f8354 or an equivalent type battery recommended by the manufacturer. If your system has a module containing a lithium battery, replace it only with the same module type made by the same manufacturer. The battery contains lithium...

  • Page 13

    Statement 4 caution: use safe practices when lifting. Three graphic illustrations for safety practices when lifting the server ≥ 18 kg (39.7 lb.) ≥ 32 kg (70.5 lb.) ≥ 55 kg (121.2 lb.) statement 5 caution: the power control button on the device and the power switch on the power supply do not turn of...

  • 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

    Caution: do not place any object on top of rack-mounted devices. Statement 31: danger electrical current from power, telephone, and communication cables is hazardous. To avoid a shock hazard: to disconnect: 1. Turn off all power sources and equipment that is to be attached to this product. For ac sy...

  • Page 16

    Statement 34: caution: to reduce the risk of electric shock or energy hazards: • this equipment must be installed by trained service personnel in a restricted-access location, as defined by the nec and iec 60950-1, first edition, the standard for safety of information technology equipment. • connect...

  • Page 17

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

  • Page 18

    Guidelines for servicing electrical equipment this topic provides guidelines that you must follow when servicing electrical equipment. Observe the following guidelines when you service electrical equipment: v check the area for electrical hazards such as moist floors, nongrounded power extension cor...

  • Page 19: 3837 And 3839 Server

    Chapter 1. The ibm system x3850 x6 and x3950 x6 types 3837 and 3839 server use this information for a product overview of the ibm ® system x3850 x6 and x3950 x6 types 3837 and 3839 server and links to additional information for users of the system and business partners. Read the safety information b...

  • Page 20

    Products that are of interest to you. From this personalized page, you can subscribe to weekly email notifications about new technical documents, search for information and downloads, and access various administrative services. If you participate in the ibm client reference program, you can share in...

  • Page 21

    Documentation that comes with the server, and the documentation might be updated occasionally to include information about those features, or technical updates might be available to provide additional information that is not included in the server documentation. To check for updates, go to http://ww...

  • Page 22

    Machine type and model number customer label space customer label space qr codes in addition, the system service card that is located between the left eia bracket and the ibm x6 storage book in the front of the server, provides a quick reference (qr) code for mobile access to service information. Yo...

  • Page 23

    You can download an ibm serverguide setup and installation dvd to help you configure the hardware, install device drivers, and install the operating system. For a list of supported optional devices for the server, see http://www.Ibm.Com/ systems/info/x86servers/serverproven/compat/us/. See the rack ...

  • Page 24

    While you select the documents. Click view book to view the selected document or documents in acrobat reader or xpdf. If you selected more than one document, all the selected documents are opened in acrobat reader or xpdf. To search all the documents, type a word or word string in the search field a...

  • Page 25

    The server might have features that are not described in the documentation that you received with the server. The documentation might be updated occasionally to include information about those features, or technical updates might be available to provide additional information that is not included in...

  • Page 26

    V four scalable memory interconnect 2 (smi2) links per microprocessor at up to 6.4 gt/s v each microprocessor has four memory channels, each memory channel has two ddr channels, and each ddr channel supports three dimms v intel ex microprocessor + c600 series chipset (pch) v hyperthreading technolog...

  • Page 27

    – one x8 full-height slot, gen2, 4 lanes wired (pcie gen3, x8 (4, 1) note: the optional ibm x6 full-length i/o book also supports full-length, full height and low-profile pcie adapters. Power supply: the server supports up to four of the following power supplies: v 1400-watt ac input power supplies ...

  • Page 28

    Note: the optional dual-port and quad-port ethernet adapters with iscsi, vnic, tcp/ip offload engine (toe), fiber channel over ethernet (fcoe), and wake on lan support, can provide up to 10 gb capability. Video controller (integrated into the imm2): v matrox g200er core (two analog ports: one front ...

  • Page 29

    Attention: airborne particulates and reactive gases acting alone or in combination with other environmental factors such as humidity or temperature might pose a risk to the server. For information about the limits for particulates and gases, see “particulate contamination” on page 1695. Airflow: v i...

  • Page 30

    International business machines corporation new orchard road armonk, new york 10504 http://www.Ibm.Com/customersupport/ for more information on the energy efficiency program, go to http://www.Ibm.Com/systems/x/hardware/energy-star/index.Html. Product type: rack server year first manufactured: 2014 i...

  • Page 31

    What your server offers use this information to get an overview of the server functions, features, capabilities, and technologies. The server uses the following features and technologies: v active energy manager the ibm active energy manager solution is an ibm systems director extension that measure...

  • Page 32

    The serverguide setup and installation dvd, which you can download from the web, provides programs to help you set up the server and install a windows operating system. The serverguide program detects installed optional hardware devices and provides the correct configuration programs and device driv...

  • Page 33

    Pc3-12800r 1600 mhz, pc3l-12800 1600 mhz or pc3l-10600 1333 mhz load reduced (lr), single-rank, dual-rank, or quad-rank, ddr3 (third-generation double-data-rate), registered, synchronous dynamic random access memory (sdram) dimms. The server also supports 200 gb and 400 gb exflash dimms. You can use...

  • Page 34

    V pci express gen3 adapter capabilities the server provides up to twelve pcie gen3 adapter slots. See “installing an adapter” on page 84 for more details and information about installing adapters. V redundant connection the dual-port and quad-port ethernet controller provides failover capability to ...

  • Page 35

    The server comes with the service advisor feature that can collect data about the system when the system detects a fault and sends that data to ibm service for problem determination. It also includes the call home feature that automatically calls ibm service when a problem occurs. The service adviso...

  • Page 36

    Reliability, availability, and serviceability this topic provides an overview of the server reliability, availability, and serviceability (ras) features. Three important computer design features are reliability, availability, and serviceability (ras). The ras features help to ensure the integrity of...

  • Page 37

    V menu-driven setup, system configuration, and redundant array of independent disks (raid) configuration programs v microprocessor built-in self-test (bist), internal error signal monitoring, internal thermal trip signal monitoring, configuration checking, and microprocessor and voltage regulator mo...

  • Page 38

    Server scalability this topic provides information about scaling from a 4-socket to an 8-socket configuration. The ibm system x3850 x6 and x3950 x6 server uses a direct qpi connection topology through the midplane to scale from a x3850 x6 (4-socket configuration) to a x3950 x6 (8-socket configuratio...

  • Page 39

    Ibm systems director this topic provides an overview of the ibm systems director systems management tool. Ibm systems director is a platform-management foundation that streamlines the way you manage physical and virtual systems in a heterogeneous environment. By using industry standards, ibm systems...

  • Page 40

    Server components this information provides an overview of the major components in the server. The server major components include the ibm x6 storage book, the lcd system information display panel, ibm x6 ddr3 compute book, ibm x6 standard i/o book, ibm x6 half-length i/o book, ibm x6 full-length i/...

  • Page 41

    Chassis shuttle rear fan-packs standard i/o book half-length i/o book full-length i/o book i/o book filler power supply filler 100 mm power supply power supply spacer 80 mm power supply the following is an illustration of the 8-socket chassis, midplane, and shuttle: 8-socket shuttle 8-socket midplan...

  • Page 42

    Front view of the server this information provides an overview of the components that are accessible from the front of the server. The storage book, lcd system information display panel, front operator panel, front i/o panel, fan-packs 1 through 8, and the ddr3 compute books are in the front of the ...

  • Page 43

    V one usb 2.0 connectors v two usb 3.0 connectors v the front operator panel connector v the lcd system information display panel connector the following illustration shows the connectors, leds, and controls that are accessible on the storage book. Storage book scroll up button scroll down button re...

  • Page 44

    Drive is being rebuilt. When the led is flashing rapidly (three flashes per second), it indicates that the controller is identifying the drive. V drive activity leds: these leds are on sas or sata hard disk drives and solid state drives. Each hot-swap drive has an activity led, and when this led is ...

  • Page 45

    V pcie slots 11 and 12 error leds: when these leds are lit, they indicate that an error has occurred in pcie slots 11 and 12 on the storage book board. V storage board error led: when this yellow led is lit, it indicates that an error with the storage book board has occurred. V usb 2.0 connector: co...

  • Page 46

    Lcd system information display panel use this information for an overview of the lcd system information display panel, which displays various types of information about the server. The lcd system information display panel is attached to the storage book on the front of the server. The lcd system inf...

  • Page 47

    System name system status check-mark above 2 indicates system is booting from alternative uefi bank. Network icon this shows a system supporting four ethernet ports. If the numbers are flashing, the ports are active uefi\post code system status ibm x3850 x6 when you navigate through the hierarchy of...

  • Page 48

    V system environmental information: – ambient temperature – cpu temperature – ac input voltage – estimated power consumption ddr3 compute book use this information for an overview of the ddr3 compute book. The ddr3 compute book is in the front of the server. Each ddr3 compute book must have a minimu...

  • Page 49

    Dimm 1 dimm 2 dimm 3 dimm 4 dimm 5 dimm 6 dimm 10 dimm 11 dimm 12 dimm 7 dimm 8 dimm 9 microprocessor the following illustration shows the location of the dimm connectors on the non-microprocessor side of the ddr3 compute book board: dimm 24 dimm 23 dimm 22 dimm 19 dimm 20 dimm 21 dimm 15 dimm 14 di...

  • Page 50

    Power supply 1 power supply 2 power supply 3 power supply 4 fan-pack 9 fan-pack 10 i/o book 1 i/o book 2 standard i/o book standard i/o book use this information to for an overview of the system standard i/o book. The components in the server standard i/o book are the minimum set of i/o components t...

  • Page 51

    V 3v battery error led: when this led is lit, it indicates that a standard i/o book battery error has occurred. V ethernet connectors: use either of these connectors to connect the server to a network. When you use the ethernet 1 connector, the network can be shared with the imm through a single net...

  • Page 52

    The server standard i/o book board provides the following slots, connectors, and integrated features: v integrated management module v.2 (imm2) v real time management module (rtmm) v one ml adapter slot v three pcie gen3 slots (8 gigatransfers per second (gt/s)) v five usb 2.0 connectors – one inter...

  • Page 53

    Half-length i/o book use this information for an overview of the half-length i/o book. The half-length i/o book installs in the rear of the server. The server provides the ability to concurrently hot-add or hot-remove pcie adapters in this i/o book. Note: the ability to hot-plug the half-length i/o ...

  • Page 54

    On: a slot error has occurred. V slot power leds: the states of the power leds are as follows: off: input power to the slot is not present. On: power to the slot is present. You cannot remove the i/o book from the server until the power leds on all three slots are off. Blinking: the slot is in the p...

  • Page 55

    The following illustration shows the connectors, leds, and controls on the full-length i/o book: full-length i/o book i/o board error led slot power leds slot error leds power button v slot error leds: the states of the slot error leds are as follows: off: the slot or adapter is in normal operation....

  • Page 56

    Power supplies use this information for an overview of the type of power supply modules that the server supports. About this task the server supports up to four 900-watt ac power supplies, 1400-watt ac power supplies, or 750-watt -48 volt dc power supplies. For more information about the supported p...

  • Page 57

    Jumpers, switches, and buttons on standard i/o book board this topic provides the location and information about the jumpers, switches, and buttons on the standard i/o book board. The following illustration shows the location of the switches, jumper, and button on the server. Note: if there is a cle...

  • Page 58

    Table 3. Standard i/o book board sw1 switch block descriptions switch number default position description 1 off power-on password override. Changing the position of this switch bypasses the power-on password check the next time the server is turned on and starts the setup utility so that you can cha...

  • Page 59

    Table 4. Button on the standard i/o bookserver button name function nmi button this button is on the rear of the standard i/o book. Press this button to force a nonmaskable interrupt to the microprocessor. You might have to use a pen or the end of a straightened paper clip to press the button. You c...

  • Page 60

    Statement 5 caution: the power control button on the device does not turn off the electrical current supplied to the device. The device also might have more than one power cord. To remove all electrical current from the device, ensure that all power cords are disconnected from the power source. 1 2 ...

  • Page 61

    Chapter 2. Installing optional devices note: the information and procedures in this documentation apply to both the 4-socket and the 8-socket configurations of the server, unless otherwise specified. Most of the illustrations in the documentation uses the 4-socket configuration of the server. This i...

  • Page 62

    Instructions for ibm business partners this topic provides additional instructions for ibm business partners. In addition to the instructions in the documentation for installing optional hardware devices, updating firmware and device drivers, and completing the installation, ibm business partners mu...

  • Page 63

    Installation guidelines use this information to understand the guidelines that you need to follow when you install the server and devices in the server. Attention: static electricity that is released to internal server components when the server is powered on might cause the system to halt, which mi...

  • Page 64

    However, you must turn off the server before you perform any steps that involve removing or installing adapter cables. V blue on a component indicates touch points, where you can grip the component to remove it from or install it in the server, open or close a latch, and so on. V orange on a compone...

  • Page 65

    V while the device is still in its static-protective package, touch it to an unpainted metal surface on the outside of the server for at least 2 seconds. This drains static electricity from the package and from your body. V remove the device from its package and install it directly into the server w...

  • Page 66

    Table 5. Supported ddr3 dimms capacity density ranks organization form factor voltage type bandwidth (mhz) 4 gb 2 gb 1r 512mb x4 low profile 1.35v rdimm 1600 mhz 8 gb 4 gb 1r 1024mb x4 low profile 1.35v rdimm 1600 mhz 16 gb 4 gb 2r 1024mb x4 low profile 1.35v rdimm 1600 mhz 32 gb 4 gb 4r 1024mb x4 l...

  • Page 67

    Table 7. The maximum amount of memory that the server supports (continued) number of compute booksinstalled in the server number of dmms installed maximum memory note: v the x3850 x6 (4-socket) can support a maximum 6 tbs of memory and the x3950 x6 (8-socket) can support a maximum of 12 tbs of syste...

  • Page 68

    Table 8. Dimm connector slots in the compute book that is associated with each memory channel and ddr3 channel (continued) microprocessor memory channels ddr3 channels dimm connector ddr3 slot number channel 1 ddr3 channel 0 19 slot 0 20 slot 1 21 slot 2 ddr3 channel 1 1 slot 0 2 slot 1 3 slot 2 cha...

  • Page 69

    Cache line is provided per channel). For more information on the independent memory mode, see “independent memory mode” on page 55. – lockstep memory mode:: this mode provides the best memory ras features. It supports dual-device data correction (dddc) for x4 sdram technology. The memory controller ...

  • Page 70

    V if you install exflash dimms on the red hat and sles operating systems, keep in mind that the server supports only red hat enterprise linux version 6.5 or later and suse linux enterprise server (sles) version 11 sp3 or later operating systems. For more information about exflash dimms, go to http:/...

  • Page 71

    Table 10. Dimm population sequence for independent memory mode (continued) dimm installation order independent mode with memory mirroring disabled independent mode with memory mirroring enabled 23 dimm connector 21 24 dimm connector 18 memory mirroring use this information for an overview of memory ...

  • Page 72

    Memory rank sparing this information provides an overview for memory rank sparing. The server supports memory rank sparing. Memory rank sparing reserves memory capacity for failover in the event of a dimm failure, and the reserved capacity is subtracted from the total available memory. Memory sparin...

  • Page 73

    Independent memory mode use this information for notes and details about independent memory mode and dimm installation sequence. Independent memory mode supports the memory mirroring and memory rank sparing features. When you use independent memory mode, consider the following. For more information ...

  • Page 74

    Table 12. Dimm population sequence for independent memory mode dimm installation order independent mode with memory mirroring disabled independent mode with memory mirroring enabled 1 dimm connector 9 dimm connectors 9 and 19 2 dimm connector 6 dimm connectors 6 and 16 3 dimm connector 1 dimm connec...

  • Page 75

    V single-device data correction (sddc) is supported for x4 sdram technology. The following table lists the installation sequence for memory mirroring in independent mode: table 13. Dimm population sequence with memory mirroring enabled or disabled in independent memory mode dimm installation order i...

  • Page 76

    Memory rank sparing in independent mode this information covers using the memory rank sparing feature in independent memory mode. The server supports memory rank sparing. Memory rank sparing reserves memory capacity for failover in the event of a dimm failure, and the reserved capacity is subtracted...

  • Page 77

    Lockstep memory mode use this information for notes and details about lockstep memory mode and dimm population sequence. Lockstep memory mode supports the memory mirroring and memory rank sparing features. When you use lockstep memory mode, consider the following: v lockstep memory mode provides the...

  • Page 78

    The following table lists the dimm installation sequence for lockstep memory mode: table 15. Dimm population sequence for lockstep memory mode dimm installation order lockstep mode with memory mirroring disabled lockstep mode with memory mirroring enabled 1 dimm connectors 9 and 15 dimm connectors 1...

  • Page 79

    V the dimm population must be identical (size, organization, etc.) for memory channel 0 and memory channel 1, and identical for memory channel 2 and memory channel 3. V memory mirroring reduces the maximum available memory by half of the installed memory. For example, if the server has 64 gb of inst...

  • Page 80

    Memory rank sparing in lockstep mode this information covers using the memory rank sparing feature of the lockstep memory mode. The server supports memory rank sparing. Memory rank sparing reserves memory capacity for failover in the event of a dimm failure, and the reserved capacity is subtracted f...

  • Page 81

    The following illustration shows the dimm connectors on the microprocessor side of the ddr3 compute book board. Dimm 1 dimm 2 dimm 3 dimm 4 dimm 5 dimm 6 dimm 10 dimm 11 dimm 12 dimm 7 dimm 8 dimm 9 microprocessor the following illustration shows the dimm connectors on the non-microprocessor side of...

  • Page 82

    Compute book cover cover release/ touch points microprocessor heatsink ddr3 compute book 5. Open the retaining clip on each end of the dimm connector. Note: to avoid breaking the retaining clips or damaging the dimm connectors, open and close the clips gently. 64 system x3850 x6 and x3950 x6 types 3...

  • Page 83

    Dimm retaining clip retaining clip 6. Touch the static-protective package that contains the dimm to any unpainted metal surface on the outside of the server. Then, remove the dimm from the package. 7. Turn the dimm so that the dimm keys align correctly with the connector. 8. Insert the dimm into the...

  • Page 84

    Compute book cover microprocessor heatsink ddr3 compute book 11. Reinstall the ddr3 compute book into the server (see “replacing a ddr3 compute book” on page 284). If you have other devices to install or remove, do so now. Otherwise, go to “completing the installation” on page 119. Installing a ddr3...

  • Page 85

    V a minimum of four ddr3 compute books must be installed in the 8-socket (x3950 x6) server. V each ddr3 compute book must have a minimum of one microprocessor and one dimm installed. V the 4-socket (x3850 x6) server supports ddr3 compute book configurations of two or four. These are the only configu...

  • Page 86

    Table 20. Installation sequence for the six compute books configuration for an 8-socket server (continued) compute book top node (bay 1) top node (bay 2) top node (bay 3) top node (bay 4) bottom node (bay 1) bottom node (bay 2) bottom node (bay 3) bottom node (bay 4) 5 compute book 5 6 compute book ...

  • Page 87

    Table 21. Installation sequence for the eight compute books configuration for an 8-socket server compute book top node (bay 1) top node (bay 2) top node (bay 3) top node (bay 4) bottom node (bay 1) bottom node (bay 2) bottom node (bay 3) bottom node (bay 4) 1 compute book 1 2 compute book 2 3 comput...

  • Page 88

    Handle 8. Replace the compute book cover(s) (see “replacing the ddr3 compute book cover” on page 220). 9. Rotate the cam handle all the way up and push it into the server until it locks in place. Results if you have other devices to install or remove, do so now. Otherwise, go to “completing the inst...

  • Page 89

    V the electromagnetic interference (emi) integrity and cooling of the server are protected by having all bays and pcie slots covered or occupied. Note: when you install a drive, save the emc shield and filler panel from the bay in the event that you later remove the device. Drive ids this topic prov...

  • Page 90

    Supported sas/sata drive backplane configurations this information describes the supported drive backplane configurations for the server. About this task note: 1. When mixing drive backplane configurations, you must install all 1.8-inch ssd drive backplanes above all 2.5-inch drive backplanes. 2. Wh...

  • Page 91

    Configuration power connector port 0 sas signal cable connector port 1 sas signal cable connector you can install a combination of 2.5-inch and 1.8-inch sas/sata drive backplanes in the server for the maximum drive capacity. However, any sas/sata adapter that you install in the server must be capabl...

  • Page 92

    Backplane configurations for 8 drives use this information for an overview of the supported backplane configurations for 8 drives. About this task the following illustrations show the supported backplane configurations to support eight drives. This configuration consists of two 4x2.5-inch drive back...

  • Page 93

    Empty 7 1.8-inch ssd drive 6 1.8-inch ssd drive 5 1.8-inch ssd drive 4 1.8-inch ssd drive 3 1.8-inch ssd drive 2 1.8-inch ssd drive 1 1.8-inch ssd drive 0 1.8-inch ssd drive backplane configuration for 12 drives use this information for an overview of the supported backplane configuration for 12 dri...

  • Page 94

    3 2.5-inch hdd/ssd drive 2 2.5-inch hdd/ssd drive 1 2.5-inch hdd/ssd drive 0 2.5-inch hdd/ssd drive 4 1.8-inch ssd drive 5 1.8-inch ssd drive 6 1.8-inch ssd drive 7 1.8-inch ssd drive 8 1.8-inch ssd drive 9 1.8-inch ssd drive 10 1.8-inch ssd drive 11 1.8-inch ssd drive backplane configuration for 16...

  • Page 95

    8 1.8-inch ssd drive 9 1.8-inch ssd drive 10 1.8-inch ssd drive 11 1.8-inch ssd drive 12 1.8-inch ssd drive 13 1.8-inch ssd drive 14 1.8-inch ssd drive 15 1.8-inch ssd drive 7 1.8-inch ssd drive 6 1.8-inch ssd drive 5 1.8-inch ssd drive 4 1.8-inch ssd drive 3 1.8-inch ssd drive 2 1.8-inch ssd drive ...

  • Page 96

    Drive tray assembly filler panel drive handle (in open position) d. Gently push the drive assembly into the drive bay until the drive stops. E. Rotate the drive-tray handle to the closed (locked) position. F. Skip to step 6. 5. To install a 1.8-inch drive, complete the following step: a. Remove the ...

  • Page 97

    Drive tray assembly release latch 1.8-inch filler panel c. Insert the drive into the drive tray with the label side of the drive facing up and push the drive tray into the drive bay until it clicks into place and is seated firmly. D. Rotate the drive tray handle to the closed position and slide the ...

  • Page 98

    Installing the half-length and full-length i/o books use this information for an overview of the supported i/o books. About this task the server provides up to twelve pcie gen3 adapter slots using the supported i/o books. The server supports an optional half-length i/o book and an optional full-leng...

  • Page 99

    Table 22. Pcie slot numbering and the associated compute book. Two-column tables that shows the association between the pcie slots and the compute books pcie slot number (facing the rear of the server) compute book associated with the pcie slot 1 compute book 4 2 compute book 4 3 compute book 4 4 co...

  • Page 100

    Installing the full-length i/o book this information provides notes and other information that you need to consider when you install the full-length i/o book and the instructions for installing the i/o book in the server. About this task the following notes provide information that you must consider...

  • Page 101

    V pcie slots 1, 3, 4, and 6 (when two full-length i/o books are installed) are x16 gen 3 adapter slots. V double-wide adapters can only be installed in pcie slots 1 or 4. When you install double-wide adapters in slots 1 or 4, you cannot install an adapter in slots 2 and 5. V this i/o book also provi...

  • Page 102

    Release latch extension bracket filler panel handle 7. Open the i/o book cam handle. 8. Align the i/o book with the i/o bay in the server and slide it into the server. 9. Rotate the handle all the way up and push it into the server until it locks in place. Results if you have other devices to instal...

  • Page 103

    V locate the documentation that comes with the adapter and follow those instructions in addition to the instructions in this section. V the server does not support any high-definition video-out connector or stereo connector on any add-on video adapter. V the server does not support pci-x adapters or...

  • Page 104

    V the server provides up to twelve pcie gen 3 and gen 2 slots. V the server also supports several optional nvidia adapters that you can purchase. Attention: do not install the nvidia grid k1 and k2, the nvidia tesla k20 and k40, and the nvidia quadro k4000 and k6000 adapter options in systems contai...

  • Page 105

    Supported raid adapters use this information for an overview of the raid adapters that are supported on the server. About this task the following table lists the supported raid adapters. For more information about enabling features on demand software raid, see “enabling features on demand raid softw...

  • Page 106

    For information about the supported ethernet adapters, see “supported ml2 (ethernet) adapters” on page 89. For information about the supported raid cache cards, see “supported raid cache cards.” for information about the supported host bus adapters, see “supported host bus adapters” on page 86. For ...

  • Page 107

    Table 26. Supported raid cache cards and where you can install the cache cards. (continued) raid cache card where to install the card notes serveraid m5100 series 1 gb flash/raid 5 upgrade for ibm system x (raid cache card) you can install this cache card in the optional sas adapter connector on the...

  • Page 108

    Table 27. Supported ml2 (ethernet) adapters and where you can install the adapters. Ethernet adapters where to install the adapter notes and features intel x540 ml2 quad-port 1 gb-t ethernet adapter for ibm system x this adapter can only be installed in slot 10 on the standard i/o book board. V port...

  • Page 109

    Table 27. Supported ml2 (ethernet) adapters and where you can install the adapters. (continued) ethernet adapters where to install the adapter notes and features broadcom netxtremeii ml2 dual-port 10 gb-t ethernet adapter for ibm system x this adapter can only be installed in slot 10 on the standard...

  • Page 110

    Supported features on demand software use this information for an overview of the supported features on demand software. About this task the following table lists the supported features on demand (fod) software. For more information, see “installing an adapter” on page 84. For more information about...

  • Page 111

    Attention: do not install the optional nvidia grid k1 and k2, the nvidia tesla k20 and k40, and the nvidia quadro k4000 and k6000 adapters in systems containing 1tb of system memory or more. If these options are installed in systems with 1tb of memory or more, it might cause undetected data corrupti...

  • Page 112

    Installing the optional serveraid m5120 sas/sata controller user this information for instructions on how to install the serveraid m5120 sas/sata controller. About this task raid cache card connector release tab cache card bracket serveraid m5120 adapter you can purchase the optional ibm serveraid m...

  • Page 113

    3. Remove the i/o book in which the failed adapter is installed. Follow the removal instructions as documented for the i/o book. 4. Open the pcie retention lever and remove the expansion slot cover from the slot in which you want to install the adapter. 5. Make sure that the pcie retention lever is ...

  • Page 114

    Installing the serveraid m5210 sas/sata controller this information provides notes and information about what you need to consider when you install this adapter in the server and the installation instructions on how to install the adapter in the server . About this task you can purchase the optional...

  • Page 115

    4. Open the pcie retention lever and remove the expansion slot cover from the slot where you want to install the adapter. 5. Touch the static-protective package that contains the adapter to any unpainted surface on the outside of the server; then, grasp the adapter by the top edge or upper corners o...

  • Page 116

    V follow the general rule for connecting the sas signal cables to the adapter and drive backplane: port 0 on the adapter to port 0 on the drive backplane and port 1 on the adapter to port 1 on the drive backplane (depending on the type of drive backplane you install in the server). To install the ad...

  • Page 117

    Installing an adapter in the full-length i/o book use this information for instructions on how to install an adapter in the full-length i/o book. About this task note: v see “installing an adapter” on page 84 for additional notes and information that you must consider when you install an adapter in ...

  • Page 118

    Expansion slot cover cover adapter (full-length) 10. Connect the auxiliary power cable from the adapter to the board (see the following illustration for the location of the connector on the board). 11. Close the pcie retention lever to secure the adapter in place. 12. Connect any cables to the adapt...

  • Page 119

    Installing a raid cache card user this information for instructions on how to install a raid cache card. About this task the server supports optional raid cache cards that you can install on the raid cache card connector on the raid adapters to upgrade to raid levels 5 and 50 support. See “supported...

  • Page 120

    3. Remove the storage book (see “removing the storage book” on page 266). 4. Disconnect the cables from the bottom drive backplane, if needed. 5. Open the retention clip on the flash power module slot. Press the blue tab outward to open the retention clip (see the following illustration for the loca...

  • Page 121

    Procedure 1. Read the safety information and installation guidelines, see “safety” on page vii and “installation guidelines” on page 45. 2. Turn off the server and peripheral devices and disconnect all power cords and external devices. 3. Remove the standard i/o book (see “removing the standard i/o ...

  • Page 122

    Power module in the slot on the right side of the air baffle, route the cable through the hole under the flash power module slot. 7. Connect one end of the cable extender, that comes with the power module, to the flash power module cable and the other end of the cable extender to the adapter. 8. Rep...

  • Page 123

    Table 29. Population sequence for the supported power supply configurations for each 4-socket node power supply configuration notes: 1 power supply the power supply should be installed in bay 3. This configuration does not support power supply redundancy. A power supply filler must be installed in b...

  • Page 124

    Installing a 750-watt -48 volt to -60 volt dc power supply use this information for considerations that you need note when you install 750-watt -48 volt to -60 volt dc power supplies and the instructions for installing the 750-watt -48 volt to -60 dc power supplies in the server. About this task not...

  • Page 125

    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 problem with one ...

  • Page 126

    Statement 34: caution: to reduce the risk of electric shock or energy hazards: • this equipment must be installed by trained service personnel in a restricted-access location, as defined by the nec and iec 60950-1, first edition, the standard for safety of information technology equipment. • connect...

  • Page 127

    5. Touch the static-protective package that contains the power supply to any unpainted metal surface on the server; then, remove the power supply from the package and place it on a static-protective surface. 6. Attach the dc power cable to the new power supply. Make sure that the power cable wires a...

  • Page 128

    11. Route the power cable through the cable hook-and-loop on the rear of the server so that it does not accidentally become unplugged. 12. Reconnect all of the cables to the peripheral devices. 13. Restart the server. Make sure that it starts correctly and recognizes the newly installed device, and ...

  • Page 129

    Table 32. Population sequence for the supported power supply configurations for each 4-socket node (continued) power supply configuration notes: 4 power supplies power supplies 1, 2, 3, and 4 must be the same input type (that is, all ac power supplies or all dc power supplies). V if you mix 900-watt...

  • Page 130

    1 2 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 w...

  • Page 131

    Filler panel 1400-watt ac power supply power supply release tab 2) go to step 5. B. To install a 900-watt power supply , complete the following steps: 1) insert the power-supply spacer into the left side (against the bay wall) of the power-supply bay and slide it in until it snaps into place on tabs...

  • Page 132

    Installing a usb embedded hypervisor flash device use this information for instructions on how to install a usb hypervisor flash device. About this task to install a hypervisor flash device, complete the following steps: procedure 1. Read the safety information and installation guidelines, see “safe...

  • Page 133

    Results if you have other devices to install or remove, do so now. Otherwise, go to “completing the installation” on page 119. Installing the drive backplanes this information provides instructions on how to install the drive backplanes in the server. About this task the following topics provide ins...

  • Page 134

    8x1.8-inch drive filler 8x1.8-inch drive backplane assembly storage book drive leds 8. Slide the drive backplane assembly into the backplane bay until it clicks into place. 9. Connect the power cable to the power connector on the drive backplane assembly (one end of the power cable is connected to t...

  • Page 135

    About this task the following is an illustration of the 4x2.5-inch drive backplane: sas signal cable connector input power cable connector : to install the 4x2.5-inch hot-swap drive backplane, complete the following steps: procedure 1. Read the safety information and installation guidelines, see “sa...

  • Page 136

    6. Connect the power cable to the power connector on the drive backplane. Note: to ensure that the hard disk drive id numbering matches the drive id numbering on the front of the server, make sure that you connect the shorter blue power cable connector to the bottom backplane and connect the grey po...

  • Page 137

    Completing the installation use this information for instructions on what you need to do after you install devices in the server to complete the installation process. About this task to complete the installation, complete the following steps: procedure 1. Make sure that all cables are connected prop...

  • Page 138

    120 system x3850 x6 and x3950 x6 types 3837 and 3839: installation and service guide.

  • Page 139

    Chapter 3. Configuration information and instructions this topic provides information about updating the firmware and using the configuration utilities. Updating the firmware this topic provides information about updating the server firmware. Note: v some cluster solutions require specific code leve...

  • Page 140

    When you replace a device in the server, you might have to update the firmware that is stored in memory on the device or restore the pre-existing firmware from a cd or dvd image. The following list indicates where the firmware is stored: v uefi firmware is stored in rom on the standard i/o book boar...

  • Page 141

    The remote presence and blue-screen capture features are integrated functions of the integrated management module (imm2). The remote presence feature provides the following functions: – remotely viewing video with graphics resolutions up to 1600 x 1200 at 75 hz, regardless of the system state – remo...

  • Page 142

    Using the serverguide setup and installation dvd this topic provides information about using the serverguide setup and installation dvd. The serverguide setup and installation dvd provides software setup tools and installation tools that are designed for your server. The serverguide program detects ...

  • Page 143

    V includes an online readme file with links to tips for your hardware and operating-system installation setup and configuration overview this topic provides an overview of how you can use the serverguide program to setup and configure the server. When you use the serverguide setup and installation u...

  • Page 144

    Installing your operating system without using serverguide this topic provides information for installing the operating system without using the serverguide program. About this task if you have already configured the server hardware and you are not using the serverguide program to install your opera...

  • Page 145

    Setup utility menu choices this topic provides information about the server setup utility menu choices. The following choices are on the uefi setup utility main menu. Depending on the version of the uefi firmware, some menu choices might differ slightly from these descriptions. For more information ...

  • Page 146

    Select this choice to view the systems-management network interface port, the imm mac address, the current imm ip address, the system ethernet mac addresses, and the host name; define the static imm ip address, subnet mask, and gateway address; specify whether to use the static ip address or have dh...

  • Page 147

    Best features for reducing power and increasing performance in applications where the maximum bus speeds are not critical. - efficiency-favor performance mode select this choice to maintain the optimal balance between performance and power consumption. The server generally produces the best performa...

  • Page 148

    Select this choice to enable or disable restarting the server whenever a nonmaskable interrupt (nmi) occurs. The default is enabled. V halt on server error select this choice to prevent the server from booting the operating system and displaying the post event viewer when a severe error is detected ...

  • Page 149

    V user security select this choice to set, change, or clear passwords. The full setup utility menu, enables all of the options in the user security option. See “passwords” for more information. This choice is on the full and limited setup utility menu. – set power-on password select this choice to s...

  • Page 150

    To set, change, and delete the power-on password. A user who types the power-on password has access to only the limited setup utility menu; the user can set, change, and delete the power-on password, if the system administrator has given the user that authority. Power-on password: this topic provide...

  • Page 151

    While the server is turned off, move switch 1 on the switch block sw1 to the on position to enable the power-on password override. You can then start the setup utility and reset the power-on password. You do not have to return the switch to the previous position. The power-on password override switc...

  • Page 152

    Starting the backup server firmware this topic provides instructions on starting the backup copy of the server firmware in the event that the primary copy of the firmware becomes damaged or corrupt. About this task the standard i/o book board contains a backup copy area for the server firmware. This...

  • Page 153

    The updatexpress system pack installer this topic provides information about the updatexpress system pack installer program. The updatexpress system pack installer detects supported and installed device drivers and firmware in the server and installs available updates. For additional information and...

  • Page 154

    Attention: installing the wrong firmware or device-driver update might cause the server to malfunction. Before you install a firmware or device-driver update, read any readme and change history files that are provided with the downloaded update. These files contain important information about the up...

  • Page 155

    The scalable complex home page will show the available state of all of the available nodes. To log on to the imm2 web interface, see “logging on to the imm web interface” on page 141. For more information about using imm2, the imm2 web interface and the imm2 telnet interface to manage and partition ...

  • Page 156

    Note: when one microprocessor fails in a four-microprocessor configuration, two microprocessors will be disabled. V automatic server restart (asr) when post is not complete or the operating system hangs and the operating system watchdog timer times out. The imm might be configured to watch for the o...

  • Page 157

    Establish a serial over lan (sol) connection to manage servers from a remote location. You can remotely view and change the uefi settings, restart the server, identify the server, and perform other management functions. Any standard telnet client application can access the sol connection. Using the ...

  • Page 158

    4. Add "ff" and "fe" in the middle of the 12 characters (for example, 5c f3 fc ff fe 5e aa d0). 5. Convert the first pair of hexadecimal characters to binary (for example, 5=0101, c=1100, which results in 01011100 f3 fc ff fe 5e aa d0). 6. Flip the 7th binary character from left (0 to 1 or 1 to 0), ...

  • Page 159

    Logging on to the imm web interface this topic provides instructions on how to log on to the imm web interface. About this task to log on to the imm2 web interface, complete the following steps: procedure 1. On a system that is connected to the server, open a web browser. In the address or url field...

  • Page 160

    Logging on to the imm cli interface using telnet this topic provides instructions on how to log on to the imm cli interface using telnet. About this task to log on to the imm cli interface using telnet, complete the following steps: note: if you boot to the operating system while in the imm gui and ...

  • Page 161

    4. At the system prompt, type your command. Note: you can type help in the command prompt if you want to see a list of commands that you can use. 5. When you are finished, type exit, to exit the session. Setting power supply power policy and system power configurations this topic provides informatio...

  • Page 162

    The following illustration is an example of the system power configuration setting in imm2 for configuring ac power supplies for redundancy mode. Note: when you change the power configuration settings, make sure you select a redundancy mode and then select the power supply system configuration that ...

  • Page 163

    Using the embedded hypervisor software use this information to find out how to enable the embedded hypervisor software on the usb flash device. About this task the vmware esxi embedded hypervisor software is available on the optional ibm usb flash device with embedded hypervisor. The usb flash devic...

  • Page 164

    Configuring the ethernet controller this topic provides information about configuring the ethernet controllers. The ethernet controller provides an interface for connecting to a 1 gbps or 10 gbps network and provides full-duplex (fdx) capability, which enables simultaneous transmission and reception...

  • Page 165

    Configuring raid arrays this topic provides instructions on how to configure raid arrays using the server setup utility. Through the setup utility, you can access utilities to configure raid arrays. The specific procedure for configuring arrays depends on the raid controller that you are using. For ...

  • Page 166

    Updating ibm systems director this topic provides instructions on how to check for and make updates to the ibm systems director program. About this task if you plan to use ibm systems director to manage the server, you must check for the latest applicable ibm systems director updates and interim fix...

  • Page 167

    11. Select the updates that you want to install, and click install to start the installation wizard. Updating the universal unique identifier and dmi/smbios data this topic provides information about updating the universal unique identifier and dmi/smbios data on the server. After the standard i/o b...

  • Page 168

    Where: xxxx is the 4-digit machine type of the server. Yyy is the 3-digit model number of the server. 2. Enter the following command: asu set system_prod_data.Sysinfoserialnum zzzzzzz where zzzzzzz is the 7-character serial number of the server. 3. Enter the following command: asu set system_prod_da...

  • Page 169

    Ipaddress is the internal lan/usb ip address of the imm. The default is 169.254.95.118. Userid is the imm account name (1 of 12 accounts). The default is userid. Password is the imm account password (1 of 12 accounts). The default is passw0rd (with a zero, not the letter o). 2. Enter the following c...

  • Page 170

    Yyy is the 3-digit model number of the server. Ipaddress is the external lan ip address of the imm. Userid is the imm account name (1 of 12 accounts). The default is userid. Password is the imm account password (1 or 12 accounts). The default is passw0rd (with a zero, not the letter o). 2. Enter the...

  • Page 171: Chapter 4. Troubleshooting

    Chapter 4. Troubleshooting this information describes the diagnostic tools and troubleshooting information that are available to help you solve problems that might occur in the server. If you cannot diagnose and correct a problem by using the information in this chapter, see appendix d, “getting hel...

  • Page 172

    To download the latest version of dsa code and the dynamic system analysis installation and user's guide, go to http://www.Ibm.Com/support/entry/portal/ docdisplay?Lndocid=serv-dsa. 4. Check for and apply code updates. Fixes or workarounds for many problems might be available in updated uefi firmwar...

  • Page 173

    Must remove nonsupported hardware before you contact ibm or an approved warranty service provider for support. B. Make sure that the server, operating system, and software are installed and configured correctly. Many configuration problems are caused by loose power or signal cables or incorrectly se...

  • Page 174

    Service bulletins use this information to find the latest tips and techniques for solving system problems. Ibm continually updates the support website with the latest tips and techniques that you can use to solve problem that you might have with the ibm system x3850 x6 server. To find service bullet...

  • Page 175

    V if the server is halted and a post error code is displayed, see appendix c, “uefi/post error codes,” on page 1665. If the server is halted and no error message is displayed, see “troubleshooting by symptom” on page 178 and “solving undetermined problems” on page 199. V for information about power-...

  • Page 176

    Diagnostic tools this topic provides an overview of the tools that are available to help diagnose server problems. The following tools are available to help you diagnose and solve hardware-related problems: v light path diagnostics use light path diagnostics to diagnose system errors quickly. See “l...

  • Page 177

    - service processor (integrated management module) status and configuration - system configuration - vital product data, firmware, and uefi configuration dsa portable creates a dsa log, which is a chronologically ordered merge of the system-event log (as the ipmi event log), the integrated managemen...

  • Page 178

    Light path diagnostics this topic provides an overview of the light path diagnostics leds. Light path diagnostics is a system of leds on various external and internal components of the server that leads you to the failed component. When an error occurs, leds are lit on the front operator panel on th...

  • Page 179

    Systemname systemstatus errors error 1 error 2 error 3 error n system vpd mtm # serial # uuid string pdsa code system fw levels uefi primary level uefi backup level imm primary level imm backup level imm hostname imm network info. Imm ext mac or imm shared mac ip add. Dns primary dns secondary dns t...

  • Page 180

    Storage book reset button power button\ led locate button\ led check log led system error led pcie slot 11 error led pcie slot 12 error led board error led drive activity led (green) drive status led (yellow) compute book leds use this information to determine the location of the leds on the compute...

  • Page 181

    Dimms and microprocessor leds use this information to determine the location of the dimms and microprocessor leds. The following illustration shows the location of the dimms and microprocessor leds on the microprocessor side of the ddr3 compute book board. (left side of board) dimm 1 - 3 error leds ...

  • Page 182

    Fan led fan-pack half-length i/o book leds use this information to determine the location of the half-length i/o book leds. The following illustration shows the location of the half-length i/o book leds. Half-length i/o book i/o board error led slot power leds slot error leds power button full-lengt...

  • Page 183

    Standard i/o book leds use this information to determine the location of the leds on the standard i/o book. The following illustration shows the location of the leds on the standard i/o book. Fan-pack 9 error led nmi button 3v battery error led i/o board error led locate led system power led system ...

  • Page 184

    Power connector ac power led (green) dc power led (green) power supply error led (yellow) the following table describes the problems that are indicated by various combinations of the power-supply leds and the power-on led on the front operator panel and suggested actions to correct the detected prob...

  • Page 185

    Light path diagnostics leds description this topic provides a description of the light path diagnostics leds. The following table describes the server leds to help you detect the location of the problems. For the location of the server leds, see “storage book leds” on page 161, “compute book leds” o...

  • Page 186

    Table 36. Light path diagnostics leds description (continued) led description locate button/led press the locate button to visually locate the server among other servers. When you press the locate button, the led will be lit and it will continue to be lit until you press it again to turn it off. Thi...

  • Page 187

    Most recent events available for analysis. For more information about the system-event log, see appendix b, “integrated management module ii (imm2) error messages,” on page 437. Messages are listed on the left side of the screen, and details about the selected message are displayed on the right side...

  • Page 188

    Viewing event logs without restarting the server use this information to learn how to view event logs without restarting the server. About this task if the server is not hung and the imm is connected to a network, methods are available for you to view one or more event logs without having to restart...

  • Page 189

    Table 37. Methods for viewing event logs (continued) condition action the server is not hung and is not connected to a network (using an operating system controlled network ports). Use any of the following methods: v run portable dsa to view the diagnostic event log (requires ipmi driver) or create ...

  • Page 190

    Clearing the error logs this topic provides instructions on how to clear the server error logs using setup utility. About this task to clear the event logs, complete the following steps. Note: the post event log is automatically cleared each time the server is restarted. Procedure 1. Turn on the ser...

  • Page 191

    Ibm dynamic system analysis this topic provides an overview of the ibm dynamic system analysis program. Ibm dynamic system analysis (dsa) collects and analyzes system information to aid in diagnosing server problems. Dsa collects the following information about the server: v drive health information...

  • Page 192

    Dsa editions this topic provides information on the two editions of the ibm dynamic system analysis program. Two editions of dynamic system analysis are available: v dsa portable dsa portable edition runs within the operating system; you do not have to restart the server to run it. It is packaged as...

  • Page 193

    Running the dsa preboot diagnostic programs this topic provides information on how to run the dsa preboot diagnostic programs. About this task note: the dsa memory test might take up to 30 minutes to run. If the problem is not a memory problem, skip the memory test. To run the dsa preboot diagnostic...

  • Page 194

    Viewing the test log results and transferring the dsa collection this topic provides information on how to view the dsa test log results and how to transfer the dsa collection of data to an external usb device or to ibm support. To view the test log for the results when the tests are completed, clic...

  • Page 195

    Ibm electronic service agent this topic provides information about the ibm electronic service agent tool for collecting server data. Ibm electronic service agent monitors, tracks, and captures system hardware errors and hardware and software inventory information, and reports serviceable problems di...

  • Page 196

    Capturing the ffdc log using ipmi commands this topic provides instructions for using the ipmi commands to capture the ffdc log data. To generate and download the first failure data capture (ffdc) log data using ipmi commands, complete the following steps: 1. From a host system, type the command: ip...

  • Page 197

    4. Reinstall the new software or new device. Connectivity problems use this information to solve connectivity problems. Table 38. Symptoms and user actions for connectivity problems v follow the suggested actions in the order in which they are listed in the action column until the problem is solved....

  • Page 198

    Table 38. Symptoms and user actions for connectivity problems (continued) v follow the suggested actions in the order in which they are listed in the action column until the problem is solved. V see chapter 5, “parts listing, system x3850 x6 and x3950 x6 types 3837 and 3839,” on page 205 to determin...

  • Page 199

    Hard disk drive problems use this information to solve hard disk drive problems. Table 40. Symptoms and user actions for hard disk drive problems 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 5, “parts listing, sy...

  • Page 200

    Table 40. Symptoms and user actions for hard disk drive problems (continued) v follow the suggested actions in the order in which they are listed in the action column until the problem is solved. V see chapter 5, “parts listing, system x3850 x6 and x3950 x6 types 3837 and 3839,” on page 205 to deter...

  • Page 201

    Table 40. Symptoms and user actions for hard disk drive problems (continued) v follow the suggested actions in the order in which they are listed in the action column until the problem is solved. V see chapter 5, “parts listing, system x3850 x6 and x3950 x6 types 3837 and 3839,” on page 205 to deter...

  • Page 202

    Hypervisor problems use this information to solve hypervisor problems. Table 41. Symptoms and user actions for hypervisor problems 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 5, “parts listing, system x3850 x6 a...

  • Page 203

    Keyboard, mouse, or pointing-device problems use this information to solve keyboard, mouse, or pointing-device problems. Table 43. Symptoms and user actions for keyboard, mouse, or pointing-device problems v follow the suggested actions in the order in which they are listed in the action column unti...

  • Page 204

    Memory problems use this information to solve memory problems. Table 44. Symptoms and user actions for memory problems 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 5, “parts listing, system x3850 x6 and x3950 x6 ...

  • Page 205

    Microprocessor problems use this information to solve microprocessor problems. Table 45. Symptoms and user actions for microprocessor problems 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 5, “parts listing, syste...

  • Page 206

    Netwok connectivity problems use this information to solve network connectivity problems. Table 47. Symptoms and user actions for network connectivity problems 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 5, “par...

  • Page 207

    Table 48. Symptoms and user actions for problems that you observer that are not normal (continued) v follow the suggested actions in the order in which they are listed in the action column until the problem is solved. V see chapter 5, “parts listing, system x3850 x6 and x3950 x6 types 3837 and 3839,...

  • Page 208

    Optional-device problems use this information to solve optional-device problems. Table 49. Symptoms and user actions for optional device problems 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 5, “parts listing, sy...

  • Page 209

    Power problems use this information to solve power problems. Table 50. Symptoms and user actions for power problems 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 5, “parts listing, system x3850 x6 and x3950 x6 typ...

  • Page 210

    Table 50. Symptoms and user actions for power problems (continued) v follow the suggested actions in the order in which they are listed in the action column until the problem is solved. V see chapter 5, “parts listing, system x3850 x6 and x3950 x6 types 3837 and 3839,” on page 205 to determine which...

  • Page 211

    Table 51. Symptoms and user actions for serial device problems (continued) v follow the suggested actions in the order in which they are listed in the action column until the problem is solved. V see chapter 5, “parts listing, system x3850 x6 and x3950 x6 types 3837 and 3839,” on page 205 to determi...

  • Page 212

    Table 52. Symptoms and user actions for serverguide problems (continued) v follow the suggested actions in the order in which they are listed in the action column until the problem is solved. V see chapter 5, “parts listing, system x3850 x6 and x3950 x6 types 3837 and 3839,” on page 205 to determine...

  • Page 213

    Table 53. Symptoms and user actions for server startup problems (continued) v follow the suggested actions in the order in which they are listed in the action column until the problem is solved. V see chapter 5, “parts listing, system x3850 x6 and x3950 x6 types 3837 and 3839,” on page 205 to determ...

  • Page 214

    Table 53. Symptoms and user actions for server startup problems (continued) v follow the suggested actions in the order in which they are listed in the action column until the problem is solved. V see chapter 5, “parts listing, system x3850 x6 and x3950 x6 types 3837 and 3839,” on page 205 to determ...

  • Page 215

    Universal serial bus (usb) port problems use this information to solve universal serial bus (usb) port problems. Table 55. Symptoms and user actions for usb port problems v follow the suggested actions in the order in which they are listed in the action column until the problem is solved. V see chap...

  • Page 216

    Results if the server does not start from the minimum configuration, see “power-supply leds” on page 165 to replace the components in the minimum configuration one at a time until the problem is isolated. Solving ethernet controller problems use this information to solve ethernet controller problems...

  • Page 217

    Solving undetermined problems use this information to solve undetermined problems. About this task if dynamic system analysis (dsa) did not diagnose the failure or if the server is inoperative, use the information in this section. If you suspect that a software problem is causing failures (continuou...

  • Page 218

    Problem determination tips this topic provides problem determination tips to help you solve server problems. Because of the variety of hardware and software combinations that you can encounter, use the following information to assist you in problem determination. The model number and machine type ar...

  • Page 219

    V uefi firmware level v imm firmware level v adapters and attachments, in the same locations v address jumpers, terminators, and cabling v software versions and levels v diagnostic program type and version level v setup utility settings v operating-system control-file setup see appendix d, “getting ...

  • Page 220

    In-band manual recovery method to recover the server firmware and restore the server operation to the primary bank, complete the following steps: procedure 1. Turn off the server, and disconnect all power cords and external cables. 2. Locate the sw1 switch block on the standard i/o book. Nmi button ...

  • Page 221

    Note: use this method if the standard i/o book board led is lit and there is a log entry or booting backup image is displayed on the firmware splash screen; otherwise, use the in-band manual recovery method. 1. Boot the server to an operating system that is supported by the firmware update package t...

  • Page 222

    Configuration and restart the server. If the server is unable to successfully complete post with the default configuration, there might be a problem with the system board. To specify the number of consecutive restart attempts in the setup utility that will trigger the nx boot failure feature, comple...

  • Page 223: 3837 And 3839

    Chapter 5. Parts listing, system x3850 x6 and x3950 x6 types 3837 and 3839 this topic provides information about list of server replaceable components. The following replaceable components are available for the system x3850 x6 and x3950 x6 types 3837 and 3839 server, except as specified otherwise in...

  • Page 224

    15 1 14 8 7 4 5 6 3 2 9 10 12 13 11 the following is an illustration of the components in the rear of the server: 16 17 18 19 20 23 24 21 22 the following is an illustration of the 8-socket chassis, midplane, and shuttle: 206 system x3850 x6 and x3950 x6 types 3837 and 3839: installation and service...

  • Page 225

    25 26 27 chapter 5. Parts listing, system x3850 x6 and x3950 x6 types 3837 and 3839 207.

  • Page 226

    Attention: do not install the nvidia grid k1 and k2, the nvidia tesla k20 and k40, and the nvidia quadro k4000 and k6000 adapter options in systems containing 1tb of system memory or more. If these options are installed in systems with 1tb of memory or more, it might cause undetected data corruption...

  • Page 227

    Table 56. Parts listing, types 3837 and 3839 (continued) index description cru part number (tier 1) cru part number (tier 2) fru part number self-encrypting drive (sed), 2.5-inch, sas gen3 hot-swap, 900 gb 10k, 6 gbps 00aj077 self-encrypting drive (sed), 2.5-inch, sas gen3 hot-swap, 600 gb 10k, 6 gb...

  • Page 228

    Table 56. Parts listing, types 3837 and 3839 (continued) index description cru part number (tier 1) cru part number (tier 2) fru part number solid state drive, enterprise value 1.8-inch, sata mlc 240 gb (for x3950 x6 8u) 00aj341 solid state drive, enterprise value 1.8-inch, sata mlc 480 gb (for x395...

  • Page 229

    Table 56. Parts listing, types 3837 and 3839 (continued) index description cru part number (tier 1) cru part number (tier 2) fru part number cables, front operator panel (included in part number 00d0333) cable management arm kit 95y4390 chassis handles kit 95y4384 eia trim bezel kit 95y4391 fillers ...

  • Page 230

    Table 56. Parts listing, types 3837 and 3839 (continued) index description cru part number (tier 1) cru part number (tier 2) fru part number microprocessor, 2.5 ghz, 37.5 mb, 130w, 15c, e7-8880 v2 44x4018 microprocessor, 2.2 ghz, 37.5 mb, 105w, 15c, e7-8880l v2 44x4038 microprocessor, 2.8 ghz, 37.5 ...

  • Page 231

    Table 56. Parts listing, types 3837 and 3839 (continued) index description cru part number (tier 1) cru part number (tier 2) fru part number nvidia quadro k6000 pci express x16 adapter note: do not install this adapter in systems containing 1tb of system memory or more. If this option is installed i...

  • Page 232

    Consumable parts this topic provides a list of server consumable parts. Consumable parts are not covered by the ibm statement of limited warranty. The following consumable parts are available for purchase from the retail store. Table 57. Consumable parts, type 3837 and 3839 index description part nu...

  • Page 233

    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, burkina fa...

  • Page 234

    Power cord part number used in these countries and regions 39m5076 110 - 120 v antigua and barbuda, aruba, bahamas, barbados, belize, bermuda, bolivia, caicos islands, canada, cayman islands, colombia, costa rica, cuba, dominican republic, ecuador, el salvador, guam, guatemala, haiti, honduras, jama...

  • Page 235

    Chapter 6. Removing and replacing components this topic provides information about removing and replacing a customer replaceable unit or a field replaceable unit. Note: the information and procedures in this documentation apply to both the 4-socket and the 8-socket configurations of the server, unle...

  • Page 236

    Removing and replacing server components this topic provides information about removing and replacing server components. This section provides information for removing and replacing components in the server. Note: the information and procedures in this documentation for removing and replacing compon...

  • Page 237

    Fan handle 4. Rotate the cam handle all the way down and slide the compute book out of the server. 5. Lay the compute book on its side, and press down on both blue touch points and slide the cover toward the rear of the ddr3 compute book. Attention: remove only one cover (on one side) at a time to p...

  • Page 238

    6. Lift the cover off and set it aside. Replacing the ddr3 compute book cover this information provides instructions on how to replace the ddr3 compute book covers. About this task the ddr3 compute book has a cover on the left side and a cover on the right side for access to the microprocessor and d...

  • Page 239

    Removing the standard i/o book use this information for instructions on how to remove the standard i/o book. Before you replace the standard i/o book, take the following steps to save data, firmware, and configuration data: v record all system configuration information, such as imm ip addresses, vit...

  • Page 240

    9. Remove any flash power modules (see “removing a raid adapter flash power module from the standard i/o book” on page 258). 10. Remove the fans (see “removing a hot-swap fan assembly” on page 251). 11. If you are instructed to return the module, follow all packaging instructions, and use any packag...

  • Page 241

    Handle handle standard i/o book 9. Rotate the handles all the way up until they are locked in place. 10. Reconnect the power cord and any cables that you removed. 11. Turn on the peripheral devices and the server. 12. Update the standard i/o book board with the latest firmware or restore the pre-exi...

  • Page 242

    4. Open the air baffle cover. Pull up on the air baffle top cover tab while pushing down on the bottom tab on the base of the air baffle to remove the cover. 5. Disconnect the flash power modules cables from the adapters and remove the flash power modules from the air baffle. 6. Rotate the air baffl...

  • Page 243

    Replacing the standard i/o book air baffle use this information for instructions on how to replace the standard i/o book air baffle. About this task the air baffle is located in the standard i/o book. To install the air baffle, complete the following steps: procedure 1. Align the tabs on the air baf...

  • Page 244

    Removing the half-length i/o book this information provides instructions for removing the half-length i/o book. About this task to remove the half-length i/o book, complete the following steps: procedure 1. Read the safety information and installation guidelines, see “safety” on page vii and “instal...

  • Page 245

    Replacing the half-length i/o book this information provides instructions for replacing the half-length i/o book. About this task note: v for notes and information that you must consider when install this i/o book, see “installing the half-length i/o book” on page 80. V if you are replacing the half...

  • Page 246

    Removing the full-length i/o book this information provides instructions for removing the full-length i/o book. About this task to remove the full-length i/o book, complete the following steps: procedure 1. Read the safety information and installation guidelines, see “safety” on page vii and “instal...

  • Page 247

    Replacing the full-length i/o book this information provides an overview of the full-length i/o book. About this task note: v for notes and information that you must consider when you install this i/o book, see “installing the full-length i/o book” on page 82. V if you are replacing the full-length ...

  • Page 248

    Removing an adapter use this information for instructions on how to remove an adapter. About this task to remove an adapter, complete the following steps: procedure 1. Read the safety information and installation guidelines, see “safety” on page vii and “installation guidelines” on page 45. 2. Turn ...

  • Page 249

    7. Close the adapter retention lever to secure the adapter in place. 8. Connect any cables to the adapter, if necessary. 9. Reinstall the i/o book in the server. 10. Perform any configuration tasks that are required for the adapter. 11. Reconnect the power cord and any cables (including external cab...

  • Page 250

    B. Grasp the orange and black release latch on the drive tray handle for the drive that you want to remove and slide the release latch down to unlock the drive-tray handle; then, rotate the drive tray handle to the right and the pull the handle toward you to slide the drive out of the bay. Lift the ...

  • Page 251

    V when you mix drive backplane configurations, all 1.8-inch ssd drive backplanes must be installed above the all 2.5-inch drive backplanes. See “drive ids” on page 71 for drive id assignment information and “supported sas/sata drive backplane configurations” on page 72 for information about the comb...

  • Page 252

    Drive tray assembly release latch 1.8-inch filler panel b. Push the drive into the drive bay and rotate the drive tray handle to the closed position and ensure that the latch is in the locked position. C. Reinstall the drive filler panel. 4. Check the drive status led to verify that the drive is ope...

  • Page 253

    Removing the 4x2.5-inch hot-swap drive backplanes use this information for instructions on how to remove the 4x2.5-inch hot-swap drive backplane assembly. About this task to remove the 2.5-inch hot-swap drive backplanes, complete the following steps: procedure 1. Read the safety information and inst...

  • Page 254

    8. If you are instructed to return the drive backplane, follow all packaging instructions, and use any packaging materials for shipping that are supplied to you. Replacing the 4x2.5-inch hot-swap drive backplanes use this information for instructions on how to replace the 4x2.5-inch hot-swap drive b...

  • Page 255

    Removing the 8x1.8-inch hot-swap drive backplane assembly use this information for instructions on how to remove the 8x1.8-inch hot-swap drive backplane assembly. About this task to remove the 8x1.8-inch hot-swap drive backplane assembly, complete the following steps: procedure 1. Read the safety in...

  • Page 256

    8. If you are instructed to return the drive backplane, follow all packaging instructions, and use any packaging materials for shipping that are supplied to you. Replacing the 8x1.8-inch hot-swap drive backplane assembly use this information for instructions on how to replace the 8x1.8-inch hot-swap...

  • Page 257

    Removing a memory module this topic provides instructions about how to remove a memory module. About this task to remove a dual inline memory module (dimm), complete the following steps: note: you can press the light path button on the compute book to light the leds on the board when the compute boo...

  • Page 258

    6. 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 module this topic provides instructions about how to replace a memory module. About this task note: v see “installing a memory mod...

  • Page 259

    Procedure 1. Touch the static-protective package that contains the dimm to any unpainted metal surface on the outside of the server. Then, remove the dimm from the package. 2. Open the retaining clip on each end of the dimm connector. Attention: to avoid breaking the retaining clips or damaging the ...

  • Page 260

    Removing the serveraid m5120 sas/sata controller for system x user this information for instructions on how to remove the serveraid m5120 sas/sata controller. About this task to remove a serveraid m5120 sas/sata adapter, complete the following steps: procedure 1. Read the safety information and inst...

  • Page 261

    See “supported raid adapters” on page 87 for more information. For configuration information, see the serveraid documentation at http://www.Ibm.Com/supportportal/. Attention: some cluster solutions require specific code levels or coordinated code updates. If the device is part of a cluster solution,...

  • Page 262

    6. Carefully grasp the adapter by the edges and pull it out of the connector on the storage book board. 7. If you are instructed to return the adapter, follow all packaging instructions, and use any packaging materials for shipping that are supplied to you. Replacing the n2215 sas/sata host bus adap...

  • Page 263

    Removing a usb embedded hypervisor flash device use this information for instructions on how to remove a usb hypervisor flash device. About this task to remove a usb embedded hypervisor flash device, complete the following steps: procedure 1. Read the safety information and installation guidelines, ...

  • Page 264

    6. If you are instructed to return the usb flash device, follow all packaging instructions, and use any packaging materials for shipping that are supplied to you. Replacing a usb embedded hypervisor flash device use this information for instructions on how to replace a usb hypervisor flash device. A...

  • Page 265

    Removing a 1400-watt or 900-watt hot-swap power supply use this information for instructions on how to remove a 1400-watt or 900-watt 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 power control b...

  • Page 266

    2. Removing a 1400-watt hot-swap power supply. A. Press and hold the orange release tab to the left. Grasp the handle and pull the power supply out of the server. 1400-watt ac power supply power supply release tab b. Set the power supply aside. C. Go to step 4. 3. Removing a 900-watt hot-swap power ...

  • Page 267

    The following notes describe the type of power supply that the server supports and other information that you must consider when you install a power supply: v you must use imm to set and change the power supply power policy and system power configurations. You can set and change the policies and con...

  • Page 268

    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 with one of these...

  • Page 269

    Filler panel spacer 900-watt ac power supply power supply release tab spacer release tab note: only install a spacer if one is not already installed. B. Grasp the handle on the rear of the power supply and slide the power supply forward into the power-supply bay until it clicks. Make sure that the p...

  • Page 270

    Fan-pack attention: to ensure proper operation, replace a failed hot-swap fan within 30 seconds. 4. If you are instructed to return the fan, follow all of the packaging instructions, and use any packaging materials for shipping that are supplied to you. Replacing a hot-swap fan assembly use this inf...

  • Page 271

    Table 59. Fan zones, fan number, and the components cooled by the fans (continued) fan zone fan-pack number components cooled by the fans 2 1 and 2 v compute book 1 v dimms connected to compute book 1 v voltage regulator for compute book 1 v the ml2 (ethernet) adapters (pcie slot 10) v pcie slot 9 3...

  • Page 272

    Fan-pack removing an ml2 (ethernet) adapter use this information for instructions on how to remove an ml2 (ethernet) adapter. About this task to remove an ml2 (ethernet) adapter, complete the following steps: procedure 1. Read the safety information and installation guidelines, see “safety” on page ...

  • Page 273

    Replacing an ml2 (ethernet) adapter use this information for instructions on how to remove an ml2 (ethernet) adapter. About this task the following are illustrations of the ml2 (ethernet) adapters that the server supports. See “supported ml2 (ethernet) adapters” on page 89 for more information about...

  • Page 274

    Intel x540 ml2 dual-port 10 gb-t ethernet adapter link led activity led link led activity led port 1 port 2 the following is an illustration of the emulex vfa5 ml2 dual-port 10 gb-sfp+ ethernet adapter for ibm system x: emulex vfa5 ml2 dual-port 10 gb-sfp+ ethernet adapter link led activity led acti...

  • Page 275

    Broadcom netxtremeii ml2 dual-port 10 gb-t ethernet adapter link led activity led link led activity led port 1 port 2 the following is an illustration of the broadcom netxtreme ii ml2 dual-port 10 gb-sfp+ ethernet adapter for ibm system x: broadcom netxtremeii ml2 dual-port 10 gb sfp+ ethernet adapt...

  • Page 276

    3. Align the edge connector on the adapter with the connector on the standard i/o book board. Press the edge of the connector firmly into the standard i/o book board connector and make sure that the adapter snaps into the connector securely. Attention: when you install an adapter, make sure that the...

  • Page 277

    5. Disconnect the flash power module cable from the adapter and remove the flash power module from the slot on the air baffle. Air baffle standard i/o book results if you are instructed to return the flash power module, follow all packaging instructions, and use any packaging materials for shipping ...

  • Page 278

    Replacing a raid adapter flash power module in the standard i/o book use this information for instructions on how to replace a raid adapter flash power module in the standard i/o book. About this task when you install raid adapters that come with flash power modules in the standard i/o book , instal...

  • Page 279

    Removing a raid cache card user this information for instructions on how to remove a raid cache card. About this task note: for additional information and notes about the adapters, see “installing an adapter” on page 84. To remove a raid cache card, complete the following steps: procedure 1. Read th...

  • Page 280

    8. Turn on the peripheral devices and the server. Removing the system battery user this information for instructions on how to remove the system battery. About this task the following notes describe information that you must consider when replacing the battery: v ibm has designed this product with y...

  • Page 281

    3. Remove the standard i/o book from the server (see “removing the standard i/o book” on page 221). 4. Remove the battery from the standard i/o book board: a. Use one finger to push the battery horizontally out of its housing. B. Use your thumb and index finger to lift the battery from the socket. 5...

  • Page 282

    To install the replacement battery on the standard i/o book board, complete the following steps: procedure 1. Follow any special handling and installation instructions that come with the replacement battery. 2. Install the new battery: a. Position the battery so that the positive (+) symbol is facin...

  • Page 283

    Front i/o panel storage book finger holes release latch 6. If you are instructed to return the front i/o panel assembly, follow all packaging instructions, and use any packaging materials for shipping that are supplied to you. Replacing the front i/o panel (usb/video) assembly use this information f...

  • Page 284

    Note: make sure that cables are installed correctly by using the keys on the connectors and the keys on the cables. Incorrect installation of the cables can damage the storage book. 4. Reinstall the storage book into the server. 5. Reconnect the power cords and any cables that you removed. 6. Turn o...

  • Page 285

    9. Remove the storage book board (see “removing the storage book board assembly” on page 268. 10. Remove the backplanes (see “removing the 4x2.5-inch hot-swap drive backplanes” on page 235 and “removing the 8x1.8-inch hot-swap drive backplane assembly” on page 237). 11. Remove the front operator pan...

  • Page 286

    Storage book 9. Rotate the cam handle all the way up and push it into the server until it locks in place. 10. Reinstall the drives in the front of the storage book. 11. Reconnect the power cord and any cables that you removed. 12. Turn on the peripheral devices and the server. Removing the storage b...

  • Page 287

    Storage book board assembly storage book 8. Open the adapter retention lever. 9. Remove the adapters from the storage book board assembly (see “removing an adapter” on page 230). 10. If you are instructed to return the board assembly, follow all packaging instructions, and use any packaging material...

  • Page 288

    Storage book board assembly storage book 2. Install the adapters (see “installing an adapter” on page 84). 3. Connect the cables to the adapters. 4. Connect the cables to the board assembly. 5. Close the adapter retention lever. 6. Align the storage book with the i/o bay on the server and slide it i...

  • Page 289

    5. Slide the blue release latch on top of the front operator panel back to remove the operator panel. Release latch lcd/operator panel 6. Turn the front operator panel over and disconnect the lcd system information display panel and the front operator panel cables. 7. If you are replacing the front ...

  • Page 290

    Replacing the front operator panel assembly use this information for instructions on how to replace the front operator panel. About this task to install the front operator panel, complete the following steps. Procedure 1. Reinstall the lcd system information display panel into the front operator pan...

  • Page 291

    6. Reconnect the front operator panel cables to the storage book board and the rear air baffle. Make sure that you reinstall the plug that your removed from the old assembly to the rear of the new air baffle. 7. Reinstall the storage book (see “replacing the storage book” on page 267). 8. Reconnect ...

  • Page 292

    8. If you are instructed to return the device, follow all packaging instructions, and use any packaging materials for shipping that are supplied to you. Replacing the lcd system information display panel use this information for instructions on how to replace the lcd system information display panel...

  • Page 293

    3. Reconnect the lcd display panel cable to the lcd display panel. 4. Reinstall the front operator panel release latch lcd/operator panel 5. Reconnect the front operator panel cable to the storage book board. 6. Reinstall the storage book in the server. 7. Reconnect the power cords and any cables th...

  • Page 294

    About this task attention: v be extremely careful, the microprocessor socket contacts are very fragile. 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 ...

  • Page 295

    6. After removal, place the heat sink on its side on a clean, flat surface. 7. Open the microprocessor socket release levers and microprocessor retainer. Attention: do not use any tools or sharp objects to lift the release levers on the microprocessor socket. Doing so might result in permanent damag...

  • Page 296

    Installation tool screws microprocessor c. Gently twist the handle on the installation tool clockwise to the closed position and lift the microprocessor out of the socket. 10. Place the microprocessor on a static-protective surface. Remove the microprocessor from the installation tool by twisting th...

  • Page 297

    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 do not touch the microprocessor contacts. Contaminants on the microprocessor contacts, such as oil from ...

  • Page 298

    E. Carefully align the microprocessor installation tool over the microprocessor socket. The microprocessor is keyed to ensure that the microprocessor is installed correctly. Installation tool screws microprocessor f. Twist the handle on the microprocessor tool counterclockwise to the open position (...

  • Page 299

    Note: v do not press the microprocessor into the socket. V do not touch the thermal grease on the bottom of the heat sink or on top of the microprocessor. Touching the thermal grease will contaminate it. V make sure that the microprocessor is oriented and aligned correctly in the socket before you c...

  • Page 300

    B. Align the screws on the heat sink with the holes on the heat sink retention module. Heatsink c. Press firmly on the center of the heat sink, then press firmly on the captive screws and tighten them with a screwdriver, alternating between the screws in a figure-8 pattern, as indicated on the heat ...

  • Page 301

    3. Use the cleaning pad to wipe the thermal grease from the bottom of the heat sink. Note: make sure that all of the thermal grease is removed. 4. Use a clean area of the cleaning pad to wipe the thermal grease from the microprocessor; then, dispose of the cleaning pad after all of the thermal greas...

  • Page 302

    Fan handle 5. Remove the ddr3 compute book covers. Press down on both blue touch points and slide the cover toward the rear of the ddr3 compute book. 6. Remove the microprocessor and heat sink (see “removing a microprocessor and heat sink” on page 275). 7. Remove the dimms (see “removing a memory mo...

  • Page 303

    V the 4-socket (x3850 x6) server supports ddr3 compute book configurations of two or four. These are the only configurations supported. The following tables list the installation sequence for the supported ddr3 compute book configurations. Table 60. Installation sequence for the two compute books co...

  • Page 304

    Table 63. Installation sequence for the six compute books configuration for an 8-socket server compute book top node (bay 1) top node (bay 2) top node (bay 3) top node (bay 4) bottom node (bay 1) bottom node (bay 2) bottom node (bay 3) bottom node (bay 4) 1 compute book 1 2 compute book 2 3 compute ...

  • Page 305

    5. Align the ddr3 compute book with the slot on the server and slide it in the server. Place one hand under the center of the compute book to support it while sliding it into the server. Fan-pack handle 6. Rotate the cam handle all the way up and push it into the server until it locks in place. 7. R...

  • Page 306

    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 problem with one ...

  • Page 307

    3. Turn off the circuit breaker(s) for the power supplies. 4. If the server is in a rack, at the back of the server, pull back the cable management arm to gain access to the rear of the server and the power supply. 5. Press and hold the orange release tab to the left. Grasp the power supply handle a...

  • Page 308

    V ibm service technicians are not certified or authorized to install or remove the 750-watt -48 v to -60 v dc power cable. You are responsible for ensuring that only a trained service technician install or remove the -48 v to -60 v dc power cable. V to reduce the risk of electric shock or energy haz...

  • Page 309

    Statement 31: danger electrical current from power, telephone, and communication cables is hazardous. To avoid a shock hazard: to disconnect: 1. Turn off all power sources and equipment that is to be attached to this product. For ac systems, remove all power cords from the chassis power receptacles ...

  • Page 310

    2. Make sure that the circuit breaker for the dc power supply is off. 3. Attach the dc power cable to the new power supply. Make sure that the power cable wires are connected securely to the -48 v, ground, and to the -48 v return terminals (as shown in the following illustration). Power input led po...

  • Page 311

    Removing the midplane use this information for instructions on how to remove the chassis midplane. About this task to remove the chassis midplane, complete the following steps: note: this procedure for removing the midplane apply to both the 4-socket and the 8-socket configurations of the server, un...

  • Page 312

    Midplane assembly alignment pins alignment pins shuttle results if you are instructed to return the midplane, follow all packaging instructions, and use any packaging materials for shipping that are supplied to you. Replacing the midplane use this information for instructions on how to replace the c...

  • Page 313

    Midplane assembly alignment pins alignment pins shuttle 2. Grasp the shuttle with your hand through the hole on the center of the shuttle and grasp the bottom of the shuttle with your other hand and align it with the shuttle slot; then, slide the shuttle into the chassis until it is seated firmly. 3...

  • Page 314

    Removing the shuttle use this information for instructions on how to remove the chassis shuttle. About this task to remove the chassis shuttle, complete the following steps: procedure 1. Read the safety information and installation guidelines, see “safety” on page vii and “installation guidelines” o...

  • Page 315

    B. Press the blue buttons on the interior wall of the top node shuttle to release the shuttle cam handles and rotate the handles all the way down. C. Now rotate the cam handles on the bottom node shuttle all the way down. Chapter 6. Removing and replacing components 297.

  • Page 316

    D. Grasp the shuttle with your hand through the hole on the center of the shuttle and grasp the bottom of the shuttle with your other hand and slide the shuttle out of the chassis. 6. Lift the midplane all the way up (off the alignment pins on the shuttle) and remove it from the shuttle. Midplane as...

  • Page 317

    Replacing the shuttle use this information for instructions on how to replace the chassis shuttle. About this task to replace the chassis shuttle, complete the following steps: note: this procedure is for both the 4u (4-socket) and 8u (8-socket) server configurations. Procedure 1. Reinstall the midp...

  • Page 318

    Illustration of the 8u shuttle: 3. Rotate the shuttle cam handles up until they lock in place on the chassis. 4. Reinstall all of the components in the rear of the server. 5. Slide the components in the front of the server back into the server. 6. Reconnect the power cords and any cables that you re...

  • Page 319

    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 320

    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 321

    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 322

    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 323

    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 324

    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 325

    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 326

    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 327

    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 328

    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 329

    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 330

    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 331

    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 332

    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 333

    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 334

    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 335

    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 336

    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 337

    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 338

    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 339

    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 340

    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 341

    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 342

    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 343

    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 344

    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 345

    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 346

    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 347

    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 348

    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 349

    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 350

    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 351

    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 352

    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 353

    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 354

    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 355

    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 356

    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 357

    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 358

    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 359

    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 360

    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 361

    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 362

    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 363

    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 364

    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 365

    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 366

    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 367

    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 368

    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 369

    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 370

    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 371

    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 372

    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 373

    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 374

    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 375

    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 376

    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 377

    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 378

    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 379

    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 380

    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 381

    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 382

    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 383

    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 384

    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 385

    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 386

    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 387

    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 388

    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 389

    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 390

    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 391

    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 392

    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 393

    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 394

    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 395

    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 396

    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 397

    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 398

    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 399

    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 400

    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 401

    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 402

    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 403

    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 404

    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 405

    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 406

    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 407

    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 408

    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 409

    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 410

    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 411

    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 412

    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 413

    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 414

    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 415

    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 416

    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 417

    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 418

    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 419

    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 420

    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 421

    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 422

    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 423

    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 424

    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 425

    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 426

    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 427

    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 428

    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 429

    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 430

    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 431

    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 432

    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 433

    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 434

    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 435

    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 436

    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 437

    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 438

    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 439

    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 440

    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 441

    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 442

    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 443

    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 444

    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 445

    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 446

    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 447

    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 448

    166-901-001 imm i2c test failed explanation: imm indicates failure in rtmm 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 449

    166-903-001 imm i2c test failed explanation: imm indicates failure in 9545a 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 disconn...

  • Page 450

    166-908-001 imm i2c test failed explanation: imm indicates failure in the 9545a bus (bus 7). 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 dis...

  • Page 451

    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 452

    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 453

    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 454

    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 455: Messages

    Appendix b. Integrated management module ii (imm2) error messages this topic provides a description of the fields that are displayed for the imm events. When a hardware event is detected by the imm on the server, the imm logs that event in the system-event log in the server. For each event code, the...

  • Page 456

    Cim information provides the prefix of the message id and the sequence number that is used by the cim message registry. Snmp trap id the snmp trap id that is found in the snmp alert management information base (mib). Automatically contact service if this field is set to yes, and you have enabled ele...

  • Page 457

    Table 65. Events that automatically notify support (continued) event id message string automatically notify support 8005010d-2b810003 [sensorelementname] is asserting predictive failure. Yes 8005010d-2b810004 [sensorelementname] is asserting predictive failure. Yes 8005010d-2b810005 [sensorelementna...

  • Page 458

    Table 65. Events that automatically notify support (continued) event id message string automatically notify support 8005010d-2b820002 [sensorelementname] is asserting predictive failure. Yes 8005010d-2b820003 [sensorelementname] is asserting predictive failure. Yes 8005010d-2b820004 [sensorelementna...

  • Page 459

    Table 65. Events that automatically notify support (continued) event id message string automatically notify support 8005010d-2b830001 [sensorelementname] is asserting predictive failure. Yes 8005010d-2b830002 [sensorelementname] is asserting predictive failure. Yes 8005010d-2b830003 [sensorelementna...

  • Page 460

    Table 65. Events that automatically notify support (continued) event id message string automatically notify support 8005010d-2b830018 [sensorelementname] is asserting predictive failure. Yes 8005010d-2b840001 [sensorelementname] is asserting predictive failure. Yes 8005010d-2b840002 [sensorelementna...

  • Page 461

    Table 65. Events that automatically notify support (continued) event id message string automatically notify support 8005010d-2b840017 [sensorelementname] is asserting predictive failure. Yes 8005010d-2b840018 [sensorelementname] is asserting predictive failure. Yes 806f0021-0b01ffff fault in slot [p...

  • Page 462

    Table 65. Events that automatically notify support (continued) event id message string automatically notify support 806f0021-0b0fffff fault in slot [physicalconnectorsystemelementname] on system [computersystemelementname]. Yes 806f0021-0b10ffff fault in slot [physicalconnectorsystemelementname] on ...

  • Page 463

    Table 65. Events that automatically notify support (continued) event id message string automatically notify support 806f010c-2b81000a uncorrectable error detected for [physicalmemoryelementname] on subsystem [memoryelementname]. Yes 806f010c-2b81000b uncorrectable error detected for [physicalmemorye...

  • Page 464

    Table 65. Events that automatically notify support (continued) event id message string automatically notify support 806f010c-2b820001 uncorrectable error detected for [physicalmemoryelementname] on subsystem [memoryelementname]. Yes 806f010c-2b820002 uncorrectable error detected for [physicalmemorye...

  • Page 465

    Table 65. Events that automatically notify support (continued) event id message string automatically notify support 806f010c-2b820011 uncorrectable error detected for [physicalmemoryelementname] on subsystem [memoryelementname]. Yes 806f010c-2b820012 uncorrectable error detected for [physicalmemorye...

  • Page 466

    Table 65. Events that automatically notify support (continued) event id message string automatically notify support 806f010c-2b830008 uncorrectable error detected for [physicalmemoryelementname] on subsystem [memoryelementname]. Yes 806f010c-2b830009 uncorrectable error detected for [physicalmemorye...

  • Page 467

    Table 65. Events that automatically notify support (continued) event id message string automatically notify support 806f010c-2b830018 uncorrectable error detected for [physicalmemoryelementname] on subsystem [memoryelementname]. Yes 806f010c-2b83ffff uncorrectable error detected for [physicalmemorye...

  • Page 468

    Table 65. Events that automatically notify support (continued) event id message string automatically notify support 806f010c-2b84000f uncorrectable error detected for [physicalmemoryelementname] on subsystem [memoryelementname]. Yes 806f010c-2b840010 uncorrectable error detected for [physicalmemorye...

  • Page 469

    Table 65. Events that automatically notify support (continued) event id message string automatically notify support 806f010d-0407ffff the [numericsensorelementname] has been disabled due to a detected fault. Yes 806f010d-0408ffff the [numericsensorelementname] has been disabled due to a detected fau...

  • Page 470

    Table 65. Events that automatically notify support (continued) event id message string automatically notify support 806f010d-2b81000f the [numericsensorelementname] has been disabled due to a detected fault. Yes 806f010d-2b810010 the [numericsensorelementname] has been disabled due to a detected fau...

  • Page 471

    Table 65. Events that automatically notify support (continued) event id message string automatically notify support 806f010d-2b82000d the [numericsensorelementname] has been disabled due to a detected fault. Yes 806f010d-2b82000e the [numericsensorelementname] has been disabled due to a detected fau...

  • Page 472

    Table 65. Events that automatically notify support (continued) event id message string automatically notify support 806f010d-2b83000b the [numericsensorelementname] has been disabled due to a detected fault. Yes 806f010d-2b83000c the [numericsensorelementname] has been disabled due to a detected fau...

  • Page 473

    Table 65. Events that automatically notify support (continued) event id message string automatically notify support 806f010d-2b840009 the [numericsensorelementname] has been disabled due to a detected fault. Yes 806f010d-2b84000a the [numericsensorelementname] has been disabled due to a detected fau...

  • Page 474

    Table 65. Events that automatically notify support (continued) event id message string automatically notify support 806f0207-0304ffff [processorelementname] has failed with frb1/bist condition. Yes 806f0207-2583ffff [processorelementname] has failed with frb1/bist condition. Yes 806f020d-0400ffff fa...

  • Page 475

    Table 65. Events that automatically notify support (continued) event id message string automatically notify support 806f020d-040effff failure predicted on [numericsensorelementname] for array [computersystemelementname]. Yes 806f020d-040fffff failure predicted on [numericsensorelementname] for array...

  • Page 476

    Table 65. Events that automatically notify support (continued) event id message string automatically notify support 806f020d-2b81080f failure predicted on [numericsensorelementname] for array [computersystemelementname]. Yes 806f020d-2b810810 failure predicted on [numericsensorelementname] for array...

  • Page 477

    Table 65. Events that automatically notify support (continued) event id message string automatically notify support 806f020d-2b820807 failure predicted on [numericsensorelementname] for array [computersystemelementname]. Yes 806f020d-2b820808 failure predicted on [numericsensorelementname] for array...

  • Page 478

    Table 65. Events that automatically notify support (continued) event id message string automatically notify support 806f020d-2b820817 failure predicted on [numericsensorelementname] for array [computersystemelementname]. Yes 806f020d-2b820818 failure predicted on [numericsensorelementname] for array...

  • Page 479

    Table 65. Events that automatically notify support (continued) event id message string automatically notify support 806f020d-2b83080f failure predicted on [numericsensorelementname] for array [computersystemelementname]. Yes 806f020d-2b830810 failure predicted on [numericsensorelementname] for array...

  • Page 480

    Table 65. Events that automatically notify support (continued) event id message string automatically notify support 806f020d-2b840807 failure predicted on [numericsensorelementname] for array [computersystemelementname]. Yes 806f020d-2b840808 failure predicted on [numericsensorelementname] for array...

  • Page 481

    Table 65. Events that automatically notify support (continued) event id message string automatically notify support 806f020d-2b840817 failure predicted on [numericsensorelementname] for array [computersystemelementname]. Yes 806f020d-2b840818 failure predicted on [numericsensorelementname] for array...

  • Page 482

    Table 65. Events that automatically notify support (continued) event id message string automatically notify support 806f050c-2b81000e memory logging limit reached for [physicalmemoryelementname] on subsystem [memoryelementname]. Yes 806f050c-2b81000f memory logging limit reached for [physicalmemorye...

  • Page 483

    Table 65. Events that automatically notify support (continued) event id message string automatically notify support 806f050c-2b820005 memory logging limit reached for [physicalmemoryelementname] on subsystem [memoryelementname]. Yes 806f050c-2b820006 memory logging limit reached for [physicalmemorye...

  • Page 484

    Table 65. Events that automatically notify support (continued) event id message string automatically notify support 806f050c-2b820015 memory logging limit reached for [physicalmemoryelementname] on subsystem [memoryelementname]. Yes 806f050c-2b820016 memory logging limit reached for [physicalmemorye...

  • Page 485

    Table 65. Events that automatically notify support (continued) event id message string automatically notify support 806f050c-2b83000c memory logging limit reached for [physicalmemoryelementname] on subsystem [memoryelementname]. Yes 806f050c-2b83000d memory logging limit reached for [physicalmemorye...

  • Page 486

    Table 65. Events that automatically notify support (continued) event id message string automatically notify support 806f050c-2b840003 memory logging limit reached for [physicalmemoryelementname] on subsystem [memoryelementname]. Yes 806f050c-2b840004 memory logging limit reached for [physicalmemorye...

  • Page 487

    Table 65. Events that automatically notify support (continued) event id message string automatically notify support 806f050c-2b840013 memory logging limit reached for [physicalmemoryelementname] on subsystem [memoryelementname]. Yes 806f050c-2b840014 memory logging limit reached for [physicalmemorye...

  • Page 488

    Table 65. Events that automatically notify support (continued) event id message string automatically notify support 806f060d-040dffff array [computersystemelementname] has failed. Yes 806f060d-040effff array [computersystemelementname] has failed. Yes 806f060d-040fffff array [computersystemelementna...

  • Page 489

    Table 65. Events that automatically notify support (continued) event id message string automatically notify support 8105010d-2b810012 [sensorelementname] is asserting predictive failure. Yes 8105010d-2b810013 [sensorelementname] is asserting predictive failure. Yes 8105010d-2b810014 [sensorelementna...

  • Page 490

    Table 65. Events that automatically notify support (continued) event id message string automatically notify support 8105010d-2b820011 [sensorelementname] is asserting predictive failure. Yes 8105010d-2b820012 [sensorelementname] is asserting predictive failure. Yes 8105010d-2b820013 [sensorelementna...

  • Page 491

    Table 65. Events that automatically notify support (continued) event id message string automatically notify support 8105010d-2b830010 [sensorelementname] is asserting predictive failure. Yes 8105010d-2b830011 [sensorelementname] is asserting predictive failure. Yes 8105010d-2b830012 [sensorelementna...

  • Page 492

    Table 65. Events that automatically notify support (continued) event id message string automatically notify support 8105010d-2b84000f [sensorelementname] is asserting predictive failure. Yes 8105010d-2b840010 [sensorelementname] is asserting predictive failure. Yes 8105010d-2b840011 [sensorelementna...

  • Page 493

    40000002-00000000 certificate authority [arg1] has detected a [arg2] certificate error. Explanation: a problem has occurred with the ssl server, ssl client, or ssl trusted ca certificate that has been imported into the imm. The imported certificate must contain a public key that corresponds to the k...

  • Page 494

    40000005-00000000 ethernet mtu setting modified from [arg1] to [arg2] by user [arg3]. Explanation: the specified user has changed the ethernet maximum transmission unit (mtu) setting of the integrated management module external network interface to the specified value. May also be shown as 400000050...

  • Page 495

    40000008-00000000 hostname set to [arg1] by user [arg2]. Explanation: the specified user has changed the integrated management module host name. May also be shown as 4000000800000000 or 0x4000000800000000 severity: info alert category: system - imm network event serviceable: no cim information: pref...

  • Page 496

    4000000b-00000000 ip address of default gateway modified from [arg1] to [arg2] by user [arg3]. Explanation: the specified user has changed the gateway address of the integrated management module external network interface to the specified value. May also be shown as 4000000b00000000 or 0x4000000b000...

  • Page 497

    4000000e-00000000 remote login successful. Login id: [arg1] from [arg2] at ip address [arg3]. Explanation: the specified user has logged in to the integrated management module. May also be shown as 4000000e00000000 or 0x4000000e00000000 severity: info alert category: system - remote login serviceabl...

  • Page 498

    40000011-00000000 security: login id: [arg1] had [arg2] login failures from cli at [arg3]. Explanation: a user has exceeded the maximum allowed number of unsuccessful login attempts from the command-line interface and has been prevented from logging in for the lockout period. May also be shown as 40...

  • Page 499

    40000014-00000000 the [arg1] on system [arg2] cleared by user [arg3]. Explanation: the specified user has deleted system log events or audit log events. May also be shown as 4000001400000000 or 0x4000001400000000 severity: info alert category: none serviceable: no cim information: prefix: imm and id...

  • Page 500

    40000017-00000000 enet[[arg1]] ip-cfg:hstname=[arg2], ip@=[arg3] ,netmsk=[arg4], gw@=[arg5] . Explanation: an imm ip address and configuration have been assigned using client data. May also be shown as 4000001700000000 or 0x4000001700000000 severity: info alert category: none serviceable: no cim inf...

  • Page 501

    4000001a-00000000 dhcp setting changed to [arg1] by user [arg2]. Explanation: the specified user has changed the dhcp setting of the integrated management module external network interface. May also be shown as 4000001a00000000 or 0x4000001a00000000 severity: info alert category: none serviceable: n...

  • Page 502

    4000001d-00000000 watchdog [arg1] failed to capture screen. Explanation: an operating-system error has occurred, and the screen capture failed. May also be shown as 4000001d00000000 or 0x4000001d00000000 severity: error alert category: system - other serviceable: no cim information: prefix: imm and ...

  • Page 503

    4000001f-00000000 please ensure that the management controller [arg1] is flashed with the correct firmware. The management controller is unable to match its firmware to the server. Explanation: the server does not support the installed imm firmware version. May also be shown as 4000001f00000000 or 0...

  • Page 504

    40000022-00000000 ssl data in the management controller [arg1] configuration data is invalid. Clearing configuration data region and disabling ssl. Explanation: there is a problem with the certificate that has been imported into the imm. The imported certificate must contain a public key that corres...

  • Page 505

    40000025-00000000 the [arg1] on system [arg2] is 75% full. Explanation: the imm event log is 75% full. When the event log is completely full, the new entries will overwrite the oldest entries. To avoid losing older log entries, save the log as a text file and clear the log. May also be shown as 4000...

  • Page 506

    40000028-00000000 management controller test alert generated by [arg1]. Explanation: the integrated management module has sent a test message to help verify connectivity. May also be shown as 4000002800000000 or 0x4000002800000000 severity: info alert category: system - other serviceable: no cim inf...

  • Page 507

    4000002b-00000000 domain name set to [arg1]. Explanation: domain name set by user may also be shown as 4000002b00000000 or 0x4000002b00000000 severity: info alert category: none serviceable: no cim information: prefix: imm and id: 0043 snmp trap id: automatically notify support: no user response: in...

  • Page 508

    4000002e-00000000 ddns registration successful. The domain name is [arg1]. Explanation: the ddns registration was successful. May also be shown as 4000002e00000000 or 0x4000002e00000000 severity: info alert category: none serviceable: no cim information: prefix: imm and id: 0046 snmp trap id: automa...

  • Page 509

    40000031-00000000 ipv6 static ip configuration enabled by user [arg1]. Explanation: the specified user has enabled ipv6 static address assignment on the integrated management module. May also be shown as 4000003100000000 or 0x4000003100000000 severity: info alert category: none serviceable: no cim i...

  • Page 510

    40000034-00000000 ipv6 static ip configuration disabled by user [arg1]. Explanation: the specified user has disabled ipv6 static address assignment on the integrated management module. May also be shown as 4000003400000000 or 0x4000003400000000 severity: info alert category: none serviceable: no cim...

  • Page 511

    40000037-00000000 enet[[arg1]] ipv6-linklocal:hstname=[arg2], ip@=[arg3], pref=[arg4] . Explanation: the ipv6 link-local address is active. May also be shown as 4000003700000000 or 0x4000003700000000 severity: info alert category: none serviceable: no cim information: prefix: imm and id: 0055 snmp t...

  • Page 512

    4000003a-00000000 ipv6 static address of network interface modified from [arg1] to [arg2] by user [arg3]. Explanation: a user modifies the ipv6 static address of a management controller may also be shown as 4000003a00000000 or 0x4000003a00000000 severity: info alert category: none serviceable: no ci...

  • Page 513

    4000003d-00000000 telnet port number changed from [arg1] to [arg2] by user [arg3]. Explanation: the specified user has changed the telnet port number. May also be shown as 4000003d00000000 or 0x4000003d00000000 severity: info alert category: none serviceable: no cim information: prefix: imm and id: ...

  • Page 514

    40000040-00000000 web-https port number changed from [arg1] to [arg2] by user [arg3]. Explanation: the specified user has changed the https port number. New https (secure web) connections must use the new port number. May also be shown as 4000004000000000 or 0x4000004000000000 severity: info alert c...

  • Page 515

    40000043-00000000 snmp agent port number changed from [arg1] to [arg2] by user [arg3]. Explanation: the specified user has changed the simple network management protocol (snmp) agent port number. May also be shown as 4000004300000000 or 0x4000004300000000 severity: info alert category: none servicea...

  • Page 516

    40000046-00000000 remote presence port number changed from [arg1] to [arg2] by user [arg3]. Explanation: a user has modified the remote presence port number may also be shown as 4000004600000000 or 0x4000004600000000 severity: info alert category: none serviceable: no cim information: prefix: imm an...

  • Page 517

    40000049-00000000 snmp [arg1] enabled by user [arg2] . Explanation: the specified user has enabled the snmpv1 or snmpv3 agent. May also be shown as 4000004900000000 or 0x4000004900000000 severity: info alert category: none serviceable: no cim information: prefix: imm and id: 0073 snmp trap id: autom...

  • Page 518

    4000004c-00000000 ldap server configuration set by user [arg1]: selectionmethod=[arg2], domainname=[arg3], server1=[arg4], server2=[arg5], server3=[arg6], server4=[arg7]. Explanation: a user changed the ldap server configuration may also be shown as 4000004c00000000 or 0x4000004c00000000 severity: i...

  • Page 519

    4000004f-00000000 date and time set by user [arg1]: date=[arg2], time-[arg3], dst auto-adjust=[arg4], timezone=[arg5]. Explanation: the specified user has changed the date and time in the integrated management module. May also be shown as 4000004f00000000 or 0x4000004f00000000 severity: info alert c...

  • Page 520

    40000052-00000000 server [arg1] scheduled for [arg2] at [arg3] by user [arg4]. Explanation: a user configured a server power action at a specific time may also be shown as 4000005200000000 or 0x4000005200000000 severity: info alert category: none serviceable: no cim information: prefix: imm and id: ...

  • Page 521

    40000055-00000000 synchronize time setting by user [arg1]: mode=[arg2], ntpserverhost=[arg3]:[arg4],ntpupdatefrequency=[arg5]. Explanation: a user configured the date and time synchronize settings may also be shown as 4000005500000000 or 0x4000005500000000 severity: info alert category: none service...

  • Page 522

    40000058-00000000 dns servers set by user [arg1]: useadditionalservers=[arg2], preferreddnstype=[arg3], ipv4server1=[arg4], ipv4server2=[arg5], ipv4server3=[arg6], ipv6server1=[arg7], ipv6server2=[arg8], ipv6server3=[arg9]. Explanation: the specified user has configured the dns servers. May also be ...

  • Page 523

    4000005b-00000000 secure web services (https) [arg1] by user [arg2]. Explanation: a user enables or disables secure web services may also be shown as 4000005b00000000 or 0x4000005b00000000 severity: info alert category: none serviceable: no cim information: prefix: imm and id: 0091 snmp trap id: aut...

  • Page 524

    4000005e-00000000 ssh [arg1] by user [arg2]. Explanation: the specified user has enabled or disabled the secure shell (ssh) service. May also be shown as 4000005e00000000 or 0x4000005e00000000 severity: info alert category: none serviceable: no cim information: prefix: imm and id: 0094 snmp trap id:...

  • Page 525

    40000061-00000000 license key for [arg1] removed by user [arg2]. Explanation: the specified user has removed an integrated management module license. Access to the specified feature is no longer allowed. May also be shown as 4000006100000000 or 0x4000006100000000 severity: info alert category: none ...

  • Page 526

    40000064-00000000 user [arg1] created. Explanation: a user account has been created. May also be shown as 4000006400000000 or 0x4000006400000000 severity: info alert category: none serviceable: no cim information: prefix: imm and id: 0100 snmp trap id: automatically notify support: no user response:...

  • Page 527

    40000067-00000000 user [arg1] role set to [arg2]. Explanation: a user account role assigned may also be shown as 4000006700000000 or 0x4000006700000000 severity: info alert category: none serviceable: no cim information: prefix: imm and id: 0103 snmp trap id: automatically notify support: no user re...

  • Page 528

    4000006a-00000000 ssh client key added for user [arg1]. Explanation: user locally defined an ssh client key may also be shown as 4000006a00000000 or 0x4000006a00000000 severity: info alert category: none serviceable: no cim information: prefix: imm and id: 0106 snmp trap id: automatically notify sup...

  • Page 529

    4000006d-00000000 management controller [arg1]: configuration saved to a file by user [arg2]. Explanation: a user saves a management controller configuration to a file. May also be shown as 4000006d00000000 or 0x4000006d00000000 severity: info alert category: none serviceable: no cim information: pr...

  • Page 530

    40000070-00000000 snmp traps enabled by user [arg1]: enabledalerts=[arg2], allowedfilters=[arg3] . Explanation: the specified user has enabled simple network management protocol (snmp) traps. May also be shown as 4000007000000000 or 0x4000007000000000 severity: info alert category: none serviceable:...

  • Page 531

    40000073-00000000 the maximum power cap value changed from [arg1] watts to [arg2] watts. Explanation: the maximum power cap value has been changed. May also be shown as 4000007300000000 or 0x4000007300000000 severity: info alert category: none serviceable: no cim information: prefix: imm and id: 011...

  • Page 532

    40000076-00000000 the new minimum power cap value exceeded the power cap value. Explanation: minimum power cap exceeds power cap may also be shown as 4000007600000000 or 0x4000007600000000 severity: warning alert category: warning - power serviceable: no cim information: prefix: imm and id: 0118 snm...

  • Page 533

    40000079-00000000 static power savings mode has been turned on by user [arg1]. Explanation: static power savings mode turned on by user may also be shown as 4000007900000000 or 0x4000007900000000 severity: info alert category: none serviceable: no cim information: prefix: imm and id: 0121 snmp trap ...

  • Page 534

    4000007c-00000000 dynamic power savings mode has been turned off by user [arg1]. Explanation: dynamic power savings mode turned off by user may also be shown as 4000007c00000000 or 0x4000007c00000000 severity: info alert category: none serviceable: no cim information: prefix: imm and id: 0124 snmp t...

  • Page 535

    4000007f-00000000 power cap throttling occurred. Explanation: power cap throttling has occurrred. May also be shown as 4000007f00000000 or 0x4000007f00000000 severity: info alert category: none serviceable: no cim information: prefix: imm and id: 0127 snmp trap id: automatically notify support: no u...

  • Page 536

    40000083-00000000 the new minimum power cap value has returned below the power cap value. Explanation: the new minimum power cap value has returned below the power cap value. May also be shown as 4000008300000000 or 0x4000008300000000 severity: info alert category: warning - power serviceable: no ci...

  • Page 537

    40000086-00000000 test call home generated by user [arg1]. Explanation: the specified user has generated a test automatic support notification. May also be shown as 4000008600000000 or 0x4000008600000000 severity: info alert category: none serviceable: no cim information: prefix: imm and id: 0134 sn...

  • Page 538

    40000089-00000000 management controller [arg1]: configuration restoration from a file by user [arg2] failed to complete. Explanation: restoration of the configuration of the specified management controller from a file by the specified user has not been completed. May also be shown as 400000890000000...

  • Page 539

    4000008b-00000000 one or more of the storage management ip addresses has changed. Explanation: this message is for the use case where an ip address for the storage management has changed may also be shown as 4000008b00000000 or 0x4000008b00000000 severity: info alert category: system - imm network e...

  • Page 540

    4000008e-00000000 device [arg1] vpd is not valid. Explanation: the vpd for a device is invalid may also be shown as 4000008e00000000 or 0x4000008e00000000 severity: warning alert category: system - other serviceable: no cim information: prefix: imm and id: 0142 snmp trap id: 22 automatically notify ...

  • Page 541

    40000091-00000000 user [arg1] has terminated an active console session. Explanation: a user has terminated an active console session may also be shown as 4000009100000000 or 0x4000009100000000 severity: info alert category: none serviceable: no cim information: prefix: imm and id: 0145 snmp trap id:...

  • Page 542

    40000094-00000000 user [arg1] has generated a new encryption key pair and installed a self-signed certificate for the tklm client. Explanation: user generated a new encryption key pair and installed a self-signed certificate for the tklm client may also be shown as 4000009400000000 or 0x400000940000...

  • Page 543

    40000097-00000000 user [arg1] has imported a server certificate for the tklm server. Explanation: user imported a server certificate for the tklm server may also be shown as 4000009700000000 or 0x4000009700000000 severity: info alert category: none serviceable: no cim information: prefix: imm and id...

  • Page 544

    4000009a-00000000 security: userid: [arg1] had [arg2] login failures from snmp client at ip address [arg3]. Explanation: this message is for the use case where a user has failed to access a management controller from snmp. May also be shown as 4000009a00000000 or 0x4000009a00000000 severity: info al...

  • Page 545

    4000009d-00000000 login id: [arg1] from [arg2] at ip address [arg3] has logged off. Explanation: this message is for the use case where a user has logged off of a management controller. May also be shown as 4000009d00000000 or 0x4000009d00000000 severity: info alert category: system - remote login s...

  • Page 546

    400000a0-00000000 user [arg1] has initiated an smtp server connection test. Explanation: user initiated an smtp server connection test. May also be shown as 400000a000000000 or 0x400000a000000000 severity: info alert category: none serviceable: no cim information: prefix: imm and id: 0160 snmp trap ...

  • Page 547

    80010002-2801ffff numeric sensor sysbrd vbat 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 - voltage serviceable: yes ...

  • Page 548

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

  • Page 549

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

  • Page 550

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

  • Page 551

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

  • Page 552

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

  • Page 553

    80010701-2701ffff numeric sensor [numericsensorelementname] going high (upper non-critical) has asserted. Explanation: imm has detected that the ambient temperature has risen above normal. May also be shown as 800107012701ffff or 0x800107012701ffff severity: warning alert category: warning - tempera...

  • Page 554

    80010901-2701ffff numeric sensor [numericsensorelementname] going high (upper critical) has asserted. Explanation: imm has detected that the ambient temperature has risen above its upper critical threshold. May also be shown as 800109012701ffff or 0x800109012701ffff severity: error alert category: c...

  • Page 555

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

  • Page 556

    80010b01-2d01ffff numeric sensor [numericsensorelementname] going high (upper non-recoverable) has asserted. Explanation: the pch temperature sensor has risen above its threshold. A hard shutdown has occurred. May also be shown as 80010b012d01ffff or 0x80010b012d01ffff severity: error alert category...

  • Page 557

    80030108-1381ffff sensor [sensorelementname] has asserted. Explanation: power supply load has reached normal limit. May also be shown as 800301081381ffff or 0x800301081381ffff severity: info alert category: system - other serviceable: no cim information: prefix: plat and id: 0508 snmp trap id: autom...

  • Page 558

    8003010f-2101ffff sensor [sensorelementname] has asserted. Explanation: this message is for the use case when an implementation has detected a sensor has asserted. May also be shown as 8003010f2101ffff or 0x8003010f2101ffff severity: info alert category: system - other serviceable: no cim informatio...

  • Page 559

    80040104-1d02ffff sensor [sensorelementname] is asserting predictive failure. Explanation: imm predicted fan 2 needs to be replaced to prevent a cooling failure. May also be shown as 800401041d02ffff or 0x800401041d02ffff severity: warning alert category: system - predicted failure serviceable: yes ...

  • Page 560

    80040104-1d05ffff sensor [sensorelementname] is asserting predictive failure. Explanation: imm predicted fan 5 needs to be replaced to prevent a cooling failure. May also be shown as 800401041d05ffff or 0x800401041d05ffff severity: warning alert category: system - predicted failure serviceable: yes ...

  • Page 561

    80040104-1d08ffff sensor [sensorelementname] is asserting predictive failure. Explanation: imm predicted fan 8 needs to be replaced to prevent a cooling failure. May also be shown as 800401041d08ffff or 0x800401041d08ffff severity: warning alert category: system - predicted failure serviceable: yes ...

  • Page 562

    8007000d-2582ffff sensor [sensorelementname] has transitioned to normal state. Explanation: this message is for the use case when an implementation has detected a sensor transition to the normal state. May also be shown as 8007000d2582ffff or 0x8007000d2582ffff severity: info alert category: warning...

  • Page 563

    V “server features and specifications” on page 7 80070101-0303ffff sensor [sensorelementname] has transitioned from normal to non-critical state. Explanation: a non-critical overtemp has been reported for the compute book 3. May also be shown as 800701010303ffff or 0x800701010303ffff severity: warni...

  • Page 564

    80070101-0b01ffff sensor [sensorelementname] has transitioned from normal to non-critical state. Explanation: this message is for the use case when an implementation has detected a sensor transitioned to non-critical from normal. May also be shown as 800701010b01ffff or 0x800701010b01ffff severity: ...

  • Page 565

    80070101-0b04ffff sensor [sensorelementname] has transitioned from normal to non-critical state. Explanation: this message is for the use case when an implementation has detected a sensor transitioned to non-critical from normal. May also be shown as 800701010b04ffff or 0x800701010b04ffff severity: ...

  • Page 566

    80070101-2c01ffff sensor [sensorelementname] has transitioned from normal to non-critical state. Explanation: the ml2 card has reported a non-critical over temperature condition. May also be shown as 800701012c01ffff or 0x800701012c01ffff severity: warning alert category: warning - temperature servi...

  • Page 567

    80070107-0302ffff sensor [sensorelementname] has transitioned from normal to non-critical state. Explanation: the compute book 2 has been removed from the system may also be shown as 800701070302ffff or 0x800701070302ffff severity: warning alert category: warning - other serviceable: yes cim informa...

  • Page 568

    80070107-2583ffff sensor [sensorelementname] has transitioned from normal to non-critical state. Explanation: how the cpu's are installed in the system does not match a supported configuration and may make cpu's inaccessible to the operating system and prevent boot. [cpu population] may also be show...

  • Page 569

    8007010d-2582ffff sensor [sensorelementname] has transitioned from normal to non-critical state. Explanation: this message is for the use case when an implementation has detected a sensor transitioned to non-critical from normal. May also be shown as 8007010d2582ffff or 0x8007010d2582ffff severity: ...

  • Page 570

    8007010d-2b810003 sensor [sensorelementname] has transitioned from normal to non-critical state. Explanation: the exflash ipmi proxy service has indicated exflash dimm 3 in compute book 1 has less than 1% write warranty remaining may also be shown as 8007010d2b810003 or 0x8007010d2b810003 severity: ...

  • Page 571

    8007010d-2b810006 sensor [sensorelementname] has transitioned from normal to non-critical state. Explanation: the exflash ipmi proxy service has indicated exflash dimm 6 in compute book 1 has less than 1% write warranty remaining may also be shown as 8007010d2b810006 or 0x8007010d2b810006 severity: ...

  • Page 572

    8007010d-2b810009 sensor [sensorelementname] has transitioned from normal to non-critical state. Explanation: the exflash ipmi proxy service has indicated exflash dimm 9 in compute book 1 has less than 1% write warranty remaining may also be shown as 8007010d2b810009 or 0x8007010d2b810009 severity: ...

  • Page 573

    8007010d-2b81000c sensor [sensorelementname] has transitioned from normal to non-critical state. Explanation: the exflash ipmi proxy service has indicated exflash dimm 12 in compute book 1 has less than 1% write warranty remaining may also be shown as 8007010d2b81000c or 0x8007010d2b81000c severity:...

  • Page 574

    8007010d-2b81000f sensor [sensorelementname] has transitioned from normal to non-critical state. Explanation: the exflash ipmi proxy service has indicated exflash dimm 15 in compute book 1 has less than 1% write warranty remaining may also be shown as 8007010d2b81000f or 0x8007010d2b81000f severity:...

  • Page 575

    8007010d-2b810012 sensor [sensorelementname] has transitioned from normal to non-critical state. Explanation: the exflash ipmi proxy service has indicated exflash dimm 18 in compute book 1 has less than 1% write warranty remaining may also be shown as 8007010d2b810012 or 0x8007010d2b810012 severity:...

  • Page 576

    8007010d-2b810015 sensor [sensorelementname] has transitioned from normal to non-critical state. Explanation: the exflash ipmi proxy service has indicated exflash dimm 21 in compute book 1 has less than 1% write warranty remaining may also be shown as 8007010d2b810015 or 0x8007010d2b810015 severity:...

  • Page 577

    8007010d-2b810018 sensor [sensorelementname] has transitioned from normal to non-critical state. Explanation: the exflash ipmi proxy service has indicated exflash dimm 24 in compute book 1 has less than 1% write warranty remaining may also be shown as 8007010d2b810018 or 0x8007010d2b810018 severity:...

  • Page 578

    8007010d-2b820002 sensor [sensorelementname] has transitioned from normal to non-critical state. Explanation: the exflash ipmi proxy service has indicated exflash dimm 2 in compute book 2 has less than 1% write warranty remaining may also be shown as 8007010d2b820002 or 0x8007010d2b820002 severity: ...

  • Page 579

    8007010d-2b820005 sensor [sensorelementname] has transitioned from normal to non-critical state. Explanation: the exflash ipmi proxy service has indicated exflash dimm 5 in compute book 2 has less than 1% write warranty remaining may also be shown as 8007010d2b820005 or 0x8007010d2b820005 severity: ...

  • Page 580

    8007010d-2b820008 sensor [sensorelementname] has transitioned from normal to non-critical state. Explanation: the exflash ipmi proxy service has indicated exflash dimm 8 in compute book 2 has less than 1% write warranty remaining may also be shown as 8007010d2b820008 or 0x8007010d2b820008 severity: ...

  • Page 581

    8007010d-2b82000b sensor [sensorelementname] has transitioned from normal to non-critical state. Explanation: the exflash ipmi proxy service has indicated exflash dimm 11 in compute book 2 has less than 1% write warranty remaining may also be shown as 8007010d2b82000b or 0x8007010d2b82000b severity:...

  • Page 582

    8007010d-2b82000e sensor [sensorelementname] has transitioned from normal to non-critical state. Explanation: the exflash ipmi proxy service has indicated exflash dimm 14 in compute book 2 has less than 1% write warranty remaining may also be shown as 8007010d2b82000e or 0x8007010d2b82000e severity:...

  • Page 583

    8007010d-2b820011 sensor [sensorelementname] has transitioned from normal to non-critical state. Explanation: the exflash ipmi proxy service has indicated exflash dimm 17 in compute book 2 has less than 1% write warranty remaining may also be shown as 8007010d2b820011 or 0x8007010d2b820011 severity:...

  • Page 584

    8007010d-2b820014 sensor [sensorelementname] has transitioned from normal to non-critical state. Explanation: the exflash ipmi proxy service has indicated exflash dimm 20 in compute book 2 has less than 1% write warranty remaining may also be shown as 8007010d2b820014 or 0x8007010d2b820014 severity:...

  • Page 585

    8007010d-2b820017 sensor [sensorelementname] has transitioned from normal to non-critical state. Explanation: the exflash ipmi proxy service has indicated exflash dimm 23 in compute book 2 has less than 1% write warranty remaining may also be shown as 8007010d2b820017 or 0x8007010d2b820017 severity:...

  • Page 586

    8007010d-2b830001 sensor [sensorelementname] has transitioned from normal to non-critical state. Explanation: the exflash ipmi proxy service has indicated exflash dimm 1 in compute book 3 has less than 1% write warranty remaining may also be shown as 8007010d2b830001 or 0x8007010d2b830001 severity: ...

  • Page 587

    8007010d-2b830004 sensor [sensorelementname] has transitioned from normal to non-critical state. Explanation: the exflash ipmi proxy service has indicated exflash dimm 4 in compute book 3 has less than 1% write warranty remaining may also be shown as 8007010d2b830004 or 0x8007010d2b830004 severity: ...

  • Page 588

    8007010d-2b830007 sensor [sensorelementname] has transitioned from normal to non-critical state. Explanation: the exflash ipmi proxy service has indicated exflash dimm 7 in compute book 3 has less than 1% write warranty remaining may also be shown as 8007010d2b830007 or 0x8007010d2b830007 severity: ...

  • Page 589

    8007010d-2b83000a sensor [sensorelementname] has transitioned from normal to non-critical state. Explanation: the exflash ipmi proxy service has indicated exflash dimm 10 in compute book 3 has less than 1% write warranty remaining may also be shown as 8007010d2b83000a or 0x8007010d2b83000a severity:...

  • Page 590

    8007010d-2b83000d sensor [sensorelementname] has transitioned from normal to non-critical state. Explanation: the exflash ipmi proxy service has indicated exflash dimm 13 in compute book 3 has less than 1% write warranty remaining may also be shown as 8007010d2b83000d or 0x8007010d2b83000d severity:...

  • Page 591

    8007010d-2b830010 sensor [sensorelementname] has transitioned from normal to non-critical state. Explanation: the exflash ipmi proxy service has indicated exflash dimm 16 in compute book 3 has less than 1% write warranty remaining may also be shown as 8007010d2b830010 or 0x8007010d2b830010 severity:...

  • Page 592

    8007010d-2b830013 sensor [sensorelementname] has transitioned from normal to non-critical state. Explanation: the exflash ipmi proxy service has indicated exflash dimm 19 in compute book 3 has less than 1% write warranty remaining may also be shown as 8007010d2b830013 or 0x8007010d2b830013 severity:...

  • Page 593

    8007010d-2b830016 sensor [sensorelementname] has transitioned from normal to non-critical state. Explanation: the exflash ipmi proxy service has indicated exflash dimm 22 in compute book 3 has less than 1% write warranty remaining may also be shown as 8007010d2b830016 or 0x8007010d2b830016 severity:...

  • Page 594

    8007010d-2b83ffff sensor [sensorelementname] has transitioned from normal to non-critical state. Explanation: the exflash ipmi proxy service has indicated compute book 3 contains an exflash dimm with less than 1% write warranty remaining may also be shown as 8007010d2b83ffff or 0x8007010d2b83ffff se...

  • Page 595

    8007010d-2b840003 sensor [sensorelementname] has transitioned from normal to non-critical state. Explanation: the exflash ipmi proxy service has indicated exflash dimm 3 in compute book 4 has less than 1% write warranty remaining may also be shown as 8007010d2b840003 or 0x8007010d2b840003 severity: ...

  • Page 596

    8007010d-2b840006 sensor [sensorelementname] has transitioned from normal to non-critical state. Explanation: the exflash ipmi proxy service has indicated exflash dimm 6 in compute book 4 has less than 1% write warranty remaining may also be shown as 8007010d2b840006 or 0x8007010d2b840006 severity: ...

  • Page 597

    8007010d-2b840009 sensor [sensorelementname] has transitioned from normal to non-critical state. Explanation: the exflash ipmi proxy service has indicated exflash dimm 9 in compute book 4 has less than 1% write warranty remaining may also be shown as 8007010d2b840009 or 0x8007010d2b840009 severity: ...

  • Page 598

    8007010d-2b84000c sensor [sensorelementname] has transitioned from normal to non-critical state. Explanation: the exflash ipmi proxy service has indicated exflash dimm 12 in compute book 4 has less than 1% write warranty remaining may also be shown as 8007010d2b84000c or 0x8007010d2b84000c severity:...

  • Page 599

    8007010d-2b84000f sensor [sensorelementname] has transitioned from normal to non-critical state. Explanation: the exflash ipmi proxy service has indicated exflash dimm 15 in compute book 4 has less than 1% write warranty remaining may also be shown as 8007010d2b84000f or 0x8007010d2b84000f severity:...

  • Page 600

    8007010d-2b840012 sensor [sensorelementname] has transitioned from normal to non-critical state. Explanation: the exflash ipmi proxy service has indicated exflash dimm 18 in compute book 4 has less than 1% write warranty remaining may also be shown as 8007010d2b840012 or 0x8007010d2b840012 severity:...

  • Page 601

    8007010d-2b840015 sensor [sensorelementname] has transitioned from normal to non-critical state. Explanation: the exflash ipmi proxy service has indicated exflash dimm 21 in compute book 4 has less than 1% write warranty remaining may also be shown as 8007010d2b840015 or 0x8007010d2b840015 severity:...

  • Page 602

    8007010d-2b840018 sensor [sensorelementname] has transitioned from normal to non-critical state. Explanation: the exflash ipmi proxy service has indicated exflash dimm 24 in compute book 4 has less than 1% write warranty remaining may also be shown as 8007010d2b840018 or 0x8007010d2b840018 severity:...

  • Page 603

    Gpt status : sec rollback err : secure boot err : 80070114-2201ffff sensor [sensorelementname] has transitioned from normal to non-critical state. Explanation: trusted platform module (tpm) event has transitioned to non critical state. May also be shown as 800701142201ffff or 0x800701142201ffff seve...

  • Page 604

    80070201-0302ffff sensor [sensorelementname] has transitioned to critical from a less severe state. Explanation: imm has detected compute book 2 has warmed to a critical temperature. May also be shown as 800702010302ffff or 0x800702010302ffff severity: error alert category: critical - temperature se...

  • Page 605

    80070201-0304ffff sensor [sensorelementname] has transitioned to critical from a less severe state. Explanation: imm has detected compute book 4 has warmed to a critical temperature. May also be shown as 800702010304ffff or 0x800702010304ffff severity: error alert category: critical - temperature se...

  • Page 606

    Telco sytems require all 4 power supplies to be populated and dc only. Related links: v “solving power problems” on page 197 v “installing power supplies” on page 104 v “removing a 1400-watt or 900-watt hot-swap power supply” on page 247 v “removing a 750-watt -48 volt to -60 volt dc power supply” o...

  • Page 607

    8007020f-2201ffff sensor [sensorelementname] has transitioned to critical from a less severe state. Explanation: the imm has reported a drive key fault or txt acm module fault. May also be shown as 8007020f2201ffff or 0x8007020f2201ffff severity: error alert category: critical - other serviceable: y...

  • Page 608

    80070219-0701ffff sensor [sensorelementname] has transitioned to critical from a less severe state. Explanation: the uefi detected a critical system board fault. May also be shown as 800702190701ffff or 0x800702190701ffff severity: error alert category: critical - other serviceable: yes cim informat...

  • Page 609

    8007021b-0302ffff sensor [sensorelementname] has transitioned to critical from a less severe state. Explanation: imm has reported a microprocessor 2 qpi link error. May also be shown as 8007021b0302ffff or 0x8007021b0302ffff severity: error alert category: critical - other serviceable: yes cim infor...

  • Page 610

    8007021b-0304ffff sensor [sensorelementname] has transitioned to critical from a less severe state. Explanation: imm has reported a microprocessor 4 qpi link error. May also be shown as 8007021b0304ffff or 0x8007021b0304ffff severity: error alert category: critical - other serviceable: yes cim infor...

  • Page 611

    80070221-1f01ffff sensor [sensorelementname] has transitioned to critical from a less severe state. Explanation: imm has reported microprocessor 1 has an external qpi link error. May also be shown as 800702211f01ffff or 0x800702211f01ffff severity: error alert category: critical - other serviceable:...

  • Page 612

    80070221-1f03ffff sensor [sensorelementname] has transitioned to critical from a less severe state. Explanation: imm has reported microprocessor 3 has an external qpi link error. May also be shown as 800702211f03ffff or 0x800702211f03ffff severity: error alert category: critical - other serviceable:...

  • Page 613

    80070221-2c01ffff sensor [sensorelementname] has transitioned to critical from a less severe state. Explanation: this message is for the use case when an implementation has detected a sensor transitioned to critical from less severe. May also be shown as 800702212c01ffff or 0x800702212c01ffff severi...

  • Page 614

    Related links: v “server features and specifications” on page 7 v “removing a microprocessor and heat sink” on page 275 v “replacing a microprocessor and heat sink” on page 278 v “thermal grease” on page 282 80070301-0302ffff sensor [sensorelementname] has transitioned to non-recoverable from a less...

  • Page 615

    3. Make sure that the room temperature is within operating specifications. 4. Make sure that the microprocessor 3 heat sink is securely installed. 5. (trained service technician only) make sure that the microprocessor 3 heat sink is installed correctly and the thermal material is correctly applied. ...

  • Page 616

    80070301-2c01ffff sensor [sensorelementname] has transitioned to non-recoverable from a less severe state. Explanation: the ml2 card has reported a non-recoverable over temperature condition. May also be shown as 800703012c01ffff or 0x800703012c01ffff severity: error alert category: critical - tempe...

  • Page 617

    80070319-2201ffff sensor s3 resume fail has transitioned to non-recoverable from a less severe state. Explanation: the s3 resume fail sesor has transitioned to non-recoverable from less severe. May also be shown as 800703192201ffff or 0x800703192201ffff severity: error alert category: critical - oth...

  • Page 618

    For a storage book vrd error: v replace storage book board. Related links: v “removing the standard i/o book” on page 221 v “replacing the standard i/o book” on page 222 v “removing the storage book” on page 266 v “replacing the storage book” on page 267 v “removing a ddr3 compute book” on page 283 ...

  • Page 619

    80070607-2b01ffff sensor [sensorelementname] has transitioned to non-recoverable. Explanation: the imm has detected compute book 1 is absent. This effects proper system cooling. May also be shown as 800706072b01ffff or 0x800706072b01ffff severity: error alert category: critical - other serviceable: ...

  • Page 620

    8007060f-2201ffff sensor [sensorelementname] has transitioned to non-recoverable. Explanation: trusted platform module (tpm) initialization error. May also be shown as 8007060f2201ffff or 0x8007060f2201ffff severity: error alert category: critical - other serviceable: yes cim information: prefix: pl...

  • Page 621

    80080025-2b01ffff device [logicaldeviceelementname] has been removed from unit [physicalpackageelementname]. Explanation: imm has detected the compute book 1 has been removed from the system. May also be shown as 800800252b01ffff or 0x800800252b01ffff severity: info alert category: system - other se...

  • Page 622

    80080025-2b03ffff device [logicaldeviceelementname] has been removed from unit [physicalpackageelementname]. Explanation: imm has detected the compute book 3 has been removed from the system. May also be shown as 800800252b03ffff or 0x800800252b03ffff severity: info alert category: system - other se...

  • Page 623

    80080025-2c01ffff device [logicaldeviceelementname] has been removed from unit [physicalpackageelementname]. Explanation: imm has detected the i/o book 1 is no longer present. Empty i/o bays do require a filler be installed for proper cooling. May also be shown as 800800252c01ffff or 0x800800252c01f...

  • Page 624

    80080125-2b01ffff device [logicaldeviceelementname] has been added. Explanation: imm has detected the compute book 1 has been added to the system. May also be shown as 800801252b01ffff or 0x800801252b01ffff severity: info alert category: system - other serviceable: no cim information: prefix: plat a...

  • Page 625

    80080125-2b04ffff device [logicaldeviceelementname] has been added. Explanation: imm has detected the compute book 4 has been added to the system. May also be shown as 800801252b04ffff or 0x800801252b04ffff severity: info alert category: system - other serviceable: no cim information: prefix: plat a...

  • Page 626

    80080128-2101ffff device [logicaldeviceelementname] has been added. Explanation: imm has detected low security jumper has been added. May also be shown as 800801282101ffff or 0x800801282101ffff severity: info alert category: system - other serviceable: no cim information: prefix: plat and id: 0536 s...

  • Page 627

    800b010a-1e81ffff redundancy lost for [redundancysetelementname] has asserted. Explanation: fan redundancy in zone 1 has been lost. May also be shown as 800b010a1e81ffff or 0x800b010a1e81ffff severity: error alert category: critical - fan failure serviceable: yes cim information: prefix: plat and id...

  • Page 628

    800b010a-1e83ffff redundancy lost for [redundancysetelementname] has asserted. Explanation: fan redundancy in zone 3 has been lost. May also be shown as 800b010a1e83ffff or 0x800b010a1e83ffff severity: error alert category: critical - fan failure serviceable: yes cim information: prefix: plat and id...

  • Page 629

    800b010a-1e85ffff redundancy lost for [redundancysetelementname] has asserted. Explanation: fan redundancy in zone 5 has been lost. May also be shown as 800b010a1e85ffff or 0x800b010a1e85ffff severity: error alert category: critical - fan failure serviceable: yes cim information: prefix: plat and id...

  • Page 630

    800b0208-1381ffff redundancy degraded for [redundancysetelementname] has asserted. Explanation: power unit is no longer in the redundant state. May also be shown as 800b02081381ffff or 0x800b02081381ffff severity: warning alert category: warning - redundant power supply serviceable: yes cim informat...

  • Page 631

    800b0309-1381ffff non-redundant:sufficient resources from redundancy degraded or fully redundant for [redundancysetelementname] has asserted. Explanation: power resource is supplying sufficient power but is no longer in a redundancy state. May also be shown as 800b03091381ffff or 0x800b03091381ffff ...

  • Page 632

    800b0508-1381ffff non-redundant:insufficient resources for [redundancysetelementname] has asserted. Explanation: power unit is no longer in the redundant state and no longer capable of providing the power needs to operate the system. May also be shown as 800b05081381ffff or 0x800b05081381ffff severi...

  • Page 633

    800b050a-1e81ffff non-redundant:insufficient resources for [redundancysetelementname] has asserted. Explanation: insufficient cooling provided by fan zone 1. May also be shown as 800b050a1e81ffff or 0x800b050a1e81ffff severity: error alert category: critical - fan failure serviceable: yes cim inform...

  • Page 634

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

  • Page 635

    800b050a-1e85ffff non-redundant:insufficient resources for [redundancysetelementname] has asserted. Explanation: insufficient cooling provided by fan zone 5. May also be shown as 800b050a1e85ffff or 0x800b050a1e85ffff severity: error alert category: critical - fan failure serviceable: yes cim inform...

  • Page 636

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

  • Page 637

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

  • Page 638

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

  • Page 639

    806f0008-0a04ffff [powersupplyelementname] has been added to container [physicalpackageelementname]. Explanation: imm has detected that power supply 4 has been added. May also be shown as 806f00080a04ffff or 0x806f00080a04ffff severity: info alert category: system - other serviceable: no cim informa...

  • Page 640

    806f000d-0401ffff the [numericsensorelementname] has been added. Explanation: hard drive 1 has been installed. May also be shown as 806f000d0401ffff or 0x806f000d0401ffff severity: info alert category: critical - hard disk drive serviceable: no cim information: prefix: plat and id: 0162 snmp trap id...

  • Page 641

    806f000d-0404ffff the [numericsensorelementname] has been added. Explanation: hard drive 4 has been installed. May also be shown as 806f000d0404ffff or 0x806f000d0404ffff severity: info alert category: critical - hard disk drive serviceable: no cim information: prefix: plat and id: 0162 snmp trap id...

  • Page 642

    806f000d-0407ffff the [numericsensorelementname] has been added. Explanation: hard drive 7 has been installed. May also be shown as 806f000d0407ffff or 0x806f000d0407ffff severity: info alert category: critical - hard disk drive serviceable: no cim information: prefix: plat and id: 0162 snmp trap id...

  • Page 643

    806f000d-040affff the [numericsensorelementname] has been added. Explanation: hard drive 10 has been installed. May also be shown as 806f000d040affff or 0x806f000d040affff severity: info alert category: critical - hard disk drive serviceable: no cim information: prefix: plat and id: 0162 snmp trap i...

  • Page 644

    806f000d-040dffff the [numericsensorelementname] has been added. Explanation: hard drive 13 has been installed. May also be shown as 806f000d040dffff or 0x806f000d040dffff severity: info alert category: critical - hard disk drive serviceable: no cim information: prefix: plat and id: 0162 snmp trap i...

  • Page 645

    806f000f-220101ff the system [computersystemelementname] has detected no memory in the system. Explanation: imm has reported that there is no memory (abr status, firmware error, sys boot status) in the system. May also be shown as 806f000f220101ff or 0x806f000f220101ff severity: error alert category...

  • Page 646

    Related links: v “finding the uefi (post) error code” on page 1666 806f000f-220104ff the system [computersystemelementname]has encountered a motherboard failure. Explanation: imm has reported a fatal system error (abr status, firmware error, sys boot status) in the system. May also be shown as 806f0...

  • Page 647

    806f000f-22010aff the system [computersystemelementname] encountered firmware error - no video device detected. Explanation: imm has reported that system firmware error no video device detected (abr status, firmware error, sys boot status) has occurred. May also be shown as 806f000f22010aff or 0x806...

  • Page 648

    806f000f-22010cff cpu voltage mismatch detected on [processorelementname]. Explanation: imm has reported a microprocessor voltage mismatch (abr status, firmware error, sys boot status) with the microprocessor socket voltage. May also be shown as 806f000f22010cff or 0x806f000f22010cff severity: error...

  • Page 649

    806f0013-1701ffff a diagnostic interrupt has occurred on system [computersystemelementname]. Explanation: the user has pressed the nmi button or there has been a malfunction with the button. May also be shown as 806f00131701ffff or 0x806f00131701ffff severity: error alert category: critical - other ...

  • Page 650

    806f0021-0b02ffff fault in slot [physicalconnectorsystemelementname] on system [computersystemelementname]. Explanation: imm has detected a fault in pcie slot 2. May also be shown as 806f00210b02ffff or 0x806f00210b02ffff severity: error alert category: critical - other serviceable: yes cim informat...

  • Page 651

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

  • Page 652

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

  • Page 653

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

  • Page 654

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

  • Page 655

    806f0021-0b0cffff fault in slot [physicalconnectorsystemelementname] on system [computersystemelementname]. Explanation: imm has detected a fault in pcie slot 12. May also be shown as 806f00210b0cffff or 0x806f00210b0cffff severity: error alert category: critical - other serviceable: yes cim informa...

  • Page 656

    806f0021-0b0effff fault in slot [physicalconnectorsystemelementname] on system [computersystemelementname]. Explanation: imm has detected a fault in pcie slot 17. May also be shown as 806f00210b0effff or 0x806f00210b0effff severity: error alert category: critical - other serviceable: yes cim informa...

  • Page 657

    806f0021-0b10ffff fault in slot [physicalconnectorsystemelementname] on system [computersystemelementname]. Explanation: imm has detected a fault in pcie slot 19. May also be shown as 806f00210b10ffff or 0x806f00210b10ffff severity: error alert category: critical - other serviceable: yes cim informa...

  • Page 658

    806f0021-2582ffff fault in slot [physicalconnectorsystemelementname] on system [computersystemelementname]. Explanation: imm has reported a fault in one of the pci slots or the pci bus without isolating the to a slot. May also be shown as 806f00212582ffff or 0x806f00212582ffff severity: error alert ...

  • Page 659

    806f002b-2101ffff a hardware change occurred on system [computersystemelementname]. Explanation: the scale config sensor reports a hardware changed occurred. May also be shown as 806f002b2101ffff or 0x806f002b2101ffff severity: info alert category: system - other serviceable: no cim information: pre...

  • Page 660

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

  • Page 661

    5. (trained service technician only) make sure that the microprocessor 3 heat sink is installed correctly and the thermal material is correctly applied. 6. (trained service technician only) replace microprocessor 3. Related links: v “server features and specifications” on page 7 v “removing a ddr3 c...

  • Page 662

    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 - power serviceable: yes cim information: prefix: plat and id: 0086 snmp trap id: 4 aut...

  • Page 663

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

  • Page 664

    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 - other serviceable: no cim information: prefix: plat and id: 0108 snmp trap id: automaticall...

  • Page 665

    806f010c-2b810002 uncorrectable error detected for [physicalmemoryelementname] on subsystem [memoryelementname]. Explanation: imm has reported a memory uncorrectable error on dimm 2 in compute book 1. May also be shown as 806f010c2b810002 or 0x806f010c2b810002 severity: error alert category: critica...

  • Page 666

    806f010c-2b810004 uncorrectable error detected for [physicalmemoryelementname] on subsystem [memoryelementname]. Explanation: imm has reported a memory uncorrectable error on dimm 4 in compute book 1. May also be shown as 806f010c2b810004 or 0x806f010c2b810004 severity: error alert category: critica...

  • Page 667

    806f010c-2b810006 uncorrectable error detected for [physicalmemoryelementname] on subsystem [memoryelementname]. Explanation: imm has reported a memory uncorrectable error on dimm 6 in compute book 1. May also be shown as 806f010c2b810006 or 0x806f010c2b810006 severity: error alert category: critica...

  • Page 668

    806f010c-2b810008 uncorrectable error detected for [physicalmemoryelementname] on subsystem [memoryelementname]. Explanation: imm has reported a memory uncorrectable error on dimm 8 in compute book 1. May also be shown as 806f010c2b810008 or 0x806f010c2b810008 severity: error alert category: critica...

  • Page 669

    806f010c-2b81000a uncorrectable error detected for [physicalmemoryelementname] on subsystem [memoryelementname]. Explanation: imm has reported a memory uncorrectable error on dimm 10 in compute book 1. May also be shown as 806f010c2b81000a or 0x806f010c2b81000a severity: error alert category: critic...

  • Page 670

    806f010c-2b81000c uncorrectable error detected for [physicalmemoryelementname] on subsystem [memoryelementname]. Explanation: imm has reported a memory uncorrectable error on dimm 12 in compute book 1. May also be shown as 806f010c2b81000c or 0x806f010c2b81000c severity: error alert category: critic...

  • Page 671

    806f010c-2b81000e uncorrectable error detected for [physicalmemoryelementname] on subsystem [memoryelementname]. Explanation: imm has reported a memory uncorrectable error on dimm 14 in compute book 1. May also be shown as 806f010c2b81000e or 0x806f010c2b81000e severity: error alert category: critic...

  • Page 672

    806f010c-2b810010 uncorrectable error detected for [physicalmemoryelementname] on subsystem [memoryelementname]. Explanation: imm has reported a memory uncorrectable error on dimm 16 in compute book 1. May also be shown as 806f010c2b810010 or 0x806f010c2b810010 severity: error alert category: critic...

  • Page 673

    806f010c-2b810012 uncorrectable error detected for [physicalmemoryelementname] on subsystem [memoryelementname]. Explanation: imm has reported a memory uncorrectable error on dimm 18 in compute book 1. May also be shown as 806f010c2b810012 or 0x806f010c2b810012 severity: error alert category: critic...

  • Page 674

    806f010c-2b810014 uncorrectable error detected for [physicalmemoryelementname] on subsystem [memoryelementname]. Explanation: imm has reported a memory uncorrectable error on dimm 20 in compute book 1. May also be shown as 806f010c2b810014 or 0x806f010c2b810014 severity: error alert category: critic...

  • Page 675

    806f010c-2b810016 uncorrectable error detected for [physicalmemoryelementname] on subsystem [memoryelementname]. Explanation: imm has reported a memory uncorrectable error on dimm 22 in compute book 1. May also be shown as 806f010c2b810016 or 0x806f010c2b810016 severity: error alert category: critic...

  • Page 676

    806f010c-2b810018 uncorrectable error detected for [physicalmemoryelementname] on subsystem [memoryelementname]. Explanation: imm has reported a memory uncorrectable error on dimm 24 in compute book 1. May also be shown as 806f010c2b810018 or 0x806f010c2b810018 severity: error alert category: critic...

  • Page 677

    806f010c-2b820001 uncorrectable error detected for [physicalmemoryelementname] on subsystem [memoryelementname]. Explanation: imm has reported a memory uncorrectable error on dimm 1 in compute book 2. May also be shown as 806f010c2b820001 or 0x806f010c2b820001 severity: error alert category: critica...

  • Page 678

    806f010c-2b820003 uncorrectable error detected for [physicalmemoryelementname] on subsystem [memoryelementname]. Explanation: imm has reported a memory uncorrectable error on dimm 3 in compute book 2. May also be shown as 806f010c2b820003 or 0x806f010c2b820003 severity: error alert category: critica...

  • Page 679

    806f010c-2b820005 uncorrectable error detected for [physicalmemoryelementname] on subsystem [memoryelementname]. Explanation: imm has reported a memory uncorrectable error on dimm 5 in compute book 2. May also be shown as 806f010c2b820005 or 0x806f010c2b820005 severity: error alert category: critica...

  • Page 680

    806f010c-2b820007 uncorrectable error detected for [physicalmemoryelementname] on subsystem [memoryelementname]. Explanation: imm has reported a memory uncorrectable error on dimm 7 in compute book 2. May also be shown as 806f010c2b820007 or 0x806f010c2b820007 severity: error alert category: critica...

  • Page 681

    806f010c-2b820009 uncorrectable error detected for [physicalmemoryelementname] on subsystem [memoryelementname]. Explanation: imm has reported a memory uncorrectable error on dimm 9 in compute book 2. May also be shown as 806f010c2b820009 or 0x806f010c2b820009 severity: error alert category: critica...

  • Page 682

    806f010c-2b82000b uncorrectable error detected for [physicalmemoryelementname] on subsystem [memoryelementname]. Explanation: imm has reported a memory uncorrectable error on dimm 11 in compute book 2. May also be shown as 806f010c2b82000b or 0x806f010c2b82000b severity: error alert category: critic...

  • Page 683

    806f010c-2b82000d uncorrectable error detected for [physicalmemoryelementname] on subsystem [memoryelementname]. Explanation: imm has reported a memory uncorrectable error on dimm 13 in compute book 2. May also be shown as 806f010c2b82000d or 0x806f010c2b82000d severity: error alert category: critic...

  • Page 684

    806f010c-2b82000f uncorrectable error detected for [physicalmemoryelementname] on subsystem [memoryelementname]. Explanation: imm has reported a memory uncorrectable error on dimm 15 in compute book 2. May also be shown as 806f010c2b82000f or 0x806f010c2b82000f severity: error alert category: critic...

  • Page 685

    806f010c-2b820011 uncorrectable error detected for [physicalmemoryelementname] on subsystem [memoryelementname]. Explanation: imm has reported a memory uncorrectable error on dimm 17 in compute book 2. May also be shown as 806f010c2b820011 or 0x806f010c2b820011 severity: error alert category: critic...

  • Page 686

    806f010c-2b820013 uncorrectable error detected for [physicalmemoryelementname] on subsystem [memoryelementname]. Explanation: imm has reported a memory uncorrectable error on dimm 19 in compute book 2. May also be shown as 806f010c2b820013 or 0x806f010c2b820013 severity: error alert category: critic...

  • Page 687

    806f010c-2b820015 uncorrectable error detected for [physicalmemoryelementname] on subsystem [memoryelementname]. Explanation: imm has reported a memory uncorrectable error on dimm 21 in compute book 2. May also be shown as 806f010c2b820015 or 0x806f010c2b820015 severity: error alert category: critic...

  • Page 688

    806f010c-2b820017 uncorrectable error detected for [physicalmemoryelementname] on subsystem [memoryelementname]. Explanation: imm has reported a memory uncorrectable error on dimm 23 in compute book 2. May also be shown as 806f010c2b820017 or 0x806f010c2b820017 severity: error alert category: critic...

  • Page 689

    806f010c-2b82ffff uncorrectable error detected for [physicalmemoryelementname] on subsystem [memoryelementname]. Explanation: imm has reported a memory uncorrectable error on compute book 2. May also be shown as 806f010c2b82ffff or 0x806f010c2b82ffff severity: error alert category: critical - memory...

  • Page 690

    806f010c-2b830002 uncorrectable error detected for [physicalmemoryelementname] on subsystem [memoryelementname]. Explanation: imm has reported a memory uncorrectable error on dimm 2 in compute book 3. May also be shown as 806f010c2b830002 or 0x806f010c2b830002 severity: error alert category: critica...

  • Page 691

    806f010c-2b830004 uncorrectable error detected for [physicalmemoryelementname] on subsystem [memoryelementname]. Explanation: imm has reported a memory uncorrectable error on dimm 4 in compute book 3. May also be shown as 806f010c2b830004 or 0x806f010c2b830004 severity: error alert category: critica...

  • Page 692

    806f010c-2b830006 uncorrectable error detected for [physicalmemoryelementname] on subsystem [memoryelementname]. Explanation: imm has reported a memory uncorrectable error on dimm 6 in compute book 3. May also be shown as 806f010c2b830006 or 0x806f010c2b830006 severity: error alert category: critica...

  • Page 693

    806f010c-2b830008 uncorrectable error detected for [physicalmemoryelementname] on subsystem [memoryelementname]. Explanation: imm has reported a memory uncorrectable error on dimm 8 in compute book 3. May also be shown as 806f010c2b830008 or 0x806f010c2b830008 severity: error alert category: critica...

  • Page 694

    806f010c-2b83000a uncorrectable error detected for [physicalmemoryelementname] on subsystem [memoryelementname]. Explanation: imm has reported a memory uncorrectable error on dimm 10 in compute book 3. May also be shown as 806f010c2b83000a or 0x806f010c2b83000a severity: error alert category: critic...

  • Page 695

    806f010c-2b83000c uncorrectable error detected for [physicalmemoryelementname] on subsystem [memoryelementname]. Explanation: imm has reported a memory uncorrectable error on dimm 12 in compute book 3. May also be shown as 806f010c2b83000c or 0x806f010c2b83000c severity: error alert category: critic...

  • Page 696

    806f010c-2b83000e uncorrectable error detected for [physicalmemoryelementname] on subsystem [memoryelementname]. Explanation: imm has reported a memory uncorrectable error on dimm 14 in compute book 3. May also be shown as 806f010c2b83000e or 0x806f010c2b83000e severity: error alert category: critic...

  • Page 697

    806f010c-2b830010 uncorrectable error detected for [physicalmemoryelementname] on subsystem [memoryelementname]. Explanation: imm has reported a memory uncorrectable error on dimm 16 in compute book 3. May also be shown as 806f010c2b830010 or 0x806f010c2b830010 severity: error alert category: critic...

  • Page 698

    806f010c-2b830012 uncorrectable error detected for [physicalmemoryelementname] on subsystem [memoryelementname]. Explanation: imm has reported a memory uncorrectable error on dimm 18 in compute book 3. May also be shown as 806f010c2b830012 or 0x806f010c2b830012 severity: error alert category: critic...

  • Page 699

    806f010c-2b830014 uncorrectable error detected for [physicalmemoryelementname] on subsystem [memoryelementname]. Explanation: imm has reported a memory uncorrectable error on dimm 20 in compute book 3. May also be shown as 806f010c2b830014 or 0x806f010c2b830014 severity: error alert category: critic...

  • Page 700

    806f010c-2b830016 uncorrectable error detected for [physicalmemoryelementname] on subsystem [memoryelementname]. Explanation: imm has reported a memory uncorrectable error on dimm 22 in compute book 3. May also be shown as 806f010c2b830016 or 0x806f010c2b830016 severity: error alert category: critic...

  • Page 701

    806f010c-2b830018 uncorrectable error detected for [physicalmemoryelementname] on subsystem [memoryelementname]. Explanation: imm has reported a memory uncorrectable error on dimm 24 in compute book 3. May also be shown as 806f010c2b830018 or 0x806f010c2b830018 severity: error alert category: critic...

  • Page 702

    806f010c-2b840001 uncorrectable error detected for [physicalmemoryelementname] on subsystem [memoryelementname]. Explanation: imm has reported a memory uncorrectable error on dimm 1 in compute book 4. May also be shown as 806f010c2b840001 or 0x806f010c2b840001 severity: error alert category: critica...

  • Page 703

    806f010c-2b840003 uncorrectable error detected for [physicalmemoryelementname] on subsystem [memoryelementname]. Explanation: imm has reported a memory uncorrectable error on dimm 3 in compute book 4. May also be shown as 806f010c2b840003 or 0x806f010c2b840003 severity: error alert category: critica...

  • Page 704

    806f010c-2b840005 uncorrectable error detected for [physicalmemoryelementname] on subsystem [memoryelementname]. Explanation: imm has reported a memory uncorrectable error on dimm 5 in compute book 4. May also be shown as 806f010c2b840005 or 0x806f010c2b840005 severity: error alert category: critica...

  • Page 705

    806f010c-2b840007 uncorrectable error detected for [physicalmemoryelementname] on subsystem [memoryelementname]. Explanation: imm has reported a memory uncorrectable error on dimm 7 in compute book 4. May also be shown as 806f010c2b840007 or 0x806f010c2b840007 severity: error alert category: critica...

  • Page 706

    806f010c-2b840009 uncorrectable error detected for [physicalmemoryelementname] on subsystem [memoryelementname]. Explanation: imm has reported a memory uncorrectable error on dimm 9 in compute book 4. May also be shown as 806f010c2b840009 or 0x806f010c2b840009 severity: error alert category: critica...

  • Page 707

    806f010c-2b84000b uncorrectable error detected for [physicalmemoryelementname] on subsystem [memoryelementname]. Explanation: imm has reported a memory uncorrectable error on dimm 11 in compute book 4. May also be shown as 806f010c2b84000b or 0x806f010c2b84000b severity: error alert category: critic...

  • Page 708

    806f010c-2b84000d uncorrectable error detected for [physicalmemoryelementname] on subsystem [memoryelementname]. Explanation: imm has reported a memory uncorrectable error on dimm 13 in compute book 4. May also be shown as 806f010c2b84000d or 0x806f010c2b84000d severity: error alert category: critic...

  • Page 709

    806f010c-2b84000f uncorrectable error detected for [physicalmemoryelementname] on subsystem [memoryelementname]. Explanation: imm has reported a memory uncorrectable error on dimm 15 in compute book 4. May also be shown as 806f010c2b84000f or 0x806f010c2b84000f severity: error alert category: critic...

  • Page 710

    806f010c-2b840011 uncorrectable error detected for [physicalmemoryelementname] on subsystem [memoryelementname]. Explanation: imm has reported a memory uncorrectable error on dimm 17 in compute book 4. May also be shown as 806f010c2b840011 or 0x806f010c2b840011 severity: error alert category: critic...

  • Page 711

    806f010c-2b840013 uncorrectable error detected for [physicalmemoryelementname] on subsystem [memoryelementname]. Explanation: imm has reported a memory uncorrectable error on dimm 19 in compute book 4. May also be shown as 806f010c2b840013 or 0x806f010c2b840013 severity: error alert category: critic...

  • Page 712

    806f010c-2b840015 uncorrectable error detected for [physicalmemoryelementname] on subsystem [memoryelementname]. Explanation: imm has reported a memory uncorrectable error on dimm 21 in compute book 4. May also be shown as 806f010c2b840015 or 0x806f010c2b840015 severity: error alert category: critic...

  • Page 713

    806f010c-2b840017 uncorrectable error detected for [physicalmemoryelementname] on subsystem [memoryelementname]. Explanation: imm has reported a memory uncorrectable error on dimm 23 in compute book 4. May also be shown as 806f010c2b840017 or 0x806f010c2b840017 severity: error alert category: critic...

  • Page 714

    806f010c-2b84ffff uncorrectable error detected for [physicalmemoryelementname] on subsystem [memoryelementname]. Explanation: imm has reported a memory uncorrectable error on compute book 4. May also be shown as 806f010c2b84ffff or 0x806f010c2b84ffff severity: error alert category: critical - memory...

  • Page 715

    806f010d-0401ffff the [numericsensorelementname] has been disabled due to a detected fault. Explanation: the drive 1 has been disabled (defunct) due to a fault detected by the controller. May also be shown as 806f010d0401ffff or 0x806f010d0401ffff severity: error alert category: critical - hard disk...

  • Page 716

    806f010d-0403ffff the [numericsensorelementname] has been disabled due to a detected fault. Explanation: the drive 3 has been disabled (defunct) due to a fault detected by the controller. May also be shown as 806f010d0403ffff or 0x806f010d0403ffff severity: error alert category: critical - hard disk...

  • Page 717

    806f010d-0405ffff the [numericsensorelementname] has been disabled due to a detected fault. Explanation: the drive 5 has been disabled (defunct) due to a fault detected by the controller. May also be shown as 806f010d0405ffff or 0x806f010d0405ffff severity: error alert category: critical - hard disk...

  • Page 718

    806f010d-0407ffff the [numericsensorelementname] has been disabled due to a detected fault. Explanation: the drive 7 has been disabled (defunct) due to a fault detected by the controller. May also be shown as 806f010d0407ffff or 0x806f010d0407ffff severity: error alert category: critical - hard disk...

  • Page 719

    806f010d-0409ffff the [numericsensorelementname] has been disabled due to a detected fault. Explanation: the drive 9 has been disabled (defunct) due to a fault detected by the controller. May also be shown as 806f010d0409ffff or 0x806f010d0409ffff severity: error alert category: critical - hard disk...

  • Page 720

    806f010d-040bffff the [numericsensorelementname] has been disabled due to a detected fault. Explanation: the drive 11 has been disabled (defunct) due to a fault detected by the controller. May also be shown as 806f010d040bffff or 0x806f010d040bffff severity: error alert category: critical - hard dis...

  • Page 721

    806f010d-040dffff the [numericsensorelementname] has been disabled due to a detected fault. Explanation: the drive 13 has been disabled (defunct) due to a fault detected by the controller. May also be shown as 806f010d040dffff or 0x806f010d040dffff severity: error alert category: critical - hard dis...

  • Page 722

    806f010d-040fffff the [numericsensorelementname] has been disabled due to a detected fault. Explanation: the drive 15 has been disabled (defunct) due to a fault detected by the controller. May also be shown as 806f010d040fffff or 0x806f010d040fffff severity: error alert category: critical - hard dis...

  • Page 723

    V “removing the ddr3 compute book cover” on page 218 v “replacing the ddr3 compute book cover” on page 220 v “removing a memory module” on page 239 v “replacing a memory module” on page 240 v “flash dimms” on page 51 806f010d-2b810002 the [numericsensorelementname] has been disabled due to a detecte...

  • Page 724

    806f010d-2b810003 the [numericsensorelementname] has been disabled due to a detected fault. Explanation: the exflash proxy service detected a fault on the exflash dimm 3 in compute book 1. May also be shown as 806f010d2b810003 or 0x806f010d2b810003 severity: error alert category: critical - hard dis...

  • Page 725

    4. If the node has recently been installed, moved, serviced, or upgraded, verify that the exflash dimm is properly seated and visually verify that there is no foreign material in any dimm connector on that memory channel. If either of these conditions is found, correct and retry with the same exflas...

  • Page 726

    V “removing a memory module” on page 239 v “replacing a memory module” on page 240 v “flash dimms” on page 51 806f010d-2b810006 the [numericsensorelementname] has been disabled due to a detected fault. Explanation: the exflash proxy service detected a fault on the exflash dimm 6 in compute book 1. M...

  • Page 727

    806f010d-2b810007 the [numericsensorelementname] has been disabled due to a detected fault. Explanation: the exflash proxy service detected a fault on the exflash dimm 7 in compute book 1. May also be shown as 806f010d2b810007 or 0x806f010d2b810007 severity: error alert category: critical - hard dis...

  • Page 728

    4. If the node has recently been installed, moved, serviced, or upgraded, verify that the exflash dimm is properly seated and visually verify that there is no foreign material in any dimm connector on that memory channel. If either of these conditions is found, correct and retry with the same exflas...

  • Page 729

    V “removing a memory module” on page 239 v “replacing a memory module” on page 240 v “flash dimms” on page 51 806f010d-2b81000a the [numericsensorelementname] has been disabled due to a detected fault. Explanation: the exflash proxy service detected a fault on the exflash dimm 10 in compute book 1. ...

  • Page 730

    806f010d-2b81000b the [numericsensorelementname] has been disabled due to a detected fault. Explanation: the exflash proxy service detected a fault on the exflash dimm 11 in compute book 1. May also be shown as 806f010d2b81000b or 0x806f010d2b81000b severity: error alert category: critical - hard di...

  • Page 731

    4. If the node has recently been installed, moved, serviced, or upgraded, verify that the exflash dimm is properly seated and visually verify that there is no foreign material in any dimm connector on that memory channel. If either of these conditions is found, correct and retry with the same exflas...

  • Page 732

    V “removing a memory module” on page 239 v “replacing a memory module” on page 240 v “flash dimms” on page 51 806f010d-2b81000e the [numericsensorelementname] has been disabled due to a detected fault. Explanation: the exflash proxy service detected a fault on the exflash dimm 14 in compute book 1. ...

  • Page 733

    806f010d-2b81000f the [numericsensorelementname] has been disabled due to a detected fault. Explanation: the exflash proxy service detected a fault on the exflash dimm 15 in compute book 1. May also be shown as 806f010d2b81000f or 0x806f010d2b81000f severity: error alert category: critical - hard di...

  • Page 734

    4. If the node has recently been installed, moved, serviced, or upgraded, verify that the exflash dimm is properly seated and visually verify that there is no foreign material in any dimm connector on that memory channel. If either of these conditions is found, correct and retry with the same exflas...

  • Page 735

    V “removing a memory module” on page 239 v “replacing a memory module” on page 240 v “flash dimms” on page 51 806f010d-2b810012 the [numericsensorelementname] has been disabled due to a detected fault. Explanation: the exflash proxy service detected a fault on the exflash dimm 18 in compute book 1. ...

  • Page 736

    806f010d-2b810013 the [numericsensorelementname] has been disabled due to a detected fault. Explanation: the exflash proxy service detected a fault on the exflash dimm 19 in compute book 1. May also be shown as 806f010d2b810013 or 0x806f010d2b810013 severity: error alert category: critical - hard di...

  • Page 737

    4. If the node has recently been installed, moved, serviced, or upgraded, verify that the exflash dimm is properly seated and visually verify that there is no foreign material in any dimm connector on that memory channel. If either of these conditions is found, correct and retry with the same exflas...

  • Page 738

    V “removing a memory module” on page 239 v “replacing a memory module” on page 240 v “flash dimms” on page 51 806f010d-2b810016 the [numericsensorelementname] has been disabled due to a detected fault. Explanation: the exflash proxy service detected a fault on the exflash dimm 22 in compute book 1. ...

  • Page 739

    806f010d-2b810017 the [numericsensorelementname] has been disabled due to a detected fault. Explanation: the exflash proxy service detected a fault on the exflash dimm 23 in compute book 1. May also be shown as 806f010d2b810017 or 0x806f010d2b810017 severity: error alert category: critical - hard di...

  • Page 740

    4. If the node has recently been installed, moved, serviced, or upgraded, verify that the exflash dimm is properly seated and visually verify that there is no foreign material in any dimm connector on that memory channel. If either of these conditions is found, correct and retry with the same exflas...

  • Page 741

    V “removing a memory module” on page 239 v “replacing a memory module” on page 240 v “flash dimms” on page 51 806f010d-2b820002 the [numericsensorelementname] has been disabled due to a detected fault. Explanation: the exflash proxy service detected a fault on the exflash dimm 2 in compute book 2. M...

  • Page 742

    806f010d-2b820003 the [numericsensorelementname] has been disabled due to a detected fault. Explanation: the exflash proxy service detected a fault on the exflash dimm 3 in compute book 2. May also be shown as 806f010d2b820003 or 0x806f010d2b820003 severity: error alert category: critical - hard dis...

  • Page 743

    4. If the node has recently been installed, moved, serviced, or upgraded, verify that the exflash dimm is properly seated and visually verify that there is no foreign material in any dimm connector on that memory channel. If either of these conditions is found, correct and retry with the same exflas...

  • Page 744

    V “removing a memory module” on page 239 v “replacing a memory module” on page 240 v “flash dimms” on page 51 806f010d-2b820006 the [numericsensorelementname] has been disabled due to a detected fault. Explanation: the exflash proxy service detected a fault on the exflash dimm 6 in compute book 2. M...

  • Page 745

    806f010d-2b820007 the [numericsensorelementname] has been disabled due to a detected fault. Explanation: the exflash proxy service detected a fault on the exflash dimm 7 in compute book 2. May also be shown as 806f010d2b820007 or 0x806f010d2b820007 severity: error alert category: critical - hard dis...

  • Page 746

    4. If the node has recently been installed, moved, serviced, or upgraded, verify that the exflash dimm is properly seated and visually verify that there is no foreign material in any dimm connector on that memory channel. If either of these conditions is found, correct and retry with the same exflas...

  • Page 747

    V “removing a memory module” on page 239 v “replacing a memory module” on page 240 v “flash dimms” on page 51 806f010d-2b82000a the [numericsensorelementname] has been disabled due to a detected fault. Explanation: the exflash proxy service detected a fault on the exflash dimm 10 in compute book 2. ...

  • Page 748

    806f010d-2b82000b the [numericsensorelementname] has been disabled due to a detected fault. Explanation: the exflash proxy service detected a fault on the exflash dimm 11 in compute book 2. May also be shown as 806f010d2b82000b or 0x806f010d2b82000b severity: error alert category: critical - hard di...

  • Page 749

    4. If the node has recently been installed, moved, serviced, or upgraded, verify that the exflash dimm is properly seated and visually verify that there is no foreign material in any dimm connector on that memory channel. If either of these conditions is found, correct and retry with the same exflas...

  • Page 750

    V “removing a memory module” on page 239 v “replacing a memory module” on page 240 v “flash dimms” on page 51 806f010d-2b82000e the [numericsensorelementname] has been disabled due to a detected fault. Explanation: the exflash proxy service detected a fault on the exflash dimm 14 in compute book 2. ...

  • Page 751

    806f010d-2b82000f the [numericsensorelementname] has been disabled due to a detected fault. Explanation: the exflash proxy service detected a fault on the exflash dimm 15 in compute book 2. May also be shown as 806f010d2b82000f or 0x806f010d2b82000f severity: error alert category: critical - hard di...

  • Page 752

    4. If the node has recently been installed, moved, serviced, or upgraded, verify that the exflash dimm is properly seated and visually verify that there is no foreign material in any dimm connector on that memory channel. If either of these conditions is found, correct and retry with the same exflas...

  • Page 753

    V “removing a memory module” on page 239 v “replacing a memory module” on page 240 v “flash dimms” on page 51 806f010d-2b820012 the [numericsensorelementname] has been disabled due to a detected fault. Explanation: the exflash proxy service detected a fault on the exflash dimm 18 in compute book 2. ...

  • Page 754

    806f010d-2b820013 the [numericsensorelementname] has been disabled due to a detected fault. Explanation: the exflash proxy service detected a fault on the exflash dimm 19 in compute book 2. May also be shown as 806f010d2b820013 or 0x806f010d2b820013 severity: error alert category: critical - hard di...

  • Page 755

    4. If the node has recently been installed, moved, serviced, or upgraded, verify that the exflash dimm is properly seated and visually verify that there is no foreign material in any dimm connector on that memory channel. If either of these conditions is found, correct and retry with the same exflas...

  • Page 756

    V “removing a memory module” on page 239 v “replacing a memory module” on page 240 v “flash dimms” on page 51 806f010d-2b820016 the [numericsensorelementname] has been disabled due to a detected fault. Explanation: the exflash proxy service detected a fault on the exflash dimm 22 in compute book 2. ...

  • Page 757

    806f010d-2b820017 the [numericsensorelementname] has been disabled due to a detected fault. Explanation: the exflash proxy service detected a fault on the exflash dimm 23 in compute book 2. May also be shown as 806f010d2b820017 or 0x806f010d2b820017 severity: error alert category: critical - hard di...

  • Page 758

    4. If the node has recently been installed, moved, serviced, or upgraded, verify that the exflash dimm is properly seated and visually verify that there is no foreign material in any dimm connector on that memory channel. If either of these conditions is found, correct and retry with the same exflas...

  • Page 759

    V “removing a memory module” on page 239 v “replacing a memory module” on page 240 v “flash dimms” on page 51 806f010d-2b830002 the [numericsensorelementname] has been disabled due to a detected fault. Explanation: the exflash proxy service detected a fault on the exflash dimm 2 in compute book 3. M...

  • Page 760

    806f010d-2b830003 the [numericsensorelementname] has been disabled due to a detected fault. Explanation: the exflash proxy service detected a fault on the exflash dimm 3 in compute book 3. May also be shown as 806f010d2b830003 or 0x806f010d2b830003 severity: error alert category: critical - hard dis...

  • Page 761

    4. If the node has recently been installed, moved, serviced, or upgraded, verify that the exflash dimm is properly seated and visually verify that there is no foreign material in any dimm connector on that memory channel. If either of these conditions is found, correct and retry with the same exflas...

  • Page 762

    V “removing a memory module” on page 239 v “replacing a memory module” on page 240 v “flash dimms” on page 51 806f010d-2b830006 the [numericsensorelementname] has been disabled due to a detected fault. Explanation: the exflash proxy service detected a fault on the exflash dimm 6 in compute book 3. M...

  • Page 763

    806f010d-2b830007 the [numericsensorelementname] has been disabled due to a detected fault. Explanation: the exflash proxy service detected a fault on the exflash dimm 7 in compute book 3. May also be shown as 806f010d2b830007 or 0x806f010d2b830007 severity: error alert category: critical - hard dis...

  • Page 764

    4. If the node has recently been installed, moved, serviced, or upgraded, verify that the exflash dimm is properly seated and visually verify that there is no foreign material in any dimm connector on that memory channel. If either of these conditions is found, correct and retry with the same exflas...

  • Page 765

    V “removing a memory module” on page 239 v “replacing a memory module” on page 240 v “flash dimms” on page 51 806f010d-2b83000a the [numericsensorelementname] has been disabled due to a detected fault. Explanation: the exflash proxy service detected a fault on the exflash dimm 10 in compute book 3. ...

  • Page 766

    806f010d-2b83000b the [numericsensorelementname] has been disabled due to a detected fault. Explanation: the exflash proxy service detected a fault on the exflash dimm 11 in compute book 3. May also be shown as 806f010d2b83000b or 0x806f010d2b83000b severity: error alert category: critical - hard di...

  • Page 767

    4. If the node has recently been installed, moved, serviced, or upgraded, verify that the exflash dimm is properly seated and visually verify that there is no foreign material in any dimm connector on that memory channel. If either of these conditions is found, correct and retry with the same exflas...

  • Page 768

    V “removing a memory module” on page 239 v “replacing a memory module” on page 240 v “flash dimms” on page 51 806f010d-2b83000e the [numericsensorelementname] has been disabled due to a detected fault. Explanation: the exflash proxy service detected a fault on the exflash dimm 14 in compute book 3. ...

  • Page 769

    806f010d-2b83000f the [numericsensorelementname] has been disabled due to a detected fault. Explanation: the exflash proxy service detected a fault on the exflash dimm 15 in compute book 3. May also be shown as 806f010d2b83000f or 0x806f010d2b83000f severity: error alert category: critical - hard di...

  • Page 770

    4. If the node has recently been installed, moved, serviced, or upgraded, verify that the exflash dimm is properly seated and visually verify that there is no foreign material in any dimm connector on that memory channel. If either of these conditions is found, correct and retry with the same exflas...

  • Page 771

    V “removing a memory module” on page 239 v “replacing a memory module” on page 240 v “flash dimms” on page 51 806f010d-2b830012 the [numericsensorelementname] has been disabled due to a detected fault. Explanation: the exflash proxy service detected a fault on the exflash dimm 18 in compute book 3. ...

  • Page 772

    806f010d-2b830013 the [numericsensorelementname] has been disabled due to a detected fault. Explanation: the exflash proxy service detected a fault on the exflash dimm 19 in compute book 3. May also be shown as 806f010d2b830013 or 0x806f010d2b830013 severity: error alert category: critical - hard di...

  • Page 773

    4. If the node has recently been installed, moved, serviced, or upgraded, verify that the exflash dimm is properly seated and visually verify that there is no foreign material in any dimm connector on that memory channel. If either of these conditions is found, correct and retry with the same exflas...

  • Page 774

    V “removing a memory module” on page 239 v “replacing a memory module” on page 240 v “flash dimms” on page 51 806f010d-2b830016 the [numericsensorelementname] has been disabled due to a detected fault. Explanation: the exflash proxy service detected a fault on the exflash dimm 22 in compute book 3. ...

  • Page 775

    806f010d-2b830017 the [numericsensorelementname] has been disabled due to a detected fault. Explanation: the exflash proxy service detected a fault on the exflash dimm 23 in compute book 3. May also be shown as 806f010d2b830017 or 0x806f010d2b830017 severity: error alert category: critical - hard di...

  • Page 776

    4. If the node has recently been installed, moved, serviced, or upgraded, verify that the exflash dimm is properly seated and visually verify that there is no foreign material in any dimm connector on that memory channel. If either of these conditions is found, correct and retry with the same exflas...

  • Page 777

    V “removing a memory module” on page 239 v “replacing a memory module” on page 240 v “flash dimms” on page 51 806f010d-2b840002 the [numericsensorelementname] has been disabled due to a detected fault. Explanation: the exflash proxy service detected a fault on the exflash dimm 2 in compute book 4. M...

  • Page 778

    806f010d-2b840003 the [numericsensorelementname] has been disabled due to a detected fault. Explanation: the exflash proxy service detected a fault on the exflash dimm 3 in compute book 4. May also be shown as 806f010d2b840003 or 0x806f010d2b840003 severity: error alert category: critical - hard dis...

  • Page 779

    4. If the node has recently been installed, moved, serviced, or upgraded, verify that the exflash dimm is properly seated and visually verify that there is no foreign material in any dimm connector on that memory channel. If either of these conditions is found, correct and retry with the same exflas...

  • Page 780

    V “removing a memory module” on page 239 v “replacing a memory module” on page 240 v “flash dimms” on page 51 806f010d-2b840006 the [numericsensorelementname] has been disabled due to a detected fault. Explanation: the exflash proxy service detected a fault on the exflash dimm 6 in compute book 4. M...

  • Page 781

    806f010d-2b840007 the [numericsensorelementname] has been disabled due to a detected fault. Explanation: the exflash proxy service detected a fault on the exflash dimm 7 in compute book 4. May also be shown as 806f010d2b840007 or 0x806f010d2b840007 severity: error alert category: critical - hard dis...

  • Page 782

    4. If the node has recently been installed, moved, serviced, or upgraded, verify that the exflash dimm is properly seated and visually verify that there is no foreign material in any dimm connector on that memory channel. If either of these conditions is found, correct and retry with the same exflas...

  • Page 783

    V “removing a memory module” on page 239 v “replacing a memory module” on page 240 v “flash dimms” on page 51 806f010d-2b84000a the [numericsensorelementname] has been disabled due to a detected fault. Explanation: the exflash proxy service detected a fault on the exflash dimm 10 in compute book 4. ...

  • Page 784

    806f010d-2b84000b the [numericsensorelementname] has been disabled due to a detected fault. Explanation: the exflash proxy service detected a fault on the exflash dimm 11 in compute book 4. May also be shown as 806f010d2b84000b or 0x806f010d2b84000b severity: error alert category: critical - hard di...

  • Page 785

    4. If the node has recently been installed, moved, serviced, or upgraded, verify that the exflash dimm is properly seated and visually verify that there is no foreign material in any dimm connector on that memory channel. If either of these conditions is found, correct and retry with the same exflas...

  • Page 786

    V “removing a memory module” on page 239 v “replacing a memory module” on page 240 v “flash dimms” on page 51 806f010d-2b84000e the [numericsensorelementname] has been disabled due to a detected fault. Explanation: the exflash proxy service detected a fault on the exflash dimm 14 in compute book 4. ...

  • Page 787

    806f010d-2b84000f the [numericsensorelementname] has been disabled due to a detected fault. Explanation: the exflash proxy service detected a fault on the exflash dimm 15 in compute book 4. May also be shown as 806f010d2b84000f or 0x806f010d2b84000f severity: error alert category: critical - hard di...

  • Page 788

    4. If the node has recently been installed, moved, serviced, or upgraded, verify that the exflash dimm is properly seated and visually verify that there is no foreign material in any dimm connector on that memory channel. If either of these conditions is found, correct and retry with the same exflas...

  • Page 789

    V “removing a memory module” on page 239 v “replacing a memory module” on page 240 v “flash dimms” on page 51 806f010d-2b840012 the [numericsensorelementname] has been disabled due to a detected fault. Explanation: the exflash proxy service detected a fault on the exflash dimm 18 in compute book 4. ...

  • Page 790

    806f010d-2b840013 the [numericsensorelementname] has been disabled due to a detected fault. Explanation: the exflash proxy service detected a fault on the exflash dimm 19 in compute book 4. May also be shown as 806f010d2b840013 or 0x806f010d2b840013 severity: error alert category: critical - hard di...

  • Page 791

    4. If the node has recently been installed, moved, serviced, or upgraded, verify that the exflash dimm is properly seated and visually verify that there is no foreign material in any dimm connector on that memory channel. If either of these conditions is found, correct and retry with the same exflas...

  • Page 792

    V “removing a memory module” on page 239 v “replacing a memory module” on page 240 v “flash dimms” on page 51 806f010d-2b840016 the [numericsensorelementname] has been disabled due to a detected fault. Explanation: the exflash proxy service detected a fault on the exflash dimm 22 in compute book 4. ...

  • Page 793

    806f010d-2b840017 the [numericsensorelementname] has been disabled due to a detected fault. Explanation: the exflash proxy service detected a fault on the exflash dimm 23 in compute book 4. May also be shown as 806f010d2b840017 or 0x806f010d2b840017 severity: error alert category: critical - hard di...

  • Page 794

    4. If the node has recently been installed, moved, serviced, or upgraded, verify that the exflash dimm is properly seated and visually verify that there is no foreign material in any dimm connector on that memory channel. If either of these conditions is found, correct and retry with the same exflas...

  • Page 795

    806f0113-1701ffff a bus timeout has occurred on bus [sensorelementname]. Explanation: imm has reported a bus uncorrectable error related to the nmi. May also be shown as 806f01131701ffff or 0x806f01131701ffff severity: error alert category: critical - other serviceable: yes cim information: prefix: ...

  • Page 796

    806f011b-1f01ffff the connector [physicalconnectorelementname] has encountered a configuration error. Explanation: imm has detected the storage i/o book has a cable / interconnect problem. May also be shown as 806f011b1f01ffff or 0x806f011b1f01ffff severity: error alert category: critical - other se...

  • Page 797

    V “replacing the storage book board assembly” on page 269 806f0207-0301ffff [processorelementname] has failed with frb1/bist condition. Explanation: imm has reported a miroprocessor 1 failed - frb1/bist condition. May also be shown as 806f02070301ffff or 0x806f02070301ffff severity: error alert cate...

  • Page 798

    806f0207-0303ffff [processorelementname] has failed with frb1/bist condition. Explanation: imm has reported a miroprocessor 3 failed - frb1/bist condition. May also be shown as 806f02070303ffff or 0x806f02070303ffff severity: error alert category: critical - cpu serviceable: yes cim information: pre...

  • Page 799

    806f0207-2583ffff [processorelementname] has failed with frb1/bist condition. Explanation: imm has reported a microprocessor failed - frb1/bist condition. May also be shown as 806f02072583ffff or 0x806f02072583ffff severity: error alert category: critical - cpu serviceable: yes cim information: pref...

  • Page 800

    806f020d-0402ffff failure predicted on [numericsensorelementname] for array [computersystemelementname]. Explanation: failure predicted (pfa) on the hard drive 2. May also be shown as 806f020d0402ffff or 0x806f020d0402ffff severity: warning alert category: system - predicted failure serviceable: yes...

  • Page 801

    806f020d-0405ffff failure predicted on [numericsensorelementname] for array [computersystemelementname]. Explanation: failure predicted (pfa) on the hard drive 5. May also be shown as 806f020d0405ffff or 0x806f020d0405ffff severity: warning alert category: system - predicted failure serviceable: yes...

  • Page 802

    806f020d-0408ffff failure predicted on [numericsensorelementname] for array [computersystemelementname]. Explanation: failure predicted (pfa) on the hard drive 8. May also be shown as 806f020d0408ffff or 0x806f020d0408ffff severity: warning alert category: system - predicted failure serviceable: yes...

  • Page 803

    806f020d-040bffff failure predicted on [numericsensorelementname] for array [computersystemelementname]. Explanation: failure predicted (pfa) on the hard drive 11. May also be shown as 806f020d040bffff or 0x806f020d040bffff severity: warning alert category: system - predicted failure serviceable: ye...

  • Page 804

    806f020d-040effff failure predicted on [numericsensorelementname] for array [computersystemelementname]. Explanation: failure predicted (pfa) on the hard drive 14. May also be shown as 806f020d040effff or 0x806f020d040effff severity: warning alert category: system - predicted failure serviceable: ye...

  • Page 805

    2. If the node has recently been installed, moved, serviced, or upgraded, verify that the exflash dimm is properly seated and visually verify that there is no foreign material in any dimm connector on that memory channel. If either of these conditions is found, correct and retry with the same exflas...

  • Page 806

    806f020d-2b810803 failure predicted on [numericsensorelementname] for array [computersystemelementname]. Explanation: the exflash proxy service reported a failure predicted (pfa) on the exflash dimm 3 in compute book 1. May also be shown as 806f020d2b810803 or 0x806f020d2b810803 severity: warning al...

  • Page 807

    Either of these conditions is found, correct and retry with the same exflash dimm. (note: event log may contain a recent 00580a4 event denoting detected change in dimm population that could be related to this problem.) 3. Check ibm support site for an applicable service bulletin or firmware update t...

  • Page 808

    806f020d-2b810806 failure predicted on [numericsensorelementname] for array [computersystemelementname]. Explanation: the exflash proxy service reported a failure predicted (pfa) on the exflash dimm 6 in compute book 1. May also be shown as 806f020d2b810806 or 0x806f020d2b810806 severity: warning al...

  • Page 809

    Either of these conditions is found, correct and retry with the same exflash dimm. (note: event log may contain a recent 00580a4 event denoting detected change in dimm population that could be related to this problem.) 3. Check ibm support site for an applicable service bulletin or firmware update t...

  • Page 810

    806f020d-2b810809 failure predicted on [numericsensorelementname] for array [computersystemelementname]. Explanation: the exflash proxy service reported a failure predicted (pfa) on the exflash dimm 9 in compute book 1. May also be shown as 806f020d2b810809 or 0x806f020d2b810809 severity: warning al...

  • Page 811

    Either of these conditions is found, correct and retry with the same exflash dimm. (note: event log may contain a recent 00580a4 event denoting detected change in dimm population that could be related to this problem.) 3. Check ibm support site for an applicable service bulletin or firmware update t...

  • Page 812

    806f020d-2b81080c failure predicted on [numericsensorelementname] for array [computersystemelementname]. Explanation: the exflash proxy service reported a failure predicted (pfa) on the exflash dimm 12 in compute book 1. May also be shown as 806f020d2b81080c or 0x806f020d2b81080c severity: warning a...

  • Page 813

    Either of these conditions is found, correct and retry with the same exflash dimm. (note: event log may contain a recent 00580a4 event denoting detected change in dimm population that could be related to this problem.) 3. Check ibm support site for an applicable service bulletin or firmware update t...

  • Page 814

    806f020d-2b81080f failure predicted on [numericsensorelementname] for array [computersystemelementname]. Explanation: the exflash proxy service reported a failure predicted (pfa) on the exflash dimm 15 in compute book 1. May also be shown as 806f020d2b81080f or 0x806f020d2b81080f severity: warning a...

  • Page 815

    Either of these conditions is found, correct and retry with the same exflash dimm. (note: event log may contain a recent 00580a4 event denoting detected change in dimm population that could be related to this problem.) 3. Check ibm support site for an applicable service bulletin or firmware update t...

  • Page 816

    806f020d-2b810812 failure predicted on [numericsensorelementname] for array [computersystemelementname]. Explanation: the exflash proxy service reported a failure predicted (pfa) on the exflash dimm 18 in compute book 1. May also be shown as 806f020d2b810812 or 0x806f020d2b810812 severity: warning a...

  • Page 817

    Either of these conditions is found, correct and retry with the same exflash dimm. (note: event log may contain a recent 00580a4 event denoting detected change in dimm population that could be related to this problem.) 3. Check ibm support site for an applicable service bulletin or firmware update t...

  • Page 818

    806f020d-2b810815 failure predicted on [numericsensorelementname] for array [computersystemelementname]. Explanation: the exflash proxy service reported a failure predicted (pfa) on the exflash dimm 21 in compute book 1. May also be shown as 806f020d2b810815 or 0x806f020d2b810815 severity: warning a...

  • Page 819

    Either of these conditions is found, correct and retry with the same exflash dimm. (note: event log may contain a recent 00580a4 event denoting detected change in dimm population that could be related to this problem.) 3. Check ibm support site for an applicable service bulletin or firmware update t...

  • Page 820

    806f020d-2b810818 failure predicted on [numericsensorelementname] for array [computersystemelementname]. Explanation: the exflash proxy service reported a failure predicted (pfa) on the exflash dimm 24 in compute book 1. May also be shown as 806f020d2b810818 or 0x806f020d2b810818 severity: warning a...

  • Page 821

    Either of these conditions is found, correct and retry with the same exflash dimm. (note: event log may contain a recent 00580a4 event denoting detected change in dimm population that could be related to this problem.) 3. Check ibm support site for an applicable service bulletin or firmware update t...

  • Page 822

    806f020d-2b820803 failure predicted on [numericsensorelementname] for array [computersystemelementname]. Explanation: the exflash proxy service reported a failure predicted (pfa) on the exflash dimm 3 in compute book 2. May also be shown as 806f020d2b820803 or 0x806f020d2b820803 severity: warning al...

  • Page 823

    Either of these conditions is found, correct and retry with the same exflash dimm. (note: event log may contain a recent 00580a4 event denoting detected change in dimm population that could be related to this problem.) 3. Check ibm support site for an applicable service bulletin or firmware update t...

  • Page 824

    806f020d-2b820806 failure predicted on [numericsensorelementname] for array [computersystemelementname]. Explanation: the exflash proxy service reported a failure predicted (pfa) on the exflash dimm 6 in compute book 2. May also be shown as 806f020d2b820806 or 0x806f020d2b820806 severity: warning al...

  • Page 825

    Either of these conditions is found, correct and retry with the same exflash dimm. (note: event log may contain a recent 00580a4 event denoting detected change in dimm population that could be related to this problem.) 3. Check ibm support site for an applicable service bulletin or firmware update t...

  • Page 826

    806f020d-2b820809 failure predicted on [numericsensorelementname] for array [computersystemelementname]. Explanation: the exflash proxy service reported a failure predicted (pfa) on the exflash dimm 9 in compute book 2. May also be shown as 806f020d2b820809 or 0x806f020d2b820809 severity: warning al...

  • Page 827

    Either of these conditions is found, correct and retry with the same exflash dimm. (note: event log may contain a recent 00580a4 event denoting detected change in dimm population that could be related to this problem.) 3. Check ibm support site for an applicable service bulletin or firmware update t...

  • Page 828

    806f020d-2b82080c failure predicted on [numericsensorelementname] for array [computersystemelementname]. Explanation: the exflash proxy service reported a failure predicted (pfa) on the exflash dimm 12 in compute book 2. May also be shown as 806f020d2b82080c or 0x806f020d2b82080c severity: warning a...

  • Page 829

    Either of these conditions is found, correct and retry with the same exflash dimm. (note: event log may contain a recent 00580a4 event denoting detected change in dimm population that could be related to this problem.) 3. Check ibm support site for an applicable service bulletin or firmware update t...

  • Page 830

    806f020d-2b82080f failure predicted on [numericsensorelementname] for array [computersystemelementname]. Explanation: the exflash proxy service reported a failure predicted (pfa) on the exflash dimm 15 in compute book 2. May also be shown as 806f020d2b82080f or 0x806f020d2b82080f severity: warning a...

  • Page 831

    Either of these conditions is found, correct and retry with the same exflash dimm. (note: event log may contain a recent 00580a4 event denoting detected change in dimm population that could be related to this problem.) 3. Check ibm support site for an applicable service bulletin or firmware update t...

  • Page 832

    806f020d-2b820812 failure predicted on [numericsensorelementname] for array [computersystemelementname]. Explanation: the exflash proxy service reported a failure predicted (pfa) on the exflash dimm 18 in compute book 2. May also be shown as 806f020d2b820812 or 0x806f020d2b820812 severity: warning a...

  • Page 833

    Either of these conditions is found, correct and retry with the same exflash dimm. (note: event log may contain a recent 00580a4 event denoting detected change in dimm population that could be related to this problem.) 3. Check ibm support site for an applicable service bulletin or firmware update t...

  • Page 834

    806f020d-2b820815 failure predicted on [numericsensorelementname] for array [computersystemelementname]. Explanation: the exflash proxy service reported a failure predicted (pfa) on the exflash dimm 21 in compute book 2. May also be shown as 806f020d2b820815 or 0x806f020d2b820815 severity: warning a...

  • Page 835

    Either of these conditions is found, correct and retry with the same exflash dimm. (note: event log may contain a recent 00580a4 event denoting detected change in dimm population that could be related to this problem.) 3. Check ibm support site for an applicable service bulletin or firmware update t...

  • Page 836

    806f020d-2b820818 failure predicted on [numericsensorelementname] for array [computersystemelementname]. Explanation: the exflash proxy service reported a failure predicted (pfa) on the exflash dimm 24 in compute book 2. May also be shown as 806f020d2b820818 or 0x806f020d2b820818 severity: warning a...

  • Page 837

    Either of these conditions is found, correct and retry with the same exflash dimm. (note: event log may contain a recent 00580a4 event denoting detected change in dimm population that could be related to this problem.) 3. Check ibm support site for an applicable service bulletin or firmware update t...

  • Page 838

    806f020d-2b830803 failure predicted on [numericsensorelementname] for array [computersystemelementname]. Explanation: the exflash proxy service reported a failure predicted (pfa) on the exflash dimm 3 in compute book 3. May also be shown as 806f020d2b830803 or 0x806f020d2b830803 severity: warning al...

  • Page 839

    Either of these conditions is found, correct and retry with the same exflash dimm. (note: event log may contain a recent 00580a4 event denoting detected change in dimm population that could be related to this problem.) 3. Check ibm support site for an applicable service bulletin or firmware update t...

  • Page 840

    806f020d-2b830806 failure predicted on [numericsensorelementname] for array [computersystemelementname]. Explanation: the exflash proxy service reported a failure predicted (pfa) on the exflash dimm 6 in compute book 3. May also be shown as 806f020d2b830806 or 0x806f020d2b830806 severity: warning al...

  • Page 841

    Either of these conditions is found, correct and retry with the same exflash dimm. (note: event log may contain a recent 00580a4 event denoting detected change in dimm population that could be related to this problem.) 3. Check ibm support site for an applicable service bulletin or firmware update t...

  • Page 842

    806f020d-2b830809 failure predicted on [numericsensorelementname] for array [computersystemelementname]. Explanation: the exflash proxy service reported a failure predicted (pfa) on the exflash dimm 9 in compute book 3. May also be shown as 806f020d2b830809 or 0x806f020d2b830809 severity: warning al...

  • Page 843

    Either of these conditions is found, correct and retry with the same exflash dimm. (note: event log may contain a recent 00580a4 event denoting detected change in dimm population that could be related to this problem.) 3. Check ibm support site for an applicable service bulletin or firmware update t...

  • Page 844

    806f020d-2b83080c failure predicted on [numericsensorelementname] for array [computersystemelementname]. Explanation: the exflash proxy service reported a failure predicted (pfa) on the exflash dimm 12 in compute book 3. May also be shown as 806f020d2b83080c or 0x806f020d2b83080c severity: warning a...

  • Page 845

    Either of these conditions is found, correct and retry with the same exflash dimm. (note: event log may contain a recent 00580a4 event denoting detected change in dimm population that could be related to this problem.) 3. Check ibm support site for an applicable service bulletin or firmware update t...

  • Page 846

    806f020d-2b83080f failure predicted on [numericsensorelementname] for array [computersystemelementname]. Explanation: the exflash proxy service reported a failure predicted (pfa) on the exflash dimm 15 in compute book 3. May also be shown as 806f020d2b83080f or 0x806f020d2b83080f severity: warning a...

  • Page 847

    Either of these conditions is found, correct and retry with the same exflash dimm. (note: event log may contain a recent 00580a4 event denoting detected change in dimm population that could be related to this problem.) 3. Check ibm support site for an applicable service bulletin or firmware update t...

  • Page 848

    806f020d-2b830812 failure predicted on [numericsensorelementname] for array [computersystemelementname]. Explanation: the exflash proxy service reported a failure predicted (pfa) on the exflash dimm 18 in compute book 3. May also be shown as 806f020d2b830812 or 0x806f020d2b830812 severity: warning a...

  • Page 849

    Either of these conditions is found, correct and retry with the same exflash dimm. (note: event log may contain a recent 00580a4 event denoting detected change in dimm population that could be related to this problem.) 3. Check ibm support site for an applicable service bulletin or firmware update t...

  • Page 850

    806f020d-2b830815 failure predicted on [numericsensorelementname] for array [computersystemelementname]. Explanation: the exflash proxy service reported a failure predicted (pfa) on the exflash dimm 21 in compute book 3. May also be shown as 806f020d2b830815 or 0x806f020d2b830815 severity: warning a...

  • Page 851

    Either of these conditions is found, correct and retry with the same exflash dimm. (note: event log may contain a recent 00580a4 event denoting detected change in dimm population that could be related to this problem.) 3. Check ibm support site for an applicable service bulletin or firmware update t...

  • Page 852

    806f020d-2b830818 failure predicted on [numericsensorelementname] for array [computersystemelementname]. Explanation: the exflash proxy service reported a failure predicted (pfa) on the exflash dimm 24 in compute book 3. May also be shown as 806f020d2b830818 or 0x806f020d2b830818 severity: warning a...

  • Page 853

    Either of these conditions is found, correct and retry with the same exflash dimm. (note: event log may contain a recent 00580a4 event denoting detected change in dimm population that could be related to this problem.) 3. Check ibm support site for an applicable service bulletin or firmware update t...

  • Page 854

    806f020d-2b840803 failure predicted on [numericsensorelementname] for array [computersystemelementname]. Explanation: the exflash proxy service reported a failure predicted (pfa) on the exflash dimm 3 in compute book 4. May also be shown as 806f020d2b840803 or 0x806f020d2b840803 severity: warning al...

  • Page 855

    Either of these conditions is found, correct and retry with the same exflash dimm. (note: event log may contain a recent 00580a4 event denoting detected change in dimm population that could be related to this problem.) 3. Check ibm support site for an applicable service bulletin or firmware update t...

  • Page 856

    806f020d-2b840806 failure predicted on [numericsensorelementname] for array [computersystemelementname]. Explanation: the exflash proxy service reported a failure predicted (pfa) on the exflash dimm 6 in compute book 4. May also be shown as 806f020d2b840806 or 0x806f020d2b840806 severity: warning al...

  • Page 857

    Either of these conditions is found, correct and retry with the same exflash dimm. (note: event log may contain a recent 00580a4 event denoting detected change in dimm population that could be related to this problem.) 3. Check ibm support site for an applicable service bulletin or firmware update t...

  • Page 858

    806f020d-2b840809 failure predicted on [numericsensorelementname] for array [computersystemelementname]. Explanation: the exflash proxy service reported a failure predicted (pfa) on the exflash dimm 9 in compute book 4. May also be shown as 806f020d2b840809 or 0x806f020d2b840809 severity: warning al...

  • Page 859

    Either of these conditions is found, correct and retry with the same exflash dimm. (note: event log may contain a recent 00580a4 event denoting detected change in dimm population that could be related to this problem.) 3. Check ibm support site for an applicable service bulletin or firmware update t...

  • Page 860

    806f020d-2b84080c failure predicted on [numericsensorelementname] for array [computersystemelementname]. Explanation: the exflash proxy service reported a failure predicted (pfa) on the exflash dimm 12 in compute book 4. May also be shown as 806f020d2b84080c or 0x806f020d2b84080c severity: warning a...

  • Page 861

    Either of these conditions is found, correct and retry with the same exflash dimm. (note: event log may contain a recent 00580a4 event denoting detected change in dimm population that could be related to this problem.) 3. Check ibm support site for an applicable service bulletin or firmware update t...

  • Page 862

    806f020d-2b84080f failure predicted on [numericsensorelementname] for array [computersystemelementname]. Explanation: the exflash proxy service reported a failure predicted (pfa) on the exflash dimm 15 in compute book 4. May also be shown as 806f020d2b84080f or 0x806f020d2b84080f severity: warning a...

  • Page 863

    Either of these conditions is found, correct and retry with the same exflash dimm. (note: event log may contain a recent 00580a4 event denoting detected change in dimm population that could be related to this problem.) 3. Check ibm support site for an applicable service bulletin or firmware update t...

  • Page 864

    806f020d-2b840812 failure predicted on [numericsensorelementname] for array [computersystemelementname]. Explanation: the exflash proxy service reported a failure predicted (pfa) on the exflash dimm 18 in compute book 4. May also be shown as 806f020d2b840812 or 0x806f020d2b840812 severity: warning a...

  • Page 865

    Either of these conditions is found, correct and retry with the same exflash dimm. (note: event log may contain a recent 00580a4 event denoting detected change in dimm population that could be related to this problem.) 3. Check ibm support site for an applicable service bulletin or firmware update t...

  • Page 866

    806f020d-2b840815 failure predicted on [numericsensorelementname] for array [computersystemelementname]. Explanation: the exflash proxy service reported a failure predicted (pfa) on the exflash dimm 21 in compute book 4. May also be shown as 806f020d2b840815 or 0x806f020d2b840815 severity: warning a...

  • Page 867

    Either of these conditions is found, correct and retry with the same exflash dimm. (note: event log may contain a recent 00580a4 event denoting detected change in dimm population that could be related to this problem.) 3. Check ibm support site for an applicable service bulletin or firmware update t...

  • Page 868

    806f020d-2b840818 failure predicted on [numericsensorelementname] for array [computersystemelementname]. Explanation: the exflash proxy service reported a failure predicted (pfa) on the exflash dimm 24 in compute book 4. May also be shown as 806f020d2b840818 or 0x806f020d2b840818 severity: warning a...

  • Page 869

    806f0221-0b02ffff package installed in slot [physicalconnectorelementname] for system [computersystemelementname]. Explanation: imm has detected that a card was was installed in a pcie slot 2. May also be shown as 806f02210b02ffff or 0x806f02210b02ffff severity: info alert category: system - other s...

  • Page 870

    806f0221-0b05ffff package installed in slot [physicalconnectorelementname] for system [computersystemelementname]. Explanation: imm has detected that a card was was installed in a pcie slot 5. May also be shown as 806f02210b05ffff or 0x806f02210b05ffff severity: info alert category: system - other s...

  • Page 871

    806f0308-0a01ffff [powersupplyelementname] has lost input. Explanation: power supply 1 ac input has been lost. May also be shown as 806f03080a01ffff or 0x806f03080a01ffff severity: info alert category: system - other serviceable: no cim information: prefix: plat and id: 0100 snmp trap id: automatica...

  • Page 872

    806f0308-0a04ffff [powersupplyelementname] has lost input. Explanation: power supply 4 ac input has been lost. May also be shown as 806f03080a04ffff or 0x806f03080a04ffff severity: info alert category: system - other serviceable: no cim information: prefix: plat and id: 0100 snmp trap id: automatica...

  • Page 873

    806f030c-2b810003 scrub failure for [physicalmemoryelementname] on subsystem [memoryelementname]. Explanation: the imm has reported a memory post failure during boot (not a runtime error) on dimm 3 in compute book 1. May also be shown as 806f030c2b810003 or 0x806f030c2b810003 severity: error alert c...

  • Page 874

    806f030c-2b810005 scrub failure for [physicalmemoryelementname] on subsystem [memoryelementname]. Explanation: the imm has reported a memory post failure during boot (not a runtime error) on dimm 5 in compute book 1. May also be shown as 806f030c2b810005 or 0x806f030c2b810005 severity: error alert c...

  • Page 875

    806f030c-2b810007 scrub failure for [physicalmemoryelementname] on subsystem [memoryelementname]. Explanation: the imm has reported a memory post failure during boot (not a runtime error) on dimm 7 in compute book 1. May also be shown as 806f030c2b810007 or 0x806f030c2b810007 severity: error alert c...

  • Page 876

    806f030c-2b810009 scrub failure for [physicalmemoryelementname] on subsystem [memoryelementname]. Explanation: the imm has reported a memory post failure during boot (not a runtime error) on dimm 9 in compute book 1. May also be shown as 806f030c2b810009 or 0x806f030c2b810009 severity: error alert c...

  • Page 877

    806f030c-2b81000b scrub failure for [physicalmemoryelementname] on subsystem [memoryelementname]. Explanation: the imm has reported a memory post failure during boot (not a runtime error) on dimm 11 in compute book 1. May also be shown as 806f030c2b81000b or 0x806f030c2b81000b severity: error alert ...

  • Page 878

    806f030c-2b81000d scrub failure for [physicalmemoryelementname] on subsystem [memoryelementname]. Explanation: the imm has reported a memory post failure during boot (not a runtime error) on dimm 13 in compute book 1. May also be shown as 806f030c2b81000d or 0x806f030c2b81000d severity: error alert ...

  • Page 879

    806f030c-2b81000f scrub failure for [physicalmemoryelementname] on subsystem [memoryelementname]. Explanation: the imm has reported a memory post failure during boot (not a runtime error) on dimm 15 in compute book 1. May also be shown as 806f030c2b81000f or 0x806f030c2b81000f severity: error alert ...

  • Page 880

    806f030c-2b810011 scrub failure for [physicalmemoryelementname] on subsystem [memoryelementname]. Explanation: the imm has reported a memory post failure during boot (not a runtime error) on dimm 17 in compute book 1. May also be shown as 806f030c2b810011 or 0x806f030c2b810011 severity: error alert ...

  • Page 881

    806f030c-2b810013 scrub failure for [physicalmemoryelementname] on subsystem [memoryelementname]. Explanation: the imm has reported a memory post failure during boot (not a runtime error) on dimm 19 in compute book 1. May also be shown as 806f030c2b810013 or 0x806f030c2b810013 severity: error alert ...

  • Page 882

    806f030c-2b810015 scrub failure for [physicalmemoryelementname] on subsystem [memoryelementname]. Explanation: the imm has reported a memory post failure during boot (not a runtime error) on dimm 21 in compute book 1. May also be shown as 806f030c2b810015 or 0x806f030c2b810015 severity: error alert ...

  • Page 883

    806f030c-2b810017 scrub failure for [physicalmemoryelementname] on subsystem [memoryelementname]. Explanation: the imm has reported a memory post failure during boot (not a runtime error) on dimm 23 in compute book 1. May also be shown as 806f030c2b810017 or 0x806f030c2b810017 severity: error alert ...

  • Page 884

    806f030c-2b81ffff scrub failure for [physicalmemoryelementname] on subsystem [memoryelementname]. Explanation: the imm has reported a memory post failure during boot (not a runtime error) on compute book 1. May also be shown as 806f030c2b81ffff or 0x806f030c2b81ffff severity: error alert category: c...

  • Page 885

    806f030c-2b820002 scrub failure for [physicalmemoryelementname] on subsystem [memoryelementname]. Explanation: the imm has reported a memory post failure during boot (not a runtime error) on dimm 2 in compute book 2. May also be shown as 806f030c2b820002 or 0x806f030c2b820002 severity: error alert c...

  • Page 886

    806f030c-2b820004 scrub failure for [physicalmemoryelementname] on subsystem [memoryelementname]. Explanation: the imm has reported a memory post failure during boot (not a runtime error) on dimm 4 in compute book 2. May also be shown as 806f030c2b820004 or 0x806f030c2b820004 severity: error alert c...

  • Page 887

    806f030c-2b820006 scrub failure for [physicalmemoryelementname] on subsystem [memoryelementname]. Explanation: the imm has reported a memory post failure during boot (not a runtime error) on dimm 6 in compute book 2. May also be shown as 806f030c2b820006 or 0x806f030c2b820006 severity: error alert c...

  • Page 888

    806f030c-2b820008 scrub failure for [physicalmemoryelementname] on subsystem [memoryelementname]. Explanation: the imm has reported a memory post failure during boot (not a runtime error) on dimm 8 in compute book 2. May also be shown as 806f030c2b820008 or 0x806f030c2b820008 severity: error alert c...

  • Page 889

    806f030c-2b82000a scrub failure for [physicalmemoryelementname] on subsystem [memoryelementname]. Explanation: the imm has reported a memory post failure during boot (not a runtime error) on dimm 10 in compute book 2. May also be shown as 806f030c2b82000a or 0x806f030c2b82000a severity: error alert ...

  • Page 890

    806f030c-2b82000c scrub failure for [physicalmemoryelementname] on subsystem [memoryelementname]. Explanation: the imm has reported a memory post failure during boot (not a runtime error) on dimm 12 in compute book 2. May also be shown as 806f030c2b82000c or 0x806f030c2b82000c severity: error alert ...

  • Page 891

    806f030c-2b82000e scrub failure for [physicalmemoryelementname] on subsystem [memoryelementname]. Explanation: the imm has reported a memory post failure during boot (not a runtime error) on dimm 14 in compute book 2. May also be shown as 806f030c2b82000e or 0x806f030c2b82000e severity: error alert ...

  • Page 892

    806f030c-2b820010 scrub failure for [physicalmemoryelementname] on subsystem [memoryelementname]. Explanation: the imm has reported a memory post failure during boot (not a runtime error) on dimm 16 in compute book 2. May also be shown as 806f030c2b820010 or 0x806f030c2b820010 severity: error alert ...

  • Page 893

    806f030c-2b820012 scrub failure for [physicalmemoryelementname] on subsystem [memoryelementname]. Explanation: the imm has reported a memory post failure during boot (not a runtime error) on dimm 18 in compute book 2. May also be shown as 806f030c2b820012 or 0x806f030c2b820012 severity: error alert ...

  • Page 894

    806f030c-2b820014 scrub failure for [physicalmemoryelementname] on subsystem [memoryelementname]. Explanation: the imm has reported a memory post failure during boot (not a runtime error) on dimm 20 in compute book 2. May also be shown as 806f030c2b820014 or 0x806f030c2b820014 severity: error alert ...

  • Page 895

    806f030c-2b820016 scrub failure for [physicalmemoryelementname] on subsystem [memoryelementname]. Explanation: the imm has reported a memory post failure during boot (not a runtime error) on dimm 22 in compute book 2. May also be shown as 806f030c2b820016 or 0x806f030c2b820016 severity: error alert ...

  • Page 896

    806f030c-2b820018 scrub failure for [physicalmemoryelementname] on subsystem [memoryelementname]. Explanation: the imm has reported a memory post failure during boot (not a runtime error) on dimm 24 in compute book 2. May also be shown as 806f030c2b820018 or 0x806f030c2b820018 severity: error alert ...

  • Page 897

    806f030c-2b830001 scrub failure for [physicalmemoryelementname] on subsystem [memoryelementname]. Explanation: the imm has reported a memory post failure during boot (not a runtime error) on dimm 1 in compute book 3. May also be shown as 806f030c2b830001 or 0x806f030c2b830001 severity: error alert c...

  • Page 898

    806f030c-2b830003 scrub failure for [physicalmemoryelementname] on subsystem [memoryelementname]. Explanation: the imm has reported a memory post failure during boot (not a runtime error) on dimm 3 in compute book 3. May also be shown as 806f030c2b830003 or 0x806f030c2b830003 severity: error alert c...

  • Page 899

    806f030c-2b830005 scrub failure for [physicalmemoryelementname] on subsystem [memoryelementname]. Explanation: the imm has reported a memory post failure during boot (not a runtime error) on dimm 5 in compute book 3. May also be shown as 806f030c2b830005 or 0x806f030c2b830005 severity: error alert c...

  • Page 900

    806f030c-2b830007 scrub failure for [physicalmemoryelementname] on subsystem [memoryelementname]. Explanation: the imm has reported a memory post failure during boot (not a runtime error) on dimm 7 in compute book 3. May also be shown as 806f030c2b830007 or 0x806f030c2b830007 severity: error alert c...

  • Page 901

    806f030c-2b830009 scrub failure for [physicalmemoryelementname] on subsystem [memoryelementname]. Explanation: the imm has reported a memory post failure during boot (not a runtime error) on dimm 9 in compute book 3. May also be shown as 806f030c2b830009 or 0x806f030c2b830009 severity: error alert c...

  • Page 902

    806f030c-2b83000b scrub failure for [physicalmemoryelementname] on subsystem [memoryelementname]. Explanation: the imm has reported a memory post failure during boot (not a runtime error) on dimm 11 in compute book 3. May also be shown as 806f030c2b83000b or 0x806f030c2b83000b severity: error alert ...

  • Page 903

    806f030c-2b83000d scrub failure for [physicalmemoryelementname] on subsystem [memoryelementname]. Explanation: the imm has reported a memory post failure during boot (not a runtime error) on dimm 13 in compute book 3. May also be shown as 806f030c2b83000d or 0x806f030c2b83000d severity: error alert ...

  • Page 904

    806f030c-2b83000f scrub failure for [physicalmemoryelementname] on subsystem [memoryelementname]. Explanation: the imm has reported a memory post failure during boot (not a runtime error) on dimm 15 in compute book 3. May also be shown as 806f030c2b83000f or 0x806f030c2b83000f severity: error alert ...

  • Page 905

    806f030c-2b830011 scrub failure for [physicalmemoryelementname] on subsystem [memoryelementname]. Explanation: the imm has reported a memory post failure during boot (not a runtime error) on dimm 17 in compute book 3. May also be shown as 806f030c2b830011 or 0x806f030c2b830011 severity: error alert ...

  • Page 906

    806f030c-2b830013 scrub failure for [physicalmemoryelementname] on subsystem [memoryelementname]. Explanation: the imm has reported a memory post failure during boot (not a runtime error) on dimm 19 in compute book 3. May also be shown as 806f030c2b830013 or 0x806f030c2b830013 severity: error alert ...

  • Page 907

    806f030c-2b830015 scrub failure for [physicalmemoryelementname] on subsystem [memoryelementname]. Explanation: the imm has reported a memory post failure during boot (not a runtime error) on dimm 21 in compute book 3. May also be shown as 806f030c2b830015 or 0x806f030c2b830015 severity: error alert ...

  • Page 908

    806f030c-2b830017 scrub failure for [physicalmemoryelementname] on subsystem [memoryelementname]. Explanation: the imm has reported a memory post failure during boot (not a runtime error) on dimm 23 in compute book 3. May also be shown as 806f030c2b830017 or 0x806f030c2b830017 severity: error alert ...

  • Page 909

    806f030c-2b83ffff scrub failure for [physicalmemoryelementname] on subsystem [memoryelementname]. Explanation: the imm has reported a memory post failure during boot (not a runtime error) on compute book 3. May also be shown as 806f030c2b83ffff or 0x806f030c2b83ffff severity: error alert category: c...

  • Page 910

    806f030c-2b840002 scrub failure for [physicalmemoryelementname] on subsystem [memoryelementname]. Explanation: the imm has reported a memory post failure during boot (not a runtime error) on dimm 2 in compute book 4. May also be shown as 806f030c2b840002 or 0x806f030c2b840002 severity: error alert c...

  • Page 911

    806f030c-2b840004 scrub failure for [physicalmemoryelementname] on subsystem [memoryelementname]. Explanation: the imm has reported a memory post failure during boot (not a runtime error) on dimm 4 in compute book 4. May also be shown as 806f030c2b840004 or 0x806f030c2b840004 severity: error alert c...

  • Page 912

    806f030c-2b840006 scrub failure for [physicalmemoryelementname] on subsystem [memoryelementname]. Explanation: the imm has reported a memory post failure during boot (not a runtime error) on dimm 6 in compute book 4. May also be shown as 806f030c2b840006 or 0x806f030c2b840006 severity: error alert c...

  • Page 913

    806f030c-2b840008 scrub failure for [physicalmemoryelementname] on subsystem [memoryelementname]. Explanation: the imm has reported a memory post failure during boot (not a runtime error) on dimm 8 in compute book 4. May also be shown as 806f030c2b840008 or 0x806f030c2b840008 severity: error alert c...

  • Page 914

    806f030c-2b84000a scrub failure for [physicalmemoryelementname] on subsystem [memoryelementname]. Explanation: the imm has reported a memory post failure during boot (not a runtime error) on dimm 10 in compute book 4. May also be shown as 806f030c2b84000a or 0x806f030c2b84000a severity: error alert ...

  • Page 915

    806f030c-2b84000c scrub failure for [physicalmemoryelementname] on subsystem [memoryelementname]. Explanation: the imm has reported a memory post failure during boot (not a runtime error) on dimm 12 in compute book 4. May also be shown as 806f030c2b84000c or 0x806f030c2b84000c severity: error alert ...

  • Page 916

    806f030c-2b84000e scrub failure for [physicalmemoryelementname] on subsystem [memoryelementname]. Explanation: the imm has reported a memory post failure during boot (not a runtime error) on dimm 14 in compute book 4. May also be shown as 806f030c2b84000e or 0x806f030c2b84000e severity: error alert ...

  • Page 917

    806f030c-2b840010 scrub failure for [physicalmemoryelementname] on subsystem [memoryelementname]. Explanation: the imm has reported a memory post failure during boot (not a runtime error) on dimm 16 in compute book 4. May also be shown as 806f030c2b840010 or 0x806f030c2b840010 severity: error alert ...

  • Page 918

    806f030c-2b840012 scrub failure for [physicalmemoryelementname] on subsystem [memoryelementname]. Explanation: the imm has reported a memory post failure during boot (not a runtime error) on dimm 18 in compute book 4. May also be shown as 806f030c2b840012 or 0x806f030c2b840012 severity: error alert ...

  • Page 919

    806f030c-2b840014 scrub failure for [physicalmemoryelementname] on subsystem [memoryelementname]. Explanation: the imm has reported a memory post failure during boot (not a runtime error) on dimm 20 in compute book 4. May also be shown as 806f030c2b840014 or 0x806f030c2b840014 severity: error alert ...

  • Page 920

    806f030c-2b840016 scrub failure for [physicalmemoryelementname] on subsystem [memoryelementname]. Explanation: the imm has reported a memory post failure during boot (not a runtime error) on dimm 22 in compute book 4. May also be shown as 806f030c2b840016 or 0x806f030c2b840016 severity: error alert ...

  • Page 921

    806f030c-2b840018 scrub failure for [physicalmemoryelementname] on subsystem [memoryelementname]. Explanation: the imm has reported a memory post failure during boot (not a runtime error) on dimm 24 in compute book 4. May also be shown as 806f030c2b840018 or 0x806f030c2b840018 severity: error alert ...

  • Page 922

    806f030d-0400ffff hot spare enabled for [computersystemelementname]. Explanation: this message is for the use case when an implementation has detected a hot spare has been enabled. May also be shown as 806f030d0400ffff or 0x806f030d0400ffff severity: info alert category: system - other serviceable: ...

  • Page 923

    806f030d-0403ffff hot spare enabled for [computersystemelementname]. Explanation: this message is for the use case when an implementation has detected a hot spare has been enabled. May also be shown as 806f030d0403ffff or 0x806f030d0403ffff severity: info alert category: system - other serviceable: ...

  • Page 924

    806f030d-0406ffff hot spare enabled for [computersystemelementname]. Explanation: this message is for the use case when an implementation has detected a hot spare has been enabled. May also be shown as 806f030d0406ffff or 0x806f030d0406ffff severity: info alert category: system - other serviceable: ...

  • Page 925

    806f030d-0409ffff hot spare enabled for [computersystemelementname]. Explanation: this message is for the use case when an implementation has detected a hot spare has been enabled. May also be shown as 806f030d0409ffff or 0x806f030d0409ffff severity: info alert category: system - other serviceable: ...

  • Page 926

    806f030d-040cffff hot spare enabled for [computersystemelementname]. Explanation: this message is for the use case when an implementation has detected a hot spare has been enabled. May also be shown as 806f030d040cffff or 0x806f030d040cffff severity: info alert category: system - other serviceable: ...

  • Page 927

    806f030d-040fffff hot spare enabled for [computersystemelementname]. Explanation: this message is for the use case when an implementation has detected a hot spare has been enabled. May also be shown as 806f030d040fffff or 0x806f030d040fffff severity: info alert category: system - other serviceable: ...

  • Page 928

    806f032b-2101ffff a firmware or software incompatibility was detected on system [computersystemelementname]. Explanation: a mismatch of imm firmware between nodes has been detected. May also be shown as 806f032b2101ffff or 0x806f032b2101ffff severity: error alert category: critical - hardware incomp...

  • Page 929

    806f040c-2b810001 [physicalmemoryelementname] disabled on subsystem [memoryelementname]. Explanation: imm has reported that memory has been disabled on dimm 1 in compute book 1. May also be shown as 806f040c2b810001 or 0x806f040c2b810001 severity: info alert category: system - other serviceable: no ...

  • Page 930

    806f040c-2b810003 [physicalmemoryelementname] disabled on subsystem [memoryelementname]. Explanation: imm has reported that memory has been disabled on dimm 3 in compute book 1. May also be shown as 806f040c2b810003 or 0x806f040c2b810003 severity: info alert category: system - other serviceable: no ...

  • Page 931

    806f040c-2b810005 [physicalmemoryelementname] disabled on subsystem [memoryelementname]. Explanation: imm has reported that memory has been disabled on dimm 5 in compute book 1. May also be shown as 806f040c2b810005 or 0x806f040c2b810005 severity: info alert category: system - other serviceable: no ...

  • Page 932

    806f040c-2b810007 [physicalmemoryelementname] disabled on subsystem [memoryelementname]. Explanation: imm has reported that memory has been disabled on dimm 7 in compute book 1. May also be shown as 806f040c2b810007 or 0x806f040c2b810007 severity: info alert category: system - other serviceable: no ...

  • Page 933

    806f040c-2b810009 [physicalmemoryelementname] disabled on subsystem [memoryelementname]. Explanation: imm has reported that memory has been disabled on dimm 9 in compute book 1. May also be shown as 806f040c2b810009 or 0x806f040c2b810009 severity: info alert category: system - other serviceable: no ...

  • Page 934

    806f040c-2b81000b [physicalmemoryelementname] disabled on subsystem [memoryelementname]. Explanation: imm has reported that memory has been disabled on dimm 11 in compute book 1. May also be shown as 806f040c2b81000b or 0x806f040c2b81000b severity: info alert category: system - other serviceable: no...

  • Page 935

    806f040c-2b81000d [physicalmemoryelementname] disabled on subsystem [memoryelementname]. Explanation: imm has reported that memory has been disabled on dimm 13 in compute book 1. May also be shown as 806f040c2b81000d or 0x806f040c2b81000d severity: info alert category: system - other serviceable: no...

  • Page 936

    806f040c-2b81000f [physicalmemoryelementname] disabled on subsystem [memoryelementname]. Explanation: imm has reported that memory has been disabled on dimm 15 in compute book 1. May also be shown as 806f040c2b81000f or 0x806f040c2b81000f severity: info alert category: system - other serviceable: no...

  • Page 937

    806f040c-2b810011 [physicalmemoryelementname] disabled on subsystem [memoryelementname]. Explanation: imm has reported that memory has been disabled on dimm 17 in compute book 1. May also be shown as 806f040c2b810011 or 0x806f040c2b810011 severity: info alert category: system - other serviceable: no...

  • Page 938

    806f040c-2b810013 [physicalmemoryelementname] disabled on subsystem [memoryelementname]. Explanation: imm has reported that memory has been disabled on dimm 19 in compute book 1. May also be shown as 806f040c2b810013 or 0x806f040c2b810013 severity: info alert category: system - other serviceable: no...

  • Page 939

    806f040c-2b810015 [physicalmemoryelementname] disabled on subsystem [memoryelementname]. Explanation: imm has reported that memory has been disabled on dimm 21 in compute book 1. May also be shown as 806f040c2b810015 or 0x806f040c2b810015 severity: info alert category: system - other serviceable: no...

  • Page 940

    806f040c-2b810017 [physicalmemoryelementname] disabled on subsystem [memoryelementname]. Explanation: imm has reported that memory has been disabled on dimm 23 in compute book 1. May also be shown as 806f040c2b810017 or 0x806f040c2b810017 severity: info alert category: system - other serviceable: no...

  • Page 941

    806f040c-2b81ffff [physicalmemoryelementname] disabled on subsystem [memoryelementname]. Explanation: imm has reported that memory has been disabled on compute book 1. May also be shown as 806f040c2b81ffff or 0x806f040c2b81ffff severity: info alert category: system - other serviceable: no cim inform...

  • Page 942

    806f040c-2b820002 [physicalmemoryelementname] disabled on subsystem [memoryelementname]. Explanation: imm has reported that memory has been disabled on dimm 2 in compute book 2. May also be shown as 806f040c2b820002 or 0x806f040c2b820002 severity: info alert category: system - other serviceable: no ...

  • Page 943

    806f040c-2b820004 [physicalmemoryelementname] disabled on subsystem [memoryelementname]. Explanation: imm has reported that memory has been disabled on dimm 4 in compute book 2. May also be shown as 806f040c2b820004 or 0x806f040c2b820004 severity: info alert category: system - other serviceable: no ...

  • Page 944

    806f040c-2b820006 [physicalmemoryelementname] disabled on subsystem [memoryelementname]. Explanation: imm has reported that memory has been disabled on dimm 6 in compute book 2. May also be shown as 806f040c2b820006 or 0x806f040c2b820006 severity: info alert category: system - other serviceable: no ...

  • Page 945

    806f040c-2b820008 [physicalmemoryelementname] disabled on subsystem [memoryelementname]. Explanation: imm has reported that memory has been disabled on dimm 8 in compute book 2. May also be shown as 806f040c2b820008 or 0x806f040c2b820008 severity: info alert category: system - other serviceable: no ...

  • Page 946

    806f040c-2b82000a [physicalmemoryelementname] disabled on subsystem [memoryelementname]. Explanation: imm has reported that memory has been disabled on dimm 10 in compute book 2. May also be shown as 806f040c2b82000a or 0x806f040c2b82000a severity: info alert category: system - other serviceable: no...

  • Page 947

    806f040c-2b82000c [physicalmemoryelementname] disabled on subsystem [memoryelementname]. Explanation: imm has reported that memory has been disabled on dimm 12 in compute book 2. May also be shown as 806f040c2b82000c or 0x806f040c2b82000c severity: info alert category: system - other serviceable: no...

  • Page 948

    806f040c-2b82000e [physicalmemoryelementname] disabled on subsystem [memoryelementname]. Explanation: imm has reported that memory has been disabled on dimm 14 in compute book 2. May also be shown as 806f040c2b82000e or 0x806f040c2b82000e severity: info alert category: system - other serviceable: no...

  • Page 949

    806f040c-2b820010 [physicalmemoryelementname] disabled on subsystem [memoryelementname]. Explanation: imm has reported that memory has been disabled on dimm 16 in compute book 2. May also be shown as 806f040c2b820010 or 0x806f040c2b820010 severity: info alert category: system - other serviceable: no...

  • Page 950

    806f040c-2b820012 [physicalmemoryelementname] disabled on subsystem [memoryelementname]. Explanation: imm has reported that memory has been disabled on dimm 18 in compute book 2. May also be shown as 806f040c2b820012 or 0x806f040c2b820012 severity: info alert category: system - other serviceable: no...

  • Page 951

    806f040c-2b820014 [physicalmemoryelementname] disabled on subsystem [memoryelementname]. Explanation: imm has reported that memory has been disabled on dimm 20 in compute book 2. May also be shown as 806f040c2b820014 or 0x806f040c2b820014 severity: info alert category: system - other serviceable: no...

  • Page 952

    806f040c-2b820016 [physicalmemoryelementname] disabled on subsystem [memoryelementname]. Explanation: imm has reported that memory has been disabled on dimm 22 in compute book 2. May also be shown as 806f040c2b820016 or 0x806f040c2b820016 severity: info alert category: system - other serviceable: no...

  • Page 953

    806f040c-2b820018 [physicalmemoryelementname] disabled on subsystem [memoryelementname]. Explanation: imm has reported that memory has been disabled on dimm 24 in compute book 2. May also be shown as 806f040c2b820018 or 0x806f040c2b820018 severity: info alert category: system - other serviceable: no...

  • Page 954

    806f040c-2b830001 [physicalmemoryelementname] disabled on subsystem [memoryelementname]. Explanation: imm has reported that memory has been disabled on dimm 1 in compute book 3. May also be shown as 806f040c2b830001 or 0x806f040c2b830001 severity: info alert category: system - other serviceable: no ...

  • Page 955

    806f040c-2b830003 [physicalmemoryelementname] disabled on subsystem [memoryelementname]. Explanation: imm has reported that memory has been disabled on dimm 3 in compute book 3. May also be shown as 806f040c2b830003 or 0x806f040c2b830003 severity: info alert category: system - other serviceable: no ...

  • Page 956

    806f040c-2b830005 [physicalmemoryelementname] disabled on subsystem [memoryelementname]. Explanation: imm has reported that memory has been disabled on dimm 5 in compute book 3. May also be shown as 806f040c2b830005 or 0x806f040c2b830005 severity: info alert category: system - other serviceable: no ...

  • Page 957

    806f040c-2b830007 [physicalmemoryelementname] disabled on subsystem [memoryelementname]. Explanation: imm has reported that memory has been disabled on dimm 7 in compute book 3. May also be shown as 806f040c2b830007 or 0x806f040c2b830007 severity: info alert category: system - other serviceable: no ...

  • Page 958

    806f040c-2b830009 [physicalmemoryelementname] disabled on subsystem [memoryelementname]. Explanation: imm has reported that memory has been disabled on dimm 9 in compute book 3. May also be shown as 806f040c2b830009 or 0x806f040c2b830009 severity: info alert category: system - other serviceable: no ...

  • Page 959

    806f040c-2b83000b [physicalmemoryelementname] disabled on subsystem [memoryelementname]. Explanation: imm has reported that memory has been disabled on dimm 11 in compute book 3. May also be shown as 806f040c2b83000b or 0x806f040c2b83000b severity: info alert category: system - other serviceable: no...

  • Page 960

    806f040c-2b83000d [physicalmemoryelementname] disabled on subsystem [memoryelementname]. Explanation: imm has reported that memory has been disabled on dimm 13 in compute book 3. May also be shown as 806f040c2b83000d or 0x806f040c2b83000d severity: info alert category: system - other serviceable: no...

  • Page 961

    806f040c-2b83000f [physicalmemoryelementname] disabled on subsystem [memoryelementname]. Explanation: imm has reported that memory has been disabled on dimm 15 in compute book 3. May also be shown as 806f040c2b83000f or 0x806f040c2b83000f severity: info alert category: system - other serviceable: no...

  • Page 962

    806f040c-2b830011 [physicalmemoryelementname] disabled on subsystem [memoryelementname]. Explanation: imm has reported that memory has been disabled on dimm 17 in compute book 3. May also be shown as 806f040c2b830011 or 0x806f040c2b830011 severity: info alert category: system - other serviceable: no...

  • Page 963

    806f040c-2b830013 [physicalmemoryelementname] disabled on subsystem [memoryelementname]. Explanation: imm has reported that memory has been disabled on dimm 19 in compute book 3. May also be shown as 806f040c2b830013 or 0x806f040c2b830013 severity: info alert category: system - other serviceable: no...

  • Page 964

    806f040c-2b830015 [physicalmemoryelementname] disabled on subsystem [memoryelementname]. Explanation: imm has reported that memory has been disabled on dimm 21 in compute book 3. May also be shown as 806f040c2b830015 or 0x806f040c2b830015 severity: info alert category: system - other serviceable: no...

  • Page 965

    806f040c-2b830017 [physicalmemoryelementname] disabled on subsystem [memoryelementname]. Explanation: imm has reported that memory has been disabled on dimm 23 in compute book 3. May also be shown as 806f040c2b830017 or 0x806f040c2b830017 severity: info alert category: system - other serviceable: no...

  • Page 966

    806f040c-2b83ffff [physicalmemoryelementname] disabled on subsystem [memoryelementname]. Explanation: imm has reported that memory has been disabled on compute book 3. May also be shown as 806f040c2b83ffff or 0x806f040c2b83ffff severity: info alert category: system - other serviceable: no cim inform...

  • Page 967

    806f040c-2b840002 [physicalmemoryelementname] disabled on subsystem [memoryelementname]. Explanation: imm has reported that memory has been disabled on dimm 2 in compute book 4. May also be shown as 806f040c2b840002 or 0x806f040c2b840002 severity: info alert category: system - other serviceable: no ...

  • Page 968

    806f040c-2b840004 [physicalmemoryelementname] disabled on subsystem [memoryelementname]. Explanation: imm has reported that memory has been disabled on dimm 4 in compute book 4. May also be shown as 806f040c2b840004 or 0x806f040c2b840004 severity: info alert category: system - other serviceable: no ...

  • Page 969

    806f040c-2b840006 [physicalmemoryelementname] disabled on subsystem [memoryelementname]. Explanation: imm has reported that memory has been disabled on dimm 6 in compute book 4. May also be shown as 806f040c2b840006 or 0x806f040c2b840006 severity: info alert category: system - other serviceable: no ...

  • Page 970

    806f040c-2b840008 [physicalmemoryelementname] disabled on subsystem [memoryelementname]. Explanation: imm has reported that memory has been disabled on dimm 8 in compute book 4. May also be shown as 806f040c2b840008 or 0x806f040c2b840008 severity: info alert category: system - other serviceable: no ...

  • Page 971

    806f040c-2b84000a [physicalmemoryelementname] disabled on subsystem [memoryelementname]. Explanation: imm has reported that memory has been disabled on dimm 10 in compute book 4. May also be shown as 806f040c2b84000a or 0x806f040c2b84000a severity: info alert category: system - other serviceable: no...

  • Page 972

    806f040c-2b84000c [physicalmemoryelementname] disabled on subsystem [memoryelementname]. Explanation: imm has reported that memory has been disabled on dimm 12 in compute book 4. May also be shown as 806f040c2b84000c or 0x806f040c2b84000c severity: info alert category: system - other serviceable: no...

  • Page 973

    806f040c-2b84000e [physicalmemoryelementname] disabled on subsystem [memoryelementname]. Explanation: imm has reported that memory has been disabled on dimm 14 in compute book 4. May also be shown as 806f040c2b84000e or 0x806f040c2b84000e severity: info alert category: system - other serviceable: no...

  • Page 974

    806f040c-2b840010 [physicalmemoryelementname] disabled on subsystem [memoryelementname]. Explanation: imm has reported that memory has been disabled on dimm 16 in compute book 4. May also be shown as 806f040c2b840010 or 0x806f040c2b840010 severity: info alert category: system - other serviceable: no...

  • Page 975

    806f040c-2b840012 [physicalmemoryelementname] disabled on subsystem [memoryelementname]. Explanation: imm has reported that memory has been disabled on dimm 18 in compute book 4. May also be shown as 806f040c2b840012 or 0x806f040c2b840012 severity: info alert category: system - other serviceable: no...

  • Page 976

    806f040c-2b840014 [physicalmemoryelementname] disabled on subsystem [memoryelementname]. Explanation: imm has reported that memory has been disabled on dimm 20 in compute book 4. May also be shown as 806f040c2b840014 or 0x806f040c2b840014 severity: info alert category: system - other serviceable: no...

  • Page 977

    806f040c-2b840016 [physicalmemoryelementname] disabled on subsystem [memoryelementname]. Explanation: imm has reported that memory has been disabled on dimm 22 in compute book 4. May also be shown as 806f040c2b840016 or 0x806f040c2b840016 severity: info alert category: system - other serviceable: no...

  • Page 978

    806f040c-2b840018 [physicalmemoryelementname] disabled on subsystem [memoryelementname]. Explanation: imm has reported that memory has been disabled on dimm 24 in compute book 4. May also be shown as 806f040c2b840018 or 0x806f040c2b840018 severity: info alert category: system - other serviceable: no...

  • Page 979

    806f0507-0301ffff [processorelementname] has a configuration mismatch. Explanation: imm has reported a microprocessor configuration mismatch on microprocessor 1. May also be shown as 806f05070301ffff or 0x806f05070301ffff severity: error alert category: critical - cpu serviceable: yes cim informatio...

  • Page 980

    806f0507-0303ffff [processorelementname] has a configuration mismatch. Explanation: imm has reported a microprocessor configuration mismatch on microprocessor 3. May also be shown as 806f05070303ffff or 0x806f05070303ffff severity: error alert category: critical - cpu serviceable: yes cim informatio...

  • Page 981

    806f0507-2583ffff [processorelementname] has a configuration mismatch. Explanation: imm has reported a microprocessor configuration mismatch has occurred. May also be shown as 806f05072583ffff or 0x806f05072583ffff severity: error alert category: critical - cpu serviceable: yes cim information: pref...

  • Page 982

    806f050c-2b810001 memory logging limit reached for [physicalmemoryelementname] on subsystem [memoryelementname]. Explanation: imm has reported that the memory logging limit has been reached on dimm 1 in compute book 1. May also be shown as 806f050c2b810001 or 0x806f050c2b810001 severity: warning ale...

  • Page 983

    806f050c-2b810003 memory logging limit reached for [physicalmemoryelementname] on subsystem [memoryelementname]. Explanation: imm has reported that the memory logging limit has been reached on dimm 3 in compute book 1. May also be shown as 806f050c2b810003 or 0x806f050c2b810003 severity: warning ale...

  • Page 984

    806f050c-2b810005 memory logging limit reached for [physicalmemoryelementname] on subsystem [memoryelementname]. Explanation: imm has reported that the memory logging limit has been reached on dimm 5 in compute book 1. May also be shown as 806f050c2b810005 or 0x806f050c2b810005 severity: warning ale...

  • Page 985

    806f050c-2b810007 memory logging limit reached for [physicalmemoryelementname] on subsystem [memoryelementname]. Explanation: imm has reported that the memory logging limit has been reached on dimm 7 in compute book 1. May also be shown as 806f050c2b810007 or 0x806f050c2b810007 severity: warning ale...

  • Page 986

    806f050c-2b810009 memory logging limit reached for [physicalmemoryelementname] on subsystem [memoryelementname]. Explanation: imm has reported that the memory logging limit has been reached on dimm 9 in compute book 1. May also be shown as 806f050c2b810009 or 0x806f050c2b810009 severity: warning ale...

  • Page 987

    806f050c-2b81000b memory logging limit reached for [physicalmemoryelementname] on subsystem [memoryelementname]. Explanation: imm has reported that the memory logging limit has been reached on dimm 11 in compute book 1. May also be shown as 806f050c2b81000b or 0x806f050c2b81000b severity: warning al...

  • Page 988

    806f050c-2b81000d memory logging limit reached for [physicalmemoryelementname] on subsystem [memoryelementname]. Explanation: imm has reported that the memory logging limit has been reached on dimm 13 in compute book 1. May also be shown as 806f050c2b81000d or 0x806f050c2b81000d severity: warning al...

  • Page 989

    806f050c-2b81000f memory logging limit reached for [physicalmemoryelementname] on subsystem [memoryelementname]. Explanation: imm has reported that the memory logging limit has been reached on dimm 15 in compute book 1. May also be shown as 806f050c2b81000f or 0x806f050c2b81000f severity: warning al...

  • Page 990

    806f050c-2b810011 memory logging limit reached for [physicalmemoryelementname] on subsystem [memoryelementname]. Explanation: imm has reported that the memory logging limit has been reached on dimm 17 in compute book 1. May also be shown as 806f050c2b810011 or 0x806f050c2b810011 severity: warning al...

  • Page 991

    806f050c-2b810013 memory logging limit reached for [physicalmemoryelementname] on subsystem [memoryelementname]. Explanation: imm has reported that the memory logging limit has been reached on dimm 19 in compute book 1. May also be shown as 806f050c2b810013 or 0x806f050c2b810013 severity: warning al...

  • Page 992

    806f050c-2b810015 memory logging limit reached for [physicalmemoryelementname] on subsystem [memoryelementname]. Explanation: imm has reported that the memory logging limit has been reached on dimm 21 in compute book 1. May also be shown as 806f050c2b810015 or 0x806f050c2b810015 severity: warning al...

  • Page 993

    806f050c-2b810017 memory logging limit reached for [physicalmemoryelementname] on subsystem [memoryelementname]. Explanation: imm has reported that the memory logging limit has been reached on dimm 23 in compute book 1. May also be shown as 806f050c2b810017 or 0x806f050c2b810017 severity: warning al...

  • Page 994

    806f050c-2b81ffff memory logging limit reached for [physicalmemoryelementname] on subsystem [memoryelementname]. Explanation: imm has reported that the memory logging limit has been reached on compute book 1. May also be shown as 806f050c2b81ffff or 0x806f050c2b81ffff severity: warning alert categor...

  • Page 995

    806f050c-2b820002 memory logging limit reached for [physicalmemoryelementname] on subsystem [memoryelementname]. Explanation: imm has reported that the memory logging limit has been reached on dimm 2 in compute book 2. May also be shown as 806f050c2b820002 or 0x806f050c2b820002 severity: warning ale...

  • Page 996

    806f050c-2b820004 memory logging limit reached for [physicalmemoryelementname] on subsystem [memoryelementname]. Explanation: imm has reported that the memory logging limit has been reached on dimm 4 in compute book 2. May also be shown as 806f050c2b820004 or 0x806f050c2b820004 severity: warning ale...

  • Page 997

    806f050c-2b820006 memory logging limit reached for [physicalmemoryelementname] on subsystem [memoryelementname]. Explanation: imm has reported that the memory logging limit has been reached on dimm 6 in compute book 2. May also be shown as 806f050c2b820006 or 0x806f050c2b820006 severity: warning ale...

  • Page 998

    806f050c-2b820008 memory logging limit reached for [physicalmemoryelementname] on subsystem [memoryelementname]. Explanation: imm has reported that the memory logging limit has been reached on dimm 8 in compute book 2. May also be shown as 806f050c2b820008 or 0x806f050c2b820008 severity: warning ale...

  • Page 999

    806f050c-2b82000a memory logging limit reached for [physicalmemoryelementname] on subsystem [memoryelementname]. Explanation: imm has reported that the memory logging limit has been reached on dimm 10 in compute book 2. May also be shown as 806f050c2b82000a or 0x806f050c2b82000a severity: warning al...

  • Page 1000

    806f050c-2b82000c memory logging limit reached for [physicalmemoryelementname] on subsystem [memoryelementname]. Explanation: imm has reported that the memory logging limit has been reached on dimm 12 in compute book 2. May also be shown as 806f050c2b82000c or 0x806f050c2b82000c severity: warning al...

  • Page 1001

    806f050c-2b82000e memory logging limit reached for [physicalmemoryelementname] on subsystem [memoryelementname]. Explanation: imm has reported that the memory logging limit has been reached on dimm 14 in compute book 2. May also be shown as 806f050c2b82000e or 0x806f050c2b82000e severity: warning al...

  • Page 1002

    806f050c-2b820010 memory logging limit reached for [physicalmemoryelementname] on subsystem [memoryelementname]. Explanation: imm has reported that the memory logging limit has been reached on dimm 16 in compute book 2. May also be shown as 806f050c2b820010 or 0x806f050c2b820010 severity: warning al...

  • Page 1003

    806f050c-2b820012 memory logging limit reached for [physicalmemoryelementname] on subsystem [memoryelementname]. Explanation: imm has reported that the memory logging limit has been reached on dimm 18 in compute book 2. May also be shown as 806f050c2b820012 or 0x806f050c2b820012 severity: warning al...

  • Page 1004

    806f050c-2b820014 memory logging limit reached for [physicalmemoryelementname] on subsystem [memoryelementname]. Explanation: imm has reported that the memory logging limit has been reached on dimm 20 in compute book 2. May also be shown as 806f050c2b820014 or 0x806f050c2b820014 severity: warning al...

  • Page 1005

    806f050c-2b820016 memory logging limit reached for [physicalmemoryelementname] on subsystem [memoryelementname]. Explanation: imm has reported that the memory logging limit has been reached on dimm 22 in compute book 2. May also be shown as 806f050c2b820016 or 0x806f050c2b820016 severity: warning al...

  • Page 1006

    806f050c-2b820018 memory logging limit reached for [physicalmemoryelementname] on subsystem [memoryelementname]. Explanation: imm has reported that the memory logging limit has been reached on dimm 24 in compute book 2. May also be shown as 806f050c2b820018 or 0x806f050c2b820018 severity: warning al...

  • Page 1007

    806f050c-2b830001 memory logging limit reached for [physicalmemoryelementname] on subsystem [memoryelementname]. Explanation: imm has reported that the memory logging limit has been reached on dimm 1 in compute book 3. May also be shown as 806f050c2b830001 or 0x806f050c2b830001 severity: warning ale...

  • Page 1008

    806f050c-2b830003 memory logging limit reached for [physicalmemoryelementname] on subsystem [memoryelementname]. Explanation: imm has reported that the memory logging limit has been reached on dimm 3 in compute book 3. May also be shown as 806f050c2b830003 or 0x806f050c2b830003 severity: warning ale...

  • Page 1009

    806f050c-2b830005 memory logging limit reached for [physicalmemoryelementname] on subsystem [memoryelementname]. Explanation: imm has reported that the memory logging limit has been reached on dimm 5 in compute book 3. May also be shown as 806f050c2b830005 or 0x806f050c2b830005 severity: warning ale...

  • Page 1010

    806f050c-2b830007 memory logging limit reached for [physicalmemoryelementname] on subsystem [memoryelementname]. Explanation: imm has reported that the memory logging limit has been reached on dimm 7 in compute book 3. May also be shown as 806f050c2b830007 or 0x806f050c2b830007 severity: warning ale...

  • Page 1011

    806f050c-2b830009 memory logging limit reached for [physicalmemoryelementname] on subsystem [memoryelementname]. Explanation: imm has reported that the memory logging limit has been reached on dimm 9 in compute book 3. May also be shown as 806f050c2b830009 or 0x806f050c2b830009 severity: warning ale...

  • Page 1012

    806f050c-2b83000b memory logging limit reached for [physicalmemoryelementname] on subsystem [memoryelementname]. Explanation: imm has reported that the memory logging limit has been reached on dimm 11 in compute book 3. May also be shown as 806f050c2b83000b or 0x806f050c2b83000b severity: warning al...

  • Page 1013

    806f050c-2b83000d memory logging limit reached for [physicalmemoryelementname] on subsystem [memoryelementname]. Explanation: imm has reported that the memory logging limit has been reached on dimm 13 in compute book 3. May also be shown as 806f050c2b83000d or 0x806f050c2b83000d severity: warning al...

  • Page 1014

    806f050c-2b83000f memory logging limit reached for [physicalmemoryelementname] on subsystem [memoryelementname]. Explanation: imm has reported that the memory logging limit has been reached on dimm 15 in compute book 3. May also be shown as 806f050c2b83000f or 0x806f050c2b83000f severity: warning al...

  • Page 1015

    806f050c-2b830011 memory logging limit reached for [physicalmemoryelementname] on subsystem [memoryelementname]. Explanation: imm has reported that the memory logging limit has been reached on dimm 17 in compute book 3. May also be shown as 806f050c2b830011 or 0x806f050c2b830011 severity: warning al...

  • Page 1016

    806f050c-2b830013 memory logging limit reached for [physicalmemoryelementname] on subsystem [memoryelementname]. Explanation: imm has reported that the memory logging limit has been reached on dimm 19 in compute book 3. May also be shown as 806f050c2b830013 or 0x806f050c2b830013 severity: warning al...

  • Page 1017

    806f050c-2b830015 memory logging limit reached for [physicalmemoryelementname] on subsystem [memoryelementname]. Explanation: imm has reported that the memory logging limit has been reached on dimm 21 in compute book 3. May also be shown as 806f050c2b830015 or 0x806f050c2b830015 severity: warning al...

  • Page 1018

    806f050c-2b830017 memory logging limit reached for [physicalmemoryelementname] on subsystem [memoryelementname]. Explanation: imm has reported that the memory logging limit has been reached on dimm 23 in compute book 3. May also be shown as 806f050c2b830017 or 0x806f050c2b830017 severity: warning al...

  • Page 1019

    806f050c-2b83ffff memory logging limit reached for [physicalmemoryelementname] on subsystem [memoryelementname]. Explanation: imm has reported that the memory logging limit has been reached on compute book 3. May also be shown as 806f050c2b83ffff or 0x806f050c2b83ffff severity: warning alert categor...

  • Page 1020

    806f050c-2b840002 memory logging limit reached for [physicalmemoryelementname] on subsystem [memoryelementname]. Explanation: imm has reported that the memory logging limit has been reached on dimm 2 in compute book 4. May also be shown as 806f050c2b840002 or 0x806f050c2b840002 severity: warning ale...

  • Page 1021

    806f050c-2b840004 memory logging limit reached for [physicalmemoryelementname] on subsystem [memoryelementname]. Explanation: imm has reported that the memory logging limit has been reached on dimm 4 in compute book 4. May also be shown as 806f050c2b840004 or 0x806f050c2b840004 severity: warning ale...

  • Page 1022

    806f050c-2b840006 memory logging limit reached for [physicalmemoryelementname] on subsystem [memoryelementname]. Explanation: imm has reported that the memory logging limit has been reached on dimm 6 in compute book 4. May also be shown as 806f050c2b840006 or 0x806f050c2b840006 severity: warning ale...

  • Page 1023

    806f050c-2b840008 memory logging limit reached for [physicalmemoryelementname] on subsystem [memoryelementname]. Explanation: imm has reported that the memory logging limit has been reached on dimm 8 in compute book 4. May also be shown as 806f050c2b840008 or 0x806f050c2b840008 severity: warning ale...

  • Page 1024

    806f050c-2b84000a memory logging limit reached for [physicalmemoryelementname] on subsystem [memoryelementname]. Explanation: imm has reported that the memory logging limit has been reached on dimm 10 in compute book 4. May also be shown as 806f050c2b84000a or 0x806f050c2b84000a severity: warning al...

  • Page 1025

    806f050c-2b84000c memory logging limit reached for [physicalmemoryelementname] on subsystem [memoryelementname]. Explanation: imm has reported that the memory logging limit has been reached on dimm 12 in compute book 4. May also be shown as 806f050c2b84000c or 0x806f050c2b84000c severity: warning al...

  • Page 1026

    806f050c-2b84000e memory logging limit reached for [physicalmemoryelementname] on subsystem [memoryelementname]. Explanation: imm has reported that the memory logging limit has been reached on dimm 14 in compute book 4. May also be shown as 806f050c2b84000e or 0x806f050c2b84000e severity: warning al...

  • Page 1027

    806f050c-2b840010 memory logging limit reached for [physicalmemoryelementname] on subsystem [memoryelementname]. Explanation: imm has reported that the memory logging limit has been reached on dimm 16 in compute book 4. May also be shown as 806f050c2b840010 or 0x806f050c2b840010 severity: warning al...

  • Page 1028

    806f050c-2b840012 memory logging limit reached for [physicalmemoryelementname] on subsystem [memoryelementname]. Explanation: imm has reported that the memory logging limit has been reached on dimm 18 in compute book 4. May also be shown as 806f050c2b840012 or 0x806f050c2b840012 severity: warning al...

  • Page 1029

    806f050c-2b840014 memory logging limit reached for [physicalmemoryelementname] on subsystem [memoryelementname]. Explanation: imm has reported that the memory logging limit has been reached on dimm 20 in compute book 4. May also be shown as 806f050c2b840014 or 0x806f050c2b840014 severity: warning al...

  • Page 1030

    806f050c-2b840016 memory logging limit reached for [physicalmemoryelementname] on subsystem [memoryelementname]. Explanation: imm has reported that the memory logging limit has been reached on dimm 22 in compute book 4. May also be shown as 806f050c2b840016 or 0x806f050c2b840016 severity: warning al...

  • Page 1031

    806f050c-2b840018 memory logging limit reached for [physicalmemoryelementname] on subsystem [memoryelementname]. Explanation: imm has reported that the memory logging limit has been reached on dimm 24 in compute book 4. May also be shown as 806f050c2b840018 or 0x806f050c2b840018 severity: warning al...

  • Page 1032

    806f050d-0400ffff array [computersystemelementname] is in critical condition. Explanation: drive 0 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 message. May a...

  • Page 1033

    806f050d-0402ffff array [computersystemelementname] is in critical condition. Explanation: drive 2 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 message. May a...

  • Page 1034

    806f050d-0404ffff array [computersystemelementname] is in critical condition. Explanation: drive 4 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 message. May a...

  • Page 1035

    806f050d-0406ffff array [computersystemelementname] is in critical condition. Explanation: drive 6 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 message. May a...

  • Page 1036

    806f050d-0408ffff array [computersystemelementname] is in critical condition. Explanation: drive 8 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 message. May a...

  • Page 1037

    806f050d-040affff array [computersystemelementname] is in critical condition. Explanation: drive 10 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 message. May ...

  • Page 1038

    806f050d-040cffff array [computersystemelementname] is in critical condition. Explanation: drive 12 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 message. May ...

  • Page 1039

    806f050d-040effff array [computersystemelementname] is in critical condition. Explanation: drive 14 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 message. May ...

  • Page 1040

    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 1041

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

  • Page 1042

    806f0607-2583ffff an sm bios uncorrectable cpu complex error for [processorelementname] has asserted. Explanation: the uefi has detected a configuration type issue with the microprocessors installed may also be shown as 806f06072583ffff or 0x806f06072583ffff severity: error alert category: critical ...

  • Page 1043

    806f060d-0400ffff array [computersystemelementname] has failed. Explanation: drive 0 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 severity: erro...

  • Page 1044

    806f060d-0402ffff array [computersystemelementname] has failed. Explanation: drive 2 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 severity: erro...

  • Page 1045

    806f060d-0404ffff array [computersystemelementname] has failed. Explanation: drive 4 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 severity: erro...

  • Page 1046

    806f060d-0406ffff array [computersystemelementname] has failed. Explanation: drive 6 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 severity: erro...

  • Page 1047

    806f060d-0408ffff array [computersystemelementname] has failed. Explanation: drive 8 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 severity: erro...

  • Page 1048

    806f060d-040affff array [computersystemelementname] has failed. Explanation: drive 10 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 severity: err...

  • Page 1049

    806f060d-040cffff array [computersystemelementname] has failed. Explanation: drive 12 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 severity: err...

  • Page 1050

    806f060d-040effff array [computersystemelementname] has failed. Explanation: drive 14 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 severity: err...

  • Page 1051

    806f070c-2581ffff configuration error for [physicalmemoryelementname] on subsystem [memoryelementname]. Explanation: imm has reported that a memory dimm configuration error has occurred. May also be shown as 806f070c2581ffff or 0x806f070c2581ffff severity: error alert category: critical - memory ser...

  • Page 1052

    806f070c-2b810002 configuration error for [physicalmemoryelementname] on subsystem [memoryelementname]. Explanation: imm has reported that a memory configuration error has occurred on dimm 2 in compute book 1. May also be shown as 806f070c2b810002 or 0x806f070c2b810002 severity: error alert category...

  • Page 1053

    806f070c-2b810004 configuration error for [physicalmemoryelementname] on subsystem [memoryelementname]. Explanation: imm has reported that a memory configuration error has occurred on dimm 4 in compute book 1. May also be shown as 806f070c2b810004 or 0x806f070c2b810004 severity: error alert category...

  • Page 1054

    806f070c-2b810006 configuration error for [physicalmemoryelementname] on subsystem [memoryelementname]. Explanation: imm has reported that a memory configuration error has occurred on dimm 6 in compute book 1. May also be shown as 806f070c2b810006 or 0x806f070c2b810006 severity: error alert category...

  • Page 1055

    806f070c-2b810008 configuration error for [physicalmemoryelementname] on subsystem [memoryelementname]. Explanation: imm has reported that a memory configuration error has occurred on dimm 8 in compute book 1. May also be shown as 806f070c2b810008 or 0x806f070c2b810008 severity: error alert category...

  • Page 1056

    806f070c-2b81000a configuration error for [physicalmemoryelementname] on subsystem [memoryelementname]. Explanation: imm has reported that a memory configuration error has occurred on dimm 10 in compute book 1. May also be shown as 806f070c2b81000a or 0x806f070c2b81000a severity: error alert categor...

  • Page 1057

    806f070c-2b81000c configuration error for [physicalmemoryelementname] on subsystem [memoryelementname]. Explanation: imm has reported that a memory configuration error has occurred on dimm 12 in compute book 1. May also be shown as 806f070c2b81000c or 0x806f070c2b81000c severity: error alert categor...

  • Page 1058

    806f070c-2b81000e configuration error for [physicalmemoryelementname] on subsystem [memoryelementname]. Explanation: imm has reported that a memory configuration error has occurred on dimm 14 in compute book 1. May also be shown as 806f070c2b81000e or 0x806f070c2b81000e severity: error alert categor...

  • Page 1059

    806f070c-2b810010 configuration error for [physicalmemoryelementname] on subsystem [memoryelementname]. Explanation: imm has reported that a memory configuration error has occurred on dimm 16 in compute book 1. May also be shown as 806f070c2b810010 or 0x806f070c2b810010 severity: error alert categor...

  • Page 1060

    806f070c-2b810012 configuration error for [physicalmemoryelementname] on subsystem [memoryelementname]. Explanation: imm has reported that a memory configuration error has occurred on dimm 18 in compute book 1. May also be shown as 806f070c2b810012 or 0x806f070c2b810012 severity: error alert categor...

  • Page 1061

    806f070c-2b810014 configuration error for [physicalmemoryelementname] on subsystem [memoryelementname]. Explanation: imm has reported that a memory configuration error has occurred on dimm 20 in compute book 1. May also be shown as 806f070c2b810014 or 0x806f070c2b810014 severity: error alert categor...

  • Page 1062

    806f070c-2b810016 configuration error for [physicalmemoryelementname] on subsystem [memoryelementname]. Explanation: imm has reported that a memory configuration error has occurred on dimm 22 in compute book 1. May also be shown as 806f070c2b810016 or 0x806f070c2b810016 severity: error alert categor...

  • Page 1063

    806f070c-2b810018 configuration error for [physicalmemoryelementname] on subsystem [memoryelementname]. Explanation: imm has reported that a memory configuration error has occurred on dimm 24 in compute book 1. May also be shown as 806f070c2b810018 or 0x806f070c2b810018 severity: error alert categor...

  • Page 1064

    806f070c-2b820001 configuration error for [physicalmemoryelementname] on subsystem [memoryelementname]. Explanation: imm has reported that a memory configuration error has occurred on dimm 1 in compute book 2. May also be shown as 806f070c2b820001 or 0x806f070c2b820001 severity: error alert category...

  • Page 1065

    806f070c-2b820003 configuration error for [physicalmemoryelementname] on subsystem [memoryelementname]. Explanation: imm has reported that a memory configuration error has occurred on dimm 3 in compute book 2. May also be shown as 806f070c2b820003 or 0x806f070c2b820003 severity: error alert category...

  • Page 1066

    806f070c-2b820005 configuration error for [physicalmemoryelementname] on subsystem [memoryelementname]. Explanation: imm has reported that a memory configuration error has occurred on dimm 5 in compute book 2. May also be shown as 806f070c2b820005 or 0x806f070c2b820005 severity: error alert category...

  • Page 1067

    806f070c-2b820007 configuration error for [physicalmemoryelementname] on subsystem [memoryelementname]. Explanation: imm has reported that a memory configuration error has occurred on dimm 7 in compute book 2. May also be shown as 806f070c2b820007 or 0x806f070c2b820007 severity: error alert category...

  • Page 1068

    806f070c-2b820009 configuration error for [physicalmemoryelementname] on subsystem [memoryelementname]. Explanation: imm has reported that a memory configuration error has occurred on dimm 9 in compute book 2. May also be shown as 806f070c2b820009 or 0x806f070c2b820009 severity: error alert category...

  • Page 1069

    806f070c-2b82000b configuration error for [physicalmemoryelementname] on subsystem [memoryelementname]. Explanation: imm has reported that a memory configuration error has occurred on dimm 11 in compute book 2. May also be shown as 806f070c2b82000b or 0x806f070c2b82000b severity: error alert categor...

  • Page 1070

    806f070c-2b82000d configuration error for [physicalmemoryelementname] on subsystem [memoryelementname]. Explanation: imm has reported that a memory configuration error has occurred on dimm 13 in compute book 2. May also be shown as 806f070c2b82000d or 0x806f070c2b82000d severity: error alert categor...

  • Page 1071

    806f070c-2b82000f configuration error for [physicalmemoryelementname] on subsystem [memoryelementname]. Explanation: imm has reported that a memory configuration error has occurred on dimm 15 in compute book 2. May also be shown as 806f070c2b82000f or 0x806f070c2b82000f severity: error alert categor...

  • Page 1072

    806f070c-2b820011 configuration error for [physicalmemoryelementname] on subsystem [memoryelementname]. Explanation: imm has reported that a memory configuration error has occurred on dimm 17 in compute book 2. May also be shown as 806f070c2b820011 or 0x806f070c2b820011 severity: error alert categor...

  • Page 1073

    806f070c-2b820013 configuration error for [physicalmemoryelementname] on subsystem [memoryelementname]. Explanation: imm has reported that a memory configuration error has occurred on dimm 19 in compute book 2. May also be shown as 806f070c2b820013 or 0x806f070c2b820013 severity: error alert categor...

  • Page 1074

    806f070c-2b820015 configuration error for [physicalmemoryelementname] on subsystem [memoryelementname]. Explanation: imm has reported that a memory configuration error has occurred on dimm 21 in compute book 2. May also be shown as 806f070c2b820015 or 0x806f070c2b820015 severity: error alert categor...

  • Page 1075

    806f070c-2b820017 configuration error for [physicalmemoryelementname] on subsystem [memoryelementname]. Explanation: imm has reported that a memory configuration error has occurred on dimm 23 in compute book 2. May also be shown as 806f070c2b820017 or 0x806f070c2b820017 severity: error alert categor...

  • Page 1076

    806f070c-2b82ffff configuration error for [physicalmemoryelementname] on subsystem [memoryelementname]. Explanation: imm has reported that a memory configuration error has occurred on compute book 2. May also be shown as 806f070c2b82ffff or 0x806f070c2b82ffff severity: error alert category: critical...

  • Page 1077

    806f070c-2b830002 configuration error for [physicalmemoryelementname] on subsystem [memoryelementname]. Explanation: imm has reported that a memory configuration error has occurred on dimm 2 in compute book 3. May also be shown as 806f070c2b830002 or 0x806f070c2b830002 severity: error alert category...

  • Page 1078

    806f070c-2b830004 configuration error for [physicalmemoryelementname] on subsystem [memoryelementname]. Explanation: imm has reported that a memory configuration error has occurred on dimm 4 in compute book 3. May also be shown as 806f070c2b830004 or 0x806f070c2b830004 severity: error alert category...

  • Page 1079

    806f070c-2b830006 configuration error for [physicalmemoryelementname] on subsystem [memoryelementname]. Explanation: imm has reported that a memory configuration error has occurred on dimm 6 in compute book 3. May also be shown as 806f070c2b830006 or 0x806f070c2b830006 severity: error alert category...

  • Page 1080

    806f070c-2b830008 configuration error for [physicalmemoryelementname] on subsystem [memoryelementname]. Explanation: imm has reported that a memory configuration error has occurred on dimm 8 in compute book 3. May also be shown as 806f070c2b830008 or 0x806f070c2b830008 severity: error alert category...

  • Page 1081

    806f070c-2b83000a configuration error for [physicalmemoryelementname] on subsystem [memoryelementname]. Explanation: imm has reported that a memory configuration error has occurred on dimm 10 in compute book 3. May also be shown as 806f070c2b83000a or 0x806f070c2b83000a severity: error alert categor...

  • Page 1082

    806f070c-2b83000c configuration error for [physicalmemoryelementname] on subsystem [memoryelementname]. Explanation: imm has reported that a memory configuration error has occurred on dimm 12 in compute book 3. May also be shown as 806f070c2b83000c or 0x806f070c2b83000c severity: error alert categor...

  • Page 1083

    806f070c-2b83000e configuration error for [physicalmemoryelementname] on subsystem [memoryelementname]. Explanation: imm has reported that a memory configuration error has occurred on dimm 14 in compute book 3. May also be shown as 806f070c2b83000e or 0x806f070c2b83000e severity: error alert categor...

  • Page 1084

    806f070c-2b830010 configuration error for [physicalmemoryelementname] on subsystem [memoryelementname]. Explanation: imm has reported that a memory configuration error has occurred on dimm 16 in compute book 3. May also be shown as 806f070c2b830010 or 0x806f070c2b830010 severity: error alert categor...

  • Page 1085

    806f070c-2b830012 configuration error for [physicalmemoryelementname] on subsystem [memoryelementname]. Explanation: imm has reported that a memory configuration error has occurred on dimm 18 in compute book 3. May also be shown as 806f070c2b830012 or 0x806f070c2b830012 severity: error alert categor...

  • Page 1086

    806f070c-2b830014 configuration error for [physicalmemoryelementname] on subsystem [memoryelementname]. Explanation: imm has reported that a memory configuration error has occurred on dimm 20 in compute book 3. May also be shown as 806f070c2b830014 or 0x806f070c2b830014 severity: error alert categor...

  • Page 1087

    806f070c-2b830016 configuration error for [physicalmemoryelementname] on subsystem [memoryelementname]. Explanation: imm has reported that a memory configuration error has occurred on dimm 22 in compute book 3. May also be shown as 806f070c2b830016 or 0x806f070c2b830016 severity: error alert categor...

  • Page 1088

    806f070c-2b830018 configuration error for [physicalmemoryelementname] on subsystem [memoryelementname]. Explanation: imm has reported that a memory configuration error has occurred on dimm 24 in compute book 3. May also be shown as 806f070c2b830018 or 0x806f070c2b830018 severity: error alert categor...

  • Page 1089

    806f070c-2b840001 configuration error for [physicalmemoryelementname] on subsystem [memoryelementname]. Explanation: imm has reported that a memory configuration error has occurred on dimm 1 in compute book 4. May also be shown as 806f070c2b840001 or 0x806f070c2b840001 severity: error alert category...

  • Page 1090

    806f070c-2b840003 configuration error for [physicalmemoryelementname] on subsystem [memoryelementname]. Explanation: imm has reported that a memory configuration error has occurred on dimm 3 in compute book 4. May also be shown as 806f070c2b840003 or 0x806f070c2b840003 severity: error alert category...

  • Page 1091

    806f070c-2b840005 configuration error for [physicalmemoryelementname] on subsystem [memoryelementname]. Explanation: imm has reported that a memory configuration error has occurred on dimm 5 in compute book 4. May also be shown as 806f070c2b840005 or 0x806f070c2b840005 severity: error alert category...

  • Page 1092

    806f070c-2b840007 configuration error for [physicalmemoryelementname] on subsystem [memoryelementname]. Explanation: imm has reported that a memory configuration error has occurred on dimm 7 in compute book 4. May also be shown as 806f070c2b840007 or 0x806f070c2b840007 severity: error alert category...

  • Page 1093

    806f070c-2b840009 configuration error for [physicalmemoryelementname] on subsystem [memoryelementname]. Explanation: imm has reported that a memory configuration error has occurred on dimm 9 in compute book 4. May also be shown as 806f070c2b840009 or 0x806f070c2b840009 severity: error alert category...

  • Page 1094

    806f070c-2b84000b configuration error for [physicalmemoryelementname] on subsystem [memoryelementname]. Explanation: imm has reported that a memory configuration error has occurred on dimm 11 in compute book 4. May also be shown as 806f070c2b84000b or 0x806f070c2b84000b severity: error alert categor...

  • Page 1095

    806f070c-2b84000d configuration error for [physicalmemoryelementname] on subsystem [memoryelementname]. Explanation: imm has reported that a memory configuration error has occurred on dimm 13 in compute book 4. May also be shown as 806f070c2b84000d or 0x806f070c2b84000d severity: error alert categor...

  • Page 1096

    806f070c-2b84000f configuration error for [physicalmemoryelementname] on subsystem [memoryelementname]. Explanation: imm has reported that a memory configuration error has occurred on dimm 15 in compute book 4. May also be shown as 806f070c2b84000f or 0x806f070c2b84000f severity: error alert categor...

  • Page 1097

    806f070c-2b840011 configuration error for [physicalmemoryelementname] on subsystem [memoryelementname]. Explanation: imm has reported that a memory configuration error has occurred on dimm 17 in compute book 4. May also be shown as 806f070c2b840011 or 0x806f070c2b840011 severity: error alert categor...

  • Page 1098

    806f070c-2b840013 configuration error for [physicalmemoryelementname] on subsystem [memoryelementname]. Explanation: imm has reported that a memory configuration error has occurred on dimm 19 in compute book 4. May also be shown as 806f070c2b840013 or 0x806f070c2b840013 severity: error alert categor...

  • Page 1099

    806f070c-2b840015 configuration error for [physicalmemoryelementname] on subsystem [memoryelementname]. Explanation: imm has reported that a memory configuration error has occurred on dimm 21 in compute book 4. May also be shown as 806f070c2b840015 or 0x806f070c2b840015 severity: error alert categor...

  • Page 1100

    806f070c-2b840017 configuration error for [physicalmemoryelementname] on subsystem [memoryelementname]. Explanation: imm has reported that a memory configuration error has occurred on dimm 23 in compute book 4. May also be shown as 806f070c2b840017 or 0x806f070c2b840017 severity: error alert categor...

  • Page 1101

    806f070c-2b84ffff configuration error for [physicalmemoryelementname] on subsystem [memoryelementname]. Explanation: imm has reported that a memory configuration error has occurred on compute book 4. May also be shown as 806f070c2b84ffff or 0x806f070c2b84ffff severity: error alert category: critical...

  • Page 1102

    806f070d-0402ffff rebuild in progress for array in system [computersystemelementname]. Explanation: imm has detected that an array rebuild on drive 2 is in progress. May also be shown as 806f070d0402ffff or 0x806f070d0402ffff severity: info alert category: system - other serviceable: no cim informat...

  • Page 1103

    806f070d-0405ffff rebuild in progress for array in system [computersystemelementname]. Explanation: imm has detected that an array rebuild on drive 5 is in progress. May also be shown as 806f070d0405ffff or 0x806f070d0405ffff severity: info alert category: system - other serviceable: no cim informat...

  • Page 1104

    806f070d-0408ffff rebuild in progress for array in system [computersystemelementname]. Explanation: imm has detected that an array rebuild on drive 8 is in progress. May also be shown as 806f070d0408ffff or 0x806f070d0408ffff severity: info alert category: system - other serviceable: no cim informat...

  • Page 1105

    806f070d-040bffff rebuild in progress for array in system [computersystemelementname]. Explanation: imm has detected that an array rebuild on drive 11 is in progress. May also be shown as 806f070d040bffff or 0x806f070d040bffff severity: info alert category: system - other serviceable: no cim informa...

  • Page 1106

    806f070d-040effff rebuild in progress for array in system [computersystemelementname]. Explanation: imm has detected that an array rebuild on drive 14 is in progress. May also be shown as 806f070d040effff or 0x806f070d040effff severity: info alert category: system - other serviceable: no cim informa...

  • Page 1107

    806f072b-2201ffff a successful software or firmware change was detected on system [computersystemelementname]. Explanation: successful software or firmware change occured for bkup auto update or rom recovery. May also be shown as 806f072b2201ffff or 0x806f072b2201ffff severity: info alert category: ...

  • Page 1108

    806f0807-0303ffff [processorelementname] has been disabled. Explanation: imm has reported that microprocessor 3 has been disabled. May also be shown as 806f08070303ffff or 0x806f08070303ffff severity: info alert category: system - other serviceable: no cim information: prefix: plat and id: 0061 snmp...

  • Page 1109

    806f0807-2583ffff [processorelementname] has been disabled. Explanation: imm has reported a microprocessor has been disabled. May also be shown as 806f08072583ffff or 0x806f08072583ffff severity: info alert category: system - other serviceable: no cim information: prefix: plat and id: 0061 snmp trap...

  • Page 1110

    806f0813-2582ffff an uncorrectable bus error has occurred on bus [sensorelementname]. Explanation: imm has reported a bus uncorrectable error. May also be shown as 806f08132582ffff or 0x806f08132582ffff severity: error alert category: critical - other serviceable: yes cim information: prefix: plat a...

  • Page 1111

    806f0823-2101ffff watchdog timer interrupt occurred for [watchdogelementname]. Explanation: the watchdog timer has expired. A watchdog interrupt has occurred. May also be shown as 806f08232101ffff or 0x806f08232101ffff severity: info alert category: system - other serviceable: no cim information: pr...

  • Page 1112

    806f090c-2b810002 [physicalmemoryelementname] on subsystem [memoryelementname] throttled. Explanation: imm determined dimm 2 in compute book 1 has been throttled due to high temperature. May also be shown as 806f090c2b810002 or 0x806f090c2b810002 severity: warning alert category: system - other serv...

  • Page 1113

    5. If exflash dimm, make sure the exflash dimm fw is updated to the latest level. 6. If the dimm problem persists and there are no other dimms with the same indication, replace the dimm. 7. If the exflash dimm problem persists and there are no other exflash dimms with the same indication, confirm th...

  • Page 1114

    806f090c-2b810005 [physicalmemoryelementname] on subsystem [memoryelementname] throttled. Explanation: imm determined dimm 5 in compute book 1 has been throttled due to high temperature. May also be shown as 806f090c2b810005 or 0x806f090c2b810005 severity: warning alert category: system - other serv...

  • Page 1115

    5. If exflash dimm, make sure the exflash dimm fw is updated to the latest level. 6. If the dimm problem persists and there are no other dimms with the same indication, replace the dimm. 7. If the exflash dimm problem persists and there are no other exflash dimms with the same indication, confirm th...

  • Page 1116

    806f090c-2b810008 [physicalmemoryelementname] on subsystem [memoryelementname] throttled. Explanation: imm determined dimm 8 in compute book 1 has been throttled due to high temperature. May also be shown as 806f090c2b810008 or 0x806f090c2b810008 severity: warning alert category: system - other serv...

  • Page 1117

    5. If exflash dimm, make sure the exflash dimm fw is updated to the latest level. 6. If the dimm problem persists and there are no other dimms with the same indication, replace the dimm. 7. If the exflash dimm problem persists and there are no other exflash dimms with the same indication, confirm th...

  • Page 1118

    806f090c-2b81000b [physicalmemoryelementname] on subsystem [memoryelementname] throttled. Explanation: imm determined dimm 11 in compute book 1 has been throttled due to high temperature. May also be shown as 806f090c2b81000b or 0x806f090c2b81000b severity: warning alert category: system - other ser...

  • Page 1119

    5. If exflash dimm, make sure the exflash dimm fw is updated to the latest level. 6. If the dimm problem persists and there are no other dimms with the same indication, replace the dimm. 7. If the exflash dimm problem persists and there are no other exflash dimms with the same indication, confirm th...

  • Page 1120

    806f090c-2b81000e [physicalmemoryelementname] on subsystem [memoryelementname] throttled. Explanation: imm determined dimm 14 in compute book 1 has been throttled due to high temperature. May also be shown as 806f090c2b81000e or 0x806f090c2b81000e severity: warning alert category: system - other ser...

  • Page 1121

    5. If exflash dimm, make sure the exflash dimm fw is updated to the latest level. 6. If the dimm problem persists and there are no other dimms with the same indication, replace the dimm. 7. If the exflash dimm problem persists and there are no other exflash dimms with the same indication, confirm th...

  • Page 1122

    806f090c-2b810011 [physicalmemoryelementname] on subsystem [memoryelementname] throttled. Explanation: imm determined dimm 17 in compute book 1 has been throttled due to high temperature. May also be shown as 806f090c2b810011 or 0x806f090c2b810011 severity: warning alert category: system - other ser...

  • Page 1123

    5. If exflash dimm, make sure the exflash dimm fw is updated to the latest level. 6. If the dimm problem persists and there are no other dimms with the same indication, replace the dimm. 7. If the exflash dimm problem persists and there are no other exflash dimms with the same indication, confirm th...

  • Page 1124

    806f090c-2b810014 [physicalmemoryelementname] on subsystem [memoryelementname] throttled. Explanation: imm determined dimm 20 in compute book 1 has been throttled due to high temperature. May also be shown as 806f090c2b810014 or 0x806f090c2b810014 severity: warning alert category: system - other ser...

  • Page 1125

    5. If exflash dimm, make sure the exflash dimm fw is updated to the latest level. 6. If the dimm problem persists and there are no other dimms with the same indication, replace the dimm. 7. If the exflash dimm problem persists and there are no other exflash dimms with the same indication, confirm th...

  • Page 1126

    806f090c-2b810017 [physicalmemoryelementname] on subsystem [memoryelementname] throttled. Explanation: imm determined dimm 23 in compute book 1 has been throttled due to high temperature. May also be shown as 806f090c2b810017 or 0x806f090c2b810017 severity: warning alert category: system - other ser...

  • Page 1127

    5. If exflash dimm, make sure the exflash dimm fw is updated to the latest level. 6. If the dimm problem persists and there are no other dimms with the same indication, replace the dimm. 7. If the exflash dimm problem persists and there are no other exflash dimms with the same indication, confirm th...

  • Page 1128

    806f090c-2b820001 [physicalmemoryelementname] on subsystem [memoryelementname] throttled. Explanation: imm determined dimm 1 in compute book 2 has been throttled due to high temperature. May also be shown as 806f090c2b820001 or 0x806f090c2b820001 severity: warning alert category: system - other serv...

  • Page 1129

    5. If exflash dimm, make sure the exflash dimm fw is updated to the latest level. 6. If the dimm problem persists and there are no other dimms with the same indication, replace the dimm. 7. If the exflash dimm problem persists and there are no other exflash dimms with the same indication, confirm th...

  • Page 1130

    806f090c-2b820004 [physicalmemoryelementname] on subsystem [memoryelementname] throttled. Explanation: imm determined dimm 4 in compute book 2 has been throttled due to high temperature. May also be shown as 806f090c2b820004 or 0x806f090c2b820004 severity: warning alert category: system - other serv...

  • Page 1131

    5. If exflash dimm, make sure the exflash dimm fw is updated to the latest level. 6. If the dimm problem persists and there are no other dimms with the same indication, replace the dimm. 7. If the exflash dimm problem persists and there are no other exflash dimms with the same indication, confirm th...

  • Page 1132

    806f090c-2b820007 [physicalmemoryelementname] on subsystem [memoryelementname] throttled. Explanation: imm determined dimm 7 in compute book 2 has been throttled due to high temperature. May also be shown as 806f090c2b820007 or 0x806f090c2b820007 severity: warning alert category: system - other serv...

  • Page 1133

    5. If exflash dimm, make sure the exflash dimm fw is updated to the latest level. 6. If the dimm problem persists and there are no other dimms with the same indication, replace the dimm. 7. If the exflash dimm problem persists and there are no other exflash dimms with the same indication, confirm th...

  • Page 1134

    806f090c-2b82000a [physicalmemoryelementname] on subsystem [memoryelementname] throttled. Explanation: imm determined dimm 10 in compute book 2 has been throttled due to high temperature. May also be shown as 806f090c2b82000a or 0x806f090c2b82000a severity: warning alert category: system - other ser...

  • Page 1135

    5. If exflash dimm, make sure the exflash dimm fw is updated to the latest level. 6. If the dimm problem persists and there are no other dimms with the same indication, replace the dimm. 7. If the exflash dimm problem persists and there are no other exflash dimms with the same indication, confirm th...

  • Page 1136

    806f090c-2b82000d [physicalmemoryelementname] on subsystem [memoryelementname] throttled. Explanation: imm determined dimm 13 in compute book 2 has been throttled due to high temperature. May also be shown as 806f090c2b82000d or 0x806f090c2b82000d severity: warning alert category: system - other ser...

  • Page 1137

    5. If exflash dimm, make sure the exflash dimm fw is updated to the latest level. 6. If the dimm problem persists and there are no other dimms with the same indication, replace the dimm. 7. If the exflash dimm problem persists and there are no other exflash dimms with the same indication, confirm th...

  • Page 1138

    806f090c-2b820010 [physicalmemoryelementname] on subsystem [memoryelementname] throttled. Explanation: imm determined dimm 16 in compute book 2 has been throttled due to high temperature. May also be shown as 806f090c2b820010 or 0x806f090c2b820010 severity: warning alert category: system - other ser...

  • Page 1139

    5. If exflash dimm, make sure the exflash dimm fw is updated to the latest level. 6. If the dimm problem persists and there are no other dimms with the same indication, replace the dimm. 7. If the exflash dimm problem persists and there are no other exflash dimms with the same indication, confirm th...

  • Page 1140

    806f090c-2b820013 [physicalmemoryelementname] on subsystem [memoryelementname] throttled. Explanation: imm determined dimm 19 in compute book 2 has been throttled due to high temperature. May also be shown as 806f090c2b820013 or 0x806f090c2b820013 severity: warning alert category: system - other ser...

  • Page 1141

    5. If exflash dimm, make sure the exflash dimm fw is updated to the latest level. 6. If the dimm problem persists and there are no other dimms with the same indication, replace the dimm. 7. If the exflash dimm problem persists and there are no other exflash dimms with the same indication, confirm th...

  • Page 1142

    806f090c-2b820016 [physicalmemoryelementname] on subsystem [memoryelementname] throttled. Explanation: imm determined dimm 22 in compute book 2 has been throttled due to high temperature. May also be shown as 806f090c2b820016 or 0x806f090c2b820016 severity: warning alert category: system - other ser...

  • Page 1143

    5. If exflash dimm, make sure the exflash dimm fw is updated to the latest level. 6. If the dimm problem persists and there are no other dimms with the same indication, replace the dimm. 7. If the exflash dimm problem persists and there are no other exflash dimms with the same indication, confirm th...

  • Page 1144

    806f090c-2b82ffff [physicalmemoryelementname] on subsystem [memoryelementname] throttled. Explanation: memory on compute book 2 has been throttled due to high temperature detected by the dimm sensor. May also be shown as 806f090c2b82ffff or 0x806f090c2b82ffff severity: warning alert category: system...

  • Page 1145

    Related links: v “server features and specifications” on page 7 v “removing a ddr3 compute book” on page 283 v “replacing a ddr3 compute book” on page 284 v “removing the ddr3 compute book cover” on page 218 v “replacing the ddr3 compute book cover” on page 220 v “removing a memory module” on page 2...

  • Page 1146

    806f090c-2b830003 [physicalmemoryelementname] on subsystem [memoryelementname] throttled. Explanation: imm determined dimm 3 in compute book 3 has been throttled due to high temperature. May also be shown as 806f090c2b830003 or 0x806f090c2b830003 severity: warning alert category: system - other serv...

  • Page 1147

    5. If exflash dimm, make sure the exflash dimm fw is updated to the latest level. 6. If the dimm problem persists and there are no other dimms with the same indication, replace the dimm. 7. If the exflash dimm problem persists and there are no other exflash dimms with the same indication, confirm th...

  • Page 1148

    806f090c-2b830006 [physicalmemoryelementname] on subsystem [memoryelementname] throttled. Explanation: imm determined dimm 6 in compute book 3 has been throttled due to high temperature. May also be shown as 806f090c2b830006 or 0x806f090c2b830006 severity: warning alert category: system - other serv...

  • Page 1149

    5. If exflash dimm, make sure the exflash dimm fw is updated to the latest level. 6. If the dimm problem persists and there are no other dimms with the same indication, replace the dimm. 7. If the exflash dimm problem persists and there are no other exflash dimms with the same indication, confirm th...

  • Page 1150

    806f090c-2b830009 [physicalmemoryelementname] on subsystem [memoryelementname] throttled. Explanation: imm determined dimm 9 in compute book 3 has been throttled due to high temperature. May also be shown as 806f090c2b830009 or 0x806f090c2b830009 severity: warning alert category: system - other serv...

  • Page 1151

    5. If exflash dimm, make sure the exflash dimm fw is updated to the latest level. 6. If the dimm problem persists and there are no other dimms with the same indication, replace the dimm. 7. If the exflash dimm problem persists and there are no other exflash dimms with the same indication, confirm th...

  • Page 1152

    806f090c-2b83000c [physicalmemoryelementname] on subsystem [memoryelementname] throttled. Explanation: imm determined dimm 12 in compute book 3 has been throttled due to high temperature. May also be shown as 806f090c2b83000c or 0x806f090c2b83000c severity: warning alert category: system - other ser...

  • Page 1153

    5. If exflash dimm, make sure the exflash dimm fw is updated to the latest level. 6. If the dimm problem persists and there are no other dimms with the same indication, replace the dimm. 7. If the exflash dimm problem persists and there are no other exflash dimms with the same indication, confirm th...

  • Page 1154

    806f090c-2b83000f [physicalmemoryelementname] on subsystem [memoryelementname] throttled. Explanation: imm determined dimm 15 in compute book 3 has been throttled due to high temperature. May also be shown as 806f090c2b83000f or 0x806f090c2b83000f severity: warning alert category: system - other ser...

  • Page 1155

    5. If exflash dimm, make sure the exflash dimm fw is updated to the latest level. 6. If the dimm problem persists and there are no other dimms with the same indication, replace the dimm. 7. If the exflash dimm problem persists and there are no other exflash dimms with the same indication, confirm th...

  • Page 1156

    806f090c-2b830012 [physicalmemoryelementname] on subsystem [memoryelementname] throttled. Explanation: imm determined dimm 18 in compute book 3 has been throttled due to high temperature. May also be shown as 806f090c2b830012 or 0x806f090c2b830012 severity: warning alert category: system - other ser...

  • Page 1157

    5. If exflash dimm, make sure the exflash dimm fw is updated to the latest level. 6. If the dimm problem persists and there are no other dimms with the same indication, replace the dimm. 7. If the exflash dimm problem persists and there are no other exflash dimms with the same indication, confirm th...

  • Page 1158

    806f090c-2b830015 [physicalmemoryelementname] on subsystem [memoryelementname] throttled. Explanation: imm determined dimm 21 in compute book 3 has been throttled due to high temperature. May also be shown as 806f090c2b830015 or 0x806f090c2b830015 severity: warning alert category: system - other ser...

  • Page 1159

    5. If exflash dimm, make sure the exflash dimm fw is updated to the latest level. 6. If the dimm problem persists and there are no other dimms with the same indication, replace the dimm. 7. If the exflash dimm problem persists and there are no other exflash dimms with the same indication, confirm th...

  • Page 1160

    806f090c-2b830018 [physicalmemoryelementname] on subsystem [memoryelementname] throttled. Explanation: imm determined dimm 24 in compute book 3 has been throttled due to high temperature. May also be shown as 806f090c2b830018 or 0x806f090c2b830018 severity: warning alert category: system - other ser...

  • Page 1161

    5. If the problem persists and there are no other dimms with the same indication, replace the dimm. Related links: v “server features and specifications” on page 7 v “removing a ddr3 compute book” on page 283 v “replacing a ddr3 compute book” on page 284 v “removing the ddr3 compute book cover” on p...

  • Page 1162

    806f090c-2b840002 [physicalmemoryelementname] on subsystem [memoryelementname] throttled. Explanation: imm determined dimm 2 in compute book 4 has been throttled due to high temperature. May also be shown as 806f090c2b840002 or 0x806f090c2b840002 severity: warning alert category: system - other serv...

  • Page 1163

    5. If exflash dimm, make sure the exflash dimm fw is updated to the latest level. 6. If the dimm problem persists and there are no other dimms with the same indication, replace the dimm. 7. If the exflash dimm problem persists and there are no other exflash dimms with the same indication, confirm th...

  • Page 1164

    806f090c-2b840005 [physicalmemoryelementname] on subsystem [memoryelementname] throttled. Explanation: imm determined dimm 5 in compute book 4 has been throttled due to high temperature. May also be shown as 806f090c2b840005 or 0x806f090c2b840005 severity: warning alert category: system - other serv...

  • Page 1165

    5. If exflash dimm, make sure the exflash dimm fw is updated to the latest level. 6. If the dimm problem persists and there are no other dimms with the same indication, replace the dimm. 7. If the exflash dimm problem persists and there are no other exflash dimms with the same indication, confirm th...

  • Page 1166

    806f090c-2b840008 [physicalmemoryelementname] on subsystem [memoryelementname] throttled. Explanation: imm determined dimm 8 in compute book 4 has been throttled due to high temperature. May also be shown as 806f090c2b840008 or 0x806f090c2b840008 severity: warning alert category: system - other serv...

  • Page 1167

    5. If exflash dimm, make sure the exflash dimm fw is updated to the latest level. 6. If the dimm problem persists and there are no other dimms with the same indication, replace the dimm. 7. If the exflash dimm problem persists and there are no other exflash dimms with the same indication, confirm th...

  • Page 1168

    806f090c-2b84000b [physicalmemoryelementname] on subsystem [memoryelementname] throttled. Explanation: imm determined dimm 11 in compute book 4 has been throttled due to high temperature. May also be shown as 806f090c2b84000b or 0x806f090c2b84000b severity: warning alert category: system - other ser...

  • Page 1169

    5. If exflash dimm, make sure the exflash dimm fw is updated to the latest level. 6. If the dimm problem persists and there are no other dimms with the same indication, replace the dimm. 7. If the exflash dimm problem persists and there are no other exflash dimms with the same indication, confirm th...

  • Page 1170

    806f090c-2b84000e [physicalmemoryelementname] on subsystem [memoryelementname] throttled. Explanation: imm determined dimm 14 in compute book 4 has been throttled due to high temperature. May also be shown as 806f090c2b84000e or 0x806f090c2b84000e severity: warning alert category: system - other ser...

  • Page 1171

    5. If exflash dimm, make sure the exflash dimm fw is updated to the latest level. 6. If the dimm problem persists and there are no other dimms with the same indication, replace the dimm. 7. If the exflash dimm problem persists and there are no other exflash dimms with the same indication, confirm th...

  • Page 1172

    806f090c-2b840011 [physicalmemoryelementname] on subsystem [memoryelementname] throttled. Explanation: imm determined dimm 17 in compute book 4 has been throttled due to high temperature. May also be shown as 806f090c2b840011 or 0x806f090c2b840011 severity: warning alert category: system - other ser...

  • Page 1173

    5. If exflash dimm, make sure the exflash dimm fw is updated to the latest level. 6. If the dimm problem persists and there are no other dimms with the same indication, replace the dimm. 7. If the exflash dimm problem persists and there are no other exflash dimms with the same indication, confirm th...

  • Page 1174

    806f090c-2b840014 [physicalmemoryelementname] on subsystem [memoryelementname] throttled. Explanation: imm determined dimm 20 in compute book 4 has been throttled due to high temperature. May also be shown as 806f090c2b840014 or 0x806f090c2b840014 severity: warning alert category: system - other ser...

  • Page 1175

    5. If exflash dimm, make sure the exflash dimm fw is updated to the latest level. 6. If the dimm problem persists and there are no other dimms with the same indication, replace the dimm. 7. If the exflash dimm problem persists and there are no other exflash dimms with the same indication, confirm th...

  • Page 1176

    806f090c-2b840017 [physicalmemoryelementname] on subsystem [memoryelementname] throttled. Explanation: imm determined dimm 23 in compute book 4 has been throttled due to high temperature. May also be shown as 806f090c2b840017 or 0x806f090c2b840017 severity: warning alert category: system - other ser...

  • Page 1177

    5. If exflash dimm, make sure the exflash dimm fw is updated to the latest level. 6. If the dimm problem persists and there are no other dimms with the same indication, replace the dimm. 7. If the exflash dimm problem persists and there are no other exflash dimms with the same indication, confirm th...

  • Page 1178

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

  • Page 1179

    V “solving power problems” on page 197 v “installing power supplies” on page 104 806f0a07-0303ffff [processorelementname] is operating in a degraded state. Explanation: the microprocessor 3 is being throttled due to thermal or power conditions. May also be shown as 806f0a070303ffff or 0x806f0a070303...

  • Page 1180

    2. If using a 900 watt rated power supply (connected at either 110v or 220 v ), may need to upgrade to a 1400 watt rated power supply (connected at 220v). Related links: v “server features and specifications” on page 7 v “solving power problems” on page 197 v “installing power supplies” on page 104 ...

  • Page 1181

    806f0a0c-2b810002 an over-temperature condition has been detected on the [physicalmemoryelementname] on subsystem [memoryelementname]. Explanation: imm determined dimm 2 in compute book 1 has an over temperature condition. May also be shown as 806f0a0c2b810002 or 0x806f0a0c2b810002 severity: error a...

  • Page 1182

    4. Check ibm support site for service bulletins/retain tips related to an over temperature condition. 5. If exflash dimm, make sure the exflash dimm fw is updated to the latest level. 6. If the dimm problem persists and there are no other dimms with the same indication, replace the dimm. 7. If the e...

  • Page 1183

    806f0a0c-2b810005 an over-temperature condition has been detected on the [physicalmemoryelementname] on subsystem [memoryelementname]. Explanation: imm determined dimm 5 in compute book 1 has an over temperature condition. May also be shown as 806f0a0c2b810005 or 0x806f0a0c2b810005 severity: error a...

  • Page 1184

    4. Check ibm support site for service bulletins/retain tips related to an over temperature condition. 5. If exflash dimm, make sure the exflash dimm fw is updated to the latest level. 6. If the dimm problem persists and there are no other dimms with the same indication, replace the dimm. 7. If the e...

  • Page 1185

    806f0a0c-2b810008 an over-temperature condition has been detected on the [physicalmemoryelementname] on subsystem [memoryelementname]. Explanation: imm determined dimm 8 in compute book 1 has an over temperature condition. May also be shown as 806f0a0c2b810008 or 0x806f0a0c2b810008 severity: error a...

  • Page 1186

    4. Check ibm support site for service bulletins/retain tips related to an over temperature condition. 5. If exflash dimm, make sure the exflash dimm fw is updated to the latest level. 6. If the dimm problem persists and there are no other dimms with the same indication, replace the dimm. 7. If the e...

  • Page 1187

    806f0a0c-2b81000b an over-temperature condition has been detected on the [physicalmemoryelementname] on subsystem [memoryelementname]. Explanation: imm determined dimm 11 in compute book 1 has an over temperature condition. May also be shown as 806f0a0c2b81000b or 0x806f0a0c2b81000b severity: error ...

  • Page 1188

    4. Check ibm support site for service bulletins/retain tips related to an over temperature condition. 5. If exflash dimm, make sure the exflash dimm fw is updated to the latest level. 6. If the dimm problem persists and there are no other dimms with the same indication, replace the dimm. 7. If the e...

  • Page 1189

    806f0a0c-2b81000e an over-temperature condition has been detected on the [physicalmemoryelementname] on subsystem [memoryelementname]. Explanation: imm determined dimm 14 in compute book 1 has an over temperature condition. May also be shown as 806f0a0c2b81000e or 0x806f0a0c2b81000e severity: error ...

  • Page 1190

    4. Check ibm support site for service bulletins/retain tips related to an over temperature condition. 5. If exflash dimm, make sure the exflash dimm fw is updated to the latest level. 6. If the dimm problem persists and there are no other dimms with the same indication, replace the dimm. 7. If the e...

  • Page 1191

    806f0a0c-2b810011 an over-temperature condition has been detected on the [physicalmemoryelementname] on subsystem [memoryelementname]. Explanation: imm determined dimm 17 in compute book 1 has an over temperature condition. May also be shown as 806f0a0c2b810011 or 0x806f0a0c2b810011 severity: error ...

  • Page 1192

    4. Check ibm support site for service bulletins/retain tips related to an over temperature condition. 5. If exflash dimm, make sure the exflash dimm fw is updated to the latest level. 6. If the dimm problem persists and there are no other dimms with the same indication, replace the dimm. 7. If the e...

  • Page 1193

    806f0a0c-2b810014 an over-temperature condition has been detected on the [physicalmemoryelementname] on subsystem [memoryelementname]. Explanation: imm determined dimm 20 in compute book 1 has an over temperature condition. May also be shown as 806f0a0c2b810014 or 0x806f0a0c2b810014 severity: error ...

  • Page 1194

    4. Check ibm support site for service bulletins/retain tips related to an over temperature condition. 5. If exflash dimm, make sure the exflash dimm fw is updated to the latest level. 6. If the dimm problem persists and there are no other dimms with the same indication, replace the dimm. 7. If the e...

  • Page 1195

    806f0a0c-2b810017 an over-temperature condition has been detected on the [physicalmemoryelementname] on subsystem [memoryelementname]. Explanation: imm determined dimm 23 in compute book 1 has an over temperature condition. May also be shown as 806f0a0c2b810017 or 0x806f0a0c2b810017 severity: error ...

  • Page 1196

    4. Check ibm support site for service bulletins/retain tips related to an over temperature condition. 5. If exflash dimm, make sure the exflash dimm fw is updated to the latest level. 6. If the dimm problem persists and there are no other dimms with the same indication, replace the dimm. 7. If the e...

  • Page 1197

    806f0a0c-2b820001 an over-temperature condition has been detected on the [physicalmemoryelementname] on subsystem [memoryelementname]. Explanation: imm determined dimm 1 in compute book 2 has an over temperature condition. May also be shown as 806f0a0c2b820001 or 0x806f0a0c2b820001 severity: error a...

  • Page 1198

    4. Check ibm support site for service bulletins/retain tips related to an over temperature condition. 5. If exflash dimm, make sure the exflash dimm fw is updated to the latest level. 6. If the dimm problem persists and there are no other dimms with the same indication, replace the dimm. 7. If the e...

  • Page 1199

    806f0a0c-2b820004 an over-temperature condition has been detected on the [physicalmemoryelementname] on subsystem [memoryelementname]. Explanation: imm determined dimm 4 in compute book 2 has an over temperature condition. May also be shown as 806f0a0c2b820004 or 0x806f0a0c2b820004 severity: error a...

  • Page 1200

    4. Check ibm support site for service bulletins/retain tips related to an over temperature condition. 5. If exflash dimm, make sure the exflash dimm fw is updated to the latest level. 6. If the dimm problem persists and there are no other dimms with the same indication, replace the dimm. 7. If the e...

  • Page 1201

    806f0a0c-2b820007 an over-temperature condition has been detected on the [physicalmemoryelementname] on subsystem [memoryelementname]. Explanation: imm determined dimm 7 in compute book 2 has an over temperature condition. May also be shown as 806f0a0c2b820007 or 0x806f0a0c2b820007 severity: error a...

  • Page 1202

    4. Check ibm support site for service bulletins/retain tips related to an over temperature condition. 5. If exflash dimm, make sure the exflash dimm fw is updated to the latest level. 6. If the dimm problem persists and there are no other dimms with the same indication, replace the dimm. 7. If the e...

  • Page 1203

    806f0a0c-2b82000a an over-temperature condition has been detected on the [physicalmemoryelementname] on subsystem [memoryelementname]. Explanation: imm determined dimm 10 in compute book 2 has an over temperature condition. May also be shown as 806f0a0c2b82000a or 0x806f0a0c2b82000a severity: error ...

  • Page 1204

    4. Check ibm support site for service bulletins/retain tips related to an over temperature condition. 5. If exflash dimm, make sure the exflash dimm fw is updated to the latest level. 6. If the dimm problem persists and there are no other dimms with the same indication, replace the dimm. 7. If the e...

  • Page 1205

    806f0a0c-2b82000d an over-temperature condition has been detected on the [physicalmemoryelementname] on subsystem [memoryelementname]. Explanation: imm determined dimm 13 in compute book 2 has an over temperature condition. May also be shown as 806f0a0c2b82000d or 0x806f0a0c2b82000d severity: error ...

  • Page 1206

    4. Check ibm support site for service bulletins/retain tips related to an over temperature condition. 5. If exflash dimm, make sure the exflash dimm fw is updated to the latest level. 6. If the dimm problem persists and there are no other dimms with the same indication, replace the dimm. 7. If the e...

  • Page 1207

    806f0a0c-2b820010 an over-temperature condition has been detected on the [physicalmemoryelementname] on subsystem [memoryelementname]. Explanation: imm determined dimm 16 in compute book 2 has an over temperature condition. May also be shown as 806f0a0c2b820010 or 0x806f0a0c2b820010 severity: error ...

  • Page 1208

    4. Check ibm support site for service bulletins/retain tips related to an over temperature condition. 5. If exflash dimm, make sure the exflash dimm fw is updated to the latest level. 6. If the dimm problem persists and there are no other dimms with the same indication, replace the dimm. 7. If the e...

  • Page 1209

    806f0a0c-2b820013 an over-temperature condition has been detected on the [physicalmemoryelementname] on subsystem [memoryelementname]. Explanation: imm determined dimm 19 in compute book 2 has an over temperature condition. May also be shown as 806f0a0c2b820013 or 0x806f0a0c2b820013 severity: error ...

  • Page 1210

    4. Check ibm support site for service bulletins/retain tips related to an over temperature condition. 5. If exflash dimm, make sure the exflash dimm fw is updated to the latest level. 6. If the dimm problem persists and there are no other dimms with the same indication, replace the dimm. 7. If the e...

  • Page 1211

    806f0a0c-2b820016 an over-temperature condition has been detected on the [physicalmemoryelementname] on subsystem [memoryelementname]. Explanation: imm determined dimm 22 in compute book 2 has an over temperature condition. May also be shown as 806f0a0c2b820016 or 0x806f0a0c2b820016 severity: error ...

  • Page 1212

    4. Check ibm support site for service bulletins/retain tips related to an over temperature condition. 5. If exflash dimm, make sure the exflash dimm fw is updated to the latest level. 6. If the dimm problem persists and there are no other dimms with the same indication, replace the dimm. 7. If the e...

  • Page 1213

    806f0a0c-2b82ffff an over-temperature condition has been detected on the [physicalmemoryelementname] on subsystem [memoryelementname]. Explanation: imm has detected an over temperature condition for memory on compute book 2. May also be shown as 806f0a0c2b82ffff or 0x806f0a0c2b82ffff severity: error...

  • Page 1214

    7. If the exflash dimm problem persists and there are no other exflash dimms with the same indication, confirm that the exflash dimm is under warranty before replacement. Related links: v “server features and specifications” on page 7 v “removing a ddr3 compute book” on page 283 v “replacing a ddr3 ...

  • Page 1215

    806f0a0c-2b830003 an over-temperature condition has been detected on the [physicalmemoryelementname] on subsystem [memoryelementname]. Explanation: imm determined dimm 3 in compute book 3 has an over temperature condition. May also be shown as 806f0a0c2b830003 or 0x806f0a0c2b830003 severity: error a...

  • Page 1216

    4. Check ibm support site for service bulletins/retain tips related to an over temperature condition. 5. If exflash dimm, make sure the exflash dimm fw is updated to the latest level. 6. If the dimm problem persists and there are no other dimms with the same indication, replace the dimm. 7. If the e...

  • Page 1217

    806f0a0c-2b830006 an over-temperature condition has been detected on the [physicalmemoryelementname] on subsystem [memoryelementname]. Explanation: imm determined dimm 6 in compute book 3 has an over temperature condition. May also be shown as 806f0a0c2b830006 or 0x806f0a0c2b830006 severity: error a...

  • Page 1218

    4. Check ibm support site for service bulletins/retain tips related to an over temperature condition. 5. If exflash dimm, make sure the exflash dimm fw is updated to the latest level. 6. If the dimm problem persists and there are no other dimms with the same indication, replace the dimm. 7. If the e...

  • Page 1219

    806f0a0c-2b830009 an over-temperature condition has been detected on the [physicalmemoryelementname] on subsystem [memoryelementname]. Explanation: imm determined dimm 9 in compute book 3 has an over temperature condition. May also be shown as 806f0a0c2b830009 or 0x806f0a0c2b830009 severity: error a...

  • Page 1220

    4. Check ibm support site for service bulletins/retain tips related to an over temperature condition. 5. If exflash dimm, make sure the exflash dimm fw is updated to the latest level. 6. If the dimm problem persists and there are no other dimms with the same indication, replace the dimm. 7. If the e...

  • Page 1221

    806f0a0c-2b83000c an over-temperature condition has been detected on the [physicalmemoryelementname] on subsystem [memoryelementname]. Explanation: imm determined dimm 12 in compute book 3 has an over temperature condition. May also be shown as 806f0a0c2b83000c or 0x806f0a0c2b83000c severity: error ...

  • Page 1222

    4. Check ibm support site for service bulletins/retain tips related to an over temperature condition. 5. If exflash dimm, make sure the exflash dimm fw is updated to the latest level. 6. If the dimm problem persists and there are no other dimms with the same indication, replace the dimm. 7. If the e...

  • Page 1223

    806f0a0c-2b83000f an over-temperature condition has been detected on the [physicalmemoryelementname] on subsystem [memoryelementname]. Explanation: imm determined dimm 15 in compute book 3 has an over temperature condition. May also be shown as 806f0a0c2b83000f or 0x806f0a0c2b83000f severity: error ...

  • Page 1224

    4. Check ibm support site for service bulletins/retain tips related to an over temperature condition. 5. If exflash dimm, make sure the exflash dimm fw is updated to the latest level. 6. If the dimm problem persists and there are no other dimms with the same indication, replace the dimm. 7. If the e...

  • Page 1225

    806f0a0c-2b830012 an over-temperature condition has been detected on the [physicalmemoryelementname] on subsystem [memoryelementname]. Explanation: imm determined dimm 18 in compute book 3 has an over temperature condition. May also be shown as 806f0a0c2b830012 or 0x806f0a0c2b830012 severity: error ...

  • Page 1226

    4. Check ibm support site for service bulletins/retain tips related to an over temperature condition. 5. If exflash dimm, make sure the exflash dimm fw is updated to the latest level. 6. If the dimm problem persists and there are no other dimms with the same indication, replace the dimm. 7. If the e...

  • Page 1227

    806f0a0c-2b830015 an over-temperature condition has been detected on the [physicalmemoryelementname] on subsystem [memoryelementname]. Explanation: imm determined dimm 21 in compute book 3 has an over temperature condition. May also be shown as 806f0a0c2b830015 or 0x806f0a0c2b830015 severity: error ...

  • Page 1228

    4. Check ibm support site for service bulletins/retain tips related to an over temperature condition. 5. If exflash dimm, make sure the exflash dimm fw is updated to the latest level. 6. If the dimm problem persists and there are no other dimms with the same indication, replace the dimm. 7. If the e...

  • Page 1229

    806f0a0c-2b830018 an over-temperature condition has been detected on the [physicalmemoryelementname] on subsystem [memoryelementname]. Explanation: imm determined dimm 24 in compute book 3 has an over temperature condition. May also be shown as 806f0a0c2b830018 or 0x806f0a0c2b830018 severity: error ...

  • Page 1230

    4. Check ibm support site for service bulletins/retain tips related to an over temperature condition. 5. If the problem persists and there are no other dimms with the same indication, replace the dimm. Related links: v “server features and specifications” on page 7 v “removing a ddr3 compute book” o...

  • Page 1231

    806f0a0c-2b840002 an over-temperature condition has been detected on the [physicalmemoryelementname] on subsystem [memoryelementname]. Explanation: imm determined dimm 2 in compute book 4 has an over temperature condition. May also be shown as 806f0a0c2b840002 or 0x806f0a0c2b840002 severity: error a...

  • Page 1232

    4. Check ibm support site for service bulletins/retain tips related to an over temperature condition. 5. If exflash dimm, make sure the exflash dimm fw is updated to the latest level. 6. If the dimm problem persists and there are no other dimms with the same indication, replace the dimm. 7. If the e...

  • Page 1233

    806f0a0c-2b840005 an over-temperature condition has been detected on the [physicalmemoryelementname] on subsystem [memoryelementname]. Explanation: imm determined dimm 5 in compute book 4 has an over temperature condition. May also be shown as 806f0a0c2b840005 or 0x806f0a0c2b840005 severity: error a...

  • Page 1234

    4. Check ibm support site for service bulletins/retain tips related to an over temperature condition. 5. If exflash dimm, make sure the exflash dimm fw is updated to the latest level. 6. If the dimm problem persists and there are no other dimms with the same indication, replace the dimm. 7. If the e...

  • Page 1235

    806f0a0c-2b840008 an over-temperature condition has been detected on the [physicalmemoryelementname] on subsystem [memoryelementname]. Explanation: imm determined dimm 8 in compute book 4 has an over temperature condition. May also be shown as 806f0a0c2b840008 or 0x806f0a0c2b840008 severity: error a...

  • Page 1236

    4. Check ibm support site for service bulletins/retain tips related to an over temperature condition. 5. If exflash dimm, make sure the exflash dimm fw is updated to the latest level. 6. If the dimm problem persists and there are no other dimms with the same indication, replace the dimm. 7. If the e...

  • Page 1237

    806f0a0c-2b84000b an over-temperature condition has been detected on the [physicalmemoryelementname] on subsystem [memoryelementname]. Explanation: imm determined dimm 11 in compute book 4 has an over temperature condition. May also be shown as 806f0a0c2b84000b or 0x806f0a0c2b84000b severity: error ...

  • Page 1238

    4. Check ibm support site for service bulletins/retain tips related to an over temperature condition. 5. If exflash dimm, make sure the exflash dimm fw is updated to the latest level. 6. If the dimm problem persists and there are no other dimms with the same indication, replace the dimm. 7. If the e...

  • Page 1239

    806f0a0c-2b84000e an over-temperature condition has been detected on the [physicalmemoryelementname] on subsystem [memoryelementname]. Explanation: imm determined dimm 14 in compute book 4 has an over temperature condition. May also be shown as 806f0a0c2b84000e or 0x806f0a0c2b84000e severity: error ...

  • Page 1240

    4. Check ibm support site for service bulletins/retain tips related to an over temperature condition. 5. If exflash dimm, make sure the exflash dimm fw is updated to the latest level. 6. If the dimm problem persists and there are no other dimms with the same indication, replace the dimm. 7. If the e...

  • Page 1241

    806f0a0c-2b840011 an over-temperature condition has been detected on the [physicalmemoryelementname] on subsystem [memoryelementname]. Explanation: imm determined dimm 17 in compute book 4 has an over temperature condition. May also be shown as 806f0a0c2b840011 or 0x806f0a0c2b840011 severity: error ...

  • Page 1242

    4. Check ibm support site for service bulletins/retain tips related to an over temperature condition. 5. If exflash dimm, make sure the exflash dimm fw is updated to the latest level. 6. If the dimm problem persists and there are no other dimms with the same indication, replace the dimm. 7. If the e...

  • Page 1243

    806f0a0c-2b840014 an over-temperature condition has been detected on the [physicalmemoryelementname] on subsystem [memoryelementname]. Explanation: imm determined dimm 20 in compute book 4 has an over temperature condition. May also be shown as 806f0a0c2b840014 or 0x806f0a0c2b840014 severity: error ...

  • Page 1244

    4. Check ibm support site for service bulletins/retain tips related to an over temperature condition. 5. If exflash dimm, make sure the exflash dimm fw is updated to the latest level. 6. If the dimm problem persists and there are no other dimms with the same indication, replace the dimm. 7. If the e...

  • Page 1245

    806f0a0c-2b840017 an over-temperature condition has been detected on the [physicalmemoryelementname] on subsystem [memoryelementname]. Explanation: imm determined dimm 23 in compute book 4 has an over temperature condition. May also be shown as 806f0a0c2b840017 or 0x806f0a0c2b840017 severity: error ...

  • Page 1246

    4. Check ibm support site for service bulletins/retain tips related to an over temperature condition. 5. If exflash dimm, make sure the exflash dimm fw is updated to the latest level. 6. If the dimm problem persists and there are no other dimms with the same indication, replace the dimm. 7. If the e...

  • Page 1247

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

  • Page 1248

    81010002-2801ffff numeric sensor [numericsensorelementname] going low (lower non-critical) has deasserted. Explanation: the cmos battery has returned to a normal voltage level. May also be shown as 810100022801ffff or 0x810100022801ffff severity: info alert category: warning - voltage serviceable: n...

  • Page 1249

    81010204-1d01ffff numeric sensor [numericsensorelementname] going low (lower critical) has deasserted. Explanation: imm has detected fan 1a or fan 1b has recovered from a low speed condition. May also be shown as 810102041d01ffff or 0x810102041d01ffff severity: info alert category: critical - fan fa...

  • Page 1250

    81010204-1d04ffff numeric sensor [numericsensorelementname] going low (lower critical) has deasserted. Explanation: imm has detected fan 4a or fan 4b has recovered from a low speed condition. May also be shown as 810102041d04ffff or 0x810102041d04ffff severity: info alert category: critical - fan fa...

  • Page 1251

    81010204-1d07ffff numeric sensor [numericsensorelementname] going low (lower critical) has deasserted. Explanation: imm has detected fan 7a or fan 7b has recovered from a low speed condition. May also be shown as 810102041d07ffff or 0x810102041d07ffff severity: info alert category: critical - fan fa...

  • Page 1252

    81010204-1d0affff numeric sensor [numericsensorelementname] going low (lower critical) has deasserted. Explanation: imm has detected fan 10a or fan 10b has recovered from a low speed condition. May also be shown as 810102041d0affff or 0x810102041d0affff severity: info alert category: critical - fan ...

  • Page 1253

    81010901-2701ffff numeric sensor [numericsensorelementname] going high (upper critical) has deasserted. Explanation: imm has detected that the ambient temperature has returned to a normal range. May also be shown as 810109012701ffff or 0x810109012701ffff severity: info alert category: critical - tem...

  • Page 1254

    81010b01-2701ffff numeric sensor [numericsensorelementname] going high (upper non-recoverable) has deasserted. Explanation: imm has detected that the ambient temperature has returned to a normal range. May also be shown as 81010b012701ffff or 0x81010b012701ffff severity: info alert category: critica...

  • Page 1255

    8103000f-2101ffff sensor [sensorelementname] has asserted. Explanation: this message is for the use case when an implementation has detected a sensor has asserted. May also be shown as 8103000f2101ffff or 0x8103000f2101ffff severity: info alert category: system - other serviceable: no cim informatio...

  • Page 1256

    8103010e-2581ffff sensor [sensorelementname] has deasserted. Explanation: imm has reported that the memory size has returned to a previous configuration. May also be shown as 8103010e2581ffff or 0x8103010e2581ffff severity: info alert category: system - other serviceable: no cim information: prefix:...

  • Page 1257

    81040104-1d02ffff sensor [sensorelementname] is deasserting predictive failure. Explanation: imm has detected that fan 2 has recovered from a predictive failure (pfa). May also be shown as 810401041d02ffff or 0x810401041d02ffff severity: info alert category: system - predicted failure serviceable: n...

  • Page 1258

    81040104-1d05ffff sensor [sensorelementname] is deasserting predictive failure. Explanation: imm has detected that fan 5 has recovered from a predictive failure (pfa). May also be shown as 810401041d05ffff or 0x810401041d05ffff severity: info alert category: system - predicted failure serviceable: n...

  • Page 1259

    81040104-1d08ffff sensor [sensorelementname] is deasserting predictive failure. Explanation: imm has detected that fan 8 has recovered from a predictive failure (pfa). May also be shown as 810401041d08ffff or 0x810401041d08ffff severity: info alert category: system - predicted failure serviceable: n...

  • Page 1260

    81070101-0301ffff sensor [sensorelementname] has deasserted the transition from normal to non-critical state. Explanation: imm has detected that compute book 1 has returned to a normal temperature. May also be shown as 810701010301ffff or 0x810701010301ffff severity: info alert category: warning - t...

  • Page 1261

    81070101-0304ffff sensor [sensorelementname] has deasserted the transition from normal to non-critical state. Explanation: imm has detected that compute book 4 has returned to a normal temperature. May also be shown as 810701010304ffff or 0x810701010304ffff severity: info alert category: warning - t...

  • Page 1262

    81070101-0b03ffff sensor [sensorelementname] has deasserted the transition from normal to non-critical state. Explanation: this message is for the use case when an implementation has detected that a sensor has deasserted a transition to non-critical from normal. May also be shown as 810701010b03ffff...

  • Page 1263

    81070101-0b06ffff sensor [sensorelementname] has deasserted the transition from normal to non-critical state. Explanation: this message is for the use case when an implementation has detected that a sensor has deasserted a transition to non-critical from normal. May also be shown as 810701010b06ffff...

  • Page 1264

    81070107-0302ffff sensor [sensorelementname] has deasserted the transition from normal to non-critical state. Explanation: the compute book 2 has been added to the system. May also be shown as 810701070302ffff or 0x810701070302ffff severity: info alert category: warning - other serviceable: no cim i...

  • Page 1265

    81070107-2583ffff sensor [sensorelementname] has deasserted the transition from normal to non-critical state. Explanation: imm has detected the cpu population error has been deasserted. May also be shown as 810701072583ffff or 0x810701072583ffff severity: info alert category: warning - other service...

  • Page 1266

    8107010d-2b810001 sensor [sensorelementname] has deasserted the transition to non-critical state. Explanation: the exflash ipmi proxy service has indicated exflash dimm 1 in compute book 1 has deasserted the 10% write warrenty sensor. May also be shown as 8107010d2b810001 or 0x8107010d2b810001 sever...

  • Page 1267

    8107010d-2b810004 sensor [sensorelementname] has deasserted the transition to non-critical state. Explanation: the exflash ipmi proxy service has indicated exflash dimm 4 in compute book 1 has deasserted the 10% write warrenty sensor. May also be shown as 8107010d2b810004 or 0x8107010d2b810004 sever...

  • Page 1268

    8107010d-2b810007 sensor [sensorelementname] has deasserted the transition to non-critical state. Explanation: the exflash ipmi proxy service has indicated exflash dimm 7 in compute book 1 has deasserted the 10% write warrenty sensor. May also be shown as 8107010d2b810007 or 0x8107010d2b810007 sever...

  • Page 1269

    8107010d-2b81000a sensor [sensorelementname] has deasserted the transition to non-critical state. Explanation: the exflash ipmi proxy service has indicated exflash dimm 10 in compute book 1 has deasserted the 10% write warrenty sensor. May also be shown as 8107010d2b81000a or 0x8107010d2b81000a seve...

  • Page 1270

    8107010d-2b81000d sensor [sensorelementname] has deasserted the transition to non-critical state. Explanation: the exflash ipmi proxy service has indicated exflash dimm 13 in compute book 1 has deasserted the 10% write warrenty sensor. May also be shown as 8107010d2b81000d or 0x8107010d2b81000d seve...

  • Page 1271

    8107010d-2b810010 sensor [sensorelementname] has deasserted the transition to non-critical state. Explanation: the exflash ipmi proxy service has indicated exflash dimm 16 in compute book 1 has deasserted the 10% write warrenty sensor. May also be shown as 8107010d2b810010 or 0x8107010d2b810010 seve...

  • Page 1272

    8107010d-2b810013 sensor [sensorelementname] has deasserted the transition to non-critical state. Explanation: the exflash ipmi proxy service has indicated exflash dimm 19 in compute book 1 has deasserted the 10% write warrenty sensor. May also be shown as 8107010d2b810013 or 0x8107010d2b810013 seve...

  • Page 1273

    8107010d-2b810016 sensor [sensorelementname] has deasserted the transition to non-critical state. Explanation: the exflash ipmi proxy service has indicated exflash dimm 22 in compute book 1 has deasserted the 10% write warrenty sensor. May also be shown as 8107010d2b810016 or 0x8107010d2b810016 seve...

  • Page 1274

    8107010d-2b81ffff sensor [sensorelementname] has deasserted the transition to non-critical state. Explanation: the imm has detected that the sensor deasserted. May also be shown as 8107010d2b81ffff or 0x8107010d2b81ffff severity: warning alert category: warning - other serviceable: yes cim informati...

  • Page 1275

    8107010d-2b820003 sensor [sensorelementname] has deasserted the transition to non-critical state. Explanation: the exflash ipmi proxy service has indicated exflash dimm 3 in compute book 2 has deasserted the 10% write warrenty sensor. May also be shown as 8107010d2b820003 or 0x8107010d2b820003 sever...

  • Page 1276

    8107010d-2b820006 sensor [sensorelementname] has deasserted the transition to non-critical state. Explanation: the exflash ipmi proxy service has indicated exflash dimm 6 in compute book 2 has deasserted the 10% write warrenty sensor. May also be shown as 8107010d2b820006 or 0x8107010d2b820006 sever...

  • Page 1277

    8107010d-2b820009 sensor [sensorelementname] has deasserted the transition to non-critical state. Explanation: the exflash ipmi proxy service has indicated exflash dimm 9 in compute book 2 has deasserted the 10% write warrenty sensor. May also be shown as 8107010d2b820009 or 0x8107010d2b820009 sever...

  • Page 1278

    8107010d-2b82000c sensor [sensorelementname] has deasserted the transition to non-critical state. Explanation: the exflash ipmi proxy service has indicated exflash dimm 12 in compute book 2 has deasserted the 10% write warrenty sensor. May also be shown as 8107010d2b82000c or 0x8107010d2b82000c seve...

  • Page 1279

    8107010d-2b82000f sensor [sensorelementname] has deasserted the transition to non-critical state. Explanation: the exflash ipmi proxy service has indicated exflash dimm 15 in compute book 2 has deasserted the 10% write warrenty sensor. May also be shown as 8107010d2b82000f or 0x8107010d2b82000f seve...

  • Page 1280

    8107010d-2b820012 sensor [sensorelementname] has deasserted the transition to non-critical state. Explanation: the exflash ipmi proxy service has indicated exflash dimm 18 in compute book 2 has deasserted the 10% write warrenty sensor. May also be shown as 8107010d2b820012 or 0x8107010d2b820012 seve...

  • Page 1281

    8107010d-2b820015 sensor [sensorelementname] has deasserted the transition to non-critical state. Explanation: the exflash ipmi proxy service has indicated exflash dimm 21 in compute book 2 has deasserted the 10% write warrenty sensor. May also be shown as 8107010d2b820015 or 0x8107010d2b820015 seve...

  • Page 1282

    8107010d-2b820018 sensor [sensorelementname] has deasserted the transition to non-critical state. Explanation: the exflash ipmi proxy service has indicated exflash dimm 24 in compute book 2 has deasserted the 10% write warrenty sensor. May also be shown as 8107010d2b820018 or 0x8107010d2b820018 seve...

  • Page 1283

    8107010d-2b830002 sensor [sensorelementname] has deasserted the transition to non-critical state. Explanation: the exflash ipmi proxy service has indicated exflash dimm 2 in compute book 3 has deasserted the 10% write warrenty sensor. May also be shown as 8107010d2b830002 or 0x8107010d2b830002 sever...

  • Page 1284

    8107010d-2b830005 sensor [sensorelementname] has deasserted the transition to non-critical state. Explanation: the exflash ipmi proxy service has indicated exflash dimm 5 in compute book 3 has deasserted the 10% write warrenty sensor. May also be shown as 8107010d2b830005 or 0x8107010d2b830005 sever...

  • Page 1285

    8107010d-2b830008 sensor [sensorelementname] has deasserted the transition to non-critical state. Explanation: the exflash ipmi proxy service has indicated exflash dimm 8 in compute book 3 has deasserted the 10% write warrenty sensor. May also be shown as 8107010d2b830008 or 0x8107010d2b830008 sever...

  • Page 1286

    8107010d-2b83000b sensor [sensorelementname] has deasserted the transition to non-critical state. Explanation: the exflash ipmi proxy service has indicated exflash dimm 11 in compute book 3 has deasserted the 10% write warrenty sensor. May also be shown as 8107010d2b83000b or 0x8107010d2b83000b seve...

  • Page 1287

    8107010d-2b83000e sensor [sensorelementname] has deasserted the transition to non-critical state. Explanation: the exflash ipmi proxy service has indicated exflash dimm 14 in compute book 3 has deasserted the 10% write warrenty sensor. May also be shown as 8107010d2b83000e or 0x8107010d2b83000e seve...

  • Page 1288

    8107010d-2b830011 sensor [sensorelementname] has deasserted the transition to non-critical state. Explanation: the exflash ipmi proxy service has indicated exflash dimm 17 in compute book 3 has deasserted the 10% write warrenty sensor. May also be shown as 8107010d2b830011 or 0x8107010d2b830011 seve...

  • Page 1289

    8107010d-2b830014 sensor [sensorelementname] has deasserted the transition to non-critical state. Explanation: the exflash ipmi proxy service has indicated exflash dimm 20 in compute book 3 has deasserted the 10% write warrenty sensor. May also be shown as 8107010d2b830014 or 0x8107010d2b830014 seve...

  • Page 1290

    8107010d-2b830017 sensor [sensorelementname] has deasserted the transition to non-critical state. Explanation: the exflash ipmi proxy service has indicated exflash dimm 23 in compute book 3 has deasserted the 10% write warrenty sensor. May also be shown as 8107010d2b830017 or 0x8107010d2b830017 seve...

  • Page 1291

    8107010d-2b840001 sensor [sensorelementname] has deasserted the transition to non-critical state. Explanation: the exflash ipmi proxy service has indicated exflash dimm 1 in compute book 4 has deasserted the 10% write warrenty sensor. May also be shown as 8107010d2b840001 or 0x8107010d2b840001 sever...

  • Page 1292

    8107010d-2b840004 sensor [sensorelementname] has deasserted the transition to non-critical state. Explanation: the exflash ipmi proxy service has indicated exflash dimm 4 in compute book 4 has deasserted the 10% write warrenty sensor. May also be shown as 8107010d2b840004 or 0x8107010d2b840004 sever...

  • Page 1293

    8107010d-2b840007 sensor [sensorelementname] has deasserted the transition to non-critical state. Explanation: the exflash ipmi proxy service has indicated exflash dimm 7 in compute book 4 has deasserted the 10% write warrenty sensor. May also be shown as 8107010d2b840007 or 0x8107010d2b840007 sever...

  • Page 1294

    8107010d-2b84000a sensor [sensorelementname] has deasserted the transition to non-critical state. Explanation: the exflash ipmi proxy service has indicated exflash dimm 10 in compute book 4 has deasserted the 10% write warrenty sensor. May also be shown as 8107010d2b84000a or 0x8107010d2b84000a seve...

  • Page 1295

    8107010d-2b84000d sensor [sensorelementname] has deasserted the transition to non-critical state. Explanation: the exflash ipmi proxy service has indicated exflash dimm 13 in compute book 4 has deasserted the 10% write warrenty sensor. May also be shown as 8107010d2b84000d or 0x8107010d2b84000d seve...

  • Page 1296

    8107010d-2b840010 sensor [sensorelementname] has deasserted the transition to non-critical state. Explanation: the exflash ipmi proxy service has indicated exflash dimm 16 in compute book 4 has deasserted the 10% write warrenty sensor. May also be shown as 8107010d2b840010 or 0x8107010d2b840010 seve...

  • Page 1297

    8107010d-2b840013 sensor [sensorelementname] has deasserted the transition to non-critical state. Explanation: the exflash ipmi proxy service has indicated exflash dimm 19 in compute book 4 has deasserted the 10% write warrenty sensor. May also be shown as 8107010d2b840013 or 0x8107010d2b840013 seve...

  • Page 1298

    8107010d-2b840016 sensor [sensorelementname] has deasserted the transition to non-critical state. Explanation: the exflash ipmi proxy service has indicated exflash dimm 22 in compute book 4 has deasserted the 10% write warrenty sensor. May also be shown as 8107010d2b840016 or 0x8107010d2b840016 seve...

  • Page 1299

    8107010d-2b84ffff sensor [sensorelementname] has deasserted the transition to non-critical state. Explanation: the imm has detected that the sensor deasserted. May also be shown as 8107010d2b84ffff or 0x8107010d2b84ffff severity: warning alert category: warning - other serviceable: yes cim informati...

  • Page 1300

    81070201-0301ffff sensor [sensorelementname] has transitioned to a less severe state from critical. Explanation: imm has detected the compute book 1 has cooled below the critial temperature level. May also be shown as 810702010301ffff or 0x810702010301ffff severity: info alert category: critical - t...

  • Page 1301

    81070201-0304ffff sensor [sensorelementname] has transitioned to a less severe state from critical. Explanation: imm has detected the compute book 4 has cooled below the critial temperature level. May also be shown as 810702010304ffff or 0x810702010304ffff severity: info alert category: critical - t...

  • Page 1302

    8107020c-2581ffff sensor [sensorelementname] has transitioned to a less severe state from critical. Explanation: imm has reported a smi lane failed has deasserted. May also be shown as 8107020c2581ffff or 0x8107020c2581ffff explanation: this message is for the use case when an implementation has det...

  • Page 1303

    8107020f-2582ffff sensor [sensorelementname] has transitioned to a less severe state from critical. Explanation: imm has reported that the "no i/o resources" sensor has transitioned to a less severe state. May also be shown as 8107020f2582ffff or 0x8107020f2582ffff severity: info alert category: cri...

  • Page 1304

    8107021b-0302ffff sensor [sensorelementname] has transitioned to a less severe state from critical. Explanation: imm has detected that microprocessor 2 has recovered from a qpi link error. May also be shown as 8107021b0302ffff or 0x8107021b0302ffff severity: info alert category: critical - other ser...

  • Page 1305

    81070221-0b0affff sensor [sensorelementname] has transitioned to a less severe state from critical. Explanation: imm has detected an over temperature condition for the ml2 adapter has been removed. May also be shown as 810702210b0affff or 0x810702210b0affff severity: info alert category: critical - ...

  • Page 1306

    81070221-1f03ffff sensor [sensorelementname] has transitioned to a less severe state from critical. Explanation: imm has detected that microprocessor 3 has recovered from a external qpi link error. May also be shown as 810702211f03ffff or 0x810702211f03ffff severity: info alert category: critical - ...

  • Page 1307

    81070221-2c02ffff sensor [sensorelementname] has transitioned to a less severe state from critical. Explanation: this message is for the use case when an implementation has detected a sensor transition to less severe from critical. May also be shown as 810702212c02ffff or 0x810702212c02ffff severity...

  • Page 1308

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

  • Page 1309

    8107030d-2582ffff sensor [sensorelementname] has deasserted the transition to non-recoverable from a less severe state. Explanation: this message is for the use case when an implementation has detected that the sensor transition to non-recoverable from less severe has deasserted. May also be shown a...

  • Page 1310

    81070608-1381ffff sensor [sensorelementname] has deasserted the transition to non-recoverable. Explanation: imm has detected that the sensor is no longer reporting a non-recoverable state. [ ps 12v ov fault : ps 12v uv fault : ps aux uv fault] may also be shown as 810706081381ffff or 0x810706081381f...

  • Page 1311

    810b0108-1381ffff redundancy lost for [redundancysetelementname] has deasserted. Explanation: power supply redundancy has been regained. May also be shown as 810b01081381ffff or 0x810b01081381ffff severity: info alert category: critical - redundant power supply serviceable: no cim information: prefi...

  • Page 1312

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

  • Page 1313

    810b010c-2581ffff redundancy lost for [redundancysetelementname] has deasserted. Explanation: memory component group has regained its redundancy may also be shown as 810b010c2581ffff or 0x810b010c2581ffff severity: info alert category: critical - memory serviceable: no cim information: prefix: plat ...

  • Page 1314

    810b0309-1381ffff non-redundant:sufficient resources from redundancy degraded or fully redundant for [redundancysetelementname] has deasserted. Explanation: imm has detected that power supply(s) capacity met or exceeded the minimum power requirement. May also be shown as 810b03091381ffff or 0x810b03...

  • Page 1315

    810b0509-1381ffff non-redundant:insufficient resources for [redundancysetelementname] has deasserted. Explanation: imm has detected that power supply(s) capacity is less than the minimum power requirement may also be shown as 810b05091381ffff or 0x810b05091381ffff severity: info alert category: crit...

  • Page 1316

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

  • Page 1317

    810b050c-2581ffff non-redundant:insufficient resources for [redundancysetelementname] has deasserted. Explanation: memory component group has regained its redundancy. May also be shown as 810b050c2581ffff or 0x810b050c2581ffff severity: info alert category: critical - memory serviceable: no cim info...

  • Page 1318

    816f0007-0303ffff [processorelementname] has recovered from ierr. Explanation: imm has detected that microprocessor 3 recovered from an ierr condition. May also be shown as 816f00070303ffff or 0x816f00070303ffff severity: info alert category: critical - cpu serviceable: no cim information: prefix: p...

  • Page 1319

    816f0008-0a02ffff [powersupplyelementname] has been removed from container [physicalpackageelementname]. Explanation: imm has detected that power supply 2 has been removed. May also be shown as 816f00080a02ffff or 0x816f00080a02ffff severity: info alert category: system - other serviceable: no cim i...

  • Page 1320

    816f0009-1381ffff [powersupplyelementname] has been turned on. Explanation: imm has detected that the system power has been turned on. May also be shown as 816f00091381ffff or 0x816f00091381ffff severity: info alert category: system - power on serviceable: no cim information: prefix: plat and id: 01...

  • Page 1321

    816f000d-0402ffff the [numericsensorelementname] has been removed from unit [physicalpackageelementname]. Explanation: presence of drive 2 is no longer detected. If hard drive is absent from drive bay a filler is required. May also be shown as 816f000d0402ffff or 0x816f000d0402ffff severity: error a...

  • Page 1322

    816f000d-0404ffff the [numericsensorelementname] has been removed from unit [physicalpackageelementname]. Explanation: presence of drive 4 is no longer detected. If hard drive is absent from drive bay a filler is required. May also be shown as 816f000d0404ffff or 0x816f000d0404ffff severity: error a...

  • Page 1323

    816f000d-0406ffff the [numericsensorelementname] has been removed from unit [physicalpackageelementname]. Explanation: presence of drive 6 is no longer detected. If hard drive is absent from drive bay a filler is required. May also be shown as 816f000d0406ffff or 0x816f000d0406ffff severity: error a...

  • Page 1324

    816f000d-0408ffff the [numericsensorelementname] has been removed from unit [physicalpackageelementname]. Explanation: presence of drive 8 is no longer detected. If hard drive is absent from drive bay a filler is required. May also be shown as 816f000d0408ffff or 0x816f000d0408ffff severity: error a...

  • Page 1325

    816f000d-040affff the [numericsensorelementname] has been removed from unit [physicalpackageelementname]. Explanation: presence of drive 10 is no longer detected. If hard drive is absent from drive bay a filler is required. May also be shown as 816f000d040affff or 0x816f000d040affff severity: error ...

  • Page 1326

    816f000d-040cffff the [numericsensorelementname] has been removed from unit [physicalpackageelementname]. Explanation: presence of drive 12 is no longer detected. If hard drive is absent from drive bay a filler is required. May also be shown as 816f000d040cffff or 0x816f000d040cffff severity: error ...

  • Page 1327

    816f000d-040effff the [numericsensorelementname] has been removed from unit [physicalpackageelementname]. Explanation: presence of drive 14 is no longer detected. If hard drive is absent from drive bay a filler is required. May also be shown as 816f000d040effff or 0x816f000d040effff severity: error ...

  • Page 1328

    816f000f-2201ffff the system [computersystemelementname] has detected a post error deassertion. Explanation: imm has detected that post error has deasserted. (abr status, firmware error, sys boot status). May also be shown as 816f000f2201ffff or 0x816f000f2201ffff severity: info alert category: crit...

  • Page 1329

    816f0021-0b02ffff fault condition removed on slot [physicalconnectorelementname] on system [computersystemelementname]. Explanation: imm has detected a fault condition in pcie slot 2 has been removed. May also be shown as 816f00210b02ffff or 0x816f00210b02ffff severity: info alert category: critical...

  • Page 1330

    816f0021-0b05ffff fault condition removed on slot [physicalconnectorelementname] on system [computersystemelementname]. Explanation: imm has detected a fault condition in pcie slot 5 has been removed. May also be shown as 816f00210b05ffff or 0x816f00210b05ffff severity: info alert category: critical...

  • Page 1331

    816f0021-0b08ffff fault condition removed on slot [physicalconnectorelementname] on system [computersystemelementname]. Explanation: imm has detected a fault condition in pcie slot 8 has been removed. May also be shown as 816f00210b08ffff or 0x816f00210b08ffff severity: info alert category: critical...

  • Page 1332

    816f0021-0b0bffff fault condition removed on slot [physicalconnectorelementname] on system [computersystemelementname]. Explanation: imm has detected a fault condition in pcie slot 11 has been removed. May also be shown as 816f00210b0bffff or 0x816f00210b0bffff severity: info alert category: critica...

  • Page 1333

    816f0021-0b0effff fault condition removed on slot [physicalconnectorelementname] on system [computersystemelementname]. Explanation: imm has detected a fault condition in pcie slot 17 has been removed. May also be shown as 816f00210b0effff or 0x816f00210b0effff severity: info alert category: critica...

  • Page 1334

    816f0021-2201ffff fault condition removed on slot [physicalconnectorelementname] on system [computersystemelementname]. Explanation: imm has detected rom space is now available.. May also be shown as 816f00212201ffff or 0x816f00212201ffff severity: info alert category: critical - other serviceable: ...

  • Page 1335

    816f0107-0301ffff an over-temperature condition has been removed on [processorelementname]. Explanation: the microprocessor 1 temperature has returned to below the critical level. May also be shown as 816f01070301ffff or 0x816f01070301ffff severity: info alert category: critical - temperature servic...

  • Page 1336

    816f0107-0304ffff an over-temperature condition has been removed on [processorelementname]. Explanation: the microprocessor 4 temperature has returned to below the critical level. May also be shown as 816f01070304ffff or 0x816f01070304ffff severity: info alert category: critical - temperature servic...

  • Page 1337

    816f0108-0a03ffff [powersupplyelementname] has returned to ok status. Explanation: imm has detected that power supply 3 has returned to a normal operational status. May also be shown as 816f01080a03ffff or 0x816f01080a03ffff severity: info alert category: critical - power serviceable: no cim informa...

  • Page 1338

    816f010c-2b810001 uncorrectable error recovery detected for [physicalmemoryelementname] on subsystem [memoryelementname]. Explanation: imm has reported a recovery from an uncorrectable memory error on dimm 1 in compute book 1. May also be shown as 816f010c2b810001 or 0x816f010c2b810001 severity: inf...

  • Page 1339

    816f010c-2b810004 uncorrectable error recovery detected for [physicalmemoryelementname] on subsystem [memoryelementname]. Explanation: imm has reported a recovery from an uncorrectable memory error on dimm 4 in compute book 1. May also be shown as 816f010c2b810004 or 0x816f010c2b810004 severity: inf...

  • Page 1340

    816f010c-2b810007 uncorrectable error recovery detected for [physicalmemoryelementname] on subsystem [memoryelementname]. Explanation: imm has reported a recovery from an uncorrectable memory error on dimm 7 in compute book 1. May also be shown as 816f010c2b810007 or 0x816f010c2b810007 severity: inf...

  • Page 1341

    816f010c-2b81000a uncorrectable error recovery detected for [physicalmemoryelementname] on subsystem [memoryelementname]. Explanation: imm has reported a recovery from an uncorrectable memory error on dimm 10 in compute book 1. May also be shown as 816f010c2b81000a or 0x816f010c2b81000a severity: in...

  • Page 1342

    816f010c-2b81000d uncorrectable error recovery detected for [physicalmemoryelementname] on subsystem [memoryelementname]. Explanation: imm has reported a recovery from an uncorrectable memory error on dimm 13 in compute book 1. May also be shown as 816f010c2b81000d or 0x816f010c2b81000d severity: in...

  • Page 1343

    816f010c-2b810010 uncorrectable error recovery detected for [physicalmemoryelementname] on subsystem [memoryelementname]. Explanation: imm has reported a recovery from an uncorrectable memory error on dimm 16 in compute book 1. May also be shown as 816f010c2b810010 or 0x816f010c2b810010 severity: in...

  • Page 1344

    816f010c-2b810013 uncorrectable error recovery detected for [physicalmemoryelementname] on subsystem [memoryelementname]. Explanation: imm has reported a recovery from an uncorrectable memory error on dimm 19 in compute book 1. May also be shown as 816f010c2b810013 or 0x816f010c2b810013 severity: in...

  • Page 1345

    816f010c-2b810016 uncorrectable error recovery detected for [physicalmemoryelementname] on subsystem [memoryelementname]. Explanation: imm has reported a recovery from an uncorrectable memory error on dimm 22 in compute book 1. May also be shown as 816f010c2b810016 or 0x816f010c2b810016 severity: in...

  • Page 1346

    816f010c-2b81ffff uncorrectable error recovery detected for [physicalmemoryelementname] on subsystem [memoryelementname]. Explanation: imm has reported a recovery from an uncorrectable memory error on compute book 1. May also be shown as 816f010c2b81ffff or 0x816f010c2b81ffff severity: info alert ca...

  • Page 1347

    816f010c-2b820003 uncorrectable error recovery detected for [physicalmemoryelementname] on subsystem [memoryelementname]. Explanation: imm has reported a recovery from an uncorrectable memory error on dimm 3 in compute book 2. May also be shown as 816f010c2b820003 or 0x816f010c2b820003 severity: inf...

  • Page 1348

    816f010c-2b820006 uncorrectable error recovery detected for [physicalmemoryelementname] on subsystem [memoryelementname]. Explanation: imm has reported a recovery from an uncorrectable memory error on dimm 6 in compute book 2. May also be shown as 816f010c2b820006 or 0x816f010c2b820006 severity: inf...

  • Page 1349

    816f010c-2b820009 uncorrectable error recovery detected for [physicalmemoryelementname] on subsystem [memoryelementname]. Explanation: imm has reported a recovery from an uncorrectable memory error on dimm 9 in compute book 2. May also be shown as 816f010c2b820009 or 0x816f010c2b820009 severity: inf...

  • Page 1350

    816f010c-2b82000c uncorrectable error recovery detected for [physicalmemoryelementname] on subsystem [memoryelementname]. Explanation: imm has reported a recovery from an uncorrectable memory error on dimm 12 in compute book 2. May also be shown as 816f010c2b82000c or 0x816f010c2b82000c severity: in...

  • Page 1351

    816f010c-2b82000f uncorrectable error recovery detected for [physicalmemoryelementname] on subsystem [memoryelementname]. Explanation: imm has reported a recovery from an uncorrectable memory error on dimm 15 in compute book 2. May also be shown as 816f010c2b82000f or 0x816f010c2b82000f severity: in...

  • Page 1352

    816f010c-2b820012 uncorrectable error recovery detected for [physicalmemoryelementname] on subsystem [memoryelementname]. Explanation: imm has reported a recovery from an uncorrectable memory error on dimm 18 in compute book 2. May also be shown as 816f010c2b820012 or 0x816f010c2b820012 severity: in...

  • Page 1353

    816f010c-2b820015 uncorrectable error recovery detected for [physicalmemoryelementname] on subsystem [memoryelementname]. Explanation: imm has reported a recovery from an uncorrectable memory error on dimm 21 in compute book 2. May also be shown as 816f010c2b820015 or 0x816f010c2b820015 severity: in...

  • Page 1354

    816f010c-2b820018 uncorrectable error recovery detected for [physicalmemoryelementname] on subsystem [memoryelementname]. Explanation: imm has reported a recovery from an uncorrectable memory error on dimm 24 in compute book 2. May also be shown as 816f010c2b820018 or 0x816f010c2b820018 severity: in...

  • Page 1355

    816f010c-2b830002 uncorrectable error recovery detected for [physicalmemoryelementname] on subsystem [memoryelementname]. Explanation: imm has reported a recovery from an uncorrectable memory error on dimm 2 in compute book 3. May also be shown as 816f010c2b830002 or 0x816f010c2b830002 severity: inf...

  • Page 1356

    816f010c-2b830005 uncorrectable error recovery detected for [physicalmemoryelementname] on subsystem [memoryelementname]. Explanation: imm has reported a recovery from an uncorrectable memory error on dimm 5 in compute book 3. May also be shown as 816f010c2b830005 or 0x816f010c2b830005 severity: inf...

  • Page 1357

    816f010c-2b830008 uncorrectable error recovery detected for [physicalmemoryelementname] on subsystem [memoryelementname]. Explanation: imm has reported a recovery from an uncorrectable memory error on dimm 8 in compute book 3. May also be shown as 816f010c2b830008 or 0x816f010c2b830008 severity: inf...

  • Page 1358

    816f010c-2b83000b uncorrectable error recovery detected for [physicalmemoryelementname] on subsystem [memoryelementname]. Explanation: imm has reported a recovery from an uncorrectable memory error on dimm 11 in compute book 3. May also be shown as 816f010c2b83000b or 0x816f010c2b83000b severity: in...

  • Page 1359

    816f010c-2b83000e uncorrectable error recovery detected for [physicalmemoryelementname] on subsystem [memoryelementname]. Explanation: imm has reported a recovery from an uncorrectable memory error on dimm 14 in compute book 3. May also be shown as 816f010c2b83000e or 0x816f010c2b83000e severity: in...

  • Page 1360

    816f010c-2b830011 uncorrectable error recovery detected for [physicalmemoryelementname] on subsystem [memoryelementname]. Explanation: imm has reported a recovery from an uncorrectable memory error on dimm 17 in compute book 3. May also be shown as 816f010c2b830011 or 0x816f010c2b830011 severity: in...

  • Page 1361

    816f010c-2b830014 uncorrectable error recovery detected for [physicalmemoryelementname] on subsystem [memoryelementname]. Explanation: imm has reported a recovery from an uncorrectable memory error on dimm 20 in compute book 3. May also be shown as 816f010c2b830014 or 0x816f010c2b830014 severity: in...

  • Page 1362

    816f010c-2b830017 uncorrectable error recovery detected for [physicalmemoryelementname] on subsystem [memoryelementname]. Explanation: imm has reported a recovery from an uncorrectable memory error on dimm 23 in compute book 3. May also be shown as 816f010c2b830017 or 0x816f010c2b830017 severity: in...

  • Page 1363

    816f010c-2b840001 uncorrectable error recovery detected for [physicalmemoryelementname] on subsystem [memoryelementname]. Explanation: imm has reported a recovery from an uncorrectable memory error on dimm 1 in compute book 4. May also be shown as 816f010c2b840001 or 0x816f010c2b840001 severity: inf...

  • Page 1364

    816f010c-2b840004 uncorrectable error recovery detected for [physicalmemoryelementname] on subsystem [memoryelementname]. Explanation: imm has reported a recovery from an uncorrectable memory error on dimm 4 in compute book 4. May also be shown as 816f010c2b840004 or 0x816f010c2b840004 severity: inf...

  • Page 1365

    816f010c-2b840007 uncorrectable error recovery detected for [physicalmemoryelementname] on subsystem [memoryelementname]. Explanation: imm has reported a recovery from an uncorrectable memory error on dimm 7 in compute book 4. May also be shown as 816f010c2b840007 or 0x816f010c2b840007 severity: inf...

  • Page 1366

    816f010c-2b84000a uncorrectable error recovery detected for [physicalmemoryelementname] on subsystem [memoryelementname]. Explanation: imm has reported a recovery from an uncorrectable memory error on dimm 10 in compute book 4. May also be shown as 816f010c2b84000a or 0x816f010c2b84000a severity: in...

  • Page 1367

    816f010c-2b84000d uncorrectable error recovery detected for [physicalmemoryelementname] on subsystem [memoryelementname]. Explanation: imm has reported a recovery from an uncorrectable memory error on dimm 13 in compute book 4. May also be shown as 816f010c2b84000d or 0x816f010c2b84000d severity: in...

  • Page 1368

    816f010c-2b840010 uncorrectable error recovery detected for [physicalmemoryelementname] on subsystem [memoryelementname]. Explanation: imm has reported a recovery from an uncorrectable memory error on dimm 16 in compute book 4. May also be shown as 816f010c2b840010 or 0x816f010c2b840010 severity: in...

  • Page 1369

    816f010c-2b840013 uncorrectable error recovery detected for [physicalmemoryelementname] on subsystem [memoryelementname]. Explanation: imm has reported a recovery from an uncorrectable memory error on dimm 19 in compute book 4. May also be shown as 816f010c2b840013 or 0x816f010c2b840013 severity: in...

  • Page 1370

    816f010c-2b840016 uncorrectable error recovery detected for [physicalmemoryelementname] on subsystem [memoryelementname]. Explanation: imm has reported a recovery from an uncorrectable memory error on dimm 22 in compute book 4. May also be shown as 816f010c2b840016 or 0x816f010c2b840016 severity: in...

  • Page 1371

    816f010c-2b84ffff uncorrectable error recovery detected for [physicalmemoryelementname] on subsystem [memoryelementname]. Explanation: imm has reported a recovery from an uncorrectable memory error on compute book 4. May also be shown as 816f010c2b84ffff or 0x816f010c2b84ffff severity: info alert ca...

  • Page 1372

    816f010d-0402ffff the [numericsensorelementname] 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 - hard disk drive serviceable: no cim information: prefix: plat and id...

  • Page 1373

    816f010d-0405ffff the [numericsensorelementname] 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 - hard disk drive serviceable: no cim information: prefix: plat and id...

  • Page 1374

    816f010d-0408ffff the [numericsensorelementname] 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 - hard disk drive serviceable: no cim information: prefix: plat and id...

  • Page 1375

    816f010d-040bffff the [numericsensorelementname] 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 - hard disk drive serviceable: no cim information: prefix: plat and i...

  • Page 1376

    816f010d-040effff the [numericsensorelementname] 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 - hard disk drive serviceable: no cim information: prefix: plat and i...

  • Page 1377

    816f010d-2b810002 the [numericsensorelementname] has been enabled. Explanation: the exflash proxy service deasserted a previous reported fault on the exflash dimm 2 in compute book 1. May also be shown as 816f010d2b810002 or 0x816f010d2b810002 severity: info alert category: critical - hard disk driv...

  • Page 1378

    816f010d-2b810005 the [numericsensorelementname] has been enabled. Explanation: the exflash proxy service deasserted a previous reported fault on the exflash dimm 5 in compute book 1. May also be shown as 816f010d2b810005 or 0x816f010d2b810005 severity: info alert category: critical - hard disk driv...

  • Page 1379

    816f010d-2b810008 the [numericsensorelementname] has been enabled. Explanation: the exflash proxy service deasserted a previous reported fault on the exflash dimm 8 in compute book 1. May also be shown as 816f010d2b810008 or 0x816f010d2b810008 severity: info alert category: critical - hard disk driv...

  • Page 1380

    816f010d-2b81000b the [numericsensorelementname] has been enabled. Explanation: the exflash proxy service deasserted a previous reported fault on the exflash dimm 11 in compute book 1. May also be shown as 816f010d2b81000b or 0x816f010d2b81000b severity: info alert category: critical - hard disk dri...

  • Page 1381

    816f010d-2b81000e the [numericsensorelementname] has been enabled. Explanation: the exflash proxy service deasserted a previous reported fault on the exflash dimm 14 in compute book 1. May also be shown as 816f010d2b81000e or 0x816f010d2b81000e severity: info alert category: critical - hard disk dri...

  • Page 1382

    816f010d-2b810011 the [numericsensorelementname] has been enabled. Explanation: the exflash proxy service deasserted a previous reported fault on the exflash dimm 17 in compute book 1. May also be shown as 816f010d2b810011 or 0x816f010d2b810011 severity: info alert category: critical - hard disk dri...

  • Page 1383

    816f010d-2b810014 the [numericsensorelementname] has been enabled. Explanation: the exflash proxy service deasserted a previous reported fault on the exflash dimm 20 in compute book 1. May also be shown as 816f010d2b810014 or 0x816f010d2b810014 severity: info alert category: critical - hard disk dri...

  • Page 1384

    816f010d-2b810017 the [numericsensorelementname] has been enabled. Explanation: the exflash proxy service deasserted a previous reported fault on the exflash dimm 23 in compute book 1. May also be shown as 816f010d2b810017 or 0x816f010d2b810017 severity: info alert category: critical - hard disk dri...

  • Page 1385

    816f010d-2b820002 the [numericsensorelementname] has been enabled. Explanation: the exflash proxy service deasserted a previous reported fault on the exflash dimm 2 in compute book 2. May also be shown as 816f010d2b820002 or 0x816f010d2b820002 severity: info alert category: critical - hard disk driv...

  • Page 1386

    816f010d-2b820005 the [numericsensorelementname] has been enabled. Explanation: the exflash proxy service deasserted a previous reported fault on the exflash dimm 5 in compute book 2. May also be shown as 816f010d2b820005 or 0x816f010d2b820005 severity: info alert category: critical - hard disk driv...

  • Page 1387

    816f010d-2b820008 the [numericsensorelementname] has been enabled. Explanation: the exflash proxy service deasserted a previous reported fault on the exflash dimm 8 in compute book 2. May also be shown as 816f010d2b820008 or 0x816f010d2b820008 severity: info alert category: critical - hard disk driv...

  • Page 1388

    816f010d-2b82000b the [numericsensorelementname] has been enabled. Explanation: the exflash proxy service deasserted a previous reported fault on the exflash dimm 11 in compute book 2. May also be shown as 816f010d2b82000b or 0x816f010d2b82000b severity: info alert category: critical - hard disk dri...

  • Page 1389

    816f010d-2b82000e the [numericsensorelementname] has been enabled. Explanation: the exflash proxy service deasserted a previous reported fault on the exflash dimm 14 in compute book 2. May also be shown as 816f010d2b82000e or 0x816f010d2b82000e severity: info alert category: critical - hard disk dri...

  • Page 1390

    816f010d-2b820011 the [numericsensorelementname] has been enabled. Explanation: the exflash proxy service deasserted a previous reported fault on the exflash dimm 17 in compute book 2. May also be shown as 816f010d2b820011 or 0x816f010d2b820011 severity: info alert category: critical - hard disk dri...

  • Page 1391

    816f010d-2b820014 the [numericsensorelementname] has been enabled. Explanation: the exflash proxy service deasserted a previous reported fault on the exflash dimm 20 in compute book 2. May also be shown as 816f010d2b820014 or 0x816f010d2b820014 severity: info alert category: critical - hard disk dri...

  • Page 1392

    816f010d-2b820017 the [numericsensorelementname] has been enabled. Explanation: the exflash proxy service deasserted a previous reported fault on the exflash dimm 23 in compute book 2. May also be shown as 816f010d2b820017 or 0x816f010d2b820017 severity: info alert category: critical - hard disk dri...

  • Page 1393

    816f010d-2b830002 the [numericsensorelementname] has been enabled. Explanation: the exflash proxy service deasserted a previous reported fault on the exflash dimm 2 in compute book 3. May also be shown as 816f010d2b830002 or 0x816f010d2b830002 severity: info alert category: critical - hard disk driv...

  • Page 1394

    816f010d-2b830005 the [numericsensorelementname] has been enabled. Explanation: the exflash proxy service deasserted a previous reported fault on the exflash dimm 5 in compute book 3. May also be shown as 816f010d2b830005 or 0x816f010d2b830005 severity: info alert category: critical - hard disk driv...

  • Page 1395

    816f010d-2b830008 the [numericsensorelementname] has been enabled. Explanation: the exflash proxy service deasserted a previous reported fault on the exflash dimm 8 in compute book 3. May also be shown as 816f010d2b830008 or 0x816f010d2b830008 severity: info alert category: critical - hard disk driv...

  • Page 1396

    816f010d-2b83000b the [numericsensorelementname] has been enabled. Explanation: the exflash proxy service deasserted a previous reported fault on the exflash dimm 11 in compute book 3. May also be shown as 816f010d2b83000b or 0x816f010d2b83000b severity: info alert category: critical - hard disk dri...

  • Page 1397

    816f010d-2b83000e the [numericsensorelementname] has been enabled. Explanation: the exflash proxy service deasserted a previous reported fault on the exflash dimm 14 in compute book 3. May also be shown as 816f010d2b83000e or 0x816f010d2b83000e severity: info alert category: critical - hard disk dri...

  • Page 1398

    816f010d-2b830011 the [numericsensorelementname] has been enabled. Explanation: the exflash proxy service deasserted a previous reported fault on the exflash dimm 17 in compute book 3. May also be shown as 816f010d2b830011 or 0x816f010d2b830011 severity: info alert category: critical - hard disk dri...

  • Page 1399

    816f010d-2b830014 the [numericsensorelementname] has been enabled. Explanation: the exflash proxy service deasserted a previous reported fault on the exflash dimm 20 in compute book 3. May also be shown as 816f010d2b830014 or 0x816f010d2b830014 severity: info alert category: critical - hard disk dri...

  • Page 1400

    816f010d-2b830017 the [numericsensorelementname] has been enabled. Explanation: the exflash proxy service deasserted a previous reported fault on the exflash dimm 23 in compute book 3. May also be shown as 816f010d2b830017 or 0x816f010d2b830017 severity: info alert category: critical - hard disk dri...

  • Page 1401

    816f010d-2b840002 the [numericsensorelementname] has been enabled. Explanation: the exflash proxy service deasserted a previous reported fault on the exflash dimm 2 in compute book 4. May also be shown as 816f010d2b840002 or 0x816f010d2b840002 severity: info alert category: critical - hard disk driv...

  • Page 1402

    816f010d-2b840005 the [numericsensorelementname] has been enabled. Explanation: the exflash proxy service deasserted a previous reported fault on the exflash dimm 5 in compute book 4. May also be shown as 816f010d2b840005 or 0x816f010d2b840005 severity: info alert category: critical - hard disk driv...

  • Page 1403

    816f010d-2b840008 the [numericsensorelementname] has been enabled. Explanation: the exflash proxy service deasserted a previous reported fault on the exflash dimm 8 in compute book 4. May also be shown as 816f010d2b840008 or 0x816f010d2b840008 severity: info alert category: critical - hard disk driv...

  • Page 1404

    816f010d-2b84000b the [numericsensorelementname] has been enabled. Explanation: the exflash proxy service deasserted a previous reported fault on the exflash dimm 11 in compute book 4. May also be shown as 816f010d2b84000b or 0x816f010d2b84000b severity: info alert category: critical - hard disk dri...

  • Page 1405

    816f010d-2b84000e the [numericsensorelementname] has been enabled. Explanation: the exflash proxy service deasserted a previous reported fault on the exflash dimm 14 in compute book 4. May also be shown as 816f010d2b84000e or 0x816f010d2b84000e severity: info alert category: critical - hard disk dri...

  • Page 1406

    816f010d-2b840011 the [numericsensorelementname] has been enabled. Explanation: the exflash proxy service deasserted a previous reported fault on the exflash dimm 17 in compute book 4. May also be shown as 816f010d2b840011 or 0x816f010d2b840011 severity: info alert category: critical - hard disk dri...

  • Page 1407

    816f010d-2b840014 the [numericsensorelementname] has been enabled. Explanation: the exflash proxy service deasserted a previous reported fault on the exflash dimm 20 in compute book 4. May also be shown as 816f010d2b840014 or 0x816f010d2b840014 severity: info alert category: critical - hard disk dri...

  • Page 1408

    816f010d-2b840017 the [numericsensorelementname] has been enabled. Explanation: the exflash proxy service deasserted a previous reported fault on the exflash dimm 23 in compute book 4. May also be shown as 816f010d2b840017 or 0x816f010d2b840017 severity: info alert category: critical - hard disk dri...

  • Page 1409

    816f0113-1701ffff bus [sensorelementname] has recovered from a bus timeout. Explanation: the imm has detected that a system has recovered from a nmi state bus timeout. May also be shown as 816f01131701ffff or 0x816f01131701ffff severity: info alert category: critical - other serviceable: no cim info...

  • Page 1410

    816f0125-2c05ffff [managedelementname] detected as present. Explanation: the imm has detected the storage book is now present. May also be shown as 816f01252c05ffff or 0x816f01252c05ffff severity: info alert category: system - other serviceable: no cim information: prefix: plat and id: 0390 snmp tra...

  • Page 1411

    816f0207-0303ffff [processorelementname] has recovered from frb1/bist condition. Explanation: imm has reported that microprocessor 3 has recovered from a frb1/bist condition. May also be shown as 816f02070303ffff or 0x816f02070303ffff severity: info alert category: critical - cpu serviceable: no cim...

  • Page 1412

    816f020d-0400ffff failure no longer predicted on [numericsensorelementname] for array [computersystemelementname]. Explanation: the predicted failure for drive 0 no longer exists. May also be shown as 816f020d0400ffff or 0x816f020d0400ffff severity: info alert category: system - predicted failure se...

  • Page 1413

    816f020d-0403ffff failure no longer predicted on [numericsensorelementname] for array [computersystemelementname]. Explanation: the predicted failure for drive 3 no longer exists. May also be shown as 816f020d0403ffff or 0x816f020d0403ffff severity: info alert category: system - predicted failure se...

  • Page 1414

    816f020d-0406ffff failure no longer predicted on [numericsensorelementname] for array [computersystemelementname]. Explanation: the predicted failure for drive 6 no longer exists. May also be shown as 816f020d0406ffff or 0x816f020d0406ffff severity: info alert category: system - predicted failure se...

  • Page 1415

    816f020d-0409ffff failure no longer predicted on [numericsensorelementname] for array [computersystemelementname]. Explanation: the predicted failure for drive 9 no longer exists. May also be shown as 816f020d0409ffff or 0x816f020d0409ffff severity: info alert category: system - predicted failure se...

  • Page 1416

    816f020d-040cffff failure no longer predicted on [numericsensorelementname] for array [computersystemelementname]. Explanation: the predicted failure for drive 12 no longer exists. May also be shown as 816f020d040cffff or 0x816f020d040cffff severity: info alert category: system - predicted failure s...

  • Page 1417

    816f020d-040fffff failure no longer predicted on [numericsensorelementname] for array [computersystemelementname]. Explanation: the predicted failure for drive 15 no longer exists. May also be shown as 816f020d040fffff or 0x816f020d040fffff severity: info alert category: system - predicted failure s...

  • Page 1418

    816f020d-2b810803 failure no longer predicted on [numericsensorelementname] for array [computersystemelementname]. Explanation: the exflash proxy service deasserted a previous reported predicted failure for exflash dimm 3 in compute book 1. May also be shown as 816f020d2b810803 or 0x816f020d2b810803...

  • Page 1419

    816f020d-2b810806 failure no longer predicted on [numericsensorelementname] for array [computersystemelementname]. Explanation: the exflash proxy service deasserted a previous reported predicted failure for exflash dimm 6 in compute book 1. May also be shown as 816f020d2b810806 or 0x816f020d2b810806...

  • Page 1420

    816f020d-2b810809 failure no longer predicted on [numericsensorelementname] for array [computersystemelementname]. Explanation: the exflash proxy service deasserted a previous reported predicted failure for exflash dimm 9 in compute book 1. May also be shown as 816f020d2b810809 or 0x816f020d2b810809...

  • Page 1421

    816f020d-2b81080c failure no longer predicted on [numericsensorelementname] for array [computersystemelementname]. Explanation: the exflash proxy service deasserted a previous reported predicted failure for exflash dimm 12 in compute book 1. May also be shown as 816f020d2b81080c or 0x816f020d2b81080...

  • Page 1422

    816f020d-2b81080f failure no longer predicted on [numericsensorelementname] for array [computersystemelementname]. Explanation: the exflash proxy service deasserted a previous reported predicted failure for exflash dimm 15 in compute book 1. May also be shown as 816f020d2b81080f or 0x816f020d2b81080...

  • Page 1423

    816f020d-2b810812 failure no longer predicted on [numericsensorelementname] for array [computersystemelementname]. Explanation: the exflash proxy service deasserted a previous reported predicted failure for exflash dimm 18 in compute book 1. May also be shown as 816f020d2b810812 or 0x816f020d2b81081...

  • Page 1424

    816f020d-2b810815 failure no longer predicted on [numericsensorelementname] for array [computersystemelementname]. Explanation: the exflash proxy service deasserted a previous reported predicted failure for exflash dimm 21 in compute book 1. May also be shown as 816f020d2b810815 or 0x816f020d2b81081...

  • Page 1425

    816f020d-2b810818 failure no longer predicted on [numericsensorelementname] for array [computersystemelementname]. Explanation: the exflash proxy service deasserted a previous reported predicted failure for exflash dimm 24 in compute book 1. May also be shown as 816f020d2b810818 or 0x816f020d2b81081...

  • Page 1426

    816f020d-2b820803 failure no longer predicted on [numericsensorelementname] for array [computersystemelementname]. Explanation: the exflash proxy service deasserted a previous reported predicted failure for exflash dimm 3 in compute book 2. May also be shown as 816f020d2b820803 or 0x816f020d2b820803...

  • Page 1427

    816f020d-2b820806 failure no longer predicted on [numericsensorelementname] for array [computersystemelementname]. Explanation: the exflash proxy service deasserted a previous reported predicted failure for exflash dimm 6 in compute book 2. May also be shown as 816f020d2b820806 or 0x816f020d2b820806...

  • Page 1428

    816f020d-2b820809 failure no longer predicted on [numericsensorelementname] for array [computersystemelementname]. Explanation: the exflash proxy service deasserted a previous reported predicted failure for exflash dimm 9 in compute book 2. May also be shown as 816f020d2b820809 or 0x816f020d2b820809...

  • Page 1429

    816f020d-2b82080c failure no longer predicted on [numericsensorelementname] for array [computersystemelementname]. Explanation: the exflash proxy service deasserted a previous reported predicted failure for exflash dimm 12 in compute book 2. May also be shown as 816f020d2b82080c or 0x816f020d2b82080...

  • Page 1430

    816f020d-2b82080f failure no longer predicted on [numericsensorelementname] for array [computersystemelementname]. Explanation: the exflash proxy service deasserted a previous reported predicted failure for exflash dimm 15 in compute book 2. May also be shown as 816f020d2b82080f or 0x816f020d2b82080...

  • Page 1431

    816f020d-2b820812 failure no longer predicted on [numericsensorelementname] for array [computersystemelementname]. Explanation: the exflash proxy service deasserted a previous reported predicted failure for exflash dimm 18 in compute book 2. May also be shown as 816f020d2b820812 or 0x816f020d2b82081...

  • Page 1432

    816f020d-2b820815 failure no longer predicted on [numericsensorelementname] for array [computersystemelementname]. Explanation: the exflash proxy service deasserted a previous reported predicted failure for exflash dimm 21 in compute book 2. May also be shown as 816f020d2b820815 or 0x816f020d2b82081...

  • Page 1433

    816f020d-2b820818 failure no longer predicted on [numericsensorelementname] for array [computersystemelementname]. Explanation: the exflash proxy service deasserted a previous reported predicted failure for exflash dimm 24 in compute book 2. May also be shown as 816f020d2b820818 or 0x816f020d2b82081...

  • Page 1434

    816f020d-2b830803 failure no longer predicted on [numericsensorelementname] for array [computersystemelementname]. Explanation: the exflash proxy service deasserted a previous reported predicted failure for exflash dimm 3 in compute book 3. May also be shown as 816f020d2b830803 or 0x816f020d2b830803...

  • Page 1435

    816f020d-2b830806 failure no longer predicted on [numericsensorelementname] for array [computersystemelementname]. Explanation: the exflash proxy service deasserted a previous reported predicted failure for exflash dimm 6 in compute book 3. May also be shown as 816f020d2b830806 or 0x816f020d2b830806...

  • Page 1436

    816f020d-2b830809 failure no longer predicted on [numericsensorelementname] for array [computersystemelementname]. Explanation: the exflash proxy service deasserted a previous reported predicted failure for exflash dimm 9 in compute book 3. May also be shown as 816f020d2b830809 or 0x816f020d2b830809...

  • Page 1437

    816f020d-2b83080c failure no longer predicted on [numericsensorelementname] for array [computersystemelementname]. Explanation: the exflash proxy service deasserted a previous reported predicted failure for exflash dimm 12 in compute book 3. May also be shown as 816f020d2b83080c or 0x816f020d2b83080...

  • Page 1438

    816f020d-2b83080f failure no longer predicted on [numericsensorelementname] for array [computersystemelementname]. Explanation: the exflash proxy service deasserted a previous reported predicted failure for exflash dimm 15 in compute book 3. May also be shown as 816f020d2b83080f or 0x816f020d2b83080...

  • Page 1439

    816f020d-2b830812 failure no longer predicted on [numericsensorelementname] for array [computersystemelementname]. Explanation: the exflash proxy service deasserted a previous reported predicted failure for exflash dimm 18 in compute book 3. May also be shown as 816f020d2b830812 or 0x816f020d2b83081...

  • Page 1440

    816f020d-2b830815 failure no longer predicted on [numericsensorelementname] for array [computersystemelementname]. Explanation: the exflash proxy service deasserted a previous reported predicted failure for exflash dimm 21 in compute book 3. May also be shown as 816f020d2b830815 or 0x816f020d2b83081...

  • Page 1441

    816f020d-2b830818 failure no longer predicted on [numericsensorelementname] for array [computersystemelementname]. Explanation: the exflash proxy service deasserted a previous reported predicted failure for exflash dimm 24 in compute book 3. May also be shown as 816f020d2b830818 or 0x816f020d2b83081...

  • Page 1442

    816f020d-2b840803 failure no longer predicted on [numericsensorelementname] for array [computersystemelementname]. Explanation: the exflash proxy service deasserted a previous reported predicted failure for exflash dimm 3 in compute book 4. May also be shown as 816f020d2b840803 or 0x816f020d2b840803...

  • Page 1443

    816f020d-2b840806 failure no longer predicted on [numericsensorelementname] for array [computersystemelementname]. Explanation: the exflash proxy service deasserted a previous reported predicted failure for exflash dimm 6 in compute book 4. May also be shown as 816f020d2b840806 or 0x816f020d2b840806...

  • Page 1444

    816f020d-2b840809 failure no longer predicted on [numericsensorelementname] for array [computersystemelementname]. Explanation: the exflash proxy service deasserted a previous reported predicted failure for exflash dimm 9 in compute book 4. May also be shown as 816f020d2b840809 or 0x816f020d2b840809...

  • Page 1445

    816f020d-2b84080c failure no longer predicted on [numericsensorelementname] for array [computersystemelementname]. Explanation: the exflash proxy service deasserted a previous reported predicted failure for exflash dimm 12 in compute book 4. May also be shown as 816f020d2b84080c or 0x816f020d2b84080...

  • Page 1446

    816f020d-2b84080f failure no longer predicted on [numericsensorelementname] for array [computersystemelementname]. Explanation: the exflash proxy service deasserted a previous reported predicted failure for exflash dimm 15 in compute book 4. May also be shown as 816f020d2b84080f or 0x816f020d2b84080...

  • Page 1447

    816f020d-2b840812 failure no longer predicted on [numericsensorelementname] for array [computersystemelementname]. Explanation: the exflash proxy service deasserted a previous reported predicted failure for exflash dimm 18 in compute book 4. May also be shown as 816f020d2b840812 or 0x816f020d2b84081...

  • Page 1448

    816f020d-2b840815 failure no longer predicted on [numericsensorelementname] for array [computersystemelementname]. Explanation: the exflash proxy service deasserted a previous reported predicted failure for exflash dimm 21 in compute book 4. May also be shown as 816f020d2b840815 or 0x816f020d2b84081...

  • Page 1449

    816f020d-2b840818 failure no longer predicted on [numericsensorelementname] for array [computersystemelementname]. Explanation: the exflash proxy service deasserted a previous reported predicted failure for exflash dimm 24 in compute book 4. May also be shown as 816f020d2b840818 or 0x816f020d2b84081...

  • Page 1450

    816f0308-0a03ffff [powersupplyelementname] has returned to a normal input state. Explanation: imm has detected that the input power for power supply 3 has been restored. May also be shown as 816f03080a03ffff or 0x816f03080a03ffff severity: info alert category: system - other serviceable: no cim info...

  • Page 1451

    816f030c-2b810002 scrub failure for [physicalmemoryelementname] on subsystem [memoryelementname] has recovered. Explanation: a memory post failure detected during boot on dimm 2 in compute book 1 has recovered. May also be shown as 816f030c2b810002 or 0x816f030c2b810002 severity: info alert category...

  • Page 1452

    816f030c-2b810005 scrub failure for [physicalmemoryelementname] on subsystem [memoryelementname] has recovered. Explanation: a memory post failure detected during boot on dimm 5 in compute book 1 has recovered. May also be shown as 816f030c2b810005 or 0x816f030c2b810005 severity: info alert category...

  • Page 1453

    816f030c-2b810008 scrub failure for [physicalmemoryelementname] on subsystem [memoryelementname] has recovered. Explanation: a memory post failure detected during boot on dimm 8 in compute book 1 has recovered. May also be shown as 816f030c2b810008 or 0x816f030c2b810008 severity: info alert category...

  • Page 1454

    816f030c-2b81000b scrub failure for [physicalmemoryelementname] on subsystem [memoryelementname] has recovered. Explanation: a memory post failure detected during boot on dimm 11 in compute book 1 has recovered. May also be shown as 816f030c2b81000b or 0x816f030c2b81000b severity: info alert categor...

  • Page 1455

    816f030c-2b81000e scrub failure for [physicalmemoryelementname] on subsystem [memoryelementname] has recovered. Explanation: a memory post failure detected during boot on dimm 14 in compute book 1 has recovered. May also be shown as 816f030c2b81000e or 0x816f030c2b81000e severity: info alert categor...

  • Page 1456

    816f030c-2b810011 scrub failure for [physicalmemoryelementname] on subsystem [memoryelementname] has recovered. Explanation: a memory post failure detected during boot on dimm 17 in compute book 1 has recovered. May also be shown as 816f030c2b810011 or 0x816f030c2b810011 severity: info alert categor...

  • Page 1457

    816f030c-2b810014 scrub failure for [physicalmemoryelementname] on subsystem [memoryelementname] has recovered. Explanation: a memory post failure detected during boot on dimm 20 in compute book 1 has recovered. May also be shown as 816f030c2b810014 or 0x816f030c2b810014 severity: info alert categor...

  • Page 1458

    816f030c-2b810017 scrub failure for [physicalmemoryelementname] on subsystem [memoryelementname] has recovered. Explanation: a memory post failure detected during boot on dimm 23 in compute book 1 has recovered. May also be shown as 816f030c2b810017 or 0x816f030c2b810017 severity: info alert categor...

  • Page 1459

    816f030c-2b820001 scrub failure for [physicalmemoryelementname] on subsystem [memoryelementname] has recovered. Explanation: a memory post failure detected during boot on dimm 1 in compute book 2 has recovered. May also be shown as 816f030c2b820001 or 0x816f030c2b820001 severity: info alert category...

  • Page 1460

    816f030c-2b820004 scrub failure for [physicalmemoryelementname] on subsystem [memoryelementname] has recovered. Explanation: a memory post failure detected during boot on dimm 4 in compute book 2 has recovered. May also be shown as 816f030c2b820004 or 0x816f030c2b820004 severity: info alert category...

  • Page 1461

    816f030c-2b820007 scrub failure for [physicalmemoryelementname] on subsystem [memoryelementname] has recovered. Explanation: a memory post failure detected during boot on dimm 7 in compute book 2 has recovered. May also be shown as 816f030c2b820007 or 0x816f030c2b820007 severity: info alert category...

  • Page 1462

    816f030c-2b82000a scrub failure for [physicalmemoryelementname] on subsystem [memoryelementname] has recovered. Explanation: a memory post failure detected during boot on dimm 10 in compute book 2 has recovered. May also be shown as 816f030c2b82000a or 0x816f030c2b82000a severity: info alert categor...

  • Page 1463

    816f030c-2b82000d scrub failure for [physicalmemoryelementname] on subsystem [memoryelementname] has recovered. Explanation: a memory post failure detected during boot on dimm 13 in compute book 2 has recovered. May also be shown as 816f030c2b82000d or 0x816f030c2b82000d severity: info alert categor...

  • Page 1464

    816f030c-2b820010 scrub failure for [physicalmemoryelementname] on subsystem [memoryelementname] has recovered. Explanation: a memory post failure detected during boot on dimm 16 in compute book 2 has recovered. May also be shown as 816f030c2b820010 or 0x816f030c2b820010 severity: info alert categor...

  • Page 1465

    816f030c-2b820013 scrub failure for [physicalmemoryelementname] on subsystem [memoryelementname] has recovered. Explanation: a memory post failure detected during boot on dimm 19 in compute book 2 has recovered. May also be shown as 816f030c2b820013 or 0x816f030c2b820013 severity: info alert categor...

  • Page 1466

    816f030c-2b820016 scrub failure for [physicalmemoryelementname] on subsystem [memoryelementname] has recovered. Explanation: a memory post failure detected during boot on dimm 22 in compute book 2 has recovered. May also be shown as 816f030c2b820016 or 0x816f030c2b820016 severity: info alert categor...

  • Page 1467

    816f030c-2b82ffff scrub failure for [physicalmemoryelementname] on subsystem [memoryelementname] has recovered. Explanation: a memory post failure detected during boot on compute book 2 has recovered. May also be shown as 816f030c2b82ffff or 0x816f030c2b82ffff severity: info alert category: critical...

  • Page 1468

    816f030c-2b830003 scrub failure for [physicalmemoryelementname] on subsystem [memoryelementname] has recovered. Explanation: a memory post failure detected during boot on dimm 3 in compute book 3 has recovered. May also be shown as 816f030c2b830003 or 0x816f030c2b830003 severity: info alert category...

  • Page 1469

    816f030c-2b830006 scrub failure for [physicalmemoryelementname] on subsystem [memoryelementname] has recovered. Explanation: a memory post failure detected during boot on dimm 6 in compute book 3 has recovered. May also be shown as 816f030c2b830006 or 0x816f030c2b830006 severity: info alert category...

  • Page 1470

    816f030c-2b830009 scrub failure for [physicalmemoryelementname] on subsystem [memoryelementname] has recovered. Explanation: a memory post failure detected during boot on dimm 9 in compute book 3 has recovered. May also be shown as 816f030c2b830009 or 0x816f030c2b830009 severity: info alert category...

  • Page 1471

    816f030c-2b83000c scrub failure for [physicalmemoryelementname] on subsystem [memoryelementname] has recovered. Explanation: a memory post failure detected during boot on dimm 12 in compute book 3 has recovered. May also be shown as 816f030c2b83000c or 0x816f030c2b83000c severity: info alert categor...

  • Page 1472

    816f030c-2b83000f scrub failure for [physicalmemoryelementname] on subsystem [memoryelementname] has recovered. Explanation: a memory post failure detected during boot on dimm 15 in compute book 3 has recovered. May also be shown as 816f030c2b83000f or 0x816f030c2b83000f severity: info alert categor...

  • Page 1473

    816f030c-2b830012 scrub failure for [physicalmemoryelementname] on subsystem [memoryelementname] has recovered. Explanation: a memory post failure detected during boot on dimm 18 in compute book 3 has recovered. May also be shown as 816f030c2b830012 or 0x816f030c2b830012 severity: info alert categor...

  • Page 1474

    816f030c-2b830015 scrub failure for [physicalmemoryelementname] on subsystem [memoryelementname] has recovered. Explanation: a memory post failure detected during boot on dimm 21 in compute book 3 has recovered. May also be shown as 816f030c2b830015 or 0x816f030c2b830015 severity: info alert categor...

  • Page 1475

    816f030c-2b830018 scrub failure for [physicalmemoryelementname] on subsystem [memoryelementname] has recovered. Explanation: a memory post failure detected during boot on dimm 24 in compute book 3 has recovered. May also be shown as 816f030c2b830018 or 0x816f030c2b830018 severity: info alert categor...

  • Page 1476

    816f030c-2b840002 scrub failure for [physicalmemoryelementname] on subsystem [memoryelementname] has recovered. Explanation: a memory post failure detected during boot on dimm 2 in compute book 4 has recovered. May also be shown as 816f030c2b840002 or 0x816f030c2b840002 severity: info alert category...

  • Page 1477

    816f030c-2b840005 scrub failure for [physicalmemoryelementname] on subsystem [memoryelementname] has recovered. Explanation: a memory post failure detected during boot on dimm 5 in compute book 4 has recovered. May also be shown as 816f030c2b840005 or 0x816f030c2b840005 severity: info alert category...

  • Page 1478

    816f030c-2b840008 scrub failure for [physicalmemoryelementname] on subsystem [memoryelementname] has recovered. Explanation: a memory post failure detected during boot on dimm 8 in compute book 4 has recovered. May also be shown as 816f030c2b840008 or 0x816f030c2b840008 severity: info alert category...

  • Page 1479

    816f030c-2b84000b scrub failure for [physicalmemoryelementname] on subsystem [memoryelementname] has recovered. Explanation: a memory post failure detected during boot on dimm 11 in compute book 4 has recovered. May also be shown as 816f030c2b84000b or 0x816f030c2b84000b severity: info alert categor...

  • Page 1480

    816f030c-2b84000e scrub failure for [physicalmemoryelementname] on subsystem [memoryelementname] has recovered. Explanation: a memory post failure detected during boot on dimm 14 in compute book 4 has recovered. May also be shown as 816f030c2b84000e or 0x816f030c2b84000e severity: info alert categor...

  • Page 1481

    816f030c-2b840011 scrub failure for [physicalmemoryelementname] on subsystem [memoryelementname] has recovered. Explanation: a memory post failure detected during boot on dimm 17 in compute book 4 has recovered. May also be shown as 816f030c2b840011 or 0x816f030c2b840011 severity: info alert categor...

  • Page 1482

    816f030c-2b840014 scrub failure for [physicalmemoryelementname] on subsystem [memoryelementname] has recovered. Explanation: a memory post failure detected during boot on dimm 20 in compute book 4 has recovered. May also be shown as 816f030c2b840014 or 0x816f030c2b840014 severity: info alert categor...

  • Page 1483

    816f030c-2b840017 scrub failure for [physicalmemoryelementname] on subsystem [memoryelementname] has recovered. Explanation: a memory post failure detected during boot on dimm 23 in compute book 4 has recovered. May also be shown as 816f030c2b840017 or 0x816f030c2b840017 severity: info alert categor...

  • Page 1484

    816f030d-0400ffff hot spare disabled for [computersystemelementname]. Explanation: this message is for the use case when an implementation has detected a hot spare has been disabled. May also be shown as 816f030d0400ffff or 0x816f030d0400ffff severity: info alert category: system - other serviceable...

  • Page 1485

    816f030d-0403ffff hot spare disabled for [computersystemelementname]. Explanation: this message is for the use case when an implementation has detected a hot spare has been disabled. May also be shown as 816f030d0403ffff or 0x816f030d0403ffff severity: info alert category: system - other serviceable...

  • Page 1486

    816f030d-0406ffff hot spare disabled for [computersystemelementname]. Explanation: this message is for the use case when an implementation has detected a hot spare has been disabled. May also be shown as 816f030d0406ffff or 0x816f030d0406ffff severity: info alert category: system - other serviceable...

  • Page 1487

    816f030d-0409ffff hot spare disabled for [computersystemelementname]. Explanation: this message is for the use case when an implementation has detected a hot spare has been disabled. May also be shown as 816f030d0409ffff or 0x816f030d0409ffff severity: info alert category: system - other serviceable...

  • Page 1488

    816f030d-040cffff hot spare disabled for [computersystemelementname]. Explanation: this message is for the use case when an implementation has detected a hot spare has been disabled. May also be shown as 816f030d040cffff or 0x816f030d040cffff severity: info alert category: system - other serviceable...

  • Page 1489

    816f030d-040fffff hot spare disabled for [computersystemelementname]. Explanation: this message is for the use case when an implementation has detected a hot spare has been disabled. May also be shown as 816f030d040fffff or 0x816f030d040fffff severity: info alert category: system - other serviceable...

  • Page 1490

    816f040c-2b810001 [physicalmemoryelementname] enabled on subsystem [memoryelementname]. Explanation: imm has reported that memory on dimm 1 in compute book 1 has been enabled. May also be shown as 816f040c2b810001 or 0x816f040c2b810001 severity: info alert category: system - other serviceable: no ci...

  • Page 1491

    816f040c-2b810004 [physicalmemoryelementname] enabled on subsystem [memoryelementname]. Explanation: imm has reported that memory on dimm 4 in compute book 1 has been enabled. May also be shown as 816f040c2b810004 or 0x816f040c2b810004 severity: info alert category: system - other serviceable: no ci...

  • Page 1492

    816f040c-2b810007 [physicalmemoryelementname] enabled on subsystem [memoryelementname]. Explanation: imm has reported that memory on dimm 7 in compute book 1 has been enabled. May also be shown as 816f040c2b810007 or 0x816f040c2b810007 severity: info alert category: system - other serviceable: no ci...

  • Page 1493

    816f040c-2b81000a [physicalmemoryelementname] enabled on subsystem [memoryelementname]. Explanation: imm has reported that memory on dimm 10 in compute book 1 has been enabled. May also be shown as 816f040c2b81000a or 0x816f040c2b81000a severity: info alert category: system - other serviceable: no c...

  • Page 1494

    816f040c-2b81000d [physicalmemoryelementname] enabled on subsystem [memoryelementname]. Explanation: imm has reported that memory on dimm 13 in compute book 1 has been enabled. May also be shown as 816f040c2b81000d or 0x816f040c2b81000d severity: info alert category: system - other serviceable: no c...

  • Page 1495

    816f040c-2b810010 [physicalmemoryelementname] enabled on subsystem [memoryelementname]. Explanation: imm has reported that memory on dimm 16 in compute book 1 has been enabled. May also be shown as 816f040c2b810010 or 0x816f040c2b810010 severity: info alert category: system - other serviceable: no c...

  • Page 1496

    816f040c-2b810013 [physicalmemoryelementname] enabled on subsystem [memoryelementname]. Explanation: imm has reported that memory on dimm 19 in compute book 1 has been enabled. May also be shown as 816f040c2b810013 or 0x816f040c2b810013 severity: info alert category: system - other serviceable: no c...

  • Page 1497

    816f040c-2b810016 [physicalmemoryelementname] enabled on subsystem [memoryelementname]. Explanation: imm has reported that memory on dimm 22 in compute book 1 has been enabled. May also be shown as 816f040c2b810016 or 0x816f040c2b810016 severity: info alert category: system - other serviceable: no c...

  • Page 1498

    816f040c-2b81ffff [physicalmemoryelementname] enabled on subsystem [memoryelementname]. Explanation: imm has reported that memory on compute book 1 has been enabled. May also be shown as 816f040c2b81ffff or 0x816f040c2b81ffff severity: info alert category: system - other serviceable: no cim informat...

  • Page 1499

    816f040c-2b820003 [physicalmemoryelementname] enabled on subsystem [memoryelementname]. Explanation: imm has reported that memory on dimm 3 in compute book 2 has been enabled. May also be shown as 816f040c2b820003 or 0x816f040c2b820003 severity: info alert category: system - other serviceable: no ci...

  • Page 1500

    816f040c-2b820006 [physicalmemoryelementname] enabled on subsystem [memoryelementname]. Explanation: imm has reported that memory on dimm 6 in compute book 2 has been enabled. May also be shown as 816f040c2b820006 or 0x816f040c2b820006 severity: info alert category: system - other serviceable: no ci...

  • Page 1501

    816f040c-2b820009 [physicalmemoryelementname] enabled on subsystem [memoryelementname]. Explanation: imm has reported that memory on dimm 9 in compute book 2 has been enabled. May also be shown as 816f040c2b820009 or 0x816f040c2b820009 severity: info alert category: system - other serviceable: no ci...

  • Page 1502

    816f040c-2b82000c [physicalmemoryelementname] enabled on subsystem [memoryelementname]. Explanation: imm has reported that memory on dimm 12 in compute book 2 has been enabled. May also be shown as 816f040c2b82000c or 0x816f040c2b82000c severity: info alert category: system - other serviceable: no c...

  • Page 1503

    816f040c-2b82000f [physicalmemoryelementname] enabled on subsystem [memoryelementname]. Explanation: imm has reported that memory on dimm 15 in compute book 2 has been enabled. May also be shown as 816f040c2b82000f or 0x816f040c2b82000f severity: info alert category: system - other serviceable: no c...

  • Page 1504

    816f040c-2b820012 [physicalmemoryelementname] enabled on subsystem [memoryelementname]. Explanation: imm has reported that memory on dimm 18 in compute book 2 has been enabled. May also be shown as 816f040c2b820012 or 0x816f040c2b820012 severity: info alert category: system - other serviceable: no c...

  • Page 1505

    816f040c-2b820015 [physicalmemoryelementname] enabled on subsystem [memoryelementname]. Explanation: imm has reported that memory on dimm 21 in compute book 2 has been enabled. May also be shown as 816f040c2b820015 or 0x816f040c2b820015 severity: info alert category: system - other serviceable: no c...

  • Page 1506

    816f040c-2b820018 [physicalmemoryelementname] enabled on subsystem [memoryelementname]. Explanation: imm has reported that memory on dimm 24 in compute book 2 has been enabled. May also be shown as 816f040c2b820018 or 0x816f040c2b820018 severity: info alert category: system - other serviceable: no c...

  • Page 1507

    816f040c-2b830002 [physicalmemoryelementname] enabled on subsystem [memoryelementname]. Explanation: imm has reported that memory on dimm 2 in compute book 3 has been enabled. May also be shown as 816f040c2b830002 or 0x816f040c2b830002 severity: info alert category: system - other serviceable: no ci...

  • Page 1508

    816f040c-2b830005 [physicalmemoryelementname] enabled on subsystem [memoryelementname]. Explanation: imm has reported that memory on dimm 5 in compute book 3 has been enabled. May also be shown as 816f040c2b830005 or 0x816f040c2b830005 severity: info alert category: system - other serviceable: no ci...

  • Page 1509

    816f040c-2b830008 [physicalmemoryelementname] enabled on subsystem [memoryelementname]. Explanation: imm has reported that memory on dimm 8 in compute book 3 has been enabled. May also be shown as 816f040c2b830008 or 0x816f040c2b830008 severity: info alert category: system - other serviceable: no ci...

  • Page 1510

    816f040c-2b83000b [physicalmemoryelementname] enabled on subsystem [memoryelementname]. Explanation: imm has reported that memory on dimm 11 in compute book 3 has been enabled. May also be shown as 816f040c2b83000b or 0x816f040c2b83000b severity: info alert category: system - other serviceable: no c...

  • Page 1511

    816f040c-2b83000e [physicalmemoryelementname] enabled on subsystem [memoryelementname]. Explanation: imm has reported that memory on dimm 14 in compute book 3 has been enabled. May also be shown as 816f040c2b83000e or 0x816f040c2b83000e severity: info alert category: system - other serviceable: no c...

  • Page 1512

    816f040c-2b830011 [physicalmemoryelementname] enabled on subsystem [memoryelementname]. Explanation: imm has reported that memory on dimm 17 in compute book 3 has been enabled. May also be shown as 816f040c2b830011 or 0x816f040c2b830011 severity: info alert category: system - other serviceable: no c...

  • Page 1513

    816f040c-2b830014 [physicalmemoryelementname] enabled on subsystem [memoryelementname]. Explanation: imm has reported that memory on dimm 20 in compute book 3 has been enabled. May also be shown as 816f040c2b830014 or 0x816f040c2b830014 severity: info alert category: system - other serviceable: no c...

  • Page 1514

    816f040c-2b830017 [physicalmemoryelementname] enabled on subsystem [memoryelementname]. Explanation: imm has reported that memory on dimm 23 in compute book 3 has been enabled. May also be shown as 816f040c2b830017 or 0x816f040c2b830017 severity: info alert category: system - other serviceable: no c...

  • Page 1515

    816f040c-2b840001 [physicalmemoryelementname] enabled on subsystem [memoryelementname]. Explanation: imm has reported that memory on dimm 1 in compute book 4 has been enabled. May also be shown as 816f040c2b840001 or 0x816f040c2b840001 severity: info alert category: system - other serviceable: no ci...

  • Page 1516

    816f040c-2b840004 [physicalmemoryelementname] enabled on subsystem [memoryelementname]. Explanation: imm has reported that memory on dimm 4 in compute book 4 has been enabled. May also be shown as 816f040c2b840004 or 0x816f040c2b840004 severity: info alert category: system - other serviceable: no ci...

  • Page 1517

    816f040c-2b840007 [physicalmemoryelementname] enabled on subsystem [memoryelementname]. Explanation: imm has reported that memory on dimm 7 in compute book 4 has been enabled. May also be shown as 816f040c2b840007 or 0x816f040c2b840007 severity: info alert category: system - other serviceable: no ci...

  • Page 1518

    816f040c-2b84000a [physicalmemoryelementname] enabled on subsystem [memoryelementname]. Explanation: imm has reported that memory on dimm 10 in compute book 4 has been enabled. May also be shown as 816f040c2b84000a or 0x816f040c2b84000a severity: info alert category: system - other serviceable: no c...

  • Page 1519

    816f040c-2b84000d [physicalmemoryelementname] enabled on subsystem [memoryelementname]. Explanation: imm has reported that memory on dimm 13 in compute book 4 has been enabled. May also be shown as 816f040c2b84000d or 0x816f040c2b84000d severity: info alert category: system - other serviceable: no c...

  • Page 1520

    816f040c-2b840010 [physicalmemoryelementname] enabled on subsystem [memoryelementname]. Explanation: imm has reported that memory on dimm 16 in compute book 4 has been enabled. May also be shown as 816f040c2b840010 or 0x816f040c2b840010 severity: info alert category: system - other serviceable: no c...

  • Page 1521

    816f040c-2b840013 [physicalmemoryelementname] enabled on subsystem [memoryelementname]. Explanation: imm has reported that memory on dimm 19 in compute book 4 has been enabled. May also be shown as 816f040c2b840013 or 0x816f040c2b840013 severity: info alert category: system - other serviceable: no c...

  • Page 1522

    816f040c-2b840016 [physicalmemoryelementname] enabled on subsystem [memoryelementname]. Explanation: imm has reported that memory on dimm 22 in compute book 4 has been enabled. May also be shown as 816f040c2b840016 or 0x816f040c2b840016 severity: info alert category: system - other serviceable: no c...

  • Page 1523

    816f040c-2b84ffff [physicalmemoryelementname] enabled on subsystem [memoryelementname]. Explanation: imm has reported that memory on compute book 4 has been enabled. May also be shown as 816f040c2b84ffff or 0x816f040c2b84ffff severity: info alert category: system - other serviceable: no cim informat...

  • Page 1524

    816f0507-0303ffff [processorelementname] has recovered from a configuration mismatch. Explanation: microprocessor 3 has recovered from a microprocessor configuration mismatch. May also be shown as 816f05070303ffff or 0x816f05070303ffff severity: info alert category: critical - cpu serviceable: no ci...

  • Page 1525

    816f050c-2581ffff memory logging limit removed for [physicalmemoryelementname] on subsystem [memoryelementname]. Explanation: imm has reported that the memory logging limit has been removed. May also be shown as 816f050c2581ffff or 0x816f050c2581ffff severity: info alert category: warning - memory s...

  • Page 1526

    816f050c-2b810003 memory logging limit removed for [physicalmemoryelementname] on subsystem [memoryelementname]. Explanation: imm has reported that the memory on dimm 3 in compute book 1 logging limit has been removed. May also be shown as 816f050c2b810003 or 0x816f050c2b810003 severity: info alert ...

  • Page 1527

    816f050c-2b810006 memory logging limit removed for [physicalmemoryelementname] on subsystem [memoryelementname]. Explanation: imm has reported that the memory on dimm 6 in compute book 1 logging limit has been removed. May also be shown as 816f050c2b810006 or 0x816f050c2b810006 severity: info alert ...

  • Page 1528

    816f050c-2b810009 memory logging limit removed for [physicalmemoryelementname] on subsystem [memoryelementname]. Explanation: imm has reported that the memory on dimm 9 in compute book 1 logging limit has been removed. May also be shown as 816f050c2b810009 or 0x816f050c2b810009 severity: info alert ...

  • Page 1529

    816f050c-2b81000c memory logging limit removed for [physicalmemoryelementname] on subsystem [memoryelementname]. Explanation: imm has reported that the memory on dimm 12 in compute book 1 logging limit has been removed. May also be shown as 816f050c2b81000c or 0x816f050c2b81000c severity: info alert...

  • Page 1530

    816f050c-2b81000f memory logging limit removed for [physicalmemoryelementname] on subsystem [memoryelementname]. Explanation: imm has reported that the memory on dimm 15 in compute book 1 logging limit has been removed. May also be shown as 816f050c2b81000f or 0x816f050c2b81000f severity: info alert...

  • Page 1531

    816f050c-2b810012 memory logging limit removed for [physicalmemoryelementname] on subsystem [memoryelementname]. Explanation: imm has reported that the memory on dimm 18 in compute book 1 logging limit has been removed. May also be shown as 816f050c2b810012 or 0x816f050c2b810012 severity: info alert...

  • Page 1532

    816f050c-2b810015 memory logging limit removed for [physicalmemoryelementname] on subsystem [memoryelementname]. Explanation: imm has reported that the memory on dimm 21 in compute book 1 logging limit has been removed. May also be shown as 816f050c2b810015 or 0x816f050c2b810015 severity: info alert...

  • Page 1533

    816f050c-2b810018 memory logging limit removed for [physicalmemoryelementname] on subsystem [memoryelementname]. Explanation: imm has reported that the memory on dimm 24 in compute book 1 logging limit has been removed. May also be shown as 816f050c2b810018 or 0x816f050c2b810018 severity: info alert...

  • Page 1534

    816f050c-2b820002 memory logging limit removed for [physicalmemoryelementname] on subsystem [memoryelementname]. Explanation: imm has reported that the memory on dimm 2 in compute book 2 logging limit has been removed. May also be shown as 816f050c2b820002 or 0x816f050c2b820002 severity: info alert ...

  • Page 1535

    816f050c-2b820005 memory logging limit removed for [physicalmemoryelementname] on subsystem [memoryelementname]. Explanation: imm has reported that the memory on dimm 5 in compute book 2 logging limit has been removed. May also be shown as 816f050c2b820005 or 0x816f050c2b820005 severity: info alert ...

  • Page 1536

    816f050c-2b820008 memory logging limit removed for [physicalmemoryelementname] on subsystem [memoryelementname]. Explanation: imm has reported that the memory on dimm 8 in compute book 2 logging limit has been removed. May also be shown as 816f050c2b820008 or 0x816f050c2b820008 severity: info alert ...

  • Page 1537

    816f050c-2b82000b memory logging limit removed for [physicalmemoryelementname] on subsystem [memoryelementname]. Explanation: imm has reported that the memory on dimm 11 in compute book 2 logging limit has been removed. May also be shown as 816f050c2b82000b or 0x816f050c2b82000b severity: info alert...

  • Page 1538

    816f050c-2b82000e memory logging limit removed for [physicalmemoryelementname] on subsystem [memoryelementname]. Explanation: imm has reported that the memory on dimm 14 in compute book 2 logging limit has been removed. May also be shown as 816f050c2b82000e or 0x816f050c2b82000e severity: info alert...

  • Page 1539

    816f050c-2b820011 memory logging limit removed for [physicalmemoryelementname] on subsystem [memoryelementname]. Explanation: imm has reported that the memory on dimm 17 in compute book 2 logging limit has been removed. May also be shown as 816f050c2b820011 or 0x816f050c2b820011 severity: info alert...

  • Page 1540

    816f050c-2b820014 memory logging limit removed for [physicalmemoryelementname] on subsystem [memoryelementname]. Explanation: imm has reported that the memory on dimm 20 in compute book 2 logging limit has been removed. May also be shown as 816f050c2b820014 or 0x816f050c2b820014 severity: info alert...

  • Page 1541

    816f050c-2b820017 memory logging limit removed for [physicalmemoryelementname] on subsystem [memoryelementname]. Explanation: imm has reported that the memory on dimm 23 in compute book 2 logging limit has been removed. May also be shown as 816f050c2b820017 or 0x816f050c2b820017 severity: info alert...

  • Page 1542

    816f050c-2b830001 memory logging limit removed for [physicalmemoryelementname] on subsystem [memoryelementname]. Explanation: imm has reported that the memory on dimm 1 in compute book 3 logging limit has been removed. May also be shown as 816f050c2b830001 or 0x816f050c2b830001 severity: info alert ...

  • Page 1543

    816f050c-2b830004 memory logging limit removed for [physicalmemoryelementname] on subsystem [memoryelementname]. Explanation: imm has reported that the memory on dimm 4 in compute book 3 logging limit has been removed. May also be shown as 816f050c2b830004 or 0x816f050c2b830004 severity: info alert ...

  • Page 1544

    816f050c-2b830007 memory logging limit removed for [physicalmemoryelementname] on subsystem [memoryelementname]. Explanation: imm has reported that the memory on dimm 7 in compute book 3 logging limit has been removed. May also be shown as 816f050c2b830007 or 0x816f050c2b830007 severity: info alert ...

  • Page 1545

    816f050c-2b83000a memory logging limit removed for [physicalmemoryelementname] on subsystem [memoryelementname]. Explanation: imm has reported that the memory on dimm 10 in compute book 3 logging limit has been removed. May also be shown as 816f050c2b83000a or 0x816f050c2b83000a severity: info alert...

  • Page 1546

    816f050c-2b83000d memory logging limit removed for [physicalmemoryelementname] on subsystem [memoryelementname]. Explanation: imm has reported that the memory on dimm 13 in compute book 3 logging limit has been removed. May also be shown as 816f050c2b83000d or 0x816f050c2b83000d severity: info alert...

  • Page 1547

    816f050c-2b830010 memory logging limit removed for [physicalmemoryelementname] on subsystem [memoryelementname]. Explanation: imm has reported that the memory on dimm 16 in compute book 3 logging limit has been removed. May also be shown as 816f050c2b830010 or 0x816f050c2b830010 severity: info alert...

  • Page 1548

    816f050c-2b830013 memory logging limit removed for [physicalmemoryelementname] on subsystem [memoryelementname]. Explanation: imm has reported that the memory on dimm 19 in compute book 3 logging limit has been removed. May also be shown as 816f050c2b830013 or 0x816f050c2b830013 severity: info alert...

  • Page 1549

    816f050c-2b830016 memory logging limit removed for [physicalmemoryelementname] on subsystem [memoryelementname]. Explanation: imm has reported that the memory on dimm 22 in compute book 3 logging limit has been removed. May also be shown as 816f050c2b830016 or 0x816f050c2b830016 severity: info alert...

  • Page 1550

    816f050c-2b83ffff memory logging limit removed for [physicalmemoryelementname] on subsystem [memoryelementname]. Explanation: imm has reported that the memory on compute book 3 logging limit has been removed. May also be shown as 816f050c2b83ffff or 0x816f050c2b83ffff severity: info alert category: ...

  • Page 1551

    816f050c-2b840003 memory logging limit removed for [physicalmemoryelementname] on subsystem [memoryelementname]. Explanation: imm has reported that the memory on dimm 3 in compute book 4 logging limit has been removed. May also be shown as 816f050c2b840003 or 0x816f050c2b840003 severity: info alert ...

  • Page 1552

    816f050c-2b840006 memory logging limit removed for [physicalmemoryelementname] on subsystem [memoryelementname]. Explanation: imm has reported that the memory on dimm 6 in compute book 4 logging limit has been removed. May also be shown as 816f050c2b840006 or 0x816f050c2b840006 severity: info alert ...

  • Page 1553

    816f050c-2b840009 memory logging limit removed for [physicalmemoryelementname] on subsystem [memoryelementname]. Explanation: imm has reported that the memory on dimm 9 in compute book 4 logging limit has been removed. May also be shown as 816f050c2b840009 or 0x816f050c2b840009 severity: info alert ...

  • Page 1554

    816f050c-2b84000c memory logging limit removed for [physicalmemoryelementname] on subsystem [memoryelementname]. Explanation: imm has reported that the memory on dimm 12 in compute book 4 logging limit has been removed. May also be shown as 816f050c2b84000c or 0x816f050c2b84000c severity: info alert...

  • Page 1555

    816f050c-2b84000f memory logging limit removed for [physicalmemoryelementname] on subsystem [memoryelementname]. Explanation: imm has reported that the memory on dimm 15 in compute book 4 logging limit has been removed. May also be shown as 816f050c2b84000f or 0x816f050c2b84000f severity: info alert...

  • Page 1556

    816f050c-2b840012 memory logging limit removed for [physicalmemoryelementname] on subsystem [memoryelementname]. Explanation: imm has reported that the memory on dimm 18 in compute book 4 logging limit has been removed. May also be shown as 816f050c2b840012 or 0x816f050c2b840012 severity: info alert...

  • Page 1557

    816f050c-2b840015 memory logging limit removed for [physicalmemoryelementname] on subsystem [memoryelementname]. Explanation: imm has reported that the memory on dimm 21 in compute book 4 logging limit has been removed. May also be shown as 816f050c2b840015 or 0x816f050c2b840015 severity: info alert...

  • Page 1558

    816f050c-2b840018 memory logging limit removed for [physicalmemoryelementname] on subsystem [memoryelementname]. Explanation: imm has reported that the memory on dimm 24 in compute book 4 logging limit has been removed. May also be shown as 816f050c2b840018 or 0x816f050c2b840018 severity: info alert...

  • Page 1559

    816f050d-0401ffff critical array [computersystemelementname] has deasserted. Explanation: the raid array drive 1 is no longer in a critical condition. May also be shown as 816f050d0401ffff or 0x816f050d0401ffff severity: info alert category: critical - hard disk drive serviceable: no cim information...

  • Page 1560

    816f050d-0404ffff critical array [computersystemelementname] has deasserted. Explanation: the raid array drive 4 is no longer in a critical condition. May also be shown as 816f050d0404ffff or 0x816f050d0404ffff severity: info alert category: critical - hard disk drive serviceable: no cim information...

  • Page 1561

    816f050d-0407ffff critical array [computersystemelementname] has deasserted. Explanation: the raid array drive 7 is no longer in a critical condition. May also be shown as 816f050d0407ffff or 0x816f050d0407ffff severity: info alert category: critical - hard disk drive serviceable: no cim information...

  • Page 1562

    816f050d-040affff critical array [computersystemelementname] has deasserted. Explanation: the raid array drive 10 is no longer in a critical condition. May also be shown as 816f050d040affff or 0x816f050d040affff severity: info alert category: critical - hard disk drive serviceable: no cim informatio...

  • Page 1563

    816f050d-040dffff critical array [computersystemelementname] has deasserted. Explanation: the raid array drive 13 is no longer in a critical condition. May also be shown as 816f050d040dffff or 0x816f050d040dffff severity: info alert category: critical - hard disk drive serviceable: no cim informatio...

  • Page 1564

    816f0607-0301ffff an sm bios uncorrectable cpu complex error for cpu 1 has deasserted. Explanation: an sm bios uncorrectable cpu complex error has been deasserted for microprocessor 1. May also be shown as 816f06070301ffff or 0x816f06070301ffff severity: info alert category: critical - cpu serviceab...

  • Page 1565

    816f0607-0304ffff an sm bios uncorrectable cpu complex error for [processorelementname] has deasserted. Explanation: an sm bios uncorrectable cpu complex error has been deasserted for microprocessor 4. May also be shown as 816f06070304ffff or 0x816f06070304ffff severity: info alert category: critica...

  • Page 1566

    816f060d-0400ffff array in system [computersystemelementname] has been restored. Explanation: imm has detected that a failed array (drive 0) has been restored. May also be shown as 816f060d0400ffff or 0x816f060d0400ffff severity: info alert category: critical - hard disk drive serviceable: no cim in...

  • Page 1567

    816f060d-0403ffff array in system [computersystemelementname] has been restored. Explanation: imm has detected that a failed array (drive 3) has been restored. May also be shown as 816f060d0403ffff or 0x816f060d0403ffff severity: info alert category: critical - hard disk drive serviceable: no cim in...

  • Page 1568

    816f060d-0406ffff array in system [computersystemelementname] has been restored. Explanation: imm has detected that a failed array (drive 6) has been restored. May also be shown as 816f060d0406ffff or 0x816f060d0406ffff severity: info alert category: critical - hard disk drive serviceable: no cim in...

  • Page 1569

    816f060d-0409ffff array in system [computersystemelementname] has been restored. Explanation: imm has detected that a failed array (drive 9) has been restored. May also be shown as 816f060d0409ffff or 0x816f060d0409ffff severity: info alert category: critical - hard disk drive serviceable: no cim in...

  • Page 1570

    816f060d-040cffff array in system [computersystemelementname] has been restored. Explanation: imm has detected that a failed array (drive 12) has been restored. May also be shown as 816f060d040cffff or 0x816f060d040cffff severity: info alert category: critical - hard disk drive serviceable: no cim i...

  • Page 1571

    816f060d-040fffff array in system [computersystemelementname] has been restored. Explanation: imm has detected that a failed array (drive 15)has been restored. May also be shown as 816f060d040fffff or 0x816f060d040fffff severity: info alert category: critical - hard disk drive serviceable: no cim in...

  • Page 1572

    816f070c-2b810001 configuration error for [physicalmemoryelementname] on subsystem [memoryelementname]has deasserted. Explanation: imm has reported on dimm 1 in compute book 1 a memory configuration error has recovered. May also be shown as 816f070c2b810001 or 0x816f070c2b810001 severity: info alert...

  • Page 1573

    816f070c-2b810004 configuration error for [physicalmemoryelementname] on subsystem [memoryelementname]has deasserted. Explanation: imm has reported on dimm 4 in compute book 1 a memory configuration error has recovered. May also be shown as 816f070c2b810004 or 0x816f070c2b810004 severity: info alert...

  • Page 1574

    816f070c-2b810007 configuration error for [physicalmemoryelementname] on subsystem [memoryelementname]has deasserted. Explanation: imm has reported on dimm 7 in compute book 1 a memory configuration error has recovered. May also be shown as 816f070c2b810007 or 0x816f070c2b810007 severity: info alert...

  • Page 1575

    816f070c-2b81000a configuration error for [physicalmemoryelementname] on subsystem [memoryelementname]has deasserted. Explanation: imm has reported on dimm 10 in compute book 1 a memory configuration error has recovered. May also be shown as 816f070c2b81000a or 0x816f070c2b81000a severity: info aler...

  • Page 1576

    816f070c-2b81000d configuration error for [physicalmemoryelementname] on subsystem [memoryelementname]has deasserted. Explanation: imm has reported on dimm 13 in compute book 1 a memory configuration error has recovered. May also be shown as 816f070c2b81000d or 0x816f070c2b81000d severity: info aler...

  • Page 1577

    816f070c-2b810010 configuration error for [physicalmemoryelementname] on subsystem [memoryelementname]has deasserted. Explanation: imm has reported on dimm 16 in compute book 1 a memory configuration error has recovered. May also be shown as 816f070c2b810010 or 0x816f070c2b810010 severity: info aler...

  • Page 1578

    816f070c-2b810013 configuration error for [physicalmemoryelementname] on subsystem [memoryelementname]has deasserted. Explanation: imm has reported on dimm 19 in compute book 1 a memory configuration error has recovered. May also be shown as 816f070c2b810013 or 0x816f070c2b810013 severity: info aler...

  • Page 1579

    816f070c-2b810016 configuration error for [physicalmemoryelementname] on subsystem [memoryelementname]has deasserted. Explanation: imm has reported on dimm 22 in compute book 1 a memory configuration error has recovered. May also be shown as 816f070c2b810016 or 0x816f070c2b810016 severity: info aler...

  • Page 1580

    816f070c-2b81ffff configuration error for [physicalmemoryelementname] on subsystem [memoryelementname]has deasserted. Explanation: imm has reported on compute book 1 a memory configuration error has recovered. May also be shown as 816f070c2b81ffff or 0x816f070c2b81ffff severity: info alert category:...

  • Page 1581

    816f070c-2b820003 configuration error for [physicalmemoryelementname] on subsystem [memoryelementname]has deasserted. Explanation: imm has reported on dimm 3 in compute book 2 a memory configuration error has recovered. May also be shown as 816f070c2b820003 or 0x816f070c2b820003 severity: info alert...

  • Page 1582

    816f070c-2b820006 configuration error for [physicalmemoryelementname] on subsystem [memoryelementname]has deasserted. Explanation: imm has reported on dimm 6 in compute book 2 a memory configuration error has recovered. May also be shown as 816f070c2b820006 or 0x816f070c2b820006 severity: info alert...

  • Page 1583

    816f070c-2b820009 configuration error for [physicalmemoryelementname] on subsystem [memoryelementname]has deasserted. Explanation: imm has reported on dimm 9 in compute book 2 a memory configuration error has recovered. May also be shown as 816f070c2b820009 or 0x816f070c2b820009 severity: info alert...

  • Page 1584

    816f070c-2b82000c configuration error for [physicalmemoryelementname] on subsystem [memoryelementname]has deasserted. Explanation: imm has reported on dimm 12 in compute book 2 a memory configuration error has recovered. May also be shown as 816f070c2b82000c or 0x816f070c2b82000c severity: info aler...

  • Page 1585

    816f070c-2b82000f configuration error for [physicalmemoryelementname] on subsystem [memoryelementname]has deasserted. Explanation: imm has reported on dimm 15 in compute book 2 a memory configuration error has recovered. May also be shown as 816f070c2b82000f or 0x816f070c2b82000f severity: info aler...

  • Page 1586

    816f070c-2b820012 configuration error for [physicalmemoryelementname] on subsystem [memoryelementname]has deasserted. Explanation: imm has reported on dimm 18 in compute book 2 a memory configuration error has recovered. May also be shown as 816f070c2b820012 or 0x816f070c2b820012 severity: info aler...

  • Page 1587

    816f070c-2b820015 configuration error for [physicalmemoryelementname] on subsystem [memoryelementname]has deasserted. Explanation: imm has reported on dimm 21 in compute book 2 a memory configuration error has recovered. May also be shown as 816f070c2b820015 or 0x816f070c2b820015 severity: info aler...

  • Page 1588

    816f070c-2b820018 configuration error for [physicalmemoryelementname] on subsystem [memoryelementname]has deasserted. Explanation: imm has reported on dimm 24 in compute book 2 a memory configuration error has recovered. May also be shown as 816f070c2b820018 or 0x816f070c2b820018 severity: info aler...

  • Page 1589

    816f070c-2b830002 configuration error for [physicalmemoryelementname] on subsystem [memoryelementname]has deasserted. Explanation: imm has reported on dimm 2 in compute book 3 a memory configuration error has recovered. May also be shown as 816f070c2b830002 or 0x816f070c2b830002 severity: info alert...

  • Page 1590

    816f070c-2b830005 configuration error for [physicalmemoryelementname] on subsystem [memoryelementname]has deasserted. Explanation: imm has reported on dimm 5 in compute book 3 a memory configuration error has recovered. May also be shown as 816f070c2b830005 or 0x816f070c2b830005 severity: info alert...

  • Page 1591

    816f070c-2b830008 configuration error for [physicalmemoryelementname] on subsystem [memoryelementname]has deasserted. Explanation: imm has reported on dimm 8 in compute book 3 a memory configuration error has recovered. May also be shown as 816f070c2b830008 or 0x816f070c2b830008 severity: info alert...

  • Page 1592

    816f070c-2b83000b configuration error for [physicalmemoryelementname] on subsystem [memoryelementname]has deasserted. Explanation: imm has reported on dimm 11 in compute book 3 a memory configuration error has recovered. May also be shown as 816f070c2b83000b or 0x816f070c2b83000b severity: info aler...

  • Page 1593

    816f070c-2b83000e configuration error for [physicalmemoryelementname] on subsystem [memoryelementname]has deasserted. Explanation: imm has reported on dimm 14 in compute book 3 a memory configuration error has recovered. May also be shown as 816f070c2b83000e or 0x816f070c2b83000e severity: info aler...

  • Page 1594

    816f070c-2b830011 configuration error for [physicalmemoryelementname] on subsystem [memoryelementname]has deasserted. Explanation: imm has reported on dimm 17 in compute book 3 a memory configuration error has recovered. May also be shown as 816f070c2b830011 or 0x816f070c2b830011 severity: info aler...

  • Page 1595

    816f070c-2b830014 configuration error for [physicalmemoryelementname] on subsystem [memoryelementname]has deasserted. Explanation: imm has reported on dimm 20 in compute book 3 a memory configuration error has recovered. May also be shown as 816f070c2b830014 or 0x816f070c2b830014 severity: info aler...

  • Page 1596

    816f070c-2b830017 configuration error for [physicalmemoryelementname] on subsystem [memoryelementname]has deasserted. Explanation: imm has reported on dimm 23 in compute book 3 a memory configuration error has recovered. May also be shown as 816f070c2b830017 or 0x816f070c2b830017 severity: info aler...

  • Page 1597

    816f070c-2b840001 configuration error for [physicalmemoryelementname] on subsystem [memoryelementname]has deasserted. Explanation: imm has reported on dimm 1 in compute book 4 a memory configuration error has recovered. May also be shown as 816f070c2b840001 or 0x816f070c2b840001 severity: info alert...

  • Page 1598

    816f070c-2b840004 configuration error for [physicalmemoryelementname] on subsystem [memoryelementname]has deasserted. Explanation: imm has reported on dimm 4 in compute book 4 a memory configuration error has recovered. May also be shown as 816f070c2b840004 or 0x816f070c2b840004 severity: info alert...

  • Page 1599

    816f070c-2b840007 configuration error for [physicalmemoryelementname] on subsystem [memoryelementname]has deasserted. Explanation: imm has reported on dimm 7 in compute book 4 a memory configuration error has recovered. May also be shown as 816f070c2b840007 or 0x816f070c2b840007 severity: info alert...

  • Page 1600

    816f070c-2b84000a configuration error for [physicalmemoryelementname] on subsystem [memoryelementname]has deasserted. Explanation: imm has reported on dimm 10 in compute book 4 a memory configuration error has recovered. May also be shown as 816f070c2b84000a or 0x816f070c2b84000a severity: info aler...

  • Page 1601

    816f070c-2b84000d configuration error for [physicalmemoryelementname] on subsystem [memoryelementname]has deasserted. Explanation: imm has reported on dimm 13 in compute book 4 a memory configuration error has recovered. May also be shown as 816f070c2b84000d or 0x816f070c2b84000d severity: info aler...

  • Page 1602

    816f070c-2b840010 configuration error for [physicalmemoryelementname] on subsystem [memoryelementname]has deasserted. Explanation: imm has reported on dimm 16 in compute book 4 a memory configuration error has recovered. May also be shown as 816f070c2b840010 or 0x816f070c2b840010 severity: info aler...

  • Page 1603

    816f070c-2b840013 configuration error for [physicalmemoryelementname] on subsystem [memoryelementname]has deasserted. Explanation: imm has reported on dimm 19 in compute book 4 a memory configuration error has recovered. May also be shown as 816f070c2b840013 or 0x816f070c2b840013 severity: info aler...

  • Page 1604

    816f070c-2b840016 configuration error for [physicalmemoryelementname] on subsystem [memoryelementname]has deasserted. Explanation: imm has reported on dimm 22 in compute book 4 a memory configuration error has recovered. May also be shown as 816f070c2b840016 or 0x816f070c2b840016 severity: info aler...

  • Page 1605

    816f070c-2b84ffff configuration error for [physicalmemoryelementname] on subsystem [memoryelementname]has deasserted. Explanation: imm has reported on compute book 4 a memory configuration error has recovered. May also be shown as 816f070c2b84ffff or 0x816f070c2b84ffff severity: info alert category:...

  • Page 1606

    816f070d-0402ffff rebuild completed for array in system [computersystemelementname]. Explanation: imm has detected that an array rebuild (drive 2) has completed. May also be shown as 816f070d0402ffff or 0x816f070d0402ffff severity: info alert category: system - other serviceable: no cim information:...

  • Page 1607

    816f070d-0405ffff rebuild completed for array in system [computersystemelementname]. Explanation: imm has detected that an array rebuild (drive 5) has completed. May also be shown as 816f070d0405ffff or 0x816f070d0405ffff severity: info alert category: system - other serviceable: no cim information:...

  • Page 1608

    816f070d-0408ffff rebuild completed for array in system [computersystemelementname]. Explanation: imm has detected that an array rebuild (drive 8) has completed. May also be shown as 816f070d0408ffff or 0x816f070d0408ffff severity: info alert category: system - other serviceable: no cim information:...

  • Page 1609

    816f070d-040bffff rebuild completed for array in system [computersystemelementname]. Explanation: imm has detected that an array rebuild (drive 11) has completed. May also be shown as 816f070d040bffff or 0x816f070d040bffff severity: info alert category: system - other serviceable: no cim information...

  • Page 1610

    816f070d-040effff rebuild completed for array in system [computersystemelementname]. Explanation: imm has detected that an array rebuild (drive 14) has completed. May also be shown as 816f070d040effff or 0x816f070d040effff severity: info alert category: system - other serviceable: no cim information...

  • Page 1611

    816f0807-0302ffff [processorelementname] has been enabled. Explanation: imm has reported microprocessor 2 has been enabled. May also be shown as 816f08070302ffff or 0x816f08070302ffff severity: info alert category: system - other serviceable: no cim information: prefix: plat and id: 0060 snmp trap i...

  • Page 1612

    816f0807-2583ffff [processorelementname] has been enabled. Explanation: imm has reported that one or more microprocessors have been enabled. May also be shown as 816f08072583ffff or 0x816f08072583ffff severity: info alert category: system - other serviceable: no cim information: prefix: plat and id:...

  • Page 1613

    816f0813-2583ffff bus [sensorelementname] has recovered from an uncorrectable bus error. Explanation: imm has reported that the system has recovered from a bus uncorrectable error. May also be shown as 816f08132583ffff or 0x816f08132583ffff severity: info alert category: critical - other serviceable...

  • Page 1614

    816f090c-2b810003 [physicalmemoryelementname] on subsystem [memoryelementname] is no longer throttled. Explanation: dimm throttling on dimm 3 in compute book 1 has been turned off. May also be shown as 816f090c2b810003 or 0x816f090c2b810003 severity: info alert category: system - other serviceable: ...

  • Page 1615

    816f090c-2b810006 [physicalmemoryelementname] on subsystem [memoryelementname] is no longer throttled. Explanation: dimm throttling on dimm 6 in compute book 1 has been turned off. May also be shown as 816f090c2b810006 or 0x816f090c2b810006 severity: info alert category: system - other serviceable: ...

  • Page 1616

    816f090c-2b810009 [physicalmemoryelementname] on subsystem [memoryelementname] is no longer throttled. Explanation: dimm throttling on dimm 9 in compute book 1 has been turned off. May also be shown as 816f090c2b810009 or 0x816f090c2b810009 severity: info alert category: system - other serviceable: ...

  • Page 1617

    816f090c-2b81000c [physicalmemoryelementname] on subsystem [memoryelementname] is no longer throttled. Explanation: dimm throttling on dimm 12 in compute book 1 has been turned off. May also be shown as 816f090c2b81000c or 0x816f090c2b81000c severity: info alert category: system - other serviceable:...

  • Page 1618

    816f090c-2b81000f [physicalmemoryelementname] on subsystem [memoryelementname] is no longer throttled. Explanation: dimm throttling on dimm 15 in compute book 1 has been turned off. May also be shown as 816f090c2b81000f or 0x816f090c2b81000f severity: info alert category: system - other serviceable:...

  • Page 1619

    816f090c-2b810012 [physicalmemoryelementname] on subsystem [memoryelementname] is no longer throttled. Explanation: dimm throttling on dimm 18 in compute book 1 has been turned off. May also be shown as 816f090c2b810012 or 0x816f090c2b810012 severity: info alert category: system - other serviceable:...

  • Page 1620

    816f090c-2b810015 [physicalmemoryelementname] on subsystem [memoryelementname] is no longer throttled. Explanation: dimm throttling on dimm 21 in compute book 1 has been turned off. May also be shown as 816f090c2b810015 or 0x816f090c2b810015 severity: info alert category: system - other serviceable:...

  • Page 1621

    816f090c-2b810018 [physicalmemoryelementname] on subsystem [memoryelementname] is no longer throttled. Explanation: dimm throttling on dimm 24 in compute book 1 has been turned off. May also be shown as 816f090c2b810018 or 0x816f090c2b810018 severity: info alert category: system - other serviceable:...

  • Page 1622

    816f090c-2b820002 [physicalmemoryelementname] on subsystem [memoryelementname] is no longer throttled. Explanation: dimm throttling on dimm 2 in compute book 2 has been turned off. May also be shown as 816f090c2b820002 or 0x816f090c2b820002 severity: info alert category: system - other serviceable: ...

  • Page 1623

    816f090c-2b820005 [physicalmemoryelementname] on subsystem [memoryelementname] is no longer throttled. Explanation: dimm throttling on dimm 5 in compute book 2 has been turned off. May also be shown as 816f090c2b820005 or 0x816f090c2b820005 severity: info alert category: system - other serviceable: ...

  • Page 1624

    816f090c-2b820008 [physicalmemoryelementname] on subsystem [memoryelementname] is no longer throttled. Explanation: dimm throttling on dimm 8 in compute book 2 has been turned off. May also be shown as 816f090c2b820008 or 0x816f090c2b820008 severity: info alert category: system - other serviceable: ...

  • Page 1625

    816f090c-2b82000b [physicalmemoryelementname] on subsystem [memoryelementname] is no longer throttled. Explanation: dimm throttling on dimm 11 in compute book 2 has been turned off. May also be shown as 816f090c2b82000b or 0x816f090c2b82000b severity: info alert category: system - other serviceable:...

  • Page 1626

    816f090c-2b82000e [physicalmemoryelementname] on subsystem [memoryelementname] is no longer throttled. Explanation: dimm throttling on dimm 14 in compute book 2 has been turned off. May also be shown as 816f090c2b82000e or 0x816f090c2b82000e severity: info alert category: system - other serviceable:...

  • Page 1627

    816f090c-2b820011 [physicalmemoryelementname] on subsystem [memoryelementname] is no longer throttled. Explanation: dimm throttling on dimm 17 in compute book 2 has been turned off. May also be shown as 816f090c2b820011 or 0x816f090c2b820011 severity: info alert category: system - other serviceable:...

  • Page 1628

    816f090c-2b820014 [physicalmemoryelementname] on subsystem [memoryelementname] is no longer throttled. Explanation: dimm throttling on dimm 20 in compute book 2 has been turned off. May also be shown as 816f090c2b820014 or 0x816f090c2b820014 severity: info alert category: system - other serviceable:...

  • Page 1629

    816f090c-2b820017 [physicalmemoryelementname] on subsystem [memoryelementname] is no longer throttled. Explanation: dimm throttling on dimm 23 in compute book 2 has been turned off. May also be shown as 816f090c2b820017 or 0x816f090c2b820017 severity: info alert category: system - other serviceable:...

  • Page 1630

    816f090c-2b830001 [physicalmemoryelementname] on subsystem [memoryelementname] is no longer throttled. Explanation: dimm throttling on dimm 1 in compute book 3 has been turned off. May also be shown as 816f090c2b830001 or 0x816f090c2b830001 severity: info alert category: system - other serviceable: ...

  • Page 1631

    816f090c-2b830004 [physicalmemoryelementname] on subsystem [memoryelementname] is no longer throttled. Explanation: dimm throttling on dimm 4 in compute book 3 has been turned off. May also be shown as 816f090c2b830004 or 0x816f090c2b830004 severity: info alert category: system - other serviceable: ...

  • Page 1632

    816f090c-2b830007 [physicalmemoryelementname] on subsystem [memoryelementname] is no longer throttled. Explanation: dimm throttling on dimm 7 in compute book 3 has been turned off. May also be shown as 816f090c2b830007 or 0x816f090c2b830007 severity: info alert category: system - other serviceable: ...

  • Page 1633

    816f090c-2b83000a [physicalmemoryelementname] on subsystem [memoryelementname] is no longer throttled. Explanation: dimm throttling on dimm 10 in compute book 3 has been turned off. May also be shown as 816f090c2b83000a or 0x816f090c2b83000a severity: info alert category: system - other serviceable:...

  • Page 1634

    816f090c-2b83000d [physicalmemoryelementname] on subsystem [memoryelementname] is no longer throttled. Explanation: dimm throttling on dimm 13 in compute book 3 has been turned off. May also be shown as 816f090c2b83000d or 0x816f090c2b83000d severity: info alert category: system - other serviceable:...

  • Page 1635

    816f090c-2b830010 [physicalmemoryelementname] on subsystem [memoryelementname] is no longer throttled. Explanation: dimm throttling on dimm 16 in compute book 3 has been turned off. May also be shown as 816f090c2b830010 or 0x816f090c2b830010 severity: info alert category: system - other serviceable:...

  • Page 1636

    816f090c-2b830013 [physicalmemoryelementname] on subsystem [memoryelementname] is no longer throttled. Explanation: dimm throttling on dimm 19 in compute book 3 has been turned off. May also be shown as 816f090c2b830013 or 0x816f090c2b830013 severity: info alert category: system - other serviceable:...

  • Page 1637

    816f090c-2b830016 [physicalmemoryelementname] on subsystem [memoryelementname] is no longer throttled. Explanation: dimm throttling on dimm 22 in compute book 3 has been turned off. May also be shown as 816f090c2b830016 or 0x816f090c2b830016 severity: info alert category: system - other serviceable:...

  • Page 1638

    816f090c-2b83ffff [physicalmemoryelementname] on subsystem [memoryelementname] is no longer throttled. Explanation: dimm throttling in compute book 3 has been turned off. May also be shown as 816f090c2b83ffff or 0x816f090c2b83ffff severity: info alert category: system - other serviceable: no cim inf...

  • Page 1639

    816f090c-2b840003 [physicalmemoryelementname] on subsystem [memoryelementname] is no longer throttled. Explanation: dimm throttling on dimm 3 in compute book 4 has been turned off. May also be shown as 816f090c2b840003 or 0x816f090c2b840003 severity: info alert category: system - other serviceable: ...

  • Page 1640

    816f090c-2b840006 [physicalmemoryelementname] on subsystem [memoryelementname] is no longer throttled. Explanation: dimm throttling on dimm 6 in compute book 4 has been turned off. May also be shown as 816f090c2b840006 or 0x816f090c2b840006 severity: info alert category: system - other serviceable: ...

  • Page 1641

    816f090c-2b840009 [physicalmemoryelementname] on subsystem [memoryelementname] is no longer throttled. Explanation: dimm throttling on dimm 9 in compute book 4 has been turned off. May also be shown as 816f090c2b840009 or 0x816f090c2b840009 severity: info alert category: system - other serviceable: ...

  • Page 1642

    816f090c-2b84000c [physicalmemoryelementname] on subsystem [memoryelementname] is no longer throttled. Explanation: dimm throttling on dimm 12 in compute book 4 has been turned off. May also be shown as 816f090c2b84000c or 0x816f090c2b84000c severity: info alert category: system - other serviceable:...

  • Page 1643

    816f090c-2b84000f [physicalmemoryelementname] on subsystem [memoryelementname] is no longer throttled. Explanation: dimm throttling on dimm 15 in compute book 4 has been turned off. May also be shown as 816f090c2b84000f or 0x816f090c2b84000f severity: info alert category: system - other serviceable:...

  • Page 1644

    816f090c-2b840012 [physicalmemoryelementname] on subsystem [memoryelementname] is no longer throttled. Explanation: dimm throttling on dimm 18 in compute book 4 has been turned off. May also be shown as 816f090c2b840012 or 0x816f090c2b840012 severity: info alert category: system - other serviceable:...

  • Page 1645

    816f090c-2b840015 [physicalmemoryelementname] on subsystem [memoryelementname] is no longer throttled. Explanation: dimm throttling on dimm 21 in compute book 4 has been turned off. May also be shown as 816f090c2b840015 or 0x816f090c2b840015 severity: info alert category: system - other serviceable:...

  • Page 1646

    816f090c-2b840018 [physicalmemoryelementname] on subsystem [memoryelementname] is no longer throttled. Explanation: dimm throttling on dimm 24 in compute book 4 has been turned off. May also be shown as 816f090c2b840018 or 0x816f090c2b840018 severity: info alert category: system - other serviceable:...

  • Page 1647

    816f0a07-0302ffff the processor [processorelementname] is no longer operating in a degraded state. Explanation: imm has detected microprocessor 2 is no longer running in the degraded state. May also be shown as 816f0a070302ffff or 0x816f0a070302ffff severity: info alert category: warning - cpu servi...

  • Page 1648

    816f0a0c-2b810001 an over-temperature condition has been removed on the [physicalmemoryelementname] on subsystem [memoryelementname]. Explanation: the over temperature condition for memory on dimm 1 in compute book 1 has been deasserted. May also be shown as 816f0a0c2b810001 or 0x816f0a0c2b810001 se...

  • Page 1649

    816f0a0c-2b810004 an over-temperature condition has been removed on the [physicalmemoryelementname] on subsystem [memoryelementname]. Explanation: the over temperature condition for memory on dimm 4 in compute book 1 has been deasserted. May also be shown as 816f0a0c2b810004 or 0x816f0a0c2b810004 se...

  • Page 1650

    816f0a0c-2b810007 an over-temperature condition has been removed on the [physicalmemoryelementname] on subsystem [memoryelementname]. Explanation: the over temperature condition for memory on dimm 7 in compute book 1 has been deasserted. May also be shown as 816f0a0c2b810007 or 0x816f0a0c2b810007 se...

  • Page 1651

    816f0a0c-2b81000a an over-temperature condition has been removed on the [physicalmemoryelementname] on subsystem [memoryelementname]. Explanation: the over temperature condition for memory on dimm 10 in compute book 1 has been deasserted. May also be shown as 816f0a0c2b81000a or 0x816f0a0c2b81000a s...

  • Page 1652

    816f0a0c-2b81000d an over-temperature condition has been removed on the [physicalmemoryelementname] on subsystem [memoryelementname]. Explanation: the over temperature condition for memory on dimm 13 in compute book 1 has been deasserted. May also be shown as 816f0a0c2b81000d or 0x816f0a0c2b81000d s...

  • Page 1653

    816f0a0c-2b810010 an over-temperature condition has been removed on the [physicalmemoryelementname] on subsystem [memoryelementname]. Explanation: the over temperature condition for memory on dimm 16 in compute book 1 has been deasserted. May also be shown as 816f0a0c2b810010 or 0x816f0a0c2b810010 s...

  • Page 1654

    816f0a0c-2b810013 an over-temperature condition has been removed on the [physicalmemoryelementname] on subsystem [memoryelementname]. Explanation: the over temperature condition for memory on dimm 19 in compute book 1 has been deasserted. May also be shown as 816f0a0c2b810013 or 0x816f0a0c2b810013 s...

  • Page 1655

    816f0a0c-2b810016 an over-temperature condition has been removed on the [physicalmemoryelementname] on subsystem [memoryelementname]. Explanation: the over temperature condition for memory on dimm 22 in compute book 1 has been deasserted. May also be shown as 816f0a0c2b810016 or 0x816f0a0c2b810016 s...

  • Page 1656

    816f0a0c-2b81ffff an over-temperature condition has been removed on the [physicalmemoryelementname] on subsystem [memoryelementname]. Explanation: the over temperature condition for memory on compute book 1 has been deasserted. May also be shown as 816f0a0c2b81ffff or 0x816f0a0c2b81ffff severity: in...

  • Page 1657

    816f0a0c-2b820003 an over-temperature condition has been removed on the [physicalmemoryelementname] on subsystem [memoryelementname]. Explanation: the over temperature condition for memory on dimm 3 in compute book 2 has been deasserted. May also be shown as 816f0a0c2b820003 or 0x816f0a0c2b820003 se...

  • Page 1658

    816f0a0c-2b820006 an over-temperature condition has been removed on the [physicalmemoryelementname] on subsystem [memoryelementname]. Explanation: the over temperature condition for memory on dimm 6 in compute book 2 has been deasserted. May also be shown as 816f0a0c2b820006 or 0x816f0a0c2b820006 se...

  • Page 1659

    816f0a0c-2b820009 an over-temperature condition has been removed on the [physicalmemoryelementname] on subsystem [memoryelementname]. Explanation: the over temperature condition for memory on dimm 9 in compute book 2 has been deasserted. May also be shown as 816f0a0c2b820009 or 0x816f0a0c2b820009 se...

  • Page 1660

    816f0a0c-2b82000c an over-temperature condition has been removed on the [physicalmemoryelementname] on subsystem [memoryelementname]. Explanation: the over temperature condition for memory on dimm 12 in compute book 2 has been deasserted. May also be shown as 816f0a0c2b82000c or 0x816f0a0c2b82000c s...

  • Page 1661

    816f0a0c-2b82000f an over-temperature condition has been removed on the [physicalmemoryelementname] on subsystem [memoryelementname]. Explanation: the over temperature condition for memory on dimm 15 in compute book 2 has been deasserted. May also be shown as 816f0a0c2b82000f or 0x816f0a0c2b82000f s...

  • Page 1662

    816f0a0c-2b820012 an over-temperature condition has been removed on the [physicalmemoryelementname] on subsystem [memoryelementname]. Explanation: the over temperature condition for memory on dimm 18 in compute book 2 has been deasserted. May also be shown as 816f0a0c2b820012 or 0x816f0a0c2b820012 s...

  • Page 1663

    816f0a0c-2b820015 an over-temperature condition has been removed on the [physicalmemoryelementname] on subsystem [memoryelementname]. Explanation: the over temperature condition for memory on dimm 21 in compute book 2 has been deasserted. May also be shown as 816f0a0c2b820015 or 0x816f0a0c2b820015 s...

  • Page 1664

    816f0a0c-2b820018 an over-temperature condition has been removed on the [physicalmemoryelementname] on subsystem [memoryelementname]. Explanation: the over temperature condition for memory on dimm 24 in compute book 2 has been deasserted. May also be shown as 816f0a0c2b820018 or 0x816f0a0c2b820018 s...

  • Page 1665

    816f0a0c-2b830002 an over-temperature condition has been removed on the [physicalmemoryelementname] on subsystem [memoryelementname]. Explanation: the over temperature condition for memory on dimm 2 in compute book 3 has been deasserted. May also be shown as 816f0a0c2b830002 or 0x816f0a0c2b830002 se...

  • Page 1666

    816f0a0c-2b830005 an over-temperature condition has been removed on the [physicalmemoryelementname] on subsystem [memoryelementname]. Explanation: the over temperature condition for memory on dimm 5 in compute book 3 has been deasserted. May also be shown as 816f0a0c2b830005 or 0x816f0a0c2b830005 se...

  • Page 1667

    816f0a0c-2b830008 an over-temperature condition has been removed on the [physicalmemoryelementname] on subsystem [memoryelementname]. Explanation: the over temperature condition for memory on dimm 8 in compute book 3 has been deasserted. May also be shown as 816f0a0c2b830008 or 0x816f0a0c2b830008 se...

  • Page 1668

    816f0a0c-2b83000b an over-temperature condition has been removed on the [physicalmemoryelementname] on subsystem [memoryelementname]. Explanation: the over temperature condition for memory on dimm 11 in compute book 3 has been deasserted. May also be shown as 816f0a0c2b83000b or 0x816f0a0c2b83000b s...

  • Page 1669

    816f0a0c-2b83000e an over-temperature condition has been removed on the [physicalmemoryelementname] on subsystem [memoryelementname]. Explanation: the over temperature condition for memory on dimm 14 in compute book 3 has been deasserted. May also be shown as 816f0a0c2b83000e or 0x816f0a0c2b83000e s...

  • Page 1670

    816f0a0c-2b830011 an over-temperature condition has been removed on the [physicalmemoryelementname] on subsystem [memoryelementname]. Explanation: the over temperature condition for memory on dimm 17 in compute book 3 has been deasserted. May also be shown as 816f0a0c2b830011 or 0x816f0a0c2b830011 s...

  • Page 1671

    816f0a0c-2b830014 an over-temperature condition has been removed on the [physicalmemoryelementname] on subsystem [memoryelementname]. Explanation: the over temperature condition for memory on dimm 20 in compute book 3 has been deasserted. May also be shown as 816f0a0c2b830014 or 0x816f0a0c2b830014 s...

  • Page 1672

    816f0a0c-2b830017 an over-temperature condition has been removed on the [physicalmemoryelementname] on subsystem [memoryelementname]. Explanation: the over temperature condition for memory on dimm 23 in compute book 3 has been deasserted. May also be shown as 816f0a0c2b830017 or 0x816f0a0c2b830017 s...

  • Page 1673

    816f0a0c-2b840001 an over-temperature condition has been removed on the [physicalmemoryelementname] on subsystem [memoryelementname]. Explanation: the over temperature condition for memory on dimm 1 in compute book 4 has been deasserted. May also be shown as 816f0a0c2b840001 or 0x816f0a0c2b840001 se...

  • Page 1674

    816f0a0c-2b840004 an over-temperature condition has been removed on the [physicalmemoryelementname] on subsystem [memoryelementname]. Explanation: the over temperature condition for memory on dimm 4 in compute book 4 has been deasserted. May also be shown as 816f0a0c2b840004 or 0x816f0a0c2b840004 se...

  • Page 1675

    816f0a0c-2b840007 an over-temperature condition has been removed on the [physicalmemoryelementname] on subsystem [memoryelementname]. Explanation: the over temperature condition for memory on dimm 7 in compute book 4 has been deasserted. May also be shown as 816f0a0c2b840007 or 0x816f0a0c2b840007 se...

  • Page 1676

    816f0a0c-2b84000a an over-temperature condition has been removed on the [physicalmemoryelementname] on subsystem [memoryelementname]. Explanation: the over temperature condition for memory on dimm 10 in compute book 4 has been deasserted. May also be shown as 816f0a0c2b84000a or 0x816f0a0c2b84000a s...

  • Page 1677

    816f0a0c-2b84000d an over-temperature condition has been removed on the [physicalmemoryelementname] on subsystem [memoryelementname]. Explanation: the over temperature condition for memory on dimm 13 in compute book 4 has been deasserted. May also be shown as 816f0a0c2b84000d or 0x816f0a0c2b84000d s...

  • Page 1678

    816f0a0c-2b840010 an over-temperature condition has been removed on the [physicalmemoryelementname] on subsystem [memoryelementname]. Explanation: the over temperature condition for memory on dimm 16 in compute book 4 has been deasserted. May also be shown as 816f0a0c2b840010 or 0x816f0a0c2b840010 s...

  • Page 1679

    816f0a0c-2b840013 an over-temperature condition has been removed on the [physicalmemoryelementname] on subsystem [memoryelementname]. Explanation: the over temperature condition for memory on dimm 19 in compute book 4 has been deasserted. May also be shown as 816f0a0c2b840013 or 0x816f0a0c2b840013 s...

  • Page 1680

    816f0a0c-2b840016 an over-temperature condition has been removed on the [physicalmemoryelementname] on subsystem [memoryelementname]. Explanation: the over temperature condition for memory on dimm 22 in compute book 4 has been deasserted. May also be shown as 816f0a0c2b840016 or 0x816f0a0c2b840016 s...

  • Page 1681

    816f0a0c-2b84ffff an over-temperature condition has been removed on the [physicalmemoryelementname] on subsystem [memoryelementname]. Explanation: the over temperature condition for memory on compute book 4 has been deasserted. May also be shown as 816f0a0c2b84ffff or 0x816f0a0c2b84ffff severity: in...

  • Page 1682

    1664 system x3850 x6 and x3950 x6 types 3837 and 3839: installation and service guide.

  • Page 1683

    Appendix c. Uefi/post error codes use this information for an introduction to the uefi/post error codes and descriptions of the fields that are displayed for the event code. Uefi/post diagnostic error codes can be generated when the server starts up or while the server is running. Uefi/post codes ar...

  • Page 1684

    Finding the uefi (post) error code this topic provides information about how to locate the uefi/post error code. Several methods are available to help you locate the uefi/post error code based on the systems-management platform you are using or if you are viewing test results generated by the dsa pr...

  • Page 1685

    I.18005 [i.18005] explanation: a discrepancy has been detected in the number of cores reported by one or more processor packages within the system. Processors have mismatched number of cores severity: error user response: complete the following steps: 1. If this is a newly installed option, ensure t...

  • Page 1686

    I.18008 [i.18008] explanation: currently, there is no additional information for this event. Processors have mismatched internal ddr3 frequency severity: error user response: complete the following steps: 1. Verify that supported and matching dimms are installed in the channel in the correct populat...

  • Page 1687

    I.1800b [i.1800b] explanation: a cache size mismatch has been detected for one or more processor packages. Processors have one or more cache levels with mismatched size severity: error user response: complete the following steps: 1. Verify that matching processors are installed in the correct proces...

  • Page 1688

    I.1800f [i.1800f] explanation: a processor family mismatch has been detected for one or more processor packages. Processors have mismatched family severity: error user response: complete the following steps: 1. Verify that matching processors are installed in the correct processor sockets according ...

  • Page 1689

    I.3048005 [i.3048005] explanation: uefi has booted from the backup flash bank. Booting backup uefi image severity: info user response: complete the following steps: 1. Check ibm support site for an applicable service bulletin or firmware update that applies to this error. 2. Reflash primary uefi ima...

  • Page 1690

    I.3818003 [i.3818003] explanation: the crtm flash driver could not lock the secure flash region. Crtm could not lock secure flash region severity: info user response: complete the following steps: 1. If system failed to boot successfully, dc cycle system. 2. If system boots to f1 setup, flash uefi i...

  • Page 1691

    I.580a5 [i.580a5] explanation: mirror fail-over complete. Dimm number % has failed over to to the mirrored copy. Dimm mirror fail-over detected severity: info user response: complete the following steps: 1. Check the system-event log for uncorrected dimm failures and replace those dimms. I.580a6 [i....

  • Page 1692

    S.2011001 [s.2011001] explanation: an uncorrected pcie error has occurred at bus % device % function %. The vendor id for the device is % and the device id is %. Pci serr detected severity: error user response: complete the following steps: 1. Check ibm support site for an applicable device driver, ...

  • Page 1693

    S.3020007 [s.3020007] explanation: a firmware fault has been detected in the uefi image. Internal uefi firmware fault detected, system halted severity: error user response: complete the following steps: 1. Check ibm support site for an applicable service bulletin or firmware update that applies to t...

  • Page 1694

    S.3050007 [s.3050007] explanation: a firmware fault has been detected in the uefi image. Internal uefi firmware fault detected, system halted severity: error user response: complete the following steps: 1. Check ibm support site for an applicable service bulletin or firmware update that applies to t...

  • Page 1695

    S.3070007 [s.3070007] explanation: a firmware fault has been detected in the uefi image. Internal uefi firmware fault detected, system halted severity: error user response: complete the following steps: 1. Check ibm support site for an applicable service bulletin or firmware update that applies to t...

  • Page 1696

    S.51003 [s.51003] explanation: an uncorrectable memory error was detected in dimm slot % on rank %. An uncorrectable memory error was detected on processor % channel %. The failing dimm within the channel could not be determined. An uncorrectable memory error has been detected. Fatal memory error oc...

  • Page 1697

    S.58008 [s.58008] explanation: a dimm has failed the post memory test. Dimm failed memory test severity: error user response: complete the following steps: 1. You must ac-cycle the system to re-enable affected dimm connector or re-enable manually using f1 setup 2. If the node has been recently insta...

  • Page 1698

    S.680b8 [s.680b8] explanation: internal qpi link failure detected. Internal qpi link failure detected severity: error user response: complete the following steps: 1. Check ibm support site for an applicable service bulletin or firmware update that applies to this error. 2. Inspect processor socket f...

  • Page 1699

    W.3058009 [w.3058009] explanation: driver health protocol: missing configuraiton. Requires change settings from f1. Driver health protocol: missing configuration. Requires change settings from f1 severity: warning user response: complete the following steps: 1. Go to f1 setup > system settings > set...

  • Page 1700

    W.305800d [w.305800d] explanation: driver health protocol: disconnect controller failed. Requires 'reboot'. Driver health protocol: disconnect controller failed. Requires 'reboot' severity: warning user response: complete the following steps: 1. Reboot the system to reconnect the controller. 2. If p...

  • Page 1701

    W.3808002 [w.3808002] explanation: an error occurred while saving uefi settings to the imm. Error updating system configuration to imm severity: warning user response: complete the following steps: 1. Use f1 setup, verify and save settings to recover settings. 2. Reset the imm. 3. Ac cycle the syste...

  • Page 1702

    W.381800d [w.381800d] explanation: tpm physical presence is in asserted state tpm physical presence is in asserted state severity: warning user response: complete the following steps: 1. Complete any administrative tasks requiring the tpm physical presence switch to be in the "on" position.. 2. Rest...

  • Page 1703

    W.58001 [w.58001] explanation: the pfa threshold limit (correctable error logging limit) has been exceeded on dimm number % at address %. Mc5 status contains % and mc5 misc contains %. Dimm pfa threshold exceeded severity: error user response: complete the following steps: 1. If the node has recentl...

  • Page 1704

    W.58017 [w.58017] explanation: dimm re-enabled dimm re-enabled severity: warning user response: complete the following steps: 1. Check system log for related dimm failures. W.580a1 [w.580a1] explanation: invalid memory configuration for mirror mode. Please correct memory configuration. Unsupported d...

  • Page 1705

    W.580a8 [w.580a8] explanation: system memory resized system memory resized severity: warning user response: complete the following steps: 1. Check system log for related dimm failures and replace those dimms. W.580b0 [w.580b0] explanation: memory smi link failure memory smi link failure severity: wa...

  • Page 1706

    1688 system x3850 x6 and x3950 x6 types 3837 and 3839: installation and service guide.

  • Page 1707

    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 1708

    You can solve many problems without outside assistance by following the troubleshooting procedures that ibm provides in the online help or in the documentation that is provided with your ibm product. The documentation that comes with ibm systems also describes the diagnostic tests that you can perfo...

  • Page 1709

    Creating a personalized support web page you can create a personalized support web page by identifying ibm products that are of interest to you. To create a personalized support web page, go to http://www.Ibm.Com/support/ mynotifications. From this personalized page, you can subscribe to weekly emai...

  • Page 1710

    1692 system x3850 x6 and x3950 x6 types 3837 and 3839: installation and service guide.

  • Page 1711: Notices

    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 1712

    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 http://www.Ibm.Com...

  • Page 1713

    Device that has exceeded this limit might fail to respond to system-generated 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 specif...

  • Page 1714

    Table 68. 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 deliquesc...

  • Page 1715

    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 1716

    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 1717

    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 1718

    Korea communications commission (kcc) statement this is electromagnetic wave compatibility equipment for business (type a). Sellers and users need to pay attention to it. This is for any areas other than home. Russia electromagnetic interference (emi) class a statement people's republic of china cla...

  • Page 1719: Index

    Index numerics 4-socket to 8-socket upgrade kit installing 42 a about the checkout procedure 156 about the server checkout procedure 156 abr, automatic boot failure recovery 203 ac good led 166 accessible documentation 1696 acoustical noise emissions 10 active energy manager plug-in 13 adapter insta...

  • Page 1720

    Compute book covers removing 218, 220 compute book leds 162 compute book, ddr3 30 configuration information 121 configuration, nx boot failure 203 configuration, server updating 119 configurations, backplane supported 73 configuring a multinode system 135 raid arrays 147 the ethernet controller 146 ...

  • Page 1721

    Dynamic system analysis (dsa) preboot diagnostics program 13 e electrical input 11 electronic emission class a notice 1697 electronic service agent 177 embedded hypervisor using 145 enabling features on demand ethernet software 146 features on demand ethernet software upgrade key 146 features on dem...

  • Page 1722

    Hard disk drive status led 25 hardware service and support telephone numbers 1691 heat output 11 heat sink replacing 278 heat sink and microprocessor removing 276 help from the world wide web 1690 from world wide web 1690 sending diagnostic data to ibm 1690 sources of 1689 host bus adapter for syste...

  • Page 1723

    J japan class a electronic emission statement 1699 jumper on the standard i/o book board 39 uefi boot recovery 202 jumper, on the standard i/o book board 39 jumper, switches, and button on the standard i/o bookboard 39 k keyboard problems 185 korea class a electronic emission statement 1700 l lcd di...

  • Page 1724

    Operator panel, on the front of the server 27 optional device problems 190 options installing 43 overriding the power-on password 40 overview memory mirroring 53 of the ddr3 compute book 30 of the full-length i/o book 36, 82 of the half-length i/o book 35 overview of the integrated management module...

  • Page 1725

    Removing (continued) 1.8-inch hot-swap sas/sata drives 231 2.5-inch hot-swap sas/sata drives 231 a 1400-watt or 900-watt hot-swap power supply 247 a 750-watt -48 volt to -60 volt dc power supply 287 a hot-swap drive 231 a hot-swap fan 251 a microprocessor and heat sink 276 a raid adapter flash power...

  • Page 1726

    Service advisor feature, enabling 176 service and support before you call 1689 hardware 1691 software 1691 service bulletins 156 service card, server and qr code 4 service request, ibm automated 176 service technicians, trained guidelines xv serviceability, server 18 servicing the server xvi setting...

  • Page 1727

    Upgrade kit, installing 42 usb connector 33 usb 2.0 connector 27 usb 3.0 connectors 27 usb hypervisor flash device removing 245 replacing 246 using 177 embedded hypervisor 145 embedded hypervisor functions 145 the boot manager program 133 the imm first failure data capture feature 177 the remote pre...

  • Page 1728

    1710 system x3850 x6 and x3950 x6 types 3837 and 3839: installation and service guide.

  • Page 1730

    Part number: 00fh434 printed in usa (1p) p/n: 00fh434.