|C H A P T E R 1|
This chapter contains the following topics:
The Sun Validation and Test Suite (SunVTS) software performs multiple diagnostic hardware tests from a single user interface. SunVTS verifies the connectivity, functionality, and reliability of controllers and devices.
Use SunVTS to test one device or multiple devices. Some of the major test categories are as follows:
SunVTS comprises of many individual tests that support testing of a wide range of products and peripherals. Most of the tests can test devices in a 32-bit or 64-bit Solaris operating system (OS).
Such flexibility requires that the proper test modes and options need to be selected to maximize its effectiveness. This document covers the individual test options, modes, and requirements. For overall test configuration modes and options refer to the SunVTS User's Guide.
Note - When an error occurs in SunVTS testing, the test message window displays the error number, the error description, the probable cause of the error, and the recommended actions. Because this information is displayed at the time of the error, error messages are not included in this document.
The default installation directory for SunVTS is /opt/SUNWvts. However, when you are installing SunVTS, you can specify a different directory. Refer to the SunVTS User's Guide for installation information.
The standard command line argument, -V, displays the SunVTS version and release date of the test, if available.
sunpci2test now supports the SunPCi III cards. Solaris 10 OS supports SunPCi-III Version 3.2.2 with Patch 118591-03 only. Solaris 10 does not support the SunPCi-2 card.
SunVTS 6.2 was first introduced and designed to run in the Solaris 10 1/06 (Solaris 10 Update 1) OS and subsequent compatible releases. SunVTS 6.2 is not supported on OS releases prior to Solaris 10 3/05 (Solaris 10).
The operating system kernel must be configured to support all peripherals that are to be tested.
Some SunVTS tests have special requirements such as the connection of loopback connectors, installation of test media, or the availability of disk space. These requirements are listed for each test in the corresponding chapter in this document.
Many individual tests make up the SunVTS collection of tests. Each test is a separate process from the SunVTS kernel. Each test can be run individually from the command line or from the SunVTS user interface.
When SunVTS is started, the SunVTS kernel automatically probes the system kernel to determine the hardware devices. The devices are then displayed on the SunVTS control panel with the appropriate tests and test options. This provides a quick check of your hardware configuration, and no time is wasted trying to run tests that are not applicable to your configuration.
During testing, the hardware tests send the test status and messages to the SunVTS kernel through interprocess communication (IPC) protocols. The kernel passes the status to the user interface and logs the messages.
SunVTS has a shared object library that contains test-specific probing routines. At runtime, the SunVTS kernel dynamically links in and calls these probing routines to initialize its data structure with test-specific information. You can add new tests into the SunVTS environment without recompiling the SunVTS source code.
Beginning with SunVTS 3.0, the SunVTS kernel and most tests support 32-bit and 64-bit operating systems. When the sunvts command is used to start SunVTS, the appropriate tests (32-bit or 64-bit versions) are presented.
In Solaris 10 or later OSs, only 64-bit compatible tests are supported. Because each test is a separate program, you can run individual tests directly from the command line. Run tests from specific directories as follows:
If you are not sure which OS is running, refer to the Solaris System Administration manuals. In Solaris 10 OS, you can use the following command to identify the application support of your system.
You can run SunVTS tests from the JDS graphical user interface or the TTY interface. SunVTS tests can also be run individually from a shell tool command line, using the command-line syntax for each test (refer to Running a Test From the Command Line). TABLE 1-1 describes the various SunVTS user interfaces. Refer to the SunVTS User's Guide for more information on these interfaces.
The common way to run SunVTS testing is through a SunVTS user interface--JDS or the TTY interface.
Test configuration, control, and results are easily accessed through buttons and dialog boxes. These buttons and dialog boxes are covered in the SunVTS User's Guide. However, the Test Parameter Options dialog box is unique for each test, and is therefore covered in this manual.
The options displayed in this menu differ for each test, but the Apply menu, and the Reset and Cancel buttons are generic. TABLE 1-2 describes all the items.
A list of test options that are used to customize the testing of the selectable device, group, or all devices. The options are specific for each test and are covered in the test specific-chapters in this manual.
In some cases it may be more convenient to run a single SunVTS test from the command line rather than through a SunVTS user interface. The following information describes how to do this.
Unless specified, the test runs without the SunVTS kernel (vtsk). All events and errors are sent to stdout or stderr and are not logged in the log files.
When you run a test in this way, you must specify all test options in the form of command-line arguments. There are two types of command-line arguments:
The standard syntax for all SunVTS tests is:
testname [-scruvdtelnf] [-i number] [-w number][-o test-specific-arguments]
Note - 64-bit tests are located in the sparcv9 subdirectory: /opt/SUNWvts/bin/sparcv9/testname, or the relative path to which you installed SunVTS. If a test is not present in this directory, then it might be available as a 32-bit test only. For more information, see 32- and 64-Bit Tests.
The following table defines the standard SunVTS command-line arguments:
Enables a core image of the test process to be created in the current working directory upon receipt of certain signals, otherwise those signals are caught and handled to prevent a core from being generated. The default is to disable the creation of a core image.
Runs the test in Online Functional mode. This is the same mode that tests run in when executed with the vtsui.online command. It is a non-intrusive version that will not significantly affect other applications. See the note below. The default is true.
SunVTS includes test-specific arguments that follow the format specified in the getsubopt(3c) man page. Separate each test-specific argument by commas, with no space after the comma. For example: #./sample -v -o dev=/dev/audio,volume=78. For information about test-specific arguments refer to the specific test chapter in this document.
SunVTS includes a number of tests that exercise frame buffers:
If you are testing more than one frame buffer, follow these guidelines and instructions.
Caution - Disable the Power Management screen saver option and the
The following rules apply when you test multiple frame buffers (displays) simultaneously:
If you start sunvts or vtsk from a screen other than the console monitor, frame buffer locking is not available. In this case:
Do not run any graphic programs (including vtsui) on the remote frame buffer during graphic testing.
If you are testing multiple frame buffers or remote frame buffers, you might need to enable or disable frame buffer locking.
Take one of the following actions:
Take one of the following actions: