Posted By biglouie on 01/17/2011 07:20 AM
Ive just done a tcpdump and you were correct, the traffic received on the 4.4.4.4 [backup] interface is being routed out the 100.100.100.100 [primary] interface, so I guess this is why the connections to 4.4.4.4 are failing. Do you know how to remedy this? Looking through the manuals it may need a persistence profile setup but I'm not too sure.
thanks
I had the same setup as you - multiple links, default gateway pool, and Virtual Servers on the different links. Two difference though - I was using inbound wide ips to direct the traffic to the Virtual Servers and I also didn't have all traffic going out only one link.
Since the Virtual Server is automatically mapped to the proper link, the inbound part is working fine. Now, it's up to the pool member (web server) to respond. The pool member should respond to the inside interface of the Link Controller whose job it is to send the response out the proper link.
Assuming you're using the default Auto Last Hop settings (http://support.f5.com/kb/en-us/solu...r=12151666), Link Controller should response to the mac address from which it received the request which I'd expect to be the router for link 4.4.4.4. If you're not using Auto Last Hop, I'd expect Link Controller to use its routing table which likely says to use the 100.x link as long as it's available.
You haven't made any changes to that default behavior, have you? I'm hoping I'm being accurate...it's been a bit since I've used Link Controller. Since you asked about persistence, shall I assume you aren't using any at all right now? Also, are you testing 4.4.4.4 from an outside network?
Finally, might be wise to make a case with support and run them through what you're seeing as I'm confident this has been encountered before.