7.3

n
NSX Load Balancer Component
You can create NAT rules for a NAT one-to many network component that is associated to the VIP
network of an NSX load balancer component.
For example, if the NAT network component is associated to a load balancer component that is load
balancing three machines, you can define a NAT rule that allows port 90 on the external IP to connect
to the load balancer VIP through port 80 on the NAT network using UDP protocol.
You can create any number of NAT rules and you can control the order in which the rules are processed.
The following elements are not supported for NAT rules:
n
NICs that are not in the current network
n
NICs that are configured to get IP addresses by using DHCP
n
Machine clusters
To add NAT rules to a NAT network component in a blueprint, see Add an On-Demand NAT or On-
Demand Routed Network Component.
For related information about using NAT rules, see public articles such as this vmwarelab blog post.
Add an On-Demand NAT or On-Demand Routed Network Component
You can add an NSX on-demand NAT network component or NSX on-demand routed network component
to the design canvas in preparation for associating their settings to one or more vSphere machine
components in the blueprint.
When you associate an existing network component or an on-demand network component with a
machine component, the NIC information is stored with the machine component. The network profile
information that you specify is stored with the network component.
You can add multiple network and security components to the design canvas.
You can have more than one on-demand network component in a single blueprint. However, all of the on-
demand network profiles that are used in the blueprint must reference the same external network profile.
For machine components that do not have a Network or Security tab, you can add network and security
custom properties, such as VirtualMachine.Network0.Name, to their Properties tab in the design
canvas. NSX network, security, and load balancer properties are only applicable to vSphere machines.
Prerequisites
n
Create and configure network settings for NSX. See Configuring vRealize Automation and NSX
Administration Guide.
n
Verify that the NSX inventory has executed successfully for your cluster.
To use NSX configurations in vRealize Automation, you must run data collection.
n
Create an on-demand network profile. See Creating a Network Profile.
For example, if you are adding an on-demand NAT network component see Creating a NAT Network
Profile For an On-Demand Network.
Configuring vRealize Automation
VMware, Inc. 392