C H A P T E R  2

Flash Upgrading Your Server

This chapter contains procedures and information for upgrading Sun Blade X6220 server module to the current software release. See the following sections:


How to Flash Upgrade Your Server

This section shows a summary of the steps you should perform to update your server to the current software release.

1. Review Chapter 3 for known issues and considerations regarding the flash upgrade.

2. Determine the version of the firmware that you currently have.

See How to Determine The Firmware Version of Your Server.

Updating the BIOS and ILOM Firmware

1. Download the flash image .ima file by following links from the URL below:

http://www.sun.com/download/

a. Locate the Hardware Drivers section.

b. Click the X64 Servers and Workstations.

c. Click the link for the Sun Blade X6220 Server Module release that you want to upgrade to.

d. Click Download.

e. Enter your Username and Password.



Tip - If you do not have a Username and Password, you can register free of charge by clicking Register Now.


f. Click Accept License Agreement.

g. Click the on the appropriate file name:

SW 1.0.1:ilom.X6220-1.1.8.ima

SW 1.0.2: ilom.X6220-1.1.8-BIOS26.ima

SW 1.1a: ilom.X6220-2.0.3.1-r26140.ima

SW 1.2: ilom.X6220-2.0.3.2-r30997.ima

SW 2.0: ilom.X6220-2.0.3.3-r34514.ima

SW 2.1: ilom.X6220-2.0.3.10-r36968.ima

SW 3.0: ilom.X6220-3.0.3.34-r44801.ima

2. Perform the flash upgrade by using one of the following:



Tip - Because of the increased memory usage during web-based GUI operations, you might need to use N1 System Manager or the ILOM CLI load command to upgrade the ILOM firmware.


For details on firmware flashing, see the document appropriate to the method you are using:

http://docs.sun.com/app/docs/prod/n1.sysmgr#hic

http://docs.sun.com

For Example, from the ILOM CLI, use the following command:


load -source tftp://tftpserver/firmware.ima

Where tftpserver is a trivial file-transfer protocol (TFTP) server and firmware.ima is one of the following image files:

SW 1.0.1:ilom.X6220-1.1.8.ima

SW 1.0.2: ilom.X6220-1.1.8-BIOS26.ima

SW 1.1a: ilom.X6220-2.0.3.1-r26140.ima

SW 1.2: ilom.X6220-2.0.3.2-r30997.ima

SW 2.0: ilom.X6220-2.0.3.3-r34514.ima

SW 2.1: ilom.X6220-2.0.3.10-r36968.ima

SW 3.0: ilom.X6220-3.0.3.34-r44801.ima



caution icon Caution - To ensure a successful flash upgrade, do notattempt to modify the ILOM configuration, or use other ILOM GUI, CLI, SNMP, or IPMI interfaces during the flash upgrade process. Wait until after the flash upgrade succeeds to make further ILOM configuration changes. Note that the ILOM upgrade procedure might reset the service processor if it detects recent ILOM configuration changes, or multiple ILOM users or connections.


 

Note - A firmware upgrade causes the server and ILOM to reset. An upgrade takes about 20 minutes to complete. ILOM will enter a special mode to load new firmware. No other tasks can be performed in ILOM until the firmware upgrade is complete and the ILOM is reset.


3. (Optional) If you cannot get output to your serial console after the flash upgrade, you might have to clear CMOS settings. This is because your default CMOS settings might have been changed by the new BIOS upgrade.

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

Where SP-IP is the IP address of the service processor.

4. (Optional) If you have any problems with the flash upgrade, refer to the section Recovering From a Failed Flash Update.

Updating the LSI Firmware



caution icon Caution - During an update, never power off the system.


In order to update the LSI firmware, you must boot the system from a special CD or CD image. There are two ways you can do this:

Remote Console Method

1. Download the LSI firmware .iso file from the Sun Fire X64 servers web site to the remote system.

2. Using a web browser, connect to the ILOM and open the ILOM GUI.

https://sp_ip_address

Where sp_ip_address is the IP address of the service processor.

3. Select Remote Control -> Redirection.

4. Select 8-bit or 16-bit color.

5. Select Launch Redirection.

6. Respond to all prompts.

7. At the login prompt for the JavaRconsole window, type root, and then type the root password.

8. In the JavaRconsole window, select Devices.

9. Attach the LSI firmware update image .iso file.

a. Select the CD-ROM Image.

b. At the pop-up screen navigate to the ISO file you downloaded in Step 1 and click Open.

10. From the main SP ILOM GUI, select Remote Control -> Remote Power Control

11. Select Power -> Action -> Reset.

12. When the system reboots, select “1” (Perform the Update) from the JavaRconsole window.

The update proceeds. When complete, the console responds with a new prompt.

13. In the JavaRConsole window select Devices -> CDROM Image to detach the LSI firmware update .iso file.

14. Select JavaRConsole Keyboard -> Control Alt Delete.

15. On system boot, you will notice the new LSI firmware version.

Local Method

1. Download the LSI firmware .iso file from the Sun Fire X64 servers web site and burn it to a bootable CD.



Note - The bootable CD will appear blank when viewed using the operating system. This is expected behavior (CR6554839).


2. Attach a USB CD or DVD drive to the server module USB port.

3. Insert the bootable CD and reboot the server.

4. When the system reboots, select “1” to perform the update.

The firmware is upgraded.

5. Reboot the system and you will see that the LSI firmware version has been updated.

More on Updating the LSI Firmware

For information about the LSI firmware and BIOS, see the documentation files that accompany the LSI download. For LSI firmware versions included in this release, see Software Release Firmware Versions.


How to Determine The Firmware Version of Your Server

This section provides three methods of determining your firmware version build number:

Determining the Firmware Version Using the CLI Through the Management Ethernet Port

See the Integrated Lights Out Manager 3.0 User’s Guide for more detailed information on this procedure.

1. Connect an RJ-45 Ethernet cable to the NET MGT Ethernet port on the chassis CMM.

2. Establish an SSH connection using the following command:


# ssh -l root SP-IP

Where SP-IP is the IP address of the server module service processor.

3. Enter the default password when you are prompted:

changeme

After you have successfully logged in, the SP displays its default command prompt:

->

4. Type the version command, which will return output similar to the following:


-> version
SP firmware version: 1.x.x
SP firmware build number: 18640
SP firmware date: Tue Sep 13 12:50:37 PDT 2006
SP filesystem version: 0.1.13

The ILOM firmware is the build number listed above.

Determining the Firmware Version Using the CLI Through the Serial Port

1. Configure your terminal device or the terminal emulation software running on a laptop or PC to the following settings:

2. Connect a dongle cable to the server module.

3. Connect a serial cable from the RJ-45 SER MGT port on the server module dongle to your terminal device or PC.

4. Press Enter on the terminal device to establish a connection between that terminal device and the server’s SP.

The SP displays a login prompt.

SUNSP0003BA84D777 login:

In this example login prompt, 0003BA84D777 is the Ethernet MAC address of the SP. This will be different for each server.

5. Log in to the ILOM SP and type the default user name (root) with the default password (changeme).

After you have successfully logged in, the SP displays its default command prompt:

->

6. Type the version command, which will return output similar to the following:


-> version
SP firmware version: 1.x.x
SP firmware build number: 18640
SP firmware date: Tue Sep 13 12:50:37 PDT 2006
SP filesystem version: 0.1.13

The ILOM firmware build version is the build number listed above.

Determining the Firmware Version Using the Web Interface

1. Connect to the ILOM web GUI by typing the IP address of the server’s SP into your browser’s URL field. For example:

https://129.146.53.150

2. Log in to the ILOM SP and type the default user name (root) with the default password (changeme).

The first web page that is presented is the System Information -> Versions page, which includes the Build Number.

Locating ILOM Service Processor Addresses

Use one of the three methods listed here to locate the ILOM SP and IP address:

 

How to Reset the SP

To reset the ILOM SP, you can do any of the following:

Where SP-IP is the IP address of the service processor.

For complete details, see the Integrated Lights Out Manager 2.0 User’s Guide.


Recovering From a Failed Flash Update

This section contains instructions for recovering from a failed Sun Blade X6220 ILOM firmware upgrade. Several issues have been identified with the firmware upgrade, which could result in a failed or incomplete firmware upgrade.

Use the following procedure to recover from a failed firmware upgrade. Note that in a small percentage of cases (such as when no output is displayed on the SP serial port), the Graphics Redirect and Service Processor (GRASP) board must be replaced.



caution icon Caution - The last ILOM firmware released for Sun Blade X6220 server module must be used to recover from a failed flash update.


Prerequisites:


Note - Numbers printed below are in hexidecimal unless otherwise noted.


Recovery Steps:

1. Determine if the ILOM SP first-level booter (referred to in this procedure as U-Boot) is intact. Follow documented procedures to connect to the SP serial port, apply power to the system, and observe the initial ILOM boot messages.

See the Sun Blade X6220 Server Module Installation Guide for details.

2. Enter the ILOM SP U-Boot command interpreter with xyzzy.

When the message, Booting linux in 2 seconds... is displayed, during ILOM initial boot, type xyzzy to enter the U-Boot command interpreter.



Note - The characters typed will not echo. Cutting and pasting the characters improves the chance of success. You might try cycling power to the system and entering xyzzy several times.


3. Set the phy speed as follows:

a. Type the following command to confirm the phy number:

mii info

b. Now set the speed to 100 mbit, using the phy number in the following command:

mii write phy number 0 2000

For example:

mii write 4 0 2000

4. Disable automatic reboot.

Set the U-Boot environment variable, bootretry, to -1 to temporarily disable automatic reboot:


set bootretry -1

5. Configure the network for TFTP access.

a. Copy the ILOM SP firmware image to a TFTP server that is accessible on the same IP subnet as the ILOM SP network port.

b. Set the network variables using the dhcp command or set the static IP address for the ILOM SP, TFTP server, gateway, and netmask as shown in the following example:


set ipaddr n.n.n.n
set serverip n.n.n.n
set gatewayip n.n.n.n
set netmask n.n.n.n 

6. Use the U-Boot tftp command to download the ILOM firmware image.

tftp 100000 firmware.ima

Where firmware.ima is the name of the image file, such as, ILOM.X6220-1.1.x.ima.



Note - If the TFTP server or filename is incorrect, you might need to enter Control-C to halt the tftp command, then repeat this recovery procedure.


You should see a message similar to:


=> tftp 100000 ilom.XX6220-x.x.x.ima 
Using FCC1 ETHERNET device
TFTP from server 10.6.154.8; our IP address is 10.6.154.99
Filename ’ilom.X6220-x.x.x.ima’.
Load address: 0x100000
Loading:
###########################################################
###########################################################
###########################################################
###########################################################
##########################
done
Bytes transferred = 13107200 (e00000 hex)

7. Confirm that the download succeeded:

a. Confirm that the tftp command output ends with:


Bytes transferred = ByteCount

b. Check the ByteCount number against the file size.

c. Use the md command and confirm that its output displays strings from the beginning of the firmware image file. For example:


=> md 100000
00100000: 244d4f44 554c4524 01004000 00000200    $MODULE$..@.....
00100010: 00000000 000000f2 67726173 70000000    ........grasp...
00100020: 01000200 40000000 61000000 0000ffff    ....@...a.......
00100030: ffff0000 00000100 00000000 0000aa55    ...............U
00100040: 46575f56 45525349 4f4e3d31 2e302e31 FW_VERSION=1.0.1
00100050: 0a46575f 44415445 3d4d6172 20203320 .FW_DATE=Mar  3
00100060: 32303036 0a46575f 4255494c 4454494d    2006.FW_BUILDTIM
00100070: 453d3130 3a35363a 30370a46 575f4445    E=10:56:07.FW_DE
00100080: 53433d57 41524e49 4e47203a 20554e4f    SC=WARNING : UNO
00100090: 46464943 49414c20 4255494c 44212120    FFICIAL BUILD!!
001000a0: 0affffff ffffffff ffffffff ffffffff    ................

8. Erase the existing ILOM flash image:



caution icon Caution - Interrupting the flash recovery process from this point onwards, or entering an incorrect U-Boot command, might result in a disabled service processor, which will require replacement. DO NOT stop or remove power from the system from this point onward.


a. Erase the exiting flash image with the erase fe020000 ffffffff command.

A series of dots will be displayed indicating the progress of the erase. For example:


=> erase fe020000 ffffffff
.................................................................................Erased 200/200 sectors

b. If you see the error message: Step Warning: protected sectors will not be erased! remove the protection first with the following commands:


protect off fe020000 ffffffff
erase fe020000 ffffffff



Note - If a persistent failure occurs, the service processor is not flash-upgradable, and must be replaced. Refer to the Sun Blade X6220 Server Module Service Manual for details on replacing the SP board.


9. Use the U-Boot cp.b command to copy the new ILOM firmware image as follows:


cp.b 10000 StartAddress ByteCount

The .ima file needs to be loaded so that it fits right up against the highest available memory address. You need to start copying the image to flash at different addresses, depending on the size of the .ima file.

To correctly position the image, compute the image StartAddress as follows:

0xffffffff - image size + 1

See the following examples of the StartAddress calculation:

11M image (11534336 bytes): 0xffffffff - 11534336 + 1 = 0xff500000

12.5M image (13107200 bytes): 0xff380000.

14M image (14680064, or 0xe00000 bytes): 0xff200000

The ByteCount should match the output of the tftp command, which should be just the hex representation of the .ima file size. It must be a hex value though, since U-Boot doesn’t understand decimal numbers.

For example:


=> cp.b 100000 ff380000 c80000
Copy to Flash .............................................................................................................................................done

c. Use the fmh command to verify the new ILOM firmware image.

Before resetting, make sure the copy succeeded, using the fmh command, which should display firmware sections. For example

 

 


=> fmh
Listing FMH Modules
Flash Size : 32768 KB
Erase Size : 128 KB
Sector Count : 256
FMH Located at 0xff200000 of Size 0x00020000
Name    : grasp
Ver     : 1.1
Type    : 0x0002
Flags   : 0x0000
Size    : 0x000001ad
Location: 0xff200040
LoadAddr: 0xffffffff
CheckSum: Not Computed
--------------------------------------------------
FMH Located at 0xff220000 of Size 0x00120000
Name    : sysbios
Ver     : 1.25
Type    : 0x0000
Flags   : 0x0100
Size    : 0x00100000
Location: 0xff240000
LoadAddr: 0xffffffff
CheckSum: Valid
--------------------------------------------------
FMH Located at 0xff340000 of Size 0x00020000
Name    : bob-strm
Ver     : 1.0
Type    : 0x0000
Flags   : 0x0101
Size    : 0x0000c0eb
Location: 0xff340040
LoadAddr: 0xffffffff
CheckSum: Valid
--------------------------------------------------
FMH Located at 0xff360000 of Size 0x000c0000
Name    : osimage
Ver     : 1.0
Type    : 0x0006
Flags   : 0x0119
Size    : 0x000aaf27
Location: 0xff360040
LoadAddr: 0x00c00000
CheckSum: Valid
--------------------------------------------------


FMH Located at 0xff420000 of Size 0x00800000
Name    : root
Ver     : 1.0
Type    : 0x0007
Flags   : 0x0101
Size    : 0x007c5040
Location: 0xff440000
LoadAddr: 0xffffffff
CheckSum: Valid
--------------------------------------------------
 
FMH Located at 0xffc20000 of Size 0x00160000
Name    : www
Ver     : 1.0
Type    : 0x0007
Flags   : 0x0101
Size    : 0x00121000
Location: 0xffc40000
LoadAddr: 0xffffffff
CheckSum: Valid
--------------------------------------------------
 
FMH Located at 0xffd80000 of Size 0x00140000
Name    : params
Ver     : 1.0
Type    : 0x0011
Flags   : 0x0001
Size    : 0x00120000
Location: 0xffda0000
LoadAddr: 0xffffffff
CheckSum: Not Computed
--------------------------------------------------
 
FMH Located at 0xffee0000 of Size 0x00060000
Name    : boot
Ver     : 1.0
Type    : 0x0001
Flags   : 0x0000
Size    : 0x0003cb6c
Location: 0xfff00000
LoadAddr: 0xffffffff
CheckSum: Not Computed
-------------------------------------------------- 

 



Note - If the fmh command doesn’t show anything, you may have entered an incorrect memory address somewhere. Start again from step 5. Do not reset the SP in this state.


10. Reset the ILOM service processor.

Once you are certain that the service processor firmware image has been recovered, you can restart the service processor with the reset command.


=> reset

The SP should boot correctly.



Note - The sunservice account is not supported in ILOM 3.0. Contact your sunservice representative if you want to enable your sunservice account in ILOM 3.0.


11. When the SP has booted all the way to the linux login prompt, log in with the following

Remember, you will have lost all configuration data after performing the flash update.

12. Restore the /coredump partition with this command:


/usr/local/bin/format_coredump

The format_coredump program might be named something like: format_coredump.galaxy.2M, but there is only one such program in /usr/local/bin. Enter ls /usr/local/bin to see a list of programs and run whichever one is there.

13. Recover the system BIOS.



Note - This manual ILOM SP recovery process does not reflash the system BIOS. Repeat the firmware upgrade process, using the ILOM GUI or CLI procedures as described in How to Flash Upgrade Your Server and the Integrated Lights-Out Manager 2.0 User’s Guide.


14. Reset your service processor and BIOS configuration settings as needed, because they might be lost during this recovery.