Network performance issues come in all shapes and sizes, and can require vast amounts of time and resources to solve. As a matter of fact, in my last column, I explored recent survey data that shows 42 percent of IT teams feel they spend too much time troubleshooting the network. In addition, 38 percent feel they can't proactively identify performance issues and 35 percent have poor visibility across the entire network. Regardless of these challenges, network operations (NetOps) teams still need to push forward and do everything in their power to correct problems before they impact end user experiences and the proverbial bottom line.
Here are three examples of painful network performance issues you're likely to encounter this year, and how Network Performance Monitoring and Diagnostic (NPMD) solutions can help you overcome them:
1. Horrible VoIP / Unified Communications Interruptions
Picture this: A multinational pharmaceutical company with widely-distributed development, operations, and manufacturing recently installed an extensive (and expensive) telepresence solution. It enables global collaboration and helps the company bring products to market more quickly by leveraging the most talented employees, regardless of their location. But unfortunately, the quality is poor, resulting in team members constantly saying, "Why is the meeting quality we just experienced so bad? Didn't we just spend millions on this system? It's so frustrating."
In most cases, poor performance can be traced to Quality of Service (QoS) mis-configurations. And this becomes ever more likely in a highly-distributed network where traffic flows through multiple network devices, all which must be properly configured. With today's modern NPMD solutions you can reduce configuration errors with easy-to-apply, rules-based QoS policies and templates. The ability to save, backup, and deploy automatically-scheduled configuration changes means policies are consistent and accurate across the entire network. As policies are implemented, real-time performance reports can quickly identify errors for immediate remediation. Many traditional NPMD solutions lack the end-to-end visibility of the new next-gen platforms, which allow NetOps to resolve QoS issues impacting UC performance across complex networks … and eliminate employee complaints about QoS for good.
2. The Dreaded "Poor Performance" Report
Imagine that a handful of Tier 1 support engineers at a global network equipment manufacturer with distributed "follow-the-sun" technical support centers are reporting problems when using the online support software. The engineers only experience this problem occasionally, oftentimes making it all the way through the call, but sometimes experiencing long delays (10-20 seconds) per entry into the system. This is creating poor customer experiences and generating a needless increase in support escalations. The problem is not specific to a location, and a number of users have experienced the occasional slow-down.
Intermittent problems like this can be some of the most challenging and time-consuming for IT to track down. But not if your teams are using NPMD solutions. With enterprise-wide topology maps and the ability to set alerts for (in this case) application and network latency on the application in question, network engineers can quickly see who is experiencing the problem, when they are experiencing it, and the general conditions during which the problem arises. By comparing application and network latency measurements, NetOps can see the network is responding quickly, but at times, the application is not.
Assuming the network has been configured with some sort of packet capture appliance in at least one location where problems are being experienced, the network engineer can then drill into the network packets themselves, all the way into the payload, to see the specific application calls are made when the delays happen, and any errors reported as a result. With this level of detailed information in hand, NetOps is armed with the evidence they need to approach the application team and quickly address the problem.
3. Wait - What Just Happened? We Need Instant Replay!
In just about every case, you hear about a network issue after it's happened. That usually leaves you with two less-than-ideal choices. The first is to wait for it to happen again. Depending on the severity of the problem, that may not even be an option and even if it is, it just about always comes with some level of business impact. The second is to work to actively reproduce the problem. This is often very time consuming, and sometimes requires the time and cooperation of the person reporting the problem, hampering productivity for everyone involved.
With NPMD solutions, you can actively store raw Flow data that allows you to go back in time to replay a flow and watch the transport service across the network for forensic analysis. There's no need to wait for the issue to happen again "in the wild," or to attempt to recreate it manually. You already have a recording of the flow or flows in question. (Tip: be sure to use solutions that don't average up the data. With some solutions, if you don't catch a problem soon enough, the data gets rolled up into minute reports, which skews the data and often make it unusable for forensic analysis.)
These are just a few examples of the many types of network performance problems NetOps teams experience every day. As you can see, if you're equipped with the right network management tools and in-depth insights, these issues can be identified, analyzed and resolved much more quickly.
Modern enterprises are generating data at an unprecedented rate but aren't taking advantage of all the data available to them in order to drive real-time, actionable insights. According to a recent study commissioned by Actian, more than half of enterprises today are unable to efficiently manage nor effectively use data to drive decision-making ...
According to a study by Forrester Research, an enhanced UX design can increase the conversion rate by 400%. If UX has become the ultimate arbiter in determining the success or failure of a product or service, let us first understand what UX is all about ...
The requirements of an APM tool are now much more complex than they've ever been. Not only do they need to trace a user transaction across numerous microservices on the same system, but they also need to happen pretty fast ...
Performance monitoring is an old problem. As technology has advanced, we've had to evolve how we monitor applications. Initially, performance monitoring largely involved sending ICMP messages to start troubleshooting a down or slow application. Applications have gotten much more complex, so this is no longer enough. Now we need to know not just whether an application is broken, but why it broke. So APM has had to evolve over the years for us to get there. But how did this evolution take place, and what happens next? Let's find out ...
There are some IT organizations that are using DevOps methodology but are wary of getting bogged down in ITSM procedures. But without at least some ITSM controls in place, organizations lose their focus on systematic customer engagement, making it harder for them to scale ...