You can use vSphere Web Client to deploy NSX Manager, NSX Policy Manager, or the Cloud Service Manager as a virtual appliance.
The NSX Policy Manager is a virtual appliance that lets you manage policies. You can configure policies to specify rules for NSX-T Data Center components such as logical ports, IP addresses, and VMs. NSX Policy Manager rules allow you to set high-level usage and resource access rules that are enforced without specifying the exact details.
Cloud Service Manager is a virtual appliance that uses NSX-T Data Center components and integrates them with your public cloud.
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.
- Locate the NSX-T Data Center Unified Appliance 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 appears 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.
- Select the port group or destination network for the NSX Manager.
- Specify the NSX Manager passwords and IP settings.
- Accept the nsx-manager role.
Select the nsx-policy-manager role from the drop-down menu to install the NSX Policy Manager appliance.
Select the nsx-cloud-service-manager role from the drop-down menu to install the NSX Cloud appliance.
The nsx-manager nsx-cloud-service-manager (multi-role) role is not supported.
- (Optional) For optimal performance, reserve memory for the NSX-T Data Center 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-T Data Center component has sufficient memory to run efficiently. See System Requirements.
- Open the console of the NSX-T Data Center component to track the boot process.
- After the NSX-T Data Center component boots, 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 ...
- Verify that your NSX-T Data Center component has the required connectivity.
Make sure that you can perform the following tasks.
Ping your NSX-T Data Center component from another machine.
The NSX-T Data Center component can ping its default gateway.
The NSX-T Data Center component can ping the hypervisor hosts that are in the same network as the NSX-T Data Center component using the management interface.
The NSX-T Data Center component can ping its DNS server and its NTP server.
If you enabled SSH, make sure that you can SSH to your NSX-T Data Center component.
If connectivity is not established, make sure the network adapter of the virtual appliance 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 of NSX Manager>. For example, https://10.16.176.10.
You must use HTTPS. HTTP is not supported.