Sun Microsystems, Inc.  Oracle System Handbook - ISO 7.0 May 2018 Internal/Partner Edition
   Home | Current Systems | Former STK Products | EOL Systems | Components | General Info | Search | Feedback

Asset ID: 1-79-1616903.1
Update Date:2018-03-26
Keywords:

Solution Type  Predictive Self-Healing Sure

Solution  1616903.1 :   Sun Server X3-2 (formerly Sun Fire X4170 M3) Symptoms and Solutions  


Related Items
  • Sun Server X3-2
  •  
Related Categories
  • PLA-Support>Sun Systems>x86>Server>SN-x86: Sun Server X3
  •  




In this Document
Purpose
Details
References


Applies to:

Sun Server X3-2 - Version All Versions to All Versions [Release All Releases]
Information in this document applies to any platform.

Purpose

 This document outlines the top non-hardware issues our customers encounter on the Sun Server X3-2 (formerly Sun Fire X4170 M3), with the firmware version which fixes that issue or the workaround


These issues are outlined in more detail on the internal Sun Server X3-2 and X3-2L (Sun Fire X4170 M3, X4270 M3) Current Product Issues <Document: 1437822.1> page

Details

Documentation X3-2  -  Patches&Firmware X3-2  -  My Oracle Support Community (MOSC) Sun x86 Systems  -  Oracle System Handbook X3-2

 

SymptomDetailsResolution/Workaround

Boot failures with FMA fault Event "SPX86-8003-UC - IIO VT-d Fatal Error" seen when 3rd party USB devices are installed.

This issue was specifically observed on systems using a 3rd party KVM switch.

With an affected USB device attached the system will fail to boot and FMA may fault the CPU with an SPX86-8003-UC event. For example:


fault = fault.io.intel.iio.vtd-fatal@/SYS/MB/P0

Workaround: If this issue is experienced remove the USB device and clear the fault to allow the system to boot.

Resolution: Update system to the latest ILOM firmware (SW 1.4.0 or later)

ILOM Java Remote Console no longer works after upgrade to Java 7 update 40 and above

After upgrading Java version 7 to upgrade 40 and above, the Java security settings changed and the ILOM console certificate on older systems is no longer acceptable to Java, so the console application will not open.

Workaround: Don't upgrade Java, or modify the security settings with exceptions, per MOS Doc ID 1614577.1

Resolution: Update system to the latest ILOM firmware (SW 1.3.0 or later)

Resetting ILOM may cause the host to hang. Possibly CPU faults may also occur at the same time during the boot after force resetting the host.

Host hung after ipmiflash completing reflashing ILOM, and ILOM shows following message repeatedly:

BTKCS Driver BT: "pod" Host timed out trying to write, ifc->host_busy @ 0x08

Host hang with blinking cursor on VGA output waiting for system to reboot

FMA may report: An internal fault on a processor has occurred

Workaround: Avoid unnecessary reboots of the ILOM SP. 

Resolution: Update system to the latest ILOM firmware (SW 1.2.1 or later)

If Power Management for the the system is disabled the server will experience a performance loss.

If the customer disables the "Power Technology" option in the BIOS it will cause the system to run the processors at their minimum clock frequency causing system performance loss.

Workaround: The Intel Power Technology option in the BIOS should be left enabled and all of the sub options should be left at their default settings.


Resolution: Update system to the latest ILOM firmware (SW 1.2.0 or later)

Systems may become warm and encounter a temperature warning when several are racked together and left in standby mode.

Temperature Warnings reported

SERVICE Alert LED on. SEL log output reports thermal alarms

FMA may show:  SPX86-8003-A4, fault.chassis.temp.warn

Workaround: Either unplug the systems if they are not going to be powered on or power the systems on so that the power supply fans can provide cooling.

Resolution: Update system to the latest ILOM firmware (SW 1.1.1 or later)


Attachments
This solution has no attachment
  Copyright © 2018 Oracle, Inc.  All rights reserved.
 Feedback