Academy/NSX 4.x Network Virtualization Professional (2V0-41.24)
VCF
NSX 4.x Network Virtualization Professional (2V0-41.24)
VCF 9.0vcp-foundation
NSX Advanced Data Center architecture, logical switching/routing, security services, and advanced features. Deep technical proficiency for deployment. Exam target: NSX 4.x — 2V0-41.24 is listed under "VMware Legacy Certifications" on Broadcom's certification hub and is not a VCF 9.0 exam. 55 items per the exam guide (Broadcom's certification page says 70), 135 minutes.
2V0-41.24
VCP
55
Questions
135m
Duration
300 (scaled)
Pass Score
56
Objectives
Exam Blueprint Weights
Section titles, groupings and weights below are VCDX Academy study groupings, NOT the official Broadcom blueprint structure. Broadcom publishes no section weights. Always cross-check the official exam guide. Official exam guide ↗
Section 1 — Architecture and Technologies
~12%
Section 2 — Installation and Configuration
~18%
Section 3 — Logical Switching
~15%
Section 4 — Logical Routing
~18%
Section 5 — Security Services
~18%
Section 6 — Operations and Troubleshooting
~19%
Version Evolution
Exam target: NSX 4.x (2V0-41.24 is listed under "VMware Legacy Certifications" on Broadcom's certification hub, not a VCF 9.0 exam; the VCF version tags here mark the VCF releases this NSX material applies to). NSX 4.x is the NSX-T 3.x architecture carried forward, not a redesign. Key points: (1) Converged management and control planes: since NSX-T 2.4 the central control plane runs inside the 3-node NSX Manager cluster; there is no separate Controller appliance (VCF 9.0.1, NSX Management and Control Plane Models).
(2) Policy API/UI is the supported interface; the Manager API/UI is deprecated (blueprint 2.3.1). (3) BUM replication per overlay segment: Hierarchical Two-Tier (default, VCF-recommended) or Head; selection follows TEP-subnet layout, not host count. (4) Two-tier Tier-0/Tier-1 routing, ECMP across up to 8 Edge nodes, and Stateful Active/Active Tier-0/Tier-1 gateways (interface groups, state synchronisation).
(5) Federation: one active and one standby Global Manager cluster, Local Managers per location, RTEP connectivity between Edge clusters, 500 ms maximum RTT between GM/LM nodes (VCF 9.0.1, NSX Federation Requirements). NSX-V to NSX-T migration (Migration Coordinator) is history for VCF 9.0 estates; the skills that transfer are overlay switching, Edge sizing by throughput band and replication-mode selection.
Learning Outcomes
Understand NSX 4.x Network Virtualization Professional concepts and architecture
Exam insight: since NSX-T 2.4 the central control plane (CCP) runs INSIDE the NSX Manager appliance — there is no separate NSX Controller appliance to deploy. Production uses a 3-node NSX Manager cluster (quorum 2 of 3; a 2-node cluster is never supported), and VCF 9.0 also supports a single NSX Manager for reduced-footprint deployments.
Choose and justify the BUM replication mode (Hierarchical Two-Tier by default, Head for a single TEP subnet) and apply segment-profile BUM rate limiting when broadcast storms saturate a large cluster.
NSX 4.x separates control and management into distinct planes for scalability and resilience:
Management Plane: NSX Manager Cluster (3-node HA)
Cluster config:
3 NSX Manager nodes (Medium: 6 vCPU/24 GB each) with a cluster VIP. The VIP is owned by one node at a time and provides high availability only; it does not load-balance requests across the cluster (VCF-NSX-LM-REQD-CFG-002, VCF 9.0.1 docs p.560). Use an external load balancer if API traffic must be spread.
Functions:
Policy management (segments, DFW rules, AD integration), inventory sync with vCenter, certificate management
Failure tolerance:
1 node down = cluster quorum maintained (2-of-3); 2 nodes down = cluster isolated (no config changes)
Database:
Distributed datastore (Corfu) replicated across the three Manager nodes (Corfu server named in the VCF 9.0 release notes, VCF 9.0.1 docs p.423)
Control Plane: Central Control Plane (CCP) & Local Control Plane (LCP)
Central Control Plane (CCP):
Runs inside the 3-node NSX Manager cluster — there is no separate NSX Controller appliance (VCF 9.0.1, NSX Management and Control Plane Models). Computes and distributes runtime state:
MAC, IP (ARP) and TEP tables per segment
BUM replication (TEP group / MTEP) membership
TEP-to-segment mapping for Geneve encapsulation
Distributed firewall and routing configuration realised on each transport node
Local Control Plane (LCP):
User-space agents on every transport node (ESX host or Edge) that receive state from the CCP and program the in-kernel data plane. Responsible for:
Programming the VDS data path (Geneve encap/decap, distributed routing) and the DFW rule tables on the host
Reporting local status back to the CCP
Redundancy: if the CCP is unreachable, the LCP keeps forwarding with the last known state; only new learning and policy changes stop until the Manager cluster recovers.
Data Plane: Host switch (VDS 7.0+ on ESXi; N-VDS only on Edge nodes) & TEP Tunneling
Kernel-based virtual switch (replaces traditional vDS for NSX). NOTE: on ESXi the data plane is the VDS — N-VDS was deprecated in NSX-T 3.1.2 and removed for ESXi hosts in NSX 4.0.0.1; it remains only for Edge transport nodes. Multiple host switches per host support complex topologies (zone-isolated segments)
One or more TEPs per host on a VLAN-backed underlay; multiple TEPs (as drawn above) are a bandwidth and uplink-resiliency design choice, not a minimum. Can be same VLAN (convergence) or separate VLANs (isolation)
MTU:
Geneve needs at least 1600 end to end (the roughly 50-byte Geneve overhead already includes the outer IP/UDP headers); VCF 9.0 requires 1700 or greater on host and Edge TEP VLANs and first-hop gateways to leave room for Geneve options (VCF-NET-REQD-MTU-006, VCF 9.0.1 docs p.585), and 9000 is the usual jumbo-frame setting on switch ports
Physical server running the NSX Edge image. Documented minimum 8 cores/32 GB/200 GB, recommended 24 cores/256 GB/200 GB, up to 80 cores per system; DPDK needs AES-NI and 1 GB huge pages (VCF 9.0.1, NSX Edge Bare Metal Requirements). Chosen for multi-100G and small-packet workloads; not deployed by VCF workflows
VM-based edge:
NSX Edge VM form factors (VCF 9.0.1, NSX Edge VM Resource Requirements): Small 2 vCPU/4 GB (proof-of-concept only), Medium 4 vCPU/8 GB (L2-L4, total throughput under 2 Gbps), Large 8 vCPU/32 GB (2-10 Gbps, L7 LB, TLS inspection), Extra Large 16 vCPU/64 GB (higher throughput, L7 LB, VPN, URL filtering, IDS/IPS, malware prevention). 200 GB disk for every size. VCF deploys Edge VMs; size by throughput and feature band, not by a per-VM Gbps cap
Cluster topology:
2+ edges in Active-Active (HA) or Active-Standby. Active-Active requires BGP/ECMP load balancing across edges
Datapath:
Edge nodes also run LCP; maintain local routing table cache for sub-millisecond convergence on CCP loss Exam insight: since NSX-T 2.4 the central control plane (CCP) runs INSIDE the NSX Manager appliance — there is no separate NSX Controller appliance to deploy. Production uses a 3-node NSX Manager cluster (quorum 2 of 3; a 2-node cluster is never supported), and VCF 9.0 also supports a single NSX Manager for reduced-footprint deployments.
Know TEP tunneling and the VDS data path (N-VDS was removed on ESXi hosts in NSX 4.0.0.1; it survives only inside NSX Edge nodes, public-cloud agents and bare-metal workloads)
Key Takeaways
Exam insight: since NSX-T 2.4 the central control plane (CCP) runs INSIDE the NSX Manager appliance — there is no separate NSX Controller appliance to deploy. Production uses a 3-node NSX Manager cluster (quorum 2 of 3; a 2-node cluster is never supported), and VCF 9.0 also supports a single NSX Manager for reduced-footprint deployments.
Exam question: "Your cluster has 200 hosts and broadcast storms causing network saturation. How do you optimize?" Answer: confirm the segments use Hierarchical Two-Tier replication (the default and VCF-recommended mode), then apply a segment-profile BUM rate limit (segment security profile) to cap broadcast/unknown-unicast/multicast per port.
T0/T1 Routing Model: T0 connects to physical network (edge nodes), T1 connects to segments (logical switches). ECMP design: one Active/Active T0 spread across the Edge nodes of the cluster (up to 8 Edge nodes, VCF 9.0.1 docs p.1183), with BGP multipath to the ToRs. Edge sizing: Medium (<2 Gbps, L2-L4), Large (2-10 Gbps, L7 LB/TLS), Extra Large (above that, VPN/IDS-IPS); bare metal (min 8 cores/32 GB, recommended 24 cores/256 GB) for multi-100G needs. Failure modes: T0 loss = no external connectivity; T1 loss = isolated segment but overlay unaffected.
Federation Design Caveats: Global Manager-to-location latency must be 500 ms or less (150 ms or less when networks are stretched); routed L3 between sites is sufficient. The active and standby Global Manager clusters sit in different locations, and each location keeps its own Local Manager cluster. Plan BUM handling for stretched segments and the GM/LM failure behaviour. Recommendation: test stretched segments and failover scenarios with production-like latency before rollout.
Network Evolution: NSX-V→NSX-T→NSX 4.x transition eliminated legacy modes. NSX 4.x uses Geneve overlay (VXLAN belonged to NSX for vSphere) over a VLAN-backed TEP underlay. MTU sizing critical: Geneve needs 1600+ end to end, and VCF 9.0 requires 1700+ on TEP VLANs and gateways (VCF-NET-REQD-MTU-006). Holodeck lab constraint: edge node VMs limited to modest sizing; plan accordingly for resource-constrained environments.
NSX Logical Switching & Routing — Segments, Gateways, Transport Zones#
NSX logical switching and routing form the backbone of VCF networking. This topic covers segment creation, transport zone design, Tier-0/Tier-1 gateway architecture, and routing protocols.
Logical Segments (Overlay & VLAN)
Overlay Segments: GENEVE-encapsulated Layer 2 broadcast domains. VMs attached to the same overlay segment can communicate at L2 regardless of which ESXi host they reside on. Traffic between hosts is tunneled via TEP-to-TEP GENEVE encapsulation (UDP port 6081).
VLAN Segments: Direct VLAN-tagged segments for connecting to physical infrastructure (bare-metal servers, physical appliances, external networks). No encapsulation — traffic uses standard 802.1Q VLAN tags on the physical switch fabric.
Segment Profiles: Define QoS, IP Discovery, MAC Discovery, and Segment Security settings per segment. Key profiles:
IP Discovery: ARP snooping and DHCP snooping to build IP-MAC mapping tables. Prevents ARP spoofing.
MAC Discovery: Controls MAC learning behavior. MAC limit per port prevents MAC flooding attacks.
BUM Traffic Handling: two replication modes, set per overlay segment (VCF 5.2 design guide Table 85 and VCF-NSX-OVERLAY-RCMD-CFG-002; NSX Administration Guide):
Hierarchical Two-Tier (default, VCF-recommended): transport nodes are grouped by TEP subnet; the source TEP sends one copy to a mediator TEP (MTEP) in each remote subnet, which replicates locally. Fewer copies leave the source when hosts span several TEP subnets.
Head replication: the source TEP sends a copy to every other TEP on the segment. Simple; suits a single TEP subnet.
Hybrid and multicast modes belonged to NSX for vSphere (VXLAN logical switches) and are not NSX 4.x options; choose by TEP-subnet layout, not by a host-count threshold.
Transport Zones
Transport Zone (TZ) defines the span of a logical switch — which hosts can participate in a given set of segments.
Overlay Transport Zone: Hosts that participate in GENEVE overlay networking. Each host can belong to one overlay TZ. TZ scope determines which hosts can host VMs on overlay segments.
VLAN Transport Zone: Hosts or Edge nodes that participate in VLAN-backed segments. A host/edge can belong to multiple VLAN TZs. Used for uplink connectivity to physical network.
Design Patterns:
Single Overlay TZ (simple): All hosts in one overlay TZ. All segments reachable from all hosts. Suitable for single-domain deployments.
Multi TZ (isolation): Separate overlay TZs per workload domain or tenant. Segments in TZ-A are invisible to hosts in TZ-B. Provides network-level isolation.
Edge TZ: Separate VLAN TZ for Edge node uplinks. Isolates Edge traffic from host traffic.
Tier-0 Gateway — External Connectivity
Tier-0 (T0) gateway provides north-south routing between the NSX overlay and the physical network. T0 runs as a service router on NSX Edge nodes.
T0 HA Modes:
Active-Standby: One active Edge, one standby. Stateful failover (sessions preserved). Use when stateful services (NAT, firewall, VPN) are required.
Active-Active (stateless, ECMP): up to 8 Edge nodes forward concurrently with ECMP to the fabric. Only stateless services (reflexive NAT, stateless firewall) are supported in this mode; use it for high-bandwidth routing.
Stateful Active-Active (NSX 4.0.x onward; exam objectives 2.10.4 and 2.16.5): Edge nodes in the Tier-0 or Tier-1 are paired in sub-clusters with interface groups across their uplinks; flows are punted to the owning service router and connection state is synchronised, so stateful SNAT/DNAT and Gateway Firewall run while several Edges forward (VCF 9.0.1, Interface Groups; State Synchronization of Tier-0 Gateways; NAT on gateways).
Routing Protocols:
BGP: Preferred for enterprise deployments. T0 peers with physical ToR/spine switches via eBGP. Supports route redistribution (connected, static, NAT, LB VIPs, T1 connected subnets). Multi-hop BGP for non-directly-connected peers.
OSPF: Alternative to BGP. T0 participates in OSPF area. Suitable for environments where BGP is not permitted or physical switches only support OSPF.
Static Routes: Manual route entries. Simplest but no dynamic failover. Use for lab/small environments.
Tier-1 (T1) gateway provides routing for tenant/workload segments. T1 connects upstream to T0 for external access.
Design Patterns:
One T1 per workload domain: Simple, clean isolation between domains.
One T1 per application: Granular control. Each app (payroll, CRM, HR) gets its own T1 with dedicated NAT, LB, and firewall rules.
One T1 per tenant: Multi-tenancy. Each tenant gets isolated routing and services.
T1 Services:
NAT: SNAT (outbound masquerade) and DNAT (inbound service publishing). Configured per-T1.
DHCP: Local DHCP server on T1 or DHCP relay to external server.
DNS Forwarding: Conditional DNS forwarding rules on T1.
Load Balancing: L4/L7 load balancing on T1 (or Avi Load Balancer integration, which Broadcom recommends for general-purpose and advanced load balancing).
Gateway Firewall: Stateful firewall rules on T1 for north-south traffic inspection.
Route Advertisement: T1 advertises its connected subnets, NAT IPs, and LB VIPs to T0. T0 then redistributes to physical network. This chain enables end-to-end reachability: Physical → T0 → T1 → Overlay Segment → VM.
NSX Edge Cluster Design
Edge Cluster: Logical grouping of Edge nodes that host T0 and T1 service routers.
Sizing Guidelines (VCF 9.0.1, NSX Edge VM Resource Requirements; sizes are by total throughput and feature band, not a per-VM cap):
Small 2 vCPU/4 GB: proof-of-concept only; L7 rules on a Tier-1 are not realised.
Medium 4 vCPU/8 GB: L2-L4 services (NAT, routing, L4 firewall, L4 LB) under 2 Gbps total.
Large 8 vCPU/32 GB: 2-10 Gbps total, plus L7 load balancer and TLS inspection. Holodeck and most VCF management-domain Edge clusters use Large.
Extra Large 16 vCPU/64 GB: above the Large band — L7 LB, VPN, URL filtering, IDS/IPS, malware prevention.
Bare metal: minimum 8 cores/32 GB, recommended 24 cores/256 GB, for multi-100G or small-packet workloads; needs AES-NI and 1 GB huge pages for DPDK.
Edge Placement Anti-Affinity: Edge VMs must run on separate ESXi hosts (anti-affinity rules). Edge VMs should NOT run on the same hosts as workload VMs if possible (dedicated Edge cluster recommended for production).
Edge Uplink Design: Each Edge node has uplink interfaces connected to VLAN TZ segments that connect to physical ToR switches. Redundant uplinks to two ToR switches for HA. BGP peering from both uplinks for ECMP load distribution.
Key Takeaways
Overlay segments use GENEVE encapsulation (UDP 6081). VLAN segments use 802.1Q tagging. Transport zones control segment visibility across hosts.
T0 gateway: north-south routing on Edge nodes. HA modes: Active-Standby (stateful), Active-Active ECMP (stateless, up to 8 Edges) and Stateful Active-Active (interface groups + state sync; stateful NAT and Gateway FW with multiple active Edges). BGP preferred for enterprise, OSPF as alternative.
T1 gateway: per-tenant/workload routing with NAT, DHCP, DNS, LB, Gateway FW services. One T1 per domain/app/tenant depending on isolation requirements.
BUM handling: Hierarchical Two-Tier (default, VCF-recommended) or Head replication, set per segment; choose by TEP-subnet layout, not host count. Hybrid/multicast modes were NSX-V.
NSX Security Services, VPC, & Advanced Features in VCF 9.0#
NSX (NSX 9.0 in VCF 9.0; NSX 4.2 for the 2V0-41.24 exam) provides Projects and Virtual Private Cloud (VPC) constructs and security services beyond basic DFW and Gateway FW.
Virtual Private Cloud (VPC) in NSX
VPCs (introduced in the NSX 4.1.x line, with multi-tenancy and VPC enhancements in NSX 4.2.0 per its release notes, and extended in NSX 9.0) provide self-service network isolation for tenants within a VCF environment.
VPC Architecture: A VPC is created under an NSX Project. Each VPC gets its own isolated network space with: private IP subnets (RFC 1918), NAT gateway for external access, security policies (DFW rules scoped to VPC), and load balancer instances.
VPC: Tenant self-service. Tenant creates subnets within their VPC allocation. NSX handles underlying segment, T1, and NAT configuration automatically.
Use Case: Multi-tenant environments where each team needs isolated networking without requiring NSX skills.
NSX Projects: Organizational boundary for VPCs. A Project maps to a team or business unit. Projects use the system default overlay transport zone. Project admin can create VPCs, subnets, and security groups within their project scope.
Security Intelligence & VCF Operations for Networks
Security Intelligence (formerly NSX Intelligence, renamed in NSX 4.2; a vDefend capability): Analytics platform for network visibility:
Flow Visualization: Real-time and historical flow graphs showing VM-to-VM communication.
Recommendation Engine: Suggests DFW rules based on observed traffic patterns.
Security Posture: Dashboard showing unprotected VMs, open ports, and recommended segmentation.
Micro-Segmentation Planning: Automated discovery of application boundaries from flow data.
VCF Operations for Networks (formerly Aria Operations for Networks / vRealize Network Insight):
DR with consistent network policy: Same DFW rules at both primary and DR site.
Active-active datacenters: Workloads at both sites share network identity (same IP/MAC).
Workload mobility: vMotion or HCX migration between federated sites without network reconfiguration.
Limitations: latency between the Global Manager and each location must be 500 ms or less for non-stretched networks, or 150 ms or less for stretched networks (VCF 9.0.1 docs p.2301); routed L3 connectivity between sites is sufficient. Place the active and standby Global Manager clusters in different locations. GM failure doesn't affect local LM operations (LMs continue independently). Stretched segments add complexity — plan BUM traffic handling and failure domain isolation carefully.
NSX Service Insertion
Service Insertion: Allows third-party network services (Palo Alto, Fortinet, Check Point) to be inserted into the NSX data path without changing the network topology.
Architecture: NSX redirects selected traffic to a partner service appliance for inspection, then returns it to the original path. Configuration: define service chain (which appliances, in what order), attach to DFW rules via service profiles.
Use Case: Organizations that require specific vendor firewalls for compliance but want to leverage NSX for transport and micro-segmentation.
NSX Load Balancing
Native NSX Load Balancer (still in the 2V0-41.24 scope): L4 (TCP/UDP) and L7 (HTTP/HTTPS) load balancing on T1 gateways. In VCF 9.0 general-purpose load balancing with the built-in NSX load balancer is no longer part of the VCF entitlement (it remains entitled for VCF infrastructure components and Layer 4 load balancing for vSphere Supervisor), and Broadcom recommends Avi Load Balancer (VCF 9.0.1 docs p.235; announced in the NSX 4.2.0 release notes).
Virtual Server: VIP + port + pool + health monitor.
Pool: Group of backend servers with load distribution method (round-robin, least-connection, IP-hash).
Health Monitor: HTTP/HTTPS/TCP/UDP/ICMP checks against pool members.
VMware Avi Load Balancer (formerly NSX Advanced Load Balancer): For general-purpose and advanced L7 requirements: WAF (Web Application Firewall), SSL offload, content-based routing, real-time analytics, autoscaling. Deployed as Avi Controller + Avi Service Engine (SE) VMs. Integrated with NSX and VCF Automation.
Key Takeaways
VPC (NSX 4.1.x onward, NSX 9.0 in VCF 9.0): Self-service network isolation for tenants. VPCs are created under NSX Projects. Each VPC gets private subnets, NAT, security policies, and LB — without requiring NSX expertise.
NSX Federation: Global Manager (cross-site policy) + Local Managers (per-site execution). Enables stretched segments and consistent DFW policies across datacenters.
Security Intelligence (formerly NSX Intelligence, part of vDefend) provides flow-based micro-segmentation recommendations. VCF Operations for Networks provides cross-platform path analysis and change tracking.
NSX LB: Native L4/L7 on T1 gateways (general-purpose use no longer in the VCF 9.0 entitlement; Broadcom recommends Avi). Avi Load Balancer (formerly NSX Advanced Load Balancer) for general-purpose and advanced needs (WAF, analytics, autoscaling).
DPU-based acceleration — vSphere Distributed Services Engine — offloads NSX datapath work from the host CPU onto a SmartNIC/DPU. SCOPE THE DFW-ON-DPU CONTENT TO NSX 4.x: see the EOL note at the end.
WHAT IS OFFLOADED (verbatim from the NSX 4.0.1.1 release notes)
├── Networking: overlay and VLAN segments, distributed IPv4/IPv6 routing, NIC teaming across DPU ports
├── Security (Tech Preview at 4.0.1.1): Distributed Firewall, Distributed IDS/IPS
└── Visibility & Ops: Traceflow, IPFIX, packet capture, port mirroring, statistics — plus UPT v2
VERSION PROGRESSION
├── NSX 4.1.0: DFW-on-DPU and UPT v2 promoted to GA
├── Distributed IDS/IPS on DPU: NEVER left Tech Preview
└── NSX 4.2.0: dual-DPU support (active/standby and active/active), superseding the earlier one-DPU-per-host limit
REQUIREMENTS
vLCM-managed cluster; vSphere 8.0+; NSX Enterprise Plus per-core licensing; Enhanced Data Path (EDP) host-switch mode; a supported NVIDIA BlueField-2 (25G, 100G from 4.1.1) or AMD Pensando (25G/100G) DPU.
END OF LIFE — DFW ON DPU IN VCF 9.x
vDefend 9.0 announces End of Life for the vDefend Distributed Firewall for Data Processing Units (SmartNICs/DPU) (VMware vDefend 9.0 Release Notes), foreshadowed in NSX 4.2.3, whose release notes deprecate the DFW engine embedded in DPUs and keep it supported until NSX 4.2 end of support.
Be precise about the distinction: the EOL covers the DFW engine running in the DPU, while networking offload is still documented in VCF 9.0 — vSphere Distributed Services Engine offload, IPFIX on a DPU-backed VDS (vmknic on the 'ops' TCP/IP stack, VCF 9.0.1 docs p.2494) and ERSPAN on a DPU-backed VDS (full offload on AMD Pensando, partial on NVIDIA BlueField, p.2496); the VCF 9.1.1 release notes also carry a dual-DPU known issue. NSX Edge VM datapath interfaces can use Uniform Passthrough (UPT) (p.2056).
Design caveat: VCF domain and cluster creation workflows treat DPU-backed NICs as regular NICs, so network offloading is not available on hosts used that way (known issue, p.265).
Key Takeaways
DPU offload (vSphere Distributed Services Engine) covers overlay/VLAN segments, distributed routing, NIC teaming, Traceflow, IPFIX, packet capture, port mirroring and statistics; DFW-on-DPU went GA in NSX 4.1.0 while Distributed IDS/IPS on DPU never left Tech Preview.
Requires a vLCM cluster, vSphere 8.0+, EDP host-switch mode, NSX Enterprise Plus per-core licensing, and a supported NVIDIA BlueField-2 or AMD Pensando DPU. NSX 4.2.0 added dual-DPU (A/S and A/A).
Scope DFW-on-DPU to NSX 4.x: vDefend 9.0 declares EOL for the DFW-in-DPU engine. Networking offload on DPU-backed VDS (IPFIX, ERSPAN) and Edge UPT are still documented in VCF 9.0, but VCF domain/cluster workflows treat DPU NICs as regular NICs (VCF 9.0.1 known issue).
Exam Mapping: 2V0-41.24 — NSX 4.x Network Virtualization Professional
See NSX 4.x Network Virtualization Professional exam blueprint for detailed objectives
NSX 4.x production uses vSphere Distributed Switch (VDS) with NSX preparation (converged VDS). Legacy N-VDS is deprecated. OVS and Nexus 1000v are not used.
The Management plane (NSX Manager cluster) handles desired state and API interactions. Data plane forwards packets. Control plane distributes forwarding tables.
Overlay Transport Zone defines scope where GENEVE overlay segments can exist and transport nodes participate. Not VLAN-backed, L3 routing, or firewall boundary.
In NSX 4.x, management and control planes are collapsed into the NSX Manager cluster. NSX Controller was separate in older versions. Edge handles data plane. vCenter manages compute.
TEPs receive IPs from NSX-managed IP Pool or DHCP configured in the Transport Node Profile. Not static vCenter assignment, HA heartbeat, or L2 broadcast.
BGP (or OSPF) peering on multiple uplinks, with the ECMP toggle on, gives equal-cost paths to the upstream routers and withdraws a failed path automatically (add BFD for fast detection) (VCF 9.0.1 docs p.1859, p.1878). Static routes can carry several next hops (p.1852), but they are not dynamic: with only static routes the service router stays up, so a failed next hop is removed only when a Static Route BFD Peer detects the failure (VCF 9.0.1 docs p.1879-1880: Configure NSX BFD; Static Route BFD Peer p.1880). DHCP relay and LACP serve different purposes.
NSX backup best practice: automatic scheduled file-based backups to SFTP plus on-demand before changes. Not 6-month manual, unsupported, or per-minute snapshots.
Minimum 1600 MTU required for GENEVE overlay (1700+ recommended, 9000 ideal). 1500 causes fragmentation. 9000 strictly and 2048 only are incorrect requirements.
When deploying an NSX Edge transport node, which form factor is REQUIRED to support advanced services like TLS inspection and high-throughput routing at scale?
Large or Extra Large (bare metal for highest performance)
Large or Extra Large Edge is required for advanced services like TLS inspection, IDS/IPS. Small and Medium lack resources. Not all sizes support all features equally.
BUM (Broadcast, Unknown unicast, Multicast) traffic is replicated to all TEPs with VMs on the segment using head-end replication. Not dropped, forwarded to Tier-0 only, or encrypted.
Same-host intra-segment traffic is handled by local in-kernel switching — no TEP encapsulation or external routing needed. Not ToR switch, Tier-1, or NSX Manager.
DR runs on every transport node providing local first-hop routing. Not Edge-only, legacy NSX-V only, or north-south only. It handles east-west traffic at the host level.
Spreading ECMP traffic across multiple Edge nodes needs an Active-Active Tier-0: in active-active mode traffic is load balanced across all members, while in Active-Standby all traffic is processed by one elected active member (VCF 9.0.1 docs p.1846). ECMP itself is enabled with the ECMP toggle in the Tier-0 BGP/OSPF settings (p.1859, p.1878). A single Edge or an Active-Standby SR still uses ECMP over its own two VLAN uplinks to two TORs (NSX Edge Uplink Redundancy, p.2054), but that does not spread traffic across Edge nodes. Preemptive is for failback.
VRF Lite provides multiple isolated routing tables on a shared Tier-0 for multi-tenancy without separate Edge deployments. Not VLAN trunk, DHCP pool, or IPSec.
Segment advertisement must be enabled on Tier-0 under Route Redistribution to advertise NSX segments via BGP. It doesn't happen automatically. Static routes only limits flexibility.
Tier-1 without Edge cluster association cannot host stateful services — NAT, Gateway FW, LB require Service Router on Edge. It won't run on ESXi hosts or physical routers.
Tier-0 gateway provides northbound connection to physical routers with BGP peering. Tier-1 connects to Tier-0. DLR is legacy. Service gateway is a different concept.
No Tier-1 to Tier-0 route advertisement: check route advertisement settings — Connected Segments, NAT IPs must be enabled. BGP isn't used between Tier-1 and Tier-0. MTU and Edge cluster are secondary checks.
Gateway Firewall runs on Tier-0/Tier-1 Service Routers on Edge nodes for north-south and inter-tier traffic. Not in ESXi kernel (that's DFW), NSX Manager, or VMware Tools.
NSX Distributed IDS/IPS is enforced in the hypervisor at the VM vNIC, inspecting east-west traffic. Not only north-south, not a physical appliance, not cloud-only.
An Identity Firewall rule uses which attribute for group membership?
HTTP cookies
MAC address only
Port number only
Active Directory group membership (AD groups synchronised into NSX through the AD/LDAP identity source; logins detected by Guest Introspection or Event Log Scraping)
Identity Firewall rules are determined by membership in an Active Directory group: NSX synchronises the configured OUs from the AD/LDAP identity source and learns user logins through Guest Introspection (thin agent) or Active Directory event-log scraping. VMware Identity Manager / Workspace ONE Access authenticates NSX UI and API users; it is not the IDFW membership path. Not MAC address, port number or HTTP cookies.
Route-based IPSec VPN uses a VTI (virtual tunnel interface) with routing to direct traffic, enabling dynamic routing over the tunnel. Policy-based uses selectors/ACLs instead.
Avi Load Balancer (NSX ALB) replaces the built-in NSX LB with advanced Layer 4-7 capabilities including real-time analytics, SSL offload, WAF, and GSLB. It does not replace the DFW — the DFW handles micro-segmentation while Avi handles application delivery. Avi is neither a routing protocol nor a storage policy.
DFW rules are evaluated in category order: Ethernet (L2) → Emergency → Infrastructure → Environment → Application. Ethernet handles L2 pre-filtering; among the L3/L4 categories, Emergency is processed first. This makes Emergency rules ideal for break-glass scenarios or quarantine overrides. They are not evaluated last, disabled by default, or limited to edge traffic.
NSX Groups with dynamic membership criteria allow workload grouping based on VM name, tag, OS type, or other attributes. This enables policy automation — when a VM matches criteria, it's automatically included. Static IP sets, vCenter folders, and resource pools lack this dynamic, tag-driven membership capability.
On an ESXi transport node, 'nsxcli -c get logical-switch <uuid>' displays the operational state of a specific logical switch including VNI, replication mode, and connected VMs. esxcli network commands are for standard networking, vmkload_mod lists kernel modules, and net-dvs shows DVS internals but not NSX logical switches.
Traceflow injects a synthetic tagged packet that traverses the overlay path, showing exactly which segments, routers, and DFW rules it passes through. This is invaluable for troubleshooting connectivity. It does not benchmark throughput, capture production packets, or export BGP tables.
A freshly deployed NSX environment defaults to Allow — all traffic passes unless explicitly blocked. Best practice for zero-trust is to build out policies first, then change the default rule to Deny. It does not default to Deny, Reject, or Reflexive.
/var/log/proton/nsxapi.log contains the proton service logs capturing API requests, authentication events, and core management operations. /var/log/messages is a generic system log, nginx logs cover the reverse proxy layer, and vsan.log is for vSAN — not NSX.
When BGP is stuck in Idle, the first diagnostic is 'get bgp neighbor' on the Edge CLI to check neighbor state, then verify IP reachability (ping) and TCP/179 connectivity to the peer. Checking CPU temperature, NSX Manager disk, or vCenter inventory won't address BGP peering issues.
On an Edge transport node, 'get bfd-sessions' lists the BFD sessions to every remote TEP; state Up means the Geneve tunnel is healthy (VCF 9.0.1 pp.2042, 2787). On an ESX host use 'nsxdp-cli bfd sessions list'. 'show vpn' and 'show nsx cluster' are not NSX CLI verbs, and 'get interfaces counters' shows interface statistics, not tunnel state.
Syslog forwarding is configured in NSX Manager under System → Fabric → Profiles or System → Settings, pointing to the SIEM endpoint. Configuring only vCenter syslog misses NSX-specific events. DFW logs alone are insufficient, and DNS zone transfers are unrelated.
Traceflow provides end-to-end packet-level visibility between two workloads, showing the exact path through overlay segments, DFW rules, and routing components. Port mirroring captures all traffic (not targeted), ESXi ping tests basic connectivity only, and vCenter charts show metrics not packet paths.
NSX Manager support bundles are collected from the NSX Manager UI → System → Support Bundle, gathering logs from the management and control planes. They are not collected from vCenter alone, individual ESXi hosts, or Aria Operations.
On the Edge CLI, list the logical routers (get logical-routers), enter the Tier-0 SR VRF context (vrf <id>) and run get bgp neighbor summary to see the BGP peer state; get bgp neighbor <ip> advertised-routes shows what is advertised (VCF 9.0.1 docs p.2784). The other commands either don't exist or use incorrect syntax for the NSX Edge CLI.
VMware's overarching vision for a software-defined networking layer connecting any endpoint (VM, container, bare-metal) across any cloud with consistent policy. NSX is its principal implementation. It emphasizes decoupled, distributed network and security services that travel with workloads.
Management Plane
The NSX tier that receives API and UI input, validates configuration, and stores intent in the policy database. It runs on the NSX Manager cluster nodes. The plane never forwards user data packets.
Control Plane
The NSX tier responsible for distributing runtime state — forwarding tables, TEP lists, DFW rules — from the policy database to every transport node. It is split between central and local control components inside NSX Manager and on each ESXi host. It operates independently of the data path.
Data Plane
The NSX tier that performs actual packet forwarding and enforcement on transport nodes: ESXi hosts, Edge nodes, and bare-metal servers. It implements segments, Tier gateways, DFW, and tunnels. Data-plane health is the direct determinant of user-visible network behavior.
N-VDS
N-VDS (NSX-managed Virtual Distributed Switch): an NSX-owned virtual switch historically used on ESXi for NSX and still used on bare-metal Edge nodes and non-vSphere hosts. N-VDS on ESXi is deprecated; VCF/NSX deployments from NSX 3.x onward use VDS-based transport so NSX and vSphere share the same switch.
VDS-Based Transport
The default NSX deployment model on vSphere 7.0+ where a standard vSphere Distributed Switch carries NSX traffic and hosts are prepared as transport nodes without a separate N-VDS. It simplifies operations and allows VMs to sit on NSX segments via the same switch used for VDS port groups.
DPU-Based Acceleration
An NSX data-plane offload mode where networking and security processing moves to a Data Processing Unit (SmartNIC) on the ESXi host. It frees CPU cycles and provides deterministic low-latency forwarding for demanding workloads. DPU support is explicit per NIC model in the HCL.
NSX Policy API
The modern declarative NSX REST API under /policy/api/v1 where administrators push a desired state (segments, gateways, security). Supersedes the legacy Manager API (/api/v1). All modern NSX automation targets the Policy API.
Desired State Model
The NSX behavior in which the Policy API stores intent and the control plane reconciles it with the data plane. Failed realization surfaces as a Realization Alarm on the affected object. Pull-based reconciliation makes NSX self-healing for most transient issues.
Corfu Database
The distributed, log-structured datastore inside the NSX Manager cluster that stores configuration and state. Runs on the three-node Manager cluster using Paxos-like quorum. Health visible via 'get cluster status' on an NSX Manager.
NSX Manager Cluster
A three-node NSX control and management appliance cluster deployed with a cluster VIP for API/UI access. It requires low-latency network between nodes and provides HA for management and central control plane. Production deployments always use three nodes, never one.
Transport Node VIB
The NSX kernel module package installed on ESXi to enable overlay, distributed routing, and DFW. Installation is performed by NSX Manager when the host is prepared as a transport node. A failed VIB install is a common first-day issue and blocks segment attachment.
Host Transport Node
An ESXi host prepared with NSX VIBs and TEP VMkernel interfaces so it can originate and terminate overlay tunnels. Host transport nodes run the distributed router and DFW for local VMs. They are grouped into transport zones to define their reachability scope.
Edge Transport Node
An NSX Edge — VM or bare-metal — that runs the service router (SR) and centralized services such as NAT, VPN, and LB. Edge transport nodes sit in transport zones and are grouped into Edge clusters. They are the north-south hinge between NSX overlays and the physical network.
IP Pool (TEP)
A range of IP addresses allocated for TEP VMkernel interfaces on transport nodes. Each prepared host leases one IP per uplink. Exhaustion blocks new host preparation and is a typical scale-out blocker.
NSX RBAC with vIDM
The integration of NSX with an identity provider for SAML/OIDC-based authentication and role mapping. In VCF 9 this is primarily via the VCF Identity Broker (legacy deployments used Workspace ONE Access / vIDM). Maps AD or IdP groups to NSX roles such as Enterprise Admin or Auditor. Local NSX users are retained as break-glass accounts.
NSX Backup Configuration
The scheduled export of NSX Manager cluster state to an SFTP server, covering policy, certificates, and runtime configuration. Backups are the only supported recovery path for NSX Manager corruption. Restore requires an empty Manager of the same version.
Edge VM Form Factors
NSX Edge VM sizing options: Small (lab), Medium (~2 Gbps services), Large (~10 Gbps with services), and Extra Large (bare-metal-class). Changing form factor requires redeployment. Size drives CPU/memory/NIC allocation and is a design commitment.
Compute Manager
An NSX Manager registration of a vCenter so NSX can discover hosts, prepare clusters, and deploy Edge VMs. One Compute Manager per vCenter. Registration uses vCenter thumbprint verification and dedicated service credentials.
NSX Manager Cluster VIP
A virtual IP floating across the three NSX Manager nodes so clients reach the cluster via one endpoint. Only the active node holds the VIP; failover is seconds on node failure. Requires all three nodes in the same subnet.
Segment
The NSX policy-plane object representing a logical Layer 2 broadcast domain, either overlay-backed (Geneve) or VLAN-backed. Each segment binds to a transport zone and optionally to a Tier-1 gateway for routing. It is the primary attachment point for VM vNICs in NSX.
Segment Profile
A reusable configuration bundle applied to segments controlling security (SpoofGuard, MAC learning), QoS, IP/MAC discovery, and DHCP. Profiles enforce consistent defaults across many segments. They replace per-segment manual tuning and support policy-driven provisioning.
MAC Learning
A segment-profile feature that lets NSX learn MAC addresses behind a VM vNIC, required for nested hypervisors and promiscuous workloads. Without MAC learning, traffic destined for learned MACs is dropped. It is enabled only where needed because it increases resource use.
BUM Traffic Handling
The way NSX forwards Broadcast, Unknown unicast, and Multicast traffic on overlay segments using either head-end replication (source TEP sends copies) or hybrid replication with the physical network. Choice affects underlay load and convergence on large segments. It is configured per transport zone.
L2 Bridge
An NSX service that extends a VLAN-backed network into an overlay segment, typically used during migration or to connect physical appliances. The bridge runs on an Edge node or an ESXi host bridge profile. It is a Layer 2 join, not a Layer 3 router, so both sides share the subnet.
Overlay Packet Walk
The sequence a frame traverses when two VMs on different hosts communicate on the same overlay segment: DFW check, Geneve encapsulation by source TEP, underlay routing, decapsulation by destination TEP, DFW check, delivery. Understanding the walk is the foundation of NSX troubleshooting.
SpoofGuard
A segment-profile security feature that rejects traffic whose source IP or MAC does not match the VM's learned binding, preventing impersonation attacks. It is particularly effective when combined with IDFW and micro-segmentation. It must be enabled explicitly per segment profile.
Segment VLAN ID
An attribute on a VLAN-backed NSX segment defining the 802.1Q tag carried on uplinks. Distinct from overlay segments, which use Geneve VNIs. Admins create VLAN segments for traffic that must exit NSX untunneled.
IP Discovery Profile
An NSX segment profile that enables ARP snooping, DHCP snooping, VMware Tools-based discovery, and duplicate-IP detection to learn VM IPs. Populates bindings used by SpoofGuard and the Identity Firewall. Tuned per-segment based on trust level.
Tier-0 Gateway
The top-of-stack NSX router that peers with physical infrastructure via BGP or OSPF and provides north-south connectivity. It can be shared by many Tier-1 gateways (tenants) and hosts Edge-node services such as NAT and VPN. HA modes are active-active ECMP or active-standby.
Tier-1 Gateway
A tenant-scoped NSX router that connects segments and provides local services (DHCP, DNS relay) before uplinking to a Tier-0. It can be fully distributed (DR-only) or add a centralized service router when services require it. It is the primary isolation boundary between tenants.
ECMP Routing
An NSX Tier-0 active-active behavior where multiple Edge nodes advertise the same route to physical peers, distributing north-south traffic in parallel. It scales throughput linearly up to the active node count. Stateful services are incompatible with ECMP and require active-standby.
VRF Lite
An NSX Tier-0 feature that creates multiple logical routing instances on a shared Tier-0, each with its own routing table and BGP peering. It supports multi-tenant isolation without dedicating a Tier-0 per tenant. It is a common compromise between cost and isolation.
Reflexive NAT
A stateless 1:1 NAT mode on NSX Tier-0/Tier-1 gateways (each NSX UI rule creates one stateless SNAT and one stateless DNAT). Because it uses no state table, it is the only NAT type supported on active-active (ECMP) Tier-0 gateways, where stateful SNAT/DNAT are unsupported due to asymmetric paths.
Gateway DHCP Service
An NSX-provided DHCP server or relay running on a Tier-0 or Tier-1 that leases IPs to VMs attached to segments. It supports pools, reservations, and custom options. It eliminates the need for external DHCP infrastructure in many tenant designs.
Route Redistribution
The NSX feature that imports connected segments, static routes, and NAT IPs into BGP or OSPF advertisements to the physical network. Incorrect redistribution is a frequent cause of unreachable VMs or routing loops. It is configured per Tier-0 with route maps.
HA Mode (T0)
Tier-0 availability choice: Active-Active (ECMP across up to eight Edges, stateless services only) or Active-Standby (one active Edge, full stateful services). Switching mode requires recreating the T0. Drives north-south throughput and feature availability.
Route Map
An NSX policy that filters or modifies routes on BGP neighbor sessions, using prefix lists and community matching. Used to enforce route acceptance/advertisement policy to upstream ToRs. Applied per-neighbor direction (in/out).
DFW Rule Table
The ordered, category-scoped list of distributed firewall rules evaluated on each vNIC for east-west traffic. Rules are evaluated top-down within a category, with first-match winning, and categories are evaluated left-to-right. Visibility into this table is central to DFW troubleshooting.
Security Group (NSX)
A dynamic or static collection of VMs, IPs, MACs, segments, or tags used as source/destination/applied-to in DFW and gateway firewall rules. Dynamic membership from tags enables policy that follows workloads automatically. It is the principal abstraction for micro-segmentation.
Identity Firewall (IDFW)
An NSX DFW capability that scopes rules to Active Directory users or groups instead of only IP/VM membership. It requires VMware Tools or Guest Introspection on Windows VMs to map user sessions to IPs. Typical use cases include VDI per-user access control.
Gateway Firewall Service Profile
A stateful filter configuration applied to Tier-0/Tier-1 north-south traffic, with rules specifying service (port/protocol), action, and logging. Unlike DFW, it runs on the Edge SR. It is the NSX equivalent of a traditional perimeter firewall.
Route-Based IPSec VPN
A tunnel type that uses a virtual tunnel interface (VTI) on the NSX Edge and relies on BGP or static routes to steer traffic into the tunnel. It is simpler to operate at scale than policy-based VPN because routing, not selectors, decides what is encrypted. It is the preferred model for site-to-site VPN in NSX.
L2 VPN
An NSX Edge service that extends a Layer 2 segment across an IPSec tunnel to a remote site, used for migration scenarios such as HCX Network Extension. It preserves VM IPs during cross-site moves. It should be treated as a migration tool, not a permanent architecture.
NSX ALB Integration
Integration between NSX and the Avi Load Balancer Controller (formerly NSX Advanced Load Balancer) for L4–L7 application delivery inside NSX networks. Avi is the recommended LB in VCF 9; the built-in NSX load balancer is deprecated and scheduled for removal. Integration is configured by adding NSX-T as a Cloud on the Avi Controller.
Distributed IDS/IPS
A Distributed Firewall extension running signature-based intrusion detection/prevention inline at each vNIC. Signatures update from Broadcom's threat feed. Requires NSX Advanced or ATP license; policies target security groups.
Malware Prevention
An NSX ATP service that inspects east-west and north-south files against known hashes and cloud-based sandboxing. Runs on the Service-Defined Firewall; requires NSX Advanced Threat Prevention. Integrates with Network Detection and Response.
NSX Syslog Export
The configuration that forwards NSX Manager and transport-node logs to an external syslog destination such as VCF Operations for Logs. It is mandatory for audit and security-incident analysis. It is set per appliance and requires the destination to accept high-volume UDP or TCP traffic.
/var/log/proton
The log directory on NSX Manager nodes where the core Proton management service writes its logs. Proton issues frequently manifest as API failures, slow UI, or cluster split-brain. It is always part of any support bundle.
get logical-switch CLI
An NSX CLI command that lists segments (logical switches) and their VNI, transport zone, and state on the queried node. It is the first check when a VM cannot reach others on the same segment. It is typically followed by get logical-port for vNIC-specific state.
Tunnel Status Check
The verification that each transport node has functional overlay tunnels to every peer in its transport zone, typically via the NSX Manager Fabric view or get tunnels CLI. Missing or down tunnels explain cross-host overlay failures. BFD state is the authoritative indicator.
Route Advertisement Failure
A symptom where a Tier-0 does not announce expected prefixes (connected segments, static routes, NATs) to upstream BGP peers. The cause is usually missing redistribution or an incorrect route map. It is diagnosed with get bgp neighbor advertised-routes on the Edge.
DFW Default Rule
The final rule in each DFW category, typically allow-all in Application and deny-all in Environment/Infrastructure depending on design. Misconfiguring the default rule to deny-all without exceptions is a frequent cause of platform-wide outages. Always log the default rule during rollout.
Edge Node Health
The composite status of an Edge covering CPU, memory, datastore, interface, and service states. VCF Operations tracks it continuously, and the NSX UI exposes per-Edge dashboards. Unhealthy Edges are evacuated from active-standby pairs automatically to restore service.
get cluster status
The NSX Manager CLI command reporting health of the manager cluster: group leader, member states, database replication. Must show all members 'CONNECTED' and databases 'ACTIVE'. Common first command during manager-plane troubleshooting.
IPFIX (NSX)
An NSX flow-export feature that samples east-west and north-south traffic on segments and DFW and exports to a collector. Used with vRealize Network Insight (VMware Aria Operations for Networks) for flow analytics. Independent of VDS IPFIX.
Was this page useful?Thanks — noted.
Type to search. ↑↓ to move,
Enter to open, Esc to close.