Management Plane Sizer
What VCF Management Services costs you in worker nodes today, what it could cost, and what you have to do to get there. Including why the saving does not survive installing Log Management.
Runs entirely in your browser. Nothing you enter is sent anywhere.
Where this environment is
VCF Management Services is a VCF component. VVF is out of scope for all of this.
This is the single input that decides whether you already have the smaller footprint.
The rightsizing procedure is for management clusters and refuses to run on a consumption cluster.
Decides whether Small HA is in play, and on 9.1 whether you have a problem.
The reduced footprint is only available while both of these stay off. This is a design decision, not an operational one.
Fleet deployments carry a higher minimum worker count than instance deployments.
Next step. Upgrade Sequencer puts the worker rollout in the right place in the order of operations, and Edition Fit Check settles whether you are on the edition this applies to at all.
What this is built on
- The node size is documented, the percentage is not. A worker is 12 vCPU and 24 GB. You will see larger percentage reductions quoted around 9.1.1. Broadcom has not published a before-and-after total, so this tool counts nodes and leaves percentages out.
- New deployments get the smaller footprint, patched ones do not. Greenfield 9.1.1 and later is sized correctly on day one. An environment patched from 9.1 keeps the worker size and replica count it had before, and nothing tells you.
- The saving is reversible, and that is the part people miss. Install Log Management or Real-time Metrics after rightsizing and the worker profile is recomputed to management.large, 16 vCPU and 32 GB. The footprint you planned on goes away the first time someone asks for centralised logging.
- Small HA arrived in 9.1.1.0. On 9.1 it is not merely absent. Broadcom states that forcing it through the API or a script leaves the system unsupported and unrecoverable.
- VCF Automation has no Small HA form factor. It deploys as a single appliance, so Small HA does not cover an availability requirement that includes automation.
Checked 7 November 2026
Checked against Broadcom documentation and knowledge base articles on 7 November 2026, against VCF 9.1.1. A worker node is 12 vCPU and 24 GB. Sizing changes between point releases, so confirm against the documentation for the build you are actually running before this reaches a plan.
Where this comes from
- The management plane got smaller. Your estate did not., the write-up behind this tool, with its own sources.
- Broadcom KB 455842, for the rightsizing procedure, the conditions under which it refuses to run, and the verification step.
- Broadcom KB 452952, for Small HA support from 9.1.1.0 and the warning about forcing it on 9.1.
- Broadcom TechDocs, VCF Management Services models, for the deployment sizes and what each carries.
- The Day N recomputation to management.large and the drain behaviour during a worker rollout are documented in an independent write-up rather than by Broadcom, and are flagged as such in the article above.
What this tool cannot know
- Your actual resource usage. It counts worker nodes at a documented size. It does not measure what your management plane is really consuming.
- How long the rollout takes in your estate. Nodes replace one at a time and that scales with the cluster.
- Anything about cost. Fewer nodes is not automatically a saving if the hosts are already paid for.
- Whether your Day N answer will hold. It is a design commitment, and the people who ask for centralised logging later are rarely in the room when it is made.
- Add-on and partner products sitting on the management plane, which have their own sizing.
Part of the VCF planning toolkit
Last, check whether you could put the management plane back if the upgrade went wrong.