CHAPTER 2

Using SunVTS

---

SunVTS 2.1 is not compatible with previous versions. Earlier user interfaces, tests, and option files will not work with the SunVTS 2.1 kernel, and vice versa.

---

Software Requirements

The default Graphical User Interface (GUI) is the Common Desktop Environment (CDE). The CDE GUI requires that the CDE End User Software be installed, or at least the SUNWdtbas package from it. See your system administrator for assistance in installing the CDE software.

---

Note - The CDE GUI is not designed to run in the OPEN LOOK environment.

---

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.

ariela% 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 the OPEN LOOK library is installed.

ariela% setenv LD_LIBRARY_PATH pathname

Check the existing LD_LIBRARY_PATH by typing env.

---

Starting SunVTS

This section tells you how to start both the SunVTS kernel and a user interface of your choice. You can also start SunVTS remotely, on a standalone system, with or without starting the kernel or user interface. These options are covered in Chapter 3, "User Interfaces."

---

Note - Do not use the ampersand (&) to run SunVTS in the background.

---

Read the sunvts syntax descriptions in TABLE 2-1 before starting SunVTS. You can start SunVTS without using any of these options.

The SunVTS GUI interface is displayed if a window environment is running; if not, the SunVTS TTY interface is displayed. If the SunVTS kernel (vtsk) is already running on your system, sunvts starts only the user interface.

---

Note - When SunVTS is invoked, the default GUI is selected according to the following criteria:

When the CDE window manager (DTWM) is running, the default GUI is CDE. When the OPEN LOOK window manager (OLWM) is running, the default GUI is OPEN LOOK.

If no window manager is running, then the TTY window is displayed.

---

TABLE 2-1 shows the full syntax of the sunvts command.

TABLE 2-1 The sunvts Syntax

/opt/SUNWvts/bin/sunvts [-tqpvsel] [-o options_file] [-f logfile_directory] [-h hostname] Argument Description -e Disables the connection permission checking feature -f logfile_directory*Specifies an alternative logfile directory other than the default directory /var/opt/SUNWvts/logs -h hostname Starts the user interface (vtsui or vtstty) on the local machine and tries to connect to the SunVTS kernel (vtsk) of the specified host machine. If hostname is the same hostname of the machine on which the tests are being run, sunvts starts the SunVTS kernel (vtsk). If vtsk is already running on the test system, the sunvts command ignores the -o, -f,-q, -p, and -s options -l Starts the OPEN LOOK user interface -o options_file Starts the SunVTS kernel with the test options loaded from the options_file; these options are saved by the user interface and are stored in the /var/opt/SUNWvts/options directory -p Starts the SunVTS kernel, but does not probe the test system's devices -q Automatically quits both the SunVTS kernel and the user interface when testing stops -s Automatically starts testing a selected group of tests; the flag must be used with the -o options_file flag -t Starts vtstty, a TTY-based program, instead of a GUI. If you do not specify this option and the system is running CDE, sunvts starts vtsui; or, if the system is running OPEN LOOK, sunvts starts vtsui.ol -v Displays version information from the SunVTS kernel and GUI * If the -f argument is exercised when running SyMON, a logfile_directory cannot be created.

In a Window Environment

· To start the SunVTS kernel (vtsk) and the CDE GUI (vtsui), type:

# /opt/SUNWvts/bin/sunvts

· To start the SunVTS kernel (vtsk) and the OPEN LOOK GUI (vtsui.ol), type:

# /opt/SUNWvts/bin/sunvts -l

In TTY Mode

· To start the SunVTS kernel (vtsk) and the TTY-based user interface (vtstty), specify the -t option by typing:

# /opt/SUNWvts/bin/sunvts -t

Using Other Commands to Start SunVTS

The sunvts command starts both the SunVTS kernel and a user interface. In some situations, however, you may not want to start both the kernel and the user interface. If the test machine is already running the SunVTS kernel, you may only want to start the user interface. On the other hand, you may want to start just the SunVTS kernel and leave it running as a background process.

· To start the SunVTS kernel using vtsk, type:

# /opt/SUNWvts/bin/vtsk

The SunVTS kernel then probes the system devices and waits for commands from an interface. See TABLE 2-2 for the vtsk application syntax.

TABLE 2-2 vtsk

/opt/SUNWvts/bin/vtsk [-epqsv] [-o options_file] [-f logfile_directory]
Argument.....Description
-e.......Disables the connection permission checking feature -f logfile_directory* Specifies an alternative logfile directory, other than the default directory /var/opt/SUNWvts/logs -o options_file]..Starts the SunVTS kernel with the test options saved in the options_file; these options are saved and stored in the /var/opt/ SUNWvts/options directory -p.......Starts the SunVTS kernel, but does not probe test system devices -q.......Quits both the SunVTS kernel and the user interface when testing is complete -s.......Starts testing a selected group of tests; this flag must be used with the -o options_file flag -v.......Displays only the version information from the SunVTS kernel, vtsk; this option does not start the vtsk daemon * If the -f option is exercised when running SyMON, a logfile_directory cannot be created.

· To start only the CDE interface, type:

% /opt/SUNWvts/bin/vtsui

· To start only the OPEN LOOK interface, type:

% /opt/SUNWvts/bin/vtsui.ol

---

Note - You do not need to be superuser (root) to start the user interface.

---

If the SunVTS kernel is running on the test system, vtsui (or vtsui.ol) automatically connects to this kernel to start the CDE (or OPEN LOOK) interface.

· To Connect to a Remote Machine's SunVTS Kernel

· To start the CDE interface, type:

% ./vtsui -h hostname

· To start the OPEN LOOK interface type:

% ./vtsui.ol -h hostname

TABLE 2-3 contains a complete listing of the vtsui arguments.

TABLE 2-3 vtsui

/opt/SUNWvts/bin/vtsui.ol (or vtsui) [-v] [-h hostname] [-q quit]
Argument	Description
-h hostname	Starts the user interface and tries to connect to the SunVTS kernel (vtsk) of the specified host machine
-q quit	Quits vtsui.ol when testing is completed
-v	Prints the version number of vtsui.ol

Using vtstty to Start the TTY Interface

If the SunVTS kernel (vtsk) is already running on the test system, you can use the vtstty command to start the SunVTS TTY interface. This command is in the SunVTS bin directory, /opt/SUNWvts/bin.

· To start the TTY interface, type:

% /opt/SUNWvts/bin/vtstty

---

Note - You do not need to be superuser (root) to start the user interface.

---

If the SunVTS kernel is running on the test system, vtstty automatically connects to this kernel and starts the TTY interface.

· To connect to a remote machine's SunVTS kernel, type:

% /vtstty -h hostname

See TABLE 2-4 for a complete listing of the vtstty arguments.

TABLE 2-4 vtstty

/opt/SUNWvts/bin/vtstty [-v] [-h hostname]
Argument	Description
-h hostname	Starts the user interface (vtsui or vtstty) and tries to connect to the SunVTS kernel (vtsk) of the specified host machine
-v	Displays version information from vtstty

· To Run the TTY Interface in a telnet or tip Window

If you want to display the SunVTS TTY interface on a telnet or tip window, you need to set the correct terminal type and the number of columns and rows in the window before starting the interface.

1. Before starting the telnet session, type stty to display the settings of the terminal.

hostname% stty speed 9600 baud; -parity hupcl rows = 39; columns = 94; ypixels = 0; xpixels = 0; swtch = <undef>; brkint -inpck -istrip icrnl -ixany imaxbel onlcr echo echoe echok echoctl echoke iexten

---

Note - Write down the values of the rows and columns settings. You will need these values for Step 4.

---

2. Connect to the test system using either the tip or telnet commands.

---

Note - Refer to the telnet(1) and tip(1) man pages for more information about these protocols.

---

3. To set the correct terminal, type set term=sun-cmd.

   In this example, the terminal is a Sun Workstation^(TM).

remotehost% set term=sun-cmd

4. Use the stty command to set the number or rows and columns in the window.

remotehost% stty rows 39 remotehost% stty columns 94

---

Using SunVTS on a Remote Machine

You can view and control a SunVTS testing session over modem lines or over a network. You can view the progress of a testing session, change testing options, and control all testing features of another machine on the network with a remote machine. FIGURE 2-1 and FIGURE 2-2 show examples of how to connect to a remote machine over modem lines and over a network.

FIGURE 2-1

FIGURE 2-2

You can run SunVTS on a remote machine in two ways:

• Connect the user interface to the SunVTS remote machine using the -h hostname option.

• Remotely log on to the machine as superuser, start the SunVTS kernel, and display the user interface on your machine.

· To connect the User Interface to a Remote SunVTS Kernel, specify the -h hostname option, by typing:

# /opt/SUNWvts/bin/sunvts -h remote_hostname

If the user interface is already running on your local machine, you can use the Connect to option to connect to a remote machine's SunVTS kernel. (See "Host (Connect to) Button" in Chapter 3, "User Interfaces" for more instructions.)

---

Note - If you run SunVTS in the OPEN LOOK environment, you must have display permissions.

---

· To Run SunVTS on a Remote Machine

1. Use xhost to give remote server access to your system before logging in.

% /usr/openwin/bin/xhost + remote_hostname

2. Replace remote_hostname with the remote machine host name.

3. Log in to the remote machine as superuser (root).

4. Change directories to the SunVTS bin directory, which is /opt/SUNWvts/bin by default.

5. Use the sunvts command to start the SunVTS kernel and display the user interface on your machine:

# ./sunvts -display local_hostname:0

a. Replace local_hostname with your local machine's host name.

---

SunVTS on a Standalone System

Some SunVTS applications require a network connection to run successfully. However, you can run SunVTS on a standalone system.

· To Run SunVTS on a Standalone System

1. Edit the /etc/rc2.d/S72inetsvc script file, and comment out the following line:

# /usr/sbin/ifconfig -au netmask + broadcast +

2. Comment out any remotely mounted file systems from the /etc/vfstab file.

   Remotely mounted file systems are not required on a standalone system.

3. Make sure ypbind is not running on the standalone system.

   Doing this ensures that ypbind is not started by the rc scripts.

4. Reboot your system.

   Now you can run SunVTS on a standalone machine.

Invoking the SunVTS Kernel (Auto Invoke)

By using the inetd feature, you no longer have to start up the sunvts kernel before attempting to connect to it. This new feature uses the inetd system facility that automatically triggers the sunvts kernel when a user interface connection request is received.

When the sunvts package is installed, all relevant setup files are modified. These same files are later cleaned up when the package is removed.

---

Quitting SunVTS

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

· To stop testing from the CDE GUI toolbar, select the Stop button.

· To stop testing from the CDE GUI Commands pull-down menu, select Stop Testing.

· To quit SunVTS from the CDE GUI Commands pull-down menu, select the Quit SunVTS submenu and drag to display the following choices:

• vts kernel and ui--terminates the user interface and the SunVTS kernel
• vts kernel--terminates only the SunVTS kernel
• vts ui--terminates only the user interface

---

Security

The SunVTS user interface running on one host can control the SunVTS kernel running on a system under test, often referred to as SUT. The user interface has to connect to the SunVTS kernel before it can control the SunVTS kernel (see "Host (Connect to) Button" in Chapter 3, "User Interfaces" for more information).

The SunVTS kernel authenticates connect requests from the SunVTS interfaces based on one of the following attributes:

• The host from which the request is initiated--If this host belongs to the list of trusted hosts specified, then this request is granted without any authentication.
• The group <groupname> to which the user using a SunVTS UI to SunVTS kernel belongs--This is the user who initiates the Connect to request. If this group is a member of a list of groups specified, then the user interface will prompt the user for a password. The SunVTS kernel compares this password against the system's databases on the system being tested. If the password does not match, or if the user is not on the list, then the connection is rejected.
• The user <username> who initiates the Connect to request using a SunVTS user interface to the SunVTS kernel (vtsk)--If this user is a member of a list of users specified, then the user interface will prompt the user for a password. The SunVTS kernel compares this password against the system's databases on the system being tested. If the password does not match or the user is not on the list, then the connection is rejected.

The list of hosts, groups, and users are specified in the security file, .sunvts_sec, which is installed in the <SunVTS2.1 install directory> /bin. A plus (+) entry in one of these lists means all hosts, groups, or users, respectively. A template of the security file (.sunvts_sec) is located in the <SunVTS2.1 install directory> /bin (see CODE EXAMPLE 2-1).

---

Note - To enable security checking, remove the plus (+) sign in the HOST section of .sunvts_sec, the default.

---

CODE EXAMPLE 2-1 Security File Template

#This file should be <SunVTS2.1 install directory>/bin/.sunvts_sec # #Any line beginning with a # is a comment line # # Trusted Hosts entry # One hostname per line. # A "+" entry on a line indicates that ALL hosts are Trusted Hosts. # No password authentication is done. # The line with the label HOSTS: is required to have the list of hosts # #HOSTS: + #host1 #host2 # # Trusted Groups entry # One groupname per line. # A "+" entry on a line indicates that ALL groups are Trusted Groups. # User password authentication is done. # The line with the label GROUPS: is required to have the list of groups # #GROUPS: #group1 # # Trusted Users entry # One username per line. # A "+" entry on a line indicates that ALL users are Trusted Users. # User password authentication is done. # The line with the label USERS: is required to have the list of users. #USERS: #user1 #user2

The SunVTS kernel authenticates the request(s) based on the entries in the security file. All access except root is denied on the local machine if the security file entry is invalid or if there is no entry in the file. You can correct an entry in this file even when the SunVTS kernel is running. When you specify the -e option with the SunVTS kernel, then the SunVTS kernel accepts Connect to requests from any host, regardless of the user identification of the SunVTS User Interface process that is initiating it.

---

Note - The user password needed for authentication purposes by vtsk is the same password used to log in to the system you are testing.

---

---

Notification by Email

The email notification feature instructs the SunVTS kernel to send the last couple of lines in the SunVTS error message file to a particular person or alias under certain circumstances during testing.

You can use the Notify pop-up menu in the Set Options menu to send a notification to the destination email address (see FIGURE 2-3 and TABLE 2-5).

FIGURE 2-3

---

Note - Send a test email to make sure the destination email address you specify is valid.

---

TABLE 2-5

Option	Description
Email Address	Indicates the email address where the test status messages are sent (the address is root by default)
Log Period	Sets time periods for receiving emails
Send Email	Determines when and if you want the test status messages sent to you through email. From this menu, you can choose: - Disabled (do not send mail) - Now (send mail immediately) - On Error (send mail when an error occurs) - Periodically (send mail with a time period set in the Log Period option) - On Error and Periodically (send mail when an error occurs as well as periodically)

---

Runtime Considerations

Managing your swap space and running other applications while running SunVTS requires special attention. A detailed discussion of these issues follows.

Managing Swap Space

The amount of SunVTS swap space required varies widely with individual hardware and software configurations. Most systems have enough swap space already configured to meet SunVTS testing requirements.

When you start using SunVTS, the amount of swap space required for testing is calculated. First, a calculation is done to determine the amount of available swap space on the system you are testing. Next, the amount of swap space needed to run the program, the selected tests, and virtual memory is calculated.

If an adequate amount of swap space is not available on your machine, a window pops up (see FIGURE 2-4) and displays the amount of additional swap space needed to run the selected diagnostic tests. In FIGURE 2-4, lightspeed is the host name and audio is an example of a test that could not be started.

FIGURE 2-4

If swap space is not available on your machine to run all of the SunVTS tests, you can either deselect some of the tests or you can add more swap space. (Refer to the System Administration Guide, Volume 1, Part 8, Managing File Systems for information about increasing swap space.)

---

Note - If your system does not have enough swap space configured, some SunVTS tests may run very slowly or the screen may freeze. If this occurs, the SunVTS kernel usually returns error messages, indicating that the problem is due to insufficient swap space.

---

Heavy System Loads

Sluggish response of the SunVTS user interface is normal during heavy testing loads. A slow SunVTS kernel response can cause the user interface to time out. If this happens, reconnect to the SunVTS kernel with the Connect to option.

The Suspend option temporarily stops testing. Use this option during heavy test loads, such as:

• To view log files or Sys Config files
• To invoke specific commands
• To change options

Select the Resume option to continue testing when user interface interaction is completed.

Running Other Applications and SunVTS

The SunVTS virtual memory test (vmem) stresses the system's virtual memory and uses most of the system's swap space. Because of this, you may not be able to run any other processes while testing the system with vmem.

Start non-SunVTS processes (for example, other OPEN LOOK applications) while using SunVTS before you begin running tests.

Using vmem to Reserve Swap Space

Use the vmem Reserve option to reserve swap space for other processes from each instance of the test.

If you plan to start other processes after you start the virtual memory test, you can use the vmem reserve option to set aside swap space for these processes before you begin testing.

For example, if you are running four instances of the test and you need 20 Mbytes of swap space for applications, you can reserve 5 Mbytes of swap space from each of the four instances of the test.

You can select the Reserve option from either the vmem Test Options menu (within the SunVTS control panel) or from the command line.

---

Caution - If metadisk (Online: DiskSuite^(TM)) is running, SunVTS may corrupt data on the metadisk. In this case, before starting SunVTS, set the system environment variable BYPASS_FS_PROBE to 1.

For example:

# BYPASS_FS_PROBE=1; export BYPASS_FS_PROBE
# ./sunvts

---