HP ProLiant 4500 Compaq ProLiant Cluster HA/F100 and HA/F200 Administrator Gui - Page 131

Table 6-2, Solving Node-to-Node Problems, Verify Cluster Service is running

Get HP ProLiant 4500 PDF manuals and user guides View all HP ProLiant 4500 manuals
Add to My Manuals
Save this manual to your list of manuals

Page 131 highlights

6-6 Compaq ProLiant Clusters HA/F100 and HA/F200 Administrator Guide Table 6-2 Solving Node-to-Node Problems continued Problem Possible Cause The second node cannot join the cluster. Improper name resolution. Cluster Service is not running. No network connectivity exists. TCP/IP is not configured properly. No IP connectivity. Primary IP address is invalid. Action 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. Verify Cluster Service is running on the first node before attempting to join the second node. Check network connectivity. Verify TCP/IP configuration on both nodes. 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. 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.

  • 1
  • 2
  • 3
  • 4
  • 5
  • 6
  • 7
  • 8
  • 9
  • 10
  • 11
  • 12
  • 13
  • 14
  • 15
  • 16
  • 17
  • 18
  • 19
  • 20
  • 21
  • 22
  • 23
  • 24
  • 25
  • 26
  • 27
  • 28
  • 29
  • 30
  • 31
  • 32
  • 33
  • 34
  • 35
  • 36
  • 37
  • 38
  • 39
  • 40
  • 41
  • 42
  • 43
  • 44
  • 45
  • 46
  • 47
  • 48
  • 49
  • 50
  • 51
  • 52
  • 53
  • 54
  • 55
  • 56
  • 57
  • 58
  • 59
  • 60
  • 61
  • 62
  • 63
  • 64
  • 65
  • 66
  • 67
  • 68
  • 69
  • 70
  • 71
  • 72
  • 73
  • 74
  • 75
  • 76
  • 77
  • 78
  • 79
  • 80
  • 81
  • 82
  • 83
  • 84
  • 85
  • 86
  • 87
  • 88
  • 89
  • 90
  • 91
  • 92
  • 93
  • 94
  • 95
  • 96
  • 97
  • 98
  • 99
  • 100
  • 101
  • 102
  • 103
  • 104
  • 105
  • 106
  • 107
  • 108
  • 109
  • 110
  • 111
  • 112
  • 113
  • 114
  • 115
  • 116
  • 117
  • 118
  • 119
  • 120
  • 121
  • 122
  • 123
  • 124
  • 125
  • 126
  • 127
  • 128
  • 129
  • 130
  • 131
  • 132
  • 133
  • 134
  • 135
  • 136
  • 137
  • 138
  • 139
  • 140
  • 141
  • 142
  • 143
  • 144
  • 145
  • 146
  • 147
  • 148
  • 149
  • 150
  • 151
  • 152
  • 153
  • 154
  • 155
  • 156
  • 157
  • 158
  • 159
  • 160
  • 161
  • 162
  • 163
  • 164
  • 165
  • 166
  • 167
  • 168
  • 169
  • 170
  • 171
  • 172
  • 173
  • 174
  • 175
  • 176
  • 177
  • 178
  • 179
  • 180
  • 181
  • 182
  • 183
  • 184
  • 185
  • 186
6-6
Compaq ProLiant Clusters HA/F100 and HA/F200 Administrator Guide
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.