
This external documentation for pyVmomi was generated using Googly Docs (aka Google Standard Documentation) which renders very cleanly in GitHub. Internal documentation for a class should be done in Sphinx format because tools like pyCharm and Eclipse can use that documentation as a hint for code completion. Note: External docs as Googly Docs, internal docs as Sphinx. Closes bug#15
27 lines
1.5 KiB
ReStructuredText
27 lines
1.5 KiB
ReStructuredText
.. _str: https://docs.python.org/2/library/stdtypes.html
|
|
|
|
.. _vSphere API 4.1: ../../../vim/version.rst#vimversionversion6
|
|
|
|
.. _vmodl.DynamicData: ../../../vmodl/DynamicData.rst
|
|
|
|
|
|
vim.net.IpStackInfo.NetToMedia
|
|
==============================
|
|
Information from an IP stack about known mappings betwwen an IP address and the underlying physical address it maps to as learned by: IPv4: Address Resolution Protocol (ARP) RFC 826 IPv6: Neighbor Discovery Protocol (NDP) RFC 4861
|
|
:extends: vmodl.DynamicData_
|
|
:since: `vSphere API 4.1`_
|
|
|
|
Attributes:
|
|
ipAddress (`str`_):
|
|
|
|
A Unicast IP address of another system directly reachable w/o routing. IPv4 address is 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.
|
|
physicalAddress (`str`_):
|
|
|
|
The media-dependent of the address or empty string if not yet learned. For Ethernet interfaces this is a MAC address reported in the format: XX:XX:XX:XX:XX:XX where XX are hexadecimal numbers.
|
|
device (`str`_):
|
|
|
|
The value will be the name of the interface as reported by the operating system.
|
|
type (`str`_):
|
|
|
|
The type/state of this entry as reported by the IP stack. See EntryType for values.
|