This document provides detailed descriptions of the manual system certification tests. After you successfully complete the manual tests described in this document, use the HCTS to run the automated tests.
These tests require two systems.
In this testing, the system under test serves data to the test manager system. In this way, the test manager system is a client of the system under test.
Make sure both systems meet the general hardware and software requirements for all certifications stated in the Hardware Certification Test Suite Installation Guide.
This section describes additional software and setup required to execute the systems hardware certification tests.
All test machines must be on their own private network. The test machines do not need to be connected back-to-back.
Connect the fibre or copper cable back-to-back. That is, connect a cable directly from the back of the test manager system to the back of the system under test.
Both system hostnames must be resolved on both systems. On the system under test, add the test manager system hostname to the /etc/hosts file. On the test manager system, add the system under test hostname to the /etc/hosts file.
Configure your Xwindows correctly on the system under test before you begin any test that includes a video test. System certification and motherboard certification include video testing.
Start Xwindows on the system under test and log on as user root before you begin any test that includes a video test.
If the system under test does not have video capability, explain the failure of the video test in the comments section of the certification submission form.
Run all tests as user root unless otherwise indicated in the HCTS test ReadMe file.
This test verifies that the Solaris OS can be installed on the system under test.
Required Hardware
Test Strategy
This test ensures that the Solaris OS will install on the system under test.
Test Procedure
Perform both CD and network installs on the system under test.
For the network install, follow these instructions for Pre-Boot Execution (PXE) installation.
Note: To specify slice layout during Solaris installation do the following:
Ensure that the Solaris partition on the system under test is sliced correctly as described in "Required Software Configuration".
Reboot the system, and ensure that no error messages appear.
Expected Results
The Solaris OS installs and works properly.
Perform this optional test if system under test includes a tape drive.
Required Hardware
Required Software
Test Strategy
This test verifies that a tape drive supported by a Solaris driver is usable.
The tar command is used to write a file to a tape, read the same file from the tape, and store it on a disk drive. Then, the sum command is used to verify that there are no differences between the two files.
This test is performed on a machine running the appropriate Solaris release. The tape drive is connected to an HBA and is one of its SCSI targets.
Test Procedure
Verify that the Solaris system is running.
Insert a tape into the tape drive, and reboot the system.
At the shell prompt, type the following:
# ls -l /dev/rmt
Output similar to the following is displayed, where n is the tape drive instance:
lrwxrwxrwx 1 root root 55 Oct 28 12:32 /dev/rmt/n -> ../../devices/pci@0,0/pci1011,26@a/pci1069,20@8/st@4,0:
If the nodes are not displayed, type the following:
# tapes -r /dev
#
ls /dev/rmt
View the output and select the tape drive device node.
If only one tape drive is installed on the system, use /dev/rmt/0 for the node.
To verify that I/O operations can be performed on the tape, type the following commands, where ksh can be substituted by the name of any file.
# cd /tmp
#
tar cvf /dev/rmt/0 -C /bin ksh
#
tar xvf /dev/rmt/0
#
sum /bin/ksh ksh
Expected Results
Copyright 2005 Sun Microsystems, Inc. All rights reserved.