Last Modified: Sep 13, 2023
Affected Product(s):
BIG-IP GTM, Install/Upgrade
Known Affected Versions:
11.0.0, 11.6.0 HF1, 11.6.0 HF2, 11.6.0 HF3, 11.6.0 HF4, 11.6.0 HF5, 11.6.0 HF6, 11.6.0 HF7, 11.6.0 HF8, 11.5.1 HF1, 11.6.1 HF1, 11.5.1 HF2, 11.6.1 HF2, 11.5.1 HF3, 11.5.1 HF4, 11.6.2 HF1, 11.1.0, 11.2.0, 11.3.0, 11.4.0, 11.4.1
Fixed In:
11.6.0, 11.5.1 HF5, 11.4.1 HF4, 11.3.0 HF9
Opened: Dec 05, 2013 Severity: 2-Critical Related Article:
K15251
Reverting a GTM monitored LTM from 11.x to 10.2 might mark down some virtual servers. When the GTM is upgraded to version 11.3.0, downgrading or rebooting the LTM to 10.2.4, results in some of the virtual servers remaining red (down). When a reboot occurs, the ltm-name field in the GTM configuration includes the folder name: /Common/vs.name.route.domain, and the LTM has been rolled back to a version in which folders were not supported, so the names do not match.
Because the ltm-name no longer matches, the virtual server is marked down. Furthermore, since the virtual server is not in the same route domain, a simple addr:port lookup fails and the virtual server's monitor request times out.
This typically occurs when a virtual server is added in a software version that supports the folder structure that names virtual servers as follows: /Common/vs.name.route.domain.
Prior to rolling the LTM back to 10.x, edit the configuration on the GTM and remove '/Common/' from the ltm-name fields of the monitored virtual servers.
An additional attempt is made to match virtual servers by addr:port, even if there is an LTM Name that does not match.