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

Last Modified: May 23, 2019

Bug Tracker

Affected Product:  See more info
BIG-IP TMOS(all modules)

Known Affected Versions:
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, 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, 13.0.0, 13.0.0 HF1, 13.0.0 HF2, 13.0.0 HF3, 13.0.1, 13.1.0, 13.1.0.1, 13.1.0.2, 13.1.0.3, 13.1.0.4, 13.1.0.5, 13.1.0.6, 13.1.0.7, 13.1.0.8, 13.1.1, 13.1.1.1, 13.1.1.2, 13.1.1.3, 13.1.1.4, 13.1.1.5, 14.0.0, 14.0.0.1, 14.0.0.2, 14.0.0.3, 14.0.0.4, 14.1.0, 14.1.0.1, 14.1.0.2, 14.1.0.3, 14.1.0.4, 14.1.0.5, 15.0.0

Opened: Jun 20, 2018
Severity: 3-Major

Symptoms

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.

Impact

Monitor status on the peer devices is reported incorrectly.

Conditions

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

Workaround

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

None

Behavior Change