Forum Discussion
Cannot ping node IP when configured in route-domain.
- Jan 08, 2019
Just a quick update: after some line by line setup checking, I found the issue.
The route-domain and self-IP are configured on the F5 as a /23 (255.255.254.0) network, however the three servers we were having issues with were configured with only /24 masks.
The health monitoring ICMP packets were being sent from the F5 to the servers and actually arriving, but since the servers IP addresses were in the begining of the /23 network and the self-IP address on the F5 was at the very top end, the servers replys were being sent to it's configured default gateway as it saw the destination was not on the local subnet (due to the incvorrect mask).
The problem arose due the default gateway being a Checkpoint firewall that was dropping the ICMP echo-replies as it did not see the originating echo-requests as they went direct! If this had just been a basic router the traffic would have completed it's jurney back to the F5, albeit by a different path than the outbound echo-request.
We tested changing the network mask on the three effected servers and immediatley they showed as available nodes on the F5.
Thnaks for the replies.
Hi Tony,
You may need an internal Self-ip assigned to the BIG-IP that is within your route domain. This will allow it to route to that pool in a different network. This has worked for me with a similar issue.
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