TCP Profile - extremely pushy F5 (RST after 300 us)

In many environments, the f5 is on the same network as the servers it manages app traffic for. In these cases, we have to use a SNAT profile to ensure traffic routes back through our device, because otherwise the server will respond to the client and the client will ignore it because it did not request data from the server.

For an example of most of our best practices, run the HTTP iapp to create the virtual server. With this it asks guiding questions and then makes all of the necessary objects. Then you also get a great treeview of all config objects used to build a VIP.

Unless your servers use your F5 as their default gateway, SNAT is needed.