Forum Discussion
VS not pass traffic to pool member
Hi Guys, need your insight here. I have a simple topology as this: browser 10.0.1.244 -> vs 10.0.1.204 pool 10.0.2.101 and 10.0.2.101 has a static route 10.0.1.244 255.255.255.255 10.0.1.204 I can only make this work with automap on. If I choose source address translation as "none", the vs stop works. I can see traffic in/out from vs but only in from pool, no out. tcpdump proves it. Could anyone help me on this one?
- Ed_Summers
Nimbostratus
Change your route on the server (10.0.2.101) for 10.0.1.244/32. The next-hop should be the BIG-IPs self-IP (floating, if available) in vlan 10.0.2.x, not the VIP for the VS.
I'm making some assumptions based on lack of info, but I assume your BIG-IP and server (10.0.2.x) are on the same network.
The route that you have specified (10.0.1.244 255.255.255.255 10.0.1.204) has a next-hop that is not on a directly-connected network of the server. This won't work unless the server can recursively find a route that provides a next-hop on a connected network. I'm assuming your BIG-IP has a self-IP in the 10.0.2.x network, as when you enable auto-map the BIG-IP will (preferentially) SNAT traffic to the floating IP on its egress VLAN.
- Jad_Tabbara__J1
Cirrostratus
Hello Joe,
If you don't want to use Automap, the only thing you need to change is your backend server (node) default gateway.
Please set it to F5_Floating_Internal_Self_IP_Addr and try again. In this way all response from servers will be routed by the BIG-IP.
Regards
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