Table of Contents
Advertisement
7.1.1 | Data Network connectivity for Lyve Rack R1
Lyve Rack R1 is designed to be highly available when client I/O is directed to the Cluster IP over data
network. The implementation relies on multicast, which has some functional implications and may not
be allowed in all deployment environments. Without any special configuration of the public data switch
(customer-owned), data direct to the Cluster IP will be retransmitted on all network ports. A preferred
way to deploy would be to configure the public data switch to group the Lyve Rack R1 node ports into
the same VLAN. The results of this will be that the multicast data will be limited to those ports in the
VLAN. If multicast setup is entirely precluded, the Cluster IP can be disabled, and an external load
balancer used in its place to direct I/O to the nodes' data IP's directly.
Note
The load balancing approach should be made sufficiently robust so as to avoid
repeatedly sending I/O to a non-responsive node (e.g., by monitoring ping or
periodically confirming connections are accepted on port 443).
The following table summarizes the network deployment options:
Deployment Mode
Without VLAN
With VLAN
Customer balanced
Customer Configuration
Required
None
Create VLAN as described
by customer switch
documentation; place two
Lyve Rack R1 nodes into
the VLAN
Installation of software or
hardware load balancer
recommended
30
Lyve Rack R1 Installation Guide
Notes
• Storage traffic directed to the Cluster IP will
be broadcasted on all network ports.
• Storage traffic is automatically balanced
between nodes.
• Down node is automatically avoided.
• Storage traffic directed to Cluster IP will be
multicast to ports within the VLAN.
• Storage traffic is automatically balanced
between nodes.
• Down node is automatically avoided.
•
I/O directed to either node's data IP will be
serviced.
•
Load balancer (software or hardware, not
included) recommended to balance I/O
between two Lyve Rack nodes.
•
Load balancer or application logic required
to avoid sending I/O to unavailable nodes
•
Not compatible with Lyve Pilot. Lyve Pilot
requires use of Cluster IP.
•
Load balancer may be configured to
terminate SSL connections. In such cases,
contact Seagate Support to enable HTTP
access on Lyve Rack.
Advertisement
Table of Contents
