IP addresses must be assigned to the VxRail external management network, vSAN network, vMotion network, and any guest networks you want to configure on the VxRail cluster. Decisions must be made on the IP address ranges reserved for each VxRail network.
Figure 41. Overview of VxRail Core Network IP Requirements
- The internal management network that is used for device discovery does not require assigned IP addresses.
- Since the external management network must be able to route upstream to network services and end users, a non-private, routable IP address range must be assigned to this network.
- The options for VxRail cluster primary storage require either Fibre Channel or Ethernet for vSAN. For a vSAN network, you can reserve a routable or non-routable (private) IP address range:
- If your plans include a multirack cluster, and you want to use a new IP subnet range in the expansion racks, reserve a routable IP address range.
- If you plan to configure the cluster into a vSAN HCI mesh topology to share vSAN storage resources, reserve a routable IP address range.
- If you are planning a standard cluster only with a local vSAN datastore, a non-routable IP address range is acceptable. In this case, traffic is passed only between the VxRail nodes that form the cluster.
- If you plan to configure a dynamic cluster to use external FC-based storage as primary storage, there is no need to reserve an IP address range.
- If your requirements for virtual machine mobility are within the VxRail cluster, a non-routable IP address range can be assigned to the vMotion network. However, if you need to enable virtual machine mobility outside of the VxRail cluster, or have plans for a multirack expansion that will use a different subnet range on any expansion racks, reserve a routable IP address range.