The Cisco CLI Analyzer is a standalone SSH client infused with Cisco TAC Intellectual Capital, and is available for Windows and Mac OS X platforms.
The TAC Data Collection tool is part of the CLI Analyzer and allows automatic collection of diagnostic commands requested by your TAC engineer. This is supported on ASA, IOS, IOS-XE, IOS-XR, NX-OS, WLC, and UCS platforms.
If you already have the CLI Analyzer installed, you may go directly to this video for a demo of the TAC Data Collection tool.
Collecting show commands from a device and sending the output to a TAC engineer appears to be a simple task, but often it is not. Errors created by copy-pasting commands to the device, terminal length cutting off outputs, email attachments too large, emails sent to one engineer while the TAC case is re-queued to another engineer in addition to the time it takes to complete this task and for TAC to follow up to correct any issues with collection errors. It should be faster and simpler. Now it is...
The TAC Data Collection Tool was created to make this process more reliable and easier.
This document will guide you through your first data collection.
Email From TAC Engineer
The TAC Data Collection process is initiated by a TAC engineer when diagnostic commands are needed from one or more of your devices.
The TAC engineer creates a data collection request identified by a TaskID which points a list of commands to collect and upload to your TAC case. A TaskID looks like "#TAC-D0A6-2561" (with the # sign and without the quotes). The TaskID needs to be entered in the CLI Analyzer to tell the tool which commands to collect and which case they should be uploaded to.
Note: Ensure you only run the TAC Data Collection tool on the device(s) your TAC engineer has requested.
This TaskID is shared by the TAC engineer in an email to the case contact similar to the one below:
-------- Forwarded Message --------
Data collection task #TAC-D0A6-2561 for TAC case 681631261
As explained in the email, using the CLI Analyzer to collect the commands is optional and customers may still collect commands with their favorite telnet/SSH client and send them to the TAC engineer by email or through the Case File Uploader.
This document will guide you through the steps to collect the commands with the TAC Data Collection tool.
Step 1. Install CLI Analyzer
If you're already running CLI Analyzer 3.2 or above, you can skip this step.
You should be able to follow the install procedure on Mac or Windows relatively easily by selecting the defaults.
First Run - Master Password
The CLI Analyzer can remember the device credentials. A master password is used to protect these credentials on your computer:
This master password will be requested each time you open the CLI Analyzer again in the future to be able to unlock the device credentials.
After entering the master password, the main window appears:
The "Devices" tab is selected and this is where you will find all your saved devices. Once you have a few devices created, you can search by name, location, version, labels etc to limit the number of devices being displayed.
Step 2. Connect to the Device
There are 3 ways to create new devices and connect to them:
Click "New Session" in the left toolbar and enter the destination IP address or hostname, the type (SSH, telnet, serial port or shared/screen sharing) and the port number. This will connect you directly to the device but this will also created a bookmark for this device under the "Devices" tab.
When the "Devices" tab is selected, click the "+" sign (with a red circle in the screenshot above) to first create a bookmark for the device.
When creating or editing a device, you can set some fields like a location or label(s) which can help limit the number of devices when searching for them. Here is how the "Devices" tab looks like after creating 3 new devices but filtering on "Euro-TAC" to only display devices whose location has been set to Euro-TAC:
Now you can connect to the device by clicking on "New Session" in the left bar or click on the connect button below the device (red circle in screenshot above).
Detecting Device Type
When the CLI Analyzer logs into a device for the first time, it runs a few commands automatically to detect the device type:
You can see in the screen shot above that the commands "show version" and "admin show diag chassis" were executed. Some commands on some platforms may take a few seconds to complete so let it run until the "Device Information" is displayed.
In the example above, the CLI Analyzer detected that this is an IOS-XR device as indicated at the bottom right of the screen (red circle).
If you reach the final device through some intermediate hops (jump server or other routers or switches), it's possible that the CLI Analyzer won't detect the correct device type. Always check the device type at the bottom right of the window. If it does not appear to be set correctly, click on the "Refresh Device Information" button at the bottom right of the window (green circle in the previous screenshot above).
When connecting frequently to devices, this device detection process may not be desired. By default, the CLI Analyzer will cache this info for up to 30 days (detection frequency is configurable in the settings). This means that if you upgrade the software version on a device, it will still appear with the previous software version in the "Devices" tab for up to 30 days. You may want to click on the "Refresh Device Information" button at the bottom right of the window (green circle in the previous screenshot above) after an upgrade.
Step 3. Run the TAC Data Collection Tool
Once connected to the correct device, click on the "Tools" button in the top right corner:
Click on the "TAC Data Collection" and a first form will appear:
The goal of this first form is to enter a TaskID. This is the TaskID you should have received from the TAC engineer via email.
If your CCO ID is the case contact, then the TaskID should appear in the "Select recent TaskID" dropdown and you just need to select the correct one in the dropdown (you may have multiple TaskID's for the same case or from different cases). Note: Be sure the "CCO Login field in CLI Analyzer reflects the same CCO ID associated with the TAC case in question. Otherwise, use the process that follows below.
If the email from the TAC engineer was forwarded to you by a colleague who is the case contact, then your username will not be associated with the service request and the CLI Analyzer will NOT be able to display the TaskID in the dropdown. Therefore, you will have to copy-paste the TaskID from the email to the "Enter TaskID manually" text box.
Note: If there's a TaskID selected in the dropdown and also one entered manually, then the one entered manually takes precedence.
Click "Continue" and the CLI Analyzer will retrieve the list of commands associated with this TaskID, display the list and ask you whether you want to proceed and collect the commands:
The "term len 0" is inserted as the first command and the original terminal length is reset at the end. So the 2 interesting commands are the ones in the middle in the example above. Press "Continue" if you agree to collect these 2 commands and send their outputs to the TAC case.
Commands are collected:
Once all commands are collected, the outputs are posted through the Cisco APIs, attached to the TAC service request and a result window appears:
Your Cisco TAC engineer is notified of the collection so the next step is to review the outputs and get back to you with the analysis and action plan.
Please review this video for a demo of the TAC Data Collection process.
Other CLI Analyzer Features
Apart from the TAC Data Collection tool, here are some other CLI Analyzer features that you may find useful:
Since version 3.6.7 I get this each time I open an SSH connection to any of the devices in my fleet. I have been using the CLI analyzer tool for more than a year and none of the devices have changed RSA keys.Deleteing the known_hosts file made no differen...
I just started using the Cisco CLI Analyzer as my default SSH-Client and I'm quite happy with all the tools and features it provides, but I've started noticing an error message in my log everytime I connect to one of my switches.The error message looks li...
This is probably petty but is there a way to get the CLI Analyzer to sort IP addresses properly? Currently it sorts 192.168.1.1, 192.168.1.10, 192.168.1.11, etc.I would like it to sort 192.168.1.1, 192.168.1.2, 192.168.1.3, etc.I tried putting 001, 0...
Hello Usually, on Windows, the most common SSH client is putty, that uses a different file format (ppk) for storing keys, than the openssh client on Linux/*Nix (.ssh/.pub) ... I talk about the internal file structure (not the extension). Is ther...