Dell PowerVault NX3500 Administrator's Guide - Page 26

Internal Network A, LAN/Client Network

Get Dell PowerVault NX3500 PDF manuals and user guides View all Dell PowerVault NX3500 manuals
Add to My Manuals
Save this manual to your list of manuals

Page 26 highlights

Internal Network A NOTE: Ensure that the IP addresses you assign on this network and internal network B are from a private IP space and do not conflict with other subnets on your network. PowerVault NX3500's internal network A is comprised of two independent Gigabit Ethernet ports. The internal network is the infrastructure for the PowerVault NX3500 clustering, and includes heartbeat monitoring, data transfer, and mirroring of information between the controllers' caches. The internal network also distributes data evenly across all LUNs in the system. To achieve complete data distribution and to maintain high-availability, each controller must have access to its peer controller. The internal network achieves this goal. NOTE: Internal network A is also referred to as peer-to-peer connections. The network uses point-to-point cable connections. Internal Network B NOTE: Ensure that the IP addresses you assign on this network are from a private IP space and do not conflict with subnets on your network. Internal Network B is the PowerVault NX3500 internal management network, which is plugged into the SAN switch and connects both controllers. All administrative related functions are performed on this network. In the event where the controllers lose communication with each other but continue to function independently (commonly referred to as the split-brain situation), the PowerVault management network automatically resets the suspected controller. This prevents the split brain situation and ensures data integrity. LAN/Client Network The connection between PowerVault NX3500 and the LAN/client network is based on a virtual IP (VIP) address that serves every controller in the cluster. The VIP address allows clients to access the PowerVault NX3500 as a single entity, thereby providing access to the file system. It enables the PowerVault NX3500 to perform load balancing between controllers, and ensures that the service continues even if a controller fails. 26 Introduction

  • 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
26
Introduction
Internal Network A
NOTE:
Ensure that the IP addresses you assign on this network and internal
network B are from a private IP space and do not conflict with other subnets on
your network.
PowerVault NX3500's internal network A is comprised of two independent
Gigabit Ethernet ports. The internal network is the infrastructure for the
PowerVault NX3500 clustering, and includes heartbeat monitoring, data
transfer, and mirroring of information between the controllers' caches. The
internal network also distributes data evenly across all LUNs in the system.
To achieve complete data distribution and to maintain high-availability, each
controller must have access to its peer controller. The internal network
achieves this goal.
NOTE:
Internal network A is also referred to as peer-to-peer connections. The
network uses point-to-point cable connections.
Internal Network B
NOTE:
Ensure that the IP addresses you assign on this network are from a private
IP space and do not conflict with subnets on your network.
Internal Network B
is the PowerVault NX3500 internal management network,
which is plugged into the SAN switch and connects both controllers. All
administrative related functions are performed on this network.
In the event where the controllers lose communication with each other but
continue to function independently (commonly referred to as the split-brain
situation), the PowerVault management network automatically resets the
suspected controller. This prevents the split brain situation and ensures data
integrity.
LAN/Client Network
The connection between PowerVault NX3500 and the LAN/client network is
based on a virtual IP (VIP) address that serves every controller in the cluster.
The VIP address allows clients to access the PowerVault NX3500 as a single
entity, thereby providing access to the file system. It enables the PowerVault
NX3500 to perform load balancing between controllers, and ensures that the
service continues even if a controller fails.