{"id":863,"date":"2014-11-18T12:39:00","date_gmt":"2014-11-18T12:39:00","guid":{"rendered":"https:\/\/fir3netwp.gmsrrpobkbd.com\/2014\/11\/18\/gtm-monitor-connections-not-being-established\/"},"modified":"2021-07-31T16:47:39","modified_gmt":"2021-07-31T16:47:39","slug":"gtm-monitor-connections-not-being-established","status":"publish","type":"post","link":"https:\/\/www.fir3net.com\/Loadbalancers\/F5-BIG-IP\/gtm-monitor-connections-not-being-established.html","title":{"rendered":"GTM – Healthcheck Monitor Connections not being Established"},"content":{"rendered":"

Issue<\/h2>\n

You may observe GTM Monitors failing with a message of ‘state: timeout’ within the logs messages. On further investigation you find that though the GTM is trying to build the connection (i.e sending the SYN), there is no response (SYN-ACK) from the destination. Resulting in the probe attempt failing.<\/p>\n

Reason<\/h2>\n

The reason for this is due to the GTM sending the connection request to a server that already has an established socket open from the GTM for the given source port.<\/p>\n

Consider the following setup,<\/p>\n