3 Running Diagnostic Tests





If your system is running SunOS Version 4.x or Solaris 2.x operating systems, use the Sundiag diagnostic program to exercise your system and verify the functionality of the SBE/S SBus card. Sundiag is a system exerciser that runs diagnostic tests on Sun hardware. Sundiag verifies the configuration, functionality and reliability of most Sun hardware controllers and devices.

Sundiag's TTY interface makes it possible to run Sundiag from a terminal that is attached to a serial port, or from a modem. For detailed instructions on using Sundiag, see the Sundiag User's Guide that is supplied with your operating system documentation.

3.1 Hardware and Software Requirements

The SBE/S SBus card can be tested with Sundiag on any system that is running SunOS version 4.1.2 or later or Solaris 2.x. If the system is running SunOS 4.x, then the operating system kernel must be configured to support all of the peripherals that are to be tested.

The amount of swap space required varies with the type and amount of hardware being tested. Sundiag requires a minimum of 8 MBytes of swap space. Frame buffer tests require additional swap space and the virtual memory test requires special swap space considerations. See the Sundiag User's Guide for the swap requirements.

3.2 SBE/S SBus Card Test Options

To fully exercise the SBE/S Sbus card, run all four of these tests. See the section that follows for detailed instructions on starting and stopping the tests. (This assumes that the devices are configured. See Appendix B.)

Note - The device ID number can be checked to determine whether devices are connected to the on board SCSI or to the SBE/S card. The kernel configuration file contains the assignment of which devices are on which SCSI bus. (Refer to the installation and release manuals for your operating system.)

Note - In SunOS 4.x and Solaris 2.x operating systems, kernel boot messages, which also display device ID information that can be used to determine if a device is connected to the on board SCSI or to the SBE/S card, are located in the var/adm/messages file. A user can refer to this file to determine whether the device being tested is on the intended bus.

Note - Appendix E of this manual lists the ID numbers for SunOS 4.x assigned (by default) to devices connected to the on board SCSI, first SBE/S card, second SBE/S card, etc. Keep in mind the ID numbers contained in Table E-1 are the default numbers, and can be changed.

    1. nettest. Use this test to check the Ethernet hardware on the system and the Ethernet controllers.
    2. tapetest. Install a scratch tape before you start this test. When you select this test it rewinds the tape, erases it, writes a pattern to a specified number of blocks, or to a SCSI tape, and writes to the end of the tape. Then, it rewinds the tape and reads and compares the information that it has just written to.
    3. rawtest and fstest. Use the rawtest to perform read-only and write-only tests on local disks. Use the fstest to exercise the SBE/S DMA disk drive.
    4. cdtest. Use the Sun CD-Demo disk that is shipped with the CD-ROM to run this test.The cdtest checks the CD table of contents and when the proper CD is specified, it verifies that the table of contents matches it own TOC table. cdtest classifies each track as Mode 1 or Mode 2. Mode 1 uses error detection and correction code (288 bytes) and mode 2 uses the space for auxiliary data or as an audio track.

3.3 Starting Sundiag

Follow these steps to run Sundiag.

    1. Become superuser.
    2. Start Sundiag and display the Sundiag window.

    If your system is running SunOS 4.x:

      a. If you are running Open Windows, exit the window mode and start Sundiag in SunView.
      b. In SunView, open a shell and type this command to display the Sundiag window.

    If your system is running Solaris 2.x:

      c. From Open Windows, type this command:

3.4 The Sundiag Window

After you enter the sundiag command, the Sundiag window is displayed on your screen. This window is the primary interface for running Sundiag. See the example shown in Figure 3-1.

The Sundiag window is divided into four small windows:

    Figure 3-1 Sundiag Window

3.5 Starting the Tests

    1. Review the information shown in the control panel window. The information in the control panel identifies the devices that are available for testing. See the example shown in Figure 3-2.
    2. Click on the device that you want to test, for example DISK DEVICES. Your selection is confirmed with the display of a check mark in the box next to the device name.

    Figure 3-2 Sundiag Control Panel

    3. Click on the OPTION button, opposite the device name, to display a pop- up option menu. See the example shown in Figure 3-3.
    4. Use the mouse to select your test options. A check mark identifies that the item is selected.

    Figure 3-3 Pop-Up Option Menu

    5. If you want to use the settings that are displayed on the pop-up menu, click the mouse on the Default button. Then, click on the Start button on the control panel to start the test.
    6. If you want to change the settings that are displayed, point the mouse at the setting. Then, press the left mouse button and cycle the settings until the setting you require is displayed. Click on the Done button. Then, click on the Start button on the control panel.
    7. Watch the console window for messages.
    8. To interrupt a test, or to stop after a test is completed, click the mouse on the Stop button.

If no problems are identified during the testing, the SBE/S SBus card is ready for operation in your system. Click the mouse on the Quit button to exit Sundiag.