1. DL manuals
  2. IBM
  3. Server
  4. System x3550 M5 Type 5463
  5. Installation And Service Manual

IBM System x3550 M5 Type 5463 Installation And Service Manual

Summary of System x3550 M5 Type 5463

  • Page 1

    Ibm system x3550 m5 type 5463 installation and service guide.

  • Page 3

    Ibm system x3550 m5 type 5463 installation and service guide.

  • Page 4

    Note before using this information and the product it supports, read the general information in appendix d, “getting help and technical assistance,” on page 821, “notices” on page 825, the warranty information document, and the safety information and environmental notices and user guide documents on...

  • Page 5: Contents

    Contents safety . . . . . . . . . . . . . . . Vii safety statements . . . . . . . . . . . . Ix chapter 1. The ibm system x3550 m5 server . . . . . . . . . . . . . . . 1 the ibm documentation cd . . . . . . . . . 5 hardware and software requirements . . . . . 5 using the documentation browser . . . ....

  • Page 6

    Universal serial bus (usb) port problems . . . 101 video problems. . . . . . . . . . . . 101 solving power problems. . . . . . . . . . 101 solving ethernet controller problems . . . . . 103 solving undetermined problems . . . . . . . 104 problem determination tips. . . . . . . . . 105 recovering the...

  • Page 7

    Appendix a. Integrated management module 2.1 (imm2.1) error messages . 269 imm events that automatically notify support . . 270 appendix b. Uefi/post diagnostic codes. . . . . . . . . . . . . . . 665 appendix c. Dsa diagnostic test results . . . . . . . . . . . . . . 685 dsa broadcom network test re...

  • Page 8

    Vi ibm system x3550 m5 type 5463: installation and service guide.

  • Page 9: Safety

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

  • Page 10

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

  • Page 11

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

  • Page 12

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

  • Page 13

    Danger some laser products contain an embedded class 3a or class 3b laser diode. Note the following. Laser radiation when open. Do not stare into the beam, do not view directly with optical instruments, and avoid direct exposure to the beam. Statement 4 caution: use safe practices when lifting. ≥ 18...

  • Page 14

    Statement 6 caution: if you install a strain-relief bracket option over the end of the power cord that is connected to the device, you must connect the other end of the power cord to an easily accessible power source. Statement 8 caution: never remove the cover on a power supply or any part that has...

  • Page 15

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

  • Page 16

    Caution: hazardous moving parts are nearby. Rack safety information, statement 2 danger v always lower the leveling pads on the rack cabinet. V always install stabilizer brackets on the rack cabinet. V always install servers and optional devices starting from the bottom of the rack cabinet. V always...

  • Page 17

    Chapter 1. The ibm system x3550 m5 server this publication contains information and instructions for setting up your ibm system x3550 m5 server, instructions for installing some optional devices, cabling and configuring the server, removing and replacing devices, and diagnostics and troubleshooting ...

  • Page 18

    Hard disk drives, 3.5-inch hot-swap serial attached scsi (sas) or sata hard disk drives or 3.5-inch simple-swap sata hard disk drives. Note: v the illustrations in this document might differ slightly from your model. V the ten 2.5-inch simple-swap hard disk drive model is not supported. The followin...

  • Page 19

    The following illustration shows a server with four 3.5-inch hot-swap hard disk drive bays. The following illustration shows a server with eight 2.5-inch simple-swap hard disk drive bays. The following illustration shows a server with four 3.5-inch simple-swap hard disk drive bays. If firmware and d...

  • Page 20

    Product name ibm system x3550 m5 server machine type type 5463 model number _____________________________________________ serial number _____________________________________________ the model number and serial number are on the id label on the front of the server, as shown in the following illustrat...

  • Page 21

    The ibm documentation cd the ibm documentation cd contains documentation for the server in portable document format (pdf) and includes the ibm documentation browser to help you find information quickly. Hardware and software requirements the ibm documentation cd requires the following minimum hardwa...

  • Page 22

    To search all the documents, type a word or word string in the search field and click search. The documents in which the word or word string appears are listed in order of the most occurrences. Click a document to view it, and press crtl+f to use the acrobat search function, or press alt+f to use th...

  • Page 23

    Depending on the server model, additional documentation might be included on the ibm documentation cd. The toolscenter for system x and bladecenter is an online information center that contains information about tools for updating, managing, and deploying firmware, device drivers, and operating syst...

  • Page 24

    Memory (depending on the model): v minimum: 4 gb v maximum: 1.5 tb – 384 gb using registered dimms (rdimms) – 1.5 tb using load reduction dimms (lrdimms) v type: – pc4-12800 (ddr4-1600), pc4-14900 (ddr4-1866) or pc4-17000 (ddr4-2133) – single-rank, dual-rank, or quad-rank – registered dimm (rdimm) o...

  • Page 25

    V a serveraid m5210 sas/sata adapter that provides raid 0, 1, and 10. Optional upgrade: – raid 5/50 (1 gb cache) with optional fod raid 6/60 and sed upgrade – raid 5/50 (1 gb flash) with optional fod raid 6/60 and sed upgrade – raid 5/50 (2 gb flash) with optional fod raid 6/60 and sed upgrade – rai...

  • Page 26

    2. The noise emission level stated is the declared (upper limit) sound power level, in bels, for a random sample of machines. All measurements are made in accordance with iso 7779 and reported in conformance with iso 9296. Actual sound-pressure levels in a given location might exceed the average val...

  • Page 27

    V maximum rate of temperature change: – tape drives: 5°c/hr (41°f/hr) – hard disk drives: 20°c/hr (68°f/hr) server off : v temperature: 5°c to 45°c (41°f to 113°f) v relative humidity: 8% to 85% v maximum dew point: 27°c (80.6°f) storage (non-operating): v temperature: 1°c to 60°c (33.8°f to 140°f) ...

  • Page 28

    V 5°c/hr for data centers employing tape drives and 20°c/hr for data centers employing disk drives. V chassis is removed from original shipping container and is installed but not in use, for example, during repair, maintenance, or upgrade. V the equipment acclimation period is 1 hour per 20°c of tem...

  • Page 29

    Director/pubs/index.Jsp?Topic=%2fcom.Ibm.Director.Main.Helps.Doc %2ffqm0_main.Html and “ibm systems director” on page 17. V integrated management module 2.1 (imm2.1) the integrated management module 2.1 (imm2.1) combines service processor functions, video controller, and remote presence and blue-scr...

  • Page 30

    (ddr4-1866), or pc4-17000 (ddr4-2133), ddr4 (fourth-generation double-data-rate), synchronous dynamic random access memory (sdram) dimms. V light path diagnostics light path diagnostics provides leds to help you diagnose problems. For more information about light path diagnostics and the leds, see t...

  • Page 31

    V systems-management capabilities the server comes with an integrated management module 2.1 (imm2.1). When the imm is used with the systems-management software that comes with the server, you can manage the functions of the server locally and remotely. The imm also provides system monitoring, event ...

  • Page 32

    V full array memory mirroring (famm) redundancy v hot-swap cooling fans with speed-sensing capability v hot-swap hard disk drives v integrated management module (imm) v memory mirroring and memory sparing support v memory error correcting code and parity test v memory down sizing (non-mirrored memor...

  • Page 33

    Ibm systems director 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 director supports multiple operating systems and virtualization technologies in ibm ...

  • Page 34

    Server controls, leds, and power this section describes the controls and light-emitting diodes (leds) and how to turn the server on and off. For the locations of other leds on the system board, see “system-board leds” on page 30. Front view the following illustrations show the controls, leds, and co...

  • Page 35

    V rack release latches: press the latches on each front side of the server to remove the server from the rack. V hard disk drive activity leds: this led is used on hot-swap sas or sata hard disk drives. Each hot-swap hard disk drive has an activity led, and when this led is flashing, it indicates th...

  • Page 36

    Operator information panel the following illustrations show the controls and leds on the operator information panel. V power-control button and power-on led: press this button to turn the server on and off manually. The states of the power-on led are as follows: off: power is not present or the powe...

  • Page 37

    Lcd operating panel assembly use this information for an overview of the lcd operating panel assembly, which displays various types of information about the server. The lcd operating panel assembly is on the front of the server. It enables you to have quick access to system status, firmware, network...

  • Page 38

    The following is an example of the information that you will see on the display panel. This example shows the layout of the information in the main menu when the debug feature is enabled. When you navigate through the hierarchy of the menu options on the lcd operating panel assembly, the display pan...

  • Page 39

    – imm hostname – imm dedicated mac address note: only the mac address that is currently in use is displayed (dedicated or shared) – imm shared mac address – ip v4 information – ip v6 address v system environmental information: – ambient temperature – cpu temperature – ac input voltage – estimated po...

  • Page 40

    V pci slot 1: depending on the server configuration, insert a low-profile pci express or a ml2 adapter into this slot. V pci slot 2: depending on the server configuration, insert a half-length, full-height pci express or a low-profile pci express adapter into this slot. V pci slot 3: insert a low-pr...

  • Page 41

    V ethernet link leds: when these leds are lit, they indicate that there is an active link connection on the 10base-t, 100base-tx, or 1000base-tx interface for the ethernet port. V ethernet activity leds: when these leds are lit, they indicate that the server is transmitting to or receiving signals f...

  • Page 42

    Server components the following illustration shows the major components in the server. The illustrations in this document might differ slightly from your hardware. 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 clos...

  • Page 43

    System-board internal connectors the following illustration shows the internal connectors on the system board. System-board external connectors the following illustration shows the external connectors on the system board. Battery fan 8 connector operator information panel connector fan 7 connector f...

  • Page 44

    System-board switches, jumpers, and buttons the following illustration shows the location of the switches, jumpers, and buttons on the server. Important: 1. Before you change any switch settings or move any jumpers, turn off the server; then, disconnect all power cords and external cables. Review th...

  • Page 45

    The following table describes the jumpers on the system board. Table 1. System board jumpers jumper number jumper name jumper setting jp11 cmos clear jumper v pins 1 and 2: normal (default). V pins 2 and 3: clears the real-time clock (rtc) registry. Jp13 uefi boot backup jumper v pins 1 and 2: norma...

  • Page 46

    Table 2. System board sw3 switch block definition switch number default position description 1 off reserved. 2 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 ...

  • Page 47

    Server power features when the server is connected to an ac power source but is not turned on, the operating system does not run, and all core logic except for the integrated management module is shut down. However, the server can respond to requests from imm, such as a remote request to turn on the...

  • Page 48

    Notes: 1. When 4 gb or more of memory (physical or logical) is installed, some memory is reserved for various system resources and is unavailable to the operating system. The amount of memory that is reserved for system resources depends on the operating system, the configuration of the server, and ...

  • Page 49

    V the server can be turned off by wake on lan feature with the following limitation: note: when you install any pci adapter, the power cords must be disconnected from the power source before you remove the pci express riser-card assembly. Otherwise, the wake on lan feature might not work. V the inte...

  • Page 50

    34 ibm system x3550 m5 type 5463: installation and service guide.

  • Page 51: Chapter 2. Configuring

    Chapter 2. Configuring this chapter provides information about updating the firmware and using the configuration utilities. Updating the firmware use this information to update the firmware. Important: 1. Some cluster solutions require specific code levels or coordinated code updates. If the device ...

  • Page 52

    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 system board. V imm2.1...

  • Page 53

    V vmware esxi embedded hypervisor an optional usb flash device with vmware esxi embedded hypervisor software is available for purchase. Hypervisor is virtualization software that enables multiple operating systems to run on a host system at the same time. The usb embedded hypervisor flash device can...

  • Page 54

    Using the serverguide setup and installation cd use this information as an overview for using the serverguide setup and installation cd. The serverguide setup and installation cd provides software setup tools and installation tools that are designed for your server. The serverguide program detects t...

  • Page 55

    Setup and configuration overview serverguide setup and configuration overview when you use the serverguide setup and installation cd, you do not need setup diskettes. You can use the cd to configure any supported ibm server model. The setup program provides a list of tasks that are required to set u...

  • Page 56

    Using the setup utility use these instructions to start the setup utility. Use the unified extensible firmware interface (uefi) setup utility program to perform the following tasks: v view configuration information v view and change assignments for devices and i/o ports v set the date and time v set...

  • Page 57

    Utility, the changes are reflected in the system summary; you cannot change settings directly in the system summary. – product data select this choice to view the system-board identifier, the revision level or issue date of the firmware, the integrated management module and diagnostics code, and the...

  • Page 58

    Select this choice to view or configure trusted platform module (tpm) support. – integrated management module select this choice to view or change the settings for the integrated management module. - power restore policy select this choice to set the mode of operation after the power lost. - command...

  • Page 59

    V date and time select this choice to set the date and time in the server, in 24-hour format (hour:minute:second). This choice is on the full setup utility menu only. V start options select this choice to view or change the start options, including the startup sequence, keyboard numlock state, pxe b...

  • Page 60

    – set administrator password select this choice to set or change an administrator password. An administrator password is intended to be used by a system administrator; it limits access to the full setup utility menu. If an administrator password is set, the full setup utility menu is available only ...

  • Page 61

    Power-on password: if a power-on password is set, when you turn on the server, you must type the power-on password to complete the system startup. You can use any combination of 6 - 20 printable ascii characters for the password. When a power-on password is set, you can enable the unattended start m...

  • Page 62

    Administrator password: if an administrator password is set, you must type the administrator password for access to the full setup utility menu. You can use any combination of 6 to 20 printable ascii characters for the password. Attention: if you set an administrator password and then forget it, the...

  • Page 63

    The updatexpress system pack installer the updatexpress system pack installer detects supported and installed device drivers and firmware in the server and installs available updates. For additional information and to download the updatexpress system pack installer, go to the toolscenter for system ...

  • Page 64

    V rom-based imm firmware flash updates. V serial over lan (sol). V serial port redirection over telnet or ssh. V smi handling v system event log (sel) - user readable event log. The imm2.1 also provides the following remote server management capabilities through the ipmitool, management utility prog...

  • Page 65

    Obtaining the imm host name use this information to obtain the imm host name. About this task if you are logging on to the imm for the first time after installation, the imm defaults to dhcp. If a dhcp server is not available, the imm uses a static ip address of 192.168.70.125. The default ipv4 host...

  • Page 66

    4. On the next screen, select integrated management module. 5. On the next screen, select network configuration. 6. Find the ip address and write it down. 7. Exit from the setup utility. Logging on to the web interface use this information to log on to the web interface. About this task to log on to...

  • Page 67

    Using the embedded hypervisor the vmware esxi embedded hypervisor software is available on the optional ibm usb flash device with embedded hypervisor. About this task the usb flash device can be installed in usb connectors on the system board (see “system-board internal connectors” on page 27 for th...

  • Page 68

    Configuring the ethernet controller the ethernet controllers are integrated on the system board. They provide an interface for connecting to a 10 mbps, 100 mbps, or 1 gbps network and provide full-duplex (fdx) capability, which enables simultaneous transmission and reception of data on the network. ...

  • Page 69

    2. When prompted, is displayed, press f1. If you have set an administrator password, you must type the administrator password to access the full setup utility menu. If you do not type the administrator password, a limited setup utility menu is available. 3. Select system settings > storage. 4. Press...

  • Page 70

    Installing a newer version about this task to locate and install a newer version of ibm systems director, complete the following steps: procedure 1. Check for the latest version of ibm systems director: a. Go to http://www.Ibm.Com/systems/management/director/ downloads.Html. B. If a newer version of...

  • Page 71

    11. Select the updates that you want to install, and click install to start the installation wizard. Updating the universal unique identifier (uuid) the universal unique identifier (uuid) must be updated when the system board is replaced. Use the advanced settings utility to update the uuid in the u...

  • Page 72

    Imm_internal_ip the imm internal lan/usb ip address. The default value is 169.254.95.118. Imm_user_id the imm account (1 of 12 accounts). The default value is userid. Imm_password the imm account password (1 of 12 accounts). The default value is passw0rd (with a zero 0 not an o). Note: if you do not...

  • Page 73

    The following commands are examples of using the userid and password default values and not using the default values. Example that does not use the userid and password default values: asu set system_prod_data.Sysinfouuid --host --user --password example that does use the userid and password default ...

  • Page 74

    4. After you install asu, type the following commands to set the dmi: asu set system_prod_data.Sysinfoprodname [access_method] asu set system_prod_data.Sysinfoserialnum [access_method] asu set system_prod_data.Sysencloseassettag [access_method] where: the server machine type and model number. Type m...

  • Page 75

    The kcs access method uses the ipmi/kcs interface. This method requires that the ipmi driver be installed. Some operating systems have the ipmi driver installed by default. Asu provides the corresponding mapping layer. You can download the advanced settings utility user's guide at http://www.Ibm.Com...

  • Page 76

    60 ibm system x3550 m5 type 5463: installation and service guide.

  • Page 77: Chapter 3. Troubleshooting

    Chapter 3. Troubleshooting this section 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 help an...

  • Page 78

    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 79

    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 80

    Service bulletins 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 x3550 m5 server. To find service bulletins that are available for the ibm system x3550 m5 server, go to http://www.Ibm.Com/suppo...

  • Page 81

    V for information about power-supply problems, see “solving power problems” on page 101, “power problems” on page 94, and “power-supply leds” on page 69. V for intermittent problems, check the event log; see “event logs” on page 73 and appendix c, “dsa diagnostic test results,” on page 685. Performi...

  • Page 82

    Diagnostic tools the section introduces available tools to help you diagnose and solve hardware-related problems. V light path diagnostics use light path diagnostics to diagnose system errors quickly. See “light path diagnostics” on page 68 for more information. V event logs the event logs list the ...

  • Page 83

    - raid controller configuration - 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 even...

  • Page 84

    10. Intel gpu 11. Nvidia gpu see “running the dsa preboot diagnostic programs” on page 78 for more information on running the dsa preboot program on the server. V troubleshooting by symptom these tables list problem symptoms and actions to correct the problems. See “troubleshooting by symptom” on pa...

  • Page 85

    For the eight 2.5-inch hot-swap server configuration, it will also come with a lcd operating panel assembly, which displays a current list of errors reported by the system and other information. See the “lcd operating panel assembly” on page 21 for more information about the lcd operating panel asse...

  • Page 86

    Ac power-supply leds: use this information to view ac power-supply leds. The following minimum configuration is required for the dc led on the power supply to be lit: v power supply v power cord note: you must turn on the server for the dc led on the power supply to be lit. The following illustratio...

  • Page 87

    Ac power-supply leds description action notes ac dc error (!) on off off power-supply not fully seated, faulty system board, or the power supply has failed. 1. Reseat the power supply. 2. Use the ibm power configurator utility to ensure current system power consumption is under limitation. For more ...

  • Page 88

    Table 4. System pulse leds (continued) led description action imm heartbeat imm2.1.1 heartbeat boot process. The following steps describe the different stages of the imm2.1 heartbeat sequencing process. 1. When this led is blinking fast (approximately 4hz), this indicates, that the imm2.1 code is in...

  • Page 89

    Event logs error codes and messages displayed in post event log, system-event log, integrated management module (imm2.1) event log, and dsa event log. V post event log: this log contains the most recent error codes and messages that were generated during post. You can view the contents of the post e...

  • Page 90

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

  • Page 91

    Viewing event logs without restarting the server 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 the server. If you have installed dynamic system analysis (dsa) portable, you can use it to view th...

  • Page 92

    Table 5. Methods for viewing event logs (continued) condition action the server is hung, and no communication can be made with the imm. V if dsa preboot is installed, restart the server and press f2 to start dsa preboot and view the event logs (see “running the dsa preboot diagnostic programs” on pa...

  • Page 93

    Ibm dynamic system analysis 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 v event logs for serveraid controllers and service processors v hardware in...

  • Page 94

    Docdisplay?Lndocid=tool-bomc. In addition to the capabilities of the other editions of dsa, dsa preboot includes diagnostic routines that would be disruptive to run within the operating-system environment (such as resetting devices and causing loss of network connectivity). It has a graphical user i...

  • Page 95

    5. Type gui to display the graphical user interface, or type cmd to display the dsa interactive menu. 6. Follow the instructions on the screen to select the diagnostic test to run. Results if the diagnostic programs do not detect any hardware errors but the problem remains during normal server opera...

  • Page 96

    Automated service request (call home) ibm provides tools that can automatically collect and send data or call ibm support when an error is detected. These tools can help ibm support speed up the process of diagnosing problems. The following sections provide information about the call home tools. Ibm...

  • Page 97

    Results cd/dvd drive problems use this information to solve cd/dvd drive problems. Table 6. Cd/dvd drive's symptoms and actions v follow the suggested actions in the order in which they are listed in the action column until the problem is solved. V if an action step is preceded by “(trained technici...

  • Page 98

    General problems use this information to solve general problems. Table 7. General symptoms and actions v follow the suggested actions in the order in which they are listed in the action column until the problem is solved. V if an action step is preceded by “(trained technician only),” that step must...

  • Page 99

    Table 8. Hard disk drive symptoms and actions (continued) v follow the suggested actions in the order in which they are listed in the action column until the problem is solved. V if an action step is preceded by “(trained technician only),” that step must be performed only by a trained technician. V...

  • Page 100

    Table 8. Hard disk drive symptoms and actions (continued) v follow the suggested actions in the order in which they are listed in the action column until the problem is solved. V if an action step is preceded by “(trained technician only),” that step must be performed only by a trained technician. V...

  • Page 101

    Intermittent problems use this information to solve intermittent problems. Table 10. Intermittent problems and actions v follow the suggested actions in the order in which they are listed in the action column until the problem is solved. V if an action step is preceded by “(trained technician only),...

  • Page 102

    Table 11. Keyboard, mouse, or usb-device's symptoms and actions (continued) v follow the suggested actions in the order in which they are listed in the action column until the problem is solved. V if an action step is preceded by “(trained technician only),” that step must be performed only by a tra...

  • Page 103

    Memory problems use this information to solve memory problems. Table 12. Memory problems and actions v follow the suggested actions in the order in which they are listed in the action column until the problem is solved. V if an action step is preceded by “(trained technician only),” that step must b...

  • Page 104

    Table 12. Memory problems and actions (continued) v follow the suggested actions in the order in which they are listed in the action column until the problem is solved. V if an action step is preceded by “(trained technician only),” that step must be performed only by a trained technician. V go to t...

  • Page 105

    Microprocessor problems use this information to solve microprocessor problems. Table 13. Microprocessor's symptoms and actions v follow the suggested actions in the order in which they are listed in the action column until the problem is solved. V if an action step is preceded by “(trained technicia...

  • Page 106

    Table 14. Monitor and video's symptoms and actions (continued) v follow the suggested actions in the order in which they are listed in the action column until the problem is solved. V if an action step is preceded by “(trained technician only),” that step must be performed only by a trained technici...

  • Page 107

    Table 14. Monitor and video's symptoms and actions (continued) v follow the suggested actions in the order in which they are listed in the action column until the problem is solved. V if an action step is preceded by “(trained technician only),” that step must be performed only by a trained technici...

  • Page 108

    Network connection problems use this information to solve network connection problems. Table 15. Network connection problems and actions v follow the suggested actions in the order in which they are listed in the action column until the problem is solved. V if an action step is preceded by “(trained...

  • Page 109

    Table 16. Optional-device problems and actions (continued) v follow the suggested actions in the order in which they are listed in the action column until the problem is solved. V if an action step is preceded by “(trained technician only),” that step must be performed only by a trained technician. ...

  • Page 110

    Power problems use this information to solve power problems. Table 17. Power problems and actions v follow the suggested actions in the order in which they are listed in the action column until the problem is solved. V if an action step is preceded by “(trained technician only),” that step must be p...

  • Page 111

    Table 17. Power problems and actions (continued) v follow the suggested actions in the order in which they are listed in the action column until the problem is solved. V if an action step is preceded by “(trained technician only),” that step must be performed only by a trained technician. V go to th...

  • Page 112

    Table 17. Power problems and actions (continued) v follow the suggested actions in the order in which they are listed in the action column until the problem is solved. V if an action step is preceded by “(trained technician only),” that step must be performed only by a trained technician. V go to th...

  • Page 113

    Table 17. Power problems and actions (continued) v follow the suggested actions in the order in which they are listed in the action column until the problem is solved. V if an action step is preceded by “(trained technician only),” that step must be performed only by a trained technician. V go to th...

  • Page 114

    Table 17. Power problems and actions (continued) v follow the suggested actions in the order in which they are listed in the action column until the problem is solved. V if an action step is preceded by “(trained technician only),” that step must be performed only by a trained technician. V go to th...

  • Page 115

    Table 18. Serial device problems and actions (continued) v follow the suggested actions in the order in which they are listed in the action column until the problem is solved. V if an action step is preceded by “(trained technician only),” that step must be performed only by a trained technician. V ...

  • Page 116

    Table 19. Serverguide problems and actions (continued) v follow the suggested actions in the order in which they are listed in the action column until the problem is solved. V if an action step is preceded by “(trained technician only),” that step must be performed only by a trained technician. V go...

  • Page 117

    Universal serial bus (usb) port problems use this information to usb port problems. Table 21. Universal serial bus (usb) port problems and actions v follow the suggested actions in the order in which they are listed in the action column until the problem is solved. V if an action step is preceded by...

  • Page 118

    C. For other rail errors (pwr rail 1 error, see step 4b), remove each component that is associated with the faulty pwr rail, one at a time, in the sequence indicated in table 22, restarting the server each time, until the cause of the overcurrent condition is identified. Table 22. Components associa...

  • Page 119

    Solving ethernet controller problems the method that you use to test the ethernet controller depends on which operating system you are using. See the operating-system documentation for information about ethernet controllers, and see the ethernet controller device-driver readme file. About this task ...

  • Page 120

    Solving undetermined problems if dynamic system analysis (dsa) did not diagnose the failure or if the server is inoperative, use the information in this section. About this task if you suspect that a software problem is causing failures (continuous or intermittent), see “software problems” on page 1...

  • Page 121

    Problem determination tips because of the variety of hardware and software combinations that can encounter, use the following information to assist you in problem determination. If possible, have this information available when requesting assistance from ibm. The model name and serial number are loc...

  • Page 122

    V diagnostic program type and version level v configuration option settings v operating-system control-file setup see appendix d, “getting help and technical assistance,” on page 821 for information about calling ibm for service. Recovering the server firmware (uefi update failure) use this informat...

  • Page 123

    5. Move the uefi boot backup jumper (jp13) from pins 1 and 2 to pins 2 and 3 to enable the uefi recovery mode. 6. Reinstall the server cover; then, reconnect all power cords. 7. Restart the server. The system begins the power-on self-test (post). 8. Boot the server to an operating system that is sup...

  • Page 124

    In-band automated boot recovery method use this information to recover the server firmware and restore the server operation to the primary bank. About this task note: use this method if the board led is lit and there is a log entry or booting backup image is displayed on the firmware splash screen; ...

  • Page 125

    Nx-boot failure configuration changes, such as added devices or adapter firmware updates, and firmware or application code problems can cause the server to fail post (the power-on self-test). If this occurs, the server responds in either of the following ways: v the server restarts automatically and...

  • Page 126

    110 ibm system x3550 m5 type 5463: installation and service guide.

  • Page 127

    Chapter 4. Parts listing, ibm system x3550 m5 type 5463 the following replaceable components are available for the ibm system x3550 m5 type 5463 server. For an updated parts listing, go to http://www.Ibm.Com/supportportal/. Replaceable server components replaceable components consist of consumable p...

  • Page 128

    The following table lists the part numbers for the server replaceable components. Index description cru part number (tier 1) cru part number (tier 2) 3 power supply, 550 watt, high efficiency, platinum, ac 94y8137 3 power supply, 750 watt, high efficiency, platinum, ac 94y8144 3 power supply, 900 wa...

  • Page 129

    Index description cru part number (tier 1) cru part number (tier 2) 5 microprocessor, intel e5-2670 v3, 2.3 ghz, 30 mb, 2133 mhz, 120 w (12-core) 00ae684 5 microprocessor, intel e5-2640 v3, 2.6 ghz, 20 mb, 1866 mhz, 90 w (8-core) 00ae688 5 microprocessor, intel e5-2630 v3, 2.4 ghz, 20 mb, 1866 mhz, ...

  • Page 130

    Index description cru part number (tier 1) cru part number (tier 2) 23 hard disk drive, 3.5-inch hot-swap, near-line sas, 2 tb, 7.2 k 90y8573 23 hard disk drive, 3.5-inch hot-swap, near-line sas, 3 tb, 7.2 k 90y8578 23 self encrypting disk drive, 3.5-inch 512e near-line sas, hot-swap, 2 tb 7.2k 12 g...

  • Page 131

    Index description cru part number (tier 1) cru part number (tier 2) serveraid m5200 series 4 gb cahe (raid 5 upgrade) 47c8669 serveraid m5200 series 1 gb cahe (raid 5 upgrade) 47c8657 serveraid m5210 sas/sata controller 46c9111 serveraid m1215 sas/sata controller 46c9115 serveraid m5225 sas/sata con...

  • Page 132

    Index description cru part number (tier 1) cru part number (tier 2) rear hard disk drive cage 00kf690 pcie riser 3 assembly cage 00kf691 cable, gpu power 00kc964 cable, power 00kc957 cable, flash power module 46c9793 cable, umiq-v2 00ak143 cable, sas 750 mm 00kc952 cable, sas 600 mm 00kc953 cable, s...

  • Page 133

    Index description cru part number (tier 1) cru part number (tier 2) thermal grease kit 41y9292 alcohol wipes 59p4739 microprocessor installation tool 00ae535 cma kit, 1u 00ka595 cma kit 49y4817 com port bracket 00kc965 adapter, dvi to vga adapter 25r9043 half high lto gen 6 sas tape drive 35p1049 us...

  • Page 134

    Table 23. Structural parts, type type 5463 (continued) index description part number 35 air baffle, 3.5-inch hard disk drive bay 00kf665 35 air baffle, 2.5-inch hard disk drive bay 00kf666 bezel, eight 2.5-inch hard disk drives (no lcd system information display panel) 00kf672 bezel, ten 2.5-inch ha...

  • Page 135

    Power cords for your safety, a power cord with a grounded attachment plug is provided to use with this product. To avoid electrical shock, always use the power cord and plug with a properly grounded outlet. Ibm power cords used in the united states and canada are listed by underwriter's laboratories...

  • Page 136

    Power cord part number used in these countries and regions 39m5151 abu dhabi, bahrain, botswana, brunei darussalam, channel islands, china (hong kong s.A.R.), cyprus, dominica, gambia, ghana, grenada, iraq, ireland, jordan, kenya, kuwait, liberia, malawi, malaysia, malta, myanmar (burma), nigeria, o...

  • Page 137

    Chapter 5. Removing and replacing components there are three types of replaceable components. V structural parts: purchase and replacement of structural parts (components, such as chassis assembly, top cover, and bezel) is your responsibility. If ibm acquires or installs a structural component at yo...

  • Page 138

    Starts, if an operating system is installed, or that a 19990305 error code is displayed, indicating that an operating system was not found but the server is otherwise working correctly. If the server is not working correctly, see “running the dsa preboot diagnostic programs” on page 78 for informati...

  • Page 139

    – to avoid straining the muscles in your back, lift by standing or by pushing up with your leg muscles. V make sure that you have an adequate number of properly grounded electrical outlets for the server, monitor, and other devices. V back up all important data before you make changes to disk drives...

  • Page 140

    V you have installed the fourth and sixth fans when you installed the second microprocessor option. Working inside the server with the power on use this information when working inside the server with the power on. Attention: static electricity that is released to internal server components when the...

  • Page 141

    Updating the server configuration when you start the server for the first time after you add or remove a device, you might receive a message that the configuration has changed. The setup utility starts automatically so that you can save the new configuration settings. Some optional devices have devi...

  • Page 142

    Returning a device or component if you are instructed to return a device or component, follow all packaging instructions, and use any packaging materials for shipping that are supplied to you. Removing and replacing server components this section provides information for removing and replacing compo...

  • Page 143

    5. Press in on the blue tab on the cover-release latch and lift the cover release latch up (the cover slides to the rear). 6. Lift the server cover off the server and set it aside. Attention: for proper cooling and airflow, replace the server cover before you turn on the server. Replacing the cover ...

  • Page 144

    6. If necessary, lock the cover. 7. Slide the server back into the rack until it latches. 8. Reconnect the external cables and power cords. Latch cover figure 35. Cover installation latch lock unlock figure 36. Locking cover 128 ibm system x3550 m5 type 5463: installation and service guide.

  • Page 145

    Removing the air baffle use this information to remove the air baffle. About this task to remove the air baffle, complete the following steps: procedure 1. Read the safety information that begins on “safety” on page vii and “installation guidelines” on page 122. 2. Turn off the server and peripheral...

  • Page 146

    Note: close the retaining clip on each end of the dimm connector before installing the air baffle for proper cooling. 5. Reinstall the cover (see “replacing the cover” on page 127). 6. Slide the server into the rack. 7. Reconnect the power cords and any cables that you removed. 8. Turn on the periph...

  • Page 147

    Figure 39. Raid adapter battery or flash power module cable routing for 3.5-inch hard disk drive server models. Chapter 5. Removing and replacing components 131.

  • Page 148

    5. Remove the raid adapter battery or flash power module from the chassis. Steps for removing the raid adapter battery or flash power module for 2.5-inch hard disk drive server models. A. Open the retention clip to remove the battery or power module. Figure 40. Raid adapter battery or flash power mo...

  • Page 149

    Steps for removing the raid adapter battery or flash power module for 3.5-inch hard disk drive server models. A. Press the blue release tabs and rotate the battery or power module holder upward. B. Slightly press the retention clip outward to remove the battery or power module. Retention clip holder...

  • Page 150

    Results if you are instructed to return the raid adapter battery or flash power module, follow all packaging instructions, and use any packaging materials for shipping that are supplied to you. Replacing a raid adapter battery or flash power module use this information to replace a raid adapter batt...

  • Page 151

    Adapter on the riser card and install the riser-card assembly in the server (see “replacing an adapter” on page 180 and “replacing a pci riser-card assembly” on page 172). 5. Connect one end of the cable to the raid adapter memory module. 6. Route the cable along the chassis. Note: the cable routing...

  • Page 152

    Attention: make sure that the cable is not pinched and does not cover any connectors or obstruct any components on the system board. 7. Remove any cable covering or obstructing the holder before opening the holder. 8. Install the battery or flash power module. Steps for installing the raid adapter b...

  • Page 153

    Steps for installing the raid adapter battery or flash power module for 3.5-inch hard disk drive server models. A. Press the blue release tabs and lift the battery or power module holder upward. B. Align the cable connector with the slot on the holder. Place the battery or flash power module into th...

  • Page 154

    9. Reinstall the cover (see “replacing the cover” on page 127). 10. Slide the server into the rack. 11. Reconnect the power cords and all external cables, and turn on the server and peripheral devices. Removing a raid adapter battery or flash power module holder use this information to remove a raid...

  • Page 155

    3. Remove the raid adapter battery or flash power module (see “removing a raid adapter battery or flash power module” on page 130). 4. To remove the holder, press the blue release tab; then, slide the holder away from the chassis. Results if you are instructed to return the raid adapter battery or f...

  • Page 156

    2. Turn off the server and peripheral devices and disconnect all power cords and external devices; then, remove the cover (see “removing the cover” on page 126). 3. Slide the tray until it snaps into position in the chassis. 4. Reinstall the cover (see “replacing the cover” on page 127). 5. Slide th...

  • Page 157

    Note: use the t8 torx wedge to remove the screws. 5. Slightly side the eia bracket to the right; then, remove it from the chassis. T8 torx wrench figure 49. Screw removal eia bracket figure 50. Eia bracket removal chapter 5. Removing and replacing components 141.

  • Page 158

    Replacing the eia bracket use this information to replace the eia bracket. About this task to replace the eia bracket, complete the following steps: procedure 1. Read the safety information that begins on “safety” on page vii and “installation guidelines” on page 122. 2. Align the eia bracket with t...

  • Page 159

    Removing and replacing tier 1 crus replacement of tier 1 crus is your responsibility. If ibm installs a tier 1 cru at your request, you will be charged for the installation. The illustrations in this document might differ slightly from your hardware. Removing hot-swap hard disk drives use this infor...

  • Page 160

    Replacing hot-swap hard disk drives use this information to replace hot-swap hard disk drives. About this task the following notes describe the type of hard disk drives that the server supports and other information that you must consider when you install a hard disk drive. For a list of supported h...

  • Page 161

    C. Gently push the drive into the bay until the drive stops. D. Rotate the tray handle to the closed (locked) position. E. Check the hard disk drive status led to verify that the hard disk drive is operating correctly. If the yellow hard disk drive status led of a drive is lit continuously, that dri...

  • Page 162

    4. Reinstall the drive bay filler panel that you removed earlier. 5. If you are instructed to return the drive assembly, follow all packaging instructions, and use any packaging materials for shipping that are supplied to you. Replacing simple-swap hard disk drives use this information to replace si...

  • Page 163

    V the electromagnetic interference (emi) integrity and cooling of the server are protected by having all bays and pci and pci express slots covered or occupied. When you install a drive, pci, or pci express adapter, save the emc shield and filler panel from the bay or pci or pci express adapter slot...

  • Page 164

    Removing the 2.5-inch hot-swap rear hard disk drive kit use this information to remove the 2.5-inch hot-swap rear hard disk drive kit. About this task to remove the 2.5-inch hot-swap rear hard disk drive kit, complete the following steps. Procedure 1. Read the safety information that begins on “safe...

  • Page 165

    6. Loosen the screw located at the rear of the chassis. 7. Remove pci riser-card assembly 3 first if it is installed on the system board (see “removing a pci riser-card assembly” on page 170). Afterwards, grasp the two handles located on the sides of the 2.5-inch hot-swap rear hard disk drive kit, a...

  • Page 166

    8. If you are instructed to return the rear hard disk drive cage, follow all packaging instructions, and use any packaging materials for shipping that are supplied to you. Replacing the 2.5-inch hot-swap rear hard disk drive kit use this information to replace the 2.5-inch hot-swap rear hard disk dr...

  • Page 167

    5. Tighten the screw to secure the rear hard disk drive kit to the chassis. 6. Lift the air duct and connect the mini-sas hd (12gb) and power cables to the rear hot-swap backplane. 2.5-inch hot-swap rear hard disk drive kit pci riser-card assembly 3 1 2 figure 63. 2.5-inch hot-swap rear hard disk dr...

  • Page 168

    7. Connect the other end of the mini-sas hd (12gb) and power cables to the 2.5-inch hot-swap hard disk drive backplane and power connector. 8. Reinstall the cover (see “replacing the cover” on page 127). Figure 65. Mini-sas hd (12gb) and power cable connector location on the rear backplane sas/sata ...

  • Page 169

    9. Slide the server into the rack. 10. Reconnect the power cords and any cables that you removed. 11. Turn on the peripheral devices and the server. Removing the dvd drive use this information to remove the dvd drive. About this task to remove a dvd drive, complete the following steps: note: the dvd...

  • Page 170

    5. Slide the drive retention clip from the side of the drive. Save the clip to use when you install the replacement drive or replace the dvd drive filler panel. 6. Attach the drive retention clip to the side of the dvd drive filler panel that you removed in step 4 on page 156. 7. Slide the dvd drive...

  • Page 171

    8. If you are instructed to return the dvd drive, follow all packaging instructions, and use any packaging materials for shipping that are supplied to you. Figure 70. Dvd drive filler panel installation for 2.5-inch hard disk drive server models figure 71. Dvd drive filler panel installation for 3.5...

  • Page 172

    Replacing the dvd drive use this information to replace the dvd drive. About this task the following notes describe the type of drives that the server supports and other information that you must consider when you install a drive. For a list of supported drives, see http://www.Ibm.Com/systems/info/x...

  • Page 173

    5. Remove the retention clip from the side of the dvd drive filler panel. Save the dvd drive filler panel for future use. Note: if you are installing an dvd drive that contains a laser, observe the following safety precautions. Statement 3 figure 72. Dvd drive filler panel removal for 2.5-inch hard ...

  • Page 174

    Caution: when laser products (such as cd-roms, dvd drives, fiber optic devices, or transmitters) are installed, note the following: v do not remove the covers. Removing the covers of the laser product could result in exposure to hazardous laser radiation. There are no serviceable parts inside the de...

  • Page 175

    10. Reconnect the power cords and any cables that you removed. 11. Turn on the peripheral devices and the server. Removing the dvd drive cable use this information to remove the dvd drive cable. About this task to remove the dvd cable, complete the following steps: procedure 1. Read the safety infor...

  • Page 176

    Attention: you must press the connector release tab in order to disconnect the dvd drive cable from the system board. Do not disconnect the dvd drive cable by using excessive force. Dvd drive connector cable connector latch dvd drive cable figure 77. Dvd drive cable removal for 2.5-inch hard disk dr...

  • Page 177

    6. Slide the dvd drive out of the server (see “removing the dvd drive” on page 153). 7. From the rear of the dvd drive cage, press and hold the connector latch (on the left of the cable connector) and grasp the cable connector and slide it to the right; then, remove the dvd drive cable from the conn...

  • Page 178

    Results if you are instructed to return the dvd drive cable, follow all packaging instructions, and use any packaging materials for shipping that are supplied to you. Replacing the dvd drive cable use this information to replace the dvd drive cable. About this task to install the dvd drive cable, co...

  • Page 179

    Dvd drive connector cable connector latch dvd drive cable figure 81. Dvd drive cable routing for 2.5-inch hard disk drive server models chapter 5. Removing and replacing components 163.

  • Page 180

    6. Replace the air baffle (see “replacing the air baffle” on page 129). 7. Reinstall the cover (see “replacing the cover” on page 127). 8. Slide the server into the rack. 9. Reconnect the power cords and any cables that you removed. 10. Turn on the peripheral devices and the server. Removing a memor...

  • Page 181

    Results if you are instructed to return the dimm, follow all packaging instructions, and use any packaging materials for shipping that are supplied to you. Memory module installation the following notes describe the types of dimms that the server supports and other information that you must consider...

  • Page 182

    V blank = 1.2 v specified - wwwww is the dimm bandwidth, in mbps 12800 = 12.80 gbps (ddr4-1600 sdrams, 8-byte primary data bus) 14900 = 14.93 gbps (ddr4-1866 sdrams, 8-byte primary data bus) 17000 = 17.00 gbps (ddr4-2133 sdrams, 8-byte primary data bus) - m is the dimm type l = load reduction dimm (...

  • Page 183

    V the rdimm options that are available for the server are 4 gb, 8 gb, and 16 gb. The server supports a minimum of 4 gb and a maximum of 384 gb of system memory using rdimms. V the lrdimm option that is available for the server is 32 gb and 64 gb. The server supports a minimum of 32 gb and a maximum ...

  • Page 184

    Dimm installation sequence depending on the server model, the server may come with a minimum of one 2 gb or 4 gb dimm installed in slot 1. When you install additional dimms, install them in the order shown in the following table to optimize system performance. In general, all three channels on the m...

  • Page 185

    7. Turn the dimm so that the alignment slot align correctly with the alignment tab. 8. Insert the dimm into the connector by aligning the edges of the dimm with the slots at the ends of the dimm connector (see “system-board internal connectors” on page 27 for the locations of the dimm connectors). 9...

  • Page 186

    Removing a pci riser-card assembly use this information to remove a pci riser-card assembly. About this task note: pci riser-card brackets must be installed even if you do not install an adapter. To remove a pci riser-card assembly, complete the following steps: procedure 1. Read the safety informat...

  • Page 187

    1u pcie riser 2 assembly (1x full-height half-length; x16 and 1x low profile; x8 or x16) 1u pcie riser 1 assembly (1x ml2; x16) figure 87. Pci riser-card assembly removal (2) 1u pcie riser 2 assembly (2 x low profile; x8 or x16) bracket 1u pcie riser 1 assembly (1x ml2; x16) figure 88. Pci riser-car...

  • Page 188

    6. Remove the adapter, if one is present, from the pci riser-card assembly (see “removing an adapter” on page 177). 7. Set the adapter and the pci riser-card assembly aside. Results if you are instructed to return the pci riser-card assembly, follow all packaging instructions, and use any packaging ...

  • Page 189

    Table 27. Configuration 2 configuration 2 configura tion number of micropro cessors installed pci riser-card assembly connector 1 on system board pci riser-card assembly connector 2 on system board slot 1 slot 2 slot 3 v three low- profile slots one or two x1/x4/x8/x16 low-profile x1/x4/x8/x16 low-p...

  • Page 190

    Table 30. Configuration 5. Note: slot 1 is for standard low-profile ml2 adapter configuration 5 configura tion number of micropro cessors installed pci riser-card assembly connector 1 on system board pci riser-card assembly connector 2 on system board slot 1 slot 2 slot 3 v one ml2 slot v two low- p...

  • Page 191

    3. Remove the cover (see “removing the cover” on page 126). 4. Install the adapter in the new pci riser-card assembly (see “replacing an adapter” on page 180). 5. Set any jumpers or switches on the adapter as directed by the adapter manufacturer. 6. Remove the pci filler panel, if one is present, fr...

  • Page 192

    1u pcie riser 2 assembly (1x full-height half-length; x16 and 1x low profile; x8 or x16) 1u pcie riser 1 assembly (1x ml2; x16) figure 91. Pci riser-card assembly installation (2) 1u pcie riser 2 assembly (2 x low profile; x8 or x16) bracket 1u pcie riser 1 assembly (1x ml2; x16) figure 92. Pci rise...

  • Page 193

    8. Reinstall the cover (see “replacing the cover” on page 127). 9. Slide the server into the rack. 10. Reconnect the power cords and any cables that you removed. 11. Turn on the peripheral devices and the server. Removing an adapter use this information to remove an adapter. About this task to remov...

  • Page 194

    Adapter expansion filler figure 94. Adapter removal from a pci riser-card assembly that has one low-profile slot (for pci riser-card assembly connector 1 on system board) adapter expansion filler figure 95. Adapter removal from a pci riser-card assembly that has one low-profile slot for ml2 card (fo...

  • Page 195

    Results if you are instructed to return the adapter, follow all packaging instructions, and use any packaging materials for shipping that are supplied to you. Adapter adapter expansion filler expansion filler figure 97. Adapter removal from a pci riser-card assembly that has two low-profile slots (f...

  • Page 196

    Replacing an adapter the following notes describe the types of adapters that the server supports and other information that you must consider when you install an adapter. About this task v locate the documentation that comes with the adapter and follow those instructions in addition to the instructi...

  • Page 197

    Table 33. Adapter configurations (continued) description option part number pci riser 1 pci riser 2 table note: 1. You can purchase ibm system x3550 m5 thermal solution kit (option part number 00y7117) to acquire two additional fans for your server. V the server provides two pci riser-card slots on ...

  • Page 198

    Table 36. Configuration 3. Note: slot 1 is for 60mm ml2 adapter configuration 3 configura tion number of micropro cessors installed pci riser-card assembly connector 1 on system board pci riser-card assembly connector 2 on system board slot 1 slot 2 slot 3 v one ml2 slot v one full- height, half- le...

  • Page 199

    Table 39. Configuration 6. Note: slot 1 is for standard low-profile ml2 adapter configuration 6 configura tion number of micropro cessors installed pci riser-card assembly connector 1 on system board pci riser-card assembly connector 2 on system board slot 1 slot 2 slot 3 v one ml2 slot v two low- p...

  • Page 200

    5. Insert the adapter into the pci riser-card assembly, aligning the edge connector on the adapter with the connector on the pci riser-card assembly. Press the edge of the connector firmly into the pci riser-card assembly. Make sure that the adapter snaps into the pci riser-card assembly securely. T...

  • Page 201

    Attention: when you install an adapter, make sure that the adapter is correctly seated in the riser-card assembly and that the riser-card assembly is securely seated in the riser-card connector on the system board before you turn on the server. An incorrectly seated adapter might cause damage to the...

  • Page 202

    Removing a serveraid sas/sata controller use this information to remove a serveraid sas/sata controller. About this task the serveraid sas/sata controller can be installed in the dedicated connector on the system board or pci riser-card slots (see “system-board internal connectors” on page 27 for th...

  • Page 203

    Steps for removing a sas/sata adapter from the pci riser-card assembly. A. Remove the pci riser-card assembly that contains the sas/sata adapter (see “removing a pci riser-card assembly” on page 170). B. Remove the sas/sata adapter from the pci riser card assembly (see “removing an adapter” on page ...

  • Page 204

    Steps for inserting a sas/sata adapter in the dedicated connector on the system board a. Insert the sas/sata adapter into the raid connector on the system board until it is firmly seated. The retention brackets secure the sas/sata adapter in place when the adapter is firmly seated into the connector...

  • Page 205

    Sas/sata power connector sas/sata configuration connector sas/sata configuration and power cable sas/sata signal cable figure 106. Serveraid adapter cable routing for four hot-swap 3.5-inch hard disk drive configuration chapter 5. Removing and replacing components 189.

  • Page 206

    Sas/sata configuration and power cable sas/sata signal cable sas/sata power connector sas/sata configuration connector figure 107. Serveraid adapter cable routing for eight hot-swap 2.5-inch hard disk drive configuration 190 ibm system x3550 m5 type 5463: installation and service guide.

  • Page 207

    8. Connect the signal cables to the sas/sata adapter: 9. Reconnect any cables that you removed. 10. Replace pci riser-card assembly 1 if you have removed it earlier (see “replacing a pci riser-card assembly” on page 172). 11. Reinstall the cover (see “replacing the cover” on page 127). 12. Turn on t...

  • Page 208

    Removing the serveraid adapter memory module use this information to remove the serveraid adapter memory module. About this task to remove the serveraid adapter memory module, complete the following steps: procedure 1. Read the safety information that begins on “safety” on page vii and “installation...

  • Page 209

    Replacing the serveraid adapter memory module use this information to replace the serveraid adapter memory module. About this task to install the serveraid adapter memory module, complete the following steps: procedure 1. Read the safety information that begins on “safety” on page vii and “installat...

  • Page 210

    Removing a thermal kit (hot-swap fan) use this information to remove a thermal kit (hot-swap fan). About this task attention: to ensure proper server operation, replace a failed hot-swap fan within 30 seconds. To remove a hot-swap-fan, complete the following steps: procedure 1. Read the safety infor...

  • Page 211

    Replacing a thermal kit (hot-swap fan) use this information to replace a thermal kit (hot-swap fan) about this task the server comes standard with four dual-motor hot-swap cooling fans. When there is one microprocessor installed, install fan 1, 2, 3, and 5 for proper cooling. Attention: to ensure pr...

  • Page 212

    Note: make sure that the newly-installed fan aligns horizontally with other correctly-seated fans for proper installation. 6. Reinstall the cover (see “replacing the cover” on page 127). 7. Slide the server into the rack. Removing a power supply use this information to remove a power supply. Removin...

  • Page 213

    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 214

    Results if you are instructed to return the power supply, follow all packaging instructions, and use any packaging materials for shipping that are supplied to you. Replacing a power supply use this information to replace a power supply. Replacing a hot-swap ac power supply use this information to re...

  • Page 215

    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 216

    4. 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 power supply connects firmly into the power-supply connector. Attention: do not mix 550-watt, 750-watt or 900-watt power supplies in the server. 5. Rou...

  • Page 217

    Removing a hot-swap hard disk drive backplane use this information to remove a hot-swap hard disk drive backplane. About this task to remove the hot-swap hard disk drive backplane, complete the following steps: procedure 1. Read the safety information that begins on “safety” on page vii and “install...

  • Page 218

    A. Carefully lift the backplane out of the chassis by pulling outwards and lifting it up. Steps for removing a 4 x 3.5-inch hot-swap hard disk drive backplane. A. Lift the release latches that secures the backplane to the chassis. B. Carefully lift the backplane out of the chassis by pulling outward...

  • Page 219

    7. Disconnect all cables from the hard disk drive backplane. Results if you are instructed to return the hard disk drive backplane, follow all packaging instructions, and use any packaging materials for shipping that are supplied to you. Replacing a hot-swap hard disk drive backplane use this inform...

  • Page 220

    B. Carefully lower the hard disk drive backplane until it is fully seated in the chassis. Steps for installing a 10 x 2.5-inch hot-swap hard disk drive backplane. A. Align the backplane with the slots on the chassis. B. Carefully lower the hard disk drive backplane until it is fully seated in the ch...

  • Page 221

    Steps for installing a 4 x 3.5-inch hot-swap hard disk drive backplane. A. Carefully lower the hard disk drive backplane until it is fully seated in the chassis. B. Secure the backplane to the chassis by pressing the release latches. 10 x 2.5-inch hard disk drive backplane figure 121. 10 x 2.5-inch ...

  • Page 222

    4. Connect the signal, power and configuration cables to the system board. Route the signal cable from the drive backplane along the chassis and connect it to the sas/sata controller connectors. Then, route the power cable and the configuration cable from the drive backplane along the chassis and co...

  • Page 223

    Sas/sata power cable sas/sata power cable sas/sata signal cables sas/sata power connector sas/sata configuration connector figure 124. 10 x 2.5-inch hot-swap backplane cable connection chapter 5. Removing and replacing components 207.

  • Page 224

    Sas/sata power cable sas/sata power cable sas/sata signal cables sas/sata power connector sas/sata configuration connector figure 125. 12 x 2.5-inch hot-swap backplane cable connection 208 ibm system x3550 m5 type 5463: installation and service guide.

  • Page 225

    5. Reinstall the hard disk drives and filler panels (see “replacing hot-swap hard disk drives” on page 144). 6. Reinstall the cover (see “replacing the cover” on page 127). 7. Slide the server into the rack. 8. Reconnect the power cords and any cables that you removed. 9. Turn on the peripheral devi...

  • Page 226

    5. Slide the blue release tab to the right with one finger while using another finger to grasp the black drive handle and pull the hard disk drives out of the server slightly to disengage them from the hard disk drive backplate (see “removing simple-swap hard disk drives” on page 145). 6. Remove the...

  • Page 227

    7. Disconnect the power and signal cables from the system board. Results if you are instructed to return the hard disk drive backplate assembly, follow all packaging instructions, and use any packaging materials for shipping that are supplied to you. Replacing a simple-swap hard disk drive backplate...

  • Page 228

    A. Align the backplate assembly with the slots on the chassis. B. Carefully lower the backplate assembly into the chassis until it is seated firmly. Steps for installing a 4 x 3.5-inch simple-swap hard disk drive backplate assembly. A. Carefully lower the backplate assembly into the chassis until it...

  • Page 229

    3. Connect the signal and power cables to the system board. Route the signal cable from the drive backplane along the chassis and connect it to the sas/sata signal connector . Then, route the power cable from the drive backplate assembly along the chassis and connect it to the simple-swap sata power...

  • Page 230

    Sas/sata power cable sas/sata signal cables sas/sata power connector figure 131. 8 x 2.5-inch simple-swap backplate assembly cable connection 214 ibm system x3550 m5 type 5463: installation and service guide.

  • Page 231

    4. Reinstall the hard disk drives and filler panels (see “replacing simple-swap hard disk drives” on page 146). 5. Reinstall the cover (see “replacing the cover” on page 127). 6. Slide the server into the rack. 7. Reconnect the power cords and any cables that you removed. 8. Turn on the peripheral d...

  • Page 232

    Removing a usb embedded hypervisor flash device use this information to remove a usb embedded hypervisor flash device. About this task to remove a usb hypervisor flash device, complete the following steps: procedure 1. Read the safety information that begins on “safety” on page vii and “installation...

  • Page 233

    Replacing a usb embedded hypervisor flash device use this information to replace a usb embedded hypervisor flash device. About this task to install a usb hypervisor flash device, complete the following steps: procedure 1. Read the safety information that begins on “safety” on page vii and “installat...

  • Page 234

    Removing the system battery use this information 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 your safety in mind. The lithium battery must be handled correctly to avoid ...

  • Page 235

    4. If necessary, lift pci riser-card assembly 1 or the 2.5-inch hot-swap rear hard disk drive kit out of the chassis (see “removing a pci riser-card assembly” on page 170 or “removing the 2.5-inch hot-swap rear hard disk drive kit” on page 148). 5. Locate the system battery on the system board. A. I...

  • Page 236

    6. Dispose of the battery as required by local ordinances or regulations. See the ibm environmental notices and user's guide on the ibm documentation cd for more information. Replacing the system battery use this information to replace the system battery. About this task the following notes describe...

  • Page 237

    5. If necessary, lift pci riser-card assembly 1 or the 2.5-inch hot-swap rear hard disk drive kit out of the chassis (see “removing a pci riser-card assembly” on page 170 or “removing the 2.5-inch hot-swap rear hard disk drive kit” on page 148). 6. Locate the system battery connector on the system b...

  • Page 238

    8. Reinstall the cover (see “replacing the cover” on page 127). 9. Slide the server into the rack. 10. Reconnect the external cables; then, reconnect the power cords and turn on the peripheral devices and the server. 11. Start the setup utility and reset the configuration. V set the system date and ...

  • Page 239

    Ten 2.5-inch hot-swap hard disk drive server configuration: front video connector front usb assembly connector operator information panel connector lcd display cable connector optical drive connector release latch figure 139. Media cage removal for eight 2.5-inch hot-swap or simple-swap hard disk dr...

  • Page 240

    Four 3.5-inch hot-swap or simple-swap hard disk drive server configuration: 5. If you are instructed to return the media cage, follow all packaging instructions, and use any packaging materials for shipping that are supplied to you. Replacing the media cage use this information to replace the media ...

  • Page 241

    Ten 2.5-inch hot-swap hard disk drive server configuration: four 3.5-inch hot-swap or simple-swap hard disk drive server configuration: front video connector front usb assembly connector operator information panel connector lcd display cable connector optical drive connector figure 142. Media cage i...

  • Page 242

    3. Reinstall the air baffle (see “replacing the air baffle” on page 129). 4. Reinstall the cover (see “replacing the cover” on page 127). 5. Slide the server into the rack. 6. Reconnect the power cords and any cables that you removed. 7. Turn on the peripheral devices and the server. Removing the fr...

  • Page 243

    Ten 2.5-inch hot-swap hard disk drive server configuration: four 3.5-inch hot-swap or simple-swap hard disk drive server configuration: figure 145. Front usb connector assembly removal for eight 2.5-inch hot-swap or simple-swap hard disk drive server configuration figure 146. Front usb connector ass...

  • Page 244

    5. If you are instructed to return the front usb connector assembly, follow all packaging instructions, and use any packaging materials for shipping that are supplied to you. Replacing the front usb connector assembly use this information to replace the front usb connector assembly. About this task ...

  • Page 245

    Ten 2.5-inch hot-swap hard disk drive server configuration: four 3.5-inch hot-swap or simple-swap hard disk drive server configuration: figure 148. Front usb connector assembly installation for eight 2.5-inch hot-swap or simple-swap hard disk drive server configuration figure 149. Front usb connecto...

  • Page 246

    3. Carefully push the media cage back into the chassis (see “replacing the media cage” on page 224). Remember to reconnect the cables that were removed from the system board. 4. Reinstall the cover (see “replacing the cover” on page 127). 5. Reconnect the power cords and any cables that you removed....

  • Page 247

    Ten 2.5-inch hot-swap hard disk drive server configuration: four 3.5-inch hot-swap or simple-swap hard disk drive server configuration: media cage video connector screws figure 151. Front video connector assembly removal for eight 2.5-inch hot-swap or simple-swap hard disk drive server configuration...

  • Page 248

    6. If you are instructed to return the front video connector assembly, follow all packaging instructions, and use any packaging materials for shipping that are supplied to you. Replacing the front video connector assembly use this information to replace the front video connector assembly. About this...

  • Page 249

    Ten 2.5-inch hot-swap hard disk drive server configuration: four 3.5-inch hot-swap or simple-swap hard disk drive server configuration: media cage video connector screws figure 154. Front video connector assembly installation for eight 2.5-inch hot-swap or simple-swap hard disk drive server configur...

  • Page 250

    3. Carefully push the media cage back into the chassis (see “replacing the media cage” on page 224). Remember to reconnect the cables that were removed from the system board. 4. Reinstall the cover (see “replacing the cover” on page 127). 5. Slide the server into the rack. 6. Reconnect the power cor...

  • Page 251

    4. Disconnect the cable from the back of the operator information panel assembly. This step applies to all types of server configurations. 5. For the eight 2.5-inch hot-swap or simple-swap and ten 2.5-inch hot-swap hard disk drive server configuration, remove the operator information panel assembly ...

  • Page 252

    Ten 2.5-inch hot-swap hard disk drive server configuration: 6. If you are instructed to return the operator information panel assembly, follow all packaging instructions, and use any packaging materials for shipping that are supplied to you. Figure 158. Operator information panel assembly removal fr...

  • Page 253

    Replacing the operator information panel assembly use this information to replace the operator information panel assembly. About this task to install the operator information panel, complete the following steps. Procedure 1. Read the safety information that begins on “safety” on page vii and “instal...

  • Page 254

    3. Carefully push the media cage back into the chassis (see “replacing the media cage” on page 224). Remember to reconnect the cables that were removed from the system board. 4. For the four 3.5-inch hot-swap or simple-swap hard disk drive server configuration, slide the operator information panel i...

  • Page 255

    5. Reconnect the operator information panel assembly cable to the operator information panel assembly. This step applies to all types of server configurations. 6. Reinstall the cover (see “replacing the cover” on page 127). 7. Slide the server into the rack. 8. Reconnect the power cords and any cabl...

  • Page 256

    Replacing the lcd system information display panel use this information to replace the lcd system information display panel. About this task to install the lcd system information display panel, complete the following steps. Note: the lcd system information display panel is available only in the ten ...

  • Page 257

    Removing the com port bracket use this information to remove the com port bracket. About this task to remove the com port bracket, complete the following steps: procedure 1. Read the safety information that begins on “safety” on page vii and “installation guidelines” on page 122. 2. Turn off the ser...

  • Page 258

    Note: for some it may be easier to remove the com port bracket by first slightly removing pcie riser 2 assembly from the system board 6. If you are instructed to return the com port bracket, follow all packaging instructions, and use any packaging materials for shipping that are supplied to you. Rep...

  • Page 259

    5. Insert pcie riser 2 assembly onto the system board (see “replacing a pci riser-card assembly” on page 172). 6. Insert the com port bracket connector into the opening of pcie riser 2 assembly from inside the server; then tighten the screws. 7. Connect the com port bracket cable to the system board...

  • Page 260

    8. Reinstall the cover (see “replacing the cover” on page 127). 9. Slide the server into the rack. 10. Reconnect the power cords and any cables that you removed. 11. Turn on the peripheral devices and the server. Removing the security bezel use this information to remove the security bezel. About th...

  • Page 261

    4. Press the release latch and rotate the security bezel away from the chassis. 5. If you are instructed to return the security bezel, follow all packaging instructions, and use any packaging materials for shipping that are supplied to you. Security bezel figure 170. Unlocking the security bezel rel...

  • Page 262

    Replacing the security bezel use this information to replace the security bezel. About this task note: installation of the security bezel is to limit access for increased security. To replace the security bezel, complete the following steps: procedure 1. Read the safety information that begins on “s...

  • Page 263

    6. Reconnect the power cords and any cables that you may have removed. 7. Turn on the peripheral devices and the server. Removing and replacing tier 2 crus you may install a tier 2 cru yourself or request ibm to install it, at no additional charge, under the type of warranty service that is designat...

  • Page 264

    To remove a microprocessor and heat sink, complete the following steps: procedure 1. Read the safety information that begins on “safety” on page vii and “installation guidelines” on page 122. 2. Turn off the server and peripheral devices and disconnect all power cords. 3. Remove the cover (see “remo...

  • Page 265

    7. Open the microprocessor socket release levers and retainer. A. Identify which release lever is labeled as the first release lever to open and open it. B. Open the second release lever on the microprocessor socket. C. Open the microprocessor retainer. Attention: do not touch the microprocessor con...

  • Page 266

    B. Align the installation tool with the screws, as shown in the following graphic, and lower the installation tool on the microprocessor. The installation tool rests flush on the socket only when it is aligned correctly. C. Using the following instructions for your installation tool to remove the mi...

  • Page 267

    D. Lift the microprocessor out of the socket. 9. Install the new microprocessor (see “replacing a microprocessor and heat sink” on page 252). Attention: if you are replacing a microprocessor, use the empty installation tool that comes with the new microprocessor to remove the microprocessor. 10. If ...

  • Page 268

    Replacing a microprocessor and heat sink the following notes describe the type of microprocessor that the server supports and other information that you must consider when you install a microprocessor and heat sink. About this task v microprocessors are to be installed only by trained technicians. I...

  • Page 269

    V both microprocessor voltage regulator modules are integrated on the system board. V read the documentation that comes with the microprocessor to determine whether you have to update the server firmware. To download the latest level of server firmware and other code updates for your server, go to h...

  • Page 270

    5. Open the microprocessor socket release levers and retainer: a. Identify which release lever is labeled as the first release lever to open and open it. B. Open the second release lever on the microprocessor socket. C. Open the microprocessor retainer. Attention: do not touch the connectors on the ...

  • Page 271

    C. Install the microprocessor using the following instructions for your installation tool. V when using the installation tool, twist the handle of the installation tool assembly counterclockwise until the microprocessor is inserted into the socket, and lift the installation tool out of the socket. F...

  • Page 272

    Attention: v do not press the microprocessor into the socket. V make sure that the microprocessor is oriented and aligned correctly in the socket before you try to close the microprocessor retainer. V do not touch the thermal material on the bottom of the heat sink or on top of the microprocessor. T...

  • Page 273

    A. Close the microprocessor retainer on the microprocessor socket. B. Identify which release lever is labeled as the first release lever to close and close it. C. Close the second release lever on the microprocessor socket. 9. Install the heat sink. Attention: v do not set down the heat sink after y...

  • Page 274

    C. Align and place the heat sink on top of the microprocessor in the retention bracket, thermal material side down. D. Press firmly on the heat sink. E. Press down on the center of the heat sink; then, press firmly on the captive screws and tighten them, alternating between the screws in a figure-8 ...

  • Page 275

    To replace damaged or contaminated thermal grease on the microprocessor and heat sink, complete the following steps: procedure 1. Place the heat sink on a clean work surface. 2. Remove the cleaning pad from its package and unfold it completely. 3. Use the cleaning pad to wipe the thermal grease from...

  • Page 276

    Removing the system board use this information to remove the system board. About this task notes: 1. When you replace the system board, you must either update the server with the latest firmware or restore the pre-existing firmware that the customer provides on a diskette or cd image. Make sure that...

  • Page 277

    A. Remove the socket covers from the microprocessor sockets on the new system board and place them on the microprocessor sockets of the system board you are removing. B. Do not allow the thermal grease to come in contact with anything, and keep each heat sink paired with its microprocessor for reins...

  • Page 278

    14. Loosen the two thumbscrews (one is near pci slot 1 and one is near pci slot 2). 15. Grasp the system board handles and slide the system board toward the front of the server until it stops. Note: make sure that the system board disengage from all system-board standoffs. 16. Slightly push the syst...

  • Page 279

    17. Remove the socket covers from the microprocessor sockets on the new system board and place them on the microprocessor sockets of the old system board that you are removing. 18. If you are instructed to return the system board, follow all packaging instructions, and use any packaging materials fo...

  • Page 280

    Demand user's guide. To download the document, go to /http:// www.Ibm.Com/systems/x/fod/, log in, and click help. 5. Some cluster solutions require specific code levels or coordinated code updates. If the device is part of a cluster solution, verify that the latest level of code is supported for the...

  • Page 281

    3. Fasten the two thumbscrews (one is near pci slot 2 and one is between fans 4 and 5). 4. For 2.5-inch hard disk drive server models, close the system board retention lever. For the 3.5-inch hard disk drive server models, press the blue release tabs and lower the battery or power module holder into...

  • Page 282

    5. Reinstall the hot-swap fans (see “replacing a thermal kit (hot-swap fan)” on page 195). 6. (trained technician only) install the microprocessor and heat sink (see “replacing a microprocessor and heat sink” on page 252). 7. Reinstall the memory modules (see “memory module installation” on page 165...

  • Page 283

    17. Start the setup utility and reset the configuration. V set the system date and time. V set the power-on password. V reconfigure the server. See “using the setup utility” on page 40 for more details. 18. Either update the server with the latest raid firmware or restore the pre-existing firmware f...

  • Page 284

    268 ibm system x3550 m5 type 5463: installation and service guide.

  • Page 285: Error Messages

    Appendix a. Integrated management module 2.1 (imm2.1) error messages 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 following fields are displayed: event identifier a hexadecimal identifier that uniq...

  • Page 286

    Cim information 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 electronic s...

  • Page 287

    Table 41. Events that automatically notify support (continued) event id message string automatically notify support 806f0021-2c01ffff fault in slot [physicalconnectorsystemelementname] on system [computersystemelementname]. (ml2 card fault) yes 806f0021-3001ffff fault in slot [physicalconnectorsyste...

  • Page 288

    Table 41. Events that automatically notify support (continued) event id message string automatically notify support 806f010c-2008ffff uncorrectable error detected for [physicalmemoryelementname] on subsystem [memoryelementname]. (dimm 8) yes 806f010c-2009ffff uncorrectable error detected for [physic...

  • Page 289

    Table 41. Events that automatically notify support (continued) event id message string automatically notify support 806f010c-2014ffff uncorrectable error detected for [physicalmemoryelementname] on subsystem [memoryelementname]. (dimm 20) yes 806f010c-2015ffff uncorrectable error detected for [physi...

  • Page 290

    Table 41. Events that automatically notify support (continued) event id message string automatically notify support 806f010d-0408ffff the drive [storagevolumeelementname] has been disabled due to a detected fault. (drive 8) yes 806f010d-0409ffff the drive [storagevolumeelementname] has been disabled...

  • Page 291

    Table 41. Events that automatically notify support (continued) event id message string automatically notify support 806f020d-0405ffff failure predicted on drive [storagevolumeelementname] for array [computersystemelementname]. (drive 5) yes 806f020d-0406ffff failure predicted on drive [storagevolume...

  • Page 292

    Table 41. Events that automatically notify support (continued) event id message string automatically notify support 806f050c-2006ffff memory logging limit reached for [physicalmemoryelementname] on subsystem [memoryelementname]. (dimm 6) yes 806f050c-2007ffff memory logging limit reached for [physic...

  • Page 293

    Table 41. Events that automatically notify support (continued) event id message string automatically notify support 806f050c-2012ffff memory logging limit reached for [physicalmemoryelementname] on subsystem [memoryelementname]. (dimm 18) yes 806f050c-2013ffff memory logging limit reached for [physi...

  • Page 294

    Table 41. Events that automatically notify support (continued) event id message string automatically notify support 806f060d-0408ffff array [computersystemelementname] has failed. (drive 8) yes 806f060d-0409ffff array [computersystemelementname] has failed. (drive 9) yes 806f060d-040affff array [com...

  • Page 295

    40000002-00000000 certificate authority [arg1] has detected a [arg2] certificate error. Explanation: this message is for the use case when there is an error with an ssl server, ssl client, or ssl trusted ca certificate. May also be shown as 4000000200000000 or 0x4000000200000000 severity: error aler...

  • Page 296

    40000005-00000000 ethernet mtu setting modified from [arg1] to [arg2] by user [arg3]. Explanation: this message is for the use case where a user modifies the ethernet port mtu setting. May also be shown as 4000000500000000 or 0x4000000500000000 severity: info alert category: none serviceable: no cim...

  • Page 297

    40000008-00000000 hostname set to [arg1] by user [arg2]. Explanation: this message is for the use case where user modifies the hostname of a management controller. May also be shown as 4000000800000000 or 0x4000000800000000 severity: info alert category: system - imm network event serviceable: no ci...

  • Page 298

    4000000b-00000000 ip address of default gateway modified from [arg1] to [arg2] by user [arg3]. Explanation: this message is for the use case where a user modifies the default gateway ip address of a management controller. May also be shown as 4000000b00000000 or 0x4000000b00000000 severity: info ale...

  • Page 299

    4000000e-00000000 remote login successful. Login id: [arg1] from [arg2] at ip address [arg3]. Explanation: this message is for the use case where a user successfully logs in to a management controller. May also be shown as 4000000e00000000 or 0x4000000e00000000 severity: info alert category: system ...

  • Page 300

    40000011-00000000 security: login id: [arg1] had [arg2] login failures from cli at [arg3]. Explanation: this message is for the use case where a user has failed to log in to a management controller from the legacy cli. May also be shown as 4000001100000000 or 0x4000001100000000 severity: warning ale...

  • Page 301

    40000014-00000000 the [arg1] on system [arg2] cleared by user [arg3]. Explanation: this message is for the use case where a management controller event log on a system is cleared by a user. May also be shown as 4000001400000000 or 0x4000001400000000 severity: info alert category: none serviceable: n...

  • Page 302

    40000017-00000000 enet[[arg1]] ip-cfg:hstname=[arg2], ip@=[arg3] ,netmsk=[arg4], gw@=[arg5] . Explanation: this message is for the use case where a management controller ip address and configuration has been assigned statically using user data. May also be shown as 4000001700000000 or 0x400000170000...

  • Page 303

    4000001a-00000000 dhcp setting changed to [arg1] by user [arg2]. Explanation: this message is for the use case where a user changes the dhcp setting. May also be shown as 4000001a00000000 or 0x4000001a00000000 severity: info alert category: none serviceable: no cim information: prefix: imm and id: 0...

  • Page 304

    4000001d-00000000 watchdog [arg1] failed to capture screen. Explanation: this message is for the use case where 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...

  • Page 305

    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: this message is for the use case where a management controller firmware version does not match the server....

  • Page 306

    40000022-00000000 ssl data in the management controller [arg1] configuruation data is invalid. Clearing configuration data region and disabling ssl. Explanation: this message is for the use case where a management controller has detected invalid ssl data in the configuration data and is clearing the...

  • Page 307

    40000025-00000000 the [arg1] on system [arg2] is 75% full. Explanation: this message is for the use case where a management controller event log on a system is 75% full. May also be shown as 4000002500000000 or 0x4000002500000000 severity: info alert category: system - event log 75% full serviceable...

  • Page 308

    40000028-00000000 management controller test alert generated by [arg1]. Explanation: this message is for the use case where a user has generated a test alert. May also be shown as 4000002800000000 or 0x4000002800000000 severity: info alert category: system - other serviceable: no cim information: pr...

  • Page 309

    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 310

    4000002e-00000000 ddns registration successful. The domain name is [arg1]. Explanation: ddns registation and values 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: automatically no...

  • Page 311

    40000031-00000000 ipv6 static ip configuration enabled by user [arg1]. Explanation: ipv6 static address assignment method is enabled by user may also be shown as 4000003100000000 or 0x4000003100000000 severity: info alert category: none serviceable: no cim information: prefix: imm and id: 0049 snmp ...

  • Page 312

    40000034-00000000 ipv6 static ip configuration disabled by user [arg1]. Explanation: ipv6 static assignment method is disabled by user may also be shown as 4000003400000000 or 0x4000003400000000 severity: info alert category: none serviceable: no cim information: prefix: imm and id: 0052 snmp trap i...

  • Page 313

    40000037-00000000 enet[[arg1]] ipv6-linklocal:hstname=[arg2], ip@=[arg3] ,pref=[arg4] . Explanation: 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 trap i...

  • Page 314

    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 315

    4000003d-00000000 telnet port number changed from [arg1] to [arg2] by user [arg3]. Explanation: a user has modified 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: 0061 snmp tr...

  • Page 316

    40000040-00000000 web-https port number changed from [arg1] to [arg2] by user [arg3]. Explanation: a user has modified the web https port number may also be shown as 4000004000000000 or 0x4000004000000000 severity: info alert category: none serviceable: no cim information: prefix: imm and id: 0064 s...

  • Page 317

    40000043-00000000 snmp agent port number changed from [arg1] to [arg2] by user [arg3]. Explanation: a user has modified the snmp agent port number may also be shown as 4000004300000000 or 0x4000004300000000 severity: info alert category: none serviceable: no cim information: prefix: imm and id: 0067...

  • Page 318

    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 319

    40000049-00000000 snmp [arg1] enabled by user [arg2] . Explanation: a user enabled snmpv1 or snmpv3 or traps 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: automatically notify su...

  • Page 320

    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 321

    4000004f-00000000 date and time set by user [arg1]: date=[arg2], time-[arg3], dst auto-adjust=[arg4], timezone=[arg5]. Explanation: a user configured the date and time settings may also be shown as 4000004f00000000 or 0x4000004f00000000 severity: info alert category: none serviceable: no cim informa...

  • Page 322

    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 323

    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 324

    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: a user configures the dns servers may also be shown as 40000058...

  • Page 325

    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 326

    4000005e-00000000 ssh [arg1] by user [arg2]. Explanation: a user enables or disables ssh services 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: automatically notify support: no u...

  • Page 327

    40000061-00000000 license key for [arg1] removed by user [arg2]. Explanation: a user removes a license key may also be shown as 4000006100000000 or 0x4000006100000000 severity: info alert category: none serviceable: no cim information: prefix: imm and id: 0097 snmp trap id: automatically notify supp...

  • Page 328

    40000064-00000000 user [arg1] created. Explanation: a user account was 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: infor...

  • Page 329

    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 330

    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 331

    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 332

    40000070-00000000 snmp traps enabled by user [arg1]: enabledalerts=[arg2], allowedfilters=[arg3] . Explanation: a user enabled the snmp traps configuration may also be shown as 4000007000000000 or 0x4000007000000000 severity: info alert category: none serviceable: no cim information: prefix: imm and...

  • Page 333

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

  • Page 334

    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 335

    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 336

    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 337

    4000007f-00000000 power cap throttling occurred. Explanation: power cap throttling 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 user r...

  • Page 338

    40000082-00000000 the measured power value has returned below the power cap value. Explanation: power exceeded cap recovered may also be shown as 4000008200000000 or 0x4000008200000000 severity: info alert category: warning - power serviceable: no cim information: prefix: imm and id: 0130 snmp trap ...

  • Page 339

    40000085-00000000 fpga firmware mismatch between nodes [arg1] and [arg2]. Please attempt to flash the fpga firmware to the same level on all nodes. Explanation: a mismatch of fpga firmware has been detected between nodes may also be shown as 4000008500000000 or 0x4000008500000000 severity: error ale...

  • Page 340

    40000088-00000000 management controller [arg1]: configuration restoration from a file by user [arg2] completed. Explanation: this message is for the use case where a user restores a management controller configuration from a file and it completes. May also be shown as 4000008800000000 or 0x400000880...

  • Page 341

    2. After 45 seconds, reconnect the server to the power source and turn on the server. 3. Retry the operation. 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...

  • Page 342

    4. (trained technician only) replace the system board. (n = power supply number) 80010204-1d01ffff numeric sensor [numericsensorelementname] going low (lower critical) has asserted. (fan 1a/1b tach) explanation: this message is for the use case when an implementation has detected a lower critical se...

  • Page 343

    80010204-1d03ffff numeric sensor [numericsensorelementname] going low (lower critical) has asserted. (fan 3a/3b tach) explanation: this message is for the use case when an implementation has detected a lower critical sensor going low has asserted. May also be shown as 800102041d03ffff or 0x800102041...

  • Page 344

    2. Replace the failing fan. (n = fan number) 80010204-1d06ffff numeric sensor [numericsensorelementname] going low (lower critical) has asserted. (fan 6a/6b tach) explanation: this message is for the use case when an implementation has detected a lower critical sensor going low has asserted. May als...

  • Page 345

    80010204-1d08ffff numeric sensor [numericsensorelementname] going low (lower critical) has asserted. (fan 8a/8b tach) explanation: this message is for the use case when an implementation has detected a lower critical sensor going low has asserted. May also be shown as 800102041d08ffff or 0x800102041...

  • Page 346

    80010701-0f02ffff numeric sensor [numericsensorelementname] going high (upper non-critical) has asserted. (rear bp temp b) explanation: this message is for the use case when an implementation has detected an upper non-critical sensor going high has asserted. May also be shown as 800107010f02ffff or ...

  • Page 347

    80010701-1002ffff numeric sensor [numericsensorelementname] going high (upper non-critical) has asserted. (pci 2 amb temp) explanation: this message is for the use case when an implementation has detected an upper non-critical sensor going high has asserted. May also be shown as 800107011002ffff or ...

  • Page 348

    80010701-1301ffff numeric sensor [numericsensorelementname] going high (upper non-critical) has asserted. (psu 1 amb temp) explanation: this message is for the use case when an implementation has detected an upper non-critical sensor going high has asserted. May also be shown as 800107011301ffff or ...

  • Page 349

    2. Check the server airflow. Make sure that nothing is blocking the air from coming into or preventing the air from exiting the server. 80010701-1403ffff numeric sensor [numericsensorelementname] going high (upper non-critical) has asserted. (dimm ab vr temp) explanation: this message is for the use...

  • Page 350

    80010701-1405ffff numeric sensor [numericsensorelementname] going high (upper non-critical) has asserted. (dimm ef vr temp) explanation: this message is for the use case when an implementation has detected an upper non-critical sensor going high has asserted. May also be shown as 800107011405ffff or...

  • Page 351

    80010701-2d01ffff numeric sensor [numericsensorelementname] going high (upper non-critical) has asserted. (pch temp) explanation: this message is for the use case when an implementation has detected an upper non-critical sensor going high has asserted. May also be shown as 800107012d01ffff or 0x8001...

  • Page 352

    80010901-0f01ffff numeric sensor [numericsensorelementname] going high (upper critical) has asserted. (rear bp temp a) explanation: this message is for the use case when an implementation has detected an upper critical sensor going high has asserted. May also be shown as 800109010f01ffff or 0x800109...

  • Page 353

    80010901-1001ffff numeric sensor [numericsensorelementname] going high (upper critical) has asserted. (pci 1 amb temp) explanation: this message is for the use case when an implementation has detected an upper critical sensor going high has asserted. May also be shown as 800109011001ffff or 0x800109...

  • Page 354

    80010901-1003ffff numeric sensor [numericsensorelementname] going high (upper critical) has asserted. (pci 3 amb temp) explanation: this message is for the use case when an implementation has detected an upper critical sensor going high has asserted. May also be shown as 800109011003ffff or 0x800109...

  • Page 355

    80010901-1401ffff numeric sensor [numericsensorelementname] going high (upper critical) has asserted. (cpu1 vr temp) explanation: this message is for the use case when an implementation has detected an upper critical sensor going high has asserted. May also be shown as 800109011401ffff or 0x80010901...

  • Page 356

    80010901-1403ffff numeric sensor [numericsensorelementname] going high (upper critical) has asserted. (dimm ab vr temp) explanation: this message is for the use case when an implementation has detected an upper critical sensor going high has asserted. May also be shown as 800109011403ffff or 0x80010...

  • Page 357

    80010901-1405ffff numeric sensor [numericsensorelementname] going high (upper critical) has asserted. (dimm ef vr temp) explanation: this message is for the use case when an implementation has detected an upper critical sensor going high has asserted. May also be shown as 800109011405ffff or 0x80010...

  • Page 358

    80010901-2d01ffff numeric sensor [numericsensorelementname] going high (upper critical) has asserted. (pch temp) explanation: this message is for the use case when an implementation has detected an upper critical sensor going high has asserted. May also be shown as 800109012d01ffff or 0x800109012d01...

  • Page 359

    80010902-0701ffff numeric sensor [numericsensorelementname] going high (upper critical) has asserted. Explanation: this message is for the use case when an implementation has detected an upper critical sensor going high has asserted. May also be shown as 800109020701ffff or 0x800109020701ffff severi...

  • Page 360

    80010b01-0f02ffff numeric sensor [numericsensorelementname] going high (upper non-recoverable) has asserted. (rear bp temp b) explanation: this message is for the use case when an implementation has detected an upper non-recoverable sensor going high has asserted. May also be shown as 80010b010f02ff...

  • Page 361

    80010b01-1003ffff numeric sensor [numericsensorelementname] going high (upper non-recoverable) has asserted. (pci 3 amb temp) explanation: this message is for the use case when an implementation has detected an upper non-recoverable sensor going high has asserted. May also be shown as 80010b011003ff...

  • Page 362

    80010b01-1402ffff numeric sensor [numericsensorelementname] going high (upper non-recoverable) has asserted. (cpu2 vr temp) explanation: this message is for the use case when an implementation has detected an upper non-recoverable sensor going high has asserted. May also be shown as 80010b011402ffff...

  • Page 363

    80010b01-1405ffff numeric sensor [numericsensorelementname] going high (upper non-recoverable) has asserted. (dimm ef vr temp) explanation: this message is for the use case when an implementation has detected an upper non-recoverable sensor going high has asserted. May also be shown as 80010b011405f...

  • Page 364

    80010b01-3701ffff numeric sensor [numericsensorelementname] going high (upper non-recoverable) has asserted. (ambient temp) explanation: this message is for the use case when an implementation has detected an upper non-recoverable sensor going high has asserted. May also be shown as 80010b013701ffff...

  • Page 365

    80030108-1301ffff sensor [sensorelementname] has asserted. (ps heavy load) explanation: this message is for the use case when an implementation has detected a sensor has asserted. May also be shown as 800301081301ffff or 0x800301081301ffff severity: info alert category: system - other serviceable: n...

  • Page 366

    80030112-0601ffff sensor [sensorelementname] has asserted. (smm mode) explanation: this message is for the use case when an implementation has detected a sensor has asserted. May also be shown as 800301120601ffff or 0x800301120601ffff severity: info alert category: system - other serviceable: no cim...

  • Page 367

    80070101-2c01ffff sensor [sensorelementname] has transitioned from normal to non-critical state. (ml2 overtemp) 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 800701012c01ffff or 0x800701012c01...

  • Page 368

    8007010f-2582ffff sensor [sensorelementname] has transitioned from normal to non-critical state. (i/o resources) 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 8007010f2582ffff or 0x8007010f258...

  • Page 369

    80070128-2e01ffff sensor [sensorelementname] has transitioned from normal to non-critical state. (me recovery) 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 800701282e01ffff or 0x800701282e01f...

  • Page 370

    80070201-0302ffff sensor [sensorelementname] has transitioned to critical from a less severe state. (cpu 2 overtemp) 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 800702010302ffff or 0x800702...

  • Page 371

    80070204-0a01ffff sensor [sensorelementname] has transitioned to critical from a less severe state. (ps 1 fan fault) 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 800702040a01ffff or 0x800702...

  • Page 372

    2. Use the ibm power configurator utility to ensure current system power consumption is under limitation. For more information and to download the utility, go to http://www-03.Ibm.Com/systems/bladecenter/resources/ powerconfig.Html. 3. Replace power supply n. (n = power supply number) 80070208-0a02f...

  • Page 373

    8007020f-2201ffff sensor [sensorelementname] has transitioned to critical from a less severe state. (txt acm module) 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 8007020f2201ffff or 0x800702...

  • Page 374

    2. If the problem persists, (trained technician only) replace the system board (see removing the system board and installing the system board). 80070219-0701ffff sensor [sensorelementname] has transitioned to critical from a less severe state. (sysbrd fault) explanation: this message is for the use ...

  • Page 375

    8007021b-0302ffff sensor [sensorelementname] has transitioned to critical from a less severe state. (cpu 2 qpilinkerr) 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 8007021b0302ffff or 0x8007...

  • Page 376

    80070301-0301ffff sensor [sensorelementname] has transitioned to non-recoverable from a less severe state. (cpu 1 overtemp) explanation: this message is for the use case when an implementation has detected a sensor transitioned to non-recoverable from less severe. May also be shown as 800703010301ff...

  • Page 377

    80070301-2c01ffff sensor [sensorelementname] has transitioned to non-recoverable from a less severe state. (ml2 overtemp) explanation: this message is for the use case when an implementation has detected a sensor transitioned to non-recoverable from less severe. May also be shown as 800703012c01ffff...

  • Page 378

    2. Remove the failing power supply. 3. (trained technician only) replace the system board. (n = power supply number) if the specified sensor is ps n 12v uv fault, complete the following steps until the problem is solved: 1. Check power supply n led. 2. Remove the failing power supply. 3. Follow acti...

  • Page 379

    80070614-2201ffff sensor [sensorelementname] has transitioned to non-recoverable. (tpm phy pres set) explanation: this message is for the use case when an implementation has detected a sensor transitioned to non-recoverable. May also be shown as 800706142201ffff or 0x800706142201ffff severity: error...

  • Page 380

    800b0008-1301ffff redundancy [redundancysetelementname] has been restored. (power unit) explanation: this message is for the use case when an implementation has detected redundancy was restored. May also be shown as 800b00081301ffff or 0x800b00081301ffff severity: info alert category: warning - redu...

  • Page 381

    800b010a-1e82ffff redundancy lost for [redundancysetelementname] has asserted. (fan zone 2) explanation: this message is for the use case when redundancy lost has asserted. May also be shown as 800b010a1e82ffff or 0x800b010a1e82ffff severity: error alert category: critical - fan failure serviceable:...

  • Page 382

    2. Replace the power supply with higher rated power. 800b030c-2581ffff non-redundant:sufficient resources from redundancy degraded or fully redundant for [redundancysetelementname] has asserted. (backup memory) explanation: this message is for the use case when a redundancy set has transitioned from...

  • Page 383

    800b050a-1e81ffff non-redundant:insufficient resources for [redundancysetelementname] has asserted. (fan zone 1) explanation: this message is for the use case when a redundancy set has transitioned to non- redundant:insufficient resources. May also be shown as 800b050a1e81ffff or 0x800b050a1e81ffff ...

  • Page 384

    800b050c-2581ffff non-redundant:insufficient resources for [redundancysetelementname] has asserted. (backup memory) explanation: this message is for the use case when a redundancy set has transitioned to non- redundant:insufficient resources. May also be shown as 800b050c2581ffff or 0x800b050c2581ff...

  • Page 385

    806f0007-0302ffff [processorelementname] has failed with ierr. (cpu 2) explanation: this message is for the use case when an implementation has detected a processor failed - ierr condition. May also be shown as 806f00070302ffff or 0x806f00070302ffff severity: error alert category: critical - cpu ser...

  • Page 386

    806f0008-0a02ffff [powersupplyelementname] has been added to container [physicalpackageelementname]. (power supply 2) explanation: this message is for the use case when an implementation has detected a power supply has been added. May also be shown as 806f00080a02ffff or 0x806f00080a02ffff severity:...

  • Page 387

    806f000d-0401ffff the drive [storagevolumeelementname] has been added. (drive 1) explanation: this message is for the use case when an implementation has detected a drive has been added. May also be shown as 806f000d0401ffff or 0x806f000d0401ffff severity: info alert category: critical - hard disk d...

  • Page 388

    806f000d-0404ffff the drive [storagevolumeelementname] has been added. (drive 4) explanation: this message is for the use case when an implementation has detected a drive has been added. May also be shown as 806f000d0404ffff or 0x806f000d0404ffff severity: info alert category: critical - hard disk d...

  • Page 389

    806f000d-0407ffff the drive [storagevolumeelementname] has been added. (drive 7) explanation: this message is for the use case when an implementation has detected a drive has been added. May also be shown as 806f000d0407ffff or 0x806f000d0407ffff severity: info alert category: critical - hard disk d...

  • Page 390

    806f000d-040affff the drive [storagevolumeelementname] has been added. (drive 10) explanation: this message is for the use case when an implementation has detected a drive has been added. May also be shown as 806f000d040affff or 0x806f000d040affff severity: info alert category: critical - hard disk ...

  • Page 391

    806f000d-040dffff the drive [storagevolumeelementname] has been added. (drive 13) explanation: this message is for the use case when an implementation has detected a drive has been added. May also be shown as 806f000d040dffff or 0x806f000d040dffff severity: info alert category: critical - hard disk ...

  • Page 392

    806f000f-220102ff subsystem [memoryelementname] has insufficient memory for operation. (abr status) explanation: this message is for the use case when an implementation has detected that the usable memory is insufficient for operation. May also be shown as 806f000f220102ff or 0x806f000f220102ff seve...

  • Page 393

    806f000f-220104ff the system [computersystemelementname]has encountered a motherboard failure. (abr status) explanation: this message is for the use case when an implementation has detected that a fatal motherboard failure in the system. May also be shown as 806f000f220104ff or 0x806f000f220104ff se...

  • Page 394

    806f000f-22010bff firmware bios (rom) corruption was detected on system [computersystemelementname] during post. (abr status) explanation: firmware bios (rom) corruption was detected on the system during post. May also be shown as 806f000f22010bff or 0x806f000f22010bff severity: info alert category:...

  • Page 395

    806f000f-2201ffff the system [computersystemelementname] encountered a post error. (abr status) explanation: this message is for the use case when an implementation has detected a post error. May also be shown as 806f000f2201ffff or 0x806f000f2201ffff severity: error alert category: critical - other...

  • Page 396

    806f0021-2201ffff fault in slot [physicalconnectorsystemelementname] on system [computersystemelementname]. (no op rom space) explanation: this message is for the use case when an implementation has detected a fault in a slot. May also be shown as 806f00212201ffff or 0x806f00212201ffff severity: err...

  • Page 397

    806f0021-2c01ffff fault in slot [physicalconnectorsystemelementname] on system [computersystemelementname]. (ml2 card fault) explanation: this message is for the use case when an implementation has detected a fault in a slot. May also be shown as 806f00212c01ffff or 0x806f00212c01ffff severity: erro...

  • Page 398

    806f0021-3002ffff fault in slot [physicalconnectorsystemelementname] on system [computersystemelementname]. (pci 2) explanation: this message is for the use case when an implementation has detected a fault in a slot. May also be shown as 806f00213002ffff or 0x806f00213002ffff severity: error alert c...

  • Page 399

    806f0023-2101ffff watchdog timer expired for [watchdogelementname]. (ipmi watchdog) explanation: this message is for the use case when an implementation has detected a watchdog timer expired. May also be shown as 806f00232101ffff or 0x806f00232101ffff severity: info alert category: system - other se...

  • Page 400

    806f0107-0302ffff an over-temperature condition has been detected on [processorelementname]. (cpu 2) explanation: this message is for the use case when an implementation has detected an over-temperature condition detected for processor. May also be shown as 806f01070302ffff or 0x806f01070302ffff sev...

  • Page 401

    806f0108-0a02ffff [powersupplyelementname] has failed. (power supply 2) explanation: this message is for the use case when an implementation has detected a power supply has failed. May also be shown as 806f01080a02ffff or 0x806f01080a02ffff severity: error alert category: critical - power serviceabl...

  • Page 402

    5. (trained technician only) if the problem occurs on the same dimm connector, check the dimm connector. If the connector contains any foreign material or is damaged, replace the system board. 6. (trained technician only) remove the affected microprocessor and check the microprocessor socket pins fo...

  • Page 403

    806f010c-2003ffff uncorrectable error detected for [physicalmemoryelementname] on subsystem [memoryelementname]. (dimm 3) explanation: this message is for the use case when an implementation has detected a memory uncorrectable error. May also be shown as 806f010c2003ffff or 0x806f010c2003ffff severi...

  • Page 404

    7. (trained technician only) replace the affected microprocessor. 8. Manually re-enable all affected dimms if the server firmware version is older than uefi v1.10. If the server firmware version is uefi v1.10 or newer, disconnect and reconnect the server to the power source and restart the server. 9...

  • Page 405

    3. Swap the affected dimms (as indicated by the error leds on the system board or the event logs) to a different memory channel or microprocessor. 4. If the problem follows the dimm, replace the failing dimm. 5. (trained technician only) if the problem occurs on the same dimm connector, check the di...

  • Page 406

    806f010c-2008ffff uncorrectable error detected for [physicalmemoryelementname] on subsystem [memoryelementname]. (dimm 8) explanation: this message is for the use case when an implementation has detected a memory uncorrectable error. May also be shown as 806f010c2008ffff or 0x806f010c2008ffff severi...

  • Page 407

    7. (trained technician only) replace the affected microprocessor. 8. Manually re-enable all affected dimms if the server firmware version is older than uefi v1.10. If the server firmware version is uefi v1.10 or newer, disconnect and reconnect the server to the power source and restart the server. 9...

  • Page 408

    3. Swap the affected dimms (as indicated by the error leds on the system board or the event logs) to a different memory channel or microprocessor. 4. If the problem follows the dimm, replace the failing dimm. 5. (trained technician only) if the problem occurs on the same dimm connector, check the di...

  • Page 409

    806f010c-200dffff uncorrectable error detected for [physicalmemoryelementname] on subsystem [memoryelementname]. (dimm 13) explanation: this message is for the use case when an implementation has detected a memory uncorrectable error. May also be shown as 806f010c200dffff or 0x806f010c200dffff sever...

  • Page 410

    7. (trained technician only) replace the affected microprocessor. 8. Manually re-enable all affected dimms if the server firmware version is older than uefi v1.10. If the server firmware version is uefi v1.10 or newer, disconnect and reconnect the server to the power source and restart the server. 9...

  • Page 411

    3. Swap the affected dimms (as indicated by the error leds on the system board or the event logs) to a different memory channel or microprocessor. 4. If the problem follows the dimm, replace the failing dimm. 5. (trained technician only) if the problem occurs on the same dimm connector, check the di...

  • Page 412

    806f010c-2012ffff uncorrectable error detected for [physicalmemoryelementname] on subsystem [memoryelementname]. (dimm 18) explanation: this message is for the use case when an implementation has detected a memory uncorrectable error. May also be shown as 806f010c2012ffff or 0x806f010c2012ffff sever...

  • Page 413

    7. (trained technician only) replace the affected microprocessor. 8. Manually re-enable all affected dimms if the server firmware version is older than uefi v1.10. If the server firmware version is uefi v1.10 or newer, disconnect and reconnect the server to the power source and restart the server. 9...

  • Page 414

    3. Swap the affected dimms (as indicated by the error leds on the system board or the event logs) to a different memory channel or microprocessor. 4. If the problem follows the dimm, replace the failing dimm. 5. (trained technician only) if the problem occurs on the same dimm connector, check the di...

  • Page 415

    806f010c-2017ffff uncorrectable error detected for [physicalmemoryelementname] on subsystem [memoryelementname]. (dimm 23) explanation: this message is for the use case when an implementation has detected a memory uncorrectable error. May also be shown as 806f010c2017ffff or 0x806f010c2017ffff sever...

  • Page 416

    6. (trained technician only) remove the affected microprocessor and check the microprocessor socket pins for any damaged pins. If a damage is found, replace the system board. 7. (trained technician only) replace the affected microprocessor. 8. Manually re-enable all affected dimms if the server firm...

  • Page 417

    806f010d-0400ffff the drive [storagevolumeelementname] has been disabled due to a detected fault. (drive 0) explanation: this message is for the use case when an implementation has detected a drive was disabled due to fault. May also be shown as 806f010d0400ffff or 0x806f010d0400ffff severity: error...

  • Page 418

    806f010d-0402ffff the drive [storagevolumeelementname] has been disabled due to a detected fault. (drive 2) explanation: this message is for the use case when an implementation has detected a drive was disabled due to fault. May also be shown as 806f010d0402ffff or 0x806f010d0402ffff severity: error...

  • Page 419

    806f010d-0404ffff the drive [storagevolumeelementname] has been disabled due to a detected fault. (drive 4) explanation: this message is for the use case when an implementation has detected a drive was disabled due to fault. May also be shown as 806f010d0404ffff or 0x806f010d0404ffff severity: error...

  • Page 420

    806f010d-0406ffff the drive [storagevolumeelementname] has been disabled due to a detected fault. (drive 6) explanation: this message is for the use case when an implementation has detected a drive was disabled due to fault. May also be shown as 806f010d0406ffff or 0x806f010d0406ffff severity: error...

  • Page 421

    806f010d-0408ffff the drive [storagevolumeelementname] has been disabled due to a detected fault. (drive 8) explanation: this message is for the use case when an implementation has detected a drive was disabled due to fault. May also be shown as 806f010d0408ffff or 0x806f010d0408ffff severity: error...

  • Page 422

    806f010d-040affff the drive [storagevolumeelementname] has been disabled due to a detected fault. (drive 10) explanation: this message is for the use case when an implementation has detected a drive was disabled due to fault. May also be shown as 806f010d040affff or 0x806f010d040affff severity: erro...

  • Page 423

    806f010d-040cffff the drive [storagevolumeelementname] has been disabled due to a detected fault. (drive 12) explanation: this message is for the use case when an implementation has detected a drive was disabled due to fault. May also be shown as 806f010d040cffff or 0x806f010d040cffff severity: erro...

  • Page 424

    806f010f-2201ffff the system [computersystemelementname] encountered a firmware hang. (firmware error) explanation: this message is for the use case when an implementation has detected a system firmware hang. May also be shown as 806f010f2201ffff or 0x806f010f2201ffff severity: error alert category:...

  • Page 425

    806f011b-0701ffff the connector [physicalconnectorelementname] has encountered a configuration error. (front usb) explanation: this message is for the use case when an implementation has detected an interconnect configuration error. May also be shown as 806f011b0701ffff or 0x806f011b0701ffff severit...

  • Page 426

    806f0123-2101ffff reboot of system [computersystemelementname] initiated by [watchdogelementname]. (ipmi watchdog) explanation: this message is for the use case when an implementation has detected a reboot by a watchdog occurred. May also be shown as 806f01232101ffff or 0x806f01232101ffff severity: ...

  • Page 427

    806f0125-1002ffff [managedelementname] detected as absent. (pci riser 2) explanation: this message is for the use case when an implementation has detected a managed element is absent. May also be shown as 806f01251002ffff or 0x806f01251002ffff severity: info alert category: system - other serviceabl...

  • Page 428

    806f0207-0302ffff [processorelementname] has failed with frb1/bist condition. (cpu 2) explanation: this message is for the use case when an implementation has detected a processor failed - frb1/bist condition. May also be shown as 806f02070302ffff or 0x806f02070302ffff severity: error alert category...

  • Page 429

    806f020d-0400ffff failure predicted on drive [storagevolumeelementname] for array [computersystemelementname]. (drive 0) explanation: this message is for the use case when an implementation has detected an array failure is predicted. May also be shown as 806f020d0400ffff or 0x806f020d0400ffff severi...

  • Page 430

    806f020d-0402ffff failure predicted on drive [storagevolumeelementname] for array [computersystemelementname]. (drive 2) explanation: this message is for the use case when an implementation has detected an array failure is predicted. May also be shown as 806f020d0402ffff or 0x806f020d0402ffff severi...

  • Page 431

    806f020d-0404ffff failure predicted on drive [storagevolumeelementname] for array [computersystemelementname]. (drive 4) explanation: this message is for the use case when an implementation has detected an array failure is predicted. May also be shown as 806f020d0404ffff or 0x806f020d0404ffff severi...

  • Page 432

    806f020d-0406ffff failure predicted on drive [storagevolumeelementname] for array [computersystemelementname]. (drive 6) explanation: this message is for the use case when an implementation has detected an array failure is predicted. May also be shown as 806f020d0406ffff or 0x806f020d0406ffff severi...

  • Page 433

    806f020d-0408ffff failure predicted on drive [storagevolumeelementname] for array [computersystemelementname]. (drive 8) explanation: this message is for the use case when an implementation has detected an array failure is predicted. May also be shown as 806f020d0408ffff or 0x806f020d0408ffff severi...

  • Page 434

    806f020d-040affff failure predicted on drive [storagevolumeelementname] for array [computersystemelementname]. (drive 10) explanation: this message is for the use case when an implementation has detected an array failure is predicted. May also be shown as 806f020d040affff or 0x806f020d040affff sever...

  • Page 435

    806f020d-040cffff failure predicted on drive [storagevolumeelementname] for array [computersystemelementname]. (drive 12) explanation: this message is for the use case when an implementation has detected an array failure is predicted. May also be shown as 806f020d040cffff or 0x806f020d040cffff sever...

  • Page 436

    806f0223-2101ffff powering off system [computersystemelementname] initiated by [watchdogelementname]. (ipmi watchdog) explanation: this message is for the use case when an implementation has detected a poweroff by watchdog has occurred. May also be shown as 806f02232101ffff or 0x806f02232101ffff sev...

  • Page 437

    806f030c-2001ffff scrub failure for [physicalmemoryelementname] on subsystem [memoryelementname]. (dimm 1) explanation: this message is for the use case when an implementation has detected a memory scrub failure. May also be shown as 806f030c2001ffff or 0x806f030c2001ffff severity: error alert categ...

  • Page 438

    6. (trained technician only) if the problem occurs on the same dimm connector, check the dimm connector. If the connector contains any foreign material or is damaged, replace the system board. 7. (trained service technician only) remove the affected microprocessor and check the microprocessor socket...

  • Page 439

    3. Make sure that the dimms are firmly seated and no foreign material is found in the dimm connector. Then, retry with the same dimm. 4. If the problem is related to a dimm, replace the failing dimm indicated by the error leds. 5. If the problem occurs on the same dimm connector, swap the affected d...

  • Page 440

    806f030c-2006ffff scrub failure for [physicalmemoryelementname] on subsystem [memoryelementname]. (dimm 6) explanation: this message is for the use case when an implementation has detected a memory scrub failure. May also be shown as 806f030c2006ffff or 0x806f030c2006ffff severity: error alert categ...

  • Page 441

    6. (trained technician only) if the problem occurs on the same dimm connector, check the dimm connector. If the connector contains any foreign material or is damaged, replace the system board. 7. (trained service technician only) remove the affected microprocessor and check the microprocessor socket...

  • Page 442

    3. Make sure that the dimms are firmly seated and no foreign material is found in the dimm connector. Then, retry with the same dimm. 4. If the problem is related to a dimm, replace the failing dimm indicated by the error leds. 5. If the problem occurs on the same dimm connector, swap the affected d...

  • Page 443

    806f030c-200bffff scrub failure for [physicalmemoryelementname] on subsystem [memoryelementname]. (dimm 11) explanation: this message is for the use case when an implementation has detected a memory scrub failure. May also be shown as 806f030c200bffff or 0x806f030c200bffff severity: error alert cate...

  • Page 444

    6. (trained technician only) if the problem occurs on the same dimm connector, check the dimm connector. If the connector contains any foreign material or is damaged, replace the system board. 7. (trained service technician only) remove the affected microprocessor and check the microprocessor socket...

  • Page 445

    3. Make sure that the dimms are firmly seated and no foreign material is found in the dimm connector. Then, retry with the same dimm. 4. If the problem is related to a dimm, replace the failing dimm indicated by the error leds. 5. If the problem occurs on the same dimm connector, swap the affected d...

  • Page 446

    806f030c-2010ffff scrub failure for [physicalmemoryelementname] on subsystem [memoryelementname]. (dimm 16) explanation: this message is for the use case when an implementation has detected a memory scrub failure. May also be shown as 806f030c2010ffff or 0x806f030c2010ffff severity: error alert cate...

  • Page 447

    6. (trained technician only) if the problem occurs on the same dimm connector, check the dimm connector. If the connector contains any foreign material or is damaged, replace the system board. 7. (trained service technician only) remove the affected microprocessor and check the microprocessor socket...

  • Page 448

    3. Make sure that the dimms are firmly seated and no foreign material is found in the dimm connector. Then, retry with the same dimm. 4. If the problem is related to a dimm, replace the failing dimm indicated by the error leds. 5. If the problem occurs on the same dimm connector, swap the affected d...

  • Page 449

    806f030c-2015ffff scrub failure for [physicalmemoryelementname] on subsystem [memoryelementname]. (dimm 21) explanation: this message is for the use case when an implementation has detected a memory scrub failure. May also be shown as 806f030c2015ffff or 0x806f030c2015ffff severity: error alert cate...

  • Page 450

    6. (trained technician only) if the problem occurs on the same dimm connector, check the dimm connector. If the connector contains any foreign material or is damaged, replace the system board. 7. (trained service technician only) remove the affected microprocessor and check the microprocessor socket...

  • Page 451

    3. Make sure that the dimms are firmly seated and no foreign material is found in the dimm connector. Then, retry with the same dimm. 4. If the problem is related to a dimm, replace the failing dimm indicated by the error leds. 5. If the problem occurs on the same dimm connector, swap the affected d...

  • Page 452

    806f030d-0400ffff hot spare enabled for [computersystemelementname]. (drive 0) 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 ser...

  • Page 453

    806f030d-0403ffff hot spare enabled for [computersystemelementname]. (drive 3) 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 ser...

  • Page 454

    806f030d-0406ffff hot spare enabled for [computersystemelementname]. (drive 6) 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 ser...

  • Page 455

    806f030d-0409ffff hot spare enabled for [computersystemelementname]. (drive 9) 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 ser...

  • Page 456

    806f030d-040cffff hot spare enabled for [computersystemelementname]. (drive 12) 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 se...

  • Page 457

    806f0323-2101ffff power cycle of system [computersystemelementname] initiated by watchdog [watchdogelementname]. (ipmi watchdog) explanation: this message is for the use case when an implementation has detected a power cycle by watchdog occurred. May also be shown as 806f03232101ffff or 0x806f032321...

  • Page 458

    806f040c-2002ffff [physicalmemoryelementname] disabled on subsystem [memoryelementname]. (dimm 2) explanation: this message is for the use case when an implementation has detected that memory has been disabled. May also be shown as 806f040c2002ffff or 0x806f040c2002ffff severity: info alert category...

  • Page 459

    806f040c-2004ffff [physicalmemoryelementname] disabled on subsystem [memoryelementname]. (dimm 4) explanation: this message is for the use case when an implementation has detected that memory has been disabled. May also be shown as 806f040c2004ffff or 0x806f040c2004ffff severity: info alert category...

  • Page 460

    806f040c-2006ffff [physicalmemoryelementname] disabled on subsystem [memoryelementname]. (dimm 6) explanation: this message is for the use case when an implementation has detected that memory has been disabled. May also be shown as 806f040c2006ffff or 0x806f040c2006ffff severity: info alert category...

  • Page 461

    806f040c-2008ffff [physicalmemoryelementname] disabled on subsystem [memoryelementname]. (dimm 8) explanation: this message is for the use case when an implementation has detected that memory has been disabled. May also be shown as 806f040c2008ffff or 0x806f040c2008ffff severity: info alert category...

  • Page 462

    806f040c-200affff [physicalmemoryelementname] disabled on subsystem [memoryelementname]. (dimm 10) explanation: this message is for the use case when an implementation has detected that memory has been disabled. May also be shown as 806f040c200affff or 0x806f040c200affff severity: info alert categor...

  • Page 463

    806f040c-200cffff [physicalmemoryelementname] disabled on subsystem [memoryelementname]. (dimm 12) explanation: this message is for the use case when an implementation has detected that memory has been disabled. May also be shown as 806f040c200cffff or 0x806f040c200cffff severity: info alert categor...

  • Page 464

    806f040c-200effff [physicalmemoryelementname] disabled on subsystem [memoryelementname]. (dimm 14) explanation: this message is for the use case when an implementation has detected that memory has been disabled. May also be shown as 806f040c200effff or 0x806f040c200effff severity: info alert categor...

  • Page 465

    806f040c-2010ffff [physicalmemoryelementname] disabled on subsystem [memoryelementname]. (dimm 16) explanation: this message is for the use case when an implementation has detected that memory has been disabled. May also be shown as 806f040c2010ffff or 0x806f040c2010ffff severity: info alert categor...

  • Page 466

    806f040c-2012ffff [physicalmemoryelementname] disabled on subsystem [memoryelementname]. (dimm 18) explanation: this message is for the use case when an implementation has detected that memory has been disabled. May also be shown as 806f040c2012ffff or 0x806f040c2012ffff severity: info alert categor...

  • Page 467

    806f040c-2014ffff [physicalmemoryelementname] disabled on subsystem [memoryelementname]. (dimm 20) explanation: this message is for the use case when an implementation has detected that memory has been disabled. May also be shown as 806f040c2014ffff or 0x806f040c2014ffff severity: info alert categor...

  • Page 468

    806f040c-2016ffff [physicalmemoryelementname] disabled on subsystem [memoryelementname]. (dimm 22) explanation: this message is for the use case when an implementation has detected that memory has been disabled. May also be shown as 806f040c2016ffff or 0x806f040c2016ffff severity: info alert categor...

  • Page 469

    806f040c-2018ffff [physicalmemoryelementname] disabled on subsystem [memoryelementname]. (dimm 24) explanation: this message is for the use case when an implementation has detected that memory has been disabled. May also be shown as 806f040c2018ffff or 0x806f040c2018ffff severity: info alert categor...

  • Page 470

    806f0413-2582ffff a pci perr has occurred on system [computersystemelementname]. (pcis) explanation: this message is for the use case when an implementation has detected a pci perr. May also be shown as 806f04132582ffff or 0x806f04132582ffff severity: error alert category: critical - other serviceab...

  • Page 471

    806f0507-0302ffff [processorelementname] has a configuration mismatch. (cpu 2) explanation: this message is for the use case when an implementation has detected a processor configuration mismatch has occurred. May also be shown as 806f05070302ffff or 0x806f05070302ffff severity: error alert category...

  • Page 472

    806f050c-2001ffff memory logging limit reached for [physicalmemoryelementname] on subsystem [memoryelementname]. (dimm 1) explanation: this message is for the use case when an implementation has detected that the memory logging limit has been reached. May also be shown as 806f050c2001ffff or 0x806f0...

  • Page 473

    806f050c-2003ffff memory logging limit reached for [physicalmemoryelementname] on subsystem [memoryelementname]. (dimm 3) explanation: this message is for the use case when an implementation has detected that the memory logging limit has been reached. May also be shown as 806f050c2003ffff or 0x806f0...

  • Page 474

    806f050c-2005ffff memory logging limit reached for [physicalmemoryelementname] on subsystem [memoryelementname]. (dimm 5) explanation: this message is for the use case when an implementation has detected that the memory logging limit has been reached. May also be shown as 806f050c2005ffff or 0x806f0...

  • Page 475

    806f050c-2007ffff memory logging limit reached for [physicalmemoryelementname] on subsystem [memoryelementname]. (dimm 7) explanation: this message is for the use case when an implementation has detected that the memory logging limit has been reached. May also be shown as 806f050c2007ffff or 0x806f0...

  • Page 476

    806f050c-2009ffff memory logging limit reached for [physicalmemoryelementname] on subsystem [memoryelementname]. (dimm 9) explanation: this message is for the use case when an implementation has detected that the memory logging limit has been reached. May also be shown as 806f050c2009ffff or 0x806f0...

  • Page 477

    806f050c-200bffff memory logging limit reached for [physicalmemoryelementname] on subsystem [memoryelementname]. (dimm 11) explanation: this message is for the use case when an implementation has detected that the memory logging limit has been reached. May also be shown as 806f050c200bffff or 0x806f...

  • Page 478

    806f050c-200dffff memory logging limit reached for [physicalmemoryelementname] on subsystem [memoryelementname]. (dimm 13) explanation: this message is for the use case when an implementation has detected that the memory logging limit has been reached. May also be shown as 806f050c200dffff or 0x806f...

  • Page 479

    806f050c-200fffff memory logging limit reached for [physicalmemoryelementname] on subsystem [memoryelementname]. (dimm 15) explanation: this message is for the use case when an implementation has detected that the memory logging limit has been reached. May also be shown as 806f050c200fffff or 0x806f...

  • Page 480

    806f050c-2011ffff memory logging limit reached for [physicalmemoryelementname] on subsystem [memoryelementname]. (dimm 17) explanation: this message is for the use case when an implementation has detected that the memory logging limit has been reached. May also be shown as 806f050c2011ffff or 0x806f...

  • Page 481

    806f050c-2013ffff memory logging limit reached for [physicalmemoryelementname] on subsystem [memoryelementname]. (dimm 19) explanation: this message is for the use case when an implementation has detected that the memory logging limit has been reached. May also be shown as 806f050c2013ffff or 0x806f...

  • Page 482

    806f050c-2015ffff memory logging limit reached for [physicalmemoryelementname] on subsystem [memoryelementname]. (dimm 21) explanation: this message is for the use case when an implementation has detected that the memory logging limit has been reached. May also be shown as 806f050c2015ffff or 0x806f...

  • Page 483

    806f050c-2017ffff memory logging limit reached for [physicalmemoryelementname] on subsystem [memoryelementname]. (dimm 23) explanation: this message is for the use case when an implementation has detected that the memory logging limit has been reached. May also be shown as 806f050c2017ffff or 0x806f...

  • Page 484

    806f050c-2581ffff memory logging limit reached for [physicalmemoryelementname] on subsystem [memoryelementname]. (all dimms) explanation: this message is for the use case when an implementation has detected that the memory logging limit has been reached. May also be shown as 806f050c2581ffff or 0x80...

  • Page 485

    806f050d-0401ffff array [computersystemelementname] is in critical condition. (drive 1) explanation: this message is for the use case when an implementation has detected that an array is critical. May also be shown as 806f050d0401ffff or 0x806f050d0401ffff severity: error alert category: critical - ...

  • Page 486

    806f050d-0403ffff array [computersystemelementname] is in critical condition. (drive 3) explanation: this message is for the use case when an implementation has detected that an array is critical. May also be shown as 806f050d0403ffff or 0x806f050d0403ffff severity: error alert category: critical - ...

  • Page 487

    806f050d-0405ffff array [computersystemelementname] is in critical condition. (drive 5) explanation: this message is for the use case when an implementation has detected that an array is critical. May also be shown as 806f050d0405ffff or 0x806f050d0405ffff severity: error alert category: critical - ...

  • Page 488

    806f050d-0407ffff array [computersystemelementname] is in critical condition. (drive 7) explanation: this message is for the use case when an implementation has detected that an array is critical. May also be shown as 806f050d0407ffff or 0x806f050d0407ffff severity: error alert category: critical - ...

  • Page 489

    806f050d-0409ffff array [computersystemelementname] is in critical condition. (drive 9) explanation: this message is for the use case when an implementation has detected that an array is critical. May also be shown as 806f050d0409ffff or 0x806f050d0409ffff severity: error alert category: critical - ...

  • Page 490

    806f050d-040bffff array [computersystemelementname] is in critical condition. (drive 11) explanation: this message is for the use case when an implementation has detected that an array is critical. May also be shown as 806f050d040bffff or 0x806f050d040bffff severity: error alert category: critical -...

  • Page 491

    806f050d-040dffff array [computersystemelementname] is in critical condition. (drive 13) explanation: this message is for the use case when an implementation has detected that an array is critical. May also be shown as 806f050d040dffff or 0x806f050d040dffff severity: error alert category: critical -...

  • Page 492

    806f052b-2101ffff invalid or unsupported firmware or software was detected on system [computersystemelementname]. (imm2 fw failover) explanation: this message is for the use case when an implementation has detected an invalid/unsupported firmware/software version. May also be shown as 806f052b2101ff...

  • Page 493

    806f0607-0302ffff an sm bios uncorrectable cpu complex error for [processorelementname] has asserted. (cpu 2) explanation: this message is for the use case when an sm bios uncorrectable cpu complex error has asserted. May also be shown as 806f06070302ffff or 0x806f06070302ffff severity: error alert ...

  • Page 494

    806f0608-1301ffff [powersupplyelementname] has a configuration mismatch. (ps configuration) explanation: this message is for the use case when an implementation has detected a power supply with a configuration error. May also be shown as 806f06081301ffff or 0x806f06081301ffff severity: error alert c...

  • Page 495

    806f060d-0401ffff array [computersystemelementname] has failed. (drive 1) explanation: this message is for the use case when an implementation has detected that an array failed. May also be shown as 806f060d0401ffff or 0x806f060d0401ffff severity: error alert category: critical - hard disk drive ser...

  • Page 496

    806f060d-0403ffff array [computersystemelementname] has failed. (drive 3) explanation: this message is for the use case when an implementation has detected that an array failed. May also be shown as 806f060d0403ffff or 0x806f060d0403ffff severity: error alert category: critical - hard disk drive ser...

  • Page 497

    806f060d-0405ffff array [computersystemelementname] has failed. (drive 5) explanation: this message is for the use case when an implementation has detected that an array failed. May also be shown as 806f060d0405ffff or 0x806f060d0405ffff severity: error alert category: critical - hard disk drive ser...

  • Page 498

    806f060d-0407ffff array [computersystemelementname] has failed. (drive 7) explanation: this message is for the use case when an implementation has detected that an array failed. May also be shown as 806f060d0407ffff or 0x806f060d0407ffff severity: error alert category: critical - hard disk drive ser...

  • Page 499

    806f060d-0409ffff array [computersystemelementname] has failed. (drive 9) explanation: this message is for the use case when an implementation has detected that an array failed. May also be shown as 806f060d0409ffff or 0x806f060d0409ffff severity: error alert category: critical - hard disk drive ser...

  • Page 500

    806f060d-040bffff array [computersystemelementname] has failed. (drive 11) explanation: this message is for the use case when an implementation has detected that an array failed. May also be shown as 806f060d040bffff or 0x806f060d040bffff severity: error alert category: critical - hard disk drive se...

  • Page 501

    806f060d-040dffff array [computersystemelementname] has failed. (drive 13) explanation: this message is for the use case when an implementation has detected that an array failed. May also be shown as 806f060d040dffff or 0x806f060d040dffff severity: error alert category: critical - hard disk drive se...

  • Page 502

    806f070c-2003ffff configuration error for [physicalmemoryelementname] on subsystem [memoryelementname]. (dimm 3) explanation: this message is for the use case when an implementation has detected a memory dimm configuration error has been corrected. May also be shown as 806f070c2003ffff or 0x806f070c...

  • Page 503

    806f070c-2006ffff configuration error for [physicalmemoryelementname] on subsystem [memoryelementname]. (dimm 6) explanation: this message is for the use case when an implementation has detected a memory dimm configuration error has been corrected. May also be shown as 806f070c2006ffff or 0x806f070c...

  • Page 504

    806f070c-2009ffff configuration error for [physicalmemoryelementname] on subsystem [memoryelementname]. (dimm 9) explanation: this message is for the use case when an implementation has detected a memory dimm configuration error has been corrected. May also be shown as 806f070c2009ffff or 0x806f070c...

  • Page 505

    806f070c-200cffff configuration error for [physicalmemoryelementname] on subsystem [memoryelementname]. (dimm 12) explanation: this message is for the use case when an implementation has detected a memory dimm configuration error has been corrected. May also be shown as 806f070c200cffff or 0x806f070...

  • Page 506

    806f070c-200fffff configuration error for [physicalmemoryelementname] on subsystem [memoryelementname]. (dimm 15) explanation: this message is for the use case when an implementation has detected a memory dimm configuration error has been corrected. May also be shown as 806f070c200fffff or 0x806f070...

  • Page 507

    806f070c-2012ffff configuration error for [physicalmemoryelementname] on subsystem [memoryelementname]. (dimm 18) explanation: this message is for the use case when an implementation has detected a memory dimm configuration error has been corrected. May also be shown as 806f070c2012ffff or 0x806f070...

  • Page 508

    806f070c-2015ffff configuration error for [physicalmemoryelementname] on subsystem [memoryelementname]. (dimm 21) explanation: this message is for the use case when an implementation has detected a memory dimm configuration error has been corrected. May also be shown as 806f070c2015ffff or 0x806f070...

  • Page 509

    806f070c-2018ffff configuration error for [physicalmemoryelementname] on subsystem [memoryelementname]. (dimm 24) explanation: this message is for the use case when an implementation has detected a memory dimm configuration error has been corrected. May also be shown as 806f070c2018ffff or 0x806f070...

  • Page 510

    806f070d-0401ffff rebuild in progress for array in system [computersystemelementname]. (drive 1) explanation: this message is for the use case when an implementation has detected that an array rebuild is in progress. May also be shown as 806f070d0401ffff or 0x806f070d0401ffff severity: info alert ca...

  • Page 511

    806f070d-0404ffff rebuild in progress for array in system [computersystemelementname]. (drive 4) explanation: this message is for the use case when an implementation has detected that an array rebuild is in progress. May also be shown as 806f070d0404ffff or 0x806f070d0404ffff severity: info alert ca...

  • Page 512

    806f070d-0407ffff rebuild in progress for array in system [computersystemelementname]. (drive 7) explanation: this message is for the use case when an implementation has detected that an array rebuild is in progress. May also be shown as 806f070d0407ffff or 0x806f070d0407ffff severity: info alert ca...

  • Page 513

    806f070d-040affff rebuild in progress for array in system [computersystemelementname]. (drive 10) explanation: this message is for the use case when an implementation has detected that an array rebuild is in progress. May also be shown as 806f070d040affff or 0x806f070d040affff severity: info alert c...

  • Page 514

    806f070d-040dffff rebuild in progress for array in system [computersystemelementname]. (drive 13) explanation: this message is for the use case when an implementation has detected that an array rebuild is in progress. May also be shown as 806f070d040dffff or 0x806f070d040dffff severity: info alert c...

  • Page 515

    806f0807-0301ffff [processorelementname] has been disabled. (cpu 1) explanation: this message is for the use case when an implementation has detected a processor has been disabled. May also be shown as 806f08070301ffff or 0x806f08070301ffff severity: info alert category: system - other serviceable: ...

  • Page 516

    806f0813-2581ffff a uncorrectable bus error has occurred on system [computersystemelementname]. (dimms) explanation: this message is for the use case when an implementation has detected a bus uncorrectable error. May also be shown as 806f08132581ffff or 0x806f08132581ffff severity: error alert categ...

  • Page 517

    806f0813-2584ffff a uncorrectable bus error has occurred on system [computersystemelementname]. (cpus) explanation: this message is for the use case when an implementation has detected a bus uncorrectable error. May also be shown as 806f08132584ffff or 0x806f08132584ffff severity: error alert catego...

  • Page 518

    806f090c-2002ffff [physicalmemoryelementname] on subsystem [memoryelementname] throttled. (dimm 2) explanation: this message is for the use case when an implementation has detected memory has been throttled. May also be shown as 806f090c2002ffff or 0x806f090c2002ffff severity: warning alert category...

  • Page 519

    806f090c-2005ffff [physicalmemoryelementname] on subsystem [memoryelementname] throttled. (dimm 5) explanation: this message is for the use case when an implementation has detected memory has been throttled. May also be shown as 806f090c2005ffff or 0x806f090c2005ffff severity: warning alert category...

  • Page 520

    806f090c-2008ffff [physicalmemoryelementname] on subsystem [memoryelementname] throttled. (dimm 8) explanation: this message is for the use case when an implementation has detected memory has been throttled. May also be shown as 806f090c2008ffff or 0x806f090c2008ffff severity: warning alert category...

  • Page 521

    806f090c-200bffff [physicalmemoryelementname] on subsystem [memoryelementname] throttled. (dimm 11) explanation: this message is for the use case when an implementation has detected memory has been throttled. May also be shown as 806f090c200bffff or 0x806f090c200bffff severity: warning alert categor...

  • Page 522

    806f090c-200effff [physicalmemoryelementname] on subsystem [memoryelementname] throttled. (dimm 14) explanation: this message is for the use case when an implementation has detected memory has been throttled. May also be shown as 806f090c200effff or 0x806f090c200effff severity: warning alert categor...

  • Page 523

    806f090c-2011ffff [physicalmemoryelementname] on subsystem [memoryelementname] throttled. (dimm 17) explanation: this message is for the use case when an implementation has detected memory has been throttled. May also be shown as 806f090c2011ffff or 0x806f090c2011ffff severity: warning alert categor...

  • Page 524

    806f090c-2014ffff [physicalmemoryelementname] on subsystem [memoryelementname] throttled. (dimm 20) explanation: this message is for the use case when an implementation has detected memory has been throttled. May also be shown as 806f090c2014ffff or 0x806f090c2014ffff severity: warning alert categor...

  • Page 525

    806f090c-2017ffff [physicalmemoryelementname] on subsystem [memoryelementname] throttled. (dimm 23) explanation: this message is for the use case when an implementation has detected memory has been throttled. May also be shown as 806f090c2017ffff or 0x806f090c2017ffff severity: warning alert categor...

  • Page 526

    806f0a07-0302ffff [processorelementname] is operating in a degraded state. (cpu 2) explanation: this message is for the use case when an implementation has detected a processor is running in the degraded state. May also be shown as 806f0a070302ffff or 0x806f0a070302ffff severity: warning alert categ...

  • Page 527

    806f0a0c-2002ffff an over-temperature condition has been detected on the [physicalmemoryelementname] on subsystem [memoryelementname]. (dimm 2) explanation: this message is for the use case when an implementation has detected an over temperature condition for memory that has been detected. May also ...

  • Page 528

    806f0a0c-2004ffff an over-temperature condition has been detected on the [physicalmemoryelementname] on subsystem [memoryelementname]. (dimm 4) explanation: this message is for the use case when an implementation has detected an over temperature condition for memory that has been detected. May also ...

  • Page 529

    806f0a0c-2006ffff an over-temperature condition has been detected on the [physicalmemoryelementname] on subsystem [memoryelementname]. (dimm 6) explanation: this message is for the use case when an implementation has detected an over temperature condition for memory that has been detected. May also ...

  • Page 530

    806f0a0c-2008ffff an over-temperature condition has been detected on the [physicalmemoryelementname] on subsystem [memoryelementname]. (dimm 8) explanation: this message is for the use case when an implementation has detected an over temperature condition for memory that has been detected. May also ...

  • Page 531

    806f0a0c-200affff an over-temperature condition has been detected on the [physicalmemoryelementname] on subsystem [memoryelementname]. (dimm 10) explanation: this message is for the use case when an implementation has detected an over temperature condition for memory that has been detected. May also...

  • Page 532

    806f0a0c-200cffff an over-temperature condition has been detected on the [physicalmemoryelementname] on subsystem [memoryelementname]. (dimm 12) explanation: this message is for the use case when an implementation has detected an over temperature condition for memory that has been detected. May also...

  • Page 533

    806f0a0c-200effff an over-temperature condition has been detected on the [physicalmemoryelementname] on subsystem [memoryelementname]. (dimm 14) explanation: this message is for the use case when an implementation has detected an over temperature condition for memory that has been detected. May also...

  • Page 534

    806f0a0c-2010ffff an over-temperature condition has been detected on the [physicalmemoryelementname] on subsystem [memoryelementname]. (dimm 16) explanation: this message is for the use case when an implementation has detected an over temperature condition for memory that has been detected. May also...

  • Page 535

    806f0a0c-2012ffff an over-temperature condition has been detected on the [physicalmemoryelementname] on subsystem [memoryelementname]. (dimm 18) explanation: this message is for the use case when an implementation has detected an over temperature condition for memory that has been detected. May also...

  • Page 536

    806f0a0c-2014ffff an over-temperature condition has been detected on the [physicalmemoryelementname] on subsystem [memoryelementname]. (dimm 20) explanation: this message is for the use case when an implementation has detected an over temperature condition for memory that has been detected. May also...

  • Page 537

    806f0a0c-2016ffff an over-temperature condition has been detected on the [physicalmemoryelementname] on subsystem [memoryelementname]. (dimm 22) explanation: this message is for the use case when an implementation has detected an over temperature condition for memory that has been detected. May also...

  • Page 538

    806f0a0c-2018ffff an over-temperature condition has been detected on the [physicalmemoryelementname] on subsystem [memoryelementname]. (dimm 24) explanation: this message is for the use case when an implementation has detected an over temperature condition for memory that has been detected. May also...

  • Page 539

    806f0a13-0302ffff a fatal bus error has occurred on system [computersystemelementname]. (cpu 2 peci) explanation: this message is for the use case when an implementation has detected a bus fatal error. May also be shown as 806f0a130302ffff or 0x806f0a130302ffff severity: error alert category: critic...

  • Page 540

    81010204-1d01ffff numeric sensor [numericsensorelementname] going low (lower critical) has deasserted. (fan 1a tach) explanation: this message is for the use case when an implementation has detected a lower critical sensor going low has deasserted. May also be shown as 810102041d01ffff or 0x81010204...

  • Page 541

    81010204-1d04ffff numeric sensor [numericsensorelementname] going low (lower critical) has deasserted. (fan 4a tach) explanation: this message is for the use case when an implementation has detected a lower critical sensor going low has deasserted. May also be shown as 810102041d04ffff or 0x81010204...

  • Page 542

    81010204-1d07ffff numeric sensor [numericsensorelementname] going low (lower critical) has deasserted. (fan 7a tach) explanation: this message is for the use case when an implementation has detected a lower critical sensor going low has deasserted. May also be shown as 810102041d07ffff or 0x81010204...

  • Page 543

    81010701-0f02ffff numeric sensor [numericsensorelementname] going high (upper non-critical) has deasserted. (rear bp temp b) explanation: this message is for the use case when an implementation has detected an upper non-critical sensor going high has deasserted. May also be shown as 810107010f02ffff...

  • Page 544

    81010701-1003ffff numeric sensor [numericsensorelementname] going high (upper non-critical) has deasserted. (pci 3 amb temp) explanation: this message is for the use case when an implementation has detected an upper non-critical sensor going high has deasserted. May also be shown as 810107011003ffff...

  • Page 545

    81010701-1402ffff numeric sensor [numericsensorelementname] going high (upper non-critical) has deasserted. (cpu2 vr temp) explanation: this message is for the use case when an implementation has detected an upper non-critical sensor going high has deasserted. May also be shown as 810107011402ffff o...

  • Page 546

    81010701-1405ffff numeric sensor [numericsensorelementname] going high (upper non-critical) has deasserted. (dimm ef vr temp) explanation: this message is for the use case when an implementation has detected an upper non-critical sensor going high has deasserted. May also be shown as 810107011405fff...

  • Page 547

    81010701-3701ffff numeric sensor [numericsensorelementname] going high (upper non-critical) has deasserted. (ambient temp) explanation: this message is for the use case when an implementation has detected an upper non-critical sensor going high has deasserted. May also be shown as 810107013701ffff o...

  • Page 548

    81010901-1001ffff numeric sensor [numericsensorelementname] going high (upper critical) has deasserted. (pci 1 amb temp) explanation: this message is for the use case when an implementation has detected an upper critical sensor going high has deasserted. May also be shown as 810109011001ffff or 0x81...

  • Page 549

    81010901-1301ffff numeric sensor [numericsensorelementname] going high (upper critical) has deasserted. (psu 1 amb temp) explanation: this message is for the use case when an implementation has detected an upper critical sensor going high has deasserted. May also be shown as 810109011301ffff or 0x81...

  • Page 550

    81010901-1403ffff numeric sensor [numericsensorelementname] going high (upper critical) has deasserted. (dimm ab vr temp) explanation: this message is for the use case when an implementation has detected an upper critical sensor going high has deasserted. May also be shown as 810109011403ffff or 0x8...

  • Page 551

    81010901-1406ffff numeric sensor [numericsensorelementname] going high (upper critical) has deasserted. (dimm gh vr temp) explanation: this message is for the use case when an implementation has detected an upper critical sensor going high has deasserted. May also be shown as 810109011406ffff or 0x8...

  • Page 552

    81010902-0701ffff numeric sensor [numericsensorelementname] going high (upper critical) has deasserted. (sysbrd 12v) explanation: this message is for the use case when an implementation has detected an upper critical sensor going high has deasserted. May also be shown as 810109020701ffff or 0x810109...

  • Page 553

    81010b01-1001ffff numeric sensor [numericsensorelementname] going high (upper non-recoverable) has deasserted. (pci 1 amb temp) explanation: this message is for the use case when an implementation has detected an upper non-recoverable sensor going high has deasserted. May also be shown as 81010b0110...

  • Page 554

    81010b01-1301ffff numeric sensor [numericsensorelementname] going high (upper non-recoverable) has deasserted. (psu 1 amb temp) explanation: this message is for the use case when an implementation has detected an upper non-recoverable sensor going high has deasserted. May also be shown as 81010b0113...

  • Page 555

    81010b01-1403ffff numeric sensor [numericsensorelementname] going high (upper non-recoverable) has deasserted. (dimm ab vr temp) explanation: this message is for the use case when an implementation has detected an upper non-recoverable sensor going high has deasserted. May also be shown as 81010b011...

  • Page 556

    81010b01-1406ffff numeric sensor [numericsensorelementname] going high (upper non-recoverable) has deasserted. (dimm gh vr temp) explanation: this message is for the use case when an implementation has detected an upper non-recoverable sensor going high has deasserted. May also be shown as 81010b011...

  • Page 557

    81030006-2101ffff sensor [sensorelementname] has asserted. (sig verify fail) explanation: this message is for the use case when an implementation has detected a sensor has asserted. May also be shown as 810300062101ffff or 0x810300062101ffff severity: info alert category: system - other serviceable:...

  • Page 558

    81030108-1301ffff sensor [sensorelementname] has deasserted. (ps heavy load) explanation: this message is for the use case when an implementation has detected a sensor has deasserted. May also be shown as 810301081301ffff or 0x810301081301ffff severity: info alert category: system - other serviceabl...

  • Page 559

    81070101-0c01ffff sensor [sensorelementname] has deasserted the transition from normal to non-critical state. (ambient status) 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...

  • Page 560

    8107010f-2201ffff sensor [sensorelementname] has deasserted the transition from normal to non-critical state. (gpt status) 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 810...

  • Page 561

    81070201-0301ffff sensor [sensorelementname] has transitioned to a less severe state from critical. (cpu 1 overtemp) 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 810702010301ffff or 0x81070201...

  • Page 562

    81070204-0a01ffff sensor [sensorelementname] has transitioned to a less severe state from critical. (ps 1 fan fault) 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 810702040a01ffff or 0x81070204...

  • Page 563

    81070208-0a02ffff sensor [sensorelementname] has transitioned to a less severe state from critical. (ps 2 therm fault) 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 810702080a02ffff or 0x810702...

  • Page 564

    8107020f-2582ffff sensor [sensorelementname] has transitioned to a less severe state from critical. (i/o resources) 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 8107020f2582ffff or 0x8107020f2...

  • Page 565

    8107021b-0301ffff sensor [sensorelementname] has transitioned to a less severe state from critical. (cpu 1 qpilinkerr) 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 8107021b0301ffff or 0x810702...

  • Page 566

    81070301-0301ffff sensor [sensorelementname] has deasserted the transition to non-recoverable from a less severe state. (cpu 1 overtemp) 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. Ma...

  • Page 567

    8107030d-2582ffff sensor [sensorelementname] has deasserted the transition to non-recoverable from a less severe state. (raid vol 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. Ma...

  • Page 568

    810b010a-1e81ffff redundancy lost for [redundancysetelementname] has deasserted. (fan zone 1) explanation: this message is for the use case when redundacy lost has deasserted. May also be shown as 810b010a1e81ffff or 0x810b010a1e81ffff severity: info alert category: critical - fan failure serviceabl...

  • Page 569

    810b0309-1301ffff non-redundant:sufficient resources from redundancy degraded or fully redundant for [redundancysetelementname] has deasserted. (power resource) explanation: this message is for the use case when a redundancy set has transitioned from non- redundant:sufficient resources. May also be ...

  • Page 570

    810b050a-1e81ffff non-redundant:insufficient resources for [redundancysetelementname] has deasserted. (fan zone 1) explanation: this message is for the use case when a redundancy set has transitioned from non- redundant:insufficient resources. May also be shown as 810b050a1e81ffff or 0x810b050a1e81f...

  • Page 571

    816f0007-0301ffff [processorelementname] has recovered from ierr. (cpu 1) explanation: this message is for the use case when an implementation has detected a processor recovered - ierr condition. May also be shown as 816f00070301ffff or 0x816f00070301ffff severity: info alert category: critical - cp...

  • Page 572

    816f0008-0a02ffff [powersupplyelementname] has been removed from container [physicalpackageelementname]. (power supply 2) explanation: this message is for the use case when an implementation has detected a power supply has been removed. May also be shown as 816f00080a02ffff or 0x816f00080a02ffff sev...

  • Page 573

    816f000d-0401ffff the drive [storagevolumeelementname] has been removed from unit [physicalpackageelementname]. (drive 1) explanation: this message is for the use case when an implementation has detected a drive has been removed. May also be shown as 816f000d0401ffff or 0x816f000d0401ffff severity: ...

  • Page 574

    816f000d-0403ffff the drive [storagevolumeelementname] has been removed from unit [physicalpackageelementname]. (drive 3) explanation: this message is for the use case when an implementation has detected a drive has been removed. May also be shown as 816f000d0403ffff or 0x816f000d0403ffff severity: ...

  • Page 575

    816f000d-0405ffff the drive [storagevolumeelementname] has been removed from unit [physicalpackageelementname]. (drive 5) explanation: this message is for the use case when an implementation has detected a drive has been removed. May also be shown as 816f000d0405ffff or 0x816f000d0405ffff severity: ...

  • Page 576

    816f000d-0407ffff the drive [storagevolumeelementname] has been removed from unit [physicalpackageelementname]. (drive 7) explanation: this message is for the use case when an implementation has detected a drive has been removed. May also be shown as 816f000d0407ffff or 0x816f000d0407ffff severity: ...

  • Page 577

    816f000d-0409ffff the drive [storagevolumeelementname] has been removed from unit [physicalpackageelementname]. (drive 9) explanation: this message is for the use case when an implementation has detected a drive has been removed. May also be shown as 816f000d0409ffff or 0x816f000d0409ffff severity: ...

  • Page 578

    816f000d-040bffff the drive [storagevolumeelementname] has been removed from unit [physicalpackageelementname]. (drive 11) explanation: this message is for the use case when an implementation has detected a drive has been removed. May also be shown as 816f000d040bffff or 0x816f000d040bffff severity:...

  • Page 579

    816f000d-040dffff the drive [storagevolumeelementname] has been removed from unit [physicalpackageelementname]. (drive 13) explanation: this message is for the use case when an implementation has detected a drive has been removed. May also be shown as 816f000d040dffff or 0x816f000d040dffff severity:...

  • Page 580

    816f0021-2201ffff fault condition removed on slot [physicalconnectorelementname] on system [computersystemelementname]. (no op rom space) explanation: this message is for the use case when an implementation has detected a fault condition in a slot has been removed. May also be shown as 816f00212201f...

  • Page 581

    816f0021-3001ffff fault condition removed on slot [physicalconnectorelementname] on system [computersystemelementname]. (internal raid) explanation: this message is for the use case when an implementation has detected a fault condition in a slot has been removed. May also be shown as 816f00213001fff...

  • Page 582

    816f0028-2101ffff sensor [sensorelementname] has returned to normal on management system [computersystemelementname]. (tpm cmd failures) explanation: this message is for the use case when an implementation has detected a sensor returned from degraded/unavailable/failure. May also be shown as 816f002...

  • Page 583

    816f0108-0a01ffff [powersupplyelementname] has returned to ok status. (power supply 1) explanation: this message is for the use case when an implementation has detected a power supply return to normal operational status. May also be shown as 816f01080a01ffff or 0x816f01080a01ffff severity: info aler...

  • Page 584

    816f010c-2002ffff uncorrectable error recovery detected for [physicalmemoryelementname] on subsystem [memoryelementname]. (dimm 2) explanation: this message is for the use case when an implementation has detected a memory uncorrectable error recovery. May also be shown as 816f010c2002ffff or 0x816f0...

  • Page 585

    816f010c-2005ffff uncorrectable error recovery detected for [physicalmemoryelementname] on subsystem [memoryelementname]. (dimm 5) explanation: this message is for the use case when an implementation has detected a memory uncorrectable error recovery. May also be shown as 816f010c2005ffff or 0x816f0...

  • Page 586

    816f010c-2008ffff uncorrectable error recovery detected for [physicalmemoryelementname] on subsystem [memoryelementname]. (dimm 8) explanation: this message is for the use case when an implementation has detected a memory uncorrectable error recovery. May also be shown as 816f010c2008ffff or 0x816f0...

  • Page 587

    816f010c-200bffff uncorrectable error recovery detected for [physicalmemoryelementname] on subsystem [memoryelementname]. (dimm 11) explanation: this message is for the use case when an implementation has detected a memory uncorrectable error recovery. May also be shown as 816f010c200bffff or 0x816f...

  • Page 588

    816f010c-200effff uncorrectable error recovery detected for [physicalmemoryelementname] on subsystem [memoryelementname]. (dimm 14) explanation: this message is for the use case when an implementation has detected a memory uncorrectable error recovery. May also be shown as 816f010c200effff or 0x816f...

  • Page 589

    816f010c-2011ffff uncorrectable error recovery detected for [physicalmemoryelementname] on subsystem [memoryelementname]. (dimm 17) explanation: this message is for the use case when an implementation has detected a memory uncorrectable error recovery. May also be shown as 816f010c2011ffff or 0x816f...

  • Page 590

    816f010c-2014ffff uncorrectable error recovery detected for [physicalmemoryelementname] on subsystem [memoryelementname]. (dimm 20) explanation: this message is for the use case when an implementation has detected a memory uncorrectable error recovery. May also be shown as 816f010c2014ffff or 0x816f...

  • Page 591

    816f010c-2017ffff uncorrectable error recovery detected for [physicalmemoryelementname] on subsystem [memoryelementname]. (dimm 23) explanation: this message is for the use case when an implementation has detected a memory uncorrectable error recovery. May also be shown as 816f010c2017ffff or 0x816f...

  • Page 592

    816f010d-0400ffff the drive [storagevolumeelementname] has been enabled. (drive 0) explanation: this message is for the use case when an implementation has detected a drive was enabled. May also be shown as 816f010d0400ffff or 0x816f010d0400ffff severity: info alert category: critical - hard disk dr...

  • Page 593

    816f010d-0403ffff the drive [storagevolumeelementname] has been enabled. (drive 3) explanation: this message is for the use case when an implementation has detected a drive was enabled. May also be shown as 816f010d0403ffff or 0x816f010d0403ffff severity: info alert category: critical - hard disk dr...

  • Page 594

    816f010d-0406ffff the drive [storagevolumeelementname] has been enabled. (drive 6) explanation: this message is for the use case when an implementation has detected a drive was enabled. May also be shown as 816f010d0406ffff or 0x816f010d0406ffff severity: info alert category: critical - hard disk dr...

  • Page 595

    816f010d-0409ffff the drive [storagevolumeelementname] has been enabled. (drive 9) explanation: this message is for the use case when an implementation has detected a drive was enabled. May also be shown as 816f010d0409ffff or 0x816f010d0409ffff severity: info alert category: critical - hard disk dr...

  • Page 596

    816f010d-040cffff the drive [storagevolumeelementname] has been enabled. (drive 12) explanation: this message is for the use case when an implementation has detected a drive was enabled. May also be shown as 816f010d040cffff or 0x816f010d040cffff severity: info alert category: critical - hard disk d...

  • Page 597

    816f0113-0301ffff system [computersystemelementname] has recovered from a bus timeout. (cpu 1 peci) explanation: this message is for the use case when an implemenation has detected that a system has recovered from a bus timeout. May also be shown as 816f01130301ffff or 0x816f01130301ffff severity: i...

  • Page 598

    816f011b-0701ffff the connector [physicalconnectorelementname] configuration error has been repaired. (front usb) explanation: this message is for the use case when an implementation has detected an interconnect configuration was repaired. May also be shown as 816f011b0701ffff or 0x816f011b0701ffff ...

  • Page 599

    816f0125-1001ffff [managedelementname] detected as present. (pci riser 1) explanation: this message is for the use case when an implementation has detected a managed element is now present. May also be shown as 816f01251001ffff or 0x816f01251001ffff severity: info alert category: system - other serv...

  • Page 600

    816f0207-0301ffff [processorelementname] has recovered from frb1/bist condition. (cpu 1) explanation: this message is for the use case when an implementation has detected a processor recovered - frb1/bist condition. May also be shown as 816f02070301ffff or 0x816f02070301ffff severity: info alert cat...

  • Page 601

    816f020d-0400ffff failure no longer predicted on drive [storagevolumeelementname] for array [computersystemelementname]. (drive 0) explanation: this message is for the use case when an implementation has detected an array failure is no longer predicted. May also be shown as 816f020d0400ffff or 0x816...

  • Page 602

    816f020d-0403ffff failure no longer predicted on drive [storagevolumeelementname] for array [computersystemelementname]. (drive 3) explanation: this message is for the use case when an implementation has detected an array failure is no longer predicted. May also be shown as 816f020d0403ffff or 0x816...

  • Page 603

    816f020d-0406ffff failure no longer predicted on drive [storagevolumeelementname] for array [computersystemelementname]. (drive 6) explanation: this message is for the use case when an implementation has detected an array failure is no longer predicted. May also be shown as 816f020d0406ffff or 0x816...

  • Page 604

    816f020d-0409ffff failure no longer predicted on drive [storagevolumeelementname] for array [computersystemelementname]. (drive 9) explanation: this message is for the use case when an implementation has detected an array failure is no longer predicted. May also be shown as 816f020d0409ffff or 0x816...

  • Page 605

    816f020d-040cffff failure no longer predicted on drive [storagevolumeelementname] for array [computersystemelementname]. (drive 12) explanation: this message is for the use case when an implementation has detected an array failure is no longer predicted. May also be shown as 816f020d040cffff or 0x81...

  • Page 606

    816f0308-0a02ffff [powersupplyelementname] has returned to a normal input state. (power supply 2) explanation: this message is for the use case when an implementation has detected a power supply that has input that has returned to normal. May also be shown as 816f03080a02ffff or 0x816f03080a02ffff s...

  • Page 607

    816f030c-2003ffff scrub failure for [physicalmemoryelementname] on subsystem [memoryelementname]has recovered. (dimm 3) explanation: this message is for the use case when an implementation has detected a memory scrub failure recovery. May also be shown as 816f030c2003ffff or 0x816f030c2003ffff sever...

  • Page 608

    816f030c-2006ffff scrub failure for [physicalmemoryelementname] on subsystem [memoryelementname]has recovered. (dimm 6) explanation: this message is for the use case when an implementation has detected a memory scrub failure recovery. May also be shown as 816f030c2006ffff or 0x816f030c2006ffff sever...

  • Page 609

    816f030c-2009ffff scrub failure for [physicalmemoryelementname] on subsystem [memoryelementname]has recovered. (dimm 9) explanation: this message is for the use case when an implementation has detected a memory scrub failure recovery. May also be shown as 816f030c2009ffff or 0x816f030c2009ffff sever...

  • Page 610

    816f030c-200cffff scrub failure for [physicalmemoryelementname] on subsystem [memoryelementname]has recovered. (dimm 12) explanation: this message is for the use case when an implementation has detected a memory scrub failure recovery. May also be shown as 816f030c200cffff or 0x816f030c200cffff seve...

  • Page 611

    816f030c-200fffff scrub failure for [physicalmemoryelementname] on subsystem [memoryelementname]has recovered. (dimm 15) explanation: this message is for the use case when an implementation has detected a memory scrub failure recovery. May also be shown as 816f030c200fffff or 0x816f030c200fffff seve...

  • Page 612

    816f030c-2012ffff scrub failure for [physicalmemoryelementname] on subsystem [memoryelementname]has recovered. (dimm 18) explanation: this message is for the use case when an implementation has detected a memory scrub failure recovery. May also be shown as 816f030c2012ffff or 0x816f030c2012ffff seve...

  • Page 613

    816f030c-2015ffff scrub failure for [physicalmemoryelementname] on subsystem [memoryelementname]has recovered. (dimm 21) explanation: this message is for the use case when an implementation has detected a memory scrub failure recovery. May also be shown as 816f030c2015ffff or 0x816f030c2015ffff seve...

  • Page 614

    816f030c-2018ffff scrub failure for [physicalmemoryelementname] on subsystem [memoryelementname]has recovered. (dimm 24) explanation: this message is for the use case when an implementation has detected a memory scrub failure recovery. May also be shown as 816f030c2018ffff or 0x816f030c2018ffff seve...

  • Page 615

    816f030d-0401ffff hot spare disabled for [computersystemelementname]. (drive 1) explanation: this message is for the use case when an implementation has detected a hot spare has been disabled. May also be shown as 816f030d0401ffff or 0x816f030d0401ffff severity: info alert category: system - other s...

  • Page 616

    816f030d-0404ffff hot spare disabled for [computersystemelementname]. (drive 4) explanation: this message is for the use case when an implementation has detected a hot spare has been disabled. May also be shown as 816f030d0404ffff or 0x816f030d0404ffff severity: info alert category: system - other s...

  • Page 617

    816f030d-0407ffff hot spare disabled for [computersystemelementname]. (drive 7) explanation: this message is for the use case when an implementation has detected a hot spare has been disabled. May also be shown as 816f030d0407ffff or 0x816f030d0407ffff severity: info alert category: system - other s...

  • Page 618

    816f030d-040affff hot spare disabled for [computersystemelementname]. (drive 10) explanation: this message is for the use case when an implementation has detected a hot spare has been disabled. May also be shown as 816f030d040affff or 0x816f030d040affff severity: info alert category: system - other ...

  • Page 619

    816f030d-040dffff hot spare disabled for [computersystemelementname]. (drive 13) explanation: this message is for the use case when an implementation has detected a hot spare has been disabled. May also be shown as 816f030d040dffff or 0x816f030d040dffff severity: info alert category: system - other ...

  • Page 620

    816f040c-2002ffff [physicalmemoryelementname] enabled on subsystem [memoryelementname]. (dimm 2) explanation: this message is for the use case when an implementation has detected that memory has been enabled. May also be shown as 816f040c2002ffff or 0x816f040c2002ffff severity: info alert category: ...

  • Page 621

    816f040c-2005ffff [physicalmemoryelementname] enabled on subsystem [memoryelementname]. (dimm 5) explanation: this message is for the use case when an implementation has detected that memory has been enabled. May also be shown as 816f040c2005ffff or 0x816f040c2005ffff severity: info alert category: ...

  • Page 622

    816f040c-2008ffff [physicalmemoryelementname] enabled on subsystem [memoryelementname]. (dimm 8) explanation: this message is for the use case when an implementation has detected that memory has been enabled. May also be shown as 816f040c2008ffff or 0x816f040c2008ffff severity: info alert category: ...

  • Page 623

    816f040c-200bffff [physicalmemoryelementname] enabled on subsystem [memoryelementname]. (dimm 11) explanation: this message is for the use case when an implementation has detected that memory has been enabled. May also be shown as 816f040c200bffff or 0x816f040c200bffff severity: info alert category:...

  • Page 624

    816f040c-200effff [physicalmemoryelementname] enabled on subsystem [memoryelementname]. (dimm 14) explanation: this message is for the use case when an implementation has detected that memory has been enabled. May also be shown as 816f040c200effff or 0x816f040c200effff severity: info alert category:...

  • Page 625

    816f040c-2011ffff [physicalmemoryelementname] enabled on subsystem [memoryelementname]. (dimm 17) explanation: this message is for the use case when an implementation has detected that memory has been enabled. May also be shown as 816f040c2011ffff or 0x816f040c2011ffff severity: info alert category:...

  • Page 626

    816f040c-2014ffff [physicalmemoryelementname] enabled on subsystem [memoryelementname]. (dimm 20) explanation: this message is for the use case when an implementation has detected that memory has been enabled. May also be shown as 816f040c2014ffff or 0x816f040c2014ffff severity: info alert category:...

  • Page 627

    816f040c-2017ffff [physicalmemoryelementname] enabled on subsystem [memoryelementname]. (dimm 23) explanation: this message is for the use case when an implementation has detected that memory has been enabled. May also be shown as 816f040c2017ffff or 0x816f040c2017ffff severity: info alert category:...

  • Page 628

    816f0413-2582ffff a pci perr recovery has occurred on system [computersystemelementname]. (pcis) explanation: this message is for the use case when an implementation has detected a pci perr recovered. May also be shown as 816f04132582ffff or 0x816f04132582ffff severity: info alert category: critical...

  • Page 629

    816f0507-2584ffff [processorelementname] has recovered from a configuration mismatch. (all cpus) explanation: this message is for the use case when an implementation has recovered from a processor configuration mismatch. May also be shown as 816f05072584ffff or 0x816f05072584ffff severity: info aler...

  • Page 630

    816f050c-2003ffff memory logging limit removed for [physicalmemoryelementname] on subsystem [memoryelementname]. (dimm 3) explanation: this message is for the use case when an implementation has detected that the memory logging limit has been removed. May also be shown as 816f050c2003ffff or 0x816f0...

  • Page 631

    816f050c-2006ffff memory logging limit removed for [physicalmemoryelementname] on subsystem [memoryelementname]. (dimm 6) explanation: this message is for the use case when an implementation has detected that the memory logging limit has been removed. May also be shown as 816f050c2006ffff or 0x816f0...

  • Page 632

    816f050c-2009ffff memory logging limit removed for [physicalmemoryelementname] on subsystem [memoryelementname]. (dimm 9) explanation: this message is for the use case when an implementation has detected that the memory logging limit has been removed. May also be shown as 816f050c2009ffff or 0x816f0...

  • Page 633

    816f050c-200cffff memory logging limit removed for [physicalmemoryelementname] on subsystem [memoryelementname]. (dimm 12) explanation: this message is for the use case when an implementation has detected that the memory logging limit has been removed. May also be shown as 816f050c200cffff or 0x816f...

  • Page 634

    816f050c-200fffff memory logging limit removed for [physicalmemoryelementname] on subsystem [memoryelementname]. (dimm 15) explanation: this message is for the use case when an implementation has detected that the memory logging limit has been removed. May also be shown as 816f050c200fffff or 0x816f...

  • Page 635

    816f050c-2012ffff memory logging limit removed for [physicalmemoryelementname] on subsystem [memoryelementname]. (dimm 18) explanation: this message is for the use case when an implementation has detected that the memory logging limit has been removed. May also be shown as 816f050c2012ffff or 0x816f...

  • Page 636

    816f050c-2015ffff memory logging limit removed for [physicalmemoryelementname] on subsystem [memoryelementname]. (dimm 21) explanation: this message is for the use case when an implementation has detected that the memory logging limit has been removed. May also be shown as 816f050c2015ffff or 0x816f...

  • Page 637

    816f050c-2018ffff memory logging limit removed for [physicalmemoryelementname] on subsystem [memoryelementname]. (dimm 24) explanation: this message is for the use case when an implementation has detected that the memory logging limit has been removed. May also be shown as 816f050c2018ffff or 0x816f...

  • Page 638

    816f050d-0401ffff critical array [computersystemelementname] has deasserted. (drive 1) explanation: this message is for the use case when an implementation has detected that an critiacal array has deasserted. May also be shown as 816f050d0401ffff or 0x816f050d0401ffff severity: info alert category: ...

  • Page 639

    816f050d-0404ffff critical array [computersystemelementname] has deasserted. (drive 4) explanation: this message is for the use case when an implementation has detected that an critiacal array has deasserted. May also be shown as 816f050d0404ffff or 0x816f050d0404ffff severity: info alert category: ...

  • Page 640

    816f050d-0407ffff critical array [computersystemelementname] has deasserted. (drive 7) explanation: this message is for the use case when an implementation has detected that an critiacal array has deasserted. May also be shown as 816f050d0407ffff or 0x816f050d0407ffff severity: info alert category: ...

  • Page 641

    816f050d-040affff critical array [computersystemelementname] has deasserted. (drive 10) explanation: this message is for the use case when an implementation has detected that an critiacal array has deasserted. May also be shown as 816f050d040affff or 0x816f050d040affff severity: info alert category:...

  • Page 642

    816f050d-040dffff critical array [computersystemelementname] has deasserted. (drive 13) explanation: this message is for the use case when an implementation has detected that an critiacal array has deasserted. May also be shown as 816f050d040dffff or 0x816f050d040dffff severity: info alert category:...

  • Page 643

    816f0607-2584ffff an sm bios uncorrectable cpu complex error for [processorelementname] has deasserted. (all cpus) explanation: this message is for the use case when an sm bios uncorrectable cpu complex error has deasserted. May also be shown as 816f06072584ffff or 0x816f06072584ffff severity: info ...

  • Page 644

    816f060d-0401ffff array in system [computersystemelementname] has been restored. (drive 1) explanation: this message is for the use case when an implementation has detected that a failed array has been restored. May also be shown as 816f060d0401ffff or 0x816f060d0401ffff severity: info alert categor...

  • Page 645

    816f060d-0404ffff array in system [computersystemelementname] has been restored. (drive 4) explanation: this message is for the use case when an implementation has detected that a failed array has been restored. May also be shown as 816f060d0404ffff or 0x816f060d0404ffff severity: info alert categor...

  • Page 646

    816f060d-0407ffff array in system [computersystemelementname] has been restored. (drive 7) explanation: this message is for the use case when an implementation has detected that a failed array has been restored. May also be shown as 816f060d0407ffff or 0x816f060d0407ffff severity: info alert categor...

  • Page 647

    816f060d-040affff array in system [computersystemelementname] has been restored. (drive 10) explanation: this message is for the use case when an implementation has detected that a failed array has been restored. May also be shown as 816f060d040affff or 0x816f060d040affff severity: info alert catego...

  • Page 648

    816f060d-040dffff array in system [computersystemelementname] has been restored. (drive 13) explanation: this message is for the use case when an implementation has detected that a failed array has been restored. May also be shown as 816f060d040dffff or 0x816f060d040dffff severity: info alert catego...

  • Page 649

    816f070c-2003ffff configuration error for [physicalmemoryelementname] on subsystem [memoryelementname]has deasserted. (dimm 3) explanation: this message is for the use case when an implementation has detected a memory dimm configuration error has deasserted. May also be shown as 816f070c2003ffff or ...

  • Page 650

    816f070c-2006ffff configuration error for [physicalmemoryelementname] on subsystem [memoryelementname]has deasserted. (dimm 6) explanation: this message is for the use case when an implementation has detected a memory dimm configuration error has deasserted. May also be shown as 816f070c2006ffff or ...

  • Page 651

    816f070c-2009ffff configuration error for [physicalmemoryelementname] on subsystem [memoryelementname]has deasserted. (dimm 9) explanation: this message is for the use case when an implementation has detected a memory dimm configuration error has deasserted. May also be shown as 816f070c2009ffff or ...

  • Page 652

    816f070c-200cffff configuration error for [physicalmemoryelementname] on subsystem [memoryelementname]has deasserted. (dimm 12) explanation: this message is for the use case when an implementation has detected a memory dimm configuration error has deasserted. May also be shown as 816f070c200cffff or...

  • Page 653

    816f070c-200fffff configuration error for [physicalmemoryelementname] on subsystem [memoryelementname]has deasserted. (dimm 15) explanation: this message is for the use case when an implementation has detected a memory dimm configuration error has deasserted. May also be shown as 816f070c200fffff or...

  • Page 654

    816f070c-2012ffff configuration error for [physicalmemoryelementname] on subsystem [memoryelementname]has deasserted. (dimm 18) explanation: this message is for the use case when an implementation has detected a memory dimm configuration error has deasserted. May also be shown as 816f070c2012ffff or...

  • Page 655

    816f070c-2015ffff configuration error for [physicalmemoryelementname] on subsystem [memoryelementname]has deasserted. (dimm 21) explanation: this message is for the use case when an implementation has detected a memory dimm configuration error has deasserted. May also be shown as 816f070c2015ffff or...

  • Page 656

    816f070c-2018ffff configuration error for [physicalmemoryelementname] on subsystem [memoryelementname]has deasserted. (dimm 24) explanation: this message is for the use case when an implementation has detected a memory dimm configuration error has deasserted. May also be shown as 816f070c2018ffff or...

  • Page 657

    816f070d-0401ffff rebuild completed for array in system [computersystemelementname]. (drive 1) explanation: this message is for the use case when an implementation has detected that an array rebuild has completed. May also be shown as 816f070d0401ffff or 0x816f070d0401ffff severity: info alert categ...

  • Page 658

    816f070d-0404ffff rebuild completed for array in system [computersystemelementname]. (drive 4) explanation: this message is for the use case when an implementation has detected that an array rebuild has completed. May also be shown as 816f070d0404ffff or 0x816f070d0404ffff severity: info alert categ...

  • Page 659

    816f070d-0407ffff rebuild completed for array in system [computersystemelementname]. (drive 7) explanation: this message is for the use case when an implementation has detected that an array rebuild has completed. May also be shown as 816f070d0407ffff or 0x816f070d0407ffff severity: info alert categ...

  • Page 660

    816f070d-040affff rebuild completed for array in system [computersystemelementname]. (drive 10) explanation: this message is for the use case when an implementation has detected that an array rebuild has completed. May also be shown as 816f070d040affff or 0x816f070d040affff severity: info alert cate...

  • Page 661

    816f070d-040dffff rebuild completed for array in system [computersystemelementname]. (drive 13) explanation: this message is for the use case when an implementation has detected that an array rebuild has completed. May also be shown as 816f070d040dffff or 0x816f070d040dffff severity: info alert cate...

  • Page 662

    816f0807-2584ffff [processorelementname] has been enabled. (all cpus) explanation: this message is for the use case when an implementation has detected a processor has been enabled. May also be shown as 816f08072584ffff or 0x816f08072584ffff severity: info alert category: system - other serviceable:...

  • Page 663

    816f0813-2584ffff system [computersystemelementname]has recovered from an uncorrectable bus error. (cpus) explanation: this message is for the use case when an implementation has detected a that a system has recovered from a bus uncorrectable error. May also be shown as 816f08132584ffff or 0x816f081...

  • Page 664

    816f090c-2003ffff [physicalmemoryelementname] on subsystem [memoryelementname] is no longer throttled. (dimm 3) explanation: this message is for the use case when an implementation has detected memory is no longer throttled. May also be shown as 816f090c2003ffff or 0x816f090c2003ffff severity: info ...

  • Page 665

    816f090c-2006ffff [physicalmemoryelementname] on subsystem [memoryelementname] is no longer throttled. (dimm 6) explanation: this message is for the use case when an implementation has detected memory is no longer throttled. May also be shown as 816f090c2006ffff or 0x816f090c2006ffff severity: info ...

  • Page 666

    816f090c-2009ffff [physicalmemoryelementname] on subsystem [memoryelementname] is no longer throttled. (dimm 9) explanation: this message is for the use case when an implementation has detected memory is no longer throttled. May also be shown as 816f090c2009ffff or 0x816f090c2009ffff severity: info ...

  • Page 667

    816f090c-200cffff [physicalmemoryelementname] on subsystem [memoryelementname] is no longer throttled. (dimm 12) explanation: this message is for the use case when an implementation has detected memory is no longer throttled. May also be shown as 816f090c200cffff or 0x816f090c200cffff severity: info...

  • Page 668

    816f090c-200fffff [physicalmemoryelementname] on subsystem [memoryelementname] is no longer throttled. (dimm 15) explanation: this message is for the use case when an implementation has detected memory is no longer throttled. May also be shown as 816f090c200fffff or 0x816f090c200fffff severity: info...

  • Page 669

    816f090c-2012ffff [physicalmemoryelementname] on subsystem [memoryelementname] is no longer throttled. (dimm 18) explanation: this message is for the use case when an implementation has detected memory is no longer throttled. May also be shown as 816f090c2012ffff or 0x816f090c2012ffff severity: info...

  • Page 670

    816f090c-2015ffff [physicalmemoryelementname] on subsystem [memoryelementname] is no longer throttled. (dimm 21) explanation: this message is for the use case when an implementation has detected memory is no longer throttled. May also be shown as 816f090c2015ffff or 0x816f090c2015ffff severity: info...

  • Page 671

    816f090c-2018ffff [physicalmemoryelementname] on subsystem [memoryelementname] is no longer throttled. (dimm 24) explanation: this message is for the use case when an implementation has detected memory is no longer throttled. May also be shown as 816f090c2018ffff or 0x816f090c2018ffff severity: info...

  • Page 672

    816f0a0c-2001ffff an over-temperature condition has been removed on the [physicalmemoryelementname] on subsystem [memoryelementname]. (dimm 1) explanation: this message is for the use case when an implementation has detected an over temperature condition for memory that has been removed. May also be...

  • Page 673

    816f0a0c-2004ffff an over-temperature condition has been removed on the [physicalmemoryelementname] on subsystem [memoryelementname]. (dimm 4) explanation: this message is for the use case when an implementation has detected an over temperature condition for memory that has been removed. May also be...

  • Page 674

    816f0a0c-2007ffff an over-temperature condition has been removed on the [physicalmemoryelementname] on subsystem [memoryelementname]. (dimm 7) explanation: this message is for the use case when an implementation has detected an over temperature condition for memory that has been removed. May also be...

  • Page 675

    816f0a0c-200affff an over-temperature condition has been removed on the [physicalmemoryelementname] on subsystem [memoryelementname]. (dimm 10) explanation: this message is for the use case when an implementation has detected an over temperature condition for memory that has been removed. May also b...

  • Page 676

    816f0a0c-200dffff an over-temperature condition has been removed on the [physicalmemoryelementname] on subsystem [memoryelementname]. (dimm 13) explanation: this message is for the use case when an implementation has detected an over temperature condition for memory that has been removed. May also b...

  • Page 677

    816f0a0c-2010ffff an over-temperature condition has been removed on the [physicalmemoryelementname] on subsystem [memoryelementname]. (dimm 16) explanation: this message is for the use case when an implementation has detected an over temperature condition for memory that has been removed. May also b...

  • Page 678

    816f0a0c-2013ffff an over-temperature condition has been removed on the [physicalmemoryelementname] on subsystem [memoryelementname]. (dimm 19) explanation: this message is for the use case when an implementation has detected an over temperature condition for memory that has been removed. May also b...

  • Page 679

    816f0a0c-2016ffff an over-temperature condition has been removed on the [physicalmemoryelementname] on subsystem [memoryelementname]. (dimm 22) explanation: this message is for the use case when an implementation has detected an over temperature condition for memory that has been removed. May also b...

  • Page 680

    816f0a13-0301ffff system [computersystemelementname] has recovered from a fatal bus error. (cpu 1 peci) explanation: this message is for the use case when an implementation has detected that a system has recovered from a bus fatal error. May also be shown as 816f0a130301ffff or 0x816f0a130301ffff se...

  • Page 681

    Appendix b. Uefi/post diagnostic codes uefi/post diagnostic error codes can be generated when the server starts or while the server is running. Uefi/post codes are logged in the imm event log in the server. For each event code, the following fields are displayed: event identifier an identifier that ...

  • Page 682

    Attention: 1. When you press ctrl+alt+delete on f1 setup menu panel, the system will reboot automatically and ask you to enter password again. 2. Most f1 setup settings, which can be load default, are chipset related items or less user input required items. However, when adjusting the iscsi settings...

  • Page 683

    I.1800c [i.1800c] explanation: a cache type mismatch has been detected for one or more processor packages. Processors have one or more cache levels with mismatched type severity: error user response: complete the following steps: 1. Verify that matching processors are installed in the correct proces...

  • Page 684

    I.18010 [i.18010] explanation: a processor stepping mismatch has been detected for one or more processor packages. Processors of the same model have mismatched stepping id severity: error user response: complete the following steps: 1. Verify that matching processors are installed in the correct pro...

  • Page 685

    I.3808004 [i.3808004] explanation: the imm system event log (sel) is full. Ipmi system event log is full severity: info user response: complete the following steps: 1. Use the imm web interface to clear the event log. 2. If imm communication is unavailable, use f1 setup to access system event logs m...

  • Page 686

    I.3818009 [i.3818009] explanation: the tpm could not be properly initialized. Tpminit: fail to initialize tpm chip. Severity: info user response: complete the following steps: 1. Check the ibm support site for an applicable service bulletin or firmware update that applies to this error. 2. Reboot th...

  • Page 687

    I.58015 [i.58015] explanation: memory spare copy initiated. Spare copy started severity: info user response: complete the following steps: 1. Information only; no action is required. I.580a4 [i.580a4] explanation: memory population change detected. Dimm population change detected severity: info user...

  • Page 688

    S.1100c [s.1100c] explanation: an uncorrectable error has been detected on processor %. Uncorrectable processor error detected severity: error user response: complete the following steps: 1. Check the ibm support site for an applicable service bulletin or firmware update that applies to this error. ...

  • Page 689

    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 the ibm support site for an applicable service bulletin or firmware update that applies ...

  • Page 690

    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 691

    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 692

    S.51003 [s.51003] explanation: an uncorrectable memory error was detected in dimm slot % on rank %. [s.51003] an uncorrectable memory error was detected on processor % channel %. The failing dimm within the channel could not be determined. [s.51003] an uncorrectable memory error has been detected. F...

  • Page 693

    S.51009 [s.51009] explanation: no system memory has been detected. No memory detected severity: error user response: complete the following steps: 1. If any memory errors are logged other than this one, take actions indicated for those codes first. 2. If no other memory diagnostic codes appear in th...

  • Page 694

    S.68005 [s.68005] explanation: an error has been detected by the the iio core logic on bus %. The global fatal error status register contains %. The global non-fatal error status register contains %. Please check error logs for the presence of additional downstream device error data. Critical ioh-pc...

  • Page 695

    W.3048006 [w.3048006] explanation: uefi has booted from the backup flash bank due to an automatic boot recovery (abr) event. Automated boot recovery, booting backup uefi image severity: warning user response: complete the following steps: 1. Check the ibm support site for an applicable service bulle...

  • Page 696

    W.305800b [w.305800b] explanation: driver health protocol: reports 'reboot' required controller. Driver health protocol: reports 'reboot' required controller severity: warning user response: complete the following steps: 1. No action required. The system will reboot at the end of post. 2. If the pro...

  • Page 697

    W.3808000 [w.3808000] explanation: an imm communication failure has occurred. Imm communication failure severity: warning user response: complete the following steps: 1. Reset the imm from the cmm. 2. Use the cmm to remove auxilliary power from the compute node. This will reboot the compute node. 3....

  • Page 698

    W.3818005 [w.3818005] explanation: the crtm flash driver could not successfully flash the staging area. The update was aborted crtm update aborted severity: warning user response: complete the following steps: 1. Continue booting the system. If system does not reset, manually reset the system. 2. If...

  • Page 699

    W.50001 [w.50001] explanation: a dimm has been disabled due to an error detected during post. Dimm disabled severity: info user response: complete the following steps: 1. If the dimm was disabled because of a memory fault, follow the procedure for that event. 2. If no memory fault is recorded in the...

  • Page 700

    W.58007 [w.58007] explanation: invalid memory configuration (unsupported dimm population) detected. Please verify memory configuration is valid. Unsupported dimm population severity: error user response: complete the following steps: 1. Ensure that the dimm connectors are populated according to the ...

  • Page 701

    Appendix c. 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 can result when you run the broadcom network test. 405-000-000 brcm:testcontrolregisters test passed ex...

  • Page 702

    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 703

    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 704

    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 705

    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 706

    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 707

    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 708

    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 709

    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 710

    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 711

    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 712

    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 713

    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 714

    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 715

    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 716

    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 717

    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 718

    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 719

    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 720

    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 721

    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 722

    Dsa emulex adapter test results the following messages can result 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 website...

  • Page 723

    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 724

    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 725

    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 726

    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 727

    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 728

    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 729

    Dsa intel network test results the following messages can result 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 latest l...

  • Page 730

    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 731

    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 732

    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 733

    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 734

    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 735

    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 736

    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 737

    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 738

    Dsa memory isolation test results the following messages can result 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: v...

  • Page 739

    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 740

    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 741

    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 742

    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 743

    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 744

    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 745

    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 746

    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 747

    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 748

    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 749

    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 750

    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 751

    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 752

    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 753

    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 754

    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 755

    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 756

    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 757

    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 758

    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 759

    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 760

    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 761

    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 762

    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 763

    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 764

    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 765

    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 766

    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 767

    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 768

    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 769

    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 770

    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 771

    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 772

    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 773

    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 774

    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 775

    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 776

    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 777

    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 778

    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 779

    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 780

    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 781

    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 782

    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 783

    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 784

    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 785

    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 786

    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 787

    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 788

    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 789

    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 790

    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 791

    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 792

    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 793

    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 794

    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 795

    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 796

    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 797

    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 798

    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 799

    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 800

    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 801

    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 802

    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 803

    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 804

    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 805

    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 806

    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 807

    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 808

    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 809

    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 810

    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 811

    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 812

    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 813

    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 814

    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 815

    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 816

    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 817

    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 818

    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 819

    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 820

    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 821

    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 822

    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 823

    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 824

    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 825

    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 826

    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 827

    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 828

    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 829

    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 830

    166-901-001 imm i2c test failed explanation: imm indicates failure in h8s 2117 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 disc...

  • Page 831

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

  • Page 832

    166-908-001 imm i2c test failed explanation: imm indicates failure in pca9557 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 disco...

  • Page 833

    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 834

    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 835

    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 836

    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 837

    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 838

    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 839

    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 840

    824 ibm system x3550 m5 type 5463: installation and service guide.

  • Page 841: 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 842

    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 843

    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 844

    Table 43. 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 845

    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 846

    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 847

    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 848

    Japan electronics and information technology industries association (jeita) statement japan electronics and information technology industries association (jeita) confirmed harmonics guidelines with modifications (products greater than 20 a per phase) korea communications commission (kcc) statement t...

  • Page 849

    Taiwan class a compliance statement notices 833.

  • Page 850

    834 ibm system x3550 m5 type 5463: installation and service guide.

  • Page 851

    Power cord safety statement attention: use no. 26 awg or larger ul-listed or csa certified telecommunication line cord. © copyright ibm corp. 2014 835.

  • Page 852

    836 ibm system x3550 m5 type 5463: installation and service guide.

  • Page 853: Index

    Index numerics 2.5-inch hot-swap rear hard disk drive kit removing 148 replacing 150 a abr, automatic boot recovery 108 ac power-supply leds 70 ac power-supply leds 70 accessible documentation 828 acoustical noise emissions 7 active energy manager plug-in 12 active memory 12 adapter removing 177 rep...

  • Page 854

    Embedded hypervisor using 51 enabling features on demand ethernet software 52 raid software 52 enterprise x-architecture technology 12 error codes and messages imm2 269 error messages 80 error symptoms dvd drive 81 general 82 hard disk drive 82 hypervisor flash device 84 intermittent 85 keyboard 85 ...

  • Page 855

    Led (continued) hard disk drive status 18 imm heartbeat 71 power-on 20 system information 20 system locator 20 system-error 20 leds ac power-supply 70 pci riser-card 72 power-supply 69 system board 30 legacy operating system requirement 39 license agreement for machine code 6 licenses and attributio...

  • Page 856

    Removing (continued) hot-swap hard disk drive 143 hot-swap hard disk drive backplane 201 lcd system information display panel 239 media cage 222 memory module 164 microprocessor 247 operator information panel assembly 234 pci riser-card assembly 170 power supply 196 raid adapter battery 130 raid ada...

  • Page 857

    Telecommunication regulatory statement 828 telephone numbers 823 test log, viewing 79 thermal grease 258 thermal kit, hot-swap fan removing 194 replacing 195 tools, call home 80 tools, diagnostic 66 trademarks 826 troubleshooting 61 symptom 80 turning off the server 32 turning on the server 31 u uef...

  • Page 858

    842 ibm system x3550 m5 type 5463: installation and service guide.

  • Page 860

    Part number: 00fl592 printed in usa (1p) p/n: 00fl592.