4.1. Relevant Information for Bug Reporting¶

In case you cannot investigate and resolve the issue by yourself using this document, make sure you open a ticket on your 6WIND Customer Zone with the relevant troubleshooting information.

This information can be generated and exported using the following commands:

vrouter> 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
vrouter> cmd troubleshooting-report export 2018-09-24_17-27-07.tgz url scp://john:s3cr3t@10.1.2.3/home/john
OK.
vrouter>

See also

The CLI User Guide, Basics / Commands section for details.

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