Go to main content

Sun Fire X4170, X4270, and X4275 Servers Product Notes

Exit Print View

Updated: July 2018
 
 

Resolved Issues as of Software Release 2.8.1

Table 10  Resolved Issues as of Platform Software Release 2.8.1
Bug ID
Description
23634048
SNMP Version 3 Traps Not Delivered
Issue:
If you change the SNMP engine ID, Oracle Integrated Lights Out Manager SNMP v3 traps do not get delivered.
Affected software:
  • Supplemental Releases 1.0, 1.2, 1.4, 2.0, 2.0.1, 2.1, 2.3, 2.4, 2.6.6, 2.6.7, 2.6.8

Fix available:
This issue is fixed in Software Release 2.8.
6806444
Oracle ILOM Remote Console Might Hang on Windows Client When Redirecting a CD-ROM Image or Floppy Image
Issue:
When using a Windows client to redirect a CD-ROM image or floppy image from the Oracle ILOM Remote Console, the Oracle ILOM Remote Console might not respond.
Affected operating systems and software:
  • Windows Operating System installed on a client system

  • Oracle ILOM 2.0 or later, and Oracle ILOM 3.0 or later

  • Java Runtime Environment (JDK) 1.6.0_07

  • Software Releases 1.0, 1.2, 1.4, 2.0, 2.0.1, 2.1, 2.3.1

Fix available:
This issue is fixed in Software Release 2.4.
6876246 6861981
Alternatives to F2 and Ctrl-E On Serial Console Line for Entering BIOS
Issue:
There is a display lag on the serial line that results in the customer pressing the F2 key or Ctrl-E key combination too late, which leads to difficulty displaying the option ROM. You can use Oracle ILOM or non-ILOM alternatives to F2 and Ctrl-E to avoid this problem and access BIOS from the serial line.
Affected operating systems and software:
  • All supported operating systems

  • Supplemental Releases 1.0, 1.2, 1.4, 2.0, 2.0.1, 2.1, 2.3.1, 2.4, 2.6.6, 2.6.7, 2.6.8

Workaround:
Non-Oracle ILOM Workaround:
  • Press "Esc" then "2" that emulates the F2 sequence on a serial line. The SAS host bus adapter (HBA) does not interpret this as Ctrl-E and still loads.

Oracle ILOM Workaround:
  1. Via IPMItool -H <ILOM IP address> -U root chassis bootdev bios, which forces the BIOS to enter setup during the next reset/boot cycle.

  2. Via Oracle ILOM command-line interface (CLI) via SSH: -> set /HOST boot_device=bios. Then enter -> start /SYS or -> reset /SYS

  3. Via Oracle ILOM web interface, select "Remote Control" tab, then "Host Control" tab, and then "BIOS" from the drop-down menu. Then reset or power on the system with the "Remote Power Control" tab.

Note -  Oracle ILOM workarounds are the preferred options because they do not require pressing any keys during BIOS bootup. However, they are only applicable for the next reset/boot cycle, and they do constitute a permanent boot order change.

6854502
NET2 NIC Port (vmnic3) Will Be Disabled When ESX 3.5 U4 Is Installed
Issue:
VMware ESX 3.5 U4 will disable the NET2 NIC port after installation on the Sun Fire X4170, X4270, and X4275 Servers.
Affected operating systems and software:
  • VMware ESX 3.5 Update 4

  • Supplemental Releases 1.0, 1.2, 1.4, 2.0, 2.0.1

Fix available:
This issue is fixed in Software Release 2.1.
6863766
Install Will Fail When Using a Diskette Made From the Tools and Drivers DVD or the Floppy Image (QLogic64.img) on the Tools and Drivers DVD to Install Windows Server 2003 64-bit to a Fiber Channel Array Over a QLogic Fiber Channel HBA
Issue:
If you use a diskette made from the Tools and Drivers (T&D) DVD or the QLogic64.img floppy image available on the Tools and Drivers DVD to install Windows Server 2003 64-bit to a Fiber Channel Array over a QLogic Fiber Channel HBA, the install will fail with a "Blue Screen" late in the setup process. The install fails because the 64-bit QLogic boot from SAN driver set available on the Tools and Drivers DVD has mismatched files and this results in a Bug Check 0x07B near the end of the installation process.
Affected operating systems and software:
  • Windows Server 2003 (64-bit)

  • Supplemental Releases 1.0, 1.2, 1.4, 2.0, 2.0.1

Fix available:
The corrected QLogic driver set, Boot from SAN for STOR Miniport 64-bit Driver (x64), for installing Windows 2003 64-bit to a QLogic connected fiber channel array (the drivers used when pressing F6 during install) are available for download at this web site: http://driverdownloads.qlogic.com/QLogicDriverDownloads_UI/Sun_Details.aspx?productid=928&OSTYPE=Window&oemid=124
This issue is fixed in Software Release 2.1.
6817764
Oracle ILOM Power Budget Feature Does Not Work Unless RHEL 5.3 Errata CPUSPEED Package Is Used
Issue:
The speedstep-centrino cpufreq driver was built into the RHEL kernel, and the acpi-cpufreq driver was included as a module. The two cpufreq scaling drivers conflict due to Red Hat init scripts. This conflict causes the RHEL kernel to not honor CPU power capping directives from Oracle ILOM.
Affected operating systems and software:
  • Red Hat Enterprise Linux (RHEL) 5.3

  • Supplemental Releases 1.0, 1.2, 1.4, 2.0, 2.0.1, 2.1, 2.3.1, 2.4, 2.6.6, 2.6.7, 2.6.8

Workaround:
The problem was corrected by Red Hat and a fix was released to the public. Users of Red Hat Enterprise Linux 5.3 should use the latest 5.3 errata cpuspeed package available for download. For more information, see the following document for download details: https://access.redhat.com/errata/RHBA-2009:0424
6830785
SLES XEN Host (Dom 0) Using igb.ko Driver Will Drop XEN Guest (Dom U) Packets When IPv4 TX Checksum Offload Is Enabled
Issue:
The XEN Host (Dom 0) will corrupt XEN Guest (Dom U) network traffic during transmission to and from the physical interface under the following conditions:
  1. XEN Host (Dom 0) is SLES 10 SP2 operating system.

  2. The inbox SLES 10 SP2 Intel igb.ko driver is being used on the XEN Host (Dom 0).

  3. IPv4 TX checksum is enabled on the XEN Guests (Dom U).

  4. XEN Guests (Dom U) are using optimized paravirtualized NIC drivers.

Affected operating systems and software:
  • SUSE Linux Enterprise Server (SLES) 10 Service Pack 2

  • Supplemental Releases 1.0, 1.2, 1.4, 2.0, 2.0.1, 2.1, 2.3.1, 2.4, 2.6.6, 2.6.7, 2.6.8

Workaround:
A later version of the driver has been compiled for SLES 10 SP2 to resolve this issue. Upgrade to the latest driver version. This issue has been documented by Novell SLES support in the following Technical Information Document (TID), which is available at this location: http://www.novell.com/support/php/search.do?cmd=displayKC&docType=kc&externalId=7003448&sliceId=1&docTypeID=DT_TID_1_1&dialogID=39728435&stateId=0%200%2060594008 . Refer to the TID for information on the latest igb driver that fixes this issue.