F5 BIG-IP LTM Specialist: Maintain and Troubleshoot — Question 25

While investigating the cause of a device failover, an LTM Specialist discovers the following events in /var/log/ltm:
01010029:5: Clock advanced by 518 ticks
01010029:5: Clock advanced by 505 ticks
01010029:5: Clock advanced by 590 ticks
01010029:5: Clock advanced by 568 ticks
01010029:5: Clock advanced by 1681 ticks
01010029:5: Clock advanced by 6584 ticks
01140029:5: HA daemon_heartbeat tmm fails action is failover and restart.
010c0026:5: Failover condition, active attempting to go standby.
Which issue caused the failover?

Answer options

• A. NTP being out of sync
• B. TMM being descheduled
• C. VLAN Fail-safe heartbeats
• D. HA missing heartbeat packets

Correct answer: B

Explanation

The correct answer is B, as the logs indicate that the TMM (Traffic Management Microkernel) was descheduled, leading to a failover event. The other options do not directly correlate with the symptoms presented in the logs, such as clock ticks or the specific failover actions recorded.