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

NAS Server Cluster Deployment

Page 25 highlights

System Overview NAS Server Cluster Deployment In a clustered deployment, network connections are divided into three categories: cluster maintenance segments, client data segments, and management segments. The default shipping configuration contains a two-port 10/100/1000 NIC that together provide one port for the cluster maintenance and one port for management and client data. An additional management port for remote console and diagnostics is provided off of the iLO port. HP recommends that this connection be placed on a management LAN separate from the corporate infrastructure. The cluster maintenance segment is also known as the heartbeat connection between the nodes. In standard configurations, this connectivity is obtained by the use of a crossover network cable. The same effect can be achieved by placing the heartbeat ports on its own switch or VLAN, as illustrated in Figure 4 as Eth1. The purpose is to isolate and guarantee the connectivity between the nodes without interruption. If interruption occurs, the remaining cluster node will assume the other node has gone down and initiate a failover. A second cluster heartbeat path is often recommended as a redundant path. The redundant path is often done over one of the remaining network segments and is not dedicated. The client data segments of a cluster must reside on identical network segments for each node. As illustrated in Figure 4, Eth2 from both nodes is shown on the same segment. This co-location on the same segment allows cluster resources such as file shares to failover to the second node and continues to provide availability to the resources. The failed resource will have the same IP address after the failover and therefore must have a port corresponding to the identified subnet of the IP address present on both nodes. The NAS server supports the use of NIC teaming in clustered configurations. All previous caveats from the "NAS server single node deployment" on networks section still apply. Integrated Lights-Out Port Management and Client Data Network Eth 2 Cluster Node A Cluster Heartbeat Eth 1 Node A HBA 1 Node A + HBA 2 ++ + ++ + + ++ Node B + HBA 2 Node B HBA 1 SAN Switch SAN Switch Cluster Node B Cluster Quorum Mirrorset LUN 1 Storage Area Network Data RAID set Node A LUN 2 Data RAID set Node B LUN 3 Figure 4: NAS server cluster deployment NAS 4000s and 9000s Administration Guide 25

  • 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

System Overview
25
NAS 4000s and 9000s Administration Guide
NAS Server Cluster Deployment
In a clustered deployment, network connections are divided into three categories: cluster
maintenance segments, client data segments, and management segments. The default shipping
configuration contains a two-port 10/100/1000 NIC that together provide one port for the
cluster maintenance and one port for management and client data. An additional management
port for remote console and diagnostics is provided off of the iLO port. HP recommends that
this connection be placed on a management LAN separate from the corporate infrastructure.
The cluster maintenance segment is also known as the heartbeat connection between the
nodes. In standard configurations, this connectivity is obtained by the use of a crossover
network cable. The same effect can be achieved by placing the heartbeat ports on its own
switch or VLAN, as illustrated in
Figure 4
as Eth1. The purpose is to isolate and guarantee the
connectivity between the nodes without interruption. If interruption occurs, the remaining
cluster node will assume the other node has gone down and initiate a failover. A second cluster
heartbeat path is often recommended as a redundant path. The redundant path is often done
over one of the remaining network segments and is not dedicated.
The client data segments of a cluster must reside on identical network segments for each node.
As illustrated in
Figure 4
, Eth2 from both nodes is shown on the same segment. This
co-location on the same segment allows cluster resources such as file shares to failover to the
second node and continues to provide availability to the resources. The failed resource will
have the same IP address after the failover and therefore must have a port corresponding to the
identified subnet of the IP address present on both nodes.
The NAS server supports the use of NIC teaming in clustered configurations. All previous
caveats from the “NAS server single node deployment” on networks section still apply.
Figure 4:
NAS server cluster deployment
Integrated Lights-Out Port
Management and
Client Data Network
Eth 2
Cluster Node A
Node A
HBA 1
Cluster Heartbeat
Eth 1
Node A
HBA 2
Node B
HBA 2
Cluster Node B
Node B
HBA 1
SAN Switch
SAN Switch
Storage Area Network
Cluster
Quorum
Mirrorset
LUN 1
Data RAID set
Node A
LUN 2
Data RAID set
Node B
LUN 3
+
+
+
+
+++++++++++++++++++++++++++++++++++++++++++++++++++
+
+
+
+
+
+
+
+