I did a quick search on the topic “NSX-T Promiscuous mode” and most of what I found where related to how to nest an NSX-T deployment.I attempted to play around in the segment profiles and no break-throughs there.When it comes to the N-VDS segment that is pushed to show in the vCenter Server Networking, there is no possibility of applying any of the vSphere vDS settings, so I started to look at other ways to see if these settings exist in the first place and then see how to change them. Taking (from experience) how it has been with nested environments before NSX-T, where the vSphere vDS was the main port-group configuration, we used to reconfigure the security parameters to accept: A Segment for the vCD stack (direct and nested where this will be mainly used for a single NSX-v Controller and ESG/s).īringing up the environment went smooth until I reached a point where I had to deploy the NSX-v Controller, this is when things went south and I could not attain connectivity.A VLAN for ESXi management (used for both physical and nested hosts).
This is how the VLANs/Segments are pieced together: Since I moved everything to NSX-T at the physical layer, I am now in the process of building an NSX-v nested environment so that still cater to the different projects that have to do with NSX-v as a networking integration point.