What is a WAN Network?

A WAN network is a Versa Director configuration object, associated with a transport domain, that represents a distinct WAN underlay connection type – such as MPLS, internet, or LTE – used when configuring SD-WAN site and interface connectivity. WAN networks configured on a parent organization can automatically propagate to its suborganizations.

Key takeaways

• A WAN network is a Director object tied to one transport domain.
• It labels the underlay connection type used by SD-WAN interfaces.
• Transport domain IDs let branches with matching circuits reach each other.
• Parent-organization WAN networks can propagate to suborganizations.
• Configured under Configuration > Objects > WAN Networks in Director.

On this page: Why it matters · How it works · Types · WAN networks & Versa · FAQ

Why are WAN networks important?

Most SD-WAN branches have more than one circuit – an MPLS link, a broadband connection, an LTE backup – and the overlay needs a way to know which underlay each interface belongs to before building policy-driven paths. A WAN network gives that underlay a name: it associates a connection type with a transport domain, so SD-WAN policy can choose the specific underlay for a given path instead of treating every circuit generically.

That labeling matters more as a deployment scales. A provider managing many customer organizations needs consistent WAN network naming under each one, and recreating objects by hand invites drift. WAN Propagation removes that manual step, copying a parent organization’s WAN networks to its suborganizations in one action. Design guidance also recommends distinct names on hub and gateway sites, since the overlay uses those names to select the correct underlay across disjoint transport domains.

What is a WAN network?

A WAN network is configured in Director view under Configuration > Objects > WAN Networks. Its fields are a Name, an optional Description, and a required Transport Domain. A transport domain isolates the access circuits at two reachable branch sites and carries a numeric ID; placing two circuits under the same ID is what lets Director know they can communicate. An inline “+ Transport Domain” control creates that domain without leaving the form.

Because a WAN network’s defining reference is a transport domain, it becomes the label an interface or device template points to when declaring which underlay a connection uses. The overlay then applies policy – not raw circuit type – to pick which WAN network to use, letting SD-WAN steer traffic across MPLS, internet, or LTE without hardcoding per-circuit logic. This differs from the general VOS “Network” construct, which groups interfaces on a routing instance rather than labeling an underlay.

Types of WAN networks

WAN network is not an enumerated type in the schema – any name is valid – but deployments consistently group them by the underlay circuit type their transport domain represents. The recurring patterns are an MPLS WAN network, tied to a private MPLS transport domain; an internet WAN network, tied to a broadband transport domain; and an LTE WAN network, typically used for cellular backup or cold-standby paths. Design guidance layers a naming pattern on top: hub and gateway sites should use WAN network names unique across the entire SD-WAN network, so overlay policy can unambiguously select the intended underlay when many sites share transport domains.

WAN networks & Versa

Versa Director exposes WAN networks and transport domains together under Configuration > Objects, since the two are configured as a pair – a transport domain groups reachable circuits, and a WAN network is the named object that interfaces, templates, and policy reference. The Propagate action lets a provider select one or more suborganizations – or all of them – to receive a copy, with an Overwrite option for when a same-named object already exists below.

WAN networks also serve as policy targets: QoS and rewrite (RW) policies can apply directly to a named WAN network – for example, remarking a forwarding class to a DSCP value on “the MPLS WAN network” specifically, rather than on every interface. That makes the WAN network a practical anchor point for both connectivity design and marking policy.

Frequently asked questions

What does a WAN network connect to in Versa Director?

A WAN network references exactly one transport domain, a required field set when the WAN network is created. The transport domain groups circuits at two reachable branch sites under a shared numeric ID, which is what lets those circuits communicate over the SD-WAN overlay.

Can a WAN network be applied to suborganizations automatically?

Yes, through WAN Propagation. From the WAN Networks list, select a WAN network, click Propagate, and choose one or more suborganizations – or all of them – to receive a copy, with an option to overwrite an existing same-named WAN network below.

Where do I configure a WAN network?

In Director view, go to Configuration > Objects > WAN Networks and click Add. Enter a Name, an optional Description, and a Transport Domain (or create one inline), then click OK. Transport domains are configured separately under Configuration > Objects > Transport Domains.

How is a WAN network different from a transport domain?

A transport domain is the grouping mechanism: a numeric ID that places two branches’ circuits in the same reachability group. A WAN network is the named object built on top of it – the label interfaces, templates, and policy reference when specifying which underlay to use.

Can policies be applied to a specific WAN network?

Yes. QoS and rewrite policies can target a named WAN network directly, for example remarking a forwarding class to a DSCP value only on the MPLS WAN network. This lets marking and QoS behavior differ by underlay type rather than applying uniformly to every interface.

More on WAN networks

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

Related terms

If you’re reading about WAN networks, these are worth looking at next.