Mar 27, 2026 - For details about updated CVE-2025-53521 (BIG-IP APM vulnerability), refer to K000156741.

Forum Discussion

william_taffet_'s avatar
william_taffet_
Icon for Nimbostratus rankNimbostratus
Sep 04, 2018

F5 LoadBalancer - wam-tcp-wan-optimized Profil

Hi guys,   We have set for one of our Pool the "wam-tcp-wan-optimized" for Protocol Profile (Client) to solve instable downloads and connections from far remote locations (from Internet) => Pb sol...
application delivery
big-ip
tbledsoe_232540's avatar
tbledsoe_232540
Historic F5 Account
Oct 18, 2018

As the BIG-IP is a full proxy there's actually two tcp profiles to consider - server facing and client facing. In general, server side gets a LAN (low latency & no congestion) profile and client side would get the WAN profile (higher latency and a better chance of congestion). To start with, I would consider building two virtual servers; one for internal connections LAN/LAN and one for external connections (LAN/WAN) for server/client connectivity.

 

If you haven't already, read everything on DevCentral by Martin Duke. In particular:

 

https://devcentral.f5.com/articles/stop-using-the-base-tcp-profile

 

AND

 

https://devcentral.f5.com/articles/tuning-the-tcp-profile-part-one

 

Of course, tuning the BIG-IP is only part of the solution, tuning the server (pool members) and potentially your client systems can have dramatic results.