The network profile information identifies the NAT network properties, its underlying external network profile, and other values used in provisioning the network when using a third-party IPAM endpoint.
Before you begin
Log in to the vRealize Automation console as a fabric administrator.
Create an external network profile. See Create an External Network Profile By Using the Supplied IPAM Endpoint or Create an External Network Profile by Using A Third-Party IPAM Provider.
Create and configure a third-party IPAM endpoint. See Create a Third-Party IPAM Provider Endpoint.
- Select .
- Click New and select NAT from the drop-down menu.
- Enter a name and, optionally, a description.
- If you have configured one or more third-party IPAM provider endpoints, select a third-party IPAM endpoint in the IPAM endpoint drop-down menu.
When you select a third-party IPAM provider endpoint that you have registered in vRealize Orchestrator, IP addresses are obtained from the specified IPAM service provider. IP specifications such as subnet mask and DNS/WINS options are not available because their functions are controlled by the selected third-party IPAM endpoint.
- Select an existing external network profile from the External Network Profile drop-down menu.
Only external network profiles that are configured to use the specified IPAM endpoint are listed and available to select.
- 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 use only static IP addresses. Every machine can access the external network, but no machine is accessible from the external network.
DHCP is not supported when using NAT with a third-party IPAM provider.
The NAT one-to-many translation type allows you to define NAT rules when you add a NAT network component to a blueprint.
- 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 255.255.0.0.
- Enter an Edge or routed gateway address in the Gateway text box.
Use a standard IPv4 address format. For example, enter 10.10.110.1.
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.
- Click the DNS tab.
- 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.
- (Optional) : Enter a Primary DNS server value.
- (Optional) : Enter a Secondary DNS server value.
- (Optional) : Enter a DNS suffixes value.
- (Optional) : Enter a DNS search suffixes value.
- (Optional) : Enter a Preferred WINS server value.
- (Optional) : Enter an Alternate WINS server value.