Once you have created a profile for a specific type of traffic, you implement the profile by associating that profile with one or more virtual servers.
You associate a profile with a virtual server by configuring the virtual server to reference
the profile. Whenever the virtual server receives that type of traffic, the BIG-IP® system applies the profile settings to that traffic, thereby controlling its
behavior. Thus, profiles not only define capabilities per network traffic type, but also ensure
that those capabilities are available for a virtual server.
Because certain kinds of traffic use multiple protocols and services, users often create multiple profiles and associate them with a single virtual server.
For example, a client application might use the TCP, SSL, and HTTP protocols and services to send a request. This type of traffic would therefore require three profiles, based on the three profile types TCP, Client SSL, and HTTP.
Each virtual server lists the names of the profiles currently associated with that virtual
server. You can add or remove profiles from the profile list, using the BIG-IP Configuration utility.
Note that the BIG-IP system has specific requirements regarding
the combinations of profile types allowed for a given virtual server.
In directing traffic, if a virtual server requires a specific type of profile that does not
appear in its profile list, the BIG-IP system uses the relevant default profile,
automatically adding the profile to the profile list. For example, if a client application sends
traffic over TCP, SSL, and HTTP, and you have assigned SSL and HTTP profiles only, LTM
automatically adds the default profile tcp to its profile list.
At a minimum, a virtual server must reference a profile, and that profile must be associated
with a UDP, FastL4, Fast HTTP, or TCP profile type. Thus, if you have not associated a profile
with the virtual server, the BIG-IP system adds a
default profile to the profile list.
The default profile that the BIG-IP system chooses depends on the configuration of the
virtual server’s protocol setting. For example, if the protocol setting is set to UDP, Local
Traffic Manager adds the
profile to its profile list.