Skip to ContentSun and Oracle Channel Sun How to Buy Log In

SunVTS 2.1.3 Test Reference Manual

包含在

Solaris 2.6 Hardware: 5/98 on Sun Hardware AnswerBook

查找更多文档

专项支持资源

以 PDF 格式下载本书

CHAPTER 1

Introduction

The Sun Validation and Test Suite (SunVTS) software runs multiple diagnostic hardware tests from a single user interface. SunVTS verifies the configuration, functionality, and reliability of most hardware controllers and devices.

SunVTS works from either the Common Desktop Environment (CDE) or the OPEN LOOK (OL)graphical user interface(GUI). The GUI lets you set test parameters quickly and easily while running the diagnostic tests. The sample screens and menus in this manual show SunVTS using the CDE user interface.

This manual describes SunVTS Version 2.1.3, which is on the SMCC Supplement CD. The default installation directory for SunVTS is /opt/ SUNWvts. When you are installing SunVTS, you can specify a different directory to install the software.

This chapter describes hardware and software requirements, how to access the tests, how tests are grouped, and standard command line arguments.

Hardware and Software Requirements

The SunVTS Version 2.1.3 software runs on any system with the Solaris 2.5, 2.5.1, or 2.6 operating environment installed. The operating system kernel must be configured to support all peripherals that are to be tested.

Some SunVTS tests have additional requirements such as the connection of loopback connectors or the availability of disk space. For additional requirements see the specific test chapter in this book.

Software Requirements

General Package Requirement

To run SunVTS the SUNWvts package must be loaded on your system. To see if this package is loaded type the following:


  % pkginfo SUNWvts

If your system responds with, "system SUNWvts Online Validation Test Suite" the package is present.

SunVTS with CDE

SunVTS is designed to run in the Common Desktop Environment (CDE). To run the CDE GUI you must have the CDE end-user software installed on your system, or at least the SUNWdtbas package from it. Perform this command to see if this package is installed on your system:


  % pkginfo SUNWdtbas

If your system responds with, "system SUNWdtbas CDE application basic runtime environment" the package is present. If necessary, see your system administrator for assistance with installing the CDE software.

SunVTS with OPEN LOOK

You must meet the following requirements to run SunVTS with the OPEN LOOK GUI:

Run Solaris operating system (Version 2.5 through 2.6)
Run OPEN LOOK, Version 3.3

Set the correct openwin path: Set the OPENWINHOME environment variable to point to the location where OPEN LOOK is installed on your system. You can ignore this requirement if you use the default location, /usr/openwin. Otherwise, use the following command and substitute the pathname variable for the actual path where OPEN LOOK is installed.


  % setenv OPENWINHOME pathname

Check the existing OPENWINHOME by typing env.

Set the correct library path: Set the LD_LIBRARY_PATH environment variable to point to the location of the Windows library directory on your system. If you use the default location, /usr/openwin/lib, you can ignore this requirement.
Otherwise, use the following command and substitute the pathname variable for the actual path where OPEN LOOK library is installed.


  % setenv LD_LIBRARY_PATH pathname

Check the existing LD_LIBRARY_PATH by typing env.

How to Access SunVTS

You can run SunVTS tests from various interfaces: The CDE and OL graphical user interfaces, or the TTY interface. SunVTS tests can also be run individually from a shell command line, using the command line syntax for each test. Table 1-1 describes the various SunVTS system interfaces.

TABLE 1-1

SunVTS System Interfaces	Description
Graphical User Interfaces (GUIs)	Users can select tests and test options by pointing and clicking with a mouse button in the CDE or OL interface.
TTY Interface	Users can run SunVTS from a terminal or modem attached to a serial port. This feature requires that you use the keyboard instead of the mouse, and it displays one screen of information at a time. However, it emulates the window system whenever possible.
Command Line Interface	Lets users run each of the SunVTS tests individually from a shell command line using the command line syntax. Each test description contains the corresponding command line syntax. For more information about running individual tests from the command line, refer to the specific test description in this manual.
Online Interface	Provides access to SunVTS testing through the SyMON monitoring tool.

Standard Command Line Arguments

Two types of command line arguments can be applied to a test: generic command arguments (common to all tests) and test-specific command line arguments. For test-specific command line arguments refer to the "Command Line Syntax" section found in each test chapter as well as TABLE 1-3 on page 6.

The standard syntax for all SunVTS tests is:


  testname [-scruvdtelnf] [-p number][-i number] [-w number]  
          [-o test specific arguments]

The following table defines the standard SunVTS command line arguments:

TABLE 1-2

Argument	Definition
`-s`	Runs a test in SunVTS mode.
`-c`	Enables a core dump; the test creates a core file if a system crash occurs.
`-r`	Run-on-Error mode; if an error occurs, the test continues the next test sequence instead of exiting.
`-u`	Displays the Usage statement.
`-v`	Runs the test in Verbose mode; the test displays VERBOSE messages that tell more about the testing process.
`-d`	Runs the test in Debug mode; the test displays DEBUG messages to help programmers debug their test code.
`-t`	Runs the test in Trace mode; the test displays TRACE messages that track down function calls and sequences currently being used by the test code.
`-e`	Runs in Stress mode; the test runs under increased system load.
`-l`	Runs in Online mode.
`-n`	Runs in Connection test mode.
`-f`	Runs in Functional test mode.
`-i` *number*	Defines the number of instances for scalable tests.
`-p` *number*	Defines the number of passes.
`-w` *number*	For scalable tests, defines to which instance the test is assigned.

Test-Specific Arguments

There are test-specific arguments, as described in TABLE 1-3 Test-specific arguments should follow the format specified in the getsubopt(3c) man page. For information about test-specific arguments refer to the specific test chapter in this book.

TABLE 1-3

Argument	Definition
`-o`	Separate each test-specific argument by commas, with no space after the each comma. For example: `#./sample -v -o dev=/dev/audio,volume=78` The test option format is specified by the man page `getsubopt`(`3C`).

Test Modes

SunVTS has three test modes:

Connection test mode--a low stress, quick testing of the availability and connectivity of the tested device.
Functional test mode--a more robust testing capability that uses whatever system resources are required to do thorough testing, and assumes that there are no other applications running.

Hardware Verification

The SunVTS kernel automatically probes the system kernel for installed hardware devices on your system or a remote system. Those devices are then displayed on the SunVTS control panel with the appropriate tests and test options. This provides a quick check of your hardware setup.

How to Test Multiple Frame Buffers

The following rules apply when you test multiple frame buffers (displays) simultaneously:

You can test multiple frame buffers on a system at the same time, but only one frame buffer can run the window environment.
To avoid incorrect test failures, for those frame buffer tests that have a window locking option, the frame buffer that runs the window environment, such as CDE or OPEN LOOK software, must have window locking enabled. Any other frame buffers must have window locking disabled.

Caution - If window locking is disabled (unlocked) on frame buffers that are running, the SunVTS tests can return false error messages if you move the mouse during testing. Even a slight mouse movement can cause a test to fail.

By default, SunVTS enables window locking on the console monitor (frame buffers that are the /dev/fb named device).
If you are running a frame buffer test from a command line, you can disable Window Locking by specifying a command line argument (see the test command line descriptions in this manual). For example, when running the generic frame buffer test (fbtest), use the lock=e/d option to enable or disable Window Locking. The example below shows the command that enables Window locking (frame buffer locking):


  #./fbtest -o dev=cgthree0,lock=e

Remote Testing of Frame Buffers

The frame buffer locking option does not work when you start sunvts or vtsk remotely. In this case, disable the window locking option to d. Do not run any graphic programs (including vtsui) on that frame buffer during graphic testing.