Sun Microsystems V490 Manual Do Utilizador
Chapter 10
Isolating Failed Parts
177
How to Isolate Faults Using Interactive
OpenBoot Diagnostics Tests
OpenBoot Diagnostics Tests
Before You Begin
Because OpenBoot Diagnostics tests require access to some of the same hardware
resources used by the operating system, they cannot be operated reliably after an
operating system halt or Stop-A key sequence. You need to reset the system before
running OpenBoot Diagnostics tests, and then reset the system again after testing.
Instructions for doing this follow.
resources used by the operating system, they cannot be operated reliably after an
operating system halt or Stop-A key sequence. You need to reset the system before
running OpenBoot Diagnostics tests, and then reset the system again after testing.
Instructions for doing this follow.
This procedure assumes you have established a system console. See:
■
What to Do
1. Halt the server to reach the ok prompt.
How you do this depends on the system’s condition. If possible, you should warn
users and shut down the system gracefully. For information, see “About the ok
Prompt” on page 49.
users and shut down the system gracefully. For information, see “About the ok
Prompt” on page 49.
2. Set the auto-boot? diagnostic configuration variable to false. Type:
3. Reset or power cycle the system.
4. Invoke the OpenBoot Diagnostics tests. Type:
The obdiag prompt and test menu appear. The menu is shown in
ok setenv auto-boot? false
ok obdiag