|C H A P T E R 20|
System Test (systest)
The systest checks the overall functionality of a Sun system by exercising the CPU, I/O, and memory channels.
The test ensures the concurrency of the different channels by the use of Solaris threads. The test aims at stimulating failures that might be caused due to the interaction of the various different hardware modules in the system. It is very stressful on the CPU, and stresses the parallel computational capability of a multiprocessor system.
|Caution - This is an exclusive mode test. This test can not be run in parallel with any other tests or applications.|
To reach the following dialog box, right-click on the test name in the System Map and select Test Parameter Options. If you do not see this test in the System Map, you might need to expand the collapsed groups, or your system might not include the device appropriate to this test. Refer to the SunVTS 6.4 User's Guide for more details.
FIGURE 20-1 systestTest Parameter Options Dialog Box
|Caution - Use discretion when defining the syspassparameter. The time taken by the test depends on many factors (number of processors, type/speed, amount of memory/swap, and so on). Always verify the time taken for one pass before deciding on higher pass values. If the syspassvalue is set to a high value, it increases the probability of detecting residual errors.|
|Note - Users are advised to not use the Processor Affinity option for this test. Doing so reduces the effectiveness of the test.|
Defines the maximum execution time of the CPU test in minutes. Acceptable range: 10 to 120 minutes. Values less than 10 minutes (except 0) will be treated as 10 minutes. If the value is 0, the test runs until completion.
Use the default values for an initial evaluation of the system.
/opt/SUNWvts/bin/systest standard-arguments -o -io=enable|disable
See TABLE 20-1 for full details.
The following examples assume you execute systest from the command-line with verbose enabled.
Example 1 invokes the following:
Example 2 invokes the following:
|Caution - Do not perform the following systestexamples (3 and 4) on production servers, because systestmay online or offline CPUs.|
Example 3 invokes the following:
Example 4 invokes the following: