C H A P T E R  2

Powering On and Configuring BIOS Settings

This chapter describes how to power on and off the server, as well as how to configure BIOS settings.

The following topics are discussed in this chapter.


2.1 Powering On and Off the Server

Refer to the following topics in this section to power on and off a server:

2.1.1 Power On the Server Module

The following procedure assumes the server module is installed in a powered-on chassis.

1. Verify that the server is in a standby power state.

In a Standby power state, the OK power LED on the front panel of the server blinks (0.1 second on, 2.9 seconds off). A standby power state indicates that the server module SP is active but the server module host is powered-off.

See FIGURE 1-1 for the OK Power LED location.



Note - The OK/Power LED will be set to standby blink only when there is enough chassis power for the server module to power on. If there is not enough chassis power, the OK/Power LED will remain off until there is enough power for the server module to power on. To troubleshoot this issue, see Troubleshoot Server Power States.


2. Apply full power to the server SP and host.

For example:

For Power button location, see FIGURE 1-1 Sun Blade X6270 Server Module Front Panel.

The OK/Power LED on the server module front panel illuminates a steady-on green light. The steady-on LED state indicates that the server module SP and host are both powered-on.

If the server does not power-on, see Troubleshoot Server Power States.

2.1.2 Power Off and Verify Server Is Ready for Removal From Chassis

Follow these steps to ensure that the server is properly powered off and is ready for removal from chassis.

1. Power off the server.

For example:

This operation will cause any Advanced Configuration and Power Interface (ACPI) enabled operating systems to perform an orderly shutdown of the operating system. Servers not running ACPI-enabled operating systems will shut down to standby power mode immediately.

stop /SYS

a. Select Remote Control --> Remote Power Control.

b. Select one of the following actions from the drop-down list.

Refer to the Sun Integrated Lights Out Manager 2.0 User’s Guide (820-1188) for more information.

2. To ensure that the system is powered off and ready to be removed from the chassis, do the following:

a. Verify that the green power LED on the front panel of the server is in standby or off state.

b. Ensure that the system was prepared for removal on the Component Management tab in ILOM.

In the Component Management tab, a Ready (no power) status will appear in the Ready To Remove column for the server.

For more details, see the prepare to remove component procedures in the Sun Integrated Lights Out Manager 2.0 Users Guide (820-1188).

For information about removing the server from the chassis and removing the cover from the server, see Removing the Server From the Chassis and Removing the Cover.

2.1.3 Troubleshoot Server Power States

Each time a server module powers on in the Sun Blade 6000 or 6048 Series Chassis, it queries the CMM to ensure that there is enough power available from the power supply units (PSUs) to power on the server. If there is not enough power to power on the server module, the SP denies the server module from receiving power (standby and main). If this situation occurs, the OK/Power LED on the front panel of the server module will remain off. To troubleshoot this power issue, follow these guidelines:

1. Review the ILOM Event Log messages to determine if the server has permission to power on. An event message is recorded in the log any time there is not an adequate amount of power available from the PSUs to power on the server module.

For more information about the ILOM event log or monitoring power consumption, refer to the Sun Integrated Lights Out Manger 2.0 User’s Guide (820-1188).

2. Ensure that the system chassis has the proper amount of power supplies installed to support powering on all the chassis components currently installed.

Refer to the system chassis documentation for information about the number of power supplies required to power on chassis components.

3. To avoid power loss, it is recommended that you use the default CMM power management settings for PSUs in ILOM.

For more information about power management, refer to the Sun Blade X6270 Server Module ILOM 2.0 Supplement Guide (820-6180) and the Sun Integrated Lights Out Manger 2.0 (ILOM 2.0) User’s Guide (820-1188).

2.1.4 Wake On LAN - Remote Power On

Wake On LAN (WOL) enables you to power on a server from another location over a network connection. Specifically this feature provides the ability for the network controller in the server to power the server on when a "magic packet" is received over the network from a remote system.

2.1.4.1 WOL Set Up Requirements

1. The Wake On LAN (WOL) feature in the Boot menu of the BIOS must be enabled.

For details, see Enabling Support for Wake ON LAN.

2. The server must be installed in a chassis that has an established connection to an active power source.

For details about how to install the power supply modules in a chassis and connect them to an active power source, see the documentation supplied with your chassis.

3. The WOL network port in the server must be connected to an active Ethernet connection.

For details about how to install a chassis network module and connect it to an active Ethernet connection, see the documentation supplied with your chassis.

4. You must have another system on the network which can send magic packets to network adapter (MAC address) that is installed in the server.

Typically you could use a magic packet program to send the packets over the network to wake a shutdown (WOL-enabled) server. For more details about how to send a magic packet over the network to a WOL-enabled server, refer to the documentation supplied with the magic packet program.

5. Test the WOL implementation by ensuring the magic packet sent over the network powers on the server.

If the test fails, verify that your network environment supports magic packets. For instance, some switches and routers may block magic packets.


2.2 About The BIOS

The Basic Input/Output System (BIOS) has a setup utility stored in the BIOS flash memory. The setup utility reports system information and can be used to configure the BIOS settings. The configurable data is provided with context-sensitive help and is stored in the system's battery-backed CMOS RAM. If the configuration stored in the CMOS RAM is invalid, the BIOS settings return to their default optimal values.

There are seven menus in the BIOS Setup Utility, which appear in this order: Main, Advanced, PCI, Boot, Security, Chipset, and Exit. To navigate the menus or options listed on the menu, use the arrow keys. The options or fields that you can configure on a menu appear in color. For further instructions on how to navigate and change settings in the BIOS Setup Utility, refer to the online instructions provided on the menu.

For additional information about the BIOS operations and menu options available on your server, refer to the following sections:

2.2.1 BIOS Booting and Set Up Considerations

Refer to the following sections for information when booting the BIOS and other
set up considerations:

2.2.1.1 Default BIOS Power-On Self-Test (POST) Events

At system startup, the BIOS performs a power-on self-test that checks the hardware on your server to ensure that all components are present and functioning properly. TABLE 2-1 identifies the events that can occur during BIOS POST, as well as specifies whether these event can prevent the host from powering-on.


TABLE 2-1 BIOS POST Events

Event

Cause

Boot continues on host?

User password violation

Attempt to enter password fails three times

No

Setup password violation

Attempt to enter password fails three times

No

Correctable ECC

Correctable ECC (error correction code) error detected

Does not apply

Uncorrectable ECC

Uncorrectable ECC error detected

Does not apply

No system memory

No physical memory detected in the system

No

No usable system memory

All installed memory has experienced an unrecoverable failure

No

Hard disk controller failure

No disk controller found

Yes

Keyboard failure

Keyboard cannot be initialized

Yes

Boot media failure

No removable boot media is found

Yes

No video device

No video controller is found

No

Firmware (BIOS) ROM corruption

BIOS checksum fails and the boot block is not corrupted

No

System restart

System boot initiated

Yes

Initiated by hard reset

Boot process started by hard reset

Yes

Memory initialization

Memory sizing is occurring.

System firmware progress

Does not apply

Primary processor initialization

Primary CPU initialization

System firmware progress

Does not apply

Initiated by warm reset

Boot process started by warm reset

Does not apply

Embedded controller management

Management controller initialization

Does not apply

Secondary processor(s) initialization

Secondary CPU initialization asserted

System firmware progress

Does not apply

Video initialization

When BIOS initializes keyboard

Does not apply

Keyboard controller initialization

When BIOS initializes keyboard

Does not apply

Option ROM initialization

BIOS initializes Option ROMs

System firmware progress

Does not apply

Option ROM space exhausted

BIOS cannot copy an option to the memory

Yes

User initiated system set up

End user initiated access to BIOS Setup Utility

System firmware progress

Does not apply

User initiated boot to OS

System boot initiated

System firmware progress

Does not apply

No bootable media

Nothing to boot from

No

PXE server not found

Boot error - PXE server not found

F12 key was pressed but BIOS fails to boot from PXE server

No

ACPI Power state

Soft-off power applied

Does not apply


2.2.1.2 BIOS POST F1 and F2 Errors

Each power-on-self-test (POST) diagnostic is a low-level test designed to pinpoint faults in a specific hardware component. If the POST diagnostics discloses an F1 or F2 error, it typically reports the following information about the error:

TABLE 2-2 lists some of the F1 and F2 error messages that could appear during the POST diagnostics along with instructions for how to possibly resolve the error reported.


TABLE 2-2 BIOS POST F1 and F2 Error Messages

BIOS POST Error Message

Error Type

Resolution

Uncorrectable Error Detected on Last Boot:IOH(0) Protocol Error (Please Check SP Log for more Details)

IOH error

  • Press F1 to continue.
  • Check the SP event log in ILOM for more details.

Uncorrectable Error Detected on Last Boot:IOH(0) QPI [x] Error (Please Check SP Log for more Details)

IOH error

  • Press F1 to continue.
  • Check the fault management function and the SP event log in ILOM for more details.

Note - Where QPI [x] equals 0 for QPI Link 0 or 1 for QPI Link 1.

Uncorrectable Error Detected on Last Boot:IOH(0) PCI-E [x] Error (Please Check SP Log for more Details)

IOH error

  • Press F1 to continue.
  • Check the fault management function and the SP event log in ILOM for more details.

Note - Where PCI-E [x] port number can range from 1 to 10 depending on the PCI root port on IOH.

Uncorrectable Error Detected on Last Boot:IOH(0) ESI Error (Please Check SP Log for more Details)

IOH error

  • Press F1 to continue.
  • Check the fault management function and the SP event log in ILOM for more details.

Uncorrectable Error Detected on Last Boot:IOH(0) Thermal Error (Please Check SP Log for more Details)

IOH error

  • Press F1 to continue.
  • Check the fault management function and the SP event log in ILOM for more details.

Uncorrectable Error Detected on Last Boot:IOH(0) DMA Error (Please Check SP Log for more Details)

IOH error

  • Press F1 to continue.
  • Check the SP event log for more details.

Uncorrectable Error Detected on Last Boot:IOH(0) Miscellaneous Error (Please Check SP Log for more Details)

IOH error

  • Press F1 to continue.
  • Check the fault management function and the SP event log in ILOM for more details.

Uncorrectable Error Detected on Last Boot:IOH(0) VTd Error (Please Check SP Log for more Details)

IOH error

  • Press F1 to continue.
  • Check the SP event log in ILOM for more details.

BMC Not Responding

ILOM error

  • Press F1 to continue.

Note - This error message might display if during the SP/BIOS communication an internal error occurs. This error might require you to restart the SP.

  • Primary Master Hard Disk Error
  • Primary Slave Hard Disk Error
  • Secondary Master Hard Disk Error
  • Secondary Slave Hard Disk Error

IDE/ATAPI error

  • Press F1 to continue.
  • Check the SP event log in ILOM for more details.

Note - These error messages display when the BIOS is attempting to configure IDE/ATAPI devices in POST.

Timer Error

8254 timer error

  • Press F1 to continue.
  • Check the SP event log in ILOM for more details.

Note - This type of error typically indicates an error while programming the count register of channel 2 of the 8254 timer. This could indicate a problem with system hardware.

RAM R/W test failed

Memory test failure

  • Press F1 to continue.
  • Check the SP event log in ILOM for more details.

Note - This type of error typically indicates that the RAM read/write test failed.

KBC BAT Test failed

Keyboard controller basic assurance test error

  • Press F1 to continue.
  • Check the SP event log in ILOM for more details.

Note - Keyboard controller BAT test failed. This error might indicate a problem with keyboard controller initialization.

Display memory test failed

Video display error

  • Press F1 to continue.
  • Check the SP event log in ILOM for more details.

CMOS Battery Low

CMOS battery error

  • Press F2 to enter BIOS Setup Utility to load system defaults.
  • Check the SP event log in ILOM for more details.
  • If necessary, replace CMOS battery.
  • CMOS Checksum Bad
  • CMOS Date/Time Not Set

CMOS error

  • Press F2 to enter BIOS Setup Utility to load system defaults.
  • Check the SP event log in ILOM for more details.

Password check failed

Password check error

  • Press F1 to continue.
  • Check the SP event log in ILOM for more details.

Note - This type of error indicates that the password entered does not match the password specified in the BIOS Setup Utility. This condition might occur for both Supervisor and User password verification.

Keyboard/Interface Error

Keyboard controller error

  • Press F1 to continue.
  • Check the SP event log in ILOM for more details.

Note - This type of error indicates that the Keyboard Controller failure. This error might indicate a problem with system hardware.

S.M.A.R.T error on the drive

S.M.A.R.T device error

  • Press F1 to continue.
  • Check the SP event log in ILOM for more details.

Note - S.M.A.R.T. failure messages might indicate the need to replace the storage device.


2.2.1.3 How BIOS POST Memory Testing Works

The BIOS POST memory testing is performed as follows:

1. The first megabyte of DRAM is tested by the BIOS before the BIOS code is copied from ROM to DRAM.

2. After existing out of DRAM, the BIOS performs a simple memory test (where a write/read of every location with the pattern 55aa55aa is performed).



Note - The simple memory test is performed only if Quick Boot is not enabled from the Boot Settings Configuration screen. Enabling Quick Boot causes the BIOS to skip the memory test.


3. The BIOS polls the memory controllers for both correctable and non-correctable memory errors and logs those errors into the SP.

4. The message, BMC Responding appears at the end of POST.

2.2.1.4 PCI Express ExpressModule Slot Booting Priority

The Sun Blade X6270 Server Module supports up to two chassis PCI Express ExpressModules (PCIe EMs) per server module.

The chassis slots for the PCIe Express Modules are detected by the BIOS during startup in this order: PCIe EM BLn.1 and PCIe EM BLn.0. For example, if the server is in slot 3, the BIOS boot priority is 3.1, 3.0.

See the chassis documentation for further information on PCIe EMs.

2.2.1.5 Ethernet Port Device and Driver Naming

The Sun Blade X6270 Server Module supports up to two 10/100/1000BASE-T Gigabit Ethernet ports provided by the network express modules (NEMs) installed in the chassis. The lower NEM port is NET 0 and the upper NEM port is NET 1, as shown in FIGURE 2-1.

If you have the InfiniBand NEM installed, only one Ethernet port per server module will be available.

FIGURE 2-1 Ethernet Port Chassis Labeling Designations


Figure showing the physical labeling of the Ethernet ports

For further information on NEMs, see the chassis documentation

The device naming for the Ethernet interfaces is reported differently by different interfaces and operating systems. FIGURE 2-2 for a diagram that explains the logical (operating system) and physical (BIOS) naming conventions used for each interface.



Note - If you have an InfiniBand NEM, the Net 0 interfaces only are used.


FIGURE 2-2 Sun Blade X6270 Server Module Ethernet Port Naming


Figure showing server module NIC naming as reported by various software interfaces

2.2.1.6 Ethernet Port Booting Priority

The order in which the BIOS detects the Ethernet ports during bootup, and the corresponding drivers that control those ports, are listed below:

1. NET 0 (INTEL NIC 0)

2. NET 1 (INTEL NIC 1)

2.2.2 BIOS Setup Utility Menus

TABLE 2-3 provides descriptions for the seven top-level BIOS setup menus.


TABLE 2-3 BIOS Setup Menus Summary

Menu

Description

Main

General system information.

Advanced

Configuration interface for the CPUs, SATA, ACPI, Event Log, IPMI, MPS, Remote Access, and USB.

PCI

Plug-and-Play (PnP) devices can be configured by the BIOS (default), or by the operating system (if applicable).

Boot

Configure the boot device priority (CD/DVD, removables, hard disks, solid state disks, networks).

Security

Install or change the user and supervisor passwords.

Chipset

Configuration options for the NorthBridge and SouthBridge devices.

Note that the Memory Chipkill option is enabled by default. Enabling Chipkill improves system reliability but degrades system performance under specific applications.

Exit

Save or discard changes.


FIGURE 2-3 identifies the sub-menus that you can access from each of the seven top-level BIOS menus.

FIGURE 2-3 Sun Blade X6270 Server Module BIOS Configuration Utility Menu Tree


Figure showing the BIOS Configuration Utility screens

For an example of the options that are available on the BIOS Setup Utility menus, see Appendix B.

2.2.3 Enabling Support for Common BIOS Settings

This section includes instructions for:

2.2.3.1 Accessing the BIOS Setup Utility Menus

The following procedures describes the steps for accessing the BIOS Setup Utility menus.


procedure icon  Access BIOS Setup Utility Menus

1. Power-on or power-cycle the server.

2. To enter the BIOS Setup Utility, press the F2 key while the system is performing the power-on self-test (POST).



Note - If there is an error during the boot process, you can press F1 to access the BIOS Setup Utility.


Alternatively, you can also use the following hot key combinations when accessing the BIOS Setup Utility from a serial connection:

The BIOS Setup Utility dialog appears.


Figure showing BIOS main menu

2.2.3.2 Enabling Support for Wake ON LAN

After installing the operating system, you might want to consider enabling the Wake On LAN (WOL) option in the BIOS Setup Utility. This features enables you to power on the server from another location over the network.


procedure icon  Enable or Disable WOL in BIOS

1. Access the BIOS Setup Utility menus.

For instructions, see Access BIOS Setup Utility Menus.

2. In the BIOS Setup Utility menus, use the arrow keys (or Tab key) to navigate to the Boot menu.

3. In the Boot menu, highlight the Wake ON LAN setting, and then press Enter.

A tab appears listing the Wake ON LAN options, one for each network port.

4. In the tab, enable the appropriate port (for example, NET0 WAKE ON LAN for network port 0), then press Enter and do one of the following:

or

5. Press F10 to save and exit.

6. Prior to testing whether the Wake ON LAN feature is active, ensure that all the setup requirements for Wake ON LAN have been met. For more details, see WOL Set Up Requirements.

2.2.3.3 Configuring Support for TPM

If you intend to use the Trusted Platform Module (TPM) feature set that is provided in Windows 2003 and Windows 2008, you must configure the Sun Blade X6270 Server Module to support this feature. For details, see the following procedure.



Note - TPM enables you to administer the TPM security hardware in your server. For additional information about implementing this feature, refer to the Windows Trusted Platform Module Management documentation provided by Microsoft.



procedure icon  Configure TPM Support

1. Access the BIOS Setup Utility menus.

For instructions, see Access BIOS Setup Utility Menus

2. In the BIOS Setup Utility dialog box, select the Advanced menu option.

The Advanced page appears.


Advanced menu

3. In the Advanced menu, select Trusted Computing and press Enter.

The Trusted Computing screen appears.


Trusted Computing Screen

4. In the Advanced Trusted Computing menu, select the TCG/TPM Support.

A tab appears listing the available TCG/TPM options.

5. In the tab, set the TCG/TPM Support option to Yes and click OK.



Note - Even if the TCG/TPM Support option is already set to Yes, you should complete the remaining steps in this procedure to ensure that all TPM configuration requirements are satisfied.


The updated Trusted Computing screen appears and indicating that the TCG/TPM Support setting has changed to Yes.



Note - In the above dialog box, the Execute TPM Command setting is set, by default, to [Don’t Change].


6. In the Advanced Trusted Computing menu, select the Execute TPM Command and press Enter.

A tab appears listing the available Execute TPM Command options.

7. In the tab, set the Execute TPM Command option to Enabled and click OK.

The updated Trusted Computing screen appears and indicating that the Execute TPM Command setting has changed to Enabled.

8. Press F10 to save the changes and exit BIOS.

9. To verify that TPM support is enabled, do the following:

a. Reboot the server then access the BIOS Setup Utility by pressing F2 key.

The BIOS Setup Utility screen appears.

b. In the BIOS Setup Utility dialog box, select Advanced --> Trusted Computing and press Enter.

The updated Trusted Computing screen appears indicting that TPM Support is set to Yes and TPM Enable Status is set to Enabled.

10. Press F10 to exit BIOS.

2.2.3.4 Configuring SP LAN Settings

You can assign an IP address for the server SP from the BIOS Setup Utility on the IPMI LAN configuration menu. Alternatively, you can also specify the LAN settings for the SP using ILOM. For instructions for setting the IP address in ILOM, see the Sun Integrated Lights Out Manager 2.0 User’s Guide.

To set the IP address in the BIOS Setup Utility, use the menus to navigate to the LAN configuration setting as follows: Advanced --> IPMI Configuration --> LAN Configuration. See FIGURE 2-3 for menu navigation tree.


procedure icon  Configure LAN Settings for SP

1. Access the BIOS Setup Utility menus.

For instructions, see Access BIOS Setup Utility Menus.

2. In the BIOS Setup Utility menus, use the arrow keys (or Tab key) to navigate to the Advanced menu.

3. In the Advanced menu, select IPMI Configuration.

4. In the IPMI Configuration menu, select LAN Confutation.

5. In the LAN Configuration settings dialog, use the arrow keys to select and specify the appropriate LAN configuration settings.


Figure showing BIOS advanced menu options

6. Press F10 to save the changes and exit.

2.2.3.5 Configuring Option ROM Settings in BIOS

The BIOS Option ROM is 128 kbytes. Of these 128 kbytes, approximately 80 kbytes are used by the VGA controller, the disk controller, and the network interface card. Approximately 48 kbytes remain for the Option ROM.


procedure icon  Enable or Disable Option ROM Settings

1. Access the BIOS Setup Utility menus.

For instructions, see Access BIOS Setup Utility Menus.

2. In the BIOS Setup Utility menus, use the arrow keys (or Tab key) to navigate to the Boot menu.

The Boot menu appears.

3. In the Boot menu, highlight the Option ROM setting, and then press Enter.


Figure showing BIOS boot options

4. In the Boot menu listing the Option ROM settings, highlight the applicable Option ROM setting to modify, then press Enter.

A tab appears listing the available settings.

5. In the tab, do one of the following:

or

6. Press F10 to save and exit.

2.2.4 Updating the BIOS Firmware

The BIOS is updated whenever you update the ILOM SP firmware. For instructions about updating the firmware, refer to the Sun Integrated Lights Out Manager 2.0 User’s Guide (820-1188).