Collecting Tech Support Logs


Tech support logs are used for offline troubleshooting. This article describes how to collect tech support logs from a single Avi Controller or 3-node Avi Controller cluster.

Note: In a 3-node Avi Controller cluster, the steps mentioned in this article automatically collect logs from all the three nodes. The commands need not be entered separately on each Avi Controller node.

Collecting tech support logs from Avi UI

Follow the instructions in this section to collect tech support logs from the Avi UI.

Navigate to Administration > Troubleshoot and select Generate to create tech support log files.

Screen Shot 2016-09-19 at 12.29.15 PM

Click on the plus sign at the rightmost position in the archive row) to display additional information. Click on the download icon as shown in the below screenshot to download the tech support file to the local drive. Download the .tar.gz file and then convey it to Avi Support for further troubleshooting.

downloading tech support log

Collecting tech support logs from Avi CLI

Follow the instructions in this section to collect tech support logs from the Avi CLI.

  • In an Avi Controller cluster, one of the nodes is the leader or the primary node. Login to the leader node using any ssh client, such as putty. is the leader node in this example.

login as: admin

Avi Cloud Controller

Avi Networks software, Copyright (C) 2013-2017 by Avi Networks, Inc.
All rights reserved.

Version:      17.1.6
Date:         2017-08-30 15:35:21 UTC
Build:        9022
Management:                UP
Gateway:                    UP

admin@'s password:

To know more about the leader node in an Avi Controller cluster, refer to Overview of the Controller Cluster. To know more about SSH key generation, refer to Avi CLI access.

  • Type shell command, and enter your credentials.

admin@avi-cntrl1:~$ shell
Login: admin
  • From the shell prompt, run the command show tech-support serviceengine.

    The command show tech-support serviceengine create debug logs for the particular SE.

    Note: For reference, Avi-Cluster1-SE1 is the Avi SE for which we want to collect the debug logs.

[admin:avi-cntrl1]: > show tech-support serviceengine Avi-cluster1-SE1
  • This command generates core files and other debug logs, which are stored in /tmp directory on the Avi Controller leader node. Use cd/tmp command from the Avi CLI to get access to the tmp directory. Check the debug logs and the other log files, which are available in compressed form with tar.gz extension.

Sample tech support log file: debuglogs.20170915-124030.tar.gz The number 20170915 in the log file debuglogs.20170915-124030.tar.gz represents the date of generation of the log files, i.e., 15 Sep 2017.

The following are the different options of tech support:

  • clustering — If you want to debug any clustering related issues, then you need to collect clustering tech support, as it collects clustering related files, for instance, cluster.conf, zookeeper, journal logs.
    show tech-support clustering is the CLI command for clustering tech support.

  • metricslogs — If you want to debug issue with metrics manager, then you can collect metricslogs techsupport.
    show tech-support metricslogs is the CLI command for metriclogs tech support.

  • debuglogs — This is the most used type for collecting tech support which has logs from cluster nodes. You can debug issues like upgrade, events, web-app, log-rotation, log core manager, redis, and so on with this tech support.
    show tech-support debuglogs is the CLI command for debuglogs tech support.

  • placement — If you want to debug any issue related to placement, then you can collect placement tech support. It collects logs like vs_mgr, res_mgr etc.
    show tech-support placement is the CLI command for placement tech support.”

  • portal — If you want to debug any portal or webapp related issues, then you can collect portal tech support. It collects logs like portal-webapp, portal_exception, and so on.
    show tech-support portal is the CLI command for portal tech support.

  • serviceengine — If you face any issue regarding specific Service Engine, then you can collect serviceengine tech support to debug that issue as it will collect all required logs from that particular Service Engine.
    show tech-support serviceengine <serviceengine-name> is the CLI command for serviceengine tech support.

  • upgrade — If you have any upgrade related issue, you can collect upgrade tech support.
    show tech-support upgrade is the CLI command for upgrade tech support.

  • virtualservice — If you have issue with any specific virtual service and need to debug it, then you can collect this tech support which has that specific virtualservice logs along with the serviceengine logs where that virtualservice is attached to.
    show tech-support virtualservice <virtualservice-name> is the CLI command for virtualservice tech support.

  • gslb — If you need to debug any issue related to gslb then you can collect gslb techsupport, which has gslb related logs only.
    show tech-support gslb is the CLI command for gslb tech support.

  • pool — If you need to debug any issue with specific pool in the system then you can collect tech support to that specific pool which has CLI commands output to that specific pool and vs_mgr logs as well.
    show tech-support pool <pool-name> is the CLI command for pool tech support.

Additional Information

The following command collects the debug logs on each of the Avi Controller nodes. This option keeps the collected tech support bundle to a minimal size. The option is especially useful if the core archive bundles that are present have already been uploaded and fixed.

show tech-support debuglogs

The following command includes the collection of the core archive bundles.

show tech-support debuglogs filter include_archive

If you have external connectivity to AWS S3 from the Avi Controller, you can upload the tech support information to the Avi customer support S3 bucket, using the following command:

upload tech-support debuglogs

Collecting tech support logs using Avi API

Follow the commands in this section to collect tech support logs using REST API.

GET https:///api/techsupport/debuglogs
GET https:///api/techsupport/debuglogs?include_archive=true
GET https:///api/techsupport/debuglogs?upload=true

Collecting Tech Support Logs via Script on the Controller

You can upload logs via script on the Controller. Before running the script, ensure:

  • A per-user or per-account token for API authentication
  • Forward proxy on the network which the Controller is part of
  • Super user access to the Controller

Note: The script is found under /opt/avi/scripts directory.

The CLI format is as follows:

User@Test-MacBook-Pro:~$ ssh admin@

Avi Cloud Controller

Avi Networks software, Copyright (C) 2013-2017 by Avi Networks, Inc.
All rights reserved. 

Version:      17.1.8
Date:         2017-09-21 06:03:07 UTC
Build:        9020
Management:                 UP 
Gateway:                     UP 

admin@'s password: 

The copyrights to certain works contained in this software are
owned by other third parties and used and distributed under
license. Certain components of this software are licensed under
the GNU General Public License (GPL) version 2.0 or the GNU
Lesser General Public License (LGPL) Version 2.1. A copy of each
such license is available at and
Last login: Fri Oct  6 07:01:03 2017 from
admin@Test-Cntl:~$ cd /opt/avi/scripts
admin@Test-Cntl:/opt/avi/scripts$ pwd
admin@Test-Cntl:/opt/avi/scripts$ ls -l 
rwxrwx-- 1 root root 14187 Sep 21 06:03

root@Test-Cntl:/opt/avi/scripts# ./ --help
usage: [-h] [-c CONFIG] [-d] [-H HOSTNAME] [-i]
[-p {http,https}] [-P] [-t TOKEN]

Attaches files to a case on the Avi Networks portal.

positional arguments:
CASE-NUMBER           case number to attach files to
FILE                  files to attach to the case

optional arguments:
-h, --help            show this help message and exit
-c CONFIG, --config CONFIG
Path to configuration file (JSON) (default: None)
-d, --debug           Enable HTTP debug (default: False)
HTTP hostname (default:
-i, --insecure        Allow insecure SSL connections (default: False)
-p {http,https}, --protocol {http,https}
HTTP protocol (default: https)
-P, --progress        Display progress indicator (default: False)
-t TOKEN, --token TOKEN
API authentication token  

The script can be executed as follows:

/opt/avi/scripts/ -H -t  -P -p https <case#>                       


admin@Test-Cntl:/opt/avi/scripts$ sudo su
[sudo] password for admin: 
root@Test-Cntl:/opt/avi/scripts# ls -ltrh /home/admin/test
total 5.4G
-rwxrwxrwx 1 admin admin 3.5G Oct  6 06:44 test.tar.gz
-rwxrwxrwx 1 admin admin 2.0G Oct  6 06:47 controller.pkg

root@Test-Cntl:/opt/avi/scripts# ./ -H -t  -P -p https 3763 /home/admin/test/controller.pkg 
root@Test-Cntl:/opt/avi/scripts# ./ -H -t  -P -p https 3763 /home/admin/test/test.tar.gz
Attaches files to a case on the Avi Networks portal.  </code></pre>