Download Qkview ((TOP))
Fritzi Schlicker
When you create a support case with F5 Support, the very first thing they will ask for is a qkview from the system. So, on this post we will go to the basics of generating this diagnostics information.
The qkview utility is an executable program that generates machine-readable (XML) diagnostic data and combines the data into a single compressed Tape ARchive (TAR) format file. You can upload this file, called a QKView file, to BIG-IP iHealth, or give it to F5 Technical Support to help them troubleshoot any issues.
Impact of procedure: The qkview utility runs a large number of commands when collecting information. This behavior may cause an additional performance burden on systems that are already under heavy load.
At the heart of BIG-IP iHealth is the qkview file technology, which provides a running snapshot of your BIG-IP system with up-to-the-minute configuration and diagnostic information. You can quickly download a qkview file from your BIG-IP system, and then upload the file to the BIG-IP iHealth system.
The BIG-IP iHealth system translates the output from your qkview file and displays the content in a customer-friendly format that mimics the familiar BIG-IP Configuration utility. In addition to translating the raw data, the BIG-IP iHealth Diagnostics component of the BIG-IP iHealth system evaluates the logs, command output, and configuration of your BIG-IP system against a database of known issues, common mistakes, and published F5 best practices. The prioritized results provide tailored feedback about configuration issues or code defects and provide a description of the issue, recommendations for resolution, and a link to further information in the AskF5 Knowledge Base.
Not sure what you're asking here. qkview files are stored as /var/tmp/.tgz if you generated it from the command line, or case_number__support_file.tar.gz if you used the gui.If you have uploaded it to iHealth, you view CPU statistics from there, under graphs.However, you can see CPU graphs from the Configuration Utility on the BigIP itself: Overview / Performance / System CPU Usage.
Manages creating and downloading QKviews from a BIG-IP. The qkview utility automatically collects configuration and diagnostic information from BIG-IP systems, and combines the data into a QKView file. F5 Support may request you send or upload this QKview to assist in troubleshooting.
4. For example, to reduce the performance burden of qkview, you can run qkview at the lowest possible priority by typing the following command:
nice -n 19 qkview (it takes some time to finish the qkview)
I did some research and I released that the certificates and privates keys are included in a qkview file.(correct me if i'm wrong). I also checked the parameters of the qkview command through cli (qkview -h) where I wasn't able to spot any parameters in order to exclude the certificates.Does anyone know any way to accomplish that ?
Greetings,You may be thinking of the UCS which does gather SSL certs and keys for backup and recovery. The qkview file may have some meta information about the cert and key files, but not the files themselves.
The error "Error uploading to iHealth" is shown in the BIG-IP GUI after trying to upload qkviews using ihealth script. The following error may be seen in the /var/log/ltm log fileihealth[xxxxx]: Error 200202 getting ihealth diagnostics for /var/tmp/.qkview
1. The BIG-IP administrator will see an error message in the GUI, even though the qkview upload to iHealth was successful.2. The analysis summary of the qkview from iHealth will not show up in the BIG-IP GUI.3. The same qkview file may be uploaded to iHealth twice.
The BIG-IP is configured to use an HTTP proxy (using the db vars proxy.host, proxy.port, proxy.protocol), and a qkview is uploaded to iHealth from the BIG-IP GUI via System -> SupportThe upload progresses to the "Analyzing the last uploaded QKView to iHealth." stage, then fails with the above message.
- It is safe to disregard the error code, as the upload is actually successful once the process has reached the "Analyzing" stage.- If possible, do not configure the BIG-IP to use an http proxy, and upload qkviews directly to iHealth.
BIG-IQ can now push qkviews from managed devices to ihealth.f5.com andprovide a link to the report of heuristic hits based on the qkview.These qkview uploads can be performed ad-hoc or as part of a F5 supportcase. If a support case is specified in the upload job, the qkview(s)will automatically be associated/linked to the support case. In additionto the link to the report, the qkview data is accessible atihealth.f5.com to take advantage of other iHealth features like theupgrade advisor.
In this example, the qkview support command on an F5 always generates a .tgz file in the /var/tmp directory, with the name of the file set to the hostname of the system.So the next thing that needs to be done is the extract the filename and path needs to be read by storing it using an update_env command.
What this command does is lists the files ending in .tgz in the /var/tmp directory, which we know is where the qkview output file is stored.The -1 flag lists the files in long format and one per line.As qkview command overrides the file with the same name each time, we will only get a single line answer.
df19127ead