Sun Blade™ X6440 Server Module Product Notes Version 2.0 Sun Microsystems, Inc. www.sun.com Part No. 820-3965-15, Rev. A November 2009 Submit comments about this document by clicking the Feedback[+] link at: http://docs.sun.
Copyright © 2009 Sun Microsystems, Inc., 4150 Network Circle, Santa Clara, California 95054, U.S.A. All rights reserved. Sun Microsystems, Inc. has intellectual property rights relating to technology embodied in the product that is described in this document. In particular, and without limitation, these intellectual property rights may include one or more of the U.S. patents listed at http://www.sun.com/patents and one or more additional patents or pending patent applications in the U.S.
Sun Blade X6440 Server Module Product Notes This document contains late-breaking information and issues for the Sun Blade™ X6440 server module.
General Information Support and Patches for Sun Blade Server Modules Support information for the Sun Blade X6440 server module is available at: http://sunsolve.sun.com Supported Operating Systems The following is a list of the minimum versions of supported operating systems for the Sun Blade X6440 server module: 2 ■ Solaris x86 10 05/08, 64-bit ■ Solaris x86 10 10/08, 64-bit ■ Solaris x86 10 05/09, 64-bit ■ OpenSolaris 2009.06 ■ Red Hat Enterprise Linux (RHEL) 4.
Documentation Support documentation for the Sun Blade X6440 server module: ■ Sun Blade X6440 Server Module Installation Guide (820-3961) ■ Sun Blade X6440 Server Module Product Notes (820-3965) ■ Sun Blade X6440 Server Module Operating Systems Installation Guide (820-3962) ■ Sun Blade X6440 Server Module Windows Operating System Installation Guide (820-3963) ■ Sun Installation Assistant for Windows and Linux User’s Guide (820-3357) ■ Sun Blade X6440 Server Module Getting Started Guide (820-3960)
Sun Blade X6440 Server Module Tools & Drivers DVD The Sun Blade X6440 Server Module Tools & Drivers DVD contains several software applications and utilities for use with your Sun Blade X6440 server module. This section describes the applications and utilities and refers you to the associated readme text files where you can find procedures for running them. ■ ILOM SP update. Used to update the SP firmware; the readme text file is located in :\remoteflash\Firmware_Update.txt.
Newly Supported Features The following new features are supported as of supplemental software release 2.0: ■ Integrated Lights Out Manager 3.0 ■ Sun ILOM Remote Console Lock ■ Sun ILOM Power Management Integrated Lights Out Manager 3.0 The Sun Blade X6440 server module supports Integrated Lights Out Manager (ILOM) 3.0 on the service processor (SP) module. For information and instructions on using ILOM 3.0 with the Sun Blade X6440 server module, see the ILOM 3.
Sun ILOM Remote Console Lock The Sun Blade X6440 server module supports the Sun ILOM Remote Console lock. The Sun ILOM Remote Console lock feature enhances your system security by enabling you to lock your computer when terminating a Sun ILOM Remote Console session. For more information and instructions for using the lock feature, see the Sun Integrated Lights Out Manager (ILOM) 3.0 Feature Updates and Release Notes (820-7329).
ILOM BIOS settings issue 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 DHCP is restored, the original IP address will be assigned.
Blade server module fails to link up at 1GbE If the Sun Blade X6440 server module is inserted into certain slots in the Sun Blade 6048 chassis, it fails to link up at 1GbE with the X5196A-Z Sun Blade 6048 Infiniband Switched Network Express Module (NEM). This issue occurs primarily on the inner slots (BL3-BL8). These slots can only link up at 100Mb. Workaround: Use the outer slots (BL0-BL2 and BL9-BL11) to link up at 1GbE. This issue is under investigation.
Certain devices’ boot option ROM fails to load A shadow ROM space issue exists when multiple bootable devices are installed in the system. Not all devices’ bootable option ROMs will successfully load. Workaround: This issue is fixed in the Tools & Drivers DVD 1.2 and later software release. Users will have the option to select which option ROM to load in the BIOS setup window.
LVM partitioning is not supported when installing SLES 10 SP2 operating system Change Request ID: 6780100 If LVM disk partitioning is selected when installing the SLES 10 SP2 operating system using SIA, the installation will fail because the platform drivers will not install correctly. Workaround: None SLES 9 SP4 operating system is not supported using SIA Change Request ID: 6771799 Do not use SIA to install the SLES 9 SP4 as SIA does not support this operating system.
Workaround: None SIA will not install FEM drivers for Windows 2003 Change Request ID: 6769562 If SIA is used to install Windows 2003 on a system that contains the model x1029 A FEM, the associated device will be highlighted with a yellow question mark in the Windows Device Manager, indicating that the drivers are not installed correctly. Workaround: None RHEL installed using SIA reports a MPT Fusion ctl drivers error Change Request ID: 6737853 If SIA is used to install RHEL 4.
When installing the Linux operating system using SIA version 2.3.8, the System Information screen displays incorrect information for the chassis type, serial number, and version number. This issue will be fixed in future software release. SIA does not display storage controllers Change Request ID: 6878694 When installing the Linux operating system using SIA version 2.3.8, the System Information screen does not display system storage controllers. This issue will be fixed in future software release.
SIA does not install operating systems via PXE server Change Request ID: 6876850 When using SIA version 2.3.8 to install OSes via a PXE server, SIA displays the following error message during the OS installation: Error enabling swap device sda2: Invalid argument This error affects all OS installations that SIA supports. This error occurs after the disk partition phase of the OS installation and might indicate that the swap device has not been initialized. Workaround: Add parameter iommu=soft in PXE server.
Delaying BIOS Upgrade During Firmware Update Can Corrupt BIOS The ILOM SP firmware upgrade procedure includes the Delay BIOS Update option, which delays the BIOS update until the host is reset. This option allows you to update the firmware without resetting the host. The following scenarios can cause your BIOS to corrupt: ■ If you select the Delay BIOS Update option, then power down the host and remove the server module from its slot before the BIOS update is complete.
Minimum Supported Browsers TABLE 1 shows the minimum supported browser versions for running the Integrated Lights Out Manager (ILOM) web interface for the Sun Blade X6440 server module on Solaris and Linux operating systems. TABLE 1 Version Numbers for Browsers 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.
● If you are logged in as root, choose to open the file with its default application. –or– ● 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. 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.
Error message appears during service processor startup The following error message may appear during service processor (SP) startup: Mike driver. insmod: cannot insert ‘/lib/modules/2.6.15.4/misc/mtd_mike/mike.ko’: No such device (1): No such device modprobe: failed to load module mike This issue is being investigated. It is safe to ignore this message. FRU data for the hard disk drives is not passed via ipmitool FRU data for the hard disk drives (HDD) is not passed via ipmitool.
Hard disk error message in the SP event log The following error message might appear in the SP event log when no hard disk is installed. System Firmware Error | Unrecoverable hard-disk controller failure | Asserted Workaround: It is safe to ignore this error message. DIMM SPD data are reported incorrectly in the FRU data Certain DDRII DIMMs are displayed incorrectly in the SP FRU data. For example, DDRII 800 MHz DIMMs are listed only as 444 MHz DIMMs in the FRU data.
Hard disk information is unknown When running the Pc-Check hard disk diagnostics, the hard disk information, hard disk firmware, and serial number are listed as unknown. Serial port test fails The Pc-Check serial port test fails because Pc-Check does not support the RJ-45 serial port connector. SunVTS Diagnostics Software Issues The following issue applies to SunVTS™ diagnostics software. SunVTS I/O port test fails The SunVTS I/O port test fails when the system is in exerciser mode.
■ ■ “Only 8 of 16 CPU cores being reported” on page 22 ■ “Post OS driver update script fails to run” on page 23 ■ “SLES OS driver installation takes a long time to complete” on page 23 ■ “NIC drivers are not supported by SLES11 OS” on page 23 ■ “SLES 9 SP4 hangs during installation or startup” on page 23 ■ “USB devices are not recognized in RHEL 4.
This issue is being investigated. Linux Issues The following issue applies to Sun Blade X6440 server modules running the supported Red Hat Enterprise Linux (RHEL) or SUSE Linux Enterprise Server (SLES) operating systems. USB device errors reported in Red Hat 5.1 The following error is generated when a USB device is inserted in the USB ports on the Sun Blade X6440 server module: usb 1-2; device not accepting address 2, error -71 This is a RHEL 5.1 issue. Workaround: You must manually create a new initrd.
3. Insert the PEM in either slot and press the Attn button. The PEM is ready to use when the OK LED turns solid green. PCI BIOS error message might appear The following error message might appear when booting or running the dmesg command in RHEL 5.1: PCI: BIOS Bug: MCFG area at e0000000 is not E820-reserved PCI: Not using MMCONFIG. It is safe to ignore this message. IGB error message might appear The following IGB error message might appear in dmesg: igb: 0000:84:00.
Workaround: Install and boot from the largesmp kernel version, which can be found in the installation media. Post OS driver update script fails to run The following error message might display when running the post OS driver (install.sh) update script: bash ./install.sh: /bin/sh: bad interpreter: Permission denied Workaround: Run the post OS driver update using the sh install.sh command, or unmount and remount the Tools & Drivers DVD manually.
Workaround: This issue can be resolved by following these steps: 1. Temporarily limit the memory to less than 4 GB. This can be accomplished by physically removing RAM to reduce it to less than 4 GB. Alternately, you can use a boot parameter to limit the memory that is used by SLES. The boot parameter is mem=nnnn, where nnnn is equal to a number less than 4000. 2. Install the latest kernel update to version 2.6.5-7.311 or newer.
2. Reboot the system for the changes to take effect. 3. Run Windows Autorun to install drivers. Yellow question mark might appear in Windows Device Manager A yellow question mark might appear in the Windows Device Manager, denoting that drivers are not installed for the following devices: ■ Sun Blade Storage SCSI Enclosure Device ■ Sun NEM Plus SCSI Enclosure Device Workaround: Run Windows Update to install the necessary drivers.
LSI RAID Expansion Module (REM) Issues This section contains the following LSI RAID REM issues: ■ “Extra hard disk drive space required when upgrading to a Mirrored RAID configuration” on page 26 ■ “Upgrade path for data merging” on page 26 Extra hard disk drive space required when upgrading to a Mirrored RAID configuration You must have 100 MB of free unpartitioned disk space at the end of the hard disk drive if you want to upgrade to a mirrored RAID configuration.
