Troubleshooting the Compaq ProLiant Clusters HA/F100 and HA/F200
6-5
Compaq Confidential – Need to Know Required
Writer: Bryan Hicks Project: Compaq ProLiant Clusters HA/F100 and HA/F200 Administrator Guide Comments:
Part Number: 380362-003 File Name: g-ch6 Troubleshooting the Compaq ProLiant Clusters HAF100 and HAF200.doc Last Saved On: 8/24/00 12:04
PM
Table 6-2
Solving Node-to-Node Problems
continued
Problem
Possible Cause
Action
Improper name resolution.
1.
Data in the WINS or DNS
server may be incorrect for
the second node.
2.
Ensure the proper cluster
name, node name, or IP
address is used.
3.
Verify Cluster Name
resource has started.
Cluster Service is not running.
Verify Cluster Service is running
on the first node before
attempting to join the second
node.
No network connectivity exists.
Check network connectivity.
TCP/IP is not configured properly.
Verify TCP/IP configuration on
both nodes.
No IP connectivity.
Verify IP connectivity to the cluster
address. If unable to ping the IP
address of the cluster, run Cluster
Administrator on the first node.
Ensure the cluster IP address
resource is running.
The second node cannot join the
cluster.
Primary IP address is invalid.
1.
Check the cluster IP address
resource properties. Ensure
the cluster has a valid IP
address and subnet mask.
Ensure IP address does not
conflict with an existing IP
address on the network.
2.
Verify addresses are valid. If
DHCP is used to obtain
noncluster IP addresses, run
IPCONFIG.EXE
to ensure the
network adapter cards have
valid IP addresses. If the
second IP address listed is
0.0.0.0, your primary
address is invalid.
Summary of Contents for ProLiant Clusters HA/F100
Page 8: ......
