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

5. Virtual SAN software components<br />

This section aims to provide a brief overview of some of the Virtual SAN software<br />

components. Many of these components are not necessary to understand for day-today<br />

use of Virtual SAN. However when it comes to troubleshooting, you may see<br />

them referenced from time to time in logs, RVC commands and especially <strong>VSAN</strong><br />

Observer outputs. Therefore, for completeness sake, a brief overview is provided.<br />

Local Log Structured Object Management - LSOM<br />

LSOM works at the physical disk level, both flash devices and magnetic disks. It<br />

handles the physical storage for Virtual SAN components on the local disks of the<br />

ESXi hosts. It also handles the read caching and write buffering for the components.<br />

Distributed Object Manager - DOM<br />

DOM is responsible for the creation of virtual machine storage objects from local<br />

components across multiple ESXi hosts in the Virtual SAN cluster by implementing<br />

distributed RAID. It is also responsible for providing distributed data access paths to<br />

these objects. There are 3 roles within DOM; client, owner and component manager.<br />

<br />

<br />

<br />

Client: Provides access to an object. There may be multiple clients per object<br />

depending on access mode.<br />

Owner: Coordinates access to the object, including locking and object<br />

configuration and reconfiguration. There is a single DOM owner per object.<br />

All objects changes and writes go through the owner. Typically the client and<br />

owner will reside on the same host, but this is not guaranteed and they may<br />

reside on different hosts.<br />

Component Manager: Interface for LSOM and the physical disks.<br />

A node’s DOM may play any of the three roles for a single object<br />

Cluster Level Object Manager - CLOM<br />

CLOM ensures that an object has a configuration that matches its policy, i.e. stripe<br />

width or failures to tolerate, to meet the requirements of the virtual machine. Each<br />

ESXi host in a Virtual SAN cluster runs an instance of clomd, which is responsible for<br />

the policy compliance of the objects. CLOM can be thought of as being responsible<br />

for the placement of objects and their components.<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 / 51

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

Saved successfully!

Ooh no, something went wrong!