Forum Discussion
TCP monitor on two nodes fail erratically
Good day,
We have a setup of consisting of four LTM's, two for external clients in a dmz, two for internal clients on the local network. Only the internal devices are in a HA group.
Currently some of our external clients need to be redirected to applications on the internal network.
Configuration of external application: External listener Pool with internal node pointing to internal listener/VS Node which is the internal VS We are using icmp/tcp_half_open as part of testing/monitoring
The external VS server runs for days and then fails. Once it failed we disable the node and enable it which marks the monitor as up, it can run for hours/minutes/days and eventually fails again. According to logs we can't reach it via icmp. My first feeling was network related however we have multiple applications created on the same VLAN identical to the troublesome VIP's monitoring with icmp.
Any suggestions?
- MvdG
Cirrus
Hi,
The best way to investigate this issue is creating tcpdumps on both external and internal F5 devices. When it fails, do you see the external F5 send an ICMP? If so, does the internal F5 receives the ICMP? Create a file you can import in Wireshark.
Are there any other devices between external and internal F5? Firewall or router? Can you see something there?
With these kind of issues tcpdump and Wireshark are the tools to use.
Good luck.
Martijn.
Recent Discussions
Related Content
* Getting Started on DevCentral
* Community Guidelines
* Community Terms of Use / EULA
* Community Ranking Explained
* Community Resources
* Contact the DevCentral Team
* Update MFA on account.f5.com