X4150 server.
|
Sun Fire X4150 Server Product Notes |
This document contains late-breaking information and issues for the Sun Fire X4150 server.
| Note - The information in the English version of the Product Notes might be more up-to-date than the translated versions. |
The following issues are covered in these product notes:
This section contains the following software information:
The following operating systems versions are supported on the Sun Fire X4150 server:
OS 10 5/08, Solaris OS 10 10/08, Solaris OS 10 5/09, Solaris 10 10/09
| Note - Additional information for servers with preinstalled Windows 2003 Server can be found in Windows Issues. |
The following software can be ordered to ship with your system or downloaded:
The software supplemental releases include BIOS and ILOM updates only. The Tools and Drivers CD is not updated for these releases. You can download the supplemental software updates at:
http://www.sun.com/servers/x64/x4150/downloads.jsp
Sun Fire X4150 Software Supplemental 3.0.2 firmware package is now available for download.
The firmware versions include:
The following issue was introduced in 3.0.3.30 build r48374: Correctable Errors Incorrectly Listed in the ILOM SEL as a Critical Error.
| Note - Refer to Issues Fixed in Software Supplemental 3.0.2 for information on issues that have been fixed with this release. |
Sun Fire X4150 and X4250 Software Supplemental 3.0.1 firmware package is now available for download.
The firmware versions include:
| Note - Refer to Issues Fixed in Software Supplemental 3.0.1 for information on issues that have been fixed with this release. |
Sun Fire X4150 and X4250 Software Supplemental 2.2.2 firmware package is now available for download.
The firmware versions include:
| Note - Refer to Issues Fixed in Software Supplemental 2.2.2 for information on issues that have been fixed with this release. |
The Tools and Drivers CD/DVD includes firmware and software for the Sun Fire X4150 server. The Tools and Drivers CD or DVD is offered as an option to order with your system. Latest versions of the Tools and Drivers CD/DVD images are available at the following download site:
http://www.sun.com/servers/x64/x4150/downloads.jsp
| Note - See Important: CPLD Update Might Be Required Before Firmware Update before updating your system firmware. |
The most recent software update is Tools and Drivers DVD Version 3.2.0.
The updates for Tools and Drivers 3.2.0 include:
Additional software updates include:
The most recent software update is Tools and Drivers DVD Version 3.1.1.
The updates for Tools and Drivers 3.1.1 include:
Additional software updates include:
| Note - Refer to Issues Fixed in Tools and Drivers DVD 3.1.1 for information on issues that have been fixed with this release. |
For further information on the ILOM 3.x, refer to the ILOM 3.0 documentation included in the Sun Fire X4150 server documentation set.
The most recent software update is Tools and Drivers DVD Version 3.1.0.
The updates for Tools and Drivers 3.1.0 include:
Additional software updates include:
| Note - Refer to Issues Fixed in Tools and Drivers DVD 3.1.0 for information on issues that have been fixed with this release. |
For further information on the ILOM 3.x, refer to the ILOM 3.0 documentation included in the Sun Fire X4150 server documentation set.
The following sections contain information on previous Tools and Drivers CD/DVD updates.
The updates for Tools and Drivers 3.0.0 include:
Diagnostics CD Bootable CD Update: SunVTS 7.0 ps4 is also included in this software update.
| Note - Refer to Issues Fixed in Tools and Drivers DVD 3.0.0 for information on issues that have been fixed with this release. |
Tools and Drivers DVD 2.2.1 is the latest ILOM and BIOS update for the Sun Fire X4150 server. The firmware versions include:
| Note - Refer to Issues Fixed in Tools and Drivers DVD Version 2.2.1 for information on issues that have been fixed with this release. |
The firmware versions for this DVD include:
| Note - Refer to Issues Fixed in Tools and Drivers DVD Version 2.2.0 for information on issues that have been fixed with this release. |
The firmware versions for Tools and Drivers CD 2.1.0 include:
Prior to installing any supported E0 stepping CPU on an ILOM system, you must first upgrade the system to 1ADQW054 BIOS. Refer to Identifying E0 Stepping Processors.
| Note - Refer to Issues Fixed in Tools and Drivers DVD Version 2.1.0 for information on issues that have been fixed with this release. |
Tools and Drivers CD 2.0 contains firmware for both Embedded Lights Out Manager (ELOM) and Integrated Lights Out Manager (ILOM) and supports ELOM to ILOM migration.
| Note - If you are using the Qimonda Memory 2GB/DDR2 HYS72T256421EFA-3S-C2 then you must update to ILOM BIOS 1ADQW052 or ELOM BIOS 1ADQW027. |
The firmware versions for ILOM and ELOM are listed in TABLE 1:
Please note the following regarding the ELOM firmware:
Refer to the ELOM-to-ILOM Migration User’s Guide for information on migrating from ELOM to ILOM.
Tools and Drivers DVD 1.3.3 is the latest ELOM update for the Sun Fire X4150 server.
| Note - This Tools and Drivers DVD is an update for ELOM only. If you are running ILOM, use the ILOM version on the Tools and Drivers DVD v 2.1.0. |
The firmware versions include:
Prior to installing any supported E0 stepping CPU on an ELOM system, you must first upgrade the system to 1ADQW027 BIOS. Refer to Identifying E0 Stepping Processors.
| Note - Refer to Issues Fixed in Tools and Drivers CD Version 1.3.3 for information on issues that have been fixed with this release. |
Tools and Drivers CD 1.3.2 contains the following updates:
| Note - To see issues that have been fixed with Tools and Drivers CD version 1.3.2, please see Issues Fixed in Tools and Drivers CD Version 1.3.2. |
Tools and Drivers CD 1.3.1 contains the following updates:
| Note - To see issues that have been fixed with Tools and Drivers CD version 1.3.1, please see Issues Fixed in Tools and Drivers CD Version 1.3.1. |
Tools and Drivers CD 1.2 contains the following updates:
The following feature enhancements have been added to the Sun Fire X4150 Tools and Drivers v1.1 CD:
| Note - Make sure to read Important: CPLD Update Might Be Required Before Firmware Update before using the Tools and Drivers CD v1.1. |
Sun Validation Test Suite (SunVTS) provides a comprehensive diagnostic tool that tests and validates Sun hardware by verifying the connectivity and functionality of most hardware controllers and devices on Sun platforms. SunVTS software can be tailored with modifiable test instances and processor-affinity features.
SunVTS is an orderable software option and can also be downloaded from:
http://www.sun.com/oem/products/vts/
For the most up-to-date information on SunVTS software, go to:
http://docs.sun.com/app/docs/prod/test.validate
Make sure to read the most recent product Release Notes before running SunVTS on your server.
The Sun Installation Assistant (SIA) is a tool supported for use with x64 Sun Fire and Sun Blade servers that assists in the installation of supported Linux and Microsoft Windows operating systems (OS) and firmware updates. With SIA, you can install the OS, the appropriate drivers, and if necessary, additional system software by simply booting the SIA media and following the prompts.
SIA is an orderable software option and can also be downloaded from the Sun Download page at:
http://www.sun.com/download/index.jsp
Updates to the SIA program can be obtained easily during the SIA installation by using the Remote Update option in the SIA.
For more information on the Sun Installation Assistant, see the Sun Installation Assistant for Windows and Linux User’s Guide For Sun Fire and Sun Blade Series Servers.
Starting with the release of the Sun Fire X4150 Tools and Drivers v1.1 CD, support is included for Intel Xeon 5200 and 5400 series processors This support requires a CPLD, BIOS and SP firmware update. To perform this update, first update the CPLD, then update the BIOS and SP firmware.
Updating the CPLD is needed if you are running ELOM only. If you are running ILOM, you only need to install Solaris patches.
|
Caution - The CPLD mustbe updated before the firmware. You must perform these procedures exactly as described to ensure correct operation of your server. |
The upgrade must be performed exactly in this order.
1. Update the system CPLD, BIOS and SP firmware. (ELOM only)
See Updating the CPLD.
2. Install the Solaris patches (ELOM and ILOM).
See Installing Solaris Patches.
4. Replace the shipped processors with the new Intel Xeon 5300 or 5400 series processors.
Refer to the Sun Fire X4150 Server Service Manual for information on removing and installing the processors.
1. Start the Embedded LOM (ELOM) SP web GUI by typing the IP address of the SP into a browser.
See the Embedded Lights Out Manager Administration Guide for instructions on using the ELOM web GUI.
2. Copy the file /remoteflash/elom/CPLD/s92v063.jbc to the local drive from the Tools and Drivers version 1.1 CD.
4. Click on the Maintenance Tab and choose Firmware Update.
Shut the server down if you are prompted.
The Firmware Update screen is displayed.
5. From the CPLD Update option, click Browse and navigate to the location of the flash file.
7. After the firmware is uploaded, you are asked to remove AC power for 10 seconds to allow the CPLD to be loaded.
Power the server off and then restart the server.
8. After the CPLD update is finished, the BIOS/SP can be updated from the bootable Tools and Drivers version 1.1 CD or through the documented TFTP interface and Web Interface.
See the Embedded Lights Out Manager Administration Guide.
1. Download the needed patches.
There are two ways to download the needed patches. The first method is preferred because it provides the latest version of the patches.
a. Mount the Tools and Drivers CD in your Solaris system.
b. Locate the patches that provide support for the Intel Xeon 5200 and 5400 series processors. Access the following directory in the Sun Fire X4150 Tools and Drivers v1.1 CD:
/<DVD_DRIVE>/drivers/sx86/patches
c. Create a new directory, as required.
d. Copy both patches to the Solaris system.
e. Reboot the system and enter Single User Mode.
Refer to Solaris OS documentation on www.docs.sun.com
f. Copy both patch directories, 125370-06 and 127112-05, to your Solaris system.
2. Run the following commands to add the patches in this order, as there are dependencies.
Where xx is the latest version of each patch. If you are using the patches from the Tools and Drivers CD, the patch versions are 125370-06 and 127112-05.
Allow the system to fully boot to the OS, as this installs the Kernel Patches.
4. After the system OS load is finished, shut down the server and then install the new processors.
The serial console settings for Solaris preinstalled distributions has changed for the release of the Tools and Drivers 1.3.1 CD and beyond.
Make the following changes in the BIOS, as needed, if using Tools and Drivers CD 1.3.1 and beyond.
To configure preinstalled Solaris using ttya: Set the External Serial Port to SP and the External Serial Port Config to COM1 (default setting).
To configure preinstalled Solaris using ttyb: Set the External Serial Port to SYSTEM and the External Serial Port to Config to COM2.
The following issues apply to the Sun Fire X4150 server hardware and BIOS:
Hard Drives in the right-side drive bays can be difficult to remove.
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.
2. Push in on the drive, while holding it pressed to the right. See Step 2 in the following figure.
3. Press the drive eject button and pull on the eject lever. See Step 3 in the following figure.
4. Use the eject lever to slide the drive out of the bay.
FIGURE 1 Removing Hard Drives From Right-Side Bays
32GB solid state drives (SSDs) are now available for the Sun Fire X4150 server. Read the following guidelines before installing SSDs on the server.
There are two configurations for SSDs on the Sun Fire X4150 server that are currently supported:
Use the following guidelines for installing SSDs when you don’t plan to install additional SAS drives:
This kit needs to be ordered separately when the SSDs are ordered.
Use the following guidelines for installing SSDs when you do plan to install additional SAS drives:
These items need to be ordered separately when the SSDs are ordered.
If you are running Intel I/O AT test tool, you need to enable the feature in the BIOS menu first.
In the BIOS Setup menu, select Advanced -> PCI Configuration -> Crystal Beach/DMA to enable the feature.
When you change the serial port sharing owner in the ILOM WebGUI or CLI from the SP to the host, the connect serial port connects, but you see no output.
This issue will be fixed in a future BIOS release.
Change the serial port sharing from SP to System using the BIOS menu directly, as follows:
1. In the BIOS setup menu, select Server -> External Serial Port
2. Change the External Serial Port selection from “SP” to “System”.
If you are using the Qimonda Memory 2GB/DDR2 HYS72T256421EFA-3S-C2, your server must be running the one of following BIOS versions:
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. Refer to TABLE 2 for a listing of the product codes that identify each E0 stepping processor.
| Note - Prior to installing any supported E0 stepping CPU, you must first upgrade the system to 1ADQW054 BIOS (for ILOM systems) or 1ADQW027 BIOS (for ELOM systems). See Tools and Drivers CD/DVD for more information. |
The BIOS serial port default settings have changed in the Tools and Drivers CD 1.3.1 firmware update. If you are using the serial console, you might need to change your default settings.
Prior to the 1.3.1 release, the default settings were COM2/TTYB/115200 and this version of the firmware changes these to the more accepted defaults of COM1/TTYA/9600. If you have reconfigured an existing installation to match the previous defaults of COM2/TTYB/115200, you will need to change your settings.
| Note - For new installations of Solaris 10 8/07 or Solaris 10 5/08 with this firmware update already applied, you do not need to make these changes. |
If the serial console was configured and running to display output of the OS on any release prior to 1.3.1, the OS output will no longer be displayed unless the changes are made prior to updating the firmware. The following sections contain instructions for changing the serial console settings for the firmware version that you are using:
Minimum versions for this procedure are RHEL 3.7 and RHEL 4.3.
Use the procedure that corresponds to the firmware version that you are using:
1. Use a text editor to edit the /etc/grub.conf file.
2. Append the following to the kernel boot parameter line:
console=tty1 console=ttyS1, 115200
For example, the new kernel boot parameter line should look similar to this:
kernel /vmlinux-2.x.x ro root=LABEL/1 rhgb quiet console=tty1
a. Add the ttyS1 to the bottom of the file.
a. Change id:5:initdefault: to id:3:initdefault:
b. Under the section “Run gettys in standard runlevels” add the following as the first line:
co:2345:respawn:/sbin/agetty ttyS1 115200 vt100B
1. Use a text editor to edit the /etc/grub.conf file.
2. Append the following to the kernel boot parameter line:
console=tty0 console=ttyS0, 9600
For example, the new kernel boot parameter line should look similar to this:
kernel /vmlinux-2.x.x ro root=LABEL/1 rhgb quiet console=tty1
a. Add the ttyS0 to the bottom of the file.
a. Change id:5:initdefault: to id:3:initdefault:
b. Under the section “Run gettys in standard runlevels” add the following as the first line:
co:2345:respawn:/sbin/agetty ttyS0 9600 vt100B
Minimum versions for this procedure is SLES 10 SP1 64-bit.
Use the procedure that corresponds to the firmware version that you are using:
1. Use a text editor to edit the /boot/grub/menu.lst file.
2. Append the following to the kernel boot parameter line:
For example, the new kernel boot parameter line should look similar to this:
kernel /boot/vmlinux root=/dev/sda2 resume=/dev/sdal
splash:silent showps console=tty0 console:ttyS1, 115200
3. Edit the /etc/securetty file.
a. Add ttyS1 to the bottom of the file.
4. Edit the /etc/inittab file.
a. Change id:5:initdefault: to id:3:initdefault:
b. Under “getty-programs for normal runlevels” add the following line:
S0:12345:respawn:/sbin/agetty -L 115200 ttyS1 vt100
1. Use a text editor to edit the /boot/grub/menu.lst file.
2. Append the following to the kernel boot parameter line:
For example, the new kernel boot parameter line should look similar to this:
kernel /boot/vmlinux root=/dev/sda2 resume=/dev/sdal
splash:silent showps console=tty0 console:ttyS0, 9600
3. Edit the /etc/securetty file.
a. Add ttyS0 to the bottom of the file.
4. Edit the /etc/inittab file.
a. Change id:5:initdefault: to id:3:initdefault:
b. Under “getty-programs for normal runlevels” add the following line:
S0:12345:respawn:/sbin/agetty -L 9600 ttyS0 vt100
Use the procedure that corresponds to the firmware version that you are using:
1. Edit the /boot/solaris/bootenv.rc file to read:
setprop ttyb-mode 115200,8,n,1,-
2. Edit the /boot/grub/menu.lst file to read:
kernel /platform/i86pc/multiboot -B console=ttyb
3. Edit the /kernel/drv/asy.conf file and add the following:
name=”asy” parent=”isa” reg=1,0x2f8,8 interrupts=3;
4. Edit the /var/svc/manifest/system/console-login.xml file to read:
<propval name=’label’ type=’astring’ value=’115200’/>
6. Reboot the system using the following command:
1. Edit the /boot/solaris/bootenv.rc file to read:
setprop ttya-mode 9600,8,n,1,-
2. Edit the /boot/grub/menu.lst file to read:
kernel /platform/i86pc/multiboot -B console=ttya
3. Edit the /kernel/drv/asy.conf file and add the following:
name=”asy” parent=”isa” reg=1,0x2f8,8 interrupts=3;
4. Edit the /var/svc/manifest/system/console-login.xml file to read:
<propval name=’label’ type=’astring’ value=’9600’/>
6. Reboot the system using the following command:
When using a remote keyboard (a keyboard other than one that is locally connected to the system) with the Sun Blade X4150 server, pressing the F12 key opens the BIOS Setup Menu.
| Note - Use Ctrl+N on a remote keyboard to enter a PXE menu instead of pressing F12. If you accidentally press F12, you will enter the BIOS Setup Menu. |
This issue will be fixed with the ILOM update of Sun Fire X4150 server.
Make sure that the LSI 3081E SAS HBA firmware is up to date.
Use the latest LSI 3081E firmware found on the Tools and Drivers CD version 1.3.2 or later, which can be downloaded from:
http://www.sun.com/servers/x64/x4150/downloads.jsp
However, DIMM capacities can be different between different DIMM pairs. For example, a valid mixed DIMM configuration may have 1GB DIMMs installed in DIMM Slots A0/B0, and 2GB DIMMs installed in DIMM slots C0/D0.
DIMMS should be installed with the largest module pair size first. For example, (4) 4GB DIMMs and (4) 2GB DIMMS should be installed as follows: A0/B0=4G, C0/D0=4G, A1/B1=2G, C1/D1=2G
The SP/BIOS flash process includes an “Update Successful” message when the service processor (SP) flash finishes. This message signals the end of the SP flash activity only. At this point in the process, the BIOS has not been flashed and premature termination of the process (for example, a manual reboot) will result in BIOS corruption. To avoid corrupting the BIOS review the flash sequence below:
| Note - Before writing a script to flash the BIOS/SP remotely, observe the sequence in real-time and test the script on a single system before updating all systems. |
1. SP begins the flash process.
2. SP completes the flash process.
3. CLI returns an Update Successful message.
4. The system reboots and the BIOS begins the flash process.
5. The BIOS flash process finishes.
The front panel USB ports support only a 3-meter cable to an attached device.
The DVD/USB container assembly can be inadvertently disconnected from the disk backplane when a direct-connect USB device or USB cable is pulled from a front panel USB port.
Apply counter-pressure to the DVD assembly when removing a USB device. In addition, do not remove a USB device when the DVD is operating. This issue will be addressed in the future with a redesigned DVD assembly.
When inserting a hard disk drive, do not extend the lever past 70 degrees. If the lever is extended past 70 degrees on insertion there is a risk that the right most tab will break off. The end result of accidentally breaking off the tab is purely cosmetic-- the drive will still function properly if fully inserted.
With Tools and Drivers CD 2.0, you now have the option to install either ELOM or ILOM system management software on your system.
Refer to the following documentation for additional information on system management for the Sun Fire X4150 server:
The issues in this section fall into one of three categories:
The following issues are specific to ILOM 3.0. Additional ILOM 3.0 information is available in Sun Integrated Lights Out Manager (ILOM) Feature Updates and Release Notes. This document is available at:
http://docs.sun.com/app/docs/coll/ilom3.0
When the CPU temperature reaches its upper critical limit, the system shuts down, though there is no event logged in the system event log (SEL) and the Tempfail LED does not light.
While the SP is being updated (flashed), do not start a new flash process. Wait until the current flash is completed before you start a new one.
When ILOM is downgraded from ILOM 3.0 to ILOM 2.0 or upgraded from ILOM 2.0 to 3.0, the BIOS version might not appear in the Firmware Upgrade section of the web interface. TABLE 3 indicates when you can expect to see the BIOS version viewable in the Firmware Upgrade section of the ILOM web interface.
If you can not get the BIOS version from web interface while it is updating, you can view the BIOS version connected with the ILOM version from these product notes. See Tools and Drivers CD/DVD.
If the BIOS is currently running and not in update mode, you can obtain the BIOS version from BIOS Setup utility or ILOM CLI.
The issues in this section apply whether you are running ILOM or ELOM. The following issues are included in this section:
This issue applies to the ELOM to ILOM migration process.
If you migrate to the transitional ELOM from the firmware provided in Tools and Drivers CD release 1.0 (BIOS 1ADQW011 and SP 0.88), the SP will not retain IP information after migrating to the transitional ELOM.
After updating transitional ELOM, log in to the CLI via serial console and fix the IP address in /SP/network.
You can then can continue with the migration to ILOM process.
Refer to the ELOM-to-ILOM Migration User’s Guide for more information on the migration process.
The Gateway address in the SP might not be persistent across SP reboots (power cycles). Make sure that the Gateway address is persistent by power cycling the SP (remove AC power, then power up the system) and checking if the Gateway address is retained. If it is not, then you must set the Gateway address via the CLI.
If the Gateway address is not persistent, then upon the reboot to the transitional ELOM during an ILOM update, the SP might not be reachable.
If you change the IP address or netmask of the service processor (SP), the routing table changes after you update the SP network configuration. Therefore, you need to re-enter the gateway information or reset the SP.
For some USB flash devices, the virtual device appears to be mounted in the ELOM, but is not actually be mounted.
This issue is under investigation.
ipmitool 1.8.9.4 can be obtained from utilities/ipmitool directory from Tools and Drivers CD.
When booting the system with the console output directed to the serial port, the Sun splash screen will not appear and you will not see the prompt to press F2 to enter the BIOS Setup utility. Use the following procedure to disable the Sun splash screen:
1. Press the F2 key to enter the BIOS Setup Utility.
2. Select Boot -> Boot Setting Configuration.
3. Set the boot setting to quiet boot - disable.
This will enable a prompt to press F2.
When updating the SP from the server management web GUI or CLI, be sure to use the SaveFlag (CLI) or Save Configuration (web GUI) commands to save the updated information. If not, the factory default settings will be used instead. For example, if static IP addressing is configured for the SP and a future update to the SP configurations was not saved, the SP may revert to the default of DHCP addressing.
When running the web GUI from a Sparc-based system, Solaris 10 OS is the minimum version that is supported.
When you launch a Remote Console session on a Solaris system, the system prompts you for a decision regarding the javaRKVM.jnlp file. You have the following two options:
If you are logged in as root, choose the option to open this file with its default application.
If you are logged in as a user other than root, do the following:
1. Choose the option to save the file.
2. The javaRKVM.jnlp file will be downloaded and must be run manually.
The download manager will display the location of this file.
3. Move the javaRKVM.jnlp file to the /tmp directory.
% mv /location_of_javaRKVM.JNLP/javaRKVM.JNLP /tmp
Where location_of_javaRKVM.JNLP is the directory where javaRKVM.JNLP resides.
4. To find the location of the javaws application, type the following in a terminal window:
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.
For example, assume the javaws application is run from the /usr/bin directory:
% /usr/bin/javaws /tmp/javaRKVM.JNLP
This will open a Remote Console session. Once the remote console window is closed, the /tmp/javaRKVM.jnlp is removed.
If you have a pop-up blocker enabled in the browser that is running the Remote Console through the ELOM web GUI, the Remote Console is blocked from launching on Firefox. If you do not see the Remote Console, check to see if the built in pop-up blocker has blocked it.
If you are running Solaris on your Remote Console system, you must log into the operating system as root (superuser) to mount any virtual devices.
There is no Java support for Red Hat Enterprise Linux 5.
Virtual media will be considered as a USB device, and will be listed as CD-ROM device. This setting will over-rule the CD-ROM currently set.
In order to enable virtual CD-ROM during bootup:
1. Press F2 to enter into BIOS menu.
2. Select Boot -> CD/DVD Drives.
3. Select Virtual CDROM as the first drive.
When installing an operating system remotely using an RKVMS session, each CD request from an installation requires the user to unmount and mount the virtual CD- ROM. When a virtual CD is ejected, the OS treats it as a USB device removal, and the CD must be mounted again to continue the installation.
The remounting of the CD during an operating system installation causes an error and the OS cannot access the CD. This will be fixed in a future release.
The following table shows the minimum versions that are supported for running the ELOM web GUI for the Sun Fire X4150 server on Solaris OS, Linux and Windows operating systems.
Java Runtime Environment (JRE) 5 Update 7 is the minimum supported version for the browsers to run the ELOM web GUI. Follow the steps below to download the JRE 5 Update 7 for Mozilla and Firefox browsers.
2. Click on the Get Java Software button.
3. Click Download Now in the new window that opens.
The web site displays the appropriate plug-in options for the operating system that you are running.
4. Click Download to download the appropriate plug-in.
Installation instructions and plug-in verification are also available on this site.
The keyboard, video, mouse and storage (KVMS) over IP feature of the ELOM SP is designed for administering your system. Applications requiring heavy video bandwidth (for example, watching videos) will not perform well with KVMS over IP.
Before attempting a floppy device/floppy image redirection in the Remote Console, you must first redirect the CDROM device or CDROM image and leave it redirected while the floppy is redirected.
The issues in this section apply to ELOM. The following issues are included in this section:
Passwords for the ELOM must be alphanumeric only. A fix is planned for a later release of the firmware.
When SP is reset, the system clock is set back to 1970/1/1 00:00. The SP clock will not reset unless the OS is booted.
1. Log in to the ELOM web GUI.
2. Click the Configuration main tab.
3. Click the Clock Setting submenu tab.
4. Select the NTP server radio button for clock synchronization.
5. Enter the NTP server IP address in the IP address field.
Direct Reading of the SPD memory is not supported in IPMItool 1.8.8. Using the IPMItool fru print command will result in a return of incorrect memory information. An updated IPMItool utility is required for this to work properly. Software support has been added for the server.
If the SP firmware becomes corrupt, IPMItool commands might not complete or fail to establish a LAN session connection.
Workaround: Using the SP update utility on the Tools and Drivers CD, reflash the SP firmware using the following command.
Where xxx is the current version of the SP firmware.
| Note - This will set the SP back to factory defaults and will remove all current settings, including users and permissions and rules. Use this procedure with caution. |
It is best to disable the web GUI time-out function when performing remote installations.
When running the Remote Console on the Solaris 10 operating system, the mouse performance might be slow. To fix this issue:
1. Log in to the ELOM web GUI and start the Remote Console.
2. Using the Remote Console window, run the following in a Solaris terminal window on the Sun Fire X4150 system:
The mouse performance issue should be resolved.
Running an RKVMS session from a Sun Fire X4150 system running Solaris will not allow the user to mount a Virtual Device. This must be done from a remote Solaris system. This is being investigated.
A Solaris OS break command entered through the ELOM serial console will not work correctly.
Either connect a monitor to the VGA port or initiate an web GUI remote console session and enter the break command through one of those two methods.
The issues in this section apply to ILOM. The following issues are included in this section:
Correctable errors detected by the background scrubber in ILOM: 3.0.3.30 build r48374 are incorrectly listed in the ILOM system event log (SEL) as a critical error with the following description:
These messages are caused by Correctable ECC Error, which should have a severity of minor, not critical. This SEL message will be fixed in a future release.
Physical presence is required when you try to log in with default account from the serial console. You will need to press the Locate button twice for the system to recognize your physical presence.
ILOM stores the time in a file every 15 minutes. After the system reboots, the time is restored to whatever time was last written to that file plus a small delta. So in most cases, major events have timestamps that are monotonically increasing.
During the boot process, the date might temporarily be displayed as January 1, 1970. This will automatically change to the current time once the boot process reaches the timestamp file check.
It is best to select the web interface time-out duration when performing remote installations. To choose the web interface time-out duration:
1. Login to the ILOM web interface.
2. Click the System Information Tab and click the Session Time-out Tab.
3. Set timeout to be 15 minutes, 30 minutes, 1 hour, or 3 hours.
You need to select the correct mouse mode corresponding to the host OS in order for your local mouse to manage the host remotely via the ILOM web interface.
1. Select the appropriate mouse mode:
2. Reset the SP to apply this change.
In order to switch control between local mouse and host mouse, you can press
“Alt +m”.
The following topics are contained in this section:
The following issue applies to SunVTS diagnostics software.
Running the "Network" test on the X4150 platform will fail due to lack of support in Solaris OS for the ESB-2 NIC loopback operations.
This will be fixed in a future version of SunVTS 7.0.
The following issues apply to the Pc-Check diagnostics software.
The following issues are contained in this section:
After creating a RAID 1 device in the BIOS, the Pc-Check diagnostics software fails to identify the device as a RAID device. Pc-Check cannot identify that the device is a RAID device, but Pc-Check can run all HDD tests.
The text for the keyboard LED test is not included in the diagnostics scripts. It can only can be run manually. This issue is under investigation and you should not attempt to run this test until a fix is available.
This issue is under investigation and you should not attempt to run this test until a fix is available.
This issue is under investigation and you should not attempt to run this test until a fix is available.
This issue is under investigation and you should not attempt to run this test until a fix is available.
This issue is under investigation and you should not attempt to run this test until a fix is available.
This issue is under investigation.
The following issues are related to the use of Sun Installation Assistant (SIA) for installing an OS on the server:
Full Power Cycle Needed After Expander Firmware Upgrade (6900072)
The SIA 2.3 User’s Guide states:
After selecting the expander(s) to upgrade, click Next.
Follow the on-screen instructions until the upgrade has completed. Upgraded code will not be used by the system until after a reboot.
| Note - To ensure that the expander firmware upgrade will take effect, after the upgrade has completed, unplug the power cord and plug it back in. |
In order to install Windows Server 2008 on a Sun Fire X4150 server using SIA, you will need to use SIA version 2.2.1 or later.
For further information on using SIA to install an operating system onto the server, see Sun Installation Assistant for Windows and Linux User’s Guide available on http://docs.sun.com.
If the .iso image size of the operating system being installed is bigger than the /tmp file size, the SIA installation will fail.
This only occurs if the http or ftp installation method is used.
Red Hat Enterprise Linux (RHEL) 5.2 installation via SIA fails when disks with legacy dmraid information are used.
Use a clean RHEL disk without legacy dmraid information.
Installing Windows 2003 from a NFS share or FTP share does not work with SIA.
| Note - This is planned to be fixed in a future release of SIA. |
For most Linux installations using SIA, the monitor resolution will need to be reset during the first-time-boot configuration, which runs after the OS installation is completed.
To reset the monitor resolution:
1. Configure the type (make/model) of the monitor.
2. Set the correct monitor resolution.
After installing and configuring Red Hat Enterprise Linux (RHEL) v. 5.1 (64-bit), the network devices are there and mapped as expected, but the interfaces are non-functional.
This issue occurs with the following configuration:
If the network cables are plugged in all NICs, this problem does not occur.
If user chooses to activate only the NIC with network cable plugged, this problem will not occur.
This problem will not occur if DHCP is chosen.
If different networks are configured for different NICs, this problem is not seen.
After booting the installed system, perform the following:
2. Enter the ifdown command for all the interfaces.
3. Enter the ifup command for the interface with network cable plugged in.
At this point, the network should be up and running.
4. To make this configuration persistent across reboots, you can make only the interface with network cable active on boot by doing the following:
a. Change to the network-scripts directory.
cd /etc/sysconfig/network-scripts
b. For the NICs that are not being used, edit the cfg-eth[1...n] file and change the line ONBOOT=yes to ONBOOT=no.
| Note - Keep the ONBOOT=yes setting for the NIC with the network cable. |
This section contains issues that apply to Sun Fire X4150 servers running the Solaris 10 operating system.
Issues contained in this section:
Do not install the driver from the Tools and Drivers CD if you are running Solaris 10 5/09. The Sun StorageTek RAID driver is included in the Solaris 10 5/09 distribution. The STK 15872 driver on the Tools and Drivers CD can be used for previous versions of Solaris.
For Solaris 10 8/07 to operate on the server with 5200 or 5400 Xeon processors, two patches are required for the OS to boot: 125370-06 and 127112-05. 125370-06 and 127112-05 are the minimum revisions required, but it is recommended that you apply the latest revisions of these patches.
After installing the OS, the system will not boot into Solaris normally until the required patches are applied. To be able to install the patches, you need to boot the system into 32-bit mode instead of the normal 64-bit mode.
1. After installing the Solaris OS, let the system reset normally, remove the Solaris CD/DVD (if inserted), and wait for the system to present the GRUB menu.
2. At the GRUB menu, before the menu times out and automatically attempts to boot the newly installed operating system, use the arrow keys to highlight the Solaris 10 8/07 s10x_u4wos_12b X86 entry and press e to edit this boot command.
A second menu with two choices appears.
3. Highlight the line containing kernel /platform/i86pc/multiboot and press e again to edit the entry.
You will now be able to edit the boot command.
4. Add kernel/unix to the end of the line so it looks like this:
grub edit> kernel /platform/i86pc/multiboot kernel/unix
5. Press Return, highlight the command that you just edited, and then press b to boot into Solaris 32-bit mode.
6. After Solaris finishes booting, log in and download the latest 125370 and 127112 patches to the system from http://sunsolve.sun.com/.
7. Now since the kernel patch should be installed in single user mode halt the system and perform the same steps as above to edit the GRUB boot command but this time edit the line so that it looks like this:
grub edit> kernel /platform/i86pc/multiboot kernel/unix -s
This will boot the system into 32-bit single user mode.
The system will prompt for the root password, and then give you a shell prompt.
8. At the prompt, run the following commands to add the patches, in this order, as there are dependencies.
Where xx is the latest version of each patch.
9. When the patches are finished installing, reboot the server.
You should now be able to let the system boot normally into 64-bit Solaris OS.
When Solaris 10 5/08 is released, these steps will not be necessary, since the required patches will have been integrated into this updated release.
This error may occur on the Sun Fire X4150 server running Solaris 10 11/06 OS with more than one hard disk drive present:
Panic cannot mount root path. Skipping System dump, no dump device configured rebooting.....
This is a known issue and bug CR 6584147 is being actively worked on for a resolution.
A reboot of the system will clear this error.
In the rare case where the error is not cleared by a reboot, please boot into Single User mode to clear the error and, once successfully booted, reboot the system. Should this scenario also be unsuccessful in clearing the error, power off and boot the system into Failsafe mode. Once in Failsafe mode, a reboot should clear the error.
The Sun Fire X4150 server with Solaris 10 11/06 OS has a number of patches included to support the Sun StorageTek SAS controller. Please note that if the preinstalled image is removed from HD0, you must use the Solaris Recovery DVD supplied with the Sun Fire X4150 server to reinstall the operating system because it includes support for your controller and hard disk drives. This issue will be resolved with the Solaris 10 8/07 OS release.
Solaris 10 OS 6/06 and 11/06 distributions have telnet vulnerability issue in the in.telnetd(1M) daemon that may allow unauthorized remote users to gain access to a Solaris host. A patch is available on the Tools and Drivers CD v2.0. Patch 120069-02 addresses the Solaris 10 6/06 and 11/06 telnet vulnerability issue. Apply the patch manually or run the install.sh script on all Solaris 10 6/06 and 11/06 distributions. For more information, please refer to Sun Security Alert 102802. This patch will be incorporated into the Solaris preinstall image at a later date.
In order to start the Solaris Xserver, all of the configured network interface cards (NIC) must be connected to the network. If a NIC is not configured, it does not need to be connected.
When installing Solaris 10 6/06 in a rack with a KVM switch, the monitor might go out of sync when the xserver starts to log into the operating system.
Any one of the following can be used as a workaround.
Install the Solaris OS in text mode, then do the following:
a. Run the install.sh script from the Tools and Drivers CD.
Running install.sh resolves the issue, as it installs the updated AST2000 VGA driver. See the Sun Fire X4150 Server Operating System Installation Guide, 820-1853, for additional instructions on running the install.sh script for Solaris.
Use KVMS over IP with the ELOM web GUI.
See the Embedded Lights-Out Management Administration Guide, 819-6588, for additional instructions on KVMS over IP.
Install Solaris in GUI mode, then do the following:
a. Boot failsafe or kill the Xserver prior to starting.
b. Run the install.sh script on the Tools and Drivers CD.
See the Sun Fire X4150 Server Operating System Installation Guide, 820-1853, for additional instructions on running the install.sh script for Solaris.
The following issues apply to Sun Fire X4150 servers running the supported Red Hat or SUSE Linux operating systems.
LSI drivers need to be manually installed on SLES systems.
1. Locate and download the LSI drivers from the Tools and Drivers CD.
a. Go to the \drivers\linux\RAID\LSI\drivers directory.
b. Copy the RHEL4_SLES9.tar.gz or RHEL5_SLES10.tar.gz file to your system.
c. Unzip and untar the file and locate the mptlinux-xxx.rpm file.
2. Use the rpm -i mptlinux-xxxxx.rpm to install the driver.
The command install.sh will not install this driver.
When typing characters on a Linux operating system running on the Sun Fire X4150 server, the keystrokes will auto-repeat. You can use the following workaround or install an updated kernel from Red Hat, see RHSA-2006:0710-7 at the following URL:
http://rhn.redhat.com/errata/RHSA-2006-0710.html
1. Select Preferences - > Keyboard from the desktop menu.
2. Uncheck the selection: keyboard repeats when key is held down.
1. Edit the file /usr/share/hal/fdi/policy/10osvendor/20-storagemethods-fdii.
2. Search for the following string: "<match key="volume.fsusage" string="filesystem">", which precedes the following commands:
<append key="volume.mount.valid_options" type="strlist">codepage=</append>
<append key="volume.mount.valid_options" type="strlist">iocharset=</append>
<append key="volume.mount.valid_options" type="strlist">umask=</append>
<append key="volume.mount.valid_options" type="strlist">uid=</append>
</match>
</match>
3. Enter the following below the commands listed in step 2:
<!-- Added for the issue that virtual ISO image can’t be shown -->
<!-- as an icon when this virtual device is inserted to REHL5 system -->
<match key="@block.storage_device:storage.vendor" string="Virtual">
<match key="@block.storage_device:storage.model" string="DVD/CD-ROM">
<match key="info.category" string="volume">
<match key="block.is_volume" bool="true">
<match key="volume.fsusage" string="">
<merge key="volume.fsusage" type="string">filesystem</merge>
<merge key="volume.fstype" type="string">iso9660</merge>
</match>
</match>
</match>
</match>
</match>
The following issues apply to Sun Fire X4150 servers running the supported Windows Server operating systems.
After installing the MegaRaid Storage Manager and Intel Network Connections (NIC Teaming), the mrmonitor service stops unexpectedly and cannot start. This affects servers running Windows Server 2003 64-bit.
Do not install the NIC Teaming software if the LSI Storage Manager software is required.
The Adaptec driver cannot be updated with the Tools and Drivers CD v2.2.1 (and earlier) auto install on Windows Server 2003 (32-bit/64-bit) and Windows Server 2008 (32-bit/64b-bit).
Manually install this driver as follows:
1. Open the Windows Device Manager.
2. Right click the device with yellow question mark.
4. Find the driver in \drivers\windows\RAID\StorageTEK\2003 or
\drivers\windows\RAID\StorageTEK\2008.
5. Click OK to install the driver.
In order to be able to run the reburn diagnostics test, you must install the OS on the C: drive of the server.
Servers shipped with the factory-installed Windows Server 2003 R2 operating system include a Getting Started Guide. Read this guide before performing the initial setup of the Windows Server 2003 R2 operating system. For initial setup procedure, refer to the Sun x64 Servers Windows 2003 R2 Preinstall Release Notes.
If you need to restore your system to the default factory-installed Windows operating system, follow the directions in the Sun x64 Servers Windows Server 2003 R2 Recovery Installation Guide enclosed in the optional recovery media kit and posted online. If you do not have the recovery media kit, contact your support representative.
For ESX 3.5 installed with multiple virtual machines (VMs) booted and operational, you might encounter the following issue after migrating from ELOM to ILOM.
After shutting down the VMs and upgrading to ILOM, when the ESX host is booted, the VMs hang at 95% of the startup process, and a yellow bang appears. The following message is displayed in the "Summary" tab in VI:
The virtual machine now boots as expected with the same identifier and will operate properly.
The following issues relate to Sun Fire X4150 servers with the LSI 3081E HBA installed.
You must leave 100 MB of free unpartitioned space at the end of the hard disk if you plan on upgrading to a mirrored configuration.
The only upgrade path that supports data merging is from a single disk to a mirror. This is a limitation of the card. If you wish to upgrade from a single disk to an IMe (Integrated Mirror Extension) or an IMS (Integrated Mirror Stripe), the operating system and its data will be lost and a reinstall/restore will be required.
When a RAID set of disks is in sync mode, the server might hang if a reboot is issued. This hang will cause the disk to lose its RAID configuration. Do not reboot while a sync is in progress. This issue is being investigated.
The following issues relate to Sun Fire X4150 servers with the Sun StorageTek SAS Controller installed.
The controller firmware can be flashed using Adaptec Storage Manager (ASM) or the flash utility (AFU) that is included on the Tools and Driver CD
Use one of the following procedures to flash the firmware:
1. Boot from the Sun Fire X4150 Server Tools and Drivers DVD.
2. At the main menu screen prompt, enter 3 to go into DOS.
3. Change the directory to firmware\SST\ .
4. Type flash.bat, then press Enter to launch the SRL card firmware update GUI.
5. In the Adaptec flash utility, select Controller, and then select the operation ’Update flash images’.
6. Make sure that the directory for the flash image is correct, and press OK to begin flash new firmware for your card.
1. Copy each *.ufi file individually to a separate floppy disk.
If you don’t do this, you might encounter read errors from one of the files when flashing the controller.
2. Shut down the operating system and reboot to DOS from a bootable floppy disk.
3. Insert the floppy with the update files.
4. Run the flash utility program named AFU.EXE to backup the current BIOS and flash the new BIOS image.
For instructions on how to update the firmware using Adaptec Storage Manager (ASM), refer to the ASM User’s Guide or the ASM online help.
Before the operating system can use hard disks attached to a StorageTek SAS Controller, the drives must first be initialized and the array created using the StorageTek BIOS setup utility. The StorageTek BIOS setup utility can be accessed using the CTRL-A keystroke combination during server POST.
To install the StorageTek Management Software on Red Hat Linux 5, an rpm must first be installed. This is because Java is not supported in Red Hat Linux 5. Use the rpm that applies to your operating system installation:
They can be found in the /drivers/linux/RAID/StorageTEK/MGMT/version folder on the Tools and Drivers CD. Copy the appropriate rpm file to your Red Hat 5 system and run the rpm -install command.
The following issues relate to Sun Fire X4150 servers with the Sun 10G Network Adapter installed.
The Sun 10G network adapter may require a firmware update to version 3.12 or later for correct operation in the Sun Fire x4150. The link for this firmware update is below.
http://www.sun.com:80/download/products.xml?id=45a593ce
The following issues apply to the Sun Fire X4150 server documentation:
An updated installation guide for Solaris 10. Red Hat Enterprise Linux (RHEL), SUSE Linux Enterprise Server (SLES), and VMware ESX Server operating systems is now available. This document combines operating system installation for the Sun Fire X4150, Sun Fire X4250, and Sun Fire X4450 servers. This document is available at:
http://docs.sun.com/app/docs/prod/sf.x4150
The following document is now available: Sun Fire X4150, X4250 and X4450 Servers Windows Operating System Installation Guide.
The information in this document supersedes the information in the Sun Fire X4150 Server Operating System Installation Guide.
Both documents are available at:
http://docs.sun.com/app/docs/prod/sf.x4150
These notes are specific to BIOS 025 in Tools and Drivers CD 1.3.1. If you are using an older BIOS, you need to implement the instructions in the Sun Fire X4150, X4250, and X4450 Servers Operating System Installation Guide for serial redirection when installing Solaris 10 OS.
ELOM now supports the default serial redirection of TTYA/COM1 versus the older method (pre -1.3.1 Tools and Drivers CD) that was TTYB/COM2.
Now the Solaris PreInstall and Jumpstart will not require an edit to the kernel mini-root to install via serial console.
Note the following regarding items in the Sun Fire X4150, X4250, and X4450 Servers Operating System Installation Guide, 820-1853-14:
For systems with firmware from Tools and Drivers 1.2 (BIOS 020) and before use the current OS installation method in the documentation.
For systems with firmware level from Tools and Drivers CD 1.3.1 (BIOS 025) and later, refer TABLE 5 on Solaris installation methods.
The instructions in this section are only relevant for Sun Fire X4150 server firmware 1.2 and below as the default serial redirection settings were TTYB/COM2.
Tools and Driver release 1.3 and later now have the default serial port set to TTYA/COM1 (Solaris defaults), so the instructions in this section are not needed.
The Sun Fire X4150 Server Service Manual, 820-1852-10, has an incorrect description and diagram of the LEDs located on the system’s power supply.
Figure 3-8 on page 3-14 of the PDF version shows an image of the power supply where the icons next to the LEDs are incorrect. The "Figure Legend" beneath this image is also incorrect.
The correct order of the LEDs and LED functions are show in the following table.
This will be corrected in a future version of the Service Manual.
The Sun Fire X4150 Server Service Manual, 820-1852-10, contains errors in the procedure to reset BIOS password using a jumper.
Pages 4-33 through 4-35 refer to using jumper J33 to reset the CMOS NVRAM and change the BIOS password. This is incorrect.
The correct jumper is J23 to both reset the CMOS NVRAM and BIOS password. This jumper is located near the CR 2032 battery, below the PCIe riser 0.
The remainder of the procedure is correct, and can be followed using the J23 jumper.
The following issues have been resolved:
Refer to the following sections for information on issues that have been fixed in the software supplemental releases:
The following issue has been fixed in Sun Fire X4150 and X4250 Software Supplemental 3.2.0:
Upgrading to the current version of ILOM (3.0.3.30 and above) corrects the Product Serial number automatically.
If you find that the product serial number is not the same as the chassis serial number on your Sun Fire X4150/X4250/X4450 systems, upgrade your ILOM to the latest version to fix this problem.
The SEL log in CLI or the Web interface reminds you to reboot ILOM to make the change take effect. This correction check happens every time ILOM reboots. If the reboot is not successful, repeat the ILOM reboot to retry.
| Note - The fru_serial_number was added to show chassis serial number to avoid confusion when the chassis serial number is different from that of the product. |
The following issue has been fixed in Sun Fire X4150 and X4250 Software Supplemental 3.0.2:
The following issues have been fixed in Sun Fire X4150 and X4250 Software Supplemental 3.0.1:
The following issues have been fixed in Sun Fire X4150 and X4250 Software Supplemental 2.2.2:
The Sun Fire X4150 Server Operating System Installation Guide (820-1853-11) includes directions on installing NIC teaming drivers in Windows 2003 Server that are inaccurate. Please follow the instructions listed below for proper NIC teaming software installation:
|
1. Install the Ethernet drivers from the Tools and Drivers CD version 1.1, using your preferred method:
a. Autorun -- Insert the Tools and Drivers CD and from the Autorun menu, choose Install/Update drivers and optional packages.
b. Manually -- Access the Ethernet properties and update the driver manually through Device Manager.
2. Once the Ethernet cards have been installed and IP addresses assigned, run the Proset installer.
3. The installer is found on the Tools and Drivers CD (starting at version 1.1) in the following location:
drivers\windows\IntelNic\2003\PROSET\2003_xx
where xx is 32 or 64 bit, use the PROSETDX.msi installer.
4. Follow the instructions on your screen and choose the Advanced Network Features from the displayed list of options.
5. To access the PROSET Teaming options, access the Ethernet card through Device Manager and choose Properties.
6. The new tabs installed will be Teaming and VLAN.
In the Sun Fire X4150 Server OS Installation Guide, 820-1853-11, Chapter 5, note that when installing Windows Server 2003 using the Sun StorageTek Driver diskette, the external USB floppy drive must be certified for use with 32-bit or 64-bit Windows Server 2003.
The following sections list issues that have been fixed in the Tools and Drivers CDs/DVDs:
To correct the following issues, download the latest Tools and Drivers CD/DVD from
http://www.sun.com/servers/x64/x4150/downloads.jsp
The following BIOS issues have been fixed in Sun Fire X4150 3.1.1 DVD
The following BIOS issues have been fixed in Sun Fire X4150 3.1.0 DVD:
The following ILOM issues have been fixed in Sun Fire X4150 3.1.0 DVD:
The Remote KVM does respond if the connection is terminated ungracefully due to any of the following actions:
If the remote KVM session does not respond due to any of these conditions, either reset SP or wait 30 minutes for the remote session to restart.
The following issues have been fixed in Sun Fire X4150 3.00 DVD:
Some non-critical events are marked as "critical". These events are changed to "minor" in Tools and Drivers DVD 2.2.1.
There are some non-decodable addresses of memory error events sent from the BIOS. This will be fixed to define a field to support the number of DIMM errors.
When you power on the system with no usable memory (no DIMMs), the BIOS reports "no usable memory" and does not power on. The message that appears in the event log uses the incorrect sensor name.
When the "Restore on AC Power Loss" is set to "Last State" from BIOS menu, the last state is not restored.
When performing a "power on" action, the BIOS will send out a "initiated by hard reset" event long. This is changed to "initiated by power up" in Tools and Drivers CD 2.2.1.
The following issues have been fixed with the BIOS update included on this Tools and Drivers CD:
The following issues have been fixed with the ILOM update included on this Tools and Drivers CD:
The following issues are fixed with Tools and Drivers CD version 2.10.
The one-click installation function that uses Windows autorun to install the LSI3081E Management Software and StorageTek Management Software does not work correctly.
This has been corrected in Tools and Drivers DVD 2.1.0.
If you do not update to the 2.1.0 Tools and Drivers DVD, you need to manually install the software.
The following issues are fixed with Tools and Drivers CD version 2.0.
When using the StorageTek SAS controller setup utility in CLI Mode, the initial menu is displayed and then "5;00H" is continuously scrolled so that the menu is scrolled off the screen. This issue have been fixed in ILOM BIOS version 1ADQW052 or later.
The following issues are fixed with Tools and Drivers CD version 1.3.3.
The firmware setup utility for the SG-XPCIE SAS-R-INT-Z HBA card is unusable through the ELOM console.
Workaround: Use the web GUI Remote Console redirection utility or a locally attached keyboard and monitor setup to configure the disks so that the OS can be installed and used.
When the CMOS checksum error occurs during POST, the POST halts until the user presses F1.
With this firmware update, optimized defaults are loaded and POST continues when the checksum error is encountered.
When you run the prtdiag command on a Solaris system when two cards are installed in slot1 and slot0, the prtdiag reports that slot1 and slot2 are in use.
When a fan is removed for the system, the Set Platform Event Filter does not set a trap for the fan.
When PSU fan rotation stops, it is recorded as an error in SEL and the PSU fail LED is lit.
The following issues are fixed with Tools and Drivers CD version 1.3.2.
With this firmware release, the system is able to detect if the PSU or power cord is removed and records an error in SEL along with the PSU fail LED.
The BIOS setting terminal type=vt100/ansi was inadvertently omitted after BIOS version 020 (from 1.2 Tools and Driver CD).
A fix for this issue is planned for a later release of the BIOS.
The following issues are fixed with Tools and Drivers CD version 1.3.1.
When removing a fan from the server, the SEL will log an event indicating that the fan is present.
For earlier SG-PCIESAS-R-INT-Z HBA firmware releases, the temperature threshold was set too low in the HBA firmware. This can cause the StorMan application to report erroneous over-temperature conditions.
If you encounter the erroneous over-temperature reports, update the HBA firmware to the latest available version if this issue is seen.
|
Copyright |
Copyright © 2010 Sun Microsystems, Inc., 4150 Network Circle, Santa Clara, California 95054, U.S.A. All rights reserved.
THIS PRODUCT CONTAINS CONFIDENTIAL INFORMATION AND TRADE SECRETS OF SUN MICROSYSTEMS, INC. USE, DISCLOSURE OR REPRODUCTION IS PROHIBITED WITHOUT THE PRIOR EXPRESS WRITTEN PERMISSION OF SUN MICROSYSTEMS, INC.
This distribution may include materials developed by third parties. Sun, Sun Microsystems, the Sun logo, Java, Netra, Solaris, StarOffice, Sun Ray, Galaxy Sun Fire X and the SunSpectrum Pac (Sunburst design) logo are trademarks or registered trademarks of Sun Microsystems, Inc. or its subsidiaries in the U.S. and other countries. Intel is a trademark or registered trademark of Intel Corporation or its subsidiaries in the United States and other countries. Intel Inside is a trademark or registered trademark of Intel Corporation , or its subsidiaries,s in the United States and other countries.
This product is covered and controlled by U.S. Export Control laws and may be subject to the export or import laws in other countries. Nuclear, missile, chemical biological weapons or nuclear maritime end uses or end users, whether direct or indirect, are strictly prohibited. Export or reexport to countries subject to U.S. embargo or to entities identified on U.S. export exclusion lists, including, but not limited to, the denied persons and specially designated nationals lists is strictly prohibited.
Use of any spare or replacement CPUs is limited to repair or one-for-one replacement of CPUs in products exported in compliance with U.S. export laws. Use of CPUs as product upgrades unless authorized by the U.S. Government is strictly prohibited.
Copyright © 2010 Sun Microsystems, Inc., 4150 Network Circle, Santa Clara, California 95054, Etats-Unis. Tous droits réservés.
CE PRODUIT CONTIENT DES INFORMATIONS CONFIDENTIELLES ET DES SECRETS COMMERCIAUX DE SUN MICROSYSTEMS, INC. SON UTILISATION, SA DIVULGATION ET SA REPRODUCTION SONT INTERDITES SANS L’AUTORISATION EXPRESSE, ECRITE ET PREALABLE DE SUN MICROSYSTEMS, INC.
Cette distribution peut des éléments développés par des tiers. Sun, Sun Microsystems, le logo Sun, Java, Netra, Solaris, StarOffice, Sun Ray, Galaxy Sun Fire X et le logo SunSpectrum Pac (Sunburst design) 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. Intel est une marque de fabrique ou une marque déposée de Intel Corporation ou de sa filiale aux Etats-Unis et dans d’autres pays. Intel Inside est une marque de fabrique ou une marque déposée de Intel Corporation ou de sa filiale aux Etats-Unis et dans d’autres pays.
Ce produit est soumis à la législation américaine sur le contrôle des exportations et peut être soumis à la règlementation en vigueur dans d’autres pays dans le domaine des exportations et importations. Les utilisations finales, ou utilisateurs finaux, pour des armes nucléaires, des missiles, des armes biologiques et chimiques ou du nucléaire maritime, directement ou indirectement, sont strictement interdites. Les exportations ou reexportations vers les pays sous embargo américain, ou vers des entités figurant sur les listes d’exclusion d’exportation américaines, y compris, mais de maniere non exhaustive, la liste de personnes qui font objet d’un ordre de ne pas participer, d’une façon directe ou indirecte, aux exportations des produits ou des services qui sont régis par la législation américaine sur le contrôle des exportations et la liste de ressortissants spécifiquement désignés, sont rigoureusement interdites.
L’utilisation de pièces détachées ou d’unités centrales de remplacement est limitée aux réparations ou à l’échange standard d’unités centrales pour les produits exportés, conformément à la législation américaine en matière d’exportation. Sauf autorisation par les autorités des Etats-Unis, l’utilisation d’unités centrales pour procéder à des mises à jour de produits est rigoureusement interdite.
Updating the CPLD
