User`s guide
Table Of Contents
- NovaScale 4020 User's Guide
- Preface
- Contents
- 1 System Description
- 2 Board Set Description
- 3 Configuration Software and Utilities
- Utilities / Drivers on Resource CD
- Power-on Sequence and Power-on Self-Test (POST)
- Extensible Firmware Interface Boot Manager
- The Extensible Firmware Interface (EFI) Shell
- BIOS Setup
- LSI Logic* SCSI Utility
- System Maintenance Utility
- EFI Platform Diagnostic Tests
- EFI Service Partition
- Console Redirection
- Terminal Mode
- Shutting Down the Server
- Servicing the System (basic knowledge)
- A Warning and Cautions
- B Working Inside the System
- C Hot-swapping System Components
- D Servicing the Electronics Bay
- Safety Warnings
118 NovaScale 4020 User’s Guide
Parameter # Parameter Data (non-volatile unless otherwise noted)
Boot flags
(semi-volatile)
[1]
(continued)
5 Data 4
[7:4] - Reserved
[3] - BIOS Shared Mode Override
Can be used to request BIOS to temporarily place the channel into Shared
access mode.
Per the recommendations in the IPMI specification, Shared access would
cause the baseboard serial controller to both remain enabled after POST/start
of OS boot, while also allowing the BMC to be accessible. This can be useful
when booting to an alternative device such as a Diagnostic Partition since it
means the partition can use the serial port but that communication with the
BMC can remain available if the partition software fails.
1b = Request BIOS to temporarily set the access mode for the channel
specified in parameter #6 to Shared. This is typically accomplished by
sending a Set Channel Access command to set the volatile access
mode setting in the BMC
0b = No request to BIOS to change present access mode setting
[2:0] - BIOS Mux Control Override
Can be used to request BIOS to force a particular setting of the serial/modem
mux at the conclusion of POST / start of OS boot. This override takes
precedence over the mux settings for the access mode even if the BIOS
Shared Mode Override is set.
000b = BIOS uses recommended setting of the mux at the end of POST.
001b = Requests BIOS to force mux to BMC at conclusion of POST/start of
OS
-
boot. If honored, this overrides the recommended setting of the
mux at the end of POST.
010b = Requests BIOS to force mux to system at conclusion of POST/start of
OS-boot. If honored, this overrides the recommended setting of the
mux at the end of POST.
Data 5 - Reserved
Boot initiator
info
(semi-volatile)
[1]
6
Address & Identity information for the party that initiated the boot. The party that
initiates the boot writes this parameter and the boot info acknowledge parameter
prior to issuing the command that causes the system power up, power cycle, or
reset. This data is written by the remote console application, not the BMC.
Boot Source
Data 1- Channel Number. Channel that delivers the boot command (e.g. chassis
control). BIOS and boot software (e.g. service partition or OS loader) can
use the Get Channel Sessions to find out information about the party that
initiated the boot
[7:4] - Reserved
[3:0] - Channel Number
Data 2:5 - Session ID. Session ID for session that the boot command will be
issued over. This value can be used with the Get Channel Sessions
command to find out information about the party that initiated the boot
Data 6:9 - Boot Info Timestamp. This timestamp is used to help software
determine whether the boot information is stale. A service partition or
OS loader may elect to ignore the boot information if it is older than
expected
The boot initiator should load this field with the timestamp value from the
IPMI Get SEL Time command prior to issuing the command that initiates
the boot.