# Data Object - VsanFileServiceConfig(vim.vsan.FileServiceConfig)

Property of
  VimVsanReconfigSpec, VsanConfigInfoEx
Extends
  DynamicData
See also
  Network, VsanFileServiceDomainConfig
Since
  vSAN API 7.0

## Data Object Description

The file service configuration for a vSAN cluster, including whether file service is enabled or not, the memory and CPU configuration for file service backend part and virtual machine, etc.

Properties

Name | Type | Description
--- | --- | ---
domains* | VsanFileServiceDomainConfig[] | The list of domains created. The first element of this list is the default domain. Leave this field empty when there is no domain to be configured with the file service enable process.
enabled | xsd:boolean | Indicates whether file service is enabled in the vSAN cluster.
fileAnalyticsEnabled* | xsd:boolean | Indicates whether file analytics is enabled in the vSAN cluster. Since vSAN API 8.0.0.3
fileServerCPUMhz* | xsd:long | The reserved CPU used by VDFS backend services, like server, proxy and sockrelay. The units is MHZ. The default value is 0, which means no dedicated CPU resources is bound. This reconfiguration takes effect during enabling file service. That means, file service should be disabled first if it is running.
fileServerMemoryMB* | xsd:long | The reserved memory used by VDFS backend services, like server, proxy and sockrelay. The unit is MB. The default and minimum value is 960. This reconfiguration takes effect during enabling file service. That means, file service should be disabled firstly if it is running.
fsvmCPU* | xsd:long | CPU cores configured for vSAN File Service Virtual Machine(by default is 2). This reconfiguration takes effect during enabling file service. That means, file service should be disabled first if it is running.
fsvmMemoryMB* | xsd:long | The reserved memory used by vSAN file service virtual machines. The unit is MB. The default and minimum values is 2048. This reconfiguration takes effect during enabling file service. That means, file service should be disabled first if it is running.
network* | ManagedObjectReference to a Network | The network that the file service will be deployed on to provide file access. Please note the security setting of this network will be updated with forged transmit and promiscuous mode enabled.
Properties inherited from DynamicData
None

*Need not be set
Show WSDL type definition
<complexType xmlns="http://www.w3.org/2001/XMLSchema" xmlns:vsan="urn:vsan" name="VsanFileServiceConfig"> <complexContent> <extension base="vsan:DynamicData"> <sequence> <element name="enabled" type="xsd:boolean"/> <element name="fileServerMemoryMB" type="xsd:long" minOccurs="0"/> <element name="fileServerCPUMhz" type="xsd:long" minOccurs="0"/> <element name="fsvmMemoryMB" type="xsd:long" minOccurs="0"/> <element name="fsvmCPU" type="xsd:long" minOccurs="0"/> <element name="network" type="vsan:ManagedObjectReference" minOccurs="0"/> <element name="domains" type="vsan:VsanFileServiceDomainConfig" minOccurs="0" maxOccurs="unbounded"/> <element name="fileAnalyticsEnabled" type="xsd:boolean" minOccurs="0"/> </sequence> </extension> </complexContent> </complexType>