Bug ID 440205: Reverting a GTM monitored LTM from 11.x to 10.2 may mark down virtual servers

Last Modified: Apr 28, 2025

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

Known Affected Versions:
11.3.0, 11.4.1

Fixed In:
11.6.0, 11.4.1 HF4, 11.3.0 HF9

Opened: Dec 09, 2013

Severity: 2-Critical

Related Article: K15251

Symptoms

If there is an LTM virtual server with a dot ( . ) in the name that is not in the same route domain as the self-IP address that the GTM uses to connect to the LTM, the virtual server is marked down.

Impact

Virtual servers that match these conditions are marked down.

Conditions

This occurs because the ltm-name field in the GTM configuration includes the folder name, for example, '/Common/vs.name.route.domain', and the LTM virtual server has been rolled back to a software version that did not support folders, so the ltm-name no longer matches. Furthermore, since the virtual server is not in the same route domain, a simple addr/port lookup fails and the virtual server monitor request times out.

Workaround

Reverting a GTM monitored LTM from 11.x to 10.x, edit the configuration on the GTM and remove '/Common/' from the ltm-name fields of the monitor virtual servers.

Fix Information

The software now attempts to match the name of the LTM 11.x virtual server with a virtual server on a 10.x BIG-IP system, so the virtual servers are not marked down.

Behavior Change

Guides & references

K10134038: F5 Bug Tracker Filter Names and Tips