Cisco Customer Success - Video

Diagnose & Resolve: Powerful Troubleshooting with Assurance and Cisco ThousandEyes

Playback confirmation!

Do you want to resume playing from last left location?

Chapter 1 Thumbnail
00:10
Welcome, agenda, and series overview
Chapter 2 Thumbnail
03:17
Catalyst Center Assurance architecture, telemetry, and onboarding
Chapter 3 Thumbnail
13:04
Overall Health dashboard demo and network services (AAA/DHCP/DNS)
Chapter 4 Thumbnail
20:03
Network Health dashboard demo: device and AP performance
Chapter 5 Thumbnail
25:51
Client Health dashboard demo: onboarding, RF, roaming
Chapter 6 Thumbnail
31:11
Issues and Events with AI analytics and guided remediation
Chapter 7 Thumbnail
39:00
Client 360 and User 360 workflows
Chapter 8 Thumbnail
49:31
Client Analytics (Apple/Samsung/Intel) and prerequisites
Chapter 9 Thumbnail
58:47
Intelligent Capture and OTA troubleshooting demos
Chapter 10 Thumbnail
01:16:50
Machine Reasoning (MRE) and ThousandEyes integration; wrap-up

Transcript

Welcome everyone, and thank you so much for joining today's expert Insights webinar on powerful troubleshooting with catalyst Center Assurance and.00:10Cisco thousand eyes.00:20I'm. And I'm joined by mail and we are both customer success specialists here at Cisco focused on catalyst center and thousandeyes technologies. I'd also like to welcome our expert panelists, Matthew Max and Paul, who will be answering your questions live.00:21And over the next 90 min, we are gonna deep dive into how these two platforms work together to help improve your troubleshooting experience. So all the way from the moment your device sends its 1st telemetry until the cloud applications that your users depend upon.00:40So the goal of our expert insight series is to share knowledge in a format where the information provided to you continues to build from the previous sessions and help drive up your adoption. So this is the 4th session of the elevate Expert Insight Foundational series. We kicked things off in the series with the.01:04Concept of prime infrastructure to catalyst center migration. We then completed the wireless automation, the device controllability session as well. And today's focus is gonna be on troubleshooting, how you go from something's wrong to here's exactly where and why or here's where the fixes are.01:24Right? And following this elevate series, we have an amplify series coming up next month where you'll have the opportunity to learn in depth about templates and other integrations in catalyst centre.01:44So while we are going through our presentation and demos today, you might have some questions that come up and you can post your questions in the Q and A panel of your Webex meeting that you can find by clicking on the three dots in the bottom right corner of your Webex window. Our panelists will look into your questions and respond, and in the event that.02:00Your question goes unanswered, your information will be recorded, so we will get back to you with an appropriate answer at a later time.02:20Now this is the agenda for today's session. We will start with the foundation, the telemetry settings, the difference between the two things assigned to site and provisioning. We will then examine the various dashboards that are populated with telemetry information that you can use to troubleshoot your issues.02:31Then is gonna take you through the troubleshooting workflows especially the client three 60, the user three 60, the client analytics, intelligent capture and the OTA tool, all of which are useful to you in troubleshooting your issues, right? Finally, I'll bring it home with extending that visibility beyond your net.02:50Network through the integration of catalyst center and thousandeyes.03:09So this is the architecture of Catalyst Center assurance from the bottom to top. Now at the bottom we have our network. It's composed of your switches, your routers, access points, your wlcs at your sitting at your office sites and data centers, right? And then there's also your ice.03:17Server, there's DHCP servers and also your CMX service, right? So all these devices especially your network devices, your routers, which is access points, wlcs, they emit metrics, right? They emit events and configuration over a whole family of protocols and APIs, right?03:37We have GRPC, SNMP, netflows, syslog, right? All of which are used to communicate to the catalyst center. This data flows into the network data platform, which is our engine that ingests these metrics and correlates it. Now, once we get this information, it is going to be processed.03:571st, there are two engines that will process this data, firstly the on prem engine, and then.04:17You're right, what you can see is the cloud based machine learning engine, right? We will go through all of the details of how to enable it and what it encompasses, but it is important for you to know that we have this AI and machine learning engine in the cloud which is able to supplement with some more information that is gonna help you troubleshoot your issues.04:23And on top, it's the assurance UI which you interact with in your day in, day out operations. And as I said behind it, we have the cloud based machine learning analytics that turn those raw telemetry data into insights and feedback.04:43So if you zoom out on this diagram, what you see is that there are two things that make this solution powerful. One is the breadth of data that is ingested and two the correlation that Atlas Center does, which turns thousands of data points into a single health story.04:59Here is the catalyst center assurance workflow. So getting to assurance is three moves, install discover, assure. The 1st step is always the same. You install your catalyst center, configure your telemetry and credential settings, and then run a discovery of devices using an IP range rate with your CDP.05:19And then you create the network hierarchy which is a crucial task for functionality. It allows all the discovered network devices into your inventory. It enables that the to connect into those devices using the right credentials that you provide and then assign them to the correct location.05:39It's the site hierarchy.05:59There are cases where you might have already built your site hierarchy and in those cases you can skip straight to discovery and add devices to your site. So assigning devices to their locations is what triggers the push off telemetry configuration. And following that, we have the device manageability feature.06:01Through which catalyst center automatically pushes the configuration that makes your devices send telemetry back. A bunch of commands that catalyst center pushes so you don't have to do them manually on all devices and it is universally applied to all the devices in your inventory so that they keep sending the telemetry necessary for catalyst center.06:20To identify issues.06:40So now that we've understood a high level workflow, let's look at how the telemetry actually gets configured, right? So you can adjust telemetry configuration in Cisco Catalyst Center to meet your network specific requirements. We have multiple options.06:43Available for you for data capture like syslog, SNMP, and netflow. The default values that are set are recommended by Cisco, but each of which you can tune your own requirements.07:03So what you see in the screenshot here, you can look at the DNA center dashboard and the telemetry configuration in your network settings tab. So this is one of the moments where we decide which data flows into the Cisco catalyst center network data platform that we looked at in the architecture slide.07:16So it's important that you configure your telemetry so that you have a reliable dashboard with all the accurate data in it. And as I mentioned earlier, we also have the device controllability setting and that is what governs Atlas Center to push the configuration to the devices.07:35So device controllability pushes the configuration required for your telemetry and assurance automatically instead of you going in and touching in every device by hand, logging into it and entering the configuration. So as I said, this is the system wide configuration. It helps automatically enable some feature.07:54It's in the network devices in which in turn allows you to pull information from them. So things such as your SNMP, netconf from there is trust sec, that it enables, right?08:14So if device controllability is not enabled, we will lose the ability to push certificates, you know, we lose functionality such as IP device tracking and some other features to the network devices, right? So these will limit our ability to monitor them properly, so it's always.08:28Advise that you enable the device controllability for a proper troubleshooting experience.08:48And another thing to remember is that there is NO way to enable or disable the device controllability for only a few or specific locations, right? Once you enable it, it works on all the devices that are in your entry. An important aspect of assurance is also how we need the wired traffic. So this also plays.08:54It's important role when you have a wired clients or when you have the device controllability enabled, it allows us to apply certain configurations in your network devices that gives us the ability to pull the wired endpoint telemetry.09:14Moving on to the procedure of onboarding devices in catalyst center, you have two ways of doing it. One is through assigning them to a certain site or the other is to provide provision the device, right? Assurance features, they do not require you to fully provision any device, but, one thing that is important is.09:33You need to make sure that your devices are all assigned to a site because by assigning them to a site that enables the assignment of telemetry configuration as well for that specific site and the assurance data can be filtered or segmented based on the sites or locations within your dashboard.09:53Now this is a common real pain point as an admin, right? How do you know whether catalyst center is actually receiving telemetry from a device, right? So previously we used to lack visibility into this, but, you know, since since a long time since we've had 237 and in all our future releases, you get a telemetry.10:18Status view in the assurance dashboard and using this you can drill into telemetry issues in the device three 60 view. So here in this snippet, you see that this checkbox is available in several dashboards and that helps you enable you to verify with telemetry collection.10:38Now checking this box, it serves as a reliable way of verifying or set up. So, e.g., in cases when you're troubleshooting instances where telemetry may not be visible in one or more dashboard, this provides a valuable starting point for addressing such issues.10:58So far we've looked at the architecture, we looked into the workflow, we've built the foundation, but now let's see what gives you on the dashboard, right? How assurance takes all that correlated telemetry and presents a holistic picture of your infrastructure health for your clients and network devices and applications.11:18So firstly, Atlas Center monitors the whole set of API, APIs across your clients, network devices, and applications. It computes a health score for each of them, right? So by abstracting the raw data into single health score and based on the most important metrics.11:40Assurance allows you as the, as in the network operator to focus on the problem areas and find the root cause quickly through intuitive workflows. So be it your wired or wireless clients or point applications, so on and so forth. Atlas Center will compute a health score for each of those components that is being.11:58Highlighted.12:18This health score is presented usually on a scale of one to ten. They are color coded so that you can focus straight on what needs attention and they roll up into the health dashboard with three 60 views behind them for additional detail. We'll look at this in the demo as well, but a score between eight to ten reflects that.12:19It is in good health. Four to seven indicates some type of warning condition whereas 123 is poor health and needs your attention, right? It's important to remember that the health score isn't your complete answer. It is not a, it may not be a glearing solution but it gives you a good idea as to where you can start.12:39Looking at 1st, right?12:59So this is our 1st dashboard, which is the overall health dashboard. This gives you a high level read on how both your network devices and your clients are doing, whether that is from a global standpoint, that is your overall network, or it can also be filtered on a per site basis. You can customize.13:04The view to look at a specific site that you're targeting or troubleshooting. And in addition to providing a summary of the health of your network and net client devices, it also provides a quick view summary of successful versus failed transactions. So if you look at this snippet, you see this network services over here such as.13:24Does your AAA DHCP DNS activity, all of which are bundled together and you can look at what their status is.13:44We'll look at them closely in the demo. We'll also get to see some several key wireless performance metrics such as your onboarding attempts, the connection speed, a holistic picture of all of those metrics, right? And it will display the sites where you have lowest performance in those metrics. And, lastly, the overall health.13:52The dashboard shows you the top ten issues in in the bottom that we'll get into the demo. You can immediately get into those issues, see, what is going on and resolve them. So all in all, this is the dashboard, which is a great starting point from which you can start drilling down into your network.14:12For health or client health depending on where the story leads.14:32So let's get into the demo of this dashboard. Now, as you can see, this is the homepage of catalyst center and in order to get into the health dashboard, what we would do is click on your menu icon and then go into assurance.14:37And then under dashboards, you'll click on help. Here is your overall dashboard as I said, by default it is set to the global view, meaning all the slides sites are included and it's the calculation. There is also the timeline which is set to 24 h.14:56But you can set it to seven days or 14 days based upon your need.15:17As you can see, you have all these slides listed over here by which you can filter and you can also set a custom time frame that you are will wanting to target in case, there is some issue that you wanna go back and check, you can filter based on that.15:24There is also the site map option. You know, if you wanna take a quick look at what the health is in all the sites around the globe, and there are your individual widgets for your network devices, wired clients, wireless clients, and the network services.15:40Right, as I said, you have the network services, the triple A server status, the DNS server status, DHCP servers, right? You get a holistic view of what is going on and then you can dig deeper if at all you want to troubleshoot something. But this is the view for your AAA server, and once we get in that you can see that.15:57That we have all these AAA related metrics, the summary, the transactions of how many were successful in the last 24 h.16:17The average latency that it took, to the AAA server and then the top sites were classified on the basis of the highest latency by transaction failures, and then you also have a chart for your server latency and transactions.16:26You also get this widget where you see all the AAA servers by the classified by the WLC and their location, which specific site do they belong to, what are their metrics such as the transactions, the number of failures, what was the average latency like, you can get a quick view of all those metrics.16:48It's from here.17:08And you can switch between all these views, as you can see when you click on the network services dropdown, you can switch between aaa DHCP and DNS. So let's go into DHCP, to look at the summary of information. So similar to what we had in triple AA, we also have all the separate video.17:14It's over here the transactions, the latency, and the failures transaction failures, if at all there were any.17:34So you can go into this time chart as well by clicking on the details under the widget, you would be able to look at all the server transactions and you would be able to filter them based on failures and successes. If you wanna target specific servers, you'd be able to do that, see what went wrong.17:48Here in this case, you can see that, you know, we have this specific server selected and we get the client table listed for it.18:09Then when you click on these top DHCP failures or the top sites, when you click on any of these options over here, you would be able to filter down into the, that specific data, which are the top ssids, which are the top DHCP failures, the top site that the highest traffic is.18:25As you can see, you also have the site analytics as you scroll down, as I said, you have the onboarding attempts, the onboarding duration, the average connection speed, the roaming attempts, and the roaming duration, right? And if you want to dig deeper, you always have the option of, you know, clicking on the hyperlink within that.18:54Widget here in this case, if you click on view site analytics, you'd be able to dig deeper into that and you know get in depth analytics.19:14And this is what I was talking about, the top ten issue types. This is particularly very helpful because you know it acts as your ATM dashboard, you log in, look into the specific page, narrow down on what are the top issues that Atlas Center was able to see over the last 24 h, and you can start.19:26You know, focusing them one by one. They're listed on the basis of priority so it helps you identify what to target 1st before you move on to the remaining ones in the list.19:46Alright, so that was the overall health dashboard and moving on, we'll move on to the next tab, which is the network health dashboard, right? And here is where you have a detailed view of all your network devices. Now similar to the over.20:03Health dashboard, you will be able to view this page on a per site or a global level. The network device health is computed from three pillars, what we call are the system, the data plane and the control plane.20:23And here's the important part, the device core is the minimum of its subscores for any device. So if you have one link weak link, that will set the score because your weakest component is, you know, your the true metric in calculating your real experience.20:37So there is the correlation that is doing the work behind the scenes, so you don't have to check ten counters. The score will automatically tell you for which device, you know, what is going on, what is the status of that device and which pillar do you need to target within that? You get a breakdown of the network device.20:53Based upon the device role, you also have the AP metrics you such as the total APs, their updown status, the access points with their highest client count, the highest interference band. So things like that from a wireless perspective, which a wireless admin.21:14Would be interested in. For the network devices, do you have information such as the overall health, the memory utilization, CPU utilization and all those things relating to the infrastructure. Let's dive into the demo. It will help us understand better.21:33So as you can see from the overall tab, we can now move on to the network tab. And as I said here as well, you get a timeline view similar to what we saw in the overall tab, you have an option to switch from the global setting to a site.21:50Specific setting, you can adjust the time time time frame of the data that you're looking at. You can switch from a timeline view to a tabular view as well. And here is the icon to check the telemetry status.22:10And you can select a specific point of time in this timeline that you have. You can scroll through, you know, this timeline and select if at all there was any spike or if at all, the performance went down.22:32And then you have the, the network devices, the split based upon what the device role is, whether it's a router or distribution access that is also classified, the status of those devices, how many of them are in good health, which one of them need your attention, right, and which one of them.22:50Is not sending any health data.23:10So you can quickly click on one of these, you know, scores that we have and get a deeper understanding of what which devices these are, right? So here in this case we have a couple of devices that are in a, that are showing red. So if you click on them, Atlas Center will be able to give you what the list of those devices.23:16And, you know, their models, the IP addresses and their overall health, right? And from here you can start digging up digging now deeper into why did you see that score?23:36With the device model, the device OS, and for the access points as well from the wireless perspective, you have, you know, a holistic view of the up down status, how many of them are up or down or which ones are not sending any data you get a classification based upon their client count.23:49And, and then based upon their interference rates.24:09So you can either look at the latest data or you can even switch to a trend setting. So if you want to look at the history, and then here you get a split of all the devices based upon their health and you can select each of those categories, you know, whether you want to target devices that are in poor health.24:16Or, certain, types of devices based on the role.24:36You can also adjust the table appearance if you want more information, so you can add some columns in here similar to, you know, the different views and catalyst center. You have the option of doing that. Then you have the van link utilization, the network devices reachability.24:46The one link availability. You can dig down deeper by clicking on any of these metrics that are being shown to you. So you can click on these links and then it will take you deeper into what that means.25:06So similar to the other dashboards, you have the option of switching between the different sites and you can quickly navigate between, you know.25:31The different sites that you are looking to troubleshoot from here.25:40Alright, now we have the client health dashboard with which provides you an analytical summary of how well your clients are able to connect to the network. And once they are connected, it shows how their connectivity experience has been. So things such as your initial onboarding, association, authentications, getting an IP assigned and all.25:51So the ongoing connectivity once they're connected. The client dashboard is the 1st step that you look into when you are measuring the performance of your wired or wireless clients that are connected to your network. You get an overall health of your client devices, but there is also a breakdown of all those connectivity related metrics.26:11You can not only see whether the devices are connected successfully or failed, but you'll have a more breakdown information for the reasons behind the connectivity failure and things as such. So there is also metrics such as the client onboarding times, the RSSA values, the SNR ratios as well.26:31So it gives you a list of all the connected clients, you can get overall in information for each of the clients, but you can also deep dive into a specific client on on a per device basis.26:51So, previously when we looked at the network dashboard, we had the ability to go into the device three 60 in the client dashboard, we'll have something similar, we can navigate into the client three 60 page. Let's get into the demo.27:03So similar to the overall and network dashboards, we would click on the client tab to get all information that is relating to the wired and wireless clients. Similarly, we have a timeline, all the options that are similar between all the dashboards, but what's more important is the split of the wireless and.27:21Why the clients and what the performance is.27:41Right. You can also filter them based upon SSID and bands that you're wanting to target for your troubleshooting. At the top of the dashboard you have the filtration option and here what you get is the latest of the trend perspective of the wireless and wireless clients. You get a sanity diagra.27:44Of all your active clients, how many of them have had a good experience with proper connectivity or which ones were not onboarded and you can dig down deeper into what is going on with them. You have the same set of information for your wired clients as well.28:04And when you click on the details, as I said, you can dig down deeper into what was the failure reason for the ones that were not onboarded, what were some of the top locations, the top access points where you have most of the clients, things as such.28:23And when you click on them, each of these individually you get the list of those clients you know belonging to that segment. Now you also have the site analytics, you get a quick overview of the onboarding attempts, the duration.28:39So that helps you quickly understand what is going on, right? You know, whether it needs any attention, whether it needs you to dig deeper or whether you think it's in a proper help.28:59And you also have the split of you know widgets, you know, based on the client onboarding times, the connect RSSI connectivity, the signal to noise ratio, the roaming times, all of which become useful, you know, when you're troubleshooting certain issues. And you, as I said, you can dig down deeper by clicking on each of these metrics individually.29:09Right, so here e.g. if you want to target the client onboarding times belonging to a certain timeframe, you would be able to see the split, you know, what was the onboarding time like you know how much was spent with the association time and how much of it was authentication and DHCP, right? You get all that data presented to you in the.29:29In a very user friendly manner. So this is for your client roaming as well. You get a split of all the clients with the highest roaming time you know ascending to descending. Then you have the fast roaming, the slow roaming, you, so you can target the ones.29:50You know, which are having certain issues with the roaming times.30:10As I said, you will get the list of the clients, so you can classify them, you know, based on their overall health and also you know based upon their individual time timings right on the onboarding time, the association time you would be able to classify them based on that. You also have a tracking feature that you can use.30:17If at all you wanna track a certain client and be notified in case the client gets detected again on your network, you'll be able to do that from here.30:37And you can list, take a look at the list of track clients that you already have you wanted to remove certain things from over there. Then you also have the client count per band and the data rate.30:47So that's about the client health dashboard, and then we have the issues, right? So as you might be already aware, catalyst center, with catalyst center you can view and troubleshoot driven troubleshooting using Cisco AI network analytics and the network analytics it leverages a cloud based.31:11Learning platform, it has some advanced AI and machine learning technologies to provide to provide you intelligent issue detection and analysis.31:31So based upon the telemetry that Atlas Center receives, it detects anomalies to determine, to help you determine the root causes and help ease the troubleshooting experience for you. So let's take a look into the demo of this one.31:40So this is how it would look like. What you would do is go into assurance dashboards, issues and events. Here you would get a list of all the issues, on a global level or even you can select the, you know, site specific view. You can take a look at the open resolved, you know, issues and all.32:00So the ones that you ignore.32:20And there's also the events tab that we look into, but you also have a site hierarchy that from which you can select a specific site that you're targeting and here in the timeline, you get a view, you know, where the issues are color coded, right? So you can quickly dive deep into.32:22Know what those were, you know, based upon their severity.32:42So you can select a specific time frame and take a look at those issues, you know, all classified by the severity and you can click on each of those issues to dive deeper into, you know, what is going on over there and what are the suggested actions.32:46So here, e.g., the one that you're gonna target is a WLC unreachable issue, right? That Center is giving to us. So once we click on it, we can either resolve it or you know or we can ignore it, we can choose to ignore it depending upon its severity and its impact.33:03You can see which area does it belong to, which WLC is this mapped to, and then the suggested actions as well. So catalyst center gives you a list of actions that you can take here. As you can see, you want to check whether the laptop is reachable, whether the physical ports are connected, and then whether the device is accessible.33:23And similarly, we have another issue that we're gonna look at, there is the fabric devices connectivity to the ice server. So we can get more details by clicking on it. Similarly. You have the problem details here. As you can see, the specific manage here is not able to reach the ice server.33:45So you get the details of the device, the time, the location, and the fabric site, and then the problem details.34:05Okay, and also a timeline as to, you know, when did it happen and how long did the issue last? How many clients were affected? Then the suggested actions as well. Now previously we just saw, you know, some text based suggestions, but here what we also have is some workflow based suggestions, right?34:12Where you have, you know, here in this case, you want to verify the route to ice server and catalyst center is able to do that, so it gives you an option to run that check right away from here. So you would be able to run those commands from here and check what is going on.34:32And then, here is another issue a layer two loop symptoms. So you would look, be able to look into these individual problems and, what, what is the initial assessment like Atlas center? What are all the list of ports and the potential loop details?34:51And then with the machine reasoning engine, you also get this ability of root cause analysis, you know, where catalyst center is able to perform some reasoning activity, you know, it runs some checks to you know understand what exactly happened. It takes it through a sequence of steps.35:13Workflow and it will, you know, go show you the conclusion of that workflow. So as you can see, it detected a loop on VLAN 31 and here is the suggested action for it.35:33Similarly in the events tab, you, you get a color coded map, right? A color grid, I would say, you know, of all these individual devices and what's going on at each of these time frames in the last 24 h or whatever timeline that you select.35:51And then you are able to see the list of events based upon which category they are, you can categorize them into devices or endpoints, and then you can see the list of events.36:14Right, that happened whether there are linked up down status, you know, whether their device availability was affected, things are such, you will be able to see all of them listed over here and you can filter them by timeframe. There is also the event analytics preview that will classify them, you know, based upon whether.36:30That was received as a syslog message, you know, what was the transition? When did the device go unreachable? When did it come back into a reachable state? It will give you all those details.36:50We'll also classify the highest severity events, the number of rare events, and what are those types and the high volume ones that you had. So there's a bunch of metrics here that are useful to you, right? There is.37:03Not, I mean, I I don't think you would need all of them to troubleshoot your issue and you it won't be glaring most of the time, but all of these can be helpful when you're targeting certain problem, right? You have the option to filter them. You have the option to look at the data that you need and then go from there.37:22Right instead of looking at the entire dashboard. So as you can see, we have the split based on wired and wireless events. This is how it looks like for wireless events as well. You will be able to target them by switching into this tab, you know, look at all the classifications and understand what's going on.37:42So, so far we reviewed the foundation, we looked into the telemetry settings, the health dashboards from different perspectives and the guided issue resolution, right? Now, the best way to understand you know how it is applied to, you know, generate you know the most tickets rate your clients, your wireless experience, right?38:10So I'm gonna hand it over to who will take you into the client three 60 and user three 60 client analytics intelligent capture and the OTA tool.38:30All right. Thank you Sai. You can see my screen? Yes? Yep. All right. Just before I go on with client three 60 and user 3602 details, remind you of the Q and A panel that you have for questions.38:40Should you have any and acknowledge something those sessions are recorded and due to a little bit of a reorg, we were not posting those diligently, but this is all getting sorted. So.39:00So, there's NO planning of seeing this, the current, the current session only in August it should be available before that. So rest assured all is recorded and we will try to get it to you as soon as possible. All right?39:18So without further ado, client three 60 and user three 60. Let's get started. So client three 60 really helps you to understand what the user experience on a specific device. It gives you a clear picture of device health over time.39:36Shows details like IP and MAC addresses, highlights any important issues, the view adapts depending on your that the device is a wired or wireless, and you can see the network onboarding path, the key events, how applications are performing. You can run the path trace.39:56Even between this device and another node to troubleshoot connectivity.40:16Just to give you an example, here's we're starting from client. So as Sai showed you, we have wireless and wired clients, and then we can appreciate the different details. If I click into the details of a wireless client, I can click this, this graph.40:24And focus only on these clients that were failing onboarding. You can see their own in poor health, so that clues me into there might be a little bit of something there.40:43All right, so let's focus on a single client. Here we go, Grace Smith high five phone. So going there, of course, you're in the client three 60 for Grace Smith's iPhone. Now we can see the timeline so we can focus on the information we want at the time we want to get.40:55Get RSSI, SNR, DAP where it was connected, a little bit of stats and events.41:15And then we can see a summary of all that has happened with this device, the onboarding path it followed, the event viewers, so it's it's the polite version of what used to be debug client Mac detail, right?41:22For those that remember that, and then I can delve into detailed information for this, this very device. And you see there Grace Smith in blue has this little blue square. Well, this is how we'll get to user three 60, which is next.41:38So, oh, funny. All right. So, I apologize for that. So as you can see, this is only Grace Smith's iPhone, right? And we view all the detailed information.42:00Now let's delve into the the user three 60.42:19So the user three 60 will give you another view that centers around the user itself. So if a problem was to, was following a single device, say I have issues with my, with my iPhone, but I don't have any issues with my MacBook Pro.42:25But then, maybe just going to a client three 60 would allow me to actually understand. But if I'm not sure I can search for my client by username, e.g., Grace Smith, and then I would get to see all of Grace Smith's device.42:45Devices, so she has an iPad, she has an iPhone, she has a PC and she has her Galaxy Pro, and all the devices are ordered by tabs like that, and each tab has a health score so that you can see, hey, she's having a problem with her iPad. She's not having a problem with her PC.43:05Your iPhone, but iPad is problematic.43:25And if I click on it, then I get the precise view of the client three 60 for that very device. Okay, so let's start a troubleshooting session. So I'm gonna go to my dashboard as you saw, I'm going to search.43:28Search for Grace Smith, and I'm going to search for her username. See here, I can see her devices listed, but I can also see Grace Smith, the user.43:48So let's choose Grace Smith, the user, so there you go, user three 60. That's another way to get to that, to that view and remember there's also that.43:59Wearing client devices when you go to the bottom to get all the juicy details, there's also the, that shortcut that's available to you.44:20All right, let's keep going. So Grace Smith's iPad, you can see that she's having she's struggling with, client events, various problems, she's failed a couple of roaming events. She's had issues with onboarding and all of that. So.44:28Let's investigate. Oopsy. Chris, don't be shy.44:46All right. I promise I won't touch anything. So, we have Grace Smith again, we have our iPad. All right.45:03So I have my timeline with all the juicy details that follow. That's a problem with this, with this way of doing things. I apologize.45:21I have the details about her onboarding, so we're still on Grace Smith. I apologize for the little interruption. I can view all the information, the issues, the onboarding information.45:47All the events that have taken place, all the issues that pertain to this client device. I can zoom in and focus only on the successful onboarding or the incomplete onboarding for that matter. And.46:00That will, allow me a correlated view of what happened. So if you know that the client health is declining because of a lower RSSI, the, the, the system.46:15Can detect that. And if the system detects that, well, it it can display it to you and you can choose whatever KPIs you you see fit to see what has happened. See, we've got connectivity issues and then it also happens to be at times where we have.46:32E.g., a low SNR.46:53Or more retries. So we get to pick the various metrics that we want to see. E.g., channel utilization just for, for, the, the sake of the example. If I go to client utilization, I will see it displayed and if there's a peak, maybe that could be the cause of the.46:55This issue with Grace's iPad.47:15All right, another point in in this in this summary is I get graphs about the RF quality and the roaming events and I can dig into each and what and.47:20Every one of those.47:40So when I had good RSSI, when I had four RSNR, how many percent, what is the percentage of retries? All the events that have taken place for that for that device when it authenticated, when it asked for a new IP address or renewed its lease, so I can.47:42Can see all this information and having it all collated in a single place allows me again to use that correlation. So this is a list of all the issues for that very device for Grace's iPad.48:02Here's the event viewer. Remember the polite view of, of seeing all the details about the association as well as the onboarding path. So I can see that she connected through an AP that AP is connected to a switch, which is then connected to the WLC.48:20So I can see the whole path like that. If I see that little red item where we were stopped, that's because there is a capture happening at the same time. So, I will be able to go back and take a look at what happened.48:39And my detailed device information will give me information on the device itself. It will give me information about the connectivity, the RF experience, and also, another, really interesting part, which is the AI analytics.49:00So client analytics while we're on it. Basically, it provides detailed insights and troubleshooting capabilities for the wireless client devices on the network. It enables you to understand the client behavior, the connectivity and the performance issues. So we have, here we have a a set of.49:31Our client insights as you can see here on the upper, upper left corner, this feature is made possible, by the way, with our through a partnership that we have with Apple and Samsung. We also have one with Intel, and.49:51Basically in wireless, for those wireless buffs among you, you know that we're always dependent on the client device, right? And we barely ever have any notion of what the client device, how the client device views the world. So this is.50:08Shifting the scale, because it allows you to gain a perspective through Catalyst Center of how the Apple or Samsung or Intel device views the world. It gives you information about the model of the, the nick. It gives you information about the OS.50:26It gives you information about, how it sees everything around it. And it also gives you information on the driver version.50:46So, for those that have been in the wireless business for a while, you know that we've had our share of issues with various client drivers, Intel being soap ever present in, in the the roster of and and enterprise fleets of laptops and P.50:56See oftentimes we're having maybe little bit of a compatibility issue with some drivers, so you can view the driver version from there if the Intel analytics are actually turned on. So it could, it is a valuable troubleshooting tool in that sense.51:15So, again, you know, it will allow you to view the out of date driver. It will allow you to validate what driver should be used, identify some hardware issues, misbehaving APs also. It could be cluing cluing you in to.51:37Roaming behavior roaming decision because you can see why a client has moved or disconnected. You get the juicy detail that you usually don't see, are being sent now to catalyst center. And, client will also automatically report if they find themselves in the port.51:57Our RF environment, so giving you lots and lots of input about how the device is behaving and the why it's behaving this way.52:17By the way, for Intel analytics, one thing that you have to know is that you need PMF enabled, and this is a sample of the information that you would see for in that Intel analytics tab. So you can see that we see the number of reported errors.52:32Temporary disconnections, you can see low RSSI and then you can see all the roaming events and it's a little bit like the two D maps that we have in the hierarchy where one can draw lines to the other that it can see. But at this time, at this time it's the the device.52:51That is at the center of this of this triangle, right? So you can see how the device views each and every one of these APs.53:11So basically the information is coming through the controller, so device has, Intel analytics possibilities, and you've got the PMF enabled. So the controller will get the data. If you were looking from the.53:24The controller, you'd see from show wireless client Mac address with the MAC address stats PC analytics.53:45You'd see this information, but when you're trying to troubleshoot and to understand things fast, even if you're looking at the UI, which you have displayed on your left hand side from the controller, it's not as.53:52It's not as intuitive, so that's why they brought it in Catalyst Center because you're already troubleshooting a client device so Catalyst Center's view is a little bit more intuitive and allows you to get a grasp.54:07Of what's being, what's being displayed. Alright, again, we find ourselves in the three 60 view. So, this is Grace Smith's iPad.54:23Alright, so you can see all this juicy stuff and then I have iOS analytics. That's the name for for Apple that is enabled, so I get the iOS analytics tab.54:38And then I can see this view from the the client device and I can see, ok, this this AP is neg 44. This one is neg 50. This one is neg 22. Here's the list of APs I can see. Here's the list of.54:54Of, client association reasons and why I decided to actually disconnect from this AP and that other AP. So here's an example of the Intel connectivity analytics.55:13So it's similar, but we renamed, of course, the, the tab and you could see here that the device through which this client is actually connected to, is in blue.55:30Right? And I have a few reported errors here, so invalid invalid information elements, alright?55:46So I get lots and lots of details, to, to better understand, how the devices are behaving beyond the usual kvrs that try to stir the, the, the client device into, into onto.56:05To another AT. Now this time you also can understand why.56:25Why the the the your KBR is not functioning the way you would like them to, to function. All right? Another example here, so, in iOS analytics.56:32I can see all the details and again my device that is at the center of it all, right? I can see where it's connected, and this is actually very, very clear. I mean the.56:54User has disconnected, the device is little and so on and so forth. You know what's happening because you have the view. And by the way, you can dig also into roaming events. So you can view what happened then.57:14You can click on all of these and get more details alright, by the way, if you want to.57:33Level this tool, what you need, you need 9800. That's the only platform that is supported for that. In terms of, APs, it would have be, it would have to be eight oh two to eleven AX APs, wave two APs.57:53The version for WLC is 1761I sure hope that you're at least at this version at this point. It is supported on this list of Apple Intel chip sets.58:13And driver software and these iOS XE WLC platforms. So most of them are there CL 40 and 80. Alright, let's move on to another really nifty tool, the OTA tool. So Catalyst Center.58:27Can actually do, intelligent capture with over the air. It was introduced in 237, intelligent capture is.58:47A swisst knife I'd say, of, of features. So we have passive on demand statistics and RF data from the AP. So, by the way, when I when we say real time, it's more frequent than the 5 min snapshot that we.58:59To get in on assurance. If you enable icap for real time, it'll be like every 30 s that the data is refreshed. You can also schedule intelligent capture and there's location traffic if you have spaces or CMX.59:19And we also have on demand SPEC for your access points. So that could also allow you to to better understand your RF environment. It uses intelligent packet capture. It uses a communication stream.59:36Frame directly between the AP and catalyst center. So here's a warning. You have to be able to communicate between Catalyst Center and the AP.59:57Directly, it's not going through the controller, so you might have to adjust some some firewalls and/access lists depending on the case, so that the streaming telemetry can, can be exported. It's using GRPC with HTTP 2.2 point oh. You get.01:00:10Real time client stats, AP stats, anomaly based PCAP, the anomaly events, and the spectrum data. This is what get that gets fed from the AP, and then from the WLC, you get the events and anomalies, you get the RRM data, the AAA failures, the AP.01:00:30The information, the KPIs, the client statistics and all of that, the usual stuff.01:00:49So, again, because it's, it's a lot of data, we recommend that you have, well, it's not a recommendation. You have to have a direct GRPC connection. It's TCP port, 32626.01:00:55And there's going to be a tunnel between the catalyst centered and the AP. So if you have firewalls, bear that in mind. And also, if you have spaces in CN or CMX.01:01:13CMX is also still supported. If you're using location services, it's, it's it's really awesome. It's a really awesome feature. I I I would highly recommend. So to enable the the intelligent capture, you have to go to menu assurance and then intelligence.01:01:29Capture settings. Under this 3rd tab, we'll see that later on the demo. You have the AP tab, there are two features, ok? So there's anomaly capture, which is a packet capture when an issue comes in, a little bit like what we saw earlier, and there's AP stats capture, so.01:01:49This is RF and real time stats. By default, of course, it's not enabled, and bear in mind that icap, there's a, there is a limit of a, about a thousand sessions and if you have.01:02:09I doubt that you end up running all 1000, but bear that in mind. You do have to to be careful about that. So, the capabilities, well.01:02:27The the youth, 1st of all, if an end user is having a persistent issue connect connection drops, long onboarding times, you know, something that's, that's really specific, then.01:02:45The, the, this tool will be perfect, because, it's packet level viewing because of its packet viewing capabilities. So, as you see in the 1st image.01:03:04It's go oops, so this image here, each triangle that you see is a packet sent from the AP to the client or to from the client to the AP depending on whether it's a.01:03:18A packet pointing up or pointing down, and, and, it will show you all the the information that you need. So you could be looking for.01:03:38AP statistics, how many clients are connected, channel utilization, all these, these things, let's let's make it take it into context and and move on to the demo so that you can understand better.01:03:57So once again, we're going back to Grace Smith's iPad. So we have the intelligent capture feature here on the top right here. So this is the iPad. I'm clicking on the intelligent capture.01:04:15Going, going into this, you can see a timeline of of the anomalies. So the red here is the anomalies. In the middle you have the location and the floormat. You can see the client moving about.01:04:35And this is really my nemossys, this presentation, so on the left you can filter on based on the anomaly. So let's focus here on the key exchange.01:04:52Will scroll down. Alright, so you can see here I have this, this key exchange that's, that's not working well.01:05:11I have my KPIs, packet numbers, all the events, so let's focus on, you saw that I can click on the anomaly.01:05:38And see the key exchanges in great detail here. So I can see the packets in and out and the exchanges So this is green, so this.01:05:55This so far is good, but as we move along to the right.01:06:15You'll see that it it's becoming red. Those packets were sent, but the the client never responded. So when it's pointing down, it's coming from the AP. When it's pointing up, it's the answer from the client. So as you can see, we saw, we w we saw.01:06:19See the the state of the transaction, I could download the packets.01:06:39And that would be in a PCAP format, and that way, I would be able to get all the juicy stuff. If I focus on the APC, I can go into the anomaly capture and AP stats capture.01:06:43Which will allowed me to tweak my packet capture.01:07:04So if I was scheduling one, e.g., a client capture, I can choose my device and then click on run now or run later, and I will have my list of wlcs.01:07:09That I'm going to focus on, so let's plan this for 11:00 P.M. oh AM ok alright, and we can take 8 h e.g., and it's on this wireless controller.01:07:24So I could, I could start a capture like that, ok? So this is another way that I could actually capture my settings. So the the crux, the one thing that I want you to remember that's very important is that all of this starts in the.01:07:44Intelligent capture tab. You can view all those parameters and tweak them to your, to your liking and when you come here, you can also download those, those traces and PCAP formats, so that's really, really handy.01:08:04Going back, I have Grace. Her anomaly. I'm going to focus on that again.01:08:25You can see here, what I was showing you earlier, the anomaly here. If I click on this tab, I will only see those dots that are red, ok?01:08:40And if I, if I could, if I come here in the on the map, if you have your CMX integration.01:09:04I apologize, I'm trying to go back to map. If you have your CMX integration, you'll see your customer client device as it moves about. It's very, it's very nifty, it's very well done, and it's very intuitive. It allows you to understand a whole bunch.01:09:14About, all of this, all of this stuff.01:09:34For that particular use case, what you need is Aeros A.ten 01:51 or 1751 and above, and obviously catalyst center ideally at 237 right now the gold version is 237.01:09:41Ten, and I invite you to, look into upgrading your.01:10:01Your, systems if they're not, this is implementing an even eleven is out. Eleven is implementing our agent, in catalyst center. We have an AI agent, and so you can actually ask your agent, hey.01:10:08Hey, show me why, my, my customer Grace Grace Smith's iPad, my client device was disconnected and what are the issues that are detected with it? And it will bring you a report with all that, that information. So it's really, really cool to see how it works.01:10:28Oh, anyways, all that being said, for the intelligent capture, as I said, aeros A.ten 01:51, iOS 60.01:10:48Ideally above 17 five catalyst center, ideally 237, and then of course, aeros, controllers, you need either 3504 or 55 twenties or 85 forties.01:10:58And or the 9800 family. For APs that are supporting this, that is even more interesting, but I'm pretty sure that everybody has that on in their rosters so 1540 1560, the 1800 series, that's.01:11:142800 series, the 38, the 48.01:11:35And of course the 90 ones as you can see here. Okay, so, pain point, right?01:11:37I want to actually troubleshoot client issues along with being able to troubleshoot I need, I have an issue with a client that's roaming and I want to understand what's happening, right?01:11:55So, here's what I can do. I can do the icap OTA sniffer using using the, the, the intelligent capture OTA feature and we can see all the progress that's being done and.01:12:11I can.01:12:32Load them up in Wireshark and, and, and, you know, slice and dice them as however I want. I can also analyze them in a catalyst center. Alright, so to go in there.01:12:34Another demo. So, we go under as I said, our, assurance intelligent capture.01:12:52Oh, ok. I'm having issues with my demo here again. Okay, so.01:13:15Let's take an example for an AP, ok? So I'm going to go there and, and check out the view, the device three 60 and from device 360I could run the OTA capture.01:13:32Okay, I can run intelligent capture. I can also run the OTA capture. So I'm going to click on that. The OTA capture, can allow me to select a certain number of APs that I want to, that I want to.01:13:47Garner information on.01:14:07So I will select the AP that I want. I will select the band, I will select all these details. Now it does require me to change the the a couple of settings on my AP.01:14:15This is very painful. I apologize. Let's start over, right?01:14:37This is OTA. So I come here, I log into my AP, I go to device three 60, and device 360I can run my OTA.01:14:59Running my OTA, I can select where I want to run that, ok? So let's say I'm going to run it over two APs. I'm going to select the parameters that I want.01:15:13So which band am I using? And all these choosy details I'm using 2.4. I am selecting the radios that I want to, to sniff over, and I have to deploy it.01:15:32So deploying, see, I'm sending a few commands that will allow me to, to capture the required traffic. So while this is running.01:15:53You can view that my client capture is also in the works. This is my OTA sniffer. So this is sniffing the traffic between those two. So if I was trying to troubleshoot a client issue that's roaming.01:16:11I can view what it's doing, in this way, alright MRE workflows, very interesting.01:16:31Before, before, people ask MRE is part of our machine learning, but that's embedded in Catalyst Center. You don't necessarily need to connect to the cloud. It's a machine reasoner. It collects client log.01:16:50E.g., in this case the the logs from the WLC and it will also take for input the client, the duration, the data from the client, and it will draw conclusions from that.01:17:09So, you know, it used to be that you had to do everything manually. Log in the controller, enter the Mac address, started tracing, do this and that. So this tool does it all and by the way, Cisco IT are in in in.01:17:27In shop IT uses that to troubleshoot. So it collects RA traces, packet captures from the controller's perspective, it can run additional commands, and then we have a network reasoner, that is a workflow based tool that checks things less.01:17:46Such as L three access and good tools to use to check for.01:18:06The the redundant links, there's also the AP focused wireless AP data collection, and then if you have a client focus, there's also wireless client data collection. So the network reasoner is here. It is unique to Catalos Center, and this.01:18:14This is a work workflow based, as I mentioned, and, it will allow you to garner.01:18:34More information. So in practice, let's take another look. So I'll start by going to tools, then network reasoner, I'm going to select wireless client data collection.01:18:43So clicking that, I'm going to input the client Mac address. By the way, be, be bear in mind that every time you run this tool, you, you are going to generate some files.01:19:06If you haven't downloaded them at the end of your exercise, this is Before you click run again, this is your last chance to download the previous files. If you click run again, those files will be overwritten. Alright? Let's go.01:19:23So, data collection. Run again. I have my files, I'm good. I'm going to enter the Mac address. I'm going to say for how long I want to run the tool, ok? I could I could enter it for 1 min, I could go 2 min.01:19:46I could go 30 min. Then I'm going to select the wlcs where I'm going to get the information. I have also to select which of these, these interfaces from the WLC I'm going to select, and then I get I get to pick five APs up to five.01:20:06Okay, so submitting that, everybody's getting their their information and everybody centers around troubleshooting this client, right? So if you have output that you would get from a shell, you could click on that.01:20:26Little blue thing and it will show you the output. So I have debug this and that. It will tell me, ok, you have to enabled this debug debug. If I had study the packet capture, it will show me all the commands that pertain to enabling this packet capture.01:20:46All right, if I issued a show version within that network reasoner, it would show me the output of show version. So I get all this information all in one place.01:21:04So just to give you an idea what it does, it starts a radioactive trace on the controller. So I've started it and I'm showing you the perspective of the controller here. So I can see that there's a packet capture that started.01:21:30And if I bounce the client, hold on.01:21:49Just a few seconds more.01:22:15It'll keep running and eventually.01:22:32I will get my whole machine reasoning issue done. Let's view the details. Alright, so there is a problem with my AP because it's SSH was not enabled. That's best practice, by the way, not to have it enabled.01:22:36So, it is what it is, but I did I was able to garner a bit of information. I've got locks, I've got texts, I've got a PCAP, all these files you download, you can reuse them and understand what happened with your client device.01:22:56Oh, and so this is a real packet capture that you can use in Wireshark that will give you all the info that you're looking for and maybe a few explanations, and then again those are logs from the controller, so you're not bound for within the.01:23:12The parameters of the actual the actual log buffer. So all that being said, as you can see, there are tons of tools that you have in catalyst center to troubleshoot wireless issues from ICAP.01:23:31To OTA, to SPEC, to all the three 60 dashboards, the.the device dashboards and all of that. But without further ado yes, I can see Paul answering to Deb. Deb, we're getting to thousand eyes.01:23:51Phy to you. Awesome. Thank you so much for the wonderful presentation. Let me go ahead and share my screen. Right, so now let's take a look at the integration between the catalyst center and Thousandeyes and how it brings you the visibility of traffic within as well as outside.01:24:10Of your network, especially in cases where you want to ensure whether the network path is performing well and whether the application of your interest is responding correctly, even across public internet which you don't control, right?01:24:29So since this is more of a capability overview and also in the interest of time, I won't be covering the deployment walkthrough. However, we will still look at the benefits that this integration brings to us. So by integrating thousandeyes with your catalyst center, what you gain is faster time to value, meaning you can seamless.01:24:41Deploy your thousand eyes enterprise agents on multiple catalyst nine K series switches from your catalyst center inventory and that will help accelerate your visibility and as well as your implementation. You can view the thousand eyes test results directly within Catalyst Center and you can map that those together.01:25:02A lot with the N bar and C bar information that you already have in catalyst center, and that will help you streamline your monitoring processes especially when it relates to applications.01:25:22And you have the benefit of rapid remediation, you are able to identify and locate network or application issues swiftly across your land, your service provider as well as the cloud or SaaS network, right? Then we have the license entitlement. This is one of the most important benefit I wanted to highlight. I request that you leverage.01:25:32The free thousand entitlements that come with your advantage licenses on your nine case switches, we don't want them to be going mistered you can run those thousand eyes tests on those agents all you need to do is follow a certain set of prerequisites, deploy these agents on your nine case switches and you're good to go.01:25:52So the core components of thousandeyes, I did want to share that before we get into the demo, we have three different types of agents and thousandeyes that can be used to create your synthetic tests and measure the network and application performance from different perspectives, right? They are the cloud agents, then you have the enterprise agents and then the endpoint agent.01:26:12These agents, they conduct, they conduct synthetic tests, they help you simulate real user traffic towards your target destinations. There are a variety of tests that you can run on each of the layers and the best part is that when you run a higher layer test, you all also have the lower layer.01:26:34Metrics nested into that test. So you can correlate those metrics between each other and identify what the issue is.01:26:52So along with the hop by half metrics like the latency data and packet loss, you also have the entire path visualization all the way up until the target. And that kind of data enables you to have the proactive issue identification before, even before your users are impacted if you set, if you set your alert, right?01:26:59The ones of key importance for us today is the enterprise agents since these are the agents that can be deployed on your catalyst nine K devices and you can gain immediate value by running synthetic tests on those agents to towards your business critical applications and services, right? So the enterprise agents are what offer you a comprehensive insight of.01:27:16A view of the application performance from the perspective of your enterprise network.01:27:36So without further ado, I'll get into the demo so this is my catalyst center instance. As I said, the dashboard of importance over here is the application one. The way you go there is clicking on the menu icon, assurance help.01:27:43And then applications, right? And here is where you would see every, you know, every bit of information that you need to troubleshoot your applications, you know, right from the assurance portion, the netflow, and all the, you know, telemetry that you get by enabling C bar and nbar. But what, that of interest.01:28:03Now is the thousand eyes test, right? You are able to integrate both these products, you are able to get the visibility of how many agents have you deployed using your catalyst center on your catalyst nine K devices, how many tests are being run over there, and how can you map those test results to what you have in your catalyst center? E.g., you have this business relevant application.01:28:23Right, you'd be able to look at all the applications that have, that are running into a poor status and based upon what those applications are, you can.01:28:43Create those synthetic tests in thousand eyes, right? And then correlate the information from here to the test data that you have in thousandeyes, right? So you also have a cross launch as well. So when you click on the test, you are able to see the list of tests that are running on your agent.01:28:52So I already have one agent deployed in this lab instance and I created one, a couple of synthetic tests, right? But, the one that we have here is running towards Webex, it's a web based HTTP server test that is the HTTP performance metrics, and as I said since this is a higher layer test.01:29:12That also includes all the lower layer metrics such as network and you know your DNS, all of those information. Now, what is of importance is that you are able to correlate the business relevant application health, the application usage, all that information over here to what's in thousand eyes, right?01:29:32This feature had been a little more improved. The integration has been improved in the newer three.x versions. Yeah but in this version, all that you have to do is deploy an agent on your devices. So you would go into provision, application hosting and then you would.01:29:52Upload the app over here. As you can see, I already have my device here that has been instrumented with the enterprise agent, right? So this has been simplified in the newer version. You just have a single integration that you need to do. But in the prior releases, you also had to take care of the OAuth integration I mean the two, three.01:30:12Next release, you have to take care of the OAuth integration, the settings but in the newer release and VX it's much more. But saying that, you know, once you have the access to your dashboard data, once you are able to see all the tests.01:30:32Over here and once you are able to see all the metrics relating to those tests, you are also able to dig deeper, you know, by clicking on the test name. You know, it will take you to that test page and you will be able to see, you know, those test details, right? I wanted to show you one example, right here.01:30:51There is one example of a Microsoft outage. This is a snapshot of an outage that was captured before. So as you can see, the target is teams.Microsoft.com. This was a HTTP server test that was configured towards this target and it is running for from a variety of cloud agents that we have, right?01:31:11A number of cloud agents over here. You could have your own enterprise agent here as well by mapping it to the test that you're running. This is, just to give you the depth of data that you get in thousandeyes.01:31:31Then you'll see the servers that are being targeted, right? So we have a layer by layer view of each of the, you know, metrics that we get within these layers, right? And you are able to even compare them between different layers, right? So right now in the web layer, we have availability response time throughput.01:31:45And similarly in network we have lost latency jitter, but if you wanted more views over here for your comparison, you could add them over here and it would bring you know all these metrics here. And the best part is that you can focus on a certain timeline that you'd like to target and see what was going on among.01:32:05You know each of these different layers, right? So you have around 24 h, seven day and 14 day period of timelines available. You can go all the way up until 30 days for your you know test data, but if you had an anomaly that you wanted to capture, you can create a snapshot of that and it will still definitely.01:32:24You know, for your reference and if you wanted to share that with the stakeholder, you could share that as well. So as you can see here, you have all this variety of information in the HTTP server layer. We have, you know, the map as well. So we are able to see all the different.01:32:44So you're able to see all the agents located in the different parts of the country and you are able to see a split of the phases, you know, when it was connecting to that web server, right? How much you know what whether there were any errors, you know, in the DNS phase or the connect phase, you know.01:33:03Whether it even reached the send receive or the case. You can also look at the tabler view which gives you an agent by agent you know split of, you know, what the errors were if there were any or the status was, you know, prior to even, you know, the issue happened, what was the response code, you know, what exactly happened over.01:33:22So as you can see, we have multiple agents that had DNS related issues, connect related issues, and also with the TLS session, you know, establishment, right? And you can, you know, look into the response time and throughput metrics as well. But as I said, you have the network, you know, layer that is.01:33:42Also nested here and you can see that, you know, what stands out over here is we have an increment in last you know on on on November 20 somewhere around you know 01:00 A.M. UTC all the way until 02:30 P.M. or 02:30 A.M. UTC, right? And thousand nice is also.01:34:02You know able to give you, you know, something that is called as internet insight. So so thousand Eyes regularly monitors the most popular applications and network providers if at all there are any outages and if at all you're running tests towards those applications or networks, it would automatically map those outages over here. So as you can see, you know.01:34:23Detected an outage within Microsoft and you know that that is available for you to look at, for us to look at.01:34:42So, we can see the last, you know, went up at this time and prior to that, everything was going well, you know, between all these different cloud agents, so we get a path visualization, a hop by hop view from the source agent all the way up until the target. In your case when you deploy your enterprise agent.01:34:49On the cat nine K you would see that over here, you would see all the details that you know related to that, what kind of test was run, what was the last like from that specific agent, the latency jitter, and what was the probing mode that you used for that synthetic test, all those details, right? You can increase or decrease the number of hops from either the source or the top.01:35:09Target perspective if you wanna look at what is going on in, you know, each of those sites and you can even look at each of the links, what was the delay like and you know most of the time when there is an issue here, e.g., if we click on one instance where the issue happened, you know, we can see that the problematic notes are highlighted.01:35:29In red, obviously since we weren't able to reach out you know to the team server, we had you know a red indication that you know all of our cloud agents, but you can also see some links where there is a massive delay or you know some nodes where you have a forwarding loss. So you are able to identify which.01:35:49This specific node is, you know, leading to this problem and you are also able to correlate that with internet insights. So you get a wide visibility of you know where the issue's happening along the way all you know up until your destination, right? So you are able to see, you know, which.01:36:09Agents have been able to communicate which agents were not able to communicate and when did the issue re, you know, revive itself when did it resolve eventually, right? So here in this case you know we have an issue within the Microsoft corporation. That is something we were able to see and we were able to tie the issue.01:36:29With that outage. So, as you can see it is a very helpful tool. You can run these tests towards your business critical applications and you are able to immediately identify once some of your users complain about accessing, e.g., office 3605 or any other applications, you're able to immediately come into this path visualization and.01:36:49And, you know, look back in time as well, see what was going on, which node was the problematic node, and if at all it doesn't lie within your you are able to create a snapshot and send it to the stakeholder who's responsible for that service.01:37:09So that was a quick demo in the interest of time. I know I had to go through it pretty quick, but so the conclusion is that we covered the foundation, the telemetry settings, the difference between assigned to site and provisioning. From there we moved into the dashboards, all the.01:37:25The Metrics available for you over there. Then Mainan took us over the three 60 views, the client analytics, and all the wonderful features, the intelligent capture OTA tool landing data collection. And finally, I was able to show you the extended visibility that you get with thousand eyes, right? So in summary, you know, today's discussion leads you towards one collected.01:37:43Troubleshooting workflow with center assurance as your internal lens and you supplemented that by thousand eyes for the external lens right in a single console. So when an app is reported slow, you can follow the path from, you know, your health dashboards from the wider wireless client all the way up until the cloud, see where the problem lives and show.01:38:03With the data, whether it's yours with other providers. So that means faster resolution, faster, MTTR metrics and clearance conversations.01:38:23No, this was a lot of content, but I really appreciate your patience today and thanks for sticking with us. I hope the session was really useful to you. If you would like to discuss your specific environment or need one on one guidance, we are looking forward to that for any of the things discussed today and when beyond our customer success team is ready to help, so please reach out to us. And once the event ends and you.01:38:35Page will be launched we would really appreciate if you could take a couple of minutes to complete the survey. We'd also like to share our previous year's session recordings and upcoming event schedules and for additional resources, please visit our expert insights like the portal.01:38:55So Matt, do we have any unanswered questions in the Q and A? Nope, it looks like everything's been answered. I think we're ready to close this out since we're running over time a little bit. So thank you everybody for for attending. We're gonna go ahead and close the session now.01:39:13Thank you for your time.01:39:33

About this Video

Author : Cisco Customer Success

Uploaded : June 18, 2026

NetworkingCatalyst Center
AI summary icon

AI summary

The recording shows how Cisco Catalyst Center Assurance and Cisco ThousandEyes work together to transform telemetry into actionable insights for faster troubleshooting. It covers enabling telemetry and Device Controllability, assigning devices to sites, and verifying Telemetry Status. It demonstrates navigating Overall, Network, and Client Health dashboards, interpreting health scores, and using Issues and Events with AI analytics and the Machine Reasoning Engine. It showcases Client 360, User 360, and Client Analytics for Apple and Intel devices, plus Intelligent Capture and the OTA tool for packet-level evidence. It concludes with deploying ThousandEyes Enterprise Agents on Cisco Catalyst 9000 switches via Application Hosting and correlating synthetic tests with Application Health for rapid remediation.

  • Enable Assurance telemetry and Device Controllability, build the site hierarchy, and validate collection across dashboards.
  • Use Client 360, User 360, Issues and Events, MRE, and Intelligent Capture with OTA to isolate root cause from RF to application.
  • Deploy ThousandEyes Enterprise Agents on Catalyst 9000, leverage included entitlements, and correlate tests to speed resolution.