Skip to main content

MPLS vs. Ethernet: Which WAN connectivity option is best?


MPLS vs. Ethernet for the WAN
Cost MPLS typically costs more than Ethernet but less than T1 lines. Ethernet is typically more affordable than MPLS.
Scalability MPLS can scale to over thousands of sites. Ethernet can scale to up to hundreds of sites.
Common applications MPLS is best and most widely used to interconnect data centers with branch offices and branches to other branches. Ethernet is best for interconnecting data centers.
WAN routing MPLS allows businesses to leave WAN routing to the service provider and keep fewer WAN engineers on staff. Ethernet gives WAN engineers control and responsibility over routing.
WAN protocol behavior MPLS can handle any-to-any connectivity, including voice and video. Ethernet offers low-latency and high-throughput, which is ideal for disaster recovery.
Quality of service MPLS has quality of service (QoS) options to enable preferential treatment of latency-sensitive traffic like VoIP. Network engineers can bypass QoS complexity by hooking switches directly to Ethernet pipes.
Service level agreements MPLS services come with service-level agreements (SLAs) that include delivery guarantees, unlike consumer broadband. IT professionals should either ask for an SLA for their Ethernet service or take WAN application delivery into their own hands.
WAN management Using MPLS for WAN connectivity requires that all network devices and management tools be compatible with both MPLS and Ethernet. Because LANs use Ethernet, using Ethernet for the WAN gives organizations an all-Ethernet infrastructure, which simplifies network management.
Availability Many service providers offer MPLS services in some metropolitan areas, but not everywhere. Ethernet exchanges have made Ethernet WAN services available in more locations.

Read the full article over at Tech Target here.

Ronald Bartels on Medium

Comments

Popular posts from this blog

Why Madge Networks, the token-ring company, went titsup

There I was shooting the breeze with an old mate. The conversation turned to why Madge Networks which I wrote about here went titsup. My analysis is that Madge Networks had a solution and decided to go out and find a problem. They deferred to more incorrect strategic technology choices. The truth of the matter is that when something goes titsup, its not because of one reason only, but a myriad of them all contributing to the negative consequence. There are the immediate or visual ones, which are underpinned by intermediate ones and finally after digging right down, there are the root causes. There is never a singular root cause for anything but I'll present my opinion and encourage everyone else to chip in. All of them together are more likely the reason the company went titsup. As far as technology brainfarts go there is no better example than Kodak . They invented the digital camera that killed them. However, they were so focused on milking people in their leg

Flawed "ITIL aligned"​ Incident Management

Many "ITIL aligned" service desk tools have flawed incident management. The reason is that incidents are logged with a time association and some related fields to type in some gobbledygook. The expanded incident life cycle is not enforced and as a result trending and problem management is not possible. Here is a fictitious log of an incident at PFS, a financial services company, which uses CGTSD, an “ITIL-aligned” service desk tool. Here is the log of an incident record from this system: Monday, 12 August: 09:03am (Bob, the service desk guy): Alice (customer in retail banking) phoned in. Logged an issue. Unable to assist over the phone (there goes our FCR), will escalate to second line. 09:04am (Bob, the service desk guy): Escalate the incident to Charles in second line support. 09:05am (Charles, technical support): Open incident. 09:05am (Charles, technical support): Delayed incident by 1 day. Tuesday, 13 August: 10:11am (Charles, technical support): Phoned Alice.

Updated: Articles by Ron Bartels published on iot for all

  These are articles that I published during the course of the past year on one of the popular international Internet of Things publishing sites, iot for all .  These are articles that I published during the course of the past year on one of the popular international Internet of Things publishing sites, iot for all . Improving Data Center Reliability With IoT Reliability and availability are essential to data centers. IoT can enable better issue tracking and data collection, leading to greater stability. Doing the Work Right in Data Centers With Checklists Data centers are complex. Modern economies rely upon their continuous operation. IoT solutions paired with this data center checklist can help! IoT Optimi