Pool of Edge nodes that runs centralised gateway services, for example VPN, NAT, load balancing and north-south routing. VCF adds it to a workload domain after that domain has been built.
Read more: Broadcom TechDocs
In the Ultra Transcenders books
Each book explains NSX Edge cluster in context, with comparison tables and the common traps.
Terms in this definition
- Agents (classic) API
First-generation Foundry Agent Service API, based on threads, messages and runs. It is deprecated, replaced by conversations and responses, and retires on 31 March 2027.
- VPN
Traffic sent through an encrypted tunnel across a public network, as in a site-to-site connection to a VPN gateway in an Azure GatewaySubnet.
- Azure NAT Gateway
Gives every resource in a subnet a managed way out to the internet through one or more fixed public IP addresses, while accepting no unsolicited inbound connections. Azure Container Apps can use it only when the environment is a workload profiles one.
- ELT
Extract, load, transform: raw data lands in the target system first and is transformed there. See ETL for the opposite order.
- Geographic
A Traffic Manager routing method that picks the endpoint according to where the user is located geographically.
- VMware Cloud Foundation
Broadcom's platform for private cloud. It unifies management of NSX, vSAN, vSphere, VCF Automation and VCF Operations as one fleet; VVF, by contrast, lacks automation and cloud management.
- workload domain
Domain in VCF for business applications. It gets a dedicated vCenter and NSX that may be dedicated or shared; the management components live separately in the management domain.
- Domain
A way of grouping workspaces by area of the business, in support of a data mesh approach. Items take on their workspace's domain, letting you filter the OneLake catalog by it, and certain tenant settings can be passed to domain admins; domains have no effect on access permissions.
Related terms
- Dual Availability Zone Design based on NSX Edge Node HA
Unlike the vSphere HA recovery design, where edges migrate between zones, this two-zone NSX Edge cluster model fixes each edge node to one zone, on either a per-zone vSphere cluster or a stretched vSAN cluster. Edge VLANs stay local and BGP peers only with that zone's top-of-rack switches, while NSX Edge node HA and BFD provide rapid failover and the strongest fault isolation.
- Fleet Level Components on NSX VLAN Segment Model
Isolates fleet management components by attaching them to an NSX segment backed by a VLAN, leaving routing to the physical network. An NSX Edge cluster is only needed if the NSX load balancer is used; deployment happens after initial setup through the API, and a stretched cluster requires that VLAN to span both zones.