Bug ID 1389401: Peer unit incorrectly shows the pool status as unknown after merging the configuration

Last Modified: Jun 25, 2024

Affected Product(s):
BIG-IP AFM, APM, ASM, DNS, GTM, LTM(all modules)

Known Affected Versions:
15.1.5.1, 15.1.6, 15.1.6.1, 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, 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, 17.0.0, 17.0.0.1, 17.0.0.2

Opened: Oct 31, 2023

Severity: 3-Major

Symptoms

The peer unit incorrectly shows the state of pool members as "checking" after merging the configuration from the terminal. Note that these are the same symptoms as ID1095217.

Impact

Pool members are marked with a state of "Checking".

Conditions

This is encountered on BIG-IP releases or Engineering Hotfixes with the fix for ID1297257, if two or more configurations are specified for an already configured pool on the peer device when using the command "tmsh load sys config merge from-terminal". Following is an example: Existing pool: ltm pool http_pool { members { member1:http { address <IP address> monitor http } } } tmsh load sys config merge from-terminal: ltm pool http_pool { members none } ltm pool http_pool { members replace-all-with { member1:http { address <IP address> monitor http } } } This may also occur with a similar configuration using the "merge from-file" operation instead of "merge from-terminal". These symptoms, matching ID1095217, occur in the presence of the fix for ID1297257, which removes the original, incorrect fix for ID1095217.

Workaround

Define all object properties at once (in a single configuration block) instead of multiple times (in multiple configuration blocks) when merging the configuration from the terminal.

Fix Information

None

Behavior Change

Guides & references

K10134038: F5 Bug Tracker Filter Names and Tips