C H A P T E R 2 |
Software 1.3a Update Procedures |
This chapter describes how to update your server to Software Release 1.3a . See the following sections:
The Integrated Lights Out Manager (ILOM) firmware and BIOS are tightly coupled and are always updated together. The LSI firmware is usually updated at the same time as the BIOS and ILOM; LSI firmware can be updated before or after the BIOS and ILOM firmware.
There are two major steps to updating your server firmware:
Note - The LSI firmware version and the BIOS version must be from the same software release. |
1. Determine the current version of the ILOM firmware. See Verifying the Firmware Version.
2. Review the section Software Release Special Considerations for known issues and considerations regarding the flash update.
3. Download the latest flash image from the following location:
http://www.sun.com/servers/entry/x4100/downloads.jsp
4. Use the ILOM GUI, the ILOM CLI load command, or N1 System Manager to perform the firmware update.
From the ILOM CLI, use the following command:
load -source tftp://tftpserver/ilom.firmware.ima
where tftpserver is the server that contains the update and ilom.firmware.ima is the image file,. For example: ilom.x4100.1.1.1-r15632.ima.
Online documentation for Sun N1 System Manager can be found at:
http://docs.sun.com/coll/1283.2
For more details on performing the update, see Updating the LSI Firmware.
5. If you have any problems with the flash update, refer to the sectionRecovering from a Failed Flash Update.
![]() |
Caution - During an update, never power off the system. |
1. Connect to the ILOM and open the ILOM GUI.
where sp_ip_address is the IP address of the service processor.
2. Select Remote Control -> Redirection.
3. Select 8-bit or 16-bit color.
6. At the login prompt for the JavaRconsole window, type root, and then type the root password.
7. In the JavaRconsole window, select Devices.
8. Attach to the LSI firmware update image .iso file. At the pop-up screen, select the CD-ROM Image.
A check mark is displayed on the drop-down menu selection.
9. Select Remote Control -> Remote Power Control in the ILOM GUI.
10. Select Power -> Action -> Reset.
11. 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.
12. In the JavaRConsole window select Devices -> CDROM Image to detach the LSI firmware update .iso file.
13. Select JavaRConsole Keyboard -> Control Alt Delete.
14. On system boot up, you will notice the new LSI firmware version.
1. Download the LSI firmware .iso file from the Sun Fire X64 servers website and burn it to a bootable CD.
Note - The bootable CD will appear blank when viewed using the operating system, but that is expected behavior (CR6554839). |
2. Insert the bootable CD and reboot the server.
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 Component Versions By Release.
There are three alternate procedures in this section that you can use:
1. Connect an RJ-45 Ethernet cable to the NET MGT Ethernet port on the back panel.
2. Establish an SSH connection using the following command, then enter the default password (changeme) when you are prompted:
After you have successfully logged in, the SP displays its default command prompt:
3. Type the version command, which returns output similar to the following:
SP firmware build number: 10644
SP firmware date: Tue Sep 13 12:50:37 PDT 2006
The ILOM firmware build is listed above.
1. Configure your terminal device or the terminal emulation software running on a laptop or PC to the following settings:
2. Connect a serial cable from the RJ-45 SER MGT port on your server’s back panel to your terminal device or PC.
3. 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.
In this example login prompt, 0003BA84D777 is the Ethernet MAC address of the SP. This will be different for each server.
4. 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:
5. Type the version command, which returns output similar to the following:
SP firmware build number: 10644
SP firmware date: Tue Sep 13 12:50:37 PDT 2006
The ILOM firmware build version is the build number listed above.
1. Connect to the ILOM Web GUI by typing the IP address of the server’s SP into your browser’s address field. For example:
2. Log in to the ILOM SP and type the default user name (root) with the default password (changeme).
The first Web page presented is the System Information -> Versions page, which includes the Build Number.
There are several methods you can use to locate ILOM SPs and their IP addresses.
For example, the following command can be used to create a list of Sun Fire X4100/X4200 servers:
n1sh show server | grep 'X4[12]00'
ipmitool -U root -P password -H sp_ip_address bmc reset cold
For more on this topic, refer to the the ILOM User’s Guide for your ILOM version.
Several issues have been identified with the firmware update, which could result in a failed or incomplete firmware update. This section describes how to recover from a failed ILOM firmware update.
Use the following procedure to recover from a failed firmware update. 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.
Note - Numbers printed below are in hexadecimal unless otherwise noted. |
|
1. Determine whether 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.
Refer to the Sun Fire X4100/X4100 M2 and X4200/X4200 M2 Servers Installation Guide, 819-1155, 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.
Set the U-Boot environment variable, bootretry, to -1 to temporarily disable automatic reboot:
4. 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 IP address for the ILOM SP and the TFTP server IP address by setting the ethaddr and serverip U-Boot variables.
set ipaddr n.n.n.n
set serverip n.n.n.n
5. Use the U-Boot tftp command to download the ILOM firmware image.
where ilom.firmware.ima is the image file, for example, ilom.x4100.1.1.1-r15632.ima.
Note - If the TFTP server or filename is incorrect, you might need to enter ^C to halt the tftp command, then repeat this recovery procedure. |
Be sure that the complete flash image is actually downloaded successfully before proceeding. You should see a message similar to:
Using FCC1 ETHERNET device
TFTP from server 10.6.154.8; our IP address is 10.6.154.99
Filename ’r10644.rom.ima’.
Load address: 0x100000
Loading:
###########################################################
###########################################################
###########################################################
###########################################################
Bytes transferred = 13107200 (c80000 hex)
6. Confirm that the download succeeded:
a. Confirm that the tftp command output ends with
Bytes transferred = ByteCount
b. Use the md command and confirm that its output displays strings from the beginning of the firmware image file. For example:
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 ................
7. Erase the existing ILOM flash image:
a. Erase the exiting flash image using the following commands:
erase ff380000 ffffffff erase 0xfe200000 0xff37ffff
You will a series of dots showing progress, followed by a confirmation:
.................................................................................Erased 200/200 sectors
b. If a failure occurs, retry the erase command repeatedly until it succeeds.
8. Program the new ILOM firmware image:
a. Use the U-Boot cp.b command to copy the new ILOM firmware image from the download location at 100000 to ff380000, until end address ffffffff.
=> cp.b 100000 ff380000 ffffffff
Copy to Flash .............................................................................................................................................done
b. 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 Located at 0xff380000 of Size 0x00020000
--------------------------------------------------
FMH Located at 0xff3a0000 of Size 0x00120000
--------------------------------------------------
FMH Located at 0xff4c0000 of Size 0x000c0000
9. 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.
Note - This manual ILOM SP recovery process does not reflash the system BIOS. Repeat the firmware update process, using the ILOM GUI or CLI procedures as described in Updating Your Server Firmware and the refer to the Integrated Lights Out Manager (ILOM) Administration Guide for ILOM. |
Be sure to reset your service processor and BIOS configuration settings as needed, because they might be lost during this recovery.
Copyright © 2007, Sun Microsystems, Inc. All Rights Reserved.