Netra 240 Server System Administration Guide

This chapter describes the diagnostics tools available to the Netra 240 server. The chapter contains the following sections:

• Overview of Diagnostic Tools
• System Prompts
• Advanced Lights Out Manager
• Power-On Self-Test Diagnostics
• OpenBoot Commands
• OpenBoot Diagnostics
• Operating System Diagnostic Tools
• Recent Diagnostic Test Results
• OpenBoot Configuration Variables
• Automatic System Recovery

---

Overview of Diagnostic Tools

Sun provides a range of diagnostic tools for use with the Netra 240 server, as summarized in the following table.

---

System Prompts

The following default server prompts are used by the Netra 240 server:

• ok--OpenBoot PROM prompt
• sc>--Advanced Lights Out Manager (ALOM) prompt
• #--Solaris software superuser (Bourne and Korn shell) prompt

FIGURE 1-1 shows the relationship between the three prompts and how to change from one to the other.

FIGURE 1-1 System Prompt Flow

The following commands are in the flow diagram in FIGURE 1-1:

• ALOM commands: console, reset, break
• Escape sequence: #.
• Solaris software commands: shutdown, halt, init 0
• OpenBoot commands: go, boot

---

Advanced Lights Out Manager

Sun Advanced Lights Out Manager (ALOM) for the Netra 240 server provides a series of LED status indicators. This section details the meaning of their status and how to turn them on and off. For more information on ALOM, see Chapter 3.

FIGURE 1-2 Location of Front Panel Indicators

Server Status Indicators

The server has three LED status indicators. They are located on the front bezel (FIGURE 1-2) and are repeated on the rear panel. A summary of the indicators is provided in TABLE 1-2.

You can turn the Locator LED on and off either from the system console or the ALOM command-line interface (CLI).

Do one of the following:

• As superuser, type:


# /usr/sbin/locator

• At the ALOM command-line interface, type:


sc> showlocator

Do one of the following:

• As superuser, type:


# /usr/sbin/locator -n

• At the ALOM command-line interface, type:


sc> setlocator on

Do one of the following:

• As superuser, type:


# /usr/sbin/locator -f

• At the ALOM command-line interface, type:


sc> setlocator off

Alarm Status Indicators

The dry contact alarm card has four LED status indicators that are supported by ALOM. They are located vertically on the front bezel (FIGURE 1-2). Information about the alarm indicators and dry contact alarm states is provided in TABLE 1-3. For more information about alarm indicators, see the Sun Advanced Lights Out Manager Software User's Guide for the Netra 240 Server (part number 817-3174). For more information about an API to control the alarm indicators, see Appendix A.

In all cases when the user sets an alarm, a message is displayed on the console. For example, when the critical alarm is set, the following message is displayed on the console:
Note that in some instances when the critical alarm is set, the associated alarm indicator is not lit. This implementation is subject to change in future releases
(see Footnote iii of TABLE 1-3).

SC Alert: CRITICAL ALARM is set 

---

Power-On Self-Test Diagnostics

Power-on self-test (POST) is a firmware program that helps determine whether a portion of the system has failed. POST verifies the core functionality of the system, including the CPU module(s), motherboard, memory, and some on-board I/O devices. The software then generates messages that can be useful in determining the nature of a hardware failure. You can run POST even if the system is unable to boot.

POST detects most system faults and is located in the motherboard OpenBoot PROM. You can program the OpenBoot software to run POST at power-on by setting two environment variables: the diag-switch? and the diag-level flag. These two variables are stored on the system configuration card (SCC).

POST runs automatically when the system power is applied, or following an automatic system reset, if all of the following conditions apply:

• diag-switch? is set to true (default is false).
• diag-level is set to min, max or menus (default is min).
• post-trigger matches the class of reset (default is power-on-reset).

If diag-level is set to min or max, POST performs an abbreviated or extended test, respectively.

If diag-level is set to menus, a menu of all the tests executed at power up is displayed.

POST diagnostic and error message reports are displayed on a console.

Controlling POST Diagnostics

You control POST diagnostics (and other aspects of the boot process) by setting OpenBoot configuration variables. Changes to OpenBoot configuration variables take effect only after the system is restarted. TABLE 1-4 lists the most important and useful of these variables. You can find instructions for changing OpenBoot configuration variables in To View and Set OpenBoot Configuration Variables.

Once POST diagnostics have finished running, POST reports back the status of each test that was run to the OpenBoot firmware. Control then reverts back to the OpenBoot firmware code.

If POST diagnostics do not uncover a fault, and your server still does not start up, run OpenBoot diagnostics tests.

1. Go to the ok prompt.

2. Type:

ok setenv diag-switch? true

3. Type:

ok setenv diag-level value

Where value is min, max, or menus, depending on the quantity of diagnostic information you want to see.

4. Type:

ok reset-all

The system runs POST diagnostics if post-trigger is set to user-reset. Status and error messages are displayed in the console window. If POST detects an error, it displays an error message describing the failure.

5. When you have finished running POST, restore the value of diag-switch? to false by typing:

ok setenv diag-switch? false

Resetting diag-switch? to false minimizes boot time.

---

OpenBoot Commands

OpenBoot commands are commands you type from the ok prompt. OpenBoot commands that can provide useful diagnostic information are as follows:

• probe-scsi and probe-scsi-all
• probe-ide
• show-devs

probe-scsi and probe-scsi-all Commands

The probe-scsi and probe-scsi-all commands diagnose problems with the SCSI devices.

Caution - If you used the haltcommand or the Stop-A key sequence to reach the okprompt, issuing the probe-scsior probe-scsi-allcommand can hang the system.

The probe-scsi command communicates with all SCSI devices connected to on-board SCSI controllers. The probe-scsi-all command also accesses devices connected to any host adapters installed in PCI slots.

For any SCSI device that is connected and active, the probe-scsi and probe-scsi-all commands display its loop ID, host adapter, logical unit number, unique world-wide name (WWN), and a device description that includes type and manufacturer.

The following sample output is from the probe-scsi command.

{1} ok probe-scsi

Target 0 

  Unit 0   Disk     SEAGATE ST373307LSUN72G 0207

Target 1 

  Unit 0   Disk     SEAGATE ST336607LSUN36G 0207

{1} ok 

The following sample output is from the probe-scsi-all command.

{1} ok probe-scsi-all

/pci@1c,600000/scsi@2,1

/pci@1c,600000/scsi@2

Target 0 

  Unit 0   Disk     SEAGATE ST373307LSUN72G 0207

Target 1 

  Unit 0   Disk     SEAGATE ST336607LSUN36G 0207

{1} ok 

probe-ide Command

The probe-ide command communicates with all Integrated Drive Electronics (IDE) devices connected to the IDE bus. This is the internal system bus for media devices such as the DVD drive.

Caution - If you used the haltcommand or the Stop-A key sequence to reach the okprompt, issuing the probe-idecommand can hang the system.

The following sample output is from the probe-ide command.

{1} ok probe-ide

Device 0  ( Primary Master ) 

         Not Present

  Device 1  ( Primary Slave ) 

         Not Present

  Device 2  ( Secondary Master ) 

         Not Present

  Device 3  ( Secondary Slave ) 

         Not Present

{1} ok 

show-devs Command

The show-devs command lists the hardware device paths for each device in the firmware device tree. CODE EXAMPLE 1-4 shows some sample output.

/pci@1d,700000

/pci@1c,600000

/pci@1e,600000

/pci@1f,700000

/memory-controller@1,0

/SUNW,UltraSPARC-IIIi@1,0

/memory-controller@0,0

/SUNW,UltraSPARC-IIIi@0,0

/virtual-memory

/memory@m0,0

/aliases

/options

/openprom

/chosen

/packages

/pci@1d,700000/network@2,1

/pci@1d,700000/network@2

/pci@1c,600000/scsi@2,1

/pci@1c,600000/scsi@2

/pci@1c,600000/scsi@2,1/tape

/pci@1c,600000/scsi@2,1/disk

/pci@1c,600000/scsi@2/tape

/pci@1c,600000/scsi@2/disk     

/pci@1e,600000/ide@d

/pci@1e,600000/usb@a

/pci@1e,600000/pmu@6

/pci@1e,600000/isa@7

/pci@1e,600000/ide@d/cdrom

/pci@1e,600000/ide@d/disk.........

1. Halt the system to reach the ok prompt.

Inform users before you shut down the system.

2. Type the appropriate command at the console prompt.

---

OpenBoot Diagnostics

Like POST diagnostics, OpenBoot diagnostics code is firmware-based and resides in the Boot PROM.

1. Type:

ok setenv diag-switch? true

ok setenv auto-boot? false

ok reset-all

2. Type:

ok obdiag

This command displays the OpenBoot diagnostics menu.

ok obdiag

_____________________________________________________________________________

|                                 o b d i a g                                |

|_________________________ __________________________________________________|

|                         |                         |                        |

|  1 flashprom@2,0        |  2 i2c@0,320            |  3 ide@d               |

|  4 network@2            |  5 network@2            |  6 network@2,1         |

|  7 network@2,1          |  8 rmc-comm@0,3e8       |  9 rtc@0,70            |

| 10 scsi@2               | 11 scsi@2,1             | 12 serial@0,2e8        |

| 13 serial@0,3f8         |                         |                        |

|_________________________|_________________________|________________________|

|   Commands: test test-all except help what setenv set-default exit         |

|____________________________________________________________________________|

3. Type:

obdiag> test n

Where n represents the number corresponding to the test you want to run.

A summary of the tests is available. At the obdiag> prompt, type:

obdiag> help

Controlling OpenBoot Diagnostics Tests

Most of the OpenBoot configuration variables you use to control POST (see TABLE 1-4) also affect OpenBoot diagnostics tests.

• Use the diag-level variable to control the OpenBoot diagnostics testing level.
• Use test-args to customize how the tests run.

By default, test-args is set to contain an empty string. You can modify test-args using one or more of the reserved keywords shown in TABLE 1-5.

If you want to customize the OpenBoot diagnostics testing, you can set test-args to a comma-separated list of keywords, as in this example:

ok setenv test-args debug,loopback,media

test and test-all Commands

You can also run OpenBoot diagnostics tests directly from the ok prompt. To do this, type the test command, followed by the full hardware path of the device (or set of devices) to be tested. For example:

ok test /pci@x,y/SUNW,qlc@2

To customize an individual test, you can use test-args, as follows:

ok test /usb@1,3:test-args={verbose,debug}

This syntax affects only the current test without changing the value of the
test-args OpenBoot configuration variable.

You can test all the devices in the device tree with the test-all command:

ok test-all

CODE EXAMPLE 1-5 displays a sample OpenBoot diagnostics test report where all tests have passed.

Hit the spacebar to interrupt testing

Testing /pci@1e,600000/isa@7/flashprom@2,0 ............................passed

Testing /pci@1e,600000/isa@7/i2c@0,320 ................................passed

Testing /pci@1e,600000/ide@d ..........................................passed

Testing /pci@1f,700000/network@2 ......................................passed

Testing /pci@1d,700000/network@2 ......................................passed

Testing /pci@1f,700000/network@2,1 ....................................passed

Testing /pci@1d,700000/network@2,1 ....................................passed

Testing /pci@1e,600000/isa@7/rmc-comm@0,3e8 ...........................passed

Testing /pci@1e,600000/isa@7/rtc@0,70 .................................passed

Testing /pci@1c,600000/scsi@2 .........................................passed

Testing /pci@1c,600000/scsi@2,1 .......................................passed

Testing /pci@1e,600000/isa@7/serial@0,2e8 .............................passed

Testing /pci@1e,600000/isa@7/serial@0,3f8 .............................passed

Pass:1 (of 1) Errors:0 (of 0) Tests Failed:0 Elapsed Time: 0:0:0:25

If you specify a path argument to test-all, only the specified device and its children are tested. The following example shows the command to test the USB bus and all devices with self-tests that are connected to the USB bus:

ok test-all /pci@9,700000/usb@1,3

OpenBoot Diagnostics Error Messages

OpenBoot diagnostics error results are reported in a tabular format that contains a short summary of the problem, the hardware device affected, the subtest that failed, and other diagnostic information. CODE EXAMPLE 1-6 displays a sample OpenBoot diagnostics error message.

Testing /pci@1e,600000/isa@7/flashprom@2,0 

   ERROR   : FLASHPROM CRC-32 is incorrect

   SUMMARY : Obs=0x729f6392 Exp=0x3d6cdf53 XOR=0x4ff3bcc1 Addr=0xfeebbffc 

   DEVICE  : /pci@1e,600000/isa@7/flashprom@2,0

   SUBTEST : selftest:crc-subtest

   MACHINE : Netra 240

   SERIAL# : 52965531 

   DATE    : 03/05/2003 01:33:59  GMT 

   CONTR0LS: diag-level=max test-args=

Error: /pci@1e,600000/isa@7/flashprom@2,0 selftest failed, return code = 1

Selftest at /pci@1e,600000/isa@7/flashprom@2,0 (errors=1) .............

failed

Pass:1 (of 1) Errors:1 (of 1) Tests Failed:1 Elapsed Time: 0:0:0:27

---

Operating System Diagnostic Tools

When the system passes OpenBoot diagnostics tests, it attempts to boot the Solaris OS. Once the server is running in multiuser mode, you have access to the software-based diagnostic tools and the SunVTS software. These tools enable you to monitor the server, exercise it, and isolate faults.

In addition to the tools just mentioned, you can refer to error and system message log files and to Solaris software information commands.

Error and System Message Log Files

Error and other system messages are saved in the /var/adm/messages file. Messages are logged to this file from many sources, including the operating system, the environmental control subsystem, and various software applications.

Solaris Software System Information Commands

The following Solaris software system information commands display data that you can use when assessing the condition of a Netra 240 server:

• prtconf
• prtdiag
• prtfru
• psrinfo
• showrev

This section describes the information that these commands give you. For more information about using these commands, refer to the appropriate man page.

prtconf Command

The prtconf command displays the Solaris software device tree. This tree includes all the devices probed by OpenBoot firmware, as well as additional devices, such as individual disks that only the operating system software recognizes. The output of prtconf also includes the total size of system memory. CODE EXAMPLE 1-7 shows an excerpt of prtconf output.

# prtconf

System Configuration:  Sun Microsystems  sun4u

Memory size: 5120 Megabytes

System Peripherals (Software Nodes):

SUNW,Netra-240

    packages (driver not attached)

        SUNW,builtin-drivers (driver not attached)

        deblocker (driver not attached)

        disk-label (driver not attached)

        terminal-emulator (driver not attached)

        dropins (driver not attached)

        kbd-translator (driver not attached)

        obp-tftp (driver not attached)

        SUNW,i2c-ram-device (driver not attached)

        SUNW,fru-device (driver not attached)

        ufs-file-system (driver not attached)

    chosen (driver not attached)

    openprom (driver not attached)

        client-services (driver not attached)

    options, instance #0

    aliases (driver not attached)

    memory (driver not attached)

    virtual-memory (driver not attached)

    SUNW,UltraSPARC-IIIi (driver not attached)

    memory-controller, instance #0

    SUNW,UltraSPARC-IIIi (driver not attached)

    memory-controller, instance #1

    pci, instance #0........

The prtconf command -p option produces output similar to that of the OpenBoot
show-devs command. This output lists only those devices compiled by the system firmware.

prtdiag Command

The prtdiag command displays a table of diagnostic information that summarizes the status of system components. The display format used by the prtdiag command can vary depending on what version of the Solaris OS is running on your system. The following code example is an excerpt of some of the output produced by prtdiag on a functional Netra 240 server running Solaris software.

# prtdiag

System Configuration: Sun Microsystems  sun4u Netra 240

System clock frequency: 160 MHZ

Memory size: 2GB 

==================================== CPUs ====================================

                      E$          CPU     CPU       Temperature         Fan

       CPU  Freq      Size        Impl.   Mask     Die    Ambient   Speed   Unit

       ---  --------  ----------  ------  ----  --------  --------  -----   ----

     MB/P0  1280 MHz  1MB         US-IIIi   2.3     -     -  

     MB/P1  1280 MHz  1MB         US-IIIi   2.3     -     - 

================================= IO Devices =================================

     Bus   Freq

Brd  Type  MHz   Slot        Name                          Model

---  ----  ----  ----------  ----------------------------  --------------------

 0   pci    66            2  network-pci14e4,1648.108e.16+                    

 0   pci    66            2  network-pci14e4,1648.108e.16+                    

 0   pci    66            2  scsi-pci1000,21.1000.1000.1 +                    

 0   pci    66            2  scsi-pci1000,21.1000.1000.1 +                    

 0   pci    66            2  network-pci14e4,1648.108e.16+                    

 0   pci    66            2  network-pci14e4,1648.108e.16+                    

 0   pci    33            7  isa/serial-su16550 (serial)                      

 0   pci    33            7  isa/serial-su16550 (serial)                      

 0   pci    33            7  isa/rmc-comm-rmc_comm (seria+                    

 0   pci    33           13  ide-pci10b9,5229.c4 (ide) 

============================ Memory Configuration ============================

Segment Table:

-----------------------------------------------------------------------

Base Address       Size       Interleave Factor  Contains

-----------------------------------------------------------------------

0x0                1GB               1           GroupID 0 

0x1000000000       1GB               1           GroupID 0 

Memory Module Groups:

--------------------------------------------------

ControllerID   GroupID  Labels

--------------------------------------------------

0              0        MB/P0/B0/D0,MB/P0/B0/D1

Memory Module Groups:

--------------------------------------------------

ControllerID   GroupID  Labels

--------------------------------------------------

1              0        MB/P1/B0/D0,MB/P1/B0/D1

In addition to the information in CODE EXAMPLE 1-8, prtdiag with the verbose option (-v) also reports on front panel status, disk status, fan status, power supplies, hardware revisions, and system temperatures (see CODE EXAMPLE 1-9).

---------------------------------------------------------------

Location   Sensor      Temperature  Lo LoWarn HiWarn  Hi Status

---------------------------------------------------------------

MB         T_ENC           22C     -7C   -5C   55C   58C   okay

MB/P0      T_CORE          57C     -       -    110C  115C okay

MB/P1      T_CORE          54C     -       -    110C  115C okay

PS0        FF_OT           -       -       -    -       -  okay

PS1        FF_OT           -       -       -    -       -  okay

In the event of an overtemperature condition, prtdiag reports an error in the Status column (CODE EXAMPLE 1-10).

---------------------------------------------------------------

Location   Sensor      Temperature  Lo LoWarn HiWarn  Hi Status

---------------------------------------------------------------

MB         T_ENC           22C    -7C    -5C     55C   58C okay

MB/P0      T_CORE         118C     -       -    110C  115C failed

MB/P1      T_CORE         112C     -       -    110C  115C warning

PS0        FF_OT           -       -       -    -       -  okay

PS1        FF_OT           -       -       -    -       -  okay

Similarly, if a particular component fails, prtdiag reports a fault in the appropriate status column (CODE EXAMPLE 1-11).

Fan Speeds:

-----------------------------------------

Location       Sensor      Status   Speed

-----------------------------------------

MB/P0/F0       RS          failed   0 rpm         

MB/P0/F1       RS          okay     3994 rpm         

F2             RS          okay     2896 rpm         

PS0            FF_FAN      okay         

F3             RS          okay     2576 rpm         

PS1            FF_FAN      okay         

---------------------------------

prtfru Command

The Netra 240 server maintains a hierarchical list of all field-replaceable units (FRUs) in the system, as well as specific information about various FRUs.

The prtfru command can display this hierarchical list, as well as data contained in the serial electrically-erasable programmable read-only memory (SEEPROM) devices located on many FRUs. CODE EXAMPLE 1-12 shows an excerpt of a hierarchical list of FRUs generated by the prtfru command with the -l option.

# prtfru -l

/frutree

/frutree/chassis (fru)

/frutree/chassis/MB?Label=MB

/frutree/chassis/MB?Label=MB/system-board (container)

/frutree/chassis/MB?Label=MB/system-board/SC?Label=SC

/frutree/chassis/MB?Label=MB/system-board/SC?Label=SC/sc (fru)

/frutree/chassis/MB?Label=MB/system-board/BAT?Label=BAT

/frutree/chassis/MB?Label=MB/system-board/BAT?Label=BAT/battery (fru)

/frutree/chassis/MB?Label=MB/system-board/P0?Label=P0

/frutree/chassis/MB?Label=MB/system-board/P0?Label=P0/cpu (fru)

/frutree/chassis/MB?Label=MB/system-board/P0?Label=P0/cpu/F0?Label=F0

/frutree/chassis/MB?Label=MB/system-board/P0?Label=P0/cpu/F0?Label=F0/fan-unit 

(fru)

/frutree/chassis/MB?Label=MB/system-board/P0?Label=P0/cpu/F1?Label=F1

/frutree/chassis/MB?Label=MB/system-board/P0?Label=P0/cpu/F1?Label=F1/fan-unit 

(fru)........

CODE EXAMPLE 1-13 shows an excerpt of SEEPROM data generated by the prtfru command with the -c option. This output displays only the containers and their data and does not print the FRU tree hierarchy.

# prtfru -c

/frutree/chassis/MB?Label=MB/system-board (container)

   SEGMENT: SD

      /ManR

      /ManR/UNIX_Timestamp32: Mon Dec  2 19:47:38 PST 2002

      /ManR/Fru_Description: FRUID,INSTR,M'BD,2X1.28GHZ,CPU

      /ManR/Manufacture_Loc: Hsinchu,Taiwan

      /ManR/Sun_Part_No: 3753120

      /ManR/Sun_Serial_No: 000615

      /ManR/Vendor_Name: Mitac International

      /ManR/Initial_HW_Dash_Level: 02

      /ManR/Initial_HW_Rev_Level: 0E

      /ManR/Fru_Shortname: MOTHERBOARD

      /SpecPartNo: 885-0076-11

/frutree/chassis/MB?Label=MB/system-board/P0?Label=P0/cpu/B0?Label=B0/bank/D0?La

bel=D0/mem-module (container)

/frutree/chassis/MB?Label=MB/system-board/P0?Label=P0/cpu/B0?Label=B0/bank/D1?La

bel=D1/mem-module (container)........

Data displayed by the prtfru command varies depending on the type of FRU. In general, it includes the following:

• FRU description
• Manufacturer name and location
• Part number and serial number
• Hardware revision levels

psrinfo Command

The psrinfo command displays the date and time that each CPU is introduced online. With the verbose (-v) option, the command displays additional information about the CPUs, including their clock speed. CODE EXAMPLE 1-14 shows sample output from the psrinfo command with the -v option.

# psrinfo -v

Status of processor 0 as of: 07/28/2003 14:43:29

  Processor has been on-line since 07/21/2003 18:43:37.

  The sparcv9 processor operates at 1280 MHz,

        and has a sparcv9 floating point processor.

Status of processor 1 as of: 07/28/2003 14:43:29

  Processor has been on-line since 07/21/2003 18:43:36.

  The sparcv9 processor operates at 1280 MHz,

        and has a sparcv9 floating point processor

showrev Command

The showrev command displays revision information for the current hardware and software. CODE EXAMPLE 1-15 shows sample output from the showrev command.

# showrev

Hostname: vsp78-36

Hostid: 8328c87b

Release: 5.8

Kernel architecture: sun4u

Application architecture: sparc

Hardware provider: Sun_Microsystems

Domain: vsplab.SFBay.Sun.COM

Kernel version: SunOS 5.8 Generic 108528-18 November 2002

When used with the -p option, the showrev command displays installed patches. CODE EXAMPLE 1-16 shows a partial sample output from the showrev command with the -p option.

Patch: 109729-01 Obsoletes:  Requires:  Incompatibles:  Packages: SUNWcsu

Patch: 109783-01 Obsoletes:  Requires:  Incompatibles:  Packages: SUNWcsu

Patch: 109807-01 Obsoletes:  Requires:  Incompatibles:  Packages: SUNWcsu

Patch: 109809-01 Obsoletes:  Requires:  Incompatibles:  Packages: SUNWcsu

Patch: 110905-01 Obsoletes:  Requires:  Incompatibles:  Packages: SUNWcsu

Patch: 110910-01 Obsoletes:  Requires:  Incompatibles:  Packages: SUNWcsu

Patch: 110914-01 Obsoletes:  Requires:  Incompatibles:  Packages: SUNWcsu

Patch: 108964-04 Obsoletes:  Requires:  Incompatibles:  Packages: SUNWcsr

At a command prompt, type the command for the kind of system information you want to display.

For more information, see Solaris Software System Information Commands. See TABLE 1-6 for a summary of the commands.

---

Recent Diagnostic Test Results

Summaries of the results from the most recent power-on self-test (POST) diagnostics tests are saved across power cycles.

1. Go to the ok prompt.

2. To see a summary of the most recent POST results, type:

ok show-post-results

This command produces a system-dependent list of hardware components, along with an indication of which components passed and which failed POST diagnostics tests.

---

OpenBoot Configuration Variables

Switches and diagnostic configuration variables stored in the IDPROM determine how and when POST diagnostics and OpenBoot diagnostics tests are performed. This section explains how to access and modify OpenBoot configuration variables. For a list of important OpenBoot configuration variables, see TABLE 1-4.

Changes to OpenBoot configuration variables take effect at the next reboot.

Halt the server to display the ok prompt.

• To display the current values of all OpenBoot configuration variables, use the printenv command.

The following example shows a short excerpt of this command's output.

ok printenv

Variable Name         Value                          Default Value

diag-level            min                            min

diag-switch?          false                          false

• To set or change the value of an OpenBoot configuration variable, use the setenv command:


ok setenv diag-level max diag-level = max

• To set OpenBoot configuration variables that accept multiple keywords, separate keywords with a space.

Using the watch-net and watch-net-all Commands to Check the Network Connections

The watch-net diagnostics test monitors Ethernet packets on the primary network interface. The watch-net-all diagnostics test monitors Ethernet packets on the primary network interface and on any additional network interfaces connected to the system board. Good packets received by the system are indicated by a period (.). Errors such as the framing error and the cyclic redundancy check (CRC) error are indicated with an X and an associated error description.

To start the watch-net diagnostic test, type the watch-net command at the ok prompt (CODE EXAMPLE 1-17).

{0} ok watch-net

Internal loopback test -- succeeded.

Link is -- up

Looking for Ethernet Packets.

`.' is a Good Packet. `X' is a Bad Packet.

Type any key to stop.................................

To start the watch-net-all diagnostic test, type watch-net-all at the ok prompt (CODE EXAMPLE 1-18).

{0} ok watch-net-all

/pci@1f,0/pci@1,1/network@c,1

Internal loopback test -- succeeded.

Link is -- up 

Looking for Ethernet Packets.

`.' is a Good Packet. `X' is a Bad Packet.

Type any key to stop.

---

Automatic System Recovery

Automatic System Recovery (ASR) consists of self-test features and an auto-configuring capability to detect failed hardware components and unconfigure them. By enabling ASR, the server is able to resume operating after certain nonfatal hardware faults or failures have occurred.

If a component is monitored by ASR and the server is capable of operating without it, the server automatically reboots if that component develops a fault or fails. This capability prevents a faulty hardware component from preventing the entire system from operating or causing the system to fail repeatedly.

If a fault is detected during the power-on sequence, the faulty component is disabled. If the system remains capable of functioning, the boot sequence continues.

To support this degraded boot capability, the OpenBoot firmware uses the 1275 Client Interface (by means of the device tree) to mark a device as either failed or disabled, by creating an appropriate status property in the device tree node. The Solaris OS does not activate a driver for any subsystem marked in this way.

As long as a failed component is electrically dormant (not causing random bus errors or signal noise, for example), the system reboots automatically and resumes operation while a service call is made.

Once a failed or disabled device is replaced with a new one, the OpenBoot firmware automatically modifies the status of the device upon reboot.

Auto-Boot Options

The auto-boot? setting controls whether the firmware automatically boots the operating system after each reset. The default setting is true.

The auto-boot-on-error? setting controls whether the system attempts a degraded boot when a subsystem failure is detected. Both the auto-boot? and auto-boot-on-error? settings must be set to true to enable an automatic degraded boot.

To set the switches, type:

ok setenv auto-boot? true

ok setenv auto-boot-on-error? true

Error-Handling Summary

Error handling during the power-on sequence can be summarized in the following three ways:

• If no errors are detected by POST or OpenBoot diagnostics, the system attempts to boot if auto-boot? is true.
• If only nonfatal errors are detected by POST or OpenBoot diagnostics, the system attempts to boot if auto-boot? is true and auto-boot-on-error? is true.

• If a fatal error is detected by POST or OpenBoot diagnostics, the system does not boot regardless of the settings of auto-boot? or auto-boot-on-error? Fatal nonrecoverable errors include the following:
• Failure of all CPUs
• Failure of all logical memory banks
• Failure of flash RAM cyclical redundancy check (CRC)
• Failure of critical field-replaceable unit (FRU) PROM configuration data
• Failure of critical application-specific integrated circuit (ASIC)

Reset Scenarios

Three OpenBoot configuration variables--diag-switch?, obdiag-trigger, and post-trigger--control how the system runs firmware diagnostics in response to system reset events.

The standard system reset protocol bypasses POST and OpenBoot diagnostics unless diag-switch? is set to true. The default setting for this variable is false. Because ASR relies on firmware diagnostics to detect faulty devices, diag-switch? must be set to true for ASR to run. For instructions, see To Enable ASR.

To control which reset events, if any, automatically initiate firmware diagnostics, use obdiag-trigger and post-trigger. For detailed explanations of these variables and their uses, see Controlling POST Diagnostics and Controlling OpenBoot Diagnostics Tests.

1. At the system ok prompt, type:

ok setenv diag-switch? true

ok setenv auto-boot? true

ok setenv auto-boot-on-error? true

2. Set the obdiag-trigger variable to power-on-reset, error-reset, or user-reset.

For example, type:

ok setenv obdiag-trigger user-reset

3. Type:

ok reset-all

The system permanently stores the parameter changes and boots automatically if the OpenBoot variable auto-boot? is set to true (its default value).

1. At the system ok prompt, type:

ok setenv diag-switch? false

2. Type:

ok reset-all

The system permanently stores the parameter change.

^{1 (TableFootnote) NC state is the normally closed state. This state represents the default mode of the relay contacts in the normally closed state.}

^{2 (TableFootnote) NO state is the normally open state. This state represents the default mode of the relay contacts in the normally open state.}This table contains details on the alarm indicators and the dry contact alarm states. It has sixteen rows and nine columns.

^{3 (TableFootnote) The implementation of this alarm indicator state is subject to change.}

^{4 (TableFootnote) The user can shut down the system using commands such as init0 and init6. This does not include the system power shutdown.}

^{5 (TableFootnote) Based on a determination of the fault conditions, the user can turn the alarm on using the Solaris platform alarm API or ALOM CLI. For more information about the alarm API see Appendix A, and for more information about the ALOM CLI, refer to the Sun Advanced Lights Out Manager Software User's Guide for the Netra 240 Server (part number 817-3174).}

^{6 (TableFootnote) The post-trigger and obdiag-trigger variables are obsolete in releases of OBP after 4.16.2.}

^{7 (TableFootnote) POST messages cannot be displayed on a graphics terminal. They are sent to ttya even when output-device is set to screen.}

Netra 240 Server System Administration Guide

817-2700-13

Copyright © 2005, Sun Microsystems, Inc. All Rights Reserved.