F5 Updated F5CAB5 Exam Questions and Answers by kyle

When troubleshooting intermittent connection resets on a "busy" Virtual Server, the administrator must examine the configured thresholds62. A "Connection Limit" is a hard cap on the number of concurrent connections a Virtual Server or pool member can handle63. If this limit is set too low, the BIG-IP will reset any new connection attempts once the threshold is reached64. The key indicator in this scenario is that the problem only affects "some users" and happens when the server is "busy," suggesting that the system is hitting a capacity ceiling rather than suffering from a persistent configuration error65. Unlike a missing SSL profile, which would likely cause all connections to fail, or a "Connection Rate Limit," which throttles how fast connections arrive, a "Connection Limit" focuses on the total volume66. Identifying this as the cause requires reviewing the Virtual Server's statistics to see if the "Current Connections" count is consistently peaking at the configured limit value.

To utilize the F5 iHealth service, a BIG-IP Administrator must generate a diagnostic snapshot of the system known as a QKView file.

GUI Path: In the BIG-IP Configuration Utility (GUI), the QKView generation tool is located under System > Support.

Process: On the Support page, the user selects the "New Support Snapshot" button. From there, they ensure "QKView" is selected. Once the BIG-IP finishes collecting the data (which includes logs, configuration, and hardware statistics), the user can download the resulting .qkview file directly to their local machine.

iHealth Integration: This file is then uploaded to ihealth.f5.com. The Upgrade Advisor tool within iHealth specifically parses this QKView to check the current configuration against known bugs, hardware limitations, or syntax changes in the target TMOS version.

Evaluation of Other Options:

System > Configuration (Option B): This section contains general system settings like DNS, NTP, and SNMP, but does not contain diagnostic tools.

System > Software Management (Option C): This is where new TMOS images (.iso files) are uploaded and installed, but it is not used for generating diagnostic reports.

System > Archives (Option D): This is used to create and manage UCS (User Configuration Set) files, which are full system backups. While UCS files contain configuration, they do not contain the deep diagnostic logs and hardware stats required by iHealth for an Upgrade Advisor analysis.

When a health monitor marks a member "Down," the goal is to determine if the issue is at the network level or the application level.

Monitor Logging (Option A): In the Pool Member configuration, an administrator can enable "Monitor Logging". This generates a detailed text file in /var/log/monitors/ that shows the exact "Send" string sent by the BIG-IP and the exact "Receive" string (or lack thereof) returned by the server.

TCPdump (Option C): This is the most definitive way to see if the monitor traffic is even leaving the BIG-IP and if the server is responding with a TCP RST (reset) or an ICMP unreachable message. A command such as tcpdump -ni host and port is standard for this task.

Why not others? While the routing table (Option B) is useful for general connectivity, if other members in the same subnet are "Up," the routing is likely fine. Statistics (Option D) show that it is down but rarely why it is down at a protocol level.

This scenario describes a classic network performance issue known as the "Mega-Proxy" problem. When an organization routes all employee traffic through a single proxy server, the BIG-IP sees thousands of unique users as having the exact same source IP address. If the administrator has configured "Source Address Affinity" persistence, the BIG-IP will correctly follow the rule but incorrectly route all users to the same single backend pool member. This creates a severe load imbalance where one server is overwhelmed while others remain idle, leading to poor application response times. To resolve this, the administrator must change the persistence profile to "HTTP Cookie". Cookie-based persistence allows the BIG-IP to place a unique identifier in each user's browser, allowing the system to distinguish between individual sessions even if they share the same source IP. This fix ensures that traffic is distributed evenly across the pool members, restoring4 the expect5ed load balancing functionality and resolving the slow performance reported by users behind the corporate proxy.