Forum Discussion
NimbostratusRound Robin Translation IP for Outbound Connections for SNAT Pool
Hi,
Please let me know if its possible to configure multiple translation IP's for a single SNAT Pool such that, for every outbound connection which originates from back end servers (origins), translation IP which goes as source IP is chosen in a round robin manner?
e.g. If we have multiple instances of a server initiating outbound connections via F5 using a SNAT pool configured with multiple translation IPs, is it possible that F5 selects translation IPs (Which shall be public IPs) in a round robin fashion? That would also mean, if a same instance retries connections, every time new translation IP should be used as source address.
Shall really appreciate any comment.
-Ayush
2 Replies
JinshuCirrus
BIG IP select the SNAP pool member based on least connections method which is perfect for the env which gets lots of connections.
If you still want to change it, you can try creating an irule with snat string.
-Jinshu
- jain_ayush09_29
Hi Jinshu,
I get your point. But let's say we have just a couple of connections from our internal servers going out via F5 using public translation IP's. There can be a case where destination can blacklist a particular translation IP. That's why we needed a mechanism where consecutive connection retry from our internal server is successful using another translation IP, hence round robin. Please let me know if its feasible? (Otherwise F5 might always allocate translation IP which has no connection, & we may not be able to establish connection)
-Ayush
