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

Networking Capacity, depicts a Compaq ProLiant Cluster HA/F200 with dual RA4000s.

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

Designing the Compaq ProLiant Clusters HA/F100 and HA/F200 2-33 Figure 2-18 depicts a Compaq ProLiant Cluster HA/F200 with dual RA4000s. This configuration can accommodate load balancing because the host bus adapters are in active/active mode to different storage systems. RA4000 A S RA4000 A S storage hub storage hub A Server S A S Server Figure 2-18. Compaq ProLiant Cluster HA/F200 with dual RA4000s Networking Capacity The final capacity planning section addresses networking. The cluster nodes must have enough network capacity to handle requests from the client machines and must gracefully handle failover/failback events. Make sure both nodes can handle the maximum number of clients that can attach to the cluster. If Node1 encounters a failure and its applications and services fail over to Node2, then Node2 needs to handle access from its own network clients as well as those that normally connect to the failed node (Node1). Note the effect of failover on network I/O bandwidth. When the cluster encounters a server failover event, only one node is responding to network I/O requests. Be sure the surviving node's network speed and protocol will sufficiently handle the maximum number of network I/Os when the cluster is running in a degraded state.

  • 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
Designing the Compaq ProLiant Clusters HA/F100 and HA/F200
2-33
Figure 2-18 depicts a Compaq ProLiant Cluster HA/F200 with dual RA4000s.
This configuration can accommodate load balancing because the host bus
adapters are in active/active mode to different storage systems.
RA4000
RA4000
Server
Server
A
S
S
S
S
A
A
A
storage hub
storage hub
Figure 2-18.
Compaq ProLiant Cluster HA/F200 with dual RA4000s
Networking Capacity
The final capacity planning section addresses networking. The cluster nodes
must have enough network capacity to handle requests from the client
machines and must gracefully handle failover/failback events.
Make sure both nodes can handle the maximum number of clients that can
attach to the cluster. If Node1 encounters a failure and its applications and
services fail over to Node2, then Node2 needs to handle access from its own
network clients as well as those that normally connect to the failed node
(Node1).
Note the effect of failover on network I/O bandwidth. When the cluster
encounters a server failover event, only one node is responding to network I/O
requests. Be sure the surviving node’s network speed and protocol will
sufficiently handle the maximum number of network I/Os when the cluster is
running in a degraded state.