Introduction
This document describes how to install ThousandEyes Enterprise Agent on Cisco routers running in SD-WAN mode that are managed by vManage.
Prerequisites:
To review the supported Cisco routers and hardware requirements, see the Support Matrix.
Part I: Prepare the TE enterprise image
- Log in to Thousandeyes account at Cisco Thousandeyes Page: https://app.thousandeyes.com
- Navigate to Cloud & Enterprise Agents > Agent Settings, then click Add New Enterprise Agent.
![Part I Step 2 (1 of 2).png Part I Step 2 (1 of 2).png](https://community.cisco.com/t5/image/serverpage/image-id/202798iDE42ECD2E49E1D17/image-size/large?v=v2&px=999)
- Select the Cisco Application Hosting tab, then copy and save your account group token.
![Part I step 2 (2 of 2).png Part I step 2 (2 of 2).png](https://community.cisco.com/t5/image/serverpage/image-id/202799iF36BED3C0ED46E3F/image-size/large?v=v2&px=999)
- Input the network related information on that page, then click Download - TAR. A file will be downloaded to your local disk, named something like 'thousandeyes-enterprise-agent-4.4.3.cisco.tar'.
Part II: Upload the TE enterprise image to the router
- Log into the vManage Portal and Navigate to Maintenance > Software Repository
![Part II Step 1.png Part II Step 1.png](https://community.cisco.com/t5/image/serverpage/image-id/202800i3CEDDF4FF6A9BFED/image-size/large?v=v2&px=999)
- Click Virtual Image and select Upload Virtual Image > vManage
![Part II Step 2.png Part II Step 2.png](https://community.cisco.com/t5/image/serverpage/image-id/202801i3933F44DD74AC416/image-size/large?v=v2&px=999)
- Upload the Thousandeyes installation image *.tar file from Part I, step 3 to vManage.
![Part II Step 3 (1 of 2).png Part II Step 3 (1 of 2).png](https://community.cisco.com/t5/image/serverpage/image-id/202802i4D5941ED7AA95BD7/image-size/large?v=v2&px=999)
- Once the image is uploaded, the filename should be present in the Virtual Image list.
![Part II Step 3 (2 of 2).png Part II Step 3 (2 of 2).png](https://community.cisco.com/t5/image/serverpage/image-id/202803i4093B4CAB50518C3/image-size/large?v=v2&px=999)
- To confirm the virtual image is ready, click Show Info to review and verify the virtual image's vnfProperties as below
![Part II step 4.png Part II step 4.png](https://community.cisco.com/t5/image/serverpage/image-id/202804i39A7645C478BDFE6/image-size/large?v=v2&px=999)
Part III: Create the feature template
- Navigate to Configuration > Templates.
- Select Feature > Create Template > Add Template.
![Part III Step 2.png Part III Step 2.png](https://community.cisco.com/t5/image/serverpage/image-id/202806i2F89E967D70906A3/image-size/large?v=v2&px=999)
-
Under Select Device, search for the device model (for example, ISR4431) that you wish to deploy an agent to. See the Support Matrix for compatible routers.
- Select ThousandEyes Agent template from under Other Templates.
![Part III Step 4.png Part III Step 4.png](https://community.cisco.com/t5/image/serverpage/image-id/202807i1ABFD5DB084A81CD/image-size/large?v=v2&px=999)
- Specify the template name and description:
![Part III Step 5 copy.png Part III Step 5 copy.png](https://community.cisco.com/t5/image/serverpage/image-id/202810iFB0C735B1F9C2ADE/image-size/large?v=v2&px=999)
- Under Basic Configuration, enter the relevant Account Group Token. If you would like the agent traffic to follow the default management route, please select Default. However, SD-WAN mode offers the options (Global, Device Specific) to send agent traffic to pre-configured VPN tunnels, instead of following the default management route
![Part III Step 6.png Part III Step 6.png](https://community.cisco.com/t5/image/serverpage/image-id/202811i16CB215327FBD1CF/image-size/large?v=v2&px=999)
- Under Advanced, configure the Name Server, Hostname, and Web Proxy.
![Part III Step 7.png Part III Step 7.png](https://community.cisco.com/t5/image/serverpage/image-id/202812iB8357F16714DD737/image-size/large?v=v2&px=999)
- Important Note: This proxy configuration doesn't support any authentication methods. If you need to configure a proxy that requires basic or PAC authentication, you will need to use the CLI deployment option.
- Click Save to save the template.
Part IV: Attach the feature template to the Device template
- Navigate to Configuration > Template, from the device template, choose the template that you want to integrate with ThousandEyes. Then click the three dots icon and select Edit.
![Part IV Step 1.png Part IV Step 1.png](https://community.cisco.com/t5/image/serverpage/image-id/202813i5C4193814F718B72/image-size/large?v=v2&px=999)
- Navigate to Additional Templates, open the ThousandEyes Agent drop-down menu, and select the template created in Part III.
![Part IV Step 2.png Part IV Step 2.png](https://community.cisco.com/t5/image/serverpage/image-id/202814i30599A9701C95782/image-size/large?v=v2&px=999)
- Click Update to save the changes.
Part V: Attach the Device template to a Device
- Once updated, you will be returned to Configuration > Templates and the templates list. Click the three dots icon and select Attach Devices.
![Part V Step 1.png Part V Step 1.png](https://community.cisco.com/t5/image/serverpage/image-id/202815i93500271416A2286/image-size/large?v=v2&px=999)
- Select the desired device(s) from the Available Devices list, then click Attach. The list will only contain vEdge devices that are the same model as the template.
![Part V Step 2.png Part V Step 2.png](https://community.cisco.com/t5/image/serverpage/image-id/202816iF63770CEC12880CB/image-size/large?v=v2&px=999)
Part VI: Verify configuration
Once the template is attached to the desired devices, you can verify it from the Running Configuration view.
- Navigate to Configuration > Devices.
- Click the three dots icon beside the desired device and select Running Configuration.
![Part VI Step 2.png Part VI Step 2.png](https://community.cisco.com/t5/image/serverpage/image-id/202817iA57A502C0FB5C910/image-size/large?v=v2&px=999)
- If it’s successful, you should be able to see the configuration information, like the following:
![Part VI Step 3.png Part VI Step 3.png](https://community.cisco.com/t5/image/serverpage/image-id/202818i53D808031E41AB92/image-size/large?v=v2&px=999)
- On the router side, you can run ‘show app-hosting list’ to verify as well.
![Part VI Step 4.png Part VI Step 4.png](https://community.cisco.com/t5/image/serverpage/image-id/202820iE15F20587E2279BF/image-size/large?v=v2&px=999)
-
Log into Thousandeyes portal, navigate to Cloud & Enterprise Agents > Agent Settings, the newly deployed Enterprise agent should show up in the Agent List.![Part VI Step 6 copy.png Part VI Step 6 copy.png](https://community.cisco.com/t5/image/serverpage/image-id/202821iBB28C2A9F0523A19/image-size/large?v=v2&px=999)
Part VII: Agent Management
Agents can be un-deployed by removing the ThousandEyes Agent feature template from the device template. However, vManage cannot disable the running Agents once they are deployed. You will need to use either the web app or the CLI for agent management.
FAQ:
What is the expected NTP behavior for a Catalyst 8000 series deployed Enterprise agent?
The enterprise agent on a Catalyst 8000 series switch uses the host system kernel clock. It also sends packets to pool.ntp.org to determine any clock offset. It does not try to adjust the host or container clock but will adjust measurement timestamps based on the clock offset.
Can the default external NTP source (pool.ntp.org) be changed to a customer's internal NTP source?
No. The agent uses pool.ntp.org to determine clock offset by default; this is currently not configurable.
How do I connect to the agent shell for Cisco agents?
To access the agent shell of a Cisco Enterprise Agent that is actively running, use the following command:
catalyst#app-hosting connect appid {application name} session
Once inside the agent shell, you can refer to the agent log for any further troubleshooting:
# tail /var/log/agent/te-agent.log