NETWORKS-303 practice question 7 of 35

TWO LTM devices are in the same Device Group and configured for Ac live/Standby Failover. The LTM Specialist observes that the HA Active and Standby device constantly changes state. All network links use the default route domain A dedicated fiber ink is used for the HA connection with a latency of 250 ms but no packet loss. What is causing the change in failover state to occur?

Full set: 522 questions
Answer options
A: The HA network is using the default routing domain.
B: The HA network is using multicast IP.
C: The HA network is not configured for mirroring.
D: The HA network latency is too high. Correct answer
Correct Answer:
D. The HA network latency is too high.
Explanation

The BIG-IP high-availability (HA) mechanism relies on timely heartbeat packets exchanged between peer devices over the HA network. The default failover timeout is three seconds. With a one-way latency of 250 ms, the round-trip time is 500 ms. This significant delay can cause heartbeat packets to arrive late, making the peer device assume its partner is down and triggering a failover. When the "down" device's heartbeat eventually arrives, the state can flap back. F5 recommends network latency for HA communication to be well under 100 ms to ensure stability.

Why Incorrect

A. Using the default route domain for HA traffic is a standard configuration and does not inherently cause failover flapping.
B. The default HA heartbeat uses multicast, but on a dedicated fiber link, multicast issues are highly unlikely to be the cause compared to the excessive latency.
C. A lack of mirroring configuration would cause client connections to drop upon failover but would not cause the HA state flapping itself.

References

1. F5 Networks Knowledge Base. (2022). K62232445: BIG-IP HA pair devices may experience unexpected failover when network latency is high. This article explicitly states that high latency can cause missed heartbeats and lead to failover.

2. F5 Networks. (2021). BIG-IP Device Service Clustering: Administration. Chapter 2: "Network Failover". This guide discusses the failover mechanism's reliance on network heartbeats and notes that network issues, including latency, can impact stability. It recommends a low-latency link.

3. F5 Networks Knowledge Base. (2020). K14135: Defining the failover timer values for a BIG-IP device group. This article details the default netfailover timeout of 3 seconds, which a 250ms latency puts at risk.

Scroll to Top