Posts in this series
Disclaimer! I am learning NSX-T, part of my learning is to deploy in my lab – if I contradict the official docs then go with the docs!
I’m deploying NSX-T in my lab, but since I already have NSX-v running on the physical hosts I’ve opted to deploy one of my nested pods, which I have scripted for an easy deployment. The pod consists of three virtual ESXi 6.5 hosts and a vCenter Server Appliance, configured with vSAN storage and two NICs per host.
I will follow the deployment plan from the installation document:
- Install NSX Manager.
- Install NSX Controllers.
- Join NSX Controllers with the management plane.
- Initialize the control cluster to create a master controller.
- Join NSX Controllers into a control cluster.
- Join hypervisor hosts with the management plane.
- Install NSX Edges.
- Join NSX Edges with the management plane.
- Create transport zones and transport nodes.
Deploying NSX Manager OVA
Deploying the NSX Manager OVA is a fairly standard affair, though I did find that once deployed some of the OVF settings had not applied and the needed re-adding by editing the VM Settings in vSphere.
- Run the Deploy OVF Template wizard and select the NSX-T Manager OVA (nsx-unified-appliance-188.8.131.52.0.6522097.ova)
- Enter the name for the NSX-T Manager appliance (pod-200-nsx-t)
- Select the target cluster or host
- Review the additional settings required for the OVF package
- Select the size of deployment (based on the intended environment type and size)
- Select the datastore on which to deploy the Manager
- Select the Management network for NSX-T
- Enter the application settings – an Admin user name and password
- Enter an Audit user name and password
- Enter an appliance root user password
- Enter the appliance hostname and network details
- Configure the additional settings for SSH access and NTP
- Review the settings and finish the wizard
Once the appliance has deployed, power on the virtual machine. In my lab environment the OVF settings did not apply, I am not sure why. I needed to manually set the network adapter to the correct network, and edit the vApp options to set the properties before the appliance would power on.
Once the appliance has booted, you can access it via HTTPS and log in with the configured admin username and password.
Read and accept the EULA (scroll all the way down to check the agree box)
Finally, the NSX Manager is deployed.
My Pod200 folder now contains 3 ESXi hosts, a vCenter Server Appliance and the NSX-T Manager