Skip to main content
  • Place orders quickly and easily
  • View orders and track your shipping status
  • Enjoy members-only rewards and discounts
  • Create and access a list of your products
  • Manage your Dell EMC sites, products, and product-level contacts using Company Administration.

Dell PowerFlex 4.6.x Technical Overview

PDF

Networking requirements and limitations

In PowerFlex, inter-node communication manages data locations, rebuild and rebalance, and access applications to stored data on one IP network, or on separate IP networks.

Use any of the management interfaces to perform management tasks in the following ways:

  • Through a separate network with access to the other PowerFlex components
  • On the same network

Configure these options in the following ways:

  • During deployment in the full PowerFlex Installer (using the CSV topology file) and using the VMware plug-in
  • After deployment with the CLI.

The following table includes the list of PowerFlex networking requirements and supported architectures or configurations.

Table 1. Networking requirements and limitationsThe following table includes the list of PowerFlex networking requirements and supported architectures or configurations.
PowerFlex minimum network requirements and supported architectures PowerFlex network limitations
  • Ethernet-based
  • Minimum supported speed: 2*10 GbE
  • Recommended speed: 2*25 GbE
  • Certified configurations: 4*25 GbE, 2*100 GbE, 4*100 GbE
  • Supported MTU: 1500/9000 (jumbo frames recommended for optimal performance)
  • High availability and load-balancing use at least two physical ports with:
    • PowerFlex native multipath across two or more subsets:
      • Supports one to eight subnets
    • Link aggregation:
      • A single IP subnet can be used if link aggregation is used, otherwise a minimum of two subnets are required.
    • It is recommended to use MDM virtual IP for simplified network stability if there are failures.
  • IP addresses: See guidelines about IP address calculation.
  • Data network latency requirements:
    • MDM: Maximum of 300 milliseconds
  • Switch redundancy:
    • Switches must be redundant. This provides continued access to components inside the rack in the network in case an access switch fails.
    • Flat network is supported.
    • Leaf-spine architecture is recommended for cross-rack traffic.
    • VXLAN is supported.
  • SDC connection through a router is supported and required for a low latency connection for optimal performance.
  • PowerFlex has a single management subnet which can be a dedicated port or a VLAN on a trunk connection. For best practices, see:
  • RMDA is not supported.
  • InfiniBand is not supported.
  • IPv4 is supported on PowerFlex software offering.
  • IPv4 is supported on PowerFlex appliance and PowerFlex rack offerings.
  • DHCP must not be deployed on a network where PowerFlex MDMs, SDS, SDR, or SDCs reside.
  • Firewall rules must allow PowerFlex ports. For port information, see the Dell PowerFlex 4.6.x Security Configuration Guide.

The following table includes the list of PowerFlex networking requirements and supported architectures for systems with replication.

Table 2. Networking requirements and limitations for systems with replicationThe following table includes the list of PowerFlex networking requirements and supported architectures for systems with replication.
PowerFlex network requirements and supported architectures for systems with replication PowerFlex network limits for systems with replication
  • Minimum best practice with replication: 4*25 GbE or 2*100 GbE
  • Additional IP addresses for site to site routing include:
    • Within a protection domain, SDRs are installed on the same hosts as SDSs. The traffic that an SDR writes to the journal volume, is sent to all SDSs that host the journal, not only the one that is co-located on the host. In the backend storage network, each SDR listens on the same node IP addresses as the SDSs and should be able to reach all SDSs within the protection domain.
    • The SDRs require additional, distinct IP addresses which allow them to communicate with remote SDRs. Usually, these should be routable addresses with a properly configured gateway. For redundancy, each SDR should have two.
  • Static routes:
    • PowerFlex asynchronous replication usually happens over a WAN between physically remote clusters that do not share the same address segments. If the default route itself is not suitable to properly direct packets to the remote SDR IP addresses, static routes must be configured to indicate either the next top address or the egress interface or both for reaching the remote subnet.
    • PowerFlex Manager can add static routes for replication use cases.
  • MDM to MDM peer metadata synchronization should take place over a WAN with less than 200-millisecond latency.
  • Local SDR to remote SDR: Latency is not as sensitive in SDR greater than SDR traffic, but round-trip time should not be greater than 200 milliseconds.
  • Firewall rules must allow PowerFlex ports. For port information, see the Dell PowerFlex 4.6.x Security Configuration Guide.

See the following configuration guidelines used by VxFlex Ready Node for example purposes only:

This section describes how to choose from these options, depending on the requirements of your organization, security considerations, performance needs, and IT environment.

PowerFlex networking considerations:

  • Single IP network: All communications and IOs used for management and for data storage are performed on the same IP network. This setup offers the following benefits:
    • Ease of use
    • Fewer IP addresses required
  • Multiple separate IP networks: Separate networks are used for management and for data storage, or separate networks are used within the data storage part of the system. This setup offers the following benefits:
    • Security
    • Redundancy
    • Performance
    • Separate IP roles in order to separate between customer data and internal management
    NOTE:Network high availability can be implemented by using NIC-bonding (see Dell PowerFlex Appliance and PowerFlex Rack with PowerFlex 4.x Cabling and Connectivity Guide) or by using several data networks in PowerFlex.

    For more information about MTU performance considerations and best practices, see the Dell PowerFlex 4.6.x Install and Upgrade Guide.

    NOTE:The MDM cluster IP address limit is 16 IP addresses, which include all cluster members (primary, secondary, and standby).
    Table 3. Range of potential IP address configurationsThe following table describes the range of potential IP address configurations:
    Column in CSV file MDM Management IP MDM IP addresses SDS all IP addresses SDS-SDS only IP addresses SDS-SDC only IP addresses
    Comments Management access Control network Rebuild and data path network Rebuild network Data path network
    • Optional, but recommended
    • This is not applicable for tiebreaker IP addresses that can be used to provide access to PowerFlex management applications, such as PowerFlex Manager, CLI, REST API, OpenStack.
    • This IP address must be externally accessible.
    • Mandatory IP addresses used for MDM control communications with SDSs and SDCs, used to convey data migration decisions, but no user data passes through the MDM.
    • Must be on the same network as the data network.
    • Must be externally accessible if no MDM Management IP addresses are used.
    • IP addresses used for both SDS-SDS and SDS-SDC communications.
    • These IP addresses will also be used to communicate with the MDM.
    • IP addresses used for SDS-SDS communication only.
    • These addresses are used for rebuild and rebalance operations.
    • These IP addresses will also be used to communicate with the MDM.
    • IP addresses used for SDS-SDC communication.
    • These addresses are only used for read/write user data operations.

    The following combinations can be used for SDS or SDC:

    • Only SDS All IPs
    • Only SDS-SDS Only IPs + SDS-SDC Only IPs
    • SDS All IPs + either SDS-SDS Only IPs or SDS-SDC Only IPs (can be used in cases of multiple networks; ensure that you do not use the same IP address more than once in the networks).
    • SDS All IPs + both SDS-SDS Only IPs and SDS-SDC Only IPs (can be used in cases of multiple networks; ensure that you do not use the same IP address more than once in the networks).

Rate this content

Accurate
Useful
Easy to understand
Was this article helpful?
0/3000 characters
  Please provide ratings (1-5 stars).
  Please provide ratings (1-5 stars).
  Please provide ratings (1-5 stars).
  Please select whether the article was helpful or not.
  Comments cannot contain these special characters: <>()\