For more information regarding the security incident at F5, the actions we are taking to address it, and our ongoing efforts to protect our customers, click here.

Forum Discussion

adithyodw_18563's avatar
adithyodw_18563
Icon for Nimbostratus rankNimbostratus
Aug 31, 2015

F5 Pool Members flapping issue

Dear All,   We are facing issue with monitoring of nodes in one of our virtual server pool, however when we check on the server side we didn’t found any discrepancy on server port side. Due to thi...
application delivery
availability
LTM
GaganD's avatar
GaganD
Icon for Nimbostratus rankNimbostratus
Sep 02, 2015

Hi Buddy, Looking at the tcpdump, your F5 is doing a TCP health check on different server ports. Normal behaviour would be that F5 will only try to connect to the port on which member server is listening on. So for example 10.64.32.16 is listening on port 44070, so health checks should only happen on port 44070. Can you confirm what monitor are you using to monitor the node 44070(may be problem is at node level)? If you are using TCP, then I can understand your problem. Please change it to icmp. You can find it out by typing list /ltm node 10.64.32.16 from tmsh