C H A P T E R 2 |
Powering On and Configuring BIOS Settings |
This chapter contains instructions on powering on and configuring the server BIOS, and it also describes how to update the BIOS and SP firmware. Changing the BIOS parameters is necessary only if you want to change the defaults.
Before powering on the server for the first time, follow the instructions in the Sun Fire V20z and Sun Fire V40z Servers--Installation Guide to set up your server.
This chapter contains the following sections:
Note - Before powering on the server for the first time, follow the setup instructions in the Sun Fire V20z and Sun Fire V40z Servers--Installation Guide. |
![]() |
Caution - Before you power on a Sun Fire V40z server for the first time, you must remove the packaging inserts from the server’s PCI card slots and CPU card slot to ensure proper airflow and cooling. You can discard these packaging inserts, which serve as protection during shipping. Do notremove the plastic air-baffle inserts from the PCI slots.
The updated release (chassis PN 380-1206) of the server does notship with the packaging insert in the PCI card slots. For information about how to identify which version of the server you have, refer to Section 3.4, Releases of the Sun Fire V20z Serverand Section 4.4, Releases of the Sun Fire V40z Server. |
If you want to configure the server BIOS, you must use a PS/2 keyboard for initial bootup. USB keyboard support is disabled in the BIOS by default. See Section 2.4, BIOS Setup Utility for more information.
Follow these steps to boot the server:
1. Ensure that an AC power cord is plugged into each power connector on the rear of the server and into an AC power outlet(s).
2. Power on the server using one of the following two methods, depending on which server type you have:
a. Turn on the AC Power switch on the server back panel (see FIGURE 1-2).
This switch provides AC power to the SP and basic hardware.
b. Push and release the platform Power button on the server front panel (see FIGURE 1-1).
This button provides power to the BIOS, operating system, and drivers.
a. Push and release the platform Power button on the server front panel (see FIGURE 1-4).
This button provides power to the BIOS, operating system, and drivers. There is no separate AC Power switch on the Sun Fire V40z server; basic AC power is applied when you plug in a power cord to a power supply.
3. When prompted, you can press the F2 key to enter the BIOS Setup utility or press the F12 key to boot from the network. To boot from the default boot device, let the prompt time out and the boot process will continue.
For further information about the BIOS Setup utility, refer to Section 2.4, BIOS Setup Utility. For information about setting up a network Preboot Execution Environment (PXE) installation, see the Sun Fire V20z and Sun Fire V40z Servers--Linux Operating System Installation Guide.
To perform a graceful shutdown of the server while running a Solaris, Linux, or UNIX® operating system, use this procedure.
Note - You must run this command as the root user. |
1. Type the following command:
This command shuts down the OS.
Depending on which OS you are using, you might also have to push the platform Power button on the front panel after the OS shuts down.
2. Do one of the following actions, depending on which model of server you have:
If you are accessing your server using a remote console terminal, you might need to use the escape sequences shown in TABLE 2-1. If a regular function key is not working properly, use the escape sequence listed next to it in the table.
You will most likely need to use the escape sequences if you are using a Linux or Solaris OS.
The Basic Input Output System (BIOS) Setup utility can be used to configure BIOS settings. When the computer is powered on, it is configured with the values stored in the BIOS ROM by the system BIOS, which gains control at boot time. Changing these parameters is only necessary if you want to change the defaults.
To change the system parameters, enter the BIOS Setup utility by pressing the F2 key when prompted, as the system is booting.
Note - If you are using a USB keyboard, the F2 key might not work properly when entering BIOS Setup unless the F-Lock key is on. |
During system boot, you can also press the F12 key to boot the network.
To access the BIOS Setup utility remotely, you can log in by means of an SSH client. Refer to the Sun Fire V20z and Sun Fire V40z Servers--Server Management Guide, for more information about managing the server remotely.
From the Main menu screen, you can access other setup screens, such as Security and Power.
To navigate between items in a menu:
Items that include submenus begin with a triangle icon. To access a submenu, select the item so that it is highlighted and press Enter.
Note - You can use the Fusion-MPT PCI SCSI BIOS Configuration utility to change the default configuration of your SCSI host adapters. You might decide to alter these default values if there is a conflict between device settings or to optimize system performance. See Appendix C for details. |
The tables in the following sections describe each parameter setting in the BIOS Setup utility.
Note - For NSV version 2.2.0.x and higher, there are certain changes in the menu options. These changes are called out in the tables. |
TABLE 2-2 shows the options that are available from the BIOS Main menu.
TABLE 2-3 shows the options that are available from the Advanced menu.
TABLE 2-4 shows the options that are available from the BIOS Security menu.
TABLE 2-5 shows the options that are available from the BIOS Power menu.
TABLE 2-6 shows the options that are available from the BIOS Boot menu. To change the order of the boot items, select an item and press the plus (+) key to move the item up in the order and the minus (-) key to move the item down in the order.
TABLE 2-7 shows the options that are available from the BIOS Exit menu.
The QuickBoot feature, which disables BIOS memory tests, defaults to disabled, which is the recommended setting.
Follow this procedure to disable the QuickBoot feature:
1. Boot the server and run BIOS Setup by pressing the F2 key during the boot process.
2. From the Advanced menu, disable the QuickBoot feature.
Now the BIOS will run at least one full memory test for your new memory when the server is rebooted.
3. Press F10 to save the changes and exit.
The system will automatically reboot and run the memory configuration tests.
4. When all memory passes the tests, press the F2 key to enter BIOS Setup.
5. Re-enable the QuickBoot option in the BIOS Advanced menu, if needed.
Only one diskette device is bootable on these servers. By default, the internal diskette device is the only device from which you can boot.
To change the assignment of the diskette devices, so that the server boots from a USB diskette device rather than the internal diskette device, perform the following steps:
1. Attach the USB diskette device.
2. Power on and reboot the system.
3. Press the F2 key to enter the BIOS Setup utility.
4. From the Advanced menu, choose I/O Device Configuration.
5. Change the USB Host Controller and USB BIOS Legacy Support submenu options to Enabled.
6. Press the F10 key to save your changes and exit.
The system will automatically reboot and run the self tests.
7. When prompted, press the F2 key to enter the BIOS Setup utility.
8. In the Boot menu, select Removable Devices.
9. Select USB Floppy from the Removable Devices submenu.
10. Press the plus (+) key to move USB Floppy to the top of the list of devices.
11. Press the F10 key to save your changes and reboot.
The USB diskette device is bootable as drive A. If left enabled, the internal diskette drive becomes drive B and is not bootable.
This section contains instructions on how to update the BIOS and SP firmware in the Sun Fire V20z and Sun Fire V40z servers.
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-based or Linux-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.
If you know the login information for the SP, you can skip to Connecting Your Local Client to the Network. |
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.
Note - It is not recommended to update a server over a WAN. |
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 Section 2.6.2.3, Resetting the Service Processor. |
The command should return something similar to the following:
If one of the following is true, you need to upgrade your system:
If one of the following is true, you need to upgrade your system:
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.
Download the following files into the directory /export/home/v40z on your local Solaris machine.
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/V2.2.0.6/updateServer.jar -f /export/home/v20z/sw_images/sp/spbase/V2.3.0.15/install.image -p 50000
java -jar /export/home/v40z/update_server/V2.2.0.6/updateServer.jar -f /export/home/v40z/sw_images/sp/spbase/V2.3.0.15/install.image -p 50000
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:
/10.6.164.10:(0)Received a ping request /10.6.164.10:(0)Replying to the ping request /10.6.164.10:(0)Waiting for an update request from a SP..this may take a few minutes /10.6.164.10:(0)Received an update request /10.6.164.10:(1)Sending an update accept message to the SP /10.6.164.10:(2)Sending a write request to the SP /10.6.164.10:(3)Transferring image file to the SP...this may take a few minutes /10.6.164.10:(4)Waiting for the file transfer status from the SP /10.6.164.10:(4)File transfer status: passed /10.6.164.10:(5)Waiting for image checksum status from the SP...this may take a few minutes /10.6.164.10:(5)Image checksum status: passed /10.6.164.10:(6)Waiting for SP boot status...this may take a few minutes /10.6.164.10:(6)Waiting for SP boot status...this may take a few minutes /10.6.164.10:(6)SP boot status: passed /10.6.164.10:(7)SP flash update complete
Once 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, then 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/V1.33.7.2/bios.sp
platform set os state update-bios /mnt/sw_images/platform/firmware/bios/V2.33.7.2/bios.sp
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. Once the BIOS update is completed, the server automatically powers off.
Once 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.
Download the following files into the directory /export/home/v40z on your local Linux machine.
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/V2.2.0.6/updateServer.jar -f /export/home/v20z/sw_images/sp/spbase/V2.3.0.15/install.image -p 50000
java -jar /export/home/v40z/update_server/V2.2.0.6/updateServer.jar -f /export/home/v40z/sw_images/sp/spbase/V2.3.0.15/install.image -p 50000
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:
/10.6.164.10:(0)Received a ping request /10.6.164.10:(0)Replying to the ping request /10.6.164.10:(0)Waiting for an update request from a SP..this may take a few minutes /10.6.164.10:(0)Received an update request /10.6.164.10:(1)Sending an update accept message to the SP /10.6.164.10:(2)Sending a write request to the SP /10.6.164.10:(3)Transferring image file to the SP...this may take a few minutes /10.6.164.10:(4)Waiting for the file transfer status from the SP /10.6.164.10:(4)File transfer status: passed /10.6.164.10:(5)Waiting for image checksum status from the SP...this may take a few minutes /10.6.164.10:(5)Image checksum status: passed /10.6.164.10:(6)Waiting for SP boot status...this may take a few minutes /10.6.164.10:(6)Waiting for SP boot status...this may take a few minutes /10.6.164.10:(6)SP boot status: passed /10.6.164.10:(7)SP flash update complete
Once 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, then 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/V1.33.7.2/bios.sp
platform set os state update-bios /mnt/sw_images/platform/firmware/bios/V2.33.7.2/bios.sp
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. Once the BIOS update is completed, the server automatically powers off.
Once 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)
Once 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, in the header of this text message, the System BIOS Revision indicates V1.34.4.2. |
PhoenixBIOS 4.0 Release 6.0 Copyright 1985-2002 Phoenix Technologies Ltd. All Rights Reserved Production RELEASE: System BIOS Revision = V1.34.4.2 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>
Once 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, in the header of this text message, the System BIOS Revision indicates V2.34.4.2. |
PhoenixBIOS 4.0 Release 6.0 Copyright 1985-2002 Phoenix Technologies Ltd. All Rights Reserved Production RELEASE: System BIOS Revision = V2.34.4.2 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>
Copyright © 2008, Sun Microsystems, Inc. All Rights Reserved.