Data Object - VsanNetworkConfigVswitchWithNoRedundancyIssue(vim.vsan.VsanNetworkConfigVswitchWithNoRedundancyIssue)

Extends: VsanNetworkConfigBaseIssue
See also: DistributedVirtualSwitch, HostSystem
Since: vSAN API 6.6

Data Object Description

Configuration issue: vSAN is using a vmknic on a vSwitch which doesn't have any physical NIC redundancy. This means in case of a physical NIC failure vSAN would not be able to use the vmknic any more to communicate with the remaining cluster. Note that physical NIC redundancy 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
numPnics	xsd:long	Number of configured physical NICs.
vds*	ManagedObjectReference to a DistributedVirtualSwitch	The Virtual Distributed Switch, if in-use.
vswitchName*	xsd:string	Standard virtual switch name, in case of VMware Standard Switch (VSS).
Properties inherited from VsanNetworkConfigBaseIssue
None
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="VsanNetworkConfigVswitchWithNoRedundancyIssue">
            <complexContent>
               <extension base="vsan:VsanNetworkConfigBaseIssue">
                  <sequence>
                     <element name="host" type="vsan:ManagedObjectReference"/>
                     <element name="vswitchName" type="xsd:string" minOccurs="0"/>
                     <element name="vds" type="vsan:ManagedObjectReference" minOccurs="0"/>
                     <element name="numPnics" type="xsd:long"/>
                  </sequence>
               </extension>
            </complexContent>
         </complexType>