To use NAT in private cloud, first configure the NSX integration, then define the NAT device. NAT networks are very similar to public networks.
To use NAT in vCloud Director, you will need the definition of a NAT network that is compatible with an Edge interface network, which connects the Edge to the external networks.
To create a NAT network:
Click the + add button
Create networks with ranges of public IPs for NAT
The name of the NAT network
|Net. Address||The network address of the NAT network|
The network mask in CIDR format. For IPv4, the networks created in the platform the netmask can have a value from 16 to 30 inclusive, and for IPv6, it can have a value of 64, 56, or 48.
For NSX, the device that will manage the NAT network
To add IP addresses to your network, click the + add button in the top right-hand corner of the Networks page.
When you add IPv6 addresses on strict networks, you don't need to set the starting address. On non-strict IPv6 networks, Abiquo recommends that you create an automatic IP address, or you can enter a From IP address manually.
The NAT network and IPs will display on the NAT tab. In the same way as for public IPs, you can quarantine NAT IPs as required.
Screenshot: NAT networks and IPs in private cloud with NSX
When users create virtual datacenters, the platform can automatically configure a NAT IP, and users can manage NAT rules, and purchase additional NAT IPs. See Manage NAT for virtual datacenters