VCF 9 Network Planner BETA
FR EN

Global Configuration

VCF Management Services — 5 FQDNs + /28 runtime block Fleet Appliance — 1 FQDN
% overhead on all recommended CIDRs
Optional — used as placeholder in Appliances & VIPs tabs to pre-fill FQDNs (hostname.suffix)
Optional prefix added before appliance name in FQDNs

Basic Configuration

NSX Configuration

VKS / Kubernetes

VKS Infrastructure VLAN: 5 IPs (recommended contiguous block) — 3 control plane VMs + 1 floating IP + 1 patching IP. Workload network, AVI VIP pool, and ingress/egress/pod CIDR ranges are separate.
NSX VPCs

Additional Services

No additional services configured.
📌 Current model: —
📌 Current model: —
📌 Current model: NSX VLAN Segment —
📌 Current model: NSX Overlay Segment —
1 FQDN required (lowercase) — e.g.: vcf-ops-proxy.vcf.domain.local 1 FQDN required (lowercase) — e.g.: vcf-license.vcf.domain.local
Instance-level — always in Mgmt VM Network
3 active + 1 upgrade/patching node
1 (standalone) or 3 (HA)

Workload Domains

No workload domains configured. Click "+ Add Workload Domain" to start.

VLAN Design

Auto-calculated from configuration — enter VLAN IDs and CIDRs below
Domain VLAN Name VLAN ID CIDR Req. IPs Rec. CIDR Mandatory Scope Notes

Appliance Allocation

Auto-generated — fill in IP addresses and FQDNs
Appliance Name Type Domain VLAN IP Address FQDN Static Notes

Virtual IP (VIP) Allocation

Auto-generated — fill in IP addresses and FQDNs
FQDN suffix: — placeholders pre-filled.
VIP Name Service Domain VLAN IP Address FQDN Notes
Validation Results ✓ No Blockers
✓ No validation issues found — configuration looks good!

Export & Import

Excel Export

Export a full planning workbook with 5 sheets:
Domain Summary · VLAN Summary · Appliance Allocation · VIPs · Validation Report

JSON Save / Load

Export or restore the full planner state as a JSON file.
All configuration, IP assignments, and FQDNs are preserved.

Project Statistics

VLANs
Appliances
VIPs
Blockers

Project Info

Project Name
Customer
Scenario
Deployment
Workload Domains

VCF Components — IP & FQDN Requirements

Click a component to see how many IPs and FQDNs it needs for the current project configuration. Reference figures sourced from VCF 9.1 IP/FQDN prerequisites.

Per VCF 9.1 design guidance, each Workload Domain is its own Layer-2 network domain / network pool: ESXi management, vMotion, vSAN and NSX Host TEP IPs for a workload domain are not drawn from the Management Domain's VLANs. The figures below are shown per domain accordingly — see the Dedicated VLANs option per workload domain on the VLAN Design tab.

Management Domain

Click a component to see details.

Project totals
VCF 9 Network Planner
Architecture Edition — Pre-Deployment Network Planning Tool
Jun 2026 BETA VMware Cloud Foundation 9
Designed & Developed by
Leonardo Coscia
Senior VMware Cloud Foundation Architect

Disclaimer

This tool is a community conversion of the official Broadcom workbook. Always cross-check values against the official VCF 9.1 documentation before deployment.

Purpose

The VCF 9 Network Planner automates the pre-deployment network design process for VMware Cloud Foundation 9 deployments. It replaces manual spreadsheet workflows with a single, self-consistent planning document.

From a handful of configuration choices, the tool derives the complete set of VLANs, appliance IP allocations, VIPs, and runs architectural validation — ready for export to Excel or JSON.

Version History

Version Date Notes
v1.8.0 Jun 2026
v1.7.2 Jun 2026
v1.7.1 Jun 2026
v1.7.0 Jun 2026
v1.6.1 Jun 2026
v1.6.0 Jun 2026
v1.5.1 Jun 2026
v1.4.0 Jun 2026
v1.3.0 Jun 2026
v1.1.0 Apr 2026
v1.0.0 Apr 2026 Initial release — full HTML, Alpine.js, Supabase auth, VCF-DD design

Capabilities

Technology Stack

VCF 9 Network Planner  ·  Designed for VMware Cloud Foundation 9 pre-deployment architecture  ·  © 2026 Leonardo Coscia