7.1
Table Of Contents
- Custom Properties Reference
- Contents
- Custom Properties Reference
- Updated Information
- Using Custom Properties
- Custom Properties Grouped by Function
- Custom Properties for Blueprints and Deployments
- Custom Properties for Naming and Analyzing Deployments
- Custom Properties for Openstack Endpoints
- Custom Properties for Clone Blueprints
- Custom Properties for Linked Clone Blueprints
- Custom Properties for FlexClone Blueprints
- Custom Properties for Basic Workflow Blueprints
- Custom Properties for Linux Kickstart Blueprints
- Custom Properties for SCCM Blueprints
- Custom Properties for WIM Blueprints
- Custom Properties for vCloud Air and vCloud Director Blueprints
- Custom Properties for Networking
- Custom Properties for PXE Provisioning
- Custom Properties for vRealize Automation Guest Agent
- Custom Properties for BMC BladeLogic Configuration Manager Integration
- Custom Properties for HP Server Automation Integration
- Custom Properties Grouped by Name
- Custom Properties Underscore (_) Table
- 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
- Using Property Definitions
- Using Property Groups
- Index
Table 3‑14. Custom Properties V Table (Continued)
Property Description
VirtualMachine.NetworkN.ProfileName
Species the name of a network prole from which
to assign a static IP address to network device N or
from which to obtain the range of static IP addresses
that can be assigned to network device N of a cloned
machine, where N=0 for the rst device, 1 for the
second, and so on.
When you use the
VirtualMachine.NetworkN.ProfileName
property, the network prole it points to is used to
allocate an IP address. However, the provisioned
machine is aached to any network that is selected in
the reservation using a round-robin fashion model.
Changing this property value after the network is
assigned has no eect on the expected IP address
values for the designated machines.
With WIM-based provisioning for virtual machines,
you can use this property to specify a network
prole and network interface or you can use the
Network section of the Virtual Reservation page. You
can also assign the network interface to a virtual
network using the
VirtualMachine.NetworkN.Name custom property.
The following aributes of the network prole are
available to enable static IP assignment in a cloning
blueprint:
n
VirtualMachine.NetworkN.SubnetMask
n
VirtualMachine.NetworkN.Gateway
n
VirtualMachine.NetworkN.PrimaryDns
n
VirtualMachine.NetworkN.SecondaryDns
n
VirtualMachine.NetworkN.PrimaryWins
n
VirtualMachine.NetworkN.SecondaryWins
n
VirtualMachine.NetworkN.DnsSuffix
n
VirtualMachine.NetworkN.DnsSearchSuffix
es
VirtualMachine.NetworkN custom properties are
specic 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 specic
reservation, do not use this property on a
reservation.
You cannot use this custom property to dene an on-
demand NAT or on-demand routed network prole
name. Because on-demand network prole names
are generated at allocation time (during
provisioning), their names are unknown when
creating or editing the blueprint. To specify NSX on-
demand network information, use the applicable
network component in the blueprint design canvas
for your vSphere machine components.
Custom Properties Reference
74 VMware, Inc.