Networking requirements for
PowerFlex file deployment
The following lists the networking requirements for a
PowerFlex file node.
Ensure that a NIC with an IP address is configured in the same range as the following networks:
PowerFlex management
PowerFlex data (1 to 4)
Create a bonded interface on the
PowerFlex node. No sub interfaces or IP addresses should be assigned to this bonded interface dedicated to NAS traffic.
PowerFlex software and
PowerFlex custom node support a single NIC or logical interface for
PowerFlex file services without the bonding requirement. For more details, see
Dell PowerFlex 4.6.x Install and Upgrade Guide.
This use case enables customers with existing network infrastructure to leverage the
PowerFlex file offering.
Dell Technologies recommends having a high-availability network of some form.
Sample configurations
A sample network configuration:
eth0 - PowerFlex Management (Node management)
eth1 - PowerFlex Data
eth2 - PowerFlex Data
bond0 (there should not be any tagged interface under bond0)
A sample IP address configuration on the PowerFlex file node:
1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN group default qlen 1000
link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
inet 127.0.0.1/8 scope host lo
valid_lft forever preferred_lft forever
inet6 ::1/128 scope host
valid_lft forever preferred_lft forever
2: eth0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc mq state UP group default qlen 1000
link/ether 00:50:56:b0:95:da brd ff:ff:ff:ff:ff:ff
altname enp11s0
altname ens192
inet 10.1.1.226/20 brd 10.234.223.255 scope global eth0
valid_lft forever preferred_lft forever
3: eth1: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc mq state UP group default qlen 1000
link/ether 00:50:56:b0:bb:8c brd ff:ff:ff:ff:ff:ff
altname enp19s0
altname ens224
inet 172.16.221.226/16 brd 172.16.255.255 scope global eth1
valid_lft forever preferred_lft forever
inet6 fe80::250:56ff:feb0:bb8c/64 scope link
valid_lft forever preferred_lft forever
4: eth2: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc mq state UP group default qlen 1000
link/ether 00:50:56:b0:3f:09 brd ff:ff:ff:ff:ff:ff
altname enp27s0
altname ens256
inet 172.17.221.226/16 brd 172.17.255.255 scope global eth2
valid_lft forever preferred_lft forever
inet6 fe80::250:56ff:feb0:3f09/64 scope link
valid_lft forever preferred_lft forever
5: docker0: <NO-CARRIER,BROADCAST,MULTICAST,UP> mtu 1500 qdisc noqueue state DOWN group default
link/ether 02:42:14:01:33:16 brd ff:ff:ff:ff:ff:ff
inet 172.29.200.1/24 brd 172.29.200.255 scope global docker0
valid_lft forever preferred_lft forever
6: eth3: <BROADCAST,MULTICAST,SECONDARY,UP,LOWER_UP> mtu 1500 qdisc mq primary bond0 state UP group default qlen 1000
link/ether 00:50:56:b0:65:04 brd ff:ff:ff:ff:ff:ff
altname enp12s0
altname ens193
7: eth4: <BROADCAST,MULTICAST,SECONDARY,UP,LOWER_UP> mtu 1500 qdisc mq primary bond0 state UP group default qlen 1000
link/ether 00:50:56:b0:65:04 brd ff:ff:ff:ff:ff:ff
altname enp4s0
altname ens161
8: bond0: <BROADCAST,MULTICAST,PRIMARY,UP,LOWER_UP> mtu 1500 qdisc noqueue state UP group default qlen 1000
link/ether 00:50:56:b0:65:04 brd ff:ff:ff:ff:ff:ffa
NOTE:The switch port connected to interfaces that are assigned to NAS bond interface should be configured to accept NAS management VLAN as untagged and NAS data VLANs as tagged.
A sample Cisco Nexus switch configuration:
interface ethernet1/1/4
no shutdown
switchport mode trunk
switchport access vlan 100
switchport trunk allowed vlan 200,201
mtu 9216
flowcontrol receive off
channel-group 8 mode active
interface port-channel10
switchport mode trunk
switchport trunk native vlan 100
switchport trunk allowed vlan 200.201
mtu 9216
no lacp suspend-individual
lacp vpc-convergence vpc 8
Data is not available for the Topic
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: <>()\