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

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 has inconsistent physical NIC speeds. It is recommended to only use physical NICs of same speed on a given vSwitch backing vSAN. 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
speedsMb | xsd:long[] | Bit rates (speed) of the links, in Mbit/s. This list only contains each present speed once. Links without any speed indication (e.g. links that are down) are not considered in the list. As there is an issue, there must be at least two members in this list.
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="VsanNetworkConfigPnicSpeedInconsistencyIssue"> <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="speedsMb" type="xsd:long" maxOccurs="unbounded"/> </sequence> </extension> </complexContent> </complexType>