Forum Discussion
Franky-frank-reg7
Altocumulus
AltocumulusConfiguring Pool members in a separate subnet of self IP on a Virtual Server
I have a requirement to configure a virtual server on a BIG-IP LTM appliance which is on prem with one of the pool members is in the cloud. Can someone please comment on how to approach this? Until ...
Yes, that is what Mohammed is saying.
You need SNAT ip (self ip) to have a route to the pool member subnet and also the pool member needs to have a route back to this SNAT ip.
SNAT ip can be floating ip,slef ip , nat pool. I don't know what you are using.
Franky-frank-reg7Altocumulus
AltocumulusThanks for prompt reply, Mohammed. Can you be a bit more specific? Are you saying the routing between the self IP and pool members in the cloud/separate data center needs to be in place?
Just trying to understand specifically what you're referring to.
Hello Franky-frank-reg7 ,
Yes , you need to define a back route from pool member ( cloud or on-prem ) network to F5 internal self ips network ( that you use it for SNAT )
so I agree with mihaic reply.
> I was very generic in my first reply to show you that you able to achieve your such approaches by correct routing between F5 and other network that communicate with it.
> most of F5 deployments , we put f5 in between external users and internal servers networks (pool members )
So you need to add routes in external networks ( where the data traffic related to users come ) point to F5 ( virtual servers ) and add back routes point to external network.
This is the same between f5 and servers even if ( f5 and servers not in the same data center ) you need to add routes on f5 directs its traffic to servers and back routes from servers network ( pool members ) point to F5 internal self ips.
If it's not clear , let me know ...