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
26 lines
1.3 KiB
ReStructuredText
26 lines
1.3 KiB
ReStructuredText
.. _int: https://docs.python.org/2/library/stdtypes.html
|
|
|
|
.. _str: https://docs.python.org/2/library/stdtypes.html
|
|
|
|
.. _vSphere API 5.0: ../../vim/version.rst#vimversionversion7
|
|
|
|
.. _vim.host.FibreChannelTargetTransport: ../../vim/host/FibreChannelTargetTransport.rst
|
|
|
|
|
|
vim.host.FibreChannelOverEthernetTargetTransport
|
|
================================================
|
|
Fibre Channel Over Ethernet transport information about a SCSI target. FCoE transport information is that of: the regular FC World Wide Node and Port Names; the VNPort MAC address and FCF MAC address which constitute a VN_Port to VF_Port Virtual Link; and the VLAN on which an FCoE target resides. More FCoE information can be found in the working draft of the T11's Fibre Channel Backbone 5 standard (FC-BB-5). The draft can be found at http://www.t11.org.
|
|
:extends: vim.host.FibreChannelTargetTransport_
|
|
:since: `vSphere API 5.0`_
|
|
|
|
Attributes:
|
|
vnportMac (`str`_):
|
|
|
|
VNPort MAC address. This MAC address should be of the form "xx:xx:xx:xx:xx:xx", where 'x' is a hexadecimal digit. Valid MAC addresses are unicast addresses.
|
|
fcfMac (`str`_):
|
|
|
|
FCF MAC address. This MAC address should be of the form "xx:xx:xx:xx:xx:xx", where 'x' is a hexadecimal digit. Valid MAC addresses are unicast addresses.
|
|
vlanId (`int`_):
|
|
|
|
VLAN ID. Valid VLAN IDs fall within the range [0,4094].
|