You can use vSphere Web Client to deploy NSX Manager as a virtual appliance.
About this task
It is recommended that you use vSphere Web Client instead of vSphere Client. If you do not have vCenter Server in your environment, use ovftool to deploy NSX Manager. See Install NSX Manager on ESXi Using the Command-Line OVF Tool.
Verify that the system requirements are met. See System Requirements.
Verify that the required ports are open. See Ports and Protocols.
If you don't already have one, create the target VM port group network. Most deployments place NSX appliances on a management VM network.
If you have multiple management networks, you can add static routes to the other networks from the NSX appliance. Prepare management VM port group on which NSX appliances will communicate.
Plan your IPv4 IP address scheme. In this release of NSX-T, IPv6 is not supported.
- Locate the NSX Manager OVA or OVF file.
Either copy the download URL or download the OVA file onto your computer.
- In vSphere Web Client, launch the Deploy OVF template wizard and navigate or link to the .ova file.
- Enter a name for the NSX Manager, and select a folder or datacenter.
The name you type will appear in the inventory.
The folder you select will be used to apply permissions to the NSX Manager.
- Select a datastore to store the NSX Manager virtual appliance files.
- If you are installing in vCenter, select a host or cluster on which to deploy the NSX Manager appliance.
Normally, you would place the NSX Manager in a cluster that provides network management utilities.
- Select the port group or destination network for the NSX Manager.
For example, if you are using vSphere distributed switches, you might place NSX Manager on a port group called Mgmt_VDS - Mgmt.
- Set the NSX Manager passwords and IP settings.
For example, this screen shows the final review screen after all the options are configured.
- For optimal performance, reserve memory for the NSX component.
A memory reservation is a guaranteed lower bound on the amount of physical memory that the host reserves for a virtual machine, even when memory is overcommitted. Set the reservation to a level that ensures the NSX component has sufficient memory to run efficiently. See System Requirements.
Open the console of the NSX component to track the boot process.
After the NSX component is completely booted, log in to the CLI as admin and run the get interface eth0 command to verify that the IP address was applied as expected.
nsx-component> get interface eth0 Interface: eth0 Address: 192.168.110.25/24 MAC address: 00:50:56:86:7b:1b MTU: 1500 Default gateway: 192.168.110.1 Broadcast address: 192.168.110.255 ...
Ensure that your NSX component has the required connectivity.
Make sure that you can ping your NSX component.
Make sure that the NSX component can ping its default gateway.
Make sure that your NSX component can ping the hypervisor hosts that are in the same network as the NSX component.
Make sure that the NSX component can ping its DNS server and its NTP server.
If you enabled SSH, make sure that you can SSH to your NSX component.
If connectivity is not established, make sure the network adapter is in the proper network or VLAN.
What to do next
Connect to the NSX Manager GUI by from a supported web browser. The URL is https://<IP address or hostname of NSX Manager>. For example: https://192.168.110.75.
You must use HTTPS. HTTP is not supported.