CHAPTER 1

OpenBoot 3.x Commands

---

This chapter describes the OpenBoot^(TM) 3.x commands for the Sun Enterprise 3x00, 4x00, 5x00, and 6x00 servers.

---

Environmental Monitoring

Use the following commands for environmental monitoring:

· disable-environmental-monitor
· enable-environmental-monitor

disable-environmental-monitor

Usage

disable-environmental-monitor ( -- )

Purpose

To stop monitoring power supply status, board temperatures, and board hot plug while the screen displays the ok prompt.

enable-environmental-monitor

Usage

enable-environmental-monitor ( -- )

Purpose

To start monitoring power supply status, board temperatures, and board hot plug while the screen displays the ok prompt.

---

Note - This command is enabled by default.

---

---

Messages Indicating Environmental Conditions

The following system messages indicate environmental conditions:

PROM NOTICE: Overtemp detected on board <n>. PROM NOTICE: System has cooled down. PROM WARNING: Board <n> is too hot. PROM NOTICE: Insufficient power detected. PROM NOTICE: Power supply restored. PROM NOTICE: Board insert detected. PROM NOTICE: Reset Initiated...

If a board temperature is above a predetermined temperature threshold for that board type, the OpenBoot PROM (OBP) initiates a reset. This results in POST disabling the faulty board.

If Insufficient power detected is not fixed in 30 seconds, then the OBP initiates a reset to enable POST to deconfigure the necessary boards.

If a board insert is detected, the OBP turns the reset flag on. This causes the boot command to reset the system and POST to attach the board to the system.

---

Resetting and Power Cycling the System From a Remote Console

You can reset the system or power cycle from a remote console under these conditions:

• The console must be connected to port A on the clock board.
• The key switch must be in either the On or Diagnostic setting. If it is in the Secure or Off position, remote key sequences and button resets are ignored.
• Security features (such as OpenBoot security-mode) are disabled.
• Type slowly, no faster than 0.5 seconds and no slower than 5 seconds between characters.

TABLE 1-1 lists remote console commands, which are useful for resetting the system under general conditions. The remote XIR reset command is useful in software development and debugging. For a discussion of this command, see "Externally Initiated Reset XIR.

TABLE 1-1

Command	Keyboard Key Sequence
Remote power off/on	Return Return ~ Control-Shift-p
Remote system reset	Return Return ~ Control-Shift-r
Remote XIR (CPU) reset	Return Return ~ Control-Shift-x
Key: Return = ASCII 0d hexadecimal ~ = ASCII 7e hexadecimal Control-Shift-p = 10 hexadecimal Control-Shift-r = 12 hexadecimal Control-Shift-x = 18 hexadecimal

---

Note - The remote console logic circuit continues to receive power, even if you have commanded system power off.

---

Since the remote console logic looks for certain patterns on the ttya line in the hardware that can be used to reset the machine, it is important that only authorized personnel have access to the ttya serial port.

---

Externally Initiated Reset XIR

If a hard hang occurs on a system, use XIR to reset and get information about the system state at the time of the hard hang.

· To Initiate an XIR:

· Use either the XIR button on the clock board or the remote console XIR sequence.

When an XIR occurs, memory is cleared but some CPU state is saved.

· To Display This XIR Information:

· Type the following command at the ok prompt immediately after the XIR:

ok .xir-state-all

The output displays the CPU state for each CPU:

#1 ok .xir-state-all CPU ID#1 TL=1 TT=3 TPC=e0028688 TnPC=e0028688 TSTATE=9900001e06 CPU ID#5 TL=1 TT=3 TPC=e002755c TnPC=e0027560 TSTATE=4477001e03

---

Note - The XIR does not override the NVRAM auto-boot? variable.

---

Where:

TL	Trap level
TT	Trap type
TPC	Trap program counter
TSate	Trap state

---

Hardware Watchdog

The Sun Enterprise xx00 family of servers provide the ability to enable a hardware timer that will hard-reset the system if it times out. To enable the use of this feature, watchdog_enable must be set to 1 in /etc/system.

---

Flash PROM Management

The following OpenBoot 3.x commands are used in flash PROM management:

· flash-update-system
· prom-copy
· update-proms

flash-update-system

Usage

flash-update-system ( -- )

Purpose

To download the default flash images on all the boards in the system.

---

Note - The default device used is the one pointed to by "net."

---

The default image names are described in TABLE 1-2.

TABLE 1-2

Board Type	Image File Name	Description
CPU board PROMs	cpu.flash	N/A
1	io2sbus.flash	Dual SBus I/O board
2	io1sbus.flash	Single SBus I/O board with graphics
3	pci.flash	Dual PCI I/O board
4	io2sbus+.flash	Dual SBus I/O board (SOC+ chip)
5	io1sbus+.flash	Single SBus I/O board with graphics (SOC+ chip)

---

Note - This command does not update boards in low power mode.

---

prom-copy

Usage

prom-copy ( src dst -- )

Purpose

To copy a flash PROM from board src to board dst. Source (src) and Destination (dst) are specified by slot number.

update-proms

Usage

update-proms ( -- )

Purpose

To synchronize the latest copy of each type of PROM on all other boards of the same type.

This command copies the latest version of each PROM (CPU and I/O boards) to all other boards of the same type. This results in all boards of the same type having the latest (same) PROM.

---

System Configuration and Diagnostic Information

To print system configuration and diagnostic information, use prtdiag instead of using an OpenBoot command. The diagnostic information displayed lists the failed field replaceable units (FRUs) in the system. For more information on prtdiag, see the prtdiag man page.

prtdiag(1M) Options

-v lists the most recent AC Power failure, the most recent hardware fatal error information, and, if applicable, environmental status.

-l logs its output to syslogd(1M) only if failures or errors exist in the system.

---

TOD Clock Management

This section describes the following commands related to time-of-day (TOD) clock management, which includes NVRAM:

· copy-clock-tod-to-io-boards
· copy-io-board-tod-to-clock-tod

copy-clock-tod-to-io-boards

Usage

copy-clock-tod-to-io-boards

Purpose

To copy the contents of the clock board NVRAM and the contents of the TOD clock to all good I/O boards in the system.

This occurs automatically if all of the following conditions are true:

• There is a functioning clock board in the system.
• Its contents match that of at least one I/O board in the system.

copy-io-board-tod-to-clock-tod

Usage

copy-io-board-tod-to-clock-tod  ( src -- )

Purpose

To update the contents of a clock board (probably new) with the contents from one of the backup I/O board copies.

---

Note - This may have to be done if the clock board was replaced and the user wants to restore its original NVRAM.

---

---

Specific NVRAM Variables

This section describes the following NVRAM variables:

· configuration-policy
· disabled-board-list
· disabled-memory-list
· memory-interleave
· sbus-probe-default
· sbus-specific-probe

configuration-policy

Variable Name	Value	Default Value
configuration-policy	component	component

This variable determines the configuration policy. When a faulty component is detected, the value options are as follows:

Hardware Device	Description
Component (default)	Disable only what failed.
System	Stop the system in POST if any component failed tests.
Board	Disable the entire board that contains the failed component.

disabled-board-list

---

Note - The master board (the CPU board in the lowest slot) will not be disabled if it is put in the disabled-board-list. The operating system displays a warning as follows: WARNING: Disabled board 0 was really active

---

A valid example is:

ok setenv disabled-board-list 45	(disable boards in slots 4 and 5)
ok setenv disabled-board-list 7af	(disable boards in slots 7, 10, and 15)

This is a list of boards that are not to be used by the system. These boards are put in low-power mode on the next reset and remain there until the list is reset to null, and the system is reset.

To reset the list to null, type:

ok set-default disabled-board-list

For a step-by-step procedure on how to disable a defective board, see Chapter 2, "Disabling Hardware".

disabled-memory-list

This command lists the boards with memory on them that will not be used. This variable takes effect on the next reset or power-on. For both of the above variables, the list is a sequence of any number of boards 0 through 9 and a through f.

An example follows:

ok setenv disabled-memory-list 234f

The above command indicates that memory on the CPU/Memory board that is plugged in the system slot numbers 2, 3, 4, and f will be disabled.

To reset the list to null, type:

ok set-default disabled-memory-list

memory-interleave

Variable Name	Value	Default Value
memory-interleave	max	max

This variable determines how the memory on various boards is to be interleaved. The default value is maximum interleaving. When it is set to "min," no interleaving is required. This takes effect on the next reset or power-on.

sbus-probe-default

Variable Name	Value
sbus-probe-default	d3120

This variable defines the SBus device probe order on an I/O board per SBus, where:

d	On-board SOC
3	On-board FEPS
0-2	SBus slots 0, 1, and 2

The device probe order on a Type 1 I/O board is as follows, since the five SBus devices are divided between two SBuses:

lo sbus	d, 1, 2
hi sbus	3,0

However, on a Type 2 I/O board, since there is only 1 SBus, the probe order is:

lo sbus	absent	(UPA/FFB Port in its place)
hi sbus	d, 3, 2, 0	(no slot 1)

To change the default probe order to 123d0, type:

ok setenv sbus-probe-default 123d0

Remember that this changes the default probe order for all boards in the system. You can also use this to skip over an SBus slot, by not including it in the list of devices to probe. To change the probe order for a specific board, use the sbus-specific-probe variable.

sbus-specific-probe

Variable Name	Value
sbus-specific-probe	1:d120

This variable controls the SBus probe order on a given list of boards. To set the probe order as 320 on an I/O board in slot 4, type:

ok setenv sbus-specific-probe 4:320

The number preceding the colon ( : ) is the slot number; the numbers following it are the SBus device numbers in the desired probe order. All unlisted I/O boards in the system use the default probe order as defined by the sbus-default-probe NVRAM variable.

Multiple boards can be defined by this variable as follows:

ok setenv sbus-specific-probe 4:320 6:d3210 7:0123d