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 Architecture Deep Dive#

Three-Plane Architecture

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

┌──────────────────────────────────────────────────────┐
│                     ESXi Host 1                      │
│  ┌────────────────────────────────────────────────┐  │
│  │ VMs: Web VM, App VM (on Overlay Segment)       │  │
│  └─────────┬──────────────────────────────────────┘  │
│            │ vNIC traffic                            │
│  ┌─────────▼──────────────────────────────────┐      │
│  │  VDS 7.0+ with NSX (ESXi host switch)      │      │
│  │  • DFW rules applied (kernel)              │      │
│  │  • Geneve encapsulation (overlay)          │      │
│  └─────────┬──────────────────────────┬───────┘      │
│            │                          │              │
│  ┌─────────▼────┐           ┌─────────▼────┐         │
│  │ TEP NIC 1    │           │ TEP NIC 2    │         │
│  │ 192.168.1.11 │           │ 192.168.2.11 │         │
│  └──────────────┘           └──────────────┘         │
│                                                      │
│         TEP (tunnel endpoint) uplinks                │
│         to physical leaf switches                    │
└──────────────────────────────────────────────────────┘

N-VDS:

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)

Geneve encapsulation:

Geneve protocol (overlay) encapsulates logical packets in physical underlay. Header: IP(src=TEP_A, dst=TEP_B)/UDP(6081)/Geneve

TEP redundancy:

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

NSX Edge Nodes

NSX Edge provides gateway services (Tier-0, Tier-1), VPN, load balancing:

Bare metal edge:

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.

Understand Management/Control/Data plane separation

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.
  • Segment Security: BPDU filter, DHCP server/client blocking, rate limiting for broadcast/unknown-unicast/multicast (BUM) traffic.

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.

Route Redistribution: Controls which routes T0 advertises to the physical network. Options: Connected subnets (T0 interfaces), T1 connected (subnets behind T1 gateways), NAT IPs, LB VIPs, static routes, IPSec VPN subnets.

Tier-1 Gateway — Tenant/Workload Routing

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 vs Traditional Segments:

  • Traditional: Admin creates segments, T1 gateways, DFW rules manually. Requires NSX expertise.
  • 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):

  • Cross-Platform Visibility: Network topology across NSX, physical switches, AWS VPC, Azure VNet.
  • Path Analysis: End-to-end path from VM to external endpoint showing every hop, rule, and latency.
  • Change Tracking: Audit trail of all NSX configuration changes with before/after comparison.
  • Troubleshooting: Correlate network events with VM performance metrics from VCF Operations.

NSX Federation

NSX Federation enables consistent network and security policy across multiple NSX Manager instances (typically across datacenters).

Architecture:

  • Global Manager (GM): Central policy manager for federation. Deploys as 3-node cluster (separate from local NSX Managers).
  • Local Manager (LM): Per-site NSX Manager cluster. Executes policies received from GM.
  • Stretched Segments: L2 segments spanning multiple sites via GM coordination. VMs on same segment at different sites communicate at L2.
  • Stretched T0 Gateway: T0 spanning multiple sites for consistent north-south routing.

Federation Use Cases:

  • 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.
  • Persistence: Source IP, cookie-based session persistence.

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 (NSX 4.x scope)#

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

Labs in This Section

📝 Quiz — Network Virtualization 4.x

0/55 correct

Section 1 — Architecture and Technologies

Q1
NSX data plane components for transport nodes in NSX 4.x production are based on:
  • A standalone OVS bridge
  • Only the legacy N-VDS
  • Cisco Nexus 1000v
  • vSphere Distributed Switch (VDS) with NSX preparation (converged VDS)
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.
Q2
Which NSX plane is responsible for maintaining desired state and API interactions from users/scripts?
  • Management plane (NSX Manager cluster)
  • Control plane
  • Forwarding plane
  • Data plane
The Management plane (NSX Manager cluster) handles desired state and API interactions. Data plane forwards packets. Control plane distributes forwarding tables.
Q3
An NSX Manager cluster for production deployment typically consists of:
  • 2 nodes with active-passive
  • 5 nodes minimum
  • 1 node
  • 3 nodes behind a VIP for high availability
Production NSX Manager cluster: 3 nodes behind a VIP for high availability and quorum. 1 or 2 nodes lack HA. 5 is excessive.
Q4
GENEVE encapsulation in NSX overlay networking uses which IP protocol and default destination port?
  • TCP 443
  • GRE (protocol 47)
  • UDP 4789
  • UDP 6081
GENEVE encapsulation uses UDP port 6081. TCP 443 is HTTPS management. UDP 4789 is VXLAN (legacy). GRE protocol 47 is different encapsulation.
Q5
A Transport Zone of type 'overlay' provides:
  • VLAN-backed switching only
  • A firewall boundary for DFW
  • A Layer 3 routing domain
  • The scope where overlay (GENEVE) segments can exist and transport nodes can carry them
Overlay Transport Zone defines scope where GENEVE overlay segments can exist and transport nodes participate. Not VLAN-backed, L3 routing, or firewall boundary.

Section 2 — Installation and Configuration

Section 3 — Logical Switching

Section 4 — Logical Routing

Section 5 — Security Services

Section 6 — Operations and Troubleshooting

🃏 Flashcards — Network Virtualization 4.x

56 cards
Card 1 of 56
Virtual Cloud Network
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.
Was this page useful?
Type to search. ↑ ↓ to move, Enter to open, Esc to close.