JavaScript is required to for searching.
Skip Navigation Links
Exit Print View
Sun Server X2-4 (formerly Sun Fire X4470 M2)

Product Notes, Software Release 1.4.2

search filter icon
search icon

Document Information

Using This Documentation

1.  Sun Server X2-4 Product Notes

Sun Server X2-4 Name Change

Supported Operating Systems

Oracle Unbreakable Enterprise Kernel for Linux

Supported Firmware and Software

Supported Firmware in Software Releases

Supported Diagnostics

Firmware Updates

Supported Software

Supported Memory Configurations

Supported PCIe Cards

Quantity and Slot Restrictions

Minimum Firmware Revisions for PCIe Cards

Sun Flash Accelerator F20 PCIe Card Requirements

Card Placement and Cooling

ESM Replacement Interval

Internal Sun Storage 6Gb SAS PCIe RAID HBA Requirements

Sun Storage 10GbE FCoE PCIe Low Profile Dual Port CNA and OS Support

Resolved Issues

Known Open Issues

Hardware Known Issue

BIOS Known Issues

Oracle Solaris Known Issues

Oracle Linux, SUSE Linux Enterprise Server (SLES), and Red Hat Enterprise Linux (RHEL) Known Issues

Oracle VM Known Issue

Windows Known Issues

Oracle Integrated Lights Out Manager (ILOM) Known Issue

Oracle Hardware Installation Assistant Known Issues

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

Known Open Issues

The following tables describe known open issues and workarounds related to the Sun Server X2-4.

Hardware Known Issue

Table 1-4 Hardware Known Open Issue

Bug ID
Description
None
Do not mix dual-rank and quad-rank DIMMs.
Issue:

The Sun Server X2-4 now supports dual-rank and quad-rank DIMMs. However, mixing dual-rank DIMMs with quad-rank DIMMs in the same memory riser degrades performance.

Affected Hardware:
  • Sun Server X2-4

Workaround:

Do not mix dual-rank and quad-rank DIMMs in the same server.

BIOS Known Issues

Table 1-5 BIOS Known Open Issues

Bug ID
Description
15576675
Amount of memory reported by BIOS is less than actual memory installed.
Issue:

In the BIOS splash screen and in the main BIOS Setup Utility menu, the system reports 8 MB less memory than what is installed to account for the Intel architecture's consumption of 8 MB of debug memory.

Affected Software:
  • All Sun Server X2-4 Software Releases

Workaround:

There is no workaround.

15725542
PXE boot might fail after running Pc-Check diagnostics.
Issue:

When attempting a PXE boot immediately after running Pc-Check in Extended mode, the boot attempt might fail with a message similar to the following:

Intel(R) Boot Agent GE v1.3.35 Copyright (C) 1997-2009, Intel Corporation Intel(R) Boot Agent PXE Base Code (PXE-2.1 build 087) Copyright (C) 1997-2009, Intel Corporation

Affected Software:
  • Software Release 1.1 running Oracle ILOM 3.0.16.12, and BIOS 16.02.01.01 with Pc- Check 6.29s

Workaround:

Power cycle or warm reboot the system.

15707452
Incorrect IPMI warning codes for DIMM DDR training errors are generated during BIOS POST.
Issue:

Incorrect IPMI warning codes for DIMM DDR training errors are generated during system BIOS POST. The Service Required LED might indicate an error and the following warning codes might be displayed in system event log (SEL) entries:

0x0d WARN_DD_TRAINING_ERROR warning: 0x02 - WARN_DIMM_MISMATCH 0x03 - WARN_USER_RANK_DISABLE 0x05 - WARN_MEMBIST_ECC_SYMBOL 0x09 - WARN_THROT_INSUFFICIENT

Affected Software:
  • All Sun Server X2-4 Software Releases

Workaround:

These are benign error messages that can be safely ignored.

Oracle Solaris Known Issues

Table 1-6 Oracle Solaris Known Open Issues

Bug ID
Description
15781718
Oracle Solaris 11 displays the following warning message: "NOTICE: BIOS BUG: Invalid Bus Number in PCI IRQ Routing Table"
Issue:

Warning message displays in Oracle Solaris 11 after operating system installation.

Affected Operating System:
  • Oracle Solaris 11 11/11 and 11.1

Workaround:

This warning message can be safely ignored. It is an informational message for an unexpected but harmless incident.

15760687
System panics at beginning of Oracle Solaris 10 8/11 installation onto a Sun Server X2-4 system configured for RAID 10 and with the Sun Storage 6-Gb SAS PCIe HBA card installed.
Issue:

A system panic might occur during the installation of Oracle Solaris 10 8/11 onto a Sun Server X2-4 that is configured for RAID 10, when the hard disk drives are connected to an internal Sun Storage 6-Gb SAS PCIe HBA card (SGX-SAS6-INT-Z or SG-SAS6-INT-Z). The panic is caused by a known issue with the HBA mptsas driver.

Affected Operating System:
  • Oracle Solaris 10 8/11

Workaround:

Apply a mptsas driver Install Time Update (ITU) patch during the OS installation. The steps to resolve this panic issue are detailed in the ReadMe file for the ITU patch, which can be found in the Oracle Solaris folder in the Tools and Drivers DVD of Software Release 1.2 and later releases.

15756723
Oracle Solaris 10 8/11 system panics and reboots after three hours of network stress.
Issue:

Solaris 10 8/11 might panic and then reboot during an extended time of network stress.

Affected Operating System:
  • Oracle Solaris 10 8/11

Workaround:

Install Patch 147441-08 (or higher version), which you can download from My Oracle Support. Run the install shell script to install the related patch.

15726332

15692870

Intel SpeedStep function does not work with Oracle Solaris 10 9/10, Oracle Solaris 10 8/11, or Oracle Solaris 11 Express.
Issue:

The Intel SpeedStep functionality does not work on systems running Oracle Solaris 10 9/10, Oracle Solaris 10 8/11, and Oracle Solaris 11 Express.

Affected Operating Systems:
  • Oracle Solaris 10 9/10

  • Oracle Solaris 10 8/11

  • Oracle Solaris 11 Express

Workaround:

This issue can be fixed by editing the configuration file /etc/power.conf to change cpupm enable to cpupm enable poll-mode.

Oracle Linux, SUSE Linux Enterprise Server (SLES), and Red Hat Enterprise Linux (RHEL) Known Issues

Table 1-7 Oracle Linux, SLES, and RHEL Known Open Issues

Bug ID
Description
15786284
RHEL 6.2 - APEI: Can not request iomem region <000000007f790800-000000007f790804> for GARs.
Issue:

The following error message of APEI will be shown in RHEL 6.2 dmesg when the system boots using default kernel parameters:

APEI: Can not request iomem region <000000007f790800-000000007f790804> for GARs.

This inconsistent description of the APEI ERST feature in ACPI specification 4.x/5.x renders the ERST function of APEI unusable in Linux.

Affected Operating System:
  • Red Hat Enterprise Linux (RHEL) 6.2

Workaround:

Disable ERST of APEI by appending erst_disable to the kernel command line. The following information will be displayed in dmesg: ERST: Error Record Serialization Table (ERST) support is disabled.

15776200
Hardware error messages and false mcelog errors appear in dmesg on two-processor and four-processor server configurations running SLES 11 SP2.
Issue:

The following error message might appear when running SLES 11 SP2 on a two-processor or four-processor system:.

MCE Error, Status code: d00001000009008f

Affected Operating System:
  • SUSE Linux Enterprise Server (SLES) 11 SP2

Workaround:

If the error messages are not persistent, and there is no obvious performance degradation, you can safely ignore them. If the error messages are persistent, identify and replace the marginal components.

15780082
Value of the crash kernel option for RHEL 5.8 and Oracle Linux 5.8 needs to be increased to a minimum of 128M@32M.
Issue:

When using the Oracle Unbreakable Enterprise Kernel for Linux, a higher memory setting is required for the crash kernel option in the /etc/grub.conf file. Booting with crashkernel1=128M@16M will result in the following error: crashkernel reservation failed - memory is in use.

Affected Operating Systems:
  • Oracle Linux 5.8

  • Red Hat Enterprise Linux (RHEL) 5.8

Workaround:

The minimum value for the crash kernel option is 128M@32M. Based on the system configuration, an even higher value might be required. If kdump service loading fails, increase the second value (32M). If the system hangs or crashes during dumping the core, increase the first value (128M).

15759139
Quad Gigabit Ethernet UTP PCIe and Dual Gigabit Ethernet PCIe option cards do not work on SLES 10 SP4 XEN.
Issue:

On SLES 10 SP4 XEN, the Quad Gigabit Ethernet UTP PCIe (X4446A-Z) and the Dual Gigabit Ethernet PCIe (X7281A) do not work normally because of a XEN kernel issue.

Affected Operating System:
  • SUSE Linux Enterprise Server (SLES) 10 SP4

Workaround:

This issue has been fixed in SLES 11 SP1 XEN kernel; however, there is no workaround for this issue in SLES 10 SP4 XEN kernel.

15761043
SLES 11 SP1 XEN and Oracle VM 3.0.2 might report map_irq failed.
Issue:

SLES 11 SP1 XEN and Oracle VM 3.0.2 may report map irq failed.

Affected Operating System and Software:
  • SUSE Linux Enterprise Server (SLES) 11 SP1

  • Oracle VM 3.0.2

Workaround:

Add the following to the kernel line of the GRUB file: extra_guest_irqs=64,2048 nr_irqs=2048

15636521
Oracle Linux 5.5, RHEL 5.5, and SLES 11 SP1 allow only a limited number of interrupt vectors.
Issue:

Certain hardware configurations that include many high bandwidth I/O cards with drivers that use multiple MSI vectors per instance might cause the kernel to run out of interrupts. This situation might result in a long pause or system hang at boot time or I/O devices that are unusable due to driver instances unable to get required interrupts. This situation is especially likely to occur for the Xen Hypervisor and Dom0 with multiple InfiniBand and 10GbE network cards using SR-IOV, but is also possible on the SMP kernel.

Affected Operating Systems:
  • Oracle Linux 5.5

  • Red Hat Enterprise Linux (RHEL) 5.5

  • SUSE Linux Enterprise Server (SLES) 11 SP1

Workaround:

Booting with kernel argument pci=nomsi will allow the system to boot with no long pause in UDEV and no system hang. The system will, however, be forced to use a single IO-APIC PIN interrupt per function. If you need MSI instead of IO-APIC interrupts, then you might need to use some combination of the following methods to alleviate the problem:

  • Blacklist some drivers by adding the module name to the text file /etc/modprobe.d/blacklist. This prevents the module from loading and using the device.

  • Force certain drivers (such as mlx4_core : infiniband) to load last, and take advantage of the code in those drivers that asks for optimal MSI number of vectors. If those vectors are not available, retry with increasingly fewer number of vectors.

15718589
Oracle Linux 5.6 fails to allocate memory space on onboard Intel 82576 network interface card (NIC) ports.
Issue:

Oracle Linux 5.6 displays "PCI: Failed to allocate mem resource" for the onboard Intel 82576 network interface card, which supports the Intel SR-IOV feature. Oracle Linux 5.6 will then attempt to allocate memory space that is required by Virtual Function exported by Intel's SR-IOV capability.

Affected Operating System:
  • Oracle Linux 5.6 and later

Workaround:

You must first enable SR-IOV support and ARI support features in the Advanced tab in the BIOS Setup Utility.

15691490
Error message is received when running RHEL 6.0.
Issue:

The following error message might be received when running RHEL 6.0 on the server:

EDAC MC: Ver: 2.1.0 Sep 1 2012 PCI: Discovered peer bus ff PCI: Discovered peer bus f3 EDAC i7core: Driver loaded. i7core_edac: probe of 0000:80:14:0 failed with error -22

Affected Operating System:
  • Red Hat Enterprise Linux (RHEL) 6.0

Workaround:

This is expected behavior and the error message can be safely ignored.

15705525
Repeatedly executing the lspci- command might cause a system that is running RHEL 6.0 to reset when under high I/O stress.
Issue:

Repeatedly executing the lspci -vv command might cause a system that is running RHEL 6.0 to reset when under high I/O stress. This issue occurs when the Sun Storage 6 Gb SAS PCIe Internal HBA (SGX-SAS6-INT-Z or SG-SAS6-INT-Z) or the Sun Storage 6 Gb SAS PCIe RAID Internal HBA (SGX-SAS6-R-INT-Z or SG-SAS6-R-INT-Z) cards are installed in a system.

Affected Operating Systems:
  • Red Hat Enterprise Linux (RHEL) 6.0 and later

Workarounds:
  • Only execute the lspci -vv command when the system is idle. Do not execute the lspci -vv command in frequent succession.

  • Upgrade the firmware of the Sun Storage 6 Gb SAS PCIe Internal HBA or the Sun Storage 6 Gb SAS PCIe RAID Internal HBA to the latest version.

15697578
Error messages are received when running RHEL 5.5 and LSI MegaRAID Storage Manager on a system configured with Sun Storage 6 Gb SAS PCIe RAID Internal HBA or Sun Storage 6 Gb SAS PCIe Internal HBA.

Issue:

This issue applies to a system configured with the Sun Storage 6 Gb SAS PCIe RAID, Internal HBA (SGX-SAS6-R-INT-Z or SG-SAS6-R-INT-Z) or the Sun Storage 6 Gb SAS PCIe, Internal HBA (SGX-SAS6-INT-Z or SG-SAS6-INT-Z). You might receive the following error messages if the system is running the RHEL 5.5 operating system, using the default RHEL 5.5 installation options and the default Security Enhanced Linux (SELinux) software configuration settings:

kernel: mrmokernel: mrmonitord[6058]: mrmonitord[15918]: segfault at 00000000ffffffff rip 00000000ffffffff rsp 00000000ffdab11c error 14

This is because SELinux is preventing mrmonitord from loading /usr/lib/libAlertStrings.so.1.0.0, which requires text relocation.This occurs because the SELinux Streams (LiS) interface and RHEL 5.5, which are both required by the graphical interface to run, cannot install properly on the system due to the default SELinux software mode and policy preventing them from doing so.

Affected Operating System and Software:
  • Red Hat Enterprise Linux (RHEL) 5.5

  • LSI MegaRAID Storage Manager 8.00-5

Workarounds:

To enable the LiS interface to properly install on the system, perform one or both of the following workaround procedures. These workaround procedures provide basic steps to prevent these error messages from occurring. For more information, see the RHEL 5.5 OS documentation at http://www.redhat.com.

Procedure 1:

  1. Disable the SELinux software temporarily at system boot time by adding the value selinux=0 to the kernel line of the GRUB menu.

  2. Continue the system boot.

Procedure 2:

  1. Disable the SELinux software permanently by editing the /etc/selinux/config file to change the mode of the SELinux software from enforcing to disable or permissive. For example:

    # vi /etc/selinux/config SELINUX=disabled

    or

    # vi /etc/selinux/config SELINUX=permissive

  2. Reboot the system.

Oracle VM Known Issue

Table 1-8 Oracle VM Known Issue

Bug ID
Description
15786012
Warning appears in dmesg saying 'dbus-daemon' uses 32-bit capabilities.
Issue:

On 64-bit Oracle VM systems, you might see the following warning in dmesg: warning: 'dbus-daemon' uses 32-bit capabilities (legacy support in use).

Affected Operating System:
  • Oracle VM 3.0

Workaround:

This message is only a warning and can be safely ignored.

Windows Known Issues

Table 1-9 Windows Known Open Issues

Bug ID
Description
15699476
Firmware upgrade fails when using IPMIflash on Windows Server 2008 R2 systems.
Issue:

IPMIflash 1.8.10.4 for Windows Server 2008 R2 (64-bit) fails during the firmware upgrade process. The service processor remains in a consistent state and displays no side effects.

Affected Operting System and Software:
  • IPMIflash 1.8.10.4

  • Windows Server 2008 R2 (64-bit)

Workaround:

Use the Oracle ILOM command-line interface (CLI) or the web interface to perform Oracle ILOM firmware updates.

For Oracle ILOM 3.0 instructions, see the Oracle Integrated Lights Out Manager (ILOM) 3.0 Daily Management–CLI Procedures Guide or the Oracle Integrated Lights Out Manager (ILOM) 3.0 Daily Management–Web Procedures Guide. These documents are located at: http://www.oracle.com/pls/topic/lookup?ctx=ilom30

For Oracle ILOM 3.1 instructions, see the Oracle Integrated Lights Out Manager (ILOM) 3.1 Quick Start Guide at:

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

15702216
Service processor reboot causes a system crash on Windows Server 2008 R2 systems.
Issue:

A service processor reboot might cause a system crash on a system that is running the Windows Server 2008 R2 operating system.

Affected Operating System:
  • Windows Server 2008 R2 (64-bit)

Workaround:

Upgrade the onboard Intel 82576 network interface card (NIC) Windows driver to version 11.4.7.0 or later. The latest Windows drivers are provided with the Tools and Drivers firmware. See Download Firmware and Software Using My Oracle Support for instructions on downloading the latest tools and drivers firmware.

15676534
All disks that are attached to Sun Storage 10GbE FCoE PCIe Converged Network Adapter are lost after a system reboot.
Issue:

When you install a Sun Storage 10GbE FCoE PCIe Low Profile Dual Port Twin-Ax/SR Converged Network Adapter (CNA) (SG-PCIEFCOE2-Q-SR or SG-PCIEFCOE2-Q-TA) on a Sun Server X2-4 that is running the Windows operating system and then reboot the system, you lose access to all of the disks that are attached to the CNA.

Affected Operating Systems:
  • Windows Server 2008 SP2 (64-bit)

  • Windows Server 2008 R2 (64-bit)

Workaround:

There is no workaround. The Windows operating system is not supported with the Sun Storage 10GbE FCoE PCIe CNA.

15712471
The SMBIOS HCT test case of the Windows 2008 R2 WHQL certification fails on systems that are configured with 1 TB of memory.
Issue:

The SMBIOS HCT test case of the Windows 2008 R2 hardware quality testing (WHQL) certification fails on systems that are configured with 1 TB of memory. Software release 1.0 only supports up to 512-GB (8GB x 64) memory on systems that are running the Windows Server 2008 R2 operating system.

Affected Operating System:
  • Windows Server 2008 R2 (64-bit)

Workaround:

There is no workaround for Software Release 1.0. Software patch release 1.0.1 will support 1 TB (16 GB x 64) of memory for systems that are running the Windows Server 2008 R2 operating system.

Oracle Integrated Lights Out Manager (ILOM) Known Issue

Table 1-10 Oracle ILOM Known Open Issue

Bug ID
Description
None
Unable to Launch Oracle ILOM Remote Console
Issue:

Due to Java security changes, with the previous Oracle ILOM firmware if you used Java 7 update 51 or newer, you could not launch Oracle ILOM Remote Console. With the new Oracle ILOM firmware (ILOM 3.1.2.24.d) if use Java 7 update 51 or newer, you can launch Oracle ILOM Remote Console.

Affected Software:
  • Oracle ILOM

  • Java 7 Update 51 or newer

Workaround:

Use Oracle ILOM firmware release 3.1.2.24.d or later.

Oracle Hardware Installation Assistant Known Issues

Table 1-11 Oracle Hardware Installation Assistant Known Open Issues

Bug ID
Description
15731356
Oracle Hardware Installation Assistant CD does not support remote updating of BIOS, firmware, and operating system drivers.
Issue:

The Oracle Hardware Installation Assistant CD does not support the remote updating of the latest system BIOS, firmware, and operating system drivers from Oracle.

Affected Software:
  • Oracle Hardware Installation Assistant

  • All Sun Server X2-4 Software Releases

Workaround:

There is currently no workaround.

16517092
Oracle Linux OS Fails to Boot Occasionally
Issue:

When using Oracle Hardware Installation Assistant to prepare the selected disk for Oracle Linux operating system (OS) installation, you need to exit from Oracle Hardware Installation Assistant, then reboot Oracle Hardware Installation Assistant into the prepared disk to complete the installation. Occasionally the installation process stops and this error message appears: “Missing Operating System.” This issue occurs very infrequenctly, in approximately less than five percent of Oracle Linux installation attempts that use Oracle Hardware Installation Assistant to prepare the disk.

Affected Software:
  • Oracle Hardware Installation Assistant

  • Oracle Linux 6.4 and 5.9

Workaround:

After you exit from Oracle Hardware Installation Assistant, you need to reboot into Oracle Hardware Installation Assistant to complete the OS installation. You can launch Oracle Hardware Installation Assistant using either local or remote media. If you are using remote media, you will launch Oracle Hardware Installation Assistant from a virtual CD/DVD using remote keyboard, video, mouse (RKVM) through the server's service processor, or a PXE network boot image. To ensure that Oracle Hardware Installation Assistant launches, verify that the respective networks are setup correctly, depending on the launch method you choose. Then, launch Oracle Hardware Installation Assistant and complete the disk preparation step.

18156539
Oracle Hardware Installation Assistant GUI Fails to Launch Occasionally
Issue:

When launching Oracle Hardware Installation Assistant, the application's graphical user interface (GUI) occasionally fails to appear. This issue occurs very infrequently, in approximately less than five percent of the attempts to launch Oracle Hardware Installation Assistant.

Affected Software:
  • Oracle Hardware Installation Assistant

Workaround:

You can launch Oracle Hardware Installation Assistant using either local or remote media. If you are using remote media, you will launch Oracle Hardware Installation Assistant from a virtual CD/DVD using remote keyboard, video, mouse (RKVM) through the server's service processor or a PXE network boot image. To ensure that Oracle Hardware Installation Assistant launches, verify that the repsective networks are setup correctly, depending on the launch method you choose. Then, launch Oracle Hardware Installation Assistant.