NSX Home Lab (1/6) – Deploy NSX Components

1) Requirements

  • Physical Machine – To run nested ESX Servers.
  • vCenter – To manage nested ESX Servers and to integrate with NSX
  • Domain Controller – AD + DNS
  • Licenses – vSphere and NSX

2) My Home Lab Environment

  • ESX running on Physical Machine
  • vCenter and Domain Controller running on main ESXi host
  • 7 Nested ESX Servers

  • Each Nested ESX server has two network adapters. 1st Adapter –Uplink to vSwitch, 2nd Adapter – Uplink to NSX dVSwitch.

  • Template – Ubuntu with apache and MySQL installed. Used to deploy VMS and test network connectivity
  • Network Planning
    • Management VLAN – Used for ESX, vCenter and NSX management.
    • Workload VLAN – Used for testing connectivity between physical network to logical networks
    • VXLAN 5001 – Used for Web Servers
    • VXLAN 5002 – Used for DB Servers

3) Deploy NSX Manager OVA

  • Right Click management ESX Server and Deploy OVF Template.

  • Select Management Network –

The Admin credentials you provide in this step is used for log in to NSX Manager UI

4) Configure NSX Manager

  • Login to NSX manager
    url : https://nsxmanagerIP
    credentials: admin/<password set while deploying ova>

  • View summary

  • Register vCenter Server

  • Check NSX registration in vCenter Web Client

  • Backup NSX

  • Assign License

5) Configure NSX Control Plane

  • Create IP Pool. These IPs will be used by NSX Control Cluster VMs

  • Add Controllers

    Important Note:

    In the following screenshots I have deployed controller nodes in Edge cluster, which is against best practice.Recommended Best practice is to Deploy Controller nodes in Management Cluster not in Edge Cluster.

  • Add two more NSX Controllers

  • Prepare ESX Hosts in Compute and Edge Cluster
    Stop vSphere Update Manager Service before preparing ESX Hosts.
    If you are using NSX 6.3 update ESX host to 6.5a (http://www.virtuallyghetto.com/2017/02/potential-esxi-host-preparation-issues-with-nsx-6-3.html)

  • Configure VXLAN

  • Assign a Segment ID Pool: Specify a segment ID pool for each NSX Manager to isolate your network traffic

    If any of your transport zones will use multicast or hybrid replication mode, you must add a multicast address or a range of multicast addresses

  • Create Transport Zone
    Transport zones dictate which clusters and, therefore, which VMs can participate in the use of a particular network.

Deploy Cross VC NSX – Step by Step Lab (1/3)
NSX Home Lab (2/6) – Logical Switching
No tags for this post.

3 thoughts on “NSX Home Lab (1/6) – Deploy NSX Components

  1. Hi Luis,

    I am running my homelab on Dell Poweredge R710
    2 Quad Core Xeon 5560 Processor ( Hyper threading enabled)
    Storage 3* 500GB SAS 7.2K Disks = 1.5 TB Storage
    RAM : 96gig.


  2. Hi Naresh,

    Can you please share your Physical esx network configuration. How many vswitch you are using and how many uplink you have in your Physical ESX.

    I am having the below mention HW
    Dell Poweredge R720
    2 Quad Core Xeon 5560 Processor ( Hyper threading enabled)
    Storage 2* 1TB Disks = 2 TB Storage
    RAM : 384gig.
    1 Physical NIC.

    All the nested ESX is having – 2 vCPU – 16 GB Ram -80 GB Ram – 2 nic

Leave a Comment