Last Modified: Oct 06, 2020
See more info
Known Affected Versions:
10.2.4, 11.3.0, 11.4.1, 11.5.1, 11.5.1 HF1, 11.5.1 HF10, 11.5.1 HF11, 11.5.1 HF2, 11.5.1 HF3, 11.5.1 HF4
11.6.0, 11.5.1 HF5, 11.4.1 HF9
Opened: Dec 10, 2013
Related AskF5 Article: K14900
If an GTM VS ltm_name contains a folder, such as /Common/vs.1, and the server is a 10.2.4 or earlier LTM, GTM may not be able to monitor it.
VSes that match the conditions will be marked down because of timeouts.
This can happen if The ltm_name is folderized (Which can happen if the LTM was run at 11.x and regressed or rebooted to 10.2.4). and The GTM VS name does not match the VS name on the LTM. (Which can happen if the VS name on the LTM contains a '.' which will be converted to a '_' by GTM. and The LTM VS is in a different route domain than the LTM's self ip that GTM is using to talk to the LTM. The LTM big3d will be unable to correctly identify the VS in question, and will send no response. This will cause the GTM to mark the VS red when the timeout period has elapsed.
Edit the GTM configuration and either delete the ltm_name field or remove the folder(s) from the ltm_name field and reload the config.
The LTM big3d now correctly identifies and monitors 10.2.4 or earlier LTM virtual servers.