Virtual SAN requires correctly configured network interfaces.

The hosts in your Virtual SAN cluster must be part of a Virtual SAN network and must be on the same subnet. On each host, configure at least one Virtual SAN interface. You must configure this interface on all host in the cluster, no matter whether the hosts contribute storage or not.

Note:

Virtual SAN does not support IPv6.

Follow these guidelines:

  • Virtual SAN requires a private 1Gb network. As a best practice, use 10Gb network.

  • On each host, dedicate at minimum a single physical 1Gb Ethernet NIC to Virtual SAN. You can also provision one additional physical NIC as a failover NIC.

  • You can use vSphere standard switches on each host, or you can configure your environment with a vSphere Distributed Switch.

  • For each network that you use for Virtual SAN, configure a VMkernel port group with the Virtual SAN port property activated.

  • Use the same Virtual SAN Network label for each port group and ensure that the labels are consistent across all hosts.

  • Use Jumbo Frames for best performance.

  • Virtual SAN supports IP-hash load balancing, but cannot guarantee improvement in performance for all configurations. You can benefit from IP-hash when Virtual SAN is among its many consumers. In this case, IP-hash performs the load balancing. However, if Virtual SAN is the only consumer, you might not notice changes. This specifically applies to 1G environments. For example, if you use four 1G physical adapters with IP-hash for Virtual SAN, you might not be able to use more than 1G. This also applies to all NIC teaming policies that we currently support. For more information on NIC teaming, see the Networking Policies section of the vSphere Networking Guide.

  • Virtual SAN does not support multiple VMkernel adapters on the same subnet for load balancing. Multiple VMkernel adapters on different networks, such as VLAN or separate physical fabric, are supported.

  • You should connect all hosts participating in Virtual SAN to a single L2 network, which has multicast (IGMP snooping) enabled. If the hosts participating in Virtual SAN span across multiple switches or even across L3 boundaries, you must ensure that your network is configured correctly to enable multicast connectivity. You can change multicast addresses from the defaults if your network environment requires, or if you are running multiple Virtual SAN clusters on the same L2 network.

For more information, see the vSphere Networking documentation.