HP StorageWorks 4000s NAS 4000s and 9000s Administration Guide - Page 215

Cluster Group Overview, Node Based Cluster Groups, Load Balancing

Page 215 highlights

Cluster Administration Creating and managing these resources and groups must be managed through Cluster Administrator, available from the Cluster tab of the WebUI. Complete online help for creating the various cluster objects is available in the Cluster Administrator tool. Cluster Group Overview A default cluster group is automatically created when the cluster is first created. This default cluster group contains an Internet Protocol (IP) Address resource, a Network Name resource, and the Quorum disk resource. When the new cluster is created, the (IP) address and the cluster name that were specified during setup are set up as the IP address and network name of this default cluster group. Caution: Do not delete or rename the Cluster Group or IP Address. Doing so will result in losing the cluster and will require reinstallation of the cluster. When creating groups, the administrator's first priority is to gain an understanding of how to manage the groups and their resources. Administrators may choose to create a resource group and a virtual server (IP Address resource and Network Name resource) for each node that will contain all resources owned by that node, or the administrator may choose to create a resource group and virtual server for each physical disk resource. Additionally, the administrator should try to balance the load of the groups and their resources on the cluster between the two nodes. Node Based Cluster Groups Creating only one resource group and one virtual server for each node facilitates group and resource administration. This setup allows administrators to include all file share resources under one group. Clients access all of the resources owned by one node through a virtual server name. In node based cluster groups, each group has its own network name and IP address. The administrator decides on which node to place each physical disk resource. This configuration provides a very coarse level of granularity. All resources within a group must remain on the same node. Only two IP addresses and network names are required. This configuration creates less overhead for resource and network administration. A possible disadvantage of this approach is that the resource groups can potentially grow large when many file shares are created. Load Balancing The creation of separate cluster groups for each virtual server provides more flexibility in balancing the processing load on the cluster between the two nodes. Each cluster group can be assigned to a cluster node with the preferred owner parameter. For example, if there are two cluster groups, the cluster could be set up to have the first cluster group owned by node A and the second cluster group owned by node B. This allows the network load to be handled by both devices simultaneously. If only one cluster group exists, it can only be owned by one node and the other node would not serve any network traffic. NAS 4000s and 9000s Administration Guide 215

  • 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
  • 187
  • 188
  • 189
  • 190
  • 191
  • 192
  • 193
  • 194
  • 195
  • 196
  • 197
  • 198
  • 199
  • 200
  • 201
  • 202
  • 203
  • 204
  • 205
  • 206
  • 207
  • 208
  • 209
  • 210
  • 211
  • 212
  • 213
  • 214
  • 215
  • 216
  • 217
  • 218
  • 219
  • 220
  • 221
  • 222
  • 223
  • 224
  • 225
  • 226
  • 227
  • 228
  • 229
  • 230
  • 231
  • 232
  • 233
  • 234
  • 235
  • 236
  • 237
  • 238
  • 239
  • 240
  • 241
  • 242
  • 243
  • 244
  • 245
  • 246

Cluster Administration
215
NAS 4000s and 9000s Administration Guide
Creating and managing these resources and groups must be managed through Cluster
Administrator, available from the Cluster tab of the WebUI. Complete online help for creating
the various cluster objects is available in the Cluster Administrator tool.
Cluster Group Overview
A default cluster group is automatically created when the cluster is first created. This default
cluster group contains an Internet Protocol (IP) Address resource, a Network Name resource,
and the Quorum disk resource. When the new cluster is created, the (IP) address and the
cluster name that were specified during setup are set up as the IP address and network name of
this default cluster group.
Caution:
Do not delete or rename the Cluster Group or IP Address. Doing so will result in
losing the cluster and will require reinstallation of the cluster.
When creating groups, the administrator's first priority is to gain an understanding of how to
manage the groups and their resources. Administrators may choose to create a resource group
and a virtual server (IP Address resource and Network Name resource) for each node that will
contain all resources owned by that node, or the administrator may choose to create a resource
group and virtual server for each physical disk resource. Additionally, the administrator should
try to balance the load of the groups and their resources on the cluster between the two nodes.
Node Based Cluster Groups
Creating only one resource group and one virtual server for each node facilitates group and
resource administration. This setup allows administrators to include all file share resources
under one group. Clients access all of the resources owned by one node through a virtual
server name.
In node based cluster groups, each group has its own network name and IP address. The
administrator decides on which node to place each physical disk resource. This configuration
provides a very coarse level of granularity. All resources within a group must remain on the
same node. Only two IP addresses and network names are required. This configuration creates
less overhead for resource and network administration. A possible disadvantage of this
approach is that the resource groups can potentially grow large when many file shares are
created.
Load Balancing
The creation of separate cluster groups for each virtual server provides more flexibility in
balancing the processing load on the cluster between the two nodes. Each cluster group can be
assigned to a cluster node with the preferred owner parameter. For example, if there are two
cluster groups, the cluster could be set up to have the first cluster group owned by node A and
the second cluster group owned by node B. This allows the network load to be handled by both
devices simultaneously. If only one cluster group exists, it can only be owned by one node and
the other node would not serve any network traffic.