Bug ID 1322413: After config sync, FQDN node status changes to Unknown/Unchecked on peer device

Last Modified: Apr 04, 2025

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

Known Affected Versions:
14.1.5.1, 14.1.5.2, 14.1.5.3, 14.1.5.4, 14.1.5.6, 15.1.7, 15.1.8, 15.1.8.1, 15.1.8.2, 15.1.9, 15.1.9.1, 15.1.10, 15.1.10.2, 15.1.10.3, 15.1.10.4, 15.1.10.5, 15.1.10.6, 16.1.0, 16.1.1, 16.1.2, 16.1.2.1, 16.1.2.2, 16.1.3, 16.1.3.1, 16.1.3.2, 16.1.3.3, 16.1.3.4, 16.1.3.5, 16.1.4, 16.1.4.1, 16.1.4.2, 16.1.4.3, 16.1.5, 16.1.5.1, 16.1.5.2, 17.0.0.1, 17.0.0.2, 17.1.0, 17.1.0.1, 17.1.0.2, 17.1.0.3, 17.1.1, 17.1.1.1, 17.1.1.2, 17.1.1.3, 17.1.1.4, 17.1.2, 17.1.2.1

Opened: Jul 20, 2023

Severity: 3-Major

Symptoms

If changes are made to the FQDN node configuration, which has a node monitor configured, and the configuration is synced to a device group, ephemeral nodes generated from the FQDN node may show Availability as “unknown” and Monitor Status as “unchecked”.

Impact

The affected nodes will be displayed with an Availability as “unknown” and Monitor Status as “unchecked”.

Conditions

This may occur on versions of BIG-IP with fixes for ID724824 and ID1006157, under the following conditions: - BIG-IP systems are configured in a device group - The device group is configured for Manual Sync (Full or Incremental) - One or more FQDN nodes are configured with a node monitor (which could be the Default Node Monitor) - A change is made to the configuration of the FQDN node - A Full configuration sync is performed (by a Manual sync with the device group configured for a Full sync, as an automatic fallback/recovery action from a failed Incremental sync, or by using the “force-full-load-push” keyword): tmsh run cm config-sync to-group example-group force-full-load-push

Workaround

To resolve this condition, remove and add the node monitor: - Remove the node monitor from the FQDN node configuration (or from default-node-monitor): tmsh mod ltm node example monitor none (tmsh mod ltm default-node-monitor rule none) - Sync this change to the device group (Incremental sync) - Add the node monitor again to the FQDN node configuration (or to default-node-monitor): tmsh mod ltm node example monitor my_node_monitor (tmsh mod ltm default-node-monitor rule my_node_monitor) - Sync this change to the device group (Incremental sync)

Fix Information

None

Behavior Change

Guides & references

K10134038: F5 Bug Tracker Filter Names and Tips