test

SunVTS 5.0 User's Guide

Chapter 5 Using the SunVTS TTY User Interface

This chapter describes how to run a test session using the SunVTS TTY UI. The procedures are written in a step-by-step form so you can use them to become familiar with SunVTS using the SunVTS TTY UI. This chapter is divided into the following sections:

Note -

This chapter assumes that you have already performed the following procedures: o Installed SunVTS as described in Chapter 2, Installing and Removing SunVTS o Started SunVTS as described in Chapter 3, Starting SunVTS o Prepared your system for testing as described in "Preparing Devices for Testing"

See Appendix A, SunVTS Window and Dialog Box Reference for descriptions of each SunVTS window and dialog box.

Getting Started with the SunVTS TTY UI

This section describes how to use the fundamental features of the SunVTS TTY UI to perform diagnostic testing on a system. For information about using more advanced features, see "Using Additional Features with the SunVTS TTY UI".

The SunVTS TTY UI Main Window and Keyboard Commands

The SunVTS TTY UI is an 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 graphical interfaces are also available in the TTY interface.

You can use the TTY interface to run SunVTS from a serial terminal, or through a graphical window tool such as a shell tool, command tool, or CDE terminal window.

The procedures in this chapter explain how to use the TTY main window:

Figure 5-1 SunVTS TTY Main Window

Graphic

Table 5-1 SunVTS TTY Main Window

Window Item 

Description 

Control panel

Provides access to SunVTS controls.

Test_Groups panel

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

Status panel 

Displays SunVTS test status information. 

Message console panel

The area where test messages are displayed. No user input is accepted in this panel. You can use up and down arrow keys to scroll through the messages in this panel. 

Navigating the SunVTS TTY UI

Use keyboard commands instead of mouse and pointer action to control SunVTS in the TTY UI. The following table lists the keyboard commands and explains how to use them.

Table 5-2 TTY Keyboard Commands

Key 

Description of Action 

Tab

Moves you from one panel to another.

For example, if you are working in the Control panel and press the Tab key, the focus (or highlight) shifts to the Status panel. Highlighted panels are bordered by asterisks (*).  

Arrow keys

Moves between selections within a panel

Return

  • Displays a menu

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

Spacebar

Selects or deselects a checkbox: 

  • [*]= selected

  • [ ]= deselected

Backspace key

Deletes text in a text field

Escape

Discards 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

To Configure SunVTS for a Test Session

  1. Identify the current state of SunVTS in the Status panel.

    Figure 5-2 Status panel (TTY)

    Graphic

    • System_status--provides the following status of SunVTS:

      • Idle--no testing is taking place

      • Testing--a test session is running

      • Suspend--a test session is suspended

      • Replay--a previously recorded test session is displayed

      • Stopping--is momentarily displayed when a test session stops

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

    • Total_errors--the total number of errors from all tests.

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

    • List of devices to test with pass and error counts.

  2. Select a test mode (Functional or Connection).

    About 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 no other applications are running.

    How to do it:

    1. Use the tab key to move to the Control panel ((if needed).

    2. Use the arrow keys to highlight test_mode and press return.

      The test_mode menu is displayed.

      Figure 5-3 test_mode Menu (TTY)

      Graphic

    3. Use the arrow keys to highlight functional or connectivity and press return.

    4. Use the arrow key to highlight OK in the confirmation dialog box and press return.

      Note -

      You can exit any menu, at any time with the <Esc> key.

  3. Specify the display mode (logical or physical).

    About display modes:

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

    • Physical Mapping--shows the exact location of each device on the system in relation to how the devices are connected to each other. If you are testing a single-board type system, each device is shown under the system board. Multi-board type systems show each device under the board (for example, board0, board1, and so on) to which the device is attached. For example, if you have multiple disk drives connected to different disk interfaces, each disk would be displayed under the respective interface. From Physical Mapping, you can determine the actual location of each device. When possible, the board number and controller type for the device are also displayed.

    How to do it:

    1. Use the arrow keys to highlight grouping and press return.

      The grouping menu is displayed.

      Figure 5-4 grouping Menu (TTY)

      Graphic

    2. Use the arrow keys to highlight logical or physical and press return.

  4. Enable Intervention mode (if needed).

    About Intervention mode:

    Any device that requires your intervention before the test can run (such as loading media for tape, CD-ROM, and diskette tests) also requires that you notify SunVTS that you have performed this action by enabling Intervention mode. You can not select any intervention mode devices until you enable this mode.

    How to do it:

    1. Prepare the device for testing (see "Preparing Devices for Testing").

    2. Use the tab key to move to the Control panel.

    3. Use the arrow keys to highlight intervention and press return.

    4. Use the arrow keys to highlight Enable and press return.

  5. Select the device groups that you want to test.

    About device groups:

    An asterisk next to a device group in the Test_Groups panel indicates that the devices in that group are selected. Depending on the devices on your system, and the test mode that you select, SunVTS selects certain devices by default. You can change the selected devices.

    How to do it:

    1. Use the tab key to move to the Control panel.

    2. Use the arrow keys to highlight test_select and press return.

    3. Use the arrow keys to highlight one of the following:

      • Default--selects the SunVTS default selected devices

      • None--deselects all devices

      • All--selects all devices

      • Custom--indicates that you intend to select your own set of devices to test.

  6. Select specific devices to test.

    About specific devices:

    In the previous step, you selected sets of devices for testing by choosing device groups. You can further refine your device selection by selecting or deselecting specific devices.

    How to do it:

    1. Use the tab key to move to the Test_Groups panel.

    2. Use the arrow keys to highlight the device group for which you plan to select or deselect individual devices, and press return.

      The individual devices within that group are displayed in a list.

      Figure 5-5 Devices within a Group (TTY)

      Graphic

    3. Use the arrow keys to highlight the [ ] (brackets) next to the device that you want to select or deselect.

    4. Press the space-bar to toggle the asterisk.

    5. Press return to close the group.

      Notice that the Status panel displays (or removes) the devices as you select (or deselect) them.

  7. Modify the system-level test options (if desired).

    About test options:

    SunVTS is ready to test each device once you select it. You can, however, modify test options that alter the way tests run to suit your testing needs. There are three levels where you control test options:

    • System-level options--control the testing attributes of all devices. This is the highest level, applying all your options globally. When you modify option values at this level, the option settings are propagated down to the group level and device level options.

    • Group-level options--control the testing attributes of all the devices in the group. Settings made at this level propagate down, setting all the options in the group.

    • Device-level options--control the testing of a single, specific device.

    The order that you apply the system-level, group-level, and device-level options is important. Start by assigning the system-level options, then assign the group-level options, and finish with the device-level options. Otherwise, if you make lower-level options, then higher-level options, the higher-level options will propagate down and undo your lower-level options. An alternative to this approach is to use locks and overrides to protect lower-level options. See "Preserving Test Options with Locks and Overrides".

    How to do it:

    1. Tab to the Control panel.

    2. Use the arrow keys to highlight set_options and press return.

      The set_options menu is displayed.

      Figure 5-6 set_options Menu (TTY)

      Graphic

    3. Use the arrow keys to select one of the following menus, and press return:

      • Thresholds

      • Notify

      • Schedule

      • Test_execution

      • Advanced

      Note -

      For descriptions of these menus see "SunVTS Dialog Boxes".

    4. Use the arrow keys and numeric keys to set the options values.

    5. Use the arrow keys to highlight Apply and press return.

  8. Modify group-level and device-level options (if desired).

    About group-level and device-level options:

    Group-level and device-level options are similar to the system-level testing attributes, but instead pertain to a specific device (or device group) only. You modify these options by changing values in the following dialog boxes:

    • Test_Parameters

    • Test_Execution

    • Advanced

    • Schedule (group-level only)

    How to do it:

    1. Tab to the Test_Groups panel.

    2. Use the arrow keys to highlight the device group and press return.

      At this point you can choose to access the group-level option menu instead by highlighting Option (instead of the device-level) and press return. Then go to Step d. Otherwise, the following steps will direct you to modify device-level options.

    3. Use the arrow keys to select a device from the device list and press return.

      The Test_Options menu is displayed.

      Figure 5-7 Test_Options Menu

      Graphic

    4. Select one of the option dialog boxes (Test_Parameters, Test_Execution, or Advanced) and press return.

      Note -

      For descriptions of these menus, see "SunVTS Dialog Boxes".

    5. Use the arrow and numeric keys to modify the options in the dialog box.

    6. Use the arrow keys to highlight apply and press return.

      If you selected the Test_Parameters dialog box, you will be prompted to apply your changes to one of the following:

      • Within_Instance--applies the option settings to this test instance (test instance 1 for example) for this device with Apply, or to all the same instances within the same device-group with Apply_to_group, or to all the same instances for all like devices with Apply_to_All.

      • Across_All_Instances--applies the option settings to all test instances (for example, instance 1 and 2) to this device with Apply, or to all the instances for all the devices in the group with Apply_to_group, or to all the instances for all like devices with Apply_to_all.

      Figure 5-8 Apply Menu Choices

      Graphic

The test session configuration is complete. Continue to the next procedure to run the test session.

To Run, Monitor, and Stop a Test Session

  1. Start the test session.

    How to do it:

    1. Use the tab key to move to the Control panel.

    2. Use the arrow keys to highlight start and press return.

      The start menu is displayed.

    3. With start highlighted (the default) press return.

      The test session begins.

    Depending on how you configured the options in the Test_Execution menus, testing will continue until:

    • a test error is detected (this is the default behavior). If you enter a value for Run_On_Error, SunVTS continues to run until the specified number of errors is reached.

    • testing has reached the Max_Passes value. The default is to run indefinite test passes.

    • testing has reached the Max_Time value. The default is to run indefinitely.

    • you select Stop in the Control panel.

  2. Monitor the overall test session status by watching the Status panel.

    The Status panel indicates that a test session is running by displaying testing for the System_status. The System_passes, Total_errors, and elapsed_time will increment.

  3. Monitor specific tests by watching the Status panel.

    Watch for:

    • An asterisk--displayed next to each device indicating which device is currently under test. Depending on how you configured SunVTS (with the System Concurrency option), single or multiple devices are tested concurrently.

    • Pass and Error columns--Indicates the state of each device test.

  4. Check for test messages by watching the Message console panel.

    The Message console panel displays test messages under the following circumstances:

    • When a test error occurs

    • If you enable trace mode

    • If you enable verbose mode

    Use the up and down arrow keys to scroll through messages in this panel.

  5. Stop the test session (if desired).

    How to do it:

    1. Use the tab key to move to the Control panel.

    2. If stop is not highlighted, use the arrow keys to highlight it, and press return.

      The test session displays a confirmation menu.

    3. Press <Esc> to dismiss the confirmation menu.

      The test session stops.

To Review and Reset Test Session Results

  1. Review the logs.

    About logs:

    SunVTS provides access to four log files:

    • SunVTS test error log--contains time-stamped SunVTS test error messages. The log file pathname is /var/opt/SUNWvts/logs/sunvts.err. This file is not created until a SunVTS test failure occurs.

    • SunVTS kernel error log--contains time-stamped SunVTS kernel and SunVTS probe errors. SunVTS kernel errors are errors that relate to running SunVTS, and not to testing of devices. The log file pathname is /var/opt/SUNWvts/logs/vtsk.err. This file is not created until SunVTS reports a SunVTS kernel error.

    • SunVTS information log--contains informative messages that are generated when you start and stop SunVTS test sessions. The log file pathname is /var/opt/SUNWvts/logs/sunvts.info. This file is not created until a SunVTS test session runs.

    • Solaris system message log--is a log of all the general Solaris events logged by syslogd. The pathname of this log file is /var/adm/messages.

    How to do it:

    1. Use the tab keys to move to the Control panel.

    2. Use the arrow keys to highlight log_files.

      The log_files menu is displayed.

    3. Use the arrow keys to select one of the three log files and press return.

    4. Use the arrow keys to select one of the following:

      • Display--the content of the log file is displayed.

        Note -

        SunVTS uses your default editor to display the log file. In many cases, the default editor is vi and you can use the standard vi commands to view the content. However, the file is opened in read-only mode, so you cannot do anything to alter the content. Use the vi command :q to quit and return to the main TTY window.

      • Remove--the content of the log file is deleted.

      • Print--the print menu is displayed. Specify the name of the printer in this menu, highlight Apply, and press return. The content of the log file is sent to the printer.

        Note -

        Take the length of the log file into consideration before you print it.

    5. Press <Esc> to close the log_file menu.

  2. Interpret SunVTS messages

    There are many messages for each of the many tests that run under SunVTS. For this reason, it is difficult to document the implication of each message that you might see. Most messages contain all the explanatory text that is possible for each event that is encountered. Some messages are information messages (INFO, VERBOSE, WARNING) which do not represent an error, while some messages are error messages (ERROR and FATAL), indicating that the test detected a failure. This section explains generic test message information.

    SunVTS information message example:


    04/24/00 17:19:47 systemA SunVTS5.0: VTSID 34 disktest.VERBOSE c0t0d0: "number of blocks 3629760"

    SunVTS error message example:


    05/02/00 10:49:43 systemA SunVTS5.0: VTSID 8040 disktest.  FATAL diskette: "Failed get_volmgr_name()"   Probable_Cause(s):     (1)No floppy disk in drive  Recommended_Action(s):     (1)Check the floppy drive

    Whenever possible, the error message supplies a message type (Table 5-3), followed by the message text, one or more probable causes, and one or more recommended corrective actions.

    The following table describes the types of messages you might encounter. All messages are displayed in the Message panel, and most are logged in one of the SunVTS logs (Info or Error).

    Table 5-3 Message Types

    Message Type 

    Log file 

    Description 

    INFO

    Info log 

    Displayed when a non-error test event occurs. 

    ERROR

    Error and Info logs 

    Displayed when a test detects an error, often an indication of a problem with a specific function or feature of the device under test. 

    FATAL

    Error and Info logs 

    Displayed when a test detects a severe error that might cause the test to exit, such as a failure to open a device. These errors are indicative of hardware failures. 

    VERBOSE

    Not logged 

    Test progression messages that are displayed when the verbose feature is enabled.  

    WARNING

    Info log 

    Displayed when something affects the test that is not an error, such as a device that is busy. 

    You can write scripts that watch for certain SunVTS events as they are logged in the log files, and which trigger an action when a particular message string occurs. If you plan to do this, read the information about the message format. See Table 4-2.

    Note -

    The message syntax changed as of SunVTS 4.0. For the old message syntax information, see Appendix B, Frequently Asked Questions. In a future version of SunVTS, the old message format will no longer be supported. Update any scripts that rely on the old message format.

  3. Reset the test session results (if desired).

    How to do it:

    1. Use the tab key to move to the Control panel.

    2. Use the arrow keys to highlight reset and press return.

      The information in the Status panel is reset. This does not reset your test options.

Using Additional Features with the SunVTS TTY UI

This section describes additional SunVTS features using the SunVTS TTY user interface:

Connecting to Another Host

You can connect the SunVTS user interface on your local system to a SunVTS kernel that is running on another system in your network. Once you are connected to the remote system, all of the controls in the TTY UI control the testing of the remote system.

To Connect to Another Host

  1. Make sure that the SunVTS kernel is running on the remote system.

    You can do this in several ways. You can remote login (using rlogin or telnet) to the remote system and run the vtsk command (see "To Start the SunVTS Kernel (vtsk)") to start the kernel.

    Note -

    On the remote system, you must login (or switch user) as a user that has SunVTS privileges (superuser by default) before you can start the SunVTS kernel (vtsk).

  2. Open the Connect_to_Host menu:

    1. In the Control panel, highlight connect_to and press return.

    2. Enter the remote system hostname in the connect_to_host field.

    3. Highlight Apply and press return.

    4. Press <Esc> when you receive the connect_to confirmation box.

    The SunVTS UI now controls SunVTS on the remote system. The remote system hostname is displayed at the top of the TTY main menu.

Using the Email Notification Feature

You can have SunVTS send test status messages to you using email.

To Enable Email Notification

  1. In the Control panel, highlight set_options and press return.

    The set_options menu is displayed.

  2. Select Notify and press return.

  3. Complete the notify menu items.

  4. Highlight Apply and press return.

Controlling the Size of the Log Files

The log file sizes of the SunVTS test error log (/var/opt/SUNWvts/logs/sunvts.err), the SunVTS kernel error log (/var/opt/SUNWvts/logs/vtsk.err) and the information log (/var/opt/SUNWvts/logs/sunvts.info) are each limited to a maximum size of 1 Mbyte by default. When the log file reaches the maximum size, the content is moved to a file called logfilename.backup. Additional events are added to the main log files. If the log file reaches the maximum size again, the content is moved to the backup file, overwriting the earlier backup file content. Only one backup file is maintained for each log file.

You can modify the log file maximum size specification.

To Modify the Log File Size Limits

  1. In the Control panel, highlight set_options and press return.

    The set_options menu is displayed.

  2. Highlight Thresholds in the set_options menu and press return.

  3. Enter a value (1-5) in the Max System Log Size field.

  4. With Apply highlighted, press return.

Preserving Test Options with Locks and Overrides

With locks and overrides you can preserve or override the options you set at the system level, group level, and device level.

Locks

Normally, when you change an option setting at the system level or group level, the new option setting propagates down to all lower levels. Enabling the lock prevents an option setting made at a higher level from affecting the lower-level option setting.

Note -

Overrides nullify lower-level locks.

To Set (or Unset) a Lock

  1. Open the Test Advanced Options dialog box from the group level or device level you want to lock as follows:

    1. Move to the Test_Groups panel.

    2. Highlight the group that has the device for which you plan to set (or unset) a lock, and press return.

      The group devices are displayed.

    3. Highlight the device and press return.

      The Test_Options menu is displayed.

    4. Highlight Advanced and press return.

      The Advanced options menu is displayed.

    5. Highlight the setting for the Test Lock and press return.

    6. Highlight enabled (or disabled) and press return.

    7. Highlight Apply in the Advanced menu.

      The lock is set (or unset).

Overrides

You can use overrides to void the lock protection. Setting the system-level override nullifies all locks, and setting a group-level override nullifies all the locks below that group.

To Set (or Unset) an Override

  1. Open the Advanced Option dialog box at one of the following levels:

    • System-level--select Advanced from the set_options in the Control panel.

    • Group-level--select Advanced from Options next the to group in the Test_Groups panel.

  2. Highlight the Override setting (enable/disable), and press return.

    The enable disable menu is displayed.

  3. Select enable (or disable), and press return.

  4. Highlight Apply, and press return.

Scaling Your Test Session

You can use a combination of options to scale testing intensity to meet your diagnostic needs. For example, you can modify test options so that each test instance runs simultaneously, thus increasing the stress level for a single or multiprocessor system. The following procedures can be used individually or in combination to scale the test session.

To Modify the Number of Test Instances

You can scale your test session by running multiple copies of the same test on your devices. Each copy is called a test instance. Each test instance is a separate process of the same test. The number of test instances can be set at the system level, group level, and the device level as follows:

  1. Open the Test_Execution Option menu at one of the following levels:

    • System-level--select Test_Execution from the set_options menu in the Control panel.

    • Group-level--select Test_Execution from Options next to the group in the Test_Groups panel.

    • Device-level--select Test_Execution from the device in the device option menu.

  2. Highlight the Num of Instances setting, and enter the value you want.

  3. Highlight Apply, and press return.

To Modify Test Concurrency Options

The test concurrency option sets the number of tests that run at a given time during a test session. You can set this value to one to run one test at a time, or increase the test concurrency value thus increasing the stress level of your test session.

There are two options you can modify in the Schedule Option dialog boxes (at the system level and group level) to scale your test session:

  1. Open the Schedule Option menu at one of the following levels:

    • System-level--select Schedule from the set_options menu in the Control panel.

    • Group-level--select Schedule from Options next to the group in the Test_Groups panel.

  2. Highlight the concurrency setting, and enter the value you want.

  3. Highlight Apply, and press return.

To Bind a Test to a Processor with the Processor Affinity Option (for Multiprocessor Systems)

By default, the Solaris kernel assigns each test instance to whichever processor is available at the time. On multiprocessor systems, you can bind (assign) a test instance to a particular processor as follows:

  1. Open the Test_Execution Option menu at one of the following levels:

    • System-level--select Test_Execution from the set_options menu in the Control panel.

    • Group-level--select Test_Execution from Options next to the group in the Test_Groups panel.

    • Device-level--select Test_Execution from the device in the device option menu.

    Note -

    The Processor Affinity field is only displayed on multiprocessor systems.

    Note -

    The Processor Affinity option is not available for processor tests such as cputest and fputest. These tests are associated with each individual processor on your system and you cannot bind these tests to a different processor.

  2. Highlight the Processor Affinity setting, and enter the value you want.

  3. Highlight Apply, and press return.

Using the Debugging Features

You can enable certain options that cause the SunVTS test session to output more test data than when you run the session with the default option values. The following procedures describe how to enable these features.

To Enable (or Disable) Debugging Options

  1. Open the Test_Execution Option menu at one of the following levels:

    • System-level--select Test_Execution from the set_options menu in the Control panel.

    • Group-level--select Test_Execution from Options next to the group in the Test_Groups panel.

    • Device-level--select Test_Execution from the device in the device option menu.

  2. Enable (or disable) one or more of the following options:

    • Verbose--displays verbose messages indicating when the test is starting and stopping during the test session.

    • Core File--when enabled, creates a core file when a test session results in a core dump. The core file is called sunvts_install_dir/bin/core.testname.xxxxxx , where testname is the test that dumped the core, and xxxxxx is a character string generated by the system in order to make the file name unique.

  3. Highlight Apply, and press return.

Saving a Test Session Configuration for Repeated Use (Option Files)

You can use the Option Files feature to save the current set of selected devices and test options for reuse. This is a convenient feature when you plan to use the same test session configuration over and over again.

The configuration information is saved in a filename of your choice in the /var/opt/SUNWvts/options directory.

Note -

Do not manually edit any option file. Unnecessary or spurious characters in the option file can cause unexpected behavior when you use them.

To Create an Option File

  1. Configure SunVTS for the test session that you want to save.

    See "To Configure SunVTS for a Test Session".

  2. Highlight option_files in the Control panel, and press return.

    The Option Files menu box is displayed.

  3. Specify an option file name in the Option File field.

  4. Highlight Store, and press return.

To Load an Option File
Note -

Loading an option file that was created on another system is permitted, but you must make sure that the configuration is valid for the system you plan to test.

Note -

Do not load an option file that was created in a 64-bit environment into a 32-bit environment.

  1. Highlight option_files in the Control panel, and press return.

    The Option Files menu box is displayed.

  2. Highlight List and press return.

    The list of available option files is displayed.

  3. Highlight an option file from the list, and press return.

  4. Highlight Load, and press return.

    The test session configuration is loaded into SunVTS. You can use this configuration, or modify it before you start the test session.

To Remove an Option File

  1. Highlight option_files in the Control panel, and press return.

    The Option Files menu box is displayed.

  2. Highlight List and press return.

    The list of available option files are displayed.

  3. Highlight the option file from the list that you want to delete, and press return.

  4. Highlight Remove, and press return.

Using the Auto-Start Feature

You can use the auto-start feature, along with saved option files, to simplify the process of configuring a test session and running it.

To Configure SunVTS to use the Auto-Start Feature

  1. Highlight set_options from the Control panel, and press return.

    The set_options menu is displayed.

  2. Highlight Schedule and press return.

    The Schedule menu is displayed.

  3. Enable the Auto Start setting in the Schedule menu.

  4. Highlight Apply and press return.

  5. Create an option file as described in "To Create an Option File".

    The option file that you create is configured to use the auto-start feature.

To Use the Auto-Start Feature

  1. Highlight quit UI and Kernel from the quit menu in the Control panel.

    You must quit SunVTS and restart it for the auto-start feature to work.

  2. Use the following command to restart SunVTS from the command-line, specifying the Option File that you created:


    # /opt/SUNWvts/bin/sunvts -to option_file

    SunVTS displays the TTY main window and automatically starts the test session.

Suspending and Resuming a Test Session

You can suspend a test session. For example, you might want to look at messages on the Console panel that have scrolled out of view, or you may want to view and print a log file.

To Suspend and Resume a Test Session

  1. While the test session is running, highlight suspend in the Control panel, and press return.

    "Suspended" is displayed in the Status panel, and the test session pauses until you resume it.

  2. While the test session is suspended, highlight resume in the Control panel, and press return.

    "Testing" is displayed in the Status panel, and the SunVTS kernel resumes the suspended test session.

Recording and Replaying a Test Session

You can use the Record and Replay feature to record a SunVTS test session. Only one test session recording is saved at a time.

The events are recorded in a file called /var/opt/SUNWvts/vts_replay_file.

Once a test session is recorded, you can use the recorded events to drive the SunVTS kernel so it reproduces the recorded sequence of events at a later time.

Note -

The Record and Replay feature closely reproduces the sequence of events, but it cannot reproduce the time periods of these events because the execution times vary from one run to another.

To Record and Replay a Test Session

  1. Configure SunVTS for the test session that you want to run.

    See "To Configure SunVTS for a Test Session".

  2. Highlight start in the Control panel and press return.

    The start menu is displayed.

  3. Highlight Start with Record and press return.

    The test session runs, and the events are recorded. When testing stops, the recorded session is available to replay.

  4. Highlight start in the Control panel and press return.

    The start menu is displayed.

  5. Highlight Replay and press return.

    The kernel reruns the same tests, with the same configuration that you specified.

Note -

During the replay, the kernel is actually rerunning the tests, not just re-displaying the recorded session.

Scheduling Test Sequences With the Deterministic Scheduler

SunVTS TTY UI provides a Deterministic scheduler that allows you to determine what tests run, and in what order. If you do not use this fearture, selected tests run in an order that is determined by the SunVTS kernel.

Deterministic Scheduler Overview

The Deterministic Scheduler is available as dsched Menu in the Control Panel in the SunVTS TTY UI.

Note -

Since the Control panel shows only 2 lines at a time, you might need to press Control-F to see dsched. dsched is available on the third line in Control panel.

Note -

To select an item in the menu, highlight the item using the arrow keys, then press return.

The following list provides an overview of the steps you perform to start, run, and quit the Deterministic Scheduler feature. Detailed instructions follow.

  1. Start SunVTS with the SunTTY user interface.

  2. Start the Deterministic Scheduler.

  3. Create one or more tasks, using the Task Manager screen. A task is a SunVTS test session configuration (one or more selected SunVTS tests, test options, and specific test mode).

  4. Create the sequence, using the Sequence Manager screen. A sequence is a group of tasks specified to run in a certain order.

  5. Define the number of times (loops) that sequence runs, using the Sequence Runner screen.

  6. Start the sequence.

  7. When the sequence is done, reset the Detreministic Scheduler if desired.

  8. Quit the Determinsitic Scheduler from the main Dsched Menu.

Getting Started With the Deterministic Scheduler

  1. Start SunVTS with the SunVTS TTY user interface as described in "Starting SunVTS" on page (INSERT THE RIGHT X-REF for ch. and page#).

  2. Start the Dterministic Scheduler as described below:

    1. Use Control-F to view the choices on the third line in the Control panel. Use arrow keys to highlight dsched (Deterministic Scheduler) and press return.

      The Deterministic Scheduler menu is displayed.

      INSERT GRAPHIC (dsched menu)

    2. Start the Deterministic Scheduler by highlighting and pressing return on StartDS in the Dsched Menu.

      INSERT GRAPHIC (start DS menu) HERE. Link it to step 2?

  3. Create your task(s) as described below:

    1. Invoke the Task Manager screen by selecting Task Manager in the Start DS menu.

      The Task Manager screen is displayed.

      INSERT GRAPHIC (task manager screen) HERE.

    2. To see the list of existing tasks, select List... from the Task Manager screen and press return.

      The Tasks Available menu is displayed with the list of Available Tasks.

      INSER GRAPHIC (tasks available menu with available tasks(TTY) HERE.

      Note -

      If this is the first time that the Deterministic Scheduler is used, you must create a minimum of one task.

    3. In the Test Groups panel, configure a test session (select one or more devices and your desired test mode).

      If you assign more than one test to a task, the order of the tests within this task cannot be predicted. If you want to control the order of every test, assign only one test for each task.

      When the Deterministic Scheduler is started, it changes the default values of Max System Passes from 0 (run indefinitely) to 1 (run one pass). This is necessary so that each task only runs selected tests once and proceeds to run subsequent tasks in the sequence.

    4. In the Task Manager screen, enter a task name, in the Task File text field.

    5. Select Store to save the task.

      Your task is created. To check your task, perform Step b.

    6. Repeat Step c through Step e to create additional tasks.

    7. To see the test session configuration for a particular task, invoke the Task Available screen by selecting List... and select a particular task. The selected task appears in the Task File field. Select Load in the Task Manger screen.

      The SunVTS Status panel shows the SunVTS test configuration associated with the selected task.

    8. To modify a task:

      Select the task from Tasks Available screen; load it by selecting the Load from the Task Manager screen; change the test configuration in the Test Groups panel; and select Store in the Task Manager screen.

    9. To delete a task:

      Select it from Tasks Available screen and press Remove in the Task Manager screen.

      The task is removed from the Available Task list.

  4. Create a sequence as follows:

    1. Invoke the Sequence Manager screen by selecting the Sequence Manager in the Start DS menu.

      INSERT GRAPHIC (Sequence Manager screen) HERE.

    2. To see the list of existing sequences, select List... on the Sequence Manager screen and press return.

      INSERT GRAPHIC (List...menu showing all sequence files in Sequence Manager) HERE.

      The Sequence Files menu is displayed with the list of existing sequences.

      Note -

      Use Control-F/Control-B to scroll through all the sequences.

    3. Enter the name of the sequence file you want to create in the Sequence Name test field.

    4. Select the Task Insert/Delete -> Insert Tasks on Sequence Manager screen. The Tasks Available screen is displayed.

    5. Select a task from the list of tasks available for this sequence from the Tasks Available screen. This displays a screen with Insert Task as the only choice to select. Press return after selecting Insert Task.

      INSERT GRAPHIC (Sequence of Screens that is displayed) HERE.

      The particular task you selected is inserted into the sequence.

    6. Repeat Step e to add additional tasks into the sequence.

    7. Select Store to store the sequence.

    8. You can view the list of tasks available in this sequence by selecting Tasks In Sequence on the Sequence Manager screen.

    9. To delete a particular task from a sequence:

      1. Load the sequence by selecting the sequence from the Sequence Files screen, which is displayed by selecting List... .

      2. Select Task Insert / Delete->Delete Task / Set Task Insert Task.

        The Tasks In Sequence screen is displayed with a list of tasks in the sequence.

      3. Select the task you want to remove. This displays another screen with two choices. Select Delete Task.

        The selected task is deleted from the sequence.

        INSERT GRAPHIC (Sequence of Screens displayed during the Delete Task option) HERE.

      4. Repeat the above two steps for removing any additional tasks.

      5. Save the sequence by selecting Store.

    10. To remove a particular sequence:

      Load the sequence by selecting the sequence from the Sequence Files screen, which is displayed by selcting List... . Select Remove.

      The selected sequence is deleted from the Deterministic Scheduler.

      Note -

      The tasks associated with the deleted sequence are not deleted.

    11. To insert a task in a particular position in the current tasks within a sequence:

      1. Load the sequence by selecting the sequence from the Sequence Name in the Sequence Manager screen.

      2. Select Task Insert/Delete ->Delete Task / Set Task Insert Mark.

      3. Select the task that is directly above the place where you want the new task inserted.

        This displays another screen with Insert Task.

      4. Select the Insert Task.

        This marks your insertion point. Any task you add after this step, in this sequence, will be located below this insertion mark.

      5. Repeat Step d through Step e to insert additional tasks.

    12. To save the sequence for future use, enter a name in the Sequence Name field and select Store in the Sequence Manager screen.

  5. Running the sequence:

    1. Invoke the Sequence Runner screen by selecting Sequence Runner in the Start DS menu.

      INSERT GRAPHIC (Sequence Runner Screen) HERE.

    2. Select the sequence that you want to run by using List... .

      The tasks in this selected sequence are listed under Tasks In Sequence field in Sequence Runner screen. Use Control-F or Control-B to view all the tasks.

    3. Change the Total Loop value to the number of times you desire to repeate the sequence of tests.

      Note -

      The default and minimum number of Total Loops value is 1. You can change the Total Loop value to the desired value, up to a maximum of 10 loops.

    4. Select the Start button to start the sequence.

      While testing is underway, you can do any of the following:

      • Monitor the test progress in the TTY Status panel. All test results are logged in the SunVTS log files.

      • Close the Sequence Runner screen by selecting the Quit DS UI from the Quit DS menu. Testing will continue, and results will be displayed in the TTY Status panel.

        Note -

        When the DS is in running mode, the selection of Show DS displays the Sequence Runner screen. Otherwise, this selection causes the Start DS menu to display.

      • Suspend and resume the sequence by selcting the Suspend and Resume commands in the Sequence Runner screen.

  6. Use the Reset button to reset the TTY Status panel and Deterministic Scheduler.

    The TTY Status panel tests statistics and the Deterministic Scheduler's current loop count are reset.

  7. To quit the Deterministic Scheduler when you are done, select dsched->Quit DS Options->Quit DS.