Filter
Top Products
134 Managing the PowerVault NX3500
Client users access the system through a variety of network topologies.
Depending on the physical capabilities of the network infrastructure,
the
PowerVault NX3500
:
• Belongs to all LAN or client subnets. 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. For more information, see "Accessing the System" on page 133.
• Does not belong to any of the LAN or 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 or 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 can access the system.
NOTE: Do not intermix VIPs from different subnets in a single DNS name. For more
information on bonding mode and VIP setting, see "Managing Client Access" on
page 123
Performance and Static Routes
Routed networks provide another opportunity to enhance performance
through a feature called static routes. This feature allows you to configure the
exact paths in which the system communicates with various clients on a
routed network.