Dell PowerFlex 4.5.x Technical Overview

Networking

This section describes the various considerations for managing inter-node communication: through a separate network with access to the PowerFlex components, or on the same network.

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

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

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

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 https://www.dellemc.com/collateral/white-papers/h17332-dellemc-vxflex-os-networking-best-practices.pdf) or by using several data networks in PowerFlex.

  For more information about MTU performance considerations and best practices, see the PowerFlex Configure and Customize 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 Mgmt IP	MDM IPs	SDS All IPs	SDS-SDS Only IPs	SDS-SDC Only IPs
  Comments	Management Access	Control Network	Rebuild and Data Path Network	Rebuild Network	Data Path Network
  	Optional, but recommended; 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. MDM Virtual IP is supported on the data network.	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).