Last Modified: Apr 28, 2025
Affected Product(s):
BIG-IP LTM
Known Affected Versions:
11.4.1, 11.5.0, 11.5.1, 11.5.1 HF1, 11.5.1 HF2, 11.5.1 HF3, 11.5.1 HF4, 11.5.1 HF5, 11.5.1 HF6, 11.5.1 HF7, 11.5.1 HF8, 11.5.1 HF9, 11.5.1 HF10, 11.5.1 HF11, 11.5.2, 11.5.2 HF1, 11.5.3, 11.5.3 HF1, 11.5.3 HF2, 11.5.4, 11.5.4 HF1, 11.5.4 HF2, 11.5.4 HF3, 11.5.4 HF4, 11.5.5, 11.5.6, 11.5.7, 11.5.8, 11.5.9, 11.5.10, 11.6.0, 11.6.0 HF1, 11.6.0 HF2, 11.6.0 HF3, 11.6.0 HF4, 11.6.0 HF5, 11.6.0 HF6, 11.6.0 HF7, 11.6.0 HF8, 11.6.1, 11.6.1 HF1, 11.6.1 HF2, 11.6.2, 11.6.2 HF1, 11.6.3, 11.6.3.1, 11.6.3.2, 11.6.3.3, 11.6.3.4, 11.6.4, 11.6.5, 11.6.5.1, 11.6.5.2, 11.6.5.3
Fixed In:
12.0.0
Opened: Oct 30, 2014 Severity: 3-Major Related Article:
K04014438
When a UCS file with ZebOS.conf is restored, the running configuration for the routing protocols (ZebOS) does not get refreshed/reloaded with the configuration from ZebOS.conf in the UCS file.
Without any warning to indicate that the desired configuration from the restored ZebOS.conf is not the running config, there would be unintended network related misconfiguration
The ZebOS.conf file in the UCS file has a different configuration settings from that of the running configuration for the routing protocols in ZebOS.
Restart tmrouted.
The tmrouted is restarted whenever a UCS file is restored in the BIG-IP system. The routing protocols will pick the changes from the ZebOS.conf restored from the UCS file.