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

Steele6599_8766's avatar
Steele6599_8766
Icon for Nimbostratus rankNimbostratus
Mar 25, 2014

SMTP load balancing with Exchange 2010

So I setup the load balancing on our F5 but now have an issue with the receive connectors.. in the past we had different receive connectors on our Hub Transport for different external users. Depend...
application delivery
design
LTM
microsoft
Dayne_Miller_19's avatar
Dayne_Miller_19
Historic F5 Account
Mar 25, 2014

You could take Cory's suggestion one step further and, rather than using SNAT Auto Map, have an iRule pick a SNAT address to use depending on the original source. That would allow you to still have multiple receive connectors based on origin, with a different SNAT address for each origin subnet (or however you do the segregation). If you want an example of such an iRule, let me know and I'll post something.

 

Dayne_Miller_19's avatar
Dayne_Miller_19
Historic F5 Account
Jun 30, 2014
As luck would have it, there's a pretty good example here: https://devcentral.f5.com/s/feed/0D51T00006i7WdGSAU (bottom of the thread). The SERVER_CONNECTED portion would be optional in your case; it's just for logging. If you're matching against networks rather than specific IP addresses, the 'Selective SNAT' iRule example at https://clouddocs.f5.com/api/irules/selectivesnat.html shows how to use a data group to set up one or more network definitions to match against. Keep in mind that SNATing done from an iRule will override whatever the SNAT behavior that's set on the virtual server. Let us know how those work for you!