7.1

7 (Optional) For an on-demand NAT network component, click the DCHP tab to specify IP address range
and lease length values.
You can edit the start and end IP address values for the DCHP range. When the virtual machine is
provisioned with DCHP, the network adapter assigns an IP address to the machine that is within this
range. It is a static network adapter by default. The IP address values cannot be those of the network or
broadcast addresses used in the associated subnet. You cannot overlap static IP ranges.
DHCP is available only for on-demand one-to-many NAT network components.
8 (Optional) Enter a start IP address value in the IP range start text box.
9 (Optional) Enter an end IP address value in the IP range end text box.
10 Enter a DCHP lease length, in seconds, in the Lease time (seconds) text box or leave blank for an
unlimited lease length.
11 (Optional) Click the IP Ranges tab.
The IP range or ranges specied in the network prole are displayed. You can change the sort order or
column display. For NAT networks, you can also change IP range values.
12 Click Finish to save the blueprint as draft or continue conguring the blueprint.
What to do next
You can continue conguring network seings by adding additional network components and by selecting
seings in the Network tab of a vSphere machine component in the blueprint canvas.
Using Load Balancer Components in the Blueprint Canvas
You can add one or more on-demand NSX load balancer components to the design canvas to congure
vSphere machine component seings in the blueprint.
The network and security component seings that you add to the blueprint design canvas are derived from
your NSX conguration and require that you have installed the NSX plug-in and run data collection for the
NSX inventory for vSphere clusters. Network and security components are specic to NSX and are available
for use with vSphere machine components only. For information about conguring NSX, see NSX
Administration Guide.
The following rules apply to load balancer pools and VIP network seings in the blueprint:
n
If the pool network prole is NAT, the VIP network prole can be the same NAT network prole in the
same NAT network prole.
n
If the pool network prole is routed, the VIP network prole can only be on the same routed network.
n
If the pool network prole is external, the VIP network prole can only be the same external network
prole.
An NSX Edge resource is also created and load balancer details such as VIP, load-balanced tier, and
congured services are recorded as properties of the Edge resource.
Add an On-Demand Load Balancer Component
You can use an on-demand load balancer component to add an NSX load balancer to the design canvas and
congure its seings for use with vSphere machine components and Software or XaaS components that
pertain to vSphere.
The load balancer seings distribute task processing among provisioned machines in a network.
For related information about creating NSX application proles to dene the behavior of a particular type of
network trac, see the NSX Administration Guide.
Configuring vRealize Automation
288 VMware, Inc.