A network is a Versa VOS configuration object that groups similar interfaces running on similar routing instances so administrators can manage them as a single unit instead of configuring each interface separately. Networks simplify interface management across SD-WAN branches, hubs, and gateways; an interface can belong to only one network at a time.
Key takeaways
- A network groups interfaces that share a similar routing instance.
- One interface can belong to only one network at a time.
- Networks reduce repetitive per-interface configuration on VOS devices.
- WAN Network is a related but distinct transport-domain object.
- Configured through Versa Director and Concerto device templates.
On this page: Why it mattersHow it worksHow networks workNetworks & VersaFAQ
Why are networks important?
VOS devices often have many interfaces performing similar roles – several WAN links on the same routing instance at a branch, for example. Without a grouping construct, administrators would reference each interface individually in every policy, template, and monitoring rule, which becomes repetitive and error-prone as interface counts grow. Combining interfaces that share a routing instance into a network lets administrators manage, reference, and troubleshoot them as one entity, and the one-network-per-interface rule keeps membership unambiguous – a given interface’s traffic behavior is never split across two competing groupings. This matters most in SD-WAN deployments, where a branch, hub, or gateway can carry many WAN, LAN, and tunnel interfaces across MPLS, internet, and LTE transports; without networks, tracking which interface belongs to which underlay or role would depend on naming discipline rather than on the platform itself.
What is a network?
A network combines interfaces that share a routing instance into a single configuration object that Versa Director and Concerto reference, rather than requiring every policy or template to enumerate interfaces individually. The object doesn’t create new forwarding behavior on its own – the routing instance and the interfaces still do the actual work. A network is an administrative grouping that makes those interfaces easier to select, reference, and audit as a set. Because an interface can belong to only one network, membership is unambiguous: there is no case where a policy has to decide which of two networks an interface’s traffic really belongs to. This one-to-one relationship also keeps a network’s scope predictable – it is a subset of a routing instance’s interfaces, not a competing grouping layered on top of it.
How networks work
Because every network is scoped to a routing instance, an interface’s network membership depends on which routing instance it runs on – moving an interface to a different routing instance moves it out of its old network’s eligible pool. In Versa Director, interface and WAN link names are configured from the Add/Edit Template > Interfaces tab, and administrators are advised to give WAN links unique names across gateway and hub sites as the SD-WAN deployment grows. A closely related but distinct object is the WAN Network: where a network groups interfaces sharing a routing instance, a WAN Network represents a distinct WAN underlay connection type tied to a transport domain, referenced by SD-WAN site and interface connectivity when choosing a path. The two objects solve adjacent problems – one organizes interfaces by routing context, the other organizes underlay transports by domain.
Networks & Versa
Networks are a VOS-level construct: any VOS device with multiple similar interfaces on a routing instance can group them into a network rather than referencing each interface separately in policy, whether managed through Versa Director templates or Concerto profiles. In SD-WAN designs, this grouping becomes more valuable as branch, hub, and gateway devices accumulate WAN, LAN, tunnel, and cross-connect interfaces across MPLS, internet, and LTE transports – the guidance to keep WAN link names unique across gateways and hubs exists precisely because so many interfaces and networks can coexist on a single device. Networks are referenced, not duplicated, across the templates and policies that use them, so a change to a network’s membership doesn’t require touching every place that references it.
Frequently asked questions
Can an interface belong to more than one network?
No. Versa VOS enforces a one-to-one relationship: an interface can be part of only one network at a time. If an interface needs to be grouped differently, it must be removed from its current network before being added to another.
Does a network change how traffic is forwarded?
No. A network is an administrative grouping, not a forwarding construct – the underlying routing instance and interface configuration determine forwarding behavior. Grouping interfaces into a network makes them easier to manage and reference together; it does not add or change routes.
What is the difference between a network and a WAN Network?
A network groups interfaces that share a routing instance, for general interface management. A WAN Network is a more specific object tied to a transport domain that represents a distinct WAN underlay connection type used in SD-WAN site and interface connectivity.
Where are networks configured?
Networks are configured on VOS devices through Versa Director device templates or Concerto profiles, alongside the interfaces and routing instances they group. Interface-level settings, including WAN link names used on gateway and hub sites, are set from the template’s Interfaces tab.
Why would a group of interfaces need to be combined into a network?
Combining similar interfaces into a network reduces repetitive per-interface configuration and gives administrators one object to reference in policies, templates, and troubleshooting, instead of tracking each interface individually as branch, hub, and gateway devices accumulate more WAN, LAN, and tunnel interfaces over time.
More on networking
If you want to learn more, these are sources we trust.
| Versa SD-WAN | Versa Academy |
|---|---|
| Versa’s SD-WAN product pages, covering the underlay and overlay concepts that VOS networks and WAN Networks help manage. | Versa’s training platform, with courses covering VOS configuration objects including networks and routing instances. |
Related terms
If you’re reading about networks, these are worth looking at next.
| Routing Instance | Zone | WAN Network |
|---|---|---|
| The forwarding context a network’s interfaces run on; a network is scoped to the routing instances it groups. | A security construct that also groups interfaces and networks, but for policy match criteria rather than administrative grouping. | A transport-domain object representing a distinct WAN underlay connection type, referenced by SD-WAN site and interface connectivity. |