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

Table 6-4, Solving Client-to-Cluster Connectivity Problems, Use Cluster Administrator to verify

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 138 highlights

Troubleshooting the Compaq ProLiant Clusters HA/F100 and HA/F200 6-13 Table 6-4 Solving Client-to-Cluster Connectivity Problems continued Problem Possible Cause Clients do not see virtual servers. Virtual servers may not have their own IP addresses or Network Name resources. Client protocol problem. Resource name resolution problem may exist. Improper WINS configuration. IP address problem if the client is accessing the resource through a specific IP address. Action Use Cluster Administrator to verify that both resources are online. 1. Verify client is accessing the cluster using the correct cluster network name or IP address. 2. Verify client has TCP/IP protocol correctly installed and configured. Use NetBT cache (Nbtstat.exe on the Windows NT CD) to determine whether the name had been previously resolved. Confirm proper WINS configuration at the client using the WINS administrator. If WINS is not used, the hosts or lmhosts file will contain entries for each virtual server's network name and IP address. Ping the IP address of the cluster resource and cluster nodes from a DOS command prompt. Continued

  • 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
Troubleshooting the Compaq ProLiant Clusters HA/F100 and HA/F200
6-13
Table 6-4
Solving Client-to-Cluster Connectivity Problems
continued
Problem
Possible Cause
Action
Virtual servers may not have their
own IP addresses or Network
Name resources.
Use Cluster Administrator to verify
that both resources are online.
Client protocol problem.
1.
Verify client is accessing the
cluster using the correct
cluster network name or IP
address.
2.
Verify client has TCP/IP
protocol correctly installed
and configured.
Resource name resolution
problem may exist.
Use NetBT cache (Nbtstat.exe on
the Windows NT CD) to determine
whether the name had been
previously resolved.
Improper WINS configuration.
Confirm proper WINS
configuration at the client using
the WINS administrator. If WINS is
not used, the
hosts
or
lmhosts
file
will contain entries for each virtual
server’s network name and IP
address.
Clients do not see virtual servers.
IP address problem if the client is
accessing the resource through a
specific IP address.
Ping the IP address of the cluster
resource and cluster nodes from a
DOS command prompt.
Continued