From the explanation - this is your scenario
When you say management has no NSX license - do you mean it has vSphere Ent plus license but not from NSX licensing?
The problem i have is in defining the vlans specially the managmnet/Vmotion ect on Management cluster and almost same on Compute on edge pod --> As far as I know there won't be any change the way that you create your Management & V-Motion networks, however you need to finalize the Network schema before that.
I was trying to understand the communication and flow of traffic between the vlans from management cluster to edge/compute.
VXLAN is required for E-W communication which depends on VTEP IP but not based on the ESXi management IP
Hope it will clarify your doubts.
The network port requirements are listed on the KBs that Luke has provided in previous reply.
It is fine to deploy NSX Manager and NSX Controllers on Management Cluster as long as you don't need NSX features (VXLAN, DFW) on the Management Cluster.
Plus you will be deploying Edge on the Compute/Edge Cluster so only those 6 Compute/Edge hosts need to be licensed and installed/prepared for NSX.
Any communications from NSX Manager/NSX Controllers to ESXi Hosts, other NSX Management components and vice versa would use the management VLAN using the port listed in the KB.Bayu Wibowo | vExpert NSX, VCIX6-DCV/NV, Cisco Champion, AWS-SAA1 person found this helpful
Author of VMware NSX Cookbook http://bit.ly/NSXCookbook
https://nz.linkedin.com/in/bayupw | twitter @bayupw