Compaq ProLiant Clusters HA/F100 Administrator's Manual page 167

Table 6-4
Solving Client-to-Cluster Connectivity Problems
Problem
Clients cannot access
resources on a cluster node.
Clients cannot access cluster
resources.
Troubleshooting the Compaq ProLiant Clusters HA/F100 and HA/F200 6-13
continued
Possible Cause
The corporate LAN Ethernet card
has failed, but the private
interconnect (cluster
communication) continues to
operate. The clients no longer
have access to their primary
cluster node and are failed over
to the secondary cluster node.
The applications in use by the
clients remain on the primary
cluster node because the private
interconnect is still operating,
precluding a failover of the
applications.
WINS- or DNS-related problems
exist.
Action
1. Manually fail over each of the
applications from the primary
server to the secondary server.
Make sure automatic failback is
disabled, to prevent the
application from failing back to the
inaccessible primary server.
2. Implement a redundant
interconnect/LAN strategy. Install
three PCI network cards per
server. Set up one as a private
interconnect configured for cluster
communication only. Set up the
other cards for client access (the
LAN) and for cluster
communication. Configure the LAN
network cards using the TLAN
Teaming and Configuration Utility
(for ThunderLAN NICs) or the
Network Teaming and
Configuration Utility (for Intel
NICs). Configured in this way, the
private interconnect has two
backups and the primary LAN
network card has a backup as
well.
1. Verify that the client machines are
configured with WINS or DNS.
2. Verify that the cluster nodes are
configured with either WINS or
DNS.
3. If DNS is used for the cluster
nodes, make sure a DNS address
record for the cluster exists in the
DNS database, particularly if the
client is on a different subnet than
the cluster.
Continued