Bug ID 709471: Azure: A failure to load mcpd configuration during the startup triggers "load sys config default" after an hour, if the config load failure is not corrected.

Last Modified: Sep 13, 2023

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

Known Affected Versions:
12.1.0, 12.1.1, 12.1.2, 12.1.3, 12.1.3.1, 12.1.3.2, 12.1.3.3, 12.1.3.4, 12.1.3.5, 12.1.3.6, 12.1.3.7, 12.1.4, 12.1.4.1, 12.1.5, 12.1.5.1, 12.1.5.2, 12.1.5.3, 12.1.6, 13.0.0, 13.0.0 HF1, 13.0.0 HF2, 13.0.0 HF3, 13.0.1

Opened: Mar 09, 2018

Severity: 3-Major

Symptoms

- An "load sys config default" is reported in /var/log/ltm that wasn't initiated by the user manually. This can break password based SSH connectivity as the default config load wipes out the MCPD configuration.

Impact

User could lose the BIG-IP configuration.

Conditions

- BIG-IP is running in Azure. - A mis-configuration in MCPD on-disk config in /config/*.conf files that fails "load sys config" during the startup. - The broken configuration stays that way for more than an hour. If the "load sys config" failure isn't corrected for an hour, the azure-init vadc startup script loads the default config to correct the problem, thus wiping out user configuration.

Workaround

- If user has access to the BIG-IP, they should try to fix the "load sys config" failure manually by modifying the mcpd configuration in /config/*.conf files. This would prevent the eventual "load sys config default". - If user doesn't have access to the BIG-IP, there isn't really a workaround for this issue.

Fix Information

None

Behavior Change

Guides & references

K10134038: F5 Bug Tracker Filter Names and Tips