Oracle Server X7-2 Service Manual: Part No: E72445-13
Oracle Server X7-2 Service Manual: Part No: E72445-13
Oracle Server X7-2 Service Manual: Part No: E72445-13
Oracle customers that have purchased support 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.
Référence: E72445-13
Copyright © 2017, 2019, Oracle et/ou ses affiliés. Tous droits réservés.
Ce logiciel et la documentation qui l'accompagne sont 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 stipulation expresse de votre contrat de licence ou de la loi, vous ne pouvez pas copier, reproduire, traduire, diffuser, modifier, accorder de licence, transmettre,
distribuer, exposer, exécuter, publier ou afficher 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 fins d'interopérabilité avec des logiciels tiers ou tel que prescrit par la loi.
Les informations fournies dans ce document sont susceptibles de modification 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 livré sous licence au Gouvernement des Etats-Unis, ou à quiconque qui aurait souscrit la licence de ce logiciel pour le
compte du Gouvernement des Etats-Unis, la notice suivante s'applique :
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-specific supplemental
regulations. As such, use, duplication, disclosure, modification, 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.
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 un risque de dommages corporels. Si vous utilisez ce logiciel ou ce 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 affiliés déclinent toute responsabilité quant aux dommages causés par l'utilisation de ce logiciel ou matériel pour des
applications dangereuses.
Oracle et Java sont des marques déposées d'Oracle Corporation et/ou de ses affiliés. Tout autre nom mentionné peut correspondre à des marques appartenant à d'autres propriétaires
qu'Oracle.
Intel et Intel Xeon sont des marques ou des marques déposées d'Intel Corporation. Toutes les marques SPARC sont 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 de 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 affiliés déclinent toute responsabilité ou garantie expresse quant aux contenus, produits ou services émanant de tiers, sauf mention contraire stipulée
dans un contrat entre vous et Oracle. En aucun cas, Oracle Corporation et ses affilié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, sauf mention contraire stipulée dans un contrat entre vous et Oracle.
Accès aux services de support Oracle
Les clients Oracle qui ont souscrit un contrat de support ont accès au support électronique via My Oracle Support. Pour plus d'informations, visitez le site http://www.oracle.com/
pls/topic/lookup?ctx=acc&id=info ou le site http://www.oracle.com/pls/topic/lookup?ctx=acc&id=trs si vous êtes malentendant.
Contents
5
Contents
Removing and Replacing an NVMe Storage Drive Using Oracle Linux ................... 74
▼ Unmount an NVMe Storage Drive ...................................................... 74
▼ Remove an NVMe Storage Drive ........................................................ 76
▼ Verify Removal of an NVMe Storage Drive .......................................... 77
▼ Install an NVMe Storage Drive .......................................................... 77
▼ Power On an NVMe Storage Drive and Attach a Device Driver ................ 78
▼ Verify Operation of an NVMe Storage Drive ......................................... 78
Removing and Replacing an NVMe Storage Drive Using Microsoft Windows
Server .......................................................................................................... 78
▼ Remove an NVMe Storage Drive ........................................................ 79
▼ Install an NVMe Storage Drive .......................................................... 79
7
Contents
Inconsistencies Between DIMM Fault Indicators and the BIOS Isolation of Failed
DIMMs ...................................................................................................... 105
Using the Server Fault Remind Button ............................................................ 105
▼ Identify and Remove a DIMM .................................................................. 106
▼ Install a DIMM ...................................................................................... 108
Servicing the Internal HBA Card and HBA Super Capacitor (FRU) .................. 169
▼ Remove the Internal HBA Card and HBA Super Capacitor ............................. 170
▼ Install the Internal HBA Card and HBA Super Capacitor ............................... 173
9
Contents
11
Contents
Index ................................................................................................................ 309
■ Overview – Describes how to troubleshoot and maintain the Oracle Server X7-2.
■ Audience – Technicians, system administrators, authorized service providers, and trained
hardware service personnel who have been instructed on the hazards within the equipment
and are qualified to remove and replace hardware.
■ Required knowledge – Advanced experience troubleshooting and replacing hardware.
Feedback
Provide feedback about this documentation at https://www.oracle.com/goto/docfeedback.
These sections describe the controls, connectors, status indicators, system components, and
replaceable components of the server:
Note - Always update the server with the latest firmware, drivers, and other hardware-related
software by downloading the latest software release package when you first receive the server,
and for every new software release. For information about the software release packages and
how to download the software, refer to “Getting Firmware and Software” in Oracle Servers
X7-2 and X7-2L Installation Guide.
Product Description
The Oracle Server X7-2 is an enterprise-class, one rack unit (1U) server. It supports the
following components:
■ Up to two Intel processors. Processors with the following capabilities are supported:
■ Intel Xeon 8160, 24-core, 2.1 GHz, 150W processors
■ Intel Xeon 6140, 18-core, 2.3 GHz, 140W processors
■ Intel Xeon 6128, 6-core, 3.4 GHz, 115W processors
■ Intel Xeon 4114, 10-core, 2.0-2.2 GHz, 85W processors
■ Up to 12 DDR4 DIMMs per processor for a maximum of 24 RDIMMs (16GB and 32GB)
and LRDIMMs (64GB) with speeds up to 2667 MT/sec are supported in dual-processor
systems.
■ Four PCIe Gen3 slots in dual-processor systems: one slot, slot 4, is dedicated to the internal
HBA. PCIe slot 1 is nonfunctional in single-processor systems.
■ Storage drive configurations can comprise both hard disk drives (HDDs) or solid state disk
drives (SSDs). Configurations include:
Related Information
The following figure shows the controls, status indicators (LEDs), connectors, and drives on the
front panel of the Oracle Server X7-2.
Related Information
■ “Back Panel Components and Cable Connections” on page 18
■ “About System Components” on page 19
Note - For more information on back panel components and connections, see “Back Panel
Connector Locations” on page 40. See also “Back Panel Pinhole Switches” on page 45.
Related Information
Callout Description
1 Eight storage drives
2 Front LED indicator module
3 Disk backplane
4 Super capacitor (Energy storage module for the Oracle Storage 12 Gb SAS PCIe RAID HBA, Internal card
in PCIe slot 4.)
5 Fan modules
6 Motherboard
7 Processors and heatsinks (Single-processor systems contain only a single processor in socket P0; socket P1
contains a cover to protect processor socket pins.)
8 Battery
9 (Optional) Internal USB drive
10 Air baffle
11 Top cover
12 Internal M.2 flash SSDs
13 (Optional) PCIe card in slot 3
14 Oracle Storage 12 Gb/s SAS PCIe RAID HBA card in PCIe slot 4
15 (Optional) PCIe card in slot 2
16 (Optional) PCIe card in slot 1
Callout Description
Note - PCIe slot 1 is nonfunctional in single-processor systems.
17 PCIe risers (3)
18 DIMMs (Only twelve DIMMs are supported in single-processor systems and the DIMMs must be installed
in P0 DIMM sockets.)
19 Power supplies
20 Server chassis
Customer-Replaceable Units
The following table lists the customer-replaceable units (CRUs) in the server and directs you to
the replacement instructions.
Related Information
■ “Field-Replaceable Units” on page 22
Field-Replaceable Units
The following table lists the field-replaceable units (FRUs) in the server and directs you to the
replacement instructions.
Related Information
■ “Customer-Replaceable Units” on page 21
■ “Illustrated Parts Breakdown” on page 19
This section includes information about troubleshooting hardware component faults for the
Oracle Server X7-2. It contains the following topics:
■ “Troubleshooting Server Component Hardware Faults” on page 23
■ “Troubleshooting With Diagnostic Tools” on page 37
■ “Attaching Devices to the Server” on page 39
■ “Getting Help” on page 46
■ “Auto Service Requests” on page 48
For more information about server troubleshooting and diagnostics, refer to the Oracle x86
Servers Diagnostics and Troubleshooting Guide for Servers With Oracle ILOM 4.0.x at https:
//www.oracle.com/goto/x86admindiag/docs.
This section contains maintenance-related information and procedures that you can use to
troubleshoot and repair server hardware issues. The following topics are covered.
■ “Troubleshooting Server Hardware Faults” on page 23
■ “Troubleshooting and Diagnostic Information” on page 27
■ “Troubleshooting Using the Server Front and Back Panel Status Indicators” on page 28
■ “Troubleshooting System Cooling Issues” on page 34
■ “Troubleshooting Power Issues” on page 36
When a server hardware fault event occurs, the system lights the Fault-Service Required LED
and captures the event in the Oracle ILOM event log. If you set up notifications through Oracle
ILOM, you also receive an alert through the notification method you chose. When you become
aware of a hardware fault, address it immediately.
Use the following process to address a hardware fault (for the step-by-step procedure, see
“Troubleshoot Hardware Faults Using the Oracle ILOM Web Interface” on page 25).
Related Information
■ “Troubleshoot Hardware Faults Using the Oracle ILOM Web Interface” on page 25
Note - The screens shown in this procedure might differ from those for your server.
This procedure uses the basic troubleshooting steps described in “Basic Troubleshooting
Process” on page 24.
Use this procedure to troubleshoot hardware faults using the Oracle ILOM web interface and, if
necessary, prepare the server for service.
Note - This procedure provides one basic approach to troubleshooting hardware faults. It uses
the Oracle ILOM web interface. However, the procedure can be performed using the Oracle
ILOM command-line interface (CLI). For more information about the Oracle ILOM web
interface and CLI, refer to the Oracle ILOM documentation.
■ Processors
■ Memory
■ Power
■ Cooling
■ Storage
■ Networking
2. In the Status section of the Oracle ILOM Summary Information page, identify the
server subsystem that requires service.
In the following example, the Status page shows that the Processor subsystem requires service,
which indicates that a hardware component in the subsystem is in a fault state.
The Open Problems page provides detailed information, such as the time the event occurred,
the component and subsystem name, and a description of the issue. It also includes a link to an
Oracle Knowledge Base article.
Tip - The System Log provides a chronological list of all the system events and faults that
occurred since the log was last reset and includes additional information, such as severity levels
and error counts. The System Log also includes information on the devices not reported in the
Status section. To access the System Log, in the left panel, click System Log.
In this example, the hardware fault with CPU 0 requires local/physical access to the server.
5. Before going to the server, review the Oracle Server X7-2 Product Notes for
information related to the issue or the component.
The Product Notes contain up-to-date information about the server, including hardware-related
issues. To access the Product Notes, go to https://www.oracle.com/goto/x7-2/docs.
6. To prepare the server for service, see “Preparing for Service” on page 49.
After servicing the component, you might need to clear the fault in Oracle ILOM. For more
information, refer to the service procedure for the component.
The following list displays diagnostic and troubleshooting-related procedures and references
that can assist you with resolving server issues.
■ Oracle x86 Servers Diagnostics and Troubleshooting Guide for Servers With Oracle ILOM
4.0.x
■ Oracle X7 Series Servers Administration Guide
■ “Troubleshooting Using the Server Front and Back Panel Status Indicators” on page 28
■ “Managing Server Hardware Faults Through the Oracle ILOM Fault Management
Shell” on page 37
These sections describe the status indicators (LEDs) located on the front and back of the server,
including those found on components and ports. This section includes the following topics:
Related Information
A normal server boot process involves two indicators, the service processor SP OK LED
indicator and the System OK LED indicator.
When AC power is connected to the server, the server boots into standby power mode:
1. The SP OK LED blinks slowly (0.5 seconds on, 0.5 seconds off) while the SP is starting,
and the System OK LED remains off until the SP is ready.
2. After a few minutes, the main System OK LED slowly flashes the standby blink pattern
(0.1 seconds on, 2.9 seconds off), indicating that the SP (and Oracle ILOM) is ready for
use. In Standby power mode, the server is not initialized or fully powered on at this point.
When powering on the server (either by the On/Standby button or Oracle ILOM), the server
boots to full power mode:
1. The System OK LED blinks slowly (0.5 seconds on, 0.5 seconds off), and the SP OK LED
remains lit (no blinking).
2. When the server successfully boots, the System OK LED remains lit. When the System OK
LED and the SP OK LED indicators remain lit, the server is in Main power mode.
Note - The green System OK LED indicator and the green SP OK indicator remain lit (no
blinking) when the server is in a normal operating state.
There are seven system-level status indicators (LEDs), some of which are located on both the
server front panel and the back panel. For the location of the status indicators, see “Front and
Back Panel Components” on page 16. The following table describes these indicators.
Each fan module has one status indicator (LED). The LEDs are located on the chassis mid-
wall adjacent to and aligned with the fan modules and are visible when the server top cover is
removed.
There are two status indicators (LEDs) on each power supply. These indicators are visible from
the back of the server.
The server has one 10/100/1000BASE-T Ethernet management domain interface, labeled NET
MGT. There are two status indicators (LEDs) on this port. These indicators are visible from the
back of the server.
Note - The 10/25GbE SFP+ (NET 1 and NET 2) ports are the default network ports for the
server. When using an SFP+ port, network connectivity is disabled on the 10GBASE-T RJ-45
GbE (NET 1 and NET 2) ports.
There are two status indicators (LEDs) on each port. These indicators are visible from the rear
of the server.
Maintaining the proper internal operating temperature of the server is crucial to the health of the
server. To prevent server shutdown and damage to components, address over temperature and
hardware-related issues as soon as they occur. If your server has a temperature-related fault, use
the information in the following table to troubleshoot the issue.
If your server does not power on, use the information in the following table to troubleshoot the
issue.
The Oracle ILOM Fault Management Shell enables you to view and manage fault activity on
managed servers and other types of devices.
For more information about how to use the Oracle ILOM Fault Management Shell, refer to the
Oracle ILOM User's Guide for System Monitoring and Diagnostics Firmware Release 4.0.x in
the Oracle Integrated Lights Out Manager (ILOM) 4.0 Documentation Library at https://www.
oracle.com/goto/ilom/docs.
The server and its accompanying software and firmware contain diagnostic tools and features
that can help you isolate component problems, monitor the status of a functioning system,
and exercise one or more subsystem to disclose more subtle or intermittent hardware-related
problems.
Each diagnostic tool has its own specific strength and application. Review the tools listed in this
section and determine which tool might be best to use for your situation. After you determine
the tool to use, you can access it locally, while at the server, or remotely.
■ “Diagnostic Tools” on page 38
■ “Diagnostic Tool Documentation” on page 39
Diagnostic Tools
The selection of diagnostic tools available for your server range in complexity from a
comprehensive validation test suite (Oracle VTS) to a chronological event log (Oracle ILOM
event Log). The selection of diagnostic tools also includes standalone software packages,
firmware-based tests, and hardware-based LED indicators.
The following table summarizes the diagnostic tools that you can use when troubleshooting or
monitoring your server.
The following table identifies where you can find more information about diagnostic tools.
The following sections contain procedural information for attaching devices to the server so you
can access diagnostic tools when troubleshooting and servicing the server:
This procedure explains how to connect devices to the server (remotely and locally), so that you
can interact with the service processor (SP) and the server console.
1. Connect an Ethernet cable to the Gigabit Ethernet (NET) connector as needed for
OS support.
See “Back Panel Connector Locations” on page 40.
2. To connect to the service processor's Oracle ILOM over the network, connect an
Ethernet cable to the Ethernet port labeled NET MGT.
See “Back Panel Connector Locations” on page 40.
3. To access the Oracle ILOM command-line interface (CLI) locally, connect a serial
null modem cable to the RJ-45 serial port labeled SER MGT.
To access the system console, connect the RJ-45 cable to a terminal or terminal emulator, log on
to Oracle ILOM, and type start /HOST/console.
See “Back Panel Connector Locations” on page 40.
By default, the service processor (SP) controls the serial management (SER MGT) port and
uses it to redirect the host serial console output. Using Oracle ILOM, you can assign the host
console (COM1) as owner of the SER MGT port output, which allows the host console to
output information directly to the SER MGT port. Serial port sharing is useful for Windows
kernel debugging, because you can view non-ASCII character traffic output from the host
console.
Set up the network on the SP before attempting to change the serial port owner to the host
server. If the network is not set up first, and you switch the serial port owner to the host
server, you cannot connect using the CLI or web interface to change the serial port owner
back to the SP. To return the serial port owner setting to the SP, restore access to the serial
port on the server. For details, refer to the Oracle Integrated Lights Out Manager (ILOM) 4.0
Documentation Library at https://www.oracle.com/goto/ilom/docs.
If you accidentally lose access to Oracle ILOM, contact Oracle Service and follow the process
to return the serial port ownership back to the SP.
You can assign serial port output using either the Oracle ILOM CLI interface or web interface,
as described in the following sections:
■ “Assign Serial Port Output Using the Oracle ILOM CLI” on page 43
■ “Assign Serial Port Output Using the Oracle ILOM Web Interface” on page 43
1. Open an SSH session, and at the command line, log in to the SP Oracle ILOM
CLI.
Log in as a user with root or administrator privileges. For example:
ssh root@ipaddress
4. In the Serial Port Settings page, select Host Server as the serial port owner.
Note - The drive names provided in the table assume that NVMe cabling between the
motherboard NVMe connectors and the disk backplane is correct.
This section contains information about the boot order and device naming for the Gigabit
Ethernet ports on the back panel of the server. For location information, see “Back Panel
Connector Locations” on page 40.
The order in which the BIOS detects the Ethernet ports during server boot is listed below.
Note - You can change the boot priority using the Boot Device Priority screen available in the
Boot menu of the BIOS Setup Utility.
1. NET 0
2. NET 1
3. NET 2
The device naming for the Ethernet interface is reported differently by different interfaces
and operating systems. The following table shows the BIOS (physical) and operating system
(logical) naming convention for the interface. This naming convention might vary depending on
the conventions of your operating system and which devices are installed in the server.
Note - Naming used by the interfaces might vary from that listed below depending on which
devices are installed in the system.
Note - For Windows, port names such as Ethernet, Ethernet 2, and Ethernet 3 are used by
default. However, actual port naming is based on the order of enumeration, typically during
operating system installation. Additionally, Windows allows you to rename the ports to meet
application-specific needs.
Oracle Service personnel might instruct you to use the back panel pinhole switches to reset the
NMI, Host Warm Reset, or SP, as shown in the following figure.
3 SP Reset
†
Oracle Service use only.
Getting Help
The following sections describe how to get additional help to resolve server-related problems.
Contacting Support
If the troubleshooting procedures in this chapter fail to solve your problem, use the following
table to collect information that you might need to communicate to support personnel.
IP address
Server name (system host name)
Network or internet domain name
Proxy server configuration
Related Information
■ “Locating the Chassis Serial Number” on page 47
You might need your server serial number when you ask for service on your system. Record
this number for future use. Use one of the following resources or methods to locate your server
serial number.
■ The serial number is located on the Radio-frequency Identification (RFID) label on the
bottom left side of the front panel bezel, below the general status LEDs.
For illustrations of the server front panel, see “Front and Back Panel
Components” on page 16.
■ The serial number is recorded on a label that is attached to the top-front surface of the
system.
■ The serial number is recorded on the yellow Customer Information Sheet (CIS) that is
attached to your server packaging.
Oracle Auto Service Requests (ASR) is a feature available to customers having Oracle Premier
Support and is provided to those customers at no additional cost. Oracle ASR is the fastest
way to restore system availability if a hardware fault occurs. Oracle ASR software is secure
and customer installable, with the software and documentation downloadable from My Oracle
Support at https://support.oracle.com. When you log in to My Oracle Support, refer to the
"Oracle Auto Service Request" knowledge article document (ID 1185493.1) for instructions on
downloading the Oracle ASR software.
When a hardware fault is detected, Oracle ASR opens a service request with Oracle and
transfers electronic fault telemetry data to help expedite the diagnostic process. Oracle
diagnostic capabilities then analyze the telemetry data for known issues and delivers immediate
corrective actions. For security, the electronic diagnostic data sent to Oracle includes only what
is needed to solve the problem. The software does not use any incoming Internet connections
and does not include any remote access mechanisms.
These sections describe safety considerations and provide prerequisite procedures and
information to replace components within the server:
■ “Safety Precautions” on page 49
■ “Safety Symbols” on page 50
■ “Electrostatic Discharge Safety” on page 50
■ “FRU Key Identity Properties (KIP) Automated Update” on page 51
■ “Required Tools” on page 52
■ “Preparing the Server for Component Replacement” on page 52
Related Information
■ “Returning the Server to Operation” on page 211
Safety Precautions
For your protection, observe the following safety precautions when setting up your equipment:
■ Follow all standard cautions, warnings, and instructions marked on the equipment and
described in the Oracle Server X7-2 Safety and Compliance Guide and in the printed
Important Safety Information for Oracle's Hardware Systems.
■ Ensure that the voltage and frequency of your power source match the voltage and
frequency inscribed on the equipment's electrical rating label.
■ Follow the electrostatic discharge safety practices as described in “Electrostatic Discharge
Safety” on page 50.
■ Disconnect both power supply cords (if necessary) before servicing components.
Related Information
■ “Safety Symbols” on page 50
Safety Symbols
The following symbols might appear in this book. Note their meanings.
Caution - Hot surface. Avoid contact. Surfaces are hot and might cause personal injury if
touched.
Caution - Hazardous voltages are present. To reduce the risk of electric shock and danger to
personal health, follow the instructions.
Related Information
■ “Safety Precautions” on page 49
■ “Electrostatic Discharge Safety” on page 50
Devices that are sensitive to electrostatic discharge (ESD), such as the motherboard, PCIe cards,
drives, processors, and memory cards require special handling.
Caution - The boards and drives contain electronic components that are extremely sensitive to
static electricity. Ordinary amounts of static electricity from clothing or the work environment
can destroy components. Do not touch the components along their connector edges.
chassis. Following this practice equalizes the electrical potentials between you and the
server.
Note - An antistatic wrist strap is not included in the Ship Kit for the server. However,
antistatic wrist straps are included with optional components.
Related Information
■ “Safety Precautions” on page 49
■ “Safety Symbols” on page 50
■ “Preparing the Server for Component Replacement” on page 52
■ “Returning the Server to Operation” on page 211
Oracle ILOM includes a key identity properties (KIP) auto-update feature that ensures product
information that is used for service entitlement and warranty coverage is accurately maintained
by the server at all times, including during hardware replacement activities.
The KIP includes the server product name, product part number (PPN), and product serial
number (PSN). The KIP is stored in the FRUID (field-replaceable unit identifiers) container of
the three server FRUs that are designated quorum members.
When a server FRU that contains the KIP is removed and a replacement component is installed,
the KIP of the replacement component is programmed by Oracle ILOM to contain the same
KIP as the other two components.
Note - Only one of the quorum members can be replaced at a time. Automated updates can only
be completed when two of the three quorum members contain matching key identity properties.
Related Information
■ “Servicing Power Supplies (CRU)” on page 87
■ “Servicing the Disk Backplane (FRU)” on page 151
■ “Servicing the Motherboard Assembly (FRU)” on page 199
Required Tools
Related Information
■ “Preparing for Service” on page 49
Before you can remove and install components that are inside the server, you must perform the
procedures in some or all of the following tasks:
Note - When replacing the storage drives or power supplies, not all of these procedures are
necessary. See the replacement tasks for those components for more information.
Related Information
■ “Returning the Server to Operation” on page 211
To determine how you want to power off the server, view the options in the following table.
Note - Some server components, such as storage drives, power supplies, and fan modules are
hot-pluggable. Components that are hot-pluggable do not require the server to be powered down
when performing service procedures.
Description Link
Power down the server gracefully to save all data and to ■ “Power Down Server Gracefully Using the Oracle
prevent data from being corrupted. Performing a graceful ILOM CLI” on page 54
shutdown ensures that the system is ready for restart. ■ “Power Down Server Gracefully Using the Oracle
ILOM Web Interface” on page 55
■ “Power Down Server Gracefully Using the On/
Standby Button” on page 56
If the server is not responding, or you must shut down ■ “Power Down the Server for Immediate Shutdown
the server quickly, perform an immediate shutdown. Using the On/Standby Button” on page 57
■ “Power Down the Server for Immediate Shutdown
Using the Oracle ILOM CLI” on page 57
■ “Power Down the Server for Immediate
Shutdown Using the Oracle ILOM Web
Interface” on page 58
Related Information
■ “Power On the Server” on page 216
Performing a graceful shutdown ensures that all of your data is saved and the system is ready
for restart.
Note - The stop /System command does not guarantee a system shutdown. This command
is only a request to the host operating system (OS) to perform a system shutdown. To ensure
a system shutdown, see “Power Down the Server for Immediate Shutdown Using the Oracle
ILOM CLI” on page 57.
If the system is running the Oracle Solaris OS, refer to the Oracle Solaris system administration
documentation for additional information.
The host server performs an orderly power shutdown to Standby power mode, and the
System OK LED on the front panel begins blinking. See “Server System-Level Status
Indicators” on page 29.
Caution - When you power down the server using Oracle ILOM, the server enters Standby
power mode. Power is still directed to the service processor remote management subsystem and
power supply fans. To completely power off the server, you must disconnect the power cords
from the power supplies.
Related Information
■ “Power Down Server Gracefully Using the Oracle ILOM Web Interface” on page 55
■ “Power Down Server Gracefully Using the On/Standby Button” on page 56
■ “Power Down the Server for Immediate Shutdown Using the On/Standby
Button” on page 57
■ “Power On the Server” on page 216
5. In the left pane, click Host Management → Power Control, and select Graceful
Shutdown and Power Off from the Action list.
7. Disconnect the power cords and data cables from the server.
See “Disconnect Cables From the Server” on page 59.
Caution - When you power down the server using Oracle ILOM, the server enters Standby
power mode. Power is still directed to the service processor and power supply fans. To
completely power off the server, you must disconnect the power cords from the power supplies.
Related Information
■ “Power Down Server Gracefully Using the Oracle ILOM CLI” on page 54
■ “Power Down Server Gracefully Using the On/Standby Button” on page 56
■ “Power Down the Server for Immediate Shutdown Using the On/Standby
Button” on page 57
■ “Power On the Server” on page 216
1. Press and quickly release the On/Standby button on the front panel.
This action causes ACPI-enabled operating systems to perform an orderly shutdown of the
operating system. Servers not running ACPI-enabled operating systems shut down to Standby
power mode immediately.
When main power is off, the System OK LED on the front panel begins blinking, indicating that
the server is in Standby power mode. See “Server System-Level Status Indicators” on page 29.
2. Disconnect the power cords and data cables from the server.
See “Disconnect Cables From the Server” on page 59.
Caution - When you power down the server using the On/Standby button, the server enters
Standby power mode. Power is still directed to the service processor and power supply fans. To
completely power off the server, you must disconnect the power cords from the power supplies.
Related Information
■ “Power Down Server Gracefully Using the Oracle ILOM CLI” on page 54
■ “Power Down Server Gracefully Using the Oracle ILOM Web Interface” on page 55
■ “Power Down the Server for Immediate Shutdown Using the On/Standby
Button” on page 57
■ “Power On the Server” on page 216
Caution - An immediate power-off might corrupt system data, therefore, use this procedure to
power down the server only after attempting the graceful power down procedure.
1. Press and hold the On/Standby button for four seconds to force the Main power
off and to enter Standby power mode.
When Main power is off, the System OK LED on the front panel begins blinking,
indicating that the server is in Standby power mode. See “Server System-Level Status
Indicators” on page 29.
Caution - When you press the On/Standby button to enter Standby power mode, power is still
directed to the service processor and power supply fans. To completely power off the server,
you must disconnect the power cords from the power supplies.
Related Information
■ “Power Down Server Gracefully Using the Oracle ILOM CLI” on page 54
■ “Power Down Server Gracefully Using the Oracle ILOM Web Interface” on page 55
■ “Power Down Server Gracefully Using the On/Standby Button” on page 56
■ “Power Down the Server for Immediate Shutdown Using the Oracle ILOM
CLI” on page 57
■ “Power Down the Server for Immediate Shutdown Using the Oracle ILOM Web
Interface” on page 58
■ “Power On the Server” on page 216
Caution - An immediate power-off might corrupt system data, therefore, use this procedure to
power down the server only after attempting the graceful power down procedure.
Oracle ILOM displays the default command prompt (->), indicating that you have successfully
logged in to Oracle ILOM.
Caution -When the server is powered down, it enters Standby power mode In standby power
mode, power is still directed to the service processor and power supply fans. To completely
power off the server, you must disconnect the power cords from the power supplies.
Related Information
■ “Power Down the Server for Immediate Shutdown Using the On/Standby
Button” on page 57
■ “Power Down the Server for Immediate Shutdown Using the Oracle ILOM Web
Interface” on page 58
Caution - An immediate power-off might corrupt system data, therefore, use this procedure to
power down the server only after attempting the graceful power down procedure.
2. In the left pane, click Host Management → Power Control, and select Immediate
Power Off in the Select Action list.
Caution -When the server is powered down, it enters Standby power mode In standby power
mode, power is still directed to the service processor and power supply fans. To completely
power off the server, you must disconnect the power cords from the power supplies.
Related Information
■ “Power Down the Server for Immediate Shutdown Using the On/Standby
Button” on page 57
■ “Power Down Server Gracefully Using the Oracle ILOM CLI” on page 54
■ “Power On the Server” on page 216
Caution -The system supplies Standby power to the circuit boards when the power cords are
connected even when the system is powered off.
Related Information
■ “Back Panel Components and Cable Connections” on page 18
■ “Powering Down the Server” on page 53
■ “Remove the Server From the Rack” on page 61
■ “Reconnect Data Cables and Power Cords” on page 216
■ Storage drives
■ Fan modules
■ Power supplies
■ PCIe risers
■ PCIe cards and cables
■ SAS cables
■ NVMe cables
■ DIMMs
■ Internal USB flash drive
■ M.2 flash SSDs
■ System battery
■ Processors
■ Disk backplane
■ Front LED indicator module
■ Motherboard assembly
If the server is installed in a rack with extendable slide-rails, use this procedure to extend the
server to the maintenance position.
1. To prevent the rack from tipping forward when the server is extended, extend all
rack anti-tilt mechanisms.
Refer to “Stabilize the Rack” in Oracle Servers X7-2 and X7-2L Installation Guide. Also refer
to the Oracle Rack Cabinet 1242 User's Guide at https://docs.oracle.com/cd/E85660_01/
index.html.
2. Verify that no cables will be damaged or will interfere when the server is
extended.
Although the cable management arm (CMA) that is supplied with the server is hinged to
accommodate extending the server, you should ensure that all cables and cords are capable of
extending.
3. From the front of the server, open and hold the left and right release latch covers
in the open position [1].
When in an open position, the release latch covers engage the slide-rail release latches [1].
Caution - Deploy any rack anti-tilt mechanism before releasing the slide-rail release latches.
4. While the release latch covers are in the open position, slowly pull the server
forward until the slide-rails latch into a locked position [2].
The server is now in the extended maintenance position.
Related Information
■ “Disconnect Cables From the Server” on page 59
■ “Remove the Server From the Rack” on page 61
■ “Reinstall the Server Into the Rack” on page 213
Caution - The server weighs approximately 35.0 lbs (15.88 kg). Two people are required to
dismount and carry the chassis.
1. Disconnect all the cables and power cords from the server.
4. From the front of the server, pull the green slide-rail release tabs toward the front
of the server, and pull the server out of the rack until it is free of the rack rails.
A slide-rail release tab is located on each slide-rail.
Note - To pull the green slide-rail release tab, place your finger in the center of the tab, not on
the end, and apply pressure as you pull the tab toward the front of the server.
Related Information
■ “Disconnect Cables From the Server” on page 59
■ “Take Antistatic Measures” on page 62
■ “Extend the Server to the Maintenance Position” on page 59
■ “Reinstall the Server Into the Rack” on page 213
Note - An antistatic wrist strap is not included in the Ship Kit for the server. However, antistatic
wrist straps might be included with options and components.
Related Information
■ “Remove Antistatic Measures” on page 213
1. Ensure that the AC power cords are disconnected from the server power
supplies.
Note - Fan modules are hot-pluggable and do not require AC power cables to be disconnected
from the server power supplies.
2. If the release button latch is in the locked position, use a Torx T15 screwdriver to
turn the release button latch clockwise to the unlocked position.
Lift up on the release button on top of the server cover. Lifting the release button causes the
server cover to slide toward the rear of the chassis for easy removal.
Related Information
■ “Take Antistatic Measures” on page 62
■ “Install the Server Top Cover” on page 212
This section describes how to service storage drives. Storage drives are customer-replaceable
units (CRUs) that do not require you to power off the server. For more information about CRUs,
see “Illustrated Parts Breakdown” on page 19 and “Customer-Replaceable Units” on page 21.
■ “Storage Drives Hot-Plug Conditions” on page 65
■ “Storage Drive Failure and RAID” on page 66
■ “Storage Drive Locations and Numbering” on page 66
■ “Removing and Replacing a Storage Drive” on page 67
■ “Removing and Replacing an NVMe Storage Drive Using Oracle Solaris” on page 71
■ “Removing and Replacing an NVMe Storage Drive Using Oracle Linux” on page 74
■ “Removing and Replacing an NVMe Storage Drive Using Microsoft Windows
Server” on page 78
Related Information
■ “Remove and Install Filler Panels” on page 211
The hard-disk drives (HDDs), solid-state drives (SSDs), or NVMe SSD drives that are installed
in the server are in most cases hot-pluggable. This capability depends on how the drives are
configured and whether the drive is an NVMe device. To hot-plug a drive you must take the
drive offline before you can remove it. When you take the drive offline, you prevent any
application from accessing the drive and remove the logical software links to the drive. For an
NVMe storage drive, you must not only take the drive offline, but also power down the drive
slot.
■ The drive cannot be logically isolated from the online operations of the server.
■ The operating system does not support hot plug for the drive.
If any of these disk drive conditions are true, then you must shut down the system before you
replace the drive. See “Powering Down the Server” on page 53.
Note - Replacing a storage drive does not require removing the server from a rack.
Related Information
For instructions for configuring RAID on the server, refer to “Configuring Storage Drives for
Operating System Installation” in Oracle Servers X7-2 and X7-2L Installation Guide.
Callout Description
1 Storage drive 0 HDD/SSD/NVMe
2 Storage drive 1 HDD/SSD/NVMe
3 Storage drive 2 HDD/SSD/NVMe
4 Storage drive 3 HDD/SSD/NVMe
5 Storage drive 4 HDD/SSD/NVMe
6 Storage drive 5 HDD/SSD/NVMe
7 Storage drive 6 HDD/SSD/NVMe
8 Storage drive 7 HDD/SSD/NVMe
Note - The NVMe storage drives are labeled NVMe0 through NVMe7; however, operating
systems installed on the server assign different names to the NVMe storage drives. For the
corresponding names assigned to the NVMe storage drives by server operating systems, see
“Server Operating System Names for the NVMe Storage Drives” on page 44.
■ If you are removing an HDD or SSD storage drive, type the operating system
commands required to stop the server from using the drive; otherwise,
proceed to the next step.
The exact commands required depend on the configuration of your drives. Unmount file
systems or issue RAID commands, as needed.
Note - The blue OK to Remove status indicator LED on the drive might not light, as support for
this varies depending on the operating system in use. For information on storage drive status
indicators (LEDs), see “Storage Drive Status Indicators” on page 31.
■ If you are removing an NVMe storage drive, see the procedures for your
operating system.
Note - NVMe storage drives are supported only on servers that are running Oracle Solaris,
Oracle Linux, Oracle VM, or Microsoft Windows Server. Servers that are running Red Hat
Enterprise Linux do not support NVMe drives.
4. Push the latch release button to open the drive latch [1].
Caution - The latch is not an ejector. Do not open the latch too far to the right. Doing so can
damage the latch.
5. Grasp the latch and pull the drive out of the drive slot [2].
■ If you are replacing the drive, continue to “Install a Storage Drive” on page 70.
■ If you are not replacing the drive, install a filler panel in the empty drive slot to maintain
proper airflow and perform administrative tasks to configure the server to operate without
the drive.
For information on how to install a storage drive filler panel, see “Remove and Install Filler
Panels” on page 211.
Related Information
4. Slide the drive into the slot until the drive is fully seated [1].
Related Information
■ “Storage Drive Status Indicators” on page 31
■ “Storage Drives Hot-Plug Conditions” on page 65
The following sections describe how to remove and replace an NVMe storage drive on a server
that is running the Oracle Solaris operating system.
■ “Unmount an NVMe Storage Drive” on page 71
■ “Remove an NVMe Storage Drive” on page 72
■ “Verify Removal of an NVMe Storage Drive” on page 72
■ “Install an NVMe Storage Drive” on page 73
■ “Power On an NVMe Storage Drive and Attach a Device Driver” on page 73
3. To prepare the NVMe drive for removal, that is, to detach the device driver and
power off the drive slot, type the following commands:
# hotplug poweroff Slot100
# hotplug list –lc
The following output appears for the NVMe drive that has been unmounted:
# hotplug list –lc
Connection State Description Path
---------------------------------------------------------------------------------------
Slot100 PRESENT PCIe-Native /pci@13,0/pci8086,2030@0/pci111d,80b5@0/pci111d,80b5@5
4. Verify that the OK to Remove indicator (LED) on the NVMe storage drive is lit.
Perform this procedure to physically remove an NVMe storage drive from the server.
1. Identify the physical location of the NVMe drive that you want to remove.
For storage drive locations, see “Storage Drive Locations and Numbering” on page 66.
2. Verify that the OK to Remove indicator (LED) on the NVMe storage drive is lit.
3. On the drive that you plan to remove, push the latch release button to open the
drive latch.
4. Grasp the latch and pull the drive out of the drive slot.
See “Remove a Storage Drive” on page 67.
Perform this procedure to physically install an NVMe storage drive into the server.
Note - After you physically remove an NVMe storage drive from the server, wait at least 10
seconds before installing a replacement drive.
1. Remove the replacement drive from its packaging and place the drive on an
antistatic mat.
4. Slide the drive into the slot until the drive is fully seated.
See “Install a Storage Drive” on page 70.
3. To check the NVMe drive health, firmware level, temperature, get error log,
SMART data, security erase, low level format, and other data, type:
# nvmeadm list
Related Information
■ “Storage Drive Status Indicators” on page 31
■ “Storage Drives Hot-Plug Conditions” on page 65
■ “Storage Drive Failure and RAID” on page 66
■ “Storage Drive Locations and Numbering” on page 66
The following sections describe how to remove and replace an NVMe storage drive on a server
that is running the Oracle Linux operating system.
/sys/devices/pci0000:80/0000:80:03.0/0000:b0:00.0/0000:b1:04.0/0000:b2:00.0/misc/
nvme0
/sys/devices/pci0000:80/0000:80:03.0/0000:b0:00.0/0000:b1:05.0/0000:b4:00.0/misc/
nvme1
In the above listing the PCIe addresses are highlighted in bold text.
b. To obtain the slot number (APIC ID) for the bus address, type the following
command to list all of the PCIe slot numbers and the corresponding bus
addresses:
# egrep –H ‘.*’ /sys/bus/pci/slots/*/address
This commands returns output similar to the following:
/sys/bus/pci/slots/10/address:0000:b8:00
/sys/bus/pci/slots/11/address:0000:b6:00
/sys/bus/pci/slots/12/address:0000:b2:00 (instance nvme0, pcie slot 12, drive
label nvme2)
/sys/bus/pci/slots/13/address:0000:b4:00 (instance nvme1, pcie slot 13, drive
label nvme3)
In the above output, the bus addresses for the corresponding NVMe instances are
highlighted in bold text.
Note - In the above output, notice that the instance names for the NVMe drives do not
correspond to the NVMe drive labels on the front of the server, that is, pci/slots/12/address:
0000:b2:00 corresponds to instance nvme0; however, on the front of the server, this drive is
labeled NVMe2. For a table that shows the relationship between the pci/slot# and the NVMe
storage drive label on the front of the server, see “Server Operating System Names for the
NVMe Storage Drives” on page 44.
c. Disconnect all users of the NVMe drive and back up the NVMe drive data as
needed.
i. Use the umount command to unmount any file systems that are mounted
on the device.
ii. Remove the device from any multiple device (md) and Logical Volume
Manager (LVM) volume using it.
If the device is a member of an LVM Volume group, then it might be necessary
to move data off the device using the pvmove command, then use the vgreduce
command to remove the physical volume, and (optionally) pvremove to remove the
LVM metadata from the disk.
iii. If the device uses multipathing, run multipath -l and note all the paths
to the device. Then, remove the multipathed device using the multipath
-f device command.
iv. Run the blockdev --flushbufs device command to flush any outstanding
I/O to all paths to the device.
3. To prepare the NVMe drive for removal, that is, to detach the NVMe device driver
and power off the NVMe drive slot, type:
# echo 0 > /sys/bus/pci/slots/$slot/power
Where $slot is the slot number obtained in step Step 2b above.
4. Verify that the OK to Remove indicator (LED) on the NVMe drive is lit.
Perform this procedure to physically remove an NVMe storage drive from the server.
1. Identify the location of the NVMe drive that you want to remove.
For storage drive locations, see “Storage Drive Locations and Numbering” on page 66.
2. Verify that the OK to Remove indicator (LED) on the NVMe drive is lit.
3. On the NVMe drive you plan to remove, push the latch release button to open the
drive latch.
4. Grasp the latch and pull the drive out of the drive slot.
“Remove a Storage Drive” on page 67.
■ If you are replacing the drive, continue to “Verify Removal of an NVMe Storage
Drive” on page 77.
■ If you are not replacing the drive, install a filler panel in the empty drive slot to maintain
proper airflow and perform administrative tasks to configure the server to operate without
the drive.
For information on how to install a storage drive filler panel, see “Remove and Install Filler
Panels” on page 211.
2. View the command output and verify that the entry for the slot number that was
disabled no longer appears.
This commands returns output similar to the following:
Perform this procedure to physically install an NVMe storage drive into the server.
After you physically remove an NVMe drive from the server, wait at least 10 seconds before
installing a replacement drive.
1. Remove the replacement drive from its packaging and place the drive on an
antistatic mat.
4. Slide the drive into the slot until the drive is fully seated.
See “Install a Storage Drive” on page 70.
Related Information
Note - NVMe storage drive hot plug is not supported for an Oracle Server X7-2 running
Microsoft Windows Server. The system must be powered down before removing and replacing
an NVMe storage drive.
1. Power down the server that contains the storage drive to be removed.
See “Powering Down the Server” on page 53.
2. On the NVMe drive you plan to remove, push the latch release button to open the
drive latch.
See “Remove a Storage Drive” on page 67.
3. Grasp the latch and pull the drive out of the drive slot.
1. Remove the replacement drive from its packaging and place the drive on an
antistatic mat.
4. Slide the drive into the slot until the drive is fully seated.
See “Install a Storage Drive” on page 70.
Related Information
■ “Storage Drive Status Indicators” on page 31
■ “Storage Drives Hot-Plug Conditions” on page 65
■ “Storage Drive Failure and RAID” on page 66
■ “Storage Drive Locations and Numbering” on page 66
This section describes how to service fan modules. Fan modules are customer-replaceable units
(CRUs) that do not require you to power off the server. For more information about CRUs, see
“Illustrated Parts Breakdown” on page 19 and “Customer-Replaceable Units” on page 21.
The fan modules are located in the front of the server. See the following procedures:
■ “Remove a Fan Module” on page 81
■ “Install a Fan Module” on page 84
Related Information
■ “Remove the Server Top Cover” on page 63
You do not have to power off the server to service the fan modules.
You should not begin this procedure unless you have a replacement fan and you are ready to
install it right away.
Caution - When removing and replacing a fan module in the Oracle Server X7-2, you must
complete the entire procedure within 20 seconds to maintain adequate cooling within the
system. Remove and replace only one fan module at a time. Ensure that you have obtained the
replacement fan module and that is it is ready for installation before starting the replacement
procedure. Each fan module contains two fans, with two fan motors per fan. The four fan
motors provide separate tachometer signals so that the fan module reports four tach signals to
Oracle ILOM. Even if only one fan motor is faulted within the fan module, the Oracle ILOM
service processor detects that four fan motors have failed to spin while the fan module is
removed. If the fan module is not replaced within 20 seconds of removal, Oracle ILOM will
take the protective action to shut down the system to prevent thermal damage to the system.
a. Using your thumb and forefinger, grasp the fan module in the finger
recesses located in the plastic between the fans.
Caution - When removing a fan module, do not rock it back and forth. Rocking a fan module
can cause damage to the motherboard connectors.
Caution - Do not service any other components in the fan compartment unless the system is
shut down and the power cords are removed.
■ If you removed the fan assembly as part of another procedure, return to that procedure.
■ Otherwise, continue to “Install a Fan Module” on page 84.
Related Information
2. With the server top cover removed, position the replacement fan module into the
server.
The fan modules are keyed to ensure that they are installed in the correct orientation.
3. Press down on the fan module and apply firm pressure to fully seat the fan
module.
4. Verify that the fan module status indicator (LED) that aligns with the replaced fan
module is extinguished.
6. Verify that the Top Fan Fault LED on the front of the server and the Fault-Service
Required LEDs on the front and back of the server are extinguished.
See “Troubleshooting Using the Server Front and Back Panel Status Indicators” on page 28 for
more information about identifying and interpreting system indicators.
Related Information
■ “Remove a Fan Module” on page 81
This section describes how to service power supplies. Power supplies are customer-replaceable
units (CRUs) that do not require you to power off the server. For more information about CRUs,
see “Illustrated Parts Breakdown” on page 19 and “Customer-Replaceable Units” on page 21.
The power supplies are located at the back of the server. See the following procedures:
■ “Power Supply Overview” on page 87
■ “Remove a Power Supply” on page 88
■ “Install a Power Supply” on page 90
The server supports model A266 (1200 watt) power supplies. The A266 power supply unit
(PSU) provides conversion from the AC lines to the system, accepting ranges from 100-240
volts AC (VAC). These PSUs are designed to be hot-pluggable, and in most cases will provide
fully redundant “1+1” power, allowing the system to suffer the loss of a PSU or an AC feed
with no loss to system availability.
In maximally configured systems, it is possible that the worst-case power consumption of the
system could exceed the capacity of a single PSU. The PSUs provide an over-subscription
mode, which allows the system to operate with fault-tolerance even with modest excursions
beyond the rated capacity of a single PSU. This over-subscription support is accomplished
using hardware signaling between the PSU and motherboard circuitry, which can force the
system to throttle processor (CPU) and memory power in the event that a PSU is lost. The
resulting power savings will be enough to allow the system to continue to run (in a lower-
performance state) until the power problem is resolved.
The following status indicators (LEDs) are lit when a power supply fault is detected:
For more information, see “Power Supply Status Indicators” on page 31.
If a power supply fails and you do not have a replacement available, leave the failed power
supply installed to ensure proper airflow in the server.
Related Information
■ “Troubleshooting Using the Server Front and Back Panel Status Indicators” on page 28
Callout Description
1 Power supply 0
Callout Description
2 Power supply 1
A lit amber Fault-Service Required LED on a power supply indicates that a failure was
detected. You can also use the Oracle ILOM show faulty command at the Oracle ILOM
command line prompt (->) to identify a power supply failure.
Alternatively, to list all known faults in the server, log in to the Oracle Solaris OS and issue
the fmadm faulty command, or log in to the Oracle ILOM service processor from the Oracle
ILOM Fault Management Shell and issue the fmadm faulty command. For more information
about how to use the Oracle ILOM Fault Management Shell and supported commands, refer to
the Oracle ILOM User's Guide for System Monitoring and Diagnostics Firmware Release 4.0.x
in the Oracle Integrated Lights Out Manager (ILOM) 4.0 Documentation Library at https://
www.oracle.com/goto/ilom/docs.
Note - The fans of a failed power supply might still be spinning when the system is powered on.
You can remove a power supply while the fans are still spinning.
3. Gain access to the rear of the server where the failed power supply is located.
4. If the cable management arm (CMA) is installed, disconnect both CMA left-side
connectors and move the CMA out of the way.
Refer to “Remove the Cable Management Arm” in Oracle Servers X7-2 and X7-2L Installation
Guide.
Caution - When disconnecting the CMA left-side connectors, use your arm to support the
CMA so that it does not hang down under its own weight and stress the right-side connectors;
otherwise, the CMA might be damaged. You must continue to support the CMA until you have
reconnected both of the left-side connectors.
6. Grasp the power supply handle and push the power supply latch to the left [1].
Caution - Whenever you remove a power supply, you should replace it with another power
supply; otherwise, the server might overheat due to improper airflow.
Related Information
■ “Back Panel Components and Cable Connections” on page 18
■ “Power Supply Status Indicators” on page 31
■ “Install a Power Supply” on page 90
Caution - Always replace a failed power supply with a power supply of the same type (model).
1. Remove the replacement power supply from its packaging and place it on an
antistatic mat.
2. Align the replacement power supply with the empty power supply slot [1].
3. Slide the power supply into the bay until it is fully seated [2].
You will hear an audible click when the power supply fully seats.
5. Verify that the amber Fault-Service Required LED on the replaced power supply
and the Fault-Service Required LEDs on the front and back panels of the server
are not lit.
Note - After you have replaced Power Supply 0, you must reset the Oracle ILOM service
processor (SP) to propagate the key identity properties (KIP) data to the new power supply. For
instructions on resetting the SP, refer to the Oracle Integrated Lights Out Manager (ILOM) 4.0
Configuration and Maintenance Guide Firmware Release 4.0.x at https://www.oracle.com/
goto/ilom/docs. Power Supply 1 does not contain KIP data, and therefore does not require an
SP reset after replacement.
Related Information
This section describes how to service a USB flash drive. The USB flash drive is a customer-
replaceable unit (CRU) that requires you to power off the server. For more information
about CRUs, see “Illustrated Parts Breakdown” on page 19 and “Customer-Replaceable
Units” on page 21.
Caution - These procedures require that you handle components that are sensitive to static
discharge. This sensitivity can cause the component to fail. To avoid damage, ensure that you
follow antistatic practices as described in “Electrostatic Discharge Safety” on page 50.
Caution - Ensure that all power is removed from the server before removing or installing a
flash drive or damage to the drive might occur. You must disconnect all power cables from the
system before performing these procedures.
Related Information
■ “USB Ports” on page 223
The server can be equipped with one internal USB flash drive.
a. Power off the server, and disconnect the power cords from the power
supplies.
See “Powering Down the Server” on page 53.
c. Attach an antistatic wrist strap to your wrist and then to a metal area on the
chassis.
See “Take Antistatic Measures” on page 62.
2. Grasp the USB flash drive and pull it out of the internal USB port.
Related Information
■ “Remove an Internal USB Flash Drive” on page 93
2. Insert the USB flash drive into the internal USB port.
c. Reconnect the power cords to the server power supplies and reconnect the
data cables.
See “Reconnect Data Cables and Power Cords” on page 216.
Related Information
■ “Install an Internal USB Flash Drive” on page 94
This section describes how to service memory modules (DIMMs). DIMMs are customer-
replaceable units (CRUs) that require you to power off the server. For more information
about CRUs, see “Illustrated Parts Breakdown” on page 19 and “Customer-Replaceable
Units” on page 21.
The Oracle Server X7-2 supports a variety of DIMM configurations that can include quad-rank
(QR) and dual-rank (DR) DIMMs.
Caution - These procedures require that you handle components that are sensitive to
electrostatic discharge. This sensitivity can cause the components to fail. To avoid
damage, ensure that you follow antistatic practices as described in “Electrostatic Discharge
Safety” on page 50.
Caution - Ensure that all power is removed from the server before removing or installing
DIMMs, or damage to the DIMMs might occur. You must disconnect all power cables from the
system before performing these procedures.
The following topics and procedures provide information to assist you when replacing a DIMM
or upgrading DIMMs:
■ “DIMM and Processor Physical Layout” on page 98
■ “DIMM Population Scenarios” on page 99
■ “DIMM Population Rules” on page 100
■ “Populating DIMMs for Optimal System Performance” on page 101
■ “Populating DIMMs in Single-Processor Systems for Optimal System
Performance” on page 101
■ “Populating DIMMs in Dual-Processor Systems for Optimal System
Performance” on page 103
■ “DIMM Operating Speeds” on page 104
■ “DIMM Rank Classification Labels” on page 104
■ “Inconsistencies Between DIMM Fault Indicators and the BIOS Isolation of Failed
DIMMs” on page 105
Related Information
The physical layout of the DIMMs and processor(s) is shown in the following figure. When
viewing the server from the front, processor 0 (P0) is on the left.
Each processor, P0 and P1, has twelve DIMM slots organized into six memory channels. Each
channel contains two DIMM slots: a white DIMM slot (channel slot 0) and a black DIMM slot
(channel slot 1).
Note - In single-processor systems, the DIMM slots associated with processor 1 (P1) are
nonfunctional and should not be populated with DIMMs.
Related Information
■ “DIMM Population Scenarios” on page 99
■ “DIMM Population Rules” on page 100
■ “Populating DIMMs for Optimal System Performance” on page 101
■ “DIMM Operating Speeds” on page 104
■ “DIMM Rank Classification Labels” on page 104
■ “Inconsistencies Between DIMM Fault Indicators and the BIOS Isolation of Failed
DIMMs” on page 105
you must replace the failed DIMM with a DIMM of the same size (in gigabytes) and type
(quad-rank or dual-rank). In this scenario, you should not change the DIMM configuration.
■ You have purchased new DIMMs and you want to use them to upgrade the server's memory.
In this scenario, you should adhere to DIMM population rules and follow the recommended
DIMM population order for optimal system performance.
Related Information
The population rules for adding DIMMs to the server are as follows:
■ The server supports 64-GB quad-rank (QR) Load-Reduced DIMMs (LRDIMMs) and 32-
GB dual-rank (DR) and 16-GB DR Registered DIMMs (RDIMMs).
■ Mixing of single-rank and dual-rank DIMMs is not supported.
■ Do not mix DIMM types in the server. For example, do not mix 64-GB LRDIMMs and 16-
GB or 32-GB RDIMMs in the same server. If the server has 64-GB LRDIMMs installed,
you cannot install 16-GB or 32-GB RDIMMs and vice versa.
■ If you are installing a mix of RDIMM sizes (for example, 16-GB and 32-GB), install the
larger size RDIMMs first, then the smaller RDIMMs, until all of the RDIMMs are installed.
■ Each memory channel is composed of a black slot (channel slot 0) and a white slot (channel
slot 1). Populate the black slot first, and then populate the white slot.
Note - The black slot for each channel must be populated first because it is considered
furthest away from the processor.
■ The server supports either one DIMM per channel (1DPC) or two DIMMs per channel
(2DPC).
■ The server operates properly with a minimum of one DIMM installed per processor.
Optimal performance is generally achieved by populating the DIMMs so that the memory is
symmetrical, or balanced. Symmetry is achieved by adhering to the following guidelines:
The following sections provide an example of how to populate the DIMM slots to achieve
optimal system performance.
The following table describes the proper order in which to populate DIMMs in a single-
processor system using the numbered callouts in the above figure, and the DIMM slot labels
(D0 through D11).
The following table describes the proper order in which to install DIMMs in a dual-processor
system using the numbered callouts in the above figure, and the DIMM slot labels (D0 through
D11).
The maximum supported memory speed is 2667 MT/s. However, not all system configurations
will support operation at this speed. The maximum attainable memory speed is limited by the
maximum speed supported by the specific type of processor. All memory installed in the system
operates at the same speed, or frequency.
DIMMs come in a variety of ranks: dual or quad. Each DIMM is shipped with a label
identifying its rank classification. The following table identifies the label corresponding to each
DIMM rank classification:
When a single DIMM is marked as failed by Oracle ILOM (for example, fault.memory.
intel.dimm.training-failed is listed in the service processor Oracle ILOM event log), BIOS
might disable the entire memory channel that contains the failed DIMM, up to two DIMMs. As
a result, none of the memory installed in the disabled channel will be available to the operating
system. However, when the Fault Remind button is pressed, only the fault status indicator
(LED) associated with the failed DIMM lights. The fault LEDs for the other DIMMs in the
memory channel remain off. Therefore, you can correctly identify the failed DIMM using the lit
LED.
When the server Fault Remind button [1] is pressed, an LED located next to the Fault Remind
button lights green to indicate that there is sufficient voltage present in the fault remind circuit
to light any fault LEDs that were lit due to a component failure. If this LED does not light when
you press the Fault Remind button, it is likely that the capacitor powering the fault remind
circuit has lost its charge. This can happen if the Fault Remind button is pressed for several
minutes with fault LEDs lit or if power has been removed from the server for more than 15
minutes.
The following figure shows the location of the Fault Remind button.
a. Power off the server, and disconnect the power cords from the power
supplies.
See “Powering Down the Server” on page 53.
c. Attach an antistatic wrist strap to your wrist and then to a metal area on the
chassis.
See “Take Antistatic Measures” on page 62.
2. Identify and note the location of the failed DIMM by pressing the Fault Remind
button on the motherboard.
■ If the DIMM Fault LED is off, then the DIMM is operating properly.
■ If the DIMM Fault LED is on (amber), then the DIMM is failed and should be replaced [1].
a. Rotate both DIMM slot ejectors outward as far as they will go.
The DIMM is partially ejected from the slot.
4. Replace each failed DIMM with either another DIMM of the same rank size (quad-
rank or dual-rank) or leave the slot empty.
For DIMM replacement instructions, see “Install a DIMM” on page 108.
Related Information
■ “DIMM and Processor Physical Layout” on page 98
■ “DIMM Population Rules” on page 100
■ “Populating DIMMs for Optimal System Performance” on page 101
■ “Install a DIMM” on page 108
Install a DIMM
1. Unpack the replacement DIMM and place it on an antistatic mat.
2. Ensure that the replacement DIMM matches the size, type, and rank of the DIMM
it is replacing.
You must not replace a dual-rank DIMM with a quad-rank DIMM and vice versa. If you violate
this rule, the performance of the server might be adversely affected. For DIMM slot population
rules, see “DIMM Population Rules” on page 100.
3. Install a DIMM.
b. Align the notch in the replacement DIMM with the connector key in the
connector slot.
The notch ensures that the DIMM is oriented correctly.
c. Push the DIMM into the connector slot until the ejector tabs lock the DIMM in
place.
If the DIMM does not easily seat into the connector slot, verify that the notch in the DIMM
is aligned with the connector key in the connector slot. If the notch is not aligned, damage
to the DIMM might occur.
c. Reconnect the power cords to the server power supplies and reconnect the
data cables.
See “Reconnect Data Cables and Power Cords” on page 216.
Note - If you want to move a failed DIMM to a new DIMM slot or re-seat a DIMM for
troubleshooting, you must first manually clear the associated DIMM fault. Otherwise, the
DIMM fault might follow the DIMM to the new slot location or reoccur on the current slot
location, causing a false DIMM fault condition.
Related Information
■ “DIMM and Processor Physical Layout” on page 98
■ “DIMM Population Rules” on page 100
■ “Populating DIMMs for Optimal System Performance” on page 101
■ “Identify and Remove a DIMM” on page 106
This section describes how to service PCIe risers. PCIe risers are customer-replaceable units
(CRUs) that require you to power off the server. For more information about CRUs, see
“Illustrated Parts Breakdown” on page 19 and “Customer-Replaceable Units” on page 21.
PCIe cards in all slots are installed on vertical risers. You must remove the associated riser to
remove and replace a PCIe card. You must remove all three PCIe risers when replacing the
motherboard.
Caution - These procedures require that you handle components that are sensitive to
electrostatic discharge. This sensitivity can cause the components to fail. To avoid
damage, ensure that you follow antistatic practices as described in “Electrostatic Discharge
Safety” on page 50.
Caution - Ensure that all power is removed from the server before removing or installing PCIe
risers, or damage to the PCIe cards installed in the risers might occur. You must disconnect all
power cables from the system before performing these procedures.
The following sections provide information to assist you in servicing PCIe risers:
Related Information
The PCIe riser that installs in PCIe slots 3 and 4 is different than the risers in PCIe slots 1 and
2. The riser for slots 3 and 4 supports an M.2 mezzanine and two PCIe cards: a standard PCIe
card and the internal HBA card. Do not attempt to install the PCIe riser for PCIe slots 3 and 4 in
slots 1 or 2, and vice versa.
Callout Description
1 PCIe riser with installed
PCIe card in slot 1 (This
slot is nonfunctional in
single-processor systems.)
2 PCIe riser with installed
PCIe card in slot 2
3 PCIe riser with M.2
mezzanine and installed
cards (2) in slots 3 and 4
(the internal HBA card is
installed in slot 4 of this
riser.)
Callout Description
Note - This riser is different
from the risers in slots 1 and
2.
Related Information
a. Power off the server and disconnect the power cords from the power
supplies.
See “Powering Down the Server” on page 53.
c. Attach an antistatic wrist strap to your wrist and then to a metal area on the
chassis.
See “Take Antistatic Measures” on page 62.
3. If a PCIe card is installed in the riser, disconnect any external cables from the
card.
4. Lift the green-tabbed latch on the rear of the server chassis next to the
applicable PCIe slot to release the rear bracket on the PCIe card [1].
Note - If the riser does not have a PCIe card installed, then lift the latch to release the PCIe slot
filler panel.
5. Lift the green-tabbed riser release lever on the PCIe riser with one hand and use
your other hand to remove the riser from the motherboard connector [1, 2].
6. If there is a PCIe card installed in the riser, place the riser on an antistatic mat
and note the slot in which the PCIe riser was originally installed; otherwise, set
the PCIe riser aside.
Related Information
■ “Install a PCIe Riser Into PCIe Slot 1 or 2” on page 114
■ “Install a PCIe Card in PCIe Slot 1 or 2” on page 123
Note - The PCIe riser in slots 3 and 4 is different than the PCIe risers in slots 1 and 2. Do not
attempt to install a PCIe riser from slot 1 or 2 into PCIe slots 3 and 4 and vice versa.
1. Determine into which slot you will install the PCIe riser.
2. Retrieve the PCIe riser and any PCIe cards attached to it.
3. Raise the green-tabbed release lever on the PCIe riser to the open (up) position
[1].
4. Gently press the riser into the motherboard connector until it is seated, and
then press the green-tabbed release lever on the PCIe riser to the closed (down)
position [1, 2].
5. Close the green-tabbed latch on the rear of the server chassis next to the
applicable PCIe slot to secure the rear bracket on the PCIe card to the server
chassis [2].
Note - If the riser does not have a PCIe card installed, install a PCIe slot filler panel and close
the green-tabbed latch to secure the filler panel.
6. If there were any external cables connected to the PCIe card, reconnect them.
c. Reconnect the power cords to the server power supplies and reconnect the
data cables.
See “Reconnect Data Cables and Power Cords” on page 216.
Related Information
■ “Remove a PCIe Riser From PCIe Slot 1 or 2” on page 113
■ “Remove a PCIe Card From PCIe Slot 1 or 2” on page 122
Note - This PCIe riser is actually installed in PCIe slot 3, but it supports an M.2 mezzanine and
up to two PCIe cards. The upper slot, referred to as slot 3, can be used for any supported PCIe
card, and, therefore, is optionally populated. The lower slot, referred to as slot 4, is dedicated
to the internal HBA card, and, therefore is always populated. The internal HBA card is a field
replaceable unit (FRU). For instructions for servicing the internal HBA card, see “Servicing the
Internal HBA Card and HBA Super Capacitor (FRU)” on page 169.
a. Power off the server and disconnect the power cords from the power
supplies.
See “Powering Down the Server” on page 53
c. Attach an antistatic wrist strap to your wrist and then to a metal area on the
chassis.
See “Take Antistatic Measures” on page 62.
2. If there is a PCIe card installed in PCIe slot 3, disconnect any external or internal
cables.
Note - Do not disconnect the SAS cables from the internal host bus adapter card in slot 4 until
after you have removed the riser from the server.
3. Open the green-tabbed latch located on the rear of the server chassis next to
PCIe slot 3 to release the rear bracket on the PCIe card [1].
Note - If the riser does not have a PCIe card installed in slot 3, then lift the latch to release the
PCIe slot 3 filler panel.
4. To release the riser from the motherboard connector, lift the green-tabbed
release lever on the PCIe riser to the open position [1].
5. Grasp the riser with both hands and remove it from the server [2].
6. Disconnect the M.2 SATA cable between the PCIe riser and motherboard SATA
connector.
7. Disconnect the SAS cables from the internal HBA card installed in PCIe slot 4.
8. Disconnect the super capacitor cable from the internal HBA card in slot 4.
Related Information
■ “Install the PCIe Riser Into PCIe Slots 3 and 4” on page 118
■ “Install a PCIe Card in PCIe Slot 3” on page 125
Note - The PCIe riser in slots 3 and 4 is different than the PCIe risers in slots 1 and 2. Do not
attempt to install a PCIe riser from slot 1 or 2 into PCIe slots 3 and 4 and vice versa.
1. Retrieve the PCIe riser and any PCIe cards attached to it.
2. Reconnect the SAS cables and the super capacitor cable to the internal HBA
card in slot 4.
To ensure SAS cables are properly connected to the internal HBA card, see “Install the Internal
HBA Cables” on page 182.
3. Reconnect the M.2 SATA cable between the PCIe riser and the motherboard
SATA connector.
4. Raise the green-tabbed release lever on the PCIe riser to the open (up) position,
and then gently press the riser into the motherboard connector until it is seated
[1].
5. Ensure that the rear bracket on the internal HBA card in PCIe slot 4 is connected
to the slot in the server chassis side wall.
If the bracket is not connected, remove the riser and reposition it so that the rear bracket
connects to the side wall, and then gently press the riser into the motherboard connector.
6. Press the green-tabbed release lever on the PCIe riser to the closed (down)
position [2].
7. To secure the rear bracket on the PCIe card to the server, close the green-tabbed
latch on the rear of the server chassis [2].
Note - If the riser does not have a PCIe card installed in slot 3, install a PCIe slot filler panel
and close the green-tabbed latch to secure the PCIe slot filler panel.
8. If there is a PCIe card in PCIe slot 3, reconnect any external or internal cables.
c. Reconnect the power cord to the server power supply and the data cables.
See “Reconnect Data Cables and Power Cords” on page 216.
10. Use Oracle ILOM to clear the server PCIe riser fault.
If the PCIe riser fault message in Oracle ILOM is not cleared under Open Problems, you
must manually clear the fault in Oracle ILOM. For instructions for manually clearing a
PCIe riser fault, see the procedure "Clear Faults for Undetected Replaced or Repaired
Hardware Components" in the Oracle ILOM User's Guide for System Monitoring and
Diagnostics Firmware Release 4.0.x in the Oracle Integrated Lights Out Manager (ILOM) 4.0
Documentation Library at https://www.oracle.com/goto/ilom/docs.
Related Information
■ “Remove the PCIe Riser From PCIe Slots 3 and 4” on page 116
■ “Remove a PCIe Card From PCIe Slot 3” on page 124
This section describes how to service PCIe cards. PCIe cards are customer-replaceable units
(CRUs) that require you to power off the server. For more information about CRUs, see
“Illustrated Parts Breakdown” on page 19 and “Customer-Replaceable Units” on page 21.
Caution - These procedures require that you handle components that are sensitive to
electrostatic discharge. This sensitivity can cause the components to fail. To avoid
damage, ensure that you follow antistatic practices as described in “Electrostatic Discharge
Safety” on page 50.
Caution - Ensure that all power is removed from the server before removing or installing
PCIe cards. You must disconnect all power cables from the system before performing these
procedures.
Note - For a complete list of supported PCIe cards, refer to the Oracle Server X7-2 Product
Notes at https://www.oracle.com/goto/x7-2/docs.
Related Information
There are three external PCIe slots and one internal PCIe slot available in the Oracle Server
X7-2. The external slots support optional, standard PCIe cards and are numbered 1, 2, and 3
from left to right when you view the server from the rear. The internal slot, which installs on the
riser in PCIe slots 3 and 4, supports a required internal SAS controller HBA card. For a view
of the back panel that shows PCIe slot numbering, see “Back Panel Components and Cable
Connections” on page 18.
Note - All of the PCIe slots comply with the PCI Express 3.0 specification and can
accommodate 25 Watt PCIe cards.
The following table lists the characteristics and requirements of the PCIe slots.
Slot Supported PCIe Card Supported PCIe Specifications Slot Connector Width/PCI Express
Number Types Lanes
1 Low-profile cards only PCIe 1.0, PCIe 2.0, PCIe 3.0 x16 mechanical/x16 electrical
2 Low-profile cards only PCIe 1.0, PCIe 2.0, PCIe 3.0 x16 mechanical/x16 electrical
3 and 4 Low-profile cards only PCIe 1.0, PCIe 2.0, PCIe 3.0 x8 mechanical/x8 electrical
Related Information
■ “Back Panel Components and Cable Connections” on page 18
a. Hold the riser in one hand and use your other hand to carefully pull the PCIe
card connector out of the riser.
b. Disconnect the rear bracket that is attached to the PCIe card from the rear of
the PCIe riser.
Caution - Whenever you remove a PCIe card, you should replace it with another PCIe card
or a PCIe filler panel. Installing PCIe filler panels in vacant PCIe slots helps reduce the level
of electromagnetic interference (EMI) emitted by the server. See “Remove and Install Filler
Panels” on page 211.
2. Insert the rear bracket that is attached to the PCIe card into the PCIe riser.
3. Hold the riser in one hand and use your other hand to carefully insert the PCIe
card connector into the riser.
a. Hold the riser in one hand and use your other hand to carefully remove the
PCIe card connector from the riser.
b. Disconnect the rear bracket attached to the PCIe card from the rear of the
PCIe riser.
Caution - Whenever you remove a PCIe card, you should replace it with another PCIe card
or a PCIe filler panel. Installing PCIe filler panels in vacant PCIe slots helps reduce the level
of electromagnetic interference (EMI) emitted by the server. See “Remove and Install Filler
Panels” on page 211.
2. Insert the rear bracket that is attached to the PCIe card into the PCIe riser.
3. Hold the riser in one hand and use your other hand to carefully insert the PCIe
card connector into the riser.
This section describes how to service M.2 flash solid-state drives (SSDs). M.2 flash SSDs
are customer-replaceable units (CRUs) that require you to power off the server. For more
information about CRUs, see “Illustrated Parts Breakdown” on page 19 and “Customer-
Replaceable Units” on page 21.
Caution - These procedures require that you handle components that are sensitive to
electrostatic discharge. This sensitivity can cause the component to fail. To avoid damage,
ensure that you follow antistatic practices as described in “Electrostatic Discharge
Safety” on page 50.
Caution - Ensure that all power is removed from the server before removing or installing
PCIe cards. You must disconnect all power cables from the system before performing these
procedures.
Related Information
2. Remove any PCIe card in PCIe slot 3 and the internal HBA in PCIe slot 4.
See “Remove a PCIe Card From PCIe Slot 3” on page 124 and “Remove the Internal HBA
Card and HBA Super Capacitor” on page 170.
Note - You do not need to remove the data cables from the PCIe cards when servicing the M.2
mezzanine. Extract the PCIe cards (with cables attached) from the PCIe slots and set them
aside.
3. Using a T10 Torx screwdriver, remove the screws that secure the M.2 mezzanine
to the PCIe riser.
4. Lift and remove the M.2 mezzanine from the PCIe riser connector.
Place the M.2 mezzanine on an antistatic mat. If required, perform the procedures for removing
the M.2 flash SSDs from the mezzanine. See “Remove an M.2 Flash SSD” on page 130.
Related Information
2. Align the M.2 mezzanine with the connector and screw holes on the PCIe riser
and then insert the mezzanine into the connector.
3. Using a T10 Torx screwdriver, install the screws that secure the M.2 mezzanine
to the PCIe riser.
4. Install the internal HBA card in PCIe slot 4 and any PCIe card in PCIe slot 3.
See “Install the Internal HBA Card and HBA Super Capacitor” on page 173 and “Install a
PCIe Card in PCIe Slot 3” on page 125.
Related Information
1. Perform the steps to remove the M.2 mezzanine containing the M.2 flash SSDs
from PCIe riser.
See “Remove an M.2 Mezzanine” on page 127. Place the M.2 mezzanine on an antistatic
mat.
2. Using your fingers, push the plastic retainer clip through the M.2 mezzanine to
release the M.2 flash SSD from the mezzanine. [1].
3. Remove the plastic retainer clip from the M.2 flash SSD.
a. Lift up on the end of the M.2 flash SSD where the plastic retainer clip was
removed by one-half to one inch.
b. Gently slide the M.2 flash SSD card rearward and out of the connector to
disengage the SSD contacts from the mezzanine socket.
Place the M.2 flash SSD on an antistatic mat.
5. Repeat Step 2 through Step 4 to remove the second M.2 flash SSD from the
opposite side of the M.2 mezzanine.
Related Information
■ “Install an M.2 Flash SSD” on page 131
Note - The M.2 mezzanine contains two M.2 flash SSD sockets (labeled SSD0 and SSD1). If
you are installing a single M.2 flash SSD on to the mezzanine, install the M.2 flash SSD into
socket SSD0.
a. Align and then insert the plastic retainer clip into the slot on the M.2 flash
SSD.
b. Hold the M.2 flash SSD so that the end of the card containing the plastic
retainer clip is approximately one-half to one inch above the M.2 mezzanine
and the other end is adjacent to the riser SSD socket [1].
c. Gently slide the M.2 flash SSD forward and into the connector to engage the
flash SSD contacts with the M.2 mezzanine socket [2].
d. Using your fingers, push down on the end of the card containing the plastic
retainer clip until the M.2 flash SSD snaps into place on the mezzanine [2].
You will hear an audible click when the M.2 flash SSD is secured to the mezzanine.
3. Repeat Step 2 to install the second M.2 flash SSD on to the opposite side of the
M.2 mezzanine.
4. Perform the steps to install the M.2 mezzanine with the replacement M.2 flash
SSDs on to the PCIe riser.
See “Install an M.2 Mezzanine” on page 129.
Related Information
■ “Remove an M.2 Flash SSD” on page 130
This section describes how to service the system battery. The system battery is a customer-
replaceable unit (CRU) that requires you to power off the server. For more information
about CRUs, see “Illustrated Parts Breakdown” on page 19 and “Customer-Replaceable
Units” on page 21.
The real-time clock (RTC) battery maintains system time when the server is powered off and
a time server is unavailable. If the server fails to maintain the proper time when the system is
powered off and not connected to a network, replace the battery.
Caution - These procedures require that you handle components that are sensitive to
electrostatic discharge. This sensitivity can cause the components to fail. To avoid
damage, ensure that you follow antistatic practices as described in “Electrostatic Discharge
Safety” on page 50.
Caution - Ensure that all power is removed from the server before removing or installing
the battery. You must disconnect the power cables from the system before performing this
procedure.
Related Information
■ “Extend the Server to the Maintenance Position” on page 59
■ “Remove the Server Top Cover” on page 63
a. Power off the server and disconnect the power cords from the power
supplies.
See “Powering Down the Server” on page 53.
c. Attach an antistatic wrist strap to your wrist and then to a metal area on the
chassis.
See “Take Antistatic Measures” on page 62.
2. To dislodge the battery from its retainer, use your finger to gently push the top
edge of the battery away from the retainer.
c. Reconnect the power cords to the server power supplies and reconnect the
data cables.
See “Reconnect Data Cables and Power Cords” on page 216.
Note - If the service processor is configured to synchronize with a network time server using
the Network Time Protocol (NTP), the Oracle ILOM SP clock will be reset as soon as the
server is powered on and connected to the network; otherwise, proceed to the next step.
4. If the service processor is not configured to use NTP, do one of the following:
■ Reset the Oracle ILOM clock using the Oracle ILOM CLI or the web interface.
Refer to the Oracle Integrated Lights Out Manager (ILOM) 4.0 Documentation Library at
https://www.oracle.com/goto/ilom/docs.
■ Use the BIOS Setup Utility to reprogram the host clock.
Refer to the Oracle X7 Series Servers Administration Guide at https://www.oracle.com/
goto/x86admindiag/docs.
The following section describes how to service processors. Processors are field-replaceable
units (FRUs). For more information about FRUs, see “Illustrated Parts Breakdown” on page 19
and “Field-Replaceable Units” on page 22.
Caution - Processors must be removed and replaced only by authorized Oracle Service
personnel.
Caution - Ensure that all power is removed from the server before removing or installing a
processor. You must disconnect the power cables from the system before performing these
procedures.
Caution - These procedures require that you handle components that are sensitive to
electrostatic discharge. This sensitivity can cause the component to fail. To avoid damage,
ensure that you follow electrostatic discharge safety measures and antistatic practices. See
“Electrostatic Discharge Safety” on page 50.
Note - On single-processor systems, processor socket 1 (P1) is shipped without a heatsink and
processor filler cover. To protect the delicate processor socket pins, do not remove the processor
cover that was installed on the motherboard.
Related Information
■ “Disconnect Cables From the Server” on page 59
■ “Take Antistatic Measures” on page 62
■ “Remove the Server From the Rack” on page 61
■ “Remove the Server Top Cover” on page 63
Caution - Be careful not to touch the processor socket pins. The processor socket pins are very
fragile. A light touch can bend the processor socket pins beyond repair.
Caution - Whenever you remove a processor, replace it with another processor and reinstall the
processor heatsink; otherwise, the server might overheat due to improper airflow. See “Install a
Processor” on page 144.
a. Power off the server and disconnect the power cords from the power
supplies.
See “Powering Down the Server” on page 53.
c. Attach an antistatic wrist strap to your wrist, and then to a metal area on the
chassis.
See “Take Antistatic Measures” on page 62.
e. Lift the air baffles up and out of the server and set them aside.
2. Identify the location of the failed processor by pressing the Fault Remind button
on the motherboard I/O card.
Note - When you press the Fault Remind button, an LED located next to the Fault Remind
button lights green, indicates that there is sufficient voltage in the fault remind circuit to light
any fault LEDs that were lit due to a failure. If this LED fails to light when you press the Fault
Remind button, it is likely that the capacitor powering the fault remind circuit lost its charge.
This can happen if you press the Fault Remind button for a long time with fault LEDs lit, or if
power was removed from the server for more than 15 minutes.
The processor fault LED for the failed processor lights. The processor fault LEDs are located
next to the processors. See “Motherboard Status Indicators” on page 33.
Callout Description
1 Fault Remind button
2 Fault Remind LED
3 Processor 0 fault LED
4 Processor 1 fault LED
3. Using a Torx T30 screwdriver, loosen the four captive nuts that secure the
processor-heatsink module to the socket: fully loosen nut 4, then 3, then 2, then
1 [1].
The blade of the screwdriver goes into the slot between the heatsink and processor carrier,
not between the processor and processor carrier.
c. Using a rocking motion, gently pry the corner of the processor carrier away
from the heatsink.
d. Remove the processor carrier (with processor still attached) from the
heatsink by prying or pinching the plastic latch tabs that attach the
processor to the heatsink.
Caution - A thin layer of thermal grease separates the heatsink and the processor. This grease
acts as an adhesive. Do not allow the thermal grease to contaminate the work space or other
components.
6. If you plan on reusing either the heatsink or processor, use an alcohol pad to
clean the thermal grease on the underside of the heatsink and on the top of the
processor. If reusing a processor, do not remove it from the processor carrier.
Caution - Failure to clean thermal grease from the heatsink could result in the accidental
contamination of the processor socket or other components. Also, be careful not to get the
grease on your fingers, as this could contaminate components.
Related Information
Install a Processor
Caution - Be careful not to touch the processor socket pins. The processor socket pins are very
fragile. A light touch can bend the processor socket pins beyond repair.
1. Attach an antistatic wrist strap to your wrist, and then to a metal area on the
chassis.
See “Take Antistatic Measures” on page 62.
2. Ensure that the replacement processor is identical to the failed processor that
you removed.
For a description of the processors that are supported by the server, see “Product
Description” on page 15.
3. Use the syringe supplied with the new or replacement processor [1] to apply 0.3
cc of thermal interface material (TIM) in an "X" pattern to the processor contact
area of the heatsink [2].
Note - Do not distribute the TIM; the pressure of the heatsink will do so for you when you
install the heatsink.
a. Open the box that contains the new processor but do not remove it from its
packaging tray.
b. Align the pin 1 indicators between the heatsink and processor carrier in
the packaging tray [1], and place the heatsink (thermal side down) onto the
processor carrier until it snaps in place and lies flat.
Note - The processor carrier has latching posts at each corner: two that insert into heatsink holes
and two that attach to the edge of the heatsink.
Callout Description
1 Pin 1 indicator
Callout Description
1 Pin 1 indicator
f. Ensure that the processor-heatsink module lies evenly on the bolster plate
and that the captive screws align with the threaded socket posts [1].
g. Using a 12.0 in-lbs (inch-pounds) torque driver with a Torx T30 bit, tighten
the processor-heatsink module to the socket. First, fully tighten captive nuts
1 and 2. Then fully tighten nuts 3 and 4 [2].
As you tighten nuts 3 and 4, some resistance occurs as the bolster leaf spring rises and
comes in contact with the heatsink.
Caution - Using an incorrect torque setting or driver bit can damage a processor-heatsink
module.
d. Reconnect the power cords to the power supplies, and power on the server.
See “Reconnect Data Cables and Power Cords” on page 216 and “Power On the
Server” on page 216.
a. To show server faults, log in to the server as root using the Oracle ILOM CLI,
and type the following command to list all known faults on the server:
-> show /SP/faultmgmt
The server lists all known faults, for example:
Alternatively, to list all known faults in the server, log into the Oracle Solaris OS and
issue the fmadm faulty command or log in to the Oracle ILOM service processor from
the Oracle ILOM Fault Management Shell and issue the fmadm faulty command. For
more information about how to use the Oracle ILOM Fault Management Shell and
supported commands, see the Oracle ILOM User's Guide for System Monitoring and
Diagnostics Firmware Release 4.0.x in the Oracle Integrated Lights Out Manager (ILOM)
4.0 Documentation Library at https://www.oracle.com/goto/ilom/docs.
b. To clear the fault identified in Step 6a, type the following command:
-> set /SYS/MB/P0 clear_fault_action=true
For example:
Alternatively, to clear all known faults in the server, log in to the Oracle Solaris OS
and issue the fmadm repair command or log in to the Oracle ILOM service processor
from the Oracle ILOM Fault Management Shell and issue the fmadm repair command.
For more information about how to use the Oracle ILOM Fault Management Shell and
supported commands, see the Oracle ILOM User's Guide for System Monitoring and
Diagnostics Firmware Release 4.0.x in the Oracle Integrated Lights Out Manager (ILOM)
4.0 Documentation Library at https://www.oracle.com/goto/ilom/docs.
Related Information
■ “Identify and Remove a Processor” on page 138
The following section describes how to service the disk backplane. The disk backplane is
a field-replaceable unit (FRU). For more information about FRUs, see “Illustrated Parts
Breakdown” on page 19 and “Field-Replaceable Units” on page 22.
Caution - The disk backplane should be removed and replaced only by authorized Oracle
Service personnel.
Caution - Ensure that all power is removed from the server before removing or installing the
disk backplane. You must disconnect the power cables before performing this procedure.
Caution - These procedures require that you handle components that are sensitive to
electrostatic discharge. This sensitivity can cause the component to fail. To avoid damage,
ensure that you follow electrostatic discharge safety measures and antistatic practices. See
“Electrostatic Discharge Safety” on page 50.
Related Information
■ “Disconnect Cables From the Server” on page 59
■ “Take Antistatic Measures” on page 62
■ “Extend the Server to the Maintenance Position” on page 59
a. Power off the server and disconnect the power cords from the power
supplies.
See “Powering Down the Server” on page 53.
c. Attach an antistatic wrist strap to your wrist, and then to a metal area on the
chassis.
See “Take Antistatic Measures” on page 62.
e. Lift up the super capacitor to release the capacitor from the reclosable
fasteners that secure it to the chassis.
Set the super capacitor aside (leaving the super capacitor cable attached) until you are
ready to install the replacement storage drive backplane.
2. Pull all storage drives out far enough to disengage them from the disk
backplane.
See “Remove a Storage Drive” on page 67.
Note - It is not necessary to completely remove the storage drives from the server; simply
pull them out far enough to disengage them from the disk backplane. If you do remove the
storage drives from the server, record their locations so that you can reinstall them in the same
locations.
3. Disconnect the SAS cables or the NVMe cables (if present) from the disk
backplane [1].
4. Disconnect the disk backplane data cable and the temperature sensor cable
from the disk backplane [2].
5. Disconnect the disk backplane power cable from the disk backplane [3].
6. Using a Torx T15 screwdriver, loosen the three captive screws that secure the
disk backplane to the chassis [4].
7. Lift the backplane up and tilt it toward the rear of the server to free it from the
hooks and right-side metal bracket, and lift it out of the server [5].
Related Information
1. Install the disk backplane into the server so that it engages the three metal
hooks and also sits behind the metal tab located on the right-side chassis wall
[1].
2. Using a Torx T15 screwdriver, tighten the three storage drive backplane captive
screws clockwise until the disk backplane is secure [2].
3. Reconnect the disk backplane power cable to the disk backplane [3].
4. Reconnect the disk backplane data cable and temperature sensor cable to the
disk backplane [4].
5. Reconnect the SAS cables or the NVMe cables (if present) to the disk backplane
[5].
c. Reconnect the power cords to the power supplies, and power on the server.
See “Reconnect Data Cables and Power Cords” on page 216 and “Power On the
Server” on page 216.
Note - IMPORTANT: When the disk backplane is replaced, the key identity properties (KIP)
of the backplane is programmed by Oracle ILOM to contain the same KIP as the other quorum
member components. If you have removed other quorum member components, you might
need to manually program the product serial number (PSN) into the new backplane. For more
information, refer to “FRU Key Identity Properties (KIP) Automated Update” on page 51.
Related Information
■ “Remove the Disk Backplane” on page 151
The following section describes how to service the front indicator module. The front indicator
module is a field-replaceable unit (FRU). For more information about FRUs, see “Illustrated
Parts Breakdown” on page 19 and “Field-Replaceable Units” on page 22.
Caution - The front indicator module should be removed and replaced only by authorized
Oracle Service personnel.
Caution - Ensure that all power is removed from the server before removing or installing
the front indicator module. You must disconnect the power cables before performing this
procedure.
Caution - These procedures require that you handle components that are sensitive to
electrostatic discharge. This sensitivity can cause the component to fail. To avoid damage,
ensure that you follow electrostatic discharge safety measures and antistatic practices. See
“Electrostatic Discharge Safety” on page 50.
Follow these procedures to remove and install the front indicator module (FIM).
■ “Remove the Front LED Indicator Module” on page 157
■ “Install the Front LED Indicator Module” on page 159
Related Information
■ “Disconnect Cables From the Server” on page 59
■ “Remove the Server From the Rack” on page 61
■ “Take Antistatic Measures” on page 62
a. Power off the server and disconnect the power cords from the power
supplies.
See “Powering Down the Server” on page 53.
c. Attach an antistatic wrist strap to your wrist, and then to a metal area on the
chassis.
See “Take Antistatic Measures” on page 62.
2. Using a Philips screwdriver, remove the two screws that secure the front
indicator module (FIM) assembly to the server chassis [1].
3. Carefully slide the FIM assembly toward the front of the server to remove it from
the chassis [2].
4. Using a Phillips screwdriver, remove the two screws that secure the plastic
temperature sensor housing to the FIM assembly, and then detach the housing
from the FIM assembly [2].
Note - You do not need to remove the temperature sensor from the housing.
5. Disconnect the FIM cable from the FIM assembly and set the FIM assembly aside
[3].
Related Information
1. Attach an antistatic wrist strap to your wrist, and then to a metal area on the
chassis.
See “Take Antistatic Measures” on page 62.
3. If not installed, install the FIM cable through the plastic temperature sensor
housing [1].
4. Connect the FIM cable to the replacement FIM assembly [1, 2].
5. Using a Phillips screwdriver, tighten the two screws to secure the temperature
sensor housing to the FIM assembly [2].
6. Carefully insert the FIM assembly into the front panel of the server chassis [3].
7. Install and tighten the two Phillips screws to secure the FIM assembly to the
server chassis [3].
b. Reconnect the power cords to the power supplies, and power on the server.
See “Reconnect Data Cables and Power Cords” on page 216 and “Power On the
Server” on page 216.
Related Information
■ “Remove the Front LED Indicator Module” on page 157
The following section describes how to service the temperature sensor. The temperature sensor
is a field-replaceable unit (FRU). For more information about FRUs, see “Illustrated Parts
Breakdown” on page 19 and “Field-Replaceable Units” on page 22.
Caution - The temperature sensor should be removed and replaced only by authorized Oracle
Service personnel.
Caution - Ensure that all power is removed from the server before removing or installing the
temperature sensor. You must disconnect the power cables before performing this procedure.
Caution - These procedures require that you handle components that are sensitive to
electrostatic discharge. This sensitivity can cause the component to fail. To avoid damage,
ensure that you follow electrostatic discharge safety measures and antistatic practices. See
“Electrostatic Discharge Safety” on page 50.
Related Information
■ “Disconnect Cables From the Server” on page 59
■ “Remove the Server From the Rack” on page 61
■ “Take Antistatic Measures” on page 62
a. Power off the server and disconnect the power cords from the power
supplies.
See “Powering Down the Server” on page 53.
c. Attach an antistatic wrist strap to your wrist, and then to a metal area on the
chassis.
See “Take Antistatic Measures” on page 62.
3. Using a Phillips screwdriver, remove the two screws that secure the front
indicator module (FIM) assembly to the server chassis [1].
4. Carefully slide the FIM assembly toward the front of the server to remove it from
the chassis [2].
5. Remove the temperature sensor from the plastic housing by pulling the sensor
from its seated location. Then remove the sensor cable by pulling it through the
slit in the housing [2, 3].
6. Remove the temperature sensor and cable by carefully pulling the sensor cable
rearward and through the left-front chassis sidewall. Then lift the temperature
sensor from the chassis [4].
Related Information
1. Install the temperature sensor by carefully inserting the sensor-end of the cable
through the rear opening directly under the left side of the disk backplane. Then
push/pull the sensor cable through the left-front chassis sidewall [1].
2. Install the temperature sensor into the plastic housing by inserting the cable
through the slit in the housing. Then ensure that the temperature sensor is
properly seated into the housing [2, 3].
3. Carefully insert the FIM assembly into the front panel of the server chassis [3].
4. Install and tighten the two Phillips screws to secure the FIM assembly to the
server chassis [4].
c. Reconnect the power cords to the power supplies, and power on the server.
See “Reconnect Data Cables and Power Cords” on page 216 and “Power On the
Server” on page 216.
Related Information
■ “Remove the Temperature Sensor” on page 163
The following section describes how to service and install the Oracle Storage 12 Gb SAS PCIe
RAID HBA, Internal card and HBA super capacitor. The internal HBA card and HBA super
capacitor are field-replaceable units (FRUs). For more information about FRUs, see “Illustrated
Parts Breakdown” on page 19 and “Field-Replaceable Units” on page 22.
For more information about the internal HBA card, refer to the Oracle Storage 12 Gb SAS PCIe
RAID HBA Internal: 16 Port and 2 GB Memory Installation Guide For HBA Model 7116970 at
https://docs.oracle.com/cd/E87591_01/index.html.
Caution - The internal HBA card and HBA super capacitor should be removed and replaced
only by authorized Oracle Service personnel.
Caution - Ensure that all power is removed from the server before removing or installing the
internal HBA card and super capacitor. You must disconnect all power cables from the system
before performing these procedures.
Caution - These procedures require that you handle components that are sensitive to
electrostatic discharge. This sensitivity can cause the component to fail. To avoid damage,
ensure that you follow electrostatic discharge safety measures and antistatic practices. See
“Electrostatic Discharge Safety” on page 50.
■ “Remove the Internal HBA Card and HBA Super Capacitor” on page 170
■ “Install the Internal HBA Card and HBA Super Capacitor” on page 173
Related Information
■ “Disconnect Cables From the Server” on page 59
Servicing the Internal HBA Card and HBA Super Capacitor (FRU) 169
Remove the Internal HBA Card and HBA Super Capacitor
2. Remove the internal host bus adapter card from the riser.
a. Hold the riser in one hand and use your other hand to carefully remove the
card from slot 4 of the riser.
b. Disconnect the rear bracket attached to the PCIe card from the rear of the
PCIe riser.
3. Disconnect the SAS cables and the super capacitor cable from the internal HBA
card and place the card on an antistatic mat.
4. If you are replacing the internal HBA card, use a No. 2 Philips screwdriver to
remove the special fitted bracket from the HBA card.
Servicing the Internal HBA Card and HBA Super Capacitor (FRU) 171
Remove the Internal HBA Card and HBA Super Capacitor
You will need to install the special fitted bracket on the replacement HBA card. Set aside the
bracket and screws until you are ready to install the replacement HBA card.
5. Lift the super capacitor up to release the reclosable fasteners that secure it to
the server's chassis [1, 2].
Note - If you are removing and replacing only the internal HBA card, you do not need to
remove the HBA super capacitor. You can disconnect the HBA super capacitor cable from the
internal HBA card and then remove the internal HBA card from the system.
Note - (Optional) Disconnect the data cable from the disk backplane to allow easy access to the
super capacitor.
6. Disconnect the super capacitor cable from the super capacitor and place the
super capacitor on an antistatic mat [2].
7. Carefully remove the SAS cables and super capacitor cable from the server by
lifting them from the left-side cable trough.
See “Remove the Internal HBA Cables” on page 179.
1. Unpack the replacement host bus adapter (HBA) card, the SAS cables, super
capacitor, and the super capacitor cable, and retrieve the PCIe riser for slot 3.
Servicing the Internal HBA Card and HBA Super Capacitor (FRU) 173
Install the Internal HBA Card and HBA Super Capacitor
2. Using a No. 2 Philips screwdriver, remove the standard HBA bracket that
shipped with the replacement HBA card.
3. Install the special fitted bracket that was removed in Step 4 in “Remove the
Internal HBA Card and HBA Super Capacitor” on page 170.
4. Carefully guide the SAS cables and super capacitor cable that connect to the
disk backplane and the super capacitor through the left-side cable trough.
Note - If you did not remove the HBA super capacitor when removing the internal HBA card,
reconnect the HBA super capacitor cable to the internal HBA card.
b. Connect the super capacitor cable to the super capacitor [1, 2].
c. Press the super capacitor into the server's chassis so that it is secured to
the existing reclosable fastener [2].
Note - If disconnected during the removal procedure, reconnect the data cable to the disk
backplane.
6. Connect the SAS cables and the super capacitor cable to the internal HBA card.
Servicing the Internal HBA Card and HBA Super Capacitor (FRU) 175
Install the Internal HBA Card and HBA Super Capacitor
To ensure SAS cables are properly connected to the internal HBA card, see “Install the Internal
HBA Cables” on page 182.
7. Insert the internal HBA card connector into the bottom connector on the riser for
PCIe slot 3 and 4. While inserting the HBA, ensure that rear bracket on the HBA
card fits into the connector slot on the PCIe riser.
Servicing the Internal HBA Card and HBA Super Capacitor (FRU) 177
178 Oracle Server X7-2 Service Manual • August 2019
Servicing the Internal HBA Cables (FRU)
The following section describes how to service the internal HBA cables. The HBA SAS cables
and super capacitor cable are a field-replaceable units (FRUs). For more information about
FRUs, see “Illustrated Parts Breakdown” on page 19 and “Field-Replaceable Units” on page 22.
Caution - The HBA SAS cable assembly should be removed and replaced only by authorized
Oracle Service personnel.
Caution - Ensure that all power is removed from the server before removing or installing
the HBA SAS cable assembly. You must disconnect the power cables before performing this
procedure.
Caution - These procedures require that you handle components that are sensitive to
electrostatic discharge. This sensitivity can cause the component to fail. To avoid damage,
ensure that you follow electrostatic discharge safety measures and antistatic practices. See
“Electrostatic Discharge Safety” on page 50.
Related Information
■ “Extend the Server to the Maintenance Position” on page 59
■ “Take Antistatic Measures” on page 62
■ “Remove the Server Top Cover” on page 63
■ “Servicing the Internal HBA Card and HBA Super Capacitor (FRU)” on page 169
a. Power off the server and disconnect the power cords from the power
supplies.
See “Powering Down the Server” on page 53.
c. Attach an antistatic wrist strap to your wrist, and then to a metal area on the
chassis.
See “Take Antistatic Measures” on page 62.
2. Disconnect both SAS cables from the disk backplane by pressing the latch on
the cable connector and then pulling out the connector [1, 2].
3. Disconnect the SAS cables and the super capacitor cable from the internal host
bus adapter (HBA) card.
b. Press the SAS cable connector latch and then pull out the connector [3].
c. Grasp the super capacitor cable connector and pull it out [3].
4. Disconnect the super capacitor cable from the super capacitor [4].
Note - You might need to disconnect the data cable from the disk backplane to ease access to
the super capacitor.
5. Carefully remove the SAS cables and the super capacitor cable from the server.
Related Information
■ “Remove the Internal HBA Card and HBA Super Capacitor” on page 170
■ “Install the Internal HBA Cables” on page 182
1. Carefully guide SAS cables and the super capacitor cable along the left-side
cable trough.
Note -SAS cable assembly, part number 7117386 is required to connect the internal HBA card
to the disk backplane.
Note - If you disconnected the data cable from the disk backplane during the removal
procedure, reconnect the data cable.
3. Connect the SAS cables and the super capacitor cable to the internal HBA card
[3].
When attaching SAS cables, ensure that you match the numbers on the SAS cables with
the SAS connectors on the disk backplane. Use the following table to ensure proper SAS
connections between the disk backplane and the internal HBA card.
4. Install the SAS cables into the disk backplane [1, 2].
To ensure proper connections, see the SAS cable connections table in Step 3.
5. Install the PCIe riser with the internal HBA card into PCIe slot 3 and 4.
See “Install the PCIe Riser Into PCIe Slots 3 and 4” on page 118.
c. Reconnect the power cords to the power supplies, and power on the server.
See “Reconnect Data Cables and Power Cords” on page 216 and “Power On the
Server” on page 216.
Related Information
■ “Install the Internal HBA Card and HBA Super Capacitor” on page 173
■ “Remove the Internal HBA Cables” on page 179
The following section describes how to service the NVMe cables. The NVMe cables are
field-replaceable units (FRUs). For more information about FRUs, see “Illustrated Parts
Breakdown” on page 19 and “Field-Replaceable Units” on page 22.
Caution - The NVMe cables should be removed and replaced only by authorized Oracle
Service personnel.
Caution - Ensure that all power is removed from the server before removing or installing the
NVMe cables. You must disconnect the power cables before performing this procedure.
Caution - These procedures require that you handle components that are sensitive to
electrostatic discharge. This sensitivity can cause the component to fail. To avoid damage,
ensure that you follow electrostatic discharge safety measures and antistatic practices. See
“Electrostatic Discharge Safety” on page 50.
Related Information
■ “Extend the Server to the Maintenance Position” on page 59
■ “Take Antistatic Measures” on page 62
■ “Remove the Server Top Cover” on page 63
a. Power off the server and disconnect the power cords from the power
supplies.
See “Powering Down the Server” on page 53.
c. Attach an antistatic wrist strap to your wrist, and then to a metal area on the
chassis.
See “Take Antistatic Measures” on page 62.
a. Using a Torx T15 screwdriver, loosen the four green captive screws that
secure the mid-wall to the server chassis.
b. Lift the mid-wall from the server chassis and set it aside.
4. Disconnect each NVMe cable from the disk backplane by pressing the latch on
the cable connector and then pulling out the connector [3].
5. Disconnect the NVMe cables from the motherboard NVMe connectors [3].
6. Carefully lift the NVMe cables from the center cable trough and remove them
from the server [4].
Related Information
1. Carefully install the NVMe cables through the center cable trough [1].
Note -NVMe cable assembly, part number 7115195 is required to connect the motherboard
NVMe connectors to the disk backplane.
Note - Each NVMe cable contains a matching label that corresponds to connectors on the
motherboard and the disk backplane. For example, the NVMe cable labeled A, plugs into
motherboard NVMe A connector and the disk backplane NVMe A connector.
b. Using a Torx T15 screwdriver, tighten the four green captive screws to
secure the mid-wall to the server chassis.
c. Reconnect the power cords to the power supplies, and power on the server.
See “Reconnect Data Cables and Power Cords” on page 216 and “Power On the
Server” on page 216.
Related Information
■ “Remove the NVMe Cable Assembly” on page 185
The following section describes how to service the power, front indicator module (FIM),
temperature sensor, and disk backplane data cables. These cables are field-replaceable units
(FRUs). For more information about FRUs, see “Illustrated Parts Breakdown” on page 19 and
“Field-Replaceable Units” on page 22.
Caution - The power, FIM, temperature sensor, and disk backplane data cables should be
removed and replaced only by authorized Oracle Service personnel.
Caution - Ensure that all power is removed from the server before removing or installing these
cables. You must disconnect the power cables before performing this procedure.
Caution - These procedures require that you handle components that are sensitive to
electrostatic discharge. This sensitivity can cause the component to fail. To avoid damage,
ensure that you follow electrostatic discharge safety measures and antistatic practices. See
“Electrostatic Discharge Safety” on page 50.
■ “Remove the Power, FIM, Temperature Sensor, and Disk Backplane Data
Cables” on page 194
■ “Install the Power, FIM, Temperature Sensor, and Disk Backplane Data
Cables” on page 196
Related Information
a. Power off the server and disconnect the power cords from the power
supplies.
See “Powering Down the Server” on page 53.
c. Attach an antistatic wrist strap to your wrist, and then to a metal area on the
chassis.
See “Take Antistatic Measures” on page 62.
b. Disconnect the disk backplane power cable from the disk backplane by
pressing the release latch on the side of the cable connector and pulling out
the connector [2].
b. Disconnect the temperature sensor cable from the disk backplane by pulling
the cable from the connector [3].
c. Remove the temperature sensor and cable from the FIM housing, then pull
the cable and sensor through the left-front chassis sidewall [4].
b. Disconnect the FIM cable from the FIM by pulling the cable from the
connector [5].
c. Eject the FIM cable from the motherboard by opening both side latches on
the connector [6].
a. Eject the disk backplane data cable from the disk backplane by opening
both side latches on the connector [7].
b. Eject the disk backplane data cable from the motherboard by opening both
side latches on the connector [8].
Related Information
■ “Install the Power, FIM, Temperature Sensor, and Disk Backplane Data
Cables” on page 196
a. Connect the disk backplane data cable to the motherboard by opening both
side latches and plugging the data cable connector into the motherboard
connector [8].
The motherboard connector side latches will close, locking the disk backplane data cable
connector in place.
b. Connect the disk backplane data cable to the disk backplane by opening
both side latches and plugging the data cable connector into the disk
backplane connector [7].
The disk backplane connector side latches will close, locking the disk backplane data cable
connector in place.
a. Install the FIM cable into the motherboard by opening both side latches and
plugging the FIM connector into the motherboard connector [6].
The motherboard connector side latches will close, locking the FIM cable connector in
place.
b. Connect the FIM cable to the FIM by plugging the cable connector into the
FIM [5].
a. Route the temperature sensor cable through the left-front chassis sidewall
and install the sensor into the FIM housing [4].
b. Connect the temperature sensor cable to the disk backplane by plugging the
cable connector into the disk backplane connector [3].
a. Connect the disk backplane power cable to the disk backplane by plugging
the cable connector into the disk backplane connector [2].
b. Connect the disk backplane power cable to the motherboard by plugging the
cable connector into the motherboard connector [1].
c. Reconnect the power cords to the power supplies, and power on the server.
See “Reconnect Data Cables and Power Cords” on page 216 and “Power On the
Server” on page 216.
Related Information
■ “Remove the Power, FIM, Temperature Sensor, and Disk Backplane Data
Cables” on page 194
The following section describes how to service the motherboard assembly. The motherboard
assembly is a field-replaceable unit (FRU). For more information about FRUs, see “Illustrated
Parts Breakdown” on page 19 and “Field-Replaceable Units” on page 22.
Caution - The motherboard assembly should be removed and replaced only by authorized
Oracle Service personnel.
Caution - Ensure that all power is removed from the server before removing or installing the
motherboard. You must disconnect the power cables before performing these procedures.
Caution - These procedures require that you handle components that are sensitive to
electrostatic discharge. This sensitivity can cause the component to fail. To avoid damage,
ensure that you follow electrostatic discharge safety measures and antistatic practices. See
“Electrostatic Discharge Safety” on page 50.
Related Information
■ “Remove the Server From the Rack” on page 61
■ “Take Antistatic Measures” on page 62
■ “Remove the Server Top Cover” on page 63
Caution - Use the Oracle ILOM backup utility prior to removing the motherboard. This utility
backs up the Oracle ILOM configuration of the service processor. For more information, see the
Oracle ILOM 4.0 Documentation Library at https://www.oracle.com/goto/ilom/docs.
a. Power off the server and disconnect the power cords from the power
supplies.
See “Powering Down the Server” on page 53.
c. Attach an antistatic wrist strap to your wrist, and then to a metal area on the
chassis.
See “Take Antistatic Measures” on page 62.
Caution - During the motherboard removal procedure, it is important to label power supplies
with the slot numbers from which they were removed (PS0, PS1). This is required because the
power supplies must be reinstalled into the slots from which they were removed; otherwise, the
server key identity properties (KIP) data might be lost. When a server requires service, the KIP
is used by Oracle to verify that the warranty on the server has not expired. For more information
on KIP, see “FRU Key Identity Properties (KIP) Automated Update” on page 51.
■ Air baffles
■ Fan modules
See “Remove a Fan Module” on page 81.
■ Power supplies
See “Remove a Power Supply” on page 88.
■ PCIe risers and attached PCIe cards
See “Servicing PCIe Risers (CRU)” on page 111, “Servicing PCIe Cards
(CRU)” on page 121, and “Servicing the Internal HBA Card and HBA Super Capacitor
(FRU)” on page 169.
Note - Remove the M.2 SATA cable between the PCIe slot 3 riser and the motherboard
SATA connector and set it aside.
b. Disconnect the disk backplane data cable by opening the ejectors and
pulling out the cable connector [2].
c. Disconnect the front indicator module (FIM) cable connector by opening the
ejectors and pulling out the cable connector [2].
d. Disconnect the NVMe cables (if present) and carefully lift them from the
center cable trough and set them aside [3].
Note - You do not need to remove the NVMe cables or the chassis mid-wall when removing the
motherboard from the server chassis.
e. Remove the SAS cables and the super capacitor cable that were connected
to the internal HBA card, and then carefully lift them from the left-side cable
trough and set them aside [4].
See “Remove the Internal HBA Cables” on page 179.
a. Using a Torx T25 screwdriver, loosen the two green captive screws that
secure the motherboard bracket/handle to the server chassis.
b. Grasp the metal bracket located just to the rear of the DIMM slots and the
finger loop, and then slide the motherboard toward the front of the server
and lift it slightly to disengage it from the eight mushroom-shaped standoffs
located on the server chassis under the motherboard.
c. Lift the motherboard out of the server chassis and place it on an antistatic
mat and next to the replacement motherboard.
5. Remove the following reusable components from the motherboard and install
them onto the replacement motherboard.
Note - Install the DIMMs only in the slots (connectors) that correspond to the slots
from which they were removed. Performing a one-to-one replacement of the DIMMs
significantly reduces the possibility that the DIMMs will be installed in the wrong slots. If
you do not reinstall the DIMMs in the same slots, server performance might suffer and some
DIMMs might not be used by the server.
7. Remove the processor socket covers from the replacement motherboard and
install the processors.
a. Grasp the processor socket cover finger grips (labeled REMOVE) and lift the
socket cover up and off the processor socket.
b. Install a processor into the socket from which you removed the processor
socket cover.
See “Install a Processor” on page 144.
c. Repeat Step 7a and Step 7b to remove the second processor socket cover
from the replacement motherboard and install the second processor.
Caution - The processor socket covers must be installed on the faulty motherboard; otherwise,
damage might result to the processor sockets during handling and shipping.
a. Align the processor socket cover over the processor socket alignment
posts. Install the processor socket cover by firmly pressing down on all four
corners (labeled INSTALL) on the socket cover.
You will hear an audible click when the processor socket cover is securely attached to the
processor socket.
b. Repeat Step 8a to install the second processor socket cover on the faulty
motherboard.
9. Check to see if the replacement motherboard has a locate light pipe installed.
■ If you do not find a replacement light pipe, perform the following steps to remove the
light pipe from the faulty motherboard.
ii. Twist the tool back and forth to release the light pipe from the housing.
i. Match the rectangular holes on the outside of the light pipe with the
retaining clips on the housing.
ii. Push the light pipe onto the housing until the clips latch in the holes.
Related Information
■ “Customer-Replaceable Units” on page 21
■ “Field-Replaceable Units” on page 22
■ “Install the Motherboard” on page 206
a. Grasp the metal bracket located to the rear of the DIMMs and the finger
grasp, and then tilt the front of the motherboard up slightly and push it into
the opening in the rear of the server chassis.
b. Lower the motherboard into the server chassis and slide it to the rear until
it engages the eight mushroom-shaped standoffs located on the server
chassis under the motherboard.
c. Ensure that the indicators, controls, and connectors on the rear of the
motherboard fit correctly into the rear of the server chassis.
d. Using a Torx T25 screwdriver, tighten the two green captive screws to
secure the motherboard bracket/handle to the server chassis [2].
a. Carefully reinstall the SAS cables and super capacitor cable along the left-
side cable trough [3].
See “Install the Internal HBA Cables” on page 182.
b. Carefully reinstall the NVMe cables (if present) into the center cable trough
and then reconnect the cables to the motherboard NVMe connectors [4].
d. Reconnect the disk backplane data cable to the motherboard connector [5].
e. Reconnect the disk backplane power cable to the motherboard connector [6]
Note - Reinstall the M.2 SATA cable between the PCIe slot 3 riser and the motherboard
SATA connector.
■ Power supplies
Caution - When reinstalling power supplies, it is important to reinstall them into the slots from
which they were removed during the motherboard removal procedure; otherwise, the server key
identity properties (KIP) data might be lost. When a server requires service, the KIP is used by
Oracle to verify that the warranty on the server has not expired. For more information on KIP,
see “FRU Key Identity Properties (KIP) Automated Update” on page 51.
c. Reconnect the power cords to the power supplies, and power on the server.
See “Reconnect Data Cables and Power Cords” on page 216 and “Power On the
Server” on page 216.
Note - IMPORTANT: After replacing the motherboard, you might need to manually program
the product serial number (PSN) into the new motherboard. This is necessary because the
motherboard is a secondary member of a select group (or quorum) of components used
for maintaining the PSN for service entitlement, and if you replace more than one of the
quorum members during any given service procedure, a secondary quorum member might
need to be programmed with the PSN. See “FRU Key Identity Properties (KIP) Automated
Update” on page 51.
Related Information
■ “Customer-Replaceable Units” on page 21
■ “Field-Replaceable Units” on page 22
■ “Remove the Motherboard” on page 199
After replacing components inside of the server, perform the procedures in the following
sections:
Before you can install an optional server component into the server, you must remove the filler
panel from the location into which you intend to install the component. When you remove
a storage drive or a PCIe card from the server, you must install either a replacement for the
component removed or a filler panel.
Note - In single-processor systems, PCIe slot Note - In single-processor systems, PCIe slot
1 is nonfunctional; therefore, there is no need 1 is nonfunctional; therefore, the server ships
to remove the filler panel for slot 1. with this filler panel installed.
2. Check both sides of the chassis to ensure that the top cover is fully down and
flush with the chassis.
If the cover is not fully down and flush with the chassis, slide the cover towards the back of the
chassis to position the cover in the correct position.
3. Gently slide the cover toward the front of the chassis until it latches into place
with an audible click [2].
As you slide the cover toward the front of the server, the release button on the top of the server
automatically rotates downward to the closed position. Latch the top cover by pushing down
on the button until it is flush with the cover and you hear an audible click. An audible click
indicates that the cover is latched.
4. Use a Torx T15 screwdriver to turn the release button latch counter-clockwise to
the locked position.
Related Information
■ “Remove the Server Top Cover” on page 63
Related Information
■ “Take Antistatic Measures” on page 62
Caution - Deploy any rack anti-tilt mechanisms before installing the server into the rack.
Caution - The server weighs approximately 35.0 lbs (15.88 kg). Two people are required to
carry the chassis and install it into the rack.
1. Lift the server from the antistatic mat, and reinstall the server into the rack.
Refer to “Installing the Server Into a Rack” in Oracle Servers X7-2 and X7-2L Installation
Guide for the installation instructions specific to your rackmount kit.
2. If the cable management arm (CMA) is not installed, that is, you removed it
because you removed the server completely out of the rack, install the CMA.
For installation instructions for the CMA, refer to “Install the Cable Management Arm
(Optional)” in Oracle Servers X7-2 and X7-2L Installation Guide.
3. If the cables are disconnected from the back of the server, that is, you
disconnected the cables because you removed the server completely out of the
rack, reconnect the cables.
■ To identify the location of cable connectors on the back of the server, refer
to “Back Panel Connector Locations” on page 40.
Related Information
■ “Remove the Server From the Rack” on page 61
■ “Reconnect Data Cables and Power Cords” on page 216
1. Push the server back into the rack, as described in the following steps.
a. Simultaneously pull and hold the two green release tabs (one on each side
of the slide rails on the server) toward the front of the server while you push
the server into the rack.
As you push the server into the rack, verify that the cable management arm (CMA) retracts
without binding.
Note - To pull a green release tab, place your finger in the center of the tab, not on the end, and
apply pressure as you pull the tab toward the front of the server.
b. Continue pushing the server into the rack until the slide-rail locks (on the
front of the server) engage the slide-rail assemblies.
You will hear an audible click when the server is in the normal rack position.
2. If the CMA is not installed, that is, you removed it because you removed the
server completely out of the rack, install the CMA.
For installation instructions for the CMA, refer to “Install the Cable Management Arm
(Optional)” in Oracle Servers X7-2 and X7-2L Installation Guide.
3. If the cables are disconnected from the back of the server, that is, you
disconnected the cables because you removed the server completely out of the
rack, reconnect the cables.
■ For instructions to reconnect cables to the back of the server, see “Reconnect Data Cables
and Power Cords” on page 216.
■ To identify the location of cable connectors on the back of the server, see “Back Panel
Connector Locations” on page 40.
Related Information
■ “Reconnect Data Cables and Power Cords” on page 216
3. If necessary, reinstall the cables into the cable management arm and secure
them with Velcro straps.
Related Information
■ “Disconnect Cables From the Server” on page 59
■ “Reinstall the Server Into the Rack” on page 213
■ “Return the Server to the Normal Rack Position” on page 214
■ “Power On the Server” on page 216
Power on the server to Main power mode by performing one of the following
actions:
■ Log in to the Oracle ILOM web interface, click Host Management → Power
Control and select Power On from the Select Action list.
■ Log in to the Oracle ILOM command-line interface (CLI), and type the
following command at the Oracle ILOM prompt:
When the server is powered on to Main power mode and the power-on self-test (POST)
code checkpoint tests have completed, the green System OK LED status indicator on the
front panel of the server lights and remains lit.
Related Information
■ “Powering Down the Server” on page 53
■ “Reconnect Data Cables and Power Cords” on page 216
The server has five auto-negotiating gigabit Ethernet (GbE) ports. Three Ethernet ports use
standard RJ-45 connectors, and two use enhanced small form-factor pluggable (SFP+) port
connectors. The transfer rates are shown in the following table.
Related Information
The server has one 10/100/1000BASE-T Ethernet management domain interface, labeled NET
MGT. For information on configuring this port for managing the server with Oracle ILOM,
refer to the Oracle Integrated Lights Out Manager (ILOM) 4.0 Documentation Library at
https://www.oracle.com/goto/ilom/docs.
Related Information
The serial management connector, labeled SER MGT, is an RJ-45 connector that can be
accessed from the back panel. This port is the default connection to the server Oracle ILOM SP.
Use this port only for server management.
Parameter Setting
Connector SER MGT
Rate 9600 baud
Parity None
Stop bits 1
Data bits 8
The following figure and table describe the SER MGT port pin signals.
If you need to connect to the SER MGT port using a cable with either a DB-9 or a DB-25
connector, follow the pin descriptions in the tables to create a crossover adapter appropriate for
your serial connection.
Related Information
■ “Back Panel Components and Cable Connections” on page 18
■ “Disconnect Cables From the Server” on page 59
■ “Reconnect Data Cables and Power Cords” on page 216
USB Ports
The server has two USB ports for attaching supported USB 3.0-compliant devices. There is one
USB port on the server back panel, and one on the motherboard.
The following figure and table describe the USB port pin signals.
Related Information
■ “Back Panel Components and Cable Connections” on page 18
■ “Disconnect Cables From the Server” on page 59
■ “Reconnect Data Cables and Power Cords” on page 216
This section provides an overview of BIOS configuration management, UEFI BIOS, and the
BIOS Setup Utility:
Related Information
■ Oracle ILOM – “Maintaining x86 BIOS Configuration Parameters” in the Oracle ILOM
Administrator's Guide for Configuration and Maintenance Firmware Release 4.0 in the
Oracle Integrated Lights Out Manager (ILOM) 4.0 Documentation Library at https://www.
oracle.com/goto/ilom/docs.
■ BIOS Setup Utility – “Common BIOS Setup Utility Tasks” on page 231
If the PCIe riser fault message in Oracle ILOM is not cleared under Open Problems, you
must manually clear the fault in Oracle ILOM. For instructions for manually clearing a PCIe
riser fault, see the procedure "Clear Faults for Undetected Replaced or Repaired Hardware
Components" in the Oracle ILOM User's Guide for System Monitoring and Diagnostics
Firmware Release 4.0 in the Oracle Integrated Lights Out Manager (ILOM) 4.0 Documentation
Library at https://www.oracle.com/goto/ilom/docs.
The following table provides descriptions for the top-level BIOS Setup Utility menus.
Menu Description
Main General product information, including memory, time/date, security settings, system serial
number, and CPU and DIMM information.
Advanced Configuration information for the CPU, trusted computing, USB, and other information. Set the
IP address for the server SP.
IO Manage configuration settings for I/O devices, such as I/O virtualization settings, and enable and
disable Option ROMs.
Boot Configure the boot device priority.
Save & Exit Save changes and exit, discard changes and exit, discard changes, or restore the default BIOS
settings.
See “BIOS Setup Utility Menu Options” on page 255 for examples of each of these screens.
Related Information
■ “Navigate BIOS Setup Utility Menus” on page 228
When viewing the BIOS output from a terminal using the serial console redirection feature,
some terminals do not support function keys. BIOS supports the mapping of function keys
to Control key sequences when serial redirection is enabled. The following table provides a
description of the function key to Control key sequence mappings.
Related Information
You can access the BIOS Setup Utility screens from the following interfaces:
■ Use a terminal (or terminal emulator connected to a computer) through the serial port on the
back panel of the server.
■ Connect to the server using the Oracle ILOM Remote System Console Plus application.
■ From the local server, press the On/Standby button on the front panel of the server to
power off the server, and then press the On/Standby button again to power on the server.
■ From the Oracle ILOM web interface, click Host Management → Power Control and
select Reset from the Select Action list.
■ From the Oracle ILOM CLI, type reset /System
2. After the server resets, to enter the BIOS Setup Utility, press the F2 key (Ctrl
+E from a serial connection) when prompted and while the BIOS is running the
power-on self-tests (POST).
Related Information
■ “BIOS Setup Utility Menus” on page 226
■ “BIOS Key Mappings” on page 226
■ “BIOS Setup Utility Menu Options” on page 255
■ “Exit BIOS Setup Utility” on page 253
To navigate the menus or options listed on a menu, use the arrow keys. The currently selected
option or sub-menu is highlighted. For further instructions on how to navigate and change
settings in the BIOS Setup Utility, refer to the online information provided on the menu.
2. Use the left and right arrow keys to select the different primary menu options.
As you select each menu option, the top-level screen for that menu option appears.
3. To navigate options presented on a top-level screen, use the up and down arrow
keys.
Only options that can be modified are highlighted when you press the up and down arrow keys.
■ If an option can be modified, as you select the option, user instructions for
modifying the option appear in the right column of the screen.
5. Press the Esc key to return from a sub-menu screen to the previous menu
screen.
Pressing Esc from a top-level menu is equivalent to selecting the Discard Changes and Exit
option from the Save & Exit Menu.
7. Press the F10 key to save your changes and exit the BIOS Setup Utility.
Alternatively, you can select the Save & Exit menu, and then select Save Changes and Exit to
save your changes and exit the BIOS Setup Utility.
Note - After modifying any BIOS settings, the subsequent reboot might take longer than a
typical reboot where no settings were modified. The additional delay is required to ensure that
changes to the BIOS settings are synchronized with Oracle ILOM.
Related Information
Oracle Server X7-2 is equipped with a Unified Extensible Firmware Interface (UEFI)-
compatible BIOS, which runs with all operating systems that are supported on the server. The
BIOS firmware controls the system from power-on until an operating system is booted, and
allows you to configure, enable, disable, or manage system components.
In UEFI BIOS, the configuration screens for the add-in cards appear as menu items in the BIOS
Advanced Menu as part of the standard BIOS Setup Utility screens. For example, if the Oracle
Storage 12 Gb SAS PCIe RAID HBA, Internal card is installed in the server, the configuration
utility for the HBA appears as a menu selection.
■ View the BIOS configuration synchronization status and synchronize the configuration
parameters
■ Reset the factory defaults for the service processor (SP) and Oracle ILOM BIOS
■ Backup or restore the BIOS configuration
■ Enable UEFI diagnostics to run at system boot
For more information about Oracle ILOM BIOS configuration and management tools, refer to
the Oracle Integrated Lights Out Manager (ILOM) 4.0 Documentation Library at: https://
www.oracle.com/goto/ilom/docs.
Oracle Server X7-2 UEFI BIOS supports UEFI Secure Boot. UEFI Secure Boot defines how
platform firmware can authenticate a digitally signed UEFI image, such as an operating system
loader or a UEFI driver.
When enabled, UEFI Secure Boot provides a policy-based invocation of various UEFI
executable images, using cryptographic signatures to identify the software publishers. UEFI
Secure Boot also requires all third-party UEFI drivers and operating system boot loaders to be
signed by Microsoft or with Key Exchange Key (KEK) by using BIOS setup.
UEFI Secure Boot is disabled by default. For configuration information, see “Configure UEFI
Secure Boot” on page 242.
Oracle Server X7-2 uses Trusted Execution Technology (TXT), which provides authenticity of
a platform and its operating system.
When enabled, TXT ensures that the operating system (OS) starts in a trusted environment, and
provides the OS with additional security capabilities not available to an untrusted OS. Using
cryptographic techniques, TXT provides measurements of software and platform components
so that system software as well as local and remote management applications may use those
measurements to make trust decisions. Trusted Execution Technology defends against software-
based attacks aimed at stealing sensitive information by corrupting system or BIOS code, or
modifying a platform's configuration.
For additional information about BIOS setup tasks, refer to the Oracle X7 Series Servers
Administration Guide at https://www.oracle.com/goto/x86admindiag/docs
■ “Verify BIOS Factory Default Settings” on page 232
In the BIOS Setup Utility, you can return the BIOS settings to the optimal factory default
values, as well as view and edit settings as needed. Any changes that you make in the BIOS
Setup Utility (using the F2 key) persist until the next time you change the settings.
Before you begin, ensure that a console connection is established to the server.
2. After the server resets and begins the initialization process, when prompted,
press the F2 key to access the BIOS Setup Utility.
■ Press the F9 key to automatically load the optimal factory default settings.
4. Press the F10 key to save the changes and exit the BIOS Setup Utility.
Related Information
■ “Access BIOS Setup Utility Menus” on page 227
The Boot Options Priority list displays the boot device candidates for the system.
In addition to using the F2 key to view or edit the system BIOS settings, you can use the F8
key during the BIOS startup to specify a temporary boot device. This selected boot device is in
effect only for the current system boot. The permanent boot device specified using the F2 key
will be in effect after booting from the temporary boot device.
■ From the local server, press the On/Standby button on the front panel of the server to
power off the server, and then press the On/Standby button again to power on the server.
■ From the Oracle ILOM web interface, click Host Management → Power Control and
select Reset from the Select Action list. Click Save, and then click OK
■ From the Oracle ILOM CLI, type reset /System
2. After the server resets and begins the initialization process, press the F8 key (or
Ctrl+P from a serial connection) when prompted while the UEFI BIOS is running
the power-on self-test (POST) to access the boot device menu.
3. In the Please Select Boot Device dialog box, select the boot device according to
the operating system you elected to use, and then press Enter.
4. Follow the on-screen instructions to install the operating system from the
selected boot device.
Related Information
The TMP feature set is enabled by default. If you wish to disable it, or to enable it after it has
been disabled, perform the procedure in this section.
Note - TPM enables you to administer the TPM security hardware in your server. For additional
information about implementing this feature, refer to the Windows Trusted Platform Module
Management documentation provided by your operating system or third-party software vendor.
4. On the Trusted Computing 2.0 Configuration screen, select Security TPM Device
Support and press Enter. Do one of the following:
5. On the updated Trusted Computing 2.0 Configuration screen, press the F10 key
to save the changes and exit the BIOS Setup Utility.
Related Information
3. On the IO Menu screen, select either Internal Devices or Add In Cards and press
Enter to display the internal device or add-in card slot for which you want to
enable or disable the PCI-E UEFI Driver.
4. On the Internal Devices screen, select the internal device or add In card slot that
you want to configure.
5. On the PCI-E UEFI Driver Enable screen, select PCI-E UEFI Driver Enable and
press Enter. Do one of the following:
6. Press the F10 key to save the changes and exit the BIOS Setup Utility.
Related Information
3. On the IO Menu screen, select Add In Cards and press Enter to display the add-in
card slots.
4. On the Add In Cards screen, select the slot in which you want to configure the
card and press Enter.
5. On the IO resource allocation screen for that card, select IO Enable and press
Enter. Do one of the following:
■ Select Enabled to enable I/O resource allocation for the I/O card.
■ Select Disabled to disable I/O resource allocation for the I/O card.
6. Press the F10 key to save the changes and exit the BIOS Setup Utility.
Related Information
3. On the Security Settings screen, select Secure Boot and press Enter.
4. On the Secure Boot screen, select Secure Boot and press Enter. Do one of the
following:
■ Select Enabled to enable UEFI Secure Boot. Continue with the next step to
manage policy variables.
■ Select Disabled to disable UEFI Secure Boot. Continue with Step 8 to save
changes and exit from the BIOS Setup Utility.
When enabled, Secure Boot allows you to manage Secure Boot policy variables.
5. To manage Secure Boot policy variables, select Key Management and press Enter.
The Key Management screen provides options to provision factory default Secure Boot keys or
to enroll an Extensible Firmware Interface (EFI) image.
6. If you want to provision factory default keys, select Provision Factory Defaults
and press Enter. Do one of the following:
■ Select Enabled to allow the provisioning of factory default Secure Boot keys
when the system is in Setup Mode. When enabled, you can select Install
Factory Default Keys to force the system to User Mode and install all the
factory default Secure Boot keys.
remove all Secure Boot keys from the system. Selecting this option also
resets the system to Setup Mode.
7. If you want to enroll an EFI image, select Enroll Efi Image and press Enter.
a. On the Select a File System screen, Scroll through the list and select the file
system that contains the EFI file and press Enter.
b. On the Select File screen, scroll through the list and select the EFI file (or
another available file) and press Enter.
c. On the next Select File screen, scroll through the list and select the image
file that you want to run in Secure Boot mode and press Enter.
d. To save all Secure Boot policy variables, select Save all Secure Boot
variables and press Enter.
e. On the Select a File System screen, select the file system where you want to
save the EFI file and press Enter.
The Secure Boot policy variables are saved to the root folder in the target file system.
8. Press the F10 key to save the changes and exit the BIOS Setup Utility.
Related Information
The Trusted Platform Module (TPM) feature must be enabled on your server before enabling
Trusted Execution Technology (TXT). See “Configure TPM Support” on page 234.
4. On the TXT screen, select Enable Intel(R) TXT and press Enter. Do one of the
following:
5. Press the F10 key to save the changes and exit the BIOS Setup Utility.
Related Information
2. Use the up and down arrow keys to select the desired action.
4. In the confirmation dialog box, select Yes to proceed and exit the BIOS Setup
Utility, or select No to stop the exit process.
Note - After modifying any BIOS settings, the subsequent reboot might take longer than a
typical reboot where no settings were modified. The additional delay is required to ensure that
changes to the BIOS settings are synchronized with Oracle ILOM.
Related Information
■ “Access BIOS Setup Utility Menus” on page 227
■ “BIOS Setup Utility Menus” on page 226
This section includes screens of the main menus in the BIOS Setup Utility for Oracle Server
X7-2. Following the screen for each menu is a table of the options available from that menu.
Related Information
This section includes a screen of the BIOS Main Menu. The options that are available from the
Main Menu are described in the table that follows. Options in the table that are marked as “(R/
O)” are read-only information and cannot be changed.
The following tables describe the options provided by the BIOS Main Menu and submenus.
Example: 42.01.04.01
System Date Current date is displayed. You can
change the date setting.
Example: 13:38:27
UPI Link Speed (R/O) SLOW/ Intel UltraPath Interconnect (UPI)
operational speed is displayed. The
Example: 224 GB
Current Memory Speed (R/O) Memory speed is displayed.
Example: Healthy
BMC Firmware Revision (R/O) The service processor firmware version
is displayed.
Example: 1134FML00V
Board Serial Number Board serial number is displayed.
Example: 489089M+1637E2002E
CPU INFORMATION (R/O) Attributes of a single processor (CPU)
are defined. A separate information
structure is provided for each processor
supported in the system. Most of the
values are dependent on the processor.
Socket 0 CPU Information (R/O) If CPU socket 0 is populated, the
following options are listed. Otherwise,
displays “Not Present.”
Genuine Intel CPU @ 2.6 GHz Processor ID brand is displayed.
CPU Signature Processor information is displayed.
Example: 50654
Microcode Patch Software update (microcode patch)
information is displayed.
Example: 2000009
Example: 26
Active Cores Number of active processor cores is
displayed.
Intel HT Technology Indicates whether Intel Hyper Threading
is supported.
Intel VT-x Technology Indicates whether Intel Virtualization
Technology is supported.
L1 Data Cache Example: 32 KB x 26
L1 Code Cache Example: 32 KB x 26
L2 Cache Example: 1024 KB x 26
L3 Cache Example: 36608 KB
Socket 1 CPU Information (R/O) If CPU socket 1 is populated, the same
options as Socket 0 CPU Information
are displayed. Otherwise, displays “Not
Present.”
DIMM INFORMATION (R/O) Memory module (DIMM) presence and
size information are displayed.
Processor 0 DIMMs (R/O) For D0...D11, if a DIMM is present,
memory size (in gigabytes) is displayed.
Otherwise, displays “Not Present.”
Processor 1 DIMMs (R/O) Same as Processor 0.
SECURITY Configure the security settings.
TXT Enable Intel TXT Disable/ Disabled Enables Intel Trusted Execution
Enable Technology (TXT).
HDD Security Configuration Set User Password Set an HDD user password for the
selected drive.
Secure Boot Customize Secure Boot settings.
Attempt Secure Boot Disabled/Enabled Disabled Secure Boot is activated when Platform
Key (PK) is enrolled, System mode
is User/Deployed, and Compatibility
Support Module (CSM) function is
disabled.
Related Information
This section includes a screen of the BIOS Advanced Menu. The options that are available from
the Advanced Menu are described in the table that follows. Options in the table that are marked
as “(R/O)” are read-only information and cannot be changed.
Example: Update
0ABBCCDDEEFF to
0ABBCCF07901 by inputting
F07901
Enable DHCP Disabled/Enabled Disabled Enable or disable DHCP.
Initiator IP Address NA 0.0.0.0 Set initiator IP address in dotted-
decimal notation.
Initiator Subnet Mask NA 0.0.0.0 Set initiator subnet mask IP
address in dotted-decimal
notation.
Gateway NA 0.0.0.0 Set initiator gateway IP address
in dotted-decimal notation.
Target Name NA NA The worldwide unique name of
the target. Only IQN format is
accepted.
Target IP address 0.0.0.0 None Set target IP address in dotted-
decimal notation.
Target Port 3260 Change target port number.
Boot LUN 0 Set the hexadecimal
representation of the boot logical
unit number (LUN).
Example: 4752-3A4F-6b7e-
2F99
Authentication Type CHAP/None CHAP Define the Challenge-
Handshake Authentication
Protocol (CHAP). Available
settings are CHAP, Kerberos,
and None.
CHAP Type One Way/Mutual One Way Set CHAP type to either One
Way or Mutual.
CHAP Name NA None Set CHAP name.
CHAP Secret NA None Set the CHAP secret password.
The secret length range is 12 to
16 bytes.
Delete Attempts NA NA Delete one or more attempts.
Change Attempt Order NA NA Change the order of attempts.
Use arrow keys to select the
attempt, then press plus or minus
(+/-) keys to move the attempt
up/down in the attempt order
list.
10 Mbs Full
CEE (only)
BBS
Int 18h
Int 19h
Hide Setup Prompt Enabled/Disabled Disabled Configure whether the Setup
Prompt is displayed during
ROM initialization.
■ 0 = 4 seconds
■ 15 = no delay
■ 1-14 = timeout value in
seconds
Link Speed AutoNeg AutoNeg Configure the link speed setting
to be used when booting the
1Gbps selected protocol. For dual port
adapters, the adapter supports
10Gbps multiple combinations of link
speeds per port.
25Gbps
VLAN Mode Enabled/Disabled Disabled Configure the virtual LAN
(VLAN) mode.
VLAN ID NA 1 Configure the VLAN ID (1…
4094).
Note - This selection is
available only when VLAN
Mode is Enabled.
NIC + RDMA Mode (R/O) NA Disabled
Blink LEDs NA 0 Configure blink LEDs for a
duration of up to 15 seconds.
Link Status (R/O) NA Connected Specifies the link status of the
port.
Chip Type (R/O) NA NA Displays the manufacturer and
model of the Ethernet controller.
PCI Device ID (R/O) NA 16E2 Displays the PCI device
identifier.
Bus:Device:Function (R/O) NA NA Displays the Bus device function
identifier.
Permanent MAC Address(R/O) NA NA Lists the MAC address of the
Ethernet controller.
Virtual MAC Address (R/O) NA NA Lists the virtual MAC address of
the Ethernet controller.
Note - Depending on the devices that are populating your PCIe slots, you will see different
entries if the devices are publishing their driver health status.
115200
Data Bits 7/8 8 Select the data bits.
Parity None/Even/Odd/Mark/Space None A parity bit can be sent with
the data bits to detect some
transmission errors.
Note - The options in this section are available only when the Security TPM Device Support
option is set to Enabled.
Balanced Energy
Energy Efficiency
Uncore Frequency Scaling Enabled/Disabled Disabled Enable or disable Uncore
Frequency Scaling (USF).
Related Information
This section includes a screen of the BIOS IO Menu. The options that are available from the IO
Menu are described in the table that follows.
Related Information
Related Information
■ “BIOS Main Menu Selections” on page 255
■ “BIOS Advanced Menu Selections” on page 260
■ “BIOS IO Menu Selections” on page 276
■ “BIOS Exit Menu Selections” on page 282
This section includes a screen of the BIOS Exit Menu. The options that are available from the
Exit Menu are described in the table that follows.
Related Information
■ “BIOS Main Menu Selections” on page 255
■ “BIOS Advanced Menu Selections” on page 260
■ “BIOS IO Menu Selections” on page 276
■ “BIOS Boot Menu Selections” on page 280
This section includes information about monitoring components and identifying SNMP
messages for the Oracle Server X7-2.
■ “Monitoring Component Health and Faults Using Oracle ILOM” on page 285
■ “Monitoring System Components” on page 286
■ “Identifying SNMP Trap Messages” on page 297
Related Information
■ Oracle Integrated Lights Out Manager (ILOM) 4.0 Documentation Library at: https://
www.oracle.com/goto/ilom/docs
The Oracle ILOM 4.0 interfaces provide easy-to-view information about the health status of
system components. From the Oracle ILOM web interface or in the Oracle ILOM command-
line interface (CLI), you can collect system-specific information about the server, determine the
health state of discrete components, and view any open problems on the server. Oracle ILOM
automatically detects system hardware faults and environmental conditions on the server. If a
problem occurs on the server, Oracle ILOM will automatically do the following:
■ Illuminate the Fault-Service Required LED status indicator on the server front and
back panels. See “Troubleshooting Using the Server Front and Back Panel Status
Indicators” on page 28 and “Monitoring System Components” on page 286.
■ Identify the faulted component in the Open Problems table. Open problems detected
on a host server or system chassis are viewable from either the Open Problems web
page or the /System/Open_problems CLI target. Refer to View Open Problems Detected
on a Managed Device in the Oracle ILOM User's Guide for System Monitoring and
Diagnostics Firmware Release 4.0.x in the Oracle Integrated Lights Out Manager (ILOM)
4.0 Documentation Library at https://www.oracle.com/goto/ilom/docs.
■ Record system information about the faulted component or condition in the Oracle ILOM
event log. Refer to Managing ILOM Log Entries in the Oracle ILOM User's Guide for
System Monitoring and Diagnostics Firmware Release 4.0.x in the Oracle Integrated Lights
Out Manager (ILOM) 4.0 Documentation Library at https://www.oracle.com/goto/ilom/
docs.
For further information about administering open problems that are detected and reported by
Oracle ILOM, refer to “Administering Open Problems” in the Oracle ILOM Administrator's
Guide for Configuration and Maintenance Firmware Release 4.0.x in the Oracle Integrated
Lights Out Manager (ILOM) 4.0 Documentation Library at https://www.oracle.com/goto/
ilom/docs.
The tables in this section identify the system components and describe the naming conventions
applied to the components of Oracle Server X7-2.
Each section corresponds to an IPMI entity ID and lists sensors, indicators, and field-
replaceable units (FRUs) related to that entity. The tables contain the following fields:
■ Component Name – Shows the user-visible component name used in management
interfaces to refer to a specific sensor, indicator, or FRU. The IPMI name is a shortened
form of the component name, and is indicated by the boldface portion of the component
name.
■ IPMI Type – Indicates the type of sensor, indicator, or FRU represented.
■ Description – Describes the particular component name reference.
■ Values – Defines the states of the sensor, indicator, or FRU entity, and any specific units or
values that are expected, if applicable.
Note - Some component names are hidden in the Oracle ILOM user interfaces. Further, as of
Oracle ILOM 3.2, the Oracle ILOM 3.0 legacy targets /SYS and /STORAGE have been replaced
by /System. Even though these legacy targets might be hidden, you can still use them to issue
commands. For information on legacy targets, see the ILOM 3.2 Documentation Library at
https://www.oracle.com/goto/ilom/docs.
20h-ACPI_SOFT_OFF
/SYS/VPS Threshold Virtual power sensor Watts
sensor
/SYS/VPS_CPUS Threshold Virtual power sensor (CPUs) Watts
sensor
/SYS/VPS_MEMORY Threshold Virtual power sensor (Memory) Watts
sensor
/SYS/VPS_FANS Threshold Virtual power sensor (Fans) Watts
sensor
/SYS/T_AMB Threshold Ambient temperature on system Degrees Celsius
sensor motherboard
/SYS/TEMP_FAULT Indicator Temperature Fault LED Color: Amber
Off: Normal
Off: Normal
Off: Normal
Off: Normal
Off: Normal
Off: Normal
Related Information
The system has four 40-mm fan modules with two fans in each module. The following table
lists the system cooling unit components.
Component Name (Oracle ILOM CLI IPMI Type Description Values (if applicable)
Targets)
/SYS/MB/FM[0-3] FRU Fan module FRU
/SYS/MB/FM[0-3]/F[0-x] FRU Individual fan
/SYS/MB/FM[0-3]/PRSNT Discrete sensor Fan module is present. 01h-ENTITY_ABSENT
02h-ENTITY_PRESENT
/SYS/MB/FM[0-3]/F[0-x]/TACH Threshold sensor Fan module fan speed RPM
/SYS/MB/FM[0-3]/SERVICE Indicator Fan Fault-Service Required LED Color: Amber
Location: Motherboard
Off: Normal
Related Information
■ “System Chassis Components” on page 287
■ “Disk Backplane Components” on page 290
■ “Memory Device Components” on page 291
■ “Power Unit Components” on page 291
■ “Processor Components” on page 293
■ “System Motherboard Components” on page 293
■ “System Firmware Components” on page 295
■ “Hard Disk Drive Components” on page 295
Component Name (Oracle ILOM CLI Targets) IPMI Type Description Values (if applicable)
/SYS/DBP FRU Disk backplane FRU
/SYS/DBP/PRSNT Discrete sensor Disk backplane presence 01h-ENTITY_ABSENT
02h-ENTITY_PRESENT
/SYS/DBP/HDD[0-x] Pseudo Hard disk drives (HDD)
/SYS/DBP/HDD[0-x]/PRSNT Discrete sensor Hard disk drive presence 01h-ENTITY_ABSENT
02h-ENTITY_PRESENT
/SYS/DBP/HDD[0-x]/STATE State sensor Hard disk drive state 01h-FAULT_STATUS
02h-IDENTITY
04h-INSTALLED
20h-SLOT_POWER_OFF
/SYS/DBP/HDD[0-x]/SERVICE Indicator Fault-Service Required Color: Amber
LED
Location: HDD
Off: Normal
Off: Normal
02h-ENTITY_PRESENT
Related Information
■ “System Chassis Components” on page 287
■ “Cooling Unit Components” on page 289
■ “Memory Device Components” on page 291
■ “Power Unit Components” on page 291
Component Name (Oracle ILOM CLI Targets) IPMI Type Description Values (if applicable)
/SYS/MB/P[0-x]/D[0-11] FRU Host CPU DIMM FRU
/SYS/MB/P[0-x]/D[0-11]/PRSNT Discrete Host CPU DIMM is 01h-ENTITY_ABSENT
sensor present.
02h-ENTITY_PRESENT
/SYS/MB/P[0-x]/D[0-11]/SERVICE Indicator Host CPU DIMM Fault- Color: Amber
Service Required LED
Location: Motherboard
Off: Normal
Related Information
■ “System Chassis Components” on page 287
■ “Cooling Unit Components” on page 289
■ “Disk Backplane Components” on page 290
■ “Power Unit Components” on page 291
■ “Processor Components” on page 293
■ “System Motherboard Components” on page 293
■ “System Firmware Components” on page 295
■ “Hard Disk Drive Components” on page 295
Component Name (Oracle ILOM CLI Targets) IPMI Type Description Values (if applicable)
/SYS/PS[0-1] FRU Power supply FRU
/SYS/PS[0-1]/PRSNT Discrete sensor Power supply is 01h-ENTITY_ABSENT
present.
02h-ENTITY_PRESENT
/SYS/PS[0-1]/STATE Discrete sensor Multistate, power Presence detected
supply sensor type, per
IPMI Failure detected
Predictive failure
Configuration error
/SYS/PS[0-1]/P_IN Power sensor Input power draw Watts
/SYS/PS[0-1]/P_OUT Power sensor Output power Watts
/SYS/PS[0-1]/V_IN Voltage sensor Input voltage Volts
/SYS/PS[0-1]/V_12V Voltage sensor 12V output voltage Volts
/SYS/PS[0-1]/V_12V_STBY Voltage sensor 12V standby output Volts
voltage
/SYS/PS[0-1]/T_IN Temperature sensor PSU input temperature Degrees Celsius
/SYS/PS[0-1]/T_OUT Temperature sensor PSU output Degrees Celsius
temperature
Related Information
Processor Components
Component Name (Oracle ILOM CLI IPMI Type Description Values (if applicable)
Targets)
/SYS/MB/P[0-x] FRU Host CPU FRU
/SYS/MB/P[0-x]/PRSNT Discrete sensor Host CPU is present. 01h-ENTITY_PRESENT
02h-ENTITY_ABSENT
/SYS/MB/P[0-x]/SERVICE Indicator Host CPU Fault-Service Color: Amber
Required LED
Location: Motherboard
Off: Normal
Related Information
■ “System Chassis Components” on page 287
■ “Cooling Unit Components” on page 289
■ “Disk Backplane Components” on page 290
■ “Memory Device Components” on page 291
■ “Power Unit Components” on page 291
■ “System Motherboard Components” on page 293
■ “System Firmware Components” on page 295
■ “Hard Disk Drive Components” on page 295
Component Name (Oracle ILOM CLI IPMI Type Description Values (if applicable)
Targets)
/SYS/MB FRU General host system motherboard
FRU
Component Name (Oracle ILOM CLI IPMI Type Description Values (if applicable)
Targets)
/SYS/MB/CPLD FRU Motherboard CPLD/FPGA firmware
version
/SYS/MB/NET[0-x] FRU Host Ethernet FRU
/SYS/MB/RISER[1-x]/PCIE[1-x] FRU PCIe slot
/SYS/MB/RISER[1-x]/PCIE[1-x]/PRSNT Discrete sensor PCIe slot is occupied. 01h-ENTITY_ABSENT
02h-ENTITY_PRESENT
/SYS/MB/T_OUT_SLOT[1-3] Threshold sensor Cooling zone chassis exhaust Degrees Celsius
temperature, located behind the
specified PCIe slots
On: SP is operating.
02h-ENTITY_PRESENT
/SYS/MB/RISER3/SSD[0-1] FRU Internal M.2 SSD drives
/SYS/MB/RISER3/SSD[0-1]/PRSNT Discrete sensor M.2 SSD drive presence 01h-ENTITY_ABSENT
02h-ENTITY_PRESENT
/SYS/MB/RISER3/SSD[0-1]/STATE State sensor M.2 SSD drive state sensor 04h-INSTALLED
20h-SLOT_POWER_OFF
Related Information
■ “System Chassis Components” on page 287
Related Information
■ “System Chassis Components” on page 287
■ “Cooling Unit Components” on page 289
■ “Disk Backplane Components” on page 290
■ “Memory Events” on page 305
■ “Power Unit Components” on page 291
■ “Processor Components” on page 293
■ “System Motherboard Components” on page 293
■ “Hard Disk Drive Components” on page 295
The following table lists the hard disk drive (HDD) components.
Component Name (Oracle ILOM CLI IPMI Type Description Values (if applicable)
Targets)
/SYS/DBP/HDD[0-x] FRU Hard disk drive FRU From host
Component Name (Oracle ILOM CLI IPMI Type Description Values (if applicable)
Targets)
/SYS/DBP/HDD[0-x]/PRSNT Discrete sensor Hard disk drive presence 01h-ENTITY_ABSENT
02h-ENTITY_PRESENT
/SYS/DBP/HDD[0-x]/STATE Discrete sensor Writable multistate, slot/connector 01h-FAULT_STATUS
sensor type, per IPMI
02h-IDENTITY
04h-INSTALLED
20h-SLOT_POWER_OFF
/SYS/DBP/HDD[0-x]/SERVICE Indicator Hard disk drive Fault-Service Color: Amber
Required LED
Location: HDD
Off: Normal
Location: HDD
Off: Normal
02h-ENTITY_PRESENT
Related Information
https://www.oracle.com/goto/ilom/docs
The tables in these sections list the set of SNMP traps that are generated from Oracle ILOM.
■ “Environmental Events” on page 297
■ “Hard Disk Drive Events” on page 299
■ “Power Events” on page 299
■ “Fan Events” on page 304
■ “Memory Events” on page 305
■ “Entity Presence Events” on page 306
Environmental Events
Severity and Description: Critical; A temperature sensor has reported that its value has gone /SYS/MB/T_IN_SLOT[1-3]
above an upper fatal threshold setting or below a lower fatal threshold setting.
/SYS/MB/T_OUT_SLOT[1-3]
The sunHwTrapThresholdType object indicates whether the threshold was an upper or lower
threshold.
SNMP Trap: sunHwTrapTempFatalThresholdDeasserted /SYS/PS[0-1]/T_OUT
Oracle ILOM Event Message: Lower fatal threshold no longer exceeded /SYS/PS[0-1]/T_IN
Severity and Description: Informational; A temperature sensor has reported that its value has /SYS/MB/T_IN_SLOT[1-3]
gone below an upper fatal threshold setting or above a lower fatal threshold setting.
/SYS/MB/T_OUT_SLOT[1-3]
The sunHwTrapThresholdType object indicates whether the threshold was an upper or lower
threshold.
Severity and Description: Critical; A temperature sensor has reported that its value has gone /SYS/MB/T_IN_SLOT[1-3]
above an upper critical threshold setting or below a lower critical threshold setting.
/SYS/MB/T_OUT_SLOT[1-3]
The sunHwTrapThresholdType object indicates whether the threshold was an upper or lower
threshold.
SNMP Trap: sunHwTrapTempCritThresholdDeasserted /SYS/PS[0-1]/T_OUT
Oracle ILOM Event Message: Upper critical threshold no longer exceeded /SYS/PS[0-1]/T_IN
Severity and Description: Informational; A temperature sensor has reported that its value has /SYS/MB/T_IN_SLOT[1-3]
gone below an upper critical threshold setting or above a lower critical threshold setting.
/SYS/MB/T_OUT_SLOT[1-3]
The sunHwTrapThresholdType object indicates whether the threshold was an upper or lower
threshold.
SNMP Trap: sunHwTrapTempFatalThresholdExceeded /SYS/T_AMB
Severity and Description: Critical; A temperature sensor has reported that its value has gone
above an upper fatal threshold setting or below a lower fatal threshold setting.
The sunHwTrapThresholdType object indicates whether the threshold was an upper or lower
threshold.
SNMP Trap: sunHwTrapTempFatalThresholdDeasserted /SYS/T_AMB
Severity and Description: Informational; A temperature sensor has reported that its value has
gone below an upper fatal threshold setting or above a lower fatal threshold setting.
The sunHwTrapThresholdType object indicates whether the threshold was an upper or lower
threshold.
Related Information
Severity and Description: Major: A sensor associated with a slot or connector has detected an error.
SNMP Trap: sunHwTrapSlotOrConnectorOk /SYS/DBP/HDD[0-x]/STATE
Severity and Description: Informational; A sensor associated with a slot or connector has returned
to its normal state.
Related Information
■ “System Chassis Components” on page 287
■ “Cooling Unit Components” on page 289
■ “Disk Backplane Components” on page 290
■ “Memory Device Components” on page 291
■ “Power Unit Components” on page 291
■ “Processor Components” on page 293
■ “System Motherboard Components” on page 293
■ “Hard Disk Drive Components” on page 295
Power Events
Severity and Description: Major; A power supply sensor has detected an error.
SNMP Trap: sunHwTrapPowerSupplyOk /SYS/PS[0-1]/STATE
Severity and Description: Major; A power supply sensor has detected an error.
SNMP Trap: sunHwTrapPowerSupplyError /SYS/PS[0-1]/STATE
Severity and Description: Major; A power supply sensor has detected an error.
SNMP Trap: sunHwTrapPowerSupplyOk /SYS/PS[0-1]/STATE
Severity and Description: Major; A power supply sensor has detected an error.
SNMP Trap: sunHwTrapPowerSupplyError /SYS/PS[0-1]/STATE
Severity and Description: Major; A power supply sensor has detected an error.
SNMP Trap: sunHwTrapPowerSupplyOk /SYS/PS[0-1]/STATE
Severity and Description: Major; A power supply sensor has detected an error.
SNMP Trap: sunHwTrapPowerSupplyError /SYS/PS[0-1]/STATE
Severity and Description: Major; A power supply sensor has detected an error.
SNMP Trap: sunHwTrapPowerSupplyOk /SYS/PS[0-1]/STATE
Severity and Description: Major; A power supply sensor has detected an error.
SNMP Trap: sunHwTrapPowerSupplyError /SYS/PS[0-1]/STATE
Severity and Description: Major; A power supply sensor has detected an error.
SNMP Trap: sunHwTrapPowerSupplyOk /SYS/PS[0-1]/STATE
Severity and Description: Major; A power supply sensor has detected an error.
SNMP Trap: sunHwTrapPowerSupplyError /SYS/PS[0-1]/STATE
Severity and Description: Major; A power supply sensor has detected an error.
SNMP Trap: sunHwTrapPowerSupplyOk /SYS/PS[0-1]/STATE
Severity and Description Major; A power supply sensor has detected an error.
SNMP Trap: sunHwTrapPowerSupplyOk /SYS/PS[0-1]/STATE
Severity and Description: Major; A power supply sensor has detected an error.
SNMP Trap: sunHwTrapSensorNonCritThresholdExceeded /SYS/VPS
Severity and Description: Minor; A sensor has reported that its value has gone above an upper
non critical threshold setting or below a lower non critical threshold setting. This generic 'sensor'
trap is generated when the SNMP agent does not recognize the component type.
The sunHwTrapThresholdType object indicates whether the threshold was an upper or lower
threshold.
SNMP Trap: sunHwTrapSensorThresholdOk /SYS/VPS
Severity and Description: Informational; A sensor has reported that its value is in the normal
operating range. This generic 'sensor' trap is generated when the SNMP agent does not recognize
the component type.
SNMP Trap: sunHwTrapSensorNonCritThresholdExceeded /SYS/VPS_FANS
Severity and Description: Minor; A sensor has reported that its value has gone above an upper /SYS/PS[0-1]/P_OUT
noncritical threshold setting or below a lower noncritical threshold setting. This generic 'sensor'
trap is generated when the SNMP agent does not recognize the component type.
The sunHwTrapThresholdType object indicates whether the threshold was an upper or lower
threshold.
SNMP Trap: sunHwTrapSensorThresholdOk /SYS/VPS_FANS
Oracle ILOM Event Message: Upper noncritical threshold no longer exceeded /SYS/PS[0-1]/P_IN
Severity and Description: Informational; A sensor has reported that its value is in the normal /SYS/PS[0-1]/P_OUT
operating range. This generic 'sensor' trap is generated when the SNMP agent does not recognize
the component type.
SNMP Trap: sunHwTrapSensorFatalThresholdExceeded /SYS/PS[0-1]/P_IN
Severity and Description: Critical; A power supply sensor has reported that its value has gone
above an upper fatal threshold setting or below a lower fatal threshold setting.
Oracle ILOM Event Message: Lower fatal threshold no longer exceeded /SYS/PS[0-1]/P_OUT
Severity and Description: Informational; A power supply sensor has reported that its value has
gone below an upper fatal threshold setting or above a lower fatal threshold setting.
The sunHwTrapThresholdType object indicates whether the threshold was an upper or lower
threshold.
SNMP Trap: sunHwTrapSensorCritThresholdExceeded /SYS/PS[0-1]/P_IN
Severity and Description: Major; A power supply sensor has reported that its value has gone
above an upper critical threshold setting or below a lower critical threshold setting.
The sunHwTrapThresholdType object indicates whether the threshold was an upper or lower
threshold.
SNMP Trap: sunHwTrapSensorCritThresholdDeasserted /SYS/PS[0-1]/P_IN
Oracle ILOM Event Message: Lower critical threshold no longer exceeded /SYS/PS[0-1]/P_OUT
Severity and Description: Informational; A power supply sensor has reported that its value has
gone below an upper critical threshold setting or above a lower critical threshold setting.
The sunHwTrapThresholdType object indicates whether the threshold was an upper or lower
threshold.
SNMP Trap: sunHwTrapVoltageFatalThresholdExceeded /SYS/PS[0-1]/V_12V
Severity and Description: Critical; A voltage sensor has reported that its value has gone above /SYS/PS[0-1]/V_IN
an upper fatal threshold setting or below a lower fatal threshold setting.
The sunHwTrapThresholdType object indicates whether the threshold was an upper or lower
threshold.
SNMP Trap: sunHwTrapVoltageFatalThresholdDeasserted /SYS/PS[0-1]/V_12V
Oracle ILOM Event Message: Lower fatal threshold no longer exceeded /SYS/PS[0-1]/V_12V_STBY
Severity and Description: Informational; A voltage sensor has reported that its value has gone /SYS/PS[0-1]/V_IN
below an upper fatal threshold setting or above a lower fatal threshold setting.
The sunHwTrapThresholdType object indicates whether the threshold was an upper or lower
threshold.
SNMP Trap: sunHwTrapVoltageCritThresholdExceeded /SYS/PS[0-1]/V_12V
Severity and Description: Critical; A voltage sensor has reported that its value has gone above /SYS/PS[0-1]/V_IN
an upper critical threshold setting or below a lower critical threshold setting.
Oracle ILOM Event Message: Upper critical threshold no longer exceeded /SYS/PS[0-1]/V_12V_STBY
Severity and Description: Informational; A voltage sensor has reported that its value has gone /SYS/PS[0-1]/V_IN
below an upper critical threshold setting or above a lower critical threshold setting.
The sunHwTrapThresholdType object indicates whether the threshold was an upper or lower
threshold.
SNMP Trap: sunHwTrapVoltageNonCritThresholdExceeded /SYS/PS[0-1]/V_12V
Severity and Description: Minor; A voltage sensor has reported that its value has gone above an /SYS/PS[0-1]/V_IN
upper noncritical threshold setting or below a lower noncritical threshold setting.
The sunHwTrapThresholdType object indicates whether the threshold was an upper or lower
threshold.
SNMP Trap: sunHwTrapVoltageOk /SYS/PS[0-1]/V_12V
Oracle ILOM Event Message: Upper noncritical threshold no longer exceeded /SYS/PS[0-1]/V_12V_STBY
Severity and Description: Informational; A voltage sensor has reported that its value is in the /SYS/PS[0-1]/V_IN
normal operating range.
SNMP Trap: sunHwTrapSensorNonCritThresholdExceeded /SYS/VPS_CPUS
Severity and Description: Minor; A sensor has reported that its value has gone above an upper
noncritical threshold setting or below a lower noncritical threshold setting. This generic 'sensor'
trap is generated when the SNMP agent does not recognize the component type.
The sunHwTrapThresholdType object indicates whether the threshold was an upper or lower
threshold.
SNMP Trap: sunHwTrapSensorThresholdOk /SYS/VPS_CPUS
Oracle ILOM Event Message: Upper noncritical threshold no longer exceeded /SYS/VPS_MEMORY
Severity and Description: Informational; A sensor has reported that its value is in the normal
operating range. This generic 'sensor' trap is generated when the SNMP agent does not recognize
the component type.
Related Information
■ “System Chassis Components” on page 287
■ “Cooling Unit Components” on page 289
■ “Disk Backplane Components” on page 290
■ “Memory Device Components” on page 291
Fan Events
Severity and Description: Major; A fan speed sensor has reported that its value has gone above
an upper critical threshold setting or below a lower critical threshold setting.
The sunHwTrapThresholdType object indicates whether the threshold was an upper or lower
threshold.
SNMP Trap: sunHwTrapFanSpeedCritThresholdDeasserted /SYS/MB/FM[0-3]/F[0-x]/TACH
Severity and Description: Informational; A fan speed sensor has reported that its value has gone
below an upper critical threshold setting or above a lower critical threshold setting.
The sunHwTrapThresholdType object indicates whether the threshold was an upper or lower
threshold.
SNMP Trap: sunHwTrapFanSpeedFatalThresholdExceeded /SYS/MB/FM[0-3]/F[0-x]/TACH
Severity and Description: Critical; A fan speed sensor has reported that its value has gone above
an upper fatal threshold setting or below a lower fatal threshold setting.
The sunHwTrapThresholdType object indicates whether the threshold was an upper or lower
threshold.
SNMP Trap: sunHwTrapFanSpeedFatalThresholdDeasserted /SYS/MB/FM[0-3]/F[0-x]/TACH
Severity and Description: Informational; A fan speed sensor has reported that its value has gone
below an upper fatal threshold setting or above a lower fatal threshold setting.
The sunHwTrapThresholdType object indicates whether the threshold was an upper or lower
threshold.
Related Information
Memory Events
Severity and Description: Informational; A memory component fault has been cleared.
SNMP Trap: sunHwTrapMemoryFault /SYS/MB
Severity and Description: Informational; A memory component fault has been cleared.
Related Information
■ “System Chassis Components” on page 287
■ “Cooling Unit Components” on page 289
■ “Disk Backplane Components” on page 290
■ “Memory Device Components” on page 291
■ “Power Unit Components” on page 291
■ “Processor Components” on page 293
■ “System Motherboard Components” on page 293
■ “Hard Disk Drive Components” on page 295
Severity and Description: Major; A processor sensor has detected an error. Device absent.
SNMP Trap: sunHwTrapProcessorOk /SYS/MB/P[0-x]/PRSNT
Severity and Description: Major; A processor sensor has returned to its normal state. Device
present.
SNMP Trap: sunHwTrapProcessorError /SYS/MB/P[0-x]/PRSNT
Severity and Description: Major; A processor sensor has detected an error. Device disabled.
SNMP Trap: sunHwTrapProcessorOk /SYS/MB/P[0-x]/PRSNT
Severity and Description: Major; A processor sensor has returned to its normal state. Device
enabled.
Related Information
■ “System Chassis Components” on page 287
B C
battery cable part number
description, 21 NVMe cables, 190
installing, 135 SAS cables, 182
removing, 133 cables
BIOS data and power
Ethernet ports booting priority, 44 connecting, 216
BIOS factory defaults, verifying, 232 disconnecting, 59
BIOS Setup Utility cabling the server, 40
accessing, 227 chassis components, 287
Advanced screen, 260 chassis serial number, locating, 47
Boot screen, 280 components and nomenclature, 287
Exit screen, 282 connecting devices to server, 39
exiting from, 253 connector locations, 39
function keys, 226 cooling
IO screen, 276 troubleshooting issues, 34
Main screen, 255 cooling unit components, 289
menus, accessing, 227
navigating menu options, 228
setup screens summary, 226 D
shortcut key sequences, 226 diagnostics
TPM support, 234 available tools, 38
UEFI BIOS, 230 documentation, 39
309
Index
H replacing, 169
hard disk drive components, 295 internal M.2 flash SSDs
hard disk drive events, 299 description, 21
hard drives See storage drives internal USB flash drive
hardware faults description, 21
diagnosing, 27 installing, 94
HBA super capacitor removing, 93
installing, 173 IO allocation
removing, 170 enabling and disabling resources, 239
replacing, 169 IO BIOS screen, 276
hot-plugging storage drives, 65 IPMI type, 286
I L
identifying Simple Network Management Protocol latch release button
(SNMP) Trap messages, 297 storage drive, 69, 72, 76
illustrated parts breakdown, 19 LED indicator module
installing components description, 22
battery, 135 LEDs
DIMMs, 108 boot drive, 31
disk backplane cables, 196 power supply, 31, 88, 88
fan modules, 84 storage drive, 31
FIM, 159 system status, 29
FIM cable, 196 Locate Button/LED, 29
HBA super capacitor, 173 locating chassis serial number, 47
internal HBA card, 173
internal USB flash drive, 94
M.2 flash SSD, 131 M
M.2 mezzanine, 129 M.2 flash SSD
motherboard assembly, 206 installing, 131
NVMe cables, 189 removing, 130
PCIe risers, 114, 118 M.2 mezzanine
power cable, 196 installing, 129
power supply, 90 removing, 127
processors, 144 Main BIOS screen, 255
SAS cable assembly, 182 memory See DIMMs
server into rack, 213 memory device components, 291
storage drives, 70, 73, 77 memory events, 305
temperature sensor, 166 menus, BIOS Setup Utility, 227
temperature sensor cable, 196 motherboard assembly
internal HBA card description, 22
installing, 173 installing, 206
removing, 170 removing, 199
311
Index
313
Index
T
technical support, 46
temperature sensor
installing, 166
removing, 163
replacing, 163
temperature sensor cable
installing, 196
removing, 194
servicing, 193
tools required, 52
troubleshooting
information when contacting support, 46
overview, 37
server, 23
using diagnostic tools, 37
using LED status indicators, 28
using Oracle ILOM, 23
Trusted Execution Technology (TXT)