Forum Discussion
AltocumulusConfiguring Pool members in a separate subnet of self IP on a Virtual Server
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.
Hello Franky-frank-reg7 ,
I want to say that in F5 you have a great availabilty to perform all of your approaches like your scenario now between
Cloud and on-prem.
> Firstly , you can achieve your approaches.
you can configure (Virtual servers , self ips ) in different subnets or same subnets , the same with ( Pool members and self ips ) you can do it within same subnet and different subnets as well even if your F5 appliance in a Data center and the servers in another data center.
> Secondly , the only thing controls your process is " Routing " , you can achieve your scenario with proper Routing between on-prem and Cloud if your F5 appliance have the right routes configured on to reach to Servers.
> third , I have done before an implementation between ( Virtual servers , External self-ips , Pool members and internal self ips ) all of this in single interface " One - Arm " deployment I mean , and it works well.
The whole I needed was Very good Vlans and Routing planning , to control the direction of traffic ( in /out ) my F5 appliance.
So Go a head , you can get it , but make sure with each route between two on-prem and Cloud sites.
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.
