Dell PowerVault NX3500 Administrator's Guide - Page 120

PowerVault NX3500, address from that list see the following comments regarding DNS

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

sure that the services continue even if a controller fails. Without being aware of the system's architecture, clients benefit from its high availability and high performance. Client users may access the system in a variety of network topologies. From a performance perspective, the important question is which subnets the clients belong to (there may be more than one) and can the PowerVault NX3500 be on the same subnets. Depending on the physical capabilities of the network infrastructure, the PowerVault NX3500: • Belongs to all LAN/client subnets, in which case all clients are considered flat. From a performance perspective, this is the most optimal configuration. In such network configurations, it is sufficient to define one client access virtual IP address (VIP) for each subnet, the same VIP that is described in Accessing the System. • Does not belong to any of the LAN/Client subnets, in which case all clients are considered routed. In such situations, the clients access the data via a router or layer 3 switches. In such network configurations it is recommended to define multiple client access virtual IP addresses in a single subnet, and provide some mechanism for clients to select an IP address from that list (see the following comments regarding DNS configuration). • Belongs to some of the LAN/Client subnets, in which case some clients are flat and some are routed. In such network configurations it is recommended to use both methods described above, and inform the users about the VIPs they need to use, depending on whether they are flat or routed. It is recommended to define an entry in the DNS for every subnet that the system belongs to, so that clients can access the data without remembering the VIPs. If there are multiple VIPs in the subnet, define a single name in your DNS server that will issue IP addresses from that list in a round-robin fashion and that all the clients access the system by that DNS name. NOTE: Never intermix VIPs from different subnets in a single DNS name. 120 Managing the PowerVault NX3500

  • 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
120
Managing the PowerVault NX3500
sure that the services continue even if a controller fails. Without being aware
of the system's architecture, clients benefit from its high availability and high
performance.
Client users may access the system in a variety of network topologies. From a
performance perspective, the important question is which subnets the clients
belong to (there may be more than one) and can the PowerVault NX3500 be
on the same subnets.
Depending on the physical capabilities of the network infrastructure,
the
PowerVault NX3500
:
•
Belongs to all LAN/client subnets, in which case all clients are considered
flat. From a performance perspective, this is the most optimal
configuration. In such network configurations, it is sufficient to define one
client access virtual IP address (VIP) for each subnet, the same VIP that is
described in Accessing the System.
•
Does not belong to any of the LAN/Client subnets, in which case all clients
are considered routed. In such situations, the clients access the data via a
router or layer 3 switches. In such network configurations it is
recommended to define multiple client access virtual IP addresses in a
single subnet, and provide some mechanism for clients to select an IP
address from that list (see the following comments regarding DNS
configuration).
•
Belongs to some of the LAN/Client subnets, in which case some clients are
flat and some are routed. In such network configurations it is
recommended to use both methods described above, and inform the users
about the VIPs they need to use, depending on whether they are flat or
routed.
It is recommended to define an entry in the DNS for every subnet that the
system belongs to, so that clients can access the data without remembering
the VIPs. If there are multiple VIPs in the subnet, define a single name in your
DNS server that will issue IP addresses from that list in a round-robin fashion
and that all the clients access the system by that DNS name.
NOTE:
Never intermix VIPs from different subnets in a single DNS name.