For more information regarding the security incident at F5, the actions we are taking to address it, and our ongoing efforts to protect our customers, click here.

Forum Discussion

RayD's avatar
RayD
Icon for Nimbostratus rankNimbostratus
May 15, 2014

Forwarding to virtual server on another LTM controller

My organization is preparing to run a test and target campaign, where they want to route a small subset of traffic to a new version of the application seamlessly. This works fine if both the old and...
application delivery
devops
iRules
Kevin_Stewart's avatar
Kevin_Stewart
Icon for Employee rankEmployee
May 15, 2014

I may be missing something here, but there's no reason why you can't define a pool on one controller to contain VIP addresses on another controller. SNAT would only be necessary if return routing was an issue.

client -> LTM A VIP -> (pool) -> LTM B VIP -> (pool) -> server

With address translation enabled in each VIP, LTM A will change the destination address to that of the pool member (LTM B's VIP). Traffic arriving at the LTM B VIP will be translated to the server's address. If you don't apply SNAT, then the source address arriving at the server will be the true client address. You then just need to make sure that 1) the server responds back through LTM B, and 2) that LTM B responds back through LTM A, which may require SNATs applied in either or both locations.