7.2

Table Of Contents
Table 34. Available Network Types for a vRealize Automation Network Profile
Network Type Description
External Existing network 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.
You can use IP ranges obtained from the supplied VMware IPAM endpoint or from a third-party IPAM service
provider endpoint that you have registered and configured in vRealize Orchestrator, such as Infoblox IPAM. An
IP range is created from an IP block during allocation.
An external network profile with a static IP range is a prerequisite for NAT and routed networks.
See Create an External Network Profile By Using the Supplied IPAM Endpoint and Create an External Network
Profile by Using A Third-Party IPAM Provider.
NAT On-demand network created during provisioning. NAT 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.
See Create a NAT Network Profile for an On-Demand Network.
Routed On-demand network created during provisioning. Routed networks contain 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.
You can use IP ranges obtained from the supplied VMware IPAM endpoint or from a third-party IPAM service
provider endpoint that you have registered and configured in vRealize Orchestrator, such as Infoblox IPAM. An
IP range is created from an IP block during allocation.
A routed network profile defines a routable space and available subnets.
See Create a Routed Network Profile By Using the Supplied IPAM Endpoint.
Using Network Profiles to Control IP Address Ranges
You can use network profiles to assign static IP addresses from a predefined range to virtual machines
that are provisioned by cloning, by using Linux kickstart or autoYaST, or to cloud machines that are
provisioned in OpenStack by using kickstart.
By default, vRealize Automation uses Dynamic Host Configuration Protocol (DHCP) to assign IP
addresses to provisioned machines.
You can create network profiles to define a range of static IP addresses that you can assign to machines.
You can assign network profiles to specific network paths on a reservation. Machines that are provisioned
by cloning or by kickstart or autoYaST and are attached to a network path with an associated network
profile are provisioned with an assigned static IP address. For provisioning with a static IP address
assignment, you must use a customization specification.
Configuring vRealize Automation
VMware, Inc. 222