The management configuration of the port.
Whether the port is a conflict port. A port could be marked as conflict
if an entity is discovered connecting to a port that is already
occupied, or if the port is created by the host without conferring
with Virtual Center Server. A conflict port will not have its runtime
state persisted and the port can't move away from the host, i.e no
vMotion if a Virtual Machine is using a conflict port.
If the port is marked conflict in the case of two entities connecting to
the same port (see
conflict), this is the
key of the port which the connected entity is contending for.
The entity that connects to the port.
This is a cookie represents the current instance of association between
port and vnic/pnic (which is represented as DistributedVirtualSwitchPortConnection
objects). The same cookie is present on the pnic/vnic configuration (see
connectionCookie)in order for the port to
authenticate that the peer is the rightfull connectee of the port.
The UUID of DistributedVirtualSwitch that the port belongs to.
The port key.
The last time the State#runtimeInfo value was changed.
The key of the portgroup that the port belongs to, if any.
The host that services this port
The runtime state of the port.
Properties inherited from DynamicData