Bug ID 724824: Ephemeral nodes on peer devices report as unknown and unchecked after full config sync

Last Modified: Sep 13, 2023

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

Known Affected Versions:,,,,, 12.1.4,, 12.1.5,,, 13.0.0, 13.0.0 HF1, 13.0.0 HF2, 13.0.0 HF3, 13.0.1, 13.1.0,,,,,,,,, 13.1.1,,,,, 13.1.3,,,,, 14.0.0,,,,,, 14.0.1,, 14.1.0,,,,,, 14.1.2,,,,,,,,, 14.1.3, 15.0.0, 15.0.1,,,,, 15.1.0,,,,,, 15.1.1

Fixed In:
16.0.0, 15.1.2,,,

Opened: Jun 20, 2018

Severity: 3-Major


After a Full Configuration Sync is performed in a device cluster, Ephemeral (FQDN) nodes on peers to the device initiating the Configuration Sync will report their status as Unknown with monitor status of Unchecked. Note: The nodes are still monitored properly by the peer devices even though they are not reported as such.


Monitor status on the peer devices is reported incorrectly.


-- Full configuration sync performed in a device cluster. -- Ephemeral (FQDN) nodes configured.


Any of the following three options will correct reporting status on the peer devices: -- Restart bigd -- Cause monitoring to the FQDN nodes to fail for at least one probing interval, and then restore monitoring accessibility. -- Disable and then re-enable the FQDN node Each of these workarounds results in the reported status of the FQDN node on the peer reporting correctly again. The workarounds do not prevent a subsequent configuration sync from placing the FQDN nodes back into Unknown status on peers, however.

Fix Information


Behavior Change

Guides & references

K10134038: F5 Bug Tracker Filter Names and Tips