| SunVTS 5.1 Patch Set 11 Release Notes |     |
| SunVTS 5.1 Patch Set 11 Release Notes | |
|
SunVTS 5.1 Patch Set 11 Release Notes |
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.
1. Install the minimum End User Solaris Software Group.
2. 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. |
3. 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.
4. 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:
1. 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.
2. 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.
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.
You must install Patch ID 119914-07 (available at sunsolve.sun.com) before performing emlxtest. emlxtest is not displayed without this patch installed.
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.
You must install Patch ID 119914-07 (available at sunsolve.sun.com) before performing emlxtest. emlxtest is not displayed without this patch installed.
When too many instances of SunVTS functional tests are run in parallel on UltraSPARC T1 CMT CPU-based (sun4v) entry-level servers with low memory configuration, SunVTS tests might fail due to lack of system resources. For example, you could see an error message similar to the following:
Workaround: Decrease the number of SunVTS test instances or perform SunVTS functional tests separately. In addition, you can increase the delay value for CPU tests or increase the test memory reserve space.
The usbtest keyboard test might indicate a successful keyboard probe when a keyboard is not present.
Performing netlbtest on all ipge ports simultaneously in systems with Sun PCI-Express Dual Gigabit MMF/UTP adapters could fail. Performing netlbtest on one port per adapter, avoids this failure.
Workaround: Perform netlbtest on one port per Sun PCI-Express Dual Gigabit MMF/UTP adapter.
The netlbtest external loopback test could incorrectly report that the test passed when no loopback packets were transmitted or received by the ipge driver.
On dual-port host bus adapters (HBAs), testing both ports simultaneously could cause intermittent test failures.
Workaround: Test only one port of dual-port HBAs at a time.
audiotest on Sun Ultra 45 workstations currently supports the line-in/line-out external loopback test only.
Creating option files on Enterprise and Sun Fire 15K servers (UltraSPARC III) with the SunVTS GUI could cause a core dump.
Workaround: Use the TTY user interface to create option files.
SunVTS memory tests might log a warning message similar to the following in rare cases when the ECC Error Monitor (errmon) option is enabled.
Workaround: Disable the errmon option. The errmon option is disabled by default.
Installing SunVTS x86 packages on a SPARC server to serve x86 clients with SunVTS images is not supported. Installing SunVTS SPARC packages on an x86/x64 server to serve SPARC clients is supported.
In rare cases, repeated reuse of DVD+RW optical media on Sun Ultra 45 workstations could cause failures when performing high stress DVD+RW SunVTS tests.
Workaround: Replace the DVD+RW media upon failure, or use other types of media such as CD-RW.
On systems with a large number of devices, applying the Comprehensive option of the Auto Config feature causes the vtsui to lose connection to the SunVTS kernel (vtsk).
Workaround: Do not apply this option on systems with a large number of devices.
For qlctest to perform properly, you must have Version 4.4.5 or later of the San Foundation Kit (SFK) installed which allows HBAAPI support. To install the latest SFK, go to http://sunsolve.sun.com and download and install the software (SAN_4.4.5_install_it.tar.gz).
You must reboot the system for driver changes to take effect.
Older 1 GB Fiber Channel Host Bus Adapters (FC HBAs) typically do not use the latest SFK. If you wish to test HBAs without the latest SFK installed, use the previous version of SunVTS (5.1 PS9). 2 GB FC HBAs are not displayed in qlctest without the latest SFK installed.
Workaround: Install the latest SFK.
When performing a certain sequence of tasks of mixed test modes, failures causing error messages similar to the following could occur:
fputest does not appear on sun4m machines due to conflicting shared probe libraries.
Do not perform env4test on 32-bit machines. Doing so causes env4test to fail.
Workaround: Use a 64-bit Solaris Operating System to perform env4test.
atmtest might improperly fail with the maximum option values selected.
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.
If processor sets are defined, you must first delete the processor sets before running SunVTS.
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.
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.
| SunVTS 5.1 Patch Set 11 Release Notes | 819-4848-11 | |
Copyright © 2006, Sun Microsystems, Inc. All Rights Reserved.