Hardware Certification Test Suite 2.4.1 User's Guide

Contents Previous: Reviewing and Copying Test Results

Appendix A

# Automated Tests

This appendix lists the tests that HCTS automatically runs when you certify a system, motherboard, or controller. See Certifying Systems and Certifying Controllers.

This appendix first briefly describes all tests in the HCTS. This appendix then lists which tests are run for each type of certification.

- System Level 1 Tests
- System Level 2 Tests
- Motherboard Level 1 Tests
- Motherboard Level 2 Tests
- Network Level 1 Tests
- Network Level 2 Tests
- Storage Level 1 Tests
- Storage Level 2 Tests
- Serial I/O Level 1 Tests
- Serial I/O Level 2 Tests

## Descriptions of All HCTS Tests

The following table gives a brief description of each HCTS test. The table also provides a link to a complete description of each test.

CON5repeat | Stresses disk controllers and their device drivers, and tests that the system functions correctly under heavy load. `CON5repeat` accomplishes this by running many concurrent instances of a basic test that copies and compares directories, and reports an error if any of the copies fails or does not compare as expected.
CON5_6 | Same as `CON5repeat` but functions as an NFS stress test by using an NFS mount as the target directory.
bonnie | Performs several tests on a file of known size. This performance test suite is a series of disk I/O stress tests. Tests are performed in three areas: sequential input, sequential output, and random seeks.
cdrom | Copies a directory tree from a CD to a directory on the hard disk, and then verifies that the original tree and the copy are identical. Insert a CD into the CD drive. If possible, the CD should contain a complex directory tree.
cl3se3 | Checks for data corruption by continually transmitting a data pattern between the system under test and the test manager system. See System Requirements for definitions of these two systems.
cl3se3_6 | Checks for data corruption by continually transmitting a data pattern between the system under test and the test manager system on the IPv6 network. See System Requirements for definitions of these two systems.
dd | Reads from a disk slice repeatedly using different block sizes. Both raw and block devices can be specified.
flowctl | Sets the terminal parameter with the requested baud rate and flow control using the standard `ioctl`(2) system call. Then transfers and receives data continuously between two serial I/O controllers. Finally, verifies that flow control happened and the transmission is correct.
flp | Tests the functionality of the diskette drive by repeatedly executing `fdformat`(1) on a diskette. Insert a writable diskette into the diskette drive.
fs_stress | Stresses Solaris file systems. This test is performed against a user-configurable range of file system types and devices. By default, this test is performed against all available file systems and all devices. All I/O is sequential, although an option to specify the use of random file and transfer sizes is available.
ftpstress | Checks for data corruption by continually copying files between remote machines using FTP.
ftpstress_6 | Checks for data corruption by continually copying files between remote machines using FTP on the IPv6 network.
hupctl | Tests modem or serial port or serial card functional property. Hangs up on last close.
largedisk | Checks whether the system will support a USB hard disk that has a large size.
lsalr | Generates a load on the network by transmitting an `ls`(1) of the remote machine to the local machine.
lsalr_6 | Generates a load on the network by transmitting an `ls`(1) of the remote machine to the local machine on the IPv6 network.
mcpu | Performs large matrix multiplication operations to stress CPUs in the system.
memory | Uses `vmemtest` to read and write virtual memory. Generates a heavy load on swap devices. For Level 1 certification, only physical memory is tested.
mpflip | Repeatedly turns processors on and off in a multiprocessor system.
scp | Checks for data corruption by continually copying files between remote machines by using `scp`(1).
scp_6 | Checks for data corruption by continually copying files between remote machines by using `scp`(1) on the IPv6 network.
rmdtest | Tests for data corruption during read and write operations on removable media, such as Zip disks.
sanity | Detects errors in the driver load and unload routines (such as memory leaks) by loading and unloading the driver and verifying (using `ping`(1M)) that the connection is brought up correctly each time.
ser_rdwt | Sets the terminal parameter with the requested baud rate. Then sets `VMIN` and `VTIME` using the standard `ioctl`(2) system call. Then this test performs read and write operations on the controllers being certified. Finally, checks whether the read and write operations were done correctly.
spray | Gathers statistics about network packet transmission on a busy network by continually transmitting packets between remote machines using UDP.
spray_6 | Gathers statistics about network packet transmission on a busy IPv6 network. This test continually transmits packets between remote machines using UDP6.
txrx | Sets the terminal parameter with the requested baud rate using POSIX interfaces. Then transfers and receives data continuously between two serial I/O controllers. Finally, verifies that the data transmission was correct.
video | Runs `x11perf`, an X11 server performance test program, and reports how fast the X server executed the tests.

## System Level 1 Tests

The HCTS runs the automated tests for System Level 1 certification in the following six groups.

For a brief description of each of these tests, see "Descriptions of All HCTS Tests."

See "Certifying a System" for instructions on how to use HCTS to certify your system.

Group 1: `video`
Group 2: `cdrom`
Group 3: `flp`
Group 4: CPU (`mcpu`) and memory (`memory`) tests run in parallel.
Group 5: storage (`dd` and `fs_stress`)
Group 6: network (`CON5repeat`, `ftpstress`, `lsalr`, `scp`, `CON5_6`, `ftpstress_6`, `lsalr_6`, and `scp_6`)

If you enable IPv6, the System Level 1 suite of tests runs for about 19.5 hours. Group 1 runs for about one hour. Groups 2 and 3 each run for about fifteen minutes. Group 4 runs for about 2 hours. The storage tests run for about 4 hours. The network tests run for about 12 hours. The IPv4 tests run for about 4 hours. The IPv6 tests run for about 8 hours. If you do not enable IPv6, the System Level 1 suite of tests runs for about 11.5 hours. The readme file for each test gives the default run time for that test.

The `rmdtest` test runs only if you select the Zip Drive check box on the System Certification Screen.

The `video` test runs first. If your system does not have video capability, explain the failure of the video test in the comments section of the certification submission form.

## System Level 2 Tests

The HCTS runs the automated tests for System Level 2 certification in the following six groups.

For a brief description of each of these tests, see "Descriptions of All HCTS Tests."

See "Certifying a System" for instructions on how to use HCTS to certify your system.

Group 1: `video`
Group 2: `cdrom`
Group 3: `flp`
Group 4: CPU (`mcpu`) and memory (`memory`) tests run in parallel.
Group 5: storage (`bonnie`, `dd`, and `fs_stress`)
Group 6: network (`sanity`, `CON5repeat`, `cl3se3`, `scp`, `ftpstress`, `lsalr`, `spray`, `cl3se3_6`, `scp_6`, `ftpstress_6`, `lsalr_6`, and `spray_6`)

If you enable IPv6, the System Level 2 suite of tests runs for about 47.5 hours, or for about two days. Group 1 runs for about two hours. Groups 2 and 3 each run for about fifteen minutes. Group 4 runs for about 4 hours. The storage tests run for about 21 hours. The network tests run for about 20 hours. The IPv4 tests run for about 14 hours. The IPv6 tests run for about 6 hours. If you do not enable IPv6, the System Level 2 suite of tests runs for about 41.5 hours. The readme file for each test gives the default run time for that test.

The `rmdtest` test runs only if you select the Zip Drive check box on the System Certification Screen.

The `video` test runs first. If your system does not have video capability, explain the failure of the video test in the comments section of the certification submission form.

## Motherboard Level 1 Tests

The HCTS runs the automated tests for Motherboard Level 1 certification in the following four groups.

For a brief description of each of these tests, see "Descriptions of All HCTS Tests."

See "Certifying a Motherboard" for instructions on how to use HCTS to certify your motherboard.

Group 1: `video`
Group 2: CPU (`mcpu`) and memory (`memory`) tests run in parallel.
Group 3: storage (`dd` and `fs_stress`)
Group 4: network (`CON5repeat`, `ftpstress`, `lsalr`, `scp`, `CON5_6`, `ftpstress_6`, `lsalr_6`, and `scp_6`)

If you enable IPv6, the Motherboard Level 1 suite of tests runs for about 19 hours. Group 1 runs for about one hour. Group 2 runs for about 2 hours. The storage tests run for about 4 hours. The network tests run for about 12 hours. The IPv4 tests run for about 4 hours. The IPv6 tests run for about 8 hours. If you do not enable IPv6, the Motherboard Level 1 suite of tests runs for about 11 hours. The readme file for each test gives the default run time for that test.

The `video` test runs first. All other tests run in parallel after the video test finishes.

If your system does not have video capability, explain the failure of the video test in the comments section of the certification submission form.

## Motherboard Level 2 Tests

The HCTS runs the automated tests for Motherboard Level 2 certification in the following four groups.

For a brief description of each of these tests, see "Descriptions of All HCTS Tests."

See "Certifying a Motherboard" for instructions on how to use HCTS to certify your motherboard.

Group 1: `video`
Group 2: CPU (`mcpu`) and memory (`memory`) tests run in parallel.
Group 3: storage (`bonnie`, `dd`, and `fs_stress`)
Group 4: network (`sanity`, `CON5repeat`, `cl3se3`, `scp`, `ftpstress`, `lsalr`, `spray`, `cl3se3_6`, `scp_6`, `ftpstress_6`, `lsalr_6`, and `spray_6`)

If you enable IPv6, the Motherboard Level 2 suite of tests runs for about 47 hours, or for about two days. Group 1 runs for about two hours. Group 2 runs for about 4 hours. The storage tests run for about 21 hours. The network tests run for about 20 hours. The IPv4 tests run for about 14 hours. The IPv6 tests run for about 6 hours. If you do not enable IPv6, the Motherboard Level 2 suite of tests runs for about 41 hours. The readme file for each test gives the default run time for that test.

The `mpflip` test runs in Group 2. The `mpflip` test runs only the additional processors that exist on test system.

The `video` test runs first. All other tests run in parallel after the video test finishes.

See "Certifying a Motherboard" for instructions on how to use HCTS to certify your motherboard.

If your system does not have video capability, explain the failure of the video test in the comments section of the certification submission form.

## Network Level 1 Tests

If you do not enable IPv6 certification, the Network Level 1 suite of tests runs for 4 hours. Each test listed below runs for one hour. The readme file for each test gives the default run time for that test.

For a brief description of each of these tests, see "Descriptions of All HCTS Tests."

See "Certifying Network Controllers" for instructions on how to use HCTS to certify your network controller.

- `CON5repeat`
- `ftpstress`
- `lsalr`
- `scp`

If you enable IPv6 certification, the Network Level 1 suite of tests runs for 12 hours. Four tests run on each of the following two IPv6 interfaces:

- IPv6 interface
- IPv6 over the IPv4 tunnel interface

Each test runs for one hour, for a total of eight hours, except for the Fast Ethernet and Gigabit Ethernet tests. Fast Ethernet and Gigabit Ethernet tests with IPv6 enabled run for 12 hours.

- `CON5_6`
- `ftpstress_6`
- `lsalr_6`
- `scp_6`

## Network Level 2 Tests

The HCTS runs the automated tests for Network Level 2 certification in the following four groups.

For a brief description of each of these tests, see "Descriptions of All HCTS Tests."

See "Certifying Network Controllers" for instructions on how to use HCTS to certify your network controller.

Group 1: `sanity`
Group 2: `CON5repeat`
Group 3: `cl3se3`, `scp`
Group 4: `ftpstress`, `lsalr`, `spray`

If you do not enable IPv6 certification, the Network Level 2 suite of tests runs for 14 hours. Group 1 runs for 2 hours, and Groups 2, 3, and 4 run for 4 hours each. The readme file for each test gives the default run time for that test.

If you enable IPv6 certification, the Network Level 1 suite of tests runs for 20 hours. Six additional groups of tests run on the IPv6 network. Three of these groups run on the IPv6 interface. The other three groups run on the IPv6 over IPv4 tunnel interface. Each of these six groups of tests runs for 1 hour, for a total of 6 hours.

If IPv6 certification is enabled, HCTS runs the following six groups of tests:

For a brief description of each of these tests, see "Descriptions of All HCTS Tests."

Group 5: `CON5repeat`
Group 6: `cl3se3_6`, `scp_6`
Group 7: `ftpstress_6`, `lsalr_6`, `spray_6`
Group 8: `CON5repeat`
Group 9: `cl3se3_6`, `scp_6`
Group 10: `ftpstress_6`, `lsalr_6`, `spray_6`

Groups 5, 6, and 7 are run on the IPv6 interface. Groups 8, 9, and 10 are run on the IPv6 over IPv4 tunnel interface.

## Storage Level 1 Tests

See "Certifying Storage Controllers" for instructions on how to use HCTS to certify your storage controller.

Different sets of tests are used to certify different technologies.

### Fibre Channel, RAID, SATA, and SCSI Level 1 Tests

The following tests run simultaneously for four hours. The readme file for each test gives the default run time for that test.

For a brief description of each of these tests, see "Descriptions of All HCTS Tests."

- `dd`
- `fs_stress`

### USB Level 1 Tests

The following tests run simultaneously for two hours. The readme file for each test gives the default run time for that test.

For a brief description of each of these tests, see "Descriptions of All HCTS Tests."

- `dd`
- `fs_stress`
- `largedisk`

## Storage Level 2 Tests

See "Certifying Storage Controllers" for instructions on how to use HCTS to certify your storage controller.

Different sets of tests are used to certify different technologies.

The HCTS runs the `bonnie` performance test for about three hours and then runs all the other stress tests simultaneously.

### Fibre Channel, RAID, and SATA Level 2 Tests

Fibre Channel, RAID, and SATA tests run for a total of 21 hours: 3 hours for `bonnie` and 18 hours for the other tests. The readme file for each test gives the default run time for that test.

For a brief description of each of these tests, see "Descriptions of All HCTS Tests."

- `bonnie`
- `dd`
- `fs_stress`
- `mpflip`

### SCSI Level 2 Tests

SCSI tests run for a total of 21 hours: 3 hours for `bonnie` and 18 hours for the other tests. The readme file for each test gives the default run time for that test.

For a brief description of each of these tests, see "Descriptions of All HCTS Tests."

- `bonnie`
- `dd`
- `fs_stress`
- `cdrom`
- `mpflip`

### USB Level 2 Tests

USB hard drive tests run for a total of 15 hours: 3 hours for `bonnie` and 12 hours for the other tests. The readme file for each test gives the default run time for that test.

For a brief description of each of these tests, see "Descriptions of All HCTS Tests."

- `bonnie`
- `dd`
- `fs_stress`
- `largedisk`
- `mpflip`

## Serial I/O Level 1 Tests

The HCTS runs the automated tests for Serial I/O Level 1 certification in the following four groups.

For a brief description of each of these tests, see "Descriptions of All HCTS Tests."

See "Certifying Serial I/O Controllers" for instructions on how to use HCTS to certify your serial I/O controller.

Group 1: `flowctl`
Group 2: `txrx`
Group 3: `ser_rdwt`
Group 4: `hupctl`

Groups 1, 2, and 3 each run for two hours, for a total of six hours. Group 4 runs for 10 minutes. The readme file for each test gives the default run time for that test.

## Serial I/O Level 2 Tests

The HCTS runs the automated tests for Serial I/O Level 2 certification in the following four groups.

For a brief description of each of these tests, see "Descriptions of All HCTS Tests."

See "Certifying Serial I/O Controllers" for instructions on how to use HCTS to certify your serial I/O controller.

Group 1: `flowctl`, `mpflip`, `scp`
Group 2: `cl3se3`, `mpflip`, `txrx`
Group 3: `ser_rdwt`, `mpflip`
Group 4: `hupctl`

Groups 1, 2, and 3 each run for eight hours, for a total of 24 hours. Group 4 runs for 10 minutes. The readme file for each test gives the default run time for that test.

Next: Usage Notes

Copyright 2005 Sun Microsystems