Cisco Customer Success - Video

SDWAN Integration with ThousandEyes

Playback confirmation!

Do you want to resume playing from last left location?

Chapter 1 Thumbnail
00:10
Welcome, introductions, and agenda
Chapter 2 Thumbnail
02:13
Challenges with traditional WAN traffic monitoring
Chapter 3 Thumbnail
05:07
Cisco ThousandEyes overview and key capabilities
Chapter 4 Thumbnail
09:45
Agents, tests, and dashboard basics
Chapter 5 Thumbnail
13:21
SD-WAN integration: prerequisites, routing, and options
Chapter 6 Thumbnail
18:02
Workflow setup: tokens, images, pools, and connection
Chapter 7 Thumbnail
23:17
Troubleshooting and verification commands
Chapter 8 Thumbnail
28:18
vManage workflow demo and agent deployment
Chapter 9 Thumbnail
51:00
ThousandEyes UI tour: agents, tests, alerts, and units
Chapter 10 Thumbnail
01:08:45
Views, path visualization, endpoint agents, and wrap-up

Transcript

All right, good morning, good afternoon folks. Thank you so much for joining us today. Today's topic is going to be SD WAN integration with thousand eyes.00:10Today I am joined by my colleagues from the NXCSS team. I'll be going over some of the theory portion of what are some of the challenges of thousandeyes of of the traditional van monitoring, how the thousandeyes solution helps us overcome some of those challenges, and I'll be going over the deployment workflow. My colleague Tusha will be going.00:19Through the live demo towards the end of the session and he'll show us how things look when you're deploying thousand eyes from the SD WAN dashboard perspective. And then I'll have Sai take over from him and show us how things look on the thousand eyes side of this workflow.00:39And we also have Ryan joining us today as panelists. So, if you have any questions, any concerns, anything, please go ahead and reach out to us in the chat. If we don't have an answer for your question right away, we're happy to take it as homework, take it back with us and reach out to you with the answers for your questions. But please do keep this.00:55Session interactive in the chat.01:15All right, so today's agenda is going to be a quick introduction. We'll go through some challenges that traditional band monitoring is faced with. We'll look at thousandeyes solution. We'll talk about how it helps us overcome those challenges.01:20We'll go over what are the components of this thousand eyes solution. We'll look into some deployment options, deployment prerequisites and firewall port considerations. Then once we start with the deployment workflow, we'll go through the steps that we take to set up the workflow.01:37We'll address some common troubleshooting or challenges that you may face during the workflow. And finally, I'll talk about how do we monitor these agents once you've successfully set up the workflow. And towards the end as promised, we'll have a live demo.01:55All right, so 1st thing, let's talk about some traditional, some challenges we have with the traditional band traffic monitoring, right? So firstly, we know that right now our users are not in the office and our applications are not in the data center. We have our users working as remote employees from around the world.02:13And we have applications hosted and moving towards the cloud as well. So it's just as important today to understand how our traffic is performing out there on the internet as well, which is where we start seeing some challenges with the traditional when traffic monitoring, right?02:32With SD WAN, we do get some visibility into the enterprise networks, we get visibility into how the traffic is performing through our overlay tunnels. However, as soon as the traffic leaves the SD WAN fabric and it enters maybe your provider's network, it enters your cloud pro provider's architecture.02:50That's where our visibility starts to become limited, and that's where the troubleshooting also starts to become challenging. That's why one of the 1st challenges we get is limited visibility beyond the SD WAN fabric, which directly leads us to our second issue, which is difficulty identifying the ISP and internet path issues, right?03:08When a user reports poor application performance, IT teams are often left wondering, well, I know that the issue is not in my network. I know that it's somewhere out there, but our traffic is going through so many hops in the network that it becomes challenging for us to understand, 1st of all, which path is my traffic taking and where in this path is my traffic being.03:27Impacted. Maybe it's packet loss, maybe asymmetric routing, maybe latency. It could be several things. But without that visibility resolution takes longer time, which leads us directly to our 3rd challenge, which is a longer mean time resolution.03:47And while we're dealing with all of this, it becomes critical for the IT teams to troubleshoot the issue and understand what's actually causing the issue because they're having to engage with multiple providers, analyze and investigate the issue at multiple different hops.04:02Off the traffic from source to destination making it challenging to isolate the issue in a shorter amount of time. And somewhere here we also start to see a gap in how our end users experiences and what our level of knowledge is when it comes to end user experience. With our traditional SD WAN metrics.04:17They don't always show us what the user's experience is actually like, right? Maybe there are some users who are seeing slow HTTP page loads, maybe there's some delay in DNS resolution and maybe there's some overall performance issues with our applications. Unfortunately, the traditional metrics don't cover that information for us. That's where we.04:37Have the thousand eyes endpoint agents that helps us close that gap by providing us both user level and device level visibility.04:57So that's where we have Cisco thousandeyes solution into the picture, right? And I think it's safe to say that thousandeyes has been around for quite some time now, so most of us may have heard of it. Some of us may have already worked with it pretty intensely. But if there's anyone here that is brand new to Cisco Thousandeyes, welcome. Cisco thousand Eyes is.05:07A simple cloud based intelligent platform that extends visibility across our entire digital delivery path. So all the way from source, all the way to the destination. It helps our IT teams to see how applications and services are performing not only within our enterprise infrastructure.05:27But I also have visibility on how it's performing out there on the internet, on the way it's to its server, right? So that's one of the 1st capabilities that Cisco thousandeyes provides, which is the end to end network visibility. Second, we also have internet and ISP path intelligence, which helps us identify issues beyond our enterprise boundaries.05:44It's actually, one of the key options that we see in our main thousandeyes dashboard which we'll cover towards the end of this deck. Thirdly, we also have the application experience monitoring, so now we know exactly how our users are feeling about our applications, whether it's hosted within our enterprise network or outside somewhere on the cloud.06:05All of these capabilities directly lead the IT teams to rapid root cause analysis, which means not only are we resolving our issues faster and improving our performance, but we're also building resilient digital infrastructures. So what are the components that entail thousand Eyes, right? Thousandeyes, it all.06:24Operates in a very simple workflow strategy, right? 1st thing you're doing is you're gonna deploy the agents.06:44And then you're gonna go ahead and define the test, and then we'll analyze the data that is the result of the test we've defined. And we'll do a little bit of a deep dive into what each of these component entails. So let's 1st look at the agents, right? We have three types of agents. We have the cloud agents, enterprise agents.06:50Agents and endpoint agents. While for the scope of the SD WAN integration.07:10It's enough to know about enterprise agents. I think it would be a disgrace for me to not talk about what cloud agents and endpoint agents also have to offer, right? Cloud agents are globally distributed and managed by thousandeyes. On the slide, you can see there's a screenshot from the thousandeyes dashboard which shows you how dispersed these cloud agents are.07:16But what is the use case here, right? E.g., if you have any applications, any public facing applications that you're hosting within your enterprise infrastructure.07:36You will want to know how the users out there regardless of where they're connecting from, which part of the world they're connecting from. You will want to know how your application is performing and how the users are feeling about these applications. That's where cloud agents shine. They give us this outside in perspective, so we have a good amount of information on how.07:45How our users are perceiving the applications that are facing the internet?08:05Then we have the enterprise and the endpoint agents. The enterprise agents are customer managed and they're deployed within our enterprise infrastructure, maybe branch sites, data centers or even in cloud environments. They monitor connectivity and performance for both internal and external.08:10Services. So you could say that they give us an inside out perspective of how our network is performing and how our applications are performing. Contrary to that, the endpoint agents are directly installed on employee PCs, Macs, and their personal devices, right? These agents show the real experience of what the individual.08:30Your user is facing when they're connecting to our internal enterprise infrastructure from outside, from a remote location. Especially let's say if these users are reporting any application performance issues, IT teams, because these endpoint agents also monitor how the underlying Wi Fi van.08:50An internet connection of the user is performing, IT teams are able to quickly decipher whether the issue is with the application server with the enterprise infrastructure or if the issue is with the local network that the user is connecting from. By combining these three types of agents, the cloud, enterprise and endpoint organiz.09:09Organizations are able to achieve a comprehensive visibility into how our enterprise network is performing, how our applications are performing, and cherry on cake is how the users are feeling about both of these elements.09:29Now, 2nd component of the solution is the test, right? As you can see in this diagram, you are able to set up tests at various levels. At the network level, you are able to set up tests such as agent to server and agent to age to understand how.09:45The connectivity is looking, how the path performance is, and several other metrics. At routing level, you are able to set up BGP tests which provide visibility into internet route announcements or maybe even routing behavior. Maybe you're troubleshooting some reachability issues. So you're able to leverage the tests on this level.10:00And then you also have the DNS level test that you're able to do where you're able to use it to leverage to troubleshoot any DNS resolution issues, any delays with DNS resolution, and the more popular one, which is the HTTP server test that's done at the web layer, right? At this stage, you are able to understand the availability of the HTTP server.10:18And you're able to get an insight into how the application performance or the web application performance is looking.10:38This is a quick screen grab from what the thousand eyes dashboard looks like when you're trying to set up the test, but certainly we'll spend more time into learning about this dashboard, the various test options we have towards the end in our live demo.10:47And last puzzle piece of the thousand eyes solutions is the data itself. It's just as important to understand once you've deployed the agents, once you've defined the test, it's important for us to understand how to interpret the data that we're seeing, right? Before we go into various options in the thousand eyes dashboards towards the.11:02End of the deck at the during our live demo. I want to give a quick shout out to the main dashboard that we have just to give you an understanding of what kind of elements are we looking at in the main dashboard. Firstly, we have the centralized KPI visibility, right? It gives us a quick glance about critical informations, right? Like are my agents online? Where are the.11:21Geographically located. If I have any tests defined, e.g., in the screenshot here, you can see that I have a HTTP server test set up for cisco.webex.com.11:41And it gives me information about what is my server availability looking like, what is my round trip time? Now, it directly leads me to our second element, which is the drill down troubleshooting, right? In addition to getting a quick glance of what my overview is giving me, I'm able to drill down into specifics. Teams can begin with like a high level troubleshooting flow.11:52From the dashboard and then start going into individual tests, clicking on it and maybe understanding what kind of metrics are you looking at. If you wanna edit the settings of the test, maybe you want to set a higher threshold for what constitutes as a packet loss. You can go ahead and do that. You also have path visualization where you're able to understand exactly how the thousand eye pro.12:12Hopes are moving from source to destination. So the drill down troubleshooting helps you get a deeper perspective into some of these agents and the tests that they're conducting. And the last.12:32I guess option I want to shout out on this dashboard is the Internet insights, right? This allows for IT teams or any operations teams that's managing these networks for you to have a understanding of any internet outages that maybe happening out there. As a result, if there are any internal test failures.12:43And at the same time, let's say maybe there's like a ISP server outage going on. So they're able to correlate and quickly understand that it could be the, you know, cause of the issue. Alright, so now that we understand the components of the thousand eyes solution, let's quickly look into what are some of the deployment requirements, right?13:01For the SD WAN, in order for us to use this workflow based integration, and I just want to quickly call out that for the purpose of this presentation and for the purpose of the demo, we'll be using the workflow method today. A lot of you folks here who've been working with Thousandeyes in the past.13:21And let's say you work with older releases or maybe you were working with devices that were being managed by your classic templates and classic policies, you would have done the the integration and the traditional method. But with SD WAN versions starting from 2016 and higher.13:38And provided your devices are being managed by config groups, you are now able to leverage a workflow to set up this integration. It is very simple, very straightforward, and it just takes us four steps to perform that. We'll go over that deployment workflow a little later in this deck. 2nd main requirement is default routing and.13:55It is extremely important that we take care of this because we need to make sure our thousand eyes agent which is deployed on our routers is able to communicate to the backend servers over the public internet. The 3rd main requirement is a global IP address pool and DNS servers.14:16It is essential for these to be configured because A agent needs an IP address and B agent needs the DNS servers to be able to resolve the host name of the thousand eyes backend servers to be able to communicate with them to periodically check in with them. And lastly, from SD one perspective, the only other thing pending would be to make sure.14:33For downloading the right thousand eyes agent software from the thousand eyes portal.14:53And you're gonna upload it to the software repository. Now from thousandeyes perspective, the main thing that you want to make sure is you have an account with organization admin role so that you're able to download the agent, copy the you're able to set up the agent, copy the account group token, and just start the workflow.14:57With these requirements in place, the only other thing pending for us is to understand what are our options, right? When it comes to deployment. There are two ways you can associate an agent. Either you can deploy it through transport VPN or you can deploy it to service VPN and each one serves a different use case.15:16The transport VPN option would be best suited if you have a single WAN interface environments, right? In this option, thousandeyes traffic probes will just use whatever underlay connection is available and your routing or any policy configuration that you have will have NO bearing on how this traffic is being routed.15:36However, if you have multi van deployment, right? If you have multiple VAN interfaces, then placing the thousand Eyes agent in transport VPN may not be the most useful thing to do because it will cause the router to load balance the probe traffic, which means the result that we get from it may not be consistent and not so useful.15:55Right because it's not following the same path each time. In such a scenario, it would be ideal for us to set up the thousandeyes agent in the service VPN option. And it is also recommended to use this option when application performance monitoring is your more important use case, right? It not only provides us granular control over.16:15Which van transport the probes are going to be sent out on. But it also helps us or rather empowers us to conduct a lot of these tests to our application servers to see how they're performing.16:35With service VPNs, IT teams or anyone that's, you know, setting up these for you can create data policies that directly influence how these probes are being routed out from your network to the backend servers. So for this reason, service VPN is generally what the preferred method is. And as a matter of fact, for the scope of.16:47Of this demonstration, we're doing the same because we're trying to show you how we can monitor applications using this integration.17:07Lastly firewall port considerations. I'm not gonna go into each of these, but if you happen to have a firewall in the path between the agent and thousandeyes backend servers out on the internet, you would wanna make sure your firewall is allowing traffic in the outbound/inbound direction depending on which port we're looking at. So this is gonna be.17:15A quick handy guide for you to make sure your firewall is allowing all of these ports.17:35That said, let's start looking into what are the simple four steps that we need to perform in order for us to set up this integration. So couple of these steps maybe familiar to you if you've already done this integration in the past. So step one is gonna be obtaining the account group token from the thousandeyes portal.17:42So for that, you'll 1st log into your thousandeyes dashboard. You'll click on network and app synthetics, click on agent settings, and then click on add new enterprise agent. For the purpose of integrating SD WAN with thousandeyes, you're gonna click on catalyst routing.18:02Which will take you to this page where you'll be able to copy the account group token. There are two important actions you'll be performing on this page, right? One is you're gonna copy this account group token and maybe safely store it in a notepad, a text document, whatever works for you.18:19And then you'll want to download the right image. Now, when these screenshots were taken and also for the demonstration, we're using C 8300 and C 8200, both of which are X 86 architecture, so you should be able to download this image. And as a matter of fact, I think a lot of hardware platforms that you'll be working with are going to be this architecture. However.18:34You will want to make sure you're verifying this once. If you could just go ahead and share the document, there is a complete list of supported hardware and software documents and the table also mentions what architecture it is. So it will be a good handy guide for you to understand 1st of all, whether your router is supported or not and.18:54What architecture image you need to be downloading. Thank you, Tushar. So step two is going to be the image that you downloaded in the previous page. You're gonna go ahead and upload that to the vmanage repository. So you'll go back to your catalyst dashboard. You're gonna click on maintenance, software repository.19:14Then click on virtual images, click on manager, and you can either drag or drop the image or you can search for it. But once you go ahead and upload the image, the only other step pending on your dashboard side would be to set up a network pool from the network hierarchy page.19:34For that, you'll go to configuration, click on network hierarchy, click on add pool. This will be under your global settings. You're gonna click on add pool. I gave it a name called thousandeyes pool. This is the subnet that will be used to provide IP addresses to the thousand eyes agent and the gateway.19:52We'll show you exactly what that looks like. So I use a subnet 192168 hundred.zero and I use the mask 24. So go ahead and add that. Now the last step is starting the workflow from the workflow library on the dashboard.20:10You'll go into workflows, click on workflow library, and then search for configure thousandeyes. You can go ahead and click start. And this is a pretty self explanatory step by step guide. So 1st thing you're gonna do is you're gonna connect the Cisco Thousandeyes account. This is usually.20:27Something that you'll only do the very 1st time, right? Once you've established the connection, it's gonna stay connected. So you'll only do the step 1st time. You're gonna click on connect thousand eyes. It's gonna prompt you the window that's shown on 2nd screenshot. Go ahead and confirm your information and that should be it.20:44Once that step is successfully completed, in the account groups, all your account groups will be listed. In my case, I only had one at the time of the screenshot, so I go ahead and select that. That's the only one in my dropdown. And next time let's say in the future, if you deploy the agents again, you'll directly be taken to this step. You don't have to do the step one again.21:00Once you've selected the account group, you can select the application. Again, this is an optional step. If you want to choose to go ahead without setting an application, you can also do that. For this demonstration, we've selected Cisco Webex. And then you'll go to the next step. You're gonna click on Webex and you'll fill in the.21:20The subdomain here we filled Cisco.com. The rest of the information is automatically filled in for you, but if you want to adjust the time interval, you are welcome to do so.21:39And then you'll click next, and at this point you'll be selecting which site and which router will be where the the enterprise agent will be deployed. So in our case, we've selected the Mexico site. We're selecting the name of the device and as I said before, we are deploying it on.21:51Service VPN, so the VRF that I have on this router is 104. So I go ahead and select that. If you have multiple vrfs, this dropdown can be used to select the right service VRF.22:11Once you select that, you'll finally reach the summary page. You're gonna verify all the information you've set and you're gonna go ahead and click start monitoring. So that's all the procedure is for how to initiate the workflow. Now, let's look at some common scenarios that.22:21You may face when you are setting up this workflow, right? 1st of all, as soon as you click on start workflow, there are two tasks that are going to be triggered in your activity window. One is going to be the thousand eyes workflow status and the other is going to be your configuration group. The thousandeyes workflow status will almost always go through.22:38Just fine, right? If you're meeting all your requirements, it should go through just fine. Now the config group push is the more important one. Now what essentially is happening here in the backend is the we manage is pushing certain lines of thousand eyes related configuration to your router. So if you run into any issues and config group fails.22:58You can click on it to get additional information. Now, when we were setting up this demo lab, we did run into few issues which we thought we might call out for your benefit, right? E.g., in this case, it looks like the error is pretty straightforward. It tells me it failed to deploy the config group and it says please configure IPV four DNS server.23:17Under van VPN. That seems pretty straightforward, right? So I'm gonna go ahead and click on my config group, click on the transport VPN, and yes, I can see my DNS servers were not configured. So I went ahead and configured those and I saved the changes and deployed the config group again.23:38Now, at this stage, the config group pushed was successful and if you have console logs enabled on your router, this is exactly what you would be seeing on the router when the config group is being pushed. You can see the thousandeyes app is being installed right now.23:56Once it is installed, it's gonna go ahead and create a interface virtual port group for automatically. It's going to assign an IP address to it and it's gonna change the status to up. And then we can see the app hosting itself started, start succeeded. TE started successfully. TE is the app ID for the thousand eyes.24:11And it says current state is running. So this is ideally what you would expect to see in a successful workflow completion status. I also want to quickly shout out what is the exact configuration that will be pushed to your router. So you can see the interface virtual port group four is automatically being pushed. It's getting an IP.24:31The address from the pool that we defined, we see our TE token, which if you recall from the thousandeyes dashboard on step one, you would have copied it to your notepad or text, that is the token that's showing up here is give us information about what is the platform on which this agent is being pushed. So this is a configuration that will be applied to your router.24:51And a successful configuration push would look something like this.25:11Now there are few other commands that you could benefit from if you're ever running into any issues. I think if you're trying to verify what is a configuration being pushed, you can use show SD WAN running config pipe section app hosting. If you have multiple iox applications, you can use the command show app hosting list.25:17My personal favorite is show app hosting detail app ID, and since for a thousand eyes, the app ID is gonna be T you're just gonna write T here. It will give us detail information of the status and it will also give us information on if there are any errors that our thousandeyes probes traffic is facing. I do have a.25:37Screenshot of one of the errors that we ran into, so I'll show you that on the next slide.25:57If you want to directly connect to the container and maybe run few or like you know cat for few logs or tail for some real time logs, this is the command that you would be using to actually directly connect to the container. So you'll be app hosting connect app ID, we'll say TE session bin bash.26:02Once you enter that, you can either cat for teagent.cfg logs to see the exact configuration file or you can even tail or cat for the TE agent.logs to see real time on what is the status of the probes, right? Whether the agent is checking in with the backend server or not. And if you wanna exit from.26:19In the container, you can simply type exit and come out of the container and if you wanna check, maybe you're running into some routing issues, show IP route is yet another command that we commonly use.26:39Now the command that I said my personal favorite, the show app hosting detail app IDTE, this is the output that you'll be getting. We can see it gives us the information of the agent, it gives us the information of the usage, it tells us about the virtual port group four and the IP address being assigned to it.26:51And the more important one, the information about the probe. So when we were deploying this demonstration, we noticed that even though our config group push was successful, for some reason the agent was not showing up on the thousandeyes dashboard. And then we ran this command and we noticed that the probe was failing and.27:09The error indicates call error could not resolve host SC one.thousand eyes.com. So it turns out in our lab it was a routing issue. We didn't have the right NAT commands in place. So once we set that up, we were able to resolve this issue and let's say once you fixed it, you would see something like agent checking in, which means the agent is.27:29Is now checking in with the backend servers. So this is a very useful command to have handy if you're running into any issues where the config group is successful, it's successfully pushed.27:49The app is showing as running, but then maybe the agent is not coming up online on the thousand eyes dashboard or maybe the agent is showing us offline. So this would be a really nice command for you to run to verify. Of course you have TAC teams to reach out to, but these are some things that you can run on your end prior to opening a case with TAC.27:59So now that we've deployed the agent, let's look at how do we monitor the agents, right? So 1st thing, you are actually able to monitor the agents and if you have any tests set up, you're able to monitor it directly from the SD WAN dashboard as well. So you can click on tools, click on Thousandeyes monitoring.28:18And then it will give you the agents that are online. And if you click on the test tab, if you have any tests set up, let's say during the setup, maybe you set up the webex.com as an application for which you want to run some tests, those will also show up under tests. But keep in mind that this is a purely monitoring page only. You cannot set up new tests from here.28:36However, what you can do is if you click on add sites, you can deploy more agents from here. If you click on add site, it directly takes you to your workflow and then you can start deploying the routers from there. But do keep in mind couple of things, right?28:57If for any reason the router you're expecting to see does not show up in the workflow, there are two things you'd want to confirm. One is 1st of all, is this a supported hardware or not? You can refer to the documentation that Tushar shared in the chat for that. 2nd thing is if your router is not being managed by config group, your router will not be listed there. So a couple of.29:12You know, things to keep in mind.29:32So this is what you can see from thousandeyes page. Now let's say you want more information about the results that you're getting from the test. Maybe you want to get more information about the agents. You can directly launch the thousandeyes dashboard from this very page. You'll just click on launch thousandeyes. So let's see how things look from the thousandeyes perspective.29:34On the thousand eyes dashboard, if you click on dashboard, you, you know, if you'll obviously get the view of the agent, the agent status, the tests that are being run, but you can also get more information by clicking on network and app synthetics and click on agents. So at the time of the screenshot we had one agent live, so when I clicked on it.29:53I can see it gives me information about the agent, right? When was the last time it checked in, what platform it's being hosted on and whether it's online or offline. Now let's say you want to set up some tests again you'll click on network and app synthetics, click on test settings, and you have all these options. You can either click on, you can set up an HTTP server test.30:12Test or maybe you want to set up a DNS server test. You can also do that.30:32And let's say, we set up an HTTP server test. This is how the page would look. You will define what the URL is gonna be. You can mention how often you want the test to run. You can select, let's say you have multiple agents and maybe you just want two out of the four agents to run this test. You can also select which agent runs this test.30:37And what kind of alerts you want to receive? Alright, so I'll hand it over to Shar and Sai to give us a live demo now. Is my screen visible? Yes, to Shar, I can see a thousand eyes screen.30:55Okay, alright 1st things 1st, right? So if you, if we take a look at this deployment of enterprise agent, right? There are two few prerequisites that we need to.31:14Go through, right? The 1st one is to download that TE agent and to put in credentials for your thousand eyes portal, right? So the initial portal, when you are going through the workflow, right? Let's say you're trying to add a.31:31Side, right? So initial, initially it will take you through the process of connecting to thousandeyes, right? Portal where you were putting your credentials, right? Which will be, which you would of course have. And the secondary prerequisite is to have that.31:51Have that containerized email image uploaded to your vmanage, which we have already done. If we look at the software repository, virtual images, we already have that uploaded here. That can be downloaded from your.32:11You need a thousand eyes portal, right? Going into agent setting.32:32Here when you're trying to add an agent, it will give you for any of your hardware hardware platforms that are present led into meraki, catalyst switching, catalyst routing, your routers, IR switches and everything, right? So here we did download this.32:40Atlas routing.33:00Catalyst routing agent and our device architecture is X 8664, right? And once we download it and copy this access account group token, that is that will be used on our V manage UI.33:03So, yeah, the access or the agent can be deployed through workflow library as well and it is pre present on our legacy way of doing through templates as well for, but for your today's demo, we'll be going.33:21Going through workflows. This basically is present through workflows as well as tools, right? As we have seen, when we try adding in a site, it will automatically redirect us back to the.33:41Workflows page. Here, once we initially put in our credentials, it will take us to select the account groups, right? Here if we see we have different account groups, right? So here has created her own account.33:58Group which I am part of, right? So I'm gonna select that.34:18Then, going into selecting a particular application, right? What application test do you want, do we want to monitor or what application do we want want to monitor, right? Based on this, it's gonna create a test for us. So we can do continu.34:27You know without application or what does that do is basically deploy a thousand eye agent, right? And we, we would see that we would not be able to see any tests out there.34:46So here, right, if I look at this right now, I have one online agent, right? But I do not see any test created. So we just deployed a thousand eye agent on our C 8200, right? Which is up and we can go into, our thousand eye agent.35:02A thousand IPs and we can look at what are the tests and everything that are set up or can be run through that particular through that particular agent. You will be taking over taking us over that.35:22But yeah, going back to our V manage workflow, right? So, going through selecting a particular account, selecting particular.35:39Application I'm just gonna add a subdomain, here I'm selecting on our primary.35:56We have already deployed a thousand. So whenever we are going through this, you would see it would ask you to select a particular site that you want to deploy that particular agent. Here we are in our scenario, in our use case we are deploying a service site.36:16We are using service site deployment where you can deploy this agent on transport site as well. So here we have created the service site VRF through which we are gonna deploy this. After this rate.36:35What what it gives you is basically your summary of what settings we have done and that is it, right? Once you start monitoring it, it is basically going through the process of deploying, deploying that thousand eyes agent on the.36:52Under device itself.37:12You would see, we do not have to do any configuration or so, right? It basically directly goes through deploying that thousand eye agent and configuration required. What are some prerequisites right now if you see this.37:14This profile was not present, right? This is an auto generated auto generated profile when we went through deploying the thousand eyes agent through the workflows.37:33What are some prerequisites that needs to be prep needs to be present on the device itself as already mentioned, right? We need to have DNS enabled on the device itself, right? Because, our agent or.37:47It makes some API call, right? When we are going through this process, it is making an API call to the thousand eyes portal and then.38:06Grabbing some information and deploying the tests and everything on both the sites. With addition to having DNS present DNS entries present on our device, we need to have.38:18Natting enabled on our transport transport interface. If we do not have NAT enabled on this, right? It does not have or basically it's reaching out to our internet and that particular.38:33Point right data center to grab all the information. So here if you can see this is a lab environment, so we had to put in, domain name to IP address information here for it to resolve whatever API calls that it's making to this part.38:54Particular URL. In addition to that, we have NAT enabled, right? If we, if we see right here we have a NAT route and a NAT statement present on this particular device.39:13Once this is run, right? Like it should go through that process if we are looking at that particular process, right? It should go through if we look at the logs, right? So it's going through that process of configuring iox started is.39:36S IOX.39:53Then successfully downloaded the T package which was present on our vmanage, right? So it's basically downloaded that and it's successfully verifying app IDs. I saw some questions around a failure of deploying a T agent through this particular.39:55Workflow. This could be due to multiple reasons, right? If you do not have NAT enabled, if you do not have DNS.40:15Entries present, right? You would see some issues while deploying this particular thousandeyes agent. Here this is our primary router which already had a deployed thousand eye agent.40:25Right? So when I ran, when I run few of this commands right show as the running pipe section app hosting, it gives me information about our thousand eye agent, right? If we look at some of this information, right, one key key.40:42Detail that I missed right was we creating, we creating a pool for this, right? A IP pool for this.41:02Right, so if we go into pools, right, we already had a pool creator for this, right? This pool is basically being used, used by our thousand eye agent or thousandeyes container that is being spun up on the device itself.41:13Let me go back to the SSH portal, I'm gonna log back into both the routers.41:34Twos.41:54Login to the primary router as well.42:16Okay, let's validate, ok, I can validate initially from going to thousand monitoring.42:27I don't see any other agents present like this is on our primary router, right? And ideally I should see a test name that goes through. Let's see if it.42:48Okay, it went through correctly let's see on the thousand and on this devices.43:04So I see the thousand eye thousand eyes agent configuration at least is present on the device. It went through that process. Let's see if the container is up and running.43:33Okay, the state is running.43:50Profile names are running, ok.44:10It's going through ok agent is in checking in so I don't see any errors here. Ideally, in previous scenario when we had, as shown before right on her presentation, if we had any DNS issues or.44:16Not issues we will see some kind of errors present in this.44:34So let's see on the test as well on the agent side ok.44:40I see one out of two agents, so this will take some time to come up, right? But we can go through the initial deployed agents. You will walk us through some of that information, right? And how the test that we see.45:14That are also that can be built here and also brought up here. I think this particular test right which was created is from our current current.45:30Yeah, current deployment, but ideally it should go through, right? It may take some time. As we can see that agent is basically going through and is present on the Mexico router.45:47Oh, was I looking at a different let's see. Sorry, I was looking at a different router. Let me take a look at the primary or secondary router as well where we went through that particular process.46:05I will type over there.46:40Okay, yeah on our secondary routers also I can see the configuration. Let's look at if the agent has come up. Sometimes this does take a little time to come up fully so let's see.46:45Okay, it is in running state. Yeah, so in this scenario also, as we can see there is NO errors that are seen, so it may take some time to fully sync up and show up. In addition to that, right, Asherita had shown, there are.47:12Some additional commands like in scenario in case of me seeing any errors, right? And we wanted troubleshoot, we had put in some shown some command rate. So we can take take a look at what exactly is going on with that particular thousand.47:32From a thousand eyes container, right? Here, here are the commands which can be used to.47:52Get into root of it and then look at, look at the config file and also tail some of the files which show what exactly is going on, right?48:02So this gives us information about the agent config itself and there is another command or another file that we can tell to look at what exactly is going.48:20On with that particular agent. So this is the part for it and if we are running into any particular errors, right? Let's say DNS errors the.48:37The API call is not being made, you would see that pop up here. Let's check back in here. I'm gonna just refresh this.49:00Yeah, it may take some time so we can wait. I'll I'll hand it over to go over the thousand eyes piece of this, right? But from the V manage itself, as you can see, you cannot create any additional tests, right? You cannot create any additional.49:31Steps when when you are going through the workflow, right? Whatever tests that you create would pop up here.49:50Right? But other than that, it is only for monitoring purpose. You can see what, what agents that we have deployed, what device it is deployed to, and that is it. For any making any additional test, you basically have to go back to.49:58Our thousand eyes, right? Where you can create test right and look at agent settings and all of that information. Alright, I'll hand it over to go over the thousand eyes piece.50:20And some of this test we have.50:40Ran some of this tests right to see the underlay path and everything so I'll hand it over to. Awesome. Thank you so much for and for the wonderful presentation. Let me go ahead and share my screen.50:43Okay. Are you able to see my thousandeyes browser? Yes, you can see it. Awesome. Thank you so much. All right, so as we've seen so far, we've looked at how thousandeyes can be integrated with SD WAN. We've seen how to onboard.51:00The agent into the SD WAN router and how you can get started with one of the initial tests from there, right?51:20This demo is to show you how thousandeyes looks like, you know, help you get familiarized with it, get comfortable with it so that you are able to create your own tests, look at the data and make sure that it is useful to you, right? So as you can see, this is how the thousandeyes UI looks like once we log in, right? So you would go into app.51:29Enter your email address and password.51:50And you would be able to see, your organization that you logged into, right? So in the top right corner, you'd be able to see those details, which organization you belong to. This would be your customer organization name, and you could create multiple account groups for different verticals within your organization.51:53Right, so I have all these account groups listed over here so you would see something similar for your own account group and you would see which region do you belong to, right? So you can set your theme as well, but apart from that, you can look at your notifications if at all there is any test recommendations, if at all there is a.52:10Any issues with the existing enterprise agents, you would see that.52:30Right so that you can immediately take a look at what's going on so that you don't miss any important data when an issue happens, right? In addition to that, there is also this wonderful feature, the AI assistant, right? So for the test that you've created in thousandeyes, for the agents that you already have in place, right? So you can.52:34Look at the data either by going into the views or you can also work with the AI assistant, right? So if you have a test running towards the Slack application, right? So you can quickly ask what is going on with my Slack application, you know, what happened at this certain point of time, right? So, what was the latency.52:53See your last about, right? And if at all there were any issues, you know, you would be able to see the assistant respond to you, right? So these are a sample of questions, right? So we can ask something like troubleshooting an application, what are the latest issues so it would go into your alert list and see what happened.53:14Based on the thresholds that you've set, any agents that are requiring, so these are a quick, you know, few examples for you to get started. So I would suggest that you use them. And along with that, you also have the thousand integration, right? So you, what you can do is using OAuth, you can set up a connector, right? With.53:32Thousand eyes, and you can do that either from cloud or cursor.53:52And what that would do is it would connect with thousand eyes acting as the MCP server and you can ask your questions even without logging into the thousandeyes directly, you know, from your cursor client or cloud client. So that is a few things I wanted to mention, but going into the dashboard itself, right? So.53:56Where it takes you upon logging in is the thousand eyes built in dashboard, it will by default give you the status of your agents, any alerts that were seen. You can set the timeline, right? Whether you want it to be as fixed time interval, you know, for a certain date or you can also set relative time interval.54:14Whether the last 1 h until the last 60 days, right? And then you can activate that.54:34So you'd be able to see everything that happened within that time frame, right? There is also an option of creating snapshots, right? So this is very useful because by default you get a data retention of 31 days for your enterprise agent data.54:40And around 90 days for your endpoint experience data, right? So if you want to save something for later, you know, that you want to keep coming back to you can save a snapshot and give it a time frame until which you don't want it to be deleted, you can create that.54:57And you can share it with the people, right? E.g., if there is certain issue within the dashboard that you want others, you know, who don't have access to your dashboard to look at, you can immediately save that snapshot and share it with them, right? And you can also.55:12Generate a report, right? From this dashboard, you can download it as a PDF, you know, if at all there is any metrics, you know, in there, if you want to generate a report, you can do that in either PDF or CSV format, right? So this is the default dashboard, but just for the sake of an example, I would like to show you a custom dashboard, right? So this one was built for.55:28You know, particularly for end user help desk targeting endpoint experience data, right? So we have some agents deployed on endpoint agents. So here in this case I just have one endpoint agent deployed in my own Mac, right? And I have all these widgets created for myself so that I can immediately come into.55:48Here see which you know if if I had more devices I'd be able to see which one is running into a memory issue.56:08You know which end user experience is the lowest you know between all the domains that I'm interested in, right? I can look at the worst tent tests, you know, based upon, you know, their timing, right? There is also loss latency, you know, signal quality, all those metrics. You can add more here.56:14You know, there's a variety of widgets that you can add, right? You get it in different formats, group bars, pie charts, you can get color grids, so there is many ways that you can represent the data, right? And once you select that, you also have.56:34A variety of data that you can focus on, right? Be it from your endpoint experience, be it from your, you know, end enterprise and cloud agents, right? If you have cloud insights configured, you can use that. If you have alerts that you want to focus on, you can put them in your dashboard. So the idea is.56:51As you create your dashboard so that it can immediately, you know, use it as your ATM dashboard once you log in, see what the status is.57:11Now see what what is going on and get a feel of your environment. Now going into the enterprise agents, right? Because that's what we were able to deploy on our router. So this is the menu, you know, as you can see we are in the dashboard section right now, but if you go into event detection.57:20Would be able to see the list of events, whether there were any alerts that were created, you can go into the alerts to look at that. But what is of interest, you know, for today's call is our network and app synthetics. So here you would see everything relating to enterprise and cloud agents, right? So once you create.57:38Once you instrument your thousand agent on your router.57:59You would be able to see them show up in the agent settings, right? Similarly, you know, once the agent is present, you can create your test by navigating into the test settings. And once the tests start collecting data, you would be able to get into views and see, you know, what is the data, right? You can be able to see the views over a period of time.58:03So now that we've imported agents or instrumented agents in your router, you can go into the agent settings and here you would see the list of agents that you already have, right? As of now I have a virtual agent sitting on a VM.58:23And the raspberry Pi and this is one 9300 agent that is the right as of now offline, but you'll be able to see the list of agents, their status, whether they're online, offline, what is their test utilization like, you know, how much bandwidth are they consuming, you'll be able to see those details and by clicking on the agent, you'll have.58:40More details on on the agent, right? You can set the territory country. This is all picked up by default, but you can change it as needed.59:00Right, how many tests are configured, so on and so forth, you know, whether there is any chromium package and this is essential, the browser bot is essential for you to run the layer seven tests right the page load and the transaction tests right so there is also the advanced settings you can you know set your target for your test.59:08You can set your browser board settings. You can look into your information like the IP addresses, the operating system, you know, that your agent is running on the version, and you can also get some system information network interfaces and deeply DNS configuration.59:29So once the agent is in place, similarly you have the cloud tab, you have the global configuration if at all you had any proxy settings that you need to configure for your enterprise agent, you can be able to look at that. But yeah, once you have the agent in place, what is of your interest is to create your tests, right? Because that is where you'd be getting all your.59:48Data from, right? So here I can see the list of tests that I have already created, I can classify them by type, I can even filter them.01:00:09So I want to look at, you know, certain tests, I can also attach tags to, you know, certain type of tests if I'm targeting like here e.g. health overview, I can just select that tag, I can filter them by tag and you know based on that I can.01:00:16I can be able to look at all the tests that are relevant in that time, right? And, now creating tests, right? So once you have the agent in place, the next step would be to obviously create your test, right? So you have a plethora of options over there. You can run an agent to server test an agent to agent test. If you are.01:00:33Getting between branch to DC you can place two different agents and you know run an agent to agent test between both of them. There is also HTTP server test, so you have tests at each of the layers and you can run them you know from thousandeyes. You have.01:00:53A lot of settings, you know, customizations that you can perform, right? But, but by default, you know, e.g., this is a HTTP server test, you would provide your URL here, name your test, right? We would suggest that you name it according to your objective, right? Whether you're troubleshooting a certain thing or, you know.01:01:09It just helps you easily identify them when you look at the list of tests that you have. And so there's the frequency. You want to make sure that you set the right frequency for your test so that you have the right amount of data.01:01:29So remember that your unit utilization or your licenses utilization consumption will depend upon this frequency as well. So it is important that you do not cross your your unit consumption. So there is also a nice calculator that is available. You can use that.01:01:43If at all you want to calculate how many units you need for a test, you can, you know, go into manage account settings and usage and billing. Here you can see this hyperlink, right? Calculate the units you need, right? And here, you can be able to enter what.01:02:04Kind of tests you want to run, what is the frequency, how often you want it to run, whether you want the test to run from a cloud agent or an enterprise agent. And based on that, it will provide you how many units you will need for that test, right? As you can see, these are some of the tests that I have already created, so it is giving me.01:02:23Me up look into that, but I can add more rows here.01:02:43And I can select the type of test I want to run, e.g. agent to agent, right? Because the agent will be run from both directions, so you can set that as well. You can use both directions or source target or target to source.01:02:48Right? And once you do that, you can increase the number of enterprise agents or cloud agents that you would like to use, right? And based on that, you would see your monthly usage getting reflected over here, right? So that you can plan well so that you don't exceed your utilization or.01:03:04The units that are available to you.01:03:23So that is about a thousand calculator. It's a very helpful tool. I suggest you all use it. But coming back into the test creation, right? So you would provide the URL to the target, you know, in this case for the server test name it, set the frequency, select your agents.01:03:26So when you click on select your agents, you'll be able to see, you know, by default it goes to the enterprise agents. You can collapse, you can expand them all, see what are all the agents that are available for you to run the test from, and you can also select cloud agents if at all you want to use an external cloud agent for benchmarking purposes.01:03:45Right, so you can also use a cloud agent for that. You can set them you can select them according to the provider, the location, right? So you have a lot of options. So we have cloud agents available in our like 400 cities across the globe and you are you can readily consume them.01:04:05For your tests, right? So once the agents are selected you also have the option of selecting the alerts, right? So by default we have a few alert rules that are in place such as the default network alert rule, right? So the this looks into the last latency and jitter, right?01:04:25But all it exceeds a certain value, you know, it will trigger trigger an alert, you can take a look into them by going into manage and alert rules, right? And here you would see.01:04:44You know, what are the rules that you have right now and you can create more on top of them, right? So, I want to show you the default rules, right? So e.g., this one is for a default network alert alert rule that works on agent to server test, right? And.01:04:55It triggers an alert if at all packet loss is greater than 25 %. So it may not be suitable for you. So in that case you can create your own alert rule and you can set your own values right and you can set your own conditions as well. So there's a lot of customization that is available for you, you know, with these alerts.01:05:15And there is also in depth settings that are available, you know, we can choose to have bandwidth measured or not, right? Based on this as well, your test consumption will vary. You can choose to have MTU or not.01:05:36You can set your transmission rate, you can select your protocol by default, it is set to TCP because, you know, we have rate limiting usually out in the internet for ICMP, so you can set select your own protocol, you can set the number of path traces if at all there are more number of paths.01:05:52Towards you know your target and you want to ensure that every path is being detected, you can select the number of pack traces, right? You can increase them or decrease them according to your preference, right? You can select the probing mode. In TCP we have the selective acknowledgement you know option or the force in option.01:06:09So you can select between all those options, whether you want to do the back trace within the session or outside of the session, you can select that. If there is any proxy, you would be able to, you know, enter those settings over here. The TLS options, if you want to be specific about your TLS, if you want to make sure that it.01:06:28Is running version one.three, you can check that you can verify the SSL certificate.01:06:48And you can add your own client certificate to avoid any SSL errors, right? There is also since this is a HTTP server test, we have also have a custom settings available for that test, right? The timeout, the target response.01:06:54Whether, you know, what is the this desired status code? Sometimes it may not be you know HTTP ok, right? You you might desiring, you might be desiring some other response code so you can select that over here, right? So you have a plethora of options, you know, for whichever test that you want to create, right?01:07:10In addition to agent to server HTTP server and agent to agent test, you also have the the RTP stream or the SIP server performance which allows you to look at the voice.01:07:29And the video quality, right? You can be able to review those information as well with even within the agent to agent test, you have the option of selecting UDP protocol, so you can switch between protocols as per your need and you can set your DSCP values if at all there is any QoS in place.01:07:41You want to, you know, check whether.01:08:01You know the the quality is being ensured, you can set your own DSCP value and when the thousand eyes performs those tests it will make sure that these markings are included in the header, right? So there's a lot of customizations that you can do and once the tests are created, you, you'll be able to.01:08:04See them in this list?01:08:24Classified according to the type, the target and you know there are any alerts whether it's disabled. So you can enable them from here or, you know, disable them as well, you know, from here. And once the test is created, once you have enough data, you can be able to go into views directly from this page, right? You can just click on this icon.01:08:25That is beside the name and it will take you to the views of the test.01:08:45And as you can see, I'm right now in the views page, right? And here I would be able to see all the tests that I have which are collecting data. So this one is disabled, so I see that marked over here, but I can be able to filter them according to the test type. If I want to only focus on agent to agent test I can look at that.01:08:53Right, I can select my own test site over here if I only want to target certain agents.01:09:13I can select that from here, right? So I can select enterprise agents and if I only want to target a specific agent, I can do that from here, right? And you can group them by test type or tags. So as I said, you can assign tags to your test.01:09:18And once you do that, you know, you can look at multiple tests that are tagged with the same name, right? So you can group them according to that. So for the sake of example, I'll be looking at this specific agent to server test, right? The, which is running towards cisco.com.01:09:35Right, so as you can see, I have the option, so by default, what you see is a view of the average, you know, between both the agents from which the test is running from, right? But I can select a specific agent if I want to purely focus on that one and it will give me only.01:09:55The metrics relating pertaining to that agent, right? So you can select the agents, you can select the targets as well, right? If you had multiple agent to server tests you can add them, right? You can add them to the selected tests and you can compare the metrics.01:10:14So here is how you would, you know, see it in your own thousand, right? So once you deploy the test, you would see a layer by layer view of all the metrics, right? Since this is an agent to server test, we have a metrics that are relate the network layer metrics, right? And when you click on the dropdown here in the metric drop.01:10:32Down. You'd be able to see what are all the metrics that are available to you. So you have loss, latency jitter.01:10:52And you can switch between each of these metrics, and you can also compare them. E.g., you wanted to see, you know, how is the latency like at a certain point of time? You can be able to select, you know, that view as well here and you can compare them both.01:10:57In one in one page. And you can switch between different times, right? As I said, you have, you can go back up to 31 days but if you want to target a specific time period during when you had certain issues.01:11:13So you can use this scroll bar over here and you can select a time period of your choice and you can dig down deeper into what was going on at that point of time, what led to the problem that you're seeing, right? And if at all.01:11:28This device or the network played a role in that problem. You would be able to see all of those details. Now, along with the, you know, metrics and the, you know, the layers, right? You also have the patch visualization, you know, which is most sought after by our customers, right? You you want to know where.01:11:45Is the failure happening?01:12:05Along the path rate, you want to have a node by node visualization, a hop by hop visualization until your target so that you are able to easily target where is the loss and where is your latency, right? So you would be easily be able to see from the path visualization if at all a certain node is contributing to the loss or.01:12:06If at all a link is contributing to your latency, you would be able to see from here, right? So you can hover over your enterprise agent from where your test is running to have more details, right? So what was the last like at this point of time? So you can select a specific period, you know, see why did you have a such high latency?01:12:26At that point of time and see what were the other metrics, right? You can also have a trace route style output. You can click on this and you would see the trace route representation of your you know path until the target.01:12:46Hey Sai, sorry to interrupt, but while you're on this page, I also wanted to see if you can quickly shout out the explain selection option. I know some of these AI features are likely coming into play with, you know, integration between cloud control and thousand eyes, but.01:13:02We're aware that every day there's something new coming out with Cisco, the dashboard is evolving as we speak, so sometimes it maybe a bit confusing to us, you know, I I'm I'm curious, right? Like what exactly is this dashboard showing to us so that I my this is my personal favorite, when you click on explain selection, it's like it's already building a prompt for you and it's.01:13:18Gonna tell you what it is that you're looking on the dashboards. Maybe we can quickly shout that out too.01:13:39So that's a great mention. Thank you so much for that. So as said, you can immediately use this option, the explain selection option as well. So as as of now I had this specific time frame selected on 21st of August at you know 09:15, right? So one when I selected that and you know.01:13:43When I click on this option, it would automatically thousand eyes would automatically look into, you know, what happened in that period for this test, for this specific test in the frame, right? And it will be able to tell us, you know, whether there were any issues during that period, right? So here as you can see once I selected, you know, it.01:14:03Automatically created this prompt for me with the timestamps you know the when when the test ran and also the, you know, its observations, right? So it was able to see that we ran a test from this specific agent and it is fully within the baseline.01:14:23Latency of 1.1 milliseconds and 0 % packet loss, right? So if at all you had an anomaly scenario where you had a high loss, right? Here I don't have such scenario in my environment, but if you have such scenario, you can select that specific instance and you can click on the.01:14:40Sales selection and.01:15:00It will be able to show you, you know, what went wrong during that time. It will be able to correlate not just the latency and loss metrics, but also if there were any outages with the service that you are targeting within this test here in in our case cisco.com, right? So it's a very useful tool as I said.01:15:01And I would suggest all of you use it.01:15:21Right, so that's about the, you know, path path visualization, right? That's about the views of your test, right? Now similarly, you have a same sort of, you know, options for your endpoint agents, right? So once.01:15:26You deploy your agents, you would be able to see them here in agent settings, right? So you can add a new agent, either windows, Mac or android. So it's it's very straightforward. You can get your endpoint agents in place so that you have the perspective of both your end user.01:15:42Devices as well as, your enterprise agent devices, right? So once you have your endpoint agents in place, you can create your endpoint agent tests, right? So you have the option of adding your own application or you have the option of using one of the templates here.01:16:01So these are one of the most commonly used applications so you can directly use them, but you can also create your own custom application. You can give it the application name and you have the option to select your tests, right? So you, you can create either the network or the HTTP server test.01:16:20So the test creation is pretty similar, you know, the configuration is pretty similar to what we've seen on the enterprise agent side, you would set your target, which agents you want the test to run from, whether you want to prioritize the test for certain agents or whether you want it to.01:16:39Use the typical round round robin form of scheduling. You can also set your frequency. Yeah, you can set your own frequency for the test and the best part is within endpoint agent devices, the frequency doesn't matter when it comes to your license consumption rate by default, every endpoint agent consumes one.01:16:55Endpoint agent license and you can run up to ten tests right on that endpoint agent and you can set any frequency.01:17:16That you prefer. And once you have the tests in place, you can be able to go into views, right? And have a view into, have a look into the data that is being collected. In endpoint agents we have the option of running real user tests as well.01:17:25So if there are domains that that that you are interested in, you can create, you know, a test for them, right? So e.g., here in my case, I am interested in the performance, you know, whenever my users navigate to any of these domains, right? So I have entered all of these over here, so.01:17:43If at all my endpoint agents that I have in place, navigate to any of these domains, their experience would be captured automatically and you would be able to see them in the views.01:18:03And along with that, you have the scheduled test views from the test that you created. You can switch between tests similarly, right? You know, as you, as you've seen for enterprise agents, you can switch between the endpoint agent tests and you can review their metrics.01:18:16So this one is a HTTP server test, so I have metrics such as availability response time and throughput. I can, you know, similarly I can use the the time window here to go back into certain timeframe. I also have the underlying layer in the network layer, so I I can be able to correlate and come.01:18:35Where if at all the network contributed to any of the bad user experience.01:18:55And here similarly, you know, from the endpoint agent perspective, you'll get the path visualization. So as you can see, it's going to my gateway, my provider and then to the target, right? It's the path which is taken. In the path visualization, you have these filters available for you. You can group them.01:19:02You know, by agent you can group your agents by network, you know, if you if you had a many number of agents, you can group them by network or you can look at them individually by specific agent. You can highlight, you know, the notes that are contributing to a loss. You can select the ones that are.01:19:20You know, e.g., facing more than 40 % forwarding you can you can select that you can make those settings over here. If at all you want to focus on links that are you know contributing to the delay you can, you know, customize those settings over here.01:19:38And there is also this option that you can expand on the number of hops, right? Either from the source side or from the target side. So it just gives you more granularity, right? You more more you know ability to customize your outputs, right?01:19:55So I think that's all I had on my side. So we looked into the enterprise agents, we looked into the endpoint agents, we looked at the dashboards, how you can create your alerts, right? And set set set your thresholds for your alerts. I know it was a lot of content, it maybe overwhelming in the.01:20:151st go but you know feel free to reach out to us if you have a specific use case, we would love to help you, you know, get on board, create your tests and, you know, realize the value from it.01:20:35But that's it from my side, so back to you to share. Thank you, Sai, thank you so much for that detailed walkthrough. All right folks, we're almost at the end of our session here. We have five more minutes. If you have any last questions or concerns, please feel free to drop them in the chat.01:20:47And if you don't have any questions at the moment, we still want to appreciate, you know, the time you've taken to come join us to learn about thousandeyes, to learn about how SD WAN can benefit from integration with thousand eyes. But yes, you know how to reach out to us. If you don't have any other questions or concerns, you're welcome to drop off.01:21:07Off, you will be provided with a survey once you leave the session, so please do fill that survey out. Let us know what's working and what's not working for you so we can keep improving and make these sessions more meaningful for you. We'll be here for a couple more minutes to see if you have any other last minute questions or concerns, but otherwise, thank you so much for joining today and hope you have a good.01:21:27The Rest of the day.01:21:47

About this Video

Author : Cisco Customer Success

Uploaded : August 27, 2026

NetworkingCatalyst SD-WAN
AI summary icon

AI summary

Explore how Cisco Catalyst SD-WAN integrates with Cisco ThousandEyes to extend visibility beyond the overlay and accelerate root-cause analysis. The recording outlines challenges with traditional WAN monitoring and shows how end-to-end visibility, ISP path intelligence, and Application Experience Monitoring enable rapid diagnostics. It walks through agent types (Cloud Agents, Enterprise Agents, Endpoint Agents), deployment choices (Service VPN or Transport VPN), prerequisites (routing, DNS, NAT, firewall ports), and the vManage Workflow Library steps to onboard Enterprise Agents. A live demo then configures HTTP, DNS, BGP, and Agent-to-Server or Agent-to-Agent tests, reviews dashboards with KPIs, Path Visualization, and Internet Insights, and uses AI features such as Explain Selection to interpret anomalies. The session closes with monitoring from vManage and deep troubleshooting on the router and in ThousandEyes.

  • Explains a four-step workflow to deploy Enterprise Agents from vManage using Config Groups and Service VPN or Transport VPN options.
  • Reduces mean time to resolution with end-to-end Path Visualization, ISP path intelligence, Internet Insights, and practical router troubleshooting commands.
  • Operationalizes monitoring by creating tests and alerts, planning license units, and using AI Assistant and Explain Selection to speed analysis.