Troubleshooting and Diagnostics

2 Troubleshooting and Diagnostics

This section includes information about troubleshooting hardware component faults for the Oracle Server X9-2L. It contains the following topics:

For more information about server troubleshooting and dianostics, refer to the Oracle x86 Servers Diagnostics and Troubleshooting Guide at Oracle x86 Servers Administration, Diagnostics, and Applications Documentation.

Troubleshooting Server Component Hardware Faults

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

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 choose. When you become aware of a hardware fault, address it immediately.

To investigate a hardware fault, see the following:

Basic Troubleshooting Process

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).

Identify the server subsystem containing the fault.

You can use Oracle ILOM to identify the failed component.
Review the Oracle Server X9-2L Product Notes at Oracle Server X9-2L Documentation.

The product notes contain up-to-date information about the server, including hardware-related issues.
Prepare the server for service using Oracle ILOM.

If you determined that the hardware fault requires service (physical access to the server), use Oracle ILOM to take the server offline, activate the Locate button/LED, and if necessary, power off the server.
Prepare the service workspace.

Before servicing the server, prepare the workspace, ensuring Electrostatic Discharge Safety (ESD) protection for the server and components.

See Preparing for Service.
Service the components.

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

Note:
A component designated as a field-replaceable unit (FRU) must be replaced by Oracle Service personnel. Contact Oracle Service.
Clear the fault in Oracle ILOM.

Depending on the component, you might need to clear the fault in Oracle ILOM. Generally, components that have a FRU ID, clear the fault automatically.

Troubleshoot Hardware Faults Using the Oracle ILOM Web Interface

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.

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, you can perform the procedure 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.

Log in to the server SP Oracle ILOM web interface.
Open a browser and direct it using the IP address of the server SP. On the Login screen, enter a user name (with administrator privileges) and password. The Summary Information page appears.

The Status section of the Summary Information page provides information about the server subsystems, including:
- Processors
- Memory
- Power
- Cooling
- Storage
- Networking
- PCI Devices
- Firmware
In the Status section of the Oracle ILOM Summary Information page, identify the server subsystem that requires service.

For example, if a hardware component in the subsystem is in a fault state, the Status column notes the status as Service Required.
To identify the faulty component, click the component in the Status section.

The Oracle ILOM page showing the faulty component appears.
To get more information, click the Open Problems link.

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.
Before going to the server, review the Oracle Server X9-2L 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 Oracle Server X9-2L Documentation.
To prepare the server for service, see Preparing for Service.

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.
Service the component.

Troubleshooting and Diagnostic Information

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 at Oracle x86 Servers Administration, Diagnostics, and Applications Documentation
Oracle X9 Series Servers Administration Guide at Oracle x86 Servers Administration, Diagnostics, and Applications Documentation
Troubleshooting Using the Server Front and Back Panel Status Indicators
Managing Server Hardware Faults Through the Oracle ILOM Fault Management Shell

Troubleshooting Using the Server Front and Back Panel Status Indicators

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:

Front Panel Components

Back Panel Components and Cable Connections

Server Boot Process and Normal Operating State Indicators

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:

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.
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:

The System OK LED blinks slowly (0.5 seconds on, 0.5 seconds off), and the SP OK LED remains lit (no blinking).
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.

Server System-Level Status Indicators

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. The following table describes these indicators.

Status Indicator Name	Color	State and Meaning
Locate Button/LED	White	Indicates the location of the server. OFF – Server is operating normally. FAST BLINK (250 ms) – Use Oracle ILOM to activate this LED indicator to enable you to locate a particular system quickly and easily. Pressing the Locate button toggles the LED indicator fast blink on or off.
Fault-Service Required	Amber	Indicates the fault state of the server. OFF – The server is operating normally. STEADY ON – A fault is present on the server. This LED indicator lights whenever a fault indicator lights for a replaceable component on the server. Note: When this LED indicator is lit, a system console message might appear that includes a recommended service action.
System OK	Green	Indicates the operational state of the chassis. OFF – AC power is not present or the Oracle ILOM boot is not complete. STANDBY BLINK (on for 100 ms, off for 2900 ms) – Standby power is on, but the chassis power is off and the Oracle ILOM SP is running. SLOW BLINK (1000 ms) – Startup sequence was initiated on the host. This pattern begins soon after you power on the server. This status indicates either: power-on self-test (POST) code checkpoint tests are running on the server host system, or the host is transitioning from the powered-on state to the standby state on shutdown. STEADY ON – The server is powered on, and all host POST code checkpoint tests are complete. The server is in one of the following states: the server host is booting the operating system (OS), or the server host is running the OS.
SP OK	Green	Indicates the state of the service processor. OFF – Service processor (SP) is not running. SLOW BLINK – SP is booting. STEADY ON – SP is fully operational.
Top Fan	Amber	Indicates that one or more of the internal fan modules failed. OFF – Indicates steady state; no service is required. STEADY ON – Indicates service required.
Back Power Supply Fault	Amber	Indicates that one of the server power supplies failed. OFF – Indicates steady state; no service is required. STEADY ON – Indicates service required; service the power supply.
System Over Temperature Warning	Amber	Indicates a warning for an overtemperature condition. OFF – Normal operation; no service is required. STEADY ON – The system is experiencing an overtemperature warning condition. Note: This is a warning indication, not a fatal overtemperature. Failure to correct this might result in the system overheating and shutting down unexpectedly.
DO NOT SERVICE	White	Indicates that the system is not ready to service. OFF – Normal operation. STEADY ON – The system is not ready for service. Note: The DO NOT SERVICE indicator is application specific. This indicator is only illuminated on demand by the Host application.

Server Fan Status Indicators

Each fan module has one status indicator (LED). The LEDs are located on the chassis fan tray adjacent to and aligned with the fan modules, and are visible when the server top cover is removed.

Status Indicator Name	Icon	Color	State and Meaning
Fan Status		Amber	Off – The fan module is correctly installed and operating within specification. Amber – The fan module is faulty. The front TOP FAN LED and the front and back panel Fault-Service Required LEDs are also lit if the system detects a fan module fault.

Storage Drive Status Indicators

There are three status indicators (LEDs) on each drive.

Status Indicator Name	Color	State and Meaning
OK/Activity	Green	OFF – Power is off or installed drive is not recognized by the system. STEADY ON – The drive is engaged and is receiving power. RANDOM BLINK – There is disk activity. Status indicator LED blinks on and off to indicate activity.
Fault-Service Required	Amber	OFF – The storage drive is operating normally. STEADY ON – The system detected a fault with the storage drive.
OK to Remove	Blue	STEADY ON – The storage drive can be removed safely during a hot-plug operation. OFF – The storage drive is not prepared for removal.

Power Supply Status Indicators

There are two status indicators (LEDs) on each power supply. These indicators are visible from the back of the server.

Status Indicator Name	Icon	Color	State and Meaning
AC OK/ DC OK		Green	OFF – No AC power is present. SLOW BLINK – Normal operation. Input power is within specification. DC output voltage is not enabled. STEADY ON – Normal operation. Input AC power and DC output voltage are within specification.
Fault-Service Required		Amber	OFF – Normal operation. No service action is required. STEADY ON – The power supply (PS) detected a PS fan failure, PS overtemperature, PS overcurrent, or PS overvoltage or undervoltage.

Network Management Port Status Indicators

The server has one 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.

Status Indicator Name	Location	Color	State and Meaning
Activity	Top left	Green	ON – Link up. OFF – No link or down link. BLINKING – Packet activity.
Link speed	Top right	Green	ON – 1000BASE-T link. OFF – 100BASE-T link.

Ethernet Port Status Indicators

The server has one 100/1000BASE-T Gigabit Ethernet port (NET 0). There are two status indicators (LEDs) that are visible from the back of the server.

Status Indicator Name	Location	Color	State and Meaning
Activity	Bottom left	Green	ON – Link up. OFF– No activity. BLINKING – Packet activity.
Link speed	Bottom right	Bi-colored: Amber/Green	OFF – 100BASE-T link (if link up). Green ON – 1000BASE-T link.

Motherboard Status Indicators

The motherboard contains the following status indicators (LEDs).

Status Indicator	Description
DIMM Fault Status Indicators	Each 32 DIMM slot on the motherboard has an amber fault status indicator (LED) associated with it. If Oracle ILOM determines that a DIMM is faulty, pressing the Fault Remind button on the motherboard I/O card signals the service processor to light the fault LED associated with the failed DIMM. See Servicing the DIMMs (CRU).
Processor Fault Status Indicators	The motherboard includes a fault status indicator (LED) adjacent to each of the two processor sockets. These LEDs indicate when a processor fails. Pressing the Fault Remind button on the motherboard I/O card signals the service processor to light the fault status indicators associated with the failed processors. See Servicing Processors (FRU).
Fault Remind Status Indicator	This status indicator (LED) is located next to the Fault Remind button and is powered from the super capacitor that powers the fault LEDs on the motherboard. This LED lights to indicate that the fault remind circuitry is working properly in cases where no components failed and, as a result, none of the component fault LEDs illuminate. See Using the Server Fault Remind Button.
STBY PWRGD Status Indicator	This green status indicator (LED) is labeled STBY PWRGD and is located on the motherboard near the back of the server. This LED lights to inform a service technician that the motherboard is receiving Standby power from at least one of the power supplies. This LED helps prevent service actions on the server internal components while the AC power cords are installed and power is being supplied to the server.

Troubleshooting System Cooling Issues

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, you need to address overtemperature 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.

Cooling Issue	Description	Action	Prevention
External Ambient Temperature Too High	The server fans pull cool air into the server from its external environment. If the ambient temperature is too high, the internal temperature of the server and its components increases. This can cause poor performance and component failure.	Verify the ambient temperature of the server space against the environmental specifications for the server. If the temperature is not within the required operating range, remedy the situation immediately.	Periodically verify the ambient temperature of the server space to ensure that it is within the required range, especially if you made any changes to the server space (for example, added additional servers). The temperature must be consistent and stable.
Airflow Blockage	The server cooling system uses fans to pull cool air in from the server front intake vents and exhaust warm air out the server back panel vents. If the front or back vents are blocked, the airflow through the server is disrupted and the cooling system fails to function properly causing the server internal temperature to rise.	Inspect the server front and back panel vents for blockage from dust or debris. Inspect the server interior for improperly installed components or cables that can block the flow of air through the server.	Periodically inspect and clean the server vents using an ESD certified vacuum cleaner. Ensure that all components, such as cards, cables, fans, air baffles and dividers are properly installed. Never operate the server without the top cover installed.
Cooling Areas Compromised	The air baffle, component filler panels, and server top cover maintain and direct the flow of cool air through the server. These server components must be in place for the server to function as a sealed system. If these components are not installed correctly, the airflow inside the server can become chaotic and non-directional, which can cause server components to overheat and fail.	Inspect the server interior to ensure that the air baffle is properly installed. Ensure that all external-facing slots (storage drive, PCIe) are occupied with either a component or a component filler panel. Ensure that the server top cover is in place and sits flat and snug on top of the server.	When servicing the server, ensure that the air baffle is installed correctly and that the server has no unoccupied external-facing slots. Never operate the server without the top cover installed.
Hardware Component Failure	Components, such as power supplies and fan modules, are an integral part of the server cooling system. When one of these components fails, the server internal temperature can rise. This rise in temperature can cause other components to enter into an over-temperature state. Some components, such as processors, might overheat when they are failing, which can also generate an over-temperature event. To reduce the risk related to component failure, power supplies and fan modules are installed in pairs to provide redundancy. Redundancy ensures that if one component in the pair fails, the other functioning component can continue to maintain the subsystem.	Investigate the cause of the overtemperature event, and replace failed components immediately. See Troubleshooting Server Hardware Faults.	Component redundancy is provided to allow for component failure in critical subsystems, such as the cooling subsystem. However, once a component in a redundant system fails, the redundancy no longer exists, and the risk for server shutdown and component failures increases. Therefore, it is important to maintain redundant systems and replace failed components immediately.

Troubleshooting Power Issues

If your server does not power on, use the information in the following table to troubleshoot the issue.

Power Issue	Description	Action	Prevention
AC Power Connection	The AC power cords are the direct connection between the server power supplies and the power sources. The server power supplies need separate stable AC circuits. Insufficient voltage levels or fluctuations in power can cause server power problems. The power supplies operate at a particular voltage and within an acceptable range of voltage fluctuations. Refer to Electrical Requirements in Oracle Servers X9-2 and X9-2L Installation Guide.	Verify that both AC power cords are connected to the server Verify that the correct power is present at the outlets and monitor the power to verify that it is within the acceptable range. Verify proper connection and operation by verifying the power supply (PS) indicator panels, which are located at the back of the server on the power supplies. Lit green AC OK indicators indicate a properly functioning power supply. An amber AC OK indicator indicates that the AC power to the power supply is insufficient.	Use the AC power cord Velcro retaining clips and position the cords to minimize the risk of accidental disconnection. Ensure that the AC circuits that supply power to the server are stable and not overburdened.
Power Supplies (PSUs)	The server power supply units (PSUs) provide the necessary server voltages from the AC power outlets. If the power supplies are inoperable, unplugged, or disengaged from the internal connectors, the server cannot power on. Note: Use the Velcro straps on the back of the server to secure the power cord connectors to the back of the power supplies. The Velcro retaining straps minimize the risk of accidental disconnection.	Verify that the AC cables are connected to both power supplies. Verify that the power supplies are operational (the PSU indicator panel must have a lit green AC OK indicator). Ensure that the power supply is properly installed. A power supply that is not fully engaged with its internal connector does not have power applied and does not have a lit green AC OK indicator	When a power supply fails, replace it immediately. To ensure redundancy, the server has two power supplies. This redundant configuration prevents server downtime, or an unexpected shutdown, due to a failed power supply. The redundancy allows the server to continue to operate if one of the power supplies fails. However, when a server is being powered by a single power supply, the redundancy no longer exists, and the risk for downtime or an unexpected shutdown increases. When installing a power supply, ensure that it is fully seated and engaged with its connector inside the drive bay. A properly installed power supply has a lit green AC OK indicator.
Top Cover	The server top cover maintains the air pressures inside the server, prevents accidental exposure to hazardous voltages, and protects internal components from physical and environmental damage.	Do not operate the server without the top cover installed unless you are hot-plugging a fan module, and then ensure that you complete the operation and replace the cover within 60 seconds. See Servicing Fan Modules (CRU) and Install the Server Top Cover.	Be careful to avoid bending or otherwise warping the top cover.

Power Issue

Description

Action

Prevention

AC Power Connection

The AC power cords are the direct connection between the server power supplies and the power sources. The server power supplies need separate stable AC circuits. Insufficient voltage levels or fluctuations in power can cause server power problems. The power supplies operate at a particular voltage and within an acceptable range of voltage fluctuations. Refer to Electrical Requirements in Oracle Servers X9-2 and X9-2L Installation Guide.

Verify that both AC power cords are connected to the server
Verify that the correct power is present at the outlets and monitor the power to verify that it is within the acceptable range.
Verify proper connection and operation by verifying the power supply (PS) indicator panels, which are located at the back of the server on the power supplies. Lit green AC OK indicators indicate a properly functioning power supply. An amber AC OK indicator indicates that the AC power to the power supply is insufficient.

Use the AC power cord Velcro retaining clips and position the cords to minimize the risk of accidental disconnection. Ensure that the AC circuits that supply power to the server are stable and not overburdened.

Power Supplies (PSUs)

The server power supply units (PSUs) provide the necessary server voltages from the AC power outlets. If the power supplies are inoperable, unplugged, or disengaged from the internal connectors, the server cannot power on.

Note: Use the Velcro straps on the back of the server to secure the power cord connectors to the back of the power supplies. The Velcro retaining straps minimize the risk of accidental disconnection.

Verify that the AC cables are connected to both power supplies.
Verify that the power supplies are operational (the PSU indicator panel must have a lit green AC OK indicator).

Ensure that the power supply is properly installed. A power supply that is not fully engaged with its internal connector does not have power applied and does not have a lit green AC OK indicator

When a power supply fails, replace it immediately. To ensure redundancy, the server has two power supplies. This redundant configuration prevents server downtime, or an unexpected shutdown, due to a failed power supply. The redundancy allows the server to continue to operate if one of the power supplies fails. However, when a server is being powered by a single power supply, the redundancy no longer exists, and the risk for downtime or an unexpected shutdown increases. When installing a power supply, ensure that it is fully seated and engaged with its connector inside the drive bay. A properly installed power supply has a lit green AC OK indicator.

Top Cover

The server top cover maintains the air pressures inside the server, prevents accidental exposure to hazardous voltages, and protects internal components from physical and environmental damage.

Do not operate the server without the top cover installed unless you are hot-plugging a fan module, and then ensure that you complete the operation and replace the cover within 60 seconds. See Servicing Fan Modules (CRU) and Install the Server Top Cover.

Be careful to avoid bending or otherwise warping the top cover.

Managing Server Hardware Faults Through the Oracle ILOM Fault Management Shell

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 5.0.x at Oracle Integrated Lights Out Manager (ILOM) 5.0 Documentation.

Troubleshooting With Diagnostic Tools

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

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.

Diagnostic Tool	Type	What It Does	Accessibility	Remote Capability
Oracle ILOM	SP firmware	Monitors environmental condition and component functionality sensors, generates alerts, performs fault isolation, and provides remote access.	Can function in either Standby power mode or Main power mode and is not OS dependent.	Remote and local access.
Hardware-based LED indicators	Hardware and SP firmware	Indicates status of overall system and particular components.	Available when system power is available.	Local, but sensor and indicators are accessible from Oracle ILOM web interface or command-line interface (CLI).
Power-On Self-Test (POST)	Host firmware	Tests core components of system: CPUs, memory, and motherboard I/O bridge integrated circuits.	Runs on startup. Available when the operating system is not running.	Local, but can be accessed through Oracle ILOM Remote System Console Plus.
UEFI Diagnostics	SP firmware	Tests and detects problems on all processors, memory, disk drives, and network ports.	Use either the Oracle ILOM web interface or the command-line interface (CLI) to run UEFI diagnostics.	Remote access through Oracle ILOM Remote System Console Plus.
Oracle ILOM SP/Diag shell	SP firmware	Allows you to run HWdiag commands to check the status of a system and its components, and access HWdiag logs.	Can function on Standby power and when operating system is not running.	Local, but remote serial access is possible if the SP serial port is connected to a network-accessible terminal server.
Oracle Solaris commands	Operating system software	Displays various kinds of system information.	Requires operating system.	Local, and over network.
Oracle Linux commands	Operating system software	Displays various kinds of system information.	Requires operating system.	Local, and over network.
Oracle VTS	Diagnostic tool standalone software	Exercises and stresses the system, running tests in parallel.	Requires the Solaris operating system. Install Oracle VTS software separately.	View and control over network.

Diagnostic Tool Documentation

The following table identifies where you can find documentation for more information about diagnostic tools.

Diagnostic Tool	Documentation	Location
Oracle ILOM	Oracle Integrated Lights Out Manager 5.0 Documentation Library	Oracle Integrated Lights Out Manager (ILOM) 5.0 Documentation
UEFI Diagnostics or HWdiag	Oracle x86 Servers Diagnostics and Troubleshooting Guide	Oracle x86 Servers Administration, Diagnostics, and Applications Documentation
System indicators and sensors	This document	Troubleshooting Using the Server Front and Back Panel Status Indicators
Oracle VTS	Oracle VTS software and documentation	Oracle VTS 8.2.0 Documentation Library

Attaching Devices to the Server

The following sections contain procedures for attaching devices to the server so you can access diagnostic tools when troubleshooting and servicing the server:

Attach Devices to 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.

Connect an Ethernet cable to the Gigabit Ethernet (NET 0) connector as needed for OS support.

See Back Panel Connector Locations.
To connect to the Oracle ILOM service processor over the network, connect an Ethernet cable to the Ethernet port labeled NET MGT.

See Back Panel Connector Locations.
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.

Back Panel Connector Locations

The following illustration shows and describes the locations of the back panel connectors. Use this information to set up the server, so that you can access diagnostic tools and manage the server during service.

Figure showing back panel cable connections and ports.

Callout	Cable Port or Expansion Slot	Description
1	Power supply 0 input power Power supply 1 input power	The server has two power supply connectors, one for each power supply. Do not attach power cables to the power supplies until you finish connecting the data cables to the server. The server goes into Standby power mode, and the Oracle ILOM service processor initializes when the AC power cables are connected to the power source. System messages might be lost after 60 seconds if the server is not connected to a terminal, PC, or workstation. Note: Oracle ILOM signals a fault on any installed power supply that is not connected to an AC power source, as it might indicate a loss of redundancy.
2	Network management port (NET MGT)	The service processor NET MGT port is the optional connection to the Oracle ILOM service processor. The NET MGT port is configured by default to use Dynamic Host Configuration Protocol (DHCP). The service processor NET MGT port uses an RJ-45 cable for a 100/1000BASE-T connection.
3	Ethernet port (NET 0)	The Ethernet port enables you to connect the system to the network. The Ethernet port uses an RJ-45 cable for a 100/1000BASE-T connection.
4	USB port	The USB port supports hot-plugging. You can connect and disconnect a USB cable or a peripheral device while the server is running without affecting system operations.
5	Serial management port (SER MGT)	The service processor SER MGT port uses an RJ-45 cable and terminal (or emulator) to provide access to the Oracle ILOM command-line interface (CLI). Using Oracle ILOM, you can configure it to connect to the system console. Note: The serial management port does not support network connections.

Configuring Serial Port Sharing

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) 5.0 Documentation Library at Oracle Integrated Lights Out Manager (ILOM) 5.0 Documentation.

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

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

Where ipaddress is the IP address of the server SP.

For more information, see Accessing Oracle ILOM in Oracle X9 Series Servers Administration Guide at Oracle x86 Servers Administration, Diagnostics, and Applications Documentation.

The Oracle ILOM CLI prompt (->) appears.
To set the serial port owner, type:

-> set System/SP/serial/portsharing owner=host

Note:
The serial port sharing value, by default, is owner=SP.
Connect a serial host to the server.

Assign Serial Port Output Using the Oracle ILOM Web Interface

Log in to the SP Oracle ILOM web interface.

Open a web browser and direct it using the IP address of the server SP. Log in as root or a user with administrator privileges. See Accessing Oracle ILOM in Oracle X9 Series Servers Administration Guide at Oracle x86 Servers Administration, Diagnostics, and Applications Documentation.
On the Summary Information page, select ILOM Administration → Connectivity from the navigation menu on the left side of the screen.
Select the Serial Port tab.

Note:
The serial port sharing setting, by default, is Service Processor.
On the Serial Port Settings page, select Host Server as the serial port owner.
Click Save for the changes to take effect.
Connect a serial host to the server.

Server Operating System Names for the NVMe Storage Drives

If NVMe storage drives are installed in the server front panel, they are labeled NVMe0 through NVMe11. The server operating systems assign these storage drives different names. For the corresponding names assigned by the operating systems, see the following table. The drive names provided in the table assume that:

Oracle Retimer card is installed in PCIe slot 10 and the cabling to the disk backplane is correct
NVMe cabling between the motherboard and the disk backplane is correct

Storage Drive Labels	Names Assigned by the Server Operating Systems
NVMe0	PCIe Slot 100
NVMe1	PCIe Slot 101
NVMe2	PCIe Slot 102
NVMe3	PCIe Slot 103
NVMe4	PCIe Slot 104
NVMe5	PCIe Slot 105
NVMe6	PCIe Slot 106
NVMe7	PCIe Slot 107
NVMe8	PCIe Slot 108
NVMe9	PCIe Slot 109
NVMe10	PCIe Slot 110
NVMe11	PCIe Slot 111

Ethernet Device Naming

This section contains information about the device naming for the one 10-Gigabit Ethernet port (labeled NET 0) on the back panel of the server. See Back Panel Connector Locations.

Ethernet Port Device Naming

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. The device 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 be different from the names in the following table, depending on which devices are installed in the system.

Port	Oracle Solaris	Oracle Linux 7 and 8	Windows (example default name, see note below)
Net 0	igb0	eno1	Ethernet

Note:

For Windows, a port name such as Ethernet is 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.

MAC Address Mapping to Ethernet Ports

A system serial label that displays the MAC ID (and the associated barcode) for the server is attached to the top, front left side of the Oracle Server X9-2L server disk cage bezel.

This MAC ID (and barcode) corresponds to a hexadecimal (base 16) MAC address for a sequence of six consecutive MAC addresses. These six MAC addresses correspond to the server network ports, as shown in the following table.

Base MAC Address	Corresponding Ethernet Port
“base” + 0	NET 0
“base” + 1	Unassigned
“base” + 2	Unassigned
“base” + 3	Unassigned
“base” + 4	SP (NET MGT)
“base” + 5	Used only when Network Controller-Sideband Interface (NC-SI) sideband management is configured.

Back Panel Pinhole Switch

Oracle Service personnel might instruct you to use the back panel pinhole switch to reset the SP, as shown in the following figure.

Figure showing the location of the SP Reset pinhole switch on the server back panel.

Callout	Icon	Description
1		SP Reset

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 do not solve your problem, use the following table to collect information that you might need to communicate to Oracle Support.

System Configuration Information Needed	Your Information
Service contract number
System model
Operating environment
System serial number
Peripherals attached to the system
Email address and phone number for you and a secondary contact
Street address where the system is located
Superuser password
Summary of the problem and the work being done when the problem occurred
Other Useful Information
IP address
Server name (system host name)
Network or internet domain name
Proxy server configuration

Locating the Chassis Serial Number

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.
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.
Using Oracle ILOM:
- From the web interface, view the serial number on the System Information screen.
- From the command-line interface (CLI), type the command: show /System

Auto Service Requests

Oracle Auto Service Requests (ASR) is available at no additional cost to customers with Oracle Premier Support. 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 at My Oracle Support. 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 diagnostics 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.

For more information about Oracle ASR, go to Oracle Premier Support.