# Data Object - HostNetCapabilities(vim.host.NetCapabilities)

Property of
  HostConfigInfo, HostNetworkSystem
Extends
  DynamicData

## Data Object Description

Capability vector indicating the available product features.

Properties

Name | Type | Description
--- | --- | ---
canSetPhysicalNicLinkSpeed | xsd:boolean | The flag to indicate whether or not a physical network adapter's link speed and duplex settings can be changed through this API. For a hosted product, the host uses its physical network adapters for network connectivity. Configuration of link speed is done through regular host operations. In ESX Server, the configuration can be changed through this API.
dhcpOnVnicSupported | xsd:boolean | This flag indicates whether or not the host is able to support dhcp configuration for vnics. Since VI API 2.5
dnsConfigSupported | xsd:boolean | The flag to indicate whether DNS configuration for the host is supported. Since VI API 2.5
ipRouteConfigSupported | xsd:boolean | The flag to indicate whether ip route configuration for the host is supported. Since VI API 2.5
ipV6Supported | xsd:boolean | The flag to indicate whether the host is capable of communicating using ipv6 protocol Since vSphere API 4.0
maxPortGroupsPerVswitch* | xsd:int | The maximum number of port groups supported per virtual switch. This property will not be set if this value is unlimited. Since VI API 2.5
nicTeamingPolicy* | xsd:string[] | The available teaming policies if the platform supports network adapter teaming.
supportsNetworkHints | xsd:boolean | The flag to indicate whether or not the host is able to support the querying of network hints.
supportsNicTeaming | xsd:boolean | The flag to indicate whether or not network adapter teaming is available. Multiple network adapters can be bridged to a virtual switch through a BondBridge. Also, network adapter teaming policies such as failover order and detection are enabled.
supportsVlan | xsd:boolean | The flag to indicate whether or not VLANs can be configured on PortGroups attached to VirtualSwitch objects. This allows VLANs for virtual machines without requiring special VLAN capable hardware switches.
usesServiceConsoleNic | xsd:boolean | The flag to indicate whether or not a service console network adapter is used or required. This means that the system software has two TCP/IP stacks. As a result, at least two types of VirtualNics may be created -- the normal VirtualNic and the service console VirtualNic. If this is not set, then only the VirtualNic type is supported.
vnicConfigSupported | xsd:boolean | The flag to indicate whether Virtual NIC configuration is supported. This means that operations to add, remove, update virtualNic are supported. Since VI API 2.5
vswitchConfigSupported | xsd:boolean | The flag to indicate whether virtual switch configuration is supported. This means that operations to add, remove, update virtual switches are supported. Since VI API 2.5
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="HostNetCapabilities"> <complexContent> <extension base="vsan:DynamicData"> <sequence> <element name="canSetPhysicalNicLinkSpeed" type="xsd:boolean"/> <element name="supportsNicTeaming" type="xsd:boolean"/> <element name="nicTeamingPolicy" type="xsd:string" minOccurs="0" maxOccurs="unbounded"/> <element name="supportsVlan" type="xsd:boolean"/> <element name="usesServiceConsoleNic" type="xsd:boolean"/> <element name="supportsNetworkHints" type="xsd:boolean"/> <element name="maxPortGroupsPerVswitch" type="xsd:int" minOccurs="0"/> <element name="vswitchConfigSupported" type="xsd:boolean" minOccurs="0"/> <element name="vnicConfigSupported" type="xsd:boolean" minOccurs="0"/> <element name="ipRouteConfigSupported" type="xsd:boolean" minOccurs="0"/> <element name="dnsConfigSupported" type="xsd:boolean" minOccurs="0"/> <element name="dhcpOnVnicSupported" type="xsd:boolean" minOccurs="0"/> <element name="ipV6Supported" type="xsd:boolean" minOccurs="0"/> </sequence> </extension> </complexContent> </complexType>