F5 Logo MyF5
Search
  1. MyF5 Home
  2. VELOS Systems: Getting Started
  3. Troubleshooting options
Manual Chapter : Troubleshooting options

Applies To:

Show Versions Show Versions

F5OS-C

  • 1.6.1, 1.5.0, 1.3.2, 1.3.1, 1.3.0, 1.2.2, 1.2.1, 1.2.0, 1.1.4, 1.1.3, 1.1.2, 1.1.1, 1.1.0
Manual Chapter

Troubleshooting options

If you have trouble getting the
VELOS
 system set up and configured, there are some options available to help you.
Many functions in the system will log events to the
velos.log
 file. In the CLI, you can use the
file list path
 command to view the files in the
log/controller
 directory.
You can also search the knowledge articles on my.f5.com.

Generate system reports (QKView) from the webUI

If you want to upload a QKView file to the F5 iHealth server, your
VELOS
 system must have DNS configured and have internet access to these services using the HTTPS/443 remote service/port:
  • api.f5.com
  • ihealth-api.f5.com
You can generate a QKView file from either the system controller or chassis partition webUI. Both reports contain diagnostic information, such as configuration data, log files, time series statistics, and platform information.
  1. Log in to the VELOS system controller webUI or the chassis partition webUI using an account with admin access.
  2. On the left, click
    DIAGNOSTICS
    System Reports
    .
    The System Reports screen displays. A list of QKView files that were previously generated are shown with any reports that were uploaded to iHealth.
  3. To generate a system report, click
    Generate QKView
     in the upper right corner of the screen.
    The Generate QKView box displays these additional options:
    Option
    Description
    Filename
    Specify a name for the file to which QKView file data is written. The default filename is <
    system-name
    >.tar.
    Timeout Value
    Specify the time in seconds after which to stop QKView file data collection. The default value is 0, which indicates no timeout.
    Max File Size
    Exclude all files greater than the specified size (in MB). The range is from 2 MB to 1000 MB. The default value is 500 MB.
    Max Core Size
    Exclude core files greater than this size (in MB). The range is from 2 MB to 1000 MB. The default value for maximum core size is 25 MB.
    Exclude Cores
    Specify whether core files should be excluded from the QKView file. The default is to include core files.
    The system runs many commands to collect the diagnostic information, so generating the report might affect its performance.
    It takes a few minutes for the system to finish creating the report and list it on the screen. The QKView Status changes to
    File generated successfully
     when it is done.
  4. To upload the report to the F5 iHealth server, select the check box next to the QKView name and click
    Upload to iHealth
    .
    For information on uploading the report using a web proxy, see "Configure iHealth uploads and web proxy from the webUI".
    The QKView tar file uploads to iHealth, where you can get help to diagnose the health and proper operation of the system. You can view the report at ihealth2.f5.com.
  5. To delete a QKView file, select it and click
    Delete
    .

Generate a tcpdump

You can use the
tcpdump
 utility to capture traffic in chassis partitions. You can then save the captured traffic as a file that can be analyzed to help troubleshoot network issues.
  1. Connect using SSH to the chassis partition management IP address.
  2. Log in to the command line interface (CLI) of the chassis partition using an account with admin access.
    When you log in to the system, you are in user (operational) mode.
  3. Generate a tcpdump.
    system diagnostics tcpdump
    These options are available to use with this command:
    Option
    Description
    Example
    -i | interface
    Specifies the interface on which to capture packets. Omit or specify
    0/0.0
     to indicate all interfaces.
    This example captures traffic on interface 1.0 on blade number 2:
    system diagnostics tcpdump interface 2/1.0
    -w | outfile
    Specifies the pcap file to write the captured packets.
    This example sends the output to a specified directory:
    system diagnostics tcpdump outfile <
    file-name
    >.pcap
    bpf
    Specifies the Berkeley packet filter (BPF) expression for tcpdump. This option uses standard BPF syntax.
    This example captures traffic where the source IP address is 192.0.2.0 and the destination port is 80:
    system diagnostics tcpdump bpf "src host 192.0.2.0 and dst port 80"
    The system supports the use of standard tcpdump options. For more information, see www.tcpdump.org/manpages/tcpdump.1.html.

Other file and configuration management commands

You can also use these commands to help with troubleshooting. You can type a question mark (
?
) or press the Tab key to see possible command completions in the CLI.
For a comprehensive list of CLI commands, see the CLI Reference for your
F5OS
 system at clouddocs.f5.com
Command
Description
system database config config-backup config-restore
Saves the CDB configuration to an XML file and restores CDB configuration.
file list path <
dir-path
>
Displays the contents of the specified directory.
file show <
file-path
>
Displays the contents of a specified file.
Contact Support Contact Support

Have a Question?

Support and Sales >

About F5

Education

F5 Sites

Support Tasks




©2023 F5, Inc. All rights reserved.


Trademarks Policies Privacy California Privacy Do Not Sell My Personal Information