Loading...
Loading...
Pool members may not be marked correctly. They may be marked UP when they should be DOWN, or vice versa.
GTM may not notice that the monitored Pool Member is DOWN, and will leave it marked UP. Pool Members may be erroneously marked UP and used as answers in DNS Responses thus directing clients to unreachable nodes.
If a monitor is configured with a timeout that is less than the interval, such as: gtm monitor external /Common/sample-timeout { defaults-from /Common/external destination *:* interval 10 probe-timeout 22 run /Common/sample_monitor timeout 5 }
Configure monitors with a timeout value that is greater than the interval value.
Fixed an issue where Pool Member health is marked incorrectly.
Click on a version to see all relevant bugs
F5 Integration
Learn more about where this data comes from
BugZero Plan
Streamline upgrades with automated vendor bug scrubs
BugZero Prevent
Wish you caught this bug sooner? Get proactive today.