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

Network Considerations

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

2-34 Compaq ProLiant Clusters HA/F100 and HA/F200 Administrator Guide Network Considerations This section addresses clustering items that affect the corporate LAN. MSCS has specific requirements regarding which protocol can be used and how IP address and network name resolution occurs. Additionally, consider how network clients will interact within a clustering environment. Some client-side applications may need modification to receive the maximum availability benefits of operating a cluster. Network Configuration Network Protocols TCP/IP and NBT (NetBIOS over TCP/IP) are the only transport protocols that are supported in an MSCS failover environment. Other protocols, such as NetBEUI, IPX/SPX (Novell), NB/IPX, or DLC (IBM) may be used, but they cannot take advantage of the failover features of MSCS. Applications that use these other protocols will function identically to a single-server environment. Users can still use these protocols, but they will connect directly to the individual servers and not to the virtual servers on the cluster, just as in a single-server environment. If a failure occurs, any connections using these protocols will not switch over. Since these protocols cannot fail over to another server, avoid these protocols, if possible. WINS and DNS WINS (Windows Internet Name Service) and DNS (Domain Name Service) are supported in MSCS. Use WINS to register the network names and IP addresses of cluster resources. If WINS is not used, create an entry in the hosts or lmhosts file that lists each network name and IP address pair, as well as the cluster name and its IP, address since these function as virtual servers to the clients. If clients are located on a different subnet than the cluster nodes, modify the DNS database to add a DNS address record for the cluster.

  • 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
2-34
Compaq ProLiant Clusters HA/F100 and HA/F200 Administrator Guide
Network Considerations
This section addresses clustering items that affect the corporate LAN. MSCS
has specific requirements regarding which protocol can be used and how
IP address and network name resolution occurs. Additionally, consider how
network clients will interact within a clustering environment. Some client-side
applications may need modification to receive the maximum availability
benefits of operating a cluster.
Network Configuration
Network Protocols
TCP/IP and NBT (NetBIOS over TCP/IP) are the only transport protocols that
are supported in an MSCS failover environment. Other protocols, such as
NetBEUI, IPX/SPX (Novell), NB/IPX, or DLC (IBM) may be used, but they
cannot take advantage of the failover features of MSCS.
Applications that use these other protocols will function identically to a
single-server environment. Users can still use these protocols, but they will
connect directly to the individual servers and not to the virtual servers on the
cluster, just as in a single-server environment. If a failure occurs, any
connections using these protocols will not switch over. Since these protocols
cannot fail over to another server, avoid these protocols, if possible.
WINS and DNS
WINS (Windows Internet Name Service) and DNS (Domain Name Service)
are supported in MSCS. Use WINS to register the network names and IP
addresses of cluster resources. If WINS is not used, create an entry in the
hosts
or
lmhosts
file that lists each network name and IP address pair, as well as the
cluster name and its IP, address since these function as virtual servers to the
clients.
If clients are located on a different subnet than the cluster nodes, modify the
DNS database to add a DNS address record for the cluster.