nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

NSX - L3 between Controller nodes

jibbajabba

I am watching the Pluralsight course on NSX and a colleague of mine, who is VCIX-NV, warned me that there are some problems in both courses.

For example, in the first one, Jason Nash says that "VMware told him that you cannot do L3 between Controller Nodes and that you need to do a stretched L2 if the controller nodes are in different racks".

I cannot find any official documents on that ...

Thoughts ?

Find more posts tagged with

SAVE $250 on Your Boot Camp — Use Code "EXAM26"

Exclusively for TechExams members for Infosec Boot Camps starting before April 30, 2026

View Boot Camps

Comments

Wagnaard

It's still a fairly new product, so they are still figuring things out. I took a training class and found it to be an amazing product. But very unforgiving. Fat finger a digit in step 2 you may not realize it until step 10. Then you have to do a tear down. My colleague somehow managed to destroy his ESXi host.
So I would not be surprised if there are discrepancies this early on.

jibbajabba

In a recent discussion we found out that the KBs relating to NSX and vCloud Director make no sense either ...

Ah well, I hope the VCP-NV book due to release in June, has things "figured out" by then

dave330i

The install document only states controller must be reachable from NSX Manager and vsphere management network. Nothing about same subnet.

jibbajabba

dave330i wrote: »

The install document only states controller must be reachable from NSX Manager and vsphere management network. Nothing about same subnet.

Thanks .. can't see it in the document, but might just be bind .. More reading needed.

I guess could check the SETs as well.

Edit:

Interesting