TL;DR / Quick Summary:
A side-by-side comparison of the brains behind VMware NSX-T and Azure Local SDN: NSX Manager vs Network Controller. Includes clustering guidance, API access, and automation notes.
Now that we’ve covered some helpful SDN insights, it’s time to compare and contrast the two software-defined solutions. What better place to begin than with the brains behind each architecture?
Below you’ll find a breakdown of NSX Manager and Azure Network Controller, along with resource links for deeper dives.
Feel free to check in on this series:
FYI:
The current details are based on today’s supported architecture. However, Microsoft is revamping its SDN management experience in Azure Local 2405 and Windows Server 2025 — stay tuned for that future post.
The NSX Manager – The Brains of this Outfit
NSX Manager is the central brain of VMware’s software-defined networking. A group of three NSX Manager nodes form a high-availability management cluster — scaling independently of the size of the environment.
It operates at the management plane, not the data plane — which is critical. Even if the NSX management cluster goes down, your data flows and firewall rules stay active.
Key responsibilities:
Runs on Corfu DB to store and sync configuration data across the cluster
REST API and Web UI for all configurations
Computes and distributes virtual network state
For more information on the NSX Manager and how to install/admin the cluster, please see the below links:
https://docs.vmware.com/en/VMware-NSX/4.1/administration/GUID-FBFD577B-745C-4658-B713-A3016D18CB9A.html
https://nsx.techzone.vmware.com/api/checkuseraccess?referer=/sites/default/files/NSX-T%20Reference%20Design%20Guide%203-0.pdf
The Network Controller – the Uber Brains of this Outfit 🙂
The Azure Network Controller is the core of Microsoft’s SDN management. It delivers a programmable, centralized automation point for SDN infrastructure.
Like NSX Manager, it resides on the management plane and remains isolated from the data path. Even during outages, your traffic keeps flowing.
Cluster design:
- Minimum 3 VMs for 2-host deployments
- 5 VMs recommended for HA on 4+ hosts
Key features:
- Automates SDN config and lifecycle tasks
- Monitors health and remediates drift
- Uses OVSDB (Open vSwitch DB Protocol) as the southbound interface
- Sends HNV policies to Host Agents, which program Hyper-V switch flow engines
For more information about the Network Controller, I recommend the following:
https://learn.microsoft.com/en-us/azure-stack/hci/concepts/network-controller-overview
https://learn.microsoft.com/en-us/windows-server/networking/sdn/technologies/network-controller/network-controller-high-availability
Summary:
Whether you use NSX or Azure Local SDN, a resilient and accessible management plane is non-negotiable.
Both platforms offer:
- GUI, API, and CLI access
- Integration with automation pipelines
- Distributed, highly available clustering
Choose based on how you plan to scale, automate, and maintain visibility across your hybrid cloud network.
The thoughts and opinions in this article are mine and do not reflect those of my employer.
TL;DR / Quick Summary:Compare how NSX and Azure Local SDN manage north-south traffic, edge VM architecture, Tier-0 routing, and software-defined load balancing...