Upgrade Sequencer
The order to upgrade VCF components in, and the gates between them. Encodes the prerequisites that sit in release notes rather than upgrade guides.
Runs entirely in your browser. Nothing you enter is sent anywhere.
Where you are
VxRail has its own lifecycle and its own exclusions.
What you run today
Before you sequence anything, Estate Readiness Triage tells you which clusters are even coming, Edition Fit Check tells you what you are landing on, and Upgrade Runway tells you whether there is time.
Why order matters more than version numbers
- Patches are not synchronised across components. Broadcom's patch release page is explicit that patch releases do not require a new Bill of Materials and that you can apply only the components that apply to you. Any tracker showing 9.1.1 as a single flat version is giving you a number that does not exist in your estate.
- The gates that bite are not in the upgrade guide's order. They are in the release notes of the component you were not planning to touch. ClusterClass versions, removed built-ins, and address ranges are the usual three.
- Mixed versions under one vCenter are supported during a transition, not as a destination. Running 8.x and 9.1 clusters side by side is fine while you move. It is also two versions of the truth in your runbooks, so give the transition an end date when you plan it, not afterwards.
- This is a planning aid, not a runbook. It encodes the traps that keep appearing in release notes. It does not replace the interoperability matrix or the upgrade documentation for your exact build.
Checked 7 November 2026
Checked against VCF 9.1.1 upgrade documentation on 7 November 2026. The order of operations and the gates within it change between point releases, so confirm against the upgrade guide for your specific target build.
Where this comes from
- The staged path from vSphere 8 to VCF 9.1, the write-up behind this sequence, with its own sources.
- Broadcom KB 452952, on enabling HA for VCF Management Services and why forcing it on 9.1 is unrecoverable.
- Broadcom KB 455842, on the management services footprint and the rollout behaviour during a worker replacement.
- Broadcom VCF 9.1.1 upgrade documentation, for the component order and the version floors.
What this tool cannot know
- Your add-on and partner products, which often have their own order and their own floors.
- How long each step takes in your estate. The sequence is an order, not a schedule.
- Anything about rollback. Several of these steps do not have one, which is precisely why the gates are marked.
- Third-party integrations hanging off vCenter, which tend to be discovered during the change rather than before it.
Part of the VCF planning toolkit
Last, the control map, for when risk or audit ask what the change does to their evidence.