Forum Discussion
Thank you so much Simon and boneyard!
I did quite some reading. Now I understand your initial suggestion a lot better.
It seems a second F5 will be needed to perform source NAT for outbound communication sessions so all departing traffic carries the IP of the inbound F5, or original VIP address. Maybe one day there will be a F5 device that can handle both inbound and outbound sessions?
Armed with the understanding, I'll engage our F5 team to devise a solution to our Middleware challenge.
> It seems a second F5 will be needed to perform source NAT for outbound communication sessions so all departing traffic carries the IP of the inbound F5, or original VIP address. Maybe one day there will be a F5 device that can handle both inbound and outbound sessions?
I don't understand where you got that idea from. It is perfectly feasible to implement this in a single LTM device. As I say, this is very common and does not require multiple BigIP devices.