test

SunVTS 3.0 User's Guide

Appendix A SunVTS Tutorial

Follow the procedures in this chapter to become familiar with the basic methods used to configure and run SunVTS. For more specialized SunVTS functionality refer to additional chapters in this book.

Tutorials in this chapter:

Overview of SunVTS Procedures

The following list describes typical steps that you perform to test your system with the SunVTS diagnostic:

  1. Become superuser

  2. Load required test media and/or loopback connectors

  3. Start your desired window environment (CDE, OPEN LOOK, or none)

  4. Start the SunVTS diagnostic

  5. Configure SunVTS with the desired options

  6. Run the tests

  7. Review the test results

Note -

The tutorials in this chapter guide you through these steps, however, numbered steps in this list do not correspond to the numbered steps in the tutorials.

Running SunVTS With CDE (Tutorial)

This section is divided into the following subsections:

Initial Steps

Follow these steps when you start SunVTS:

  1. Log in to the system and become superuser.

  2. Insert test media (optional, see the note below):

    Several devices require media or loopback connectors for testing. Install such requirements before starting SunVTS to allow the SunVTS kernel to properly identify each device.

    You must install media in these devices if you plan to test them in Functional mode:

    • Tape drive--load a scratch tape in the tape drive that you plan to test. The tape test has a Read-only mode, but use a scratch tape to avoid inadvertently writing over data.

    • CD-ROM drive--load a compact disc (CD) into the drive. It can be an audio or data CD.

    • Diskette drive--load a scratch diskette in the drive. The diskette test has a Read-only mode, but use a scratch diskette to avoid inadvertently writing over data.

    • Communication ports--many of these tests require a loopback connector attached to the port. Attach any required loopback connectors for the ports you plan to test. For more information about loopback connectors refer to the SunVTS 3.0 Test Reference Manual.

    Note -

    This tutorial does not assume that you have a tape, CD-ROM, or diskette drive or loopback connectors attached to the system that you are testing. Therefore, the following procedures in this tutorial do not require installation of test media or connectors.

Start SunVTS on Your System

The following steps assume that the SunVTS package and the CDE environment is installed on your system, and that you have performed the steps in "Initial Steps"".

  1. Start the CDE graphical user interface environment if it is not already running.

  2. Start the SunVTS application:

    # /opt/SUNWvts/bin/sunvts

    The sunvts command starts the SunVTS kernel (vtsk) and the SunVTS user interface (vtsui, the CDE GUI, in this case). As the kernel initializes, it determines what devices are connected to your system, probes the devices, and passes this information to the user interface.

    The user interface that starts is determined on the following criteria:

    • When the CDE window manager (DTWM) is running, the default SunVTS GUI is CDE.

    • When the OPEN LOOK window manager (OLWM) is running, the default SunVTS GUI is OPEN LOOK.

    • If no window manager is running, then SunVTS starts the TTY mode interface.

    Note -

    If you receive an error message such as: connection to ":0.0" refused by server Xlib: Client is not authorized to connect to Server Error: Can't open display: :0.0 You may need to grant xhost permissions by typing: xhost +

    There are command line options that can be used on the SunVTS command line. For details refer to "To Start SunVTS on a Local System ".

SunVTS Testing (Part 1 - Basic Concepts)

After performing the steps in the previous section, the SunVTS CDE user interface is displayed on your screen as shown below. SunVTS is in an idle state with all testing parameters set to default values.

This section will step you through basic SunVTS configuration concepts, test execution, and review of test results.

Figure A-1 SunVTS Display (CDE)

Graphic

Note -

Refer to "CDE User Interface" for more detailed information on the CDE User Interface.

  1. Select the test mode (refer to Figure A-2):

    Test modes:

    • Connection test mode--provides a low-stress, quick testing of the availability and connectivity of selected devices. These tests are non-intrusive meaning they will release the devices after a quick test, and they will not place a heavy load on system activity.

    • Functional test mode--provides more robust testing of your system and devices. It will use your system resources for thorough testing and it assumes that there are no other applications running.

    • Functional test mode through SyMON--When SunVTS is invoked by the SyMON Online GUI, Functional mode runs in a restricted fashion. When SyMON is running it is assumed that the system is in production use. For this reason functional mode means the tests run in a non- intrusive fashion so that they do not significantly affect other applications.

    Note -

    Functional mode, when executed from SyMON, invokes non-intrusive tests which do not significantly affect other applications.

    1. Click on the Connection test button.

    2. Click on the Functional test button.

      As you change modes, the tests that are selectable change.

    Figure A-2 SunVTS Select Mode Buttons

    Graphic

  2. Identify the configuration of your system in the System Map:

    The devices that SunVTS identified on your system are listed in the System Map window of the SunVTS display (see Figure A-3 ).

    SunVTS can display devices in two ways:

    • Physical mapping--which shows the exact location of each device on the system for Field Replaceable Unit (FRU) identification. From physical mapping, you can determine the actual location of the devices. When possible, the board number and controller type for the device are also displayed. This view is only available on systems that have the configd program installed (part of the SyMON SUNWsyc package). Do not select Physical Mapping at this time.

    • Logical mapping-- organizes the list of devices, according to their function, into groups. For example, disk, tape, and CD-ROM drives are placed in the SCSI-Devices group. You can focus your testing on a specific group or on all of the groups on the system.

      Figure A-3 SunVTS System Map (Logical View)

      Graphic

  3. Expand the Processor(s) device group to show the individual testable devices by clicking on the plus symbol. (See Figure A-4 below.)

    A "+" (plus) indicates that the device group is collapsed, meaning individual devices are grouped together and hidden from view under a device category.

    A "-" (minus) indicates that the device group is expanded so you see each device for a given category.

    For example, clicking on the plus symbol next to "Processors(s)" expands the Processor category to show the types of testable devices for that group (such as "system" and "CPU-init0") as well as the name of the SunVTS test in parenthesis (such as systest and fputest) that is used to test each device.

    Note - Detailed information about each SunVTS test is located in the SunVTS 3.0 Test Reference Manual.

    Figure A-4 SunVTS System Map (Processor Group Expanded)

    Graphic

  4. Click on the check mark next to "system" and "cpu" to deselect these devices for testing.

    If a check mark is present then the device is selected for testing.

    Some devices are initially selected when SunVTS is first started. These devices are the default set of devices to test in Functional mode.

    When you select or deselect a device group, all devices in that group become selected or deselected.

    You will not be able to select some devices such as the Comm-ports and other devices at this time. They require that Intervention mode to be enabled (refer to the next step).

  5. Click on the Intervention button (see Figure A-5) to enable the selection of additional tests.

    Certain devices like the Comm-port, tape drive, CD_ROM, and diskette device tests require that you intervene before such devices can be selected for testing. These devices require the installation of media or loopback connectors (in Functional mode only).

    This tutorial does not test these devices, however, if you wish to run such tests, and you have not loaded the required media, do so now. Afterwards, click the Intervention button (refer to Figure A-5 below) to indicate that the required media is in place. These tests are now selectable, however SunVTS does not verify that the proper media is installed. If you attempt to run such tests without the media, the test will fail.

    Note -

    If you are loading test media after SunVTS is started, it may be necessary to have the SunVTS kernel reprobe the system. Refer to Figure 4-3 for details.

  6. Use the Select devices buttons (see Figure A-5) to select and deselect devices to test:

    1. Click on the "None" button.

      All tests for all devices are deselected.

    2. Click on the "All" button.

      All tests for all devices are selected. However, if intervention is not enabled then those tests that require intervention will not be selected.

    3. Click on the "Default" button.

      SunVTS selects the default set of tests. If interventions is selected then the default tests may be the entire set of tests for your system.

    Figure A-5 SunVTS Select Devices Button

    Graphic

  7. Set up the following test configuration:

    1. Select Connection mode.

    2. Select None from the Select devices box.

    3. Select (place a check mark in the box) of the Comm-port box.

      Note -

      If you don't have comm-port displayed, you may not have such a device on your system. In this case, choose another device group such as the Processor(s) device group.

  8. Start the test by clicking on the green Start button in the upper left corner.

    Testing starts immediately. Since SunVTS is in Connection mode, only one pass of the selected test runs and SunVTS Returns to an idle state.

    Messages are displayed in the Test message window in the lower section of the SunVTS display. Error messages, if they occur, are also reported in this window.

    Colors in the system map indicate pass or fail conditions. During testing, the name of a device changes color from black to green if it has at least one pass and no failures. The moment a device has a failure, the name changes to red.

  9. View the results of the test:

    1. Look at the Status area of the display (see Figure A-6).

      The following is reported:

      • Testing status--provides the following status of SunVTS:

        • Idle indicates that no testing is taking place

        • Testing indicates that SunVTS is running

        • Suspend indicates that testing is suspended

        • Replay indicates that a previously recorded session is displayed

        • Stopping is momentarily displayed as SunVTS stops testing

      • System passes--displays the total number of successful system passes (a system pass is when all selected tests have been run once).

      • Cumulative errors--reports the total number of errors from all selected tests.

      • Elapsed test time--indicates the total number of hours, minutes, and seconds that elapsed during testing.

      Figure A-6 Test Status Area

      Graphic

    2. Look at the Test messages window:

      This window displays the test status and error messages. There is a scrollbar that gives you access to messages that exceed the window size.

      Figure A-7 Test Messages Window

      Graphic

    3. Look at the Test logs:

      1. Click on the Log button at the top of the display.

        The log file window is displayed. Three different files contain test results:

        • SunVTS error status log (/var/opt/SUNWvts/logs/sunvts.err)--contains test error messages.

        • SunVTS information log (/var/opt/SUNWvts/logs/sunvts.info)--contains informative messages that are generated when you start and stop SunVTS. These messages include start and stop times, as well as information that appears in the Status area of the main display.

        • Solaristm system message log (/var/adm/messages)--contains a log of all the general UNIX messages (as determined by the /etc/syslog.conf file).

        The Log file button in the top of this window allows you to switch between three logs files. The Delete and Print buttons give you quick access to such functions.

      2. Click on the Log file button to select a different log file to view.

      3. Click on the Close button.

        The Log file window is dismissed.

  10. Reset the current test statistics by clicking on the Reset button (at the top of the display).

    The test status information is reset to zero. This does not clear the log files.

  11. Clear the Test messages window by clicking on the Clear button (lower right corner of the SunVTS display).

    The window is cleared. This does not clear the log files.

The previous steps introduced you to important SunVTS functionality. To investigate additional SunVTS features continue with the tutorial below. Or, if you want to quit the SunVTS diagnostic, select Quit SunVTS from Commands in the menu bar, and click on UI and Kernel.

SunVTS Testing (Part 2 - Using Additional Features)

The following steps assume that SunVTS is started and that you are familiar with its basic operation as described in part 1.

This section will have you run morethorough tests.

  1. Select Functional test mode.

  2. Use SunVTS to get a report of your system configuration (see Figure A-8 ):

    1. Click on Reports from the Menu bar.

      The Reports menu appears.

    2. Click on System configuration from the menu.

      A window showing your system configuration is displayed.

      If you have access to a printer and you wish to print a copy of this list, click on the Print button, specify your printer name in the window, and click OK.

    3. Click on the Close button in the system configuration window.

      The configuration window is dismissed.

    Figure A-8 CDE Reports Menu

    Graphic

  3. Use the SunVTS Notify option to receive email:

    1. Click on Options from the Menu bar

      The Option menu appears.

    2. Click on Notify from the menu.

      The Notify window appears (see the figure below). The following options are available:

      • Send Email--determines how email notification will be handled:

        • Disabled (never send email)

        • Now (send email immediately)

        • On Error (send email when an error occurs)

        • Periodically (send email every x number of minutes, as defined by Log Period)

        • On Error & Periodically (send on error and periodically)

      • Email Address--indicates the email address where the test status messages are sent.

      • Log Period--specifies the time, in minutes, for sending test status email messages.

      Figure A-9 Notify Option Menu

      Graphic

    3. Set up the Notify menu as follows:

      1. Send Email--On Error and Periodically

      2. Email Address--your email address (e.g., user1@pergola)

      3. Log Period--15 (fifteen minutes)

      4. Click on Apply.

      Email will be sent to you the next time that SunVTS testing is started, provided that testing exceeds the time specified in the log period, or an error was detected.

  4. Set up test execution options:

    1. Click on Options in the Menu bar.

    2. Select Test Execution from the menu (see Figure A-10).

      Global test execution parameters are displayed. Use these parameters to control the overall testing activity. These parameters can also be set on individual groups and on individual devices (covered later). The following list summarizes each setting. Additional descriptions are located in "Options Menu".

      • Stress--runs certain tests in stress mode, working the device harder than normal.

      • Verbose--displays verbose messages in the SunVTS Console window

      • Core File --when enabled, creates a core file if certain events occur. When disabled, no core file is created, but the event is displayed in the message window and logged in the error log.

      • Run On Error--when disabled, SunVTS stops testing when an error occurs. When enabled, SunVTS continues testing until the Max Errors value (see below) is met.

      • Max Passes--specifies the maximum number of test passes to perform. If this value is zero, Functional Mode tests will run indefinitely, or until the number of errors meets the Max Error value or Max Time value.

      • Max Errors--specifies the maximum number of allowable errors before testing is stopped. If this value is zero, testing continues regardless of errors.

      • Max Time--states the time limit (in minutes) for testing. If this value is zero, there is no time limit.

      • Number of Instance --specifies the number of test instances (simultaneous copies of a test) for each test that supports multiple instances.

    3. Apply the following settings:

      • Stress - disabled

      • Verbose - enabled

      • Core - disabled

      • Run-on Error - enabled

      • Max Passes - 2

      • Max Errors - 10

      • Max Time - 0

      • Num. of Instances - 2

      Note -

      These parameters are not applicable when SunVTS is in Connection test mode.

      Figure A-10 Test Execution Option Menu

      Graphic

    4. Click on apply.

      The Test Execution menu is dismissed.

  5. Expand all Device Groups:

    Instead of expanding each device group by clicking on each plus in the System Map, you can accomplish the same thing through the View commands as follows:

    1. Click on View in the Menu bar.

    2. Click on Open system map.

      All device groups are expanded in the system map, showing each device and the test associated with it.

  6. Access the Test Parameter Options for a specific device:

    These options allow you to specify specific test options for each test. The menu that is displayed is different for each test. This tutorial looks at the options for nettest as an example. To see the options for other tests, bring up the Test Parameters menu the same way. For detailed information about each test and associated options, refer to the SunVTS 3.0 Test Reference Manual.

    1. Click the right mouse button (menu button) on nettest to display a pull-down menu.

    2. Click on Test Parameter Options.

      The Test Parameter Options menu is displayed (see the figure below).

      Figure A-11 Example of a Test Parameter Menu

      Graphic

    3. Click on Enable for the Print_Warning option (refer to the above figure).

    4. Click on Apply.

  7. Access the Test Execution Options for a device group:

    The Test Execution Options pop-up menu provides the access to the same options as Test Execution under Options in the Menu bar. The difference is that these Test Execution options apply only to a specific device or device group (used in this tutorial) and are not global settings. For descriptions on each setting refer to "Options Menu".

    1. Click the right mouse button (menu button) on Processor(s).

      The pull-down menu provides access to configuration menus for all devices within that device group.

    2. Select Test Execution.

    3. Change the Max Passes parameter to 4.

      In an earlier step, you set the global Max Passes parameter to 10. By changing this parameter, all device tests will be limited to ten passes, but all devices in the Processor group will be limited to 4.

    4. Click on Apply.

  8. View the performance statistics for the system by clicking on the Meter button (at the top of the display).

    The Sun Performance Meter panel is displayed (see Figure A-12). This meter shows a graphical display of the system performance statistics even while SunVTS is in the idle state. It may be convenient to watch these meters when you are performing stress testing.

    The following statistics are reported:

    • CPU--percentage of CPU being used

    • pkts--Ethernet packets per second

    • page--paging activity in pages per second

    • swap--jobs swapped per second

    • intr--number of device interrupts per second

    • disk--disk traffic in transfers per second

    • contxt--number of context switches per second

    • load--average number of processes over the last minute

    • colls--Ethernet collisions per second

    • errs--receiving packet errors per second

    Figure A-12 The Performance Meter Panel

    Graphic

  9. Set up the following test configuration:

    1. Select Functional Test Mode.

    2. Select None from the Select devices box.

    3. Select the following devices to test:

      1. Processor(s) device group

      2. Network device group

  10. Click on the Start button.

    Testing starts and will run for quite a while.

  11. Observe the following while testing is in progress:

    • Many messages are displayed in the Test message window because the SunVTS Verbose option is enabled.

    • Asterisks appear next to the device indicating which devices are currently being tested.

    • The devices under test change color. Green indicates that at least one pass is complete and there are no errors. Red indicates that at least one error has occurred.

    • The Performance meter panel indicates changes in system activity levels.

    • You may have received email, provided the log period has been met.

  12. Click on the Stop button.

  13. Check the status of individual tests as follows:

    1. Click the right mouse button (menu button) on systest.

    2. Select Status from the menu.

      A menu displays the test, number of passes, and number of failures.

    3. Click on Close to dismiss the status window.

  14. To quit the SunVTS diagnostic, select Quit SunVTS from Commands in the menu bar, and click on UI and Kernel.

    Note -

    Before quitting SunVTS, you must stop any tests that are running. Some tests, such as the tape test, do not stop immediately because they require time to rewind.

    This concludes the "Running SunVTS With CDE (Tutorial)"".

    Additional SunVTS features are described throughout this book.

Running SunVTS With the TTY Interface (Tutorial)

To Use SunVTS With the TTY Interface

The TTY interface is a ASCII based, screen-oriented interface that does not require a graphical window environment. Most of the control and monitoring options that are available in the SunVTS GUI interface are also available in the TTY interface.

You can use the TTY interface to run SunVTS from a terminal, shelltool, command tool, or a modem attached to a serial port.

  1. Start SunVTS with the TTY interface:

    The TTY main window is displayed (figure below):

    # /opt/SUNWvts/bin/sunvts -t

    Figure A-13 TTY Main Window

    Graphic

  2. Identify the four main areas in the display (see Figure A-13):

    • Control panel--access to SunVTS commands and options.

    • System map--shows the testable devices (categorized in test groups) and provides access to their test options.

    • Status panel--displays the SunVTS test status information

    • Console Area--the area where test and error messages are displayed. No user input is possible in this area.

  3. Review these keyboard commands:

    Keyboard commands, instead of mouse and pointer action, are used to control SunVTS with the TTY interface. The following steps lead you through some of the common procedures. In all cases, use these keyboard commands to select and apply your test input.

    Table A-1 TTY Keyboard Commands

    Key 

    Description of Action 

    Tab 

    Moves the highlight or shifts the focus to the next window. For example, if you are working in the Control panel and press the Tab key, the focus (or highlight) shifts to the Status panel. A panel that is highlighted will be bordered by asterisks (*). Before you can change an option, you must first highlight that panel. 

    Return 

    - Displays a menu 

    - Selects and applies a choice or a command in a menu 

    Spacebar 

    Selects or deselects an option checkbox; [ ]= select; [*]= deselect

    Arrow keys 

    Moves between options in a highlighted panel 

    Backspace key 

    Deletes text in a text field 

    Escape 

    Closes a pop-up menu or window 

    Control-F 

    Scrolls forward in a scrollable window 

    Control-B 

    Scrolls backward in a scrollable window 

    Control-X 

    Quits the TTY user interface but leaves the SunVTS kernel running 

    Control-L 

    Refreshes the TTY window 

  4. Move between the main display areas (press the Tab key several times).

    As you use the Tab key, your position in the display is indicated by dark rectangle. It is important to keep track of your position in the display. When the dark triangle is over a word or command, it is highlighted (ready to be selected).

    As you press the Tab key, you move from the Control panel to the Status panel to the System Map, and back.

  5. Select your test mode:

    1. Use the Tab key until you are in the Control panel area (Start will be highlighted).

    2. Use the right arrow key to highlight test_mode.

    3. Use the Return key to display the test_mode menu.

    4. Use the down arrow to highlight Connectivity (Connection mode).

      (The up and down arrows are used to move between options.)

      For descriptions of Connection and Functional test modes refer to "Test Modes".

    5. Press Return to apply the change and exit the menu.

    6. Press the Return key again to reenter the test_mode menu.

    7. Use the arrow key to highlight Functional and press Return.

      SunVTS prompts you to verify this change.

    8. Use the arrow key to highlight OK and press Return.

  6. Use the Tab key to move to the System map (Test_Group area).

    The asterisk([*]) in the brackets, next to group name, indicates that all devices in that group are selected for testing.

  7. To see devices listed inside a group:

    1. Use the right arrow key to highlight Processors.

    2. Use the Return key to display a menu that shows you the individual devices and their tests (see the following figure).

      Figure A-14 Processor Group Tests (TTY Interface)

      Graphic

    3. Press the Escape key to Return to the main menu.

  8. Deselect test groups:

    1. Press the Tab key to move to the Control panel area.

    2. Use the arrow key to highlight test_select.

    3. Press the Return key to open the test_select menu.

    4. Highlight None, and press Return.

      All asterisks next to each test groups are no longer displayed indicating that no tests are selected.

  9. Modify device specific test options:

    1. Press the Tab key to move to the System Map.

    2. Use the arrow key to highlight Network and press Return.

      Your network device(s) are shown in the menu.

    3. Highlight nettest (or whatever network test is available on your system), and press Return.

    4. Highlight Test_Parameters and press Return.

      The Test Parameters menu for nettest is displayed. For the purpose of this tutorial, you will only be directed to change the Print_Warning option.

    5. Use the arrow keys to highlight the word Disabled (next to Print_Warning, refer to the following figure).

      Figure A-15 nettest Test_Parameters (TTY Interface)

      Graphic

    6. Press Return once to open the enable/disable menu, and again to select enable.

      The Print_Warning value is set to enable. Do not press the Escape key; the change must be applied.

    7. Use the arrow keys to highlight Apply, and press Return.

      The change is applied and you return to the previous menu.

    8. Press Return to enter the nettest option menu again.

    9. Highlight Test_Execution, and press Return.

    10. Highlight the Verbose option "disabled", and press Return twice to change it to enabled.

    11. Use the arrow keys to highlight Apply, and press Return.

  10. Select a device for testing:

    Any number of tests can be selected. For the purpose of this tutorial, you will only be directed to select one test (nettest).

    1. Use the arrow key to highlight the brackets ([ ]) next to nettest.

    2. Press the space bar.

      An asterisk appears in the brackets indicating that this test is selected.

    3. Press Escape to return to the main TTY window.

      The system map will show an asterisk next to the Network group (refer to the following figure).

      Figure A-16 Network Group Selected in the System Map (TTY Interface)

      Graphic

  11. To set global options:

    1. Use the Tab key to move to the Control panel area.

    2. Use the down arrow to move to the second row of commands.

    3. Use an arrow key to highlight set_options.

    4. Press Return to open the set_options menu.

    5. Press Return again to open the Thresholds menu.

    6. Type 3 next to Max_System_Passes.

    7. Use the arrow keys to highlight Apply and press Return.

  12. To start testing:

    1. Use the arrow keys to highlight Start in the Control panel area.

    2. Press Return once to get the start menu, and again to select Start.

      Testing begins. The Console window displays messages because the verbose option is enabled. The Status panel displays the testing status such as the system status, passes, errors, and the elapsed time.

      Note -

      nettest checks all the networking hardware on the system CPU board and separate networking controller cards. For this test to be meaningful, the system must be attached to a network.

  13. Review the test results:

    1. Observe the message window that appears when testing is done (refer to the figure below).

      This window displays the test results for all of the tested devices.

      Figure A-17 TTY Message Window

      Graphic

    2. Press Escape to dismiss the Message window.

      No other commands will work until this window is dismissed.

  14. Review the log files:

    SunVTS events are recorded in three log files. Refer to "The Log Files Button" for details. This tutorial directs you to view the contents of the Information log.

    1. Tab to the Control panel area.

    2. Highlight log_files and press Return.

    3. Highlight Information and press Return.

    4. Highlight Display and press Return.

      The contents of the SunVTS Information log are displayed.

      To display the log file, SunVTs opens a temporary file using the default editor for the shell (Bourne, korn, or c-shell, and so on) that you are using. In many cases, this is the vi editor. All of the standard editor commands are valid in this file, however, no changes will alter the permanent log file.

      Assuming that you are using the vi editor, use the following vi commands to view the log file contents:

      • Arrow keys--move the cursor one line, or character at a time.

      • Control-F--display the next screen

      • Control-B--display the previous screen

      • /string--search forward for string

      • Esc,Q--quit

      Figure A-18 SunVTS Information Log (TTY Interface)

      Graphic

    5. When you are done reading the information log file, press the Escape key, then :q to dismiss it.

    6. Press Escape again to dismiss the log_file menu.

  15. To reset the current test status information:

    It is a good idea to reset previous test status information before you begin another test session.

    1. Tab to the Control panel area.

    2. Highlight reset and press Return.

      The Status panel is cleared.

      Note -

      The messages in the lower Console window are not cleared by reset.

  16. To Exit SunVTS:

    1. If you are not in the Control panel area, move there now (Tab key).

    2. Highlight quit and press Return once to get the Quit menu, and again to select quit UI and kernel.

      SunVTS is closed and your display is cleared.

Running a Test From the Command Line (Tutorial)

In some cases it may be more convenient to run a single SunVTS test from the command line. 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.

There are two directories where tests reside:

Use the pathname based on the type (32-bit or 64-bit) of operating system that is running.

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 command line execution is:

testname [-scruvdtelnf] [-p number] [-i number] [-w number] [-o test_specific_arguments]

The standard command-line argument usage for all SunVTS tests is:

Table A-2 Standard Command-line Arguments
 Argument Definition
-sRun a test as though it were invoked from the SunVTS kernel (vtsk). This causes the test to send output to an RPC port that the SunVTS kernel is using. The default is to send the output to stdout or stderr.
-c 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.
-r Enables run on error so that when an error occurs, the test continues with the next test sequence instead of exiting. The default is false.
-u  Displays command line usage information.
-v Runs the test in Verbose mode and displays messages with more detailed information about the testing process. The default is false.
-d Runs the test in debug mode and displays messages to help programmers debug their test code. The default is false.
-t Runs the test in test Trace mode and displays messages that track function calls and sequences currently in use by the test code. The default is false.
-e Runs the test in Stress mode by increasing the system load. The default is false.
-l Runs the test in Online Functional mode. This is the same mode that tests run in when executed through SyMON. It is a non-intrusive version that will not significantly affect other applications. See the note below. The default is true.
-n Runs the test in Connection mode. See the note below.The default is false.
-f Runs the test in full Functional test mode. This mode assumes that the test has complete control of the device under test. See the note below. The default is false.
-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.
-o Used to indicate that the options and arguments that follow are test specific. Note: Separate each test specific argument by commas, with no space after each comma.

Note -

If you choose to specify a test mode with the l, n, or f option, specify only one option at a time because only one test mode can be selected at a time.

Run A Single Test from the Command Line

  1. Review the command line syntax and arguments for the test you plan to run:

    There are nearly fifty individual SunVTS tests. The tests that you choose to run depends on the configuration of your system. For this exercise you are directed to run one of three tests (for devices that are somewhat common to all configurations.) Choose the test that matches your system configuration (choices are listed below). For information on cammand line systax and test options refer to the SunVTS 3.0 Test Reference Manual.

  2. Load any required test media (tape, CD, or diskette) or loopback connectors required by the test.

    Note -

    This is a necessary step for several tests, however, none of the examples in this exercise require test media or loopback connectors.

  3. Run the test (choose one of the examples below):

    To test your audio device:

    # /opt/SUNWvts/bin/audiotest -vf -p1 -o M,X

    In this example, -vf -p1 -o are standard arguments (common to all tests), and M,X are two arguments specific to the audiotest. Notice that the test specific arguments are separated by a comma and no spaces.

    To test your disk drive:

    # /opt/SUNWvts/bin/disktest -n -p2 -o dev=c0t0d0

    This example tests a disk drive called c0t0d0. You may need to replace this device name with a device name of a disk that is connected to your system.

    To test your CPU:

    # /opt/SUNWvts/bin/systest -v -f -p3 -i5

  4. Watch the display as the tests run.

    If an error occurs, an error message will be reported to the screen. Since the test is running without the SunVTS kernel, events and error are not logged in log files.