#  Copyright(c) 1989-1998 Sun Microsystems, Inc.
#  All rights reserved.
#ident  "@(#)README  1.83  01/02/07  SMI"

SunVTS 4.3 README File
----------------------

Introduction
============

   SunVTS 4.3 is Sun's Validation Test Suite. SunVTS is a comprehensive
   software diagnostic tool that tests and validates Sun hardware by 
   verifying the connectivity and functionality of most hardware controllers
   and devices on Sun platforms.

   The SunVTS 4.3 release is supported in the Solaris 8 04/01 operating 
   environment.

   Solaris       SunOS   SunVTS
   ===========   =====   ======
   8 04/01       5.8     4.3
   8 01/01       5.8     4.2
   8 10/00       5.8     4.1
   8 6/00        5.8     4.0
   8             5.8     4.0
   7 11/99       5.7     3.4
   7 8/99        5.7     3.3
   7 5/99        5.7     3.2
   7 3/99        5.7     3.1
   7             5.7     3.0
   2.6 5/98      5.6     2.1.3
   2.6 3/98      5.6     2.1.2
   2.5.1 11/97   5.5.1   2.1.1

SunVTS 4.3 Package Information
==============================

   SunVTS 4.3 contains 4 packages:
    
   	SUNWvts   - contains the SunVTS kernel, user interface, and the
		    collection of tests.
   	SUNWvtsx  - is a package extension to provide SunVTS 64-bit package 
   		    components.
   	SUNWvtsmn - contains the SunVTS man pages.
        SUNWvtsol - contains the SunVTS OpenWindows components.
                    Note: Prior to 4.1, the SunVTS OpenWindows components
                          were part of the SUNWvts package.  As of SunVTS 4.1, 
			  you must install SUNWvtsol to run the SunVTS 
			  OpenWindows GUI and tests.


SunVTS 4.3 Installation
=======================

   The following example will install SunVTS into the default 
   directory (/opt):
   
   #cd 'directory of SUNWvts' (for example, if loading from the "Solaris 
		       Supplement" CD, "cd /cdrom/cdrom0/SunVTS_4.3/Product")
   #pkgadd -d `pwd` SUNWvts  SUNWvtsmn SUNWvtsx SUNWvtsol
         
   Note: If you want SunVTS to install in a directory other than the 
         default (/opt), use the "-a none" argument with the pkgadd command.
         You will be asked where you want to install the package. 


SunVTS 4.3 Uninstallation
=======================

   The following example will uninstall SunVTS  
		       
   #pkgrm  SUNWvts  SUNWvtsmn SUNWvtsx SUNWvtsol
         


How to run SunVTS 4.3
=====================

   # cd /opt/SUNWvts/bin (or cd to the directory that holds the SUNWvts package)
   
   Choose one of the following commands to start SunVTS:
   # ./sunvts     (to run SunVTS kernel and default GUI on the local machine.)
   # ./sunvts -l  (to run SunVTS kernel and OpenWindows GUI on the local
                   machine.)
   # ./sunvts -t  (to run SunVTS kernel in TTY mode on the local machine.)
   # ./sunvts -h hostname (To connect and test a remote machine 'hostname',
                           but display GUI on the local host.)
   # ./sunvts -display local_hostname:0 (When run remotely, this option starts 
     					SunVTS kernel on the remote machine 
					and the GUI is displayed on the local 
     					machine designated as local_hostname:0)

     Note: Make sure the DISPLAY environment variable is set correctly while
     running "sunvts" remotely. Otherwise SunVTS will use vtstty as the
     default user interface.
			 
     Note: The SUNWvts package must be installed on the local and remote
     machines for the above examples. The SUNWvtsx package must be installed
     on systems that run in 64-bit mode.
     
     Note: The sunvts startup program will start the appropriate SunVTS kernel
     (32-bit or 64-bit) based on the mode that the operating system is
     running.
			 
     More detailed description about sunvts usage and other utility commands
     can be found in the SunVTS 4.3 User's Guide.
   
Special Note on OpenWindows GUI
===============================

   The SunVTS OpenWindows User Interface may not support the latest SunVTS
   features.  For full feature support, use the SunVTS CDE or TTY interface.
   The SunVTS OpenWindows User Interface will be sustained, but not enhanced,
   as long as OpenWindows is supported in the Solaris environment.
   
NEWS update for this release:
=============================

1) New security feature available

   As of SunVTS 4.1, SunVTS can be installed to use the Sun Enterprise 
   Authentication Mechanism (SEAM) to provide secure user authentication, data 
   integrity, and privacy, for transactions over networks using Kerberos V5 
   technology.  Your network environment must have the SEAM server/client 
   software configured for this SunVTS security feature to work.  
   Refer to the SunVTS 4.3 User's Guide for details. 
   SEAM is one of the components in the "Solaris Admin Pack" CD. 

2) The new features added to the SunVTS 4.3 release as follows (compared to 
   SunVTS 4.2):

   Tests:
   -----
   dpmtest           - New test for Daktari storage enclosure .
   mpconstest        - New test to verify the system cache coherency on 
		       multiprocessor systems. 
   l1dcachetest,     - New test to exercise the external cache.
   l2dcachetest

3) The feature enhancements have been added to the SunVTS 4.3 release as 
   follows (compared to SunVTS 4.2):

    RFE#4392732 - SunVTS Physical mapping without configd 
    RFE#4375130 - sptest enhancement for cherrystone.  
    RFE#1205082 - Informative pop-up.
    
    Note: Prior to SunVTS 4.3, it was required to install
    a package that contains Sun Management Center Agent 
    configd program for some platforms. This was required
    for SunVTS Physical mapping feature. This is no longer 
    required. 
 

SunVTS Usage Notes:
===================
  
1) The disktest has the capability of premounting all unmounted disks so 
   that it could run the file system subtests against those disks. 
   (The test would do read-write operations on the file system).  
   However, by default all unmounted disks are left untouched. 

   As of SunVTS 3.0, the disktest probe by default does not pre-mount any
   partitions.  If the user wants SunVTS to pre-mount all the unmounted
   partitions which have filesystem, the user has to set the environment
   variable BYPASS_FS_PROBE to zero.

   For Example:
   # BYPASS_FS_PROBE=0; export BYPASS_FS_PROBE
   # ./sunvts

   However, even if pre-mounting is enabled, SunVTS disk probe does check
   for the existence of Veritas and Solstice Disksuite on the system and
   does not pre-mount any partitions if their presence is detected.

   Caution: Running a media subtest on a disk partition in the WriteRead mode
            may cause data corruption if the same partition is being used by
            other programs.

   Loading an option file that was created when BYPASS_FS_PROBE was set to 0
   (zero) might not work if the BYPASS_FS_PROBE environment variable is no
   longer set to 0 (zero).

   This error is caused when SunVTS expects to use the predefined mount point
   names (/disktest_cntndnsn) that are created when BYPASS_FS_PROBE is set to
   0 (zero), but these mount points do not exist while BYPASS_FS_PROBE is not
   set to 0 (zero).  The workaround is to create two separate option files
   for the two different states of the BYPASS_FS_PROBE environment variable.

2) By default, SunVTS security mode is turned on.  This is a change from the
   earlier revisions prior to SunVTS 3.1. To turn it off or to make
   modifications to the default settings refer to the Security section in this
   README and in the SunVTS 4.3 User's Guide.
   
3) Running SunVTS graphic tests with EStar screen saver enabled may cause a
   graphics test error.  Use 'xset s off' to turn the screen saver functions
   off before starting the test.   When you are done testing, use
   'xset s default' to set the system to its default screen saver
   characteristics.

4) When running SunVTS on large configurations (E.g., E10000) take these issues
   into consideration:

     The OpenWindows GUI (vtsui.ol) can only display up to 1200 devices.  For
     configurations with larger number of devices use the CDE GUI (vtsui)
     or the TTY UI (vtstty) which have support for up to 10000 devices.
   
     The amount of time required for SunVTS to complete its probing and to start
     the interface depends on the size of the SUT's configuration.  A probing
     time of as much as 10 minutes has been observed on a E10000 system with
     about 2000 disks. 
      
5) Option files from SunVTS 2.0 or later, are not backward compatible to
   SunVTS 1.0.
    
6) Running the CDE GUI (vtsui) in the localized environment may not display the
   proper fonts if the vtsui resource file (Vtsui) is not properly translated.
   Refer to the SunVTS 4.3 User's Guide for more information.

7) If the SunVTS kernel (vtsk) was inappropriately killed by SIGKILL (-9), 
   the next time it is started vtsk could possibly hang. Use
   "kill -HUP pid_of_inetd" to reinitialize the inetd if no other significant
   application software is running at the same time. Then restart sunvts.   

8) Running sunvts, vtsui, and vtsui.ol in background (&) mode is 
   not allowed, and is not necessary since SunVTS releases the display
   window once the GUI starts. The same is true while running in TTY-mode,
   vtstty needs the window for display and key-in for input.  
   
9) To display physical mapping, click the "Physical" button next to the 
   "System View". This will result in a re-mapping of the entire GUI test 
   buttons as well as the test status.  Changing the Logical and 
   Physical View during SunVTS testing is NOT recommended because the 
   previous system/test status may get reset. 

10) Do not run SunVTS with the CDE GUI(vtsui) while using the OpenWindows
   environment because you can have problems in the display and pop-up windows
   due to font size differences. Also, if the CDE software is not loaded, two
   required shared libraries, libDtWidget.so and libDtSvc.so, will not be
   present.
   
11) Separate files exist for .customtest and .customtest_OtherDevices in
   64 bit version (SUNWvtsx).  They are by default installed in the directory
   /opt/SUNWvts/bin/sparcv9 whereas the package SUNWvts installs them in
   /opt/SUNWvts/bin for 32 bit version.

12) The environment variable VTS_PM_PATH will be used to locate the pix map
   files when they are not in the default installation directory.  If SunVTS
   is installed under a different base directory from the default, SunVTS
   will issue the following error message about the use of this environment
   variable when it is run.

   ERROR: Unable to locate image files. Please set environment variable
          VTS_PM_PATH to image file directory.

   For example, to set the environment variable in Bourne shell, do the
   following:

   # VTS_PM_PATH=<your-installation-base-directory>/SUNWvts/bin/pm
   # export VTS_PM_PATH
   # ./sunvts

13) Support for 64-bit testing capabilities as supported by Solaris operating
   environment was added since the SunVTS 3.0 release.  However the following
   tests are not supported in 64-bit mode:

      cg14test     isdntest     tcxtest

   More detailed descriptions about the above tests can be found in the 
   SunVTS 4.3 Test Reference Manual.

14) As of SunVTS 3.3, the way that StorEdge-A5XXX devices are grouped in the
   SunVTS System Map (for logical mapping) changed.  Prior to version 3.3,
   the enclosure was grouped under the SENA(n) group and the disks were
   grouped under the SCSI-Devices group.  Now the enclosure and disks are
   both grouped under the StorEdge-A5XXXX_enclosure_name group.

15) As of SunVTS 4.0, the SunVTS messages have a new format by default.

   New format:

        <timestamp> <hostname> "SunVTS<version>:" [VTSID <vts_msgid>
        <modulename>[.<submodulename>][.<insttnum>][(P#)].<vts_msgtype>]
        [<device_pathname>:] <msg_text>

        e.g. 04/19/00 10:46:37 gyver SunVTS4.1: VTSID 35 disktest.1(P4).VERBOSE
             c0t0d0: "Testing 2199312 blocks on disk"

   Old format:

        SUNWvts.<modulename[submodulename]>.<vts_msgid> <timestamp>
        <modulename>.[instnum][(P#)] <device_pathname|hostname> <vts_msgtype>:
        <msg_text>

        e.g. SUNWvts.disktest.35 04/19/00 10:49:27 disktest.1(P4) c0t0d0
	     VERBOSE: "Testing 2199312 blocks on disk"
  
   In the event that you have a script that relies on the old message format,
   there is a new SunVTS environment variable (VTS_OLD_MSG) that you can set 
   so that SunVTS messages are displayed using the old message format. 
   To use the old message format, set the environment variable VTS_OLD_MSG to
   YES.

   Note--the old message format will not be supported in future SunVTS
         releases. The VTS_OLD_MSG variable should only be used temporarily
         until your script is updated to recognize the new message format.

16) Deterministic test scheduler (available from the SunVTS 4.0 release) is
    supported with the CDE GUI only.  The TTY UI support will be available
    in a future release.

17) Automatic Configuration (available from the SunVTS 4.3 release) is 
    supported with the CDE GUI only.  The TTY UI support will be available in 
    a future release.

18) As of SunVTS 4.1, there is a new environment variable.

         VTS_CMD_HOST=<hostname>

    This environment variable is used by vts_cmd.  The hostname is the test
    machine running the SunVTS kernel (vtsk).  If this is not set, vts_cmd
    will attempt to send the commands to the local machine's SunVTS kernel.

19) mpconstest will only run on machines that support the "v8plus"
    instructions. If the "v8plus" instructions are not supported, the test
    will not appear on the Test Selection GUI."


20> To get the cpupmtest to run properly,you must perform the following
    procedure:
  
   a> Disable the Power Management autopm mode by making sure that the
      following lines are in the /etc/power.conf file.

      autoshutdown   30  9:00  9:00   noshutdown
      autopm         disable

   b>   Make sure the following line is in the /etc/system file.

        set us:us_direct_pm = 0x1

21)   For sctest , the smart card hardware needs to be initialized properly
      as a part of  hardware installation or during bootup. If it is
      not initialized, the test will fail  printing the message
      "Card detection test failed"  in sunvts.err file .


SunVTS Overview 
===============

SunVTS TEST MODES
-----------------

SunVTS 4.3 has the following supported test modes:

  Connection Test:	Minimal access of device to verify
			accessibility/availability.

  Functional Test:	Detailed tests to thoroughly test device/system on an  
	(default)	"offline" system. In addition, there is a "stress"
                        sub-mode that can be selected during functional
                        testing for the purpose of stress testing.

  Auto Config:		Invokes Automatic Configuration.

			
Online Diagnostics
------------------

As of SunVTS 4.3, the SunVTS online testing capability which was initiated 
using the vtsui.online command is no longer available. The SUNWodu package 
providing this online testing functionality has been removed. 

Online Diagnostic testing of Sun systems is now available through the Sun 
Management Center software using the Sun Hardware Diagnostic Suite add-on 
software. Refer to http://www.sun.com/sunmanagementcenter for details.


SECURITY
--------

SunVTS has two security mechanisms, basic security and SEAM security.
Refer to the SunVTS 4.3 User's Guide.


Logfile and Option File Directory 
---------------------------------

Default log directory is /var/opt/SUNWvts/logs.
Default option file directory is /var/opt/SUNWvts/options.


Internationalization
--------------------

SunVTS 4.3 is I18N compliant.

SunVTS 4.3 software has an internationalization hook available. However, 
there is no specific language, other than English, localized so far. 
The hook is therefore not fully verified. A user needs to be familiar with 
internationalization to use this feature. If you are running SunVTS in
English, in a locale environment and the font display is not right, refer
to the installation chapter of the SunVTS 4.3 User's Guide for additional
instructions.

All test messages are located in the /opt/SUNWvts/lib/locale/C/LC_MESSAGES
directory (assuming SunVTS was installed in the default directory). The CDE
GUI resource file, Vtsui, can be found in /opt/SUNWvts/lib/Vtsui.


Year 2000 
---------

SunVTS 4.3 is Y2000 compliant.


Other Documents Available
=========================

   SunVTS 4.3 User's Guide 
   SunVTS 4.3 Test Reference Manual 
   SunVTS Quick Reference Card 

   These documents will become part of Solaris 8 04/01  on Sun Hardware 
   AnswerBook set.  These and other documents can be accessed at 
   http://docs.sun.com.
