JavaScript is required to for searching.
Skip Navigation Links
Exit Print View
Sun Server X3-2 (formerly Sun Fire X4170 M3)

Product Notes, Version 1.2.1

search filter icon
search icon

Document Information

Using This Documentation

Getting the Latest Software and Firmware

About This Documentation

Related Documentation

Feedback

Support and Accessibility

Sun Server X3-2 Product Notes

Sun Server X3-2 Name Change

Supported Hardware

Supported Firmware Versions

Supported Operating Systems

Important Operating Notes

Operational Changes for UEFI BIOS Configuration

Single-Processor to Dual-Processor Upgrade Is Not Supported

Update Your System to the Latest Software Release

Avoid Overwriting the Embedded Oracle System Assistant USB Flash Drive

Oracle Solaris 10 8/11 Required Patches

Preinstalled Oracle VM Server and Oracle VM Manager Compatibility Requirements

Supported Operating System Limitations

Update HBA Firmware to Support UEFI BIOS

Segfaults Might Occur on Servers Running 64-bit Linux Operating Systems

Failure of a Single Server Fan Module Might Impact Performance

Standby Over-temperature Protection

MAC Address Mapping to Ethernet Ports

Inspect Grounding Strap on 3.5-inch HDD Bracket Before Installing

Battery Module

Server Management Tools

Supported PCIe Cards

Resolved Issues

Resolved Issue for This Software Release

Resolved Issues for Previous Software Releases

Known Issues

Hardware Known Issues

Oracle Solaris Operating System Known Issues

Linux Operating Systems and Virtual Machine Known Issues

Oracle System Assistant Known Issues

Documentation Known Issues

Software Release 1.2.1 Documentation Incorrectly Implies Ability to Set RAID Volume as Global Hot Spare

Cautions Statements Added to the Sun Server X3-2 Service Manual

Correction to the Version of the Oracle VM Server Software Preinstalled on the Server

Note Changed to Caution Statement in the Sun Server X3-2 Installation Guide for Oracle VM

Corrections to the Sun Server X3-2 Installation Guide for Linux Operating Systems

Incorrect Layout of the Sun Server X3-2 Front Panel Controls and Indicators Documented in the Sun Server X3-2 Installation Guide and the Sun Server X3-2 Service Manual

Sun Server X3-2 Installation Guide Updated to Include Configuration Instructions for the Oracle Linux Operating System Preinstalled on the Server

Sun Server X3-2 Service Manual Updated to Include URLs to the Sun Server X3-2 Service Animations

Operating Altitude Limits for China Markets

Translated Documents Use Abbreviated Titles

Incorrect Server Name in the Printed Getting Started Guide

Getting Server Firmware and Software

Firmware and Software Updates

Firmware and Software Access Options

Available Software Release Packages

Accessing Firmware and Software

Download Firmware and Software Using My Oracle Support

Requesting Physical Media

Gathering Information for the Physical Media Request

Installing Updates

Installing Firmware

Installing Hardware Drivers and OS Tools

Oracle Solaris Operating System Known Issues

Table 9 Oracle Solaris Operating System Known Open Issues

BugDB
Description
15762166 (formerly CR 7123018)
When using a text installer to install Oracle Solaris 11 11/11 to a 3-terabyte (3-TB) HDD, accepting the installation program default for disk partitioning will result in a failed installation.
Issue:

Note - This issue does not apply to DVD-based installs or installs performed using the Automated Installer (AI). This issue only affects text-based installs.


When installing Oracle Solaris 11 11/11 onto a 3-TB hard disk drive (HDD), the Oracle Solaris 11 11/11 text installer presents this misleading default to the installer: “Use the whole disk.” This default setting seems to be acceptable because other user messages in the installation program indicate that only 2-TB of the HDD will be used.

If this default setting is accepted, the installation program mistakenly loads Oracle Solaris 11 11/11 onto the entire 3-TB HDD, instead of a 2-TB partition, and the installation fails.


Note - Installing Oracle Solaris 11 11/11 to the entire 3-TB HDD requires support for Unified Extensible Firmware Interface (UEFI) BIOS and Oracle Solaris 11 11/11 does not support UEFI BIOS.


Affected software:
  • Oracle Solaris 11 11/11

  • Releases 1.0, 1.1, 1.1.1, and 1.2


Note - This issue does not affect Oracle Solaris 11.1


Workaround:

For text installs, in the Fdisk Partition screen, when prompted, select Use a partition of the disk, instead of Use the whole disk.

15755307 (formerly CR 7112301)
Xorg GUI might fail to start with certain hardware configurations under Oracle Solaris 11 11/11.
Issue:

Note - This issue is fixed in Support Repository Update (SRU) 5 for Oracle Solaris 11 11/11. If you have installed SRU 5, you will not experience this problem.


Systems containing SR-IOV capable devices in certain configurations might encounter problems with the X11 Xorg graphical user interface (GUI) not starting on startup. Systems running the Oracle Solaris 11 11/11 preinstalled operating system software will already contain the workaround for this issue. However, if you do a new installation using the Oracle Solaris 11 11/11 distribution media and observe the X11 GUI failing to start, you will have to perform the workaround described below.

Affected software:
  • Oracle Solaris 11 11/11

  • Releases 1.0, 1.1, 1.1.1, and 1.2


Note - This issue does not affect Oracle Solaris 11.1


15755307 (formerly CR 7112301) (Continued)
Workaround:

If you are doing a GUI-based install of Oracle Solaris 11 11/11, then you need to perform steps 1-3 below to allow the GUI to start for the install, then perform all of the steps (that is, steps 1-4) on the first boot after the install.

If you log in to the system without using the graphical console (by using the text or serial console or Ethernet login), then perform step 4 after the first boot after the install.

  1. Edit the GRUB line displayed when booting and change the default graphics console to either ttya for a serial console, or text for VGA text, depending on your preference. Add -kd as kernel flags as well.

    For example:

    kernel /platform/i86pc/kernel/amd64/unix

    becomes:

    kernel /platform/i86pc/kernel/amd64/unix -kd -Bconsole=text

    or

    kernel /platform/i86pc/kernel/amd64/unix -kd -Bconsole=ttya

    To edit the GRUB line, do the following:

    Press ‘e' to edit the grub entry.

    Press ‘e' to edit the selected line.

    Type the changes.

    Press <esc> to finish.

    Press b to boot.

  2. When the Oracle Solaris OS drops into the debugger, enter the following to set a breakpoint at pcie'_init:

    [0]> ::bp pcie'_init

    :c

  3. When the Oracle Solaris OS hits the breakpoint, enter the following to set the variable 0> pcie_br_flags/W 0:

    pcie'pcie_br_flags: 0x1 = 0x0

    [0]>:c

  4. After the system has booted and you can log in, you can avoid the need for setting the variable using the debugger by appending this line: set pcie:pcie_br_flags=0 to /etc/system.

    #echo 'set pcie:pcie_br_flags=0' >> /etc/system

15773526 (formerly CR 7146324)
No USB controller in fmtopo for servers, and “fault.sunos.eft.unexpected_telemetry” is reported.
Issue:

On the server, Fault Management Architecture (FMA) topology does not include USB controllers. If an FMA ereport is generated for a EHCI USB controller, the fmadm faulty command will generate an unexpected_telemetry fault and the Service Required LED will be illuminated.

Affected software:
  • Oracle Solaris 11 11/11

  • Releases 1.0, 1.1, 1.1.1 and 1.2


Note - This issue does not affect Oracle Solaris 11.1


Workaround:

Consult /var/adm/messages for more information about the source of the error.

To clear the fault(s) and extinguish the Service Required LED, perform the following steps:

  1. On the Solaris host, log in as root and type: fmadm faulty.

    Record the uuid of the fault.

  2. To clear the fault, type: fmadm acquit <uuid>.

    This command will clear the fault from both the Oracle Solaris Operating System and the service processor.

  3. Log in to the service processor as root and restart the service processor. Type: -> reset /SP

15777292 (formerly CR 7151581)
During system boot, a warning message might appear on the console.
Issue:

During system boot, WARNING: npel: no ranges property might appear on the console.

Affected software:
  • Oracle Solaris 10 8/11 and Oracle Solaris 11 11/11

  • Releases 1.0, 1.1, 1.1.1, and 1.2

Workaround:

This message is benign and can be ignored.

None
Oracle Solaris 11 11/11 Preinstall might encounter a five-minute delay during the first boot.
Issue:

Customers using the Oracle Solaris 11 11/11 Preinstall option might encounter a five-minute delay during first boot. During this delay, the system is configuring the ilomconfig-interconnect service. This only occurs on first boot; the system will boot normally on subsequent restarts.Customers monitoring the system's first boot from the system console will observe the system reaching this stage in the boot-up and pause for approximately five minutes and display the following warning:

SunOS Release 5.11 Version 11.0 64-bit Copyright (c) 1983, 2011, Oracle and/or its affiliates. All right reserved. WARNING: npel: no ranges property

Please note that this issue is not related to the WARNING: npel: no ranges property message, which is a separate issue that is documented in Bug ID 15777292 (formerly CR 7151581).

Affected software:
  • Oracle Solaris 11 11/11 Preinstall

  • Releases 1.0, 1.1, 1.1.1, and 1.2

Workaround:

Wait for the ilomconfig-interconnect service to complete its configuration.

15793363 (formerly CR 7170842)

Oracle ILOM might not support the clearing of faults diagnosed by the Oracle Solaris Operating System.
Issue:

Oracle Integrated Lights Out Manager (ILOM) might not be able to repair or clear a fault diagnosed by the Oracle Solaris Operating System.

Affected software:
  • Oracle ILOM 3.1

  • Oracle Solaris 10 8/11 and 11 11/11

  • Releases 1.0, 1.1, 1.1.1, and 1.2

Workaround:

Do either of the following:

  • Use the Oracle Solaris Operating System to repair or clear the fault.

  • Run the following procedure from the faultmgmt shell of the Oracle ILOM command-line interface (CLI).

  1. Find the uuid of the faults in the output of fmadm faulty.

  2. Clear the faults using fmadm acquit <uuid>

15786729 (formerly CR 7162900)

Oracle ILOM Hard Cap power setting does not work with Oracle Solaris Operating Systems.
Issue:

Oracle Integrated Lights Out Manager (ILOM) Hard Cap power setting fails to set maximum power limit on the server with Oracle Solaris Operating Systems if the Hard Cap power setting is enabled before the hand off to the operating system.

Affected software:
  • Oracle ILOM 3.1

  • Oracle Solaris 10 8/11 and 11 11/11

  • Releases 1.0, 1.1, 1.1.1, and 1.2


Note - This issue does not affect Oracle Solaris 11.1


Workaround:

None.

15834619

Network test status is incorrectly reported when Oracle VTS 7.0ps14 is run on systems also running the Oracle Solaris 11.1 Operating System.
When the Oracle VTS network test is run on systems running Oracle Solaris 11.1, the status "No such file or device node" is incorrectly reported for the server's network ports.
Affected software:
  • Oracle Solaris 11.1

  • Oracle VTS 7.0ps14

  • Release 1.2

Workaround:

None.

15829089

Oracle Solaris Operating System panics during a system power off or a system reboot.
Issue:

The Oracle Solaris Operating System panics during a system power off or during a system reboot when either the SG-XPCIEFCOE2-Q-SR or SG-XPCIEFCOE2-Q-TA PCIe cards are installed in the system.

Affected hardware and software:
  • Sun Storage 10 GbE PCIe FCoE Converged Network Adapter: QLogic Low Profile, Dual Port and SR Optics (SG-XPCIEFCOE2-Q-SR)

  • Sun Storage 10 GbE PCIe FCoE Converged Network Adapter: QLogic Low Profile, Dual Port and Twin-Ax (SG-XPCIEFCOE2-Q-TA)

  • Oracle Solaris 11 11/11 and 11.1

  • Release 1.2

Workaround:

There is currently no workaround for this issue. This issue is scheduled to be fixed in a later release of the Oracle Solaris OS.

15805238

Oracle Solaris 11.1 Operating System installation process might fail.
Issue:

The Oracle Solaris 11.1 Operating System installation process might fail at the following point during the OS installation if you are using an ISO image to install the OS.Enter user name for system maintenance (control-d tobypass):

Affected software:
  • Oracle Solaris 11.1

  • Release 1.2

Workaround:

If this issue occurs during the Oracle Solaris 11.1 Operating System installation, disable the Intel Virtualization Technology for Directed I/O (VT-d) setting in the system BIOS settings. This setting can be disabled in the BIOS Setup Utility IO > I/O Virtualization menu.

For information on entering the BIOS Setup Utility and disabling the VT-d setting, see “Accessing the BIOS Setup Utility” in the Sun Server X3-2 Administration Guide.