| Sun Crypto Accelerator 4000 Board Version 1.1 Installation and User's Guide |    
|
| Sun Crypto Accelerator 4000 Board Version 1.1 Installation and User's Guide |
|
| C H A P T E R 7 |
|
Diagnostics and Troubleshooting |
This chapter describes diagnostic tests and troubleshooting for the Sun Crypto Accelerator 4000 software. This chapter includes the following sections:
The core SunVTS wrapper provides test control and a user interface to a suite of tests. Some of those tests are delivered with packages SUNWvts and SUNWvtsx to make up a bundle that is contained on the Solaris 8/9 Software Supplement CD. Other, unbundled, tests that use the SunVTS core are packaged with the driver software of the device tested.
The Sun Crypto Accelerator 4000 board can be tested by three SunVTS tests. Two of those tests, nettest and netlbtest, are bundled with the core SunVTS software beginning with the release of SunVTS 5.1 Patch Set (PS) 2. These tests operate on the Ethernet circuitry of the board.
The third SunVTS test, vcatest, is delivered in the SUNWvcav package on the Sun Crypto Accelerator 4000 CD and operates with the core SunVTS wrapper to provide diagnostics of the cryptographic circuitry of the board.
TABLE 7-1 shows the method of updating installed SunVTS software to provide SunVTS netlbtest and nettest support for the vca driver.
SunVTS software is delivered on the Solaris Software Supplement CD that is distributed with each Solaris release. The version of SunVTS software listed in the Base SunVTS Software column of TABLE 7-1 is distributed on the Solaris Software Supplement CD included in the Solaris release identified on the same line.
Entries in TABLE 7-1 that begin with "SunVTS" identify the version of a set of SunVTS packages. Within each SunVTS package set, the SUNWvts and SUNWvtsx packages must be installed.
The Required Replacement Packages column in TABLE 7-1 lists the SunVTS package sets that must replace the previously installed SunVTS package set. Remove the previously installed SunVTS packages before adding the SunVTS replacement packages. The previously installed SunVTS packages must be removed by the same method you used to installed them. For example, if you used the pkgadd command to install the packages, use the pkgrm command to remove the packages.
If an entry is shown in the Required Overlay Patch column in TABLE 7-1, use the patchadd command to install that patch over the SunVTS packages shown in the Base SunVTS Software column. Do not remove the previously installed SunVTS packages before adding the required patch.
Using the patchadd command to install patch 113614-11 is the equivalent of replacing the previously installed SunVTS packages with the SunVTS5.1ps2 packages.
The replacement packages are available at: http://www.sun.com/oem/products/vts/
The overlay patches are available at:
http://sunsolve.sun.com/
|
Note - The required SunVTS packages and any required patches must be installed before the SUNWvcav package is installed. The SUNWvcav package contains the SunVTS test vcatest. |
Refer to the SunVTS test reference manual, user's guide, and quick reference card for instructions on how to perform and monitor these diagnostics tests. These documents are available on the Solaris on Sun Hardware Documentation Set at http://docs.sun.com. These documents are also provided on the Solaris Software Supplement CD that is distributed with the Solaris release on your system.
|
Note - SunVTS can be used only if you have installed the required SunVTS packages and any required SunVTS patches. |
1. As superuser, start SunVTS.
Refer to the SunVTS user's guide for detailed instructions on starting SunVTS.
The following instructions assume that you have started SunVTS using the CDE user interface.
2. On the SunVTS Diagnostic main window, set the System Map to Logical mode.
|
Note - Physical mode is supported; however, this procedure assumes you are using Logical mode. |
3. Disable all tests by clearing their check boxes.
4. Select the check box for Cryptography, then select the plus box for Cryptography to display all tests in the Cryptography group.
5. Clear check boxes in the Cryptography group that are not named vcatest.
Refer to the SunVTS user's guide for the exact procedure. When the probe completes and a vcatest is displayed, continue to Step 6.
6. Select one of the instances of vcatest then right-click and drag to display the Test Parameter Options dialog box.
These options, which only pertain to the vcatest, are described in Test Parameter Options for vcatest.
7. After you have made all your selections, click Apply from the Within Instance drop-down menu to change the selected instance of vcatest, or select Apply from the Across All Instances drop-down menu to change all checked instances of vcatest.
This action removes the dialog box and returns you to the SunVTS Diagnostic main window.
8. Select one of the instances of vcatest then right-click and drag to display the Test Execution Options dialog box.
An alternate method of displaying Test Execution Options dialog box is to select the Options drop-down main menu; then select Test Executions. These options are generic SunVTS controls that affect all tests. Refer to the SunVTS user's guide for detailed information.
9. When you have made all selections, select Apply to remove the dialog box and return to the SunVTS Diagnostic main window.
10. Click Start to perform the selected tests.
11. Click Stop to stop all tests.
TABLE 7-2 describes the vcatest subtests.
To perform vcatest from the command line instead of the CDE interface, specify all arguments in the command-line string.
In 32-bit mode, the path to vcatest is /opt/SUNWvts/bin/. In 64-bit mode, the path is /opt/SUNWvts/bin/sparcv9/.
All SunVTS standard options are supported from the command-line interface for vcatest. Test-specific options are specified with the -o argument.
Refer to the SunVTS test reference manual for a definition of the standard command-line arguments. The vcatest is a Functional mode test; therefore, -f must be included. Include -u to display a usage message, or -v for VERBOSE messages. Items enclosed in square brackets denote optional entries.
The following is an example of invoking vcatest in 32-bit mode as a standalone program. The following command performs all subtests on vca0:
The following is an example of invoking vcatest in 64-bit mode from the SunVTS infrastructure. The following command tests RSA, DSA, and MD5 on vca2:
When performing vcatest from the command line, omission of an option produces the default behavior for that option, as stated in TABLE 7-3.
1. As superuser, start SunVTS.
Refer to the SunVTS user's guide for detailed startup instructions.
The following instructions assume that SunVTS was started using the CDE user interface.
2. On the SunVTS Diagnostic main window, set the System Map to Logical mode.
|
Note - Physical mode is also supported; however, this procedure assumes you are using Logical mode. |
3. Disable all tests by clearing their check boxes.
4. Select the check box for Network, then select the plus box for Network to display all tests in the Network group.
5. Clear check boxes in the Network group that are not named vcaN(netlbtest).
Note that N specifies the placement of the instance number of the device under test.
Refer to the SunVTS user's guide for the exact procedure. When the probe completes and a vcaN(netlbtest) is displayed, continue to Step 6.
6. Select the Intervention Mode button. Select one of the instances of vcaN(netlbtest), then right-click and drag to display the Test Parameter Options dialog box.
These options, which only pertain to netlbtest, are described in the SunVTS test reference manual.
7. After you have made all selections, select Apply from the Within Instance drop-down menu to change the selected instance of vcaN(netlbtest), or select Apply from the Across All Instances drop-down menu to change all checked instances of vcaN(netlbtest).
This action removes the dialog box and returns you to the SunVTS Diagnostic main window.
8. Select one of the instances of vcaN(netlbtest) then right-click and drag to display the Test Execution Options dialog box.
An alternate method of displaying the Test Execution Options dialog box is to select the Options drop-down main menu; then select Test Executions. These options are generic SunVTS controls that affect all tests. Refer to the SunVTS user's guide for detailed information.
9. When you have made all selections, select Apply to remove the dialog box the return to the SunVTS Diagnostic main window.
10. Click Start to perform the selected tests.
11. Click Stop to stop all tests.
1. As superuser, start SunVTS.
Refer to the SunVTS user's guide for detailed startup instructions.
|
Note - The following instructions assume that SunVTS was started using the CDE user interface. |
2. On the SunVTS Diagnostic main window, set the System Map to Logical mode.
|
Note - Physical mode is also supported; however, this procedure assumes you are using Logical mode. |
3. Disable all tests by clearing their check boxes.
4. Select the check box for Network, then select the plus box for Network to display all tests in the Network group.
5. Clear check boxes in the Network group that are not named vcaN(nettest).
Note that N specifies the placement of the instance number of the device under test.
If the preceding ifconfig entry is not listed, the nettest probe does not consider the device testable. Follow the ifconfig online manual page instructions for bringing an interface online.
Once the ifconfig -a produces the preceding entry, return to the SunVTS Diagnostic main window and probe the system to find vca by selecting Reprobe system in the Commands drop-down menu.
Refer to the SunVTS user's guide for the exact procedure. When the probe completes and a vca0(nettest) is displayed, continue to Step 6.
6. Select one of the instances of vcaN(nettest), then right-click and drag to display the Test Parameter Options dialog box.
These options, which only pertain to nettest, are described in the SunVTS test reference manual.
7. After you have made all selections, select Apply from Within Instance drop-down menu to change the selected instance of vcaN(nettest), or select Apply from the Across All Instances drop-down menu to change all checked instances of vcaN(nettest).
This action removes the dialog box and returns you to the SunVTS Diagnostic main window.
8. Select one of the instances of vcaN(nettest), then right-click and drag to display the Test Execution Options dialog box.
An alternate method of displaying the Test Execution Options dialog box is to select the Options drop-down main menu; then select Test Executions. These options are generic SunVTS controls that affect all tests. Refer to the SunVTS user's guide for detailed information.
9. When you have made all selections, select Apply to remove the dialog box, then return to the SunVTS Diagnostic main window.
10. Click Start to perform the selected tests.
11. Click Stop to stop all tests.
|
Note - Do not select nettest and netlbtest to be performed simultaneously. |
The Sun Crypto Accelerator 4000 board does not contain lights or other indicators to reflect cryptographic activity on the board. To determine whether cryptographic work requests are being performed on the board, use the kstat(1M) command to display the device usage:
|
Note - In the previous example, 0 is the instance number of the vca device. This number should reflect the instance number of the board for which you are performing the kstat command. |
Displaying the kstat information indicates whether cryptographic requests or "jobs" are being sent to the Sun Crypto Accelerator 4000 board. A change in the jobs values over time indicates that the board is accelerating cryptographic work requests sent to the Sun Crypto Accelerator 4000 board. If cryptographic work requests are not being sent to the board, verify your web server configuration per the web server specific configuration.
Do not attempt to interpret the kernel/driver statistic values returned by kstat(1M). These values are maintained within the driver to facilitate field support. The meanings and actual names may change over time.
|
Note - If the nostats property is defined in the /kernel/drv/vca.conf file, the capture and display of statistics will be disabled. This property can be used to help prevent traffic analysis. |
The following tests are available to help identify problems with the adapter if the system does not boot.
You can invoke the FCode self-test diagnostics by using the test or test-all commands from the OpenBoot PROM ok prompt. If you encounter an error while performing diagnostics, appropriate messages will be displayed. Refer to the OpenBoot Command Reference Manual for more information on the test and test-all commands.
The FCode self-test exercises most functionality subsection by subsection and ensures the following:
To perform the Ethernet diagnostics, you must first bring the system to a stop at the OpenBoot PROM ok prompt after issuing a reset. If you do not reset the system, the diagnostic tests might cause the system to hang.
For more information about the OpenBoot commands in this section, refer to the OpenBoot Command Reference Manual.
Use the standard shutdown procedures described in the Solaris Handbook for Sun Peripherals.
2. At the OpenBoot PROM ok prompt, set the auto-boot? configuration variable to false.
4. Type show-nets to display the list of devices and enter a selection:
You see a list of devices, similar to the example below, specific to the adapter:
|
Note - To perform the following self-test with the test command, the Ethernet port must be connected to a network. |
5. Perform the self-test using the test command:
The following tests are performed when the test command is executed:
If the test passes, you see the following messages:
ok test /pci@8,600000/network@1 Testing /pci@8,600000/network@1 Register tests: passed Internal loopback test: passed /pci@8,600000/network@1: 100 Mbps half duplex link up |
If the board is not connected to a network, you see the following messages:
ok test /pci@8,600000/network@1 Testing /pci@8,600000/network@1 Register tests: passed Internal loopback test: passed /pci@8,600000/network@1: link down |
6. After testing the adapter, type the following to return the OpenBoot PROM ok prompt interface to standard operating mode:
7. Set the auto-boot? configuration parameter to true.
8. Reset and reboot the system.
This section describes the commands available at the OpenBoot PROM level for troubleshooting the board. Refer to the OpenBoot Command Reference Manual for more information on the commands described in the following subsections.
To determine whether the Sun Crypto Accelerator 4000 device is listed in the system: from the OpenBoot PROM ok prompt, type show-devs to display the list of devices. You see lines in the list of devices, similar to the examples below, specific to the board:
ok show-devs . . /chosen /packages /upa@8,480000/SUNW,ffb@0,0 /pci@8,600000/network@1 /pci@8,600000/SUNW,qlc@4 /pci@8,600000/SUNW,qlc@4/fp@0,0 . . |
In the preceding example, the /pci@8,600000/network@1 entry identifies the device path to the board. There will be one such line for each board in the system.
To determine whether the Sun Crypto Accelerator 4000 device properties are listed correctly: from the ok prompt, type .properties to display the list of properties.
To monitor a network connection: from the ok prompt, type the apply watch-net command with the device path:
The system monitors network traffic, displaying "." each time it receives an error-free packet and "X" each time it receives a packet with an error that can be detected by the network hardware interface.
| Sun Crypto Accelerator 4000 Board Version 1.1 Installation and User's Guide | 817-3693-10 |
|
Copyright © 2004, Sun Microsystems, Inc. All rights reserved.
To Perform vcatest