Sun Fire X2250 Server Product Notes

This document contains late-breaking information and issues for the
Sun Firetrademark X2250 server.

The following sections are included in these product notes:


General Information

Support for Sun Fire Servers

Support information for the Sun Fire X2250 server is available at:

http://www.sun.com/servers/x64/x2250/support.xml

Supported Operating Systems

The following is a list of the minimum versions of supported operating systems for the Sun Fire X2250 server:

Documentation

Support documentation for the Sun Fire X2250 server includes:

These and other Sun Fire server documents are available at http://docs.sun.com.


Sun Fire X2250 Server Tools & Drivers CD

The Sun Fire X2250 Server Tools & Drivers CD contains several software applications and utilities for use with your Sun Fire X2250 server. This section describes the applications and utilities and refers you to the associated readme text files where you can find procedures for running them.



Note - This utility can be performed on a Windows-based system or a Linux/Solaris-based system.



Latest Firmware Updates

The Sun Fire X2250 server is shipping with the initial release of BIOS and Integrated Lights Out Manager (ILOM) firmware. Currently, there are no firmware updates available.


Newly Supported Options

The Sun Fire X2250 server supports the following new options:

Serial Port Sharing

The Sun Fire X2250 server supports serial port sharing. Configured via the system BIOS, this feature lets you switch the serial port output between the host (COM1) or the Service Processor (SP) serial console.

To switch the serial port output:

1. During system boot, type F2 to enter the system BIOS.

2. Select IPMI 2.0 Configuration > External Serial Port.

3. Choose BMC to direct the serial port output to the SP serial console; choose System to direct the serial output to the host (COM1).

4. Exit the system BIOS and save changes to the configuration.

PCI-E Max Payload

The Sun Fire X2250 server includes the PCI-E Max Payload setting in the BIOS setup menu. To access this setting, select F2 during system boot to enter the system BIOS. Select Advanced > PCI Configuration.

SF Bypass

The Sun Fire X2250 server includes the SF Bypass setting in the BIOS setup menu. SF Bypass enables and disables the Snoop Filter. To access this setting, select F2 during system boot to enter the system BIOS. Select Advanced > Memory.


Documentation Issues

The following issues apply to the Sun Fire X2250 server documentation set:

PCI Riser Card

The PCI riser card documented in the Sun Fire X2250 Server Service Manual (820-4593), section 4.5.2 incorrectly shows a 2-slot riser card in Figures 4-6, 4-7, and 4-8. Though a 2-slot riser card will fit into the server chassis, the lower slot will be unusable due to interfering components on the motherboard.

Resetting the SP Password and BIOS Password

The procedures documented in “How to Reset the Service Processor and BIOS Passwords” in the Sun Integrated Lights Out Manager Supplement for Sun Fire X2250 Server (820-4596) are incorrect.

To reset the Sun Fire X2250 server SP password, follow the procedures in the Sun Integrated Lights Out Manger 2.0 User’s Guide (820-1188).

The Administrator password becomes changeme.

CPU Replacement Rules for the Sun Fire X2250

Change Request ID: 6834049

The procedures documented in section 4.5.13 “Installing a New CPU” and section 4.5.12 “Replacing a CPU and Heatsink” in the Sun Fire X2250 Server Service Manual (820-4593) should include the following CPU replacement rules:


Hardware and BIOS Issues

The following issues apply to the Sun Fire X2250 server hardware and/or BIOS:

Front USB Port Cable Limitations

The front USB ports support only a 3-meter cable to an attached device.

Incorrect Network Settings Recorded When DHCP Server Is Offline

If ILOM is set to use a DHCP-assigned IP address, and the DHCP server is offline, wait until the DHCP server is online before attempting to reboot. Issuing a reboot or manually changing from DHCP to a static IP address will result in incorrect Gateway and IP address settings to be recorded. Once the DHCP server is restored, the original IP address will be assigned by DHCP.

Workaround:

Do not reboot the server until DHCP is restored. If access is urgently required to ILOM, connect a terminal to the serial console’s NET Management port and manually assign a static IP address.

Leading Zero in IP Address Causes an Invalid
IP Address Error

If a leading zero is placed in any of the four IP address octets, ILOM will report an invalid IP address error. For example, entering 10.29.54.02 or 10.029.54.2 will cause an error due to the leading zero.

Workaround:

Do not use leading zeros in the IP address. This issue will be fixed in a future firmware release.

BIOS Boot Order Issue

If a USB device (Flash, HDD, FDD, CD ROM, etc.) is inserted into the system, these devices are assigned lower boot priority. For example, a USB HDD will be recognized as a HDD but will be considered a third-priority HDD in relation to the two onboard devices.

Workaround:

To enable the system to boot from the newly inserted USB device, the boot order must be temporarily changed. This issue will be fixed in a future BIOS release.

RKVMS Issue

When the virtual CD-ROM is enabled, the virtual CD does not appear in the boot list.

Workaround:

1. Mount the virtual CD-ROM and reboot the system.

2. During system boot, type F2 to enter the system BIOS.

3. Navigate to the Boot list and access the CD-ROM device list.

4. Promote the AMI Virtual CD/DVD to be the first item in the boot list.

This will enable you to choose to boot from the virtual CD because it will now be listed in the BBS list.

This issue will be fixed in a future BIOS release.

BMC Not Responding

In rare circumstances, you may see a BMC not responding message during BIOS P.O.S.T. If the BIOS halts and reports this message, perform the following workaround procedure.

Workaround:

1. Press Ctrl-alt-Del.

2. Reboot the server.

This issue will be fixed in a future BIOS release.

Service Processor IP Address Does Not Update In the System BIOS Screen

When changing the Service Processor (SP) IP address via the system BIOS, the IP address does not update immediately on the system BIOS screen. If this occurs, perform the following workaround procedure:

Workaround:

1. During system boot, type F2 to enter the system BIOS.

2. Navigate to Advanced > IPMI 2.0 Configuration > Set LAN Configuration > IP Address.

3. Select IP Address, change the mode to Static and enter the desired IP address. Press ESC.

4. Select Subnet Mask, retype the default subnet address and press Enter. Press ESC.

5. Select IP Address and verify that the IP address has been updated.

6. Save changes and exit the system BIOS to reboot your server.

One HDD Not Detected In Compatible Mode

Type F2 to enter BIOS Setup Utility, navigate to Advanced --> IDE Configuration and change ATA/IDE Configuration to Compatible.

This is the expected behavior and a limitation for Compatible mode.

If set to Compatible mode, and also set to SATA Pri. PATA Sec, the IDE
CD-ROM will be the primary device and SATA1 will be mapped to the secondary device. SATA0 HDD can not be used.

If set to SATA Pri. PATA Sec, SATA0 will be mapped to the primary IDE HDD device and the IDE CD-ROM will be the secondary device. SATA1 HDD can not be used.

If you want all HDDs and the CD-ROM to be detected, select Enhanced mode in the BIOS Setup utility.

Identifying E0 Stepping Processors

If you have an E0 stepping processor installed in your system, the BIOS has already been updated. If you receive an E0 stepping processor as a separate option, you can identify the processor by the labeling on the box.

TABLE 1 contains a list of the product codes that identify each E0 stepping processor.


TABLE 1 E0 Processor Product Code Identifiers

Processor

E0 Product Code

E5405

2.00GHz, 1333, 80W

AT80574KJ041N

L5420

2.50GHz, 1333, 50W

AT80574JJ060N

X5460

3.16GHz, 1333, 120W

AT80574KJ087N

X5472

Quad, 3.0 1600, 120W

AT80574KL080N

E5472

Quad, 3.0, 1600, 80W

AT80574KL080NT

X5482

Quad, 3.2, 1600, 120W

AT80574KL088NT

X5272

Dual, 3.4, 1600, 120W

AT80573KL0966M

E5462

Quad, 2.8 1600, 80W

AT80574KL072N




Note - Prior to installing any supported E0 stepping processor, you must first upgrade the system to BIOS version 3A11 (or later), Tools & Drivers 1.1 (or later).


ILOM Update Will Not Automatically Update the BIOS

When updating ILOM, the BIOS is not automatically updated on the Sun Fire X2250 Server.

Workaround:

Update the BIOS separately. To remotely update the BIOS, follow the procedures in Appendix B, “Updating Sun Fire X2250 BIOS From a Remote Client” in the Sun Fire X2250 Server Service Manual (820-4593).

BIOS Sends a Hard Reset Sel Log

Change Request ID: 6840921

The system BIOS sends a hard reset sel log during system power on or during a system power cycle.

Workaround: None.

This issue will be fixed in a future BIOS release.

System Can Not Boot From a Redirected CD-ROM

Change Request ID: 6841004

The system can not boot from a redirected CD if both the CD and floppy image are redirected at the same time from the Java Remote Console.

Workaround: Do not redirect both the CD and floppy image at the same time.

This issue will be fixed in a future BIOS release.


Integrated Lights Out Manager Issues

The following issues apply to the Sun Fire X2250 server when the server is managed by the Integrated Lights Out Manager (ILOM):

For more information about ILOM, see the online Sun Integrated Lights Out Manager User’s Guide (820-1188) at http://docs.sun.com.

Minimum Supported Browsers

TABLE 2 shows the minimum supported browser versions for running the Integrated Lights Out Manager (ILOM) web interface for the Sun Fire X2250 server on Solaris, Linux, and Windows operating systems.


TABLE 2 Supported Browsers for ILOM

Solaris x86

RHEL 32-bit

RHEL 64-bit

SLES 32-bit

SLES 64-bit

Windows

Mozilla

1.7

1.7.12

1.7.13

1.7.8

1.7.13

N/A

Firefox

1.5.0.4

1.0.7

1.5.0.4

1.5.0.4

1.5.0.4

1.5.0.4

Internet Explorer

N/A

N/A

N/A

N/A

N/A

6


Session Times Out Prematurely

When the Session Timeout is set to 3 hours in the ILOM web interface, the session will always time out before 3 hours.

Workaround: None.

This issue is will be fixed in a future ILOM firmware release.

Procedure to Mount Remote CD-ROM From a Solaris System

When you launch a Java Remote Console (RKVMS) session from a Solaris system, the Mount CD ROM option will not display a CD-ROM drive, even when a CD is correctly mounted.

Workaround:

By default, volmgt is enabled at all time. Before using the Java Remote Console (RKVMS) to start CD-ROM/floppy redirection, volmgt needs to be disabled. Follow this procedure.

1. Disable volmgt. Type:

> >/etc/init.d/volmgt stop

2. Launch the Java Remote Console (RKVMS).

3. Assign root privilege to the Java processor that is running on RKVMS. Type:

> >ppriv -s +file_dac_read ‘pgrep java‘;

4. Insert a bootable CD into the CD-ROM drive on your Solaris desktop.

5. Click the cdrom menu item in the Java Remote Console to start CD-ROM redirection.

The path of the CD-ROM drive should appear.

No Events Are Generated for a Memory Mismatch

No events are generated in the service processor (SP) logs or BIOS BMC event logs for DIMMs of different sizes that are within the same branch.

Workaround: None.

This issue will be fixed in a future ILOM firmware release.

Locate LED Cannot Be Set to Different Values

The Locate LED cannot be set to different values (for example, fast blink) using the web interface. For example, this procedure has no effect on the Locate LED.

1. Log in to the ILOM web interface as Administrator.

2. Navigate to the System Monitoring > Indicators tab.

3. Select /SYS/LOCATE.

4. From the pull-down menu, select Set LED to Fast Blink.

A confirmation message appears.

5. Click OK to confirm the action.

Workaround: None.

This issue will be fixed in a future ILOM firmware release.

No Warning When Password Length Is Exceeded

When using the ILOM web interface, no errors or warnings are issued when you exceed the 16-character limit for passwords.

Workaround: None.

This issue will be fixed in a future ILOM firmware release.

Pc-Check Diagnostics Do Not Run in Manual Mode

When the Pc-Check diagnostic tool is set to run manually (that is, /SP/diag is set to manual), the diagnostics do not run. This occurs because the virtual floppy device is listed last in the BIOS boot devices listing.

Workaround:

1. Open a terminal window.

2. Type the following command to set the virtual floppy as the primary boot device:

ipmitool -H localhost -U root -P changeme chassis bootdev floppy

You can now run the Pc-Check tool in manual mode.

KVMS Authentication Does Not Work With Remote Authentication Mechanisms

User authentication for KVMS sessions cannot be performed using any of the remote user authentication mechanisms, such as RADIUS, LDAP, or Active Directory.

Workaround: None.

This issue will be fixed in a future ILOM firmware release.

Solaris Remote Console Session Requires Java Plugin

When you launch an ILOM Remote Console session on a Solaris system, the system may prompt you for a decision regarding the javaRKVM.jnlp file. You have the following two options:

single-step bullet  If you are logged in as root, choose to open the file with its default application.

-or-

single-step bullet  If you are logged in as a user (not root), do the following:

1. Choose the option to save the file.

2. Download the javaRKVM.jnlp file and run it manually.

The download manager will display the location of this file.

3. To find the location of the javaws application, enter the following in a terminal window:

% which javaws

4. Move the javaRKVM.jnlp file to the /tmp directory. Type:

% mv /location_of_javaRKVM.JNLP/javaRKVM.JNLP /tmp

Where location_of_javaRKVM.JNLP is the directory where javaRKVM.JNLP resides.

5. Execute the following command from the terminal window:

% /location_of_javaws/javaws /tmp/javaRKVM.JNLP

Where location_of_javaws is the directory where javaws resides.

Example:

Assuming the javaws application is run from the /usr/bin directory:

% /usr/bin/javaws /tmp/javaRKVM.JNLP

will open a Remote Console session.

Once the Remote Console window is closed, the /tmp/javaRKVM.jnlp is removed.


Diagnostics Issues

This section contains diagnostics issues for the Sun Fire X2250 Server.

Pc-Check Issues

The following issue applies to the Pc-Check diagnostics software, version 6.20:

Procedure to Run Pc-Check Embedded in the ILOM Firmware

Follow this procedure:

1. Log in to the ILOM web interface.

2. Select Remote Control > Diagnostics tabs, and then set the mode for Pc-Check.

3. Power cycle or power on the server to activate Pc-Check.

When the Pc-Check mode is set back to disabled, the next power-on or power-cycle event will then take that event. For example, if you used ILOM to set the
Pc-Check status to enabled and that mode is currently running, and if you then set the status to disabled, ILOM will not exit Pc-Check or kill the background scripts until the next power-on or power-cycle event. ILOM does not see any localized resets, such as a control-alt-delete, and therefore it cannot verify that the resets occurred.

Sun VTS Issues

The following issue applies to Sun VTS software:

Sun VTS Fails in Internal Loopback Mode

Change Request ID: 6723514

The Sun VTS netlbtest fails in internal loopback mode. This occurs because the e1000g network interface card (NIC) driver is not supported by the Intel 82564EBT and Intel 82563EB chipsets being used by the Sun Fire X2250 server.


Operating System Issues

This section contains the following operating system issues:

For a list of minimum supported operating systems, see Supported Operating Systems.

Solaris Issue



Note - The Sun Fire X2250 server is delivered with a preinstalled Solaris OS. This OS is set by default to be redirected through the serial console connection (ttya). To redirect the OS to a local monitor and keyboard, use the GRUB menu at boot time, and select the VGA option.


Some KVM Switches Out of Sync Following Solaris Installation

When installing Solaris 10 5/08 on a Sun Fire X2250 server that is mounted in a rack and connected to a KVM switch, the monitor might go out of sync when the Xserver starts to log in to the OS.

There are three Workarounds:

a. Run the install.sh script from the Tools & Drivers CD.

b. Reboot the server.

Running install.sh resolves the issue, as it installs the updated AST2000 VGA driver. See the Sun Fire X2250 Server Operating System Installation Guide (820-4592) for additional instructions on running the install.sh script for Solaris.

See the Sun Integrated Lights Out Manager User’s Guide (820-1188) for additional instructions about KVMS over IP.

a. Boot failsafe or kill the Xserver prior to starting.

b. Run the install.sh script from the Tools & Drivers CD.

See the Sun Fire X2250 Server Operating System Installation Guide (820-4592) for additional instructions on running the install.sh script for Solaris.

Linux Issues

The following issues apply to Sun Fire X2250 servers running the supported RedHat or SUSE operating systems.

USB Device Errors Reported in Red Hat 5.1

The following error message is generated when a USB device is inserted in the rear USB port on the Sun Fire X2250 server:

usb 1-2; device not accepting address 2, error -71

This is a Red Hat Linux issue.

Workaround:

You must manually create a new initrd.img file in your current installation:

1. Open a terminal window.

2. Navigate to the /boot directory. Type:

cd /boot

3. Rename the initrd.img file by typing the command:

mv initrd-<version>.img initrd-<version>.img.save

4. Create a new initrd.img file by typing the command:

mkinitrd initrd-<version>.img <uname - r>

5. Reboot the server for the changes to take effect.

Intel RAID Drivers for Sun Installation Assistant or Manual OS Installation Are Not Functioning

When using the Sun Installation Assistant (SIA) or Red Hat/SUSE DVD to install Linux on the Sun Fire X2250 server, ensure that the HDD configuration mode is set to IDE. RAID drivers for the Intel ESB2 chipset are not functioning correctly. This issue is being addressed with the Linux OS providers and Intel.


Sun Installation Assistant Issues

The following section details issues when installing Windows and Linux operating systems using the Sun Installation Assistant (SIA), including:

NFS, HTTP, and FTP Installation Modes are Not Available for Windows

Change Request ID: 6723239

NFS, HTTP, and FTP installation modes are not available when installing Windows using SIA. Windows installation support is available only for CD installations (remote RKVM and local).

SIA is Unable to Configure the Video Card and Monitor Type

Change Request ID: 6715608

SIA is unable to configure the video card and monitor type for Linux OS (Red Hat and SLES) installations. The user may have to manually set the type (make and model) of the monitor and set the correct monitor resolution after the installation completes.

SIA Does Not Support RAID Installations

Change Request ID: 6718362

Redundant array of independent disks (RAID) installations are not supported in SIA.

This issue will be fixed in a future SIA release.

RHEL Must be Installed on a Single Disk

Change Request ID: 6719224

Red Hat Enterprise Linux (RHEL) version 5.1 must be installed on a single disk. Placing the boot and swap partitions on one disk and placing the root partition on the another disk will cause the Red Hat installer (Anaconda) to crash, which then causes SIA to hang.

SIA Does Not Recognize SATA RAID Drives

Change Request ID: 6846718

When using SIA to install Windows Server 2003, SIA does not recognize the SATA RAID drive created by the ESB2 chipset.

Workaround:

None.

System Does not Reboot After Installing the OS

Change Request ID: 6847509

When using SIA to install an OS in SATA AHCI mode, occasionally the system will not reboot when you click the Reboot button at the end of the installation process.

Workaround:

Manually reset the system to reboot the system.


Issues Fixed With Previous Tools and Drivers CD Updates

The following table details issues that have been acknowledged, addressed, or fixed with each version of the Tools and Drivers CD:


BIOS Version

CR #

Description

From 1.2 to 1.3

6725671

  • Unable to change the service processor IP address using BIOS

6701632

  • BIOS gets stuck with DMA-1 Error when IDE configuration is set to “Compatible”

From 1.1.1 to 1.2

6779317

  • Lower than expected Infiniband card performance; four performance options added to BIOS Setup Utility
  • Read Completion Coalescing enable/disable
  • Force Read Coalescing enable/disable
  • PCI-e Max Payload size selection 128/256
  • Snoop filter bypass enable/disable

 

6752788

  • BIOS GUID value did not match ILOM UUID

 

6786281

  • BIOS continuously tries to boot instead of waiting for “F1 to continue” when no bootable device is found

 

6786286

  • During POST, BIOS date did not match the build date

 

6786289

  • POST errors automatically resume after 5 seconds

 

6786291

  • Display product serial number during POST

 

6786293

  • Support IPMI interface in Windows 2008

 

6789295

  • Correct ECC Eventlog format

 

6786296

  • System always powers up after AC power loss after shutdown from non-ACPI operating system

 

6780767

  • GUID is swapping with HOST NIC0 MAC address when it should be the SP MAC address

 

6687589

  • Uboot data integrity memory test failed

 

6698177

  • ILOM does not allow hyphen “-” character in SNMP community string

 

6756584

  • Graceful shutdown causes an immediate power off

 

6752788

  • FRUID GUID does not match what BIOS reads as GUID, affecting PXE boot

 

6715073

  • No mouse (absolute) via RKVMS using W2K3/W2K8 EE Server X64

 

6733930

  • Mouse redirection not working when using RHEL4.7 and Windows XP clients

 

6696738

  • Relative mouse mode on SP KVMS does not work will with Linux X11 mouse driver

From 1.1 to 1.1.1

6696717

  • Garbage SP log entries for “Set System Boot Options” created when /SYS is started on SP

 

6708525

  • USB/AMI redirection: USB trap with virtual FDD/CDROM (Pc-Check?)

 

6671576

  • RKVMS Caps Lock, Num Lock and Scroll Lock indicators not functioning

From 1.0a to 1.1

6786504

  • Support Harpertown/Wolfdale-DP E-0 CPU

 

6786484

  • ILOM initiated NMI is not recognized by BIOS

 

6786488

  • BIOS will not stop on a CMOS checksum error and display “press F1 to continue or F2 to enter SETUP” - just load optimized default

 

6786479

  • Unreported memory I/O test on Windows 2003

 

6786482

  • Support DIMM sparing function

 


Copyright

Sun Microsystems, Inc. détient les droits de propriété intellectuels relatifs à la technologie incorporée dans le produit qui est décrit dans ce document. En particulier, et ce sans limitation, ces droits de propriété intellectuelle peuvent inclure un ou plus des brevets américains listés à l'adresse http://www.sun.com/patents et un ou les brevets supplémentaires ou les applications de brevet en attente aux Etats - Unis et dans les autres pays.

Cette distribution peut comprendre des composants développés par des tierces parties.

Des parties de ce produit pourront être dérivées des systèmes Berkeley BSD licenciés par l'Université de Californie. UNIX est une marque déposée aux Etats-Unis et dans d'autres pays et licenciée exclusivement par X/Open Company, Ltd.

Sun, Sun Microsystems, le logo Sun, Java, Solaris, Sun Fire, Sun Solve, Sun Service, et SunVTS sont des marques de fabrique ou des marques déposées de Sun Microsystems, Inc., ou ses filiales, aux Etats-Unis et dans d'autres pays.

Microsoft sont est marques de fabrique ou des marques déposées de Microsoft Corporation ou de sa filiale aux Etats-Unis et dans d’autres pays. Windows est une marque de fabrique ou une marques déposée de Microsoft Corporation ou de sa filiale aux Etats-Unis et dans d’autres pays. Intel est une marque déposée ou marque déposée d'Intel Corporation ou ses filiales aux Etats-Unis et à d'autres pays. Le logo Adobe est une marque déposée de Adobe Systems, Incorporated.

L'utilisation de pieces detachees ou d'unites centrales de remplacement est limitee aux reparations ou a l'echange standard d'unites centrales pour les produits exportes, conformement a la legislation americaine en matiere d'exportation. Sauf autorisation par les autorites des Etats-Unis, l'utilisation d'unites centrales pour proceder a des mises a jour de produits est rigoureusement interdite.

LA DOCUMENTATION EST FOURNIE “EN L'ETAT” ET TOUTES AUTRES CONDITIONS, DECLARATIONS ET GARANTIES EXPRESSES OU TACITES SONT FORMELLEMENT EXCLUES, DANS LA MESURE AUTORISEE PAR LA LOI APPLICABLE, Y COMPRIS NOTAMMENT TOUTE GARANTIE IMPLICITE RELATIVE A LA QUALITE MARCHANDE, A L'APTITUDE A UNE UTILISATION PARTICULIERE OU A L'ABSENCE DE CONTREFACON.