Sun Oracle Blade X4-2B Service Manual

Sun Blade X4-2B Service Manual

Part No: E37039–04 March, 2014

This software and related documentation are provided under a license agreement containing restrictions on use and disclosure and are protected by intellectual property laws. Except as expressly permitted in your license agreement or allowed by law, you may not use, copy, reproduce, translate, broadcast, modify, license, transmit, distribute, exhibit, perform, publish, or display any part, in any form, or by any means. Reverse engineering, disassembly, or decompilation of this software, unless required by law for interoperability, is prohibited.

The information contained herein is subject to change without notice and is not warranted to be error-free. Ifyou nd any errors, please report them to us in writing.

If this is software or related documentation that is delivered to the U.S. Government or anyone licensing it on behalf of the U.S. Government, the following notice is applicable:

U.S. GOVERNMENT END USERS. Oracle programs, including any operating system, integrated software, any programs installed on the hardware, and/or documentation, delivered to U.S. Government end users are "commercial computer software" pursuant to the applicable Federal Acquisition Regulation and agency-specic supplemental regulations. As such, use, duplication, disclosure, modication, and adaptation of the programs, including any operating system, integrated software, any programs installed on the hardware, and/or documentation, shall be subject to license terms and license restrictions applicable to the programs. No other rights are granted to the U.S. Government.

This software or hardware is developed for general use in a variety of information management applications. It is not developed or intended for use in any inherently dangerous applications, including applications that may create a risk of personal injury. If you use this software or hardware in dangerous applications, then you shall be responsible to take all appropriate fail-safe, backup, redundancy, and other measures to ensure its safe use. Oracle Corporation and its aliates disclaim any liability for any damages caused by use of this software or hardware in dangerous applications.

Oracle and Java are registered trademarks of Oracle and/or its aliates. Other names may be trademarks of their respective owners.

Intel and Intel Xeon are trademarks or registered trademarks of Intel Corporation. All SPARC trademarks are used under license and are trademarks or registered trademarks of SPARC International, Inc. AMD, Opteron, the AMD logo, and the AMD Opteron logo are trademarks or registered trademarks of Advanced Micro Devices. UNIX is a registered trademark of The Open Group.

This software or hardware and documentation may provide access to or information on content, products, and services from third parties. Oracle Corporation and its aliates are not responsible or and expressly disclaim all warranties of any kind with respect to third-party content, products, and services. Oracle Corporation and its aliates will not be responsible for any loss, costs, or damages incurred due to your access to or use of third-party content, products, or services.

Ce logiciel et la documentation qui l’accompagnesont protégés par les lois sur la propriété intellectuelle. Ils sont concédés sous licence et soumis à des restrictions d’utilisation et de divulgation. Sauf disposition de votre contrat de licence ou de la loi, vous ne pouvez pas copier, reproduire, traduire, diuser, modier, breveter, transmettre, distribuer, exposer, exécuter, publier ou acher le logiciel, même partiellement, sous quelque forme et par quelque procédé que ce soit. Par ailleurs, il est interdit de procéder à toute ingénierie inverse du logiciel, de le désassembler ou de le décompiler, excepté à des ns d’interopérabilité avec des logiciels tiers ou tel que prescrit par la loi.

Les informations fournies dans ce document sont susceptibles de modication sans préavis. Par ailleurs, Oracle Corporation ne garantit pas qu’elles soient exemptes d’erreurs et vous invite, le cas échéant, à lui en faire part par écrit.

Si ce logiciel, ou la documentation qui l’accompagne,est concédé sous licence au Gouvernement des Etats-Unis, ou à toute entité qui délivre la licence de ce logiciel ou l’utilise pour le compte du Gouvernement des Etats-Unis, la notice suivante s’applique:

Ce logiciel ou matériel a été développé pour un usage général dans le cadre d’applications de gestion des informations. Ce logiciel ou matériel n’est pas conçu ni n’est destiné à être utilisé dans des applications à risque, notamment dans des applications pouvant causer des dommages corporels. Si vous utilisez ce logiciel ou matériel dans le cadre d’applications dangereuses, il est de votre responsabilité de prendre toutes les mesures de secours, de sauvegarde, de redondance et autres mesures nécessaires à son utilisation dans des conditions optimales de sécurité. Oracle Corporation et ses aliés déclinent toute responsabilité quant aux dommages causés par l’utilisation de ce logiciel ou matériel pour ce type d’applications.

Oracle et Java sont des marques déposées d’OracleCorporation et/ou de ses aliés. Tout autre nom mentionné peut correspondre à des marques appartenant à d’autrespropriétaires qu’Oracle.

Intel et Intel Xeon sont des marques ou des marques déposées d’Intel Corporation.Toutes les marques SPARCsont utilisées sous licence et sont des marques ou des marques déposées de SPARC International, Inc. AMD, Opteron, le logo AMD et le logo AMD Opteron sont des marques ou des marques déposées d’Advanced Micro Devices. UNIX est une marque déposée d’The Open Group.

Ce logiciel ou matériel et la documentation qui l’accompagne peuvent fournir des informations ou des liens donnant accès à des contenus, des produits et des services émanant de tiers. Oracle Corporation et ses aliés déclinent toute responsabilité ou garantie expresse quant aux contenus, produits ou services émanant de tiers. En aucun cas, Oracle Corporation et ses aliés ne sauraient être tenus pour responsables des pertes subies, des coûts occasionnés ou des dommages causés par l’accès à des contenus, produits ou services tiers, ou à leur utilisation.

140306@25097

Contents

Using This Documentation ...................................................................................................................5

Sun Blade X4-2B Model Name ......................................................................................................5

Getting the Latest Firmware and Software ...................................................................................5

Documentation and Feedback ......................................................................................................6

About This Documentation ...........................................................................................................6

Support and Training .....................................................................................................................7

Access to Oracle Support ...............................................................................................................7

Contributors ....................................................................................................................................7

Change History ...............................................................................................................................7

Service Manual Overview ......................................................................................................................9

About the Sun Blade X4-2B ................................................................................................................ 11

Product Description .................................................................................................................... 11

About Front and Rear Panels ...................................................................................................... 12

About the Chassis ......................................................................................................................... 21

About System Components ........................................................................................................ 24

Troubleshooting the Server Module ................................................................................................. 29

Troubleshooting Server Module Hardware Faults .................................................................. 29

Diagnostic Tools .......................................................................................................................... 36

Troubleshooting and Diagnostic Information ......................................................................... 37

Gather Service Information ........................................................................................................38

Locate the Server Module Serial Number .................................................................................. 38

Troubleshoot Server Module Power Problems ........................................................................ 39

About the DIMM and Processor Test Circuit .......................................................................... 41

Recover the SP Firmware Using the Preboot Menu (Service Only) ....................................... 41

Preparing for Service ........................................................................................................................... 43

Preparing the Server Module for Component Replacement .................................................. 43

Powering Down the Server Module ........................................................................................... 47

Performing ESD and Anti-static Prevention Measures ........................................................... 53

Remove the Server Module from the Sun Blade Chassis ......................................................... 55

Server Module and Component Filler Panels ........................................................................... 56

Install Server Module Filler Panels ............................................................................................. 57

Remove the Server Module Top Cover ..................................................................................... 58

Turning the Locate Indicator On and O ................................................................................. 59

Required Tools ............................................................................................................................. 61

FRU TLI Auto-Update ................................................................................................................ 61

Servicing Server Module Components ............................................................................................. 63

Servicing a Storage Drive (CRU) ................................................................................................ 63

Servicing DIMMs (CRU) ............................................................................................................ 74

Servicing USB Flash Sticks (CRU) ............................................................................................. 84

Servicing a Fabric Expansion Module (CRU) ........................................................................... 87

Servicing a RAID Expansion Module (CRU) ........................................................................... 89

Servicing Processors (FRU) ........................................................................................................94

Servicing the Motherboard Assembly (FRU) ......................................................................... 117

Servicing the System Battery (CRU) ........................................................................................ 125

Returning the Server Module to Operation .................................................................................... 127

Return the Server Module to Operation .................................................................................. 127

Install the Server Module Top Cover ....................................................................................... 128

Remove Server Module Filler Panel ......................................................................................... 129

Install the Server Module in the Chassis .................................................................................. 130

Powering On the Server Module .............................................................................................. 131

BIOS Power-On Self-Test (POST) Checkpoints ........................................................................... 135

POST Code Checkpoint Memory Testing .............................................................................. 135

Viewing POST Code Checkpoints ........................................................................................... 136

POST Code Checkpoint Reference .......................................................................................... 137

BIOS Setup Utility Menu Options ................................................................................................... 147

BIOS Main Menu Selections ..................................................................................................... 147

BIOS Advanced Menu Selections ............................................................................................. 155

BIOS I/O Menu Selections ........................................................................................................ 165

BIOS Boot Menu Selections ...................................................................................................... 173

BIOS Save and Exit Menu Selections ....................................................................................... 175

Index ................................................................................................................................................... 177

Contents

Sun Blade X4-2B ServiceManual • March, 20144

UsingThis Documentation

This section describes how to get the latest rmware and software for the system, documentation and feedback, and a document change history.

■

“Sun Blade X4-2B Model Name ” on page 5

■

“Getting the Latest Firmware and Software” on page 5

■

“Documentation and Feedback” on page 6

■

“About This Documentation” on page 6

■

“Support and Training” on page 7

■

“Contributors” on page 7

■

“Change History” on page 7

Sun Blade X4-2B Model Name

The name identies the following:

■

1: The alpha character, X, identies an x86 product.

■

2: The rst number, 4, identies the generation of the server.

■

3: The second number, 2, identies the number of processors.

■

4: The alpha character, B, identies the product as a blade server.

Getting the Latest Firmware and Software

Firmware, drivers, and other hardware-related software for each Oracle x86 server, server module (blade), and blade chassis are updated periodically.

You can obtain the latest version in one of three ways:

■

Oracle System Assistant – This is a factory-installed option for Sun Oracle x86 servers. It has all the tools and drivers you need and resides on a USB drive installed in most servers.

■

My Oracle Support – http://support.oracle.com

■

Physical media request

For more information, see

Oracle x86 Administration Guide for X4 Series Servers

(http://www.oracle.com/goto/x86AdminDiag/docs).

Documentation and Feedback

Documentation Link

All Oracle products http://www.oracle.com/documentation

Sun Blade X4-2B server module http://www.oracle.com/goto/X4-2B/docs

X4 server series system administration Oracle x86 Administration Guide for X4 Series

Servers (http://www.oracle.com/goto/ x86AdminDiag/docs)

Oracle System Assistant Oracle x86 Administration Guide for X4 Series

Servers (http://www.oracle.com/goto/ x86AdminDiag/docs)

Oracle Integrated Lights Out Manager(ILOM) 3.1 http://www.oracle.com/goto/ILOM/docs

Oracle Hardware Management Pack http://www.oracle.com/goto/OHMP/docs

Chassis Sun Blade 6000 modular system http://www.oracle.com/goto/SB6000/docs

Provide feedback on this documentation at: http://www.oracle.com/goto/docfeedback.

About This Documentation

This documentation set is available in both PDF and HTML. The information is presented in topic-based format (similar to online help) and therefore does not include chapters, appendixes, or section numbering.

You can generate a PDF that includes all information about a particular topic subject (such as hardware installation or product notes) can be generated by clicking the PDF button in the upper left corner of the HTML page.

Documentation and Feedback

Sun Blade X4-2B ServiceManual • March, 20146

Support and Training

These web sites provide additional resources:

■

Support: http://support.oracle.com

■

Training: http://education.oracle.com

Access to Oracle Support

Oracle customers have access to electronic support through My Oracle Support. For information, visit

http://www.oracle.com/pls/topic/lookup?ctx=acc&id=info or visit

http://www.oracle.com/pls/topic/lookup?ctx=acc&id=trs if you are hearing impaired.

Contributors

Primary Authors: Lisa Kuder, Ray Angelo, Mark McGothigan.

Contributors: Mike Ma, Qing-su Hu, Lu Wei, Cynthia Chin-Lee, Michael Tabor, Ralph Woodley, Ling Chen, Qing Gu, Donghua Zhou, David Zhuang.

Change History

The following lists the release history of this documentation set:

■

September 2013. Initial publication.

■

March 2013. Software 1.1 update.

Change History

Service Manual Overview

The Sun Blade X4-2B Service Manual contains service and maintenance procedures for the Sun Blade X4-2B server module. The major sections of this manual are described in the following table.

Description Link

Overview of the server module features and components.

“About the Sun Blade X4-2B” on page 11

Troubleshooting and corrective maintenance-related information.

“Troubleshooting the Server Module” on page 29

Procedures for preparing to service the server module and powering o the server module.

“Preparing for Service ” on page 43

Procedures for removal and installation of server module components.

“Servicing Server Module Components ” on page 63

Procedures for returning the server to operation and powering on the server module.

“Returning the Server Module to Operation ” on page 127

Information about POST code checkpoint testing, provides methods to view POST checkpoint codes, lists the POST code checkpoints, and describes how to congure POST code checkpoint options.

“BIOS Power-On Self-Test (POST) Checkpoints ” on page 135

Information about BIOS Setup Utility screen selections and setup options.

“BIOS Setup Utility Menu Options” on page 147

About the Sun Blade X4-2B

These sections describe the controls, connectors, LEDs, system components and replaceable components of the server module.

Description Link

Review the product overview. “Product Description” on

page 11

Identify status indicators, features, and components of server front and rear panels.

“About Front and Rear Panels” on page 12

Review Sun Blade 6000 chassis, ILOM and CMM components and functions.

“About the Chassis” on page 21

Review replaceable components and component serviceability.

“About System Components” on page 24

Product Description

Oracle's Sun Blade X4-2B server module consists of two processors (from the Intel ® Xeon ® processor E5-2600 V2 processor family), and 24 DIMM slots for a maximum of 768 GB of memory. The blade server module is inserted in to a Sun Blade 6000 chassis, which provides power and cooling to the blades. The Sun Blade X4-2B server module is an ideal blade for building enterprise cloud infrastructures.

Optional I/O modules can be installed. A RAID expansion module (REM) is installed on the Sun Blade X4-2B server module for RAID and SAS drive connectivity. A Fabric Expansion Module (FEM) is also installed on the server module. The FEM enables a connection to the Network Express Modules (NEMs) through the Sun Blade 6000 chassis' midplane. The Sun Blade X4-2B also features an on-board service processor (SP) to enable Oracle Integrated Lights Out Manager (ILOM). Oracle ILOM provides secure local and remote server management.

See Also:

■

“About Oracle ILOM ” on page 23

■

Sun Blade X4-2B Installation Guide

About Front and Rear Panels

This section describes the front and rear panels of the server module:

■

“Front Panel Indicators and Buttons” on page 13

■

“Rear Panel of the Server Module” on page 17

■

“UCP and the Multi-Port Dongle Cable” on page 19

Front Panel Features

The following illustration shows front panel features on the Sun Blade X4-2B.

About Front and Rear Panels

Sun Blade X4-2B ServiceManual • March, 201412

Figure Legend

1 Locate Button and Indicator– white 8 USB ports (2)

2 Ready to Remove Indicator – blue 9 Universal connector port (UCP)

3 Service Action Required Indicator – amber 10 Storage drive (HDD 0)

4 Power OK Indicator – green 11 Storage drive (HDD 1)

5 Power button 12 Storage drive (HDD 2)

6 NMI Reset button (Service only) 13 Storage drive (HDD 3)

7 RFID tag (with serial number) 14 Ejector levers

See Also:

“Front Panel Indicators and Buttons” on page 13

Front Panel Indicators and Buttons

The topics included in this section show the location of the Sun Blade X4-2B front panel indicators and buttons and describe their functions.

Location of Front Panel Indicators and Buttons

The following illustration shows the server module front panel indicator and button locations.

Front PanelIndicators and Buttons

Legend Name

1 Locate Button and Indicator – White

2 Ready To Remove Indicator – Blue

3 Service Action Required Indicator – Amber

4 Power Button

5 Power OK Indicator – Green

6 NMI Button – Service use only

Detailed descriptions and functions follow.

Locate Indicator Button

Front PanelIndicators and Buttons

Sun Blade X4-2B ServiceManual • March, 201414

Function:

■

Combination white indicator and button.

■

Activate the Locate Indicator remotely from Oracle ILOM to identify a server module within a chassis.

■

Press and hold the Locate Indicator button to activate the front panel lamp test.

■

See “Turning the Locate Indicator On and O” on page 59.

Ready ToRemove Indicator

Function:

■

Blue indicator.

■

Indicates when it is safe to remove the server module from the chassis.

■

O: Normal operation. Do not remove the server module.

■

On solid: The server module is ready to remove. See “Remove the Server Module from the

Sun Blade Chassis” on page 55

Service Action Required Indicator

Front PanelIndicators and Buttons

Function:

■

Amber LED.

■

Indicates a server module component fault.

■

O: Normal operation.

■

On solid: The server module has a fault. See “Troubleshooting the Server Module” on

page 29

PowerOK Indicator and Button

Function:

■

Green Indicator and recessed button.

■

Use the Power button to toggle the server between standby power and full power states.

■

Use a stylus to operate the Power button.

■

The Power/OK Indicator shows the status of the server power:

■

Service processor is booting: Fast blink

■

Host is booting: Slow blink at 1 Hz.

■

Standby power state (SP booted): Blink 0.2 seconds on, 2.8 seconds o

■

Full power state: On solid (does not blink)

■

For more information, see “About Server Power States and Resets” on page 47.

Front PanelIndicators and Buttons

Sun Blade X4-2B ServiceManual • March, 201416

NMI Button

Function:

The NMI (non-maskable interrupt) button is for service use only. Do not press.

See Also:

■

“About Front and Rear Panels” on page 12

■

“Rear Panel of the Server Module” on page 17

Rear Panel of the Server Module

The following illustration shows the rear panel features on the Sun Blade X4-2B.

Rear Panel of the Server Module

Figure Legend

1 Power connector 3 Protective shipping cover for rear connector

(remove before inserting into chassis)

2 I/O connector 4 USB ash sticks 2, 3 (P0 and P1)

See Also:

■

“About Front and Rear Panels” on page 12

■

“Front Panel Indicators and Buttons” on page 13

■

“The System Chassis” on page 21

Rear Panel of the Server Module

Sun Blade X4-2B ServiceManual • March, 201418

UCP and the Multi-Port Dongle Cable

The universal connector port (UCP) and the multi-port dongle cable provide a front panel local access point to the server module boot screen, the BIOS Setup Utility, the Oracle ILOM CLI, and Oracle System Assistant. From this access point you can perform server maintenance and setup tasks, including installing an OS.

The following illustration shows the interfaces available through the UCP using the three-connector multi-port cable.

Note – Multi-port cables are available in two varieties, a newer three cable version and a four

cable version. The four-port cable has a DB-9 serial connector, while the three-port cable does not.

UCP and the Multi-Port Dongle Cable

Figure Legend

1 DB-15 (video port)

2 RJ-45 (serial management port)

3 USB 2.0 (2 ports)

Note – Your chassis might ship with a DB-9-to-RJ-45 serial cable adapter. The adapter allows

you to attach a serial cable with a DB-9 connector to the server module using the RJ-45 port on the multi-port cable.

See Also:

UCP and the Multi-Port Dongle Cable

Sun Blade X4-2B ServiceManual • March, 201420

■

Sun Blade X4-2B Installation Guide

■

“Attach the Multi-Port Dongle Cable” on page 21

▼

Attach the Multi-Port Dongle Cable

Attach the multi-port dongle cable to the front of the server module using the universal connector port (UCP).

Note – The port does not provide a means to permanently attach the multi-port dongle cable.

The connection is intended for temporary usage. Disconnect the cable when nished.

Position the multi-port cable connector so the at side of the connectoraligns with the at side of the UCP.

Gently squeeze the sides ofthe multi-portcable connector and insert the multi-port cable into the UCP.

Connect the devices using the appropriate interfaces.

For an overview of the available interfaces on the multi-port cable, see

“UCP and the Multi-Port

Dongle Cable” on page 19

Caution – Component damage. When not in use, do not leave the cable attached to the server

module. The multi-port cable is designed for temporary use.

To disconnectthe multi-port cable, gently squeeze the sides of the cable connector and pull it away from the server module.

About the Chassis

This section includes Sun Blade 6000 modular system chassis information:

■

“The System Chassis” on page 21

■

“The Chassis Monitoring Module (CMM) ” on page 22

■

“About Oracle ILOM ” on page 23

The System Chassis

The Sun Blade X4-2B is used in a Sun Blade 6000 modular system chassis. When fully loaded, the chassis can hold a combination of up to ten storage modules and server modules. Server modules draw more power than storage modules, so power limitations apply to the number of server modules that can be installed in a Sun Blade 6000.

The System Chassis

For more information about the Sun Blade X4-2B conguration and compatibility, see

“Supported Hardware” in Sun Blade X4-2B Product Notes .

See Also:

■

Sun Blade 6000 Modular System Chassis documentation (http://www.oracle.com/pls/ topic/lookup?ctx=sb6000)

■

“The Chassis Monitoring Module (CMM) ” on page 22

■

“About Oracle ILOM ” on page 23

The Chassis Monitoring Module (CMM)

You manage the system and monitor the Sun Blade 6000 modular system chassis using the chassis monitoring module (CMM). The CMM allows you to monitor the status of the chassis and its components (including server modules and storage modules) using a chassis-level version of Oracle Integrated Lights Out Management (Oracle ILOM) rmware. CMM is a chassis-level version of Oracle ILOM provides a single point of management interaction for all chassis functions and components. You can access the CMM either remotely (using SSH or a Web browser) or locally (using a serial cable and a tip session).

With the CMM Oracle ILOM, you can:

■

Monitor the status of chassis and its server module and storage modules.

■

Send events using SNMP traps or e-mail alerts when errors and faults occur.

■

Troubleshoot errors and faults.

■

Remotely control the power state of server modules and blades.

■

Congure the server module BIOS settings.

The CMM is located on the rear of the chassis. The following illustration shows the back side of the chassis and the CMM indicator panel.

The Chassis Monitoring Module (CMM)

Sun Blade X4-2B ServiceManual • March, 201422

See Also:

■

Sun Blade 6000 Modular System documentation (http://docs.oracle.com/cd/ E19938-01/index.html)

■

“About Oracle ILOM ” on page 23

■

Oracle Integrated Lights Out Manager (ILOM) 3.1 Documentation Collection (http://www.oracle.com/pls/topic/lookup?ctx=ilom31)

About Oracle ILOM

Oracle's x86- and SPARC-based servers have an embedded service processor (SP) that contains a preinstalled system management rmware called Oracle Integrated Lights Out Manager (Oracle ILOM). Oracle ILOM enables you to access the server remotely or locally, regardless of the power-on state of the server, and actively manage and monitor the system.

With Oracle ILOM, you can:

■

Monitor the status of server module sensors and indicators.

■

Send events using SNMP traps or e-mail alerts when errors and faults occur.

■

Troubleshoot system and component errors and faults.

■

Remotely control the power state of your server module.

■

Congure the server module BIOS settings.

Oracle ILOM allows you to choose either a command-line interface (CLI) or a browser-based interface.

About Oracle ILOM

Note – The chassis also has Oracle ILOM installed on the chassis monitoring module (CMM),

which is used to manage chassis functions.

See Also:

■

“The Chassis Monitoring Module (CMM) ” on page 22

■

Oracle Integrated Lights Out Manager (ILOM) 3.1 Documentation Collection (http://www.oracle.com/pls/topic/lookup?ctx=ilom31)

■

Oracle x86 Administration Guide for X4 Series Servers (http://www.oracle.com/goto/ x86AdminDiag/docs)

About System Components

This section includes an illustrated parts breakdown, a replaceable component (CRU and FRU) list, and a component serviceability list:

■

“Illustrated Parts Breakdown” on page 24

■

“Replaceable Components (FRUs and CRUs)” on page 26

■

“Component Serviceability” on page 26

Note – Some Sun Blade X4-2B components are optional. Your server module might not contain

every replaceable component.

Illustrated Parts Breakdown

The following illustration and table identies the replaceable components for the Sun Blade X4-2B:

About System Components

Sun Blade X4-2B ServiceManual • March, 201424

Call Out Description Call Out Description

1 Storage drives (4 maximum, HDD or

SSD)

6 USB 2.0 sticks (0 and 1)

2 RAID expansion module (REM) 7 DIMMs DDR3 LV (24 maximum)

3 Processors (0 and 1) 8 System battery (type: CR2032 )

4 Heat sink assemblies (0 and 1) 9 Server module enclosure (Includes

motherboard, disk backplane, and enclosure assembly.)

5 Fabric expansion modules (FEM)

Note – FEMs are available in two form

factors (single-width and double-width).

See Also:

■

“About System Components” on page 24

■

“Install Server Module Filler Panels” on page 57

Illustrated Parts Breakdown

Replaceable Components (FRUs and CRUs)

The replaceable components in your Sun Blade X4-2B are designated as either eld-replaceable units (FRU) or customer-replaceable units (CRU). A part designated as a FRU must be replaced by an Oracle-qualied service technician.

The following table lists the FRU and CRU components.

Component Description Designation

HDDs or SSDs (and llers) CRU

DIMMs (and llers) CRU

Battery, system CRU

USB 2.0 drives (rear) CRU

FEM CRU

REM CRU

Processor and heat sink assembly (CPU) FRU

Motherboard and blade enclosure assembly FRU

See Also:

■

“About System Components” on page 24

Component Serviceability

Components are either hot serviceable or cold serviceable. Hot service capability allows you to safely remove this component while the server module is running. Cold service capability requires a powered o state, so you need to remove the server module from the chassis.

The following table lists the serviceability of components.

Component Description Serviceability

HDDs or SSDs (and llers)

Hot

DIMMs (and optional llers) Cold

Battery, system Cold

USB 2.0 drives (rear)

Cold

For instructions on safe removal of HDDs or SSDs, consult your operating system .

Server module must be removed from the chassis to access.

Replaceable Components (FRUs and CRUs)

Sun Blade X4-2B ServiceManual • March, 201426

Component Description Serviceability

FEM Cold

REM Cold

Processor and heat sink assembly (CPU) Cold

Motherboard and blade enclosure assembly Cold

See Also:

■

“About System Components” on page 24

Component Serviceability

Troubleshooting the Server Module

These sections introduce the diagnostic tools and strategies available to help you diagnose problems with the Sun Blade X4-2B.

Description Link

Troubleshoot server hardware problems.

“Troubleshooting Server Module Hardware Faults” on page 29

Find additional troubleshooting and diagnostic information.

“Troubleshooting and Diagnostic Information” on page 37

Understand the motherboard-based test circuit.

“About the DIMM and Processor Test Circuit ” on page 41

Gather information about the system to help a service engineer or technician work on your system.

“Gather Service Information” on page 38

Investigate power issues. “Troubleshoot Server

Module Power Problems” on page 39

Recover the SP rmware (Service personnel only).

“Recover the SP Firmware Using the Preboot Menu (Service Only)” on page 41

Troubleshooting Server Module Hardware Faults

When a server hardware problem occurs, the system lights the Service Action Required indicator and captures it as an event in the system event log (SEL). If you have set up notications through Oracle ILOM, you also receive an alert through the notication method you chose. When notied that a hardware fault has occurred, you should investigate it immediately.

Use the following to investigate a hardware-related fault:

■

“Service Troubleshooting Task List” on page 30

■

“Troubleshoot Hardware Faults” on page 31

Service Troubleshooting Task List

These tasks provide an overview for troubleshooting a hardware fault.

Step Task Link

1 Gather Service Information. “Gather Service Information” on

page 38

2 Identify the failed component.

Use Oracle ILOM web interface or CLI to identify the server subsystem and failed component.

“Troubleshooting Server Module Hardware Faults” on page 29

3 Review the server Product Notes.

After you have identied the failed component, review the most recent Product Notes for the server. The product notes contains up-to-date information about the server, including hardware-related issues that may aect the failed component.

http://www.oracle.com/

goto/X4-2B/docs

4 Prepare the server for service.

If you have determined that the hardware fault requires service (physical access to the server), use Oracle ILOM to power o the server, activate the Locate indicator, and take the server oine.

Before removing the server module from the chassis, prepare the work space, and ensure ESD protection for the server and components.

“Preparing for Service ” on page 43

5 Service components.

To service the components, see the removal, installation, and replacement procedures in this document.

Note – A component designated as FRU must be replaced by

Oracle Service personnel. Contact Oracle Service.

“Servicing Server Module Components ” on page 63

6 Return the server to service .

Before placing the server module into the chassis, prepare the work space, ensuring ESD protection for the server and components.

“Returning the Server Module to Operation ” on page 127

Service TroubleshootingTask List

Sun Blade X4-2B ServiceManual • March, 201430

Step Task Link

7 Clear the fault in Oracle ILOM.

Optional: Depending on the component, you might need to clear the fault in Oracle ILOM.

“About Oracle ILOM” on page 23

Next Steps:

■

See “Troubleshoot Hardware Faults” on page 31

▼

Troubleshoot Hardware Faults

This procedure provides an example of troubleshooting hardware faults.This procedure expands upon the basic steps described in

“Service Troubleshooting Task List” on page 30.

Use this procedure to troubleshoot hardware faults with the Oracle ILOM web interface and, if necessary, prepare the server for service.

Note – This procedure uses a combination of the Oracle ILOM web and CLI interfaces.

However, the procedure can be performed using only the Oracle ILOM CLI interface. For more information, refer to the Oracle ILOM documentation at

http://www.oracle.com/goto/

ILOM/docs

Review the server module Product Notes for information about the server,problem, or hardware.

The Product Notes contains up-to-date information about the server, including hardware-related issues.

Access Oracle ILOM CMM.

The CMM provides an overview of all chassis subsystems to help you isolate the fault.

■

Open a web browser.

■

Type in the CMM SP IP address.

■

At the log-in screen, enter a login with root or administrator privileges.

identify the chassis subsystem that requires service.

View the ILOM Summary screen Status section, Status section of the Summary screen for information about the following chassis subsystems:

■

Blades

■

Power

■

Cooling

■

Storage

Service TroubleshootingTask List

■

I/O Modules

In the following example, the Status section indicates that service is required on one of the blades in the blades subsystem, and the Open Problems link in the left navigation panel shows one (1) logged problem:

View specic informationby clicking Open Problems in the left navigationpanel.

The Open Problems screen provides detailed information about the issue, such as the time the event occurred, the component, the subsystem, and a description.

Service TroubleshootingTask List

Sun Blade X4-2B ServiceManual • March, 201432

In the following example, the Open Problems screen indicates that a problem has occurred on blade 2 (BL2):

View the SystemLog.

The System Log provides additional detailed information about the error (event), including the severity, the component or subsystem, and the date and time the event occurred.

Access the servermodule Oracle ILOM.

The server module Oracle ILOM provides specic information about the server module and its components.

a. Access a web browser.

b. Type in the server module SP IP address.

c. At the log-in screen, enter a login with root or administrator privileges.

View the Summary screen Statussection for service required and other error indications.

Identify the component that is in a fault state from the server module Oracle ILOM web interface.

The Status section provides information for the following subsystems:

■

Processors

■

Memory

■

Power

■

Cooling

■

Storage

■

Networking

Service TroubleshootingTask List

■

I/O Modules

In the following example, the server module Status section shows that the Memory subsystem requires service:

Click the Open Problems link in the left navigation panel.

The Open Problems screen provides detailed information about the issue, such as the time the event occurred, the component, the subsystem, and a description.

Service TroubleshootingTask List

Sun Blade X4-2B ServiceManual • March, 201434

In the following example, the Open Problems screen indicates that DIMM 8 on CPU 0 has an uncorrectable ECC fault. In this example, the hardware fault with DIMM 8 of CPU 0 on blade 2 (BL2) requires local access to the server.

View the SystemLog.

The System Log provides additional detailed information about the error (event), including the severity, the component or subsystem, and the date and time the event occurred.

Replace the failed component.

a. To prepare the server for service,see

“Preparing the Server Module forComponent

Replacement”on page 43

b. To service components, see

“Servicing Server Module Components”on page 63.

c. To return the server to service, see

“Returning the Server Module to Operation ” on page 127.

After servicingthe component, you might need to clear the fault in Oracle ILOM.

Refer the component service procedure for more information. See

“Servicing Server Module

Components ” on page 63

■

“Service Troubleshooting Task List” on page 30

■

“Troubleshooting and Diagnostic Information” on page 37

■

“Preparing the Server Module for Component Replacement” on page 43

See Also

Service TroubleshootingTask List

Diagnostic Tools

There are a variety of diagnostic tools, commands, and indicators you can use to monitor and troubleshoot the server:

■

LEDs – These indicators provide a quick visual notication of the status of the server and of some of the CRUs and FRUs.

■

Oracle ILOM rmware – Firmware is located on the service processor and provides a comprehensive service portal via a command-line interface (CLI) and browser user interface (BUI) for lights-out management capabilities (remote power-on, power-o), monitoring of the health of environmental subsystems (power, fans, temperature, interlock), and fault management and automated diagnosis capabilities during server initialization (QuickPath Interconnect code and Memory Reference code), and runtime of the server.

■

Diagnostics – Accessed through Oracle ILOM, the DOS-based Pc-Check utility tests motherboard components such as processor, memory and I/O, as well as ports and slots. If enabled through Oracle ILOM, this utility will run each time the system powers on. For information about Pc-Check, refer to the Oracle x86 Servers Diagnostics, Applications, and Utilities Guide for Servers With Oracle ILOM 3.1 at http://www.oracle.com/goto/x86AdminDiag/docs.

■

POST – Power-on self-test (POST) performs diagnostics on system components upon system power-on and resets to ensure the integrity of those components. POST messages are displayed and logged in the BIOS event logs. POST works with Oracle ILOM to take faulty components oine, if needed.

■

SNMP – Simple Network Management Protocol traps are generated by the SNMP agents that are installed on the SNMP devices being managed by Oracle ILOM. Oracle ILOM receives the SNMP traps and converts them into SNMP event messages that appear in the event log.

■

Oracle Solaris OS Diagnostic Tools

■

Oracle Solaris OS Predictive Self-Healing (PSH) – The PSH technology provides automated diagnosis of error events encountered with the processor, memory subsystem, and Integrated I/O subsystem during runtime. The ability of PSH to o-line faulty processors and retire memory pages during runtime enhances system availability and prevents future interruptions. The Solaris PSH technology, ILOM, and BIOS provide extensive fault management architecture for placing processors oine and disabling of DIMMs.

■

Log les and console messages – These items provide the standard Solaris OS log les and investigative commands that can be accessed and displayed on the device of your choice.

■

Oracle VTS software – This application exercises the system, provides hardware validation, and discloses possible faulty components with recommendations for repair.

Diagnostic Tools

Sun Blade X4-2B ServiceManual • March, 201436

The LEDs, Oracle ILOM, Oracle Solaris OS PSH, and many of the log les and console messages are integrated. For example, Oracle Solaris software will display a detected fault, log it, pass information to Oracle ILOM, where it will be logged, and depending on the fault, might cause one or more LEDs to light.

Related Information:

■

“About Front and Rear Panels” on page 12

■

http://www.oracle.com/goto/ILOM/docs

■

http://www.oracle.com/goto/x86AdminDiag/docs

■

“BIOS Power-On Self-Test (POST) Checkpoints ” on page 135

Troubleshooting and Diagnostic Information

The following table lists diagnostic and troubleshooting-related procedures and references that can assist you with resolving server issues.

Information About: Link

Dagnostic tools for the Sun Blade X4-2B server and other X-4 series servers, including procedures for performing runtime and rmware-based tests, using Oracle ILOM, and running U-Boot and Pc-Check to exercise the system and isolate intermittent hardware-related problems.

x86 Diagnostics Guide

■

Administration of Sun Blade X4-2B server modules and other X4 series servers.

■

How to use Oracle System Assistant.

■

How to use Oracle ILOM system event logs (SEL) to identify a problem's possible source.

http://www.oracle.com/goto/x86AdminDiag/docs

How to use the DIMM and processor test circuit. “About the DIMM and Processor Test Circuit ” on

page 41

How to troubleshoot server module power issues. “Troubleshoot Server Module PowerProblems” on

page 39

How to recover from corrupted service processor rmware.

“Recover the SP Firmware Using the Preboot Menu (Service Only)” on page 41

How to review the power-on self test (POST) checkpoint code sequence.

“BIOS Power-On Self-Test (POST) Checkpoints ” on page 135

TroubleshootingandDiagnostic Information

▼

Gather Service Information

The rst step in determining the cause of a problem with the server is to gather information for the service call paperwork or the onsite personnel.

Follow these general guidelines when you begin troubleshooting.

Collect information about the following items:

■

Events that occurred prior to the failure

■

Whether any hardware or software was modied or installed

■

Whether the server was recently installed or moved

■

How long the server exhibited symptoms

■

The duration or frequency of the problem

Document the server settings beforeyou make anychanges.

If possible, make one change at a time in order to isolate potential problems. In this way, you can maintain a controlled environment and reduce the scope of troubleshooting.

Note the results of any change that you make. Include any errors or informational messages.

Check for potential device conicts before you add a new device.

Check for versiondependencies, especially with third-party software.

■

“Service Troubleshooting Task List” on page 30

■

“Troubleshooting and Diagnostic Information” on page 37

Locate the Server Module Serial Number

The server system serial number (SysSN) is a unique alpha-numeric label that identies your server to Oracle systems, such as My Oracle Support (MOS). The SysSN is encoded in the server. You might need it when contacting Oracle. You can nd the SysSN in the following locations:

■

Oracle System Assistant System Information (Home) screen

■

Oracle ILOM Summary screen

■

Server module front panel as shown in the following gure:

See Also

Locate the Server Module Serial Number

Sun Blade X4-2B ServiceManual • March, 201438

Related Information:

■

“About Front and Rear Panels” on page 12

■

“Powering Down the Server Module” on page 47

■

http://www.oracle.com/goto/x86AdminDiag/docs

■

http://www.oracle.com/goto/ILOM/docs

▼

Troubleshoot Server Module Power Problems

If the server module does not power on to either a full power or standby power state, the issue might be related to Sun Blade 6000 Chassis power limitations. Power limitations are managed by the CMM Oracle Integrated Lights Out Management (ILOM). Every time a server module attempts to power on, it queries the CMM Oracle ILOM to ensure that sucient power is available from the chassis power supply units (PSUs). If the PSUs cannot supply enough power, the CMM Oracle ILOM prevents the server module from receiving power (standby and full), and the server module front panel OK/Power indicator blinks and does not display solid.

The chassis power supplies can only supply enough power for certain congurations of server modules and storage modules. Review the power supply and the slot congurations (the

Locate the Server Module Serial Number

number of server modules and storage modules) of your chassis, and refer to the Sun Blade

X4-2B Product Notes

document for the server module and the Sun Blade 6000 Chassis for

conguration information.

Use this procedure to troubleshoot server module power on issues If the server module fails to power on to a standby or full power state:

Review the system event log (SEL) messages.

Conrm that theserver has permission to poweron.

If the chassis cannot supply adequate power to the server module, A message is generated in the SEL.

For more information about SEL messages and power management, refer to the

http://www.oracle.com/goto/x86AdminDiag/docs.

Ensure that the system chassis has the propernumber of powersupplies to support powering on all the chassis componentscurrently installed.

For more information about the Oracle ILOM system event log or monitoring power consumption, refer to the

Oracle Integrated Lights Out Manager (ILOM) 3.1 Documentation

Collection (http://www.oracle.com/pls/topic/lookup?ctx=ilom31).

Locate the Server Module Serial Number

Sun Blade X4-2B ServiceManual • March, 201440

Verify that the Oracle ILOM CMM powermanagement settings forPSUs is conguredto default settings, to avoidpower loss.

■

“Service Troubleshooting Task List” on page 30

■

“Troubleshooting and Diagnostic Information” on page 37

About the DIMM and Processor Test Circuit

You can identify failed DIMM and processor components by removing the server module from the chassis and pressing the internal Fault Remind test circuit button. The Fault Remind test circuit lights the failed component's Fault LED indicator.

Use the test circuit wthin 30–60 minutes. After you remove the server from the chassis (and its power source) and press the internal Fault Remind test circuit button, you have 30–60 minutes before the charge dissipates completely and disables the test circuit.

To determine if the circuit is usable, press the Fault Remind button and verify that the green Charge Status indicator is lit.

■

If the Charge Status indicator lights, the circuit is usable and you can look for an amber Fault indicator to identify the failed component.

■

If the Charge Status indicator does not light, the circuit has no charge; the error information is lost, and you need to install the server module into the chassis and power on to recharge the circuit and allow the error to occur again.

For more information about how to use the DIMM and processor test circuit to identify faulty DIMMs or processors, see:

■

“Identify Faulty DIMMs” on page 77

■

“Identify a Faulty Processor” on page 100

▼

Recover the SP Firmware Using the Preboot Menu (Service Only)

Note – This procedure must be performed by an Oracle Service representative.

The preboot menu allows you to recover the Oracle ILOM rmware image by updating (ashing) the SP rmware.

■

Set up to view server boot messages.

■

Obtain the .flash rmware image for the server.

See Also

BeforeYou Begin

About the DIMM and Processor TestCircuit

■

Refer to the http://www.oracle.com/goto/x86AdminDiag/docs for detailed preboot menu and Oracle ILOM information.

Make the .flash rmware image le for the server available on a TFTP server.

This .flash le is available on the Oracle My Oracle Support (MOS) download site.

Note – Recovering the SP rmware using the preboot menu requires a .flash le instead of the

.pkg le that is used to update the SP from Oracle ILOM.

Restart the SP.

Interrupt the SP boot processto access the preboot utility menu.

Choose one of the following methods:

■

Press the Locate button during the SP boot process. For more information, see “Turn the

Locate Indicator On and O Locally” on page 61.

■

Wait for a pause in the bootstrap process.

The preboot prompt appears.

Preboot>

At the prebootprompt, type:

net flash IPaddress path/name.flash

where IPaddress is the IP address of a TFTP server,

path is the path to the le relative to /tftpboot, and

name is the rst part of the .flash le name.

For example:

Preboot>

net flash 10.8.173.25 images/system-rom.flash

After a series of messages, the ash process nishes, and the preboot prompt appears.

Preboot>

To restartthe SP, type:

Preboot> reset

The preboot menu exits and Oracle ILOM boots.

■

Oracle Integrated Lights Out Manager (ILOM) 3.1 Documentation Collection (http://www.oracle.com/pls/topic/lookup?ctx=ilom31)

See Also

About the DIMM and Processor TestCircuit

Sun Blade X4-2B ServiceManual • March, 201442

Preparing for Service

These sections describe how to safely prepare the Sun Blade X4-2B for service and component removal and replacement:

Description Link

Before working with components within the server, power down the server module and prepare for servicing.

“Preparing the Server Module for Component Replacement” on page 43

Understand options for powering o and resetting the server.

“Powering Down the Server Module” on page 47

Guard against electrostatic discharge (ESD). “Performing ESD and Anti-static Prevention

Measures” on page 53

Remove the server module from the chassis. “Remove the Server Module from the Sun Blade

Chassis” on page 55

Note server module ller panels. “Install Server Module Filler Panels” on page 57

Remove the server cover to access internal components and test circuitry.

“Remove the Server Module Top Cover” on page 58

Understand the FRU top-level indicator auto-update feature.

“FRU TLI Auto-Update” on page 61

Assemble the required tools. “Required Tools” on page 61

▼

Preparing the Server Module for Component Replacement

This procedure describes how to prepare the server module for service, so you can:

■

Remove or replace the server module

■

Remove or install server module internal components

■

Add new server module components

■

Use the motherboard DIMM and processor Fault Remind circuitry

■

Important: Before performing removal and installation procedures, review the Sun Blade

X4-2B Product Notes

■

If necessary, back up BIOS and SP/ILOM congurations. For conguration back up options, refer to

http://www.oracle.com/goto/x86AdminDiag/docs

■

For troubleshooting information, see “Troubleshooting the Server Module” on page 29.

■

You need a server module ller panel or a replacement server module or storage module. For more information, see

“Install Server Module Filler Panels” on page 57.

Note – This procedure shows both Oracle ILOM web and CLI interface methods. The procedure

can be performed using only Oracle ILOM CLI interface. For more information about Oracle ILOM, refer to the Oracle ILOM documentation at

http://www.oracle.com/goto/ILOM/docs.

To prepare the server for service:

BeforeYou Begin

Preparing for Service

Sun Blade X4-2B ServiceManual • March, 201444

Powerdown the server module tostandby power.

See

“Powering Down the Server Module” on page 47 for detailed instructions.

a. Access Oracle ILOMweb interface.

Type the IP address into a web browser and log in as a user with root or administrator privileges. For CLI log-in instructions, see

Oracle Integrated Lights Out Manager (ILOM)

3.1 Documentation Collection (http://www.oracle.com/pls/topic/ lookup?ctx=ilom31)

b. In the Actions section of the Summaryscreen, click the PowerStateTurnO button.

This action powers o the server to standby power mode.

(Optional) In the Actions sectionof the Summary screen, click the Locate IndicatorTurn On button

This action activates the Locate indicator on the server front panel.

See

“Turning the Locate Indicator On and O” on page 59.

The following sample screen shows the Actions section of the Summary screen with the server power o and the Locate indicator turned on.

Preparing for Service

Take the server module oine.

Note – Taking the server module oine prevents any low level tasks (such as an SP update) from

being initiated on the server module while it is waiting to be accessed and serviced. An interruption of such a task could render the server unusable.

a. Access the server module SP Oracle ILOM CLI prompt.

Open a terminal window.

Type: ssh root@ipaddress

where ipaddress is the IP address of the server module SP.

Type the password.

b. Removethe server from operation by typing the followingcommand:

-> set /System/ action=prepare_to_remove

This command takes the server oine and activates the blue Ready to Remove indicator on the server module front panel.

c. Verify the state of the server by typing the following command:

-> show /System/ health

In the command output, view the health property. The value should appear as Oine. For example:

/System

Properties:

health = Offline

The server module can be accessed locally and removed from the chassis.

Set up an ESD-safe service location.

Before removing the server module from the chassis, prepare the service location. See

“Set Up

for ESD Prevention” on page 54

Remove the server module from the chassis.

See

“Remove the Server Module from the Sun Blade Chassis” on page 55.

Insert a server module ller panel into the thevacant server moduleslot immediately.

See

“Install Server Module Filler Panels” on page 57.

Preparing for Service

Sun Blade X4-2B ServiceManual • March, 201446

Remove the server module cover.

See

“Remove the Server Module Top Cover” on page 58.

■

“Servicing Server Module Components ” on page 63

■

“Returning the Server Module to Operation ” on page 127

Powering Down the Server Module

Determine how you want to power down the server by reviewing the options in the following table.

Description Link

Power down the server gracefully to prevent data from being corrupted. Performing a graceful shutdown ensures that the system is ready for restart.

■

“Power O, Graceful (Power Button)” on page 50

■

“Power O, Remote (Oracle ILOM CLI)” on page 51

■

“Power O, Remote (Oracle ILOM Web Interface)” on page 52

If the server is not responding, or you must shut down the server quickly, perform an immediate shutdown.

■

“Power O, Immediate (Power Button)” on page 50

■

“Remove Power Completely” on page 52

See Also:

■

“About Server Power States and Resets” on page 47

■

“Powering On the Server Module” on page 131

About Server Power States and Resets

This section contains information about power modes, server shutdown and reset options, and power o and reset procedures.

Note – Powering o the server module involves shutting down the server from full power mode

to standby power. Powering the server module from full power mode to standby power does not completely remove power from the server. If you need to completely remove power from the server module, you must disengage it from the power connections on the chassis mid plane by partially removing it.

Determine how you will shut down power from the following methods:

Next Steps

About Server Power States and Resets

Tip – Whenever possible, shut down the server gracefully using the server OS shutdown

procedure.

You can power o the server module locally or remotely.

■

To power o locally, use the front panel power button.

■

To power o remotely, use the server OS shutdown procedure or Oracle ILOM.

You can perform either a graceful or an immediate shutdown of the server.

■

If possible, shut down the server gracefully using the server OS shutdown procedure or Oracle ILOM.

■

An immediate shutdown should be used in emergency situations or when you know that the loss of data is nonexistent or minimal.

Power descriptions follow.

Full Power

Full power is the normal operational state for the server. When the server enters full power, power is supplied to all the server components, the server boots, and the operating system (OS) functions. You achieve full power by pressing the Power button on the server front panel when the server is in standby power. You can also achieve full power by powering on the server from Oracle ILOM. Once the server is operating in full power, the Power OK indicator is on continuously (does not blink).

Standby Power

Standby power is a non-operating state (OS does not boot), in which low-level power is supplied only to the components that are required to run the service processor (SP) and Oracle ILOM. To enter standby power, install the server into a fully-powered chassis, but do not press the front panel Power button. You can also enter standby power by powering o the server (from full power) using one of the power-o methods described in,

“Powering Down the Server

Module” on page 47

. When entering standby power mode, the server front panel Power indicator blinks quickly while the SP is booting. When the SP has booted, the indicator blinks slowly to show that the server is in standby power mode.

Graceful Shutdown

A graceful shutdown (also referred to as an orderly shutdown) is the safest method of shutting down the server to standby power mode because it warns users, closes les, and prepares the le system. To perform a graceful shutdown, use the server OS shutdown procedure or the Oracle ILOM graceful power o option.

About Server Power States and Resets

Sun Blade X4-2B ServiceManual • March, 201448

Immediate Shutdown

An immediate shutdown of the server (also referred to as an emergency shutdown) should be used only in situations when you know that the loss of data is nonexistent or acceptable. An immediate shutdown does not warn users, does not close les, nor does it prepare the le system for shut down to standby power mode.

Complete Power Removal

Shutting down the server from full power mode to standby power mode does not completely remove power from the server. When it is in standby power mode, the server is in a low-power state. This low-power state is enough to maintain the service processor (SP), which runs Oracle ILOM. To completely remove power from the server module, you must disengage its internal connector from the chassis mid-plane by performing a full or partial removal. To perform a cold reset (see following section) of the server, completely remove power, wait 30-60 seconds, and install the server back into the chassis.

Warm Reset or Reboot

A warm reset of the server is a reboot or restart of the server. It involves cycling the server power from full power mode to standby power mode and back to full power mode. For example, a warm reset might be required after a software or rmware update or when you want to launch Oracle System Assistant or access the BIOS Setup Utility.

Cold Reset

A cold reset of the server is a restart of the server from a completely powered-o state. A cold reset might be required to resolve a system issue. To perform a cold reset, place the server module in standby power mode, disconnect the server from its power source by performing a complete power removal (see above), wait 30-60 seconds, and then connect the server to its power source.

See Also:

■

“Power O, Graceful (Power Button)” on page 50

■

“Power O, Immediate (Power Button)” on page 50

■

“Power O, Remote (Oracle ILOM CLI)” on page 51

■

“Power O, Remote (Oracle ILOM Web Interface)” on page 52

■

“Remove Power Completely” on page 52

■

“Powering Down the Server Module” on page 47

■

“Powering On the Server Module” on page 131

About Server Power States and Resets

▼

Power O, Graceful (Power Button)

Note – This procedure is performed locally requiring access to the server module front panel.

Shutting down the server by pressing the front panel Power button causes operating systems with Advanced Conguration and Power Interface (ACPI) to perform an orderly shutdown of the OS. Non-ACPI enabled operating systems might ignore this event and not shut down the host. If your OS ignores this event, shut down the server using the server OS or Oracle ILOM (remotely or locally).

To power o the server gracefully,use a stylus to gently press and immediately release the front panel Power button when it clicks.

Caution – Potential for loss of data. Do not press in and hold the power button for longer than

ve seconds. Doing so causes an immediate server shutdown.

Verify that the full power is o.

The OK indicator on the front panel blinks, indicating that the server module is in standby power mode.

■

“About Server Power States and Resets” on page 47

■

“Remove the Server Module from the Sun Blade Chassis” on page 55

▼

Power O, Immediate (Power Button)

Note – This procedure is performed locally requiring access to the server module front panel.

An immediate shutdown should be used in emergency situations or when you know that the loss of data is nonexistent or acceptable.

Caution – Data loss. All applications and les close abruptly without saving. Before powering o,

warn users and close all applications.

■

Physical access to the server front panel is required.

■

“Front Panel Indicators and Buttons” on page 13

Use this procedure to immediately power o the server.

Next Steps

BeforeYou Begin

About Server Power States and Resets

Sun Blade X4-2B ServiceManual • March, 201450

Use a stylus to pressand hold the Power button for at least veseconds until the full power is o and the server module enters standby power mode.

Verify that the full power is o, and that the OK indicator on the front panel blinks, indicating that the server module is in standby power mode.

■

“About Server Power States and Resets” on page 47

■

“Remove the Server Module from the Sun Blade Chassis” on page 55

▼

Power O, Remote (Oracle ILOM CLI)

You can use the Oracle ILOM SP command-line interface (CLI) to remotely power o the server module.

Open an SSH session.

At the command line, log in to Oracle ILOMon the server module SP.

For example:

ssh root@ipadress

where ipadress is the IP address of the server module SP.

For more information, see

http://www.oracle.com/goto/x86AdminDiag/docs.

The Oracle ILOM CLI prompt appears:

At the prompt,type one of the followingcommands:

■

For graceful power o:

stop /System

■

For immediate power o:

An immediate shutdown should be used in emergency situations or when you know that the loss of data is nonexistent or acceptable.

stop -force /System

■

“About Server Power States and Resets” on page 47

■

“Turn On the Locate Indicator Remotely (Oracle ILOM Web Interface)” on page 60

■

“Turn On the Locate Indicator Remotely (Oracle ILOM CLI)” on page 59

Next Steps

About Server Power States and Resets

■

Oracle Integrated Lights Out Manager (ILOM) 3.1 Documentation Collection (http://www.oracle.com/pls/topic/lookup?ctx=ilom31)

▼

Power O, Remote (Oracle ILOMWeb Interface)

To log in, open a web browser and direct it using the IP address of the server module SP. Log in as root or a user with administrator privileges. For more information, refer to the server Administration Guide:

www.oracle.com/goto/x86AdminDiag/docs .

The Summary screen appears.

In the Actions section of the Summary screen, verifythat the powerstate is ON.

To performa graceful powero of the server, click the Turn O button.

Alternatively, other power o options are available in the Host Management > Power Control screen.

Note – An immediate shutdown option should only be used in emergency situations or when

you know that the loss of data is nonexistent or acceptable.

Click OK.

■

“About Server Power States and Resets” on page 47

■

“Turn On the Locate Indicator Remotely (Oracle ILOM Web Interface)” on page 60

■

“Turn On the Locate Indicator Remotely (Oracle ILOM CLI)” on page 59

▼

Remove Power Completely

Note – For the server module removal procedure, see “Remove the Server Module from the Sun

Blade Chassis” on page 55.

Powering the server module from full power mode to standby power mode does not completely remove power from the server. If you need to completely remove power from the server module to perform a cold reset or to place it in an non-powered state, disengage the server module from the power connections on the chassis mid-plane by partially removing it.

■

This procedure is performed locally requiring physical access to the server.

Next Steps

BeforeYou Begin

About Server Power States and Resets

Sun Blade X4-2B ServiceManual • March, 201452

Place the server module in standby power mode.

See

“Powering Down the Server Module” on page 47.

To unlock the server moduleejector arms, squeeze together the green tabs on the ends of ejector arms.

To disengage the server modulefrom the chassis internal connector, rotate both ejector arms away from the server module at the sametime until they are fully extended.

This action disengages the server module, places it in a no-power state, and leaves it protruding from the front of the chassis approximately three inches.

If you areperforming a cold reset wait at least 60 seconds beforereengaging the servermodule and chassis backplane connectors.

■

“About Server Power States and Resets” on page 47

■

“Remove the Server Module from the Sun Blade Chassis” on page 55

Performing ESD and Anti-static Prevention Measures

Server components, such as processors, circuit boards, drives, and DIMMs, are extremely sensitive to electrostatic discharge (ESD). Ordinary amounts of ESD transferred from your clothing or your work environment to components while servicing can destroy them and possibly render the server inoperable. To reduce ESD, perform the prevention measures described in this section before you service the server.

Use an Anti-static Wrist Strap and an Anti-static Mat

Always wear an anti-static wrist strap and use an anti-static mat when servicing or handling ESD-sensitive server components, such as storage drive assemblies, circuit boards (including DIMMs), and PCIe cards.

Note – Anti-static wrist straps are included with optional components.

To use the wrist strap, place the anti-static strap on your wrist and attach the clip end to a bare metal area on the chassis, server module, or blade. When properly worn, the anti-static strap equalizes the electrical potentials between you and the server.

Anti-static mats provide an ESD-free surface in which to work and set components. Some mats are grounded in the same manner as a wrist strap; that is, you attach one end of the grounding strap to the connector on the mat and attach the clip end of the strap to bare metal. If a grounding mat is not available, you can use the anti-static mylar bag in which the component was shipped.

See Also

Performing ESD and Anti-static Prevention Measures

Additionally, always handle components that have exposed connectors by the non-connector edges (do not touch the connectors) and set the components on an anti-static mat or anti-static packaging.

See Also:

■

“Set Up for ESD Prevention” on page 54

▼

Set Up for ESD Prevention

■

See “Performing ESD and Anti-static Prevention Measures” on page 53

Prepare an anti-static surface to set parts on during the removal, installation, or replacement process.

Place ESD-sensitive components such as the printed circuit boards on an anti-static mat. The following items can be used as an anti-static mat:

■

Anti-static bag used to wrap an Oracle replacement part

■

An ESD mat

■

A disposable ESD mat (shipped with some replacement parts or optional system components)

BeforeYou Begin

Performing ESD and Anti-static Prevention Measures

Sun Blade X4-2B ServiceManual • March, 201454

Attach an anti-static wrist strap.

When servicing or removing server module components, attach an anti-static strap to your wrist and then to a bare metal area on the chassis, server module, or blade.

■

“Remove the Server Module from the Sun Blade Chassis” on page 55.

▼

Remove the Server Module from the Sun Blade Chassis

To service internal server components and to troubleshoot processors and DIMMs using the motherboard Fault Remind circuitry, you need to remove the server module from the chassis. Removing the server module leaves a vacant slot in the chassis, which disrupts the chassis cooling and airow system. The system requires that every chassis slot contain a component, either a server module, a storage module, or a server module ller panel.

■

See “Preparing for Service ” on page 43.

■

You need a replacement server module, a storage module, or a server module ller panel, to ll the vacant slot created when you remove the server module. For more information, see

“Install Server Module Filler Panels” on page 57.

To unlock the server modulelever handles, squeezethe green tabs on theends of handles.

To disengage the server modulefrom the internal connector,simultaneously rotate both lever handles outward awayfrom the server module until fully extended.

The result of this action disengages the server module, places it in a no-power state, and leaves it protruding approximately three inches from the front of the chassis.

Caution – Component damage or personal injury. Blades can weigh up to 22 lbs (10kg). Use two

hands to install or remove the blade from the chassis. Do not attempt to remove the server module from the chassis using the ejector levers.

Next Steps

BeforeYou Begin

Performing ESD and Anti-static Prevention Measures

Pull the server module away fromthe Sun Blade chassis (approximately 5–6 inches) using the lever handles.

Close the lever handles.

Rotate the handles inward toward the server module front panel until they lock (click) into place.

To remove the server module,use both hands to pull the server module out of the chassis.

Set the server module on prepared work space.

See

“Set Up for ESD Prevention” on page 54.

To insert a servermodule ller panel or replacement server module in the vacantslot, do one of the following:

■

If replacing the server module with a ller panel, see“Install ServerModule Filler Panels”on

page 57.

■

If replacing the server module with a replacement server module or a storage module, see

“Install the Server Module in the Chassis”on page 130.

“Remove the Server Module Top Cover” on page 58

Server Module and Component Filler Panels

Filler panels are required for server module and storage drive vacant slots. A ller panel occupies a vacant slot to maintain proper cooling and air ow throughout the system. A ller panel is a metal or plastic enclosure that does not contain any functioning system hardware or cables.

Next Steps

Server Module and Component FillerPanels

Sun Blade X4-2B ServiceManual • March, 201456

Do not operate your system with empty slots for more than 60 seconds. Improper cooling and airow can compromise the operating performance of your system and quickly damage components.

For server module and storage drive ller panel installing and removing tasks, see:

■

“Install Server Module Filler Panels” on page 57

■

“Remove Storage Drive Filler Panels” on page 73

■

“Insert Storage Drive Filler Panels” on page 73

Note – For instructions for adding or replacing chassis component ller panels (for example,

network modules or PCI Express modules), refer to the documentation supplied with your chassis.

▼

Install Server Module Filler Panels

Install a server module ller panel after removing a server module from the chassis. The ller panel maintains cooling and prevents chassis shutdown. For more information about ller panels, see

“Server Module and Component Filler Panels” on page 56.

Caution – Chassis shutdown due to over-temperature. Vacant slots disrupt the chassis cooling.

Fill vacant slots within 60 seconds of removing a server module, storage module, of ller panel.

Locate the vacantserver module slot in the chassis.

Ensure that the ller panel release lever is in the fully open position.

Align the ller panel with the vacant slot in the chassis, ensuring that the releaselever is on the right.

Server Module and Component FillerPanels

Slide the ller panel into the vacant slot until it stops.

Close the release lever until it locks (clicks) the ller panel in place.

■

“Remove the Server Module Top Cover” on page 58

▼

Remove the Server Module Top Cover

You need to remove the server module cover to access the mother board Fault Remind circuitry and service components inside the server.

Powero the server module.

See

“Powering Down the Server Module” on page 47.

Remove the server module from the chassis.

See

“Remove the Server Module from the Sun Blade Chassis” on page 55.

Attach an anti-static wrist strap.

See

“Set Up for ESD Prevention” on page 54.

Press down on the server module cover release button and, using the indent for leverage,slide the top covertowardthe rear of the server module chassis approximately0.5 inch (12 mm).

Next Steps

Server Module and Component FillerPanels

Sun Blade X4-2B ServiceManual • March, 201458

Lift the cover straight up from the server module.

■

“Servicing Server Module Components ” on page 63

Turning the Locate Indicator On and O

This section provides procedures for turning the Locate indicator on and o remotely (using Oracle ILOM) and locally (using the front panel Locate button), so you can identify the server module within the chassis.

■

“Turn On the Locate Indicator Remotely (Oracle ILOM CLI)” on page 59

■

“Turn On the Locate Indicator Remotely (Oracle ILOM Web Interface)” on page 60

■

“Turn the Locate Indicator On and O Locally” on page 61

▼

Turn On the Locate Indicator Remotely (Oracle ILOM CLI)

Before going to the server, activate the server's Locate indicator. This allows you to identify the correct server module within the chassis.

See “Access Oracle ILOM Using CLI” in X4 Series Administration Guide.

The CLI prompt appears:

–>

Next Steps

Turningthe LocateIndicator On and O

To turn on the Locate indicator, type thefollowing command at the prompt:

set /System/ locator_indicator=on

Note – To turn o the Locate indicator, type: set /System/ locator_indicator=off

To verify the status of the Locate indicator, type:

–> show /System/ locator_indicator

The output of the command appears:

/System

Properties:

locator_indicator = Off

The value locator_indicator shows the status as either On or Off.

■

“Set Up for ESD Prevention” on page 54

■

“Remove the Server Module from the Sun Blade Chassis” on page 55

▼

Turn On the Locate Indicator Remotely (Oracle ILOM Web Interface)

Before going to the server, activate the server's Locate indicator. This allows you to identify the correct server module within the chassis.

See “Access Oracle ILOM Using a Web Browser” in X4 Series Administration Guide.

The Oracle ILOM screen appears.

Select the server module.

The Oracle ILOM Summary screen appears.

In the Actions section, verify that the Locateindicator is o, and then click the Turn On button.

Click OK.

The Locater indicator on the Summary screen changes to indicate the status of the Locate indicator.

■

“Set Up for ESD Prevention” on page 54

■

“Remove the Server Module from the Sun Blade Chassis” on page 55

Next Steps

Turningthe LocateIndicator On and O

Sun Blade X4-2B ServiceManual • March, 201460

▼

Turn the Locate Indicator On and O Locally

Once you have identied the server module by its blinking Locate indicator, use this procedure to turn o the indicator.

■

You must be physically present at the server.

■

For button and indicator location information, see “Front Panel Indicators and Buttons” on

page 13

To turn the Locate indicator on or o locally, do one of the following:

■

To turn o the blinking indicator,press the Locateindicator button.

■

To turn on the Locateindicator, press the Locate indicator button.

Note – Some procedures might require that you turn on the Locate indicator locally, as part

of a verication step.

■

To performan lamp test of allfront panel indicators,press and hold the Locate indicator until all the front panelindicators light up.

The indicators remain lit for 15-20 seconds.

■

“Set Up for ESD Prevention” on page 54

■

“Remove the Server Module from the Sun Blade Chassis” on page 55

RequiredTools

The server can be serviced with the following tools:

■

Anti-static wrist strap

■

Anti-static mat

■

No. 2 Phillips screwdriver

FRU TLI Auto-Update

Oracle ILOM includes a top-level indicator (TLI) auto-update feature that ensures that the TLI stored in the server's eld-replaceable units (FRUs) is always correct. The TLI, which is unique to each server, is used to track the server's service entitlement and warranty coverage. When a server requires service, the server's TLI is used to verify that the server's warranty has not expired.

The TLI is stored in the FRUID (eld-replaceable unit identiers) of these components: motherboard (MB).

BeforeYou Begin

●

Next Steps

FRU TLI Auto-Update

The TLI components stored in each component FRUID include:

■

Product name

■

PPN (product part number)

■

PSN (product serial number)

When a server FRU that contains the TLI is removed and a replacement module is installed, the TLI of the replacement module is programmed by Oracle ILOM to contain the same TLI as the other module.

FRU TLI Auto-Update

Sun Blade X4-2B ServiceManual • March, 201462

Servicing Server Module Components

This section contains procedures and information about how to remove and install Sun Blade X4-2B components.

Description Link

Review replaceable components and component serviceability. “About the Chassis” on page 21

Remove and install a storage drive. “Servicing a Storage Drive (CRU)” on page 63

Remove and install DIMMs. “Servicing DIMMs (CRU)” on page 74

Remove and install USB sticks. “Servicing USB Flash Sticks (CRU)” on page 84

Remove and install a FEM. “Servicing a Fabric Expansion Module (CRU)” on page 87

Remove and install a REM. “Servicing a RAID Expansion Module (CRU)” on page 89

Remove and install a processor and heat sink assembly. “Servicing Processors (FRU)” on page 94

Replace the server motherboard. “Servicing the Motherboard Assembly (FRU)” on page 117

Replace the server system battery. “Servicing the System Battery (CRU)” on page 125

Servicing a Storage Drive (CRU)

The Sun Blade X4-2B server module can contain up to four storage drives, which are hot-swappable components. The storage drives are located on the front panel of the server module.

Note – A hot-swap component can be safely removed while the server module is running.

However, before removing system drives, you might need to rst prepare the server module operating system.

To remove and install a hard drive (HDD) or a solid state drive (SSD), use the following procedures:

■

“Identifying Storage Drives” on page 64

■

“Identifying Storage Drive Indicators and Mechanical Components” on page 66

■

“Storage Drive Failure and RAID ” on page 69

■

“Replace a Storage Drive” on page 72

■

“Remove a Storage Drive” on page 70

■

“Install a New Storage Drive” on page 71

■

“About Disk Backplane Cabling” on page 69

■

“Remove Storage Drive Filler Panels” on page 73

■

“Insert Storage Drive Filler Panels” on page 73

Identifying Storage Drives

The system software designation for storage drive devices (hard disk drives [HDD] or solid state drives [SSD]) is shown in the following gure.

Identifying Storage Drives

Sun Blade X4-2B ServiceManual • March, 201464

Figure Legend

0 Hard disk drive (HDD 0) 2 Hard disk drive (HDD 2)

1 Hard disk drive (HDD 1) 3 Hard disk drive (HDD 3)

Related Information:

■

“Identifying Storage Drive Indicators and Mechanical Components” on page 66

Identifying Storage Drives

Identifying Storage Drive Indicators and Mechanical Components

The topics included in this section show the location of the storage drive indicators and mechanical components and describe their functions.

Legend Name

1 Ready to Remove indicator

2 Service Action Required indicator

3 Power/OK indicator

4 Lever Release button

5 Lever

The following topics describe storage drive indicator and mechanical component functions.

Ready to Remove Indicator

This topic describes the Ready to Remove indicator.

Identifying Storage Drive Indicators and Mechanical Components

Sun Blade X4-2B ServiceManual • March, 201466

Function:

■

Blue LED with the following states:

■

On solid: The storage drive is in standby power state. The storage drive can be removed safely during a hot-plug operation. A lit Ready to Remove indicator indicates that service action is allowed on the storage drive.

■

O: Normal operation. Do not remove the drive.

Service Action Required Indicator

This topic describes the Service Action Required indicator.

Function:

■

An amber LED with the following states:

■

On solid: The system has detected a fault with the storage drive.

■

O: Normal operation.

Power/OKIndicator

This topic describes the Power/OK indicator.

Function:

Identifying Storage Drive Indicators and Mechanical Components

■

Green LED that identies the following power state of the storage drive:

■

O: Power is o, idle (SATA only), or installed drive is not recognized by the system.

SATA HDD (SSD) only: Green LED is o when the storage drive is idle.

■

Blink, variable: Drive activity.

■

On solid (does not blink): Drive is engaged and is receiving full power.

SAS HDD only: Green LED is on when the storage drive is idle.

Note – LED activity changes for drive type:

■

SAS HDD storage drive: Green LED is on when the storage drive is idle.

■

SATA HDD (SSD) storage drive: Green LED is o when the storage drive is idle.

Lever and Lever Release Button

This topic describes the operation and purpose of the storage drive lever and the lever release button.

Function:

■

Press the lever release button to unlock the lever.

■

When the button is pressed, the spring-loaded lever unlocks and pops open.

■

Lever functions:

■

Drive removal: Use the lever to pull the drive out of the server. For more information, see

“Remove a Storage Drive” on page 70.

■

Drive installation: Use the lever to engage the drive with the internal connector. For more information, see

“Install a New Storage Drive” on page 71.

Identifying Storage Drive Indicators and Mechanical Components

Sun Blade X4-2B ServiceManual • March, 201468

Related Information:

■

“Identifying Storage Drives” on page 64

Storage Drive Failure and RAID

A single storage device failure does not cause data loss if the storage devices are congured as a mirrored RAID volume. Failed storage devices, such as HDDs, can be removed, and when a new storage device is inserted, the contents are automatically rebuilt from the rest of the array with no need to recongure the RAID parameters. If the replaced storage drive was congured as a hot-spare, the new HDD is automatically congured as a new hot-spare.

Before you permanently remove a storage device from the server that is part of an active RAID volume, you should delete the active RAID volume from the storage device. For information about how to delete a RAID volume, use the appropriate RAID management utility for the RAID controller installed.

Caution – Data loss. If you insert a storage device that has been congured with a RAID volume

into a server that did not previously have its storage devices congured with RAID volumes, the existing storage devices in the server will be converted to RAID volumes during automatic synchronization, and any existing data on the existing storage devices in the server is erased.

Related Information:

■

“Conguring RAID” in the server Administration Guide http://www.oracle.com/goto/

x86AdminDiag/docs

About Disk Backplane Cabling

The server has two internal disk backplanes, one on the right side and one on the left side. The right side backplane supports drives HDD 0 and HDD 1. The left side backplane supports drives HDD 2 and HDD 3. Each backplane has three connectors, one 10-pin power connector and two color-coded data connectors (one for each drive). Power and data cables connect the backplane to connectors on the motherboard. The connectors on the motherboard are labeled DBP Power (for power) and REM 0 - REM 3 (for data).

Cabling for the two disk backplanes:

■

Disk backplane for HDD 0 and HDD 1:

■

Backplane power: the cable connects to the nearby DBP Power connector on the MB.

■

Blue connector on the backplane (HDD 0): cable connects to the REM 0 connector on the MB.

About Disk Backplane Cabling

■

Black connector on the backplane (HDD 1): cable connects to the REM 1 connector on the MB.

■

Disk backplane for HDD 2 and HDD 3:

■

Backplane power: the cable connects to the nearby DBP Power connector on the MB.

■

Blue connector on the backplane (HDD 2): cable connects to the REM 2 connector on the MB.

■

Black connector on the backplane (HDD 3): cable connects to REM 3 on the MB.

▼

Remove a Storage Drive

If necessary, prepare the server module operating system, beforeyou remove drives.

Refer to the OS documentation.

Locate the storage drive in the server module bays.

For drive locations on the server module, see

“Identifying Storage Drives” on page 64.

Identify the faulty drive.

Faulty storage drives are identied by lit blue (Ready to Remove) and amber LED status indicators.

For more information, see

“Identifying Storage Drive Indicators and Mechanical Components”

on page 66

Press the releaselever button on the drive front panel androtate the leverinto its fully opened position.

Hold the opened release leverand gently slide the drivetowardyou.

If you arenot immediately replacing the drive, insert a ller panel into the empty drive slot on the server.

Caution – Over-temperature condition. Do not operate the server with empty storage device

slots. Always insert a ller panel into an empty storage device slot. See

“Insert Storage Drive

Filler Panels” on page 73

About Disk Backplane Cabling

Sun Blade X4-2B ServiceManual • March, 201470

“Replace a Storage Drive” on page 72

▼

Install a New Storage Drive

Locate the storage drive ller panel in the server module bays.

For drive locations on the server, see

“Identifying Storage Drives” on page 64.

Remove the storagedrive ller panel from the server module bays.

For instructions to remove drive ller panels, see

“Remove Storage Drive Filler Panels” on

page 73.

Ensure that the storage drive releaselever on the drive is in a fully opened position.

Slide the storage drive into the vacant slot by pressing the middle of the storage drivefaceplate with your thumb or nger until the release lever engages with the chassis.

The release lever starts to close as it makes contact with the chassis. Do not slide the storage drive in all the way. Leave the storage drive out approximately 0.25 to 0.50 inch (6 to 12 mm) from the opening.

Close the release lever until the storage driveclicks into place and is ush with the front of the server.

Next Steps

About Disk Backplane Cabling

A pawl near the hinge on the lever engages the sidewall drawing the drive inward and seating the drive connector with the internal hard drive backplane connector.

▼

Replace a Storage Drive

Remove the storagedrive or ller panel from the server module.

■

“Remove Storage Drive FillerPanels”on page 73

■

“Remove a StorageDrive”on page 70

Ensure that the replacement storage driverelease lever isin its fully opened position.

Slide the storage drive into the vacant slot by pressing the middle of the storage drivefaceplate with your thumb or nger until the release lever engages with the chassis.

The release lever will start to close as it makes contact with the chassis. Do not slide the storage drive in all the way. Leave the storage drive out approximately 0.25 to 0.50 inch (6 to 12 mm) from the opening.

Close the release lever until the storage driveclicks into place and is ush with the front of the server.

Note – If the storage devices were previously congured as a mirrored RAID array, an automatic

synchronization is invoked and the contents are rebuilt from the rest of the array with no need to recongure the RAID parameters. If the replaced storage device was congured as a hot-spare, the new HDD is automatically congured as a new hot-spare.

About Disk Backplane Cabling

Sun Blade X4-2B ServiceManual • March, 201472

▼

Remove Storage Drive Filler Panels

Locate the storage drive ller panel to be removedfrom the server.

Unlatch the storagedrive ller panel,and rotate the lever to its fully opened position [1].

Remove the ller panel from the slot byholding the opened release lever and gently sliding the ller panel towardyou [2].

▼

Insert Storage Drive Filler Panels

Locate the vacantstorage drive module slot in the server module.

Ensure that the release lever on the ller panel is fully opened.

Slide a standard storage drive ller panel intothe vacant storage drive slot until the release lever engages with the chassis [1].

The release lever starts to close as it makes contact with the chassis. Do not slide the ller panel in all the way. Leave the ller panel out approximately 0.25 to 0.50 inch (6 to 12 mm) from the opening.

Close the release lever until it clicks into place and is ush with the front of the server [2].

About Disk Backplane Cabling

Servicing DIMMs (CRU)

Note – This component is a customer-replaceable unit (CRU).

This section describes how to diagnose, remove, and replace DDR3 LV DIMM memory modules in the Sun Blade X4-2B.

Use these procedures to service DIMMs:

■

“DIMM Fault Remind Circuit and ECC Errors” on page 74

■

“Identify Faulty DIMMs” on page 77

■

“DIMM Population Rules and Guidelines” on page 78

■

“Remove DIMMs” on page 82

■

“Install DIMMs” on page 83

DIMM Fault Remind Circuit and ECC Errors

The following topics describe the components of the Fault Remind circuitry:

■

“Fault Remind Button and Charge Status Indicator” on page 74

■

“DIMM Fault Indicators” on page 75

FaultRemind Button and Charge Status Indicator

Servicing DIMMs (CRU)

Sun Blade X4-2B ServiceManual • March, 201474

The blue Fault Remind button (SW3001) is located on the motherboard next to the Charge Status indicator (CR3002). The Charge Status indicator indicates the usability of the test circuit. When the Fault Remind button is pressed, the Charge Status indicator, lights green to indicate that there is sucient voltage present in the Fault Remind circuit to activate the fault indicators. DIMM Fault indicators identify DIMMs in a fault state.

Note – Do not press the white Clear CMOS Button (SW1801).

Note – Press the blue Fault Remind button within 15 minutes of removing the server from the

chassis. If the green Charge Status indicator fails to light when you press the Fault Remind button, it is likely that the Fault Remind circuit has lost its charge.

DIMM Fault Indicators

The DIMM Fault indicators are located on the motherboard next to each DIMM slot. The amber indicators light up when the Fault Remind button is pressed and a DIMM fault condition exists.

DIMM Fault Remind Circuit and ECC Errors

Related Information:

■

“About the DIMM and Processor Test Circuit ” on page 41

■

“Identify Faulty DIMMs” on page 77

Inconsistencies Between DIMM Fault LEDs and the BIOS Isolationof Faulty DIMMs

When a single DIMM is marked as faulty by Oracle ILOM (for example, fault.memory.intel.dimm.training-failed is listed in the SP event log), BIOS might disable the entire memory channel that contains the faulty DIMM as failing, that is, up to three DIMMs. As a result, the memory available to the operating system is reduced. However, when the Fault Remind button is pressed, only the fault status indicator (LED) associated with the faulty DIMM lights. The fault LED for the other DIMM in the memory channel remains o. Therefore, you can correctly identify the faulty DIMM.

When the faulty DIMM is replaced and the DIMM fault is cleared using Oracle ILOM, the memory available to the operating system returns to normal. You can use the Oracle ILOM web interface or the command-line interface (CLI) to manually clear faults. For information on how

DIMM Fault Remind Circuit and ECC Errors

Sun Blade X4-2B ServiceManual • March, 201476

to use the Oracle ILOM web interface or the CLI to clear server faults, see the Oracle Integrated Lights Out Manager (ILOM) 3.1 Documentation Library at:

http://www.oracle.com/goto/

ILOM/docs

Error Correction and Parity

The server's processor provides data parity protection on its internal cache memories and error-correction code (ECC) protection. The system can detect the following types of errors: correctable and uncorrectable memory ECC errors and uncorrectable CPU internal errors. Errors are recorded in the Oracle ILOM system event log (SEL).

Advanced ECC corrects up to 4 bits in error on nibble boundaries, as long as they are all in the same DRAM. If a DRAM fails, the DDR3 DIMM continues to function. For instructions for clearing DDR3 DIMM faults, refer to

http://www.oracle.com/goto/x86AdminDiag/docs.

▼

Identify Faulty DIMMs

■

For information about using the DIMM test circuit, see “About the DIMM and Processor

Test Circuit ” on page 41

Prepare the servermodule for service.

See

“Preparing for Service ” on page 43.

Caution – Avoid component damage. Ensure that you follow electrostatic discharge safety

measures and anti static practices. This procedure requires that you handle components that are sensitive to static discharge. This sensitivity can cause components to fail. See

“Performing

ESD and Anti-static Prevention Measures” on page 53

Verify that the charge status indicator is lit green.

A lit green Charge Status indicator, located next to the Fault Remind button, indicates that the Fault Remind indicator circuit is working.

Note – The Charge Status indicator shows the test circuit power level. If the power in the circuit

is depleted, the Charge Status and the Fault Remind indicators do not light. To recharge the circuit, insert the server module into a powered-on chassis.

Press and hold the blue FaultRemind button on the motherboard (SW3001).

Note the location of the faulty DIMMs on the motherboard.

A lit amber indicator next to a DIMM slot indicates a faulty DIMM.

BeforeYou Begin

DIMM Fault Remind Circuit and ECC Errors

Indicator State DIMM Status

O Operating properly.

On (amber) Faulty.

Ensure that all DIMMs are seated correctly in their connector slots.

If re-seating the DIMM does not x the problem, remove and replace the faulty DIMM.

Note – The DIMM Fault indicator remains on when the Fault Remind button is pressed after the

DIMM is re-seated. The server module must be powered up again to verify if re-seating xes the DIMM problem.

“Remove DIMMs” on page 82

■

“DIMM Population Rules and Guidelines” on page 78

■

“About the DIMM and Processor Test Circuit ” on page 41

DIMM Population Rules and Guidelines

Use these DIMM guidelines and illustrations to help you plan the memory conguration of the Sun Blade X4-2B.

Basic Memory Guidelines

When populating DIMM slots, follow these population rules and guidelines.

■

Each processor has four DDR3 memory channels (or buses).

■

Each DDR3 memory channel supports up to three DIMMs for a total of 12 DIMMs per processor.

■

The server module supports one DIMM per channel, two DIMMs per channel, and three DIMMs per channel across all sockets. Minimum per processor: 1, Maximum per processor:

12.

■

The minimum supported memory conguration is one DIMM per processor D0.

■

The maximum supported memory conguration is 768 GB.

■

Use 8 GB DDR3–1600 LV DIMMs, 16 GB DDR3–1600 LV DIMMs only, and 32 GB DDR3-1600 LRDIMM:

■

Install up to four memory channels, with three DIMMs per channel.

■

Install up to 24 DIMMs per server module or up to 12 DIMMs per processor.

■

For optimal performance, install DIMMs in groups of three sockets per channel.

Next Steps

See Also

DIMM Population Rules and Guidelines

Sun Blade X4-2B ServiceManual • March, 201478

■

Always install DIMMs in ascending order, within a color or group following the “farthest from processor rst” convention. See the following table:

DIMM Sockets DIMM Slot Location Socket Color

First D0, D3, D6, D9 Blue

Second D1, D4, D7, D10 White

Third D2, D5, D8, D11 Black

■

The following illustration shows the motherboard, DIMM slot numbering and DIMM slot locations within the Sun Blade X4-2B enclosure.

Detailed Memory Population Rules

■

Rule 1: Always populate the channels as follows. See the following gure.

1. Fill up all the blue sockets.

Always populate the DIMMs furthest from the processor (blue sockets) rst.

DIMM Population Rules and Guidelines

2. Fill up all the white sockets.

3. Fill up the black sockets.

Example Conguration

A processor with four DIMMs. Install four DIMMs in blue sockets D0, D3, D6 and D9.

A processor with eight DIMMs. Install four DIMMs in blue sockets D0, D3, D6 and D9, and four

more DIMMs in the white sockets D1, D4, D7 and D10.

A processor with 12 DIMMs. Install processors in all the sockets as shown in the following gure.

The following gure shows the DIMM slot designations and population order for the Sun Blade X4-2B.

DIMM Population Rules and Guidelines

Sun Blade X4-2B ServiceManual • March, 201480

Tip – This is known as the "ll farthest" approach to DIMM installation.

■

Rule 2: Memory symmetry across processors is required.

Processor 1 memory must match processor 0 memory, in placement, type, size, capacity, frequency and voltage.

■

Rule 3: Each processor can support a single DIMM, two DIMMs, three DIMMs or four DIMMs per color socket set.

■

Rule 4: Within every set of four DIMMs (for example: blue socket set, white socket set, black socket set), mixing/matching of dierent size, memory speed and voltage is not allowed.

■

Memories in D0, D3, D6 and D9 must be all the same.

■

Next, memories in D1, D4, D7 and D10 must be all the same, and so on. While doing this, Rule 2 must be maintained.

■

Rule 5: Mixing and matching of dierent size, voltage and speed across dierent 4 DIMM sets is allowed. For example, memories in D0, D3, D6, D9 (blue sockets) must have the same size. But, they do not have to match memory size/voltage/speed in D1, D4, D7, D10 (white sockets).

Note – When mixing speed across dierent four DIMM sets, all memory is tuned to the

slower speed.

Note – When mixing sizes across dierent 4 DIMM sets, populate the highest density

(largest) DIMMs on the blue socket set, the next size in the white socket set and the smallest DIMMs in the black socket set.

■

Rule 6: The blade must have all LVDIMMs installed. Mixing of dierent DIMM technology is not supported.

■

Rule 7: Each processor can support a maximum of 12 dual-rank (DR) DIMMs.

■

Rule 8: For maximum performance, apply the following rules:

■

DIMMs can run in one of the following three speeds: 1600 MHz, 1333 MHz, or 1067 MHz.

■

DIMM speed rules are: (SR = single rank; DR = dual rank; LR = load reduced)

Note – Quad rank (QR) not supported.

DIMM Population Rules and Guidelines

1. One DIMM per channel or 2 DIMMs per channel = 1600 (or 1333 MHz with E5-2609v2 CPU)

2. Three DIMMs per channel = 1067 MHz.

■

Rule 9: The maximum DIMM speed is limited by the processor part number, with the DIMM population, whichever is lower. Currently, processor memory speed limitation is a function of core count:

■

12-core processors from Intel Xeon processor E5-2600 V2 product family run at a maximum speed of 1600 MHz.

■

10-core processors from Intel Xeon processor E5-2600 V2 product family run at a maximum speed of 1600 MHz

■

8-core processors from Intel Xeon processor E5-2600 V2 product family run at a maximum speed of 1600 MHz.

■

6-core processors from Intel Xeon processor E5-2600 V2 product family run at a maximum speed of 1600 MHz.

■

4-core processors from Intel Xeon processor E5-2600 V2 product family run at a maximum speed of 1333 MHz.

▼

Remove DIMMs

Prepare the servermodule for service.

See

“Preparing for Service ” on page 43.

Identify faulty DIMMs.

See

“Identify Faulty DIMMs” on page 77.

Rotate both DIMM slot ejectortabs outward totheir fully open position.

This action ejects the DIMM from the slot.

Caution – Component damage. Exercise caution when removing DIMMs close to the drive

enclosure and P1. Space near the DIMM slot ejector tabs is limited.

DIMM Population Rules and Guidelines

Sun Blade X4-2B ServiceManual • March, 201482

Carefully lift the DIMM straightup to removeit from the slot.

Place the DIMM on an anti static mat.

■

“Install DIMMs” on page 83

■

“Return the Server Module to Operation” on page 127.

▼

Install DIMMs

■

“DIMM Population Rules and Guidelines” on page 78

■

“Remove DIMMs” on page 82.

Prepare the servermodule for service.

See

“Preparing for Service ” on page 43.

Unpack the replacement DIMMs and place them on an anti static mat.

Ensure that the connector slot ejector tabs are in the open position.

Next Steps

BeforeYou Begin

DIMM Population Rules and Guidelines

Align the replacement DIMM with the connector.

Align the DIMM notch with the key in the connector. This ensures that the DIMM is oriented correctly.

Push the DIMM into the slot until the ejector tabs lift and lock the DIMM in place.

Caution – Component damage. If the DIMM does not easily seat into the connector, verify

correct orientation. If the orientation is reversed, damage to the DIMM or DIMM slot might occur.

Clear any DIMM-relatedfaults and verifyDIMM component information.

Use the Oracle ILOM web interface or CLI to view DIMM component information.

Refer to the

Oracle Integrated Lights Out Manager (ILOM) 3.1 Documentation Collection

(http://www.oracle.com/pls/topic/lookup?ctx=ilom31)

■

“Return the Server Module to Operation” on page 127.

Servicing USB Flash Sticks (CRU)

Note – The Oracle System Assistant USB drive cannot be used for OS install and boot. The drive

is encoded and this function is not permitted by the system. Do not overwrite the Oracle System Assistant USB drive.

Two USB ash drive ports (P0 and P1) are located on the motherboard at the rear of the server module. The USB ash drive port 0, P0, might contain the factory-installed Oracle System Assistant USB ash drive. This drive contains server-specic data and provides important server functionality (for more information about Oracle System Assistant, see

“Return the

Server Module to Operation” on page 127

Next Steps

Servicing USB Flash Sticks (CRU)

Sun Blade X4-2B ServiceManual • March, 201484

Caution – Data and functionality loss. USB ash drive P0 (port 0) might contain the Oracle

System Assistant USB ash drive. Do not misplace, damage, or overwrite this drive.

Use these procedures to remove and install USB ash sticks:

■

“Remove USB Flash Sticks” on page 85

■

“Install USB Flash Sticks” on page 86

▼

Remove USB Flash Sticks

Caution – Data loss. Oracle System Assistant (OSA) software resides on a USB ash drive and

comes preinstalled on X4-2B servers in USB slot P0. Do not remove the Oracle System Assistant USB drive. For information about Oracle System Assistant, see

http://www.oracle.com/

goto/x86AdminDiag/docs

Prepare the servermodule for service.

See

“Preparing for Service ” on page 43.

Note – You do not have to remove the server module top cover to access the rear USB ports.

Locate the USBports P0 (Oracle System Assistant) and P1 on the back of the motherboard.

Pull the USB ash stick out of the USB port.

■

“Return the Server Module to Operation” on page 127.

■

“Install USB Flash Sticks” on page 86

Next Steps

Servicing USB Flash Sticks (CRU)

▼

Install USB Flash Sticks

Caution – Data loss. Oracle System Assistant (OSA) software resides on a USB ash drive and

comes preinstalled on X4-2B servers in USB slot P0. Do not remove the Oracle System Assistant USB drive. For information about Oracle System Assistant, see http://www.oracle.com/

goto/x86AdminDiag/docs

Prepare the servermodule for service.

See

“Preparing for Service ” on page 43.

Note – You do not have to remove the server module top cover to access the rear USB ports.

Locate the correct rear USB port P0 (OracleSystem Assistant) or P1.

Push the USB ash driveinto port 0 or 1.

Caution – Component damage or data loss. USB ash sticks must t inside the rear of the

motherboard. Installing a longer USB drive on the rear port might damage the blade when inserted into the chassis. Drives can be no larger than 7.5 mm wide and 43 .0 mm deep.

■

“Return the Server Module to Operation” on page 127.

Next Steps

Servicing USB Flash Sticks (CRU)

Sun Blade X4-2B ServiceManual • March, 201486

Servicing a Fabric Expansion Module (CRU)

Note – This component is a customer-replaceable unit (CRU).

The fabric expansion module (FEM) is available in either single-width or double-width form factor.

Figure Legend

1 FEM double-width form factor. 2 FEMsingle-width form factor. Install in FEM 0.

Use these procedures to remove and install a fabric expansion module (FEM) card option:

■

“Remove a FEM” on page 88

■

“Install a FEM” on page 88

Servicing a Fabric Expansion Module (CRU)

▼

Remove a FEM

Prepare the servermodule for service.

See

“Preparing for Service ” on page 43.

Insert a ller panel into the empty server slot to reduce the possibility ofa system shut down.

Pull the FEM card up and out of the motherboard.

■

“Install a FEM” on page 88

■

“Return the Server Module to Operation” on page 127.

▼

Install a FEM

Prepare the servermodule for service.

See

“Preparing for Service ” on page 43.

Remove the existingFEM card.

See

“Remove a FEM” on page 88.

Slide the FEM card intothe supportbracket at a slight angle .

Ensure that the edge of the card is under the clips on the bracket.

Note – Always install a single-width form factor FEM in FEM 0.

Next Steps

Servicing a Fabric Expansion Module (CRU)

Sun Blade X4-2B ServiceManual • March, 201488

Press the FEM card carefully into the connector.

■

“Return the Server Module to Operation” on page 127.

Servicing a RAID Expansion Module (CRU)

Note – This component is a customer-replaceable unit (CRU).

The RAID expansion module (REM), if ordered, might not arrive installed on the Sun Blade X4-2B. In some cases, this option is shipped separately for customer installation. The REM enables the RAID functionality for SAS drives.

For additional information, refer to

http://www.oracle.com/goto/x86AdminDiag/docs.

Next Steps

Servicing a RAID Expansion Module (CRU)

Use these procedures to service a REM card option:

■

“Remove a REM Card” on page 90

■

“Install a REM Card” on page 90

■

“Replace a REM Battery on the REM Card” on page 92

▼

Remove a REM Card

Caution – Data loss. Back up your data to an external site before proceeding. The following steps

removes all data from the system.

Prepare the servermodule for service.

See

“Preparing for Service ” on page 43.

Open the REM latch.

Locate the REM support bracketon the motherboard,and pull the REM cardout at an angle away from the support bracket.

Pull the REM card carefully out of theconnector.

■

“Install a REM Card” on page 90

■

“Return the Server Module to Operation” on page 127.

▼

Install a REM Card

Use this procedure with the REM removal procedure to replace an existing REM, or use this procedure for rst-time installation of a REM card in the server.

BeforeYou Begin

Next Steps

Servicing a RAID Expansion Module (CRU)

Sun Blade X4-2B ServiceManual • March, 201490

Caution – Data loss. Back up your data to an external site before proceeding. The following steps

will remove all data from the system.

Prepare the servermodule for service.

See “Preparing for Service ” on page 43.

Insert a ller panel into the empty server slot to reduce the possibility ofa system shut down.

See “Install Server Module Filler Panels” on page 57.

If you arereplacing a REM card, remove the existing card.

See

“Remove a REM Card” on page 90.

Locate the REM support bracketon the motherboard.

For more information, see

“About the Chassis” on page 21.

Close the REM handle.

Slide the REM card under the anges on the support bracket.

The anges are on the support bracket opposite the REM handle.

Carefully align the connector on the underside of the REM card with the connector on the motherboard.

Gently push down on theconnector end of the REM card until the card isfully seated under the REM card retaining spring.

Caution – Component damage. Excessive downward force is not required. When properly

aligned, the connectors mate with minimum downward pressure. If not, realign the connectors slightly and try again. Do not apply excessive force.

An audible click occurs when the spring secures the card.

BeforeYou Begin

Servicing a RAID Expansion Module (CRU)

If this is a rst-time installation of a REM cardin the server module, perform the following sub-steps.

Perform the following sub–steps only if the new disk does not have an operating system, or any data. Skip this step if preloaded software resides on the storage drives.

a. Restore thedata from backups.

b. Install an operating system.

Operating System Link

Linux Sun Blade X4-2B Installation Guide for Linux Operating Systems

Oracle Solaris Sun Blade X4-2B Installation Guide for the Oracle Solaris Operating System

Windows Sun Blade X4-2B Installation Guide for Windows Operating Systems

VM Sun Blade X4-2B Installation Guide for ESX Software

Oracle VM Sun Blade X4-2B Installation Guide for Oracle VM Server

■

“Return the Server Module to Operation” on page 127.

▼

Replace a REM Battery on the REM Card

This task requires a #2 Phillips screwdriver.

Remove the REMcard.

See

“Remove a REM Card” on page 90.

Next Steps

BeforeYou Begin

Servicing a RAID Expansion Module (CRU)

Sun Blade X4-2B ServiceManual • March, 201492

Remove and retainthe three screwssecuring the REM battery to the card.

Remove the REMbattery from the REM card.

Attach the new battery tothe REM card using thethree screws.

Attach any required battery cables.

■

“Install a REM Card” on page 90

■

“Return the Server Module to Operation” on page 127.

Next Steps

Servicing a RAID Expansion Module (CRU)

Servicing Processors (FRU)

Note – This component is a eld-replaceable unit (FRU). A part designated as a FRU must be

replaced by an Oracle-qualied service technician.

Use these procedures to remove and install processor and heat sink assemblies:

■

“Selecting the Correct Processor Removal/Replacement Tool” on page 94

■

“Processor Fault Remind Circuit” on page 97

■

“Identify a Faulty Processor” on page 100

■

“Remove a Processor Heat Sink (FRU)” on page 101

■

“Remove a Processor (FRU)” on page 102

■

“Install a Processor (FRU)” on page 109

■

“Install a Processor Heat Sink (FRU)” on page 114

When replacing processors, you must install processors (CPUs) of the same speeds on the same motherboard.

Selecting the Correct Processor Removal/ReplacementTool

Caution – Component damage. The correct processor removal/replacement tool must be used to

remove and replace a processor; otherwise, the processor or the processor socket might be damaged.

Selecting the correct processor removal/replacement tool is a two-step process. First you determine the size of the processor that is being replaced, then you select the removal/replacement tool that ts that size.

The processors supported by the Sun Blade X4-2B are available in two sizes. The processors with 10 or fewer cores are smaller than the processors with 12 cores. You can determine the size of the processor that you are going to remove and replace in either of these two ways:

■

Use Oracle Integrated Lights Out Manager (ILOM) 3.1 to display processor information.

For instructions, see the Oracle Integrated Lights Out Manager (ILOM) 3.1 Documentation Library at:

http://www.oracle.com/goto/ILOM/docs.

■

Visually check the size of the processor installed in the server.

This requires that you remove the processor heatsink and open the processor independent loading mechanism (ILM) assembly that holds the processor in the socket. For instructions, see Remove a Processor. This is the same procedure that you will use when you remove the processor.

Servicing Processors (FRU)

Sun Blade X4-2B ServiceManual • March, 201494

If you choose to visually check the size of the processor, refer to the next two gures to see how to distinguish the smaller processors from the larger processors. The following image shows the smaller processor installed. Notice that the right and left edges of the processor are within the boundaries of the processor alignment brackets.

Legend Name

1 Processor alignment brackets

2 Processor left and right edges are within alignment bracket boundaries

The following illustration shows the larger processor installed. Notice that the right and left edges of the processor extend beyond the boundaries of the processor alignment brackets.

Selecting the Correct Processor Removal/Replacement Tool

Legend Name

1 Processor alignment brackets

2 Processor left and right edges extend beyond alignment bracket boundaries

After you have determined the size of the processor installed in your server, select the correct processor removal/replacement tool. Like the processors, the processor removal/replacement tool is also available in two sizes. The tool for the smaller processors (processors with 10 or fewer cores) is color-coded green. The tool for the larger processors (12-core processors) is color-coded pink. See the following illustration for the Color-Coded Processor Removal/Replacement Tool.

Legend Name

1 Green, color-coded removal/replacement tool for the smaller processors—models E5-2609 V2

(4-core), E5-2630 V2 (6-core), E5-2650 V2 (8-core), and E5-2690 V2 (10-core)

Selecting the Correct Processor Removal/Replacement Tool

Sun Blade X4-2B ServiceManual • March, 201496

Legend Name

2 Pink, color-coded removal/replacement tool for the larger processor—model E5-2697 V2 (12-core)

Caution – Component damage. The pink color-coded processor removal/replacement tool must

be used only with the larger processor (the 12-core processor). Likewise, the green color-coded removal/replacement tool must be used only with smaller processors (the 4-, 6-, 8-, and 10-core processors); otherwise, the processor or the processor socket might be damaged.

The following table provides an easy reference for matching a processor (by number of cores or model number) to the correct processor removal/replacement tool.

Processor Cores Processor Model Number Processor Removal/ReplacementTool Color Code

4-core E5-2609 V2 Green

6-core E5-2630 V2 Green

8-core E5-2650 V2 Green

10-core E5-2690 V2 Green

12-core E5-2697 V2 Pink

Note – The correct processor removal/replacement tool is included in the box with the

replacement processor. Additionally, both removal/replacement tools ship with replacement motherboards.

Processor Fault Remind Circuit

Use the Fault Remind circuit to identify a failed processor. The processor Fault Remind circuit components are the Fault Remind button, the Charge Status indicator, and the Processor Fault indicators. The following illustrations shows the location of the Fault Remind circuit components and the processors.

Processor FaultRemind Circuit

The following topics describe the components of the Fault Remind circuitry.

FaultRemind Button and Charge Status Indicator

Processor FaultRemind Circuit

Sun Blade X4-2B ServiceManual • March, 201498

Note – Do not press the white Clear CMOS Button (SW1801).

The blue Fault Remind button (SW3001) is located on the motherboard next to the Charge Status indicator (CR3002). The Charge Status indicator is next to the button and shows the usability of the processor test circuit. When the Fault Remind button is pressed, the Charge Status indicator lights green to indicate that there is sucient voltage present in the Fault Remind circuit to activate the fault indicators. Fault indicators identify a processor in a fault state.

Note – Press the Fault Remind circuitry within 15 minutes of removing the server from the

chassis. If the green Charge Status indicator fails to light when you press the Fault Remind button, it is likely that the Fault Remind circuit has lost its charge.

Processor Fault Indicators

Processor FaultRemind Circuit

The amber Processor Fault indicators are mounted on the server module motherboard next to each processor. If a processor is faulty, the indicator for the failed processor lights up when you press the Fault Remind button.

Related Information:

■

See “About the DIMM and Processor Test Circuit ” on page 41

▼

Identify a Faulty Processor

Prepare the servermodule for service.

See

“Preparing for Service ” on page 43.

Processor FaultRemind Circuit

Sun Blade X4-2B ServiceManual • March, 2014100

Sun Oracle Blade X4-2B Service Manual

Specifications and Main Features

Frequently Asked Questions

User Manual