Workload Domains now count fully — and visibly — toward the sizing totals

A user reported that the Management Domain Sizing totals seemed to include something they couldn't see or adjust in detail. Turned out to be accurate: the Workload Domains count was already adding its per-domain vCenter + NSX Manager vCPU and RAM to the totals, but never added disk (the lookup data existed and was simply unused), and had no line item in the sizing breakdown table — so it silently moved the totals with zero explanation. Disk is now included in the calculation, a dedicated "Workload Domain vCenter/NSX" row appears in the breakdown once the count is above zero, and a new WLD vCenter Size selector (previously hardcoded to Small) lets you match it to your actual deployment. Also relabeled the Cloud Proxy breakdown row to "VCF Operations — Cloud Proxy" for consistency with the other VCF Operations rows, since its plain name made it easy to overlook when auditing "VCF Ops" numbers.

Fixed Excel Workbook import — was writing wrong values into the form

Testing against a real Broadcom workbook export revealed that the Excel import (introduced in v1.1.9) was writing incorrect values into several fields — its cell mapping targeted the wrong column on "Deploy Management Domain" (D instead of the real "Your Value" column, L) and, on "Configure Management Domain", several fields pointed at a "Select Option / Feature / Final Result" summary table instead of real input cells, producing garbage like supervisorCidr = "Microsoft". core/excel-import.js's EXCEL_IMPORT_MAP has been rebuilt with ~45 cell coordinates verified directly against a real workbook export (label + sample value both checked per cell, cross-tested against both a blank and a filled-in copy); unverifiable fields (SFTP/CA toggles, NSX connectivity, vSphere Supervisor, and a few workbook-only concepts like the short SDDC hostname) were removed rather than left as guesses — they'll come back once their real input cells are located. The workbook's combined "Gateway (CIDR notation)" cell (e.g. 10.11.11.1/24) is now correctly split into the form's separate Gateway and network-CIDR fields, and the detected workbook version is read defensively from the "Version History" sheet's header row rather than a fixed cell.

Higher CPU oversubscription ratios (up to 4:1)

The CPU Oversubscription selector on the Management Domain Sizing page now offers 1:1 / 2:1 / 3:1 / 4:1, replacing the previous 1:1 / 1.5:1 / 2:1 range, per the workbook's v1.9.1.005 changelog ("Added additional CPU oversubscription rates in the Management Domain Sizing Tab") — confirmed against the workbook's own data validation list on that field (1.5:1 is no longer offered). Memory Oversubscription, a separate field in the workbook, is unchanged in this revision and remains outside this calculator's scope.

Aligned with workbook v1.9.1.005 (25 June 2026)

Broadcom's 25 June 2026 revision of the Planning & Preparation Workbook changes only one sizing value versus the prior v1.9.1.004 baseline: VCF Automation disk per node is corrected (Small 717 → 600 GB, Medium 334 → 900 GB, Large 430 → 1200 GB — verified directly against both workbook revisions, no column/tier inversion). No other lookup table, sheet, or validation list changed between the two revisions. tools/check_lt_constants.py now points at the v1.9.1.005 file and gained a dedicated vcfa check (previously the VCF Automation CPU/RAM/Disk table wasn't cross-checked against the workbook at all, even though the values were already in core/data.js).

Import an existing Planning & Preparation Excel workbook

A new Import Excel Workbook entry in the topbar's Import menu lets you pre-fill the form directly from an already filled-in Broadcom "VCF 9.1 Planning & Preparation Workbook" (.xlsx). Parsing happens entirely client-side (SheetJS, loaded from CDN with Subresource Integrity, pinned) — the workbook file is never uploaded anywhere, matching the tool's zero-network-requests-with-your-data promise. After import, a report panel lists every field as Applied, Skipped (empty cell / sheet not found) or Ambiguous (dropdown/toggle values applied without validation against the field's known options) so you can verify the result. This first iteration only covers the Deploy/Configure Management Domain pages, and its cell coordinates are uncalibrated placeholders — Broadcom's workbook file isn't distributed with this repo, so the mapping (core/excel-import.js) was built from the form's own field order rather than a real spreadsheet; always check the import report before trusting the result, and see the README's Development section if you want to help calibrate it against a real workbook.

Auto-generate-password toggles, per-portgroup VDS config & Feedback button

The vCenter Management Domain, NSX Edge and Workload Domain password fields gain dedicated Auto-Generate Password toggles (autoGenPw / nsxEdgeAutoGenPw / wldAutoGenPw), replacing the static "AUTO-GENERATED" placeholder with an explicit Selected/Unselected control that conditionally reveals the password field and omits the root vCenter password from the VCF Installer JSON export when auto-generation is selected — matching the workbook's own toggle. The Distributed Switch pages are brought to full workbook depth with a new per-portgroup configuration (name, load balancing, and Active/Standby uplink assignment for ESX Mgmt, VM Mgmt, VCF Mgmt, vMotion, vSAN and NFS traffic, plus the NSX overlay portgroup), and gain MTU, LAG and physical NIC uplink fields for the Primary/Secondary/Tertiary VDS sections. A new Feedback button in the topbar (all pages) opens a pre-filled GitHub issue (title, current app version, current page and browser user-agent) in a new tab for reporting problems or missing features — no data leaves the browser without the user's explicit submission on GitHub. Contributed by Paul van Dieen (ITQ; password toggles & portgroup config).

EVC Mode moved to day-2, aligned with vSphere 9.0 baselines

The EVC Mode field moved from the Deploy Management Domain "Cluster & Scale Options" to a new vSphere Cluster Settings section on the Configure Management Domain page — the VCF 9.x Installer offers no EVC selection during bring-up (verified against a real 9.1 deployment); EVC is applied post-deployment in vCenter (cluster → Configure → VMware EVC). The option list was rebuilt from the invented original (old Intel microarchs, "AMD EPYC Rome/Milan/Genoa" naming) to the actual vCenter 9.0 baseline names: Custom (new in vSphere 9.0), Intel "Skylake" through "Granite Rapids" Generation, and AMD "Zen" (Naples) through "Zen 5" (Turin) Generation. Intel baselines older than Skylake were dropped since those CPU families are discontinued in ESX 9.x; Skylake-SP itself was restored as supported (software support only) in the Broadcom Compatibility Guide on July 7, 2026. Same form key (evcMode), so saved plans keep their value. Contributed by Paul van Dieen (ITQ).

VCF Operations fillable at bring-up

The Deploy Management Domain page gains a VCF Operations section (deployment model, primary/replica/data node FQDN + IP, optional external load balancer, size, admin password). In VCF 9.1 the VCF Installer deploys VCF Operations fleet management during bring-up — the fields previously existed only on the Fleet Management Day-N page behind the "Deploy VCF Operations / Automation" selector, which defaults to Exclude, so a standard bring-up had nowhere to enter them. The VCF Installer JSON export now includes vcfOperationsSpec whenever the node fields are filled (Single Node mode exports the primary node only), the Day-N note no longer claims VCF Operations is Installer-unavailable, and the demo dataset covers the new section. Contributed by Paul van Dieen (ITQ).

ITQ brand redesign

Ported the visual layer of the claude.ai/design redesign onto index.html while keeping all logic and reference data in core/ (the single source of truth shared with the MCP server): new ITQ navy palette, Metropolis + Titillium fonts, a restyled top bar and sidebar, and an ITQ ↔ VMware brand toggle (heart button / Shift+B, persisted in localStorage). Emoji nav/page icons are now rendered as inline SVGs via a new iconSvg() helper — no nav data or core/ files changed. Contributed by Florian Casse (ITQ).

Aligned with workbook v1.9.1.004 (15 June 2026), credit contributors

Recalibrated vCenter disk tiers; the Supervisor Service Platform (SSP) moved from a Medium/Large/X-Large tier model to a fixed Excluded/Include toggle (8 nodes / 96 vCPU / 350 GB RAM / 3867 GB disk); License Hub disk corrected to 725 GB. VCF Operations/Automation deployment is now a single API-only select (Exclude / Deploy VCF Operations and Automation / Deploy VCF Automation), replacing the old independent Include/Exclude toggles, plus a new "Deploy Deferred Components (API-only)" section referencing the official VCF.JSONGenerator PowerShell module. tools/check_lt_constants.py now points at the new workbook and validates vcenter_disk_tiers. The About page now credits Florian Casse (MCP server & core refactor) and ITQ.

FQDN/IP prerequisites aligned with VCF 9.1 Components FQDNs and IP Addresses & Management Services design docs

The Fleet Management Day-N page's Log Management, Identity Broker, VCF Automation, and VCF Management Services sections were corrected against the official "VCF Components FQDNs and IP Addresses", "VCF Management Services in the First VCF Instance Model", "VCF Automation Network Design Options", and "VCF Operations for Logs Deployment Models" pages. Log Management now reflects 1 FQDN with all of its IPs (6 for the initial deployment, +2 per additional replica) drawn from the VCF Services Runtime IP block rather than separate Management VM Network / Fleet VLAN addresses — sample IPs moved from the 10.11.10.x range to the 10.11.99.x Runtime range, and the former "Load Balancer / Cluster VIP" fields are now labeled as an optional additional VIP on the same Integrated Load Balancer. VCF Management Services gains a clarified description and notes: the VCF Services Runtime IP block must sit on the VCF Management Network with a minimum of 12 IPs (/28) and up to 30 IPs (/27) recommended for Day-N scale-out (Log Management replicas, Real-time Metrics, etc.), and License Server is now explicitly called out as having its own FQDN/IP on the VCF Management Network, separate from the VCF Management Services FQDN set (Fleet Components, Instance Components, VCF Services Runtime, Identity Broker). Identity Broker gains a note that its single FQDN is one of the required First VCF Instance Day-0 FQDNs alongside that set. VCF Automation gains a new "Dedicated VCF Services Runtime FQDN/IP" pair (1 FQDN, separate from the fleet-level VCF Services Runtime) and the 5-address node IP pool notes are corrected to the documented /29 model — 3 IPs assigned to the VCF Automation 9.1 nodes plus 2 buffer IPs for redeploy/rolling updates, deployed by default on the VM management network or optionally on a dedicated VLAN via the fleet lifecycle API. All newly-documented FQDN fields gain a "Do not use capital letters in the FQDN (lowercase only)" note per the official requirement.

Audit fixes — sizing formulas & validation lists

A full multi-pass audit against the Excel workbook surfaced and fixed several residual divergences. Sizing calculator: Log Management is now computed per the workbook's row-26 formula (a new "Log Management Replicas" input — min 1 for Small / 3 for Medium-Large; the Large size deploys 2 nodes per replica; CPU/RAM per node from the VCFMS worker tier; disk = replicas × 575 GB) and gains the missing Large size, replacing both the previous flat estimates and the separate "Log Management Replicas" toggle; VCF Automation is now a single component computed from the per-node VCFA table × node count (×1 Small / ×3 Medium-Large), replacing the previous duplicate flat entry; Real-time Metrics scales with the Instance Profile Size (×2 nodes, ×3 for Large); Identity Broker now counts only its disk (the workbook excludes its CPU/RAM from every total); Software Depot disk corrected from 0 to 1500 GB; and the minimum host count now applies the workbook's 3-host vSAN quorum floor even for Simple deployments (previously 1-2 hosts could be shown for Simple + vSAN). Validation lists: the Deploy Cluster Teaming Policy gains "Route Based on Physical NIC Load", certificate Key Size fields gain 3072, Supervisor Control Plane Size gains XLarge, the management-domain vSAN FTT is restricted to 1-2 per the workbook, and the "NSX Connectivity Type" / "Transit Gateway Type" casing was corrected to match each field's actual workbook validation list (Title Case for NSX Connectivity, lowercase for Transit Gateway — the v1.1.1 change had matched the wrong cells). The two verification documents (tools/check_lt_constants.py, tools/sizing_scenarios.md) were re-run/updated accordingly.

Sizing calculator aligned with the Excel workbook

The Management Domain Sizing calculator's lookup tables and formulas have been re-verified line-by-line against vcf-9.1-planning-and-preparation-workbook-updated.xlsx ("Static Reference Tables" and "Management Domain Sizing" sheets) and corrected where they had drifted: SDDC Manager RAM (8 → 16 GB), NSX Manager (added Extra-Small tier, corrected XLarge), NSX Edge/VNA disk sizes (→ 200 GB) and VNA CPU/RAM, VCF Operations CPU/RAM/disk, AVI Load Balancer Large/Extra-Large, Cloud Proxy tiers (Small/Medium/Large), and a full rework of vDefend SSP into cluster-aggregate values plus a separate "vDefend/AVI Licensing Hub" add-on. The VCF Services Runtime (VCFMS) control/worker node sizing is now computed from node-count tables driven by Instance Profile Size, Cluster Model, and a new VCF Services Instance Model selector (First Instance / Additional Instance), matching the Excel's per-node × node-count + extra-disk formula. The disk-sizing chain (Required Hosts, Total Storage Required, Disk per Host) now follows the Excel's exact order of operations (interim total → FTT1 redundancy → ops reserve → growth), and Subnet Mask options now cover the full /32–/0 range (33 entries, was 24). New sizing components: VRMS, SRM, Health Reporting and Monitoring (HVM), Cloud-Based Ransomware Recovery, and HCX Connector, plus Identity Broker / VCF Operations for Networks / VCF Operations for Networks Collector upgraded from single-size placeholders to full size-tier tables. Minor validation fixes: added the "Route Based on Physical NIC Load" Teaming Policy option and corrected "NSX Connectivity Type" casing. A new tools/check_lt_constants.py script and tools/sizing_scenarios.md let these lookup tables and formulas be re-verified against the Excel workbook in the future.

DEMO data, AD toggle, Log Management replicas & navigation improvements

New "Demo" topbar button instantly fills every Management Domain field (Planning, Deploy Management Domain, vCenter, SDDC Manager, NSX Manager 3-node cluster, and a 2-node NSX Edge cluster) with a consistent, ready-to-review example based on a 4-node vSAN-ESA cluster — a confirmation prompt warns before overwriting existing values. The Active Directory / LDAP page now has an "Include/Exclude" toggle (defaults to Exclude, like the AVI/NSX Edge/VCF Operations toggles) so the detailed AD inputs are hidden until needed. Log Management (under VCF Management Services / Fleet Management Day-N) gains an HA Mode selector with dedicated replica node and load balancer / cluster VIP FQDN/IP fields when "HA Cluster" is selected. The VCF Management Services section adds 3 spare "Additional IP" fields for fleet-level scale-out. Fleet MTU now defaults to 1500 (was 9000). All password fields now show "AUTO-GENERATED" as their default sample/placeholder for a consistent convention. Discoverability: a persistent "🔌 Ports" topbar button and an As-Built page callout banner now link directly to the Ports & Protocols reference. The Ports & Protocols matrix also gains a "Group by: By Component / By Category" toggle that organizes the 19 components into 5 functional categories (Core Infrastructure, Fleet Management & Operations, Automation & Security, Recovery & Disaster Recovery, Private AI); within "By Category", each category is further sub-divided into collapsible per-component groups for easier navigation.

Live Ports Matrix & Security Hardening

The Ports & Protocols page gains a "Show my configured values" toggle: when enabled, each row displays the actual FQDN/IP you entered elsewhere in the form (vCenter, ESXi hosts, NSX Manager/Edges, SDDC Manager, VCF Operations, AD, DNS/NTP, AVI, HCX, VCF Automation, VCF Operations for Networks, Log Management, vSAN Witness, Identity Broker) next to the generic role label, and the CSV export gains matching "Resolved Source/Destination" columns — turning the reference matrix into an as-built firewall rule list. Security hardening: the Alpine.js and @alpinejs/collapse CDN scripts are now pinned to v3.14.1 with Subresource Integrity (SRI) hashes, and a new "Privacy & Data Handling" section was added to the About page and README documenting that no data ever leaves the browser and that password fields are stored/exported in plaintext.

Ports & Protocols Reference

New "Ports & Protocols" page (Reference section) provides a searchable, filterable matrix of 1083 port/protocol entries across all 19 VCF 9.1 components, sourced from Broadcom's official Ports and Protocols Tool. Browse grouped by component (collapsible), or filter by free-text search, traffic direction (Inbound/Outbound/Bidirectional/Unspecified), and component, with a "Show 100 more" pager for large result sets. A dedicated "⬇ CSV" button exports the currently filtered rows for firewall rule planning. Reference-only — not part of the VCF Installer JSON export or As-Built report.

Aligned with workbook v1.9.1.002 & Advanced Sizer

Updated against Broadcom's v1.9.1.002 revision of the VCF 9.1 Planning & Preparation Workbook (fixed sizing for the Workload Domain NSX cluster, added an Advanced Sizer for the Management Domain). Changes: the Management Domain Sizing calculator gains a vCenter Storage Size selector (Default/Large/XLarge, affecting vCenter disk footprint), an NSX Manager Model selector (Mandatory - Single Node ×1 / Mandatory - HA Cluster ×3, replacing the previous hardcoded ×3), and a Cloud Proxy Small/Standard size tier; corrected VCF Automation (VCFA) sizing values (Small/Medium/Large) to match the workbook's Static Reference Tables; the vCenter Server appliance size default changed from Small to Medium (matching the updated workbook sample); the Workload Domain count now supports up to 35; the Configure Workload Domain page's "WLD NSX Network Connectivity" section adds a WLD Edge HA Mode field (Active-Active / Active-Standby); and the Fleet Management Day-N IP samples were renumbered from the 10.11.10.x range to 10.11.99.x to avoid overlap with Management Domain addressing.

Removed Share & Print

The "Share" (URL-hash state encoding) and "Print" (browser print / PDF) toolbar buttons have been removed, along with the As-Built page's print button and the on-load URL-hash restore logic, to simplify the toolbar and avoid the size limits and staleness issues of hash-encoded state. Export JSON / Import JSON remain the supported way to back up, share, and restore your configuration, and MD / CSV remain available for As-Built reporting.

Import "VCF Installer Ready JSON"

New "JSON VCF Installer ready" / "Import VCF Installer JSON" buttons (topbar and As-Built page) let you load a previously exported SddcSpec-shaped JSON (the v1.0.3 export, or a real VCF Installer POST /v1/sddcs payload) and restore it into the form — a best-effort companion to the v1.0.3 export. Restored: top-level options (VCF version, instance name, SDDC ID, CEIP, deployment type, ESXi thumbprint validation), DNS, NTP, ESXi host FQDNs, network specs (management/vMotion/vSAN/NFS CIDR, gateway, VLAN, MTU, IP range, uplink teaming policy), vCenter, cluster, datastore (vSAN/VMFS-FC/NFSv3), distributed switch names and per-network MTUs, NSX Manager FQDNs and overlay network, VCF Operations node FQDNs and appliance size, and SDDC Manager hostname. Not restored — and flagged in a post-import summary for manual review: ESXi host management IPs, vCenter IP, NSX Manager IPs, VCF Operations IPs/load balancer/HA mode, the distributed switch profile/uplink names/LACP configuration (dvsSpecs reverse-mapping is deferred), and all passwords other than the ESXi root and vCenter root passwords — these are not present in the SddcSpec JSON by design.

VCF Management Services fields

The Fleet Management Day-N page now includes a "VCF Management Services" section covering the fleet- and instance-level lifecycle components from the Planning & Preparation workbook (Deploy Management Domain sheet, "VCF Management services" block): Fleet Components FQDN/IP, Instance Components FQDN/IP, VCF Services Runtime FQDN/IP, License Server FQDN/IP, and a shared SSH password for the vmware-system-user service account. These fields are informational/IPAM only — they are independent of the "VCF Services Runtime" / "License Server" toggles on the Management Domain Sizing calculator (which only affect resource-footprint math) and are not part of the VCF Installer JSON export, which covers Day-0 bring-up only.

VCF Installer JSON export

New "Installer" / "VCF Installer JSON" buttons (topbar and As-Built page) export a SddcSpec-shaped JSON file matching the VCF 9.1 Installer's POST /v1/sddcs request body, built from your current form data (DNS, NTP, hosts, management/vMotion/vSAN/NFS network specs, vCenter, cluster, datastore, distributed switches, NSX Manager, VCF Operations, and SDDC Manager). A new "VCF Installer Export Settings" section on the Deploy Management Domain page adds VCF Instance Name, SDDC ID, CEIP, and ESXi SSL thumbprint validation fields used by this export. Note: vSphere Supervisor (vSphere IaaS Control Plane), Fleet/SDDC LCM bootstrap options, and a few other optional installer spec blocks are not yet covered by this export — always review the generated JSON against the official VCF Installer documentation before use.

Storage type consistency & custom VDS NICs

The Management Domain Sizing "Storage Type" selector now offers the same four options as "Principal Storage Type" on the Deploy Management Domain page (vSAN-ESA, vSAN-OSA, VMFS on Fibre Channel (FC), NFSv3) and the two fields stay in sync — choosing one updates the other automatically. The vSAN network segment (VLAN/Gateway/CIDR/MTU/IP pool) and the "vSAN Datastore Name" field are no longer mandatory when a non-vSAN principal storage type (FC or NFSv3) is selected. The Distributed Switch Profile section now supports up to 10 NIC uplinks (a new "Number of Uplinks" field plus Uplink 3–10 Name fields) when "Custom Switch Configuration" is chosen as the DVS Profile.

Bug fix

Fixed a display/visibility mismatch on Include/Exclude toggle fields (e.g. Use Proxy, Deploy Cloud Proxy, vSAN Stretched Cluster, Supervisor, Identity Broker, VCF Automation/Logs/Operations for Networks, Site Protection & DR, Cyber Recovery, Ransomware Recovery, Cross Cloud Mobility, Private AI, and others) where the toggle button could display "Include" while its dependent fields stayed hidden, requiring an Include → Exclude → Include click sequence to reveal them. Toggle fields now initialize to their documented default value, so the displayed label and the visible fields are consistent from the start and a single click toggles both correctly.

Evolution update

Dark mode, keyboard navigation, share URL, expand/collapse all, jump to missing, Fill IPs, copy section, Markdown & CSV export, VLAN/IP/CIDR conflict detection, DNS pre-flight checklist, VLAN topology table, vCPU bar chart, FQDN validation, sidebar progress bars, contextual help bubbles linking to official VCF design docs, and stricter selection-field validation aligned with the original Excel data-validation lists. Also added: WLD vCenter sizing (Shared/Dedicated, with size and storage tier) on the Deploy Workload Domain page, an Instance Profile Size field in the sizing calculator that is automatically forced to "Small" when the Cluster Model is set to Simple (matching the workbook's formula), and VCF Management Services / Fleet Components (VCF Services Runtime, Cloud Proxy, License Server, Identity Broker, Software Depot, Log Management Replicas, VCF Operations for Networks and its Collector, Real-time Metrics) now included in the live sizing calculator. The Fleet Management Day-N page now models VCF Operations as a full 4-node cluster (Primary, Replica, Data, and Load Balancer nodes, each with FQDN and IP), adds a VCF Automation IP pool (5 fields, noting that Small/Standard deployments need 2 IPs and HA deployments need 4), and adds Platform Node and Collector Node IPv4/IPv6 fields for VCF Operations for Networks (with a note that these IPs must reside in the VCF Management Network).

Initial release

Full conversion of the 27-sheet VCF 9.1 Excel workbook. All deployment modes (VCF/VVF), sizing calculator, NSX Federation, AVI LB, vSphere Supervisor, Private AI, Ransomware Recovery, HCX.