QuestionQ24

VerifiedIdentify the reason load balancing is not working as expected

A BIG-IP Administrator configured a virtual server with a pool containing 3 members and chose the Round Robin load-balancing method to distribute traffic evenly among the pool members. During initial testing, traffic was not distributed evenly, and pool member 172.16.20.3 received more traffic than the other pool members.

Refer to the exhibit and the virtual server configuration below:

Question Image

ltm virtual http_vs \{  
  destination 10.10.1.100:http  
  ip-protocol tcp  
  mask 255.255.255.255  
  persist \{  
    source_addr \{  
      default yes  
    \}  
  \}  
  pool http_pool  
  profiles \{  
    tcp \{)  
  \}  
  serverssl-use-sni disabled  
  source 0.0.0.0/0  
  source-address-translation \{  
    type automap  
  \}  
  translate-address enabled  
  translate-port enabled  
\}  

What is the most likely cause of this behavior?

Explanation

Source-address persistence is enabled. After an initial connection is assigned, subsequent connections that match the persistence record are sent to the same pool member rather than being newly selected by Round Robin, which can produce uneven member traffic totals. F5 notes that a persistence profile can prevent Round Robin from distributing traffic evenly.

Learn more

Community Discussion

No comments yet. Be the first to start the discussion!