Chatbox unmonitored

And each of those connections only take a portion of the traffic. So there's another network owned by Time Warner Cable, and finally Google's network. So there's a little bit of merger and acquisition between the two Time Warner Network. You can actually see that surface in what we're seeing in their networks. So when we place a probe at the Austin office, we're seeing the content servers that Google is using to provide content to this Austin office. Different routes and, even more common, different QS behaviors. And the probe be is going to be where we send it from. So then, the path is going to be the probe plus the service. But the network is behaving as it's been programmed. This starts to allow you to pull that apart and understand each individual component, and which component is causing that bad behavior. And you wouldn't have gotten— in the past, you would not have gotten alerts to let you know that users for that application would potentially be having a problem some percentage of the time. But in this case, this is bad latency specifically for that link, as opposed to something in the overall path.

Chatbox unmonitored-16

Because there's a part of it that seems, "Wow, this is some kind of amazing spoofing that's going on," or we're looking inside of firewalls. Okay, so I imagine this is some sort of custom-crafted packet, where we are messing with the information in the packet, the port, and the TTL information. Oftentimes Traceroute gives you information that's a little bit unintuitive, like hop number three has high packet loss, while hop number four has no packet loss. So there's a layer of— there's two things different that we're doing in Net Path. So, we see, we've got our Windows 2012 server that's running Orion. We've got GNS3 VM running through Virtual Box as the hypervisor.

The first of which is, we are crafting our own packets, TCP packets, that look like the application traffic. We're using GNS3, which is an amazing network emulation tool. That's what they prefer, so that's how they packaged it.

Meanwhile, we always get the path that matches the user experience. And this case, we're actually telling you how it's getting there. All these places, that's where I want to place probes--not my main poller. So to configure a path, you're going to use the Net Path services dialogue. Here's the ones we've already defined, and this is on a different server now that we're going to get into in just a little bit. And if you think about this, we're going to start with create new service. In this case, we saw something that was caused by a config change that we made in our network, which is great, because then we as the administrator can log in and fix that. So it looks like of these four links, most of our traffic is going over that top link. to p.m., we were seeing bad behavior where 60% of our traffic was going through that link, and we were experience 100 milliseconds of delay, or 20% packet loss, or whatever it may be. First of all, and when we've done this--and certainly a lot of the customers who've already upgraded are beginning to experience this. ISPs would say, first, "That is extremely helpful." "Hold on one second." And they could get to a troubleshooting step much, much more quickly for their internal network than they otherwise would.

Okay, so we've talked about paths and probes just a little bit, so let's take a second and just untangle that. And, you also don't need instances of server for that. Now, this is performing fine now, but let's pretend it's not performing fine. Because otherwise you're going to say, "I have this percentage thing," with some anecdotal information about when it happened. And we have had, occasionally, people— actually, we had a customer I was talking to not too long ago, that they were named contact in one of the databases, one of the publicly available databases that we're pulling this information from. There's really two pieces that we're putting together here. Because we want people to help us make sure that our network's performing well. And the other piece of it is this technology to figure out what the path is, who's involved, and what specific performance you're seeing between hops. But one of the questions we get really commonly is, "How do you get this information? " And particularly, "Is this just visual Traceroute?

So we started in the lab, building this tool, to see what we could do to start providing visibility and some problem isolation, and help people solve these problems. It's like our abstraction saying, "We don't know what's in here." "We don't care." "It doesn't matter to us." But it does matter now. So we all know and love our network atlas where we can spend hours making our maps look exactly how we want. And we can see across the bottom, we've got our chart here that shows our end-to-end performance. Net Path has identified that the problem is right here.

Right, and especially now that so many of those resources that move out into the cloud, you're— they become more and more opaque from a monitoring perspective, and certainly in terms of an administrative control. So being able to figure out what's going on is an even greater challenge, certainly than being able to use— well, certainly nobody's going to give you root, but give you pretty much unlimited access, administrative access, to everything in your environment. So we need to be able to pop open the cloud and see what's going on. One of the things I like when you get into the interface here, right off the bat is, if you're not sure how to use Net Path, go up here and click on How to Use Net Path. You can actually step by step through each of the components and come away with a pretty good sense of how this works. I think the view that most people start off with, and when you install it, by default, we'll actually set up a monitor, right? We'll install what we call probe, the source of the path, in your main poller, and then we'll go start polling Google, just to give you some idea of what a path looks like. So this is kind of, if you're exploring something out on the internet, this is typical of what you would see. Here, our Austin office, which is our probe here in Austin, goes to Google. But here, you give us the destination, you assign a probe, you're done. And before that, we saw how to explore the internet beyond your firewall. So, at the left hand side, we see my computer going to Salesforce. But the unique thing about the chart being that you can actually select the interval where you're seeing a problem. Conveniently coded red so you know there was a problem. And we can actually expand issues here and see that the latency value is over critical threshold. It's also, after Net Path discovers where your transit impact is, which is really important. Well, if you're messing around with traffic shaping, that is going to affect it. And if we we're good troubleshooters here, we think Ethernet 1.0 has a traffic shaper applied.

Small issue arose surrounding stock availability but after 1 phone call to customer services, correct item dispatched same day and original delivery date adhered to. In addition to the outstanding customer service, it was the cheapest among all competitors.

Net Path™ is a revolutionary and powerful new approach to visually discover and monitor networks.

And we can get some more details if we hover over that, about how much packet loss there is, how much transit likelihood. One of the things that we've discovered, and is definitely new for internet paths is that most of these paths are multi-paths. We can see there's a very small amount of traffic being sent through this interface, so likely we're shaping, at a low percentage, of that interface's available bandwidth. Or when it's coming back and they potentially get routed to a different path because they got a new speed conversation, then they may get a link that's working, they may get a link that's not working.

And in fact, thanks to academia, we know that over 80% of internet paths are multi-paths. Our ISP has two connections from this AG 33 router over to their next layer. The important thing here is, when you place the probe at the source, it's going to get service like other users at that location. And that's really important, because you could very easily have completely different routes for completely different services based on the applications being delivered. So to create a new one here, like if we wanted to say, oh, I don't know, demo.on Port 80. Right, so we can start seeing this is the largest conversation. And if we were to click into this, we can actually take a look at the NTA data, the deeper flow analysis for all of that traffic. The interesting thing about this is that if we were looking at this from a regular monitoring perspective, there is nothing wrong with any of these devices. We have this misconfiguration of the traffic shaper behind the scenes that's causing a problem, and it's causing an application problem because the transit likelihood of this link is driving a bunch of stuff over a slow-responding link, where we've added a bunch of latency. And so one of the things that's really interesting about Net Path, is when you have these really difficult to diagnose intermittent problems, or problems that affect some people but not other people, particularly when they happen in the path. And we had talked about that before once, about sort of bad latency, the difference between good latency and bad latency, assuming that it is possible to have good latency.

If you click on that network, it will break it out into the hops that comprise that network, and then we're starting to see this hop-by-hop performance, right? And then interval I'm going to probe it, and it's not polling, because this is different. Because polling suggests you have some administrative access. So here we can see a couple places where there's red. Right off the bat, I'm red at my end, because something in this overall path is being affected, right? But just off the bat, right off the bat, I can see that there's another red link here that looks like it's inside my firewall, so just in this first view, do I suspect there's a problem inside? Like, one of the things that it's also giving here is the contact information for that particular node. That comes from one of the internet databases, and you can get even more information if you drill down and start inspecting the DNS, if you're careful in how you parse through it. So we've got configuration chains that happen between and p.m. We'll just click, and it'll tell us what changed in your configuration. So here we can see our NTA information coming across.

Tags: , ,