QuestionQ194

Identify and Resolve LTM Device Issues

An LTM Specialist must configure a virtual server that distributes connections across a pool of two application servers at 172.16.20.1 and 172.16.20.2. The application servers listen on TCP ports 80 and 443. The application administrators require clients to reach the same node for both HTTP and HTTPS requests during the same session.

Virtual servers vs_http and vs_https have been created and listen on 1.2.3.100:80 and 1.2.3.100:443, respectively.

Which configuration option produces the required behavior?

  • A Create pool app_pool with members 172.16.20.1:any and 172.16.20.2:any Assign app_pool as the default pool for both vs_http and vs_https Disable port translation for vs_http and vs_https
  • B Create pool http_pool with members 172.16.20.1:80 and 172.16.20.2:80 Assign pool http_pool as the default pool for both vs_https and vs_https Disable port translation for vs_https Create an SSL persistence profile with "match across virtual servers" enabled Assign the persistence profile to vs_http.
  • C Create pool http_pool with members 172.16.20.1:80 and 172.16.20.2:80 Create pool https_pool with members 172.16.20.1:443 and 172.16.20.2:443 Assign http_pool as the default pool for vs_http Assign https_pool as the default pool for vs_https Create a source address persistence profile with "match across services" enabled Assign the persistence profile to vs_http and vs_https
  • D Create pool http_pool with members 172.16.20.1:80 and 172.16.20.2:80 Create pool https_pool with members 172.16.20.1:443 and 172.16.20.2:443 Assign http_pool as the default pool for vs_http Assign https_pool as the default pool for vs_https Create an SSL persistence profile with "match across virtual servers" enabled
Explanation

Source address persistence directs a client back to the same node based on its source IP address. With Match Across Services enabled, BIG-IP maintains persistence across virtual servers that use the same virtual address, such as 1.2.3.100 on ports 80 and 443. Separate HTTP and HTTPS pools can be used when both contain the same node addresses. SSL persistence is not suitable for correlating plain HTTP requests with HTTPS requests because it relies on an SSL session ID.

Learn more

Community Discussion

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