7.0

Table Of Contents
Table 217. Custom Properties for Networking Configuration (Continued)
Custom Property Description
VirtualMachine.NetworkN.ProfileName
Specifies the name of a network profile 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 first device, 1
for the second, and so on.
If a network profile is specified in the network path in the
reservation on which the machine is provisioned, a static IP
address is assigned from that network profile. You can ensure
that a static IP address is assigned from a specific profile by
setting the value of this property to the name of a network
profile.
Note that changing this property value after the network is
assigned has no effect 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 profile 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 attributes of the network profile 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.DnsSearchSuffixes
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.
You cannot use this custom property to define an on-demand
NAT or on-demand routed network profile name. Because on-
demand network profile 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
VMware, Inc. 38