A staging template is a minimal Versa Director device template – supporting WAN interfaces and a limited feature set – that gives a VOS device basic connectivity to the SD-WAN Controller, typically via the Versa global ZTP server, before its post-staging production configuration is applied.
Key takeaways
- A staging template is minimal: WAN interfaces only, limited features.
- It connects a device to the Controller before production config lands.
- Devices commonly reach it through the Versa global ZTP server.
- Staging is optional – deployment can go straight to post-staging.
- Templates are built and deployed from Director’s Workflows tab.
On this page: Why it mattersHow it worksStaging templates among Director template typesStaging templates & VersaFAQ
Why are staging templates important?
Provisioning a branch device isn’t always a single step. A device may be built and shipped from a distribution point, staged in a data center or network operations center before it ever reaches its final site, or deployed first into a proof-of-concept network to validate connectivity before committing to a full rollout. Staging templates exist for exactly that gap: they get a device talking to the SD-WAN Controller with the minimum configuration necessary, without requiring every LAN port, firewall rule, and service to be defined up front.
That separation reduces risk in zero-touch provisioning. A device shipped with only staging-level configuration can reach the network, authenticate, and pull its real, post-staging configuration automatically – so the person unboxing the appliance at a branch site never has to configure anything by hand, and a mistake in the staging config is cheap and easy to isolate from a mistake in the full production configuration.
What is a staging template?
A staging template is one of the two forms a Versa Director device template can take (the other being the post-staging template). It is created with template type SD-WAN Staging and, by design, can configure WAN interfaces only – ports, NICs, and WWAN (LTE/4G/5G) interfaces – never LAN interfaces. That restriction is deliberate: a staging template’s entire job is basic reachability, not service delivery.
Staging templates are built in Director’s Workflows tab: you select an organization and Controllers, set a preferred software version, configure the WAN-side interfaces, then use the Review tab to deploy – which activates the template and associates it with the selected Controller nodes. Because staging is for testing and pre-provisioning rather than production, it supports a deliberately limited feature set compared to a post-staging template’s full configuration surface.
Staging templates among Director template types
Versa Director organizes configuration into three broad template categories: device templates (which include staging and post-staging templates), service templates (feature-specific configuration for NGFW, QoS, application steering, secure access, and similar services), and a common template automatically created per organization and applied to every device in it by default.
Within device templates, staging and post-staging are the two types. A staging template is WAN-only, minimal, and typically transient – used to redirect a device to a staging Controller, most often via the Versa Networks global ZTP server, so it can be pre-provisioned before shipping or exercised in a proof-of-concept. A post-staging template is the mandatory production template: it covers LAN, WAN, and Aggregated Ethernet interfaces, plus the routing, tunnel, and NAT configuration that turns a bare device into a working branch. A deployment can skip staging and provision a device with only a post-staging template.
Staging templates & Versa
Director Controller nodes carry a Staging Controller flag, distinct from Post-Staging Controller, so a device’s staging and production phases can even be directed to different Controllers. PKI-based IKE authentication configures its certificate authority separately for each phase too, via a Staging CA Agent field alongside the Post-Staging CA Agent. Once created, a staging template supports the same lifecycle operations as any other Director template – modify, clone, import, export, lock, and unlock – from the Configuration tab.
Staging templates are primarily associated with the Versa Networks global zero-touch provisioning (ZTP) server: a device configured to reach it picks up staging-level connectivity automatically, without an administrator preconfiguring the device by hand. From there, the device’s assigned post-staging template supplies the rest of its configuration during onboarding, as described in Create and Manage Staging and Post-Staging Templates and Configure Basic Features.
Frequently asked questions
What’s the difference between a staging template and a post-staging template?
A staging template is minimal – WAN interfaces only, a limited feature set – meant to get a device connected to the SD-WAN Controller. A post-staging template is the full production configuration, covering LAN, WAN, and Aggregated Ethernet interfaces, and is the mandatory template every device ultimately needs.
Is a staging template required to onboard a device?
No. Staging templates exist for cases where a device is pre-provisioned at a different location, such as a data center or NOC, before shipping, or for proof-of-concept testing. A deployment can skip staging entirely and onboard a device directly with only a post-staging template.
Can a staging template configure LAN interfaces?
No. Staging templates support WAN interfaces only, by design – their scope is limited to basic Controller connectivity. Configuring LAN interfaces, along with the complete set of production network services, requires the post-staging template that follows it in the device onboarding sequence.
How does a device reach a staging Controller?
Typically through the Versa Networks global zero-touch provisioning (ZTP) server, using the minimal WAN connectivity the staging template provides. Director Controller nodes can also be explicitly flagged as staging Controllers, kept separate from the post-staging Controllers a device talks to once it has its production configuration.
Where do you create and deploy a staging template?
In Director view, from the Workflows tab, select Template > Templates, add a template with type SD-WAN Staging, configure its WAN interfaces and associated organization and Controllers, then use the Review tab and click Deploy – activating the template and associating it with the selected Controller nodes.
More on Versa Director templates
If you want to learn more, these are sources we trust.
| Versa Networks: products | Versa Networks: secure SD-WAN | Versa Academy |
|---|---|---|
| The vendor’s product pages, covering Versa Director and the orchestration layer that staging templates are part of. | The SD-WAN service that a device reaches through its staging template before receiving its full configuration. | Training and labs covering Director workflows, device templates, and zero-touch provisioning hands-on. |
Related terms
If you’re reading about staging templates, these are worth looking at next.
| Device Template | Versa Director | Controller |
|---|---|---|
| The baseline-configuration object family in Director that staging and post-staging templates both belong to. | The console where staging templates are built, deployed, and associated with organizations and Controllers. | The SD-WAN device a staging template connects a branch to, sometimes flagged specifically as a staging Controller. |