Bug ID 959613: Double-monitoring a generic-host virtual server might show blank 'Reason'

Last Modified: Jun 06, 2024

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

Known Affected Versions:
12.1.4, 12.1.4.1, 12.1.5, 12.1.5.1, 12.1.5.2, 12.1.5.3, 12.1.6, 14.1.2.8, 14.1.3, 14.1.3.1, 14.1.4, 14.1.4.1, 14.1.4.2, 14.1.4.3, 14.1.4.4, 14.1.4.5, 14.1.4.6, 14.1.5, 14.1.5.1, 14.1.5.2, 14.1.5.3, 14.1.5.4, 14.1.5.6, 15.1.0.5, 15.1.1, 15.1.2, 15.1.2.1, 15.1.3, 15.1.3.1, 15.1.4, 15.1.4.1, 15.1.5, 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.0.0.1, 16.0.1, 16.0.1.1, 16.0.1.2, 16.1.3.4, 16.1.3.5, 16.1.4, 16.1.4.1, 16.1.4.2, 16.1.4.3, 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

Opened: Oct 27, 2020

Severity: 4-Minor

Symptoms

When you double-monitor a Generic Host Virtual Server using the same monitor, the 'Reason' is omitted from the output: -- Output of 'tmsh show gtm server <server> virtual-servers' shows a "blank" reason for monitoring failure/success. -- If double-monitoring at pool level, the output of 'tmsh show gtm pool <type> <pool> members' shows a "blank" reason for monitoring failure/success.

Impact

Impedes your ability to identify the failure/success reason quickly.

Conditions

-- Using the same monitor at virtual-server level and pool level AND/OR: -- Using the same monitor on two different pools (when monitoring the same virtual-server)

Workaround

-- Do not use the exact same monitor on both the virtual server and the pool level. -- If double-monitoring at pool level, do not use the exact same monitor to monitor the same virtual-server on multiple pools.

Fix Information

None

Behavior Change

Guides & references

K10134038: F5 Bug Tracker Filter Names and Tips