Last Modified: Feb 17, 2023
Affected Product:
See more info
BIG-IP LTM
Known Affected Versions:
14.1.0, 14.1.0.1, 14.1.0.2, 14.1.0.3, 14.1.0.5, 14.1.0.6, 14.1.2, 14.1.2.1, 14.1.2.2, 14.1.2.3, 14.1.2.4, 14.1.2.5, 14.1.2.6, 14.1.2.7, 14.1.2.8, 14.1.3, 14.1.3.1, 14.1.4, 14.1.4.1, 14.1.4.2, 14.1.4.3, 14.1.4.4, 14.1.4.5, 14.1.4.6, 14.1.5, 14.1.5.1, 14.1.5.2, 14.1.5.3, 15.1.0, 15.1.0.1, 15.1.0.2, 15.1.0.3, 15.1.0.4, 15.1.0.5, 15.1.1, 15.1.2, 15.1.2.1, 15.1.3, 15.1.3.1, 15.1.4, 15.1.4.1, 15.1.5, 15.1.5.1, 15.1.6, 15.1.6.1, 15.1.7, 15.1.8, 15.1.8.1, 16.1.0, 16.1.1, 16.1.2, 16.1.2.1, 16.1.2.2, 16.1.3, 16.1.3.1, 16.1.3.2, 16.1.3.3
Opened: Oct 12, 2021
Severity: 4-Minor
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 file ihealth[xxxxx]: Error 200202 getting ihealth diagnostics for /var/tmp/<hostname>.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 -> Support The 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.
None
