Powering On and Configuring BIOS Settings

C H A P T E R 2

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:

Section 2.1, Powering On the Server

Section 2.2, Powering Off the Server

Section 2.3, Escape Sequences for Remote Console Terminal

Section 2.4, BIOS Setup Utility

Section 2.5, Booting From a USB Diskette Device

Section 2.6, Updating the BIOS and SP Firmware

2.1 Powering On the Server

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.

Caution - Do not operate this server without all fans, component heat sinks, air baffles, and the cover installed. Severe damage to server components will occur if the server is operated without adequate cooling mechanisms.

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:

If you have a Sun Fire V20z server, use these steps:

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.

If you have a Sun Fire V40z server, use this step:

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.

Note - If this is the first time you are booting the server, the booting stops and displays a message on the monitor, Operating system not found, and the LCD on the front panel displays the message, OS Booting. This is normal until after you install an operating system.

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.

2.2 Powering Off the Server

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:

# poweroff

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 have a Sun Fire V20z server, turn off the AC Power switch on the server back panel to remove AC power.

If you have a Sun Fire V40z server, disconnect all power cords from all power supplies to remove AC power.

2.3 Escape Sequences for Remote Console Terminal

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.

TABLE 2-1 Special Keys for Remote Console Terminal
Function Key	Escape Sequence
HOME	<ESC> h
END	<ESC> k
INSERT	<ESC> +
DELETE	<ESC> -
PAGE UP	<ESC> ?
PAGE DOWN	<ESC> /
ALT	<ESC>^A
CTRL	<ESC>^C
F1	<ESC> 1
F2	<ESC> 2
F3	<ESC> 3
F4	<ESC> 4
F5	<ESC> 5
F6	<ESC> 6
F7	<ESC> 7
F8	<ESC> 8
F9	<ESC> 9
F10	<ESC> 0
F11	<ESC> !
F12	<ESC> @

Table lists the escape sequences when using a remote console terminal.

2.4 BIOS Setup Utility

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:

Use the up and down arrow keys to move among the settings in each menu.

Use the left and right arrow keys to change the options for each setting.

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.

2.4.1 Main Menu

TABLE 2-2 shows the options that are available from the BIOS Main menu.

TABLE 2-2 BIOS Main Menu
Menu Option	Description	Default
System Time	Type the system time (hours:minutes:seconds) in the specified fields and press Enter to save the data. Use the Tab key to move to the next field and use Shift+Tab to move to the previous field.	Current time
System Date	Type the current date in the month, day and year fields. Press Enter to save the data. Use the Tab key to move to the next field and use Shift+Tab to move to the previous field.	Current date
Legacy Diskette A	Sets the type of diskette drive installed as diskette A. Options include: Disabled, 360KB 5.25 in, 1.2MB 5.25 in, 720KB 3.5 in, 1.44/1.25MB 3.5 in and 2.88MB 3.5 in. Note: 1.44/1.25MB 3.5 in references a 1024-byte sector Japanese media format. This diskette requires a 3-mode floppy disk drive.	1.44MB /1.25MB 3.5 in.
Legacy Diskette B Note: This option not included in NSV v2.2.0.x	Sets the type of diskette drive installed as diskette B. Options include: Disabled, 360KB 5.25 in, 1.2MB 5.25 in, 720KB 3.5 in, 1.44/1.25MB 3.5 in and 2.88MB 3.5 in. Note: 1.44/1.25MB 3.5 in references a 1024 byte sector Japanese media format. This diskette requires a 3-mode floppy disk drive.	Disabled
Primary Master (default: None) Primary Subordinate (default: None) Secondary Master (default: CD-ROM)	Sets the parameters of the IDE Primary Master/Subordinate and IDE Secondary Master slots. Press Enter to activate the submenu screen to configure each of these settings. The submenu options include:
	Type: The type of IDE hard drive. Options include: Auto (allows BIOS to automatically determine the hard drive’s capacity, number of heads, etc.), User, a number from 1 to 39 to select a predetermined type of hard drive, CD/DVD-ROM, ATAPI Removable and IDE Removable.	Auto
	Multi-Sector Transfers: The number of transfer sectors. Options include: Disabled, 2, 4, 8 and 16 sectors.	Disabled
	LBA Mode Control: Determines whether BIOS will access the IDE Primary Master Device via LBA mode. Options include: Enabled and Disabled.	Disabled
	32-bit I/O: Selects the 32-bit I/O operation. Options include: Enabled and Disabled.	Disabled
	Transfer Mode: Selects the transfer mode. Options include: Standard, Fast PIO1, Fast PIO2, Fast PIO3, Fast PIO4, FPIO3/DMA1 and FPIO4/DMA2.	Standard
	Ultra DMA Mode: Selects Ultra DMA Mode. Options include: Disabled, Mode 0, Mode 1, Mode 2, Mode 3, Mode 4, Mode 5 and Mode 6.	Disabled
HDD Post Write Buffer	Enables or disables HDD Post Write Buffer support.	Enabled
Large Disk Access Mode	For UNIX, Novell Netware, or other OSs, select Other. If you are installing new software and the drive fails, change this selection and try again. Different OSs require different representations of drive geometries. Options include: DOS and Other.	DOS
Boot Summary	Enables or disables display of the system configuration on boot.	Disabled
System Memory	Displays how much system memory is recognized as present in the system.	Current memory
Extended Memory	Displays how much extended memory is recognized as present in the system.	Current memory

Table lists the options available in the BIOS Main menu, a description of each option and the default value.

2.4.2 Advanced Menu

TABLE 2-3 shows the options that are available from the Advanced menu.

TABLE 2-3 BIOS Advanced Menu
Menu Option	Description	Default
Reset Configuration Data	Clears the Extended System Configuration Data (ECSD). Options include: Yes and No.	No
Multiprocessor Specification Note: This option is not included in NSV v2.2.0.x	Configures the MP Specification revision level. Some OSs require 1.1 for compatibility. Options include: 1.4 and 1.1.	1.4
PCI Interrupts From MP Table	Configures the MP Table with PCI Interrupt entries. Options include: Yes and No.	Yes
Machine Check Stop	If enabled, system stops when a machine check error occurs. If disabled, system reboots when a machine check error occurs. Only applies if your operating system does not have its own machine check handler. Double fault scenario: If enabled, the system stops when a second fatal machine check error occurs while processing a first fatal machine check (a double fault). If disabled, the system reboots during a double fault. This also applies to what occurs on the first fatal machine check if your operating system does not have its own machine check handler.	Disabled
QuickBoot Mode	Allows the system to skip tests while booting. Options include: Enabled and Disabled.	Disabled
Error Message Handling	Disabled allows system to automatically continue to boot after displaying a detected error. The other options display the `SETUP entry or resume boot prompt,` then wait for the specified period of time or forever, while a user chooses the action to take. Options include: Disabled, Wait 5 seconds, Wait 30 seconds, Wait Forever	Wait 30 seconds
Diagnostics Boot Mode Note: This option is new in NSV v2.2.0.x	Diagnostics Boot Mode can be enabled to provide platform diagnostics (CD Diags) with the same BIOS support provided to SP Diags. The default (Disabled) reflects that the platform is usually booted normally and not in diagnostic-support mode. Enabling this option is effective only for the next boot, after which it is reset to Disabled.	Disabled
Chipset Configuration Caution: Do not change the settings unless you are sure of what you are doing. Setting items on this menu to incorrect values might cause your system to malfunction.	Options for advanced chipset features. Options include:
	SRAT Table: Enables the ACPI 2.0 Static Resource Affinity Table for OSs that support an SRAT and will disable node interleaving. Disabled allows for node interleaving. Options include: Enabled and Disabled.	Enabled
	Node Interleave: If set to Auto, node interleaving will be enabled if these three conditions are true: memory sizes match, SRAT table is disabled, and DRAM ECC Scrub CTL is disabled. Options include: Auto and Disabled.	Disabled
	Bank Interleave: If set to Auto, bank interleaving is enabled if the memory size and type match. Options include: Auto and Disabled.	Auto
	ECC: Enables or disables ECC check/correct mode. This is a global enable function for all blocks within the CPU core and NorthBridge.	Enabled
	DRAM ECC: If all memory in the system supports ECC (x72), enabling invokes initial scrub DRAM and enables system requests to DRAM to be checked and/or corrected. Options include: Enabled and Disabled.	Enabled
	ECC Scrub Redirection: Enables or disables ECC Scrubber to correct errors detected in DRAM during normal CPU requests (foreground scrubbing).	Enabled
	Chip-Kill: Enables or disables the ChipKill ECC on nodes with all x4 ECC capable DIMMS.	Enabled
	DCACHE ECC Scrub CTL: Sets the rate of background scrubbing for DCACHE lines. Options include: 5.12 s, 10.2 s, 20.5 s, 41.0 s, Disabled, 640 ns, 1.28 s, 2.56 s.	5.12 s
	L2 ECC Scrub CTL: Sets the rate of background scrubbing for L2 cache lines. Options include: 10.2 s, 20.5 s, 41.0 s, 81.9 s, Disabled, 1.28 s, 2.56 s, 5.12 s.	10.2 s
	DRAM ECC Scrub CTL: Sets the rate of background scrubbing for DRAM (in addition to normal ECC scrubbing from system requests). Background agent works independently of CPU requests and bus masters, but cannot be enabled without first enabling DRAM ECC. This option must be disabled to allow node interleaving. Options include: 163.8 s, 327.7 s, 655.4 s, 1.31 ms, Disabled, 20.5 s, 41.0 s, 81.9 s.	163.8 s
	No Spec. TLB Reload: When this is at the default (Disabled), the translation look-aside buffer (TLB) is reloaded. When enabled, TLB reloading is turned off.	Disabled
I/O Device Configuration	Options for Peripheral menu. Options include:
	PS/2 Mouse: Disabled prevents any installed PS/2 mouse from functioning, but frees up IRQ 12. Enabled forces the PS/2 mouse port to be enabled regardless of whether a mouse is present. Auto Detect enables the PS/2 mouse only if present. OS Controlled only displays if the OS controls the mouse.	Enabled
	Floppy Disk Controller: Options include: Enabled (user configuration), Disabled (no configuration), Auto (BIOS or OS chooses configuration) and OS Controlled (displayed when controlled by the operating system).	Enabled
	USB Host Controller: Enables or disables the USB hardware. Disabled resources are freed for other users.	Enabled
	USB BIOS Legacy Support: Enables or disables support for USB devices. Enable for use with a non-USB-aware OS such as DOS, Linux or Solaris.	Disabled
	Onboard PCI IDE: Enables the integrated local bus IDE adapter. Options include: Disabled, Primary, Secondary, Both.	Both
	Serial Port A: Assigns control of serial port A. Options include: Enabled, Auto, or Disabled. When enabled, you must also select the Base I/O Address and Interrupt for serial port A. - Base I/O Address: - Interrupt:	Enabled 3F8 IRQ4
Note: Sun Fire V40z servers include a serial port B; this option does not appear for Sun Fire V20z servers.	Serial Port B: Assigns control of serial port B. Options include: Enabled, Auto or Disabled. When enabled, you must also select the Base I/O Address and Interrupt for serial port B. - Base I/O Address: - Interrupt:	Enabled 2F8 IRQ3
	Ethernet Adapter 0 MAC: Displays the On-board Ethernet adapter 0 MAC address.	MAC address
	Ethernet Adapter 1 MAC: Displays the On-board Ethernet adapter 1 MAC address.	MAC address
PCI Configuration Note: The Sun Fire V20z server has two PCI slots; the Sun Fire V40z server has seven slots.	Setup items for configuring the specific PCI device slots:
	Option ROM Scan: When disabled, the device is not bootable but is still usable under the OS. When enabled, initializes the device expansion ROM; makes device bootable.	Enabled
	Enable Master: Enables or disables the selected device as a PCI bus master.	Enabled
	Latency Timer: Sets the minimum guaranteed time slice allotted for bus master in units of PCI bus clocks. Options include: 0040h, 0060h, 0080h, 00A0h, 00C0h, 00E0h, default and 0020h.	0040h
	Setup items for configuring the Embedded Broadcom device GBIT 0 or GBIT 1:
	Option ROM Scan: When disabled, the device is not bootable but still usable under the OS. When enabled, initializes device expansion ROM; makes device bootable.	Enabled
	Reserve specific IRQs for use by legacy ISA devices:
	PCI/PNP IRQ Exclusion: Reserves the specified IRQ for use by legacy ISA devices.	Available
	PCI/PNP UMB Exclusion: Reserves the specified block of upper memory for use by legacy ISA devices.	Available
Note: This option is new in NSV v2.2.0.x	Option ROM Expansion: If errors occur when option ROMs are initialized, choose Extended to increase memory during ROM expansion time. Caution: The server might hang when Extended is used with some option ROMs.	Normal
Note: This option is new in NSV v2.2.0.x	8131 Errata 56 PCLK: This indicates a card problem. The BIOS will fix the problem or will turn it off. If you select Enabled, the BIOS will not turn it off.	Disabled
Console Redirection	Additional setup to configure console. Options include:
	COM port address: If enabled, the console uses a port on the motherboard. Options include: Disabled, On-board COM A, On-board COM B.	On-board COM A
	Console connection: Indicates whether the console is connected directly to the system or through a modem. Options include: Direct and Modem.	Direct
	Baud rate: Enables the specified baud rate. Options include: 300, 1200, 2400, 9600, 19.2K, 38.4K, 57.6K, 115.2K.	9600
	Flow control: Enables flow control. Options include: None, XON/XOFF, CTS/RTS.	None
	Console type: Enables the specified console type. Options include: VT100, VT100 8 bit, ANSI 7 bit, ANSI, VT100 plus, UTF8.	VT100 plus
	Continue CR after POST: Normally, console redirection is off before the OS loads. Set this item to On to troubleshoot the BIOS boot problems. Options include: On and Off. Note: Check the OS loader for console output settings. Also refer to the Server Management Guide for information on console redirection.	On

Table lists the options available in the BIOS Advanced menu, a description of each option and the default value.

2.4.3 Security Menu

TABLE 2-4 shows the options that are available from the BIOS Security menu.

TABLE 2-4 BIOS Security Menu
Menu Option	Description	Default
Supervisor Password Is:	Displays whether a supervisor password has been entered for the system. Clear means such a password has not been used and Set means a supervisor password has been entered for the system.	Clear
User Password Is:	Displays whether a user password has been entered for the system. Clear means such a password has not been used and Set means a user password has been entered for the system.	Clear
Set Supervisor Password	Supervisor password controls access to the Setup utility. Type the Supervisor’s password to set or change it. Enables access to BIOS.	Enter
Set User Password	Type the user’s password to set or change it. Enables access to the system at boot time.	Enter
Password on Boot	Allows you to require a password to be entered when the system boots. Options include: Enabled (password required) and Disabled (password not required).	Disabled
Fixed Disk Boot Sector	Might offer protection against viruses when set to Write Protect, which protects the boot sector on the hard drive from having a virus written to it. Options include: Write Protect and Normal.	Normal

Table lists the options available in the BIOS Security menu, a description of each option and the default value.

2.4.4 Power Menu

TABLE 2-5 shows the options that are available from the BIOS Power menu.

TABLE 2-5 BIOS Power Menu
Menu Option	Description	Default
Resume on Time	Wakes the system up at the specified time. Options are On or Off.	Off
Resume Time	If turned on, specifies the time you want the system to wake up.	00.00.00
Resume Date	If turned on, specifies the date you want the system to wake up.	00/00/0000
After Power Failure	Sets the mode of operation if an AC power loss occurs. Three modes are available: Stay off: Returns the system to an off state. Power on: Returns the system to a full on state. Last state: Returns the server to the state it was at before the power went off.	Stay off

Table lists the options available in the BIOS Power menu, a description of each option and the default value.

2.4.5 Boot 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-6 BIOS Boot Menu
Menu Option	Description	Default Boot Order
Removable Devices (Floppy)	Boot from the diskette drive	First boot device
CD-ROM Drive	Boot from the CD/DVD-ROM	Second boot device
Hard Drive	Boot from the hard disk	Third boot device
Network Boot	Boot from a networked device	Networked boot device
MBA v7.0.x Slot 0210	Boot from the on-board NIC #1	Fourth boot device
MBA v7.0.x Slot 0218	Boot from the on-board NIC #2	Fifth boot device

Table lists the options available in the BIOS Boot menu, a description of each option and the default boot order.

2.4.6 Exit Menu

TABLE 2-7 shows the options that are available from the BIOS Exit menu.

TABLE 2-7 BIOS Exit Menu
Menu Item	Description
Exit Saving Changes	Exits System Setup and saves changes to CMOS.
Exit Discarding Changes	Exits System Setup without saving changes.
Load Setup Defaults	Loads defaults for all setup items.
Discard Changes	Loads previous values from CMOS for all setup items.
Save Changes	Saves setup data to CMOS.

Table lists the options available in the BIOS Exit menu and a description of each option.

2.4.7 QuickBoot Feature

The QuickBoot feature, which disables BIOS memory tests, defaults to disabled, which is the recommended setting.

Note - If you choose to set QuickBoot to enabled, you need to perform the following steps to disable the QuickBoot feature whenever you add new memory, so that the new memory configuration can be tested.

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.

2.5 Booting From a USB Diskette Device

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.

Note - To change the internal diskette drive to be drive A again, disconnect the USB diskette device and reboot the server. The internal diskette device will be assigned to drive A, and if you reattach the USB diskette device, it will be assigned to drive B.

2.6 Updating the BIOS and SP Firmware

This section contains instructions on how to update the BIOS and SP firmware in the Sun Fire V20z and Sun Fire V40z servers.

2.6.1 Overview of the Update Procedure

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.

2. Download the NSV files.

3. Share the NSV files with the appropriate permissions.

4. From a Solaris-based or Linux-based client:

a. Update the SP firmware.

b. Update the BIOS.

5. Reboot the server.

6. Perform housecleaning tasks.

2.6.2 Preparing the Server

Before you start the update:

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.

2.6.2.1 Powering On the Service Processor

The SP needs to be running; however, the platform side of the Sun Fire V20z or Sun Fire V40z server must be powered off.

For the Sun Fire V20z server:

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).

For the Sun Fire V40z server:

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).

2.6.2.2 Configuring the Service Processor Network Settings

As the SP boots and comes up, its network settings now need to be configured.

If a DHCP server is available on the network to which the SP is connected, press the Select (center) button on the LCD panel to confirm the use of DHCP. The SP will request an IP address from the DHCP server; 5 to 10 seconds later, an IP address will display on the LCD panel.

If you do not press the button before the system times out, the system automatically looks for a DHCP server.

If no DHCP service is available on the SP network, use the arrow buttons to manually enter the network-information settings: IP address, netmask and default gateway or router.

For more information, refer to the Sun Fire V20z and Sun Fire V40z Servers--Installation Guide (817-5246).

2.6.2.3 Resetting the Service Processor

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.

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.

If a DHCP server is available on the network to which the SP is connected, simply press the Select button on the LCD panel to confirm the use of DHCP.

If no DHCP service is available on the SP network, use the arrow buttons to manually enter the network-information settings: IP address, netmask and default gateway or router.

2.6.2.4 Connecting Your Local Client to the Network

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.

2.6.2.5 Configuring the Manager User and Password for the Service Processor

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 SSH session disconnects.

The SP is now set up and ready to be used to perform the server update.

2.6.3 Verify BIOS and Firmware Versions

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.

Connect to the SP Through SSH

1. Open a terminal window.

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.

Check the Software Inventory

Type the following command:

inventory get software

The command should return something similar to the following:

For a Sun Fire V20z server:

Name			Revision				Install Date							Description
Platform BIOS			V1.34.4.2				Wed Aug 31 11:15:20 2006							Platform BIOS for V20z... 
Operator Panel	V1.0.1.2						Fri Feb 11 19:17:42 2006							Operator Panel Firmware
SP Base			V2.4.0.2				Wed Aug 31 11:15:20 2006							SP Base Software

If one of the following is true, you need to upgrade your system:

The BIOS version is lower than V01.33.7.2.

The SP version is lower than 2.3.0.15.

For a Sun Fire V40z server:

Name			Revision				Install Date							Description
Platform BIOS			V2.34.4.2				Wed Aug 31 11:15:20 2006							Platform BIOS for V40z... 
Operator Panel	V1.0.1.2						Fri Feb 11 19:17:42 2006							Operator Panel Firmware
SP Base			V2.4.0.2				Wed Aug 31 11:15:20 2006							SP Base Software

If one of the following is true, you need to upgrade your system:

The BIOS version is lower than V02.33.7.2.

The SP version is lower than 2.3.0.15.

2.6.4 Performing the Server Update From a Solaris-based Client

2.6.4.1 Download and Share the NSV Files

Open a Terminal Window

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.

Create a New Directory

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:

mkdir /export/home/v20z

mkdir /export/home/v40z

You will download the update files to the directory that you create.

Download the NSV Files

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:

For a Sun Fire V20z server:

Download the following files into the directory /export/home/v20z on your local Solaris machine.

nsv_V2_4_0_6.zip

nsv-v20z-bios-fw_V2_4_0_6.zip

For a Sun Fire V40z server:

Download the following files into the directory /export/home/v40z on your local Solaris machine.

nsv_V2_4_0_6.zip

nsv-v40z-bios-fw_V2_4_0_6.zip

Unzip the NSV Package Files

Unzip the NSV release-package files into the directory you created on your local Solaris machine.

Use the following command format:

unzip <filename>

If the unzipping process creates new zip archive files, unzip these new files as well.

2.6.4.2 Mount the NSV Share on the Service Processor

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:

ifconfig -a

3. Obtain the IP address by which your local Solaris machine connects to the network.

4. Enter the following command:

ssh -l <SP_username> <SP_IP>

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:

For a Sun Fire V20z server, enter:

sp add mount -r <solaris-ip-address>:/export/home/v20z -l /mnt

For a Sun Fire V40z server, enter:

sp add mount -r <solaris-ip-address>:/export/home/v40z -l /mnt

Note - If you receive an error message when you run the mount command for the Sun Fire V20z server, add the following line to the file /etc/dfs/dfstab, and reboot the server:
share -F nfs -o ro /export/home/v20z

6. At the ssh prompt, enter the following command:

sp get mounts

The directory /export/home/v20z or /export/home/v40z should now be mounted.

2.6.4.3 Perform the SP Update

Ensure That the Platform Is Powered Off

1. To verify the power state of the platform side of the server, enter the following command:

platform get power state

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

Verify the Version of Java Runtime Environment

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:

java -version

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)

Update the SP Firmware

Step 1-Launch the SP Update Utility on the Solaris Machine

Enter one of the following commands on one continuous line in a terminal window on your local Solaris machine:

For a Sun Fire V20z server, enter:

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

For a Sun Fire V40z server, enter:

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...

Step 2-Start the Update Process From the Service Processor

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.

2.6.4.4 Perform the BIOS Update

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:

platform get power state

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:

For a Sun Fire V20z server, enter:

platform set os state update-bios /mnt/sw_images/platform/firmware/bios/V1.33.7.2/bios.sp

For a Sun Fire V40z server, enter:

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.

2.6.4.5 Verify the Updates

Power on the server again.

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.

2.6.4.6 Housecleaning Tasks

The update procedure is now complete. Please note:

If the local client from which you performed the update procedure will remain at this network location and act as a permanent NSV server, leave the directory mounted and shared.

If the local client from which you performed the update procedure is at this network location temporarily (for example, if you used a laptop computer to update your server), we recommend that you unmount and unshare the directory.

Unmount the Directory

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:

sp delete mount

3. To verify that the directory has been unmounted, enter the following command:

sp get mounts

You should not see the directory /export/home/v20z or /export/home/v40z (depending on your type of server).

Unshare the Directory

At the shell prompt, enter one of the following commands, depending on your type of server:

unshare /export/home/v20z

unshare /export/home/v40z

2.6.5 Performing the Server Update From a Linux-based Client

2.6.5.1 Download and Share the NSV Files

Open a Terminal Window

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.

Create a New Directory

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:

mkdir /export/home/v20z

mkdir /export/home/v40z

You will download the update files to the directory that you create.

Download the NSV Files

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:

For a Sun Fire V20z server:

Download the following files into the directory /export/home/v20z on your local Linux machine.

nsv_V2_4_0_6.zip

nsv-v20z-bios-fw_V2_4_0_6.zip

For a Sun Fire V40z server:

Download the following files into the directory /export/home/v40z on your local Linux machine.

nsv_V2_4_0_6.zip

nsv-v40z-bios-fw_V2_4_0_6.zip

Unzip the NSV Package Files

Unzip the NSV release-package files into the directory you created on your local Linux machine.

Use the following command format:

unzip <filename>

If the unzipping process creates new zip archive files, unzip these new files as well.

2.6.5.2 Mount the NSV Share on the Service Processor

1. Move to the directory /etc:

cd /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:

For SUSE Linux, use these commands:

a. Restart the NFS service:

/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:

showmount -e localhost

For Red Hat Enterprise Linux, use these commands:

a. Restart the NFS service:

/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:

showmount -e localhost

6. Enter the following command:

ifconfig -a

7. Obtain the IP address by which your local Linux machine connects to the network.

8. Enter the following command:

ssh -l <SP_username> <SP_IP>

9. At the ssh prompt, enter one of the following commands:

For a Sun Fire V20z server, enter:

sp add mount -r <linux-ip-address>:/export/home/v20z -l /mnt

For a Sun Fire V40z server, enter:

sp add mount -r <linux-ip-address>:/export/home/v40z -l /mnt

10. At the ssh prompt, enter the following command:

sp get mounts

The directory /export/home/v20z or /export/home/v40z should now be mounted.

2.6.5.3 Perform the SP Update

Ensure That the Platform Is Powered Off

1. To verify the power state of the platform side of the server, enter the following command:

platform get power state

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

Verify the Version of Java Runtime Environment

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:

java -version

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)

Update the SP Firmware

Step 1 - Launch the SP Update Utility on the Linux Machine

Enter one of the following commands in a terminal window on your local Linux machine:

Sun Fire V20z server:

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

Sun Fire V40z server:

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...

Step 2 - Start the Update Process From the Service Processor

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.

2.6.5.4 Perform the BIOS Update

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:

platform get power state

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:

For a Sun Fire V20z server, enter:

platform set os state update-bios /mnt/sw_images/platform/firmware/bios/V1.33.7.2/bios.sp

For a Sun Fire V40z server, enter:

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.

2.6.5.5 Verify the Updates

Power on the server again.

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.

2.6.5.6 Housecleaning Tasks

The update procedure is now complete. Please note:

If the local client from which you performed the update procedure will remain at this network location and act as a permanent NSV server, leave the directory mounted and shared.

If the local client from which you performed the update procedure is at this network location temporarily (for example, if you used a laptop computer to update your server), you should unmount and unshare the directory.

Unmount the Directory

Unmount the directory that you mounted previously.

1. From the SP, enter the following command to unmount the directory:

sp delete mount

2. To verify that the directory has been unmounted, enter the following command:

sp get mounts

You should not see the directory /export/home/v20z or /export/home/v40z (depending on your type of server).

Edit the File `/etc/exports`

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)

2.6.6 Console Output After Successful Update on a Sun Fire V20z Server

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>

2.6.7 Console Output After Successful Update on a Sun Fire V40z Server

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>

2.1 Powering On the Server

2.2 Powering Off the Server

2.3 Escape Sequences for Remote Console Terminal

2.4 BIOS Setup Utility

2.4.1 Main Menu

2.4.2 Advanced Menu

2.4.3 Security Menu

2.4.4 Power Menu

2.4.5 Boot Menu

2.4.6 Exit Menu

2.4.7 QuickBoot Feature

2.5 Booting From a USB Diskette Device

2.6 Updating the BIOS and SP Firmware

2.6.1 Overview of the Update Procedure

2.6.2 Preparing the Server

2.6.2.1 Powering On the Service Processor

2.6.2.2 Configuring the Service Processor Network Settings

2.6.2.3 Resetting the Service Processor

2.6.2.4 Connecting Your Local Client to the Network

2.6.2.5 Configuring the Manager User and Password for the Service Processor

2.6.3 Verify BIOS and Firmware Versions

Connect to the SP Through SSH

Check the Software Inventory

2.6.4 Performing the Server Update From a Solaris-based Client

2.6.4.1 Download and Share the NSV Files

Open a Terminal Window

Create a New Directory

Download the NSV Files

Unzip the NSV Package Files

2.6.4.2 Mount the NSV Share on the Service Processor

2.6.4.3 Perform the SP Update

Ensure That the Platform Is Powered Off

Verify the Version of Java Runtime Environment

Update the SP Firmware

Step 1-Launch the SP Update Utility on the Solaris Machine

Step 2-Start the Update Process From the Service Processor

2.6.4.4 Perform the BIOS Update

2.6.4.5 Verify the Updates

2.6.4.6 Housecleaning Tasks

Unmount the Directory

Unshare the Directory

2.6.5 Performing the Server Update From a Linux-based Client

2.6.5.1 Download and Share the NSV Files

Open a Terminal Window

Create a New Directory

Download the NSV Files

Unzip the NSV Package Files

2.6.5.2 Mount the NSV Share on the Service Processor

2.6.5.3 Perform the SP Update

Ensure That the Platform Is Powered Off

Verify the Version of Java Runtime Environment

Update the SP Firmware

Step 1 - Launch the SP Update Utility on the Linux Machine

Step 2 - Start the Update Process From the Service Processor

2.6.5.4 Perform the BIOS Update

2.6.5.5 Verify the Updates

2.6.5.6 Housecleaning Tasks

Unmount the Directory

Edit the File /etc/exports

2.6.6 Console Output After Successful Update on a Sun Fire V20z Server

2.6.7 Console Output After Successful Update on a Sun Fire V40z Server

Edit the File `/etc/exports`