The network profile identifies the NAT network properties, underlying external network profile, NAT type, and other values used to provision the network by using the embedded vRealize Automation IPAM.

If you want to create a NAT network profile that uses a third-party IPAM endpoint, see Specify NAT Network Profile Information with a Third-Party IPAM Endpoint.



  1. Select Infrastructure > Reservations > Network Profiles.
  2. Click New and select NAT from the drop-down menu.
  3. Enter a name and, optionally, a description.
  4. Accept the default IPAM endpoint value for the supplied vRealize Automation IPAM endpoint.
  5. Select an existing external network profile from the External Network Profile drop-down menu.
  6. Select a one-to-one or one-to-many network address translation type from the NAT type drop-down menu.




    Assign an external static IP address to each network adapter. Every machine can access the external network and is accessible from the external network.

    All external IP addresses that are assigned to an NSX edge uplink must be part of the same subnet. When using NAT 1:1 in vRealize Automation, the corresponding external network profile must contain only IP ranges that exist within a single subnet.


    One external IP address is shared among all machines on the network. An internal machine can have either DHCP or static IP addresses. Every machine can access the external network, but no machine is accessible from the external network. Selecting this option enables the Enabled check box in the DHCP group.

    The NAT one-to-many translation type allows you to define NAT rules when you add a NAT network component to a blueprint.

  7. Enter an IP subnet mask in the Subnet mask text box.

    The subnet mask specifies the size of the entire routable address space that you want to define for your network profile.

    For example, enter

  8. Enter an Edge or routed gateway address in the Gateway text box.

    Use a standard IPv4 address format. For example, enter

    The gateway IP address defined in the network profile is assigned to the NIC during allocation. If no value is assigned in the Gateway text box in the network profile, then you must use the VirtualMachine.Network0.Gateway custom property when provisioning the Edge machine.

  9. (Optional) In the DHCP group, select the Enabled check box and enter the IP range start and IP range end values.

    You can select the check box only if you set the NAT type to one-to-many.

  10. (Optional) Set a DHCP lease time to define how long a machine can use an IP address.
  11. Click the DNS tab.
  12. Enter DNS and WINS values as needed.

    DNS values are used for DNS name registration and resolution. The DNS and WINS fields are optional if you are using an internal IPAM endpoint. If you are using an external IPAM endpoint, the DNS and WINS values are provided by the third-party IPAM provider.

    1. (Optional) Enter a Primary DNS server value.
    2. (Optional) Enter a Secondary DNS server value.
    3. (Optional) Enter a DNS suffixes value.
    4. (Optional) Enter a DNS search suffixes value.
    5. (Optional) Enter a Preferred WINS server value.
    6. (Optional) Enter an Alternate WINS server value.

What to do next

Configure NAT Network Profile IP Ranges with the vRealize Automation IPAM Endpoint.