For system, network, and serial I/O testing, you must
use two test
machines:
Machine 1: System Under Test (SUT)
— This is the system you want to certify, or the system that has the
device you want to certify.
Machine 2: Test Manager system (TM)
— This system is used by
the SUT to test network and serial I/O devices. The TM should be a
system that is already listed on the HCL as Certified.
This chapter explains how to set up and connect your
Test Manager
system and System Under Test and how to install the Solaris OS and
HCTS on those two systems.
Hardware Requirements
To use HCTS, your systems must meet the following
hardware requirements:
Both Systems
Network — Both systems should be
non-production systems on an
isolated network segment. Network certification produces a flood of
traffic on other systems on the network.
Free space — Each system must
have at least the following amounts of free space:
(number_of_network_ports)x(1.5 GB) in /export/home
Use the following command to verify this requirement:
% df -h
Serial cable — Serial I/O testing
only. A serial cable is
required to connect the serial port of the Test Manager system and the
System Under Test.
System Under Test
Floating point — The System Under
Test must have hardware floating point support.
Free space — In addition to the
free space requirement stated
above for both systems, the System Under Test must have the following
free space:
Swap space is at least 1/8 of physical memory
size (Minimum 512MB).
At least 4 GB of free space in any single
Solaris slice or a non-reserved hard disk larger than 16 GB.
Use the following command to check free space:
$ df -h
A non-reserved disk does not contains any slice
mounted to/, /usr, /var,
or /export/home*.
Network — The System Under Test
must have at least one port.
Each port on the System Under Test must be connected to the Test
Manager system.
Caution - For
system certification, if the System Under Test contains more than one
disk
drive, any disk that does not have any slice mounted to/, /usr,
/var, or /export/home* is formatted. All
data on such a disk is
lost. During the test initialization process, any disk that is
scheduled to be
formatted is listed. The initialization process pauses for 60 seconds
and prompts you
to stop the certification if you do not want the disk to be
formatted.
Test Manager System
The Test Manager System should be already listed on
the Hardware Compatibility List (HCL) as Certified.
Network — The Test Manager System
must have one functional
network port for each network port on the System Under Test. The Test
Manager system must have at least as many network ports as the System
Under Test has. Each port on the System Under Test must be connected to
the Test Manager system. The Test Manager system can have no more than
five more ports than the System Under Test has.
Software Requirements
Your systems must be set up as described in this section.
The test environment must consist of only one Test
Manager system
and only one System Under Test in an isolated network segment.
Additional systems must be tested separately, at a later time.
If your Test Manager system or your System Under
Test matches the following description, then you must disable NIS:
The Solaris OS is installed on the machine and
you will not reinstall the Solaris OS before running HCTS.
NIS is set up and enabled on the machine.
You will disconnect the machine from another
network and reconnect to the isolated network segment of the test
environment.
Under these conditions, if you do not disable NIS,
the system will
behave abnormally due to inconsistent network settings. Use the
following commands to disable NIS:
/usr/lib/netsvc/yp/ypstop
The above command disables NIS until the next reboot
Either of the following commands permanently
disables NIS:
Option A:
svcadm disable svc:/network/nis/client:default
Option B:
sys-unconfig
Note - The
sys-unconfig(1M)
command restores the configuration of the system to an
“as-manufactured” state, ready to be re-configured again. Be sure to
read the sys-unconfig(1M)
man page to see
which settings will be changed. Then be sure to document what your
current settings are so that you can restore them.
Run the sys-unconfig
command.
Reboot the system.
Answer the questions on the screen. When you
are prompted to select
a name service, select “None”. When all questions are answered, the
system restarts, and NIS is disabled.
Make sure Xwindows
is running on the System Under Test.
Make sure the Test Manager system is correctly
connected to the System Under Test.
All ports in the System Under Test must be
correctly connected to
the Test Manager system. No port can be left unconnected on the System
Under Test. For Network component certification, all ports of the
network component must be connected to the Test Manager System. For
Serial I/O certification, at least 1 port must be connected to the Test
Manager System.
Back-to-back connection of the Test Manager
system and the System
Under Test - or private switch - is strongly recommended. If you have
routers, intelligent switches, or gateways between the Test Manager
system and the System Under Test, you must configure them to allow the
IP addresses described below. If you are implementing VLAN, you must
configure it to allow the IP addresses described below.
HCTS assigns a particular range of IP addresses
to a Test Manager
system and a different range of IP addresses to a System Under Test.
Network devices on the Test Manager system must allow their IP
addresses to be temporarily changed to 10.10.n.11/24, where n is 10,
11, 12, and so forth for multiple ports. Network devices on the System
Under Test must allow their IP addresses to be temporarily changed to
10.10.n.10/24, where n is 10, 11, 12, and so forth for multiple ports.
All network devices between the Test Manager system and the System
Under Test must allow these IP addresses.
If you are doing serial I/O certification, set
up the serial ports.
Make sure at least one pair of serial ports is connected between the
Test Manager system and the System Under Test.
Installing the Solaris OS
For Solaris 10 installation details, see the Release and
Installation Collection for the
particular Solaris 10 release that you want to install. Start with the
Installation
Guide: Basic Installations. For Solaris Express Developer Edition
installation details, see Solaris Express
Developer Edition Installation Guide. For additional help with Solaris
OS installation, see the Solaris
OS Install web site.
Use the following command to verify that you are running
the Solaris 10
OS or the Solaris Express Developer Edition OS:
% cat /etc/release
If you are installing the Solaris 10 OS, you must make
the
following customization:
Select "None" for "Name Service."
Select "Initial Install" for "Upgrade or Initial
Install".
Perform at least a Developer group installation. See
the Solaris 10
Package List for a list of what you get with different types of
installations. Select "Custom Install" and then select "Developer
group" or above.
For Solaris 10 installation or Solaris Express Developer
Edition installation, partition the disk
to satisfy the Hardware Requirements stated above.
You might want to back up your test systems and
reinstall the
Solaris OS before you install and run the HCTS.
The HCTS 4.0 archive is a tar file from which you need
to extract the contents. The name of the downloaded file is hcts.4.0.tar.gz.
On each machine, enter the following command to extract
the HCTS content:
$ gzip -cd hcts.4.0.tar.gz | tar xvf -
The contents are extracted into a directory called
hcts.4.0, which is placed in
the directory where you downloaded HCTS. This hcts.4.0 directory
contains the following files:
hcts.4.0.README
hcts.4.0.ReleaseNotes
SUNWhcts package
Installing HCTS
Be sure to read the hcts.4.0.README and
hcts.4.0.ReleaseNotes documents in the /hcts_extract_dir/hcts.4.0
directory
before you install HCTS.
Installation verifies that no previous version of HCTS
is on your system. If
HCTS is already installed on this system, uninstall the existing
version.
On each system, perform the following steps to install
HCTS:
% su # /usr/sbin/pkgadd -d . SUNWhcts
Watch for any questions or error messages from the
installation and respond accordingly.
The HCTS installation performs the following actions:
Verifies that no version of HCTS is already
installed on the system.
Installs the package SUNWhcts
into the /opt directory.
Installs the x11perf
binary file into /usr/X11/demo/.
Installs the x11perf.1x
man page file into /usr/X11/share/man/man1
for the video test case.
Creates a /docs
directory within the /opt/SUNWhcts
directory.
Adding a New Network Card
Take the following steps to add a new network card to a
machine that is running the Solaris OS:
Physically install the card in the machine.
Start the system.
Use either the drvconfig(1M)
command or the devfsadm(1M)
command to tell the Solaris OS that a new network card has been added.
If you do not use one of these two commands, HCTS might be unable to
certify your newly added card because the system might have outdated
hardware information. If the new card still is not recognized, reboot
your machine using the following command to force the Solaris OS to
update the hardware information.
# reboot -- -r
Running the HCTS Application
Caution - For
system certification, if the System Under Test contains more than one
disk
drive, any disk that does not have any slice mounted to /,
/usr, /opt, /var, or
/export/home*
is formatted. All data on such a disk is lost. During the test
initialization process, any disk that is scheduled to be formatted is
listed. The
initialization process pauses for 60 seconds and prompts you to stop
the certification
if you do not want the disk to be formatted.
To certify the System Under Test as a system, if the SUT
has a CD/DVD drive, insert a CD/DVD into the drive.
Using the GUI
To start the HCTS GUI, use the HCTS command:
$ /usr/bin/hcts
On the Test Manager system, if you are prompted to
select a
Mode for this machine, click the Test Manager button. HCTS will set up
the network environment to make this system an HCTS Test Manager System.
On the System Under Test, if you are prompted to select
a
Mode for this machine, click the System Under Test button.
To certify a system, click the Certification Center tab
and then the System
Certification tab. Click the Start button.
The System Certification page is shown in the following
figure:
To run the Component Certification test (Audio, CD/DVD
RW, CD/DVD ROM, Network, Serial,
Storage, USB keyboard and video tests), click the Certification Center
tab and then
the Component Certification tab. Select the component and click the
Start button.
The Component Certification page is shown in the
following figure:
When testing is finished, click the Results tab and
click the Latest Certification
Result tab.
Click the name of the test in the table to view the
detailed results for that test. Click the View Summary File link to
view
the summary of the results of all tests listed in the table.
To access the results archive file that you need to
submit to
the HCL if your certification testing passed, click the Results tab and
click
the Certification Logs tab.
Click on a file name to save the file so that you
can submit it to the HCL. To delete a results file, click the
box to the left of the file name, and then click the Delete
button. All checked files are deleted. To select all files, click the
button
with the two check marks at the top of the list of files.
To deselect all files, click the other button at the top of
the list of files.
Using the CLI
To start the HCTS command line interface, use the hctscli command. See the
hctscli(1M) man
page for more information.
Enter the following command to set up the Test Manager
system:
# /usr/bin/hctscli setup-tm
Enter the following command to certify the System Under
Test as a
system:
# /usr/bin/hctscli certify System
Enter the following command to list certifiable network
devices of the System Under
Test:
# /usr/bin/hctscli list-device Network
Enter the following command to certify the network of
the System Under Test
using the IPv4 protocol:
If no device is specified for the certify network
command, then all network
devices are tested at the same time.
Enter the following command to list serial devices of
the System Under Test:
# /usr/bin/hctscli list-device Serial
Enter the following command to certify the serial I/O
component of the System
Under Test:
# /usr/bin/hctscli certify Serial
If no device is specified for the certify
Serial command, then all serial devices
are tested one by one.
Note - After you
complete all testing, uninstall HCTS. Before you put the test systems
back into production use, you might want to reinstall your test system
to
its original configuration.
Global Options
In HCTS 4.0, there are three global options that you can
use
in GUI and CLI. These global options are:
Exit On Error - When this option
is set, HCTS exits immediately when any test case fails. The test
environment will not be cleaned.
Manual Network Setup - When this
options is set, user should
configure the IP addresses for the network interfaces to be tested
before starting the HCTS test. See the HCTS 4.0 man page for more
information.
Diagnosis - When this option is
set, a few DTrace
scripts run in parallel with test cases to collect information for
debugging. This option should only be used for failure analysis.
Certification with this option set is not qualified for HCL submission.
Custom Test Plan
The Custom Test Plan feature provides an interface for
creating test plans which
may provide additional failure diagnostics information. Custom Test
Plan results are not valid
for HCL submission.
Tunable Options permit the customization of various
predefined test arguments. By modifying the
values of these options, you can control the exposed runtime attributes
for the
Test Case operating on the associated device.
For more information, see the Custom Test Plan online
help page under
Certification Center > Custom Test Plan.
Unless otherwise licensed, code in all technical manuals herein (including articles, FAQs, samples) is provided under this License.
Print-friendly Version
