You can use network profiles to specify network settings in reservations, relative to a network path. With some machine types, you can specify a network profile when you work with blueprints in the design canvas.

You specify an external network profile when you create reservations and blueprints.

If a network profile is specified in the blueprint (by using the VirtualMAchine.NetworkN.ProfileName custom property) and by a reservation that is used by the blueprint, the network profile specified in the blueprint takes precedence. However, if the custom property is not used in the blueprint, and you select a network profile for a machine NIC, vRealize Automation uses a reservation network path for the machine NIC for which the network profile is specified.

Network profiles are used to configure network settings when machines are provisioned, and to specify the configuration of NSX Edge devices that are created when you provision machines. In a reservation, you can assign a network profile to a network path and specify any one of those paths for a machine component in a blueprint.

You can create a network profile to define a type of available network, including external network profiles and templates for network address translation (NAT) and routed network profiles that will build NSX logical switches and appropriate routing settings for a new network path to be used by provisioned machine as assigned in blueprint.

You can specify the ranges of IP addresses that network profiles can use. Each IP address in the specified ranges that are allocated to a machine is reclaimed for reassignment when the machine is destroyed.

A blueprint creator specifies NAT, external, and routed network profiles in blueprints for use in configuring network adapters and load balancers for the provisioning machine.

Table 1. Available Network Types for a vRealize Automation Network Profile

Network Type



Existing physical or logical networks configured on the vSphere server. They are the external part of the NAT and routed networks types. An external network profile can define a range of static IP addresses available on the external network. An external network profile with a static IP range is a prerequisite for NAT and routed networks.


Created during provisioning. They are networks that use one set of IP addresses for external communication and another set for internal communications. With one-to-one NAT networks, every virtual machine is assigned an external IP address from the external network profile and an internal IP address from the NAT network profile. With one-to-many NAT networks, all machines share a single IP address from the external network profile for external communication. A NAT network profile defines local and external networks that use a translation table for mutual communication.


Created during provisioning. They represent a routable IP space divided across subnets that are linked together using Distributed Logical Router (DLR). Every new routed network has the next available subnet assigned to it and is associated with other routed networks that use the same network profile. The virtual machines that are provisioned with routed networks that have the same routed network profile can communicate with each other and the external network. A routed network profile defines a routable space and available subnets. For more information about Distributed Logical Router, see NSX Administration Guide.

vRealize Automation uses vSphere DHCP to assign IP addresses to the machines it provisions, regardless of which provisioning method is used. When provisioning virtual machines by cloning (with a customization specified) or by using kickstart/autoYaST provisioning, the requesting machine owner can assign static IP addresses from a predetermined range.