{"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
\n\t\t\t\t\t\t
\n\t\t\t\t\t\t
\n\t\t\t\t\t
\n\t\t\t
\n\t\t\t\t\t\t
\n\t\t\t\t
\n\t\t\t\t\t
\n\t\t\t

\n\t\t\t\tTable of Contents\t\t\t<\/h4>\n\t\t\t\t\t\t\t
<\/i><\/div>\n\t\t\t\t
<\/i><\/div>\n\t\t\t\t\t<\/div>\n\t\t
\n\t\t\t
\n\t\t\t\t<\/i>\t\t\t<\/div>\n\t\t<\/div>\n\t\t\t\t<\/div>\n\t\t\t\t<\/div>\n\t\t\t\t
\n\t\t\t\t
\n\t\t\t
Introduction<\/h5>\t\t<\/div>\n\t\t\t\t<\/div>\n\t\t\t\t
\n\t\t\t\t\t\t
\n\t\t\t\t\t
\n\t\t\t
\n\t\t\t\t\t\t
\n\t\t\t\t
\n\t\t\t\t\t\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

\n\t\t\t
\n\t\t\t\t\t\t
\n\t\t\t\t
\n\t\t\t\t\t\t\t\t\t\t\t\t\t\"\"\t\t\t\t\t\t\t\t\t\t\t\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\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

\n\t\t\t\t
\n\t\t\t
Why Thousandeyes on a network device?<\/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\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

    \n
  1. \n

    Real-Time Network Visibility at Critical Points<\/strong>:<\/p>\n