Note
If the AMS is not on the same subnet as the SVM management IP addresses, the
Discovery server used as a proxy must reside on the same switch network broadcast
domain (Physical or VLAN), in order to allow seamless detection and MGMT IP
address configuration of the SVM and ESXi IP addresses of all nodes in the system.
The VxFlex OS data IP network requires two separate subnets.
Note
Multiple IP subnets used for the VxFlex OS data network cannot be on the same
subnet. For more information, see this VMware limitation in the following link:
.
Table 4 VxFlex OS data IP network for Subnet #1
Item
Description
Comments
N
Number of nodes
IP address
pool for
Subnet #1
The pools of IP addresses used for static allocation for
the following groups:
1. Node_DATA1_IP = internal (interconnect) IP
addresses of the VxFlex Ready Node servers
2. SVM_DATA1_IP = VxFlex OS Storage VM
Management IP addresses
3. MDM_Cluster_Virtual_IP_DATA1 = the Virtual IP
addresses 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_DMDM_Cluster_Virtual_IP_DATA1
Table 5 VxFlex OS data IP network for Subnet #2
Item
Description
Comments
N
Number of nodes
IP address
pool for
Subnet #2
The pools of IP addresses used for static allocation for
the following groups:
1. Node_DATA2_IP = internal (interconnect) IP
addresses of the VxFlex Ready Node servers
2. SVM_DATA2_IP = VxFlex OS Storage VM
Management IP addresses
3. MDM_Cluster_Virtual_IP_DATA2 = the Virtual IP
addresses 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_DMDM_Cluster_Virtual_IP_DATA2
Network Architecture and Physical Connectivity
38
Hardware Configuration and Operating System Installation Guide - ESXi Servers
