F5 Networks F5CAB5 Dumps - Pass BIG-IP Administration Support and Troubleshooting Exam in 2026

To successfully performSSL offload and re-encryptionon a BIG-IP system, the virtual server must be configured withboth a Client SSL profile and a Server SSL profile. The Client SSL profile enables BIG-IP to decrypt inbound HTTPS traffic from clients, while the Server SSL profile is required tore-encrypt traffic before forwarding it to the pool members.

From the exhibit, the virtual server has aClient SSL profile configured, which allows BIG-IP to accept HTTPS connections from clients. However, there isno Server SSL profile attached, meaning BIG-IP attempts to sendunencrypted HTTP trafficto pool members listening on HTTPS (port 443). This protocol mismatch causes the server-side SSL handshake to fail, resulting in users being unable to connect to the application.

This behavior is well documented in BIG-IP SSL troubleshooting guides: when backend servers expect HTTPS, a Server SSL profile is mandatory to establish a secure connection from BIG-IP to the pool members.

The other options are incorrect:

Removing the Client SSL profile (Option A) would break client-side HTTPS.

The server-side TCP profile (Option B) is unrelated to SSL encryption.

Forward Proxy (Option C) is only used for outbound SSL inspection scenarios.

Therefore, configuring anSSL Profile (Server)is the correct and required solution.

This log entry indicates that multiple monitors are assigned to the pool member, and the member is failing one of them.

Understanding Monitor Logic: By default, if multiple monitors are assigned to a pool or pool member without a 'Minimum To Up' (Availability Requirement) setting, the system requires all monitors to pass for the member to be marked 'Up'.

Analyzing the Log: The log clearly states: [ /Common/http: up, /Common/http2: down; ... ]. This means the standard HTTP monitor is successful, indicating the member is serving HTTP traffic, but the http2 monitor has failed.

Conclusion: Since the http monitor is 'up' but the member as a whole is 'down,' we can conclude the member is successfully responding to standard HTTP requests but not HTTP2 requests. Therefore, the member is currently only serving standard HTTP traffic.

According toofficial F5 documentation (K52015891 -- Troubleshooting BIG-IP power supply issues),hardware-related alerts for power supplies, fans, and chassis components are logged in /var/log/ltm.

When a BIG-IP device experiences a power supply issue---such as failure, intermittent outages, or fan-related faults---the system generates alerts through internal platform monitoring services. These alerts are written to the/var/log/ltmfile and often appear with messages similar to:

Chassis power supply 2 has experienced an issue. Status is as follows: FAN=bad; STATUS=bad.

This makes /var/log/ltm theauthoritative log filefor identifying and verifying power supply and chassis-related problems on BIG-IP systems.

The other log files are not appropriate for this purpose:

/var/log/daemon.logcontains general daemon messages but isnot the primary sourcefor chassis hardware alerts.

/var/log/kern.loglogs kernel-level events, not platform power status.

/var/log/auditrecords administrative actions and configuration changes.

Conclusion:

Per F5-supported guidance, when suspecting power supply outages or chassis hardware issues, the BIG-IP Administrator shouldalways check /var/log/ltm first.

To gather granular Layer 7 data such as specific HTTP methods (GET, POST, etc.) and HTTP status codes (200, 404, 500), the BIG-IP system utilizes the Analytics (AVR) profile.

Analytics Profile (Application Visibility and Reporting): While a standard HTTP profile tracks basic byte counts and requests, the Analytics profile is designed specifically to capture, analyze, and display detailed application performance metrics.

Metrics Captured: When attached to a virtual server, it records URL-level statistics, response codes, page load times, and client-side metrics.

Why not others? * HTTP Profile (Option A): This profile handles the parsing of HTTP traffic but does not provide a built-in reporting dashboard for status code distribution.

Statistics Profile (Option C): This is a legacy profile used for custom user-defined counters and does not automatically categorize HTTP methods or status codes.

Request Adapt (Option D): This is used for integrating with ICAP servers (like virus scanners) and does not perform traffic reporting.

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.