Skip Navigation Links | |
Exit Print View | |
![]() |
Oracle VTS 7.0 Software User's Guide for Patch Set 8 and Subsequent Compatible Releases |
Installing or Updating the Software
Determine Installed Software Version
Determine Installed Package Version for Oracle Solaris 11 Updates
Determine Installed Package Version for Oracle Solaris 10 Updates
Obtaining Packages for Installation
Install the Software for Oracle Solaris 11
Install the Software for Oracle Solaris 10 Updates
Upgrade the Software for Oracle Solaris 11
Upgrade the Software for Oracle Solaris 10 Updates
Uninstall the Software for Oracle Solaris 11
Uninstall the Software for Oracle Solaris 10 Updates
Preparing to Start the Software
Starting the Software (Interface)
Starting the Software (No Interface)
Start Memory Sub System Testing
Start Testing in all Stress Levels
Start Testing With Time Information
Starting the Software (CD/DVD)
Start the Software (Bootable CD/DVD)
Configuring the Test Session (GUI)
View the Host Configuration (GUI)
Change Individual Test Options (GUI)
Use the Auto Mode Sequencer (GUI)
Saving a Test Session Configuration for Repeated Use (GUI)
Create and Save a Test Session (GUI)
To Create a Configuration File to Load Sessions From a User Defined Location
Keyboard Commands for Navigation (TTY UI)
Display TTY UI HELP and Release Table
View the Host System Configuration (TTY UI)
Configuring the Test Session (TTY UI)
Change Global Options (TTY UI)
Select Devices to Test (TTY UI)
Change Individual Test Options (TTY UI)
Begin the Test Session (TTY UI)
Stop the Test Session (TTY UI)
Reset the Test Session Results (TTY UI)
Saving a Test Configuration for Repeated Use
Create and Save a Test Session (TTY UI)
Delete a Test Session (TTY UI)
Use the Auto Mode Sequencer (TTY UI)
Configuring the Test Session (CLI)
Display and Set a Test Mode (CLI)
Display and Set Global Options (CLI)
Change Individual Test Options (CLI)
Monitor the Test Session (CLI)
Saving a Test Configuration for Repeated use (CLI)
Create and Save a Test Session (CLI)
Use the Auto Mode Sequencer (CLI)
Using the Oracle VTS 7.0 PS16 Bootable Image Built on Oracle Solaris 11 Update Release
Using the Oracle VTS 7.0 PS13 or Older Bootable Image Built on Oracle Solaris 10 and Update Release
Use the Service Processor to Boot From the VTS Image
Expected Behavior in Different Use Cases
Exiting the Auto Mode Sequencer
Create a Configuration File for the Unsafe Option
Disk Test Options (Configuration File)
Disable the Solaris Screen Saver
Check Presence of ast Driver on T4 System
Host Bus Adapter Test Options Through Configuration File
Live-Network Port Testing Settings
Io_Interconnect Test Options Through Configuration File
Memory Test Swap Space Requirements
Memory Test Options Through Configuration File
Live-Network Port Testing Settings
Removable Disk Test Options Through Configuration File
Supported Configuration Parameters
VTS Harness Configuration File Parameters
Disk Test Configuration File Parameters
Removable Disk Test Configuration File Parameters
Host Bus Adapter Test Configuration File Parameters
Io_Interconnect Test Configuration File Parameters
Memory Test Configuration File Parameters
Network Test Configuration File Parameters
25-Pin Port A-to-A Port B-to-B Plug
9-Pin to 9-Pin Port-to-Port Cable
TPE Cable for Gigabit and 10/100 Ethernet
9-Pin Male DB-9 External Connector
Oracle VTS runs without any error messages, and probes the devices and registers the tests. The user can view a partial completion of a System Exercisor run on an LDOM. The following example displays a System Exercisor run as observed on PS17.1 on an LDOM.
stname:DB_ORACLE~~~Model:sun4v-platform~~~Oracle VTS 7.0ps17.1qqqqqqqk x stop reset quit reprobe test_mode global_options x x session log_files mode_sequencer host_conf help x mqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqj l**********************************Test_Groups*********************************k x [*]Memory Options testing(Pass=7/Error=0) x x [*]Ioports Options testing(Pass=1338/Error=0) x x [*]Network Options failed(Pass=0/Error=1) x x [*]Processor Options testing(Pass=5/Error=0) x x x x x x x x x x x x x x x x x x x m******************************************************************************j lqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqStatusqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqk x System_status:testing x xElapsed_time:003:35:17 Total_errors:1 x xSession_Name: Test_Mode:System Exerciser x mqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqj
The network test can fail as it relies on the ability to use loopback interfaces, which is not possible in a logical representation of a NIC, such as a vNIC.
Similar to the System Exercisor, the Component Stress run registers devices that can be probed, and enables tests by default. Power test is not enabled on an LDOM.
The following example displays a typical run as observed on an LDOM with PS17.1 installed.
?*************Hostname:DB_ORACLE~~~Model:sun4v-platform~~~Oracle VTS 7.0ps17.1*************? ? stop reset quit reprobe test_mode global_options ? ? session log_files mode_sequencer host_conf help ? ?******************************************************************************************? ?????????????????????????????????????????Test_Groups???????????????????????????????????????? ? [*]System_Interconnect Options idle(Pass=2/Error=0) ? ? [*]Io_Interconnect Options testing(Pass=1/Error=0) ? ? [*]Processor Options idle(Pass=1/Error=0) ? ? [*]Memory Options idle(Pass=1/Error=0) ? ? [ ]Power Options idle(Pass=0/Error=0) ? ? [*]Ioports Options idle(Pass=1/Error=0) ? ? [*]Network Options failed(Pass=0/Error=1) ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ???????????????????????????????????????????????????????????????????????????????????????????? ???????????????????????????????????????????Status??????????????????????????????????????????? ? System_status:testing ? ?Elapsed_time:066:04:05 Total_errors:1 ? ?Session_Name: Test_Mode:Component Stress ? ????????????????????????????????????????????????????????????????????????????????????????????
Unlike a System Exercisor run, the Component Stress is not limited by an upper time limit and continues to run until finished.
Note - As described in this guide, users should refrain from running individual test binaries from a shell command prompt. While running individual tests on an LDOM, most of them might fail or hang forever. Therefore, users are cautioned not to run any test binaries from the command line.