{"id":2458,"date":"2024-10-06T23:23:36","date_gmt":"2024-10-06T21:23:36","guid":{"rendered":"http:\/\/192.168.1.213:8088\/?p=2458"},"modified":"2024-10-10T01:54:40","modified_gmt":"2024-10-09T23:54:40","slug":"cisco-router-meet-proactive-monitoring-deploying-thousandeyes-on-catalyst-8000v","status":"publish","type":"post","link":"http:\/\/192.168.1.213:8088\/cisco-router-meet-proactive-monitoring-deploying-thousandeyes-on-catalyst-8000v\/","title":{"rendered":"Cisco Router, Meet Proactive Monitoring: Deploying ThousandEyes on Catalyst 8000V"},"content":{"rendered":"\t\t
In this post, we\u2019re exploring the world of application hosting on Catalyst routers<\/strong>, specifically focusing on deploying ThousandEyes<\/strong> on a Catalyst 8000v<\/strong> router in a Cisco Modeling Labs (CML)<\/strong> environment.<\/p> Wait a minute\u2026 ThousandEyes on a Catalyst 8000v?!<\/strong> Yes, you read that right! For all the Cisco employees and Business Unit folks reading this: I know<\/em> it\u2019s not officially supported, but as a showcase, it works just fine.<\/strong><\/span> Let\u2019s face it, not everyone has access to physical Catalyst 8k routers lying around for testing purposes, so CML is a great alternative.<\/p> I decided to write this article after some recent discussions with one of my customers, who is exploring the possibility of deploying the ThousandEyes Agent<\/strong> on their routers. This deployment serves as a practical example of how Catalyst routers can be leveraged beyond traditional routing, giving edge compute capabilities to monitor network performance right where it matters most.<\/p> Let\u2019s dive in! \ud83d\ude80<\/p>\t\t\t\t\t\t<\/div>\n\t\t\t\t<\/div>\n\t\t\t\t\t<\/div>\n\t\t<\/div>\n\t\t\t\t I wish my lab would look like this \ud83d\ude1c<\/p>\t\t\t\t\t\t<\/div>\n\t\t\t\t<\/div>\n\t\t\t\t\t<\/div>\n\t\t<\/div>\n\t\t\t\t\t<\/div>\n\t\t<\/section>\n\t\t\t\t Here are five reasons<\/strong> why deploying a ThousandEyes agent<\/strong> on a router, whether in a branch office or a data center, makes a lot of sense, especially when considering the impact of network changes and the need for pre-and post-checks<\/strong><\/span>, which was a topic that has been heavily discussed with my client:<\/p>\n Real-Time Network Visibility at Critical Points<\/strong>:<\/p>\n End-to-End Path Monitoring<\/strong>:<\/p>\n Proactive Problem Detection<\/strong>:<\/p>\n Service Assurance and Application Performance<\/strong>:<\/p>\n Impact Analysis of Network Changes<\/strong>:<\/p>\n \u00a0<\/p>\n In summary, deploying a ThousandEyes agent on routers gives you end-to-end network visibility<\/strong>, proactive monitoring<\/strong>, and post-change validation<\/strong>, helping you maintain a stable and reliable network environment while making configuration changes with confidence. So can safely wear the Thousandeyes T-shirt with a slogan that says: “Go ahead blame the network!” \ud83d\ude05<\/p>\n Keep in mind that Catalyst 8k is not the only platform where the Thousandeyes client can be deployed. The client is also supported on certain Nexus 9k, ASR, ISR 4k and Catalyst 9k devices. Guess what, not on all models as there are some requirements that I will cover later during the post.<\/p>\t\t\t\t\t\t<\/div>\n\t\t\t\t<\/div>\n\t\t\t\t In this\u00a0Cisco Modeling Labs (CML)<\/strong>\u00a0topology, a multi-location network is being simulated across\u00a0three key locations<\/strong>:\u00a0London<\/strong>,\u00a0New York<\/strong>, and\u00a0Frankfurt<\/strong>. Each location is configured with its own\u00a0Edge<\/strong>\u00a0and\u00a0Core<\/strong>\u00a0routers, connected to form a cohesive network.<\/p> Here’s a breakdown of the configuration:<\/p> 1. Autonomous Systems (AS Numbers):<\/strong><\/p> \u00a0<\/p>\t\t\t\t\t\t<\/div>\n\t\t\t\t<\/div>\n\t\t\t\t\t<\/div>\n\t\t<\/div>\n\t\t\t\t\t<\/div>\n\t\t<\/section>\n\t\t\t\t 2. Core and Edge Routers:<\/strong><\/p> \u00a0<\/strong><\/p> 3. Clients:<\/strong><\/p> \u00a0<\/strong><\/p> 4. Unmanaged Switch:<\/strong><\/p> My use case: ThousandEyes Deployment<\/strong><\/p> The topology shows the\u00a0<\/span>Core Routers<\/span>\u00a0<\/span>from the three locations connected, forming<\/span>\u00a0<\/span>inter-AS connections<\/span>\u00a0<\/span>that enable communication between<\/span>\u00a0<\/span>London<\/span>,<\/span>\u00a0<\/span>New York<\/span>, and<\/span>\u00a0<\/span>Frankfurt<\/span>. This simulates a geographically distributed network, where traffic can flow between these major hubs through BGP.<\/span><\/p> This network setup could be used for deploying and testing ThousandEyes<\/strong> agents at each edge location (London, New York, Frankfurt). These agents will monitor network performance, latency, packet loss, and other metrics between the various sites, as well as traffic to services like AWS and WebEx.<\/p> This simulation allows you to test how the network performs under different conditions, assess routing between locations, and monitor network behavior using tools like ThousandEyes<\/strong> for pre<\/strong> and post-change validation<\/strong>.<\/p><\/div>\t\t\t\t\t\t<\/div>\n\t\t\t\t<\/div>\n\t\t\t\t Here is an example of the BGP config, which is very basic:<\/p>\t\t\t\t\t\t<\/div>\n\t\t\t\t<\/div>\n\t\t\t\t Core Router:<\/strong><\/p>\t\t\t\t\t\t<\/div>\n\t\t\t\t<\/div>\n\t\t\t\t Edge Router:<\/strong><\/p>\t\t\t\t\t\t<\/div>\n\t\t\t\t<\/div>\n\t\t\t\t In my previous article, I explained what an enterprise agent is. If you don’t know, make sure to check that out<\/a>.<\/p> Deploying an enterprise agent on the device itself is very easy due to the Why Thousandeyes on a network device?<\/h5>\t\t<\/div>\n\t\t\t\t<\/div>\n\t\t\t\t
\n
\n
\n
\n
\n
\n
CML Lab setup<\/h5>\t\t<\/div>\n\t\t\t\t<\/div>\n\t\t\t\t
\n\t\t\t\t
\n\t\t\t\t\t
\n\t\t\t\t
\n\t\t\t\t\t
Lets deploy the enterprise agent on Catalyst 8000V<\/h5>\t\t<\/div>\n\t\t\t\t<\/div>\n\t\t\t\t