6.2
Table Of Contents
- Custom Properties Reference
- Contents
- Custom Properties Reference
- Updated Information
- Using Custom Properties
- Custom Properties Grouped by Function
- Custom Properties for Openstack Endpoints
- Custom Properties for Basic Workflow Blueprints
- Custom Properties for Clone Blueprints
- Custom Properties for FlexClone Blueprints
- Custom Properties for Linked Clone Blueprints
- Custom Properties for Linux Kickstart Blueprints
- Custom Properties for SCCM Blueprints
- Custom Properties for WIM Blueprints
- Custom Properties for vApp Blueprints
- Custom Properties for vRealize Automation Guest Agent
- Custom Properties for Networking
- Custom Properties for PXE Provisioning
- Custom Properties for BMC BladeLogic Configuration Manager Integration
- Custom Properties for HP Server Automation Integration
- Custom Properties Grouped by Name
- Custom Properties A Table
- Custom Properties B Table
- Custom Properties C Table
- Custom Properties E Table
- Custom Properties H Table
- Custom Properties I Table
- Custom Properties L Table
- Custom Properties M Table
- Custom Properties O Table
- Custom Properties P Table
- Custom Properties R Table
- Custom Properties S Table
- Custom Properties V Table
- Custom Properties X Table
- Using the Property Dictionary
Network assignments are performed during machine allocation. vRealize Automation retrieves network
information from the blueprint. If you want to assign more than one network, use the
VirtualMachine.NetworkN.Name custom property on your machine blueprint. If you do not provide
custom properties, allocation only assigns one network, which is picked using a round robin method in
conjunction with the selected reservation.
By default, a machine has one network device configured with the VirtualMachine.Network0.Name
property. You can configure additional network devices by using the VirtualMachine.NetworkN.Name
custom property.
The numbering of network properties must be sequential, starting with 0. For example, if you specify
custom properties for only VirtualMachine.Network0 and VirtualMachine.Network2, the properties
for VirtualMachine.Network2 are ignored, because the preceding network,
VirtualMachine.Network1, was not specified.
Table 2‑17. Custom Properties for Networking Configuration
Custom Property Description
VirtualMachine.NetworkN.Address Specifies the IP address of network device N in a machine
provisioned with a static IP address.
VirtualMachine.NetworkN.MacAddressType Indicates whether the MAC address of network device N is
generated or user-defined (static). This property is available for
cloning.
The default value is generated. If the value is static, you must
also use VirtualMachine.NetworkN.MacAddress to specify
the MAC address.
VirtualMachine.NetworkN custom properties are designed to
be specific to individual 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.
VirtualMachine.NetworkN.MacAddress Specifies the MAC address of a network device N. This property
is available for cloning.
If the value of VirtualMachine.NetworkN.MacAddressType is
generated, this property contains the generated address.
If the value of VirtualMachine.Network.N.MacAddressType
is static, this property specifies the MAC address. For virtual
machines provisioned on ESX server hosts, the address must
be in the range specified by VMware. For details, see vSphere
documentation.
VirtualMachine.NetworkN custom properties are designed to
be specific to individual 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.
Custom Properties Reference
VMware, Inc. 40