VSAN-Troubleshooting-Reference-Manual
VSAN-Troubleshooting-Reference-Manual
VSAN-Troubleshooting-Reference-Manual
Create successful ePaper yourself
Turn your PDF publications into a flip-book with our unique Google optimized e-Paper software.
Diagnostics and <strong>Troubleshooting</strong> <strong>Reference</strong> <strong>Manual</strong> – Virtual SAN<br />
Introduction to Virtual SAN Networking<br />
Before getting into network in detail, it is important to understand the roles that<br />
nodes/hosts can play in Virtual SAN. There are three roles in Virtual SAN: master,<br />
agent and backup. There is one master that is responsible for getting CMMDS<br />
(clustering service) updates from all nodes, and distributing these updates to agents.<br />
Roles are applied during cluster discovery, when all nodes participating in Virtual<br />
SAN elect a master. A vSphere administrator has no control over roles.<br />
A backup node will assume the master role should the master fail. This will avoid a<br />
complete rediscovery of every node, object and component in the cluster, as the<br />
backup role will already have a full copy of the directory contents, and can<br />
seamlessly assume the role of master, speeding up recovery in the event of a master<br />
failure.<br />
There are a number of distinct parts to Virtual SAN networking. First there is the<br />
communication that takes place between all of the ESXi hosts in the Virtual SAN<br />
cluster, indicating that they are still actively participating in Virtual SAN. This is<br />
done via multicast traffic, and a heartbeat is sent from the master to all hosts once<br />
every second to ensure they are still active.<br />
There is also communication between the master and the backup and agent nodes,<br />
where the master keeps the other nodes up to date with regards to the configuration<br />
of the cluster. This is also multicast traffic, but is relatively light from a traffic<br />
volume perspective.<br />
Lastly, there is virtual machine disk I/O. This makes up the majority of the traffic on<br />
the Virtual SAN network. VMs on the Virtual SAN datastore are made up of a set of<br />
objects. These objects may be made up of one or more components, for example a<br />
number of RAID-1 stripes or a number of RAID-0 mirrors.<br />
Invariably, a VMs compute and a VM’s storage will be located on different ESXi hosts<br />
in the cluster. It may also transpire that if a VM has been configured to tolerate one<br />
or more failures, the compute may be on node 1, the first RAID-0 mirror may be on<br />
host 2 and the second RAID-0 mirror could be on host 3. In this case, disk reads and<br />
writes for this virtual machine will have to traverse the Virtual SAN network. This is<br />
unicast traffic, and forms the bulk of the Virtual SAN network traffic.<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 / 96