Installing Diagnostics; Using Diagnostic Tests - Compaq ServerNet ServerNet II Installation Manual

Installing Diagnostics

For information about installing Diagnostics, see the section "Installing ServerNet II
Applications and Utilities" in Chapter 2 of this guide.

Using Diagnostic Tests

ServerNet II Online Diagnostics can help you isolate system failures. Use Diagnostics during
ServerNet II installations to test your configuration, when a failure occurs on the ServerNet II
SAN, or when system performance deteriorates.
NOTE: Diagnostic tests verify only that the ServerNet II SAN components are functioning normally. They
do not verify that the applications you are running are working as expected.
All — Runs all Diagnostics tests
I
Echo Test — This is the first test you should run when you suspect problems with a
I
computer communicating with another node on the SAN. It tests the communication path
between the local host and the remote node. If the echo test fails, run other tests to help
isolate the failure. We recommend you only run the test on the nodes associated with the
SAN failure. This may isolate the failure without running the Echo Test on each node.
Topology Test — Checks that the topology matches the one that was configured and
I
reports any differences
Routing Test — Checks the links between SAN nodes. Because the IBC protocol can
I
actually communicate with a Switch, it can test nearly all of the links in the SAN from any
local host. The routing test should be used after the echo test to try to find a failed link that
could be causing an echo test failure.
Command Line Interface — See Appendix H, "ServerNet II Diagnostic Resources" for
I
information about using the Command Line Interface with the Diagnostic interactive
mode.
See the decision chart in Appendix F, "Troubleshooting ServerNet II," if you are not sure when
to run a specific Diagnostic test.
IMPORTANT: Diagnostics is a troubleshooting tool designed to help isolate hard faults, such as a
disconnected cable or other equipment failure. It does not isolate intermittent faults, such as high
network traffic that results in loss of packets/information or multiple collisions.
Using ServerNet II Diagnostics 3-3