301B practice question 7 of 30

An LTM device pair is configured for failover and connection mirroring. The LTM devices are configured with virtual servers for HTTP, HTTPS with SSL offload, and SSH. An event occurs that causes a failover. HTTP and SSH sessions active at the time of failover remain active, but HTTPS sessions are dropped. What is the root cause of this problem?

Full set: 210 questions
Answer options
A: The SSL certificates on the LTM devices do NOT match.
B: Connection mirroring is incompatible with clientssl profiles. Correct answer
C: SNAT automap was NOT enabled for the HTTPS virtual servers.
D: Connection mirroring was NOT enabled for the HTTPS virtual servers.
Correct Answer:
B. Connection mirroring is incompatible with clientssl profiles.
Explanation

Connection mirroring replicates only Layer-4 connection state. The BIG-IP system explicitly does NOT mirror SSL connections that terminate on the device (clientssl/serverssl profiles). When a failover occurs, the standby unit therefore lacks the session keys and SSL context, so HTTPS connections terminate while plain TCP (HTTP) and SSH survive. Hence the root cause is the incompatibility between connection mirroring and clientssl profiles.

Why Incorrect

A. Certificate mismatch has no bearing on connection state replication or failover survival.
C. SNAT settings influence client addressing, not mirroring capability.
D. Mirroring is already globally enabled; HTTPS still drops because SSL is not supported, not due to a per-VS setting.

References

1. F5 BIG-IP TMOS: Redundancy and Mirroring Guide, “About connection mirroring”, p. 5 – lists “SSL connections that terminate on the BIG-IP system are not mirrored.”

2. F5 Knowledge Article K7208, “Which connection types are mirrored?”, Section ‘Unsupported protocols’ – states clientssl connections are excluded.

3. BIG-IP LTM Operations Guide v13, Ch. 16 “Mirroring Limitations”, para. 1 – reiterates SSL termination is not supported for mirroring.

Scroll to Top