sundiag(1M)

NAME

sundiag − SunOS hardware diagnostic program

SYNOPSIS

sundiag [ −Cpqtw ] [ −i number ] [ −o option_file ] [ −b batch_file ] [ −k kernel_name ]

[ −o saved_options_file ]
sundiag testname testname-specific_arguments [ cprquvdt ] [ h hostname ]

sundiag

AVAILABILITY

SunDiag is an optional software category, so unless you specify another location, it will be installed in the /opt directory by the operating system. See the SunDiag 4.3 User’s Guide for information about installing this optional software.

DESCRIPTION

sundiag is a diagnostic utility that runs “stress” tests on hardware devices.

Only the superuser can use sundiag.

The SunDiag program consists of the sundiag window-based user interface, along with several binary modules and executable files containing the actual test code.

There are three ways to run SunDiag tests. The SunDiag OpenWindows interface is the most popular, but a tty interface is also supplied. Tests can be run on individual hardware devices from the command lines of a C-shell or Bourne shell. The OpenWindows interface allows you to change global or individual test options using the mouse.

SunDiag testing can be “scaled” up in order to thoroughly test the more powerful single and multiprocessor systems. Individual SunDiag tests have been modified so that multiple “instances,” or copies, of a single test can be run simultaneously on selected processors. The Processor Affinity mask (PAM) is a tool that enables you to specify which processors a test will run on. Any instances of a scalable test can be set to one of the processors available using the PAM. See the SunDiag 4.3 User’s Guide for more details on which tests are scalable, and how to run them.

OPTIONS

For Starting SunDiag in OpenWindows or tty Mode

At start-up in either of these modes, sundiag probes for the hardware installed on the system under test and displays the devices it has found. If a hardware device connected to the system under test is not detected by sundiag, then it is not connected properly.

The following options are available when SunDiag is run from the OpenWindows window environment, or a tty interface.

−C Redirect the console output from any existing console window to the sundiag console sub-window. If you are using the tty interface, the console message is displayed in the message line of the status screen.

−p Skip the SunDiag kernel probe for devices. If this argument is specified, SunDiag only runs the user-defined tests it finds in .usertest.

−q Automatically quit the SunDiag program when testing stops. This option is designed for use in sh(1) or csh(1) shell scripts, and can only be issued from a command line.

−t Run sundiag in tty mode.

−w Write the system hardware configuration to the /var/adm/sundiaglog/sundiag.conf file.

−i number
Multiprocessing systems only. Specify the number of instances (copies) of scalable tests. the default setting is two times the number of processors on the system under test.

−o options_file
Use the options_file to restore options. The default option file is .sundiag. .sundiag is used if the −o option is not used and if the default file exists.

−b batch_file
Run SunDiag in batch mode. See the SunDiag 4.3 User’s Guide for details on using this option.

−k kernel_name
Specify the customized kernel name used to boot the system. The default kernel name is /kernel/unix. The performance monitor is disabled when this option is specified.

For Running SunDiag Tests from a Command Line

The following options are available when running individual SunDiag tests from a command line (“standard arguments”):

c Create a core dump file if the system under test crashes.

p Skip any test loops.

r Continue testing after an error has occurred. The test continues with the next test sequence instead of exiting.

q Run a faster, abbreviated version of the individual tests. Most tests have a quick version; those that do not will run normally.

u Display information on how to run the test. It shows three parts: command line usage, standard arguments and routine specific arguments.

v Display verbose messages regarding the test. These messages tell you more about the testing process that is going on. This mode is more valuable for some tests than others; graphics tests only return start and stop messages/failures.

d Display debug messages from the test. These messages provide more sophisticated information (mainly useful for test programmers).

t Display messages which allow you to trace down function calls and the sequences being used by the test code for some of the tests.

h hostname
Specify hostname to receive system messages regarding this test.

USAGE

Running the SunDiag Program from the OpenWindows Interface

When sundiag is started from the OpenWindows environment, it displays its own window interface with four subwindows:

• A test system status panel on the upper left of the screen that shows the test results.

• A performance monitor in the upper middle of the screen that tracks system activity levels.

• A control panel on the upper right of the screen that displays the hardware available for testing, and provides tools to control testing. Select the hardware to be tested by clicking SELECT on the buttons displaying the hardware device names. The selected tests will appear grey on monochrome monitors, and “pushed-in” on color monitors. Most hardware items have option menus for changing test parameters. The option menus can be opened by clicking SELECT on the Options... button to the right of each hardware device name.

• A console window on the lower left of the screen that displays system and error messages.

Running the SunDiag Program from a tty Interface

sundiag can be run from a terminal, by specifying the −t option (tty mode) when sundiag is started. In tty mode, sundiag emulates the window interface on a terminal screen. The tests and test options available in the window system are also available in tty mode. Commands and options are shown in brackets at the top of the tty screen, and are typed in at the command line on the bottom of the screen. For every command there is a single-letter abbreviation that is shown in parenthesis. When finished with a screen, the command d for done will return you to the previous screen. See the SunDiag 4.3 User’s Guide for details on how to run SunDiag in tty mode.

Running Individual SunDiag Tests from a Command Line

SunDiag tests can be run individually from shell command lines using the syntax explained above in the SYNOPSIS section. See the SunDiag 4.3 User’s Guide to identify testname and test-specific_arguments for each test.

FILES

/var/adm/sundiaglog/options/.sundiag start-up option file

/opt/sundiag/.usertest user-defined test description file

/var/adm/sundiaglog/sundiag.info SunDiag status log file

/var/adm/sundiaglog/sundiag.err SunDiag status error file

/var/adm/messages.∗ SunOS system log

/dev/MAKEDEV

Museum

Related Articles