Manage NAT for virtual datacenters

Display NAT rules

When the Network Address Translation (NAT) integration is available in your environment, to display NAT IPs and NAT rules:

1. Go to Virtual datacenters → select virtual datacenter → Network → NAT

   Open

   

    

To display NAT rules for a VM:

1. Go to Virtual datacenters

2. Select the VM

3. Go to VM control panel → NAT

   Open

   

To manage or display NAT rules for a VM:

1. Go to Virtual datacenters 

2. Edit a VM

3. Go to Networks → NAT

Create a NAT rule for DNAT

To enable VMs outside your VDC to connect to a VM with a private IP address, after you obtain a NAT IP, create a destination NAT rule, which is also called a DNAT rule. 

To create a DNAT rule:

1. Go to myCloud → Virtual datacenters → Virtual appliances

2. Edit your VM

3. If your VM does not yet have an IP, go to Network → NICs and add a private IP

4. Go to Network → DNAT

5. Click the + add button on the top right-hand side of the tab

6. Enter the details of the DNAT rule

   1. For the Original (NAT IP), select the IP address to receive external connections

   2. Select the Protocol for the connection, which can include TCP, UDP, any, and ICMP

   3. For the Translated IP, select the private IP that is attached to the VM

   4. Optionally, select the checkbox to Use all ports OR
      Enter the Original port for external connections. You cannot use an Original port for a NAT IP in more than one NAT rule.
      The platform will display the ports that are already used in other rules for the selected NAT IP.
      AND for the Translated port, enter the port on the VM

7. Click Add

8. Save the VM

Create a NAT rule for SNAT

To send outgoing traffic through a NAT IP that is not the default one, add an additional SNAT rule with these steps:

To create an SNAT rule:

1. Go to Virtual datacenters → Virtual appliances

2. Edit your VM

3. If your VM does not yet have an IP, go to Network → NICs and add a private IP

4. Go to Network → SNAT

5. Click the + add button on the top right-hand side of the tab

6. Enter the addresses of the SNAT rule

   1. For the Original IP, select the IP that is attached to the VM

   2. For the Translated (NAT IP), select the IP address to display for outgoing connections

7. Click Add

8. Save the VM

Use a NAT IP for a load balancer

To use a NAT IP address as a public IP address for a load balancer:

1. Use the virtual datacenter's NAT IP address or obtain an additional NAT IP address. See Obtain an additional NAT IP address for a virtual datacenter

2. Create the load balancer and select the NAT IP

The platform will automatically create a NAT rule to match the port mappings of the routing rule of the load balancer.

Obtain an additional NAT IP for your virtual datacenter

In addition to the NAT IP address assigned to the virtual datacenter, you can obtain NAT IP addresses for creating additional NAT rules.

To obtain an additional NAT IP address:

1. Go to Virtual datacenters → Network → NAT

2. Click the + add button on the top right-hand side of the screen

3. Select the NAT network and click Accept

The platform will reserve an IP address and allocate it to your virtual datacenter.

You can then use the NAT IP address as the public IP address for a load balancer or to provide access to a private IP address.

Limit NAT IP bandwidth for a VDC

You can use Quality of Service (QoS) traffic shaping parameters to limit the bandwidth for all the NSX NAT IPs in a virtual datacenter. 

When you create a virtual datacenter, the new "natbandwidthlimit" attribute is present but you must edit the virtual datacenter to enable it in the platform and in the NSX. 

To edit the bandwidth limit and apply it in the NSX:

1. Select the virtual datacenter 

2. Go to Network → QoS

3. Click the pencil edit button 

   1. To enable the bandwidth limit in a specific direction, select the Enabled checkbox for that direction

   2. Set QoS values for your virtual datacenter. Be sure to allow enough bandwidth to share between all the NAT IPs in the virtual datacenter.

To register changes that were made outside the platform, save existing NAT bandwidth values. In the API, to register changes, send a POST request with the existing values.