WAN AND INTERNET CONNECTIVITY

Metro Ethernet and Internet Line Management

We plan internet breakouts and links between branches according to the capacity and availability needs of applications. We check line delivery, the physical route and the services that keep working when the main link goes down, each separately.

The architecture is settled before lines are ordered

We verify that the backup line works with a failover test done by shutting down the main line.

SERVICE SCOPE / 01

Sites and internet breakouts in a single plan

If carrier lines, branch access, firewall connections and application dependencies aren’t handled together, a second line may not deliver the expected continuity.

01

Current traffic

Hourly usage and peak load analysis

02

Continuity

WAN failover and route verification

03

Operator

SLA, demarcation point and escalation

04

Observation

Latency, packet loss and access quality

METRO ETHERNET / 02

Metro Ethernet or site-to-site VPN?

Metro Ethernet is a Layer 2 connectivity service offered by the carrier over an Ethernet interface. There are point-to-point and multipoint service options. If the carrier also takes on IP routing, that is assessed separately as a Layer 3 managed WAN service. The handoff type (tagged VLAN or untagged port), MTU, committed rate (CIR) and the routing setup at both ends are settled before commissioning.

CriterionMetro EthernetSite-to-site VPN
LatencyDepends on the carrier’s service terms; usually more consistentDepends on the internet path
CostHigherUses existing lines
SetupRequires a site survey and lead timeQuick to deploy
Suitable useVoice, ERP, central storageSmall branches, backup path
ENGINEERING APPROACH / 03

Overlooked topics in WAN design

Connection type, redundancy and measurement are handled together; speed, contract and outage information is kept in one place. Fault tickets with the carrier are opened with measurement data and followed until closed.

01

Line profile

Symmetric/asymmetric capacity, static IP, CGNAT, handoff type and SLA terms are defined.

02

Two lines, one policy

Route priority, health checks and what happens to open sessions during failover are settled in advance.

03

Failover and monitoring

DNS/VPN dependencies, carrier communication and the chain of responsibility during a fault are defined in writing.

REDUNDANT INTERNET BREAKOUT / 04

How do we plan a backup internet line?

We handle redundancy under three headings: physical separation, automatic failover and regular testing.

A different physical path

If two lines enter the building by the same route, a single dig can cut both. A different carrier may not mean different physical infrastructure. We verify the last mile, building entry, route and shared equipment separately as far as possible.

Automatic failover

The firewall or router fails over based not on the line’s link state but on whether it can actually reach the internet (health check). A port showing as connected doesn’t mean the line works.

Traffic steering

Voice and critical applications can be steered to the more stable line, and backup and update traffic to the other.

Regular testing

The main line is shut down in a planned way; the failover time and affected services are recorded.

MEASUREMENT / 05

How do we measure line performance?

The source of the “the internet is slow” complaint isn’t always the line. When latency, jitter and packet loss are measured continuously, you can tell whether the problem is with the carrier or the internal network. These measurements support the fault ticket opened with the carrier.

Values we measure

  • Latency: round-trip time to a fixed point
  • Jitter: directly affects voice and video call quality
  • Packet loss: can reduce TCP performance even at low rates
  • Utilization: shows at what times the line saturates
  • Outage records: duration and frequency, for SLA tracking
CONCRETE DELIVERABLES / 06

What will you have at the end of line management work?

A diagram of links between sites, a line and service provider inventory, backup line failover test records and measured performance values.

A documented, verifiable result

01

WAN link and carrier inventory

02

Line usage and quality assessment

03

Redundancy and failover test plan

04

Carrier escalation and change records

FREQUENTLY ASKED QUESTIONS / 07

Let’s clarify a detail

If you have a question specific to your network, write to us; we’ll look at your current setup and give you a clear answer.

01

Does a second internet line guarantee uninterrupted connectivity?

No. Unless dependencies such as a shared physical route, device failure, DNS and session behavior are handled separately, a second line alone isn’t enough.

02

Is it necessary to get lines from two different service providers?

It isn’t necessary. Two lines from the same provider can be affected together in a provider-side outage. Choosing a different provider doesn’t by itself provide different physical infrastructure either. The decision is made based on budget, the infrastructure options in the area and route verification.

03

Do VPN connections drop when switching to the backup line?

Some sessions may be interrupted during failover. The new line’s IP address, NAT behavior and the time to re-establish the tunnel affect the result. In the failover test, we measure the VPN and users’ renewed access to critical applications separately. If branches will reach each other over the internet, design the identity and access rules within enterprise VPN and secure remote access.

04

Do you handle communication with the service provider?

If you authorize us, we open fault tickets, support them with measurement data and follow them until closed. Contract and commercial matters stay with you.

ERETEK NETWORK

Let’s plan your sites and internet breakouts together

Let’s start with the speed, contract and outage information of your current lines, and set redundancy and measurement needs based on that data.