test

Solaris 7 Release Notes Supplement for Sun Hardware

SunVTS 3.0 Issues

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

SunVTS Tests Not Available in 64-Bit Mode

The following SunVTS tests are not available in the 64-bit mode:

cg14test, isdntest, pstest, rtvctest, sxtest, and tcxtest

SunVTS Online Diagnostics through SyMON

The SunVTS online diagnostics feature (SUNWodu) is no longer accessible through the SyMON interface.

Disk and Floppy Drives Test (disktest) Update

File System Mounting

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 Veritas 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.

Caution - Caution -

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

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

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.

socaltest FATAL: Failed ioctl FCIO_DIAG_XRAM (4065420)

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.

HSI Board Test (sunlink) Update

In SunVTS 3.0 the sunlink test runs on HSI SBus and PCI type cards, however the SunVTS 3.0 Test Reference Manual only refers to the HSI SBus test capabilities.

A valid sunlink command line example is shown below: 

# /opt/SUNWvts/bin/sunlink -o dev=hih0,P=0+1+2+3

This command line tests the internal loopback for ports 0, 1, 2, and 3. The internal loopback should not be run in the port to port loopback setting.

ISDN Test (isdntest) Documentation

This test is part of the SunVTS 3.0, however it is not included in the SunVTS 3.0 Test Reference Manual. For isdntest test descriptions, options, command line syntax and error messages read the isdntest Postscript file (isdntest.ps) that is located in /opt/SUNWvts when the SUNWvts package is installed.

Serial Asynchronous Interface Test (saiptest)fails in external loopback mode (4171288)

The saiptest fails when the test is in 25-pin external loopback mode. Internal loopback mode runs as it should.

Workaround: Do not select 25-pin external loopback mode.

Sun GigabitEthernet Test (gemtest) Update

The following information updates the gemtest information in the SunVTS 3.0 Test Reference Manual.

Since gemtest requires a loopback connector, it can only be selected when the Intervention mode is enabled.

When gemtest is run in TTY mode, the console display becomes garbled due to the messages printed by the ge driver on the console. These messages indicate that the device has auto-negotiated and that the link is up. To refresh the display type Control-L.

Even though the gemtest does not depend on the network interface configuration status of the Sun GigabitEthernet adapter, it is recommended that the interface be brought down with the following command to avoid getting various messages such as errors pertaining to duplicate hardware addresses: 

# ifconfig gen down

The gemtest loopback cable may be made by splitting a standard fiber optic cable (see note below) into its two constituent cables. The two ends of the cable should be connected to the TX and RX ports of the adapter (the order doesn't matter), thus forming a loop.

Note -

This cable is based on the same specifications as those used for the Sun GigabitEthernet adapters (multimode, duplex, 62.5/125 micron, sc connector, 850nm).