What is a DCA Complex?

A DCA complex is the collective name for a Versa Director node (or HA pair), a Versa Controller, and a Versa Analytics cluster deployed and operated together as one management stack – the set of headend nodes a Concerto orchestrator attaches to and administers as a single unit.

Key takeaways

• DCA names the headend trio: Director, Controller, and Analytics together.
• Setting up a DCA complex is a prerequisite for installing Concerto.
• Director orchestrates, the Controller runs SD-WAN control plane, Analytics reports.
• One Concerto portal can attach to and manage several DCA complexes.
• An aggregator cluster can combine Analytics data across multiple complexes.

On this page: Why it matters · How it works · DCA complex components · DCA complex & Versa · FAQ

Why is a DCA complex important?

Director, Controller, and Analytics are three separate, specialized node types, but none of them is useful alone: Director has nothing to configure without a Controller anchoring the SD-WAN fabric, and no visibility without Analytics collecting telemetry from the devices that fabric connects. “DCA complex” is the term for the trio deployed and treated as one functioning unit – the minimum viable headend for running a Versa network.

That grouping matters operationally because Concerto, the cloud-native orchestrator, is built to attach to a DCA complex as a whole rather than to its three nodes individually. Service providers and large enterprises often run more than one DCA complex – split by region, customer boundary, or scale limits – and Concerto’s value is presenting one console across all of them, discovering each complex’s tenants and Controllers once it is attached.

What is a DCA complex?

A DCA complex is a working Versa headend: a Director node or HA pair for management and templates, one or more Controllers for the SD-WAN control plane, and an Analytics cluster for logs and reporting, all pointed at each other and at the same provider organization. Standing one up is a named prerequisite before installing Concerto – Director, then a provider organization, then Controllers, then the Analytics cluster.

Concerto attaches to a DCA complex by adding its Director cluster under Infrastructure, then running Discover Tenants to pull in the provider’s tenants and Controller nodes automatically. To have Concerto manage several DCA complexes as one estate, each complex’s provider organization must share the same name and global ID – that shared identity is what lets Concerto treat physically separate complexes as one logical whole.

DCA complex components

Versa Director is the management and orchestration node (or HA pair): it holds configuration templates, provisions devices, and exposes the REST APIs Concerto calls. Versa Controller is the SD-WAN control-plane node: it terminates IPsec tunnels from branches and hubs and distributes routing via MP-BGP, keeping the overlay fabric connected. Versa Analytics is the telemetry cluster: it ingests logs VOS devices export – firewall access, threat detection, SD-WAN traffic, DNS, and more – and serves the dashboards and searches administrators view through Concerto or Director.

DCA complex & Versa

Concerto is the layer above the DCA complex, not a replacement for it: administrators still work against Director, Controller, and Analytics underneath, but through Concerto’s single portal instead of connecting to each node directly. Installing Concerto requires a DCA complex to already exist, and attaching that complex’s Director cluster is one of Concerto’s first infrastructure steps. Because each DCA complex normally pairs with its own dedicated Analytics cluster, an aggregator cluster is what lets Concerto present combined Analytics log views – filtered by log type or by a single complex – across every DCA complex it manages.

Frequently asked questions

What does DCA stand for?

Director, Controller, and Analytics – the three Versa headend node types that together form the management, control, and telemetry stack a Concerto orchestrator attaches to and administers as one unit. Each node type plays a distinct role, and the complex only functions with all three present.

Do I need a DCA complex before I can install Concerto?

Yes. Setting up the Versa Director, Controller, and Analytics complex is the documented first step before installing a Concerto node, whether in standalone or cluster mode. Concerto attaches to an existing DCA complex rather than creating one, so Director, the Controllers, and the Analytics cluster must already be running.

Can one Concerto portal manage more than one DCA complex?

Yes. Concerto can attach to multiple DCA complexes and present them under one portal, provided each complex’s provider organization shares the same name and global ID, so Concerto recognizes them as parts of the same logical estate rather than as unrelated deployments to manage separately.

Does every DCA complex need its own Analytics cluster?

Typically yes – each DCA complex uses a separate Analytics cluster to collect logs from its own devices. Concerto’s Analytics aggregator cluster then combines data from multiple clusters, so administrators can view logs scoped to one complex or combined across every complex Concerto manages.

What is the difference between a DCA complex and Concerto?

The DCA complex is the underlying stack that does the actual work – configuration in Director, SD-WAN control on the Controller, telemetry in Analytics. Concerto is the orchestration portal layered on top, attaching to one or more DCA complexes to manage them all from a single console.

More on Versa

If you want to learn more, these are sources we trust.

Related terms

If you’re reading about the DCA complex, these are worth looking at next.