# Data Object - VsanNetworkConfigVsanNotOnVdsIssue(vim.vsan.VsanNetworkConfigVsanNotOnVdsIssue)

Extends
  VsanNetworkConfigBaseIssue
See also
  HostSystem
Since
  vSAN API 6.6

## Data Object Description

Configuration issue: vSAN is using a vmknic which is not on a vDS. This is a best practice, not a functional/support requirement.

Properties

Name | Type | Description
--- | --- | ---
host | ManagedObjectReference to a HostSystem | The Host on which the vmknic exists
vmknic | xsd:string | vmknic device name.
Properties inherited from VsanNetworkConfigBaseIssue
None
Properties inherited from DynamicData
None

Show WSDL type definition
<complexType xmlns="http://www.w3.org/2001/XMLSchema" xmlns:vsan="urn:vsan" name="VsanNetworkConfigVsanNotOnVdsIssue"> <complexContent> <extension base="vsan:VsanNetworkConfigBaseIssue"> <sequence> <element name="host" type="vsan:ManagedObjectReference"/> <element name="vmknic" type="xsd:string"/> </sequence> </extension> </complexContent> </complexType>