F5 Logo MyF5
Search
  1. MyF5 Home
  2. F5 rSeries Platforms: Platform Diagnostics
  3. View diagnostic information on F5 rSeries systems
Manual Chapter : View diagnostic information on F5 rSeries systems

Applies To:

Show Versions Show Versions

F5OS-A

  • 1.2.0
Manual Chapter

View diagnostic information on F5 rSeries systems

You can check component health and alarm conditions from the CLI and webUI. Diagnostic data is included in QKView reports, which you can upload to iHealth.
For information about severity levels and what to do when a component is unhealthy, see the Component severity levels and health section.

View event logs from the CLI

The system logs events to the
appliance.log
 file located in the
log/host
 directory. To list files and view the contents of log files, you use the
file
 command from the CLI.
  1. Connect using SSH to the management IP address.
  2. Log in to the command line interface (CLI) of the system using an account with admin access.
    When you log in to the system, you are in user (operational) mode.
  3. List all files in the log directory.
    file list path [ log/confd/ | log/host/ | log/system/ }
    This example shows an excerpt of the contents of the
    log/host/
     directory: 
    appliance-1# file list path log/host
entries {
    name anaconda/
    date Thu May 12 17:01:36 UTC 2022
    size 4.0KB
}
entries {
    name ansible.log
    date Fri Jun 17 16:18:02 UTC 2022
    size 0B
}
entries {
    name appliance.log
    date Fri Jun 17 16:18:19 UTC 2022
    size 9.8KB
}
entries {
    name audit/
    date Fri Jun 17 14:59:04 UTC 2022
    size 4.0KB
}
entries {
    name boot.log
    date Thu May 12 17:02:35 UTC 2022
    size 105B
}
...
  4. Show the contents of a log file.
    file show [ log/confd/<
    filename
    > | log/host/<
    filename
    > | log/system/<
    filename
    > ]
    This example shows the contents of the
    log/host/boot.log
     file:
    appliance-1# file show log/host/boot.log
May 12 10:02:35 localhost NET[1605]: /etc/sysconfig/network-scripts/ifup-post : updated /etc/resolv.conf
  5. Show only the most recent entries in a log file.
    file tail [ log/confd/<
    filename
    > | log/host/<
    filename
    > | log/system/<
    filename
    > ]
    This example shows the last ten lines of the
    appliance.log
     file and uses the
    -f
     option to append output as the file grows: 
    appliance-1# file tail -f log/host/appliance.log
2022-06-17 16:18:03.267761 - OMD log is initialized
2022-06-17 16:18:03.267761 - 8:-738199808 - applianceMainEventLoop::Orchestration manager startup.
2022-06-17 16:18:03.270244 - 8:-754985216 - Can now ping appliance-1.chassis.local (100.65.60.1).
2022-06-17 16:18:03.723485 - 8:-754985216 - Successfully ssh'd to appliance 127.0.0.1.
2022-06-17 16:18:14.399076 - 8:-738199808 - Appliance 1 is ready in k3s cluster.
2022-06-17 16:18:14.399095 - 8:-738199808 - K3S cluster is ready.
appliance-flannel_image|localhost:2003/appliance-flannel:0.13.0
No Image Changes Found for normal reboot
appliance-multus_image|localhost:2003/appliance-multus:3.6.3
No Image Changes Found for normal reboot
_

View component health from the CLI

You can view health information about specific components in your F5 rSeries system from the CLI. For more information about
show system health
 and other CLI commands, see the F5OS-A/F5 rSeries CLI reference at clouddocs.f5.com/api/rseries-api/rseries-cli-index.html.
  1. Connect using SSH to the management IP address.
  2. Log in to the command line interface (CLI) of the system using an account with admin access.
    The default login credentials are admin/admin. When logging in as admin for the first time, the system prompts you to change the password.
    When you log in to the system, you are in user (operational) mode.
  3. View health information about system components.
    show system health components component [ appliance | drive-slot-1 | drive-slot-2 | fantray | lcd | psu-1 | psu-2 ] [ firmware | hardware | services ] <
    hardware-identifier
    >
    The available components might vary depending on hardware model.
    This example shows the high-level hardware state for the fan tray: 
    appliance-1# show system health components component fantray hardware state
KEY                         NAME      HEALTH  SEVERITY
--------------------------------------------------------
appliance/hardware/fantray  Fan Tray  ok      info
    This example shows health information about system memory: 
    appliance-1# show system health components component appliance hardware appliance/hardware/memory
hardware appliance/hardware/memory
 state name Memory
 state health ok
 state severity info
NAME                                DESCRIPTION                      HEALTH  SEVERITY  VALUE  UPDATED AT
--------------------------------------------------------------------------------------------------------------------
memory:sensor:temperature           Memory DIMM temperature (C)      ok      info      55     2022-06-14T01:07:03Z
rasdaemon:mc:corrected:event        RAS Daemon MC corrected event    ok      info      0      2022-06-14T01:05:02Z
rasdaemon:mc:fatal:event            RAS Daemon MC fatal event        ok      info      0      2022-06-14T01:05:02Z
rasdaemon:mc:uncorrected:event      RAS Daemon MC uncorrected event  ok      info      0      2022-06-14T01:05:02Z
v6h:thermal-fault:vddq-abcd-vr-hot  VDDQ_ABCD_VR_HOT thermal fault   ok      info      0      2022-06-08T17:25:00Z
v6h:thermal-fault:vddq-efgh-vr-hot  VDDQ_EFGH_VR_HOT thermal fault   ok      info      0      2022-06-08T17:25:00Z
    This example shows the status of the tcpdump service: 
    appliance-1# show system health components component appliance services appliance/services/tcpdumpd_manager
services appliance/services/tcpdumpd_manager
 state name tcpdumpd_manager
 state health ok
 state severity info
NAME                               DESCRIPTION                               HEALTH  SEVERITY  VALUE  UPDATED AT
----------------------------------------------------------------------------------------------------------------------------
container:event:attach             Container attach event                    ok      info      0      2022-04-18T17:55:36Z
container:event:die                Container die event                       ok      info      7      2022-06-13T22:06:37Z
container:event:exec-create        Container exec create event               ok      info      0      2022-05-26T01:53:19Z
container:event:exec-detach        Container exec detach event               ok      info      0      2022-04-18T17:55:36Z
container:event:exec-die           Container exec die event                  ok      info      0      2022-04-18T17:55:36Z
container:event:exec-start         Container exec start event                ok      info      0      2022-05-26T01:53:20Z
container:event:kill               Container kill event                      ok      info      7      2022-06-13T22:06:35Z
container:event:restart            Container restart event                   ok      info      7      2022-06-13T22:06:37Z
container:event:restart-last-hour  Container restart count in the last hour  ok      info      0      2022-06-13T23:07:07Z
container:event:start              Container start event                     ok      info      7      2022-06-13T22:06:37Z
container:event:stop               Container stop event                      ok      info      7      2022-06-13T22:06:37Z
container:running                  Container running                         ok      info      true   2022-06-14T01:07:02Z

View active system alarm conditions from the CLI

You can view information about active system alarm conditions from the CLI.
  1. Connect using SSH to the management IP address.
  2. Log in to the command line interface (CLI) of the system using an account with admin access.
    When you log in to the system, you are in user (operational) mode.
  3. View a list of active system alarm conditions.
    show system alarms | tab
    This example shows a power supply unit (PSU) redundancy fault: 
    appliance-1# show system alarms | tab
ID     RESOURCE        SEVERITY  TEXT                           TIME CREATED
–––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––-          
65793  psu-1           ERROR     PSU fault detected             2022-06-01-11:11:11.999825828 UTC

Generate system reports (QKView) from the CLI

You can generate a QKView file from the CLI. The report contains diagnostic information, such as configuration data, log files, and platform information.
  1. Log in to the command line interface (CLI) of the system using an account with admin access.
    When you log in to the system, you are in user (operational) mode.
  2. Change to config mode.
    config
    The CLI prompt changes to include
    (config)
    .
  3. Generate a QKView file.
    system diagnostics qkview capture exclude-cores {
    false
     |
    true
     } filename <
    filename
    > maxcoresize <
    size
    > maxfilesize <
    size
    > timeout <
    time
    >
    These options are available:
    Option
    Description
    exclude-cores
    Specify whether core files should be excluded from the QKView file. The default is to include core files.
    filename
    Specify a name for the file to which QKView file data is written. The default filename is
    <
    system-name
    >.tar
    .
    maxcoresize
    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.
    maxfilesize
    Exclude all files greater than the specified size (in MB). The range is from 2 MB to 1000 MB. The default value for maximum file size is 500 MB.
    timeout
    Specify the time in seconds after which to stop QKView file data collection. The default value is 0, which indicates no timeout.
    In this example, you generate a QKView file named
    client-qkview.tar
     that excludes core files, sets the maximum core size to 500 MB, sets the maximum file size to 500 MB, and sets a timeout value of 0 (zero), which indicates no timeout: 
    appliance-1(config)# system diagnostics qkview capture filename client-qkview exclude-cores true maxcoresize 500 maxfilesize 500 timeout 0
result  Qkview file client-qkview is being collected
return code 200
  4. Check the status of the QKView generation process.
    system diagnostics qkview status
    A summary similar to this example displays:
    appliance-1(config)# system diagnostics qkview status
result  {"Busy":true,"Percent":12,"Status":"collecting","Message":"Collecting Data","Filename":"client-qkview"}

resultint 0
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