SunVTS 3.3 Issues

The following issues apply to the SunVTS(TM) 3.3 product.

New Features for This Release

A new test called gfxtest was added to support testing of the PGX frame buffer.

SunVTS OPEN LOOK User Interface Support

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.

Running SunVTS Online Diagnostics through Sun Enterprise SyMON

The SunVTS 3.3 online diagnostics feature (SUNWodu) is not accessible through the SyMON interface.

Instead, you can start SunVTS so it will run safely in an online environment by using the vtsui.online command.

Example:

# /opt/SUNWvts/bin/vtsui.online -h hostname

For more information about running SunVTS in an online or offline environment, refer to the SunVTS 3.3 User's Guide.

StorEdge-A5XXX Device Group Changes

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-A5XXX_enclosure_name group.

Disk Test (disktest) Mounting Issues

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. For more details, refer to the disktest chapter in the SunVTS 3.3 Test Reference Manual.

Disk Test (disktest) Option File Note

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). 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 /disktest_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.

Physical Configuration Mapping Support

The Physical Mapping function is only supported on the systems where the configd program is supported. The configd program only supports Ultra Enterprise machines. The configd package must be installed at the default installation base directory.

To display physical mapping, click the physical mapping button in the SunVTS interface. This will result in a re-mapping of the entire set of testable devices and test settings. Changing the logical and physical view during a test session is not recommended because the previous system and test status will be reset.

The SunVTS User Interface Disappears (4122829)

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

Some Devices Not Displayed Under Physical Mapping (4228489)

Certain devices that appear under logical mapping are not displayed under physical mapping, therefore, these devices are not selectable for testing.

Workaround: Use logical mapping for testing such devices.

The enatest and socaltest Cannot Run at the Same Time (4065417)

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.

The socaltest FATAL: Failed ioctl FCIO_DIAG_XRAM (4065420)

When the SunVTS socaltest is run concurrently with disktest, the socaltest may fail.

Workaround: Do not select socaltest when disktest is selected and vice-versa.

The socaltest Can Fail Under Heavy System Load (4213518)

Running socaltest with heavy system load might cause resource limitations that cause this test to fail.

Workaround: Do not run socaltest with a large number of instances and concurrency.