Symptoms

The peer unit incorrectly shows the state of pool members as "checking" after merging the configuration from the terminal.

Impact

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

Conditions

This is encountered if 2 or more configurations are specified for an already configured pool on the peer device when using the "tmsh load sys config merge from-terminal" command. For example: Existing pool: ltm pool http_pool { members { member1:http { address 10.82.243.131 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 10.82.243.131 monitor http } } }

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

Specifying the configuration for an LTM pool object multiple times when issuing the "tmsh load sys config merge from-terminal" command no longer causes LTM pool members to remain marked with a state of "Checking".

Behavior Change