PowerFlex Manager - PowerFlex logical network release, interoperability, and expansion rules

What are the differences between the logical network designs for PowerFlex Rack and Appliance? What are the interoperability and expansion rules for PowerFlex Manager for the logical network designs?

The table below summarizes the high-level differences between the different designs:

Designs	​Node hardware	Node network speed​	Number of storage data networks	Node network interface - Link aggregation (bonding/teaming) - customer networks	Node network interface - Link aggregation (bonding/teaming) - storage data networks	Switch MLAG	​Network traffic load balancing	​Flex services	Upgrade path
​Non-bonded NIC port design	​13G	​10G	2	Switch dependent bonding (static) with trunking.	Non-bonded/non-trunking	Yes	​IP HASH	​N/A	Static bonding NIC port design, LACP bonding NIC port design
​Static bonding NIC port design	​14G	​25G	2	Switch dependent bonding (static) with trunking.	Switch dependent bonding (static) with trunking.	Yes	​IP HASH	​N/A	LACP bonding NIC port design
​LACP bonding NIC port design	​14G	​25G/100G	2 (4 optional)	Switch dependent bonding (LACP) with trunking	Switch dependent bonding (LACP) with trunking.	Yes	​LACP	​Replication	N/A

NOTE:  Non-bonded NIC port design could also be deployed on 14G nodes with 25G NICs. If an existing system has four data networks, all additional nodes should be configured with four data networks for that system.

Following are the key architectural changes:

• For the 100G Flex node, the performance is optimized for 4x100G (4-ports 100G).
• Two additional storage networks, a total of four to increase storage network performance.
• The LACP link aggregation from network switchs to Flex node network interface cards.
• The LACP network load balancing across network switchs to hypervisor virtual switchs

Upgrade path based on either replication and/or future features:
 PowerFlex logical network upgrade summary

Current System	Replication requirement	Upgrade path
Non-bonded NIC port design	Yes	LACP bonding NIC port design
Static bonding NIC port design	Yes	LACP bonding NIC port design
Non-bonded NIC port design	No	Static bonding NIC port design (customers should upgrade as a minimum to stay current) or LACP bonding NIC port design is optional.
Static bonding NIC port design	No	LACP bonding NIC port design optional

NOTE: If the current PowerFlex system is either Non-bonded NIC port design or Static bonding NIC port design and the customer want to use the PowerFlex replication feature, then the PowerFlex system must be upgraded to LACP bonding NIC port design to enable replication to be supported. The Non-bonded NIC port design was based on support for 13G, Quanta, and Kylin systems. The customers must stay current on either Static bonding NIC port design or LACP bonding NIC port design. The LACP bonding NIC port design will be the default configuration to enable current and future capabilities. It is recommended for existing customers to upgrade/migrate to LACP bonding NIC port design.

The PowerFlex logical network interoperability between Non-bonded NIC port design, Static bonding NIC port design, and LACP bonding NIC port design:
 

Current system	Co-exist	Supported
Non-bonded NIC port design	Static bonding NIC port design	Yes
Non-bonded NIC port design	LACP bonding NIC port design	No
Static bonding NIC port design	LACP bonding NIC port design	No

The PowerFlex logical network expansion guidance:

Current system	Expansion
Non-bonded NIC port design	Non-bonded NIC port design and/or Static bonding NIC port design
Static bonding NIC port design	Static bonding NIC port design

The figure below provides a visual representation to guide the expansion and interoperability of the logical network designs:


NOTE: 

• v1 = Non-bonded NIC port design
• v2 = Static bonding NIC port design
• v3 = LACP bonding NIC port design

To know how to configure network templates in the PowerFlex Manager, see PFxM - How to configure network settings in PowerFlex Manager templates