2.6.2

3.0.16.15.b

07.06.03.06

2.6.1

3.0.16.15.a

07.06.03.04

2.6

3.0.16.15

07.06.03.02

2.5.1

3.0.9.19.e

07.06.02.32

2.4

3.0.9.19.b

07.06.02.30

2.3.1 (latest update for systems running ILOM 3.0)

3.0.9.19.a

07.06.02.23

2.1.1

3.0.6.21

07.06.02.15

2.1

3.0.6.10

07.06.02.15

2.0.1

3.0.3.35.a

07.05.01.01

2.0

3.0.3.35

07.03.00.04

1.4 (latest update for systems running ILOM 2.0)

2.0.2.22

07.04.40.04

1.2

2.0.2.17

07.02.39.01

1.0

2.0.2.9

07.01.38.03

Intel CPU Microcode

SRV_C_81

Intel RC

1.05

Intel CPU Reference Code

1.02

Intel QuickPath Interconnect (QPI) Reference Code

1.05

Intel Memory Reference Code (MRC)

1.05

6904948

L/V SW2.1 SIA Does Not Find SAS Expander on Hyde

Issue:

SIA 2.3.2.9 Expander Firmware Update task reported “No expanders found,” which made the Expander task impossible to run on a Hyde server.

Affected Operating Systems and Software:

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

Fix Available:

Fix is available on Supplemental Software Release 2.4.

6806444

Sun 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 Sun ILOM Remote Console, the Sun ILOM Remote Console might not respond.

Affected Operating Systems and Software:

• Windows Operating System installed on client system
• ILOM 2.0 or later and ILOM 3.0 or later
• Sun ILOM Remote Console
• JDK 1.6.0_07
• Supplemental Releases 1.0, 1.2, 1.4, 2.0, 2.0.1, 2.1, 2.3.1, 2.4

Fix Available:

Fix is available on Supplemental Software Release 2.4.

6824822

Misleading "MB/R#/PCIE#/P" Log Entries When The PCIE Card is Not Present

Issue:

Event log messages are misleading when the host is reset on a server with no PCIE card connected on Riser2. Present, absent, hot insertion, and removal messages appear in the event log about this absent device while no messages about the other PCIE cards that are connected.

Affected Hardware and Software:

• Sun Fire X4170, X4270, and X4275 Servers
• Supplemental Releases 1.0, 1.2, 1.4, 2.0, 2.0.1, 2.1, 2.3.1, 2.4

Workaround:

Upgrade the ILOM firmware version to 3.0.9.19.a

6912443

Hard Drives Can Be Difficult to Remove From Right-Side Drive Bays

Issue:

Hard drives in the right-side drive bays can be difficult to remove.

Affected Hardware

• Sun Fire X4170, X4270, and X4275 Servers

Workaround:

Until a mechanical fix is implemented, use the following procedure to remove hard drives from right-side drive bays.

1. Press the drive to the right.

See Step 1 in the following figure.

1. Push in on the drive, while holding it pressed to the right.

See Step 2 in the following figure.

1. Press the drive eject button and pull on the eject lever.

See Step 3 in the following figure.

1. Use the eject lever to slide the drive out of the bay.

See Step 4 in the following figure.

6938599

Incorrect Ordering Listed on the Top Cover Service Label

Issue:

The top cover service label (on the lid) of the Sun Fire X4275 has incorrect ordering listed for the Right LED Label. Some systems manufactured before September 2009 also have incorrect labeling on the front right ear.

The top cover lists the LED order as:

• Rear PS
• Temperature
• Top Fan

Affected Hardware and Software:

• Sun Fire X4170, X4270, and X4275 Servers
• Supplemental Releases 1.0, 1.2, 1.4, 2.0, 2.0.1, 2.1, 2.3.1, 2.4

Workaround:

The correct order is:

• Top Fan
• Rear PS
• Temperature

6795890

USB Devices Not Shown in BIOS Boot Order When Using a CompactFlash Device

Issue:

In rare cases, when a CompactFlash device is connected using the CompactFlash connector, some USB devices might not be accessible in the BIOS boot-list.

Affected Hardware and Software:

• Sun Fire X4170, X4270, and X4275 Servers
• Supplemental Releases 1.0, 1.2, 1.4, 2.0, 2.0.1, 2.1, 2.3.1, 2.4

Workaround:

Reboot the system. If the problem persists after the reboot, initiate a service call.

6790478

6800183

SATA Solid-State Drives Not Supported With LSI HBA on Sun Fire X4270 and X4275 Servers

Issue:

Using SATA Solid-State Drives (SSDs) with the SG-XPCIE8SAS-I-2 Sun StorageTek 8-port Internal SAS PCIe LSI 308IE HBA is not supported in the Sun Fire X4270 or Sun Fire X4275 Server and might cause unpredictable system behavior.

Affected Hardware and Software:

• Sun Fire X4270 and X4275 Servers
• Supplemental Releases 1.0, 1.2, 1.4, 2.0, 2.0.1, 2.1, 2.3.1, 2.4

Workaround:

There is no workaround. Check for the availability of a patch for this defect.

6858722

PCIe Errors Reported With QLE2562 Card Attached Using Active Riser

Issue:

If the Sun QLogic QLE2562-based, 8 Gigabit/second PCI-E Dual FC Host Adapter (SG-XPCIE2FC-QF8-Z) or Sun QLogic QLE2560-based, 8 Gigabit/second PCI-E Single FC Host Adapter (SG-XPCIE1FC-QF8-Z) are placed in PCIe slot 1, 2, 4, or 5, a stream of correctable PCIe errors will be reported. This can cause performance issues and operating system stability issues due to the large number of errors received.

Affected Hardware and Software:

• Sun Fire X4270 and X4275 Servers
• Supplemental Releases 1.0, 1.2, 1.4, 2.0, 2.0.1, 2.1, 2.3.1, 2.4

Workaround:

The Sun QLE2562-based or QLE-2560-based cards must be placed in PCIe slot 0 or 3 only.

7005619

Operating System Might Hang After Running Pc Check Diagnostics

Issue:

After running Pc Check, if you attempt to install or boot an operating system, the OS install or boot might hang.

Affected Software:

• Software releases 1.0, 1.2, 1.4, 2.0, 2.0.1, 2.1, 2.3.1, 2.4

Workaround:

Reboot the system after running Pc Check and before trying to install or boot an operating system.

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 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 Software Software Releases 1.0, 1.2, 1.4, 2.0, 2.0.1, 2.1, 2.3.1, 2.4

ILOM Workarounds:

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 ILOM cli via ssh: -> set /HOST boot_device=bios -> start /SYS or -> reset /SYS
3. Via 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 - The ILOM workarounds listed above 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.

Non-ILOM Workaround:

1. Press "Esc" then "2" that emulates the F2 sequence on a serial line. The SAS HBA does not interpret this as Ctrl-E and still loads.

6917623

“EHCI: BIOS handoff failed” Message Appears When Legacy USB is Enabled

Issue:

The following BIOS error appears in the log during boot: [ 118.727293] 0000:00:1d.7 EHCI: BIOS handoff failed (BIOS bug ?) 01010001...

Affected Operating Systems and Software:

• All supported operating systems
• Supplemental Software Software Releases 1.0, 1.2, 1.4, 2.0, 2.0.1, 2.1, 2.3.1, 2.4

6716289

Amount of Memory Reported by BIOS and System Is Less Than Actual Memory Installed

Issue:

In the BIOS splash screen and in the main BIOS Setup menu, the system reports 8MB less memory than installed.

Affected Software:

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

Workaround:

There is no workaround. Check for the availability of a patch for this defect.

6839587

System Will Not Boot From Hard Disk Drive With Unused CF Card Installed

On systems on which an unused Compact Flash (CF) card was factory installed, on the first reboot a blank screen appears after the BIOS/POST, the system does not boot the installed OS, and the system hangs.

Affected Hardware and Software:

• Sun Fire X4170, X4270 and X4275 Servers
• Supplemental Releases 1.0, 1.2, 1.4, 2.0, 2.0.1, 2.1, 2.3.1, 2.4

Workaround:

Use the BIOS to modify the boot order so that the system will boot from the desired hard disk drive, not the Compact Flash.

To modify the boot order:

1. Go into the BIOS Setup menus (F2 during BIOS POST) and navigate to the Boot tab.
2. Go into Boot Device Priority and change the boot order.
3. Press F10 to save the new settings and exit.

6913602

ILOM Fails To Read DIMM FRU Information When Host is On

Issue:

When the host is on, FRU information for DIMMs is lost after Reset ILOM with factory option and ILOM reboot.

Affected Software:

• ILOM3.0.9.19.b r59793

Workaround:

Power off the Host before setting reset_to_defaults=factory, then reboot the SP.

6779289

In-chip Connectivity Between the SP and the Host OS Is Not Supported When Using Sideband Network Port Sharing

Issue:

When configured for sideband (SB) network port sharing, in-chip connectivity between the service processor (SP) and the host OS is not supported by the on-board host Gigabit Ethernet controller.

Affected Software:

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

Workaround:

Use a different port or route to transmit traffic between the source and destination targets instead of using L2 bridging/switching.

6795975

Subsequent ILOM Session KVMS Interface Might Not Work

Issue:

When multiple Sun ILOM Remote Console sessions are opened to the same service processor, the additional session's keyboard interface might not work. The first session's keyboard interface is not affected.

Affected Software:

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

Workaround:

• Double-click in the Sun ILOM Remote Console dialog to activate the mouse then move the mouse.

Or

• In the Sun ILOM Remote Console menu bar, select Devices --> Mouse, then move the mouse.

6800702

6813782

64-bit JRE Fails to Launch the Sun ILOM Remote Console

Issue:

An attempt to start Storage Redirection in ILOM might fail when using a 64-bit JRE. Since the 64-bit JRE is the default on a 64-bit system, you might also need to download a 32-bit JRE. When using a 64-bit JRE to start storage redirection, an "Unsupported platform" error will appear.

Affected Software:

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

Workaround:

Install a 32-bit JRE on the 64-bit system. JREs can be downloaded at:

http://java.com/en/download/index.jsp

6873660

Property write_cache_enabled Is Not Available on the ILOM SP

Issue:

Certain controllers (for example, Adaptec) enable the user to configure a RAID with the Write_Cache parameter set to predefined values. Irrespective of what this parameter is set to, this property is not available to the user from the ILOM SP CLI. Ideally this property would reside under /STORAGE/raid/controller#/raid_id#/. Currently the Adaptec SDK does not provide this data.

Affected Operating Systems and Software:

• Solaris 10 05/09, RHEL 4.8 and 5.3, SLES 10 SP2, SLES 11, and VMware ESX 3.5 Update 4
• ILOM 3.0.6.10
• Supplemental Release 2.1, 2.3.1, 2.4

Workaround:

There is no workaround. Check for the availability of an update.

6875715

Property max_disks Is Always Incorrectly Set to 0 on ILOM SP

Issue:

The maximum number of disks that a controller supports is a property of that controller and should be available as part of the Storage Viewer functionality under /STORAGE/raid/controller# on the ILOM SP CLI. Currently this property value is always incorrectly set to 0.

Affected Operating Systems and Software:

• Solaris 10 05/09, RHEL 4.8 and 5.3, SLES 10 SP2, SLES 11, and VMware ESX 3.5 Update 4
• ILOM 3.0.6.10
• Supplemental Release 2.1, 2.3.1, 2.4

Workaround:

There is no workaround. Check for the availability of an update.

6877654

Property raid_global_hotspare Does Not Display the Correct Information for Certain Controllers and Operating Systems on the ILOM SP

Issue:

When a RAID is configured to have a global hotspare using the Adaptec Configuration, the corresponding raid_global_hotspare parameter in ILOM SP CLI does not indicate that information. Instead the raid_dedicated_hotspare parameter is displayed as true.

Affected Operating Systems and Software:

• Solaris 10 05/09, RHEL 4.8 and 5.3, SLES 10 SP2, SLES 11, and VMware ESX 3.5 Update 4
• ILOM 3.0.6.10
• Supplemental Release 2.1, 2.3.1, 2.4

Workaround:

There is no workaround. Check for the availability of an update.

6882835 6884652

Power Management Budget Is Not Supported on RHEL 4.7, 5.3, or 5.4

Issue:

Multiple issues occur if you try to use the Power Budget feature of Power Management on servers running Red Hat Enterprise Linux (RHEL) 4.7, 5.3, or 5.4. These issues can lead to configured power budgets being exceeded or lower than expected CPU performance.

Affected Operating Systems and Software:

• Red Hat Enterprise Linux (RHEL) 4.7, 5.3, 5.4
• ILOM 3.0.6
• Supplemental Release 2.1, 2.3.1, 2.4

Workaround:

Do not use the Power Budget feature when running Red Hat Enterprise

Linux (RHEL) 4.7, 5.3, or 5.4.

6779112

Misleading Status for Power Supplies Reported by VMware Health Status Screen

Issue:

The VMware Virtual Infrastructure client Health Status screen under the Power component reports the server power supplies in an Off-Line Disabled state and 0 watts, even though the power supplies are on-line and enabled.

Affected Operating Systems and Software:

• VMware ESX 3.5 Update 4
• Supplemental Releases 1.0, 1.2, 1.4, 2.0, 2.0.1, 2.1, 2.3.1, 2.4

Workaround:

While in the VMware Virtual Infrastructure client Health Status screen, click on Other component from the list of available options to view the correct power supply status.

6835570

Local Storage Drive Is Not Seen After Installing VMware ESXi 3.5 Update 4

Issue:

If the Sun Fire X4170, X4270, or X4275 Server has a local storage drive attached to the PCI-Express SAS LSI Controller (SG-XPCIE8SAS-I-Z), the local storage drive is not seen by the system after installing VMware ESXi 3.5 Update 4.

Affected Operating Systems and Software:

• VMware ESXi 3.5 Update 4
• Supplemental Releases 1.0, 1.2, 1.4, 2.0, 2.0.1, 2.1, 2.3.1, 2.4

Workaround:

After completing the ESXi installation, follow these steps to add the local storage drive to the storage inventory.

1. Add the ESXi host to the datacenter of your choice using the Virtual Infrastructure Client.
2. Select the ESXi host added in step one, then click the Configuration tab.
3. In the hardware box (in the upper left of the display), select Storage.
4. In the upper right part of the display, click the Add Storage... link.
5. Ensure that the Disk/LUN Storage Type is selected, then click Next.
6. Highlight the vmhba entry that corresponds to the local storage drive and click Next.
7. Select the Use free space entry and click Next.
8. Create a Datastore Name (for example, local_storage), then click Next.
9. Adjust the Maximum file size, if needed, then click Next.
10. Verify the proposed disk layout, then click Finish.

The local Virtual Machine File System (VMFS) datastore should now be available for use.

6854502

Net2 NIC Port (vmnic3) Will Be Disabled When ESX 3.5 Update 4 Is Installed

Issue:

VMware ESX 3.5 Update 4 will disable the Net2 NIC port after installation on the Sun Fire X4170, X4270, and X4275 Servers.

Affected Hardware, Operating Systems, and Software:

• Sun Fire X4170, X4270, and X4275 Servers
• VMware ESX 3.5 Update 4
• Supplemental Releases 1.0, 1.2, 1.4, 2.0, 2.0.1, 2.1, 2.3.1, 2.4

Workaround:

Append the noapic parameter to the end of the kernel line in /boot/grub/menu.lst. Check for the availability of a future BIOS update for this defect.

6930223

Network Case Fails When Running SUNVTS7PS8

Issue:

When running SUNVTS7.0PS8, the network case will fail. The fix has not yet been backported to Solaris10.

Affected Software:

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

Workaround:

Run NIC loopback test with SUNVTS, you need to use a loopback connector.

6889350

Solaris FMA may fail to load and cause hang on system shutdown with particular memory configuration

Issue:

With mixed 4Gb and 8Gb dimms present in the same channel, Solaris FMA may fail to start correctly on system boot, and may cause the system to hang on shutdown.

Svcs will report that the fma daemon (fmd) is offline.

This issue has been seen with the following memory configuration:

8Gb dimms in D2,D5,D8 and 4Gb dimms in D1, D4, D7

Affected Operating Systems and Software:

• Solaris 10 10/08
• Solaris 10 5/09

Workaround:

For the above memory configuration, placing the dimms in the following order does not cause this issue

8Gb dimms in D1,D4,D7 and 4Gb dimms in D2, D5, D8

Arrange dimms to ensure that all dimms within a channel are the same capcity.

The Solaris 10 patch 136914-01 is available on http://sunsolve.sun.com.

6731637

Boot Disk Size Limitation

Issue:

Solaris 10 05/09 will not install on a disk device that is greater than 1TB in size.

Affected Hardware, Operating Systems, and Software:

• Sun Fire X4170, X4270, and X4275 Servers
• Solaris 10 05/09
• Supplemental Releases 1.0, 1.2, 1.4, 2.0, 2.0.1, 2.1, 2.3.1, 2.4

Workaround:

This issue will be resolved in the next release of Solaris. Install the OS on a boot device that is 1TB or smaller.

6836590

High-Speed USB 2.0 Devices Might Not Enumerate Properly

Issue:

In rare cases when booting the Solaris Operating System, a USB initialization problem can occur that causes high-speed devices to go undetected by Solaris.

Affected Hardware, Operating Systems, and Software:

• Sun Fire X4170, X4270, and X4275 Servers
• Solaris 10 10/08
• Supplemental Releases 1.0, 1.2, 1.4, 2.0, 2.0.1, 2.1, 2.3.1, 2.4

Workaround:

Reboot Solaris. If USB enumeration issues persist across multiple consecutive reboots, then the problem is not due to this known issue. Initiate a service call.

6836594

DVD Drive Might Not Be Detected by Solaris, and Subsequently by BIOS

Issue:

In rare cases, when booting the Solaris Operating System, a USB initialization problem can occur that causes the system’s internal DVD drive and any devices attached to the front panel USB ports to go undetected by Solaris, even though the devices were seen by BIOS. Once this occurs, these devices will fail to be detected by both BIOS and Solaris for subsequent warm reboots.

Affected Hardware, Operating Systems, and Software:

• Sun Fire X4170 and X4270 Servers
• Solaris 10 10/08
• Supplemental Releases 1.0, 1.2, 1.4, 2.0, 2.0.1, 2.1, 2.3.1, 2.4

Workaround:

Turn the chassis main power off and then back on. If issues with the DVD or other USB devices persist for multiple consecutive power off/on cycles, then the problem is not due to this known issue. Initiate a service call.

6883310

On Systems Running the Solaris OS, Setting the Power Management Hardcap Power Limit Prior to Booting the System Does Not Control System Power

Issue:

If you set a power limit with timelimit=0 (none) prior to booting the system and the operating system (OS) is Solaris 10 05/09, the power limit is not adhered to by the system.

Affected Operating Systems and Software:

• Solaris 10 05/09
• Supplemental Release 2.1, 2.3.1, 2.4

Workaround:

After the OS is booted, do the following:

1. Disable the budget activation state.
2. Re-enable the budget activation state.

Note - This must be done each time after the OS is booted.

6974818

Black Screen Shows Occasionally When Booting OEL 5.4 XEN Kernel

Issue:

During power cycle testing on the Lynx X4270, and after several reboots of the OEL 5.4 XEN kernel, the server will occasionally hang and the screen go black.

Affected Hardware, Operating Systems, and Software:

• Sun Fire X4170, X4270, X4275 Server
• Oracle Enterprise Linux (OEL) 5.4; Red Hat Enterprise Linux
• Supplemental Releases 1.0, 1.2, 1.4, 2.0, 2.0.1, 2.1, 2.3.1, 2.4

Workaround:

Update inbox NIC driver version to igb-2.19 or higher.

6771120

Benign Error Messages Seen When Using RHEL 5.3

Issue:

When using RHEL 5.3, benign error messages might be seen in the boot logs. These benign messages are related to the PCI device probe of the Aspeed video device.

Example of benign error messages:

• PCI: Ignore bogus resource 6 [0:0] of 0000:20:05.0

Or

• PCI: Ignore bogus resource 6 [0:0] of 0000:35:05.0

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

Workaround:

These error messages are benign and have no effect on the system stability or performance.

6800672

ixgbe (1.3.53) Driver Is Not Supported on RHEL 5.3

Issue:

The latest ixgbe (1.3.53) driver from Intel cannot compile on RHEL 5.3 for PCI Express Single (1106A-Z) or Dual (1108A-Z or 1107A-Z) 10-Gigabit Ethernet unless the setting for Large Receive Offload is disabled.

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

Workaround:

Compile with the earlier ixgbe driver (1.3.47).

6801897

RHEL 4.7 ipmi_si Driver Does Not Load - IPMI Service Fails to Start

Issue:

IPMI service fails to start. RHEL 4.7 ipmi_si driver does not load with default parameters.

Affected Operating Systems and Software:

• Red Hat Enterprise Linux (RHEL) 4.7
• Supplemental Releases 1.0, 1.2, 1.4, 2.0, 2.0.1, 2.1, 2.3.1, 2.4

Workaround:

1. Edit /etc/modprobe.conf
2. Add the following line to change default ipmi_si driver parameters:

options ipmi_si type="kcs" ports=0xCA2 regspacings="4"

1. Save changes and exit.
2. Stop the service:

/etc/init.d/ipmi stop || service ipmi stop

1. Start the service:

/etc/init.d/ipmi start || service ipmi start

6816210

Intel’s PCI Express 10Gb Ethernet Cards Might Not Work With Some RHEL5.3 Inbox ixgbe Drivers

Issue:

There are issues with using RHEL 5.3 inbox ixgbe drivers and Intel’s PCI Express 10Gb Ethernet cards (with fixed transceivers) I/O devices. The RHEL 5.3 ixgbe drivers are:

• 1.3.18-k4
• 1.3.47-NAPI
• 1.3.56.5

The Intel I/O devices are:

• For Intel 1-port Fiber XFP SR (Oplin): X1106A-Z (PCIe)
• For Intel 2-port Fiber XFP SR (Oplin): X1108A-Z (EM) and X1107A-Z (PCIe)

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

Workaround:

To use these devices and RHEL 5.3, you will have to update the drivers.

6817764

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

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:

http://rhn.redhat.com/errata/RHBA-2009-0424.html

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

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

Please refer to the TID for information on the latest igb driver that fixes this issue.

15787147 (formerly SunBT 7163456)

Blue Screen Appears When Installing Windows 2008 64 Bit on a System With 2GB DIMMs. Will Only Install When 4GB DIMMs Are Installed

Issue:

Blue screen appears when loading Windows 2008 64 bit on the Sun Fire X4170 server with 2GB DIMMs installed.

Affected Operating Systems and Firmware:

• Windows Server 2008, Version 6.0 (Build 6002, Service Pack 2)
• SP Firmware Version 3.0.6.21

Workaround:

Use the latest Oracle Hardware Installation Assistant or the Tools and Drivers DVD to download the fixed Adaptec driver V16795, which resolves this issue.

6756232

CompactFlash Card Might Not Be Detected by Windows Setup Utility

Issue:

The Windows Server 2003, 2008, and 2008-R2 Setup Utility copies the system boot files to the first disk found in the boot order. Windows detects the CompactFlash (CF) device as an ATA class device but, it is attached via the USB bus. The drives attached via USB are not supported by Microsoft for Windows Server as system boot devices.

Affected Operating Systems and Software:

• Windows Server 2008
• Windows Server 2008-R2
• Windows Server 2003
• Supplemental Releases 1.0, 1.2, 1.4, 2.0, 2.0.1, 2.1, 2.3.1, 2.4

Workaround:

The CF card must be lower in the Boot Device Priority List than the target disk. For more information, see the BIOS section in the Sun Fire X4170, X4270, and X4275 Servers Service Manual (820-5830).

6783538

Blue Error Screen Might Appear When the Infiniband Host Channel Adapter Is Disabled in Windows Device Manager

Issue:

If the X4237A Infiniband Host Channel Adapter card is disabled in Windows Device Manager, Windows Server 2008 stops in a Blue Screen with Bug Check 0x122 - General WHEA Error indicated.

Affected Operating Systems and Software:

• Windows Server 2008
• Supplemental Releases 1.0, 1.2, 1.4, 2.0, 2.0.1, 2.1, 2.3.1, 2.4

Workaround:

Do not disable the X4237A card in Windows Device Manager. If the card is disabled causing the Blue Screen with Bug Check 0x122, reboot the host system to recover. The X4237A card will be enabled upon reboot. Check for the availability of a patch for this defect.

6803931

After Installation, Windows Might Have a Device That Is Marked With a Yellow Exclamation Point in the Device Tree Found in Windows Device Manager

Issue:

After installation of Windows Server 2003 on the Sun Fire X4275 Server, Windows might have a device that is marked with a yellow exclamation point (Yellow Bang) in the device tree found in Windows Device Manager. This device will be found under Other Devices in the device tree, and the name of the device is "LSILOGIC SASX28 A.1 SCSI Enclosure Device.” Note that there is no functional impact to the system should this occur. The only indication is the Yellow Bang seen in Device Manager. This problem is not encountered in Windows Server 2008.

Affected Hardware, Operating Systems, and Software:

• Sun Fire X4275 Server
• Windows Server 2003
• Supplemental Releases 1.0, 1.2, 1.4, 2.0, 2.0.1, 2.1, 2.3.1, 2.4

Workaround:

To resolve the problem, download and install the Sun Fire X4275 Server Tools and Drivers DVD.

To download the Sun Fire X4275 Tools and Drivers DVD:

1. Go to http://www.sun.com and click Downloads & Trials and select Top Downloads from the drop-down list.
2. Click the Downloads A-Z tab on the Sun Downloads page.
3. Find and click Sun Fire X4275 Server Tools and Drivers DVD in the alphabetical listing.
4. Download the Tools and Driver package and locate the latest Tools and Drivers CD image or the latest Sun Installation Assistant CD image depending upon your choice of installation method.
5. Install the driver for the LSI SAS x28 Expander (file lsinodrv.inf). This driver can be found on the Tools and Drivers DVD under Windows\w2k3\i386ısi for 32-bit or Windows\w2k3\amd64ısi for 64-bit. Once the new driver has been installed, the LSI device is no longer marked with a Yellow Bang, and it can be found under System Devices in Windows Device Manager with the new name of LSI SAS x28 Expander.

6820942

Windows Server 2008 64-bit Does Not Install to Local Disk With a QLogic PCIe Card Installed

Issue:

When installing Windows Server 2008 to the internal SAS/SATA disk or array on a system that includes a 4 Gigabit/second Dual-Port Fiber Channel PCI-Express Card (SG-XPCIE2FC-QF4), the system might crash and reboot if the option card is attached to an external storage area network (SAN).

Note - This is not a problem if the target for the operating system is the external SAN.

Affected Operating Systems and Software:

• Windows Server 2008 (64-bit)
• Supplemental Releases 1.0, 1.2, 1.4, 2.0, 2.0.1, 2.1, 2.3.1, 2.4

Workaround:

Do not attach the SAN array until after the operating system is installed to local disk(s). Check for the availability of a patch for this defect. This problem will be fixed in Service Pack 2 from Microsoft.

6820950

LSI MegaRaid Storage Manager Does Not Work Properly When Installed With Intel Network Connections Software in Microsoft Windows Server 2003 (x64)

Issue:

After installing the MegaRaid Storage Manager and Intel Network Connections (NIC) Teaming, the mrmonitor service stops unexpectedly and cannot start.

Affected Operating Systems and Software:

• Windows Server 2003 (for x64 servers)
• Supplemental Releases 1.0, 1.2, 1.4, 2.0, 2.0.1, 2.1, 2.3.1, 2.4

Workaround:

Do not install the NIC Teaming software if the LSI Storage Manager software is required.

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 T&D 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 T&D 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, 2.1, 2.3.1, 2.4

Workaround:

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

Check for the availability of a fix in updates to the T&D DVD software.

6856639

Installation of Windows Server 2008 R2 Stalls During the "Completing installation..." Phase

Issue:

There is a potential issue with Sun Fire X4170, X4270, and X4275 Servers when installing Windows Server 2008 R2. During the installation the system stalls at the "Completing installation..." phase of Windows setup. The mouse will still respond, but no progress is made and the installation will not complete. If the system is restarted, setup will be incomplete and must be restarted.

Affected Hardware, Operating Systems, and Software:

• Sun Fire X4170, X4270, and X4275 Servers
• Windows Server 2008 R2
• In-box Ethernet Controller driver that ships with Windows Server 2008 R2
• Supplemental Releases 1.0, 1.2, 1.4, 2.0, 2.0.1, 2.1, 2.3.1, 2.4

Workaround:

You can resolve this issue by installing an updated Ethernet Controller driver during the installation procedure so that it replaces Microsoft’s in-box driver in Windows Server 2008 and Windows Server 2008 R2.

The required updated driver is included on the Tools and Drivers (T&D) DVD for server Software 2.1. Also included on the T&D DVD is an AutoUnattend.xml file and the following instructions:

• How to copy the AutoUnattend.xml and driver files to a USB thumb drive (or similar removable-media drive)
• How to use the USB thumb drive to replace the in-box Ethernet Controller driver during the installation of Windows Server 2008 R2

The instructions are in the following directory on the T&D DVD:

<DVD>\windows\w2k8r2\drivers\readme.html

The T&D DVD for Software 2.1 is available for download at the following locations:

• For the Sun Fire X4170 Server: http://www.sun.com/servers/x64/x4170/downloads.jsp
• For the Sun Fire X4270 Server: http://www.sun.com/servers/x64/x4270/downloads.jsp
• For the Sun Fire X4275 Server: http://www.sun.com/servers/x64/x4275/downloads.jsp

6879304

Windows Server 2008 R2 Generates System Event Log Warning Messages When Power Is Being Limited by ILOM Power Management

Issue:

When power is being limited by the ILOM Power Management feature, the Windows Server 2008 R2 operating system will generate warning messages in the System Event Log informing the user that the processor(s) are being restricted. Example Event: The Speed of Processor xx in group x is being limited by system firmware. The processor has been in this reduced performance state for xxxx seconds since last report.

Affected Hardware, Operating Systems, and Software:

• All Sun servers with Power Management support
• Windows Server 2008 R2
• Supplemental Release 2.1

Workaround:

None needed. These are expected events and are not indicative of a problem.

6835303

SIA Installation Does Not Work Correctly When Installing an ISO Image of the Red Hat Operating System Using NFS

Issue:

If you elect to install the Red Hat operating system from an ISO image that is exported using a network file system (NFS) server, profiles for the Red Hat installation will not be propagated to the installation. This will result in the following behavior:

• Anaconda will prompt the user for the installation type (desktop, client, server, or minimal).
• Individual packages will not be pre-selected based on the installation type, and the user will have to select these manually.

Affected Operating Systems and Software:

• Red Hat Enterprise Linux (RHEL) 4.x and 5.x
• Supplemental Releases 1.0, 1.2, 1.4, 2.0, 2.0.1, 2.1, 2.3.1, 2.4

Workaround:

When using SIA to install the Red Hat operating system, do not use an ISO image exported using NFS.

6805366

AHCI Device Driver Is Not Installed if SIA Is Used to Install Windows Server 2003 to RAID

Issue:

If you are installing to an LSI or Sun StorageTek Raid HBA, SIA might not automatically install the AHCI device driver for Windows 2003 installations. SIA will copy the AHCI device driver to disk (install target) but you might need to install this driver using Windows Device Manager.

Affected Operating Systems and Software:

• Windows Server 2003
• Supplemental Releases 1.0, 1.2, 1.4, 2.0, 2.0.1, 2.1, 2.3.1, 2.4

Workaround:

Any of the following is an acceptable workaround for this issue:

• Use Windows Device Manager to install the AHCI device driver that was copied to disk (install target). For instructions for using Device Manager to update or install device drivers, refer to the Windows Device Manager documentation.
• Restart the SIA installation, and accept the automatic SIA updates when presented with the option.
• Download the latest SIA CD for this platform from http://www.sun.com and restart the installation.

6861956

SIA Installation Does Not Work Correctly When Installing an ISO Image of the Red Hat Operating System Using NFS

Issue:

If you elect to install the Red Hat operating system from an ISO image that is exported using a network file system (NFS) server, profiles for the Red Hat installation will not be propagated to the installation. This will result in the following behavior:

• Anaconda will prompt the user for the installation type (desktop, client, server, or minimal).
• Individual packages will not be pre-selected based on the installation type, and the user will have to select these manually.

Affected Operating Systems and Software:

• Red Hat Enterprise Linux (RHEL) 4.x and 5.x
• Supplemental Releases 1.0, 1.2, 1.4, 2.0, 2.0.1, 2.1, 2.3.1, 2.4

Workaround:

When using SIA to install the Red Hat operating system, do not use an ISO image exported using NFS.

6864864

SIA Will Cause Kudzu to Be Run for Red Hat 4.7 x64 Installations With Emulex Cards

Issue:

When an installed system is booting for the first time, SIA unintentionally causes Kudzu, a Red Hat hardware configuration utility, to be run for Red Hat 4.7 x64 installations with Emulex Cards.

Affected Operating Systems and Software:

• Red Hat Enterprise Linux 4.7 64-bit
• Supplemental Release 2.1, 2.3.1, 2.4

Workaround:

Configure the Emulex cards through the Kudzu interface.

6944969

Locating Faulty DIMMs Differs in ILOM Mapping Versus BIOS Mapping

Issue:

ILOM and BIOS use different formats to identify the location of a faulty DIMM.

• For ILOM, the format is Px/Dx, where x is 0 or 1 for CPUs, and 0 to 8 for DIMMs.
• For BIOS, the format is CPUx/CHANNELx/DIMMx, where x is 0 or 1 for CPUs, and 0 to 2 for channels and DIMMs.

Affected Software:

• ILOM SP firmware version 3.0.9.19.a
• BIOS firmware version 07.06.02.23

Workaround:

The different formats will be documented in the next version of the Lynx Service Manual (820-5830).

6779289

Missing Content for Platform-Specific ILOM Sideband Management Feature

Issue:

The ILOM Sideband Management topic in the Sun Integrated Lights Out Manager (ILOM) 2.0 Supplement for Sun Fire X4170, X4270, and X4275 Servers (820-7629) is missing some special considerations.

Corrected Information:

Special Considerations for Sideband Management:

When Sideband Management is enabled in ILOM, the following conditions might occur:

• In-chip connectivity between the SP and the host operating system might not be supported by the on-board host Gigabit Ethernet controller.

If this condition occurs, use a different port or route to transmit traffic between the source and destination targets instead of using L2 bridging/switching.

• Server host power cycles might cause a brief interruption of network connectivity for server Gigabit Ethernet ports (NET 0, 1, 2, 3) that are configured for sideband management.

If this condition occurs, configure the adjacent switch/bridge ports as host ports.

Note - If the ports are configured as switch ports and participate in the Spanning Tree Protocol (STP), you might experience longer outages due to spanning tree recalculation.

6840674

SAS Expander Card Sensor Is Not Documented

Issue:

The /SYS/SAS_EXP/PRSNT sensor is not documented for ILOM 2.0. This sensor detects whether the SAS Expander Card is installed. This card connects to the disk drive backplane.

Corrected Information:

The following information will be added to the Sun Integrated Lights Out Manager (ILOM) 2.0 Supplement for Sun Fire X4170, X4270, and X4275 Servers (820-7629):

• Sensor Name: /SYS/SAS_EXP/PRSNT
• Sensor Type: Entity Presence
• Description: SAS Expander Card present monitor

Note - This card connects to the disk backplane and the SAS cable connects to it.

Note - This sensor is only supported on the Sun Fire X4275 Server.

6851878

Missing Content for Server Ambient Temperature Sensors

Issue:

The sensor descriptions in the Sun Integrated Lights Out Manager (ILOM) 2.0 Supplement for Sun Fire X4170, X4270, and X4275 Servers (820-7629) do not indicate where the /SYS/MB/T_AMB and /SYS/T_AMB sensors are located.

Corrected Information:

• /SYS/MB/T_AMB: The motherboard ambient temperature sensor is located on the front end of the motherboard directly behind the storage drives.
• /SYS/T_AMB: The system ambient temperature sensor is located on the underside of the fan board.