Prerequisites for an Automated NAT Deployment to NSX-T Data Center

Page last updated:

Warning: VMware Enterprise PKS v1.6 is no longer supported because it has reached the End of General Support (EOGS) phase as defined by the Support Lifecycle Policy. To stay up to date with the latest software and security updates, upgrade to a supported version.

An unprepared environment is an NSX-T Data Center instance that you have not already configured for use with Enterprise PKS. Enterprise PKS Management Console helps you to complete the configuration of an unprepared environment, but the environment must meet certain infrastructure prerequisites.

  • 3 NSX Manager Nodes deployed
  • NSX Management Cluster formed
  • Virtual IP address assigned for the Management Cluster or load balancer

For information about the supported versions of NSX-T Data Center, see the release notes.

General Requirements

  • Edge Cluster with at least 2 NSX-T Data Center Edge Nodes deployed and connectivity to an uplink network configured and verified
  • Overlay Transport Zone created, with the edge nodes included
  • VLAN Transport Zone created, with the edge nodes included
  • MTU of all transport nodes and physical interfaces configured to 1600 or more
  • Obtain the following IP addresses for the uplink network to use:
    • Subnet, subnet mask, gateway, and VLAN ID of the uplink network
    • Addresses within the uplink subnet for the Tier 0 uplinks
    • Address to use for the HA Virtual IP on the Tier-0 router
  • Obtain the following IP additional addresses:
    • CIDR ranges to use for deployment, pods, and nodes. This range of IP addresses must not be in conflict with any other workloads.
    • IP addresses of DNS and NTP servers
    • A range of 5 available floating IP addresses
  • If your NSX-T Data Center environment uses custom certificates, obtain the CA certificate for NSX Manager

    Note: If NSX-T Data Center uses custom certificates and you do not provide the CA certificate for NSX Manager, Enterprise PKS Management Console automatically generates one and registers it with NSX Manager. This can cause other services that are integrated with NSX Manager not to function correctly.

Proof-of-Concept Deployments

The requirements above are for production environments. In proof-of-concept deployments one NSX Manager node is sufficient. The NSX management cluster and load balancer are also optional for proof-of-concept deployments. One NSX-T Data Center Edge node is sufficient for proof-of-concept deployments.

Please send any feedback you have to