Last Modified: May 14, 2019
See more info
Known Affected Versions:
12.0.0, 12.0.0 HF1, 12.0.0 HF2, 12.0.0 HF3, 12.0.0 HF4, 12.1.0, 12.1.0 HF1, 12.1.0 HF2, 12.1.1, 12.1.1 HF1, 12.1.1 HF2, 12.1.2, 12.1.2 HF1, 12.1.2 HF2, 12.1.3, 13.0.0, 13.0.0 HF1, 13.0.0 HF2, 13.0.0 HF3
13.1.0, 13.0.1, 18.104.22.168
Opened: Jul 12, 2016
Related AskF5 Article: K21551422
The confpp script is invoked to pass TMOS configuration information to other non-TMOS daemons running on a BIG-IP system. When a BIG-IP system is rebooted, if TMOS configuration elements are parsed or configuration changes or other events occur early in the boot process, the corresponding changes may not be propagated to the confpp.dat file and processed by the confpp script. As a result, configuration information may not be propagated as expected to non-TMOS daemons. A common symptom of this issue is that syslog-ng configuration is not updated to reflect the selection of the primary blade in a VIPRION chassis.
Expected configuration settings may not be applied to non-TMOS daemons upon a reboot. For example, syslog-ng configuration may not be updated to include expected logging on the primary blade in a VIPRION chassis.
This issue may occur when booting an affected version of BIG-IP, such as: - Rebooting blades in a VIPRION chassis. - Rebooting a BIG-IP appliance or Virtual Edition instance.
On a running BIG-IP system that shows symptoms of this issue, changing a db variable will trigger the confpp script to run and update the relevant non-TMOS daemons with appropriate settings from the current configuration. To implement this workaround, use the Traffic Management Shell (tmsh) to update a db variable. For example: tmsh modify sys db log.clusterd.level value "Informational" This issue can be avoided by forcing the MCP configuration to be reloaded from configuration files instead of from the MCP binary database (mcpdb.bin). For details, see: K13030: Forcing the mcpd process to reload the BIG-IP configuration.
Configuration data/changes that occur early in the BIG-IP boot process are propagated successfully to non-TMOS daemons by the confpp script.