1.0

2.0.2.8

1.0

1.2

2.0.2.18

1.07

1.3

2.0.2.20

1.12

1.3.1

2.0.2.20 r49755

1.14

2.0

3.0.3.35

1.07

2.1

3.0.3.35.a

1.12

2.1.1

3.0.3.35.a r49758

1.14

2.2.0

3.0.9.18 r55822

2.03

2.2.1

3.0.9.18 r57886

2.03

6969114

Web GUI Upgrade to SW 2.2.0 Resets All ILOM Settings to Defaults

Issue:

Upgrading an X2270 system to firmware bundle SW 2.2.0 (ILOM 3.0.9.18 build r55822 / BIOS 2.03) using the web GUI results in the reset of all ILOM settings to defaults even if the "preserve settings" option is selected. This problem does not occur when the firmware is upgraded using the CLI.

Affected Software:

• Supplemental Release 2.2.0

Fix Available:

A fix is now available in Supplemental Release 2.2.1, ILOM3.0.9.18 r57886. If you have lost your IP address as a result of the update, instructions to configure the SP network using the ipmitool in the host OS can be found in the ILOM 3.0 Documentation Collection at http://docs.sun.com/apps/docs/prod/int.lights.mgr30#hic

1. Install latest ipmitool released by Sun, latest version is v1.8.10.3. (Or the version with "sunoem cli" command)

2. Open SP CLI interface with ipmitool in Host OS, then configure the SP network using the following commands:

nsgsh-dhcp-242:~ # ipmitool -V

ipmitool version 1.8.10.3

nsgsh-dhcp-242:~ # ipmitool -I open sunoem cli Connected. Use ^D to exit.

-> cd /SP/network

cd /SP/network

/SP/network

-> set pendingipaddress=xx.xxx.xx.xxx

set pendingipaddress=xx.xxx.xx.xxx

-> set pendingipdiscovery=static

set pendingipdiscovery=static

-> set commitpending=true

set commitpending=true

Note - Use "-I bmc" in Solaris OS, but use "-I open" in Linux OS to specify kcs interface.

6795975

Multiple Remote ILOM Console Sessions Might Not Work Correctly

Issue:

When multiple 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.

Fix Available:

Fix is now available in Supplemental Software release 2.2.0

6839546

IPMI GUID Changes When Switching ILOM Management Between Sideband and Out-of-Band

Issue:

When switching ILOM management between sideband and out-of-band, the IPMI GUID will change. This unexpected behavior might affect applications that use IPMI GUID for system management (for example, Sun xVM Ops Center) or for deployments that use SMBIOS UUID for server provisioning. Ensure that the ILOM configuration for sideband or out-of-band is complete prior to configuring third-party system management or server provisioning tools.

Fix Available:

Fix is now available in Supplemental Software release 2.2.0

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

• Supplemental Releases 1.2, 1.3, 2.0, 2.1
• Sun ILOM Remote Console
• JDK 160
• Windows operating system installed on client system

Fix Available:

Fix is now available in Supplemental Software release 2.2.0

6788702

Enhanced IDE Mode Is Not Supported With SIA

Issue:

If you are installing Linux with Sun Installation Assistant (SIA), no disks will be found if the onboard controller is configured for Enhanced IDE mode.

Affected Software:

• Red Hat Enterprise Linux 4.7/5.3 and SUSE Linux Enterprise Server 10 SP2
• Supplemental Releases 1.0, 1.2, 1.3, 2.0, 2.1

Fix Available:

Fix is now available in Supplemental Software release 2.2.0

6849217

BIOS Might Allow Security Vulnerabilities

Issue:

Security vulnerabilities in the BIOS might allow a local privileged user that has the ability to run fully privileged code to gain access to the CPU’s System Management Mode or execute arbitrary code in the BIOS.

6937671

Selectable De-emphasis Value is 6dB in BIOS Default Setting

Issue:

After loading Optimal Defaults in BIOS, the selectable de-emphasis value appears as 6dB. The value should be 3.5 dB.

Workaround:

Manually change the setting from 6db to 3.5db in the BIOS setup.

66894296

BIOS 1.14 Default/Optimal Settings (Max AHCI Ports) Are Set to 4 Ports

Issue:

Current release BIOS 1.14 has "Max Ports on SATA#1" BIOS option default/optimal settings as "4 Ports". In that setting the MB FMOD ports will be forced to operate off of the slower IDE settings and not AHCI. The default should be "6 Ports" so that the FMOD ports will operate of AHCI.

Workaround:

Fix will be available in BIOS 1.15.

N/A

OK to Remove/Fault LED Label Not Supported

Issue:

The HDD Coral brackets have a label for the OK to Remove/Fault LED.

Affected Hardware and Software:

• Supplemental Releases 1.0, 1.2, 1.3, 2.0, 2.1, 2.2

Workaround:

The LEDs are not supported on the Sun Fire X2270 Server.

6790472

Virtual CD/DVD-ROM Not Available Via Redirection in Solaris

Issue:

When the Sun Fire X2270 Server is running Solaris and another system is connecting to a RKVM session via the X2270 SP, the virtual CD-ROM will not mount on the Solaris system until volmgt is stopped.

Affected Hardware and Software:

• Supplemental Releases 1.0, 1.2, 1.3, 2.0, 2.1, 2.2

Workaround:

To stop volmgt, type the command: /etc/init.d/volmgt stop

6750934

Eth1 Is Not Configured During SP Boot Up

Issue:

The following error is received during SP boot up:

Setting up IP spoofing protection: rp_filter.Configuring network interfaces...FTGMAC100: eth1:ftgmac100_open mach/timer.c: Just lost 2 clock interrupts.SIOCSIFNETMASK: Cannot assign requested address <===SIOCSIFBRDADDR: Cannot assign requested address <===Failed to bring up eth1. <===

The interface (eth1) will vary depending on which network port is not configured. In the above error example, eth1 was displayed because out-of-band (OOB) management port /SYS/SP/NET0 (eth0) was not configured.

Affected Hardware and Software:

• Supplemental Releases 1.0, 1.2, 1.3, 2.0, 2.1, 2.2

Workaround:

None.

N/A

DIMM and CPU LEDs Do Not Illuminate on Systems That Do Not Contain Service Processors

Issue:

The DIMM and CPU LEDs do not illuminate to indicate an error condition in servers that do not contain a service processor. DIMM and CPU error LEDs require the optional service processor module to operate correctly.

Affected Hardware and Software:

• Supplemental Releases 1.0, 1.2, 1.3, 2.0, 2.1, 2.2

Workaround:

None.

N/A

Bottom USB Port on Motherboard Cannot Be Used

Issue:

Due to mechanical reasons, the bottom USB port that is located internally on the chassis motherboard cannot be used.

Affected Hardware and Software:

• Supplemental Releases 1.0, 1.2, 1.3, 2.0, 2.1, 2.2

Workaround:

Use the top USB port on the chassis motherboard.

6803145

SNMPv3 Traps Are Not Received When Using MD5 Authentication

Issue:

SNMPv3 traps are not being received when MD5 authentication is used in the server configuration. The behavior is the same when MD5 authentication is selected with DES encryption or with no (None) encryption.

Affected Hardware and Software:

• Supplemental Releases 1.0, 1.2, 1.3, 2.0, 2.1, 2.2

Workaround:

None. Check for the availability of a patch for this defect.

N/A

Entering the RAID Configuration Utility

Issue:

When configuring a system for RAID in the system BIOS, the Intel RAID utility screen that lets users access the utility might flash too quickly on the screen, causing users to miss which keys to select in order to enter the utility.

Affected Software:

• Supplemental Releases 1.0, 1.2, 1.3, 2.0, 2.1, 2.2

Workaround:

If this occurs, select Ctrl + I after the initial POST screen when the system performs the memory test.

N/A

SP Console Serial Port Inherits Host Settings

Issue:

When the serial port is switched from the Host console (where it is sitting in the system BIOS configuration) to the SP console (where it is sitting during the login prompt), the SP console login prompt changes to all CAPS. All further characters that are typed at the console are entered as CAPS.

Affected Software:

• Supplemental Releases 1.0, 1.2, 1.3, 2.0, 2.1, 2.2

Workaround:

Select Ctrl + C to return to a normal login prompt.

N/A

Date and Time Do Not Match Between BIOS and Service Processor

Issue:

If the SP and BIOS firmware is corrupted and then recovered, the SP and BIOS time will not match.

Affected Software:

• Supplemental Releases 1.0, 1.2, 1.3, 2.0, 2.1, 2.2

Workaround:

Manually update the SP and BIOS date and time, or configure ILOM to use a network time protocol (NTP) server.

6809522

BIOS Only Boots From the First HDD Listed in the Boot List Order

Issue:

Using /SP/Bootlist to control the boot order via ILOM, the BIOS will only boot from the first hard disk drive (HDD) listed.

Affected Software:

• Supplemental Releases 1.0, 1.2, 1.3, 2.0, 2.1, 2.2

Workaround:

If you need to boot from another HDD listed in the boot order, change the HDD to the primary boot disk in the BIOS boot order list.

6716289

Memory Count at Startup is 8MB Short

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.3, 2.0, 2.1, 2.2

Workaround:

None. Check for the availability of a patch for this defect.

6878145

Kernel Panic Occurs During The ILOM Boot Process

Issue:

The following timeout failures occur during the ILOM boot process:

• Timeout getting ’fru_version’ attribute for ’/SYS/MB/BIOS’
• Timeout waiting for sunservice password prompt
• Timeout waiting for login prompt after reboot
• Timeout waiting for SP login

Affected Hardware and Software:

SP daughter card 373-0429-01

Workaround:

Contact Sun Service and replace the SP daughter card with FRU F373-0429-02.

6800702, 6813782

Storage Redirection Not Supported on Sun ILOM Remote Console

Issue:

An attempt to start storage redirection might fail when using a 64-bit JRE (Java runtime environment) to launch the Sun ILOM Remote Console. 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 appears.

Affected Software:

• Supplemental Releases 1.0, 1.2, 1.3, 2.0, 2.1, 2.2

Workaround:

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

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

6937202

Start/Reset/SYS Causes Several KCS Command: Master Write Read: Logs To Be Generated

Issue:

Between 1000 and 2000 KCS Command: Master Write Read: logs are generated during a system start or reset. For example:

5947 Mon Nov 15 05:50:03 2010 Audit Log minor

KCS Command : Master Write Read : channel number = 0 : bus ID = 1 : bus type = private : slave address = 0x2E : read count = 0 : write data = 0x0 0x2A : success

5946 Mon Nov 15 05:50:03 2010 Audit Log minor

KCS Command : Master Write Read : channel number = 0 : bus ID = 1 : bus type = private : slave address = 0x3E : read count = 0 : write data = 0x0 0x3F : success

5945 Mon Nov 15 05:50:03 2010 Audit Log minor

KCS Command : Master Write Read : channel number = 0 : bus ID = 1 : bus type = private : slave address = 0x2E : read count = 0 : write data = 0x0 0x2E : success

This is an expected behavior in current BIOS and ILOM implementations because it is designed to record all these transactions in the log.

Affected Software:

• Supplemental Release 2.2.0

Workaround:

If you want to see specific event logs, go to the ILOM Web browser interface and select System Monitoring->Event log, use the filter to filter out these massive events.

N/A

Hitachi 1TB HDD Does Not Come Back Online

Issue:

When hot-plugging an Hitachi 1TB hard disk drive (HDD) on a server that is running the Solaris 10 OS, the HDD does not come back online.

Affected Software:

• Solaris 10 5/09
• Supplemental Releases 1.0, 1.2, 1.3, 2.0, 2.1, 2.2

Workaround:

Open a terminal window and type the cfadm -x sata_port reset command to bring the HDD back online.

6764573

USB KVMS Redirected Keyboard and Storage Will Not Work With Intel VT-d Enabled

Issue:

USB devices used for remote KVMS redirected keyboard and storage will not work with Intel VT-d enabled. An installation over redirected DVD might start, then hang after an IOMMU fault message is displayed on the console. The redirected USB keyboard will also hang. Other devices might be affected as well. When the failure occurs, IOMMU faults will display a message similar to:

WARNING: dmar0,0 generated a fault event when translating DMA read on address 0x0 for PCI(0, 26, 7), the reason is: The Read field in a page-table entry is Clear when DMA read

WARNING: /pci@0,0/pci1028,235@1a,7 (ehci0): Unrecoverable USB Hardware Error.

Affected Software:

• OpenSolaris 2008.11
• Supplemental Releases 1.0, 1.2, 1.3, 2.0, 2.1, 2.2

6764573 Continued

Workaround:

Perform one of the following procedures:

• Disable VT-d in BIOS:

At system start-up, press F2 after POST to enter BIOS Setup.

Choose Advanced tab then disable the setting for VT-d.

Or

• Disable intel-iommu in Solaris GRUB menu:

Note - Help for editing the GRUB menu is available at the bottom of each screen.

1. During installation, modify the GRUB menu by adding:
   -B intel-iommu=no
2. When the GRUB menu appears, type 'e' to edit then scroll to the appropriate boot entry.
3. Using the arrow keys, select the line that looks like this:

kernel$ /platform/i86pc/kernel/$ISADIR/unix

4. Press 'e' to edit the entry.

5. Append -Bintel-iommu=no to the line so that it looks like this:

kernel$ /platform/i86pc/kernel/$ISADIR/unix -Bintel-iommu=no

6. Press Enter then press 'b' to boot.

If you are adding this boot option to a list of existing options, note that the delimiter for boot options is a comma.

For example:

kernel$ /platform/i86pc/kernel/$ISADIR/unix -Bconsole=ttya,intel-iommu=no

7. After the installation completes, repeat the GRUB editing step outlined above prior to boot.

Boot, and edit /platform/i86pc/kernel/drv/rootnex.conf, adding the line:

intel-iommu=no

8. After installation, modify:

/platform/i86pc/kernel/drv/rootnex.conf, adding intel-iommu=no

9. Rebuild the boot archive by typing:

bootadm update-archive

6794301

Boot Disk Size Limitation

Issue:

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

Affected Operating Systems and Hardware:

• Solaris 10 10/08
• Supplemental Releases 1.0, 1.2, 1.3, 2.0, 2.1

Workaround:

Install the OS on a boot device that is 1TB or smaller.

N/A

IPMI Service Fails to Start

Issue:

IPMI service fails to start in RHEL 4.7 and SLES10 SP2.

Affected Software:

• Red Hat Enterprise Linux (RHEL) 4.7 and SUSE Linux Enterprise Server 10 SP2
• Supplemental Releases 1.0, 1.2, 1.3, 2.0, 2.1

Workaround:

To start IPMI service:

1. Review the dmidecode output to determine the KCS base port address.

For example, Base Address: 0x000000000000CA2 (I/O)

1. From the terminal window, type the following command, entering the base address from the previous step for <base address>.

modprobe ipmi_si type=”kcs” ports=<base address> regspacing=”4”

1. To start the IPMI service, type the following command:

service ipmi start

N/A

Mouse Cursor Disappears

Issue:

The mouse cursor disappears after running the install.sh script on SLES10 SP2.

Affected Software:

• SUSE Linux Enterprise Server 10 SP2
• Supplemental Releases 1.0, 1.2, 1.3, 2.0, 2.1

Workaround:

After running the script, restart the server by using the keyboard hot keys or a command line entry from the terminal window. Once the server restarts, the mouse cursor will reappear.

N/A

Mouse Moves Erratically During SLES10 SP2 Installation

Issue:

The mouse experiences erratic movements during the SLES10 SP2 installation.

Affected Software:

• SUSE Linux Enterprise Server 10 SP2
• Supplemental Releases 1.0, 1.2, 1.3, 2.0, 2.1

Workaround:

Log in to ILOM, navigate to the Remote Control --> Mouse Mode Settings tab. From the Mouse Mode drop-down list, select Relative.

6783673

Windows Server 2008 Might Require Hotfix for PCI Express Bus Driver

Issue:

Microsoft has an updated PCI bus driver for PCI Express that addresses a potential bug where the Max Payload Size might be configured incorrectly on the PCI Express root port if the root port is disabled and then re-enabled.

Affected Software:

• Windows Server 2008
• Supplemental Releases 1.0, 1.2, 1.3, 2.0, 2.1

Workaround:

There is a Knowledge Base Article (http://support.microsoft.com/kb/952681) that has a link to a hotfix, which the end-user can download if the problem is encountered in the field. The problem should be addressed when Service Pack 2 is released.

6783538

Windows Server 2008 Displays a Blue Screen Error if the X4237A IB Adapter Card Is Disabled

Issue:

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

Affected Software:

• Windows Server 2008
• Supplemental Releases 1.0, 1.2, 1.3, 2.0, 2.1

Workaround:

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

N/A

Windows Server 2003 Installation Requires a Boot Driver

Issue:

If installing Windows Server 2003 32/64-bit in AHCI mode, a boot driver is required.

Affected Software:

• Windows Server 2003
• Supplemental Releases 1.0, 1.2, 1.3, 2.0, 2.1

Workaround:

The floppy driver/floppy image can be located on the Sun Fire X2270 Server Tools & Drivers CD.

N/A

Windows Server 2008 Detects Disk Ordering Differently

Issue:

If installing Windows Server 2008 OS, the OS will detect the disk ordering differently than the BIOS when in AHCI mode.

Affected Software:

• Windows Server 2008
• Supplemental Releases 1.0, 1.2, 1.3, 2.0, 2.1

Workaround:

Install the AHCI driver from the Tools & Drivers CD prior to partitioning the disk during the Windows OS installation. Once the updated AHCI driver is installed, the disk layout will be detected correctly. For instructions on installing the AHCI driver, see the Sun Fire X2270 Server Windows Operating System Installation Guide (820-7143).

6956659

SIA 2.3.18.0: Incorrect Driver Information Messages in OS Installation Completed Page

Issue:

During installation of SIA 2.3.18.0, the following message appears:

Installing tpm,csc,drivers... completed

The tpm driver is only for Windows 2003.

Affected Software:

• Supplemental Releases 1.0, 1.2, 1.3, 2.0, 2.1, 2.2

Workaround:

The tpm messages will be removed from non-Windows 2003 pages in the next release.

6796419

OS Will Not Boot if Installing SLES With SIA in IDE Mode

Issue:

If you are installing SLES 10 SP2 with Sun Installation Assistant (SIA) and the onboard controller is configured in IDE mode, the OS will not boot after installation.

Affected Software:

• SUSE Linux Enterprise Server 10 SP2
• Supplemental Releases 1.0, 1.2, 1.3, 2.0, 2.1

Workaround:

Choose one of the following workarounds:

• Install SLES 10 SP2 without the use of the Sun Installation Assistant.
• Do not use IDE mode for the onboard controller. Instead, use the default AHCI mode.
• If you must use IDE mode, manually edit the GRUB menu by performing the following procedure:
• During the installation, choose the OS you want to boot.
• In the Boot Options field, add the following:

root=/dev/sda2 resume=/dev/sda1

1. To make these changes permanent, do the following:

a. After the OS is started, modify the GRUB menu by typing the following command in a terminal window:

vi /boot/grub/menu.1st

b. Modify the root= entry in the kernel line for GRUB menu entries:

title Linux

title Failsafe

with the following:

root=/dev/sda2

Note that the root= entry will be similar to the following:

root=/dev/diskby-id/ata-

SEAGATE_STN7250SBSUN500G_0703C0MRBS_5QG0MRBS-part2

Similarly, change the resume= entry from resume=/dev/hda1 to resume=/dev/sda1

c. Save /boot/grub/menu.1st by typing the following command:

:wq

6821555

SIA Allows Windows Server 2003 32-bit R2 to Be Installed

Issue:

Sun Installation Assistant allows Windows Server 2003 32-bit R2 to be installed on the server. SIA should only allow the SP2 version of the OS to be installed on the server, that is, Windows Server 2003 32-bit R2 SP2.

Affected Software:

• Windows Server 2003
• Supplemental Releases 1.0, 1.2, 1.3, 2.0, 2.1

Workaround:

None.