Use case · 5G WAN

Reach your network gear even when the network is down.

When the main network fails, the tools you'd use to fix it often fail too. An independent 5G path lets your team reach routers, firewalls and power controls remotely, instead of sending a truck.

TYPICAL SITEData rooms, remote sites, branches
WHAT HURTSOutages need a site visit
WHAT WE CHANGEA separate way in over 5G
Sound familiar?

What it looks like day to day.

A typical scenario based on the environments we work in, not a specific customer.

  • Outages mean driving to the site to reboot something
  • Remote access depends on the same link that failed
  • Remote sites have no on-site IT
  • Recovery takes hours when it should take minutes
Network down, no way in compared with Team reaches gear over 5GNetwork topology. Existing: Network down, no way in. Proposed: a 5G gateway connects the site router through the carrier network to the internet and applications.AEXISTING CONDITIONSNTSSITEINTERNET / APPSFIBER / ISPDOWNEDGE RTRCORE / FWNOC / ITNO ACCESSNO WAY INEXISTING── WIRED ╌╌ WIRELESSBPROPOSED DESIGNNTSSITEINTERNET / APPSFIBER / ISPDOWNEDGE RTRCORE / FWNOC / ITOOB · 5GCARRIER RANACTIVEREACHABLEPROPOSED · 5G WAN · MONITORED── WIRED ╌╌ WIRELESSA — Network down, no way inB — Team reaches gear over 5G
Sheet A shows existing conditions; sheet B shows the proposed design. Illustrative, not to scale.
Why it happens

Remote access shares the path that broke.

If your remote access runs over the production network, it disappears exactly when you need it. A separate cellular path to a console server or router gives your team a way in that doesn't depend on the broken link.

What we do

How we fix it.

5G WAN connects a location to the internet over the cellular network, as its main connection, its backup, or a separate path for emergency access.

  1. Identify critical gear

    Routers, firewalls, switches and power at each site.

  2. Add the separate path

    A 5G console server or router, ideally on a different carrier.

  3. Lock it down

    Strong authentication and logging for emergency access.

  4. Test it regularly

    Make sure it works before you need it.

Every site starts with a coverage check for each carrier, so the right carrier and antenna are picked before anything ships.

What changes

What's different after.

Fewer truck rolls

Fix it remotely.

Faster recovery

Minutes instead of hours.

Peace of mind

A way in during the worst outage.

Is it a fit?

Where this works, and where something else fits better.

We recommend what solves the problem, even when it's a different solution.

A good fit for

  • Data rooms and remote network sites
  • Branches without local IT
  • Critical infrastructure locations

Something else may fit better

For your IT or engineering team

Technical detail

The design decisions, the end-to-end path and how the result is tested.

Show

Out-of-band access should reach only the management assets required for diagnosis and recovery, through strong authentication and audited use.

Design decisions

Design decisionWhat we need to understandHow we engineer it
IndependenceReview carrier, antenna, power, device, path, DNS, identity, and facility dependencies.Separate the recovery path from the failures it is expected to survive.
ReachabilityList console ports, management interfaces, PDUs, sensors, and jump services.Permit only approved administrative paths and protocols.
ActivationDefine always-on, on-demand, or event-driven access and authentication.Log, alert, expire, and review every use of the recovery channel.

The end-to-end path

  1. CELLULAR ACCESSIndependent carrier pathLow-bandwidth recovery transport
  2. OOB GATEWAYFirewall · VPN · MFARestricted administrative entry
  3. MANAGEMENT PLANEConsole · PDU · interfacesDiagnosis and remote control
  4. PRODUCTION EDGERouter · firewall · WANThe system being recovered

Out-of-band is not general backup internet. Its narrow purpose is secure diagnosis and recovery when production paths are unavailable.

How the result is tested

  • Isolation test Remove the production WAN, firewall, routing, DNS, and management VPN.
  • Power test Exercise utility, UPS, PDU, and gateway restart scenarios.
  • Console test Reach every approved device and perform a controlled recovery action.
  • Security test Verify MFA, authorization, source restrictions, logging, and session expiry.
  • Carrier test Measure cellular availability and antenna conditions at each site.
  • Drill test Run a documented recovery exercise with the on-call team.
Practical next step

Tell us about the sites that need to stay online.

Share what's happening and where. We'll recommend the right fix and the next step, starting from your floor plans or site details.

Start your project