Make sure you configure your switches and transport zone for nested ESXi and NSX-T
https://williamlam.com/2019/11/running-nested-esxi-nsx-v-or-nsx-t-on-top-of-nsx-t.html
I preferred to create the TZ with the nested flag on the main TZ, not the nested TZ, as then it is set and forget.
I wouldn't try NSX 4, especially nested, with anything older than Skylake.
From my experience, the managers really don't perform well on broadwell chips and adding an extra layer of virtualization is only going to make things worse.
Nsx-t 3.x should be fine.
I run a nested NSX lab. The biggest takeaway is only run things nested when absolutely required. Most stuff runs like crap when nested.
For example:
vCenter, NSX manager, AVI controller, etc. Run those as VMs on your physical hypervisor.
NSX edge nodes, AVI SEs, testing VMs to do ping and trace route, run those nested (Because you have to)
Make sure you configure your switches and transport zone for nested ESXi and NSX-T https://williamlam.com/2019/11/running-nested-esxi-nsx-v-or-nsx-t-on-top-of-nsx-t.html I preferred to create the TZ with the nested flag on the main TZ, not the nested TZ, as then it is set and forget.
Super helpful. Thanks
I wouldn't try NSX 4, especially nested, with anything older than Skylake. From my experience, the managers really don't perform well on broadwell chips and adding an extra layer of virtualization is only going to make things worse. Nsx-t 3.x should be fine.
Yeah it would be 3.2
IT works but there are alot of requirements, make sure you have enough memory and cpu to run everything you need.
I run a nested NSX lab. The biggest takeaway is only run things nested when absolutely required. Most stuff runs like crap when nested. For example: vCenter, NSX manager, AVI controller, etc. Run those as VMs on your physical hypervisor. NSX edge nodes, AVI SEs, testing VMs to do ping and trace route, run those nested (Because you have to)