Chapter 7 Diagnostics and Troubleshooting 129
Note – If the nostats property is definedin the /kernel/drv/vca.conf file, the
capture and display of statistics will be disabled. This property may be used to help
prevent traffic analysis.
Using the OpenBoot PROM FCode Self-Test
The following tests are available to help identify problems with the adapter if the
system does not boot.
Youcan invoke the FCode self-test diagnostics by using the OpenBoot PROM (OBP)
test or test-all commands. 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:
■Connectivity during adapter board installation
■Verificationthat all components required for a system boot are functional

▼Performing the Ethernet FCode Self-Test

Diagnostic

Toperform the Ethernet diagnostics, you must first bring the system to a stop at the
OBP prompt after issuing a reset. If you do not resetthe 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.
1. Shut down the system.
Use the standard shutdown procedures described in the Solaris Handbook for Sun
Peripherals.
2. At the OBP prompt, set the auto-boot? configuration variable to false.
ok setenv auto-boot? false