Initial VCF Operations node. Under high availability a replica keeps a copy of what it holds; extra capacity comes from data nodes.
Read more: Broadcom TechDocs
In the Ultra Transcenders books
Each book explains primary node in context, with comparison tables and the common traps.
Terms in this definition
- VCF Operations
VCF's console for running the fleet. It covers alerting, monitoring, capacity, reporting, log analysis and licensing alongside fleet management of identity, passwords, certificates and lifecycle.
- HA
High availability means a service keeps running despite local failures, for instance by spreading replicas across zones.
- Azure AI Search replica
Additional copy of a search service's engine and indexes. Replicas spread queries for load balancing and improve availability, so adding them is the fix when queries are throttled with HTTP 503.
- Capacity
A reserved block of compute for a tenant whose size is fixed by its SKU; Fabric F SKUs express it in capacity units (CUs). Workspaces assigned to it unlock features like Copilot, and from F64 upwards people with free licences can view Power BI content.
Related terms
- integrated load balancer
Optional Cluster VIP feature in VCF Operations for logs that puts a built-in balancer before the primary node, so an HA deployment has no single point of failure and needs no external appliance.
- PAK file
VCF Operations is upgraded by uploading one of these to Software Update in the /admin interface of the primary node, which updates every node in the cluster plus its cloud proxies. Management packs come in this format too.