| Sun Fire V20z and Sun Fire V40z Servers--SP and BIOS Update ReadMe |     |
| Sun Fire V20z and Sun Fire V40z Servers--SP and BIOS Update ReadMe | |
|
Updating the BIOS and SP Firmware |
This document contains instructions on how to update the BIOS and SP firmware in the Sun Fire
V20z and Sun Fire V40z servers.
For additional information, refer to the Sun Fire V20z and Sun Fire V40z Servers--User Guide (817-5248-12). For a description of new features and known issues, refer to the Sun Fire V20z and Sun Fire V40z Servers--Release Notes (817-5252-16).
To update the BIOS and SP firmware, you must perform these steps:
1. Check the system inventory to verify your current version of the BIOS and SP firmware components.
3. Share the NSV files with the appropriate permissions.
4. From a Solaris software-based or Linux software-based client:
6. Perform housecleaning tasks.
1. Ensure that you do not have a firewall or VPN client enabled on your local machine. These applications block file sharing, and prevent the SP from mounting the share and accessing the NSV files.
2. Check that Java runtime environment version 1.4.2 or higher is installed on your local machine. If necessary, you can download the most recent version from http://www.java.com.
3. Ensure that you have an SSH client properly installed on your local machine.
The SP needs to be running; however, the platform side of the Sun Fire V20z or Sun Fire V40z server must be powered off.
Plug in the AC power cord on the back of the chassis and turn on the AC power switch on the back panel. The front LCD display must be lit (SP is on) but the green power LED must be off (platform is off).
Plug in the AC power cords to the power supplies on the back of the chassis. The front LCD display must be lit (SP is on) but the green power LED must be off (platform is off).
As the SP boots and comes up, its network settings now need to be configured.
If you do not press the button before the system times out, the system automatically looks for a DHCP server.
For more information, refer to the Sun Fire V20z and Sun Fire V40z Servers--Installation Guide (817-5246).
|
Note - If the SP is already configured with a login name and password, but you do not have the login information, you will need to reset the SP.
|
1. Press any of the three operator-panel buttons next to the front-panel LCD screen.
The LCD displays the option Server Menu.
2. Press the Forward (right) button until the option "SP menu" is displayed.
3. Press the Select (center) button to confirm.
4. Press the Forward button until the option "Use Defaults" is displayed.
5. Press the Select button twice to confirm.
The SP resets itself to the factory settings and reboots.
Ensure that the local client used to perform the update is connected to the management network (the same local area network [LAN] as one of the SP 10/100 Ethernet management ports).
If you are not sure, try to ping the SP IP address from your local client. If the command is successful, your local client is on the same LAN as the SP port.
To configure the manager user and password:
1. Connect to the SP with the ssh client using the IP address that appears on the LCD display on the front panel.
2. Log in with user name setup and no password.
3. When prompted, create the first manager-level user. For example, username sun and password sun.
The SP is now set up and ready to be used to perform the server update.
Ensure that you record the current SP settings and firmware revisions.
The following steps explain how to verify the version of the BIOS and firmware currently installed on the server.
2. Using ssh, connect to the SP IP address that appears on the LCD display on the front panel.
3. Log in with your SP user name and password.
|
Note - If you have not yet set up an account on the SP or if you have forgotten your login information, refer to Resetting the Service Processor. |
The command should return something similar to the following:
Ensure that your local Solaris machine is connected to the same local area network (LAN) as one of the SP ports.
Open a new terminal window on your local Solaris machine.
This directory will serve as the central repository from which your Sun Fire V20z and Sun Fire V40z servers will download the new firmware during the update process.
On your local Solaris machine, create one of the following directories, depending on your type of server:
You will download the update files to the directory that you create.
1. Download the NSV update files to the directory that you created. The files for both types of server can be found at the following URL:
http://www.sun.com/servers/entry/v20z/downloads.html
2. Under the section "Firmware and Utilities (NSV)," click on "Current Release."
3. Download the following NSV release-package files:
Download the following files into the directory /export/home/v20z on your local Solaris machine.
Where x.x.x.x is the NSV version number, and y.y.y.y is the BIOS update number related to the NSV number.
Download the following files into the directory /export/home/v40z on your local Solaris machine.
Where x.x.x.x is the NSV version number, and y.y.y.y is the BIOS update number related to the NSV number.
Unzip the NSV release-package files into the directory you created on your local Solaris machine.
Use the following command format:
If the unzipping process creates new zip archive files, unzip these new files as well.
1. At the shell prompt, enter one of the following commands, depending on your type of server:
share -F nfs -o ro /export/home/v20z
share -F nfs -o ro /export/home/v40z
2. Enter the following command:
3. Obtain the IP address by which your local Solaris machine connects to the network.
4. Enter the following command:
Where <SP_username> is your user name for logging in to the SP and <SP_IP> represents the SP IP address that is displayed on the front-panel LCD display of the Sun Fire V20z or Sun Fire V40z server.
5. At the ssh prompt, enter one of the following commands:
sp add mount -r <solaris-ip-address>:/export/home/v20z -l /mnt
sp add mount -r <solaris-ip-address>:/export/home/v40z -l /mnt
6. At the ssh prompt, enter the following command:
The directory /export/home/v20z or /export/home/v40z should now be mounted.
1. To verify the power state of the platform side of the server, enter the following command:
|
Note - If the platform is powered on, the green LED below the floppy diskette drive is illuminated. |
2. If the result returned is ON, then power off the platform side with the following command:
platform set power state off -f
Ensure that Java runtime environment (JRE) 1.4 or higher is installed on your local Solaris machine. If your version of JRE is lower than 1.4, this update procedure will not work.
From a terminal window, type the following command:
If Java is properly installed, you will see a result similar to the following:
java version "1.4.2_06"
Java(TM) 2 Runtime Environment, Standard Edition (build 1.4.2_06-b03)
Java HotSpot(TM) Client VM (build 1.4.2_06-b03, mixed mode)
Enter one of the following commands on one continuous line in a terminal window on your local Solaris machine:
java -jar /export/home/v20z/update_server/Vx.x.x.x/updateServer.jar -f /export/home/v20z/sw_images/sp/spbase/Vy.y.y.y/install.image -p 50000
Where x.x.x.x is the version number of the Update Server application, and y.y.y.y is the version number of the SP firmware.
java -jar /export/home/v40z/update_server/Vx.x.x.x/updateServer.jar -f /export/home/v40z/sw_images/sp/spbase/Vy.y.y.y/install.image -p 50000
Where x.x.x.x is the version number of the Update Server application, and y.y.y.y is the version number of the SP firmware.
The following message appears in the terminal window:
The SP update process will take several minutes to complete during which the SP will be rebooted. You may now execute the "sp update flash all" command on the SP to start the update...
Return to the terminal window with the SSH connection to the SP.
Launch the update process with the following command:
sp update flash all -i <ip_address_solaris_machine> -p 50000
The SP executes the command and reboots itself. The reboot process takes a few minutes.
The SSH session automatically terminates.
In the terminal window running the Java utility, the following messages appear as the SP reboots and updates itself:
$ java -jar ./s update_server/V2.2.0.6/updateServer.jar -f
./sw_images/sp/spbase/V2.4.0.10/install.image -p 50000
[Fri Jun 09 10:45:38 PDT 2006] Update server is ready; port 50000
[Fri Jun 09 10:46:12 PDT 2006] [/10.4.145.238] [SP_BASE LATEST] Update
started
[Fri Jun 09 10:50:42 PDT 2006] [/10.4.145.238] [SP_BASE LATEST] Update
complete: ./sw_images/sp/spbase/V2.4.0.10/install.image
When the message "(7) SP flash update complete" appears, unless you need to update more servers, you can close the Java SP Update utility.
Ensure that the platform is powered off before you update the BIOS.
1. To verify the power state of the platform side of the server, enter the following command:
|
Note - If the platform is powered on, the green LED below the floppy diskette drive is illuminated. |
2. If the result returned is ON, power off the platform side with the following command:
platform set power state off -f
3. At the SP prompt, enter one of the following commands, depending on your type of server:
platform set os state update-bios /mnt/sw_images/platform/firmware/bios/Vx.x.x.x/bios.sp
Where x.x.x.x is the BIOS version number.
platform set os state update-bios /mnt/sw_images/platform/firmware/bios/Vx.x.x.x/bios.sp
Where x.x.x.x is the BIOS version number.
This update process might take several minutes before any output is returned. The output in your terminal window should look similar to the following:
This command may take several minutes. Please be patient.
Bios started
Bios Flash Transmit Started
Bios Flash Transmit Complete
Bios Flash update Progress: 7
Bios Flash update Progress: 6
Bios Flash update Progress: 5
Bios Flash update Progress: 4
Bios Flash update Progress: 3
Bios Flash update Progress: 2
Bios Flash update Progress: 1
Bios Flash update complete
4. When the BIOS update is completed, the server automatically powers off.
When the server powers on, if the BIOS and SP firmware update operations were successful, a BIOS message is displayed on the console.
For the beginning section of this message, see Console Output After Successful Update on a Sun Fire V20z Server or Console Output After Successful Update on a Sun Fire V40z Server.
The update procedure is now complete. Please note:
To unmount the directory that you mounted previously:
1. Open a terminal window and connect to the SP through ssh.
2. From the SP, enter the following command to unmount the directory:
3. To verify that the directory has been unmounted, enter the following command:
You should not see the directory /export/home/v20z or /export/home/v40z (depending on your type of server).
At the shell prompt, enter one of the following commands, depending on your type of server:
Ensure that your local Linux machine is connected to the same local area network (LAN) as one of the SP ports.
Open a new terminal window on your local Linux machine.
This directory will serve as the central repository from which your Sun Fire V20z and Sun Fire V40z servers will download the new firmware during the update process.
On your local Linux machine, create one of the following directories, depending on your type of server:
You will download the update files to the directory that you create.
1. Download the NSV update files to the directory that you created. The files for both types of server can be found at the following URL:
http://www.sun.com/servers/entry/v20z/downloads.html
2. Under the section "Firmware and Utilities (NSV)," click on "Current Release."
3. Download the NSV release-package files:
Download the following files into the directory /export/home/v20z on your local Linux machine.
Where x.x.x.x is the NSV version number, and y.y.y.y is the BIOS update number related to the NSV number.
Download the following files into the directory /export/home/v40z on your local Linux machine.
Where x.x.x.x is the NSV version number, and y.y.y.y is the BIOS update number related to the NSV number.
Unzip the NSV release-package files into the directory you created on your local Linux machine.
Use the following command format:
If the unzipping process creates new zip archive files, unzip these new files as well.
1. Move to the directory /etc:
2. Open the file /etc/exports using your preferred text editor.
3. Add one of the following lines, depending on your type of server, to the exports file:
/export/home/v20z *(rw,no_root_squash)
/export/home/v40z *(rw,no_root_squash)
4. Move to the directory /etc/init.d.
5. Restart the NFS service using one of the following methods, depending on what type of Linux you are using:
/etc/init.d/nfsserver stop
/etc/init.d/nfsserver start
b. Use the command below to verify that /export/home/v20z or /export/home/v40z is listed:
/etc/init.d/nfs stop
/etc/init.d/nfs start
b. Use the command below to verify that /export/home/v20z or /export/home/v40z is listed:
6. Enter the following command:
7. Obtain the IP address by which your local Linux machine connects to the network.
8. Enter the following command:
where <SP_username> is your user name for logging in to the SP and <SP_IP> represents the SP IP address that is displayed on the front-panel LCD display of the Sun Fire V20z or Sun Fire V40z server.
9. At the ssh prompt, enter one of the following commands:
sp add mount -r <linux-ip-address>:/export/home/v20z -l /mnt
sp add mount -r <linux-ip-address>:/export/home/v40z -l /mnt
10. At the ssh prompt, enter the following command:
The directory /export/home/v20z or /export/home/v40z should now be mounted.
1. To verify the power state of the platform side of the server, enter the following command:
|
Note - If the platform is powered on, the green LED below the floppy diskette drive is illuminated. |
2. If the result returned is ON, then power off the platform side with the following command:
platform set power state off -f
Ensure that Java runtime environment (JRE) 1.4 or higher is installed on your local Linux machine. If your version of JRE is lower than 1.4, this update procedure will not work.
From a terminal window, type the following command:
If Java is properly installed, you will see a result similar to the following:
java version "1.4.2_06"
Java(TM) 2 Runtime Environment, Standard Edition (build 1.4.2_06-b03)
Java HotSpot(TM) Client VM (build 1.4.2_06-b03, mixed mode)
Enter one of the following commands in a terminal window on your local Linux machine:
java -jar /export/home/v20z/update_server/Vx.x.x.x/updateServer.jar -f /export/home/v20z/sw_images/sp/spbase/Vy.y.y.y/install.image -p 50000
Where x.x.x.x is the version number of the Update Server application, and y.y.y.y is the version number of the SP firmware.
java -jar /export/home/v40z/update_server/Vx.x.x.x/updateServer.jar -f /export/home/v40z/sw_images/sp/spbase/Vy.y.y.y/install.image -p 50000
Where x.x.x.x is the version number of the Update Server application, and y.y.y.y is the version number of the SP firmware.
|
Note - Enter the command on one continuous line at the prompt. |
The following message appears in the terminal window:
The SP update process will take several minutes to complete during which the SP will be rebooted. You may now execute the "sp update flash all" command on the SP to start the update...
Return to the terminal window with the SSH connection to the SP.
Launch the update process with the following command:
sp update flash all -i <ip_address_linux_machine> -p 50000
The SP executes the command and reboots itself. The reboot process takes a few minutes.
The SSH session automatically terminates.
In the terminal window running the Java utility, the following messages appear as the SP reboots and updates itself:
$ java -jar ./s update_server/V2.2.0.6/updateServer.jar -f
./sw_images/sp/spbase/V2.4.0.10/install.image -p 50000
[Fri Jun 09 10:45:38 PDT 2006] Update server is ready; port 50000
[Fri Jun 09 10:46:12 PDT 2006] [/10.4.145.238] [SP_BASE LATEST] Update
started
[Fri Jun 09 10:50:42 PDT 2006] [/10.4.145.238] [SP_BASE LATEST] Update
complete: ./sw_images/sp/spbase/V2.4.0.10/install.image
When the message "(7) SP flash update complete" appears, unless you need to update more servers, you can close the Java SP Update utility.
Ensure that the platform is powered off before you update the BIOS.
1. To verify the power state of the platform side of the server, enter the following command:
|
Note - If the platform is powered on, the green LED below the floppy diskette drive is illuminated. |
2. If the result returned is ON, power off the platform side with the following command:
platform set power state off -f
3. At the SP prompt, enter one of the following commands, depending on your type of server:
platform set os state update-bios /mnt/sw_images/platform/firmware/bios/Vx.x.x.x/bios.sp
Where x.x.x.x is the BIOS version number.
platform set os state update-bios /mnt/sw_images/platform/firmware/bios/Vx.x.x.x/bios.sp
Where x.x.x.x is the BIOS version number.
This update process might take several minutes before any output is returned. The output in your terminal window should look similar to the following:
This command may take several minutes. Please be patient.
Bios started
Bios Flash Transmit Started
Bios Flash Transmit Complete
Bios Flash update Progress: 7
Bios Flash update Progress: 6
Bios Flash update Progress: 5
Bios Flash update Progress: 4
Bios Flash update Progress: 3
Bios Flash update Progress: 2
Bios Flash update Progress: 1
Bios Flash update complete
4. When the BIOS update is complete, the server automatically powers off.
When the server powers on, if the BIOS and SP firmware update operations were successful, a BIOS message is displayed on the console.
For the beginning section of this message, see Console Output After Successful Update on a Sun Fire V20z Server or Console Output After Successful Update on a Sun Fire V40z Server.
The update procedure is now complete. Please note:
Unmount the directory that you mounted previously.
1. From the SP, enter the following command to unmount the directory:
2. To verify that the directory has been unmounted, enter the following command:
You should not see the directory /export/home/v20z or /export/home/v40z (depending on your type of server).
1. Open the file /etc/exports using your preferred text editor.
2. Remove the line that you had added, depending on your type of server, from the exports file:
/export/home/v20z *(rw,no_root_squash)
/export/home/v40z *(rw,no_root_squash)
When the server reboots, if the BIOS and firmware update operations were successful, a text message appears. The following text shows the beginning of a sample message for an updated server.
|
Note - Ensure that the System BIOS Revision indicates the updated version number in the header of this text message. |
PhoenixBIOS 4.0 Release 6.0
Copyright 1985-2002 Phoenix Technologies Ltd.
All Rights Reserved
Production RELEASE: System BIOS Revision = Vx.x.x.x
SP Interface (PRS) Revision = 97
SP - BIOS Interface Active
xxxxxxxxxxxxxxxxxxxxxxxxxx
xx Sun Microsystems xx
xx Sun Fire V20z xx
xxxxxxxxxxxxxxxxxxxxxxxxxx
CPU0 = AMD Opteron(tm) Processor 250
CPU1 = AMD Opteron(tm) Processor 250
2 Processors Detected, CG - CG
PCIX - Slot0: PCIX-66 Slot1: PCIX-133
4031M System RAM Passed
1024K Cache SRAM Passed
ATAPI CD-ROM: CD-224E
Mouse initialized
<...continued>
When the server reboots, if the BIOS and firmware update operations were successful, a text message appears; the following text shows the beginning of a sample message for an updated server.
|
Note - Ensure that the System BIOS Revision indicates the updated version number in the header of this text message. |
PhoenixBIOS 4.0 Release 6.0
Copyright 1985-2002 Phoenix Technologies Ltd.
All Rights Reserved
Production RELEASE: System BIOS Revision = Vx.x.x.x
SP Interface (PRS) Revision = 14
xxxxxxxxxxxxxxxxxxxxxxxxxx
xx Sun Microsystems xx
xx Sun Fire V40z xx
xxxxxxxxxxxxxxxxxxxxxxxxxx
CPU0 = AMD Opteron(tm) Processor 848
CPU1 = AMD Opteron(tm) Processor 848
CPU2 = AMD Opteron(tm) Processor 848
CPU3 = AMD Opteron(tm) Processor 848
4 Processors Detected, CG - CG - CG - CG
7743M System RAM Passed
1024K Cache SRAM Passed
ATAPI CD-ROM: DV-28E-B
Mouse initialized
<...continued>
| Sun Fire V20z and Sun Fire V40z Servers--SP and BIOS Update ReadMe | 819-2714-14 | |
Copyright © 2006, Sun Microsystems, Inc. All Rights Reserved.