We set out to create a resource to specifically help IT Managers compare MPLS, VPLS and SD-WAN providers / vendors.
If you’re in the market for MPLS WAN connectivity, you’re probably looking for a single resource that lists the most prominent providers/vendors for Global and UK business.
Within our WAN Purchasing Group, we are often asked our opinion of vendors. Because we believe strongly in answering the questions we are asked, we put together a comparison list of most prominent UK and Global MPLS providers to help kickstart your project.
Due to legal reasons, we're no longer able to list each provider on
As you vet the various providers, please remember that although all providers have a basic capability, you'll need to evaluate across many key areas to avoid a procurement mistake.
If you'd like a reliable guide to assist in researching your WAN providers, check out our WAN buyers Mindmap below.
We'll start with the top 3 challenges.
The age old problem, how to ensure your UK or Global MPLS provider is clear and transparent with their marketing?
The majority of service related detail is hidden behind the scenes. In order the gain the clarity you require, it is imperative to align your own business requirements with each key area of provider capability.
Easier said than done but our provider checklist Mindmap will put you on the right track.
Create a statement of networking infrastructure requirements from strategy through to security and beyond. The creation of a VPN Statement of Requirements (SoR) document requires looking inwardly into your existing MPLS capability from the perspective of strengths and weaknesses.
Consider how your existing WAN is performing as a bottleneck to the business. What areas of improvement would result in the WAN becoming an enabler?
There are risks, pitfalls and opportunities when comparing, delivering and supporting an MPLS WAN. Some of which simply cannot be avoided and will create impact and delay to your project.
We strongly recommend using our free content to deliver a risk statement back into the business.
We know IT teams are busy. With this in mind, we worked to create a single document outlining every key WAN buying area together with technology comparison.
SD-WAN, MPLS and VPLS are all compared. Delivery, application performance, reporting, user flows are outlined to ensure your team consider every important area.
Some years prior to writing this article, we made a major mindset and strategy shift within our business. We previously worked as a consultancy producing bespoke private Ethernet layer 3 MPLS and layer 2
We were not aware at the time but we were essentially conducting research into some of the key vectors, risks, pitfalls and opportunities which surround WAN procurement.
The realisation dawned on our team that, although the procurement of both layer 3 and layer 2 WAN technology would always be challenging, we could arm businesses and their IT teams with the best possible network infrastructure procurement process.
A blueprint guide to WAN comparison success.
Today, the process outlined within the Mindmap forms the very basis of our business workflows.
What follows in this article, is an overview of the areas which are the focus of our BT Authorised Business partnership today.
The point is this - that the Enterprise WAN is rarely a single product. Moreover, today’s network architecture is created using numerous solutions & products, a hybrid design of managed capability vs requirements.
I will admit, the commodity mindset certainly simplifies the infrastructure procurement process of networks. The required tools are a copy of Excel; your businesses site list, some approximate Ethernet line bandwidths and a column named
However, the risk is high since there is no alignment of your business specifics with the capability of the global and UK MPLS market space.Creating an MPLS providers list The issue we face is in the level of analysis of existing situations. In other words, the problems of the past are not solvable by the process which created them in the first place. Our opinion is that Enterprise WAN architecture design begins with your business specifics.
The issue we face is in the level of analysis of existing situations. In other words, the problems of the past are not solvable by the process which created them in the first place. Our opinion is that Enterprise WAN architecture design begins with your business specifics.
Any organisation which leads their given field will understand the need to ensure core processes are efficient and accurate. When dealing with any company (whether Business to Business or Business to Consumer), you will know yourself how satisfying the sales process is when it just works.
With the right managed telecoms capability in place, companies move forward smoothly to the next project, application, or feature which relies on WAN or ISP connectivity. In the majority of situations, a hybrid WAN design is now the norm with networks architected as both layer 3 and layer 2 connectivity from MPLS networks and across Internet circuits.
Above. The Mindmap to help your business compare MPLS providers.
Gaining insight into Enterprise VPN application types, their flow and any given sites trend over time requires a reporting tool of some type.
In some instances, the capability of existing reporting is poor, perhaps only detailing bandwidth usage. If applications are running well, with no user issues, there may be
Interviewing a subset of users about performance will provide a basic insight and should be completed regardless of stats availability. The issue for your IT team is that any reports of slow applications may relate to the LAN, the users PC, services and so on and not the WAN. The ideal base level of your IP VPN sites statistical data would surround individual application type, usage trend, latency performance, QoS (Quality of Service) and any associated downtime.
A comprehensive level of line stats will allow your team to understand how traffic flows move and where the potential for congestion or downtime may occur. Armed with this information, cost effective scalable VPN bandwidth options are a possibility from your prospective UK or Global MPLS provider comparison list.
The ideal base level of your IP VPN sites statistical data would surround individual application type, usage trend, latency performance, QoS (Quality of Service) and any associated downtime.
There are clearly some sites which are more important than others including small broadband offices with ADSL / mobile 3G / 4G connectivity that may not require a comprehensive level of stats.
The real reach of
To force transparency, any reader considering the solutions from MPLS providers should ask to see true service Provider Edge coverage. The impact of low PE coverage is
A small country will not suffer a huge amount from a latency perspective since even with extended local loop tail circuits, the traffic paths will not be excessively long. However, when creating your international businesses network architecture, optimal data performance for
The distance between metro PE nodes and your office lines has the potential to add significant latency. Network infrastructure and Line Diversity - over and above potential latency impact, Ethernet IP VPN diversity is up next. With a low MPLS PE coverage, your office sites have limited options when connecting to prospective network services. Whether low diversity coverage is an issue is largely dependent on your requirements and location quantity.
Businesses with significant reach should carefully consider the true provider edge reach in order to understand the potential impact to their business. On another note, we also recommend requesting the structure of the POP where the MPLS PE is located in terms of security, fire suppression, battery backup and so on. We know of several UK and Global MPLS
Diversity and resiliency also require a focus at the broadband / ADSL / EFM (Ethernet First Mile) level since many providers aggregate traffic within their networks. Dual aggregation points should be available to maximise uptime across broadband / ADSL / EFM. This applies to fibre and ADSL2. Additional diversity is available by the use of BGP (Border Gateway Protocol).
Above. Aligning networking requirements has this result if done incorrectly.
Statistics and reporting are the key
With services such as cloud-based computing, sophisticated applications and users consuming bandwidth resources from all manner of connectivity, IT teams need to be more informed than ever. The solution trend today is for application-aware stats which allow businesses to really understand, at a granular level, how particular applications are performing from the perspective of uptime and latency.
Over time, trends will appear allowing IT to predict where bandwidth upgrades are required or whether other technologies such as WAN acceleration may assist to improve network performance. QoS policy (Quality of Service) creates an environment where we are able to prioritise applications based on importance.
Over time, trends will appear allowing IT to predict where bandwidth upgrades are required or whether other technologies such as WAN acceleration may assist to improve network performance.
However, setting the prioritisation bandwidth is difficult without understanding usage over time.
When considering MPLS services, reporting is more important than ever with traffic originating via multiple wholesale providers with different support methodologies and performance. We have mentioned additional latency from extended tail circuits - viewing stats over time will inform the business where possible improvements may be required.
CoS - Quality of Service settings CoS - Quality of Service settings. We also note an emerging Enterprise technology within the statistics solution arena which is reporting down to host level. This means your organisation will be able to understand exactly where issues exist from a users laptop across the LAN and WAN.The way in which this functionality is achieved is by using an agent which is installed on the
The way in which this functionality is achieved is by utilising an agent which is installed on the
This new style of reporting makes it easier to manage MPLS service providers since the entire LAN and WAN is available for review.
A real tangible reason why IT Managers decide not to proceed with MPLS provider change surrounds the fear of networks change and associated migration. However, the problematic experience suffered by the majority of global and UK businesses is because expectations are not set correctly.
There is no doubt about it, WAN migration is a difficult and challenging experience but there are key areas where attention to detail will remove some of these frustrations. In addition, you are not the first company to migrate their WAN and therefore the risks and pitfalls should be made totally clear up front in the form of a project plan. The plan should contain notes and feedback as to where delays may occur and the remedy if issues require resolution.
Clearly, not all issues are known up front (
A discussion regarding actual customer migration technique should also form a key part of your investigations.
There are numerous ways to migrate from one supplier to another but the key is supportability of any proposed options. In the main, the HQ site is the last to migrate which will require dual running of providers and solutions for a short period of time.Unfortunately, UK or Global MPLS migration and provision is more challenging than their national counterparts. In-country language, import restrictions, time differences, holidays all conspire to add a layer of complexity.
Unfortunately, UK or Global MPLS migration and provision is more challenging than their national counterparts. In-country language, import restrictions, time differences, holidays all conspire to add a layer of complexity.
Perhaps one of the most frustrating aspects of dealing with MPLS providers surrounds making changes throughout the contract. Fortunately, this is one area where innovation is occurring with the advent of new customer portal systems where simple changes to bandwidth, QoS (Quality of Service policy) and change requests are made with simplicity.
The portal approach will allow your enterprise to track previous changes, log new changes and generally access data surrounding your network and lines. Your services references, circuit line ID’s, contract terms, bandwidth and so forth should all be clear, at a glance, via a shared portal of document storage system. The days of a high-level fluffy Visio network diagram existing on a team members laptop should be over as the risk of out of date versions and lost data is high.
The change and documentation process should form a key component of your procurement investigations - ask the view systems and dummy data.
Above. Migrating your provider network.
We've discussed MPLS PE coverage previously - an example of where asking the right questions regarding reach will arm your team with the best possible idea of how capable any given service provider is to meet your requirements. Our preferred sales approach is one where a provider aligns your business specifics with their particular product set which clearly sets out the capability of any given service.
The new era of sales is one of expectation setting whereby each member of the team understands the impact of decisions vs their procurement project. In other words: Requirements > Capability > Expectations and Impact.
Not a particularly exciting aspect of MPLS providers but an area of services which are necessary to scrutinise. The support and management of any MPLS solutions
A portal system is of use to both log tickets and
We often find that UK and Global
The WAN is rarely a single product. More over, today’s architecture is created using numerous products, a hybrid design of capability vs requirements.
While a provider may have a significant support team in one particular country, this may not be the case when looking at other locations.
First, never engineer a global or UK
The SLA will normally include commitments to circuit line delivery, circuit uptime, application performance per QoS setting, and support fix times. The delivery of circuits is subject to many moving parts and while the SLA may commit to (for example) 50 working days, the reality may be somewhat different. Will service credits really make up for incorrectly setting expectations internally within your business? The same scenario exists for support and time guarantees.
An SLA which commits to 100% uptime (some leased lines for example) looks great on paper but is of little consolation if your service is down for extended periods of time. In short, the SLA should be used as a high-level indication of line and service performance. The reality should be considered by putting in place the best possible design vs your requirements.
We would be remiss if an article went out without at least one mention of cloud-based services. And rightly so since the
The default 'networks' procurement approach is to ensure a provider also offers cloud-based services. However, there is no reason why cloud services cannot be procured outside of the WAN. In reality, the discussion of cloud deserves a separate article which we will release soon.
Where the Enterprise has a requirement to manage their own network infrastructure capability at layer 3, a VPLS VPN provides the option of adding your own layer 3 routing. In some instances, carriers and telco's do not support certain IP traffic or routing setups, in which case a managed in-house or 3rd party solution is applicable via VPLS with layer 3 overlay. In addition to VPLS, VLL (Virtual Leased Lines) are a evolution of MPLS - point to point or multipoint pseudowire line (emulation) over geographically extended distances.
The point is this - that the WAN is rarely a single product. More over, today’s architecture is created using numerous products, a hybrid design of capability vs requirements.
Above. The MPLS provider SLA (arty picture taken from one of our Cisco books!)
There are certain scenario's where your business may require to extend your UK or Global MPLS providers capability. The comparison of NNI providers is a little more difficult.
As an example, mergers and acquisitions will create a challenge if your existing
The focus should be on the demarcation of each service within the DC as a situation may occur with support where each provider will blame the other for problems making troubleshooting protracted and troublesome. From a topology and design perspective, the involvement of more than one provider will create additional latency due to the multiple HOP's involved.
And, QoS (Quality of Service) will need to be passed between each provider or remarked by an intermediate device. We have some experience of creating MPLS designs across multiple providers, get in contact to discuss the challenges.
The security of a layer 2 and layer 3 VPN based on MPLS is, in general, a given and certainly not a cause for concern.
The security of a layer 2 and layer 3 VPN based on MPLS is, in general, a given and certainly not a cause for concern. There are some customers such as government or financial which will require further added security in the form of encryption.
It is not uncommon to find customers adding IPSec across their private VPN to further secure traffic. Where a combination of private networking security and IPSec is not enough, the only ultra secure alternative would be to consider dedicated fibre. while no connectivity is totally secure, today's networks are by nature, fine for most businesses.
We have witnessed
However, this approach is normally based on a commodity buying process - i.e. the lowest cost of networks outputted by multiple carriers, telcos and providers in the market place. Companies such as BT only utilise Open Reach tail circuits, others will aggregate multiple tail providers to achieve the best possible costs. There are benefits to each approach. The choice of provider or reseller will often be assisted by the sector which you operate within, i.e. Government, Local Council, Education and so forth.
The sector experience applies to both the service providers and their resources. I.e. when meeting with project managers and account managers, their sector experience is a real plus point. Each sector (as you will no doubt understand) has specific challenges and regulations which exist. An understanding of each sector will alleviate potential pain points when creating your proposal. Lastly, consider the expertise of any reseller carefully.
There are numerous IT companies with a core ability in, for example, IT support that are moving toward the WAN reseller model. However, while they may have a good core expertise, they may add only limited value within their MPLS or
MPLS Providers and Further reading:
Private MPLS (Multi-protocol label switching) VPN product page
Routers - Learn more about Layer 3 Routing
Learn more about Layer 2
Frame Relay Service - Wiki on Frame Relay (Legacy technology)
ATM - Wiki on ATM (Legacy technology)
EFM - Ethernet First Mile
GEA - Generic Ethernet Access
ADSL - Article on DSL technology
Broadband - Article on Broadband technology
Cisco article on QoS for video
Routers and Quality of Service / Class of Service - An article on QoS / CoS
An article on network security