C H A P T E R 2 |
Installing and Removing SunVTS |
This chapter describes how to install and remove the SunVTS diagnostic program:
SunVTS packages are located on the Solaris Software DVDs that ship with the Solaris release.
The SunVTS following table lists and describes the required SunVTS packages. These packages are not installed by default.
The Solaris 10 operating system must be installed (with the Entire Distribution software group [SUNWCall] at minimum), and booted to multi-user level (run level 3).
There must be at least 62 MB of available disk space in the partition where SunVTS will reside. The /opt directory is the default installation location.
Note - Refer to Appendix B for information about which revisions of SunVTS are supported on different Solaris Operating System releases. |
There are several utilities available for installing packages. This chapter describes how to use the pkgadd utility and Solaris Web Start 2.0 to install SunVTS from a local CD-ROM drive. For information on how to install packages using other installation methods, see the Solaris Sun Hardware Platform Guide.
If you installed SunVTS software from a previous release, you should remove all packages associated with that release before installing the new SunVTS software. Remove the old SunVTS packages with the same method you installed the packages.
If you installed SunVTS using Web Start 2.0, you must also remove the software using Web Start 2.0. If you installed SunVTS with the pkgadd command, you must also remove the software with the pkgrm command.
1. Log in to the system and become superuser:
2. Check to see if any SunVTS packages are currently installed on the system:
If the system does not display anything, then no SunVTS packages are installed and you can proceed with the installation.
If you see any messages such as the following message, then SunVTS is installed and you should remove the existing SunVTS software before proceeding. See Removing SunVTS.
3. Load the Solaris Software DVD into the DVD-ROM drive.
Volume Manager automatically mounts the DVD.
4. Install SunVTS using pkgadd as shown in one of the examples below.
The following command prompts you to enter the directory where SunVTS will reside instead of using the default (/opt) directory.
Note - If you install SunVTS in a directory other than the default (/opt) directory, you must set the VTS_PM_PATH variable before you use the SunVTS CDE interface. See To Perform Additional Setup When SunVTS Is Installed in a Directory Other Than /opt. |
5. Answer the installation questions.
You are asked if you want to enable the Kerberos-based, Sun Enterprise Authentication Mechanism (SEAM) security which provides the highest level of SunVTS security. You should only enable this if you have the SEAM software installed and the SEAM server and clients configured in your networked environment. Refer to SunVTS Security. You can always answer no to this question, even when SEAM is configured in your environment.
If you choose to run SunVTS with SEAM security, use the following SEAM assignments:
Complete Service Name--set to sunvts@host, where host is the fully qualified domain name of the host where the SunVTS kernel is running.
6. Install the SunVTS supporting packages that are appropriate for your configuration. (See SunVTS Packages for more details.)
Note - Type -a none option again if you used it for the installation of SUNWvts. |
Note - The configd packages (SUNWeswsa, SUNWsycfd, SUNWesnta, and SUNWeswga) are no longer needed, and no longer supplied, for physical mapping support. |
7. Verify the presence of the packages:
# pkginfo SUNWvts SUNWvtsts SUNWvtsmn system SUNWvts SunVTS system SUNWvtsmn SunVTS Man Pages system SUNWvtsts SunVTS |
|
1. Insert the Solaris Software Supplement CD into your CD ROM drive.
If your system is running Sun Enterprise Volume Manager, it should automatically mount the CD-ROM to the /cdrom/cdrom0 directory.
If your system is not running Sun Enterprise Volume Manager, mount the CD-ROM as follows:
2. In a terminal window, type the following:
3. When the Solaris Web Start GUI is displayed, select Next.
4. Select Default Install or Custom Install from the Solaris Web Start GUI.
a. If you want to install all of the default installed software, select Default Install, then select Next. SunVTS software is installed by default if you select Default Install. See the Solaris Sun Hardware Platform Guide for a list of what software is installed by default.
b. If you only want to install some of the software products, select Custom Install, then select Next. Select the software you want to install, then select Next.
Use the Product Registry utility (/usr/bin/prodreg) and select the product to be removed.
|
The SunVTS man pages are installed in the SunVTS_install_dir/man directory
(/opt/SUNWvts/man by default). To access them, add this directory to your MANPATH shell variable in the initialization file that corresponds to your login shell (usually .profile for the Bourne and Korn shells or .login for the C shell).
1. Using an editor, add the SunVTS man directory (/opt/SUNWvts/man by default) to the MANPATH variable in the appropriate initialization file.
2. Have the shell read the modified initialization file by sourcing it (with the . [dot] or source command) or log out and log back in.
3. Verify that the SunVTS man directory is part of the MANPATH variable:
Note - For more information about customizing a user's work environment, shell variables, and initialization files, refer to your Solaris system administration guides. |
|
When you install SunVTS in a directory other than the default directory (/opt), you must set the VTS_PM_PATH environment variable before you can use the SunVTS CDE user interface. This variable is used to locate graphic elements in the SunVTS CDE interface.
Note - The VTS_PM_PATH variable is not required if SunVTS is installed in the default directory (/opt). |
1. Using an editor, open the appropriate initialization file such as .profile (for the Bourne or Korn shells) or .login (for the C shell).
2. Add the VTS_PM_PATH variable as shown:
3. Have the shell read the modified initialization file by sourcing it (with the . [dot] or source command) or log out and log back in.
SunVTS has two security mechanisms that you can choose from:
(SEAM) to provide secure user authentication, data integrity and privacy, for transactions over networks using a Kerberos V5 technology.
The SunVTS installation process prompts you to specify which security mechanism you want to use. You must use one or the other, and the SEAM security implementation is the default if you press the return key through the installation questions.
The SunVTS user interface (vtsui and vtstty) must connect to the SunVTS kernel (vtsk) before it can be used to control testing. The SunVTS kernel selectively accepts "connect to" requests from the SunVTS interface based on entries in the SunVTS_install_dir/bin/.sunvts_sec file. Connection permission is governed by three categories in this file as follows:
HOSTS--if the requesting user is on a host that belongs to the HOSTS category, then this request is granted without any authentication.
GROUPS--if the requesting user is a member in a group that is a member of GROUPS category, then the user interface will prompt the user for a password. The SunVTS kernel compares this password against the password database on the system under test (SUT). If the password does not match, or if the user is not on the list, then the connection is rejected.
USERS--if the requesting user is a member of the USER category, then the user interface will prompt the user for a password. The SunVTS kernel compares this password against the password database on the SUT. If the password does not match, or the user is not on the list, then the connection is rejected.
A plus (+) entry in one of these categories means all hosts, groups, or users, are trusted.
The user password needed for authentication is the same password used to log in to the system under test.
The check for connection permission starts with the HOSTS category, then the GROUP category, and finally, the USERS category. A connection is granted as soon as the connection request matches an entry.
If a security file entry is invalid or if there is no entry in the file, all access except root is denied on the local machine. However, you can correct an entry in this file even while the SunVTS kernel is running.
When you specify the -e option while starting the SunVTS kernel, the kernel accepts "connect to" requests from any host, regardless of the entries in the .sunvts_sec file.
Note - As of SunVTS 3.1, the .sunvts_sec file, by default, is configured for root on the system under test. All other "connect to" requests are rejected. |
Note - The .sunvts_sec file is bypassed if you enable the SEAM security. |
The following shows the contents of the default .sunvts_sec file.
Code Example of the Security File (.sunvts_sec):
To use SEAM-based security with SunVTS, you must have the following:
The complete SEAM 1.0.1 client/server application must be installed and running in your network environment.
The systems for which you install SunVTS must have, at minimum, the SEAM 1.0.1 client software installed.
The SunVTS SEAM security system is based on Kerberos V5 technology, which revolves around the concept of a ticket. A ticket is a set of electronic information that serves as identification for a user or a service. When you connect to another host through SunVTS, you transparently send a request for a ticket to a Key Distribution Center (KDC), which accesses a database to authenticate your identity. The KDC returns a ticket granting you permission to access the other machine. "Transparently" means that you do not need to explicitly request a ticket; it happens in the background as part of the remote connection. No user password is transmitted in the network. Only the authenticated client can get a ticket for a specific service; another client cannot gain access under an assumed identity.
If you choose to run SunVTS with SEAM security, use the following SEAM assignments:
Complete Service Name--set to sunvts@host, where host is the fully qualified domain name of the host where the SunVTS kernel is running.
The best time to establish the SunVTS security mode is during the SunVTS installation.
1. Decide which level of security you want to use with SunVTS.
If you decide to use the SEAM security (highest level of security), make sure that your system is running SEAM.
2. Install SunVTS as described in Installing SunVTS.
The installation program asks you if you want SEAM security enabled. Answer accordingly:
Yes (the default)--The Kerberos SEAM security is enabled for SunVTS. No additional action is required to administer SunVTS security. SunVTS uses the authentication as defined in the SEAM software configuration in your network environment to grant and deny access to SunVTS. Do NOT select this security scheme if you do not have the SEAM software installed and configured in your network environment.
No--The basic security file is used, and SEAM is not enabled. When the installation is complete, you can access SunVTS as superuser on the system under test, or modify the .sunvts_sec file to authorize other users.
If you need to switch the security from SEAM to basic, or vice-versa, after you have installed SunVTS, follow these steps:
2. Make sure that SunVTS is not started.
3. Change directories to the SunVTS binary directory:
Note - If SunVTS is installed in a directory other than /opt, adjust your references accordingly. |
4. With an editor, open the .sunvts_sec_gss file.
This file contains one line that is appended with one of the following:
5. Change the ON (or OFF) value to the opposite value, save the change, and quit the editor.
Note - The ON and OFF values are case sensitive. Make sure you specify them using capital letters. |
The security mechanism that you specified is enabled.
Use environment variables to control certain aspects of SunVTS as described in the following table. Except for the MANPATH variable, you only use these variables when you need to alter the default characteristics of SunVTS.
Used by disktest when you want to run subtests that require SunVTS to pre-mount all mountable partitions. Refer to the disktest chapter in the SunVTS Test Reference Manual for details. |
|
Append the MANPATH variable with the location of the SunVTS man page location (/opt/SUNWvts/man by default) so the man command can locate and display the SunVTS man pages. See To Set Up Access to the SunVTS Man Pages. |
|
Used by the vts_cmd command to specify the hostname for the SunVTS kernel to connect to. Refer to the vts_cmd man page for details. |
|
As of SunVTS 5.0, this variable is no longer supported. It was used to display test messages in a pre-SunVTS 4.0 format, usually because a script relies on the older format. Now your scripts must accept the current SunVTS message formtat. |
|
Only used when SunVTS is not installed in the default directory
|
SunVTS software is available in English, and is Internationalization (I18N) compliant, which means it is structured in a way that a user who is familiar with internationalization can take advantage of this feature to run SunVTS in a localized environment.
In a localized environment, you can run SunVTS in English or with localized fonts. Perform one of the two following procedures based on how you want SunVTS to run.
|
Set the LANG variable to English before you start SunVTS. The following is an example using the C shell:
|
1. As superuser, create a directory as follows:
Where LANG is the language code (for example, ja for Japan EUC, or fr for French) for the language that you are using.
2. Copy the SunVTS Xresource (Vtsui) file into the directory you just created:
Note - The example above is based on installing SunVTS in the default (/opt) directory. If SunVTS is installed in different directory, adjust the pathnames accordingly. |
3. Customize the font definitions in the Vtsui file to accommodate font specifications required by your localized environment.
Developers can add their own custom tests to the SunVTS environment. This book does not describe custom test development, but does list the tasks necessary to add a custom test into the SunVTS environment.
|
1. Copy your custom test binary to the SunVTS bin directory based on the 32-bit or 64-bit functionality of your binary test:
2. Modify one of the following .customtest files based on the 32-bit or 64-bit functionality of your binary test:
The format of the .customtest file is described in The .customtest File Format.
3. Restart SunVTS or reprobe the system.
When invoked, SunVTS displays the custom test in the SunVTS user interface.
The .customtest file defines the test options and the default option values for your custom test. The tester can change these options using the option dialog boxes through the SunVTS user interface. However, the Reset button returns the options to the default settings as defined in the .customtest file.
Each line in this file is made up of two or more fields that are separated by a semicolon where:
The third field is an option line (optional field). If used, this field must be in the format specified.
To specify more than one option, separate each option by a comma:
SunVTS invokes the above test as follows:
You cannot use the .customtest file when a test has a probe attached. You must ensure that the binaries are compatible with the version of the Solaris kernel on which SunVTS is currently running.
Note - If .customtest is renamed as .customtest-group, all of the associated tests will appear under the specified group. |
It is necessary to remove SunVTS before installing a new version. The following instructions describe how to remove SunVTS using the pkgrm command.
Use the same tool or utility for installation and removal of the SunVTS software. If you use pkgadd for installation, use pkgrm to uninstall; if you use Web Start for installation, use the product registry to uninstall.
|
1. Log in to the system and become superuser.
2. Remove the packages with the pkgrm command:
Note - As of SunVTS 5.0, the SUNWvtsol package is obsolete. You should remove it if it is installed on the system for which you plan to install SunVTS 6.0. |
Copyright © 2006, Sun Microsystems, Inc. All Rights Reserved.