Maximizing Diagnostic Testing - Sun Microsystems Netra 440 Diagnostics And Troubleshooting Manual

Maximizing Diagnostic Testing

To maximize system reliability, it is useful to have POST and OpenBoot Diagnostics
tests trigger in the event of an operating system panic or any reset, and to run
automatically the most comprehensive tests possible. For background information,
see "Diagnostics: Reliability versus Availability" on page
To Maximize Diagnostic Testing
M
1. Log in to the system console and access the ok prompt.
2. Do one of the following, whichever is more convenient:
Set the server's system control rotary switch to the Diagnostics position.
I
You can do this at the server's front panel or, if you are running your test session
remotely from console display, through the ALOM interface.
Set the diag-switch? variable to true. Type:
I
ok setenv diag-switch? true
3. Set the OpenBoot configuration diag-script variable to all. Type:
ok setenv diag-script all
This allows OpenBoot Diagnostics tests to run automatically on all motherboard
components and IEEE 1275-compatible devices.
Note – If you prefer that OpenBoot Diagnostics examine only motherboard-based
devices, set the diag-script variable to normal.
4. Set OpenBoot configuration variables to trigger diagnostic tests. Type:
ok setenv post-trigger all-resets
ok setenv obdiag-trigger all-resets
56 Netra 440 Server Diagnostics and Troubleshooting Guide • April 2004
14.