- DL manuals
- IBM
- Server
- x3550 M4 Type 7914
- Installation And Service Manual
IBM x3550 M4 Type 7914 Installation And Service Manual
Summary of x3550 M4 Type 7914
Page 1
Ibm system x3550 m4 type 7914 installation and service guide.
Page 3
Ibm system x3550 m4 type 7914 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 829, “notices” on page 833, the warranty information document, and the safety information and environmental notices and user guide documents on...
Page 5
Contents safety . . . . . . . . . . . . . . . Vii guidelines for trained service technicians . . . . Ix inspecting for unsafe conditions . . . . . . Ix guidelines for servicing electrical equipment . . X safety statements . . . . . . . . . . . . Xi chapter 1. The ibm system x3550 m4 server . . . . ....
Page 6
Installing updates with your management server is connected to the internet . . . . 121 installing updates with your management server is not connected to the internet . . . 121 updating the universal unique identifier (uuid) . . . . . . . . . . . . . . 122 updating the dmi/smbios data . . . . . . 1...
Page 7
Replacing a serveraid sas/sata controller 255 removing the serveraid adapter memory module . . . . . . . . . . . . . 260 replacing the serveraid adapter memory module . . . . . . . . . . . . . 261 removing the dual-port network adapter . . 262 replacing the dual-port network adapter . . 263 removing...
Page 8
Vi ibm system x3550 m4 type 7914: installation and service guide.
Page 9
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
Guidelines for trained service technicians this section contains information for trained service technicians. Inspecting for unsafe conditions use this information to help you identify potential unsafe conditions in an ibm ® product that you are working on. Each ibm product, as it was designed and m...
Page 12
Guidelines for servicing electrical equipment observe these guidelines when you service electrical equipment. V check the area for electrical hazards such as moist floors, nongrounded power extension cords, and missing safety grounds. V use only approved tools and test equipment. Some hand tools hav...
Page 13
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 14
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 cont...
Page 15
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 16
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 17
Caution: do not place any object on top of rack-mounted devices. Statement 27 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 serve...
Page 18
Xvi ibm system x3550 m4 type 7914: installation and service guide.
Page 19
Chapter 1. The ibm system x3550 m4 server this publication contains information and instructions for setting up your ibm system x3550 m4 server, instructions for installing some optional devices, cabling and configuring the server, removing and replacing devices, and diagnostics and troubleshooting ...
Page 20
Note: the illustrations in this document might differ slightly from your model. The following illustration shows the 2.5-inch hot-swap server models with an optional optical drive bay. The following illustration shows the 3.5-inch hot-swap or simple-swap server models. The servers support up to thre...
Page 21
Note: the illustrations in this document might differ slightly from your hardware. In addition, the system service label, which is on the cover of the server, provides a qr code for mobile access to service information. You can scan the qr code using a qr code reader and scanner with a mobile device...
Page 22
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 23
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 24
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 25
Table 1. Server features and specifications microprocessor (depending on the model): v supports up to two multi-core microprocessors (one installed) v level-3 cache v two quickpath interconnect (qpi) links speed up to 8.0 gt per second notes: v use the setup utility program to determine the type and...
Page 26
Table 1. Server features and specifications (continued) video controller (integrated into imm2): v matrox g200er2 note: the maximum video resolution is 1600 x 1200 at 75 hz. – svga compatible video controller – ddr3 528 mhz sdram video memory controller – avocent digital video compression – 16 mb of...
Page 27
Table 1. Server features and specifications (continued) environment: compliant with ashrae class a3 specifications. Server on : v temperature: – 5°c to 40°c (41°f to 104°f) – altitude: 0 to 950 m (3,117 ft); decrease the maximum system temperature by 1°c for every 175-m increase in altitude. V maxim...
Page 28
Http://www.Ibm.Com/customersupport/ for more information on the energy efficiency program, go to http://www.Ibm.Com/systems/x/hardware/energy-star/index.Html product type: computer server year first manufactured: 2012 internal/external power supply efficiency: v http://www.Plugloadsolutions.Com/psu_...
Page 29
What your server offers this section introduces features and technologies the server uses and provides. V active energy manager the ibm active energy manager solution is an ibm systems director plug-in that measures and reports server power consumption as it occurs. This enables you to monitor power...
Page 30
The problem. Optionally, the imm also provides a virtual presence capability for remote server management capabilities. The imm provides remote server management through the following industry-standard interfaces: – intelligent platform management interface (ipmi) version 2.0 – simple network manage...
Page 31
The server supports up to two multi-core microprocessors. The server comes with a minimum of one microprocessor. V pci adapter capabilities the server has two pci interface slots (one supports low-profile cards, and one supports half-length, full-height cards). Slot 2 can support pci express or pci-...
Page 32
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 33
V power management: compliance with advanced configuration and power interface (acpi) v power-on self-test (post) v predictive failure analysis (pfa) alerts on memory, microprocessors, sas/sata hard disk drives or solid state drives, fans, power supplies, and vrm v redundant ethernet capabilities wi...
Page 34
The ibm systems director web and command-line interfaces provide a consistent interface that is focused on driving these common tasks and capabilities: v discovering, navigating, and visualizing systems on the network with the detailed inventory and relationships to the other network resources v not...
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 advanced operator information panel and the operator information panel depending on your server model. V power-control button and power-on led: press this button to turn the server on and off manually. The state...
Page 37
V system-error led: when this yellow led is lit, it indicates that a system error has occurred. A system-error led is also on the rear of the server. An led on the light path diagnostics panel on the operator information panel or on the system board is also lit to help isolate the error. This led is...
Page 38
The following illustration shows the leds and controls on the light path diagnostics panel. V remind button: this button places the system-error led on the operator information panel into remind mode. In remind mode, the system-error led flashes once every 2 seconds until the problem is corrected, t...
Page 39
V nmi button: press this button to force a nonmaskable interrupt to the microprocessor. It allows you to blue screen the server and take a memory dump (use this button only when directed by the ibm service support). You might have to use a pen or the end of a straightened paper clip to press the but...
Page 40
V ethernet activity leds: when these leds are lit, they indicate that the server is transmitting to or receiving signals from the ethernet lan that is connected to the ethernet port. V ethernet link leds: when these leds are lit, they indicate that there is an active link connection on the 10base-t,...
Page 41
Flashing slowly (once per second): the server is turned off and is ready to be turned on. You can press the power-control button to turn on the server. Lit: the server is turned on. V system-locator led: use this led to visually locate the server among other servers. You can use ibm systems director...
Page 42
Turning off the server use this information to turn off the server. When you turn off the server and leave it connected to power, the server can respond to requests to the service processor, such as a remote request to turn on the server. While the server remains connected to power, one or more fans...
Page 43
Chapter 2. Installing optional devices this section provides detailed instructions for installing optional hardware devices in the server. In addition to the instructions in this chapter for installing optional hardware devices, updating the firmware and device drivers, and completing the installati...
Page 44
Instructions for ibm business partners in addition to the instructions in this section for installing optional hardware devices, updating firmware and device drivers, and completing the installation, ibm business partners must also complete the following steps. 1. After you have confirmed that the s...
Page 45
Blue on a component indicates touch points, where you can grip the component to remove it from or install it in the server, open or close a latch, and so on. Orange on a component or an orange label on or near a component indicates that the component can be hot-swapped, which means that if the serve...
Page 46
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. Figure 15. System-board internal connectors 28 ibm system x3550 m4 type 7914: ...
Page 47
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 48
The following table describes the jumpers on the system board. Table 2. System board jumpers jumper number jumper name jumper setting jp1 cmos clear jumper v pins 1 and 2: normal (default). V pins 2 and 3: clears the real-time clock (rtc) registry. Jp2 uefi boot backup jumper v pins 1 and 2: normal ...
Page 49
The following table describes the functions of the sw3 switch block on the system board. Table 3. System board sw3 switch block definition switch number default position description 1 off reserved. 2 off reserved. 3 off reserved. 4 off power-on password override. Changing the position of this switch...
Page 50
System-board leds the following illustration shows the light-emitting diodes (leds) on the system board. System-board optional-device connectors the following illustration shows the connectors on the system board for the optional devices. Figure 18. System-board leds 32 ibm system x3550 m4 type 7914...
Page 51
Installation guidelines use this information for installation. Attention: static electricity that is released to internal server components when the server is powered-on might cause the system to halt, which might result in the loss of data. To avoid this potential problem, always use an electrostat...
Page 52
For additional information about tools for updating, managing, and deploying firmware, see the toolscenter for system x and bladecenter at http://publib.Boulder.Ibm.Com/infocenter/toolsctr/v1r0/. V before you install optional hardware, make sure that the server is working correctly. Start the server...
Page 53
System reliability guidelines to help ensure proper system cooling and system reliability, make sure that the following requirements are met. V each of the drive bays has a drive or a filler panel and electromagnetic compatibility (emc) shield installed in it. V each of the power-supply bays has a p...
Page 54
Handling static-sensitive devices use this information to handle static-sensitive devices. Attention: static electricity can damage the server and other electronic devices. To avoid damage, keep static-sensitive devices in their static-protective packages until you are ready to install them. To redu...
Page 55
5. 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. Removing the air baffle use this information to remove the air baffle. About this task to remove the air baffle, complete the following steps: ...
Page 56
5. Remove the air baffle from the server and set it aside. Attention: for proper cooling and airflow, replace the air baffle before you turn on the server. Operating the server with the air baffle removed might damage server components. Installing drives the following notes describe the type of hard...
Page 57
Drive ids the drive id that is assigned to each drive is printed on the front of the server. The following illustrations show the locations of the ids of the drives. The id numbers and the drive bay numbers are the same. 2.5-inch hot-swap hard disk drive ids the hot-swap-drive id that is assigned to...
Page 58
2.5-inch simple-swap hard disk drive ids the simple-swap-drive id that is assigned to each drive is printed on the front of the server. The following illustration shows the location of the ids of the hard disk drives. The id numbers and the drive bay numbers are the same. 3.5-inch simple-swap hard d...
Page 59
4. Install the hard disk drive in the drive bay: a. Make sure that the tray handle is in the open (unlocked) position. B. Align the drive with the guide rails in the bay. C. Gently push the drive into the bay until the drive stops. D. Rotate the tray handle to the closed (locked) position. E. Check ...
Page 60
V you can install up to three 3.5-inch simple-swap sata hard disk drives in the server. Do not install hot-swap drives into a simple-swap server model, it is not supported. V you can install one 2.5-inch simple-swap sata hard disk drives in bay 0 in the server. Do not install hot-swap drives into a ...
Page 61
B. Gently push the drive into the bay until the drive stops. 6. Reinstall the drive bay filler panel that you removed earlier. 7. If you are installing additional simple-swap hard disk drives, do so now. Results if you have other devices to install or remove, do so now. Otherwise, go to “completing ...
Page 62
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 optical drive that contains a laser, observe the following safety precautions. Statement 3 caution: when laser products (such as cd-roms, dvd drive...
Page 63
Danger some laser products contain an embedded class 3a or class 3b laser diode. Note the following. Laser radiation when open. Do not stare into the beam, do not view directly with optical instruments, and avoid direct exposure to the beam. Class 1 laser product laser klasse 1 laser klass 1 luokan ...
Page 64
10. Connect the dvd drive cable (see “replacing the dvd drive cable” on page 233). The following illustration shows the cable routing for the dvd drive: figure 31. Dvd drive installation 46 ibm system x3550 m4 type 7914: installation and service guide.
Page 65
Results if you have other devices to install or remove, do so now. Otherwise, go to “completing the installation” on page 96. Installing an optional dvd drive cable use this information to install an optional dvd drive cable. About this task to install the dvd drive cable, complete the following ste...
Page 66
To the left until it is firmly seated. The following illustration shows cable routing for the dvd cable: attention: follow the optical drive cable routing as the illustration shows. Make sure that the cable is not pinched and does not cover any connectors or obstruct any components on the system boa...
Page 67
Results if you have other devices to install or remove, do so now. Otherwise, go to “completing the installation” on page 96. Installing a memory module the following notes describe the types of dimms that the server supports and other information that you must consider when you install dimms. V whe...
Page 68
- ggggg is the total capacity of the dimm (for example, 1 gb, 2 gb, or 4 gb) - er is the number of ranks 1r = single-rank 2r = dual-rank 4r = quad-rank - xff is the device organization (bit width) x4 = x4 organization (4 dq lines per sdram) x8 = x8 organization x16 = x16 organization - v is the sdra...
Page 69
V the maximum memory speed is determined by the combination of the microprocessor, dimm speed, dimm type, operating modes in uefi settings, and the number of dimms installed in each channel. V in two-dimm-per-channel configuration, the server automatically operates with a maximum memory speed of up ...
Page 70
V dimms in the server must be the same type (rdimm, udimm, or lrdimm) to ensure that the server will operate correctly. V when you install one quad-rank dimm in a channel, install it in the dimm connector furthest away from the microprocessor. Notes: 1. You can install dimms for microprocessor 2 as ...
Page 71
Memory mirrored channel memory mirrored channel mode replicates and stores data on two pairs of dimms within two channels simultaneously. If a failure occurs, the memory controller switches from the primary pair of memory dimms to the backup pair of dimms. To enable memory mirrored channel through t...
Page 72
Table 7. Memory mirrored channel mode dimm population sequence (continued) number of dimms number of installed microprocessor dimm connector table note: dimm connectors 3, 6, 7, 10, 15, 18, 19, and 22 are not used in memory mirrored channel mode when udimms are installed in the server. Memory rank s...
Page 73
Installing a memory module use this information to install a memory module. About this task procedure 1. Read the safety information that begins on “safety” on page vii and “installation guidelines” on page 33. 2. Turn off the server and peripheral devices and disconnect the power cords and all exte...
Page 74
Results if you have other devices to install or remove, do so now. Otherwise, go to “completing the installation” on page 96. Installing 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. Ab...
Page 75
Table 10. Adapter configurations (continued) description option part number pci riser 1 pci riser 2 ibm 600gb high iops mlc modular adapter 90y4365 six fans installed required 1 six fans installed required 1 ibm 800gb high iops mlc modular adapter 90y4369 six fans installed required 1 six fans insta...
Page 76
Table 11. Pci riser slots supported configurations pci riser-card slot number configuration 1 configuration 2 (two microprocessors installed) configuration 3 slot 1 pci express 3.0 (x16) card with a pci express riser card with a standard bracket pci express 3.0 (x16) card with a pci express riser ca...
Page 77
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 78
Installing a serveraid sas/sata controller use this information to install a serveraid sas/sata controller. About this task note: for brevity, in this documentation the serveraid sas/sata controller is often referred to as the sas/sata adapter or the serveraid adapter. The serveraid sas/sata control...
Page 79
Note: remove the pci bracket that come with serveraid h1110, serveraid m1115, or serveraid m5110 sas/sata adapter before installing a sas/sata adapter in the dedicated connector on the system board. B. Insert the sas/sata adapter into the pci riser cards (see “replacing an adapter” on page 250). 8. ...
Page 80
9. Connect the signal cables to the sas/sata adapter: a. Serveraid h1110 adapter : take the signal cable that is attached to the drive backplane for drive bays 0 through 3 and connect it to the sas/sata connector on the serveraid adapter. Figure 43. Serveraid adapter cable routing figure 44. Servera...
Page 81
B. Serveraid m1115 adapter : take the signal cable that is attached to the drive backplane for drive bays 4 through 7 and connect it to the serveraid adapter connector for drive bays 4 through 7 (port 1). Connect the other signal cable that is attached to the drive backplane for drive bays 0 through...
Page 82
Installing the serveraid adapter memory module use this information to install 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 “installa...
Page 83
Installing a raid adapter battery or flash power module when you install any raid adapter that comes with batteries or flash power modules, it is sometimes necessary to install the batteries or flash power modules in another location in the server to prevent the batteries or flash power modules from...
Page 84
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 battery holder before opening the battery holder. 8. Install the battery or flash power module: a. Release the retentio...
Page 85
Note: the positioning of the battery or flash power module depends on the type of the battery or flash power module that you install. C. Connect the other end of the cable to the battery or flash power module. D. Lower and press down on the retention clip until it snaps in place to hold the battery ...
Page 86
Installing the dual-port network adapter you can purchase one of the following dual-port network adapters to add two additional network ports in the server. About this task to order a dual-port network adapter option, contact your ibm sales representative or ibm reseller. Table 12. Supported dual-po...
Page 87
V to download the latest version of drivers for iscsi and fcoe from the ibm website, complete the following steps: 1. Go to http://www.Ibm.Com/support/fixcentral/. 2. Click product support > system x > product family > system x3550 m4 > 7914 . 3. From the operating system menu, select your operating...
Page 88
6. Touch the static-protective package that contains the new adapter to any unpainted metal surface on the server. Then, remove the adapter from the package. 7. Align the adapter so that the port connectors on the adapter line up with the pin and thumbscrew on the chassis; then, align the connector ...
Page 89
8. Press the adapter firmly until the pin, and retention brackets engage the adapter. Make sure the adapter is securely seated on the connector on the system board. Attention: make sure the port connectors on the adapter are aligned properly with the chassis on the rear of the server. An incorrectly...
Page 90
Installing a hot-swap ac power supply use this information to install a hot-swap ac power supply. About this task the following notes describe the type of power supply that the server supports and other information that you must consider when you install a power supply: v before you install an addit...
Page 91
Caution: never remove the cover on a power supply or any part that has the following label attached. Hazardous voltage, current, and energy levels are present inside any component that has this label attached. There are no serviceable parts inside these components. If you suspect a problem with one ...
Page 92
7. Connect the other end of the power cord to a properly grounded electrical outlet. 8. Make sure that the ac power led and the dc power led on the ac power supply are lit, indicating that the power supply is operating correctly. The two green leds are to the right of the power-cord connector. 9. If...
Page 93
Installing a hot-swap dc power supply observe the following precautions when you install a hot-swap dc power supply. The following notes describe the type of power supply that the server supports and other information that you must consider when you install a power supply: v before you install an ad...
Page 94
V this equipment shall be connected directly to the dc supply system earthing electrode conductor or to a bonding jumper from an earthing terminal bar or bus to which the dc supply system earthing electrode conductor is connected. V this equipment shall be located in the same immediate area (such as...
Page 95
Danger electrical current from power, telephone, and communication cables is hazardous. To avoid a shock hazard: v do not connect or disconnect any cables or perform installation, maintenance, or reconfiguration of this product during an electrical storm. V connect all power cords to a properly wire...
Page 96
Statement 34 caution: to reduce the risk of electric shock or energy hazards: v this equipment must be installed by trained service personnel in a restricted-access location, as defined by the nec and iec 60950-1, first edition, the standard for safety of information technology equipment. V connect ...
Page 97
Installing a hot-swap dc power supply to install a hot-swap dc power supply, complete the following steps. About this task attention: only trained service personnel other than ibm service technicians are authorized to install and remove the -48 volt dc power supply, and make the connections to and d...
Page 98
6. 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. 7. Route the power cord through the handle and cable tie if any, so that it does not acci...
Page 99
12. If you are adding a power supply to the server, attach the redundant power information label that comes with this option on the server cover near the power supplies. Installing a hot-swap fan use this information to install a hot-swap fan. About this task the server comes standard with four dual...
Page 100
5. Orient the fan over the fan slot in the fan assembly bracket so that the fan connector aligns with the connector on the system board. Figure 60. Fan installation 82 ibm system x3550 m4 type 7914: installation and service guide.
Page 101
6. Insert the fan into the fan slot in the fan assembly bracket and press it down until it is seated correctly in the slot and the fan connector is seated correctly in the connector on the system board. Note: make sure that the newly-installed fan aligns horizontally with other correctly-seated fans...
Page 102
A. Align the flash device with the connector on the system board and push it into the usb connector until it is firmly seated. B. Press down on the retention latch to lock the flash device into the usb connector. Results if you have other devices to install or remove, do so now. Otherwise, go to “co...
Page 103
V do not use any tools or sharp objects to lift the locking levers on the microprocessor socket. Doing so might result in permanent damage to the system board. V each microprocessor socket must always contain either a socket cover or a microprocessor and heat sink. V be sure to use only the installa...
Page 104
V to order an additional optional microprocessor, contact your ibm sales representative or ibm reseller. There are two types of microprocessor installation tools. The tools are similar in function and design, however tool a has one setting for installing one size of microprocessor, and supports the ...
Page 105
6. 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 106
C. Align the installation tool with the microprocessor socket. The installation tool rests flush on the socket only if properly aligned. D. Install the microprocessor using the following instructions for your installation tool. V if using installation tool a, twist the handle on the microprocessor t...
Page 107
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 108
Attention: when you handle static-sensitive devices, take precautions to avoid damage from static electricity. For details about handling these devices, see “handling static-sensitive devices” on page 36. 9. Close the microprocessor socket release levers and retainer: a. Close the microprocessor ret...
Page 109
A. Remove the plastic protective cover from the bottom of the heat sink. B. Position the heat sink over the microprocessor. The heat sink is keyed to assist with proper alignment. C. Align and place the heat sink on top of the microprocessor in the retention bracket, thermal material side down. D. P...
Page 110
Thermal grease the thermal grease must be replaced whenever the heat sink has been removed from the top of the microprocessor and is going to be reused or when debris is found in the grease. About this task when you are installing the heat sink on the same microprocessor that it was removed from, ma...
Page 111
6. Install the heat sink onto the microprocessor. Installing a sas/sata 4 pac hdd option you can install an ibm system x3550 m4 hot-swap sas/sata 4 pac hdd option to add four additional 2.5-inch hot-swap hard disk drives in the server. About this task see http://www.Ibm.Com/systems/info/x86servers/s...
Page 112
7. Install the filler panels that come with the sas/sata 4 pac hdd option into empty drive bays. Results if you have other devices to install or remove, do so now. Otherwise, go to “completing the installation” on page 96. Installing the operator information panel assembly use this information to in...
Page 113
The following notes describe additional information when you install the cable: v to connect the operator information panel cable on the system board, press evenly on the cable. Pressing on one side of the cable might cause damage to the cable or connector. V the operator information panel cable mus...
Page 114
Completing the installation use this information to complete the installation. About this task to complete the installation, complete the following steps: procedure 1. If you removed the air baffle, reinstall it (see “replacing the air baffle”). 2. If you removed the server cover, replace it (see “r...
Page 115
Replacing the cover use this information to replace the cover. About this task to replace the server cover, complete the following steps: procedure 1. Make sure that all cables, adapters, and other components are installed and seated correctly and that you have not left loose tools or parts inside t...
Page 116
6. Slide the server all the way into the rack until it latches. Connecting the cables the following illustrations show the locations of the input and output connectors of the server. Figure 80. Cover installation figure 81. 2.5-inch model front of server figure 82. 3.5-inch model front of server 98 ...
Page 117
You must turn off the server before you connect or disconnect cables. See the documentation that comes with any external devices for additional cabling instructions. It might be easier for you to route cables before you connect the devices to the server. Updating the server configuration when you st...
Page 118
100 ibm system x3550 m4 type 7914: installation and service guide.
Page 119
Chapter 3. 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 120
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 f...
Page 121
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 122
Table 13. Server configuration and applications for configuring and managing raid arrays server configuration raid array configuration (before operating system is installed) raid array management (after operating system is installed) serveraid-h1110 adapter lsi utility (setup utility, press ctrl+c),...
Page 123
Serverguide features this information provides an overview of the serverguide features. Features and functions can vary slightly with different versions of the serverguide program. To learn more about the version that you have, start the serverguide setup and installation cd and view the online over...
Page 124
Typical operating-system installation serverguide typical operating-system installation the serverguide program can reduce the time it takes to install an operating system. It provides the device drivers that are required for your hardware and for the operating system that you are installing. This s...
Page 125
Starting the setup utility use this information to start the setup utility. About this task to start the setup utility, complete the following steps: procedure 1. Turn on the server. Note: approximately 5 to 10 seconds after the server is connected to power, the power-control button becomes active. ...
Page 126
– devices and i/o ports select this choice to view or change assignments for devices and input/output (i/o) ports. You can configure the serial ports, configure remote console redirection, enable or disable integrated ethernet controllers, the sas/sata controllers, sata optical drive channels, pci s...
Page 127
Select this choice to view or reset imm to the default settings. - reset imm select this choice to reset imm. – recovery select this choice to view or change the system recovery parameters. - post attempts select this choice to view or change the number of attempts to post. V post attempts limit sel...
Page 128
Select this choice to view, add, delete, or change the device boot priority, boot from a file, select a one-time boot, or reset the boot order to the default setting. V system event logs select this choice to enter the system event manager, where you can view the post event log and the system-event ...
Page 129
Select this choice to cancel the changes that you have made in the settings and restore the factory settings. V exit setup select this choice to exit from the setup utility. If you have not saved the changes that you have made in the settings, you are asked whether you want to save the changes or ex...
Page 130
Attention: before you change any switch settings or move any jumpers, turn off the server; then, disconnect all power cords and external cables. See the safety information that begins “safety” on page vii. Do not change settings or move jumpers on any system-board switch or jumper blocks that are no...
Page 131
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 132
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 133
V power/reset control (power-on, hard and soft shutdown, hard and soft reset, schedule power control). V query power-supply input power. 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 reada...
Page 134
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 135
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 136
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 28 for th...
Page 137
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 138
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 139
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 140
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 141
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 142
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 143
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 144
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 145
Chapter 4. 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 146
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 147
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 148
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 m4 server. To find service bulletins that are available for the ibm system x3550 m4 server, go to http://www.Ibm.Com/suppo...
Page 149
V for information about power-supply problems, see “solving power problems” on page 175, “power problems” on page 166, and “power-supply leds” on page 141. V for intermittent problems, check the event log; see “event logs” on page 146 and appendix c, “dsa diagnostic test results,” on page 693. Perfo...
Page 150
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 134 for more information. V event logs the event logs list the...
Page 151
- 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 152
10. Fusionio storage 11. Intel gpu 12. Nvidia gpu see “running the dsa preboot diagnostic programs” on page 151 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 “troubleshoo...
Page 153
The following illustration shows the light path diagnostics panel. Note any leds that are lit, and then reinstall the light path diagnostics panel in the server. V remind button: press this button to place the system-error led/check log led on the front information panel into remind mode. By placing...
Page 154
– all known errors are corrected. – the server is restarted. – a new error occurs, causing the system-error led to be lit again. V reset button: press this button to reset the server and run the power-on self-test (post). You might have to use a pen or the end of a straightened paper clip to press t...
Page 155
Light path diagnostics leds this section describes the leds on the light path diagnostics panel and suggested actions to correct the detected problems. For additional information, see “server controls, leds, and power” on page 16 and “system-board leds” on page 32 for the location of the system boar...
Page 156
Table 14. Light path diagnostics panel leds (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. Led...
Page 157
Table 14. Light path diagnostics panel leds (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. Led...
Page 158
Table 14. Light path diagnostics panel leds (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. Led...
Page 159
Table 14. Light path diagnostics panel leds (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. Led...
Page 160
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 161
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. Follow actions in the “power problems” on page 166. 3. If the over spec led on the light path diagnostics is lit...
Page 162
Dc power-supply leds description action notes in ok out ok error (!) on on off normal operation. Off off off no dc power to the server or a problem with the dc power source. 1. Check the dc power to the server. 2. Make sure that the power cord is connected to a functioning power source. 3. Restart t...
Page 163
System pulse leds use this information to diagnose possible errors that are indicated by the system pulse leds. The following leds are on the system board and help you to monitor the system power-on and power-off sequencing and boot progress (see “system-board leds” on page 32 for the location of th...
Page 164
Event logs error codes and messages displayed in post event log, system-event log, integrated management module (imm2) 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 eve...
Page 165
Operating-system event logs. You can view the dsa event log through the dsa program (see “viewing event logs without restarting the server”). For more information about dsa and dsa messages, see “ibm dynamic system analysis” on page 149 and appendix c, “dsa diagnostic test results,” on page 693. Vie...
Page 166
Table 16. Methods for viewing event logs condition action the server is not hung and is connected to a network (using an operating system controlled network ports). Use any of the following methods: v run dsa portable to view the diagnostic event log (requires ipmi driver) or create an output file t...
Page 167
Clearing the event logs use this information to clear the event logs. About this task to clear the event logs, complete the following steps: note: the post error log is automatically cleared each time the server is restarted. Procedure 1. Turn on the server. 2. When the prompt setup is displayed, pr...
Page 168
For system-specific information about the action that you should take as a result of a message that dsa generates, see appendix c, “dsa diagnostic test results,” on page 693. If you cannot find a problem by using dsa, see “solving undetermined problems” on page 177 for information about testing the ...
Page 169
Running the dsa preboot diagnostic programs use this information to run the dsa preboot diagnostic programs. About this task note: the dsa memory test might take up to 30 minutes to run. If the problem is not a memory problem, skip the memory test. To run the dsa preboot diagnostic programs, complet...
Page 170
Diagnostic text messages diagnostic text messages are displayed while the tests are running. A diagnostic text message contains one of the following results: passed: the test was completed without any errors. Failed: the test detected an error. Aborted: the test could not proceed because of the serv...
Page 171
Ibm electronic service agent ibm electronic service agent monitors, tracks, and captures system hardware errors and hardware and software inventory information, and reports serviceable problems directly to ibm support. You can also choose to collect data manually. It uses minimal system resources, a...
Page 172
Cd/dvd drive problems use this information to solve cd/dvd drive problems. V follow the suggested actions in the order in which they are listed in the action column until the problem is solved. V if an action step is preceded by “(trained technician only),” that step must be performed only by a trai...
Page 173
General problems use this information to solve general problems. 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 techni...
Page 174
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 the ibm support website at http://www.Ibm.Com/suppo...
Page 175
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 the ibm support website at http://www.Ibm.Com/suppo...
Page 176
Intermittent problems use this information to solve intermittent problems. 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 trai...
Page 177
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 the ibm support website at http://www.Ibm.Com/suppo...
Page 178
Memory problems use this information to solve memory problems. V follow the suggested actions in the order in which they are listed in the action column until the problem is solved. V if an action step is preceded by “(trained technician only),” that step must be performed only by a trained technici...
Page 179
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 the ibm support website at http://www.Ibm.Com/suppo...
Page 180
Monitor and video problems use this information to solve monitor and video problems. Some ibm monitors have their own self-tests. If you suspect a problem with your monitor, see the documentation that comes with the monitor for instructions for testing and adjusting the monitor. If you cannot diagno...
Page 181
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 the ibm support website at http://www.Ibm.Com/suppo...
Page 182
Network connection problems use this information to solve network connection problems. 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 on...
Page 183
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 the ibm support website at http://www.Ibm.Com/suppo...
Page 184
Power problems use this information to solve power problems. V follow the suggested actions in the order in which they are listed in the action column until the problem is solved. V if an action step is preceded by “(trained technician only),” that step must be performed only by a trained technician...
Page 185
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 the ibm support website at http://www.Ibm.Com/suppo...
Page 186
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 the ibm support website at http://www.Ibm.Com/suppo...
Page 187
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 the ibm support website at http://www.Ibm.Com/suppo...
Page 188
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 the ibm support website at http://www.Ibm.Com/suppo...
Page 189
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 the ibm support website at http://www.Ibm.Com/suppo...
Page 190
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 the ibm support website at http://www.Ibm.Com/suppo...
Page 191
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 the ibm support website at http://www.Ibm.Com/suppo...
Page 192
Software problems use this information to solve software problems. 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 tech...
Page 193
Video problems use this information to solve video problems. See “monitor and video problems” on page 162. Solving power problems use this information to solve power problems. About this task power problems can be difficult to solve. For example, a short circuit can exist anywhere on any of the powe...
Page 194
Table 17. Components associated with power rail errors (continued) pwr rail error in the imm event log components pwr rail 4 error v pci adapter power cable (if one is installed) v fan 1 v fan 2 v hard disk drives v dimms 7 through 12 pwr rail 5 error v dvd drive (if one is installed) v fan 3 v fan ...
Page 195
– the cable must be securely attached at all connections. If the cable is attached but the problem remains, try a different cable. – if you set the ethernet controller to operate at 100 mbps, you must use category 5 cabling. – if you directly connect two servers (without a hub), or if you are not us...
Page 196
Procedure 1. Turn off the server. 2. Make sure that the server is cabled correctly. 3. Remove or disconnect the following devices, one at a time, until you find the failure. Turn on the server and reconfigure it each time. V any external devices. V surge-suppressor device (on the server). V printer,...
Page 197
– is the failure repeatable? – has this configuration ever worked? – what changes, if any, were made before the configuration failed? – is this the original reported failure? V diagnostic program type and version level v hardware configuration (print screen of the system summary) v uefi firmware lev...
Page 198
The flash memory of the server consists of a primary bank and a backup bank. You must maintain a bootable uefi firmware image in the backup bank. If the server firmware in the primary bank becomes corrupted, you can either manually boot the backup bank with the uefi boot backup jumper (jp2), or in t...
Page 199
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 supported by the firmware update package that you downloaded. 9. Perform the firmware update by following the inst...
Page 200
Out-of-band method use this information to recover the server firmware and restore the server operation to the primary bank. See the imm2 documentation (integrated management module ii user's guide) at http://www.Ibm.Com/support/entry/portal/docdisplay?Lndocid=migr-5086346. Automated boot recovery (...
Page 201
Chapter 5. Parts listing, ibm system x3550 m4 type 7914 the following replaceable components are available for the ibm system x3550 m4 type 7914 server. For an updated parts listing, go to http://www.Ibm.Com/supportportal/. Replaceable server components replaceable components consist of consumable p...
Page 202
The following table lists the part numbers for the server replaceable components. Figure 94. Server components 184 ibm system x3550 m4 type 7914: installation and service guide.
Page 203
Table 18. Parts listing, type 7914 index description cru part number (tier 1) cru part number (tier 2) 2 mellanox connectx-3 dual-port qdr/fdr10 mezz card 90y4956 2 qlogic dual-port 10gbe sfp+ embedded vfa 90y5099 2 emulex dual-port 10gbe sfp+ embedded vfa iii 90y5100 2 emulex dual port 10gbe sfp+ e...
Page 204
Table 18. Parts listing, type 7914 (continued) index description cru part number (tier 1) cru part number (tier 2) 7 serveraid m5110 sas/sata adapter 00ae807 7 serveraid m5120 sas/sata adapter 00ae811 7 serveraid m5210 sas/sata adapter 46c9111 9 power supply (acbel), 550 watt, ac 94y8105 9 power sup...
Page 205
Table 18. Parts listing, type 7914 (continued) index description cru part number (tier 1) cru part number (tier 2) 17 solid state drive, 2.5-inch simple-swap, sata, 128 gb 90y8669 17 solid state drive, 2.5-inch simple-swap, sata, 200 gb 43w7745 17 solid state drive, 2.5-inch simple-swap, sata, 240 g...
Page 206
Table 18. Parts listing, type 7914 (continued) index description cru part number (tier 1) cru part number (tier 2) 23 system board (server base assembly for use with intel xeon processor e5-2600 series) type 7914 - a2y, b2y, c2y, c4y, d2y, 52y,62y, e1y, e2y, e3y, e4y, e5y, eay, eby, ecy, edy, f2y, g...
Page 207
Table 18. Parts listing, type 7914 (continued) index description cru part number (tier 1) cru part number (tier 2) 25 microprocessor, intel e5-2690 v2, 3.0 ghz, 25 mb, 1866 mhz 130 w (10-core) 00y2787 25 microprocessor, intel e5-2697 v2, 2.7 ghz, 30 mb, 1866 mhz, 130 w (12-core) 00y2777 25 microproc...
Page 208
Table 18. Parts listing, type 7914 (continued) index description cru part number (tier 1) cru part number (tier 2) hba 4gb fc pcie dual-port adapter 00y5627 netxtreme ii 1000 express ethernet adapter 39y6070 intel pro/1000 pf server adapter 42c1752 qlogic 10gb cna converged network adapter (cna) 42c...
Page 209
Table 18. Parts listing, type 7914 (continued) index description cru part number (tier 1) cru part number (tier 2) bracket assembly, rear i/o 94y7567 cable, power cord 39m5377 cable, mini sas 1 m 39r6530 cable, mini sas 3 m 39r6532 cable, mini sas 610 mm 00y8634 cable, sas 610 mm 00d3276 cable, mini...
Page 210
Table 18. Parts listing, type 7914 (continued) index description cru part number (tier 1) cru part number (tier 2) labels, chassis 94y7604 labels, system service and fru/cru (2.5-inch) 94y7605 half high lto gen 3 sas tape drive 46x5663 half high lto gen 4 sas tape drive 46x5672 half high lto gen 5 s...
Page 211
Table 19. Structural parts, type 7914 (continued) index description part number slide rail kit, universal 94y6719 miscellaneous parts kit includes: cable clip (front, internal) cable retainer (rear, external) dvd filler dvd retention bracket ibm logo (eia bracket) fan filler m2.5x3.5 screw m3x0.5 sc...
Page 212
For units intended to be operated at 230 volts (outside the u.S.): use a cord set with a grounding-type attachment plug. The cord set should have the appropriate safety approvals for the country in which the equipment will be installed. Power cords for a specific country or region are usually availa...
Page 213
Power cord part number used in these countries and regions 39m5081 110 - 120 v antigua and barbuda, aruba, bahamas, barbados, belize, bermuda, bolivia, caicos islands, canada, cayman islands, colombia, costa rica, cuba, dominican republic, ecuador, el salvador, guam, guatemala, haiti, honduras, jama...
Page 214
196 ibm system x3550 m4 type 7914: installation and service guide.
Page 215
Chapter 6. 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 216
Cabling sas/sata serveraid controller use this information to cable the sas/sata serveraid controller. The following illustrations show the internal routing and connectors for the sas/sata signal cables. Notes: 1. To connect the sas/sata signal cables, make sure that you first connect the signal cab...
Page 217
Cabling backplane use this information to cable the backplane. The following illustration shows the internal routing and connectors for the 3.5-inch simple-swap hard disk drives sata signal and power cables. Figure 97. Serveraid-m5110 cable connection chapter 6. Removing and replacing components 199.
Page 218
The following illustration shows the internal routing and connectors for the 3.5-inch hot-swap hard disk drives sas/sata signal, power and configuration cables with the sas/sata adapter installed. Figure 98. 3.5-inch simple-swap backplate assembly cable connection 200 ibm system x3550 m4 type 7914: ...
Page 219
The following illustration shows the internal routing and connectors for the sas/sata signal, power and configuration cables with the sas/sata adapter installed. Figure 99. 3.5-inch hot-swap backplane cable connection chapter 6. Removing and replacing components 201.
Page 220
Cabling raid adapter battery or flash power module use this information to cable the raid adapter battery or flash power module. The following illustration shows the internal routing and connectors for the raid adapter battery or flash power module cable with the raid adapter memory module installed...
Page 221
Cabling specpower use this information to cable the specpower. The following illustration shows the internal routing and connectors for the server models with one 2.5-inch simple-swap hard disk drives. Figure 101. Raid adapter battery or flash power module cable connection chapter 6. Removing and re...
Page 222
Cabling dvd drive the internal routing and connectors for the dvd drive. Notes: 1. To disconnect the optional optical drive cable, you must first press the connector release tab, and then disconnect the cable from the connector on the system board. Do not disconnect the cable by using excessive forc...
Page 223
Cabling operator information panel the internal routing and connectors for the operator information panel. The following notes describe additional information you must consider when you install or remove the operator information panel cable: v to remove the operator information panel cable, slightly...
Page 224
Cabling front usb and video connector the internal routing and connectors for the front usb and video cables. The following notes describe additional information you must consider when you install or remove the front usb and video cables: v to remove the front usb and video cables, slightly press th...
Page 225
Removing and replacing server components this section provides information for removing and replacing components in the server. Removing and replacing structural parts replacement of structural parts is your responsibility. If ibm installs a structural part at your request, you will be charged for t...
Page 226
Removing the cover use this information to remove the cover. About this task to remove the server cover, complete the following steps: procedure 1. Read the safety information that begins on “safety” on page vii and “installation guidelines” on page 33. 2. Turn off the server and peripheral devices ...
Page 227
Replacing the cover use this information to replace the cover. About this task to replace the server cover, complete the following steps: procedure 1. Make sure that all cables, adapters, and other components are installed and seated correctly and that you have not left loose tools or parts inside t...
Page 228
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 33. 2. Turn off the server and peripheral ...
Page 229
Replacing the air baffle use this information to replace the air baffle. About this task to install 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 33. 2. Turn off the server and peripher...
Page 230
Removing a raid adapter battery or flash power module use this information to remove a remotely installed raid adapter battery or flash power module. About this task if a raid adapter battery or flash power module is installed near the fan cage and you need to replace it, complete the following step...
Page 231
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 232
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: a. Release the retention clip in the op...
Page 233
Note: the positioning of the battery or flash power module depends on the type of the battery or flash power module that you install. C. Connect the other end of the cable to the battery or flash power module. D. Lower and press down on the retention clip until it snaps in place to hold the battery ...
Page 234
Removing a raid adapter battery or flash power module holder use this information to remove a raid adapter battery or flash power module holder. About this task if a raid adapter battery or flash power module is installed remotely near the fan cage and you need to replace it, complete the following ...
Page 235
Replacing a raid adapter battery or flash power module holder use this information to replace a raid adapter battery or flash power module holder. About this task to install a raid adapter battery or flash power module holder, complete the following steps: procedure 1. Read the safety information th...
Page 236
6. Slide the server into the rack. 7. Reconnect the power cords and all external cables, and turn on the server and peripheral devices. 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 inst...
Page 237
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 238
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 239
3.5-inch hot-swap hard disk drive ids: the hot-swap-drive id that is assigned to each drive is printed on the front of the server. The following illustration shows the location of the ids of the hard disk drives. The id numbers and the drive bay numbers are the same. Figure 117. 2.5-inch hot-swap ha...
Page 240
Removing simple-swap hard disk drives use this information to remove simple-swap hard disk drives. About this task you must turn off the server before removing simple-swap drives from the server. To remove a simple-swap sata hard disk drive, complete the following steps. Attention: v to avoid damage...
Page 241
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 simple-swap hard disk drives. About this task you must turn off the ...
Page 242
B. Gently push the drive into the bay until the drive stops. 6. Reinstall the drive bay filler panel that you removed earlier. 7. If you are installing additional simple-swap hard disk drives, do so now. 8. Turn on the peripheral devices and the server. Drive ids: the drive id that is assigned to ea...
Page 243
3.5-inch simple-swap hard disk drive ids: the simple-swap-drive id that is assigned to each drive is printed on the front of the server. The following illustration shows the location of the ids of the hard disk drives. The id numbers and the drive bay numbers are the same. Removing a dvd drive use t...
Page 244
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 228. 7. Slide the dvd drive...
Page 245
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. Replacing a dvd drive use this information to replace a dvd drive. About this task the following notes describe the type of drives that the serv...
Page 246
3. Remove the cover (see “removing the cover” on page 36). 4. Remove the dvd drive filler panel if it is installed. Locate the blue release tab on the rear of the dvd drive filler panel; then, while you press the tab, push the dvd drive filler panel out of the drive bay. 5. Remove the retention clip...
Page 247
Danger some laser products contain an embedded class 3a or class 3b laser diode. Note the following. Laser radiation when open. Do not stare into the beam, do not view directly with optical instruments, and avoid direct exposure to the beam. Class 1 laser product laser klasse 1 laser klass 1 luokan ...
Page 248
10. Connect the dvd drive cable (see “replacing the dvd drive cable” on page 233). The following illustration shows the cable routing for the dvd drive: figure 130. Dvd drive installation 230 ibm system x3550 m4 type 7914: installation and service guide.
Page 249
11. Reconnect the power cords and any cables that you removed. 12. 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 250
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. 6. From the rear of the dvd drive cage, press and hold the connector latch (on the left of the cable connector) and gr...
Page 251
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 252
The following illustration shows cable routing for the dvd cable: attention: follow the optical drive cable routing as the illustration shows. Make sure that the cable is not pinched and does not cover any connectors or obstruct any components on the system board. Figure 134. Dvd drive cable latch 2...
Page 253
6. Replace the air baffle (see “replacing the air baffle” on page 211). 7. Replace the cover (see “replacing the cover” on page 209). 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. Figure 135. Dvd dr...
Page 254
Removing a memory module use this information to remove a memory module. About this task to remove a dual inline memory module (dimm), complete the following steps: procedure 1. Read the safety information that begins on “safety” on page vii and “installation guidelines” on page 33. 2. Turn off the ...
Page 255
Installing a memory module the following notes describe the types of dimms that the server supports and other information that you must consider when you install dimms. V when you install or remove dimms, the server configuration information changes. When you restart the server, the system displays ...
Page 256
- bb is the jedec spd revision encoding and additions level - cc is the reference design file for the design of the dimm - d is the revision number of the reference design of the dimm note: to determine the type of a dimm, see the label on the dimm. The information on the label is in the format xxxx...
Page 257
V the rdimm options that are available for the server are 2 gb, 4 gb, 8 gb, and 16 gb. The server supports a minimum of 2 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. The server supports a minimum of 32 gb and a maximum of 7...
Page 258
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 ...
Page 259
Table 22. Memory mirrored channel mode dimm population sequence number of dimms number of installed microprocessor dimm connector first pair of dimms 1 1, 4 second pair of dimms 1 9, 12 third pair of dimms 1 2, 5 fourth pair of dimms 1 8, 11 fifth pair of dimms 1 3, 6 sixth pair of dimms 1 7, 10 sev...
Page 260
Table 23. Memory rank sparing mode dimm population sequence (continued) number of dimms number of installed microprocessor dimm connector third pair of dimms 1 8, 9 fourth pair of dimms 1 11, 12 fifth pair of dimms 1 7, 10 sixth pair of dimms 1 3, 6 seventh pair of dimms 2 13, 14 eighth pair of dimm...
Page 261
6. Touch the static-protective package that contains the dimm to any unpainted metal surface on the outside of the server. Then, remove the dimm from the package. 7. Turn the dimm so that the alignment slot align correctly with the alignment tab. 8. Insert the dimm into the connector by aligning the...
Page 262
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 263
Replacing a pci riser-card assembly use this information to replace 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 install a pci riser-card assembly, complete the following steps: procedure 1. Read the safety infor...
Page 264
Note: support the server from the middle of the rear chassis when installing pci riser-card assembly 2. 9. Replace the cover (see “replacing the cover” on page 209). 10. Slide the server into the rack. 11. Reconnect the power cords and any cables that you removed. 12. Turn on the peripheral devices ...
Page 265
Results if you are instructed to return the pci riser-card bracket, follow all packaging instructions, and use any packaging materials for shipping that are supplied to you. Replacing the pci riser-card bracket to the riser card use this information to replace the pci riser-card bracket to the riser...
Page 266
5. If you need to install an adapter (see “replacing an adapter” on page 250). 6. Reconnect the cables for the adapter. 7. Replace the pci riser card assembly (see “replacing a pci riser-card assembly” on page 245). 8. Replace the cover (see “replacing the cover” on page 209). 9. Slide the server in...
Page 267
4. Grasp the pci riser-card assembly at the blue tabs and lift to remove the pci riser-card assembly. 5. Place the pci riser-card assembly on a flat and static-protective surface. 6. Carefully grasp the adapter by its top edge or upper corners, and pull the adapter from the pci riser-card assembly. ...
Page 268
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 269
Table 25. Adapter configurations (continued) description option part number pci riser 1 pci riser 2 ibm flash adapter f3200 enterprise value 00ae867 not supported six fans installed required 1 qlogic 8200 dual-port 10gbe sfp+ vfa 90y4600 six fans installed required 1 six fans installed required 1 se...
Page 270
Table 26. Pci riser slots supported configurations (continued) pci riser-card slot number configuration 1 configuration 2 (two microprocessors installed) configuration 3 slot 2 pci express 3.0 (x8) card with a pci express riser card with a standard bracket pci express 3.0 (x16) card with a pci expre...
Page 271
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 272
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 28 for th...
Page 273
Note: if you have installed the optional serveraid adapter memory module, remove it and keep it in future use (see “removing the serveraid adapter memory module” on page 260). 8. Pull the sas/sata adapter horizontally out of the connector on the system board. Results if you are instructed to return ...
Page 274
6. Align the sas/sata adapter so that the keys align correctly with the connector on the system board. 7. Insert the sas/sata adapter in the dedicated connector on the system board or pci riser-card slots. Attention: incomplete insertion might cause damage to the server or the adapter. A. Insert the...
Page 275
8. Route the backplane signal cables (see “cabling backplane” on page 199). Figure 152. Adapter installation chapter 6. Removing and replacing components 257.
Page 276
9. Connect the signal cables to the sas/sata adapter: a. Serveraid h1110 adapter : take the signal cable that is attached to the drive backplane for drive bays 0 through 3 and connect it to the sas/sata connector on the serveraid adapter. Figure 153. Serveraid adapter cable routing figure 154. Serve...
Page 277
B. Serveraid m1115 adapter : take the signal cable that is attached to the drive backplane for drive bays 4 through 7 and connect it to the serveraid adapter connector for drive bays 4 through 7 (port 1). Connect the other signal cable that is attached to the drive backplane for drive bays 0 through...
Page 278
Results note: when you restart the server, you are prompted to import the existing raid configuration to the new serveraid adapter. 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 ...
Page 279
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 280
Removing the dual-port network adapter use this information to remove the dual-port network adapter. About this task to remove the dual-port network adapter, complete the following steps: procedure 1. Read the safety information that begins on “safety” on page vii and “installation guidelines” on pa...
Page 281
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. Replacing the dual-port network adapter you can purchase one of the following dual-port network adapters to add two additional network ports ...
Page 282
Table 27. Supported dual-port network adapters on the network connector (continued) dual-port network adapter option part number fru part number remark table note: 1. You can purchase ibm system x3550 m4 thermal solution kit (option part number 00y7117) to acquire two additional fans for your server...
Page 283
The emulex dual port 10gbe sfp+ embedded vfa iii is automatically disabled if one of the following errors occurs: v an error log indicates a temperature warning for the ethernet adapter. V all power supplies are removed or the server is disconnected from the power source. To install the dual-port ne...
Page 284
8. Press the adapter firmly until the pin, and retention brackets engage the adapter. Make sure the adapter is securely seated on the connector on the system board. Attention: make sure the port connectors on the adapter are aligned properly with the chassis on the rear of the server. An incorrectly...
Page 285
10. Fasten the two captive screws on the network adapter. 11. Reinstall the pci riser-card assembly in pci riser connector 2 if you have removed it previously (see “replacing a pci riser-card assembly” on page 245). 12. Replace the cover (see “replacing the cover” on page 209). 13. Slide the server ...
Page 286
Attention: to ensure proper operation, replace a failed hot-swap fan within 30 seconds. Results if you are instructed to return the fan, follow all of the packaging instructions, and use any packaging materials for shipping that are supplied to you. Replacing a hot-swap fan use this information to r...
Page 287
4. Orient the fan over the fan slot in the fan assembly bracket so that the fan connector aligns with the connector on the system board. Figure 165. Fan installation chapter 6. Removing and replacing components 269.
Page 288
5. Insert the fan into the fan slot in the fan assembly bracket and press it down until it is seated correctly in the slot and the fan connector is seated correctly in the connector on the system board. Note: make sure that the newly-installed fan aligns horizontally with other correctly-seated fans...
Page 289
Removing a hot-swap ac power supply: use this information to remove a hot-swap ac power supply. About this task when you remove or install a hot-swap power supply, observe the following precautions. Statement 5 caution: the power control button on the device and the power switch on the power supply ...
Page 290
2. If only one power supply is installed, turn off the server and peripheral devices and disconnect all power cords. 3. If the server is in a rack, at the back of the server, pull back the cable management arm to gain access to the rear of the server and the power supply. 4. Press and hold the relea...
Page 291
V this equipment shall be located in the same immediate area (such as, adjacent cabinets) as any other equipment that has a connection between the earthed conductor of the same dc supply circuit and the earthing conductor, and also the point of earthing of the dc system. The dc system shall not be e...
Page 292
Danger electrical current from power, telephone, and communication cables is hazardous. To avoid a shock hazard: v do not connect or disconnect any cables or perform installation, maintenance, or reconfiguration of this product during an electrical storm. V connect all power cords to a properly wire...
Page 293
Statement 34 caution: to reduce the risk of electric shock or energy hazards: v this equipment must be installed by trained service personnel in a restricted-access location, as defined by the nec and iec 60950-1, first edition, the standard for safety of information technology equipment. V connect ...
Page 294
4. Press and hold the release tab to the left. Grasp the handle and pull the power supply out of the server. 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 us...
Page 295
V these power supplies are designed for parallel operation. In the event of a power-supply failure, the redundant power supply continues to power the system. The server supports a maximum of two power supplies. Statement 5 caution: the power control button on the device and the power switch on the p...
Page 296
3. If you are installing a hot-swap power supply into an empty bay, remove the power-supply filler from the power-supply bay. 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 fir...
Page 297
10. If you are adding a power supply to the server, attach the redundant power information label that comes with this option on the server cover near the power supplies. Installing a hot-swap dc power supply: observe the following precautions when you install a hot-swap dc power supply. The followin...
Page 298
V these power supplies are designed for parallel operation. In the event of a power-supply failure, the redundant power supply continues to power the system. The server supports a maximum of two power supplies. Regulations v it is the customer's responsibility to supply the necessary power cable. To...
Page 299
Danger electrical current from power, telephone, and communication cables is hazardous. To avoid a shock hazard: v do not connect or disconnect any cables or perform installation, maintenance, or reconfiguration of this product during an electrical storm. V connect all power cords to a properly wire...
Page 300
Statement 34 caution: to reduce the risk of electric shock or energy hazards: v this equipment must be installed by trained service personnel in a restricted-access location, as defined by the nec and iec 60950-1, first edition, the standard for safety of information technology equipment. V connect ...
Page 301
Replacing a hot-swap dc power supply: to install a hot-swap dc power supply, complete the following steps. About this task attention: only trained service personnel other than ibm service technicians are authorized to install and remove the -48 volt dc power supply, and make the connections to and d...
Page 302
6. 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. 7. Route the power cord through the handle and cable tie if any, so that it does not acci...
Page 303
12. If you are adding a power supply to the server, attach the redundant power information label that comes with this option on the server cover near the power supplies. Removing the hot-swap drive backplane use this information to remove the hot-swap drive backplane. About this task to remove the h...
Page 304
B. Lift the hard disk drive backplane up to remove it from the server. If you would like to remove the 2.5-inch drive backplane. A. Lift the hard disk drive backplane up to remove it from the server. Figure 176. Latch adjustment figure 177. Backplane removal 286 ibm system x3550 m4 type 7914: instal...
Page 305
6. 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 the hot-swap drive backplane use this information to...
Page 306
Is fully seated. B. Adjust the latch to the locked position. If you would like to install the 2.5-inch drive backplane. Figure 179. Backplane installation figure 180. Latch adjustment 288 ibm system x3550 m4 type 7914: installation and service guide.
Page 307
A. Insert the hard disk drive backplane into the slots on the backplane bracket and push the hard disk drive backplane down until the backplane is fully seated. 5. Connect the signal, power and configuration cables to the system board. Route the signal cable from the drive backplane along the chassi...
Page 308
Removing the simple-swap drive backplate assembly use this information to remove the simple-swap drive backplate assembly. About this task to remove the simple-swap hard disk drive backplate assembly, complete the following steps: procedure 1. Read the safety information that begins on “safety” on p...
Page 309
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 the simple-swap drive backplate assembl...
Page 310
B. Adjust the latch to the locked position on 3.5-inch server models. 4. 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 a...
Page 311
9. Turn on the peripheral devices and the server. 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 tha...
Page 312
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 313
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 314
5. Remove the system battery: a. If there is a rubber cover on the battery holder, use your fingers to lift the battery cover from the battery connector. B. Use one finger to tilt the battery horizontally out of its socket, pushing it away from the socket. Attention: neither tilt nor push the batter...
Page 315
Replacing the system battery use this information to replace the system battery. About this task the following notes describe information that you must consider when replacing the system battery in the server. V when replacing the system battery, you must replace it with a lithium battery of the sam...
Page 316
A. Tilt the battery so that you can insert it into the socket on the side opposite the battery clip. B. Press the battery down into the socket until it clicks into place. Make sure that the battery clip holds the battery securely. C. If you removed a rubber cover from the battery holder, use your fi...
Page 317
Removing the bezel use this information to remove the bezel. About this task to remove the bezel, complete the following steps: procedure 1. Read the safety information that begins on “safety” on page vii and “installation guidelines” on page 33. 2. Turn off the server and peripheral devices and dis...
Page 318
Replacing the bezel use this information to replace the bezel. About this task to install the bezel, complete the following steps: procedure 1. Read the safety information that begins on “safety” on page vii and “installation guidelines” on page 33. 2. Turn off the server and peripheral devices and ...
Page 319
6. Reinstall the hard disk drives and drive bay filler panels into the drive bays (see “replacing hot-swap hard disk drives” on page 219 or “replacing simple-swap hard disk drives” on page 223). 7. Install the cover (see “replacing the cover” on page 209). 8. Reconnect the power cords and any cables...
Page 320
5. Remove the usb cage screw from the chassis. 6. Disconnect the cables from the front usb connector. 7. Pull the front usb connector assembly out slightly; then, rotate it downward until the tabs on the bottom of the front usb connector assembly disengages from the chassis and set it aside. Figure ...
Page 321
Replacing the front usb connector assembly use this information to replace the front usb connector assembly. About this task to install the front usb connector assembly, complete the following steps: procedure 1. Read the safety information that begins on “safety” on page vii and “installation guide...
Page 322
6. Reconnect the front usb cable to the front usb connector on the system board. 7. Reinstall the bezel (see “replacing the bezel” on page 300). 8. Reinstall the hard disk drives and drive bay filler panels into the drive bays (see “replacing hot-swap hard disk drives” on page 219 or “replacing simp...
Page 323
Removing the front video connector assembly use this information to remove the front video connector assembly. About this task to remove the front video connector assembly, complete the following steps: procedure 1. Read the safety information that begins on “safety” on page vii and “installation gu...
Page 324
5. Pull the front video connector assembly out slightly until it disengages from the chassis and set it aside. Replacing the front video connector assembly use this information to replace the front video connector assembly. About this task to install the front video connector assembly, complete the ...
Page 325
4. Reinstall the video connector assembly screws. 5. Reconnect the front video cable to the front video connector on the system board. 6. Install the cover (see “replacing the cover” on page 209). 7. Reconnect the power cords and any cables that you removed. 8. Slide the server into the rack. 9. Tur...
Page 326
Removing the operator information panel assembly use this information to remove the operator information panel assembly. About this task to remove the operator information panel, complete the following steps. Procedure 1. Read the safety information that begins on “safety” on page vii and “installat...
Page 327
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 328
The following notes describe additional information when you install the cable: v to connect the operator information panel cable on the system board, press evenly on the cable. Pressing on one side of the cable might cause damage to the cable or connector. V the operator information panel cable mus...
Page 329
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 designated for your server. The illustrations in this document might differ slightly from your hardware. Removing a microprocesso...
Page 330
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 33. 2. Turn off the server and peripheral devices and disconnect all power cords. 3. Remove the cover (see “remov...
Page 331
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 332
V if using installation tool b,1lift the interlock latch and hold it up while you2twist the microprocessor installation tool handle counterclockwise to the open position, and then release the interlock latch. The following illustration of the installation tool shows the location of the interlock lat...
Page 333
C. Using the following instructions for your installation tool to remove the microprocessor. V if using installation tool a, gently twist the handle clockwise to the closed position and lift the microprocessor out of the socket. V if using installation tool b, gently twist the handle of the installa...
Page 334
9. Install the new microprocessor (see “replacing a microprocessor and heat sink”). Attention: if you are replacing a microprocessor, use the empty installation tool that comes with the new microprocessor to remove the microprocessor. 10. If you do not intend to install a microprocessor on the socke...
Page 335
V do not use any tools or sharp objects to lift the locking levers on the microprocessor socket. Doing so might result in permanent damage to the system board. V each microprocessor socket must always contain either a socket cover or a microprocessor and heat sink. V be sure to use only the installa...
Page 336
V to order an additional optional microprocessor, contact your ibm sales representative or ibm reseller. V there are two types of microprocessor installation tools. The tools are similar in function and design, however tool a has one setting for installing one size of microprocessor, and supports th...
Page 337
6. 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 338
C. Align the installation tool with the microprocessor socket. The installation tool rests flush on the socket only if properly aligned. D. Install the microprocessor using the following instructions for your installation tool. V if using installation tool a, twist the handle on the microprocessor t...
Page 339
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 340
Attention: when you handle static-sensitive devices, take precautions to avoid damage from static electricity. For details about handling these devices, see “handling static-sensitive devices” on page 36. 9. Close the microprocessor socket release levers and retainer: a. Close the microprocessor ret...
Page 341
A. Remove the plastic protective cover from the bottom of the heat sink. B. Position the heat sink over the microprocessor. The heat sink is keyed to assist with proper alignment. C. Align and place the heat sink on top of the microprocessor in the retention bracket, thermal material side down. D. P...
Page 342
Thermal grease: the thermal grease must be replaced whenever the heat sink has been removed from the top of the microprocessor and is going to be reused or when debris is found in the grease. About this task when you are installing the heat sink on the same microprocessor that it was removed from, m...
Page 343
6. Install the heat sink onto the microprocessor. Removing the heat-sink retention module use this information to remove the heat-sink retention module. About this task to remove a heat-sink retention module, complete the following steps: procedure 1. Read the safety information that begins on “safe...
Page 344
Replacing the heat-sink retention module use this information to replace the heat-sink retention module. About this task to install a heat-sink retention module, complete the following steps: procedure 1. Read the safety information that begins on “safety” on page vii and “installation guidelines” o...
Page 345
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 346
B. Do not allow the thermal grease to come in contact with anything, and keep each heat sink paired with its microprocessor for reinstallation. Contact with any surface can compromise the thermal grease and the microprocessor socket. A mismatch between the microprocessor and its original heat sink c...
Page 347
17. 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. 18. Grasp the system board handles and lift up the system board and carefully remove it from the server, being...
Page 348
19. 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. 20. If you are instructed to return the system board, follow all packaging instructions, and use any packaging materials fo...
Page 349
Board. For information about the advanced upgrade, see “using the remote presence and blue-screen capture features” on page 115. 4. Reactivate any features on demand features. Instructions for automating the activation of features and installing activation keys is in the ibm features on demand user'...
Page 350
3. Fasten the two thumbscrews (one is near pci slot 2 and one is between fans 4 and 5). 4. Rotate the fan assembly bracket down toward the rear of the server. Figure 241. System-board standoffs figure 242. Thumbscrews engagement 332 ibm system x3550 m4 type 7914: installation and service guide.
Page 351
5. Install the hot-swap fans (see “replacing a hot-swap fan” on page 268). 6. Install the system battery (see “replacing the system battery” on page 297). 7. (trained technician only) install the microprocessor and heat sink (see “replacing a microprocessor and heat sink” on page 316). 8. Install th...
Page 352
334 ibm system x3550 m4 type 7914: installation and service guide.
Page 353
Appendix a. Integrated management module ii (imm2) 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 uniquel...
Page 354
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 355
Table 28. Events that automatically notify support (continued) event id message string automatically notify support 806f0021-2c01ffff fault in slot [physicalconnectorsystemelementname] on system [computersystemelementname]. (mezz card error) yes 806f0021-3001ffff fault in slot [physicalconnectorsyst...
Page 356
Table 28. Events that automatically notify support (continued) event id message string automatically notify support 806f010c-200affff uncorrectable error detected for [physicalmemoryelementname] on subsystem [memoryelementname]. (dimm 10) yes 806f010c-200bffff uncorrectable error detected for [physi...
Page 357
Table 28. Events that automatically notify support (continued) event id message string automatically notify support 806f010c-2016ffff uncorrectable error detected for [physicalmemoryelementname] on subsystem [memoryelementname]. (dimm 22) yes 806f010c-2017ffff uncorrectable error detected for [physi...
Page 358
Table 28. Events that automatically notify support (continued) event id message string automatically notify support 806f0207-2584ffff [processorelementname] has failed with frb1/bist condition. (all cpus) yes 806f020d-0400ffff failure predicted on drive [storagevolumeelementname] for array [computer...
Page 359
Table 28. 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 360
Table 28. 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 361
Table 28. Events that automatically notify support (continued) event id message string automatically notify support 806f0813-2581ffff a uncorrectable bus error has occurred on system [computersystemelementname]. (dimms) yes 806f0813-2582ffff a uncorrectable bus error has occurred on system [computer...
Page 362
40000003-00000000 ethernet data rate modified from [arg1] to [arg2] by user [arg3]. Explanation: this message is for the use case where a user modifies the ethernet port data rate. May also be shown as 4000000300000000 or 0x4000000300000000 severity: info alert category: none serviceable: no cim inf...
Page 363
40000006-00000000 ethernet locally administered mac address modified from [arg1] to [arg2] by user [arg3]. Explanation: this message is for the use case where a user modifies the ethernet port mac address setting. May also be shown as 4000000600000000 or 0x4000000600000000 severity: info alert categ...
Page 364
40000009-00000000 ip address of network interface modified from [arg1] to [arg2] by user [arg3]. Explanation: this message is for the use case where user modifies the ip address of a management controller. May also be shown as 4000000900000000 or 0x4000000900000000 severity: info alert category: sys...
Page 365
4000000c-00000000 os watchdog response [arg1] by [arg2] . Explanation: this message is for the use case where an os watchdog has been enabled or disabled by a user. May also be shown as 4000000c00000000 or 0x4000000c00000000 severity: warning alert category: none serviceable: no cim information: pre...
Page 366
4000000f-00000000 attempting to [arg1] server [arg2] by user [arg3]. Explanation: this message is for the use case where a user is using the management controller to perform a power function on the system. May also be shown as 4000000f00000000 or 0x4000000f00000000 severity: info alert category: non...
Page 367
40000012-00000000 remote access attempt failed. Invalid userid or password received. Userid is [arg1] from web browser at ip address [arg2]. Explanation: this message is for the use case where a remote user has failed to establish a remote control session from a web browser session. May also be show...
Page 368
40000015-00000000 management controller [arg1] reset was initiated by user [arg2]. Explanation: this message is for the use case where a management controller reset is initiated by a user. May also be shown as 4000001500000000 or 0x4000001500000000 severity: info alert category: none serviceable: no...
Page 369
40000018-00000000 lan: ethernet[[arg1]] interface is no longer active. Explanation: this message is for the use case where a management controller ethernet interface is no longer active. May also be shown as 4000001800000000 or 0x4000001800000000 severity: info alert category: none serviceable: no c...
Page 370
4000001b-00000000 management controller [arg1]: configuration restored from a file by user [arg2]. Explanation: this message is for the use case where a user restores a management controller configuration from a file. May also be shown as 4000001b00000000 or 0x4000001b00000000 severity: info alert c...
Page 371
3. Reinstall the rndis or cdc_ether device driver for the operating system. 4. Disable the watchdog. Check the integrity of the installed operating system. 5. Update the imm firmware. Important: some cluster solutions require specific code levels or coordinated code updates. If the device is part of...
Page 372
40000020-00000000 management controller [arg1] reset was caused by restoring default values. Explanation: this message is for the use case where a management controller has been reset due to a user restoring the configuration to default values. May also be shown as 4000002000000000 or 0x400000200000...
Page 373
40000023-00000000 flash of [arg1] from [arg2] succeeded for user [arg3] . Explanation: this message is for the use case where a user has successfully flashed the firmware component (mc main application, mc boot rom, bios, diagnostics, system power backplane, remote expansion enclosure power backplan...
Page 374
40000026-00000000 the [arg1] on system [arg2] is 100% full. Explanation: this message is for the use case where a management controller event log on a system is 100% full. May also be shown as 4000002600000000 or 0x4000002600000000 severity: info alert category: system - event log 75% full serviceab...
Page 375
40000029-00000000 security: userid: [arg1] had [arg2] login failures from an ssh client at ip address [arg3]. Explanation: this message is for the use case where a user has failed to log in to a management controller from ssh. May also be shown as 4000002900000000 or 0x4000002900000000 severity: inf...
Page 376
4000002c-00000000 domain source changed to [arg1] by user [arg2]. Explanation: domain source changed by user may also be shown as 4000002c00000000 or 0x4000002c00000000 severity: info alert category: none serviceable: no cim information: prefix: imm and id: 0044 snmp trap id: automatically notify su...
Page 377
4000002f-00000000 ipv6 enabled by user [arg1] . Explanation: ipv6 protocol is enabled by user may also be shown as 4000002f00000000 or 0x4000002f00000000 severity: info alert category: none serviceable: no cim information: prefix: imm and id: 0047 snmp trap id: automatically notify support: no user ...
Page 378
40000032-00000000 ipv6 dhcp enabled by user [arg1]. Explanation: ipv6 dhcp assignment method is enabled by user may also be shown as 4000003200000000 or 0x4000003200000000 severity: info alert category: none serviceable: no cim information: prefix: imm and id: 0050 snmp trap id: automatically notify...
Page 379
40000035-00000000 ipv6 dhcp disabled by user [arg1]. Explanation: ipv6 dhcp assignment method is disabled by user may also be shown as 4000003500000000 or 0x4000003500000000 severity: info alert category: none serviceable: no cim information: prefix: imm and id: 0053 snmp trap id: automatically noti...
Page 380
40000038-00000000 enet[[arg1]] ipv6-static:hstname=[arg2], ip@=[arg3] ,pref=[arg4], gw@=[arg5] . Explanation: ipv6 static address is active may also be shown as 4000003800000000 or 0x4000003800000000 severity: info alert category: none serviceable: no cim information: prefix: imm and id: 0056 snmp t...
Page 381
4000003b-00000000 dhcpv6 failure, no ip address assigned. Explanation: s dhcp6 server fails to assign an ip address to a management controller. May also be shown as 4000003b00000000 or 0x4000003b00000000 severity: warning alert category: none serviceable: no cim information: prefix: imm and id: 0059...
Page 382
4000003e-00000000 ssh port number changed from [arg1] to [arg2] by user [arg3]. Explanation: a user has modified the ssh port number may also be shown as 4000003e00000000 or 0x4000003e00000000 severity: info alert category: none serviceable: no cim information: prefix: imm and id: 0062 snmp trap id:...
Page 383
40000041-00000000 cim/xml http port number changed from [arg1] to [arg2] by user [arg3]. Explanation: a user has modified the cim http port number may also be shown as 4000004100000000 or 0x4000004100000000 severity: info alert category: none serviceable: no cim information: prefix: imm and id: 0065...
Page 384
40000044-00000000 snmp traps port number changed from [arg1] to [arg2] by user [arg3]. Explanation: a user has modified the snmp traps port number may also be shown as 4000004400000000 or 0x4000004400000000 severity: info alert category: none serviceable: no cim information: prefix: imm and id: 0068...
Page 385
40000047-00000000 led [arg1] state changed to [arg2] by [arg3]. Explanation: a user has modified the state of an led may also be shown as 4000004700000000 or 0x4000004700000000 severity: info alert category: none serviceable: no cim information: prefix: imm and id: 0071 snmp trap id: automatically n...
Page 386
4000004a-00000000 snmp [arg1] disabled by user [arg2] . Explanation: a user disabled snmpv1 or snmpv3 or traps may also be shown as 4000004a00000000 or 0x4000004a00000000 severity: info alert category: none serviceable: no cim information: prefix: imm and id: 0074 snmp trap id: automatically notify ...
Page 387
4000004d-00000000 ldap set by user [arg1]: rootdn=[arg2], uidsearchattribute=[arg3], bindingmethod=[arg4], enhancedrbs=[arg5], targetname=[arg6], groupfilter=[arg7], groupattribute=[arg8], loginattribute=[arg9]. Explanation: a user configured an ldap miscellaneous setting may also be shown as 400000...
Page 388
40000050-00000000 server general settings set by user [arg1]: name=[arg2], contact=[arg3], location=[arg4], room=[arg5], rackid=[arg6], rack u-position=[arg7]. Explanation: a user configured the location setting may also be shown as 4000005000000000 or 0x4000005000000000 severity: info alert categor...
Page 389
40000053-00000000 server [arg1] scheduled for every [arg2] at [arg3] by user [arg4]. Explanation: a user configured a recurring server power action may also be shown as 4000005300000000 or 0x4000005300000000 severity: info alert category: none serviceable: no cim information: prefix: imm and id: 008...
Page 390
40000056-00000000 smtp server set by user [arg1] to [arg2]:[arg3]. Explanation: a user configured the smtp server may also be shown as 4000005600000000 or 0x4000005600000000 severity: info alert category: none serviceable: no cim information: prefix: imm and id: 0086 snmp trap id: automatically noti...
Page 391
40000059-00000000 lan over usb [arg1] by user [arg2]. Explanation: a user configured usb-lan may also be shown as 4000005900000000 or 0x4000005900000000 severity: info alert category: none serviceable: no cim information: prefix: imm and id: 0089 snmp trap id: automatically notify support: no user r...
Page 392
4000005c-00000000 secure cim/xml(https) [arg1] by user [arg2]. Explanation: a user enables or disables secure cim/xml services may also be shown as 4000005c00000000 or 0x4000005c00000000 severity: info alert category: none serviceable: no cim information: prefix: imm and id: 0092 snmp trap id: autom...
Page 393
4000005f-00000000 server timeouts set by user [arg1]: enableoswatchdog=[arg2], oswatchdogtimout=[arg3], enableloaderwatchdog=[arg4], loadertimeout=[arg5]. Explanation: a user configures server timeouts may also be shown as 4000005f00000000 or 0x4000005f00000000 severity: info alert category: none se...
Page 394
40000062-00000000 global login general settings set by user [arg1]: authenticationmethod=[arg2], lockoutperiod=[arg3], sessiontimeout=[arg4]. Explanation: a user changes the global login general settings may also be shown as 4000006200000000 or 0x4000006200000000 severity: info alert category: none ...
Page 395
40000065-00000000 user [arg1] removed. Explanation: a user account was deleted may also be shown as 4000006500000000 or 0x4000006500000000 severity: info alert category: none serviceable: no cim information: prefix: imm and id: 0101 snmp trap id: automatically notify support: no user response: infor...
Page 396
40000068-00000000 user [arg1] custom privileges set: [arg2]. Explanation: user account priveleges assigned may also be shown as 4000006800000000 or 0x4000006800000000 severity: info alert category: none serviceable: no cim information: prefix: imm and id: 0104 snmp trap id: automatically notify supp...
Page 397
4000006b-00000000 ssh client key imported for user [arg1] from [arg2]. Explanation: user imported an ssh client key may also be shown as 4000006b00000000 or 0x4000006b00000000 severity: info alert category: none serviceable: no cim information: prefix: imm and id: 0107 snmp trap id: automatically no...
Page 398
4000006e-00000000 alert configuration global event notification set by user [arg1]: retrylimit=[arg2], retryinterval=[arg3], entryinterval=[arg4]. Explanation: a user changes the global event notification settings. May also be shown as 4000006e00000000 or 0x4000006e00000000 severity: info alert cate...
Page 399
40000071-00000000 the power cap value changed from [arg1] watts to [arg2] watts by user [arg3]. Explanation: power cap values changed by user may also be shown as 4000007100000000 or 0x4000007100000000 severity: info alert category: none serviceable: no cim information: prefix: imm and id: 0113 snmp...
Page 400
40000074-00000000 the soft minimum power cap value changed from [arg1] watts to [arg2] watts. Explanation: soft minimum power cap value changed may also be shown as 4000007400000000 or 0x4000007400000000 severity: info alert category: none serviceable: no cim information: prefix: imm and id: 0116 sn...
Page 401
40000077-00000000 power capping was activated by user [arg1]. Explanation: power capping activated by user may also be shown as 4000007700000000 or 0x4000007700000000 severity: info alert category: none serviceable: no cim information: prefix: imm and id: 0119 snmp trap id: automatically notify supp...
Page 402
4000007a-00000000 static power savings mode has been turned off by user [arg1]. Explanation: static power savings mode turned off by user may also be shown as 4000007a00000000 or 0x4000007a00000000 severity: info alert category: none serviceable: no cim information: prefix: imm and id: 0122 snmp tra...
Page 403
4000007d-00000000 power cap and external throttling occurred. Explanation: power cap and external throttling occurred may also be shown as 4000007d00000000 or 0x4000007d00000000 severity: info alert category: none serviceable: no cim information: prefix: imm and id: 0125 snmp trap id: automatically ...
Page 404
40000080-00000000 remote control session started by user [arg1] in [arg2] mode. Explanation: remote control session started may also be shown as 4000008000000000 or 0x4000008000000000 severity: info alert category: none serviceable: no cim information: prefix: imm and id: 0128 snmp trap id: automati...
Page 405
40000083-00000000 the new minimum power cap value has returned below the power cap value. Explanation: minimum power cap exceeds power cap recovered may also be shown as 4000008300000000 or 0x4000008300000000 severity: info alert category: warning - power serviceable: no cim information: prefix: imm...
Page 406
40000086-00000000 test call home generated by user [arg1]. Explanation: test call home generated by user. May also be shown as 4000008600000000 or 0x4000008600000000 severity: info alert category: none serviceable: no cim information: prefix: imm and id: 0134 snmp trap id: automatically notify suppo...
Page 407
40000089-00000000 management controller [arg1]: configuration restoration from a file by user [arg2] failed to complete. Explanation: this message is for the use case where a user restores a management controller configuration from a file and the restoration fails to complete. May also be shown as 4...
Page 408
4000008b-00000000 one or more of the storage management ip addresses has changed. Explanation: this message is for the use case where an ip address for the storage management has changed may also be shown as 4000008b00000000 or 0x4000008b00000000 severity: info alert category: system - imm network e...
Page 409
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 sensor going low has asserted. May also be shown as 800102041d01ffff or 0x800102041...
Page 410
2. Replace the failing fan. (n = fan number) 80010204-1d04ffff numeric sensor [numericsensorelementname] going low (lower critical) has asserted. (fan 4a/4b 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 411
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 also be shown as 800102041d06ffff or 0x800102041...
Page 412
80010701-1001ffff numeric sensor [numericsensorelementname] going high (upper non-critical) has asserted. (pci riser 1 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 800107011001ffff o...
Page 413
80010701-1401ffff numeric sensor [numericsensorelementname] going high (upper non-critical) has asserted. (cpu1 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 800107011401ffff or 0x...
Page 414
80010701-1403ffff numeric sensor [numericsensorelementname] going high (upper non-critical) has asserted. (dimm ab 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 800107011403ffff or...
Page 415
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 416
80010701-2c01ffff numeric sensor [numericsensorelementname] going high (upper non-critical) has asserted. (mezz card 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 800107012c01ffff or ...
Page 417
80010901-0c01ffff numeric sensor [numericsensorelementname] going high (upper critical) has asserted. (ambient 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 800109010c01ffff or 0x80010901...
Page 418
80010901-1002ffff numeric sensor [numericsensorelementname] going high (upper critical) has asserted. (pci riser 2 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 800109011002ffff or 0x8001...
Page 419
80010901-1402ffff numeric sensor [numericsensorelementname] going high (upper critical) has asserted. (cpu2 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 800109011402ffff or 0x80010901...
Page 420
80010901-1404ffff numeric sensor [numericsensorelementname] going high (upper critical) has asserted. (dimm cd 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 800109011404ffff or 0x80010...
Page 421
80010901-1406ffff numeric sensor [numericsensorelementname] going high (upper critical) has asserted. (dimm gh 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 800109011406ffff or 0x80010...
Page 422
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 423
80010b01-0c01ffff 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 80010b010c01ffff...
Page 424
80010b01-1401ffff numeric sensor [numericsensorelementname] going high (upper non-recoverable) has asserted. (cpu1 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 80010b011401ffff...
Page 425
80010b01-1404ffff numeric sensor [numericsensorelementname] going high (upper non-recoverable) has asserted. (dimm cd 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 80010b011404f...
Page 426
80010b01-2c01ffff numeric sensor [numericsensorelementname] going high (upper non-recoverable) has asserted. (mezz card 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 80010b012c01ff...
Page 427
80030012-2301ffff sensor [sensorelementname] has deasserted. (os realtime mod) explanation: this message is for the use case when an implementation has detected a sensor has deasserted. May also be shown as 800300122301ffff or 0x800300122301ffff severity: info alert category: system - other servicea...
Page 428
8007010f-2201ffff sensor [sensorelementname] has transitioned from normal to non-critical state. (gpt status) 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 8007010f2201ffff or 0x8007010f2201ff...
Page 429
3. Reboot the system. 4. (trained technician only) if the error continues, replace the planar. 80070201-0301ffff sensor [sensorelementname] has transitioned to critical from a less severe state. (cpu 1 overtemp) explanation: this message is for the use case when an implementation has detected a sens...
Page 430
80070202-0701ffff sensor [sensorelementname] has transitioned to critical from a less severe state. (sysbrd vol 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 800702020701ffff or 0x8007...
Page 431
80070204-0a02ffff sensor [sensorelementname] has transitioned to critical from a less severe state. (ps 2 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 800702040a02ffff or 0x800702...
Page 432
80070208-0a02ffff sensor [sensorelementname] has transitioned to critical from a less severe state. (ps 2 therm 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 800702080a02ffff or 0x8007...
Page 433
8007020f-2582ffff sensor [sensorelementname] has transitioned to critical from a less severe state. (i/o resources) 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 8007020f2582ffff or 0x8007020...
Page 434
3. Check for the system firmware version and update to the latest version. Important: 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 cluster solution before you up...
Page 435
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 436
80070603-0701ffff sensor [sensorelementname] has transitioned to non-recoverable. (pwr rail 1-6 fault) explanation: this message is for the use case when an implementation has detected a sensor transitioned to non-recoverable. May also be shown as 800706030701ffff or 0x800706030701ffff severity: err...
Page 437
80070608-0a02ffff sensor [sensorelementname] has transitioned to non-recoverable. Explanation: this message is for the use case when an implementation has detected a sensor transitioned to non-recoverable. May also be shown as 800706080a02ffff or 0x800706080a02ffff severity: error alert category: cr...
Page 438
8008010f-2101ffff device [logicaldeviceelementname] has been added. (phy presence jmp) explanation: this message is for the use case when an implementation has detected a device was inserted. May also be shown as 8008010f2101ffff or 0x8008010f2101ffff severity: info alert category: system - other se...
Page 439
800b0108-1301ffff redundancy lost for [redundancysetelementname] has asserted. (power unit) explanation: this message is for the use case when redundancy lost has asserted. May also be shown as 800b01081301ffff or 0x800b01081301ffff severity: error alert category: critical - redundant power supply s...
Page 440
4. Reseat the fans. 5. Replace the fans. (n = fan number) 800b010c-2581ffff redundancy lost for [redundancysetelementname] has asserted. (backup memory) explanation: this message is for the use case when redundancy lost has asserted. May also be shown as 800b010c2581ffff or 0x800b010c2581ffff severi...
Page 441
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 redundancy degraded or fully redundant to non-redund...
Page 442
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 443
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 444
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 445
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 446
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 447
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 448
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 449
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 450
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 451
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 452
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 453
3. Update the server firmware (uefi and imm) and adapter firmware. Important: 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 cluster solution before you update the...
Page 454
806f0021-3001ffff fault in slot [physicalconnectorsystemelementname] on system [computersystemelementname]. (internal raid) explanation: this message is for the use case when an implementation has detected a fault in a slot. May also be shown as 806f00213001ffff or 0x806f00213001ffff severity: error...
Page 455
806f0028-2101ffff sensor [sensorelementname] is unavailable or degraded on management system [computersystemelementname]. (tpm cmd failures) explanation: this message is for the use case when an implementation has detected a sensor is unavailable or degraded. May also be shown as 806f00282101ffff or...
Page 456
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 457
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 458
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 459
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 460
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 461
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 462
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 463
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 464
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 465
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 466
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 467
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 468
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 469
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 470
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 471
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 472
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 473
3. Replace the following components one at a time, in the order shown, restarting the server each time: a. Hard disk drive b. Cable from the system board to the backplane c. Hard disk drive backplane (n = hard disk drive number) 806f010d-0401ffff the drive [storagevolumeelementname] has been disable...
Page 474
806f010d-0403ffff the drive [storagevolumeelementname] has been disabled due to a detected fault. (drive 3) 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 806f010d0403ffff or 0x806f010d0403ffff severity: error...
Page 475
806f010d-0405ffff the drive [storagevolumeelementname] has been disabled due to a detected fault. (drive 5) 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 806f010d0405ffff or 0x806f010d0405ffff severity: error...
Page 476
806f010d-0407ffff the drive [storagevolumeelementname] has been disabled due to a detected fault. (drive 7) 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 806f010d0407ffff or 0x806f010d0407ffff severity: error...
Page 477
806f0113-0301ffff a bus timeout has occurred on system [computersystemelementname]. (cpu 1 peci) explanation: this message is for the use case when an implementation has detected a bus timeout. May also be shown as 806f01130301ffff or 0x806f01130301ffff severity: error alert category: critical - oth...
Page 478
4. (trained technician only) replace the system board. Front video : 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. M...
Page 479
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 480
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 481
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 482
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 483
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 484
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 485
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 486
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 487
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 488
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 489
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 490
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 491
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 492
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 493
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 494
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 495
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 496
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 497
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 498
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 499
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 500
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 501
806f040c-2001ffff [physicalmemoryelementname] disabled on subsystem [memoryelementname]. (dimm 1) explanation: this message is for the use case when an implementation has detected that memory has been disabled. May also be shown as 806f040c2001ffff or 0x806f040c2001ffff severity: info alert category...
Page 502
806f040c-2003ffff [physicalmemoryelementname] disabled on subsystem [memoryelementname]. (dimm 3) explanation: this message is for the use case when an implementation has detected that memory has been disabled. May also be shown as 806f040c2003ffff or 0x806f040c2003ffff severity: info alert category...
Page 503
806f040c-2005ffff [physicalmemoryelementname] disabled on subsystem [memoryelementname]. (dimm 5) explanation: this message is for the use case when an implementation has detected that memory has been disabled. May also be shown as 806f040c2005ffff or 0x806f040c2005ffff severity: info alert category...
Page 504
806f040c-2007ffff [physicalmemoryelementname] disabled on subsystem [memoryelementname]. (dimm 7) explanation: this message is for the use case when an implementation has detected that memory has been disabled. May also be shown as 806f040c2007ffff or 0x806f040c2007ffff severity: info alert category...
Page 505
806f040c-2009ffff [physicalmemoryelementname] disabled on subsystem [memoryelementname]. (dimm 9) explanation: this message is for the use case when an implementation has detected that memory has been disabled. May also be shown as 806f040c2009ffff or 0x806f040c2009ffff severity: info alert category...
Page 506
806f040c-200bffff [physicalmemoryelementname] disabled on subsystem [memoryelementname]. (dimm 11) explanation: this message is for the use case when an implementation has detected that memory has been disabled. May also be shown as 806f040c200bffff or 0x806f040c200bffff severity: info alert categor...
Page 507
806f040c-200dffff [physicalmemoryelementname] disabled on subsystem [memoryelementname]. (dimm 13) explanation: this message is for the use case when an implementation has detected that memory has been disabled. May also be shown as 806f040c200dffff or 0x806f040c200dffff severity: info alert categor...
Page 508
806f040c-200fffff [physicalmemoryelementname] disabled on subsystem [memoryelementname]. (dimm 15) explanation: this message is for the use case when an implementation has detected that memory has been disabled. May also be shown as 806f040c200fffff or 0x806f040c200fffff severity: info alert categor...
Page 509
806f040c-2011ffff [physicalmemoryelementname] disabled on subsystem [memoryelementname]. (dimm 17) explanation: this message is for the use case when an implementation has detected that memory has been disabled. May also be shown as 806f040c2011ffff or 0x806f040c2011ffff severity: info alert categor...
Page 510
806f040c-2013ffff [physicalmemoryelementname] disabled on subsystem [memoryelementname]. (dimm 19) explanation: this message is for the use case when an implementation has detected that memory has been disabled. May also be shown as 806f040c2013ffff or 0x806f040c2013ffff severity: info alert categor...
Page 511
806f040c-2015ffff [physicalmemoryelementname] disabled on subsystem [memoryelementname]. (dimm 21) explanation: this message is for the use case when an implementation has detected that memory has been disabled. May also be shown as 806f040c2015ffff or 0x806f040c2015ffff severity: info alert categor...
Page 512
806f040c-2017ffff [physicalmemoryelementname] disabled on subsystem [memoryelementname]. (dimm 23) explanation: this message is for the use case when an implementation has detected that memory has been disabled. May also be shown as 806f040c2017ffff or 0x806f040c2017ffff severity: info alert categor...
Page 513
806f040c-2581ffff [physicalmemoryelementname] disabled on subsystem [memoryelementname]. (all dimms) explanation: this message is for the use case when an implementation has detected that memory has been disabled. May also be shown as 806f040c2581ffff or 0x806f040c2581ffff severity: info alert categ...
Page 514
806f0507-0301ffff [processorelementname] has a configuration mismatch. (cpu 1) explanation: this message is for the use case when an implementation has detected a processor configuration mismatch has occurred. May also be shown as 806f05070301ffff or 0x806f05070301ffff severity: error alert category...
Page 515
806f0507-2584ffff [processorelementname] has a configuration mismatch. (all cpus) explanation: this message is for the use case when an implementation has detected a processor configuration mismatch has occurred. May also be shown as 806f05072584ffff or 0x806f05072584ffff severity: error alert categ...
Page 516
806f050c-2002ffff memory logging limit reached for [physicalmemoryelementname] on subsystem [memoryelementname]. (dimm 2) 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 806f050c2002ffff or 0x806f0...
Page 517
806f050c-2004ffff memory logging limit reached for [physicalmemoryelementname] on subsystem [memoryelementname]. (dimm 4) 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 806f050c2004ffff or 0x806f0...
Page 518
806f050c-2006ffff memory logging limit reached 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 reached. May also be shown as 806f050c2006ffff or 0x806f0...
Page 519
806f050c-2008ffff memory logging limit reached for [physicalmemoryelementname] on subsystem [memoryelementname]. (dimm 8) 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 806f050c2008ffff or 0x806f0...
Page 520
806f050c-200affff memory logging limit reached for [physicalmemoryelementname] on subsystem [memoryelementname]. (dimm 10) 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 806f050c200affff or 0x806f...
Page 521
806f050c-200cffff memory logging limit reached 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 reached. May also be shown as 806f050c200cffff or 0x806f...
Page 522
806f050c-200effff memory logging limit reached for [physicalmemoryelementname] on subsystem [memoryelementname]. (dimm 14) 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 806f050c200effff or 0x806f...
Page 523
806f050c-2010ffff memory logging limit reached for [physicalmemoryelementname] on subsystem [memoryelementname]. (dimm 16) 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 806f050c2010ffff or 0x806f...
Page 524
806f050c-2012ffff memory logging limit reached 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 reached. May also be shown as 806f050c2012ffff or 0x806f...
Page 525
806f050c-2014ffff memory logging limit reached for [physicalmemoryelementname] on subsystem [memoryelementname]. (dimm 20) 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 806f050c2014ffff or 0x806f...
Page 526
806f050c-2016ffff memory logging limit reached for [physicalmemoryelementname] on subsystem [memoryelementname]. (dimm 22) 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 806f050c2016ffff or 0x806f...
Page 527
806f050c-2018ffff memory logging limit reached 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 reached. May also be shown as 806f050c2018ffff or 0x806f...
Page 528
806f050d-0400ffff array [computersystemelementname] is in critical condition. (drive 0) explanation: this message is for the use case when an implementation has detected that an array is critical. May also be shown as 806f050d0400ffff or 0x806f050d0400ffff severity: error alert category: critical - ...
Page 529
806f050d-0402ffff array [computersystemelementname] is in critical condition. (drive 2) explanation: this message is for the use case when an implementation has detected that an array is critical. May also be shown as 806f050d0402ffff or 0x806f050d0402ffff severity: error alert category: critical - ...
Page 530
806f050d-0404ffff array [computersystemelementname] is in critical condition. (drive 4) explanation: this message is for the use case when an implementation has detected that an array is critical. May also be shown as 806f050d0404ffff or 0x806f050d0404ffff severity: error alert category: critical - ...
Page 531
806f050d-0406ffff array [computersystemelementname] is in critical condition. (drive 6) explanation: this message is for the use case when an implementation has detected that an array is critical. May also be shown as 806f050d0406ffff or 0x806f050d0406ffff severity: error alert category: critical - ...
Page 532
806f0513-2582ffff a pci serr has occurred on system [computersystemelementname]. (pcis) explanation: this message is for the use case when an implementation has detected a pci serr. May also be shown as 806f05132582ffff or 0x806f05132582ffff severity: error alert category: critical - other serviceab...
Page 533
806f0607-0301ffff an sm bios uncorrectable cpu complex error for [processorelementname] has asserted. (cpu 1) explanation: this message is for the use case when an sm bios uncorrectable cpu complex error has asserted. May also be shown as 806f06070301ffff or 0x806f06070301ffff severity: error alert ...
Page 534
806f0607-2584ffff an sm bios uncorrectable cpu complex error for [processorelementname] has asserted. (all cpus) explanation: this message is for the use case when an sm bios uncorrectable cpu complex error has asserted. May also be shown as 806f06072584ffff or 0x806f06072584ffff severity: error ale...
Page 535
4. Replace the raid adapter. 5. Replace the hard disk drive that is indicated by a lit status led. 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 80...
Page 536
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 537
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 538
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 539
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 540
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 541
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 542
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 543
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 544
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 545
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 546
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 547
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 548
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 549
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 550
806f0807-0302ffff [processorelementname] has been disabled. (cpu 2) explanation: this message is for the use case when an implementation has detected a processor has been disabled. May also be shown as 806f08070302ffff or 0x806f08070302ffff severity: info alert category: system - other serviceable: ...
Page 551
806f0813-2582ffff a uncorrectable bus error has occurred on system [computersystemelementname]. (pcis) explanation: this message is for the use case when an implementation has detected a bus uncorrectable error. May also be shown as 806f08132582ffff or 0x806f08132582ffff severity: error alert catego...
Page 552
806f0823-2101ffff watchdog timer interrupt occurred for [watchdogelementname]. (ipmi watchdog) explanation: this message is for the use case when an implementation has detected a watchdog timer interrupt occurred. May also be shown as 806f08232101ffff or 0x806f08232101ffff severity: info alert categ...
Page 553
806f090c-2003ffff [physicalmemoryelementname] on subsystem [memoryelementname] throttled. (dimm 3) explanation: this message is for the use case when an implementation has detected memory has been throttled. May also be shown as 806f090c2003ffff or 0x806f090c2003ffff severity: warning alert category...
Page 554
806f090c-2006ffff [physicalmemoryelementname] on subsystem [memoryelementname] throttled. (dimm 6) explanation: this message is for the use case when an implementation has detected memory has been throttled. May also be shown as 806f090c2006ffff or 0x806f090c2006ffff severity: warning alert category...
Page 555
806f090c-2009ffff [physicalmemoryelementname] on subsystem [memoryelementname] throttled. (dimm 9) explanation: this message is for the use case when an implementation has detected memory has been throttled. May also be shown as 806f090c2009ffff or 0x806f090c2009ffff severity: warning alert category...
Page 556
806f090c-200cffff [physicalmemoryelementname] on subsystem [memoryelementname] throttled. (dimm 12) explanation: this message is for the use case when an implementation has detected memory has been throttled. May also be shown as 806f090c200cffff or 0x806f090c200cffff severity: warning alert categor...
Page 557
806f090c-200fffff [physicalmemoryelementname] on subsystem [memoryelementname] throttled. (dimm 15) explanation: this message is for the use case when an implementation has detected memory has been throttled. May also be shown as 806f090c200fffff or 0x806f090c200fffff severity: warning alert categor...
Page 558
806f090c-2012ffff [physicalmemoryelementname] on subsystem [memoryelementname] throttled. (dimm 18) explanation: this message is for the use case when an implementation has detected memory has been throttled. May also be shown as 806f090c2012ffff or 0x806f090c2012ffff severity: warning alert categor...
Page 559
806f090c-2015ffff [physicalmemoryelementname] on subsystem [memoryelementname] throttled. (dimm 21) explanation: this message is for the use case when an implementation has detected memory has been throttled. May also be shown as 806f090c2015ffff or 0x806f090c2015ffff severity: warning alert categor...
Page 560
806f090c-2018ffff [physicalmemoryelementname] on subsystem [memoryelementname] throttled. (dimm 24) explanation: this message is for the use case when an implementation has detected memory has been throttled. May also be shown as 806f090c2018ffff or 0x806f090c2018ffff severity: warning alert categor...
Page 561
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 562
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 563
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 564
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 565
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 566
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 567
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 568
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 569
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 570
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 571
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 572
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 573
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 574
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 575
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 576
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 577
81010701-0c01ffff 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 810107010c01ffff o...
Page 578
81010701-1401ffff numeric sensor [numericsensorelementname] going high (upper non-critical) has deasserted. (cpu1 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 810107011401ffff o...
Page 579
81010701-1404ffff numeric sensor [numericsensorelementname] going high (upper non-critical) has deasserted. (dimm cd 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 810107011404fff...
Page 580
81010701-2c01ffff numeric sensor [numericsensorelementname] going high (upper non-critical) has deasserted. (mezz card 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 810107012c01ffff...
Page 581
81010901-1001ffff numeric sensor [numericsensorelementname] going high (upper critical) has deasserted. (pci riser 1 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 0x...
Page 582
81010901-1402ffff numeric sensor [numericsensorelementname] going high (upper critical) has deasserted. (cpu2 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 810109011402ffff or 0x8101...
Page 583
81010901-1405ffff numeric sensor [numericsensorelementname] going high (upper critical) has deasserted. (dimm ef 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 810109011405ffff or 0x8...
Page 584
81010901-2d01ffff numeric sensor [numericsensorelementname] going high (upper critical) has deasserted. (pch 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 810109012d01ffff or 0x81010901...
Page 585
81010b01-1001ffff numeric sensor [numericsensorelementname] going high (upper non-recoverable) has deasserted. (pci riser 1 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 81010b01...
Page 586
81010b01-1402ffff numeric sensor [numericsensorelementname] going high (upper non-recoverable) has deasserted. (cpu2 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 81010b011402...
Page 587
81010b01-1405ffff numeric sensor [numericsensorelementname] going high (upper non-recoverable) has deasserted. (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 deasserted. May also be shown as 81010b011...
Page 588
81010b01-2d01ffff numeric sensor [numericsensorelementname] going high (upper non-recoverable) has deasserted. (pch 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 81010b012d01ffff...
Page 589
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 590
8107010f-2582ffff sensor [sensorelementname] has deasserted the transition from normal to non-critical state. (i/o resources) 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 591
81070202-0701ffff sensor [sensorelementname] has transitioned to a less severe state from critical. (sysbrd vol 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 810702020701ffff or 0x810702...
Page 592
81070208-0a01ffff sensor [sensorelementname] has transitioned to a less severe state from critical. (ps 1 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 810702080a01ffff or 0x810702...
Page 593
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 594
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 595
81070301-0302ffff sensor [sensorelementname] has deasserted the transition to non-recoverable from a less severe state. (cpu 2 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 596
81070608-0a02ffff sensor [sensorelementname] has deasserted the transition to non-recoverable. (ps2 12v oc fault) explanation: this message is for the use case when an implementation has detected that the sensor transition to non-recoverable has deasserted. May also be shown as 810706080a02ffff or 0...
Page 597
810b010c-2581ffff redundancy lost for [redundancysetelementname] has deasserted. (backup memory) explanation: this message is for the use case when redundacy lost has deasserted. May also be shown as 810b010c2581ffff or 0x810b010c2581ffff severity: info alert category: critical - memory serviceable:...
Page 598
810b0509-1301ffff non-redundant:insufficient resources for [redundancysetelementname] has deasserted. (power resource) explanation: this message is for the use case when a redundancy set has transitioned from non- redundant:insufficient resources. May also be shown as 810b05091301ffff or 0x810b05091...
Page 599
810b050c-2581ffff non-redundant:insufficient resources for [redundancysetelementname] has deasserted. (backup memory) explanation: this message is for the use case when a redundancy set has transitioned from non- redundant:insufficient resources. May also be shown as 810b050c2581ffff or 0x810b050c25...
Page 600
816f0008-0a01ffff [powersupplyelementname] has been removed from container [physicalpackageelementname]. (power supply 1) explanation: this message is for the use case when an implementation has detected a power supply has been removed. May also be shown as 816f00080a01ffff or 0x816f00080a01ffff sev...
Page 601
816f000d-0400ffff the drive [storagevolumeelementname] has been removed from unit [physicalpackageelementname]. (drive 0) explanation: this message is for the use case when an implementation has detected a drive has been removed. May also be shown as 816f000d0400ffff or 0x816f000d0400ffff severity: ...
Page 602
816f000d-0402ffff the drive [storagevolumeelementname] has been removed from unit [physicalpackageelementname]. (drive 2) explanation: this message is for the use case when an implementation has detected a drive has been removed. May also be shown as 816f000d0402ffff or 0x816f000d0402ffff severity: ...
Page 603
816f000d-0404ffff the drive [storagevolumeelementname] has been removed from unit [physicalpackageelementname]. (drive 4) explanation: this message is for the use case when an implementation has detected a drive has been removed. May also be shown as 816f000d0404ffff or 0x816f000d0404ffff severity: ...
Page 604
816f000d-0406ffff the drive [storagevolumeelementname] has been removed from unit [physicalpackageelementname]. (drive 6) explanation: this message is for the use case when an implementation has detected a drive has been removed. May also be shown as 816f000d0406ffff or 0x816f000d0406ffff severity: ...
Page 605
816f000f-2201ffff the system [computersystemelementname] has detected a post error deassertion. (abr status) explanation: this message is for the use case when an implementation has detected that post error has deasserted. May also be shown as 816f000f2201ffff or 0x816f000f2201ffff severity: info al...
Page 606
816f0021-2582ffff fault condition removed on slot [physicalconnectorelementname] on system [computersystemelementname]. (all pci error) 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 816f00212582fff...
Page 607
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 608
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 609
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 610
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 611
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 612
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 613
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 614
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 615
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 616
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 617
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 618
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 619
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 620
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 621
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 622
816f0125-1002ffff [managedelementname] detected as present. (pci riser 2) explanation: this message is for the use case when an implementation has detected a managed element is now present. May also be shown as 816f01251002ffff or 0x816f01251002ffff severity: info alert category: system - other serv...
Page 623
816f0207-0302ffff [processorelementname] has recovered from frb1/bist condition. (cpu 2) explanation: this message is for the use case when an implementation has detected a processor recovered - frb1/bist condition. May also be shown as 816f02070302ffff or 0x816f02070302ffff severity: info alert cat...
Page 624
816f020d-0401ffff failure no longer predicted on drive [storagevolumeelementname] for array [computersystemelementname]. (drive 1) 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 816f020d0401ffff or 0x816...
Page 625
816f020d-0404ffff failure no longer 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 no longer predicted. May also be shown as 816f020d0404ffff or 0x816...
Page 626
816f020d-0407ffff failure no longer predicted on drive [storagevolumeelementname] for array [computersystemelementname]. (drive 7) 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 816f020d0407ffff or 0x816...
Page 627
816f030c-2001ffff scrub failure for [physicalmemoryelementname] on subsystem [memoryelementname]has recovered. (dimm 1) explanation: this message is for the use case when an implementation has detected a memory scrub failure recovery. May also be shown as 816f030c2001ffff or 0x816f030c2001ffff sever...
Page 628
816f030c-2004ffff scrub failure for [physicalmemoryelementname] on subsystem [memoryelementname]has recovered. (dimm 4) explanation: this message is for the use case when an implementation has detected a memory scrub failure recovery. May also be shown as 816f030c2004ffff or 0x816f030c2004ffff sever...
Page 629
816f030c-2007ffff scrub failure for [physicalmemoryelementname] on subsystem [memoryelementname]has recovered. (dimm 7) explanation: this message is for the use case when an implementation has detected a memory scrub failure recovery. May also be shown as 816f030c2007ffff or 0x816f030c2007ffff sever...
Page 630
816f030c-200affff scrub failure for [physicalmemoryelementname] on subsystem [memoryelementname]has recovered. (dimm 10) explanation: this message is for the use case when an implementation has detected a memory scrub failure recovery. May also be shown as 816f030c200affff or 0x816f030c200affff seve...
Page 631
816f030c-200dffff scrub failure for [physicalmemoryelementname] on subsystem [memoryelementname]has recovered. (dimm 13) explanation: this message is for the use case when an implementation has detected a memory scrub failure recovery. May also be shown as 816f030c200dffff or 0x816f030c200dffff seve...
Page 632
816f030c-2010ffff scrub failure for [physicalmemoryelementname] on subsystem [memoryelementname]has recovered. (dimm 16) explanation: this message is for the use case when an implementation has detected a memory scrub failure recovery. May also be shown as 816f030c2010ffff or 0x816f030c2010ffff seve...
Page 633
816f030c-2013ffff scrub failure for [physicalmemoryelementname] on subsystem [memoryelementname]has recovered. (dimm 19) explanation: this message is for the use case when an implementation has detected a memory scrub failure recovery. May also be shown as 816f030c2013ffff or 0x816f030c2013ffff seve...
Page 634
816f030c-2016ffff scrub failure for [physicalmemoryelementname] on subsystem [memoryelementname]has recovered. (dimm 22) explanation: this message is for the use case when an implementation has detected a memory scrub failure recovery. May also be shown as 816f030c2016ffff or 0x816f030c2016ffff seve...
Page 635
816f0313-1701ffff system [computersystemelementname] has recovered from an nmi. (nmi state) explanation: this message is for the use case when an implementation has detected a software nmi has been recovered from. May also be shown as 816f03131701ffff or 0x816f03131701ffff severity: info alert categ...
Page 636
816f040c-2003ffff [physicalmemoryelementname] enabled on subsystem [memoryelementname]. (dimm 3) explanation: this message is for the use case when an implementation has detected that memory has been enabled. May also be shown as 816f040c2003ffff or 0x816f040c2003ffff severity: info alert category: ...
Page 637
816f040c-2006ffff [physicalmemoryelementname] enabled on subsystem [memoryelementname]. (dimm 6) explanation: this message is for the use case when an implementation has detected that memory has been enabled. May also be shown as 816f040c2006ffff or 0x816f040c2006ffff severity: info alert category: ...
Page 638
816f040c-2009ffff [physicalmemoryelementname] enabled on subsystem [memoryelementname]. (dimm 9) explanation: this message is for the use case when an implementation has detected that memory has been enabled. May also be shown as 816f040c2009ffff or 0x816f040c2009ffff severity: info alert category: ...
Page 639
816f040c-200cffff [physicalmemoryelementname] enabled on subsystem [memoryelementname]. (dimm 12) explanation: this message is for the use case when an implementation has detected that memory has been enabled. May also be shown as 816f040c200cffff or 0x816f040c200cffff severity: info alert category:...
Page 640
816f040c-200fffff [physicalmemoryelementname] enabled on subsystem [memoryelementname]. (dimm 15) explanation: this message is for the use case when an implementation has detected that memory has been enabled. May also be shown as 816f040c200fffff or 0x816f040c200fffff severity: info alert category:...
Page 641
816f040c-2012ffff [physicalmemoryelementname] enabled on subsystem [memoryelementname]. (dimm 18) explanation: this message is for the use case when an implementation has detected that memory has been enabled. May also be shown as 816f040c2012ffff or 0x816f040c2012ffff severity: info alert category:...
Page 642
816f040c-2015ffff [physicalmemoryelementname] enabled on subsystem [memoryelementname]. (dimm 21) explanation: this message is for the use case when an implementation has detected that memory has been enabled. May also be shown as 816f040c2015ffff or 0x816f040c2015ffff severity: info alert category:...
Page 643
816f040c-2018ffff [physicalmemoryelementname] enabled on subsystem [memoryelementname]. (dimm 24) explanation: this message is for the use case when an implementation has detected that memory has been enabled. May also be shown as 816f040c2018ffff or 0x816f040c2018ffff severity: info alert category:...
Page 644
816f0507-0301ffff [processorelementname] has recovered from a configuration mismatch. (cpu 1) explanation: this message is for the use case when an implementation has recovered from a processor configuration mismatch. May also be shown as 816f05070301ffff or 0x816f05070301ffff severity: info alert c...
Page 645
816f050c-2001ffff memory logging limit removed 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 removed. May also be shown as 816f050c2001ffff or 0x816f0...
Page 646
816f050c-2004ffff memory logging limit removed for [physicalmemoryelementname] on subsystem [memoryelementname]. (dimm 4) 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 816f050c2004ffff or 0x816f0...
Page 647
816f050c-2007ffff memory logging limit removed 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 removed. May also be shown as 816f050c2007ffff or 0x816f0...
Page 648
816f050c-200affff memory logging limit removed for [physicalmemoryelementname] on subsystem [memoryelementname]. (dimm 10) 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 816f050c200affff or 0x816f...
Page 649
816f050c-200dffff memory logging limit removed 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 removed. May also be shown as 816f050c200dffff or 0x816f...
Page 650
816f050c-2010ffff memory logging limit removed for [physicalmemoryelementname] on subsystem [memoryelementname]. (dimm 16) 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 816f050c2010ffff or 0x816f...
Page 651
816f050c-2013ffff memory logging limit removed 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 removed. May also be shown as 816f050c2013ffff or 0x816f...
Page 652
816f050c-2016ffff memory logging limit removed for [physicalmemoryelementname] on subsystem [memoryelementname]. (dimm 22) 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 816f050c2016ffff or 0x816f...
Page 653
816f050c-2581ffff memory logging limit removed 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 removed. May also be shown as 816f050c2581ffff or 0x81...
Page 654
816f050d-0402ffff critical array [computersystemelementname] has deasserted. (drive 2) explanation: this message is for the use case when an implementation has detected that an critiacal array has deasserted. May also be shown as 816f050d0402ffff or 0x816f050d0402ffff severity: info alert category: ...
Page 655
816f050d-0405ffff critical array [computersystemelementname] has deasserted. (drive 5) explanation: this message is for the use case when an implementation has detected that an critiacal array has deasserted. May also be shown as 816f050d0405ffff or 0x816f050d0405ffff severity: info alert category: ...
Page 656
816f0607-0301ffff an sm bios uncorrectable cpu complex error for [processorelementname] has deasserted. (cpu 1) explanation: this message is for the use case when an sm bios uncorrectable cpu complex error has deasserted. May also be shown as 816f06070301ffff or 0x816f06070301ffff severity: info ale...
Page 657
816f0608-1301ffff [powersupplyelementname] configuration is ok. (ps configuration) explanation: this message is for the use case when an implementation when a power supply configuration is ok. May also be shown as 816f06081301ffff or 0x816f06081301ffff severity: info alert category: critical - power...
Page 658
816f060d-0402ffff array in system [computersystemelementname] has been restored. (drive 2) 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 816f060d0402ffff or 0x816f060d0402ffff severity: info alert categor...
Page 659
816f060d-0405ffff array in system [computersystemelementname] has been restored. (drive 5) 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 816f060d0405ffff or 0x816f060d0405ffff severity: info alert categor...
Page 660
816f070c-2001ffff configuration error for [physicalmemoryelementname] on subsystem [memoryelementname]has deasserted. (dimm 1) 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 816f070c2001ffff or ...
Page 661
816f070c-2004ffff configuration error for [physicalmemoryelementname] on subsystem [memoryelementname]has deasserted. (dimm 4) 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 816f070c2004ffff or ...
Page 662
816f070c-2007ffff configuration error for [physicalmemoryelementname] on subsystem [memoryelementname]has deasserted. (dimm 7) 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 816f070c2007ffff or ...
Page 663
816f070c-200affff configuration error for [physicalmemoryelementname] on subsystem [memoryelementname]has deasserted. (dimm 10) 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 816f070c200affff or...
Page 664
816f070c-200dffff configuration error for [physicalmemoryelementname] on subsystem [memoryelementname]has deasserted. (dimm 13) 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 816f070c200dffff or...
Page 665
816f070c-2010ffff configuration error for [physicalmemoryelementname] on subsystem [memoryelementname]has deasserted. (dimm 16) 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 816f070c2010ffff or...
Page 666
816f070c-2013ffff configuration error for [physicalmemoryelementname] on subsystem [memoryelementname]has deasserted. (dimm 19) 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 816f070c2013ffff or...
Page 667
816f070c-2016ffff configuration error for [physicalmemoryelementname] on subsystem [memoryelementname]has deasserted. (dimm 22) 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 816f070c2016ffff or...
Page 668
816f070c-2581ffff configuration error for [physicalmemoryelementname] on subsystem [memoryelementname]has deasserted. (all dimms) 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 816f070c2581ffff ...
Page 669
816f070d-0402ffff rebuild completed for array in system [computersystemelementname]. (drive 2) explanation: this message is for the use case when an implementation has detected that an array rebuild has completed. May also be shown as 816f070d0402ffff or 0x816f070d0402ffff severity: info alert categ...
Page 670
816f070d-0405ffff rebuild completed for array in system [computersystemelementname]. (drive 5) explanation: this message is for the use case when an implementation has detected that an array rebuild has completed. May also be shown as 816f070d0405ffff or 0x816f070d0405ffff severity: info alert categ...
Page 671
816f0807-0301ffff [processorelementname] has been enabled. (cpu 1) explanation: this message is for the use case when an implementation has detected a processor has been enabled. May also be shown as 816f08070301ffff or 0x816f08070301ffff severity: info alert category: system - other serviceable: no...
Page 672
816f0813-2581ffff system [computersystemelementname]has recovered from an uncorrectable bus error. (dimms) 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 816f08132581ffff or 0x816f08...
Page 673
816f090c-2001ffff [physicalmemoryelementname] on subsystem [memoryelementname] is no longer throttled. (dimm 1) explanation: this message is for the use case when an implementation has detected memory is no longer throttled. May also be shown as 816f090c2001ffff or 0x816f090c2001ffff severity: info ...
Page 674
816f090c-2004ffff [physicalmemoryelementname] on subsystem [memoryelementname] is no longer throttled. (dimm 4) explanation: this message is for the use case when an implementation has detected memory is no longer throttled. May also be shown as 816f090c2004ffff or 0x816f090c2004ffff severity: info ...
Page 675
816f090c-2007ffff [physicalmemoryelementname] on subsystem [memoryelementname] is no longer throttled. (dimm 7) explanation: this message is for the use case when an implementation has detected memory is no longer throttled. May also be shown as 816f090c2007ffff or 0x816f090c2007ffff severity: info ...
Page 676
816f090c-200affff [physicalmemoryelementname] on subsystem [memoryelementname] is no longer throttled. (dimm 10) explanation: this message is for the use case when an implementation has detected memory is no longer throttled. May also be shown as 816f090c200affff or 0x816f090c200affff severity: info...
Page 677
816f090c-200dffff [physicalmemoryelementname] on subsystem [memoryelementname] is no longer throttled. (dimm 13) explanation: this message is for the use case when an implementation has detected memory is no longer throttled. May also be shown as 816f090c200dffff or 0x816f090c200dffff severity: info...
Page 678
816f090c-2010ffff [physicalmemoryelementname] on subsystem [memoryelementname] is no longer throttled. (dimm 16) explanation: this message is for the use case when an implementation has detected memory is no longer throttled. May also be shown as 816f090c2010ffff or 0x816f090c2010ffff severity: info...
Page 679
816f090c-2013ffff [physicalmemoryelementname] on subsystem [memoryelementname] is no longer throttled. (dimm 19) explanation: this message is for the use case when an implementation has detected memory is no longer throttled. May also be shown as 816f090c2013ffff or 0x816f090c2013ffff severity: info...
Page 680
816f090c-2016ffff [physicalmemoryelementname] on subsystem [memoryelementname] is no longer throttled. (dimm 22) explanation: this message is for the use case when an implementation has detected memory is no longer throttled. May also be shown as 816f090c2016ffff or 0x816f090c2016ffff severity: info...
Page 681
816f0a07-0301ffff the processor [processorelementname] is no longer operating in a degraded state. (cpu 1) explanation: this message is for the use case when an implementation has detected a processor is no longer running in the degraded state. May also be shown as 816f0a070301ffff or 0x816f0a070301...
Page 682
816f0a0c-2002ffff an over-temperature condition has been removed 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 removed. May also be...
Page 683
816f0a0c-2005ffff an over-temperature condition has been removed on the [physicalmemoryelementname] on subsystem [memoryelementname]. (dimm 5) 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 684
816f0a0c-2008ffff an over-temperature condition has been removed 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 removed. May also be...
Page 685
816f0a0c-200bffff an over-temperature condition has been removed on the [physicalmemoryelementname] on subsystem [memoryelementname]. (dimm 11) 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 686
816f0a0c-200effff an over-temperature condition has been removed 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 removed. May also b...
Page 687
816f0a0c-2011ffff an over-temperature condition has been removed on the [physicalmemoryelementname] on subsystem [memoryelementname]. (dimm 17) 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 688
816f0a0c-2014ffff an over-temperature condition has been removed 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 removed. May also b...
Page 689
816f0a0c-2017ffff an over-temperature condition has been removed on the [physicalmemoryelementname] on subsystem [memoryelementname]. (dimm 23) 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 690
816f0a13-0302ffff system [computersystemelementname] has recovered from a fatal bus error. (cpu 2 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 816f0a130302ffff or 0x816f0a130302ffff se...
Page 691
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 692
I.11002 [i.11002] a processor mismatch has been detected between one or more processors in the system. Explanation: one or more mismatched processors detected severity: error user response: complete the following steps: 1. This message could occur with messages about other processor configuration pr...
Page 693
I.18007 [i.18007] a power segment mismatch has been detected for one or more processor packages. Explanation: processors have mismatched power segments severity: error user response: complete the following steps: 1. Processors installed do not have the same power requirements 2. Ensure that all proc...
Page 694
I.1800b [i.1800b] a cache size mismatch has been detected for one or more processor packages. Explanation: processors have one or more cache levels with mismatched size severity: error user response: complete the following steps: 1. Verify that matching processors are installed in the correct proces...
Page 695
I.1800f [i.1800f] a processor family mismatch has been detected for one or more processor packages. Explanation: processors have mismatched family severity: error user response: complete the following steps: 1. Verify that matching processors are installed in the correct processor sockets according ...
Page 696
I.3048005 [i.3048005] uefi has booted from the backup flash bank. Explanation: booting backup uefi image severity: info user response: complete the following steps: 1. Refer to service information for this product section on uefi recovery to return system to primary bank. I.3808004 [i.3808004] the i...
Page 697
I.58015 [i.58015] memory spare copy initiated. Explanation: spare copy started severity: info user response: complete the following steps: 1. No user required for this event. This is for informational purposes only. I.580a4 [i.580a4] memory population change detected. Explanation: dimm population ch...
Page 698
S.1100c [s.1100c] an uncorrectable error has been detected on processor %. Explanation: uncorrectable processor error detected severity: error user response: complete the following steps: 1. Check ibm support site for an applicable service bulletin or firmware update that applies to this error. 2. R...
Page 699
S.3020007 [s.3020007] a firmware fault has been detected in the uefi image. Explanation: 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 700
S.3050007 [s.3050007] a firmware fault has been detected in the uefi image. Explanation: 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 701
S.3108007 [s.3108007 ] the default system settings have been restored. Explanation: system configuration restored to defaults severity: error user response: complete the following steps: 1. Check ibm support site for an applicable service bulletin or firmware update that applies to this error. S.381...
Page 702
S.51006 [s.51006] a memory mismatch has been detected. Please verify that the memory configuration is valid. Explanation: one or more mismatched dimms detected severity: error user response: complete the following steps: 1. Could follow an uncorrectable memory error or failed memory test. Check log ...
Page 703
S.68005 [s.68005] 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. Explanation: critical ioh-pc...
Page 704
W.3048006 [w.3048006] uefi has booted from the backup flash bank due to an automatic boot recovery (abr) event. Explanation: automated boot recovery, booting backup uefi image severity: warning user response: complete the following steps: 1. Check ibm support site for an applicable service bulletin ...
Page 705
W.305800b [w.305800b] driver health protocol: reports 'reboot' required controller. Explanation: driver health protocol: reports 'reboot' required controller severity: warning user response: complete the following steps: 1. No action required – system will reboot at the end of post. 2. If problem pe...
Page 706
W.3108002 [w.305800e] driver health protocol: reports invalid health status driver. Explanation: gpt (guid partition table) corruption severity: warning user response: complete the following steps: 1. F1 setup -> system settings -> recovery -> disk gpt recovery, set to "automatic"; save settings, th...
Page 707
W.3818005 [w.3818005] the crtm flash driver could not successfully flash the staging area. The update was aborted explanation: crtm update aborted severity: warning user response: complete the following steps: 1. Continue booting system. If system does not reset, manually reset the system. 2. If the...
Page 708
5. Check ibm support site for an applicable service bulletins (service bulletins) that applies to this memory error. (link to ibm support service bulletins) 6. (trained service technician only) if problem continues to re-occur on the same dimm connector, inspect dimm connector for foreign material a...
Page 709
W.68002 [w.68002] a cmos battery error has been detected explanation: cmos battery fault severity: error user response: complete the following steps: 1. If the system was recently installed, moved, or serviced, makesure the batter is properly seated. 2. Check ibm support site for an applicable servi...
Page 710
692 ibm system x3550 m4 type 7914: installation and service guide.
Page 711
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 712
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 713
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 714
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 715
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 716
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 717
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 718
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 719
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 720
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 721
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 722
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 723
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 724
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 725
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 726
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 727
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 728
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 729
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 730
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 731
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 732
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 733
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 734
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 735
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 736
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 737
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 738
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 739
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 740
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 741
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 742
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 743
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 744
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 745
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 746
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 747
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 748
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 749
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 750
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 751
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 752
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 753
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 754
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 755
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 756
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 757
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 758
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 759
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 760
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 761
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 762
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 763
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 764
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 765
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 766
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 767
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 768
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 769
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 770
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 771
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 772
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 773
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 774
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 775
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 776
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 777
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 778
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 779
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 780
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 781
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 782
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 783
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 784
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 785
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 786
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 787
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 788
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 789
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 790
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 791
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 792
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 793
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 794
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 795
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 796
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 797
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 798
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 799
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 800
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 801
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 802
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 803
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 804
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 805
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 806
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 807
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 808
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 809
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 810
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 811
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 812
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 813
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 814
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 815
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 816
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 817
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 818
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 819
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 820
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 821
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 822
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 823
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 824
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 825
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 826
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 827
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 828
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 829
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 830
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 831
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 832
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 833
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 834
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 835
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 836
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 837
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 838
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 839
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 840
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 841
166-905-001 imm i2c test failed explanation: imm indicates failure in max7319 device bus (bus 4). Severity: error serviceable: yes recoverable: no automatically notify support: no user response: perform the actions mentioned one at a time and try the test after each action: 1. Turn off the system an...
Page 842
166-908-001 imm i2c test failed explanation: imm indicates failure in pca9567 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 843
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 844
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 845
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 846
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 847
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 848
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 849
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 850
832 ibm system x3550 m4 type 7914: installation and service guide.
Page 851
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 852
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 853
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 854
Table 30. 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 855
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 856
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 857
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 858
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 859
Taiwan class a compliance statement notices 841.
Page 860
842 ibm system x3550 m4 type 7914: installation and service guide.
Page 861
Index numerics 2.5-inch hot-swap hard disk drive ids 39, 220 2.5-inch simple-swap hard disk drive ids 40, 224 3.5-inch hot-swap hard disk drive ids 39, 221 3.5-inch simple-swap hard disk drive ids 40, 225 4 pac hdd option, installing 93 a abr, automatic boot recovery 182 ac power-supply leds 142 ac ...
Page 862
Documentation (continued) format 836 updates 1 using 830 documentation, updated finding 5 drive ids 39, 220, 224 installing 38 dsa edition 150 program, overview 149 test log, viewing 152 text message format 152 dsa log 146, 147 dsa portable 132, 150 dsa preboot 132, 150 dsa, sending data to ibm 26, ...
Page 863
Imm heartbeat led 145 imm host name 116 imm web interface 117 imm2 102 error messages 335 important notices 6, 834 in-band automated boot recovery method 181 manual recovery method 180 information center 830 inspecting for unsafe conditions ix installation guidelines 33 installation guidelines 33 in...
Page 864
Pci riser-card leds location 145 pci riser-card assembly removing 244 replacing 245 pci riser-card bracket removing 246 replacing 247 people's republic of china class a electronic emission statement 840 post 149 event log 147 post event log 146 post/uefi diagnostic codes 673 power power-control butt...
Page 865
Russia class a electronic emission statement 840 s safety vii safety information 6 safety statements vii, xi sas/sata 4 pac hdd option installing 93 sas/sata controller installing 60 removing 254 replacing 255 sas/sata serveraid controller 198 sending diagnostic data to ibm 26, 830 serial number 1 l...
Page 866
848 ibm system x3550 m4 type 7914: installation and service guide.
Page 868
Part number: 00kc050 printed in usa (1p) p/n: 00kc050