Deployment Guide

15 VxFlex Network Deployment Guide using Dell EMC Networking 25GbE switches and OS10EE
VxFlex data IP network calculations
Item
Description
Comments
N
Number of nodes
Data network 1
The pools of IP addresses used for static allocation for the following
groups:
1. Node_DATA1_IP = VxFlex internal (interconnect) IP addresses
2. SVM_DATA1_IP = SVM management IP addresses
3. MDM_Cluster_Virtual_IP_DATA1 = The virtual IP of the MDM
cluster in the Data1 network
For clarity, the first
subnet is referred to
as Data1
The formula to calculate the subnet pool or subnet needs is:
N * Node_DATA1_IP + N * SVM_DATA1_IP + MDM_Cluster_Virtual_IP_DATA1
Data network 2
The pools of IP addresses used for static allocation for the following
groups:
1. Node_DATA2_IP = VxFlex Nodes internal (interconnect) IP
addresses
2. SVM_DATA2_IP = SVM management IP addresses
3. MDM_Cluster_Virtual_IP_DATA2 = The virtual IP of the MDM
cluster in the Data2 network
For clarity, the
second subnet is
referred to as Data2
The formula to calculate the subnet pool or subnet needs is:
N * Node_DATA2_IP + N * SVM_DATA2_IP + MDM_Cluster_Virtual_IP_DATA2
The IP ranges and default gateway for each IP subnet are shown in Table 4. VMware vMotion, Data1, and
Data2 do not require default gateways in this configuration. If routing is required for Data1 and Data2, see
Routing VxFlex Virtual Machine traffic in Appendix B.
IP address ranges
IP Pool
IP Subnet
Default gateway
ESXI_VMOTION_IP
172.16.32.0/24
n/a
HOST_AND_SVM_MGMT_IP
172.16.33.0/24
172.16.33.253
Node_DATA1_IP & SVM_DATA1_IP
172.16.34.0/24
n/a
Node_DATA2_IP & SVM_DATA2_IP
172.16.35.0/24
n/a
Each data and management network can reside on a different VLAN, enabling separation at a much higher
granularity. In this deployment guide, VLANs are used to separate each subnet as shown in Table 5.
VLAN and subnet association