Host Network System Get Network Info
The network configuration and runtime information.
The unique identifier for the managed object to which the property attaches; the serialized managed object reference for a request has the form moType/moId, in this case HostNetworkSystem/{moId}.
The vSphere release schema. The current specification covers vSphere 8.0.2.0 APIs.
OK
"HostNetworkInfo Object"Virtual switches configured on the host.
Proxy switches configured on the host.
Port groups configured on the host.
Physical network adapters as seen by the primary operating system.
Remote direct memory access devices, if any are present on the host.
Virtual network adapters configured on the host (hosted products) or the vmkernel.
In the hosted architecture, these network adapters are used by the host to communicate with the virtual machines running on that host. In the VMkernel architecture, these virtual network adapters provide the ESX Server with external network access through a virtual switch that is bridged to a physical network adapter. The VMkernel uses these network adapters for features such as VMotion, NAS, iSCSI, and remote MKS connections.
Virtual network adapters configured for use by the service console.
The service console uses this network access for system management and bootstrapping services like network boot. The two sets of virtual network adapters are mutually exclusive. A virtual network adapter in this list cannot be used for things like VMotion. Likewise, a virtual network adapter in the other list cannot be used by the service console.
This data object type describes the DNS configuration.
All IPv4 addresses, subnet addresses, and netmasks are specified using dotted decimal notation. For example, "192.0.2.1". IPv6 addresses are 128-bit addresses represented as eight fields of up to four hexadecimal digits. A colon separates each field (:). For example, 2001:DB8:101::230:6eff:fe04:d9ff. The address can also consist of the symbol '::' to represent multiple 16-bit groups of contiguous 0's only once in an address as described in RFC 2373.
IP Route Configuration.
All IPv4 addresses, subnet addresses, and netmasks are specified as strings using dotted decimal notation. For example, "192.0.2.1". IPv6 addresses are 128-bit addresses represented as eight fields of up to four hexadecimal digits. A colon separates each field (:). For example, 2001:DB8:101::230:6eff:fe04:d9ff. The address can also consist of symbol '::' to represent multiple 16-bit groups of contiguous 0's only once in an address as described in RFC 2373.
IP Route Configuration.
All IPv4 addresses, subnet addresses, and netmasks are specified as strings using dotted decimal notation. For example, "192.0.2.1". IPv6 addresses are 128-bit addresses represented as eight fields of up to four hexadecimal digits. A colon separates each field (:). For example, 2001:DB8:101::230:6eff:fe04:d9ff. The address can also consist of symbol '::' to represent multiple 16-bit groups of contiguous 0's only once in an address as described in RFC 2373.
IpRouteTableInfo.
This is the list of all static routes on the host
DHCP Service instances configured on the host.
NAT service instances configured on the host.
Enable or disable IPv6 protocol on this system.
If true then dual IPv4/IPv6 stack enabled else IPv4 only.
List of NetStackInstances
List of opaque switches configured on the host.
List of opaque networks
The nsx transport node Id
Whether NSX N-VDS to VDS migration is required
Since: vSphere API Release 7.0.2.0
Current status of NVDS to VDS migration.
See HostNetworkConfig.HostNetworkConfigMigrationStatusEnum for supported values.
Since: vSphere API Release 7.0.2.0
curl -H 'Authorization: <value>' https://{api_host}/sdk/vim25/{release}/HostNetworkSystem/{moId}/networkInfo