Sizing tool

Management Domain Sizing & Fit Check

Reproduces the Broadcom Planning & Preparation Workbook (v1.9.1.001) Management Domain Sizing sheet, and adds the check the spreadsheet lacks: enter the cluster you intend to build and see whether the fleet fits at N-1, and where the headroom is. Everything runs in your browser; nothing is sent anywhere.

Deployment profile

Simple deploys at Small only; High Availability at Medium or Large.

Proposed cluster & host spec

Management components

An Edge-backed Supervisor (VPC + Centralized Transit Gateway, or classic NSX) needs its Edge cluster at Large minimum. The VPC + Distributed Transit Gateway path uses a VNA cluster and no Edge; vDS networking uses no NSX. Per-domain Supervisors are set on each workload domain below.

On a new deployment the Installer adds a unified cloud proxy automatically at bring-up, so it is there whether or not it is ticked — leave it on for greenfield. Untick it when sizing an upgrade or an existing fleet whose proxy is already accounted for. Day-N additional collectors come on top of this one.

Workload domains

Each workload domain's vCenter and (dedicated) NSX Managers run inside the management domain, so they add to its footprint.

Fit against your cluster

DimensionFleet needsCluster offersHeadroom

CPU and RAM are checked against the tolerated failure: N-1 (one host) for a standard cluster, or N/2 (the surviving AZ must run everything) for a stretched cluster. Storage rebuild is covered by the reserve %, and stretched mirrors a full copy per AZ.

Fleet requirement

Component footprint (0 line items)
ComponentNodesvCPURAM GBDisk GB
vSAN raw capacity breakdown

Figures transcribed from reference/vcf-9.1-planning-and-preparation-workbook.xlsx (v1.9.1.001), sheet Management Domain Sizing. This is a planning aid; always confirm the final numbers against the official workbook for your revision.