| SunVTS 5.1 Patch Set 7 Release Notes |     |
| SunVTS 5.1 Patch Set 7 Release Notes | |
|
SunVTS 5.1 Patch Set 7 Release Notes |
The following issues apply to the SunVTS
5.1 PS7 product.
The SunVTS 5.1 PS7 software is compatible with the Solaris 8 2/02, Solaris 8 HW 12/02, Solaris 8 HW 5/03, Solaris 8 HW 7/03, Solaris 8 2/04, Solaris 9, Solaris 9 9/02, Solaris 9 12/02, Solaris 9 4/03, Solaris 9 8/03, Solaris 9 12/03, Solaris 9 4/04, and Solaris 9 9/04 operating systems. The following new features are added to the SunVTS 5.1 PS7 release.
In a future release of SunVTS, some of the existing SunVTS diagnostics might be consolidated into a single test binary. The existing test binaries for such consolidated tests will be removed and a new consolidated binary will be delivered. The likely candidates for consolidation include the following:Optical media tests: cdtest, dvdtest, cddvdrwtest
USB port tests: usbaudiotest, usbkbtest, usbppptest
Serial port tests: sptest, sutest
Parallel port tests: bpptest, ecpptest
The following tests will be discontinued in the next major release of SunVTS:
Advanced Frame Buffer Test (afbtest)
Alarm Card Test for Netra CT Systems (alarm2test)
Alarm Card Test (alarmtest)
Color Graphics Frame Buffer Test (cg14test)
Frame Buffer, GX, GXplus, and TurboGX Options Test (cg6test)
Sun StorEdge A5x00 Test (enatest)
Sun StorEdge 1000 Enclosure Test (enctest)
Environmental Test (env4test)
Frame Buffer Test (fbtest)
Fast Frame Buffer Test (ffbtest)
Graphics Frame Buffer Test (gfbtest)
PGX32 Frame Buffer Test (gfxtest)
Sun Enterprise Cluster 2.0 Network Hardware Test (scitest)
Environmental Sensing Card Test (sentest)
Soc+ Host Adapter Card Test (socaltest)
Sun Fire Link Interconnect Test (wrsmtest)
Sun XVR-4000 Graphics Accelerator Test (zulutest)
|
Note - The SunPCi |
Refer to the SunVTS 5.1 Patch Set 7 Documentation Supplement for details about the new features and tests offered in this release.
The online help documentation available with the SunVTS 5.1 software includes a chapter describing the RAM test (ramtest). This test is supported only in SunVTS 5.1 Patch Set 4 (PS4) onward.
This section lists corrections to errors in the Supported Test Modes tables of the following test chapters in the SunVTS 5.1 Test Reference Manual:
Compact Disk Test (cdtest)
CPU Test (cputest)
Disk and Floppy Drives Test (disktest)
DVD Test (dvdtest)
ECP 1284 Parallel Port Printer Test (ecpptest)
Sun StorEdge A5x00 Test (enatest)
Functional and Online test modes are supported in SunVTS 5.1.
Sun StorEdge 1000 Enclosure Test (enctest)
Environmental Test (env2test)
Online and Exclusive test modes are not supported in SunVTS 5.1.
Environmental Test (env4test)
Floating Point Unit Test (fputest)
Online and Exclusive test modes are supported in SunVTS 5.1.
Cache Consistency Test (mpconstest)
Multiprocessor Test (mptest)
Qlogic 2202 Board Test (qlctest)
Only Exclusive and Connection test modes are supported in SunVTS 5.1.
Serial Ports Test (sptest)
System Service Processor Test (ssptest)
SunHSI Board Test (sunlink)
System Test (systest)
Tape Drive Test (tapetest)
S24 Frame Buffer Test (tcxtest)
In Appendix A, SunVTS Window and Dialog Box Reference, Table A-11 indicates the incorrect default value of 0 (zero) for the Max Errors field of the example systest Test Parameter Options dialog box in Figure A-11. The correct default value of the Max Errors field of the systest Test Parameter Options dialog box is 1 (one) as indicated in Figure A-11.
Also in Appendix A, Table A-13 indicates the incorrect default value of 0 (zero) for the Max System Errors field of the example systest Threshold Options dialog box in Figure A-13. The correct default value of the Max System Errors field of the systest Threshold Options dialog box is 1 (one) as indicated in Figure A-13.
You might encounter an installation problem when you attempt to install SunVTS with an installation program other than the pkgadd command as described in the following subsections.
If SunVTS 5.1 software is installed in the default /opt directory, you cannot install a subsequent SunVTS 5.1 Patch Set release in a different directory on the same system. When this duplicate installation is attempted with pkgadd, the following error message occurs:
The reason for this error is that the base package revision is the same for both SunVTS 5.1 and any subsequent SunVTS 5.1 Patch Set release. When a SunVTS 5.1 Patch Set release is installed in the default /opt directory which already has SunVTS 5.1 software installed, the installation completes successfully with the following warning message:
This appears to be an attempt to install the same architecture and version of a package which is already installed. This installation will attempt to overwrite this package. |
From SunVTS 5.1, the SunVTS software depends on XML packages that are not included with the Solaris 8 2/02 distribution. For Solaris 9, all of the prerequisite packages are installed with the End User Solaris Software Group as a minimum.
You may install SunVTS 5.1 on Solaris 8 2/02, Solaris 8 HW 12/02, Solaris 8 HW
5/03, Solaris 8 HW 7/03, or Solaris 8 2/04. If you choose to install SunVTS 5.1 or later on any of these releases, you must separately install the required XML packages (SUNWlxml[32-bit] and SUNWlxmlx[64-bit]) from either the Solaris 8 HW 12/02, Solaris 8 HW 5/03, Solaris 8 HW 7/03, or Solaris 8 2/04 Software Supplement CD-ROM.
Install the minimum End User Solaris Software Group.
Install the XML packages SUNWlxml(32 bit) and SUNWlxmlx(64 bit) from either the Solaris 8 HW 12/02, Solaris 8 HW 5/03, Solaris 8 HW 7/03, or Solaris 8 2/04 Software Supplement CD-ROM.
|
Note - These XML packages are not available in the Solaris 8 2/02 distribution. |
Install SUNWzlib(32 bit) and SUNWzlibx(64 bit) packages from the Entire Solaris Software Group from either the Solaris 8 2/02, Solaris 8 HW 12/02, Solaris 8 HW
5/03, Solaris 8 HW 7/03, or Solaris 8 2/04 Software CD-ROM.
Install the optional SUNWcpc(x)/SUNWcpcu(x) packages only if you want to enable displaying certain performance counters for certain CPU and memory tests. Otherwise, these packages need not be installed.
The SUNWcpc(x)/SUNWcpcu(x) packages are included in the Entire Solaris Software Group for Solaris 8 2/02, Solaris 8 HW 12/02, Solaris 8 HW 5/03, Solaris 8 HW 7/03, and Solaris 8 2/04. These packages are not included in the End User Solaris Software Group for Solaris 8 2/02, Solaris 8 HW 12/02, Solaris 8 HW 5/03, Solaris 8 HW 7/03, nor Solaris 8 2/04.
To install SunVTS for Solaris 9 and later releases:
Install the End User Solaris Software Group (or any software group).
The XML packages (SUNWlxml[32-bit] and SUNWlxmlx[64-bit]) and the SUNWzlib packages (SUNWzlib[32 bit] and SUNWzlibx[64 bit]) are part of the End User Solaris Software Group (and Entire Solaris Software Groups) for Solaris 9 releases.
Install the optional SUNWcpc(x)/SUNWcpcu(x) packages only if you want to enable displaying certain performance counters for certain CPU and memory tests. Otherwise, these packages need not be installed.
The SUNWcpc(x)/SUNWcpcu(x) packages are part of the Entire Solaris Software Group and not the End User Solaris Software Group.
Web Start 2.0 may not install SunVTS on systems that do not have the Solaris 64-bit environment installed. Web Start 2.0 removes the SunVTS 32-bit packages when the SunVTS 64-bit packages cause the installation to suspend.
Workaround: Use the pkgadd command to install the 32-bit SunVTS packages as described in the SunVTS 5.1 User's Guide.
When you install SunVTS using Web Start 2.0, you are not prompted to enable the Sun Enterprise Authentication Mechanism (SEAM) Kerberos v5, SunVTS security feature. The installation defaults in a way that installs SunVTS without this high level of security. If you do not want the high-level security, there is no problem.
Workaround: To enable the high-level SEAM security, use the pkgadd command to install SunVTS packages as described in the SunVTS 5.1 User's Guide.
When you attempt to install SunVTS using Web Start 2.0, you are unable to change the directory where SunVTS is installed. SunVTS will be installed in /opt.
Workaround: Use the pkgadd -a none command to install SunVTS in the directory of your choice as described in the SunVTS 5.1 User's Guide.
Use the same tool or utility for installation and removal of the SunVTS software. If you use pkgadd for installation, use pkgrm to uninstall; if you use Web Start for installation, use the Product Registry to uninstall.
The test registration does not work properly for DVD-RW drives with DVD-ROM media. SunVTS registers cdtest for DVD-RW drives when vold is running and it registers dvdtest when vold is stopped.Workaround: Perform this test only if the dvdtest gets registered for the DVD-ROM media.
fputest does not appear on sun4m machines due to conflicting shared probe libraries.Workaround: None.
When using nipmitest in the SunVTS GUI, clicking Apply, Apply to Group, or Apply to All from the Test Parameter Options dialog box could bring up the following error message: "ERROR: Failed to apply some options. Check error logs for details."
If this occurs, error messages similar to the following are displayed in the SunVTS error log (sunvts.err):
If a CPU is taken offline for dynamic reconfiguration after SunVTS is invoked, the SunVTS kernel (vtsk) receives out of date information about the online CPUs. This incorrect information causes the GUI to show "RED" and no message is printed. The run on error option (-r) does not work if this occurs.Workaround: None.
In SunVTS 5.1 Patch Set 7 onward, SunVTS requires the shared object library libCstd.so.1 to perform successfully. If this shared object library is not installed, an error message similar to the following is displayed when you attempt to start SunVTS:
/opt/SUNWvts/bin 25 % ./sunvtsld.so.1: ./sunvts: fatal: libCstd.so.1: open failed: No such file or directoryKilled |
libCstd.so.1 must be located in the /usr/lib/ directory. If the Solaris 8 or 9 installation does not have this library installed, for Solaris 8 you must install Patches 108434 (for 32-bit) or 108435 (for 64-bit); for Solaris 9 you must install Patches 111711 (for 32-bit) and 111712 (for 64-bit). The paths to these patches are as follows:
http://sunsolve.sun.com/pub-cgi/findPatch.pl?patchId=108434 http://sunsolve.sun.com/pub-cgi/findPatch.pl?patchId=108435 |
http://sunsolve.sun.com/pub-cgi/findPatch.pl?patchId=111711&rev=11http://sunsolve.sun.com/pub-cgi/findPatch.pl?patchId=111712&rev=11 |
When SunVTS is stopped, netlbtest might not exit properly when it is running in external loopback mode on a Gigabit Ethernet network interface.Workaround: Deselect netlbtest from SunVTS GUI and kill the netlbtest process manually.
If processor sets are defined, you must first delete the processor sets before running SunVTS.
On platforms with low memory, sometimes the dtlbtest fails with an error: "shmat: Invalid argument." This error is due to resource constraints within the tested system and it does not indicates faulty hardware.
The Trace Test of a test module in Connection test mode could cause the SunVTS user interface (vtsui) and kernel (vtsk) to core dump. This problem appears when empty newlines are processed in the trace output. A NULL pointer is passed for broadcast messages in such situations.
When performing sptest, the test might not pass or provide error messages for a long time.
fwcamtest could hang with the following error message: "Termination of tests could be hung. Deselect tests to bring sunvts to an idle status." If dcamtest is deselected, all records regarding the test are removed. Display of the video does not go away after deselecting and quitting SunVTS. Black video output is seen from the video window.
In rare occasions, env5test might hang when SunVTS is stopping. This causes SunVTS to not exit properly.Workaround: There are two workarounds for this problem: 1.) From the SunVTS GUI, deselect the test by unchecking the box next to the test entry. 2.) Choose a fixed number of passes for env5test to run.
The SunVTS user interfaces (vtsui and vtstty) could fail to come up and hang at probe on Netra T1 servers.
On Sun Fire 15K systems, adding new boards with DR might cause some of the processor and memory related tests to perform ineffectively. Specifically, cmttest might fail to recognize the CMT processors on the new board. Similar failures might also occur in l2sramtest, l1dcachetest, dtlbtest, ramtest, bustest, mptest, and fputest.
Workaround: Reboot the system after adding a new board with DR.
pfbtest might fail when performed in the GNOME desktop environment on a Sun XVR-100 graphics accelerator if the test is performed in the default console window.This failure does not occur in the Solaris 8 2/02 and Solaris 8 HW 3/03 operating environments. If this failure occurs, you see an error message similar to the following:
An ecpp/parallel port driver issue might cause ecpptest to fail. The failure rate is three out of 130 machines; the time to fail is about 10 hours.
Sun Blade 100 and 150 systems with SunVTS can produce errors when the serial port controller (southbridge) is also handling other traffic as data access from and to the IDE hard disk. With SunVTS simultaneously running sutest and disktest on Sun Blade 100 and 150 systems, you might see sutest report failures.
Workaround: Do not perform sutest and disktest simultaneously.
The command pkginfo -c sunvts does not produce any output in SunVTS 5.1. This situation correctly implements the -c option of the pkginfo command.
Workaround: Use the following command to receive SunVTS 5.1 package information
You can also use either of the following commands to receive additional SunVTS 5.1 package information:
Performing sutest on a port that is being used as console causes sutest to fail.
Workaround: Do not perform sutest on a port that is being used as a console.
Performing m64test for Sun PGX64 in a default console winfow, might cause intermittent failures in a GNOME environment.
Performing afbtest or m64test tests in a GNOME environment might cause intermittent failures.
| SunVTS 5.1 Patch Set 7 Release Notes | 819-0687-10 | |
Copyright © 2004, Sun Microsystems, Inc. All Rights Reserved.