Before you install an NSX Manager, make sure that your environment meets the supported requirements.

Hypervisor Host Requirements for Transport Nodes

Hypervisor

Version

CPU Cores

Memory

vSphere

Supported vSphere version

4

16 GB

CentOS Linux KVM

7.4

4

16 GB

Red Hat Enterprise Linux (RHEL) KVM

7.6, 7.5, and 7.4

4

16 GB

SUSE Linux Enterprise Server KVM

12 SP3, SP4

4

16 GB

Ubuntu KVM

18.04 and 16.04.2 LTS

4

16 GB

Table 1. Supported Hosts for NSX Managers

Support Description

Hypervisor

ESXi

For supported hosts, see the VMware Product Interoperability Matrices.

KVM

RHEL 7.4 and Ubuntu 16.04 LTS

For ESXi hosts, NSX-T Data Center supports the Host Profiles and Auto Deploy features on vSphere 6.7 U1 or higher. See Understanding vSphere Auto Deploy in the VMware ESXi Installation and Setup documentation for more information.

Caution:

On RHEL, the yum update command might update the kernel version and break the compatibility with NSX-T Data Center. Disable the automatic kernel update when you run yum update. Also, after running yum install, verify that NSX-T Data Center supports the kernel version.

Hypervisor Host Network Requirements

It is required that hypervisor hosts running NSX-T Data Center have a compatible NIC card. For supported NIC card, see the VMware Compatibility Guide.

Tip:

To quickly identify compatible cards in the Compatibility Guide, apply the following criteria:

  • Under I/O Device Type, select Network.

  • Optionally, to use supported GENEVE encapsulation, under Features, select the GENEVE options.

  • Optionally, to use Enhanced Data Path, select N-VDS Enhanced Data Path.

Enhanced Data Path NIC Drivers

Download the supported NIC drivers from the My VMware page.

NIC Card

NIC Driver

Intel 82599

ixgben 1.1.0.26-1OEM.670.0.0.7535516

Intel(R) Ethernet Controller X710 for 10GbE SFP+

Intel(R) Ethernet Controller XL710 for 40GbE QSFP+

i40en 1.2.0.0-1OEM.670.0.0.8169922

NSX Manager VM Resource Requirements

Thin virtual disk size is 3.8 GB and thick virtual disk size is 200 GB.

Appliance Size

Memory

vCPU

Disk Space

VM Hardware Version

NSX Manager Extra Small

8 GB

2

200 GB

10 or later

NSX Manager Small VM

16 GB

4

200 GB

10 or later

NSX Manager Medium VM

24 GB

6

200 GB

10 or later

NSX Manager Large VM

48 GB

12

200 GB

10 or later

Note:

As of NSX-T2.4, the NSX Manager provides multiple roles which previously required separate appliances. This includes the policy role, the management plane role and the central control plane role. The central control plane role was previously provide by the NSX Controller appliance.

  • The NSX Manager Extra Small VM resource requirements apply only to the Cloud Service Manager.

  • The NSX Manager Small VM appliance size is suitable for lab and proof-of-concept deployments, and must not be used in production.

  • The NSX Manager Medium VM appliance size is suitable for typical production environments and can support up to 64 hypervisors.

  • The NSX Manager Large VM appliance size is suitable for large-scale deployments with more than 64 hypervisors.

For maximum scale using the NSX Manager Large VM appliance size, go to the VMware Configuration Maximums tool at https://configmax.vmware.com/guest and select NSX-T Data Center from the product list.

NSX Manager Browser Support

Browser

Windows 10

Windows 8.1

Ubuntu 14.04

Mac OS X 10.11. 10.12

Internet Explorer 11

Yes

Yes

Firefox 55

Yes

Yes

Chrome 60

Yes

Yes

Yes

Safari 10

Yes

Microsoft Edge 40

Yes

Note:

Internet Explorer 11 in compatibility mode is not supported.

Supported Browser minimum resolution is 1280 x 800 px.

Network Latency Requirements

The maximum network latency between NSX Managers in a NSX Manager cluster is 10ms.

The maximum network latency between NSX Managers and Transport Nodes is 150ms.

Storage Requirements

  • The maximum disk access latency is under 10ms.

  • It is recommended that NSX Managers be placed on shared storage.

  • Storage should be highly available to avoid a storage outage causing all NSX Manager file systems to be placed into read-only mode upon event of a storage failure.

    Please consult documentation for your storage technology on how to best design a highly available storage solution.