Contained WithinFind More DocumentationFeatured Support Resources |
Chapter 1 Using the Hardware Certification Test SuiteThe Hardware Certification Test Suite (HCTS) is composed of controller tests and system tests, utilities, and a browser-based user interface. This suite runs tests to certify various network, storage, and serial I/O controllers, as well as tests to certify systems. This suite also collects log files, determines test PASS/FAIL results, and generates a final test report. All tests must pass in a single test run to be certified. This document covers the following topics: Before You BeginBefore you begin running the HCTS application, you must complete certain actions:
Installing HCTS on your test system creates a security issue. During the installation process, the installation script executes an xhost + command that opens up access to your system. HCTS should only be installed on a non-production system on a private network. System RequirementsGeneral System RequirementsTo run HCTS, your system must meet the following general criteria:
Certification Technology System RequirementsIn addition to the general system requirements, your system must meet minimum requirements for your specific testing. The following list shows the certifications performed by HCTS and provides a link to the associated test plan for that certification. Each test plan provides the specific system requirements for each certification.
Note – Besides providing the system requirements, each test plan provides detailed instructions on how to perform the manual tests for that type of certification. The manual tests must finish successfully before you run HCTS. Using the HCTS ApplicationThe tasks required to use the HCTS application can be summarized into the following categories:
Each task is described in the following subsections. Depending on the type of certification you want to perform, see Performing Systems Certifications or Performing Controller Certifications. First, though, see Starting HCTS. Starting HCTSHCTS is a web-based application that requires you to point your browser to the system under test. See How to Start HCTS for information about beginning the certification process.
|
|
device |
The device name indicated by cntndn or cndn format. |
|
slices |
The number of slices to create on the disk. This field is optional. The default is MAXSLICE, which is currently 15. |
|
type |
The type of slices to create (raw or file system). This field is optional. The default is raw. |
|
mount |
The mount-point prefix for file systems. This field is optional. The default is MOUNT, which is currently /slice. |
The following sample commented entries illustrate the use of the info-file.
c0t1d0 8 f test 0# Put eight (8) slices on /dev/rdsk/c0t1d0. # Build file systems on all eight slices. # Mount the file systems on /test.c0t1d0s1 # through /test.c0t1d0s8. Create /etc/vfstab # entries for all file systems. c0d0 10 r # Put ten (10) slices on /dev/rdsk/c0d0. # Use all of them as raw devices. c2t0d0 6 fr tst # Put six (6) slices on /dev/rdsk/c2t0d0. # Build a file system on slice 1, use slice 2 as # a raw device, build a file system on slice 3, # use slice 4 as a raw device, etc. Mount the # three file systems on /tst.c2t0d0s1, # /tst.c2t0d0s3 and /tst.c2t0d0s5 c2t0d0 6 er tst # Same as above, but export the file systems # and create /etc/dfs/dfstab entries for them. c2t0d0 # Put MAXSLICE (15) slices on /dev/rdsk/c2t0d0. # Use all of them as raw devices. c2t0d0 e # Put MAXSLICE (15) slices on /dev/rdsk/c2t0d0. # Build file systems on all slices. Mount the # file systems on /slice.c2t0d0s0 through # /slice.c2t0d0s14. Create /etc/vfstab entries # for all file systems. Export all file systems # and create /etc/dfs/dfstab entries for them.
Ensure that you have run the make.slices utility.
See How to Run the make.slices Utility for information.
Click Certify Controller to start the controller certification process.
Choose either Level 1 or Level 2 from the pull-down menu.
Select the Storage technology (RAID, SCSI, or Fibre Channel) that you want to certify and click Continue.
Click either the Certify Controller button or the Create Custom Test Generation button, depending on the type of certification that you want to perform.
The Certify Controller button enables you to certify your controller using the standard set of automated tests for the predetermined amount of time. After clicking the Certify Controller button, the Certification Stress Tests screen appears. Go to the next step to continue the certification process.
The Create Custom Test Generation button enables you to create and execute test scenarios based on a predefined list of tests. By customizing these tests, you can do the following:
Select runtimes for each test individually
Run several tests in parallel, sequentially, or both
Start multiple instances and iterations of tests
See the HCTS online help for the Create Custom Test Generation screen to obtain specific information about how to set up these tests.
If you use the Create Custom Test Generation option, your system does not qualify for the Hardware Certification List. These tests only enable you to perform additional stress testing on your system that might not be done using the standard Certify Controller option.
After clicking Certify Controller, the certification test starts and HCTS displays the Review Test Status screen. See Reviewing Test Status for more information.
At any time during the test, you can click Stop Tests to terminate the certification process.
Ensure that you have run the make.slices utility.
See How to Run the make.slices Utility for information.
Click the Certify Controller button to start the controller certification process.
Choose either Level 1 or Level 2 from the pull-down menu.
Select the USB Hard Drive option and click Continue.
Click either the Certify Controller button or the Create Custom Test Generation button, depending on the type of certification that you want to perform.
The Certify Controller button enables you to certify your controller using the standard set of automated tests for the predetermined amount of time. After clicking the Certify Controller button, the Certification Stress Tests screen appears. Go to the next step to continue the certification process.
The Create Custom Test Generation button enables you to create and execute test scenarios based on a predefined list of tests. By customizing these tests, you can do the following:
Select runtimes for each test individually
Run several tests in parallel, sequentially, or both
Start multiple instances and iterations of tests
See the HCTS online help for the Create Custom Test Generation screen to obtain specific information about how to set up these tests.
If you use the Create Custom Test Generation option, your system does not qualify for the Hardware Certification List. These tests only enable you to perform additional stress testing on your system that might not be done using the standard Certify Controller option.
Enter the size of the USB hard drive in the field provided.
This entry can be one of the following: 60K, 500M, 40G.
Click Begin Certification to start the certification tests.
Once the test starts, the Review Test Status Screen displays. See the Reviewing Test Status for more information about this screen.
At any time during the test, you can click Stop Tests to terminate the certification process.
Serial I/O controller certification enables you to certify serial asynchronous interface/PCI (SAI/P) controllers. See the associated test plan for a complete list of the automated tests performed by HCTS during the certification process.
The following procedure shows generalized steps for how to perform a Serial I/O controller certification. For specific information about each step and values that can be used, see the HCTS online help.
Click the Certify Controller button to start the controller certification process.
Choose either Level 1 or Level 2 from the pull-down menu.
Select the SAI/P option in the Serial technology section of the Controller Certification screen.
Type the ppp-client name in the field provided and click Continue.
When indicating multiple clients, separate the clients with commas. For example, a sample entry could be: client1,client2,client3.
Click either the Certify Controller button or the Create Custom Test Generation button, depending on the type of certification that you want to perform.
The Certify Controller button enables you to certify your controller using the standard set of automated tests for the predetermined amount of time. After clicking the Certify Controller button, the Certification Stress Tests screen appears. Go to the next step to continue the certification process.
The Create Custom Test Generation button enables you to create and execute test scenarios based on a predefined list of tests. By customizing these tests, you can do the following:
Select runtimes for each test individually
Run several tests in parallel, sequentially, or both
Start multiple instances and iterations of tests.
See the HCTS online help for the Create Custom Test Generation screen to obtain specific information about how to set up these tests.
If you use the Create Custom Test Generation option, your system does not qualify for the Hardware Certification List. These tests only enable you to perform additional stress testing on your system that might not be done using the standard Certify Controller option.
After clicking Certify Controller, the certification test starts and HCTS displays the Review Test Status screen. See Reviewing Test Status for more information about this screen.
At any time during the test, you can click Stop Tests to terminate the certification process.
While the test is running, the user interface displays the Review Test Status screen. This screen provides a variety of information for you as described in the following sections.
If you need to terminate the certification test, you can click Stop Tests at any time on this screen.
At the top of the screen, a status bar displays the following information:
The name of the test system
Display: Test System= hostname, where hostname indicates the name of the machine being tested.
The type of certification
Display options: Controller Certification or Systems Certification
The level of certification being run
Display options: L1, L2, or Custom Test
The category of technology being tested
Options shown: network, storage, or serial
The time the test has been running
Display: runtime:
To update the runtime status display, click your browser's Reload button often.
During the certification testing, you can view the reports or log files generated by the certification process. You can choose a report or log file from the pull-down menu and then click on View File. The user interface displays the selected report or log file. You can return to the Review Test Status screen by clicking Back on your browser.
After the certification test completes, the following additional buttons are available to you on this screen:
Delete All Logs
Allows you to delete all the logs generated by the certification process.
Copy Test Results
Allows you to copy the test results to be submitted to Sun for audit. See Copying Test Results for instructions.
After the certification process completes and you have passed all the certification requirements, you need to copy of the test results and submit them to Sun for audit.
Click Copy Test Results.
Do one of the following:
Choose the output device from the device pull-down menu.
Type the path of the location on your system to which you would like to copy the test results.
If the results are copied to a location on your system, you must supply a full path for each test run.
Ensure that the Copy option is selected, not the Preview Test option.
Click Process Report.
If you want to preview the test report before copying it, select the Preview Test option and then click Process Report. The user interface displays the test just as it will appear when it is copied and submitted to Sun for audit. Click Back to get back to the Copy Test Results screen where you can follow the procedure above to copy the test results.
The HCTS will tar the logs and final reports into one compressed tar archive file named CC.L#.summary.tar.z or SC.L#.summary.tar.z. If you rerun the test suite without deleting this file, the file for the second test run will overwrite the previous file.
The tar file format indicates the following information:
CC indicates a Controller Certification, and L# indicates the level number that you chose.
SC indicates a Systems Certification, and L# indicates the level number that you chose.
You must include the file from your final test run in the certification package that you submit to Sun.
After you are done certifying your system, do the following steps:
Submit your results to Sun for audit.
See the HCTS web site for information about the submission process.
Reinstall your test system back to its original configuration.
Reinstalling your system removes any modifications made to your system during the certification process and closes the security issue that was created by the HCTS installation process.