| Sun Blade X6220 Server Module Release Notes for Software Releases 1.x, 2.x and 3.x |     |
| C H A P T E R 3 |
|
Special Considerations for Specific Firmware Releases |
This chapter describes issues that might affect the firmware upgrade. See the following sections for special considerations for the following ILOM releases:
This section describes considerations that might affect the firmware upgrade. See the Sun Integrated Lights Out Manager 3.0 User’s Guide. For general issues on ILOM and issues that have been fixed with this release of the firmware, see the Sun Blade X6220 Server Module Product Notes.
Due to an error in the 2.0.3.10 code, the KCS channel does not work when upgrading from 2.0.3.10 to 3.0.3.34.
Do not use the KCS channel when upgrading from release 2.0.3.10 to 3.0.3.34.
This section describes considerations that might affect the firmware upgrade. See the Sun Integrated Lights Out Manager 2.0 User’s Guide. For general issues on ILOM and issues that have been fixed with this release of the firmware, see the Sun Blade X6220 Server Module Product Notes.
The Sun Blade 6000 CMM and Sun Blade 6048 CMM (Chassis Management Module) and X6220 server module service processors must all be upgraded to the latest ILOM 2.0.3.2 release.
Please upgrade the Sun Blade X6220 server modules, then the Sun Blade 6000 and Sun Blade 6048 CMM, to ILOM 2.0.3.2, using ILOM CLI, GUI, or IPMI interfaces.
This section describes considerations that might affect the firmware upgrade. See the Sun Integrated Lights Out Manager 2.0 User’s Guide. For general issues on ILOM and issues that have been fixed with this release of the firmware, see the Sun Blade X6220 Server Module Product Notes.
Software 1.1 for the Sun Blade X6220 server module contains a build of ILOM 2.0.3.1 with a serious bug. Upgrading to this ILOM version causes some FRU data to be lost. Because of this, Software 1.1 has been withdrawn and replaced by Software 1.1a.
If you have not yet upgraded to the ILOM provided with Software 1.1, this issue does not affect you. Simply discard any copies of Software 1.1 and obtain Software 1.1a which contains ILOM firmware with the fix.
If you have upgraded to the ILOM provided with Software 1.1, you must install the ILOM firmware provided with software 1.1a. Doing so will both remove the bug and recover some of the FRU data that was previously not viewable. The remaining FRU data must be re-entered manually.
You can identify your ILOM firmware using the ILOM CLI or WebGUI:
In the information you obtain, find the “Firmware Version” (just “Firmware” in the CLI) and “Firmware Build Number”. Depending on the values you obtain, you should take one of the following actions:
The ILOM bug causes the following FRU data to be lost:
You can recover the Product Part Number and Product Serial Number by installing the ILOM firmware provided with Software 1.1a. If you downgraded the ILOM after observing the problem, Product Part Number and Product Serial Number must be re-entered manually.
The Chassis Serial Number will not be recovered with the Software 1.1a update and must be re-entered in any case.
Follow these steps to re-enter the lost FRU data:
1. Use SSH to log in to the “sunservice” ILOM account. From the Solaris or Linux command line:
where ipaddress is the Service Processor IP address.
2. Enter one of the following commands.
servicetool --fru_chassis_serial_number
servicetool --fru_product_part_number --fru_product_serial_number --fru_chassis_serial_number
3. Enter the FRU ID numbers when prompted.
Note the following considerations before upgrading your server module to ILOM 2.0.3.1 firmware:
This section describes considerations that might affect the firmware upgrade. For general issues on ILOM and issues that have been fixed with this release of the firmware, see the Sun Blade X6220 Server Module Product Notes.
Refer also, to the Integrated Lights Out Manager Administration Guide for ILOM 1.1.1, and Integrated Lights Out Manager (ILOM) Supplement for Sun Blade X6220 Server Module.
The host CPU and DIMM FRU information shown by the service processor is provided to the service processor during each BIOS power-on-self-test (POST). Therefore, after a BIOS/ILOM upgrade, this FRU information is empty until the first host BIOS POST.
This is expected behavior. Reboot the server and allow it to complete POST during bootup to repopulate the FRU lists.
After updating the system BIOS, you might need to clear CMOS settings to get serial console output from the host. This is because CMOS defaults might be changed from your existing settings in the new BIOS.
If you cannot get serial console output, clear the CMOS settings. To clear CMOS settings, use the following commands (in this example, the default username, root, and the default password, changeme, are used):
ipmitool -U root -P changeme -H SP-IP chassis power off ipmitool -U root -P changeme -H SP-IP chassis bootdev disk clear-cmos=yes |
ILOM service processor might not successfully update the BIOS version, if a previous flash upgrade has failed. If the BIOS version is not correct after ILOM flash upgrade completes, use the -f force flag on the ILOM CLI load command, to force BIOS flash upgrade.
Sometimes after flashing an image on SP, the ILOM GUI will not allow you to log in and gives an Authentication fail error. Clearing the cache and cookies of the web browser enables you to log in as usual.
ILOM 1.1.x releases provide limited support for non-UN keyboards. Keys above the normal US keyboard range are transmitted to the server.
However, key remapping between US and non-US keyboards is not automatically performed, and there are keys which do not function, which results in limitations in internalization support in Java Web Start.
Use the key and character remapping capabilities of the installed server OS to work around this issue.
| Sun Blade X6220 Server Module Release Notes for Software Releases 1.x, 2.x and 3.x | 820-2507-17 | |
Copyright © 2009 Sun Microsystems, Inc. All rights reserved.
