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

The corporate LAN Ethernet card, Advanced Network Fault Detection

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

6-14 Compaq ProLiant Clusters HA/F100 and HA/F200 Administrator Guide Table 6-4 Solving Client-to-Cluster Connectivity Problems continued Problem Possible Cause Clients cannot access resources on a cluster node. 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. Clients cannot access cluster WINS- or DNS-related. resources. 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 Compaq's Advanced Network Fault Detection and Correction feature. 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. 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

  • 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-14
Compaq ProLiant Clusters HA/F100 and HA/F200 Administrator Guide
Table 6-4
Solving Client-to-Cluster Connectivity Problems
continued
Problem
Possible Cause
Action
Clients cannot access
resources on a cluster node.
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.
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 Compaq’s
Advanced Network Fault Detection
and Correction feature. Configured
in this way, the private
interconnect has two backups and
the primary LAN network card has
a backup as well.
Clients cannot access cluster
resources.
WINS- or DNS-related.
1.
Verify that the client machines are
configured with WINS.
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