SunVTS 7.0 Packages and Running Instructions
|
This chapter describes the SunVTS 7.0 software packages, and installation and running of the software. Topics include:
SunVTS 7.0 Packages
The SunVTS packages are delivered on the Solaris DVD.
SunVTS software is installed by default when the operating system is loaded onto the system. To find and upgrade to the latest version of the SunVTS software, refer to the SunVTS documentation at:
http://docs.sun.com/app/docs/prod/test.validate
TABLE 2-1 lists the SunVTS packages that contain the infrastructure and test binaries.
TABLE 2-1 SunVTS 7.0 Software Packages
|
Package name
|
Description
|
|
SUNWvts
|
Contains the test development library APIs and SunVTS kernel. You must install this package to run the SunVTS software.
|
|
SUNWvtsmn
|
Contains the man pages for the SunVTS utilities, including the command-line utility.
|
|
SUNWvtsr
|
Contains the SunVTS framework configuration files in the root partition (superuser)
|
|
SUNWvtss
|
Contains the server and browser user interface (BUI) components that must reside on the server system.
|
|
SUNWvtsts
|
Contains the test binaries for both x86 and SPARC systems.
|
Use the following command to display SunVTS package information:
# pkginfo -l SUNWvts SUNWvtsmn SUNWvtsr SUNWvtss SUNWvtsts
|
You can also use either of the following commands to display additional SunVTS package information:
Or,
Use either of the following two methods to display SunVTS version information:
# cat /usr/sunvts/bin/.version
7.0ps6build5
|
Or,
# cd /usr/sunvts/bin
# ./vts_cmd get_version
7.0ps6build5
|
Installation Requirements
The Solaris 10 5/08 or later, or an OpenSolaris build released after Solaris 10 5/08 must be installed (with the Entire Distribution software group [SUNWCall] at minimum), and booted to the multiuser level (run level 3). You must be superuser (root) to run the tests.
SunVTS 7.0 Man Pages
The SunVTS man pages are installed in the /usr/sunvts/man directory. To access the man pages, add this directory to your MANPATH variable in the initialization that corresponds to your login shell. (usually, .profile for the Bourne and Korn shells or .login for the C shell).
 To Set Up Access to the SunVTS Man Pages
|
1. Using an editor, add the SunVTS man directory (/usr/sunvts/man) to the MANPATH variable in the appropriate initialization file.
Bourne, Korn shell example:
export MANPATH=/usr/share/man:/usr/man:/usr/sunvts/man:$MANPATH
|
C shell example:
setenv MANPATH /usr/share/man:/usr/man:/usr/sunvts/man
|
2. Source the modified initialization file (with the .[dot] or the source command), or log out and log back in.
3. Verify that the SunVTS man directory is part of the MANPATH variable:
# echo $MANPATH
/usr/share/man:/usr/man:/usr/sunvts/man
|
| Note - For more information about customizing a user work environment, shell variables, and the initialization files, refer to your Solaris system administration guides.
|
Requirements for Running SunVTS
The following are required to run SunVTS 7.0:
- The system must be booted to the multiuser level.
- SunVTS software needs Java Web Console in order to use the Browser User Interface (BUI). If your Solaris installation does not have the Java Web Console packages installed, you can obtain the packages from:
http://www.sun.com/download/products.xml?id=46cb72a9
Minimum supported browsers include:
- Mozilla 1.4
- Netscape 6.2
- FireFox 1.0
Runtime Considerations
Before you start SunVTS software, consider the following runtime issues:
- System load - Before you run SunVTS software on your system, consider the added system activity created by SunVTS software and the effect of that activity on users. Depending on the mode that you select, testing can add significantly to your system load or be quite minimal.
- Other applications - Some SunVTS tests stress the system resources (such as virtual memory) to the point that other applications might not run.
- System functionality - SunVTS software is a diagnostic tool. SunVTS software runs only when your system is fully booted to run level 3 (multiuser level). SunVTS software will not run from single-user (maintenance mode) nor from run level 0 (monitor mode).
- Superuser access - For security reasons, you must be superuser to run SunVTS software.
- Graphics tests - When running tests on frame buffers, you must not run any other application or screen saver program that uses the frame buffer. Frame buffer graphic tests print test patterns on the display. This situation temporarily prevents you from working in your window environment.
- Swap space - The amount of swap space required for testing varies widely with individual hardware and software configurations. If an adequate amount of swap space is not available on your system, the status column on the browser user interface displays the message waiting for swap space.
SunVTS Test Procedures Overview
TABLE 2-2 describes the process of testing your system with SunVTS software. The table also provides a brief description and reference to required information.
TABLE 2-2 SunVTS 7.0 Test Procedure Overview
|
Step
|
Procedures
|
Description
|
|
1
|
Become superuser (root).
|
Log in as root or use su to become superuser.
|
|
2
|
Determine the current state of the system you plan to test.
|
Your system is considered online if other applications are running and the system is operating in a production capacity. If the system is online, you should stop the applications and ensure that the system remains offline for the duration of your testing.
|
|
3
|
Start SunVTS
|
Refer to Starting SunVTS.
|
|
4
|
Prepare the devices for testing.
|
Load the required test media and loopback connectors (see SunVTS 7.0 Tests). Test media is required when testing your CD- or DVD-ROM, and diskette drives.
|
|
5
|
Start the User Interface.
|
Refer to Starting the Browser User Interface. Refer to Starting the SunVTS TTY User Interface.
|
|
6
|
Start the SunVTS software.
|
For browser-based interface, click the SunVTS link under the systems category in the Java Web Console and add the host that you want to start testing. For the terminal-based user interface, see Starting the SunVTS TTY User Interface.
|
|
7
|
Set up SunVTS with desired tests selection.
|
Select the desired tests and click Start.
|
|
8
|
Review the test results.
|
Review test results by opening the log files in the system under test located in /var/sunvts/logs.
|
|
9
|
Quit SunVTS.
|
Stop all the tests on the system by clicking the Stop button and the Logout button.
|
Preparing Devices for Testing
Several tests require the installation of media or loopback connectors. Complete such requirements before the SunVTS kernel probes for devices (for example, when SunVTS software is started, or when you run the SunVTS reprobe command. This installation allows the SunVTS kernel to properly identify each device.
You must install media in these devices if you plan to test them in the System Exerciser:
- CD-ROM and DVD drives - Load appropriate media into the drive. The media can be an audio or data CD.
- Diskette drive - Load a scratch diskette in the drive. The diskette test has a read-only mode, but use a scratch tape to avoid inadvertently writing over data.
- Smart card reader - Allocate a scratch smart card for testing purposes because the SmartCard test writes on the card.
- Communication ports - Many of these tests require a loopback connector attached to the port. Attach any required loopback connectors for the ports you plan to test. For more information about connectors, see Appendix A.
- Printer ports - Requires connection to a printer.
Starting SunVTS
You must start SunVTS before selecting a specific user interface: BUI (Chapter 3), TTY (Chapter 5) and CLI (Chapter 6). (See Starting a Specific User Interface.)
To Start SunVTS
|
Type the following:
# cd /usr/sunvts/bin
# ./startsunvts
|
This begins an interactive session. SunVTS starts with the selected user interface.
Starting a Specific User Interface
The following describes how to start SunVTS from a specific user interface.
To Start the BUI on the Same System as the Host Under Test
|
Type the following:
# cd /usr/sunvts/bin
# ./startsunvts -b
|
Or,
# cd /usr/sunvts/bin
# ./startsunvts --bui
|
To Start the BUI on a System Other Than the Host Under Test
|
Two steps are involved in starting the BUI on a system other than the host under test:
1. To start the agent and JavaBridge on the system under test, type:
# cd /usr/sunvts/bin
# ./startsunvts -a
|
Or,
# cd /usr/sunvts/bin
# ./startsunvts --agent
|
2. To bring up the BUI on a different system, type:
# cd /usr/sunvts/bin
# ./startsunvts -s
|
Or,
# cd /usr/sunvts/bin
# ./startsunvts --server
|
To Start the Graphical User Interface on the Same System as the Host Under Test
|
To start the Graphical User Interface (GUI) on the same system as the host under test, type:
# cd /usr/sunvts/bin
# ./startsunvts -g
|
Or,
# cd /usr/sunvts/bin
# ./startsunvts --gui
|
To Start the TTY User Interface on the Same System as the Host Under Test
|
Type the following:
# cd /usr/sunvts/bin
# ./startsunvts -t
|
Or,
# cd /usr/sunvts/bin
# ./startsunvts --tty
|
To Start the Command-Line Interface on the Same System as the Host Under Test
|
Type the following:
# cd /usr/sunvts/bin
# ./startsunvts -c
|
Or,
# cd /usr/sunvts/bin
# ./startsunvts --commandline
|
Help Options
To list Help options, type:
# cd /usr/sunvts/bin
# ./startsunvts -h
|
Or,
# cd /usr/sunvts/bin
# ./startsunvts --help
|
Interpreting 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.
TABLE 2-3 SunVTS Information Message
12/16/07 23:02:52 ctech114 SunVTS7.0build80: VTSID 0
Processor.fputest.INFO All: Version: fputest 7.0 2007/12/04 (7.0 build80)
12/16/07 23:03:13 ctech114 SunVTS7.0build80: VTSID 0
Processor.iutest.INFO cpu-unit: Version: iutest 7.0 2007/12/04 (7.0 build80)
12/16/07 23:03:51 ctech114 SunVTS7.0build80: VTSID 0
Processor.iutest.INFO cpu-unit: Version: iutest 7.0 2007/12/04 (7.0 build80)
12/16/07 23:04:04 ctech114 SunVTS7.0build80: VTSID 0 cddvdtest.INFO
rdsk/c0t0d0s0: Version: cddvdtest 7.0 2007/12/04 (7.0 build80)
12/16/07 23:04:04 ctech114 SunVTS7.0build80: VTSID 2102 cddvdtest.INFO
rdsk/c0t0d0s0: “Media Type = DVD-ROM, Block Size = 2048,
Capacity(blocks) = 1128150,
Max on disk= 4284160
"
12/16/07 23:04:12 ctech114 SunVTS7.0build80: VTSID 0 vmemtest.INFO kmem:
Version: vmemtest 7.0 2007/12/04 (7.0 build80)
12/16/07 23:04:12 ctech114 SunVTS7.0build80: VTSID 0 pmemtest.INFO mem:
Version: pmemtest 7.0 2007/12/04 (7.0 build80)
12/16/07 23:04:27 ctech114 SunVTS7.0build80: VTSID 0
Processor.iutest.INFO cpu-unit: Version: iutest 7.0 2007/12/04 (7.0 build80)
|
TABLE 2-4 SunVTS Error Message
10/08/07 23:47:31 ctech114 SunVTS7.0build75: VTSID 8003
Interconnect.nettest.FATAL ce0(/pci@1c,600000/network@2): “System call
recvfrom returned -1 (Connect
ion refused).”
10/08/07 23:56:40 ctech114 SunVTS7.0build75: VTSID 6049
Graphics.m64test.FATAL fbs/m640: Can’t open display
Probable_Cause(s): <Permission denial from Host> <System error> <X
Server is not running>Recommended_Actions(s): <run xhost(1)> <If X
server is not running
, run X server> <If problem persists, call your authorized SUN service
provider>
10/09/07 03:43:58 ctech114 SunVTS7.0build75: VTSID 8003
Network.nettest.FATAL ce0(/pci@1c,600000/network@2): “System call
recvfrom returned -1 (Connection r
efused).”
10/09/07 10:50:00 ctech114 SunVTS7.0build75: VTSID 8058
Ioports.serialtest.FATAL su0: “Failed ioctl TIOCSILOOP, device =
/dev/term/a. Probable Cause: Port i
s in use. Please verify if a device/cable is connected to the port.
"
10/09/07 10:55:09 ctech114 SunVTS7.0build75: VTSID 8003
Network.nettest.FATAL ce0(/pci@1c,600000/network@2): “System call
recvfrom returned -1 (Connection r
efused).”
10/09/07 10:59:28 ctech114 SunVTS7.0build75: VTSID 6049
Graphics.m64test.FATAL fbs/m640: Can’t open display
Probable_Cause(s): <Permission denial from Host> <System error> <X
Server is not running>Recommended_Actions(s): <run xhost(1)> <If X
server is not running
, run X server> <If problem persists, call your authorized SUN service
provider>
10/09/07 19:07:20 ctech114 SunVTS7.0build75: VTSID 8003
Interconnect.nettest.FATAL ce0(/pci@1c,600000/network@2): “System call
recvfrom returned -1 (Connect
ion refused).”
|
Whenever possible, the error message supplies a message type, followed by the message text, one or more probable causes, and one or more recommended corrective actions. TABLE 2-5 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 2-5 SunVTS 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 encounters a severe condition that might cause the test to exit, such as a failure to open a device. These messages generally do not indicate a hardware failure.
|
|
VERBOSE
|
Verbose Log
|
Test progression messages that are displayed when the verbose feature is enabled.
|
|
WARNING
|
Info log
|
These messages warn you of a condition that might prevent the physical test to run with the test’s full capabilities. These warning messages do not necessarily indicate an error.
|
SunVTS on LDoms Enabled Systems
SunVTS 7.0 functionality is available in the control domain and guest domains on LDoms-enabled Sun SPARC servers.
On the I/O tests side, Disk and Network will show up. I/O ports will show up if a virtual keyboard is present.
If the cryptotest fails, check to see if your guest domain has MAUs configured. To do this, type the following:
# ./ldm list-bindings guest-domain-name|grep -i mau
|
This command displays output if mau is configured.
Backward Compatibility
The SUNWvts (harness and APIs) package guarantees backward compatibility across minor update releases. SunVTS software can be broken across major releases, though.
Displaying Devices Using the VTSprobe Utility
The vtsprobe command lists all of the system testable devices, associated configuration information, and corresponding hardware tests.
% /usr/sunvts/bin/vtsprobe
cmttest(cmt)
CMTstress
Number of testable CMT:8
cputest(CPU)
CPU Test
cryptotest(ncp0)
Crypto Accel Bulk 1.0
Model: N2CP Crypto Accelerator
Device Kind :N2CP-Crypto-Device
disktest(c0t0d0)
Disk-c0t0d0
Capacity: 68.35GB
Controller: mpt0
Vendor: FUJITSU
SUN Id: MAY2073RCSUN72G
Firmware Rev: 0501
Serial Number: 0709S08SHK
Device Kind :disk
cddvdtest(c1t0d0)
CD-ROM(c1t0d0)
Controller: uata0
dtlbtest(dtlb)
Data TLB Test
fputest(FPU)
Floating Point Unit Test
hsclbtest(hsclb)
Host to System Controller Loopback Test
Host to System Controller Loopback Test
iobustest(iobus)
IOBUS
platform = SUNW Sun-Fire-T200
iutest(IU)
Integer Unit Test
l1dcachetest(l1cache)
Level 1 Cache Test
l2sramtest(l2sram)
External Cache Test
mptest(mp)
MPstress
Number of processors:32
netlbtest(e1000g1)
1gbaseT
Port Address: Unknown
Host ID: 8481fe02
netlbtest(e1000g2)
1gbaseT
Port Address: Unknown
Host ID: 8481fe02
netlbtest(e1000g3)
1gbaseT
Port Address: Unknown
Host ID: 8481fe02
nettest(e1000g0)
1kbaseT
Host_Name:
Host Address: 10.12.150.50
Host ID: 8481fe02
Domain Name: blr03-01.India.Sun.COM
pmemtest(mem)
PhysicalMemory
System memory size:32760MB
ramtest(mem)
Memory
Total Physical Memory : 32760MB
serialtest(su0)
SerialPorts
Port a = su0 = /dev/term/a = /devices/...su...a
systest(system)
System Stress Test
System Configuration= Sun Microsystems sun4v
Memory size= 32760 Megabytes
System clock-frequency= 200 MHz
usbtest(kbd)
USB Device
Device information: USB Keyboard
vmemtest(kmem)
VirtualMemory
Total Swap: 27677MB
|
| SunVTS 7.0 Software User’s Guide for Initial Release Through Patch Set 7
|
820-0012-20
|
   
|
Copyright © 2010, Oracle and/or its affiliates. All rights reserved.