Platin Bilişim has cooperations with the strongest and leader brands. Our target is not only make a difference on our rivals via our certificated and powerful engineer staff but also; providing IT security products and services for our customers from end to end.

F5 Networks LTM Profiles

Profiles allow BIG-IP LTM systems to effect managed traffic flow that goes through from itself. Also, it allows BIG-IP LTM systems to understand and interpret the supported network traffic types.

BIG-IP systems include a sequence of profiles for wide application and usage examples that include traffic protocol application, connection-session persistence enabling and implementation of client authentication. The following table lists the default BIG-IP LTM profiles that are commonly used:

Protocol Profiles

FastL4: FastL4 profiles are used for Performance (Layer 4), Forwarding (Layer 2) and Forwarding (IP) virtual servers. FastL4 profile can be used to provide sending network traffic in a level of stateless IP with same as IP router.

FastL4 profile is a smaller version of HTTP profile that optimizes the controlled traffic conditions. It can be used with only performance HTTP virtual server. It is designed to reduce the connection numbers to the servers and speed up some of the HTTP connection types.

TCP: TCP profiles are the configuration devices that help you manage the TCP network traffic. Most of the configurations of TCP profile are standard SYSCTL setting types. Other configurations are special for BIG-IP system.

TCP protocols are important because they are required to apply certain profile types. For Instance,

You can benefit from various traffic management features that are shown below by applying TCP, HTTP, rewrite, HTML and OneConnect profiles together with permanence profile:

  • Content spooling for reducing server load.
  • OneConnect to minimize server-side connection
  • Layer 7 session persistence
  • iRules for managing HTTP traffic
  • HTTP data compression
  • Rewriting HTTP orientation

           BIG-IP system includes some TCP profiles that are configured before and you can use them as they are. It includes TCP profiles that are configured before to optimize LAN and WAN traffic in additional to assumed TCP profiles. You can use profiles that are configured before as they are or you can create a new profile which is based on a profile that is configured before. You can adjust values that are in profile settings in a most suitable way for your certain network area.

UDP: It is required to use an UDP profile at standard UDP virtual servers.

SCTP: Stream Control Transmission Protocol is a L4 transmission protocol that is designed for message based applications which conveys signal data’s.


OneConnect Profile

OneConnect profile can increase the performance by minimizing open connection numbers and reducing the connection setup delay between BIG-IP system and pool members.

OneConnect profile protects connection pool that is created from configured pool members. New client connections use this current pool member connections when configuration allows and there is an idle connection appears at the connection pool. Load balancing can be done independently from each client’s request at the HTTP connection when it is used together with HTTP profile.


  F5 suggests you to think the following effects and limitations that are shown below before using OneConnect profile:

  •  OneConnect is designed to work with traffic that can be controlled by BIG-IP system in L7
  •  OneConenct requires to use one HTTP profile for handling HTTP traffic. When using the assumed OneConnect profile, pool member doesn’t trust the IP address information at network headers for representing source of response correctly. X-Forwarded-For choice at one HTTP profile should be used to send client IP address by using one HTTP header.
  •  Some applications which use connection-based identity correction like NTLM, can require additional profiles or can’t be suitable with OneConnect.

HTTP Profile

HTTP Profile activates HTTP features at iRules and BIG-IP LTM policies. It is required to use other HTTP profile types like HTTP compression and web acceleration.  


        Some options in HTTP profile content;

  • Response chunking:  It changes BIG-IP LTM’s one response behavior that chunks from server.
  • Redirect Rewrite allows changing or removing of redirects which is sent from BIG-IP LTM’s pool members to prevent steering of clients to the unacceptable or unmanaged URLs. This is disabled by default.
  • Insert X-Forwarded-For is used to add client IP information requests into the HTTP header.

HTTP Compression Profile

An HTTP compression profile can facilitate BIG-IP LTM to compress response content which leads to a significant decrease in network traffic. Despite data compression can done from many web server, the usage of BIG-IP LTM for load balancing applications to compress traffic can help to minimize server load and increase total capacity.

Web Acceleration Profile

A web acceleration profile activates cache taking behavior at BIG-IP LTM according to instructions that are specified in RFC 2616. If you use HTTP compression and you have lots of static contents, web acceleration is especially suggested. Because, Big-IP LTM can take compressed response to the cache and web acceleration causes server load to decrease.

SSL Profile

  BIG-IP LTM supports the encryption of the flows between client side and server side at the certain proxy virtual servers. Client SSL profiles encrypt and decrypt client side flows. Server SSL profiles encrypt and decrypt server side flows.

SSL Access is a term that occurs when any SSL profile can’t be activated in one virtual server and pool members wait SSL. At this point, no L7 profiles may be used.