Hardware Diagnostic Suite Test Reference
|
This appendix contains descriptions of the following Hardware Diagnostic Suite tests and lists all test requirements:
CDROM Test
The CDROM test checks the CD-ROM drive.
Each track is classified as follows:
- Mode 1 uses error detection/correction code (288 bytes).
- Mode 2 uses auxiliary data space or an audio track.
TABLE A-1 CDROM Test Descriptions and Requirements
Test Mode
|
Description
|
Requirements
|
Quick Check
|
Verifies that a CD-ROM drive is connected to the system.
|
None
|
Full Test
|
Verifies the functionality of the drive by accessing and reading the media in the drive. If the media contains audio and the audio test is enabled, the test tries to play it. Only a small percentage of the media is read, as this is sufficient to verify the functionality of the drive. It also keeps the test runtime from being unnecessarily extended.
If the device is busy at the time of testing, the test exits after printing a message indicating that the device is unavailable for testing.
|
Load a CD-ROM (data or audio) into the drive before starting this test.
|
Disk Test
The Disk test verifies the functionality of hard drives.
TABLE A-2 Disk Test Descriptions and Requirements
Test Mode
|
Description
|
Requirements
|
Quick Check
|
Opens the drive, checks the drive configuration, reads a few blocks, and then closes the drive. All UNIX drive error messages are monitored and displayed. No hard drive data is written and no file system test is performed.
|
None
|
Full Test
|
Opens the drive, checks the drive configuration, performs a read-only test on the drive under test, and performs random seek checks.
No file system test is run. When the test is done, the test closes the drive. All UNIX hard drive error messages are monitored and displayed.
|
None
|
Floppy Test
The Floppy test checks the diskette drive.
TABLE A-3 Floppy Test Descriptions and Requirements
Test Mode
|
Description
|
Requirements
|
Quick Check
|
Opens the diskette drive. All UNIX diskette drive error messages are monitored and displayed. No data is written and no file system test is performed.
|
Load a UNIX-formatted diskette into the drive.
|
Full Test
|
Opens the diskette drive, checks the configuration, and performs a read-only test on the diskette. No file system test is run. When the test is complete, the test closes the diskette drive. All UNIX diskette error messages are monitored and displayed.
|
Load a UNIX-formatted diskette into the drive.
|
Memory Test
The Memory test checks the physical memory of the system. The test locates parity errors, hard and soft error correction code (ECC) errors, memory read errors, and addressing problems. The pseudo driver mem(7) is used to read the physical memory.
This test reads through all available physical memory. It does not write to any physical memory locations.
TABLE A-4 Memory Test Descriptions and Requirements
Test Mode
|
Description
|
Requirements
|
Quick Check
|
One percent of the memory is read. The test also displays how much physical memory is available. For systems that use ECC memory error handling, the test reports the ECC errors that have occurred since it was last invoked. The test reports ECC errors for a particular CPU, memory board, or SIMM.
|
None
|
Full Test
|
Performs the same test as for the Quick Check mode, except that more of the memory is read.
|
None
|
Network Test
The Network test checks all the networking hardware on the system CPU board and separate networking controllers (for example, a second SBus Ethernet controller). Such network devices include:
- Ethernet (ie and le)
- 100-Mbits per second Ethernet (be and hme)
- Token ring (tr and trp)
- Quad Ethernet (QED)
- Fiber optic (fddi, nf, bf, and pf)
- SPARCcluster system (em)
- ATM (sa and ba)
- HiPPI
For the test to be meaningful, the machine under test must be attached to a network with at least one other system on the network. This test mainly uses the Internet Control Message Protocol (ICMP), and requires at least two machines on a network--the machine under test and another machine reliable enough to be a test target. Both machines must support Transport Control Protocol/Internet Protocol (TCP/IP). The target machine must either be configured to respond to ICMP broadcast or to RPC broadcast.
First, the Network test determines the target machines to test. It sends an ICMP broadcast to find them. If it fails to find a necessary target, it tries an RPC broadcast to the RPC port mapper daemon. After finding the target, this test performs a random test in which it sends out 256 packets with random data length and random data.
The Receive Timeout is set to 120 seconds. The number of retries before an error is flagged is set to three.
TABLE A-5 Network Test Descriptions and Requirements
Test Mode
|
Description
|
Requirements
|
Quick Check
|
Checks whether the device is connected. It searches through all the network interfaces for a specified device name. If the network test does not find the device connected, the test fails; otherwise it passes.
|
System must be connected and configured for network communications through the network interface that is tested.
|
Full Test
|
Performs as described in the general description of the test.
|
System must be connected and configured for network communications through the network interface that is tested.
|
Parallel Port Test
The Parallel test verifies the functionality of the IEEE 1248 Centronics-compatible parallel port (ECP mode capable).
If the Parallel test completes successfully, the DMA circuitry and the device driver are functioning properly.
TABLE A-6 Parallel Test Descriptions and Requirements
Test Mode
|
Description
|
Requirements
|
Quick Check
|
Verifies that a bidirectional parallel port is configured on the system. The success of the test in this mode indicates that the system has the bidirectional parallel port hardware and the software driver installed.
|
None
|
Full Test
|
Checks the functionality of the device by performing an internal
loopback test on the device, using the internal fifo loopback test ioctl.
The algorithm used:
- set TFIFO mode
- pio write/read/compare on fifo contents
- dma write to fifo and pio read/compare
|
None
|
Processor Test
The Processor test checks the floating-point unit on machines with the SPARC-based architecture. It runs a series of tests that check the registers, single- and double- precision floating point to integer conversions, addition, subtraction, multiplication, division, lock check, timing, and branching and non-branching condition instructions.
TABLE A-7 Processor Test Descriptions and Requirements
Test Mode
|
Description
|
Requirements
|
Quick Check
|
Checks the characteristics of the CPU.
|
None
|
Full Test
|
Exercises the functionality of the floating point unit.
|
None
|
Serial Port Test
The Serial test checks the on-board serial ports (zs[0,1], zsh[0,1], se[0,1], se_hdlc[0,1]).
An asynchronous and a synchronous test are run in Full Test mode. They are described below:
- Asynchronous test - Uses the asynchronous communication protocol as described in the zs(7D)and se(7D) man pages. The termio(7I)interface is used for configuring port characteristics. The test writes and reads data through the loopback path and compares the data to the original data. The test first sends a single character. If no errors or timeouts are detected, the rest of the data is simultaneously written and read, then compared.
- Synchronous test - Uses the synchronous HDLC-framing interface as described in the zsh(7D) and se_hdlc(7D) man pages. Data is written and read in checksum-protected packets.The synchronous test runs in three phases:
- The first phase looks for activity on the port. If no activity is detected for at least four seconds, the test proceeds to the next phase. If activity is detected, the serial test exits with an error.
- The second phase attempts to send and receive one packet. If no packets are detected after five attempts, the test exits with an error. If a packet is returned, the result is compared to the original. If the length and content of the packets do not match exactly, the test exits with an error.
- The third phase attempts to send many packets through the loop. Some packet drops are to be expected, especially on a heavily-loaded system. Each packet is compared with its original for length and content. If a mismatch is detected, the test exits with an error.
TABLE A-8 Serial Test Descriptions and Requirements
Test Mode
|
Description
|
Requirements
|
Quick Check
|
Opens the port to determine if the device is connected. If the open operation fails and the port is not busy, the test exits with an error. If the open operation is successful or fails with a busy or exclusive use error, then the port is considered connected, and the test passes.
|
None
|
Full Test
|
Performs synchronous and asynchronous testing. If the device supports an internal loopback, then the Full Test is run using the internal loopback. The zs(7D) device supports an internal synchronous loopback and the se(7d) device supports an internal asynchronous loopback.
|
None
|
Sun StorEdge A5x00 Enclosure Test
The Sun StorEdge A5x00 Enclosure test is used to verify the functionality of the Sun StorEdge A5x00 subsystems.
The Sun StorEdge A5x00 enclosure test detects all Sun StorEdge A5x00 enclosures connected to the host and collects relevant configuration information.
TABLE A-9 Sun StorEdge A5x00 Enclosure Test Descriptions and Requirements
Test Mode
|
Description
|
Requirements
|
Quick Check
|
The host connections and the status of the enclosure are checked. The test fails if there are any broken connections or if a critical enclosure condition is detected.
|
None
|
Full Test
|
Searches for all the active and inactive connections between the host and the enclosure and reports the number of existing active connections. The test diagnoses any inactive connections and reports the possible causes for the failure.
The status of the enclosure is obtained by querying the SCSI Enclosure Services (SES) device in the enclosure. Detailed information regarding the status of the elements within the enclosure is reported. The test fails if a critical condition is detected in the enclosure.
|
None
|
Sun StorEdge A/D 1000 Enclosure Test
The Sun StorEdge A/D 1000 Enclosure test is used to verify the functionality of the Sun StorEdge 1000 enclosure.
The A/D 1000 Enclosure test detects all the connected Sun StorEdge enclosures and displays the status of the various elements in the enclosure.
TABLE A-10 Sun StorEdge A/D 1000 Enclosure Test Descriptions and Requirements
Test Mode
|
Description
|
Requirements
|
Quick Check
|
The enclosure status summary bits are read. Detailed information is reported only if an unrecoverable or critical condition is detected.
|
None
|
Full Test
|
Checks and reports the status of the following elements in the enclosure:
- Disk
- Power supply
- Fan
- Temperature
- RPA cache battery (Sun StorEdge A1000 only)
An error is registered if an unrecoverable or critical condition is detected. Noncritical conditions are reported through warning messages.
|
None
|
SPARCstorage Array Controller Test
The SPARCstorage Array Controller test checks the functionality of the controller board on the SPARCstorage Array. The SPARCstorage Array Controller test isolates failures on the array disk drives from failures on the SSA controller board.
TABLE A-11 SPARCstorage Array Controller Test Descriptions and Requirements
Test Mode
|
Description
|
Requirements
|
Quick Check
|
Checks the state of the battery module and the fan module of the SPARCstorage Array.
|
None
|
Full Test
|
Exercises the hardware and software by invoking SCSI read buffer commands of various sizes to the NVRAM. These operations exercise all components except the SCSI devices: the host Fibre Channel hardware, the array Fibre Channel hardware, the array resident management software, and the hardware component interaction on the array controller card.
Note--To test the hard drives, use the Disk test. This test also reports failure of the fan module and the NVRAM battery module of the SPARCstorage Array.
|
None
|
Tape Test
The Tape test verifies the presence or operation of various kinds of tape drives. It supports 4-mm, 8-mm, DLT, 1/4-inch cartridge, and 1/2-inch front-load tape drives.
TABLE A-12 Tape Test Descriptions and Requirements
Test Mode
|
Description
|
Requirements
|
Quick Check
|
Verifies that the drive can be opened and that the drive type can be determined. If both checks are successful, or if the drive is currently busy, then the test passes. The tape test fails if the open operation is unsuccessful for any reason other than that the drive is busy.
|
None
|
Full Test
|
Verifies that the drive can be opened and that the drive type can be determined. If both checks are successful, or if the drive is currently busy, then the test passes. The tape test fails if the open operation is unsuccessful for any reason other than that the drive is busy.
|
None
|