X6440 server module.
|
Sun Blade X6440 Server Module Product Notes |
This document contains late-breaking information and issues for the Sun Blade X6440 server module.
The following is covered in these product notes:
Support information for the Sun Blade X6440 server module is available at:
The following is a list of the minimum versions of supported operating systems for the Sun Blade X6440 server module:
Support documentation for the Sun Blade X6440 server module:
These and other Sun Blade server module documents are available at http://docs.sun.com/app/docs/prod/blade.x6440.
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.
| Note - This utility can be performed on a Windows-based system or a Linux/Solaris-based system. |
Please go to http://www.sun.com/servers/blades/downloads.jsp for the latest firmware versions.
The following new features are supported as of supplemental software release 2.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.0 Documentation Collection and the associated ILOM Supplement for the Sun Blade X6440 server module:
The ILOM 3.0 Documentation Collection is available at: http://docs.sun.com/app/docs/prod/int.lights.mgr30#hic
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).
The Sun Blade X6440 server module supports Sun ILOM power management features. Sun ILOM power management features enable you to monitor and manage your system’s power consumption. For more information and instructions for using ILOM power management features, see the Sun Integrated Lights Out Manager (ILOM) 3.0 Feature Updates and Release Notes (820-7329).
The following issues apply to the Sun Blade X6440 server module hardware and/or BIOS:
When a user boots the system to Solaris and then installs an Express Modules X1288A-Z, the hot-plug function can not work by pressing the attn button. If the user manually configures this IB PEM with cfgadm command, the following error message appears:
cfgadm: Hardware specific failure: configure failed
Install the IB-PEM card before powering on the system.
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.
Do not reboot the server until DHCP is restored, or connect a terminal to the serial console’s NET Management port and manually assign a static IP address if access is urgently required to ILOM.
If the ILOM IP address is changed via the LAN configuration in the BIOS, the IP address will not update. The old IP address is displayed. It is recommended to change the IP address via ILOM.
If you choose to change the ILOM IP address via BIOS, exit and re-enter the LAN configuration screen to see the changes.
The Mellanox Infiniband PCI-E expansion module fault light may illuminate after it has been hot-inserted into a server module running the Solaris OS. The fault light will not clear itself until the system is rebooted.
Update to the latest BIOS that is included on the Tools and Driver v1.1 DVD-ROM or a later version.
The green LED Power LED incorrectly stops blinking and turns solid green once ILOM detects that the power is good. The green Power LED should stop blinking and turn solid only when the operating system is ready.
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.
Use the outer slots (BL0-BL2 and BL9-BL11) to link up at 1GbE.
This issue is under investigation.
If more than eight X6440 server modules are to be inserted into the Sun Blade 6000 chassis (which can hold a maximum of 10 server modules), power supply redundancy must be set to non redundant mode. This will allow all X6440 server modules in the chassis to be powered on simultaneously.
The BIOS fails to permanently modify the boot order after sending the ipmitool persistent boot order change command.
This issue is fixed in the Tools & Drivers DVD 1.2 and later software release.
The BIOS fails to clear all setup settings and load system defaults after sending the ipmitool clear CMOS command.
This issue is fixed in the Tools & Drivers DVD 1.2 and later software release.
A shadow ROM space issue exists when multiple bootable devices are installed in the system. Not all devices’ bootable option ROMs will successfully load.
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.
Network express module (NEM) model X4238 requires the latest BIOS firmware to work properly. The required BIOS firmware (version 1.2) is located on the Sun Blade X6440 Server Module Tools & Drivers DVD.
The following issues apply to the Sun Installation Assistant (SIA) software:
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.
Do not use SIA to install the SLES 9 SP4 as SIA does not support this operating system.
Change Request ID: 6771790 and 6771803
Infiniband (IB) drivers for the IB passthru FEM (fabric express module) and IB NEM (network express module) will not install correctly when installing Windows 2003/2008 using SIA.
Model x1029A fabric express module (FEM) and model x4236A network express module (NEM) drivers will not install correctly when installing Linux (such as RHEL 32-bit and SLES 10 32-bit) using SIA.
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.
If SIA is used to install RHEL 4.6 on a system that does not contain a Sun Blade I/O Expansion Module II (mptsas) controller, the following error will occur when RHEL boots:
starting MPT Fusion ctl drivers FAILED
This error is harmless and can be ignored.
This issue will be fixed in future software release.
When installing the Linux operating system using SIA version 2.3.8, the ILOM version is displayed as “Unknown” in the System Information screen.
This issue will be fixed in future software release.
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.
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.
When installing some operating systems using SIA version 2.3.8, SIA might display the following error message while SIA is determining the OS:
This message can be ignored. The OS installation will complete successfully.
This issue will be fixed in future software release.
When selecting the SIA Update function in SIA 2.3.8, SIA might display the following error message:
This issue will be fixed in future software release.
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.
Add parameter iommu=soft in PXE server.
The following issues apply to the Sun Blade X6440 server module Integrated Lights Out Manager service:
For more information about the ILOM, see the online Sun Integrated Lights Out Manager 2.0 User’s Guide (820-1188) or the Sun Integrated Lights Out Manager 3.0 Documentation Collection.
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:
Do not select the Delay BIOS Update option. If you choose to use the Delay BIOS Update option:
1. Do not remove the server module from its slot until after the host has been reset and the BIOS update is complete.
2. If you are powering off the system for the first time after ILOM is upgraded, do not power on the host until the BIOS update is complete.
3. Do not attempt to update the SP firmware until after the host has been reset and the BIOS update is complete.
| Note - The BIOS update after host power-off might take 3-4 minutes. |
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.
No errors or warnings are issued to the user when the user exceeds the 16-character limit for passwords via the web interface.
This issue is scheduled to be fixed in a future ILOM firmware release.
User authentication for KVMS sessions cannot be performed using any of the remote user-authentication mechanisms, such as RADIUS, LDAP, or ActiveDirectory.
This issue is scheduled to be fixed in a future ILOM firmware release.
When you launch a Remote Console session on a Solaris system, the system will prompt you for a decision regarding the javaRKVM.jnlp file. You have the following two options:
If you are logged in as root, choose to open the file with its default application.
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. To find the location of the javaws application, enter 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.
Assuming that the javaws application is run from the /usr/bin directory, the following command will open a Remote Console session:
% /usr/bin/javaws /tmp/javaRKVM.JNLP
Once the remote console window is closed, the /tmp/javaRKVM.jnlp is removed.
On server blade insertion or server processor (SP) reset, the SP might take up to 3 minutes to start. The SP will not function during this time, and the port 80 reader will toggle between 55 and AA.
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 (HDD) is not passed via ipmitool. For example, the following error message is received:
FRU Device Description : HDD0 (ID 24)
Device not present (Requested sensor, data, or record not found)
FRU Device Description : HDD1 (ID 25)
Device not present (Requested sensor, data, or record not found)
This issue is scheduled to be fixed in a future ILOM/BIOS release.
The impitool session info all command fails. For example, the following error message is received:
impitool -H 129.148.53.83 -U root -P changeme session info all
Get session Info command failed
This issue is scheduled to be fixed in a future ILOM/BIOS release.
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
It is safe to ignore this error message.
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. This is a FRU data discrepancy and it does not impact memory and system performance.
This issue is scheduled to be fixed in a future ILOM firmware release.
This section contains the following:
The following issues apply to the Pc-Check diagnostics software.
When running the Pc-Check hard disk diagnostics, the hard disk information, hard disk firmware, and serial number are listed as unknown.
The Pc-Check serial port test fails because Pc-Check does not support the RJ-45 serial port connector.
The following issue applies to SunVTS diagnostics software.
The SunVTS I/O port test fails when the system is in exerciser mode. This occurs because the test fails to read written bytes at various baud rates when the system is under heavy stress.
Run the SunVTS I/O port test in standalone or in component mode.
This section contains the following:
For a list of minimum supported operating systems, see Supported Operating Systems.
When using a compact flash device, the following warning message might appear during Solaris startup:
WARNING: /pci@0,0/pci-ide@4/ide@0 unable to enable write cache targ=0
It is safe to ignore this message.
When installing the Solaris OS in a system that contains an LSI 1068e B3 HBA, the installation halts at the “Configuring Devices” screen. This issue does not occur when using other HBA cards in the system.
This issue is being investigated.
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.
System will hang easily on RHEL 5.4 32bit/64bit with XEN kernel
Install Intel network driver version 2.1.9 (or later version), which is available at http://downloadcenter.intel.com/Detail_Desc.aspx?agr=Y&DwnldID=18975&lang=eng.
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
You must manually create a new initrd.img file in your current installation:
2. Navigate to the /boot directory.
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 module to effect the changes.
The “acpiphp” module is not loaded in the kernel by default.
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.
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.
The following IGB error message might appear in dmesg:
igb: 0000:84:00.1: igb_set_interrupt_capability: Failed to initialize MSI-X interrupts.
Failing back to MSI interrupts.
igb: 0000:84:00.1: igb_set_interrupt_capability: Failed to initialize MSI interrupts.
Failing back to legacy interrupts.
Both onboard Intel 82575EB network interface cards (NICs) are still functional. It is safe to ignore this message. This issue is being investigated.
The following error messages might appear in the SLES 10 SP2 64-bit OS dmesg:
Evaluate _OSC Set fails. Status = 0x0005 aer_init: AER service init fails - No ACPI_OSC support aer: probe of 0000:00:0a.0:pcie01 failed with error 1
This issue is being investigated.
The Linux operating system only reports 8 CPU cores out of the possible 16 CPU cores in the server module. This issue occurs because of a Linux kernel limitation.
Install and boot from the largesmp kernel version, which can be found in the installation media.
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
Run the post OS driver update using the sh install.sh command, or unmount and remount the Tools & Drivers DVD manually.
Installing SLES OS drivers might take a long time to complete if the host firewall is enabled. This issue occurs when running the install.sh script from the Tools & Drivers DVD.
Disable the host firewall before installing SLES OS drivers.
The Sun Blade RAID Expansion Module (REM) and Intel 82575 Gigabit Ethernet Controller network interface card (NIC) drivers on the Sun Blade X6440 server module Tools & Drivers DVD do not work with the SLES11 operating system.
This issue is being investigated.
SLES 9 SP4 hangs during installation or startup on systems with over 4 GB of RAM. SLES9 SP4 (kernel 2.6.5-7.308) installs correctly on a system with a quad-core AMD Opteron processor with over 4 GB of RAM; however, on the initial boot after installation, the system hangs.
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.
After using the above method to limit the memory while the system is installed, the kernel can be updated to provide the fixes so that the full amount of memory can be used.
Information about this kernel update and how to download it is available at http://support.novell.com/techcenter/psdb/436375e56cfcb119e5e42c29cf234297.html.
The RHEL 4.7 operating system does not recognize USB 2.0 devices. This causes the OS installations that use a USB DVD-ROM or ILOM remote KVMS device to fail. More details and a fix for this issue can be found at:
http://rhn.redhat.com/errata/RHBA-2008-0650.html
Either install RHEL 4.7 over a network or install the updated kernel fix from the Red Hat web site. Alternatively, you can remove the ehci-hcd.ko module from the kernel by typing the rmmod ehci_hcd command from the system prompt.
In systems equipped with certain fibre channel (FC) PEMs and using external FC storage to install the Windows operating system, a blue screen appears during phase 2 install of MS Windows 2008 R2 (64 bits), Windows 2008 (64 bits), or Windows 2003 R2 (64 bits), and some time after the first install reboot. Additionally, installation of Linux OSes (RHEL or SLES) will fail with certain FC PEMs in SW 2.1.0.
Please do not upgrade to software 2.1.0 if your system is to run with a Windows or Linux operating system and equipped with one of the following FC PEMs:
This will be fixed in Software Release 2.2.0.
Windows autorun does not install drivers. This occurs when Windows User Account Control is turned on.
1. Turn off Windows User Account Control.
2. Reboot the system for the changes to take effect.
3. Run Windows Autorun to install drivers.
A yellow question mark might appear in the Windows Device Manager, denoting that drivers are not installed for the following devices:
Run Windows Update to install the necessary drivers.
The system does not boot Windows from a floppy drive image installation. This occurs because the BIOS sets the virtual floppy as the first (top) USB bootable device.
1. During system boot, press F2 to enter the BIOS Setup Utility.
2. From the Boot/USB devices menu, change the device boot order to set the virtual CDROM as the first (top) USB bootable device.
Before the operating system can use hard disk drives attached to a StorageTek SAS controller, the drives must first be initialized and an array created using the StorageTek BIOS Setup Utility. The StorageTek BIOS Setup Utility can be accessed by pressing the CTRL + A keystroke combination during the server blade power on self-test (POST).
This section contains the following LSI RAID REM issues:
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.
The only upgrade path that supports data merging is from a single disk to a mirror. This is a limitation of the LSI card. If you want to upgrade from a single disk to an IME (Integrated Mirror Extension) or an IMS (Integrated Mirror Stripe), the data and OS will be lost and a reinstallation and restore will be required.
|
Copyright |
Copyright © 2010 Sun Microsystems, Inc., 4150 Network Circle, Santa Clara, California 95054, Etats-Unis. Tous droits réservés.
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.
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, OpenSolaris, Sun Blade, docs.sun.com, Sun Fire et le logo Solaris sont des marques de fabrique ou des marques déposée de Sun Microsystems, Inc., ou ses filiales, aux Etats-Unis et 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. 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.