Loading...
Loading...
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.
Virtual servers that match these conditions are marked down.
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.
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.
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.
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.