The physical connections between the ports on your network switches and the NICs on the VxRail nodes enable communications for the virtual infrastructure within the VxRail cluster.
The virtual infrastructure within the VxRail cluster uses the VMware VDS to enable communication within the cluster, and out to IT management and the application user community.
VxRail has predefined logical networks to manage and control traffic within and outside of the cluster. Make VxRail logical networks accessible to the outside community. For instance, connectivity to the VxRail management system is required by IT management. VxRail networks must be configured for end-users and application owners who need to access their applications and virtual machines running in the VxRail cluster.
A network to support I/O to the VMware vSAN datastore is required unless you plan to use FC storage as the primary storage resource with a dynamic cluster. Configure a network to support VMware vSphere vMotion, which is used to dynamically migrate virtual machines between VxRail nodes to balance workload. You also need an internal management network by VxRail for device discovery. You can skip the internal management network if you plan to use manual device discovery. All PowerEdge servers that serve as the foundation for VxRail nodes include a separate Ethernet port that enables OOB connectivity to the platform to perform hardware-based maintenance and troubleshooting tasks.
A separate network to support management access to the PowerEdge servers is recommended, but not required.