Request a quote
Emergency SectorsCareers About us Blog Get in touch
Night-time skyline seen from above, with blue lines of light on a tower block

SD-WAN for branch networks: when it pays, and when two good lines will do

SD-WAN is sold as the answer to every branch network, and for some organisations with shops, branches or depots it is. For others, two good internet connections and a well-run firewall with central management do the same job. This is not another explanation of what SD-WAN is; it is how to decide which of the two you need, and what goes wrong in the move.

8 min read Written by the ITproposal team
Short answer

SD-WAN earns its keep with many sites, a lot of traffic between them or to your own data centre, and applications that cope badly with a flaky line, such as calls and tills that authorise online.

If almost everything runs in Microsoft 365 and other cloud services and you have a handful of sites, two lines on separate paths and a centrally managed firewall usually do the same work.

Whatever you choose, SD-WAN does not make a poor line good. The circuits come from a provider, and their quality and route matter more than the box behind them.

When SD-WAN pays off, and when it does not

SD-WAN is software that manages several connections at each site and chooses, per application, which path the traffic takes, with the rules set centrally. That is the whole idea. The question is not whether that is good, but whether your organisation has the problem it solves.

Five questions that usually settle it:

  • How many sites, and how different? With three offices, configuring each one is manageable. With thirty shops, depots or practices, every change becomes a project, and that is where central management starts to count.
  • Where do your applications live? If the till system, the WMS or the ERP server sits in your own data centre or at head office, a lot of traffic crosses between sites and the quality of that path is your operation. If everything is in the cloud, the path to the internet is what matters, and that is a simpler problem.
  • What cannot tolerate a hiccup? Calls over Teams or a cloud phone system, video, and tills that authorise online all notice a line that drops packets for a few seconds. Email does not.
  • Who is on site? If nobody at a branch can restart a router or check a cable, remote management weighs more heavily.
  • How often does something change? New sites, moves, pop-up shops, a seasonal depot: the more often, the more a fixed, repeatable build pays back.

Three or more yeses is a reason to look at SD-WAN seriously. One or two usually means the next section is your answer.

Two lines and a tidy firewall: often enough

Much of what organisations expect from SD-WAN a modern firewall already does: take two internet connections, fail over automatically when one drops, put tills and staff on their own segments, and manage the lot from one console. Many vendors build an SD-WAN feature into the firewall itself, in which case the choice is less a purchase than a setting.

What that setup does not do, or does less well:

  • Pick a path per application based on the measured quality at that moment, rather than switching only once a line has gone completely.
  • Move a live call to another line without a noticeable break. With plain failover, a call or an open transaction often drops and the next one starts afresh.
  • Build dozens or hundreds of sites from one template, including the links between those sites.

If none of that is a problem for you, the sensible route is two lines on separate paths, a centrally managed firewall, and a standard build that is identical at every site. That standard is the real work. Get it right and you can switch SD-WAN on later without starting again. If you would rather consume the equipment as a service than buy it, see Network as a Service.

A 4G or 5G backup that works when it has to

A mobile backup line is the simplest piece of resilience most branches can have, and also the piece that most often fails on the day it is needed. The reasons are always the same.

  • Placement. A router in a metal comms cabinet in the basement often has barely any signal. Measure reception where the device will actually sit, and fit an external antenna if needed.
  • A different route. If the fixed line goes down because of roadworks, you want a backup that does not share the same duct. Mobile is strong there; a second fixed line through the same entry point into the building is not.
  • What is allowed over it. Agree that tills, payments and voice use the backup, and that backups, updates and guest Wi-Fi do not. Otherwise the data allowance runs out before the outage does.
  • Testing. Pull the fixed line periodically, outside trading hours, and check the tills keep taking payments. A backup that has never been tested is an assumption.
  • Monitoring. An expired SIM or a cancelled bundle shows up at the next outage, unless the management platform alerts you that the backup is no longer reachable.

The SIM and the contract come from a mobile operator and should be in your organisation’s name. More on that in the boundary below.

What SD-WAN asks of your lines

SD-WAN spreads traffic across the connections you have. It does not make a poor connection good, and two poor connections do not add up to a good one. That is why an SD-WAN project starts not with hardware but with an inventory of what is available at each address.

  • Different media and routes. Full fibre plus cable, or fibre plus mobile, and ideally not both entering the building through the same point.
  • Enough upload. Cloud backups, CCTV and video calls mostly send data out. A line chosen on download speed alone will pinch there.
  • Measured quality. Latency, jitter and packet loss say more about calls and tills than the speed in the contract. Measure them for a week before you decide.
  • Lead times per address. A new circuit can be live in weeks at one address and take months at another, particularly on a business park or in a shopping centre with its own landlord. That shapes your rollout plan more than the configuration does.

Settle in advance who chooses and orders the circuits, and who reports a fault to the network operator. We can advise on and supply the fixed connection for each site; if you keep an existing contract, record who is answerable for it.

Central policy: one rule set for every site

The real gain from SD-WAN, and from any centrally managed network, is a rule set that applies to every site at once. That is also the risk: a mistake in a template is at every branch within minutes.

  • Work with site types. A shop, a depot and an office each get their own template. Keep site-specific exceptions small and write them down, or after a year you have thirty variants of one standard.
  • Segment the same way everywhere. Tills and payment traffic, staff, guests, and devices such as cameras and printers each on their own segment, with the same addressing at every site. Remote troubleshooting then becomes a matter of comparison.
  • Decide where traffic breaks out to the internet. Straight from the site is faster for cloud services, but then security has to sit there or in the cloud. Routing everything through head office is easier to watch and slower. Services that deliver networking and security together from the cloud, often called SASE, are a third route.
  • Changes with a safety net. One site first, then the rest, with a way back and a log of who changed what.

Fortinet, Cisco Meraki and Cato Networks are examples of three approaches: SD-WAN inside the firewall, management from a cloud console, and a service that delivers network and security from the cloud. Choose on how you want to run it, not on the feature list; almost every platform can do more than you will ever configure.

Moving from MPLS or separate VPNs to SD-WAN

Few organisations start with a blank sheet. They have an MPLS network from a provider, or a collection of site-to-site VPNs that grew branch by branch. Both can work perfectly well; the move is mostly a question of order.

  • Map the contracts. End date, notice period and renewal terms of every MPLS circuit and every line. A migration that runs into an automatic renewal pays twice for a while.
  • Know what runs between sites. Which applications genuinely need a path to the data centre or head office, and which already come from the cloud. Internal traffic often turns out smaller than expected.
  • Start at the hub. Head office or the data centre first, so new sites have something to connect to while the old ones still run over MPLS or VPN.
  • Run in parallel. A site only leaves the old network once it has run for a period on the new one without complaints.
  • Clean up the addressing. Overlapping IP ranges between branches are common with ad hoc VPNs and block a central build. Fix that before the rollout, not during it.

MPLS does not have to go in one step. A few sites that lean heavily on the data centre can keep it for one more contract term while the rest already run over the internet.

Rolling out branch by branch: a fixed order

Converting a branch is not a network project but a runbook you carry out the same way thirty times. The more boring it gets, the better it goes.

  • Pre-stage. The equipment arrives configured, or registers itself with the management platform when plugged in. On site, all that is left is cabling.
  • Outside trading hours. Switch over before opening or after closing, and not in the weeks around your peak season.
  • A fixed test list. A card payment, a phone call, the scanner, the printer, and then pull the fixed line to see the backup take over. Only then does the engineer leave.
  • A pilot that is hard. For the first site, do not pick the easiest one but one with poor mobile coverage, an odd layout or its own application. What works there works almost everywhere.
  • Documentation per site. Which lines, which provider, which contract reference, which devices and where they are mounted. That is what the service desk needs when the branch rings at eight in the morning.

How the tills, in-store Wi-Fi and peak days work inside such a branch is covered in our article on POS and branch connectivity.

Where our work stops

We do not supply mobile contracts or SIMs. The contracts and SIMs for the 4G/5G backup are in your organisation’s name with a mobile operator. We do advise on and supply the fixed connection: what fits each address, installation and switchover, and management of what runs on top. The physical infrastructure belongs to the network operator, and the lead time for a new connection and an outage in that network sit there.

We do not process payments. The card terminal and its connection belong to the shop’s payment provider; we make sure the path to it stays separated and clear on the network.

What we do: the design, the choice between SD-WAN and a simpler setup, the standard build, the site-by-site rollout with our own local engineers in every country, and the management afterwards.

Frequently asked

Questions we get about this

The five that come up most often.

What is the difference between SD-WAN and a VPN?

A VPN is an encrypted tunnel between two points. SD-WAN usually uses encrypted tunnels too, but manages them centrally across all sites and chooses per application which connection the traffic takes. A VPN at best fails over when a line drops; SD-WAN also steers traffic when a line still works but performs badly.

Do you need SD-WAN with only a few branches?

Usually not. With a handful of sites that mainly use cloud services, two lines on separate routes and a centrally managed firewall often do the same job. SD-WAN starts to pay off with many sites, a lot of traffic between them, or applications that cannot tolerate interruptions.

Is SD-WAN more secure than MPLS?

Not by itself. MPLS is a separate provider network but is not encrypted; SD-WAN runs encrypted over the internet, so security depends on how it is built: segmentation, where traffic breaks out to the internet and how that is protected. A well-built SD-WAN is at least as secure; a sloppy one is not.

Can SD-WAN run over 4G or 5G?

Yes. A mobile connection is simply another path alongside the fixed line, as a backup or, at a temporary site, sometimes as the main connection. Agree which traffic may use it, measure reception where the device sits, and test it periodically by unplugging the fixed line.

Do you supply the internet lines and SIMs as well?

The fixed connection, yes: we advise on and supply it for each site, and manage the network that runs on top. The physical infrastructure belongs to the network operator. We do not supply mobile contracts or SIMs for the backup; those are in your organisation’s name with a mobile operator.

Related services

Further reading

What this connects to.

Brands

The brands above, one page each

What the brand makes, which lines we supply and what we do around it.

Torn between SD-WAN and two good lines?

Send us the number of sites, what is available at each address and where your applications run. We will tell you which of the two fits, and why, before anything is ordered.

Practical IT knowledge in your inbox

New guides on management, security and the workplace, written by the people doing the work. No sales talk, and you can unsubscribe in one click.

We use your address for the newsletter only. See our privacy policy.

Request a quote Call