09.03.2015 Views

VSAN-Troubleshooting-Reference-Manual

VSAN-Troubleshooting-Reference-Manual

VSAN-Troubleshooting-Reference-Manual

SHOW MORE
SHOW LESS

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 />

peer-to-peer network state within Virtual SAN. Virtual SAN is sized such that it<br />

should never runs out of RDT associations. Here we can see that there are 45,000<br />

such associations available per host.<br />

Virtual SAN also limits how many TCP sockets it is allowed to use, and Virtual SAN is<br />

sized such that it should never runs out of its allocation of TCP sockets. As can be<br />

seen, there is a limit of 10,000 sockets per host.<br />

A Virtual SAN client represents object access in the Virtual SAN cluster. Most often<br />

than not, the client will typically represent a virtual machine running on a host. Note<br />

that the client and the object may not be on the same host. There is no hard defined<br />

limit, but this metric is shown to help understand how “clients” balance across<br />

hosts.<br />

There is always one and only one Virtual SAN owner for a given Virtual SAN object,<br />

typically co-located with the Virtual SAN client accessing this object. Virtual SAN<br />

owners coordinate all access to the Virtual SAN object and implement functionality<br />

like mirroring and striping. There is no hard defined limit, but this metric is once<br />

again shown to help understand how “owners” balance across hosts.<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 / 1 1 2

Hooray! Your file is uploaded and ready to be published.

Saved successfully!

Ooh no, something went wrong!