The following issues apply to the SunVTS(TM) 3.1 product.
The following SunVTS tests are not available in the 64-bit mode:
cg14test, isdntest, pstest, sxtest, and tcxtest
The SunVTS 3.1 online diagnostics feature (SUNWodu) is no longer accessible through the SyMON interface.
To start SunVTS to safely run in an online environment, use the vtsui.online command.
# /opt/SUNWvts/bin/vtsui.online -h hostname
For more information about running SunVTS in an online or offline environment, refer to the SunVTS 3.1 User's Guide.
In some cases, the SunVTS user interface disappears during a SunVTS test session. The SunVTS kernel is still active and the test session may continue to run.
Workaround: Restart the SunVTS user interface.
Example (starting the SunVTS CDE user interface):
# /opt/SUNWvts/bin/vtsui
The rtvctest verifies the functionality of the SunVideo SBus card.
This test is not supported on SunVTS version 3.0 and version 3.1, even though the test is listed in the SunVTS 3.0 Test Reference manual.
To run rtvctest, run SunVTS version 2.1.3 with the Solaris 2.6 5/98 operating environment.
The SunVTS OPEN LOOK user interface may not support the latest SunVTS features. For full feature support, use the SunVTS CDE or TTY interface. The SunVTS OPEN LOOK user interface will be sustained, but not enhanced, as long as OPEN LOOK is supported in the Solaris environment.
When using the physical map view, you can only see one level in the hierarchy (such as one controller on a system board). Therefore, some devices that are several levels down are not available to trace. In this case, use the logical view to select tracing for these devices.
When the SunVTS enatest is run concurrently with the socaltest, the enatest may fail.
Workaround: Do not select socaltest when enatest is selected and vice-versa.
When the SunVTS socaltest is run concurrently with enatest and disktest, the socaltest may fail.
Workaround: Do not select enatest when socaltest is selected and vice-versa.
As of SunVTS 3.0, SunVTS disktest by default does not mount any mountable partitions. To have SunVTS mount all partitions which contain a file system, set the environment variable BYPASS_FS_PROBE to 0 (zero), then start SunVTS as shown below:
# BYPASS_FS_PROBE=0; export BYPASS_FS_PROBE # ./sunvts
To return to the SunVTS default behavior so no file systems are mounted, either set the BYPASS_FS_PROBE to a non-zero value, or unset it.
Even if BYPASS_FS_PROBE is set to 0 (zero), the SunVTS disk probe checks for the existence of Sun Enterprise Volume Manager and Solstice Disksuite on the system, and does not mount any partitions if their presence is detected.
If SunVTS is invoked from the Solstice SyMON graphical user interface, SunVTS will not mount any partitions in this case either.
If a power failure occurs while the disktest is running, disk data may be destroyed.
Running the Media subtest on a disk partition in the WriteRead mode may cause data corruption if the same partition is being used by other programs. Only select this mode when the system is offline (not used by any other users or 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 no longer set to 0 (zero). Testing may fail with the following error:
SUNWvts.disktest.8088 07/24/98 15:47:22 disktest c0t0d0 FATAL: "Couldn't get file system information on /distest_c0t0d0s0, statvfs() system call failure error: No such file or directory.
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).
Workaround: Create two separate option files for the two different states of the BYPASS_FS_PROBE environment variable.