Companion resource: The Techtarget version of our free IT Managers step by step Global MPLS Network procurement Mindmap. Every risk, pitfall and opportunity outlined at a glance.
In this article, I share my thoughts on successful WAN sales process surround creating a diagnostic environment.
An approach which considers your existing VPN strengths and weaknesses which relate to specific areas within global MPLS network procurement is a good foundation for WAN procurement execution. However, I also consider expectation setting to be the next area of value led sales, particularly when buying Ethernet telecoms services such as a secure and private global MPLS network capability. One of the main consistent feedback points we received during our own WAN procurement research told us that IT teams are better placed to work around problems and issues if expectations are set up front. When expectations are known, contingency plans are built and senior members of the business at least know the potential impact and are able to react accordingly – perhaps delaying a project and so forth.
With this in mind, I thought I’d write content on some particular areas which relate to global MPLS procurement – at layer 3 and layer 2. There are indeed some specific challenges which relate to the global arena vs their national counterparts. In this article, we’ll discuss some of the main areas to consider. MPLS and VPLS services offer fantastic scalable and fractional bandwidth with 100Mbps Ethernet as the standard with a high prevalence of 1Gbps Ethernet circuits.
There are multiple areas to consider when writing about global MPLS network procurement, if we were to write about every single area in one article, you would end up with an ebook. Statistics, reporting, change process, routing, strategy and so forth all deserve an article of their own. With this in mind, I will continue to write more content moving forward.
We talk about transparency a fair amount within our day jobs. In any complex services arena, potential customers need to be sure the service providers they are working with are providing the necessary data and information outside of marketing collateral. In order to be sure this is the case, we recommend the creation of an RFI (Request for Information) which asks relevant questions to force the required detail on capability.
Some of the key RFI areas are follows (Request our template)
Carrier and Provider Reach – PE (PROVIDER EDGE)
IT Managers will no doubt be aware that a fair amount of marketing exists within the market place. Where service providers are professing to offer a high percentage of global coverage, the detail behind the marketing deserves careful consideration and thought. The capability of reach is governed by the scale of PE (Provider Edge) coverage. The PE represents the entry into an MPLS network, i.e. connectivity prior to the MPLS Provider Edge will be based on tail circuit local loop circuits. Application latency will normally be predicted by service providers as an average across their core network. When considering global networks, the performance of delay sensitive traffic such as voice and video may be within latency parameters (SLA) at first glance but the addition of local loop delay may render the application unusable. When armed with the data regarding global MPLS network PE coverage, it is possible to approximate the distance from the PE to your office which will allow your team to estimate latency delay. Readers should note that a local loop circuit does not travel in straight lines and therefore any estimate of tail circuit length is just that, an estimate. In our work we often ask the provider to demonstrate live ping data from their PE to existing clients CE (Customer Edge) devices. The live data will also help to predict performance.
VPN Resiliency and Diversity
Leading on from our discussion on PE to CE latency, adding an Ethernet failover circuit will mean using a secondary PE device within the providers network. A second PE device will require a diverse secondary tail circuit which may extend the VPNs local loop length vs the primary tail circuit. The failover circuit additional tail length must also be considered to calculate the impact to applications if the primary fails.
We have witnessed designs which implement a second tail circuit using an alternative wholesale provider. Whilst at first glance this may appear to be a sensible option, neither provider will understand the tail circuit routing of each others local loop connectivity. The outcome will normally mean points of commonality through the VPNs network creating single points of failure. Organisations with a requirement to avoid any single points of failure should order a single provider product which is designed to route dual tail circuits with no points of commonality subject to survey.
The Business Factor
There is an ongoing initiative to gain clarity on Enterprise global MPLS network & VPLS architecture vs business strategy, technical, cost and budget. The VPN carriers and the service provider market via carriers and providers is feature rich which sounds, as you will no doubt agree, positive. However, IT Management are faced with aligning their business specifics with the capability of prospective service providers which requires transparency with regards to true ability. Over the years I have collated data from experiences working with and for large Enterprise organisations allowing me to understand the key areas which require focus to achieve the best possible procurement outcome.
The problems are varied but in the main reflect an un-balanced approach to WAN procurement. When working with customers, their focus was often too far aligned with the technical elements vs business needs or IT teams were highly motivated by reducing costs. There isn’t a right or wrong as some projects are successful depending on criteria but an approach which creates a balanced framework to bring the business, technical and budget together provides the best possible outcome. There is also the danger of a service provider sales process which only consists of features and benefits rather than a diagnostic approach to your problems, issues and projects.
The overall challenges remain the same but today’s technology advancements are adding a further reliance on WAN connectivity. The cloud, collaboration, remote users and so forth only operate efficiently when connectivity is an enabler and not a bottleneck to performance. With this last statement in mind, support, agility, performance, resiliency, adds / changes, application QoS, migration, service management and stats (to name just a few!) must be capable of meeting your unique business needs.
Challenges specific to Enterprise Businesses procuring Global MPLS Network connectivity
Global organisations are faced with some specific challenges surrounding VPN migration and support. When considering migration, the regulations which exist within each region may impact the delivery of services. In addition, time zones, local language, access restrictions, bandwidth availability and local IT capability all conspire against an organisation to ensure global WAN provision remains a challenge. With this said, your organisation is not the first to go through the process. The Mindmap we have created also contains notes on expectation setting which allows your IT team to communicate back into the organisation concerning potential risks and pitfalls. As an example, the migration section will detail the areas which require highlighting in order to set expectations.
We mentioned expectation setting as (perhaps) the new era of the carrier / telco / provider sales process. When setting expectations, it is possible to gain an insight into the areas where particular focus is required. An an example, the ordering of dual Ethernet tail circuits is normally viewed as a single order from a carrier perspective. This ultimately means that the failover circuit is not delivered / handed over until the primary is delivered. Not good if you are working to timescales. With this said, it is often possible to separate out the circuits ensuring the primary is delivered outside of any reliance on the failover circuit. This is really just an example of expectation setting, if you are armed with this information up front, the business is able to make decisions accordingly.
Hybrid WAN approach to Global MPLS Network Connectivity & networks infrastructure
The service provider arena is awash with acronyms and buzz, the cloud being one example. The past has often focussed on one particular product as ‘the standard’ all Enterprise organisations should adopt. However, today’s designs and business requirements dictate that a hybrid approach to WAN design is widely adopted. The use of MPLS, VPLS, VLL, IPSec and so on is more prevalent than ever as users expect to securely connect whenever and wherever they are located. As an example, the new Cisco iWAN capability provides a single device to terminate multiple connectivity types reducing complexity and cost. MPLS, VPLS & VLL offer a standards based private WAN infrastructure which meets high security standards required within Enterprise organisations today. These products offer some great business benefits, a hybrid approach ensures your business is able to deliver real value based on firm requirements.
Layer 3 and Layer 2 access types and design / advantages
We have mentioned technologies such as MPLS, VPLS and VLL within this article, let’s explain some use cases.
MPLS VPN – Multi Protocol Label Switching – A layer 3 VPRn (Virtual Private Routed Network)
We’ve written a fair amount of content regarding MPLS, readers wishing to learn more about the history of the protocol should visit either of the following articles:
In short, IT management refer to a layer 3 Virtual Private Routed Network as MPLS. Rightly or wrongly, the term MPLS is used to describe a private routed VPN. The correct term is therefore VPRn but, for the sake of continuity, we will continue to refer to VPRn as MPLS.
In today’s market place, MPLS offers a private based routed network either managed or unmanaged with a productised set of supportable features including QoS (Quality of Service) configured across a core / customers routers. MPLS remains the standard for all organisations looking to outsource connectivity for the majority of requirements. Available on an international basis with or without managed routers and devices.
VPLS VPN Networks – Virtual Private LAN Service
VPLS is not a separate service to MPLS. In fact, VPLS is an evolution of the MPLS protocol. The service provides much the same any to any connectivity with QoS (Quality of Service) support when compared to MPLS VPRn networks – the difference is that VPLS offers layer 2 access, stripping off layer 3. As an example, when considering data centres on a global basis, VPLS offers the ability to extend the LAN across geographical locations. Extending the LAN will enable resources to be added as required, irrespective of location. If readers imagine a scenario where further servers are required because a datacenter has reached capacity, an alternative site may be used and added to the same LAN. Clustering and resiliency is maintained across the layer 2 topology.
VLL – Virtual Leased Line
VLLs are a further evolution of the MPLS protocol providing point to point and multipoint Ethernet connectivity over distance. Often referred to as pseudo wire services, a VLL circuit offers greater reach vs dedicated fibre which is subject to distance limitations. However, whilst latency and security are clearly very good, the service is not comparable to dedicated fibre which is a per customer (not shared) wire speed latency product.
The majority of MPLS, VPLS and VLL services are based around 100Mbps Ethernet and 1Gbps Ethernet services.
Application Performance – Global traffic latency and jitter across office, mobile and cloud
We alluded to tail circuit length creating additional latency earlier within this article. When documenting your existing VPN applications and their usage profile with future project and strategy, an indication of real world performance should be profiled. The majority of international providers and carriers will offer global MPLS network capability directly connected to their backbone within major cities and regions. However, the prevalence of mobility with cloud means a fair amount of traffic could / will originate from various locations across the world. The impact of regional connectivity is that certain content may need to be restricted to avoid user dissatisfaction. Applications are becoming more connectivity aware and will not operate unless optimal conditions exist. In either scenario, aligning user applications, there profile and potential access points will allow your business to understand implications.
General network advice
Overall, the procurement of global networks, multi protocol label switching or otherwise, is perhaps more challenging vs national provisioning for the reasons we have outlined. As we move forward with VPN content, we’ll update the section at the end of this post with further recommended reading. Our intent is to write more about MPLS networks and connect their migration challenges together with video tutorial content.
The evolution of predictive analytics technology continues to be something to keep an eye on in 2015. Although the technique is nothing new to the average consumer – we see it every time Netflix recommends a movie or Facebook places an ad on our news feed – it might be time to pay closer attention to the affect it could have in our work lives. Whether that impact is negative or positive is too early to determine, but one thing is certain: Technology companies are creating big data analytics software to monitor employee activity and the sophistication and capabilities of that technology are steadily increasing.
Take Workday. The company’s cloud-based human resource management software is used by hundreds of organizations to oversee their employees.
Back in November, Quentin Hardy wrote in The New York Times that Workday takes big data analytics and goes a step further than Netflix and Facebook. Instead of merely suggesting a movie or an ad to click on, Workday’s software is now capable of calculating which employees are most likely to leave a company or overspend their budgets. After collecting this information, Workday offers HR managers options that can range from job promotions to reprimands. It’s this type of dynamic analysis that sets Workday apart from other vendors, observers say.
“There are other vendors talking about ‘predictive analytics,’ but what I think is different about Workday is that they are looking at publicly available data, such as job postings, and not just aggregating customer data or bringing in a third-party data set,” said IDC Research Director Christine Dover, in an interview with TechTarget executive editor David Essex.
So on the upside, these kinds of predictive analytic tools can help companies increase productivity, reduce spending budgets and recognize employees who excel at their jobs. But for every upside, there is a downside.
Hardy, for example, wondered in his Times article what impact Workday could have on college students who haven’t even entered the workforce. As Hardy wrote, “Workday is also used for school recruitment: Should knowledge of what companies like to see on a resume affect choices in curriculum design, or the kinds of projects students work on?”
Hardy has a point. So much of the growth in technology depends on innovation, which flows from creativity. I like to believe that many people are naturally creative, and when groups of people come together to solve a problem or create a product, the answers come from a diverse set of ideas. If students start basing their curriculum choices on what they think will look appealing to potential employers, that desire to conform might end up making everyone too similar.
Students and employees already face enough pressure to impress their professors, bosses and colleagues. Will they now also have to bow to the whims of a piece of data analytics software?
Do enterprises and other organizations need a CDC-like entity to help them in their fight against cyber attacks?
The Society for Information Management (SIM) thinks they might. Madeline Weiss, director of SIM’s Advanced Practices Council (APC), said the group is evaluating whether it’s time to create what she terms “a CDC for cybersecurity,” modeled after the U.S. Centers for Disease Control and Prevention. To that end, an APC task force last month drafted a proposal for such a body, dubbed the CIO Coalition for Open Security. Its goal? To create a framework in which companies can work together, across industries, and share information about malicious cyber activities—much like the CDC collects data and issues bulletins about outbreaks and other health-related developments to the nation as a whole.
The APC is no slouch. The council comprises 33 senior IT executives, most of whom are CIOs employed by large multinational corporations and government agencies. Although the APC usually acts behind the scenes in an advisory capacity, the cybersecurity problem is so critical that the group has been spurred to action, Weiss said in an interview conducted at SIM’s annual meeting in Denver earlier this month.
A large part of that push came from David Bray, CIO of the U.S. Federal Communications Commission, who recently spoke to the group in his capacity as a guest lecturer at Oxford University. Bray delivered a dim and “extremely scary” scenario of the future of cybersecurity, Weiss said, followed by some ideas about what the industry can do about it.
“He made the point that no one organization, no matter how big they are or how well-equipped, can solve this problem,” Weiss said. “He said success is dependent upon collaboration and openness–open in the sense that there is sharing of attacks, and that there is sharing of potential, of possibilities and observations and solutions and that there should be sharing within private, public and governmental sectors.”
Similar efforts exist within other sectors, most notably in the pharmaceutical industry, where Eli Lilly’s InnoCentive acts as a repository of crowdsourced solutions aimed at tackling unresolved R&D problems. Such an approach for cybersecurity, Weiss argued, could be equally beneficial, providing companies with early-warning information and other data they need to thwart attacks. In addition, a CDC-like organization for cybersecurity could connect security problem solvers with those experiencing security issues. For example, it might be able to produce a map of distributed denial of service alerts or act as an information clearinghouse.
“Working together, we can address this issue,” Weiss said. “Working alone, we probably can’t.”
The next step is for the APC to sketch out the framework that would support the coalition, including soliciting volunteers who would lead the initiative.
“Members have done some investigation and learned that there are [similar] activities in various industries, but they seem to be staying within their industries — in other words, lots of silos,” Weiss said.
“We plan to sponsor research that will help us understand who the current key players are and determine what has worked and what hasn’t,” she added. “We then anticipate pushing for combining efforts where feasible to facilitate broader and more open sharing [of information].”
Organisations should never be forced into a features and benefits conversation with their prospective service providers. The majority of network designs produced by our BT Business partnership surrounds hybrid technologies, perhaps VPLS across data centres, layer 3 MPLS at branch sites, fibre services within the core and IPSec / SLL for remote users. In certain sites, it makes sense to deliver a layer 3 capability, in others (such as data centres) VPLS is the clear option to deliver capability. In metropolitan areas, fibre is always a good option. This kind of features and benefits sales approach will result in missed requirements and essentially a MPLS or VPLS network solution which is not fit for purpose.
A good accompanying resource is the Techtarget version of my MPLS and VPLS step by step IT Managers procurement Mindmap which is available upon request.
The mindmap examines in detail the process and considerations to make vs your own business requirements. The overall complexity is dependent on not only your requirements today but also those which need to be predicted in the future. The IT team’s work is becoming more critical than ever to communicate needs as globalisation, security, application performance, user productivity and disaster recovery is driving a critical reliance on WAN connectivity. The ultimate goal, as ever, is to maximise uptime of resources and plan for scenario’s which are unlikely but would impact the business in a major way. The WAN may appear as though innovation is fairly stagnant, we don’t hear too much in the way of significant evolution and buzz around WAN connectivity. However, applications are evolving faster than they ever have before due to enhanced productivity, different ways of working and a desire to achieve efficiencies and this a competitive edge.
What is VPLS Ethernet
Virtual Private LAN Service networks provide the ability for companies to create a LAN structure between geographically separate sites. The traditional and default choice for IT Management is generally considered to surround layer 3 VPRn (Virtual Private Routed Network) – known as MPLS in the market place. We believe the growth of VPLS services is driven by the ubiquitous access of Ethernet coupled with private cloud based services. We will go on to to explain more about our findings later.
The key benefits of VPLS solutions surround a number of key points.
Perhaps the most popular discussion surrounds the ability to extend data centre connectivity (or essentially sites which contain resources) across geographical separation. The dream is to deliver global or national connectivity whilst maintaining a base level of configuration and thus avoiding IP address reconfiguration which is required with layer 3 networks (MPLS – Virtual Private Routed networks). We are aware that globalisation is growing with data centres located in far flung locations, the challenge of deploying applications is made easier with VPLS layer 2 WAN services. A VPLS solution will extend the deployment of your server clusters into different data centres protecting against major disruption.
In another scenario, service providers and enterprises often do not meet in terms of requirements vs capability. There are some businesses which are reluctant to allow a service provider access to their layer 3 management and routing, Perhaps the organisation is needing to serve an unsupported protocol which the service providers will not transport. In this example, the ability to layer on layer 3 is a clear advantage for VPLS based connectivity.
It would be remiss not to mention VLL (Virtual Leased Line) services as they are closely related. VLL’s are designed to emulate point to point / multipoint fibre connectivity across an MPLS core network. The benefits are clear since MPLS provides the reach and emulation for circuits which would otherwise be too great in distance for dedicated fibre provision.
VPLS provides any to any connectivity using pseudowires – Virtual Ethernet circuits provisioned as a full mesh topology
VLL – point to point or multipoint Ethernet pseudowires
A pseudowire is essentially point to point emulation of Ethernet.
One important distinction to make: VPLS is an evolution in terms of capability which is built and created on the shoulders of MPLS core networks. The majority of IT managers believe that VPLS is somehow a different platform to MPLS but the reality is, MPLS core networks are the foundation for layer 2 connectivity. In other words, todays MPLS networks facilitate layer 2 and layer 3 connectivity.
Prior to VPLS becoming a mainstream technology, organisations were not only limited by distance related issues across layer 2 fibre but also dedicated high speed data circuits equalled high costs. The telco’s already owned significant core networks with layer 3 capability, the addition of a layer 2 VPN capability made sense.
Some serious benefits to consider
An organisation with a private cloud (their own hosting facility) requires further virtual servers on the same LAN segment. However, space is running out fast. In this scenario, a further data centre could be added with a connection into VPLS. Once connected, further virtual servers are able to be installed which will appear on the same connected LAN as the older full data centre facility. The plus point is clearly demonstrated to surround seamless LAN connectivity. The added benefits of a geographically separated site surrounds disaster recovery and resilience since the loss of a DC will ultimately partially remove some connected hosts but not all of them which offers greater uptime.
You have the desire and capability manage your own routed network. As the name suggest, the procurement of VPLS is at layer 2 which leaves layer 3 routing to be setup as required. Service providers set a base level of capability for MPLS.
We worked with a client recently which had decided to implement a cloud server cluster strategy for redundancy and scalability. With each cluster needing to reside in the same VLAN and network but with geographical separation for further redundancy, the organisation looked to VPLS. which enables extended VLAN. In addition, their data centres were encountering issues with power and cooling. The addition of a further datacenter allowed the client (as per point 1)
Consideration of VPLS vs MPLS
VPLS is built using a service provider product term called EVC’s (Ethernet Virtual Circuits). This is a marked difference when making a comparison to MPLS. The use of EVC’s is perceived as a scalability issue since, as network grows, the network performance may be impacted meaning there is an ultimate ceiling in terms of how many EVCs each provider router may support. The majority of providers will brush over scalability since their core networks are, over time, increasing in their ability to scale which increases their ability to support greater EVC’s. In the majority of cases, there is no need to worry or be overly concerned but clarity should always be requested depending on which provider readers are considering. On the counter point, MPLS (or rather layer 3 routed networks) are truly connectionless from the perspective of scalability.
VPLS network terminology
As I have previously mentioned, VPLS is a layer 2 VPN across an MPLS core network. When considering providers, procurement teams will often be faced with acronyms such as PE or P which refer to the edge and core devices within a network.
The PE device refers to the Provider Edge which is essentially the edge node into a service providers network. IT Managers are advised to understand the true PE capability of prospective service providers since PE coverage determines scale and diversity options. The P device is the ‘Provider’ core aggregation devices within the centre of their network used to scale the MPLS core network.
Some thoughts regarding VPLS network procurement
In general, VPLS is sold as an unmanaged service with Ethernet handoff. With this said, in some instances, the provider will offer a managed service whether this is based on a Layer 3 switch or a router. As with any WAN procurement project, the advice is to carefully consider the service capability vs your specific requirements. The Mindmap not only details some of the specifics of VPLS but also the key vectors we know to matter across application performance, uptime, topology, strategy and budget. In general VPLS services should be viewed in the same way as the more traditional layer 3 from the perspective of SLA which includes latency, jitter and uptime guarantees. Clearly an unmanaged service creates a very different adds, moves and changes process vs managed services. The typical approach when making changes is often surrounded by ‘clunky’ processes which creates delay. One of the real plus points of VPLS, as we have mentioned within this article, is the ease of self managed services. We are seeing growth within the managed services sector where organisations are outsourcing the management to specialist organisations which overlay their services with the providers supplying the connectivity. This, we believe, is a major shift in thinking since the traditional approach is to use a single provider for connectivity and management. VPLS is creating an environment of adoption which creates a little more freedom when considering how to manage services on an ongoing basis.
All of the concerns surrounding MPLS procurement are essentially the same when considering VPLS. We are in effect talking about layer 3 vs layer 2 which both using an underlying MPLS core network.
We have written a fair amount of content on WAN procurement, both MPLS and VPLS but the core of our approach remains the same. It is clear that organisations which achieve better outcomes when they are able to align their business specifics vs the service provider capability. In short, if you consider applications (as an example), our approach to execute WAN procurement involves understand how the application performs today but also how performance may be increased to improve productivity. In some instances, improving application performance may not relate to the technical aspects of a capability but perhaps admin tasks such as adds, moves and changes. As organisations begin to understand how each provider might provide a capability which adds a competitive edge, the WAN becomes and enabler rather than the typical bottleneck.
VPLS is a growing technology which, in part, is due to the emergence of cloud based solutions, whether private or public. Server clusters often require geographical diversity, VPLS networks add a unique capability here. The ability to add, remove servers as required across a layer 2 Ethernet WAN with any to any connectivity. The simplicity of layer 2 is now available across the WAN offering seamless connectivity on a Global basis. As a counter point, layer 3 services offer an out of the box routed network supporting a standard capability. As I wrote toward the beginning of this article, we are finding most project result in a hybrid approach for design. This means that VPLS is a another building block for organisations to use in their pursuit of connectivity and cloud excellence.
Additional reading: MPLS Network long form article
Wi-Fi connectivity is a great luxury to have in public places to power your favorite app, but what if your life-saving medical device relied on the wireless LAN to work?
Hospitals are using wireless devices and equipment — ranging from small patient monitoring sensors, to pharmacy inventory systems, all the way to large imaging systems — to care for patients. Needless to say, reliable, consistent Wi-Fi connectivity has become a critical network asset, rather than just a “nice to have” feature for many healthcare facilities.
As the Internet of Things (IoT) gains traction, Wi-Fi vendors are working to ensure they can offer their customers the functionality and management tools they’ll need to support the influx of Wi-Fi-enabled devices requiring network access and attention from IT. “It’s clear that for a lot of our customers, more devices are ‘turning on,’ or requiring network access, rather than just the typical user devices people are carrying in,” said Bruce Miller, vice president of product marketing for Xirrus, a Thousand Oaks, Calif.-based Wi-Fi vendor.
Healthcare certainly isn’t the only industry grappling with supporting IoT devices. However, most other verticals aren’t faced with the challenge of supporting devices that are saving lives. Xirrus is currently working with healthcare customers, as well as customers that develop Wi-Fi-enabled medical tools and devices for the IoT. Miller also highlighted some of the wireless LAN design considerations enterprise IT teams supporting IoT devices should know.
Right out of the gate, many medical devices aren’t easy for IT teams to support. This equipment often comes with low-end wireless cards because they don’t have high bandwidth needs — especially in the case of a sensor that is reporting patient data, not streaming live video. Additionally, healthcare environments are also very “noisy” from an RF and coverage perspective, Miller said. “There are a lot of devices than can interfere [with Wi-Fi signals] – we’ve even heard of up to 20 devices in one patient room,” he said. “The number of devices is getting extreme, and in some situations, that can pose a lot of challenges.” Most healthcare facilities are also filled with many small rooms with a lot of walls that cut signal strength down, and radiology labs with metal-coated walls that are difficult to penetrate, he said.
Xirrus is encouraging its healthcare customers to design for dense environments by deploying direct, in-room Wi-Fi close to the client. This means more access points are needed in an IoT-enabled environment.
Once the wireless LAN has been bolstered to address the sheer number of devices that need support, IT must be able to understand and identify all Wi-Fi-enabled equipment in their environment, Miller said.”It’s key to be able to separate out what kind of device something is, what it does, how it operates differently from another kind of device, and lastly, how it [needs to be] supported,” he said. “We’ve been doing this for a while — helping customers understand the difference between a laptop, tablet or phone, so now it’s just extending that visibility further.”
In addition to understanding what the device is, IT has to be able to make sense of the data coming from the device in an intelligent way. Then, the information must go to the right place, like patient stats to a monitoring nurse or physician or alerts to IT if a device has been moved or stolen, Miller said. “We’ve had to look at the health of…a greater variety of clients, and put those capabilities into our systems to allow IT to troubleshoot,” he said. If a device keeps disconnecting and reconnecting, or generating a lot of errors, Xirrus’ network management tools can monitor those network health stats and provide alerts to IT. “Sometimes, it’s as simple as updating a driver or software on a device, or maybe [the device] is in a bad coverage area, and IT needs to know about that, too,” he said.
Wireless LAN design and deployment has changed dramatically over the years, and they also can vary by industry. “On our side, we’ve turned our procedures and best practices upside down from what we used to do just a few years ago…We also base our products on upgradable hardware so business don’t have to roll out a whole new set of products when things change in their environment,” Miller said. “We recommend higher signal strength everywhere, 5 gig everywhere, and being able to support an adaptable infrastructure that can conform to new requirements.”
If your idea of obtaining good MPLS costs is to throw a spreadsheet of sites together and hope for the best, you might be disappointed. In this article I share some of my experience where projects have achieved some excellent results.
Part of creating a WAN proposal is building a specific capability aligned with your business. A capability and not a bottleneck. The truth is, most clients I speak with regarding change are in a poor situation because there was never any work completed to understand whether their existing WAN was in alignment with their business. A major component of this work revolves around understanding which areas of both your organisation and the service provider capability are matched. To complete this work requires an understanding of both sides of the coin. In the first instance, IT Managers need to consider particular aspects of their business from strategy through to application performance requirements. On the provider side, each and every key area which has the potential to impact your business should also be clearly understood. I’ve often been involved in a situation where the information provided by an organisation in order to price up their WAN is little more than addresses and bandwidths. In this scenario. the decision making process defaults to little more than a commodity based purchase. In the absence of value, all you are left with is price.
Dealing with special pricing teams
I have also been involved in a good amount of special bid’s. You know the kind of situation. One provider is more expensive than the other but features appear equal. Senior members of a business don’t really get the value and therefore instruct their IT management team to obtain MPLS costs at their best available rates. The problem occurs when the provider is faced with the spreadsheet I mentioned earlier. The special bid team working on your account is unable to determine whether their is serious buying intent because they don’t have a well aligned design in addition to the spreadsheet. The answer then is fairly simple. Providers (and special pricing teams) need to see buying intent, they need to know that their hard work will not be wasted on a fruitless exercise. So, whilst your intent may well be mostly ‘lowest possible pricing’ based, remember that the teams within the provider recognise which deals are more likely to result in a sale.
A base level of data to achieve great MPLS costs
If you consider a base level of data which should be the minimum required to achieve good pricing, I would suggest the following elements.
- Topology diagram presented in Visio format (including failover)
- Applications, listed by priority with QoS (Quality of Service) settings
- Your business strategy in terms of decision making process with time scales
Over and above these elements, a complete statement of requirements (SoR) will provide a major benefit to both your project and the goal of achieving MPLS costs from the providers with which you are in discussions. An SoR is a thorough document which is designed to look at every aspect of your particular business including the motivation for your project, the existing service provider and their pain points and issues together with a revised design based on these specifics. When preparing SoR content, a templates approach is required to ensure certain elements are not missed when creating the documentation. In the day job, we consider every aspect including:
User experience to the user behaviour which is increasingly mobile on a global basis. The users within your network require ubiquitous access to resources no matter where they are located.
Quality of Service – The level of bandwidth a priority required for each application on the network. Careful consideration must be given to where the traffic is sourced and destined.
Failover – Consideration of failover design and type. For example, the failover product should be designed whether the uptime is based on fibre primary and fibre failover or most cost effective copper including EFM and broadband.
US readers will no doubt tune out but wait. Although BT IP Clear is a UK based service, the technology refers (as a rule, there are exceptions) to unmanaged connectivity from BT. The US market is largely unmanaged vs the UK’s preference for managed services when procuring WAN connectivity. So, take a read through and compare a flagship UK product vs your US service provider capability. BT are no longer using BT IP Clear as a product name but the majority of IT Managers still refer to their wires only product using this brand reference. BT IP Connect is now the flagship product which also includes a wires only version together with fully managed routers where required, both Global and UK. Within the rest of this article, we’ll talk generically about the BT IP Clear capability.
- Reach and Diversity for failover – BT’s national coverage of Provider Edge (PE) devices to terminate your circuits
- SLA – The national latency, jitter, uptime and install figures
- Circuit types – From Gigabit Ethernet through to ADSL
- Other services – cloud, SIP and remote access
We have been spending a substantial amount of time over the last 18 months improving and honing our WAN procurement content. In some respects, this work is slight selfish since we are, in tandem, documenting our own sales process. Our original WAN Mindmap was generic and contained the pitfalls, risks and opportunities associated with MPLS & VPLS procurement. It is still, by far, our most requested content. Good news – when we embarked on the BT IP Clear version, we really wanted to create something which would specifically detail the procurement process as it relates to a particular product. The IP Clear service is generally positioned as wires only product and therefore attention should be paid to the attributes of a self managed service.
BT’s MPLS network is known to be well engineered and essentially covers the UK and, in the case of Global Services, the rest of the world. Gartner recently announced BT would remain within their magic quadrant because of their capability to serve global Enterprise clients. You may be forgiven for wondering how BT Global MPLS has anything to do with the BT IP Clear UK product? The same resources and investment is put into the network as a whole. As the global network evolves, so does the UK capability which increased bandwidth and presence with POP’s (Points of Presence) becoming more wide spread adding diversity and performance increases. If you ever read BT product description, the capability also mentions global reach. This said, IP Clear has always been associated with UK coverage. However, it is possible to procure a UK VPN from BT and connect international sites at a later date should your organisation grow by acquisition.
The following map details existing coverage in the UK.
It’s pretty easy to notice that the UK is well covered. Ultimately, this means your sites have less distance to travel to the nearest point of network entry. This not only reduces costs but also has the added benefit of diversity choices and the best possible latency.
The more PE nodes a provider has, the easier it is to create a diverse network. Within the generic procurement Mindmap, we always advise asking any potential provider for their true PE coverage as this will demonstrate your ability to create diversity and also demonstrate the providers true MPLS capability which is often covered up by marketing.
Let’s look at an example.
The BT Secure Plus product is designed to avoid any single point of failure. With full diversity, two routers will be configured running HSRP (Hot Standby Routing Protocol) or load balanced depending on your requirements. (Being self managed).
From the routers, BT will look to use two different points of exit from the building. Whether or not this is possible depends a) whether two points of entry exist and b) whether or not there are any restrictions on the building from the perspective of creating another entry point. Once the circuits leave the building, diverse paths will be attempted to ensure seperacy is maintained with dual BT local Exchanges used where possible. From the exchange, the circuits will ultimately arrive at dual BT Provider Edge POP’s.
As an MPLS network can carry both your voice and data traffic, you are effectively putting all of your applications under one circuit without diversity. Although you can achieve economies of scale by using MPLS a reliable service becomes essential or any savings you make by using the technology can quickly be eroded via productivity losses in the event of failure. By having so many POPs in so many key business locations BT can provide that piece of mind that we can reach a resilient POP sooner than any other provider in the UK.
There are a number of different ways to access the network, including connectivity from 1Gbit/s all the way through to standard broadband. One of the clients we are working with now are using the IP Clear ADSL product across 106 sites, only two of them are fibre based leased line products. There is a mix of availability with regards to DSL from standard ADSL2 through to FTTC (Fibre to the Cabinet). In terms of site issues, there are only 3 of the sites which are suffering from poor performance due to the locations being remote. BT are able to check site addresses to understand the kind of performance you will experience in the real world. The actual performance has been pretty good in terms of latency, here’s a live ping from the network which includes the LAN from HQ to a site connected via DSL:
Success rate is 100 percent (5/5), round-trip min/avg/max = 20/20/24 ms
CE_Router#ping 10.10.165.254.254 .254 0.254
Type escape sequence to abort.
The performance of the above ping is more than good enough for VoIP (SIP) based services and mission critical applications. The upstream bandwidth may potentially become an issue over the longer term but, for now, all is looking good.
- Lower cost fibre access direct to your site
- EFM access, aggregating copper pairs (telephone lines) to offer a single Ethernet service with built in resilience and a lower cost compared to fibre
- ADSL2+ integration as an access technology onto our WAN services
- Superfast access through Fibre To The Cabinet (FTTC) and Fibre To The Premises (FTTP)
- EMF and GEA access providers
BT IP Clear SLA (Full granular figures are included within the Mindmap)
The SLA is a commercial agreement, we always suggest organisations never design based on SLA figures and NEVER commit to the business that circuits will always perform to SLA parameters.
This said, the SLA will provide you with a good overview of predicted performance. If we know that traffic across the UK POP to POP will perform on average Xms depicted within the SLA, we are at least able to consider worst case performance. In general, latency performs better than projected SLA figures since they are always set as a monthly average.
The uptime guarantee is perhaps the most useless of all, in my opinion of course. (Not BT’s by the way, just SLA’s in general). For years we have seen figures of 99.9% as the standard for fibre based leased line connectivity. The fact remains that the SLA is of little comfort if your site is down and falls outside of these amazing averages. In this sense, it is important to design uptime based on the specific requirements of that site. The IP Clear product allows you to ensure services are built to maximise both productivity and performance regardless of the SLA figure.
Clearly the WAN is an enabler to additional services such as the cloud and SIP. BT provide a number of different cloud based options for managed services which include hosting and colocation. These services may not be as applicable for clients looking to buy IP Clear self managed IT infrastructure but it possible to create a hybrid of services. Access to SIP is a possibility by two methods. The first involves separate access using a BTNet leased line.
The other alternative is directly via the MPLS platform. However, the BTNet variant is a much easier product to implement since the product allows interface into existing ISDN-2 or ISDN-30 circuits – a Samsung device converts ISDN to IP. However, if true end to end SIP is required, access will need to be via the MPLS platform.
BT IP Clear Pricing
We are finding that project we are working on are producing some excellent commercials. As an IT Manager, you need to be aware that any project will likely yield better savings and costs when the requirements are fully outlined. The special pricing teams within BT are busy and therefore they take the projects with a good statement of requirements more seriously than those which consist of a spreadsheet and bandwidths.
Our senior designer has Distilled everything we know about BT IP Clear procurement into one of our single step by step A2 Mindmap. We borrowed some of our Techtarget MPLS VPN procurement workflows and essentially layered on the specifics of IP Clear service from the perspective of reach, latency, QoS (Quality of Service), fix times, uptime, change requests and additional BT products which interface into the capability including SIP and Cloud. Request the hybrid procurement Mindmap with added IP Clear capability.
It’s not often we’d open an article quoting Einstein. “The significant problems we face cannot be solved by the same level of thinking that created them.”
As a companion, readers may wish to request the Techtarget version of our IT Managers step by step VPN procurement Mindmap.
In other words, if you are considering changing your Global MPLS provider, something must change within your procurement process to avoid the same problems and issues occurring again.
The overall intent of any WAN procurement project is as follows:
- Avoid the typical pitfalls, issues and problems faced by the majority of Enterprise and Medium sized organisations when procuring international MPLS providers
- Align the specifics of your business strategy, applications, business continuity and process to the service provider market place
- Understand the impact of engaging with a provider which doesn’t operate a repeatable process to identify your business needs – the issues are often felt for years
- The Mindmap is designed to help you follow along as you move through the procurement process
Read on to understand some of our thoughts and ideas surrounding specific Global MPLS providers challenges.
The first steps, align your business
We all like to think we know and understand aspects of our business. In many ways, it’s not the knowledge we have but taking that knowledge and ensuring suppliers understand your value and your competitive edge – what makes your business unique. In the respect of Global MPLS network procurement, this means ensuring that any prospective provider clearly relates the specifics of your business to their capability to deliver a Global MPLS network providers service. When IT and business are mis-aligned, the business is seriously impacted. We’ve witnessed clients facing simply frustrating issues such as incorrect billing but also those clients which have suffered huge downtime and productivity issues. If you follow a repeatable process within the international service provides procurement process, you are in a better position to tick off the boxes as you complete the project ensuring good practice and due diligence is adhered to throughout your project.
The workflow for network procurement sounds vast. If you consider everything from application performance through to high availability, adds, moves and changes, delivery and migration, you gain an understanding why some companies just keep plodding on with their existing supplier. However, we know it doesn’t make sense to do more of what simply isn’t working.
Of course, being able to find a perfect provider is most certainly a futile task as there will always be aspects which don’t fit. However, if you know and clearly understand where these weaknesses exist, you are able to either work around them or adapt your business. As an example, you might find a provider which takes time to make bandwidth upgrades. This fact may either be a show stopper of something which you are able to work with depending on the detail.
In short, the areas we consider are as follows:
- Business Strategy
- Business Continuity and DR (Disaster Recovery)
- Documentation and process
- Due Diligence throughout contract
- SLA (Service Level Agreement)
- How to achieve Global and UK proposal and pricing excellence
Becoming a strategic thinker
Strategy is the direct link between your business specifics and your provider. The subject of strategy often conjures up thoughts of huge amounts of work but in reality, and as far as Global MPLS network providers procurement is concerned, strategy is about defining the key areas which make your business successful. We see this time and time again, the businesses which are successful within their particular niche really understand their go-to-market strategy, the areas which result in customer retention.
When we think about strategy, we consider your business and the impact of particular MPLS network areas. As an example, your key sites where you deliver services or data to customers must offer up a capability which contains no single point of failure. Or, perhaps there is a particular application which must perform well – the performance is key to customer satisfaction. Although these aspects will no doubt be covered in the technical design, outlining them and defining these key areas as part of your strategy will have a profound effect on the overall outcome.
Application performance and enhancements
Understanding applications is the basis of productivity for both internal users and customers engaging with your business in various forms. The way in which applications rely on MPLS varies but the key aspects cover latency, jitter, uptime and packet loss. Service providers are able to offer feature rich solutions which include QoS (Quality of Service) to provide confidence in the performance attributes. However, an SLA is only a commercial agreement – the network should never be engineered based on an SLA but there is a good indication of overall performance. The mindmap will also point you to areas which you may not have considered such as the impact of ‘chatty’ applications.
Keeping those applications running with maximum uptime
Clearly, having well performing applications is great from a business perspective. A major part of your applications performance is uptime. We recently wrote an content on the BT RA02 (Resilient Access) product where we described some of the aspects of achieving a solution with no single point of failure. We are pleased with all areas of the mindmap but particularly within the resilience and diversity section. Here, you’re able to easily see the pitfalls and the questions you need to ask of network suppliers ensuring there are no single points of failure within your capability.
Topology, any to any
The native topology of MPLS facilitates any to any connectivity. However, topology is also concerned with restricting access to certain areas of the business. As an example, clients create multiple VPN’s within a single VPN for voice and video to keep them seperate. More than applications, MPLS solutions allow you to create separation for extranet clients – you may have a supplier which requires access to areas of your network such as procurement of goods or services. The topology maybe created to facilitate this capability.
Within topology, you need to consider reach. If your organisation is looking at expanding into particular areas on a global basis, the future reach of your provider becomes a critical aspect. Even if we consider UK clients, opening a data centre in a location which is not well served by a particular provider of choice will impact you in terms of cost and potentially uptime.
Projects which need to be factored
With many organisations, there will always be a future project in the wings. We see this with various departments considering new initiatives or the business as a whole might on an acquisition trail. You may believe this area to be part of strategy but our belief is that these aspects require a section of their own. The situation you need to avoid is one where you put in place a solution which isn’t fit for purpose because the business launches a new initiative or procures another business.
Keeping up to date with documentation and due diligence
One of the major disappointments clients experience relates to poor network documentation and due diligence throughout their contract. We worked with a client recently where their network has not been configured correctly from day 1 with a serious knock on effect to their business. Applications performed but very badly and nobody from the service provider had a good understanding of configuration.
In order to avoid this situation, global MPLS providers need to define how they maintain documentation and also where the documentation is stored to avoid versioning problems. The mindmap will provide details on the areas we recommend you consider.
Throughout contract, due diligence with documentation is important. Just as a repeatable process is required for WAN supplier selection, a workflow is also required to maintain good practice covering such areas as trend reporting and SLA breaches.
Global MPLS Providers & Service Levels, Delivery and Migration
The Global MPLS network mindmap provides a focus on the key areas of service levels including the usual suspects from latency, jitter throughput to uptime and packet loss. Within each of the service areas, we point you to pitfalls and where the service provider marketing may miss out some of the key points. The SLA is a good indication of the providers performance, not only from the perspective of ongoing service but also delivery aspects of the service including adds, moves and changes.
Perhaps one of the biggest areas of weakness surrounds slow and painful adds, moves and changes. Some providers are more agile than others in respect of changes but we find that the process is often improved if the client has a clear understanding of the workflow from raising a change through to placing an order for the change and delivery. Some aspects of changes will be fast, others will take time. Again, which of these aspects that will impact your business will be understood when the specifics of your organisation are aligned with the product.
On the delivery side, the SLA will apply to lead times. There are certainly aspects to consider here which are going to become critical to your project including the actual process to take you from a design through to ordering, acceptance, and circuit delivery milestones. On top of this, you will also want to be thinking about migration and how you will take your service from one provider to another.
Budget, achieving the best international MPLS providers commercials
Obtaining a good deal requires knowledge of process. In addition to our knowledge of MPLS network pricing workflows, the mindmap does a good job of bringing other areas to your attention which make a commercial difference. An example of which is creating your statement of requirements. Any service provider prefers to work on a well qualified set of requirements and presenting your needs in this way has a dramatic effect on how they approach the commercials of your solution. If, for example, you present a list of sites on a spreadsheet, the provider will not take your requirements seriously and will forward out standard pricing.
If you have any further questions, let us know. The organisations on our PDF are also able to offer VPLS providers services.
In part one of two articles, I provide some thoughts and ideas surrounding the critical areas of UK MPLS providers & general procurement. Part 2 will include more detail on procurement but with a focus on Global. If readers are interested in a selection of recommended providers, please request the PDF by clicking the link.
WAN Procurement – evolution
Within my work as a consultant, I produced bespoke RFP content with a focus on: Strategy, applications, topology, bandwidth, QoS, Migration, Documentation, Dual Diligence, Security, Remote Users, Account Team, Support, Contracts, Cloud Strategy, Internet, Ordering Process, Migration, Product Capability, Statistics, Process and more.
Introduction, some of the key challenges within the WAN service provider market
Organisations are looking to understand which UK MPLS providers offer capability vs their specific business requirements. The market place, in the main, is still talking features and benefits which results in the majority of providers sounding the same through the sales process. One of the methods to achieving a successful WAN procurement outcome is to follow a repeatable process which provides a focus on each key vector of the procurement process. (This is the high level intent of the Mindmap) A large percentage of IT Management analyse the UK MPLS providers market place with the expectation of being in a position to decide from several providers with ease. In the majority of cases, organisations are looking at between 3 to 10 different contenders for their WAN business. The reality is that, more often than not, each WAN service provider sounds the same from the perspective of marketing. The sales process is often overloaded with features and benefits which are presented to prospects alongside the convince and persuade sales methodology. The conclusion often ends up in a decision making process based on commodity buying. In the absence of tangible business value, all we are left with is price. Whilst commercials are clearly important, the WAN must actually meet the needs of the business as the first priority. To put this statement into context, business to business sellers from service providers are unable to provide clarity with regards to complete capability. And as such, they will have no alternative but to sell on price. A wrong decision impacts contracts, delivery, support, change requests, uptime, application performance and more.
Not all providers are equal, understanding their reach
When considering which UK providers, uncovering their true network reach is often difficult. This is in the main caused by marketing statements which profess reach in the realms of 98 throughout the nation. These kind of statements are misleading and therefore clarity surrounding the reach of your prospective UK MPLS providers is critical. Whilst a provider stating a coverage ability of 98% may be true, the reach would be made up of wholesale tail circuit agreements from multiple providers such as BT Open Reach, Virgin Media Business, COLT (just a few examples). The reality is, a provider could operate one central core POP and aggregate tail circuit traffic back into this POP.
Ask to see PE (Provider Edge) coverage
In order to achieve transparency, an overview of the providers Provider Edge (PE) nodes must be analysed. The PE refers to the entry point into the providers core network and represents their true MPLS coverage. The diagram below shows how MPLS is architected vs the typical site deployment.
The diagram above details how your site connects to the local telco exchange, through to the providers first point of entry (typically a transmission POP) where traffic is backhauled to the nearest Provider Edge node. The breadth and capability of your prospective UK MPLS providers is generally defined by understanding Provider Edge devices deployed around their network.
Migrating to a new UK MPLS provider
One of the reasons why MPLS procurement projects fail is down to decision not to change provider. The value of prospective UK MPLS providers is not made clear during the sales process and therefore the confidence is not high enough and the decision not to change is made. This is common with complex procurement projects. With the above statement in mind, the value from any provider must be made clear and analysis of their migration resources should be understood. There are multiple technical methods for migrating from one supplier to another but the critical elements surround a good set of data on the existing network (think IP addressing, Quality of Services, applications and so on) to ensure migration engineers are clear regarding delivery requirements. This kind of detail should be understood from a sales process perspective since your organisation is at the stage of consider the UK MPLS providers market place. The experience of your project manager should not be overlooked. The PM resource is a major component of network delivery since they are clearly responsible for co-ordination of resources. As we discuss within our content, there are multiple moving parts with any complex IT solution and knowing the risks and pitfalls will provide benefits. In some instances, escalations will need to be used to progress issues. The PM will need to convey how the escalation process will be managed throughout delivery.
High availability and diversity
The logical progression from reach is to discuss defining prospective UK MPLS providers ability to provide high availability and failover at selected sites. The reach and coverage of MPLS Provider Edge nodes dictates the capability of the provider to build a highly resilient network. A high availability site will require connectivity to both a primary and a failover MPLS mode with geographic seperation. Aside from MPLS PE coverage, it is also important to consider the ability of tail circuit providers to offer diverse connectivity. The tail elements are detailed below.
The general industry thinking is that a single tail provider is the best route to achieving tail circuit diversity. This is at odds with the wider based IT Management perspective which suggests using multiple tail providers provides further resiliency. Let’s look at the scenario’s.
Single site, dual tail circuits
When considering one geographical location, using a single tail provider to deliver diversity is the better option. This is largely because, in a dual provider scenario, neither provider possesses knowledge of their espective tail circuit paths which results in commonality and single points of failure. The major telco’s have a specific product which is deigned to complete a site survey with a view to designing with no commonality / single point of failure. The BT RA02 product (BT Resilient Access 02) is an example of a true diverse product where primary and failover are engineered correctly (subject to survey).
Dual sites, dual tail circuits (geographic separation)
A UK MPLS providers design where sites are separated by distance allows organisations to consider using tail circuits from multiple providers. Whether there is any real benefit in designing a network in this way is a subject for further discussion since managing dual providers will require extra resource. The nature of geographic distance between each location provides confidence in the natural serration of distance. In order for both sites to communicate, a point to point circuit would be required between each site in the form of dedicated fibre (metro areas) or an Ethernet VLL (Virtual Leased Line) for greater distances.
Adds, moves and changes
In January 2012 a large global enterprise changed provider because of their frustration surrounding the adds, moves and change process of their incumbent. To the un-inititated, this may seem an extreme decision but the bureaucratic change process with their large global provider of WAN services was slow, inaccurate and business impacting. Imagine the simplest of changes taking weeks and in some cases months. The global enterprise discovered that there were alternatives – providers which provided portals and change processes which could be completed in a matter of seconds. On this basis alone, the decision was made to change. Understanding the change process of UK MPLS providers requires analsys of process. The end to end process from beginning to end should be carefully considered to ensure adds, moves and changes does not become a bottle neck to your business.
What to expect from support
When considering support, it is often the basics which take the majority of focus. In this day and age, support is almost always offered on a 24/7 basis with a good fix time for replacement hardware. As organisations look deeper into the detail, the way in which your network is supported, the skills sets and the real replacement hardware fix times is brought to the surface. For example, hardware replacement times may only begin from the point a hardware fault is diagnosed. At a high level, this is reasonable. However, there are providers which do not commit to a fault diagnosis time. The process of logging faults is a much more efficient task if the engineering team you are engaging with (via email, web or phone) is in a position to make a change and troubleshoot the hardware. More often than not, tickets are processed via a handling team which are not able to progress your issue – the knock on effect is further delay. With the previous statement in mind, the importance of engaging with service providers which offer a direct interface into engineering is clearly beneficial.
The WAN architecture vs UK MPLS Providers capability
Finally, for this wiki entry, the WAN architecture will be limited by any prospective providers overall capability including cloud services. We would not say that one element is more important than another – each organisation is different. The cloud is a hot topic with the term banded around to cover a huge array of capability. When embarking on an MPLS procurement project, the documentation of your network, the application flows, the high availability requirements and future will feed into an architecture to support the organisation – private cloud, public cloud or otherwise. The service provider market place will have a want to throw their capability in your direction to see what elements may be of interest. However, this approach is often too much and will create an environment where the capability is not clear. Therefore it is better to architect based on your specific business and request providers to meet these needs via their capability.
IT Managers are responsible for many different areas of an organisations IT infrastructure. The fact remains that it is clearly difficult to become an expert within every single product, especially as products are becoming more vast and complex. Whilst the content we produce at telecoms.wiki will not remove every issue or problem encountered within the UK MPLS providers procurement space, we hope typical issues and problems will be vastly reduced. With a repeatable diagnostic approach to procurement, organisations are at least confident that the key vectors are being covered in an ordered approach. The engagement with the wider service provider market (as previously mentioned) becomes much simpler since providers are working to your requirements rather than what ‘they believe’ to be a good fit. We see a pattern across the selection of UK MPLS providers – once companies make a commitment to follow a process through, they will enjoy a better outcome. Typically, these organisations keep on getting better, more efficient and profitable with the WAN as an enabler at the core of everything they do from a business perspective. The top performing IT Managers define how they do business and put together the processes required to meet current and future operations. If you are interested in learning more about MPLS service providers in UK markets, let us know.
By Chuck Moozakis
Private equity investment firm M/C Partners has a long pedigree in telecommunications investing. The Boston-based firm, formerly known as Media Communications Partners, has overseen more than $1.5 billion in placements over the past two decades as it focused on companies spawned from the landmark Telecommunications Deregulation Act of 1996.
So, when Managing Partner Gillis Cashman talks about the firm’s latest investment–$50 million equity funding in data center services company Involta—his thoughts bear at least a cursory listen. Why, after previously investing in heavyweight companies that included Metro PCS and Level 3 Communications, does M/C now believe Involta, with just a handful of data centers in towns such as Duluth, Minn., and Marion, Iowa, is a good bet?
The simple answer? Application performance. Or more specifically, the lack thereof.
“There is a view in cloud computing that data centers are now becoming commodities and that proximity doesn’t matter; you can host your servers anywhere,” Cashman said. But concerns about application performance, and to a lesser extent security, are inhibiting cloud’s success, he said. “When you think about application performance, it really requires a different architecture, where you need to get those servers and applications very close to the end user.
“Instead of 50 servers being in a data center in the middle of nowhere, now what you need is 50 servers at 50 data centers close to the edge where the redundancy is in the network itself.”
And, Cashman said, those DCs should be located where the need is greatest: to serve enterprises in communities that are not served by Tier 1 or Tier 2 providers. These companies, he said, still have mission-critical applications, but they can’t get the service-level agreements they need to ensure their employees and customers are getting the application performance they deserve.
“There is far more insourcing going on in smaller markets,” Cashman said. “The reason is they either don’t trust the facilities in the market or there are no facilities in the market, so they are forced to deploy their applications internally.” To target these types of customers, Involta builds a dedicated fiber link from the DC to the enterprise, effectively creating a leased line. “Performance across this network is guaranteed because it never touches the public Internet, and to me, that is a critical factor that will drive more outsourcing [to data centers]. You need to have that infrastructure in place to effectively place these private cloud architectures.”
Ensuring that Acme Manufacturing in central Iowa has the same broadband capability and application performance as XYZ MegaCorp. in New York City is smart business–and as M/C Partners almost surely agrees, it’s good business, too.