This article details the steps to install the ThousandEyes Virtual Appliance (VA) inside either an Integrated Services Router (ISR) or Aggregation Services Router (ASR), which is able to host KVM-based virtualized services. The VA is a virtual machine containing a pre-installed ThousandEyes Enterprise Agent, which can be quickly imported into a virtualization environment.
Cisco IOS XE 16.1 or higher (or IOS XE 3.17 or higher under the old versioning scheme)
ISR 4000 series router, ASR 1000 series router or ISRv software on a supported hardware platform
Minimum 8 GB RAM (ISR 4000) or 16 GB (ASR 1000)
2GB of free memory per installed Virtual Appliance
Solid-state drive storage (NIM-SSD or MSATA-SSD)
Internet connectivity from the ISR/ASR
In this example we'll install the ThousandEyes VA within an ISR as a virtual service. To assign the VA an IP address, either configure a valid DHCP pool on the router, or use static addressing. In order to connect the VA to the Internet, you need to assign a VirtualPortGroup interface as the default gateway. Make sure the VirtualPortGroup interface IP address is within the same network block as the VA's IP address. We'll use DHCP for the example, and name our example virtual service hitman.
The installation process for a VA consists of three steps:
Installing the Virtual Appliance
Activating the Virtual Appliance
Initializing the Virtual Appliance
Download the ThousandEyes Virtual Appliance for Cisco IOS XE from Cloud & Enterprise Agents > Agent Settings > Agents, using the Add New Agent button.
Copy the file onto the router hard disk via one of the following methods:
Secure Copy Protocol (SCP)
File Transfer Protocol (FTP)
Trivial File Transfer Protocol (TFTP)
USB storage device
Install the VA as a Virtual Service
isr# virtual-service install name hitman package harddisk:teva-cisco.ova
Note: If you see the following error,
Invalid package::Failed to verify virtual service package-def file::Failed to validate the certificate;Package 'te-va.cisco.ova' is 'unsigned', does not match original signing level 'Cisco signed'Aug 11 12:06:11.657: %IOSXE_VMAN-3-MSGINITFAIL: Failed to initialize required Virt-manager resource:VM [hitman]: Install failed, VM unpacking error
then execute the following commands
asr#configure terminalasr(config)#virtual-serviceasr(config-virt-serv-global)#signing level unsigned
Configure a VirtualPortGroup Interface with an IP address from within the same network block (subnet) as that of the ThousandEyes VA. Once the ThousandEyes VA is installed and activated, enter the default gateway for this IP address
isr# config tisr(config)# interface VirtualPortGroup3isr(config-if)# ip address 10.100.152.100 255.255.255.0
Assign a VirtualPortGroup interface as a gateway to virtual-service
isr# config tisr(config)# virtual-service hitmanisr(config)# vnic gateway VirtualPortGroup3
Note: VirtualPortGroupX is an interface on the ISR and must have connectivity to the ThousandEyes Collector (18.104.22.168/24) Note: The VirtualPortGroup's Line Status and Line Protocol will change to "up" only after activating the Virtual Appliance.
At this point, the ThousandEyes VA is installed on the router as a virtual service. You can check the status of the VA as follows:
isr# sh virtual-service listVirtual Service List:Name Status Package Name------------------------------------------hitman Installed teva-cisco.ova
Activate the virtual service
isr# config tisr(config)# virtual-service hitmanisr(config)# activate
The virtual service should now be activated. VirtualPortGroup interface should change its status to up and up
isr# sh virtual-service listVirtual Service List:Name Status Package Name------------------------------------------hitman Activated teva-cisco.ova
isr# sh ip int brief VirtualPortGroup 3Interface IP-Address OK? Method Status ProtocolVirtualPortGroup3 10.100.152.100 YES NVRAM up up
Connect to the VA virtual service via console
virtual-service connect name hitman console
On connecting to the virtual service console, you should see a prompt message similar to one below.
On the first run, the Virtual Appliance tries to acquire an IP address via DHCP. I have configured a DHCP pool on the ISR, pointing the default-router to my VirtualPortGroup Interface and also assigning the internal DNS nameserver. The VitrtualPortGroup 3 interface is assigned an IP address from this subnet (10.100.152.100)
isr(config)# ip dhcp pool ISR-POOLisr(dhcp-config)# network 10.100.152.0 255.255.255.0isr(dhcp-config)# default-router 10.100.152.100isr(dhcp-config)# dns-server 10.100.100.102
If you want to assign a static IP address, press N and after the hostname screen, select "Static configuration parameters" using down arrow key and space bar.
Note: To exit the console - press "CTRL+C" 3 times.
Once the Network Settings are applied, access ThousandEyes Virtual Appliance interface through the URL in that screen and login with the credentials shown in the virtual console.
Upon login, you will be prompted to change the Web Interface password.
Obtain your Account Group Token, navigate to Cloud & Enterprise Agents > Agent Settings, Agents tab and click Add New Agent button and click Show Account Group Token for Installation to reveal the token.
Paste the Account Group Token into the Account Token field. The field should turn green.
Select Yes for Browserbot if you wish; this is required for Page Load and Transaction tests.
Click Next, and verify/configure Network and Time server settings for the VA.
Run the Diagnostics check and continue to proceed to Agent status.
Check that your Agent appears on the Cloud & Enterprise Agents > Agent Settings > Agents tab, inside ThousandEyes.
That's it! You've installed an enterprise agent in the context of your ISR.
List all virtual-service containers installed
isr# sh virtual-service list
View configuration details of a virtual-service container
isr# sh virtual-service detail name hitman
View global information of installed virtual-service containers
isr# sh virtual-service global
View utilization information about a virtual-service container.
isr# sh virtual-service utilization name hitman
View virtual-service trace contents
isr# sh virtual-service trace message
Debug virtual-service container
isr# debug virtual-service all
If you want to stop the Agent from running tests, but keep the IOS XE Container installed, then,
isr# config tisr(config)# virtual-service hitmanisr(config)# no activateisr(config)# end
You can check the status of the virtual-service container using
isr# sh virtual-service listVirtual Service List:Name Status Package Name------------------------------------------hitman Deactivated teva-cisco.ova
If you want to uninstall the virtual-service container from the ISR/ASR, then,
isr# config tisr(config)# virtual-service hitmanisr(config)# no activateisr(config)# end
Once the virtual-service container is "deactivated", uninstall the virtual-service container, as
isr# virtual-service uninstall name hitman
In both cases, the agent will be shown as OFFLINE under Cloud & Enterprise Agents > Agent Settings > Agents.
Q. How does having an Enterprise Agent on Cisco IOS-XE impact performance? A. We compared a Docker version of the agent running on an Intel NUC to an agent running on the ISR. 3 Enterprise Agents were run in parallel. The performance characteristics of an agent show an approximately 25% decrease in browserbot performance relative to a standalone device running a similar configuration, however, HTTP, network, and DNS tests were within a 2% variance of a single device. Note that this was NOT a variation in performance on the ISR or other applications within the ISR.
Q. Does installing an agent have an impact on production traffic handled by the ISR or ASR? A. Enterprise Agents are installed on service-containers within the ISR. By definition, the virtual instances are compartmentalized and should not affect other applications or services on the ISR. However, you should make sure that there are enough hardware resources available on the routers to install the agent.
Q. What is the advantage of collocating Enterprise Agents within a router? Does this new deployment model allow us to expand into newer markets? A. Enterprise Agents, now deployed within an ISR or ASR router, provide an opportunity to expand into markets that might have been previously challenging, for example, retail stores or remote offices that often do not have readily available VMs or servers and procuring new hardware can be challenging and time-consuming. Piggybacking on existing hardware makes it easier for customers to deploy agents as it does not involve new, stand-alone hardware installation or security clearance. Cisco ISRs and ASRs form the vast majority of routers in branch offices across enterprise WAN, so this model can increase the probability of newer deployments.
Q. I cannot activate the Virtual Appliance. A. It was detected that in some RP's KVM support is disabled, this is shown by issuing "show virtual-service" and checking the "Machine types disabled" list. The root cause was that VTX support on the RP's processor was disabled. The way to enable VTX support is to break into ROMMON mode (steps 1, 2, 4 and 5 of "Details of the Password Recovery Procedure" section) of the RP that has VTX disabled, and issuing the following commands:
Once this is done, KVM should be listed in the "Machine types supported" list of "show virtual-service" command output and normal configuration and activation of the Virtual Appliance should follow.