How to create a custom private network gateway

When working with NSX (using NAT or ECMP configurations), the platform creates an Edge for each virtual datacenter to provide gateway, DHCP, load balancing, and so on.

Static Edge gateway configuration VM

This configuration is with the default settings, which means the nsx.static-edge-gateway property is set to true.

To use your own network security software deployed on a VM and direct all virtual datacenter traffic through this VM, create your own custom gateway in a private network.

1. Create your VM to use as a gateway 
2. Configure the VM to add NICs in the private network, and a public network or similar
3. Edit the private network and set the address of your gateway VM as the network gateway

4. Deploy the VM

The platform updates the existing leases in the NSX Edge DHCP to use the new gateway IP, and all new leases will use it too.

The platform updates the Private Network IP on the NIC of the Edge to the new gateway IP.

Non-static Edge gateway VM

This is with the nsx.static-edge-gateway property set to false.

To use your own network security software deployed on a VM and direct all virtual datacenter traffic through this VM, create your own custom gateway in a private network.

1. Create your VM to use as a gateway 
2. Configure the VM to add NICs in the private network, and a public network or similar
3. Deploy the VM
4. Edit the private network and set the address of your gateway VM as the network gateway

The platform updates the existing leases in the NSX Edge DHCP to use the new gateway IP, and all new leases will use it too.

The platform does not update the Private Network IP on the NIC of the Edge.

Change the private network IP of the Edge

To change the private network IP of the Edge

1. Edit the private network and for the Gateway, set an IP that is not in use (i.e. not assigned to any VM, with no DHCP lease). 
2. The platform updates the DHCP and it updates the Private Network IP on the NIC of the Edge to the new Gateway IP.