VCF Ready's Step 4, Customer Deliverables and Export Package, for the example estate: the Download customer package (.zip) button, the ticks to include the answers file and to anonymise names and addresses, the engagement file, the customer name Example Freight Group and the first three cards, for the Word report, the findings workbook and the evidence request; the step reads 12 Deliverables.

The deliverables, and sharing them without the customer

Part 3 of VCF Ready: what Step 4 hands over, who each deliverable is for, why they all tell the same story, and how an assessment leaves the customer’s site without the customer in it.

11 November 2026 · Adam Stretton
The VCF Ready home page with the example estate loaded: the header reads 4 Sources, 13 Clusters, 65 Hosts (2 standalone) and 596 VMs; four steps run from Estate Discovery and Scope through Readiness and Findings (6 Blockers) and Upgrade Plan and Sizing to Deliverables and Reports; and Step 1 offers live vCenter discovery or imported files.

Introducing VCF Ready

Are you VCF ready? Are you sure? The answer is spread across hundreds of Broadcom articles and pages. Introducing VCF Ready, our upgrade readiness tool: what it reads, what it finds, how it turns open questions into a workshop, and why every check cites Broadcom.

9 November 2026 · Adam Stretton
VCF Ready's Step 3, Upgrade Plan and Sizing, with its four sections closed. Route and target reads VCF 9.1.1.0, Converge into New VCF Fleet, from vSphere 8.x / 7.x. Sizing reads 26 appliances, 274 vCPU, 896 GB RAM, 33.4 TB on vSAN ESA, and 2 of 13 clusters fit with a host failed. Upgrade runbook reads 8 phases to 9.1.1.0. Architecture recommends VCF Fleet with Multiple Sites Across Multiple Regions.

The upgrade plan and sizing, from Broadcom's own sources

Part 1 read the estate and found what stands in the way. Part 2 is the plan: how VCF Ready brings Broadcom’s VCF Upgrade Planner, Planning and Preparation Workbook and design blueprints onto one page, filled in from the estate, so the route, the phases, the size of the management domain and the hosts to buy are all in view.

9 November 2026 · Adam Stretton
The trunk-subnet design: one trunk vNIC, binding maps demux VLANs 1610/1611/1612 into VPC subnets

Nested ESXi inside an NSX VPC: the trunk-subnet design

Plain VPC subnets silently blackhole a nested ESXi host. Why, and the trunk subnet and binding map design that makes nested labs work as an ordinary NSX VPC tenant.

16 September 2026 · Updated 1 October 2026 · Adam Stretton
The ordering rule: VPC, VPCAttachment, LoadBalancer, then the namespace - swap steps 3 and 4 and VIPs pend forever

The load balancer that must exist before the namespace

Addresses pending for ever, a retryable error that never stops retrying, and an ordering rule the docs don’t tell you: in a self-service NSX VPC, the load balancer must exist before the namespace that uses it.

16 September 2026 · Updated 1 October 2026 · Adam Stretton
Fail a NIC. Nothing blinks.

Dual-NIC nested hosts: what redundancy means when the fabric is virtual

A second vNIC on a nested host adds no physical redundancy, so why add it? We expected bringup to want one, and pulling vmnic0 mid-SSH proved the trunk copes: 0% loss, session intact.

16 September 2026 · Updated 1 October 2026 · Adam Stretton
Three bootstrap paths into a VPC subnet: cloud-init, sysprep, vAppConfig

Our VPC subnets have no DHCP — and that's fine

The nested ESXi appliance sat at ‘waiting for DHCP’ for ever. VPC subnets don’t hand out addresses: the VM Service does, through cloud-init, sysprep or OVF guestinfo, depending on the guest.

16 September 2026 · Updated 1 October 2026 · Adam Stretton