|
Running diagnostic tests
Running individual diagnostic tests
Individual test menu structure
The hardware component that you are testing determines what appears in its test menu. However, all individual test menus share some common features:
- 1 -- Use this option to run a comprehensive test or all tests in the menu. This is the quickest way to learn whether you have a problem on the component.
- 99 -- Use this option to exit the menu.
See Diagnostics Menus, for a detailed description of the individual test menus.
The following table describes the basic organization of test menus by numbers and shared functions.
| Menu number |
Function |
1 |
Runs all the tests in the main test group (2-19) |
2-39 |
This is the main test group. Each test tests a specific part of the component.
|
40s |
Runs additional tests, which are used to debug and narrow down the problem after you run the main test group.
|
70s through 80s
|
Displays specific information about the system component. Also lets you set specific conditions for testing. These tests are also used for initialization functions.
|
90s |
Lets you set the loop, stop, and xtnd options at the test menu level and exit.
|
Running individual diagnostics
To run diagnostics on an individual component, complete the following steps.
| Step |
Action |
| 1 |
In the Diagnostic Monitor, after the Enter
Diag, Command, or
Option prompt, enter the name of the diagnostic.
Example
gbe
Result
The Gigabit diagnostic test menu appears.
|
| 2 |
Enter the number of the test you want to run or enter 1
to run a comprehensive test.
|
|