Troubleshooting Report¶

This command allows collecting various diagnostics of the system that can be provided to 6WIND support to help debugging a problem.

The troubleshooting report includes the following information:

Linux networking information
- ethtool on all known links
- interfaces, addresses, routes, neighbours and IPsec
- active network connections
- Netfilter tables, bridge
system information
- topology
- processors hierarchy
- interrupts
- memory
- PCI peripherals
- DMI/MBIOS
- kernel version, logs, cmdline and loaded modules
- distribution
- services list
- logs
- processes list
- cpuset
- devices (/dev)
- IRQ affinity
- mounted partitions
core dumps
fast path information
- configuration, version, logs, status
- debug info (ports, tables, etc.)
running and startup configurations
license information
- average network throughput (measured in Rx)
- average and current number of IPsec tunnels
- average and current number of CG-NAT connections

List existing troubleshooting reports

vsr> cmd troubleshooting-report list
NAME                           SIZE
2018-09-24_17-21-31.tgz        295.7K
2018-09-24_17-21-40.tgz        295.8K
vsr>

Create a new troubleshooting report

vsr> cmd troubleshooting-report new
Gathering information. This may take some time...
Saved into /var/lib/yams/troubleshooting-reports/2018-09-24_17-27-07.tgz
vsr>

Delete an existing report

vsr> cmd troubleshooting-report delete 2018-09-24_17-21-31.tgz
OK.
vsr>

Export an existing report to a remote location

vsr> cmd troubleshooting-report export 2018-09-24_17-27-07.tgz url scp://john:s3cr3t@10.1.2.3/home/john
OK.
vsr> cmd troubleshooting-report export 2018-09-24_17-27-07.tgz url smtp://10.1.2.100/john@acme.com
OK.
vsr>

It is possible to export via multiple protocols: FTP, HTTP, TFTP, SCP, SFTP and SMTP (for the later, you will need to specify an email address instead of a file path).

Flush all existing reports

vsr> cmd troubleshooting-report flush
OK.
vsr>