VSAN-Troubleshooting-Reference-Manual
VSAN-Troubleshooting-Reference-Manual
VSAN-Troubleshooting-Reference-Manual
You also want an ePaper? Increase the reach of your titles
YUMPU automatically turns print PDFs into web optimized ePapers that Google loves.
Diagnostics and <strong>Troubleshooting</strong> <strong>Reference</strong> <strong>Manual</strong> – Virtual SAN<br />
MTU & jumbo frames<br />
Virtual SAN fully supports the use of jumbo frames, though it is not thought to<br />
improve Virtual SAN network performance to any great extent. However recent<br />
performance tests using Virtual SAN for VDI suggests that the use of jumbo frames<br />
does assist with reduced CPU utilization. If jumbo frames is required, ensure that<br />
the VMkernel interfaces and the virtual switches to which they connect are<br />
configured to handle this new size. The physical switches to which the physical NICs<br />
are connected also need to be configured appropriately.<br />
A good test to verify that the hosts are able to communicate to each other over this<br />
network with jumbo frames is to use the vmkping command but with the –s 9000<br />
option (for the larger packet size) and have each of the hosts in the cluster ping each<br />
other. Needless to say that if doesn’t work, no attempt should be made to enable<br />
Virtual SAN until the network is configured correctly for jumbo frames.<br />
Multicast traffic requirement<br />
As stated in the introduction, multicast traffic is used for certain Virtual SAN cluster<br />
functions. It is imperative that the Virtual SAN network facilitates multicast traffic<br />
across all hosts participating in the Virtual SAN cluster. In version 5.5, this must be<br />
over a layer-2 network. In 6.0, VMware supports multicast traffic routed over a<br />
layer-3 network.<br />
Virtual SAN uses a clustered metadata database and monitoring service (CMMDS) to<br />
make particular metadata available to each host in the cluster. The CMMDS is<br />
designed to be a highly available, performant and network efficient service that<br />
shares information regarding host, network, disks, objects, components, etc. among<br />
all of the hosts within the Virtual SAN cluster.<br />
This distribution of metadata amongst all of the ESXi hosts in the cluster, and<br />
keeping each host synchronized, could potentially consume a considerable amount<br />
of compute resources and network bandwidth. Each ESXi host is intended to contain<br />
an identical copy of this metadata which means that if general unicast forwarding<br />
was used for this traffic, there would be duplicate traffic sent to all of the ESXi hosts<br />
in the cluster.<br />
Virtual SAN leverages multicast forwarding for the discovery of hosts and to<br />
optimize network bandwidth consumption for the metadata updates from the<br />
CMMDS service. This eliminates the computing resource and network bandwidth<br />
penalties that unicast would impose in order to send identical data to multiple<br />
recipients.<br />
V M W A R E S T O R A G E B U D O C U M E N T A T I O N / 98