Sun Blade X6250 Server Module
 

GCS>Sun Microsystems>Sun FAB>Standard>Reactive
 

Access to the X6250 server module ELOM webgui will fail.

Between 100 and 130 Sun Blade X6250 Server Modules were shipped pre-RR (Revenue Release) to the Americas and EMEA Regional Stocking Locations (RSLs) which contain down rev firmware/BIOS (4.0.27/BIOS 17).

When attempting to access the ELOM webgui from a web browser access fails.

The down rev firmware/BIOS is missing sslconfig files.  This was resolved at RR on June 22, 2007 when SW1.0 (4.0.30/BIOS 17) was made the minimum supported version for the X6250 Server Module.  All other server modules have been shipped with the SW1.0 level.

To resolve this issue the firmware/BIOS must be updated to the latest supported version SW1.2 (4.0.45/BIOS 28c). Follow the steps specified in the ELOM Admin Guide 820-1253-12 to update the firmware via CLI. The ELOM Admin Guide can be found via the below link;

http://dlc.sun.com/pdf/820-1253-12/820-1253-12.pdf

These steps are listed below:

Caution: Power interruptions during the update process could leave the SP in a unbootable or nonrecoverable state. Before upgrading your firmware, ensure that you have reliable power and protect against accidental power interruptions.

Caution: The file system would become corrupted if the host operating system is not shut down before the update process begins. If the OS is running when the update process starts, the SP will shut the host down ungracefully, which could cause file system corruption.

Note: The upgrade takes about 5 minutes to complete, depending on
network traffic. During this time, no other tasks can be
performed in the Embedded Lights Out Manager (ELOM) software.
1. Copy the combined bios/bmc image to your Tftp server.
2. If the server modules OS is running, perform a clean shutdown.
3. Log in to the CLI, and navigate to the TftpUpdate directory, enter:
-> cd /SP/TftpUpdate
Note: A network failure during the file upload will result in a timeout.
This causes the SP to reboot with the prior version of the firmware.
4. To set the IP address of the TFTP server, see the example provided:
-> set ServerIP=129.148.53.204
5. To set the file name of the combined bmc.bios image, enter the following
command:
-> set Filename=filename.rom
6. Next set the save flag to "no" so that settings are not preserved during
the update and all customized BIOS settings are cleared.  This is
required so that the missing files are replaced during the update.
Note: Before updating you should save configuration information so that
after the update you can configure the server module SP with the
same IP address, etc...
-> set SaveFlag=no
7. Start the tftp download:
-> set Update=action
Example:
-> cd /SP/TftpUpdate
-> set ServerIPAddress=129.148.53.204
-> set FileName=filename.rom
-> set SaveFlag=no
-> set Update=action
getting image...
getting image successfully.
prepare to update...
Prepare OK!
Update Successful
starting update...
Note: The new BIOS cannot be seen until the server blade is fully booted.
During boot BIOS may complain of a checksum error which is normal
when updating BIOS.  If the server stops booting and gives the user
the option to hit F1 to reset to default settings, or F2 to enter
setup mode.  The user should hit F1 and reset to defaults.

Identification of Affected Parts (how to):

To identify if you have a blade affected by this issue just login to the ELOM of the server module and issue the version command.

# ssh root@IPaddress
-> version

You will likely see this problem after replacing a server module for some other failure/problem.

 Note: Whenever you replace a server module you need to check the server

       module cover for any software license agreement labeling.  If there

       is license agreement data then you must keep the old server module

       cover so the customer retains the license information to access

       their software.

 

• Service Request: 37965419
• Manual: 820-1253-12
• URL: http://dlc.sun.com/pdf/820-1253-12/820-1253-12.pdf

This solution has no attachment