Before you install or upgrade NSX, consider your network configuration and resources. You can install one NSX Manager per vCenter Server, one instance of Guest Introspection per ESXi™ host, and multiple NSX Edge instances per datacenter.

Hardware

This table lists the hardware requirements for NSX appliances.

Table 1. Hardware Requirements for Appliances

Appliance

Memory

vCPU

Disk Space

NSX Manager

16 GB (24 GB for larger NSX deployments)

4 (8 for larger NSX deployments)

60 GB

NSX Controller

4 GB

4

28 GB

NSX Edge

  • Compact: 512 MB

  • Large: 1 GB

  • Quad Large: 2 GB

  • X-Large: 8 GB

  • Compact: 1

  • Large: 2

  • Quad Large: 4

  • X-Large: 6

  • Compact, Large, Quad Large: 1 disk 584MB + 1 disk 512MB

  • XLarge: 1 disk 584MB + 1 disk 2GB + 1 disk 256MB

Guest Introspection

2 GB

2

5 GB (Provisioned space is 6.26 GB)

As a general guideline, increase NSX Manager resources to 8 vCPU and 24 GB of RAM if your NSX-managed environment contains more than 256 hypervisors or more than 2000 VMs.

For specific sizing details contact VMware support.

For information about increasing the memory and vCPU allocation for your virtual appliances, see Allocate Memory Resources, and Change the Number of Virtual CPUs in vSphere Virtual Machine Administration.

The provisioned space for a Guest Introspection appliance shows as 6.26 GB for Guest Introspection. This is because vSphere ESX Agent Manager creates a snapshot of the service VM to create fast clones, when multiple hosts in a cluster shares a storage. For more information on how to disable this option via ESX Agent Manager, refer to ESX Agent Manager documentation.

Network Latency

You should ensure that the network latency between components is at or below the maximum latency described.

Table 2. Maximum network latency between components

Components

Maximum latency

NSX Manager and NSX Controllers

150 ms RTT

NSX Manager and ESXi hosts

150 ms RTT

NSX Manager and vCenter Server system

150 ms RTT

NSX Manager and NSX Manager in a cross-vCenter NSX environment

150 ms RTT

Software

For the latest interoperability information, see the Product Interoperability Matrixes at http://partnerweb.vmware.com/comp_guide/sim/interop_matrix.php.

For recommended versions of NSX, vCenter Server, and ESXi, see the release notes for the version of NSX to which you are upgrading. Release notes are available at the NSX for vSphere documentation site: https://docs.vmware.com/en/VMware-NSX-for-vSphere/index.html.

For an NSX Manager to participate in a cross-vCenter NSX deployment the following conditions are required:

Component

Version

NSX Manager

6.2 or later

NSX Controller

6.2 or later

vCenter Server

6.0 or later

ESXi

  • ESXi 6.0 or later

  • Host clusters prepared with NSX 6.2 or later VIBs

To manage all NSX Managers in a cross-vCenter NSX deployment from a single vSphere Web Client, you must connect your vCenter Servers in Enhanced Linked Mode. See Using Enhanced Linked Mode in vCenter Server and Host Management.

To verify the compatibility of partner solutions with NSX, see the VMware Compatibility Guide for Networking and Security at http://www.vmware.com/resources/compatibility/search.php?deviceCategory=security.

Client and User Access

The following items are required to manage your NSX environment:

  • Forward and reverse name resolution. This is required if you have added ESXi hosts by name to the vSphere inventory, otherwise NSX Manager cannot resolve the IP addresses.

  • Permissions to add and power on virtual machines

  • Access to the datastore where you store virtual machine files, and the account permissions to copy files to that datastore

  • Cookies must be enabled on your Web browser to access the NSX Manager user interface.

  • Port 443 must be open between the NSX Manager and the ESXi host, the vCenter Server, and the NSX appliances to be deployed. This port is required to download the OVF file on the ESXi host for deployment.

  • A Web browser that is supported for the version of vSphere Web Client you are using. See Using the vSphere Web Client in the vCenter Server and Host Management documentation for details.