Manual Chapter : VELOS Dashboards and Diagnostics

Applies To:

Show Versions Show Versions


  • 1.0.0
Manual Chapter

VELOS Dashboards and Diagnostics

VELOS dashboard overview

The VELOS dashboards display relevant system information when you log in to the system controller or the chassis partition webUI. For example, this figure shows how the default partition is set up initially. All of the slots are associated with the default partition. (Note that only four of the slots have bladed installed.)
System controller dashboard (initial view)
Both of the dashboards are divided into sections that show:
  • Partition details
  • Active alarms
  • High availability status
Partition details on the system controller dashboard show an overview of all the partitions, and on the chassis partition dashboard they show details about the partition you are logged in to.
Active alarms show system alerts that have occurred recently. The system updates the alarms every few seconds. It shows the source of the alert, its severity, a brief description of what occurred, and when it happened.
High availability status shows which system controller is currently active, and whether the two controllers are both healthy. If both are healthy, the two system controllers handle traffic and are redundant. The system is functioning normally.

System controller dashboard

The system controller dashboard shows information about which slots have blades in them, how the chassis is divided into partitions, active alarms, and system controller high availability status. It is displayed when you log in to the system controller webUI, or click
from any other area in the system controller webUI.
System Controller dashboard
The Partition Overview section shows a graphical view of the chassis. Here two additional partitions were created. Custpart1 is assigned to slot 1, and color coded in blue, and custpart2 is assigned to slot 2, and color coded in black. The slots associated with the default partition are shown in green (but those slots are empty for now). Partitions are listed in the table on the right. The IP address of an active partition is shown as a link that you can click to log directly in to the partition.

Chassis partition dashboard

The chassis partition dashboard shows which partition you are logged in to, which slots are associated with that partition, active alarms for that partition, and lists the tenants that are deployed in that partition. The system high availability status is also shown. It provides a quick overview of the partition, and is displayed when you log in to the chassis partition webUI, or click
from any other area in the chassis partition webUI.
Chassis Partition dashboard
The System Summary section of the partition dashboard shows a graphical view of the chassis showing information about the partition you are in only. Here the default partition has not been divided into partitions, but it is in use and has is using all 8 slots (default setup). The chassis has 4 blades installed into 4 slots and 4 are empty for now. Details on the right summarize how many vCPUs are available, and how many are deployed and in use by tenants in that partition. It can also display configured and provisioned tenants.
The Tenant Overview lists the tenant deployments that are in the partition, the type, the number of vCPUs in use by the tenant, the status, and the management IP addresses. You can click the name of a tenant to view the tenant deployment information. And click the IP address to go to the log in screen of the tenant in a new browser window. The View All button lists all of the tenants on a separate screen with paging if needed.
The High Availability Status for the partition shows that the partition is being backed up on the active system controller. On the dashboard, Redundant indicates the backup and Auto means use the active controller.

Diagnostics overview

Both the system controller webUI and the chassis partition webUIs include Diagnostics tasks that you can perform. These tasks are for running system reports called QKViews, which contain configuration files, logs, and other information useful for diagnostics.
You can upload QKViews to F5's iHealth server where you can get help with understanding any issues you may be having on your system, and ensure that it is operating at its maximum efficiency.

Save iHealth credentials from the webUI

Before you begin, you need to have previously registered with F5 iHealth and have your account credentials available.
iHealth enables you to verify the proper operation of your VELOS system and ensure that your hardware and software are functioning properly. By providing customized diagnostic information, iHealth lets you to take recommended actions, and in many cases, can help you resolve common configuration issues.
You can save one set of iHealth credentials on the VELOS system.
  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
    iHealth Credentials
  3. Type your iHealth username and password, and click
The system saves your iHealth credentials. These are used when you want to upload QKView reports to the iHealth site.

Generate QKView reports from the webUI

If you have any concerns about your system operation, you can generate a QKView system report to collect configuration and diagnostic information from the VELOS system. The QKView report contains machine-readable (JSON) diagnostic data and combines the data into a single compressed tar.gz format file. You can upload the QKView file to F5 iHealth where you can get help to verify proper operation of the system and with troubleshooting any issues you are having.
You can generate a system controller QKView from the system controller webUI, and a chassis partition QKView from the chassis partition webUI. Both contain diagnostic information such as configuration data, log files, 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
    System Reports
    The System Reports screen is displayed. A list of QKView reports that were previously generated is shown along with any reports that were uploaded to iHealth.
  3. To generate a system report, click
    Generate QKView
    The system runs many commands to collect the diagnostic information, so generating the report may 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 says
    File generated successfully
    when it is done.
  4. If you want to upload the report to the F5 iHealth server, select the check box next to the QKView name, and click
    Upload to iHealth
    The system must have Internet access to ihealth-api.f.5 using the HTTPS/443 remote service/port.
    The QKView tar file is uploaded to iHealth where you can get help to diagnose the health and proper operation of the system.