
Chapter 4: Configuring the High-Level Network
4-50
Rule-based pool selection
Table 4.9 lists the various criteria you can use when creating a rule to select
a pool.
The following sections describe specific rule statements that you can use to
select pools for load balancing.
Note
You must define a pool before you can define a rule that references the pool.
Pool selection based on HTTP request data
A rule specifies what action the BIG-IP takes depending on whether a
question is answered true or false. A rule may either select a pool or ask
another question. For example, you may want a rule that logically states: "If
the packet data contains an HTTP request with a URI ending in cgi, then
load balance using the pool cgi_pool. Otherwise, load balance using the
pool default_pool".
Figure 4.19 shows a rule with an HTTP request variable that illustrates this
example.
Pool-selection criteria Description
Pool selection based on HTTP
request data
You can send connections to a pool or pools based on HTTP header information you
specify.
Pool selection based on IP
packet header data
You can send connections to a pool or pools based on IP addresses, port numbers,
IP protocol numbers, Quality of Service (Qos), and Type of Service (ToS) levels
defined within a packet.
Pool selection based on one
of operator
You can send connections to a pool or pools based on whether the destination
address is a member of a specific named class, such as one of AOL.
Pool selection based on HTTP
header data (Cache rule)
This type of rule is any rule that contains a cache statement. A cache rule selects a
pool based on HTTP header data. You cannot use it with FTP.
Table 4.9 The attributes you can configure for a rule
rule cgi_rule {
if (http_uri ends_with "cgi") {
use ( cgi_pool )
}
else {
use ( default_pool )
}
}
Figure 4.19 A rule based on an HTTP header variable
Kommentare zu diesen Handbüchern