Forum Discussion
Async traffic issue, need suggestions
IPs have been changed from what we are really using.
These are Virprion 2400s runing BIG-IP 10.2.4 Build 595.0 Hotfix HF3 in a Active/standby cluster
Client on 10.64.69.126/26 is trying to access a pool of servers on the same subnet 10.64.69.95 - 98. Their Virtual server IP is 10.64.69.39/26 it is HTTP port 80 all the way through using SNAT automap on the VS.
What I have seen is that when it fails it appears as though the initial SYN packet gets to the client and the client sends a SYN/ACK back to the F5 but the captures on the F5 do not record it ever seeing this packet, this could be an asyncronous path issue and is not my real question.
In this Scenario the client machine is using a default Gateway of our core, but if I change it to the F5 I am unable to connect to the virtual server at all. I asked f5 about this and the engineer I am working with said that made sense to him since we are using route domains, but I find that strange.
Why can't I use the F5 as my gateway to hit a Virtual server that is on that same f5 in the same route domain I am in? I had assumed I made a configuration mistake, but now I am wondering if this just is not possible.
I do plan to continue talks with F5, but I was hoping someone on her emight have some advice besides that.
Help guide the future of your DevCentral Community!
What tools do you use to collaborate? (1min - anonymous)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