Issues getting second F5 to answer on real world IP

Hi Tom,

 

 

I agree with Michael. This smells like a routing/SNAT issue to me. If the virtual is being marked up on the LTM and is receiving traffic destined for that virtual, the LTM should be sending the traffic to the relevant pool. If you are not SNATing traffic at the virtual, only the destination address will be changed (to the selected pool member's IP). If the pool member then receives traffic that has a source address of the virtual IP, it will try to return it via it's default route (unless there is a more specific one specified). The LTM will drop the traffic at this point.

 

 

I think if you've got the ASA properly forwarding the traffic to the LTM, you've made it over the biggest hurdle. Two last questions: what type of virtual are you using? I'm assuming this is HTTP traffic, did you double check that you have an HTTP profile associated with the virtual?

 

 

Hope this helps,

 

 

-George