This section explains the collection of tech support logs using CLI.

To collect tech support logs using the NSX Advanced Load Balancer CLI:

  • In an NSX Advanced Load Balancer Controller cluster, one of the nodes is the leader or the primary node. Log in to the leader node using any ssh client, such as putty. 10.10.1.1 is the leader node in the following 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:   10.10.2.2/22                UP
Gateway:      10.10.2.1                   UP

[email protected]'s password:

For more information about the leader node in an NSX Advanced Load Balancer Controller cluster, see Overview of the Controller Cluster in the VMware NSX Advanced Load Balancer.

For more information about SSH key generation, see CLI access in the VMware NSX Advanced Load Balancer.

Type shell command, and enter your credentials.

 admin@avi-cntrl1:~$ shell
 Login: <login-name> 
 Password:

  • From the shell prompt, run the command show tech-support serviceengine.

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

Note:

Avi-cluster1-SE1 is the NSX Advanced Load Balancer 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 /var/lib/avi/tech_support directory on the Controller leader node. Use cd command from the NSX Advanced Load Balancer CLI to get access to the directory. Check the debug logs and the other log files, which are available in compressed form with tar.gz extension.

The sample tech support log file is 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 - 15 Sep 2017. The following are the different options of tech support:

  • clustering — If you want to debug any clustering related issues, you need to check clustering tech support, as it collects clustering related files, for example, cluster.conf, zookeeper, journal logs.

The CLI command for clustering tech support is:

show tech-support clustering

  • metricslogs — If you want to debug issue with metrics manager, you can collect metricslogs techsupport.

The CLI command for metriclogs tech support is:

show tech-support metricslogs

  • 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, etc. with this tech support type.

The CLI command for debuglogs tech support is:

show tech-support debuglogs

  • placement — Choosing the placement type allows collection of placement tech support logs like vs_mgr, res_mgr etc.

The CLI command for placement tech support is:

show tech-support placement

  • portal — If you want to debug any portal or webapp related issues to generate logs like portal-webapp, portal_exception, etc., you can collect portal tech support .

The CLI command for portal tech support is:

show tech-support portal

  • serviceengine — If you face any issue regarding specific Service Engine, you can collect serviceengine tech support to debug that issue. The tech support collect all required logs from the specific Service Engine.

The CLI command for serviceengine tech support is:

show tech-support serviceengine <serviceengine-name>

  • upgrade — If you have any upgrade related issue, you can collect upgrade tech support.

The CLI command for upgrade tech support is:

show tech-support upgrade

  • virtualservice — If you have issue with any specific virtual service and need to debug it, you can collect virtualservice tech support. This type collects specific virtualservice logs and the serviceengine logs where the virtualservice is attached to.

The CLI command for virtualservice tech support is:

show tech-support virtualservice <virtualservice-name>

  • gslb — If you need to debug any issue related to gslb, you can collect gslb techsupport, that includes only gslb related logs.

The CLI command for gslb tech support is:

show tech-support gslb

  • pool — If you need to debug any issue with specific pool in the system, you can collect tech support for that specific pool that has CLI commands output to the pool and vs_mgr logs.

The CLI command for pool tech support is:

show tech-support pool <pool-name>