Cisco & Meraki specialists. Across the UK.
+44 203 196 6566 · option 1sales@proxar.co.uk

Connect. Secure. Manage.

Dual Internet Connection Design

Design dual internet connectivity for Cisco or Meraki sites, considering carrier diversity, routing choices and real application failover requirements.

Cisco Partner since 2009 Projects & ongoing support

Illustrative Cisco and Meraki equipment in a modern data-centre aisle
Your network. Properly considered.Design · Implementation · Support
1,000+

Devices supported
across the UK

20+

Client locations
supported

Nearly 8 Tbps

Traffic handled
at peak time

3 min

Average
response time

Average response is not a resolution time or a contractual guarantee. Support scope and response commitments are agreed for each engagement.

Dual internet connection design gives a business an alternative path when its preferred connection fails, but the outcome depends on more than installing a second line. Addressing, physical diversity, routing and application behaviour determine whether the backup is useful. MCI Network Services designs Cisco and Meraki connectivity around the failures the customer needs to withstand and the service that can realistically be delivered while one connection is unavailable.

01

The whole path

Understand how sites, providers, cloud networks and security controls fit together.

02

Resilience that can be tested

Separate a second circuit from genuine end-to-end service resilience.

03

Provider coordination

Keep addressing, routing and escalation ownership clear across organisations.

Define the purpose of the second connection

The second service may provide standby access, share normal traffic or support a particular application. We establish which objective applies and how it should affect routing and security policy. A design intended only for emergency browsing should not be presented as equivalent to continuous operation of inbound applications and site-to-site services.

We identify the important workflows and their tolerance for interruption. Voice, remote access, cloud sessions and externally allowlisted connections can react differently when the path changes. The requirement should describe the business outcome rather than rely on the assumption that every application automatically follows a new default route without consequence.

Illustrative Cisco and Meraki data-centre network infrastructure
01Network infrastructure designed around the workloads it carries.
Cisco PartnerCisco Partner
Cisco MerakiCisco Meraki
ISO 9001Quality management
ISO 27001Information security
Cyber EssentialsCyber Essentials
Cyber Essentials PlusCyber Essentials Plus

MCI Network Services is operated by Proxar Ltd. Certifications apply to the certified legal entity and the scope of its certificates. View accreditation information

Check genuine provider and physical diversity

Different supplier names do not necessarily mean independent infrastructure. We review the available evidence about local access routes, building entry, provider equipment and upstream dependencies. Where diversity cannot be confirmed, the design records the uncertainty instead of claiming that the second service protects against a shared cable or carrier failure.

The local environment matters too. Both circuits may terminate on one powered device or depend on the same switch and electrical feed. We examine those shared components and decide whether the availability requirement justifies changes beyond the internet services themselves.

Illustrative enterprise Cisco network rack in a modern office environment
02Enterprise switching and routing, built to be operated.

A useful starting point

Not sure where to start?

Bring the requirement. We will help you define the engineering work.

Talk to a specialist

Choose the routing and addressing approach

The appropriate method depends on the public addressing and services in use. Some businesses can use supported static or tracked routing, while others need a more involved multi-provider arrangement. We do not assume BGP is required simply because two circuits exist, or that provider-assigned addresses can be used unchanged through another network.

Outbound translation, inbound applications and VPN endpoints are reviewed together. A different public source address can affect external security rules, and a published service may need DNS or other recovery mechanisms. Those dependencies are included in the plan before failover is described as complete.

Illustrative Cisco and Meraki network rack in a modern office
03The office network: switching, uplinks and structured cabling.

Design health checks around usable service

A physical interface remaining up does not prove that the provider can reach the destinations the business needs. We assess the supported detection mechanisms and the conditions that should trigger use of the alternative path. The chosen signal should reflect meaningful service availability without causing repeated changes because of one unreliable test destination.

Recovery thresholds and restoration behaviour are also considered. A preferred connection returning briefly after a fault can create another interruption if traffic moves back too quickly. We test the supported behaviour and agree the appropriate operational response instead of treating the default settings as universally suitable.

Illustrative Cisco and Meraki fibre network rack with structured cabling
04Fibre, switching and the physical path behind the service.

Plan capacity and security during failover

The backup may have less bandwidth, different latency or usage constraints. We identify which applications remain essential and how traffic should be treated when the preferred path is lost. A reduced-service plan can be more useful than an unrealistic promise that every workload will operate normally through a much smaller circuit.

The alternate path must retain the required security controls. Directly connecting a backup modem around the normal firewall may restore access while bypassing protection. We review the full traffic path and ensure the customer understands any deliberate difference in inspection or policy during an outage.

Illustrative Cisco and Meraki network operations centre with monitoring displays
05Visibility, monitoring and operational control.

Test application behaviour from real endpoints

Acceptance includes representative user and server workflows before and after a controlled failure. We observe source-address changes, VPN recovery, DNS behaviour and the treatment of established sessions. A device's failover status is not sufficient evidence that an external application accepted the new connection.

Restoration is tested separately, with clear stop conditions and a route back if a critical service is affected. The record states which faults were exercised and which remain design assumptions. This gives the operations team a realistic view of what the dual-connection arrangement can deliver.

Illustrative Cisco and Meraki equipment in a modern data-centre aisle
06Resilient infrastructure from rack to service path.

Make the backup an actively maintained service

A standby circuit needs monitoring and periodic checks even when it carries little normal traffic. Provider changes, expired subscriptions or altered upstream equipment can leave it unavailable when needed. We assign responsibility for those checks and keep contact and configuration records current.

MCI can assess an existing pair of connections or prepare a new design within a wider internet edge network. Share your circuits, public services and continuity priorities. We can identify the addressing, routing and operational work needed to make the second connection a useful recovery path rather than an untested extra expense.

Illustrative Cisco and Meraki data-centre network infrastructure
07Network infrastructure designed around the workloads it carries.

Technical references

Illustrative enterprise Cisco network rack in a modern office environment
08Enterprise switching and routing, built to be operated.

Talk to a specialist

What does your network need next?

Tell us what you are planning, changing or trying to improve. We will help define a practical next step and the engineering scope.

+44 203 196 6566

Choose option 1

sales@proxar.co.uk

UK-wide service.
Most of our engineers are based in Kent, with a focus on London, Sussex, Essex and Berkshire.

Existing customers should use their agreed support and escalation channels. This form is for service enquiries, not a monitored emergency ticket.

Tell us what you need.

A short outline is enough. Please do not include passwords or sensitive network details.

Thank you. Your enquiry has been submitted.

We’ll use these details to respond to your enquiry. Please leave out passwords and sensitive network information. Read our privacy notice.