Gabe Rosas

Nailing EDP Versioning (a VCF Tech Paper Preview)

I’ve been spending a lot of time lately in the weeds of our upcoming Understanding EDP Standard Tech Paper. It’s a deep dive into the network stack architecture we’re all building on in VCF, but I wanted to pull a specific section out today to share with you all.

Getting your versions right—especially when it comes to EDP Standard—is the best way to ensure a predictable, high-performance environment. Here’s a look at what we’re recommending for the VCF 5.2.x and 9.0.x lifecycles.

VCF 5.2.x: Maximizing Performance

If you’re on VCF 5.2.x, EDP Standard is technically optional, but if you’re looking for high-performance networking or long-term architectural future-proofing, it’s the way to go.

Because of the precise coordination required between CPU scheduling, NIC drivers, and firmware, staying on the latest validated release is the most reliable path to a great outcome.

  • The Recommended Baseline (April 2026): Aim for vSphere 8.0 Update 3i & NSX 4.2.3.2.
  • The Benefit: This combination includes important stability patches and performance optimizations, particularly for environments utilizing Network I/O Control (NIOC). It also streamlines the enablement process within NSX.

A Note on the Legacy Baseline: vSphere 8.0 U3e and NSX 4.2.2.1 are the minimum requirements for EDP. While these work well for dedicated NSX Edge clusters, I recommend moving to the newer releases for general-purpose compute clusters to take advantage of the most recent refinements.

VCF 9.0.x: Streamlined Implementation

In VCF 9.0.x, EDP Standard moves from an option to the foundational architecture. The transition is now handled through a unified orchestration framework, which significantly reduces manual overhead and operational steps.

What to Expect During Deployment

  • New Deployments: EDP Standard is now the default virtual switch mode, ensuring you get optimal throughput from day one.
  • Upgrading from 5.2.x: Your existing datapath state is preserved. If you are currently running the legacy stack, you’ll stay there until you’re ready to explicitly transition.
  • Consistency: If you’ve already made the move to EDP Standard in 5.2.x, that configuration remains solid and unchanged throughout the upgrade process.

Modern Tools: TNP and VCP

We’re moving toward a more robust mechanism for datapath transitions, moving away from legacy CLI-based scripts in favor of built-in automation:

  1. The Activation Trigger (TNP): The NSX Transport Node Profile acts as the administrative trigger. By updating the TNP settings to “Enhanced Datapath – Standard,” you communicate the architectural intent to the whole cluster.
  2. The Orchestration Engine (VCP): When vSphere Configuration Profiles (VCP) are enabled, VCF leverages this framework to do the heavy lifting—placing hosts into maintenance mode and applying changes sequentially to maintain high availability for your VMs.

The Pre-Flight Checklist: Driver Minimums

Before you start flipping switches in your TNP, you need to make sure your underlying hardware is ready for the ride. EDP Standard relies heavily on specific driver capabilities to offload and accelerate that traffic.

If you are running any of these common NIC families in your hosts, you must hit these minimum driver versions to ensure stability and performance:

  • Broadcom NetXtreme-E (BCM574xx series)
    • Driver: bnxtnet
    • Minimum Version: 233.0.31.0
  • Intel E810 Series (10/25/100GbE)
    • Driver: icen
    • Minimum Version: 2.2.2.0
  • Intel 700 Series (X710/XL710/XXV710)
    • Driver: i40en
    • Minimum Version: 2.11.1.0
  • Marvell FastLinQ (QL41xxx / QL45xxx series)
    • Driver: qedentv
    • Minimum Version: 3.71.80.0
  • Mellanox/NVIDIA ConnectX Series
    • Driver: nmlx5_core
    • Minimum Version: Use Inbox driver

Quick Tip: Always double-check the Broadcom Compatibility Guide (BCG) against your specific server OEM’s custom ISO and firmware baseline. Hitting the minimum driver version is great, but you need to make sure your firmware is updated to match!

A Personal Note

I wanted to share some personal news. My father passed away a couple of weeks ago. I traveled back to Mexico yesterday to grieve with my family, to be there for his burial and the novena. If you are reading this today and your father is not yet resting, I would love it if you gave him an “I love you” call!

Writing and sharing technical insights has always been a great outlet for me, and I’m looking forward to getting the full Technical Paper out to you all very soon. Thank you for being part of this journey with me.

~
Gabe 🖖🏼😔

🕊️ Roberto Rosas Raya 1954 – 2026

Leave a comment