Bug ID 870357: Could not find a monitor instance of type /Common/bigip monitoring.

Last Modified: Jun 06, 2024

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

Known Affected Versions:
13.1.1,,,,, 13.1.3,,,,,,, 13.1.4,, 13.1.5,, 14.1.0,,,,,, 14.1.2,,,,,,,,, 14.1.3,, 14.1.4,,,,,,, 14.1.5,,,,,, 15.1.0,,,,,, 15.1.1, 15.1.2,, 15.1.3,, 15.1.4,, 15.1.5,, 15.1.6,, 15.1.7, 15.1.8,,, 15.1.9,, 15.1.10,,,

Opened: Jan 17, 2020

Severity: 4-Minor


GTM logs an error message for GTM BIG-IP virtual server without BIG-IP monitor: err gtmd[9402]: 011ae10d:3: Could not find a monitor instance of type /Common/bigip monitoring on server:vs /Common/my_vs


Confusing error log message.


Multiple virtual servers configured with the same IP/Port and GTM receives a BIG-IP monitor response for this IP/port. This issue can also occur when a 'depends-on' configuration is applied to a second virtual server which has a non-BIG-IP monitor configured on it. For example: gtm server test { addresses { } datacenter dc1 monitor BIG-IP virtual-servers { vs1 { destination } vs1_other { depends-on { test:vs1 } destination monitor gateway_icmp } } }


- Add a BIG-IP monitor to the virtual servers. - Suppress the messages using a log filter with no publisher. tmsh create sys log-config filter drop_011ae10d message-id 011ae10d source gtmd

Fix Information


Behavior Change

Guides & references

K10134038: F5 Bug Tracker Filter Names and Tips