F5CABR: F5 Certified Administrator, BIG-IP RecertificationDemo

By F5 · Question Mode

QuestionQ15

High Availability and Failover

Question Image

Refer to the exhibit above.

The BIG-IP Administrator runs the command shown and observes a device trust issue between BIG-IP devices in a device group. The issue prevents config sync on device bigip3.local.

What is preventing the config sync?

  • A Time Delta to local system is 12
  • B Both devices are standby
  • C Next Active Load factor is 0 on bigip1.local
  • D Next Active Load factor is 1 on bigip1.local
Explanation

BIG-IP device trust between members of a device group depends on certificate-based mutual authentication, which requires the system clocks on all devices to stay closely synchronized (F5 recommends configuring NTP identically on every device in the group). When the 'Time Delta to Local Device' value reported by 'show cm device' is non-zero and significant, it indicates a clock skew between the local device and the peer, which breaks the certificate/trust validation process and blocks config sync. HA state (active/standby) and Next Active Load Factor values are used only to determine failover behavior and which device becomes active — they do not affect or block configuration synchronization.

Learn more

Community Discussion

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