...
Excerpt | ||
---|---|---|
| ||
As part of the Abiquo NSX integration or NSX-T integration, you can use the NAT blueprint to configure virtual datacenters with NAT.
To configure NAT for a datacenter:
|
...
Create a NAT network
Excerpt | ||
---|---|---|
| ||
Expand | ||
| ||
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:
|
...
Enter the Number of IPs to create and the From IP address (the first in the range). The From IP address must be a new address that does not already exist in the network. After creating the first IP address, the platform will try to create the other IPs and it will skip any existing IP addresses. For example, if you have IP addresses in network 30.30.30.30, which are 30, 33, and 34 and then you request 3 new IPs from 30.30.30.31. The new IPs created should be as follows: 31, 32, 35.
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 |
Manage NAT with the API
Tip |
---|
API Documentation For the Abiquo API documentation of this feature, see Abiquo API Resources and the page for this resource NatNetworksResource. |
...