Bug ID 775733: /etc/qkview_obfuscate.conf not synced across blades

Last Modified: Sep 14, 2023

Affected Product(s):
BIG-IP All(all modules)

Known Affected Versions:
13.1.1,,,,, 13.1.3,,,,,,, 13.1.4,, 13.1.5,, 14.0.0,,,,,, 14.0.1,, 14.1.0,,,,,, 14.1.2,,,,,,,,, 14.1.3,, 14.1.4,,,,,,, 14.1.5,,,,,, 15.0.0, 15.0.1,,,,

Fixed In:

Opened: Apr 23, 2019

Severity: 3-Major


By default, sensitive data, such as SSL keys, are excluded from QKView files. However, in some cases you may want to include sensitive information in the QKView file, so it must be obfuscated it for security purposes. (Note: For information on how to configure this feature, see K55559493: Obfuscating sensitive data in a QKView file :: https://support.f5.com/csp/article/K55559493.) In high availability (HA) configurations, the /etc/qkview_obfuscate.conf file is not copied to secondary blades on chassis platforms during sync operations.


Potentially sensitive information could be uploaded to iHealth or F5 Support. This occurs because qkview acts differently if there is an obfuscate.conf on the active by automatically gathering the same information on the blades, but not obfuscating that sensitive data.


-- Run qkview. -- Upload qkview file to iHealth.


Manually copy /etc/qkview_obfuscate.conf to all blades. Note: Do not upload sensitive data to iHealth or F5 Support. If you are obfuscating data, make sure to complete this step for every blade.

Fix Information

/etc/qkview_obfuscate.conf is now synced across all blades.

Behavior Change

Guides & references

K10134038: F5 Bug Tracker Filter Names and Tips