IP Addresses
VMware limitations
The AMS or discovery server must reside on the same Layer 2 physical network
(Broadcast Domain). The Ethernet broadcast protocol is used during the initial
detection and deployment process.
Prepare IP addresses in your network for the VxFlex OS nodes, based on the following
calculations:
Table 5 VxFlex OS management IP network
Item
Description
N
Number of nodes
IP address pools
The pools of IP addresses used for static
allocation for the following groups:
1. Node_MGMT_IP =VxFlex Ready
2. SVM_MGMT_IP =VxFlex OS
3. BMC_MGMT_IP =BMC (iDRAC) IP
AMS server \Proxy
The IP address used by the AMS server
IP address
\proxy SW to manage the VxFlex OS
Nodes and logical entities
The formula to calculate IP address subnet pool or subnet needs is: N*Node_MGMT_IP
+N*SVM_MGMT_IP+N*BMC_MGMT_IP + Optional (AMS server IP address)
The VxFlex OS data IP network subnet requirements:
ESXi - 2 separate subnets
l
RHEL - 2 or 4 separate subnets
l
Note:
Each pool can belong to a single subnet or to several subnets, as long as the AMS
server has routable networking access to the management IP address.
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, in order to allow seamless detection and management IP
address configuration of the SVM and ESXi IP addresses of all nodes in the
system.
There are limitations in the VMware environment.
Multiple IP subnets
Multiple IP subnets used for the VxFlex OS data network cannot be on the same
subnet in a VMware setup.
For more information, see the VMware limitation in the following link:
Nodes' management IP addresses
storage VM management IP address
address for each node
Dell EMC VxFlex Ready Node AMS User Guide
Architecture
Comments
SVM IP addresses are
relevant for ESXi nodes, only.
Recommended to reside on
the same subnet, unless the
proxy is used for Discovery
operations
41