BugZero found this defect 201 days ago.
Data sources
All data on this page is proprietary to BugZero® or gathered from public sources
5/17/2024
BIG-IP
BIG-IP AFM
BIG-IP APM
BIG-IP ASM
BIG-IP DNS
BIG-IP GTM
BIG-IP LTM
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
No fixed releases provided.
Bug ID 1389401: Peer unit incorrectly shows the pool status as unknown after merging the configuration ... 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. ... 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 "...