Compaq ProLiant DL380 Quick Install Manual page 71

5-6 Compaq ProLiant Clusters for SCO UnixWare 7 U/300 Quick Install Guide for the Compaq ProLiant DL380
Table 5-3
Solving Node-to-Node Communication Problems
Problem
Existing node does not
rejoin the cluster
continued
Possible Cause
Node hardware failure
Ethernet crossover cable is
not correctly cabled or is
defective
Embedded NIC is not
correctly functioning
SPA is not correctly
functioning
Node hardware failure
Both X and Y ServerNet I
cables are damaged
Note: Damage can occur if
cables are improperly
secured and both cables are
severely crimped when a
rack-mount server on a
slide-rail is pushed back into
a rack.
Mismatched kernels
Action
Disconnect the node from the cluster.
Diagnose and repair hardware failures
as a stand-alone ProLiant server.
Verify that the Ethernet crossover cable
is connected as described in Chapter 2
of this guide.
Verify that the embedded NIC is correctly
configured.
Verify the SPA using the Compaq
ServerNet Verification Utility (SVU) as
described in Chapter 1, "Clustering
Overview," of this guide. Replace if
necessary.
Disconnect the node from the cluster.
Diagnose and repair hardware failures
as a stand-alone ProLiant server.
Check the ServerNet I cables to
determine that the cables are properly
connected and do not have bent pins. If
necessary, replace the ServerNet I
cables and reboot the node.
If the node now joins the cluster, verify
that the X and Y ServerNet I connections
are properly working by using the
ServerNet I graphical monitor or the
ServerNet I command line diagnostic
( )
spam .
Redo the dependent node install on any
node that does not have the latest
kernel. In the future, ensure that all
nodes are operating when building
kernels.
continued