If you prefer to automate NSX Manager installation, you can use the VMware OVF Tool, which is a command-line utility.

About this task

By default, nsx_isSSHEnabled and nsx_allowSSHRootLogin are both disabled for security reasons. When they are disabled, you cannot SSH or log in to the NSX Manager command line. If you enable nsx_isSSHEnabled but not nsx_allowSSHRootLogin, you can SSH to NSX Manager but you cannot log in as root.

Prerequisites

  • 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.

Procedure

  • (For a standalone host) Run the ovftool command with the appropriate parameters. For example,
    C:\Users\Administrator\Downloads>ovftool 
    --name=nsx-manager 
    --X:injectOvfEnv 
    --X:logFile=ovftool.log
     --allowExtraConfig 
    --datastore=ds1 
    --network="management" 
    --acceptAllEulas 
    --noSSLVerify 
    --diskMode=thin 
    --powerOn 
    --prop:nsx_ip_0=192.168.110.75 
    --prop:nsx_netmask_0=255.255.255.0 
    --prop:nsx_gateway_0=192.168.110.1 
    --prop:nsx_dns1_0=192.168.110.10 
    --prop:nsx_domain_0=corp.local 
    --prop:nsx_ntp_0=192.168.110.10 
    --prop:nsx_isSSHEnabled=<True|False> 
    --prop:nsx_allowSSHRootLogin=<True|False> 
    --prop:nsx_passwd_0=<password> 
    --prop:nsx_cli_passwd_0=<password> 
    --prop:nsx_hostname=nsx-manager 
    nsx-<component>.ova 
    vi://root:<password>@192.168.110.51
    
    
    Opening OVA source: nsx-<component>.ova
    The manifest validates
    Source is signed and the certificate validates
    Opening VI target: vi://root:<password>@192.168.110.51
    Deploying to VI: vi://root:<password>@192.168.110.51
    Transfer Completed
    Powering on VM: nsx-manager
    Task Completed
    Warning:
     - No manifest entry found for: 'nsx-<component>.ovf'.
     - File is missing from the manifest: 'nsx-<component>.ovf'.
     - ExtraConfig options exists in source.
     - Skipping monitor as the --X:waitForIp option is not given.
    Completed successfully
    
    
  • (For a host that is managed by vCenter Server) Run the ovftool command with the appropriate parameters. For example,

    C:\Users\Administrator\Downloads>ovftool 
    --name=nsx-manager 
    --X:injectOvfEnv 
    --X:logFile=ovftool.log
     --allowExtraConfig 
    --datastore=ds1 
    --network="management" 
    --acceptAllEulas 
    --noSSLVerify 
    --diskMode=thin 
    --powerOn 
    --prop:nsx_ip_0=192.168.110.75 
    --prop:nsx_netmask_0=255.255.255.0 
    --prop:nsx_gateway_0=192.168.110.1 
    --prop:nsx_dns1_0=192.168.110.10 
    --prop:nsx_domain_0=corp.local 
    --prop:nsx_ntp_0=192.168.110.10 
    --prop:nsx_isSSHEnabled=<True|False> 
    --prop:nsx_allowSSHRootLogin=<True|False> 
    --prop:nsx_passwd_0=<password> 
    --prop:nsx_cli_passwd_0=<password> 
    --prop:nsx_hostname=nsx-manager 
    nsx-<component>.ova 
    vi://administrator@vsphere.local:<password>@192.168.110.24/?ip=192.168.110.51
    
    
    

    Opening OVA source: nsx-<component>.ova
    The manifest validates
    Source is signed and the certificate validates
    Opening VI target: vi://administrator@vsphere.local@192.168.110.24:443/
    Deploying to VI: vi://administrator@vsphere.local@192.168.110.24:443/
    Transfer Completed
    Powering on VM: nsx-manager
    Task Completed
    Warning:
     - No manifest entry found for: 'nsx-<component>.ovf'.
     - File is missing from the manifest: 'nsx-<component>.ovf'.
     - ExtraConfig options exists in source.
     - Skipping monitor as the --X:waitForIp option is not given.
    Completed successfully
    
    
  • 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.

Results

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.

Note:

You must use HTTPS. HTTP is not supported.