7.0

Table 2‑14. Custom Properties for vCloud Air and vCloud Director Machine Components in
the Blueprint Canvas (Continued)
Custom Property Description
VirtualMachine.NetworkN.Name
Specifies the name of the network to connect to, for example the
network device N to which a machine is attached. This is
equivalent to a network interface card (NIC).
By default, a network is assigned from the network paths
available on the reservation on which the machine is
provisioned. Also see
VirtualMachine.NetworkN.AddressType.
You can ensure that a network device is connected to a specific
network by setting the value of this property to the name of a
network on an available reservation. For example, If you give
properties for N= 0 and 1, you get 2 NICs and their assigned
value, provided the network is selected in the associated
reservation.
VirtualMachine.NetworkN custom properties are designed to
be specific to blueprints and machines. When a machine is
requested, network and IP address allocation is performed
before the machine is assigned to a reservation. Because
blueprints are not guaranteed to be allocated to a specific
reservation, do not use this property on a reservation.
You can add this property to a vCloud Air or vCloud Director
machine component in a blueprint.
For related information, see Custom Properties for Networking.
VirtualMachine.NetworkN.AddressType
Specifies how IP address allocation is supplied to the network
provider, where NetworkN is the network number, starting with 0.
The following value are available:
n
DHCP
n
Static
n
MANUAL (available for vCloud Air and vCloud Director only)
This property is available for configuring vCloud Air,
vCloud Director, and vSphere machine components in the
blueprint. Also see VirtualMachine.NetworkN.Name.
VirtualMachine.Reconfigure.DisableHotCpu
Set to true to specify that the reconfigure machine action
restarts the specified machine. By default, the reconfigure
machine action does not restart the machine.
Performing a hot add of CPU, memory, or storage causes the
reconfigure machine action to fail and to not restart the machine
unless the Hot Add setting is enabled in vSphere for the
machine or template. You can add
VirtualMachine.Reconfigure.DisableHotCpu=true to a
machine component in a vRealize Automation blueprint to
disable the Hot Add setting and force the machine to restart
regardless of the vSphere Hot Add setting. The custom property
is only available for machine types that support hardware
reconfiguration, which are vSphere, vCloud Air, and
vCloud Director.
Custom Properties Reference
VMware, Inc. 30