Multi-site fibre and SD-WAN for SMEs

Multi-site fiber and SD-WAN for SMEs: linking branches, warehouse, and headquarters in PACA without multiplying “improvised tunnels.” On the Côte d'Azur and in Monaco, Host Technology unifies FTTH/FTTO links, voice QoS, and failover — as a local integrator from Tourrettes-sur-Loup, with monitoring and telephony in the same design.

The classic multi-site problem

Each site has its operator, its firewall, sometimes its own switchboard. Site-to-site VPNs hold until the first box change. Voice between sites suffers, backups trip over each other, and nobody knows who is responsible. SD-WAN (or a controlled VPN architecture) puts a single policy above heterogeneous links.

Host Technology starts with a single design (addressing, VLAN, voice policy) before buying SD-WAN appliances. Without that, chaos is automated.

FTTH and FTTO according to the site’s role

Critical headquarters on FTTO, branches on FTTH, 4G backup everywhere: a frequent and sound design. Host helps arbitrate cost versus GTR per address. What matters is QoS consistency and monitoring, not having the same commercial label on every invoice.

The FTTO cost is often justified at headquarters, where the IPBX, backup, and cloud access are concentrated. Branches stay on FTTH plus 4G.

SD-WAN: what it really brings to an SME

Path selection, application prioritization (voice first), automatic failover, centralized visibility. It is not reserved for large accounts if the multi-link need is real. Host Technology sizes without over-engineering: sometimes a well-done dual-WAN VPN is enough.

Consider SD-WAN when you have three links or more, application-prioritization needs, or a team that can no longer manage handmade VPNs.

Multi-site IP telephony

A central or cloud IPBX, local trunks, a readable numbering plan. QoS must be identical at each end. Without that, a Nice–Monaco call crackles as soon as a backup starts. Host aligns the voice VLAN and the SD-WAN/VPN policy.

A multi-site softphone without end-to-end QoS remains the first reason for complaints. Host treats it as an acceptance criterion.

Multi-site fiber / SD-WAN checklist

1. Map sites, current links, throughput, GTR, and critical uses.
2. Define each site’s role (headquarters, branch, warehouse, backup).
3. Choose FTTO/FTTH plus 4G per address.
4. Set a consistent voice / data QoS policy.
5. Deploy VPN or SD-WAN with tested failover.
6. Unify telephony (numbering plan, trunk).
7. Monitor all links and tunnels (alerts).
8. Document and integrate into Host managed IT.

The checklist serves as a budget roadmap for year N / N+1. Useful for SME groups opening points of sale on the Côte d'Azur.

Backup and windows

Multi-site backup jobs easily saturate branch uplinks. They are scheduled, throttled, and voice is prioritized. The central immutable copy remains the anti-ransomware foundation of the SME group.

Throttle or centralize branch backups toward the headquarters immutable vault to avoid uncontrolled copies.

Inter-site security

Segmentation: a shop’s point of sale does not need to see the whole headquarters file share. MFA on remote access. Documented firewall rules. Host Technology treats cybersecurity and the multi-site network as one project.

Lateral ransomware between sites is the scenario to avoid at all costs: segmentation and east-west filtering are part of the design.

Governance: one integrator, several operators

Each site can keep its fiber operator. The local integrator unifies the layer above. That is Host’s role on the Côte d'Azur: one design, one monitoring system, one contact when a tunnel “flaps.”

A “tunnel down” ticket with measurements attached speeds the operator. Host standardizes this format for every site.

Progressive deployment

Five sites are not cut over the same weekend. Pilot site, settling-in, expansion. Lessons from the first (QoS, Wi-Fi, telephony) speed up the following ones. Host plans the calendar with management.

The pilot site includes telephony, Wi-Fi, and backup, not only the tunnel. Otherwise you validate a VPN with no business context.

In practical terms, every PACA site has its own constraints (building, seasonality, multi-site setups across Monaco and Nice): Host Technology adapts the action plan rather than copying a fixed national template, with a single point of contact for the network, telephony, backup, and managed IT.

The documentation delivered at the end of the project (diagrams, accounts, failover procedures, operator contacts) is designed so a third party can take it over: that is a Host requirement, not an optional extra. It reduces dependence on a single person and speeds up later audits.

Finally, plan a review at 30 and 90 days: recurring tickets, QoS or throughput measurements, restore tests, and additional training. That is often when supervision thresholds are adjusted and management sees the operational gain on the Côte d'Azur.

On a multi-site PACA network, the slightest drift in addressing or QoS is paid for in voice tickets. Host Technology freezes the master design, then accepts later site openings only if the pilot (telephony, backup, monitoring) is green.

• Standardize addressing, VLANs, and naming conventions before the first deployment.
• Define an identical voice policy on every branch.
• Diversify access when continuity justifies it.
• Limit lateral movement between business networks.
• Monitor application experience, tunnels, and physical links.
• Test the return to the primary link without interrupting calls.

• Keep standard equipment and a standard configuration per site size.
• Assign LAN tickets, operator access, and the SD-WAN platform clearly.
• Measure application quality before and after each wave.
• Prepare backup administration outside the main tunnels.
• Automatically back up validated configurations.
• Review capacity and contracts at every branch opening.

The architecture file must stay simple enough for the local team to operate. It describes the normal path, the backup path, the advertised networks, and the priority applications. Each new branch reuses a validated model, with only the parameters specific to the site. Host Technology thus avoids the drift where a firewall is configured differently at each opening. Standardization shortens lead times, makes cybersecurity easier, and lets the performance of Nice, Cannes, Monaco, or Tourrettes-sur-Loup be compared from shared monitoring.

Operator contracts must be set against the technical design. A branch may believe it has two links when they use the same duct or the same collection network. Real diversity is checked as far as possible before continuity is promised. Host Technology records operator, technology, GTR, delivery point, and backup path for each address. This map helps decide a second access, an outdoor antenna, or FTTO, and gives support the information needed to open a correctly qualified ticket immediately.

FAQ: frequently asked questions

From how many sites does SD-WAN become useful?

There is no absolute threshold. Two sites with several links and a strong continuity requirement can already benefit from dynamic path selection, while three small stable branches sometimes do well with well-administered VPNs. Useful criteria are the number of tunnels, operator diversity, VoIP, expected visibility, and operating time. Host Technology compares the cost of SD-WAN with the cost of incidents and manual administration before proposing a platform.

Does SD-WAN replace FTTO or FTTH fiber?

No. It orchestrates the paths available but does not turn an unstable link into guaranteed access. Headquarters can keep FTTO with a GTR, branches professional FTTH, and every site 4G/5G backup. SD-WAN then chooses the link according to health and the application. Host Technology sizes each access according to the site’s role, then configures failover policies. Final quality still depends on the LAN, QoS, and the operators’ real capacity.

How do you protect IP telephony between several sites?

Each LAN has a voice VLAN, controlled DSCP marking, and reserved capacity. The SD-WAN or VPN keeps that class and selects the path with the best latency, loss, and jitter. The numbering plan also provides for operation if a site is isolated. Host Technology tests calls during a real failover and checks the SIP trunk and NAT. This end-to-end acceptance stops a green dashboard from hiding a degraded conversation.

How do you stop ransomware spreading between branches?

The multi-site network must not be fully open. Business VLANs, servers, points of sale, guest Wi-Fi, and technical systems communicate only according to necessary rules. Administrator access uses MFA and controlled workstations; immutable backups stay isolated from production accounts. Host Technology documents inter-site flows and blocks useless lateral movement. SD-WAN makes consistent policy distribution easier, but an explicit security design remains essential.

How do you migrate without cutting every site?

The safest method is to prepare the model, deploy a representative pilot, observe for several weeks, then extend in waves. Each cutover has a window, business tests, and a rollback. Headquarters and critical branches do not change at the same time. Host Technology coordinates operators, IP telephony, Wi-Fi, and backup so the tunnel is not validated in isolation. Lessons from the pilot correct the templates and make later deployments faster and more predictable.

Several sites to link in PACA or Monaco? Ask Host Technology for a fiber / SD-WAN audit — link map, voice QoS, cutover plan, and deployment roadmap.