VMware vSAN Network Considerations

Intro

VMware vSAN is a Hyperconverged Infrastructure Solution from VMware. It basically turns your servers direct attached disks into a storage cluster.

General Requirements

  • 10 GbE network switches are the minimum requirement for all-flash vSAN Clusters
  • 25 GBE network switches are recommended
  • Switches that support higher port speeds are designed with higher Network Processor Unit (NPU) buffers. An NPU shared switch buffer of at least 16 MB is recommended for 10 GbE network connectivity. An NPU buffer of at least 32 MB is recommended for more demanding 25 GbE network connectivity.

With vSAN ESA 25GbE is a must. (In ESA-AF-0 vSAN Ready Nodes the network bandwidth has been mentioned as 10 GbE - so probalby 10GbE will work for smaller ESA Deployments)

General Considerations

  • Use a dedicated VLAN on the Physical Network Switches for vSAN Traffic. If possible use Quality of Service Features to priorize vSAN traffic.
  • Use two physical Uplinks for vSAN Traffic, do not mix with VM Workload traffic.
  • Use a dedicated virtual Distributed Switch for vSphere Backend Services (vSAN, vMotion, FT)
  • Use Network I/O Control

vSAN over RoCE

With vSphere 7.0 U2 vSAN with RDMA is supported. RDMA typically has lower CPU utilization and less I/O latency.

If your vSAN cluster will include adapters that support RoCE (RDMA over Converged Ethernet) for vSAN storage connectivity, the supporting network must support a “lossless” transport. A “lossless” network is defined as one where no frames are dropped because of network congestion.

  • Select switches that support Data Center Bridging (DCB). The Data Center Bridging feature supports the elimination of packet loss due to buffer or queue overflow.
  • The Data Center Bridging must support bandwidth allocation based on priority settings, known as Class of Service (CoS).
  • Priority Flow Control (PFC) is required on the switches to provide RoCE traffic a higher priority than other network traffic.

All the nodes in the cluster connected to the common vSAN datastore must be configured with RoCE-supported adapter cards of the same vendor and the same model. This is strongly encouraged as a best practice to remove any possibility of slight variances in adapters from different vendors or different models disrupting I/O on the vSAN datastore.

  • The Ethernet ports on the RoCE-supported adapters are reserved for vSAN traffic only.
  • The physical network supporting vSAN is configured as a “lossless” network. Look for RoCEv2 support with your Network Switch Vendor.

Supported RDMA Network adapters can be found here:

https://www.vmware.com/resources/compatibility/search.php?deviceCategory=rdmanic&details=1&vsan_type=rdmanic&page=1&display_interval=10&sortColumn=Partner&sortOrder=Asc