Forum Discussion
Thanks for the responses.
I'll give you a bit more information so that it might make more sense as to what I need it to do. Each of my VIP interfaces will be connecting to a firewall interface. Today my 10.10.10.X VIP's use the firewall as their default gateway. There is a static default gateway on the LTM as well pointing to the 10.10.10.1 (FW) address. Each "pool server" that has a corresponding VIP on 10.10.10.X uses the 10.10.10.1 route to reach both internal and external networks.
Now I'm adding this second 10.50.50.x network to the LTM as well as to a new Firewall Interface. For inbound connections I'm fine as the FW will have a directly connected network for 10.50.50.x traffic. These 10.50.50.X VIPs will get translated to a backend 10.27.27.x bunch of servers. Internal hosts get to these 10.27.27.x servers via their 10.50.50.x VIP address as well as external hosts use a NAT entry on the FW to get to these same 10.27.27.X machines.
What I need to ensure happens (and I don't know if it's possible or how to do it) is that when a 10.27.27.x machine wants to send traffic to the internal network that it uses the 10.50.50.x FW address (and not the 10.10.10.x address). Since the LTM has a default static route of 10.10.10.1 initially I thought that the LTM would just send it to it's default gateway. If that is how it will do it (traffic sourced from 10.27.27.x will use the 10.10.10.1 gateway after being changed to it's VIP addr of 10.50.50.x) pretty much everything will break.
There were a few options mentioned above that I'd like to explore if you could point me to some documentation as well as giving me your opinion on the cleanest (i.e. easiest) way to accomplish what I need.
In a nutshell: All pools associated with 10.50.50.X VIP's use the 10.50.50.1 gateway and not the default route on the LTM to ensure the traffic goes out the correct interface on the Firewall.
All other pools can use the LTM default to find their way to internal or external netblocks.
Thanks again for helping!