In VCF 9.0, adopting a vCenter you already run, with its hosts and optionally Aria products, as the management domain of a brand-new fleet or instance; absent pieces are deployed for you. Enhanced Linked Mode setups are excluded.
Read more: Broadcom TechDocs
In the Ultra Transcenders books
Each book explains Convergence in context, with comparison tables and the common traps.
Terms in this definition
- VMware Cloud Foundation
Broadcom's platform for private cloud. It unifies management of NSX, vSAN, vSphere, VCF Automation and VCF Operations as one fleet; VVF, by contrast, lacks automation and cloud management.
- vCenter
Management software for VMs, clusters and ESX hosts. Each domain in VCF gets a dedicated one.
- management domain
VCF domain built by the VCF Installer to host a VCF Instance's management components, plus fleet-wide components such as VCF Operations and VCF Automation in the first instance. Business workloads may run there too.
- ELM
vCenter capability linking multiple vCenter instances into one SSO domain so their inventories appear together. VCF 9.0 convergence cannot take vCenter instances that use it.
Related terms
- Graceful restart
BGP can keep forwarding packets while a neighbour's control plane restarts. On NSX Edge nodes this defaults to helper only, and Tier-0 gateways are better without it because BFD-based convergence gets delayed.
- Import
A VCF Operations workflow for adopting a vCenter that is already running, whether or not NSX is present, as a workload domain of a VCF 9.0 instance; every one of its clusters is brought in, and NSX gets deployed or joined where needed. Convergence differs by making an existing environment into a management domain instead.